cancel
Showing results for 
Search instead for 
Did you mean: 

Implemented CASO and now servers on different subnets cannot be backup

ESabo
Level 6
We implemented CASO on our main back up server and now servers on different subnets cannot be backup, it took away our option to selected the NIC that is dedicated to our backup network.

We are getting the following:   "The job failed with the following error: The media server could not connect to the remote computer. The remote computer may not exist on the selected subnet. Try an alternative network interface, or allow Backup Exec to choose any available network interface."

We are at version 12 on everything.

any thoughts would be appriecated.
4 REPLIES 4

Dev_T
Level 6
Try adding the servers in the different subnets in "User Defined Selections" using the IP Address...

CraigV
Moderator
Moderator
Partner    VIP    Accredited
...following on from above, are those separate domains too? If so, you will then need to create a user account for BEWS in each domain, and add it into the correct groups (Domain Admins for eg.). Once done, add each of those user accounts into the BEWS media server under Network.
If there are trusts between those domains, you can look at using 1 service account for them all, and just adding that specific service account in the correct groups on each domain.

If you are unable to resolve those IPs --> Names on the servers, you can add in entries into your hosts file on your backup server, pointing to those servers.

Don't forget to open the correct ports on any firewall you have from between the subnets.

Laters!

ESabo
Level 6
Tried all the suggested - It is using the right IPv4 and the right NIC accordingly to the failure message.     This all worked until the CASO was implemented now it does not.    The accounts are fine the tests run.     The media server can resolve by name.     Any other suggestions?

CraigV
Moderator
Moderator
Partner    VIP    Accredited
Do what Dev T suggests and use an IP address. We do, it ensures we don't have any DNS issues...never had an issue with this.