Thanks for the quick response!
...what's the point of having two repositories on the same (physically) host?
Frankly I’m not yet sure what the point is...
Most of my past experience has been with File Level Backup
and I’ve just started exploring the capabilities of VB&R and am trying to come up with the best strategy to address a couple of key requirements:File Versioning:
For the first of my clients that I’m planning this for, Versioning
is an extremely high priority. In the dozen or so years that we’ve been servicing them, we’ve never had to perform a DR (thankfully) but we have had numerous requests like, `we need that CAD Project as it was 3 years ago’
I’m planning Cloud for OffSite storage but also Rotated External HDDs; as I can’t bring myself to be totally reliant on the Cloud being there
if & when it’s needed — and I believe that Offline Air-Gapped Drives are still the best Last Line of Defense
So I’m thinking:
Daily Backups to Local Fixed Storage (internal HDDs on the Backup Server).
Weekly (or perhaps Daily) Backups to the Cloud.
Monthly Backups to Rotated Ext-HDDs so that a reasonable number of Restore Points can provide for long-term Versioning – and provide that Last Line of Defense
But if you and/or anybody else have better ideas, I’m all ears!