Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations sizbut on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

problem recovering data using scanner and piping to uasm

Status
Not open for further replies.

resomcio

MIS
Nov 25, 2002
4
US
Hello,

I was trying to recover a particular save sets using the command scanner -S 643379202 /dev/nst0 | uasm -rv -m MSEXCH:MB=/recover. The volume it needs are:

-------------

000005 server 01/15/03 23:00:30 441 MB 643379202 hE full MSEXCH:MB
000006 server 01/15/03 23:00:30 3232 MB 643379202 mE full MSEXCH:MB
000007 server 01/15/03 23:00:30 5355 MB 643379202 tE full MSEXCH:MB

-------------


Here is what happens:



>-------------
[root@zaxxon /]# scanner -S 643379202 /dev/nst0 | uasm -rv -m
MSEXCH:MB=/recover
scanner: scanning dlt8000 tape 000005 on /dev/nst0
scanner: ssid 643379202: NOT complete
scanner: ssid 643379202: 414 MB, 13435 file(s)
scanner: done with dlt8000 tape 000005

scanner: the following save sets continue on 000006:
client name save set save time level size files
ssid S
server MSEXCH:MB 1/15/03 23:00 f 424894272 13435
643379202 S
scanner: when next volume is ready, enter device name (or `q' to quit)
[/dev/nst0]?
scanner: starting file number (or `q' to quit) [2]?
scanner: starting record number (or `q' to quit) [0]?
scanner: continuing scan with tape on device `/dev/nst0'
scanner: scanning dlt8000 tape 000006 on /dev/nst0
scanner: ssid 643379202: SYNCHRONIZED at 441 MB, 14515 file(s)
scanner: ssid 643379202: NOT complete
scanner: ssid 643379202: 3673 MB, 114255 file(s)
scanner: done with dlt8000 tape 000006

scanner: the following save sets continue on 000007:
server MSEXCH:MB 1/15/03 23:00 f 3761645000 114255
643379202 S
scanner: when next volume is ready, enter device name (or `q' to quit)
[/dev/nst0]?
scanner: starting file number (or `q' to quit) [2]?
scanner: starting record number (or `q' to quit) [0]?
scanner: continuing scan with tape on device `/dev/nst0'
scanner: scanning dlt8000 tape 000007 on /dev/nst0
scanner: fn 170 rn 0 read error Input/output error
scanner: ssid 643379202: NOT complete
scanner: ssid 643379202: 9028 MB, 225883 file(s)
scanner: done with dlt8000 tape 000007
>-------------------

at this point i'm totally confused. I don't know which tape it needs or why it should even be asking for another volume. Can someone explain why this happens?

>-------------
scanner: the following save sets continue on another volume:
server MSEXCH:MB 1/15/03 23:00 f 9245091260 225883
643379202 S
scanner: when next volume is ready, enter device name (or `q' to quit)
[/dev/nst0]?
scanner: starting file number (or `q' to quit) [2]?
scanner: starting record number (or `q' to quit) [0]?
scanner: continuing scan with tape on device `/dev/nst0'
scanner: scanning dlt8000 tape 000007 on /dev/nst0
scanner: ssid 643379202: NOT synchronized at continuation point (from
volid 439497729)


>-------------


any help would be great. thanks.

--ray
 
You are trying to recover exchange mailbox. You cannot do this using scanner / uasm combination.

The only way to properly recover exchange data is to use the NetWorker User GUI for Exchange.

If you tape is not in the media database, then you should scan in the tape using:

scanner -iv -S <ssid> <tape device>

then use the NetWorker GUI for Exchange to mark and recover the mailbox.
 
A think you use this command because you are not be able to browse the index for this save set.
The uasm not work with the MSEXCH:MB save set description, you must recover the Mail box from the gui of networker client for exchange. If you have all the tapes in the media data base the you need to recover the index for the networker exchange client.
If you are not be able to browse de apropiate version of tjhe backup then locate the save set ID and look for the backup time, type nsrck -L7 -t &quot;time&quot; client at the networker server.
This suggest mount the proper volumen an the index at this time will be recovered.

salu2
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top