Moving Large Backups between repositories

Hyper-V specific discussions

Moving Large Backups between repositories

Veeam Logoby tym » Thu Mar 16, 2017 11:01 am

Hi,

I am currently moving all backup jobs to a new repository. I know the steps to perform and they are actually working like a charm. However - the biggest backup job is nearly 50TB with a 38TB vbk and a bunch of 500GB vib/vrb. Moving these files takes approx 5 days. 5 days with no backup is not acceptable. Any idea on how I could "smartify" this transfer?

Thanks in advance.
Best,
Tim
tym
Enthusiast
 
Posts: 83
Liked: 9 times
Joined: Thu Mar 26, 2015 9:30 pm
Full Name: Tim Diekhans

Re: Moving Large Backups between repositories

Veeam Logoby v.Eremin » Thu Mar 16, 2017 11:36 am

Continue to backup to the original repository, in the meantime create a backup copy job that will gradually create backup chain in target repository. Once the initial and maybe couple of next backup copy cycles are finished, you can switch the backup job from the original to the new backup repository, mapping it to files created by backup copy job.

Keep in mind, that backup copy job doesn't copy backup chain as a whole, but rather synthetically creates required restore points in "target" location from VM data in source backup repositories. So, data contained in the old restore points won't be copied to target location.

Thanks.
v.Eremin
Veeam Software
 
Posts: 13709
Liked: 1026 times
Joined: Fri Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin

Re: Moving Large Backups between repositories

Veeam Logoby tym » Thu Mar 16, 2017 11:47 am

Hi, just configured this and initial copy is running atm. I did´t understand your last paragraph though. We are doing a synthetic full once a week. Does this mean that the daily incrementals are not copied at all?
tym
Enthusiast
 
Posts: 83
Liked: 9 times
Joined: Thu Mar 26, 2015 9:30 pm
Full Name: Tim Diekhans

Re: Moving Large Backups between repositories

Veeam Logoby v.Eremin » Thu Mar 16, 2017 12:02 pm

I meant that backup copy job (despite its name) doesn't do simple file copy, instead it synthesizes the restore point in target location from VM data in source backup repositories. When initially executed, it will re-create a current VM state captured in the latest backup file, forgetting about its old states present in other backup files. So, don't expect your backup chain to be copied to target location as is.

Kindly, check corresponding User Guide section for more information regarding the said mechanism.
v.Eremin
Veeam Software
 
Posts: 13709
Liked: 1026 times
Joined: Fri Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin

Re: Moving Large Backups between repositories

Veeam Logoby tym » Sat Apr 08, 2017 3:52 pm

Hi, I completed the transfer after a couple of failed attempts. A subsequent incremental was successful, but the transform was not:
08.04.2017 09:38:40 :: Previous full backup chain transformation failed Error: Full point was not found.

What that?

Best,
Tim
tym
Enthusiast
 
Posts: 83
Liked: 9 times
Joined: Thu Mar 26, 2015 9:30 pm
Full Name: Tim Diekhans

Re: Moving Large Backups between repositories

Veeam Logoby Mike Resseler » Mon Apr 10, 2017 5:50 am

Tim,

It means (for some reason) it cannot find the full backup and can't merge an incremental into a new full. I would advise to contact support now (and post your case ID and follow-up here also) so they can look into the logs what went wrong

Mike
Mike Resseler
Veeam Software
 
Posts: 3382
Liked: 384 times
Joined: Fri Feb 08, 2013 3:08 pm
Location: Belgium, the land of the fries, the beer, the chocolate and the diamonds...
Full Name: Mike Resseler


Return to Microsoft Hyper-V



Who is online

Users browsing this forum: No registered users and 1 guest