-
- Enthusiast
- Posts: 52
- Liked: never
- Joined: Jun 15, 2011 9:24 am
- Full Name: Ulrich Menz
- Contact:
Link a moved vm to the Backup repository again
Hi All,
the envrionment are two standalone ESXi Servers.
One Host is out of production, so I have permanently Failover to the replica vm on the other Host.
How to link the actual vm to the Backup Jobs as the old vm to prevent braking the backup chain ? - Is this possible ?
thanks
Ulrich
the envrionment are two standalone ESXi Servers.
One Host is out of production, so I have permanently Failover to the replica vm on the other Host.
How to link the actual vm to the Backup Jobs as the old vm to prevent braking the backup chain ? - Is this possible ?
thanks
Ulrich
-
- Veeam Software
- Posts: 712
- Liked: 168 times
- Joined: Nov 30, 2010 3:19 pm
- Full Name: Rick Vanover
- Location: Columbus, Ohio USA
- Contact:
Re: Link a moved vm to the Backup repository again
Hi Ulrich - Probably the best option is to create a new backup jobs, but leave the old backup jobs in place with their schedule disabled. This will have the previous chain sit in place, if you have the storage. That's the safest.
-
- Veeam Software
- Posts: 21138
- Liked: 2141 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Link a moved vm to the Backup repository again
Since replica VMs have different ID's, they will be treated as new ones and full backup will be performed anyway. You can re-add replicas to existing job or create a new job, as Rick has suggested (and optionally map it to existing chain), in both cases space for the full backup will be required. Existing VM backups will not be touched.
-
- Enthusiast
- Posts: 52
- Liked: never
- Joined: Jun 15, 2011 9:24 am
- Full Name: Ulrich Menz
- Contact:
Re: Link a moved vm to the Backup repository again
Hello,
I feared it.
In the next case it seems better to restore the original VM from the last Backup and use only the modifyed data from the replica.
In this case the chain doent break ?
Ulrich
I feared it.
In the next case it seems better to restore the original VM from the last Backup and use only the modifyed data from the replica.
In this case the chain doent break ?
Ulrich
-
- Veeam Software
- Posts: 21138
- Liked: 2141 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Link a moved vm to the Backup repository again
If you restore the original VM, it will still be registered with the new ID, since technically it is another VM.
-
- Enthusiast
- Posts: 52
- Liked: never
- Joined: Jun 15, 2011 9:24 am
- Full Name: Ulrich Menz
- Contact:
Re: Link a moved vm to the Backup repository again
thanks for this Information - Ulrich
Who is online
Users browsing this forum: Semrush [Bot] and 70 guests