Hi,
Try updating following parameters in bp.conf file of your
Netbackup master server
CLIENT_CONNECT_TIMEOUT
CLIENT_READ_TIMEOUT
Refire the backup and see...hope things will work
fine for you now
Thanks Regards,
Gaurav Rakheja,
Retail Technology Group,
ICICI Bank Ltd,
Netbackup
Dear Jeff,
You can type following commands for daemons restart on
Windows media server:
On Media server:
C:\ bpps
C:\ bpdown -v -f
C:\ bpup -v -f
C:\ bpps
Thanks Regards,
Gaurav Rakheja,
mailto:[EMAIL PROTECTED]
_
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Use following command
bpexpdate -ev media_id -d 0
Thanks Regards,
Gaurav Rakheja,
mailto:[EMAIL PROTECTED]
_
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Hindle, Greg
Sent: Tuesday, February 13, 2007 12:59 AM
To: NB List Mail
Subject: [Veritas-bu] netbackup pool
Hi,
I have some idea as were facing the same problem two months
back.
If you want to manually check the list of medias to be
ejected, go to
# cat
/usr/openv/netbackup/vault/sessions/vault_name/sid_sessio
n_id/eject.list
If you want to automate it
Copy the following scripts(vlt_end_notify,
Hi,
You can do that by following procedure:
Make a single policy and name it COMMON-POLICY-CLIENTS1234
Include all the four clients(client1, client2, client3 and
client4 ) in the above policy
Include all the three folders(/abc, /xyz and /klm ) in above
mentioned policy
Go to
--Java
Greetings
I was having the same problem at my Data Centre but later on
it was resolved after re-installing it as media server and
with corrrect Maintenance Pack.
Also u can fire the following command to view the details
truss -p tpautoconf -t
The mismatch between gdb(global database) was