Backup Central

Running NW 7.4.5 on a Windows 2008 R2 server.
We need to recover some ancient data that was written to LTO2 tapes
before we upgraded our library to one with LTO4 drives... Have had no
problem recovering from LTO2 tapes as long as the entries were still in
the indexes... But now we need to scan in a couple of save-sets from
fall of 2010 that are still on tape (expired,recycleable,but still
intact), but no longer in the indexes... When I attempt to run 'scanner
-S ssid# -I \\.\Tape### , it crashes with:

C:\Windows\system32>scanner -S 1804344764 -i \\.\Tape2147483643
8909:scanner: using '\\.\Tape2147483643' as the device name
8936:scanner: scanning LTO Ultrium-4 tape 001653L2 on \\.\Tape2147483643
8938:scanner: LTO Ultrium-4 tape 2223712427 for volume 001653L2
conflicts with existing
media database entry for LTO Ultrium-2 tape 2223712427

Does anyone know the syntax to specify that it's an LTO2 tape with the
-t (type) option ?? I've been trying what the manual outlines, but
nothing is working... keep getting errors.

Thanks,

Paul Goslin
IS&TS Unix Administration
513-612-2193
Current Office Hours Mon-Thurs 8-4

There is nothing wrong, except ...

8938:scanner: LTO Ultrium-4 tape 2223712427 for volume 001653L2 conflicts with existing media database entry for LTO Ultrium-2 tape 2223712427

However, this is severe. NW obviously uses the same volid but treats the tape as LTO4 and consequently sees a volume conflict which is not resolveable.

When we recently upgraded from LTO3 to LTO5, we did not have this problem. However, we are running 7.6.2.5.

You have 3 options:
- Delete the existing media from the index and rescan it.
- And an old LTO2 drive (if still available, used as readonly) and try a scan/recover from here.
- Get in touch with EMC support - they should know the issue. If so they will most likely ask you to update.

Hi,

I faced the same issue with LTO3 and LTO5 tapes conflict, the thing i have
done deleted the volume with nsrmm, rescan it with scanner,however as usual
it takes long time to scan the full tape but i got the all the data back
into our networker index database.

On Tue, May 22, 2012 at 9:32 PM, bingo <networker-forum < at > backupcentral.com>wrote:

There is nothing wrong, except ...

8938:scanner: LTO Ultrium-4 tape 2223712427 for volume 001653L2 conflicts
with existing media database entry for LTO Ultrium-2 tape 2223712427

However, this is severe. NW obviously uses the same volid but treats the
tape as LTO4 and consequently sees a volume conflict which is not
resolveable.

When we recently upgraded from LTO3 to LTO5, we did not have this problem.
However, we are running 7.6.2.5.

You have 3 options:
- Delete the existing media from the index and rescan it.
- And an old LTO2 drive (if still available, used as readonly) and try a
scan/recover from here.
- Get in touch with EMC support - they should know the issue. If so they
will most likely ask you to update.

+----------------------------------------------------------------------
|This was sent by carsten_reinfeld < at > avus-cr.de via Backup Central.
|Forward SPAM to abuse < at > backupcentral.com.
+----------------------------------------------------------------------

On 22/05/12 15:40, Goslin, Paul wrote:
Running NW 7.4.5 on a Windows 2008 R2 server.
We need to recover some ancient data that was written to LTO2 tapes
before we upgraded our library to one with LTO4 drives... Have had no
problem recovering from LTO2 tapes as long as the entries were still in
the indexes... But now we need to scan in a couple of save-sets from
fall of 2010 that are still on tape (expired,recycleable,but still
intact), but no longer in the indexes... When I attempt to run 'scanner
-S ssid# -I \\.\Tape### , it crashes with:

C:\Windows\system32>scanner -S 1804344764 -i \\.\Tape2147483643
8909:scanner: using '\\.\Tape2147483643' as the device name
8936:scanner: scanning LTO Ultrium-4 tape 001653L2 on \\.\Tape2147483643
8938:scanner: LTO Ultrium-4 tape 2223712427 for volume 001653L2
conflicts with existing
media database entry for LTO Ultrium-2 tape 2223712427

Does anyone know the syntax to specify that it's an LTO2 tape with the
-t (type) option ?? I've been trying what the manual outlines, but
nothing is working... keep getting errors.

You could manually define one of your LTO-4 drives as an LTO-2 drive
temporarily?

Paul,
You have to use "-t type" option with your scanner command. Your command should look like this : scanner -t "LTO Ultrium-2" -S 1804344764 -i \\.\Tape2147483643

Rovin A. D'Souza
Principal Infrastructure Engineer| BUR  NetWorker| ITIL & EMCSA Certified | ITO-DCS-Storage| MphasiS An HP  Company
Techbay, PL Compound, Morgan’s Gate, 22-5-750, Jeppu Ferry road, Mangalore - 575001 | CUG extn- #5 651423 # |email:  rovinabishek.dsouza < at > hp.com | For any escalation, please contact Afkar Khan (Afkar.Khan < at > hp.com)

 Information transmitted by this e-mail is proprietary to MphasiS and/ or its Customers and is intended for use only by the individual or entity to which it is addressed, and may contain information that is privileged, confidential or exempt from disclosure under applicable law. If you are not the intended recipient or it appears that this mail has been forwarded to you without proper authority, you are notified that any use or dissemination of this Information in any manner is strictly prohibited. In such cases, please notify us immediately at mailmaster < at > mphasis.com and delete this mail from your record

-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER < at > LISTSERV.TEMPLE.EDU] On Behalf Of Div Prakash
Sent: Tuesday, May 22, 2012 9:55 PM
To: NETWORKER < at > LISTSERV.TEMPLE.EDU
Subject: Re: [Networker] How to scan a LTO2 tape when all I have are LTO4 drives ?

Hi,

I faced the same issue with LTO3 and LTO5 tapes conflict, the thing i have done deleted the volume with nsrmm, rescan it with scanner,however as usual it takes long time to scan the full tape but i got the all the data back into our networker index database.

On Tue, May 22, 2012 at 9:32 PM, bingo <networker-forum < at > backupcentral.com>wrote:

There is nothing wrong, except ...

8938:scanner: LTO Ultrium-4 tape 2223712427 for volume 001653L2
conflicts with existing media database entry for LTO Ultrium-2 tape
2223712427

However, this is severe. NW obviously uses the same volid but treats
the tape as LTO4 and consequently sees a volume conflict which is not
resolveable.

When we recently upgraded from LTO3 to LTO5, we did not have this problem.
However, we are running 7.6.2.5.

You have 3 options:
- Delete the existing media from the index and rescan it.
- And an old LTO2 drive (if still available, used as readonly) and
try a scan/recover from here.
- Get in touch with EMC support - they should know the issue. If so
they will most likely ask you to update.

+---------------------------------------------------------------------
+-
|This was sent by carsten_reinfeld < at > avus-cr.de via Backup Central.
|Forward SPAM to abuse < at > backupcentral.com.
+---------------------------------------------------------------------
+-

BTW - i forgot to mention that we were lucky to use the old tape drives.

Thanks for All for the replies and recommendations ....
I seem to have gotten scanner running with 'scanner -i -S #### -t "LTO Ultrium-2" \\.\Tape########'

Just needed to get the syntax correct. I can only assume it is running now, there's been no error, and it hasn't returned to a command prompt yet... ( usually I've found if you're waiting, it's working ) It displayed this:

8909:scanner: using '\\.\Tape2147483643' as the device name
8936:scanner: scanning LTO Ultrium-2 tape 001653L2 on \\.\Tape2147483643
8939:scanner: LTO Ultrium-2 tape 001653L2 already exists in the media index

So I think it's working as far as I can tell...

Thanks All Once Again...
Paul
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER < at > LISTSERV.TEMPLE.EDU] On Behalf Of Dsouza, Rovinabishek
Sent: Tuesday, May 22, 2012 12:43 PM
To: NETWORKER < at > LISTSERV.TEMPLE.EDU
Subject: Re: [Networker] How to scan a LTO2 tape when all I have are LTO4 drives ?

Paul,
You have to use "-t type" option with your scanner command. Your command should look like this : scanner -t "LTO Ultrium-2" -S 1804344764 -i \\.\Tape2147483643

Rovin A. D'Souza
Principal Infrastructure Engineer| BUR  NetWorker| ITIL & EMCSA Certified | ITO-DCS-Storage| MphasiS An HP  Company Techbay, PL Compound, Morgan’s Gate, 22-5-750, Jeppu Ferry road, Mangalore - 575001 | CUG extn- #5 651423 # |email:  rovinabishek.dsouza < at > hp.com | For any escalation, please contact Afkar Khan (Afkar.Khan < at > hp.com)

 Information transmitted by this e-mail is proprietary to MphasiS and/ or its Customers and is intended for use only by the individual or entity to which it is addressed, and may contain information that is privileged, confidential or exempt from disclosure under applicable law. If you are not the intended recipient or it appears that this mail has been forwarded to you without proper authority, you are notified that any use or dissemination of this Information in any manner is strictly prohibited. In such cases, please notify us immediately at mailmaster < at > mphasis.com and delete this mail from your record

-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER < at > LISTSERV.TEMPLE.EDU] On Behalf Of Div Prakash
Sent: Tuesday, May 22, 2012 9:55 PM
To: NETWORKER < at > LISTSERV.TEMPLE.EDU
Subject: Re: [Networker] How to scan a LTO2 tape when all I have are LTO4 drives ?

Hi,

I faced the same issue with LTO3 and LTO5 tapes conflict, the thing i have done deleted the volume with nsrmm, rescan it with scanner,however as usual it takes long time to scan the full tape but i got the all the data back into our networker index database.

On Tue, May 22, 2012 at 9:32 PM, bingo <networker-forum < at > backupcentral.com>wrote:

There is nothing wrong, except ...

8938:scanner: LTO Ultrium-4 tape 2223712427 for volume 001653L2
conflicts with existing media database entry for LTO Ultrium-2 tape
2223712427

However, this is severe. NW obviously uses the same volid but treats
the tape as LTO4 and consequently sees a volume conflict which is not
resolveable.

When we recently upgraded from LTO3 to LTO5, we did not have this problem.
However, we are running 7.6.2.5.

You have 3 options:
- Delete the existing media from the index and rescan it.
- And an old LTO2 drive (if still available, used as readonly) and
try a scan/recover from here.
- Get in touch with EMC support - they should know the issue. If so
they will most likely ask you to update.

+---------------------------------------------------------------------
+-
|This was sent by carsten_reinfeld < at > avus-cr.de via Backup Central.
|Forward SPAM to abuse < at > backupcentral.com.
+---------------------------------------------------------------------
+-

The syntax is fine. However, let me suggest that you add at least one '-v' as this would provide you some feedback.

@davina
Thanks for pointing out the '-t' option. Never used this before.

Thanks for All for the replies and recommendations ....
I seem to have gotten scanner running with 'scanner -i -S #### -t
"LTO Ultrium-2" \\.\Tape########'

Just needed to get the syntax correct. I can only assume it is
running now, there's been no error, and it hasn't returned to a
command prompt yet... ( usually I've found if you're waiting, it's
working ) It displayed this:

8909:scanner: using '\\.\Tape2147483643' as the device name
8936:scanner: scanning LTO Ultrium-2 tape 001653L2 on \\.\Tape2147483643
8939:scanner: LTO Ultrium-2 tape 001653L2 already exists in the media
index

So I think it's working as far as I can tell...

Thanks All Once Again...
Paul

I use the "scanner -t <type>" all the time to scan older format tapes in a
new format drive, but in my case, I scan sdlt320 tapes in a sdlt600 drive.
Didn't know the format to specify LTO tapes. Good to know ...

Thanks Bingo,
Good Point. It does not provide ANY feedback until it completes, then it
displays the total save-set size and # of files in the save-set...
Will try to remember to add the -v next time... Don't run scanner very
often though, this is the 1st time in over 5 years I've had to run one
and it seemed to go much faster than I remember.

-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER < at > LISTSERV.TEMPLE.EDU] On
Behalf Of bingo
Sent: Tuesday, May 22, 2012 1:55 PM
To: NETWORKER < at > LISTSERV.TEMPLE.EDU
Subject: [Networker] How to scan a LTO2 tape when all I have are LTO4
drives ?

The syntax is fine. However, let me suggest that you add at least one
'-v' as this would provide you some feedback.

< at > davina
Thanks for pointing out the '-t' option. Never used this before.

+----------------------------------------------------------------------
|This was sent by carsten_reinfeld < at > avus-cr.de via Backup Central.
|Forward SPAM to abuse < at > backupcentral.com.
+----------------------------------------------------------------------