This post is more than 5 years old
51 Posts
0
1043
January 15th, 2007 03:00
Solaris disaster recovery with networker
We have a windows 2003 networker cluster running networker 7.2.2.
We have two storage nodes and two L700 libaries with 4 lto2 drives each.
We are trying to restore two solaris systems that are exactly the same. We first install a new (same hardware platform) solaris system with jumpstart. Then we install the networker client. We then start "recover -s -c . On the prompt we specify "add / " More than 80000 files are selected for restore. We then delete a lot of files and start the recover. After the completion we reboot the server and everything is fine.
However on the other server we do the same. But when we enter "add / "only 4000 files are selected for restore. On this client we have to specify the filesystems one at a time.
After the restore the server also doesn't start. Does anybody have a clue why the initial "add /" doesn't select all files? Or have any ideas why the second server works different than the first.
Proof:
bash-2.03# recover -f -q -c <2nd server>
recover: Current working directory is /
recover> add /
4470 file(s) marked for recovery
recover> exit
bash-2.03# recover -f -q -c
recover: Current working directory is /
recover> add /
81970 file(s) marked for recovery
Thanks for any help.
We have two storage nodes and two L700 libaries with 4 lto2 drives each.
We are trying to restore two solaris systems that are exactly the same. We first install a new (same hardware platform) solaris system with jumpstart. Then we install the networker client. We then start "recover -s -c . On the prompt we specify "add / " More than 80000 files are selected for restore. We then delete a lot of files and start the recover. After the completion we reboot the server and everything is fine.
However on the other server we do the same. But when we enter "add / "only 4000 files are selected for restore. On this client we have to specify the filesystems one at a time.
After the restore the server also doesn't start. Does anybody have a clue why the initial "add /" doesn't select all files? Or have any ideas why the second server works different than the first.
Proof:
bash-2.03# recover -f -q -c <2nd server>
recover: Current working directory is /
recover> add /
4470 file(s) marked for recovery
recover> exit
bash-2.03# recover -f -q -c
recover: Current working directory is /
recover> add /
81970 file(s) marked for recovery
Thanks for any help.
0 events found
No Events found!


ble1
6 Operator
•
14.4K Posts
•
56.2K Points
0
January 17th, 2007 00:00
ble1
6 Operator
•
14.4K Posts
•
56.2K Points
1
January 15th, 2007 04:00
beckersf
51 Posts
0
January 16th, 2007 23:00
So a better way would be to specify the filesystems individually, like /, /export/home etc.?