11-23-2004 07:40 PM
Now we backup the clients via VLAN A and we want to backup other clients via VLAN B. Is this possible? If yes, how do I configure this?
Now the disk agents on clients in VLAN A access the media agent on the backup server. Can a disk agent on a client in VLAN B connect to the media agent on the backup server and the same device?
Any help will be appreciated.
Thanks in advance,
11-24-2004 02:37 AM
I don't think it is a solution to my problem. I have to clarify our situation.
When trying to backup clients only connected to VLAN B, the disk agent is trying to connect the media agent on VLAN A. But there is no route between the both VLAN's. This will result in the following messages:
[Normal] From: VBDA@client.vlan-b "W:" Time: 23-11-2004 21:21:39
STARTING Disk Agent for client.vlan-b:/W "W:".
[Critical] From: BDA-NET@client.vlan-b "W:" Time: 23-11-2004 21:22:02
Cannot connect to Media Agent on system backupserver.vlan-a, port 3829
(IPC Cannot Connect System error:  Connection timed out) => aborting.
[Critical] From: VBDA@client.vlan-b "W:" Time: 23-11-2004 21:22:02
Unexpected close reading NET message => aborting.
[Normal] From: VBDA@client.vlan-b "W:" Time: 23-11-2004 21:22:02
ABORTED Disk Agent for client.vlan-b:/W "W:".
Can I specify a virtual server for the backup server and define a logical device for the same tape libray without any problem?
11-24-2004 03:18 AM
And then create additional drives under the library, one for each physical drive, hosted by the client "media server name on VLAN B".
To determine the name of the client on VLAN A and VLAN B, I would assume a ping -a
Assuming the cell manager can get to the IP address represented by "name on VLAN B".
Make sure that each drive which represents the same physical drive (ie, has the same drive index) has the same lockname configured in the Other tab of the Advanced Settings for the drive definitions.
Then your backups of clients on VLAN B should be using the drives "VLAN_B_D1", etc. or whatever you end up naming the drives which are hosted by the virtual client which is the network name of the media server on VLAN B.
11-24-2004 07:17 PM
The cell manager on the backup server can get to the IP address represented by name on VLAN B (also by name on VLAN A).
This is a solution for backing up clients on different VLAN's (without a route between each other) I have to test. Is this the only and best solution how to do this, or are there other possibilities.
Thanks so far.
11-24-2004 07:44 PM
It depends on what you mean. If you want to backup, using a dedicated backup lan, it is the correct (and the best and, as I can see, also the only) solution.
If you just want to offload the production lan there is other solutions but, this solutions need different technology. For example SAN or local backup devices.
11-24-2004 08:26 PM
I think it is the best solution for now, until the legacy servers are replaced by new servers with connections to both vlan's.