Comprehensive data protection for all workloads
Post Reply
rizks_2000
Enthusiast
Posts: 77
Liked: never
Joined: Feb 17, 2010 1:12 am
Full Name: Anthony Rizk
Contact:

Veeam Jobs & Subsequent Datastore Migration

Post by rizks_2000 »

Have run successfully voth Veeam replica and Backup jobs. Needed to move VM datastore files to different datastore. Will my Veeam jobs encounter a problem the next time they run? If so, is there an easy config change I can make for those specific jobs or will I have to capture new full synthetic backups and replicas?
Gostev
Chief Product Officer
Posts: 31773
Liked: 7274 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Veeam Jobs & Subsequent Datastore Migration

Post by Gostev »

Anthony, it depends how you are going to move your VMs.

If you use Storage VMotion, it will be seamless for Veeam, as VM ID will not change.

If your procedure involves VM registration once the file are moved to a different datastore, then this would trigger vCenter/ESX to generate new unique ID for your VMs. In that case, it would be best to re-create your backup jobs.
Post Reply

Who is online

Users browsing this forum: Baidu [Spider], Bing [Bot], bluj83, jdb and 59 guests