Salta al contenuto principale

Move and Add existing backup

Thread needs solution

I am confused about the difference between the "Move" option and the "Add existing backup". Do they perform the same action?

0 Users found this helpful

No.  Move is intended to move the destination for a task already shown in the Backup list.  The 'Add existing backup' option is for when you have files that belong to a task not shown in the list but which you want to access via the GUI.

Steve Smith wrote:

No.  Move is intended to move the destination for a task already shown in the Backup list.  The 'Add existing backup' optison is for when you have files that belong to a task not shown in the list but which you want to access via the GUI.

So, as I understand this, "move" will physically move the file to a destination for a task already shown in the Backup list? 

That is correct,

I have found move to be a slow process; I prefer to delete the backup task, then copy the files to the new location using TeraCopy, then adding the backup task back in. This maintains the date stamp on the files, whereas when moving backups using *.tibx architecture the file stamp was changed to the date the files were moved. [This may have been fixed after I discovered this unwanted behaviour.]

Ian

I agree with Ian on this. I found Move to be very slow indeed.