When I rescan a backup repo, Veeam will import backups. I use this routine quite often across many clients. Unfortunately, when I rescan a DR host, Veeam doesn't import the replicas even though it created them! I know there isn't a VBM or something like that with meta data, but I would like to see that. For example, Veeam depositing a VBM-equivalent for replicas in the datastore folder of the replica that it creates so that a rescan will recreate the Veeam catalog meta data.
If you want to know why this is important, I can elaborate.
-
- Veteran
- Posts: 316
- Liked: 48 times
- Joined: Apr 07, 2015 1:53 pm
- Full Name: James Wilmoth
- Location: Kannapolis, North Carolina, USA
- Contact:
-
- Veteran
- Posts: 316
- Liked: 48 times
- Joined: Apr 07, 2015 1:53 pm
- Full Name: James Wilmoth
- Location: Kannapolis, North Carolina, USA
- Contact:
Re: Feature Request -- Rescan and import existing replicas
Update: So I called support and eventually discovered that when the replica configuration is removed, Veeam drops all the VMs in the job into the Exclusions list. This is what causes the Seeding list to be empty. I was able to remove all but the original exclusions and then confirm that the Seeding tab showed the existing replicas and allowed mapping. So while I still don't have the Home > Replicas tab and existing replicas showing, at least I don't have to worry about duplicate replicas being created.
Who is online
Users browsing this forum: No registered users and 76 guests