We are in the process to changing our virtual center. I have been looking at how well Veeam handles this kind of change; the sort answer is it does not support this and we need to re-populate all of the backups and off-site replications.
The issue is I cannot use the backups that were taken from the old virtual center, as seeds to re-populate the new replicas at the DR site. So the uuIDs are the same and the VMDKs are the same, is just that in the new virtual center all of the host-ids, storage-ids and VMids have changed; this metadata is recorded in the .vbm files for each backup.
tsightler wrote:So if you're referring to replication, why not just use replica mapping? Sure the first pass will require a scan to build new hashes, but only changes will be copied across the wire.
For backups it's the same, just use backup mapping. The first pass will have to read the entire VMDK, but any blocks that are already in the backup will not actually be copied.
Vitaliy S. wrote:I'm afraid it will not work, as I've tried to reproduce this scenario in my lab and during the backup job a new image was created due to different moref ID in backup metadata files.
Vitaliy S. wrote:As to the replication job, if you do this, it will wipe out all previous incremental points (as far as I correctly recall it).
tsightler wrote:What do you mean an new image was created? A new VBK?
Users browsing this forum: Bing [Bot] and 4 guests