Our Veeam Backup and Enterprise Manager were both hosted on the same server, but I've now relocated the Enterprise Manager to a different server. Should I keep the guest catalog folder (VBRCatalog) on the old server?
I know VBRCatalog uses Backup server and it replicates to EM ( if it is, any additional steps required ).
Please advise
Best answer by Chris.Childerhose
You “technically” do not have to keep it as it will be rebuilt when the VEM syncs the database for VBR. I tend to leave it if I move VEM around and let it rebuild.
Thanks, Chris. Just to confirm, in this scenario, we should leave the VBRCatalog folder on the old server, and VEM will automatically sync it. There are no additional steps required to configure VEM, correct?
You would leave the VBRCatalog on the old server and when you add the VBK server to VEM on the new one it will sync the catalog to the new folder on the new server. Make sense?
+21You “technically” do not have to keep it as it will be rebuilt when the VEM syncs the database for VBR. I tend to leave it if I move VEM around and let it rebuild.
You “technically” do not have to keep it as it will be rebuilt when the VEM syncs the database for VBR. I tend to leave it if I move VEM around and let it rebuild.
Thanks, Chris. Just to confirm, in this scenario, we should leave the VBRCatalog folder on the old server, and VEM will automatically sync it. There are no additional steps required to configure VEM, correct?
+21You “technically” do not have to keep it as it will be rebuilt when the VEM syncs the database for VBR. I tend to leave it if I move VEM around and let it rebuild.
Thanks, Chris. Just to confirm, in this scenario, we should leave the VBRCatalog folder on the old server, and VEM will automatically sync it. There are no additional steps required to configure VEM, correct?
You would leave the VBRCatalog on the old server and when you add the VBK server to VEM on the new one it will sync the catalog to the new folder on the new server. Make sense?
You “technically” do not have to keep it as it will be rebuilt when the VEM syncs the database for VBR. I tend to leave it if I move VEM around and let it rebuild.
Thanks, Chris. Just to confirm, in this scenario, we should leave the VBRCatalog folder on the old server, and VEM will automatically sync it. There are no additional steps required to configure VEM, correct?
You would leave the VBRCatalog on the old server and when you add the VBK server to VEM on the new one it will sync the catalog to the new folder on the new server. Make sense?
OK, so after the catalog has synchronised to the new server I just keep the folder on both servers?
+21You “technically” do not have to keep it as it will be rebuilt when the VEM syncs the database for VBR. I tend to leave it if I move VEM around and let it rebuild.
Thanks, Chris. Just to confirm, in this scenario, we should leave the VBRCatalog folder on the old server, and VEM will automatically sync it. There are no additional steps required to configure VEM, correct?
You would leave the VBRCatalog on the old server and when you add the VBK server to VEM on the new one it will sync the catalog to the new folder on the new server. Make sense?
OK, so after the catalog has synchronised to the new server I just keep the folder on both servers?
Once you have it on the new VEM server you can remove the folder on the VBR server where VEM used to be to free up disk space.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
