VeeamON 2024 - Use Code "COMMUNITY10" for 10% Off!
@coolsport00I am a bit confused by this statement in your post.“you can indeed use Replica From Backup and use those Copy Job backups on the SOBR to Seed your Replica job VMs”What do you mean by “Replica From Backup” ? How is this different from a regular replication job and where do you configure it that allows you to use the backup or backup copy on a SOBR? Never mind. See it now under “Source” under the Virtual Machines tab when configuring the replication job. You are correct, a bit confusing. You can set up the replication job to use the backup on a SOBR as a source for the replication of VMs but cannot choose it as an option for initial seeding.
Lots of crosstalk here but it seems my original comment about NOT being able to use a backup or backup copy in a SOBR as a source for replication seed is confirmed. I have tested both and confirmed. I can provide screen shots if needed but seems like it is a known issue.
Thanks. I will have to convert everything back to SOBR’s and then retest. I will try to grab screen shots at that point.
I read it initially in point #4 in this post: I was testing in my lab and the backups and backup copies on my SOBR’s did not show up as possible sources for the seeding. After I converted the SOBRs back to individual repositories, the backups on them showed up as possible sources. Not sure if I am doing something wrong with the SOBRs not showing up as sources.
Thanks for everyone’s help. Final process was:Disabled all jobs and backup copy jobs using the repositories on the rebuilt server.Deleted the Proxy on that server from B&R server and then re-added which pushed the required proxy components to the rebuilt server.Added a temp repository to C:\backups on the rebuilt server which pushed the required repository components to that serverRe-discovered the old repository server LUNs via the iSCSI initiator on the rebuilt server and mapped them to the appropriate drive letters.Re-scanned the two repositories that were on the old server and now on the new server. This successfully discovered the repos.Re-enabled backup and backup copy jobs and they appear to be working now.
Got it thanks. Will give it a try and let you know.
Trying this in my lab. The challenge I see is that I cannot remove the server/repository in the B&R server while it is in use by backup/backup copy jobs. I cannot remove it from Managed Servers either while it is defined as a repository/proxy server. So I would have to change all backup and backup copy jobs to not use that proxy or repository prior to delete and re-adding the server in Managed Server and as a Backup Proxy and Backup Repository in the infrastructure. Am I missing something here?
Ok. I understand that part. I was talking more about the repository definition in the B&R server.
Thanks. Sounds like my second question was just answered as well.
Thanks for the response. I was thinking the same thing. The other question I have is whether I would have to delete the repositories currently on that server and then recreate them and rescan to discover the backups on those repositories? It seems likely it will not let me delete the repository server from the B&R server when there are repositories defined on them.
Looks like the upgrade to Cumulative Patch P20210525 may have done the trick. Job is now running without the warnings. Thanks Chris!
No scripts
Pretty basic backup of a single VM. No encryption, no App Aware, no Guest File Indexing. Backing up from NetApp NFS datastore using snapshots. I will get the latest patch and apply.
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
