Thanks. I will check. We are running 3.2 and it definately is working to do
the backups but not for the restores so your idea makes sense.

-----Original Message-----
From: Bob Bakh [mailto:bbakh AT veritas DOT com]
Sent: Friday, September 29, 2000 7:48 PM
To: 'McMurphy, Tim'; veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Restore across VLANs?


You may want to turn on logging and start digging.  My guess is that the lgs
will show tat the restore is trying to use a port that is being filtered,
backups have the ability to use ports sequentially, and restores use random
ports, at least that was how it was in 3.2.

So one way may work, but the other may not.

I would suggest

bprd and bpcd on the master 
and the media server bprd bpcd bpbkar bptm tar

and the client

bpcd bpbkar and tar

Bob



-----Original Message-----
From: McMurphy, Tim [mailto:Tim.McMurphy AT cdcgy DOT com]
Sent: Wednesday, September 27, 2000 12:53 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Restore across VLANs?


We can backup across our VLANs fine but when we go to do a restore we get
this error:

-----------------------------------------------------
13:39:26 (60773.001) Restoring from image created Sat Sep 16 00:19:00 2000
13:45:27 (60773.001) Status of restore from image created Sat Sep 16
00:19:00 2000 = cannot connect on socket

13:45:27 (60773.001) /var/spool/cron/crontabs/root was not restored.

13:45:29 (60773.xxx) INF - Status = cannot connect on socket.
-----------------------------------------------------

Workaround is to mount tapes on a media server in the VLAN we are restoring
to. Any ideas how to fix this?
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu