Feature Request - Copy jobs and Replicating to Remote DR Sites

[jhemphill]

Perhaps there is already a way to do this that I'm missing. If so, I would love to know.
I have a relatively small Prod and DR facility.
I want to keep disk based backups at my Prod and then the following at my DR: Backup copy, Tape, and Replication.

The problem that I'm running into, is that if my Prod controls the backup (local), backup copy, tape, and replication (all remote push) then Prod is also required to be available to restore those items at my DR - however Prod being unavailable is one reason why I have a DR site.
If my DR controls the the backup, tape, replication (all remote pulls) and the backup copy (pushed back to Prod), then my ISP is now a failure point for all of my backups.

What I want is for a Prod B&R server and a DR B&R server to be aware of each other enough to perform the appropriate local tasks where logical:
The Prod B&R runs local backups to disk.
The Prod B&R runs a backup copy job to DR disk.
The DR B&R runs a tape backup based off of the backup copy job.
The DR B&R runs a replication based off of the backup copy job.

I would greatly appreciate knowing if this is possible, or if not, maybe it can be?
Thank you.

[PetrM]

Hi Jonathan,

Yep, I agree that the request makes perfect sense but there is no logic which makes two different instances of Veeam B&R be aware of each other. According to our best practices, it's highly recommended to keep the backup server on DR site to ensure seamless working of failover plans without complex manual operations. I'd suggest to use configuration backup and restore it on another server if the backup server is down due to whatever reason.

Thanks!

[jhemphill]

"no logic" yet...
Thank you for the reply. We'll likely go this route, but it's a shame that I can't process local tasks locally.

Thanks,
Jonathan

[foggy]

You can do that and have a cold standby Veeam B&R server instance waiting in DR location for a quick configuration import to proceed with the DR tasks.