R&D Forums

We have recently installed a new repository server, using the Veeam iso.
Moving normal backup jobs was easy with Move backup wizard.
But the backups from a copy job do not have the move option.
When trying to perform the move through changing the repository in the job, it says 'Moving backups created by legacy backup copy jobs is not supported,...'
and it wants to start with a new full backup.

I would be OK with starting a new chain, but still need the old backups as well, since this is our archive, holding backups from the last 5 years.
How do i get these old backup to the hardened repo?
I do not have direct file system access, since it is a hardened server.

Hi patrickds,

Legacy Backup copies are indeed a bit of a challenge as you can see that they aren't compatible with newer features like Move and Copy Backup.

A File Copy job of the folder holding the backups will work here -- use the backup folder for that Backup Copy as a source and as a target, place it in the directory holding the backups on the hardened repo. For example:

Old Backup Copy name: "Archival BCJ"
Hardened Repository backup path: /mnt/backups

As the source, select the backups folder "Archival Backup", and as the target, just point it at the hardened repository and for the path use /mnt/backups

Let the file copy complete, then rescan the hardened repository. The backups will be under Backups > Disk (Imported) on the main page.

After some trial and error I think we are getting there.
Old backup chain is on a Scale-Out repository, distributed over 2 shares on a Synology NAS, which does not support File Copy Jobs.
So I used a File Backup job, which lasted a couple of days, with over 20TB of data to be transferred, thinking i could later move all needed files into a new directory, and have that added to the inventory.
But that didn't work out, because the file backup job uses a different file structure to store the backups.

I now discovered I can just use copy/paste from the NAS shares to the Linux server hosting the Hardened repository, in the 'Files' module.
First time I started this, I closed the copy progress window, thinking that it would continue in the background, like with most job windows, but it canceled the copy.
It's now running again, from a console on a different machine, which I can keep open until it's done.

Just a minor issue: the projected time remaining is really off.
Time elapsed: 2:30 hours , Transferred: 500GB, Remaining: 5:00 hours, for a total of 10.8TB.
The backup job lasted about 50hours for each 10TB job, so I am estimating this will be about the same, since it is running at roughly the same speed of 200GB/hour