echo p | nsradmin -p 390113 -i - -s uslgto2.aigfpc.com
rpcinfo -t usws1 390113 1
From usws1 do:
echo p | nsradmin -p 390113 -i - -s uslgto2.aigfpc.com
rpcinfo -t usws1 390113 1
If that works, do savefs -s uslgto2.aigfpc.com -vpn (run from usws1).
If VSS savesets are failing only, most likely you have issue with VSS subsstem so you should check those (there are some known patches which are must for Windows systems). Check event logs and output of vssadmin list writers command.
Make sure also that servers file (if used on client) has all possible name combinations of backup server. On multihomed systems for some reason VSS saveset used different NIC and traffic went differently than for disk drives (had that ones on 2003).
ble1
4 Operator
•
14.4K Posts
0
November 18th, 2011 09:00
From uslgto2 do:
echo p | nsradmin -p 390113 -i - -s uslgto2.aigfpc.com
rpcinfo -t usws1 390113 1
From usws1 do:
echo p | nsradmin -p 390113 -i - -s uslgto2.aigfpc.com
rpcinfo -t usws1 390113 1
If that works, do savefs -s uslgto2.aigfpc.com -vpn (run from usws1).
If VSS savesets are failing only, most likely you have issue with VSS subsstem so you should check those (there are some known patches which are must for Windows systems). Check event logs and output of vssadmin list writers command.
Make sure also that servers file (if used on client) has all possible name combinations of backup server. On multihomed systems for some reason VSS saveset used different NIC and traffic went differently than for disk drives (had that ones on 2003).