Hello,
does anybody has usecase to backup VM by VBR1, vi copy job sent to offsite repository and read image from this repository and restore by VBR2? Environments are completely independent.
My idea is to have script and copy to another folder and with another script make scan and import of images to have permanent solution.
Hello
We occasionally work on projects where we build a Cyber Vault using multiple Data Domains that replicate data between each other using native tools. The vault is located at a separate, independent site and includes its own Veeam server, which can read the repository when needed to perform a restore in a cleanroom environment.
So far, we haven’t automated the process of importing the backups into the second Veeam server, as this would first require breaking the replication, among other steps.
Hi
Hi coolsport00,
no, that the usecase
we build up 2 independent environments, then he requested offsite backup
and now he requested restore cross
so connection is only over offsite possible
even i will put into offsite VBR, then i will have 2 vCenters, …. and flr of linuxes will be not possible, because you cannot set flr appliance for each vCenter, repository, …
so then only manually to switch, when is needed - customer is doing restores over EM.
Oh ok...understood.
No matter what you do there is going to be manual intervention to get the secondary VBR server up and running. You can probably use PowerShell to scan and import the repository.
One potential issue I see is that if one VBR server starts a restore while the other tries to create and incremental backup or synthetic full is that which server gets to the file first will place a lock on it, interrupting the actions of the second VBR server.
Tommy O'Shea yes, one folder as two repositories, so shared between 2 VBRs is not supported generally, which is causing dedup issues and other staff like you described.
another option from support:
Maybe S3 with an Read Only Permission to VBR2 could also work.
Or using the VRO. The Embedded VRO VBR-Server can Map the Backup / Backup Copy Repository in Case if the primary VBR-Server is down.
so looks, that i have, what about to think of …..
CMF option is practical and good, but is costly for DR scenario only.
Suggestion from support are good one as well, but manual reconfiguration required. What is complicated for operation.
Thank you very much to all of all ideas.
I have decided to go with rsync between folder of repository and folder for repository of second VBR with import via script.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
