Hi,
Can anyone advise me if this configuration below will work? I have a Veeam backup server which has 2 NICs. 1 NIC is on a Network A. My Vcenter is also on Network A. The 2nd NIC is on Network B. Network A and B are not routable to each other. I have another windows server on Network B and I added a local drive of this server as a repository. Am I able to push my backup data using my Veeam Backup server into this repository?
-
- Influencer
- Posts: 15
- Liked: never
- Joined: May 05, 2012 3:24 pm
- Full Name: choonxye cham
- Contact:
-
- VP, Product Management
- Posts: 27377
- Liked: 2800 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: Need to find out if repository on a remote network will
Hi Choonxye,
Yes, your vCenter Server does not need a network connection to the backup repository. As soon as your backup proxy/backup server can access the repository, you are in the good shape.
Thanks!
Yes, your vCenter Server does not need a network connection to the backup repository. As soon as your backup proxy/backup server can access the repository, you are in the good shape.
Thanks!
-
- Influencer
- Posts: 15
- Liked: never
- Joined: May 05, 2012 3:24 pm
- Full Name: choonxye cham
- Contact:
Re: Need to find out if repository on a remote network will
Hi Vitaliy,
Just to provide some updates on this. I tried the above scenario on VBR v6.0 and found that backing up to the remote repository fails with a "nfc error... ". The workaround is to configure a cifs share on the remote server and use the cifs share as a repository instead. I logged a case with support on this and was told that v6.1 will resolve this issue.
Upgraded my setup to v6.1 and the problem of backing up to a remote repository is now solved.
Thanks
Just to provide some updates on this. I tried the above scenario on VBR v6.0 and found that backing up to the remote repository fails with a "nfc error... ". The workaround is to configure a cifs share on the remote server and use the cifs share as a repository instead. I logged a case with support on this and was told that v6.1 will resolve this issue.
Upgraded my setup to v6.1 and the problem of backing up to a remote repository is now solved.
Thanks
Who is online
Users browsing this forum: andreas_1985, Majestic-12 [Bot], veremin and 301 guests