After installing a second vRanger install in tandem with an existing vRanger install to load-balance ESXi (proxied) backups, the above error suddenly occurs on all backups that are attempted from the original vRanger machine. Conversely, all backups from the NEW install seem to work (backing up the same VMware infrastructure.)
In this instance, the new vRanger install's Repository share was pointed to the ORIGINAL path of the Repository. When the Repository was added to the new install, vRanger sees the pre-existing "Globalmanifest.metadata" file and prompts an "Import as Read-Only", "Import", or "Overwrite". "Import" was the option selected, and the pre-existing savepoints in the Repository were successfully imported into the new tandem install. However, this is the point where the ORIGINAL machine could no longer use the Repository for backups.
The reasons for the problem:
1) The vRanger Repository is install-specific to EACH vRanger instance in the environment. Repository shares may not be shared in tandem with multiple vRanger installs.
2) When the new install "Imported" the Repository, that Repository then was tagged as "belonging" to the new Ranger install. As a result, the pre-existing original install lost its access to the Repository.
3) Even though the Repository exists and savepoints "show up" on the "My Repository" screen of the original install, the original vRanger install can neither write nor read properly from the repository anymore. The savepoints still are present, as they still exist in the original vRanger install's database, but cannot be manipulated by it, as the original install no longer thinks it "owns" the Repository share.
1) Each vRanger install must have a unique Repository path (or paths) setup, and cannot share them between other installs. Thus, create a subfolder/different share and re-point the new tandem install to that folder/share.
2) Re-point the ORIGINAL vRanger install to the original Repository location. When prompted, click "Import" (if prompted; sometimes there is no prompt for this part of the operation).
3) This should re-establish the link the original install has with its original Repository
NOTE: Sometimes, backup jobs/savepoints will not be able to be imported during this operation, and they will "break", forcing jobs to be recreated. If pre-existing Savepoints do NOT appear (i.e do not successfully import) in the original install's "My Repository" screen, they still may be restored by the original install if the "Restore from Savepoint Manifest" option is selected during the setup of a Restore job, and the UNC path to the savepoint/credentials to it are specified.