04-15-2008 05:09 AM
04-15-2008 05:55 AM
04-15-2008 06:29 AM
04-15-2008 06:30 AM
04-15-2008 08:23 AM
04-15-2008 09:55 AM
04-16-2008 07:31 AM
Frequency of DB Backup: after each successful backup schedule
Server: Hostname_of_Master_server_that_has_the_DB_on_it!
Sequence # 1 Last Media Used: 000917
Written Allocated Type Density Media
------------------- ------------------- ---- ------- -----
1 04/16/2008 10:18:27 05/19/2005 16:15:33 RMedia hcart 000917
2 03/15/2008 09:17:05 01/04/2005 18:29:18 RMedia hcart 000886
Paths Included:
/veritas/openv/netbackup/db
/veritas/openv/volmgr/database
/veritas/openv/var
04-16-2008 07:40 AM
04-16-2008 08:01 AM
04-17-2008 07:59 AM
04-17-2008 10:03 AM
04-17-2008 10:11 AM
04-17-2008 10:22 AM
04-17-2008 10:28 AM
04-17-2008 11:29 AM
04-21-2008 06:34 PM
04-22-2008 09:10 AM
07-09-2008 12:27 AM
07-09-2008 04:24 AM
Heres what you do: rebuild a server with the same Os and patch as the dead one; layout the disks in order to accomodate the db restore (or just make one huge partition: if everything wont fit , then you need more disk: you need to know how much space was used on the original); install and patch netbackup - dont configure it; attach all your devices, robots etc;get your latest dump tape and put it in an attached tape drive and brrecover -r -tpath /dev/rmt/xxx all files and directories that came from the same server. If you failed to backup everything you have a headache; if youve got the dbs then youre mostly ok. Then trash the storage units, robots etc etc and reconfigure. Done. It works well but theres preparation needed.
Alternatively (this also works) : if youve got a ufsdump or similar, boot your server off alternative media/disk, format up your target disk(s) to receive the dump, ufsrestore the partitions, make bootable, change to be the default boot device, boot. Done. Works very well under Solaris and theres no need to apply brrecover. You will need to reconfigure your devices as youve just restored the original ones: thats a bit messy but is do-able.