544 Posts

April 4th, 2012 20:00

Hi Thierry,

Seems that your tape is not in the media database. You have to either scan the volume back into the media database using scanner -i or scanner -m , or may be it is a hardware issue , but we will troubleshoot firstly how it will goes from the NetWorker side.

What is the output of the following commands:

mminfo -q ssid=SSID -r volume,fragflags

scanner -s SSID \\.\Tape1

Where you will change the SSID for that saveset and the tape name.

Waiting your updates.

Thanks,

Ahmed Bahaa

2 Intern

 • 

326 Posts

April 4th, 2012 20:00

hi ahmed

for the file and record number...i did run mminfo and got hundreds of them... so just left the scanner -m to do the work..

2 Intern

 • 

326 Posts

April 4th, 2012 20:00

HI Ahmed

Thanks for the reply...media is in db and have mounted the next tape...not sure if it's fine and i was expecting it to ask for 042 instead of 044...anyway just mounted what scanner ask for

C:\Windows\system32>scanner -m -S 6236100555 \\.\Tape0

8909:scanner: using '\\.\Tape0' as the device name

8936:scanner: scanning LTO Ultrium-5 tape KKM035 on \\.\Tape0

8939:scanner: LTO Ultrium-5 tape KKM035 already exists in the media index

8767:scanner: write failed, Not enough space

8770:scanner: fn 241 rn 22864 read error No more data is on the tape.

29486:scanner: ssid 6236100555: NOT complete

8786:scanner: ssid 6236100555: 714 GB

8761:scanner: done with LTO Ultrium-5 tape KKM035

8921:scanner: the following save sets continue on KKM044:

client name  save set             save time     level   size  files   ssid    S

CIFS  2/25/12 13:46  f         0      0 6236100555 B

scanner: when next volume is ready, enter device name (or `q' to quit) [\\.\Tape0]?

scanner: starting file number (or `q' to quit) [2]?

scanner: starting record number (or `q' to quit) [0]?

8917:scanner: continuing scan with tape on device `\\.\Tape0'

8936:scanner: scanning LTO Ultrium-5 tape KKM044 on \\.\Tape0

8939:scanner: LTO Ultrium-5 tape KKM044 already exists in the media index

8763:scanner: ssid 6236100555: SYNCHRONIZED at 714 GB, 0 file(s)

1 Attachment

544 Posts

April 4th, 2012 20:00

For the file number and recorder number of a saveset, you can use the following Powerlink solution on " How to get file number and recorder number for specific saveset"

https://solutions.emc.com/emcsolutionview.asp?id=esg56957

In NetWorker 7.5 and higher, when a volume is marked with the scan needed flag, the user can specify the starting file and record numbers that needs to be scanned  from the media database. For example:

scanner -f file -r record  -i device

Use these options when a whole volume scan is not needed. This shortens the time required to run the scanner program. For more information, refer to the EMC NetWorker Command Reference Guide.

Thanks,

Ahmed Bahaa

544 Posts

April 7th, 2012 04:00

Hi Thierry,

How is it going till now with the scanner -m command ? Problem solved ?

Waiting your updates.

Thanks,
Ahmed Bahaa

2 Intern

 • 

326 Posts

April 9th, 2012 14:00

resuming after weekend...still running....scanner really take very long time

544 Posts

April 9th, 2012 15:00

Hi Thierry,

Is it still running for three days till now ? I know it takes a long time but i didnt see it before for three days . Did you specify a specific device for the scanner command or it is working on all the volumes ?

Thanks,

Ahmed Bahaa

2 Intern

 • 

326 Posts

April 9th, 2012 21:00

scanner completed as attached and nsrck-L7 but the browse date not visible

1 Attachment

2 Intern

 • 

326 Posts

April 9th, 2012 21:00

all the volumes....roughly ~ LTO5 takes 8 hours...scanner completed...have launched GUI to see if the session was there to be restored but not as expected since -m just builds media entry and now nsrck L7 running to rebuild online indexes

544 Posts

April 10th, 2012 19:00

Hi Thierry,

Is 25th of Feburary is the Saveset completion date ? Is there Index backup at that date (2/25/2012) to this saveset you are recovering  so that you will able to change its status to browsable ?

you can run the following command to check the indexes you have for that clients

mminfo -av -q name="index:sth-nas-01"

Thanks,

Ahmed Bahaa

2 Intern

 • 

326 Posts

April 17th, 2012 17:00

Hi

Index failed to backup and understood that scanner doesnt work for ndmp or dsa backups to be rebuild.. is this correct?

Thanks for your feedback..

544 Posts

April 17th, 2012 19:00

Hi Thierry,

Yes you are correct, and as the index backup failed, you will not be able to rebuild the online file index using scanner -i option, As for NDMP save sets or DSA save sets, this option does not reconstruct the index entries from the volume. Sorry for that.

Thanks,

Ahmed Bahaa

No Events found!

Top