I'm pushing to get DR Orchestrator but I don't know if it will happen. How would you design a secondary B&R and DB server at a DR site?
My environment:
- Veeam prod and DR infrastructure is on the same NSX network segments spanned between data centers which simplifies a lot (no networking will change in a DR situation)
- DR copies at the second site are created with Veeam copy jobs
My oversimplified ideas:
1) Full DB replication
- Create secondary VBR and DB servers at the DR site
- Do daily copies of the primary VBR config backup to the secondary VBR server
- Configure SQL replication to secondary DB
In a DR situation, just install the backup config on the secondary VBR and start recovery to DR hardware.
2) No DB replication
- Create secondary VBR and DB servers at the DR site
- Add only the DR infrastructure to the second VBR server (proxies, repos, vCenter)
In a DR situation, scan the repositories for latest backups and start recovery to DR hardware.
Anyone have any other ideas/suggestions?
-
- Influencer
- Posts: 18
- Liked: 1 time
- Joined: May 04, 2021 2:46 pm
- Full Name: Bobby Hood
- Contact:
-
- Product Manager
- Posts: 9848
- Liked: 2607 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: How to design a VBR/DB for DR without Orchestrator
Hi Bobby
I would keep it simple, create a configuration backup from the first VBR server and store it in the second site. In the same repository, where you have the copied the backups. If your Database is below 10GB, SQL express will be enough. No need to install an extra DB server.
If you primary site fails, you can import the configuration backup and start restoring the backups. You could also consider using Veeam Replicas (Replica from Backup). Then the configuration backup would be necessary to be able to failover the replicas with the Veeam console on the second VBR server.
Thanks
Fabian
I would keep it simple, create a configuration backup from the first VBR server and store it in the second site. In the same repository, where you have the copied the backups. If your Database is below 10GB, SQL express will be enough. No need to install an extra DB server.
If you primary site fails, you can import the configuration backup and start restoring the backups. You could also consider using Veeam Replicas (Replica from Backup). Then the configuration backup would be necessary to be able to failover the replicas with the Veeam console on the second VBR server.
Thanks
Fabian
Product Management Analyst @ Veeam Software
-
- Influencer
- Posts: 18
- Liked: 1 time
- Joined: May 04, 2021 2:46 pm
- Full Name: Bobby Hood
- Contact:
Re: How to design a VBR/DB for DR without Orchestrator
So the original database isn't required to import the config to the secondary VBR and begin restores? That would greatly simplify things.
-
- Product Manager
- Posts: 9848
- Liked: 2607 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: How to design a VBR/DB for DR without Orchestrator
Hi Bobby
Yes, it's that simple
https://helpcenter.veeam.com/docs/backu ... ml?ver=110
If you want to use replicas, then best practice would be to place the backup server at the secondary site.
But configuration backup restore will also work.
Thanks
Fabian
Yes, it's that simple
https://helpcenter.veeam.com/docs/backu ... ml?ver=110
If you want to use replicas, then best practice would be to place the backup server at the secondary site.
But configuration backup restore will also work.
Thanks
Fabian
Product Management Analyst @ Veeam Software
Who is online
Users browsing this forum: Bing [Bot] and 67 guests