I'm hoping some of you can give me some guidance onto this problem.
I need to find the best solution for having an DR site and at the same time locally and long term backup.
Here's my situation today.
At my production site (Site A from now on (warm site)), I got 7 hosts, running 140VM on an Nimble storage unit.
At my DR site (Site B from now on (cold site)), I got 5 hosts.
At site A I also have the following at the moment.
1 Virtual Backup Server (Master server)
1 Physical Backup Proxy Server
Between the two sites, I have an redundant 1Gbit connection.
I'm planning to buy an Nimble unit to place on Site B, and also two new physical servers to store my backup on (One for Site A, and one for site B). Both with 12x 10TB (Raid6) disc.
The various solutions I've thought of so far.
1. - Nimble to Nimble
Setup volume replication on site A to site B, to being able to failover to site B.
Set the among of snapshots on site A low (for local backup) and long on site B (for long term backup).
This seems smart, because if out of the box directly from Nimble, but it is not that flexible to find an single file to restore, either locally or remotely.
It will also give me some administrative work, to make the failover, because I need to manually clone the volumes on site B, and present these to VMware, to be able to start all of my VM again.
2. - VMware SRM with Nimble to VMware SRM with Nimble
Install VMware SRM and integrate this with Nimble, to perform the replication from site A to site B.
This also gives me the chance to test if everything works as planned, in an failover case.
Less administrative work.
But it leaves me without any backup at either sites.
3. - Veeam B&R to Veeam B&R
Setup two physical servers, on at each site, and install these as two locally backup servers.
At site A, it will make backup locally and replicate some files for long term to the server at Site B.
At site A, setup replication of VM to Veeam server at Site B, and then have this to upload it onto the Nimble unit again?! (Is this the right way of doing this?)
This will give me locally backup and long term backup at site B, and makes it a lot easier to find files / VM back in time, to restore from.
But will the replication work as easy as it does directly on the Nimble unit?!
4. - A hole new way, that I haven't t come by here
If you know about another way of doing what I want, and also smarter, then please let me know.
I'm hoping that someone can help out with this problem, and give me some guidance in what approach would be the best.
If I where to go with two physical Veeam servers, would I then make them both as proxy's for my VM Backup server, or make clean installation on both of them, to have them to work as two separately backup servers?!
Because if I go with an Veeam solution, I need to make sure, that everything backup at site A, whatever it is short term or long term, can be found and restored from the Veeam server at site B (not restored short term backup, but that I knows about that files are in the long term repository, and also about all of the replications jobs).