![]() I can’t imagine if the entire repo is encrypted what kind of havoc that could create - might be okay, might not be, but I wouldn’t want to find out in production. I can’t speak for what Chris is talking about regarding repo’s being upgraded and inaccessible to not-yet-upgraded VBR server’s, but it generally seems like a bad idea. While that might be handy for restoring a VM from a different VBR server at one location to a different location (strange use case, but the only advantage I can come up with) and it can be confusing for sure. If you use the same repo for all servers, note that all servers will see each others backups as imported/foreign objects (or encrypted objects if your backups are encrypted) because it has no information about those restore points in it’s own database but it will see those restore points in the repo. My recommendation would be that you create 3 separate folders on your backing storage, one for each repo, one repo for each server. ![]() But a very slight change might work for you. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |