1

Alex Pankratov :

Oct 23, 2018

Right-click on the backup entry in main list, select Open Folder > Archive of Deleted Items. More formally it's "$Archive (Bvckup 2)" folder at the top of the backup location,

2

Charlie54 :

Sep 08, 2019

Can we provide a custom location for the archive ?

4

Charlie54 :

Sep 11, 2019

I need the Archive Folder to be on the Source Drive.

Let me explain my scenario.

I have a Drive where I put everything.

Movies
Series
Personal
Personal History

I only need archiving on the personal folder.

So I first do a JOB on the Personal folder only, then run a job on the whole drive.

That way I have my personal archive versioning for when my wife deletes a file without knowing AND i have that same folder backup up to the other drive.

Best

5

Charlie54 :

Sep 11, 2019

So basically, I need to put the archive on the root of the source drive

6

Alex Pankratov :

Sep 11, 2019

This cannot be done if using just one backup job. Items are archived by moving/renaming, this is how the engine is written. Moving within a volume is just a file system index update, it's very quick. Moving across a volume boundary is ultimately a full-blown file copying, which is slow and requires special handling.

So either the archive remains on the backup volume, or you need to set up a secondary job to replicate the archive back to the source volume (with "deletion" set to "don't" and, perhaps, with a post-backup script to nuke the original archive).

7

Charlie54 :

Sep 11, 2019

Ok, I will add a third job in between the personal and full one where I sync the PeronsalHistory the other way around, and then sync the full drive.

So it's basically SOURCE to DESTINATION.
Archive Folder sync from DESTINATION to SOURCE.
Then sync the full drive from SOURCE to DESTINATION.

If you feel like simplifying this scenario in a  future release where we can copy the files to a custom directory.

Best

8

Alex Pankratov :

Sep 11, 2019

I understand why you have it set up this way, but this is not a common scenario by any measure. As such I see no point in supporting it natively.

9

Charlie54 :

Sep 11, 2019

Ok.

The thing is, I have about two weeks of modified history files and sometimes I roll back X days.

So I feel safe knowing the history is also backed up in case of a failure.

Is it hard to make the move command in the other way before synchronizing completely ?

10

Alex Pankratov :

Sep 11, 2019

I don't understand the question.

11

Charlie54 :

Sep 11, 2019

When I synchronize two folders with archive option.

Can't the program move the files that have been modified from destination to a folder in source, then do the synchronization as usual ?

that way people have an option to also backup the files history so that they don't loose anything in case of hardware failure

12

Alex Pankratov :

Sep 11, 2019

Can't the program move the files that have been modified from destination to a folder in source, then do the synchronization as usual ?

It can if the source and destination are on the same volume. Otherwise it cannot, because it's not a move, but rather a copy-then-delete.

13

Charlie54 :

Sep 11, 2019

Than can't it do a copy-then-delete ?

Even if it means that the speed will go down because of the two way sync.

14

Alex Pankratov :

Sep 11, 2019

Everything's possible, it's just a matter of effort required to properly support it. Doing copying requires hooking up the archiving part to the ultra copier routine, adding cancellation support, etc. That's quite a bit of work, which I think is not justified in this case, because very few people will want to keep their archives outside of the backup device.

15

Charlie54 :

Sep 11, 2019

Ok, now I understand how complicated it is.

Thank you for explaining.

I will sync the archive folder in the other way, then redo the sync to the base folder. which will work.

Not sexy, but will work. :)

16

highend :

Jul 29, 2020

Can you make a setup like this possible?

A fixed location on destination with a $time_$date subfolder and no timestamps for deleted / modified files?

The second part is easy, by setting
conf.archive_deleted_tag                           ""
conf.archive_changed_tag                           ""

but
conf.archive                                       R:\#ARCHIVE_VIVALDI\$time_$date
is created literally instead.

I'd like to have this:
R:\#ARCHIVE_VIVALDI\2020-07-29_16-25-56\<all deleted / modified files / folders>
R:\#ARCHIVE_VIVALDI\2020-07-29_17-23-12\<all deleted / modified files / folders>
etc.

The necessary part would (just) be, that conf.archive is able to resolve internal variables...

17

Alex Pankratov :

Jul 29, 2020

Adding support for expandable variables is not hard. The problem is how to handle the archive trimming.

Wait until R82. It will have this done properly.

18

highend :

Jul 29, 2020

Ok, thanks for implementing this. The current solution (many files with a date/time tag) isn't really mine...

19

highend :

Aug 08, 2020

Would it be possible to add (only) the necessary setting to a minor release?

E.g.
ArchiveExpandVars=1

Default would be 0.

This wouldn't harm anybody (it needs to be enabled manually) and the users who'd prefer this kind of folder date-base archive type could already use it now. Yeah, deleting old archive folders automatically would only be available in R82 but it's so easy to take care of this by the user during the waiting period for R82 (it's nothing more than sort these folders in a file manager by ascending name and delete the ones at the bottom that you define as "too old, I'll delete them").

It would really be a massive improvement to how archives can be handled...

20

Alex Pankratov :

Aug 08, 2020

I am not a fan of temporary features. This one, in particular, because it effectively breaks the trimming function. So, no, this is not something that I'm willing to add, sorry.