scanner command usage - dell emc · pdf filescanner command usage . p/n 300-012-537 ......
TRANSCRIPT
1
I s
EMC® NetWorker
®
Scanner Command Usage P/N 300-012-537
REV 03
July, 2015
This technical note explains various usages of the scanner command
The following topics are covered:
Terminology ............................................................................................... 2
Requirements .............................................................................................. 2
Scanner: History and Purpose .................................................................. 2
Data Storage on magnetic tape and disk ................................................ 3
Scannable sources of data ......................................................................... 5
Usage options and internals ..................................................................... 8
Advanced recovery and troubleshooting ............................................. 17
Principals KBs ........................................................................................... 23
Conclusion ................................................................................................ 23
2
Terminology
EMC NetWorker
Usage of the Scanner Command
Terminology
MediaDB (Media Database) — NetWorker internal database that keeps
track of backed up saveset information, including state, retention,
volume information, and addresses on the media.
CFI (Index Database) — NetWorker internal database that keeps track of
the metadata for client savesets, which may include media address
offsets for browsing specific files within a saveset, or special processing
information for databases or other non-filesystem savesets. the meta data
for each backup.
Requirements
Be aware of the following requirements when using the scanner
command:
You must be logged in as root or as the Windows Administrator
on the NetWorker host connected to the tape drive used for the
operation host.
The user executing the command on the Storage Node must be
part of a NSR Usergroup with the appropriate privilege to
access/commit media database data. Usually this means that the
user must be added to the NetWorker server’s Administrators
group in User Group using the standard syntax
(local_user@sn_host or domain_user@domain). The User Groups
container is located in the Configuration section of the
NetWorker Management Console (NMC).
Scanner: History and Purpose
The scanner command is primarily used to rebuild the online indexes
and media databases with content of media (tape or disk devices) in
order to ease the recovery of those data. This is generally done in case of
Disaster Recovery where indexes have been lost and only data remains.
Ultimately, scanner can be used to recover such data directly.
3
Data Storage on magnetic tape and disk
EMC NetWorker Usage of the Scanner command
Data Storage on magnetic tape and disk
This section describes the common elements for data storage on
magnetic tapes and disks.
Displacement of data
Magnetic tape physical formats are, on a physical and operational level,
standard in some ways throughout the industry. In order to write data to
and read data from a tape, all tape formats require several common
elements:
Tape Label: The label is the common term for the unique media
identifier. Depending on the format, more data elements may be carried
in the label.
Records: A record is the unit of data storage on the tape, also known as
the 'block'. Block size is determined at label time and is consistent
throughout the volume. Records / blocks are usually described in
kilobytes (most commonly 128 KBs - and sometimes limited by Windows
OSes to 64 KBs). The tape device and driver determine the maximum
block size.
File marks: A filemark is a special binary sequence that is written to the
tape periodically to separate data segments. Filemarks, or 'files' are
numbered and the enumeration represents the beginning of the
sequential media to its end. A filemark is placed at intervals between
variable numbers of distinct records and it can thus be considered that a
'file' may represent / contain that number of blocks or records.
Double filemark (End Of Data): It is currently convention amongst all
major tape manufacturers that two filemarks represents the end of the
available data - a tape device will never read beyond this mark,
irrespective of Operating System, software, or drivers. When a write
session finishes, two filemarks are written, representing the new EOD;
when a new session is initiated, the tape positions over the second
filemark, deleting it when writing commences, and leaving a single
filemark behind it.
Data is written from one or many sources in segments equal to the
configured record/block size serially to the volume, and separated
periodically by filemarks. New data is always appended to the end of the
written data, and sessions are always closed by a double filemark(the
4
Data Storage on magnetic tape and disk
EMC NetWorker
Usage of the Scanner Command
second of which is overwritten at the next write session). Data cannot be
erased from a tape volume.
Positioning on tape media
Positioning on tape media is done using industry standard tape
commands, including:
fsf (Forward Space File) - move forward the given number of files.
bsf (Backward Space File) - move backward the given number of files.
fsr (Forward Space Record) - move forward the given number of records.
bsr (Backward Space Record) - move backward the given number of
records.
rewind position to the beginning of tape.
These are all represented as part of the *nix standard mt command (for
which a port is provided with NetWorker for Windows). In most
situations, software records the file/record address(es) of data written to
the media, and reads from those file/record addresses when retrieval of
the data is required.
Deleting data and reuse of tape media
Since data is sequentially accessed, space cannot be reclaimed from a
volume, and data is never selectively erased. It is the usual practice to
write a new label over the existing one. This has several effects:
Reinitializes the tape with a new label and unique identifier.
Prepares a context for new data in the software database.
Writes the new label over the existing label, and concludes the
write with a double filemark.
Renders the existing data on the tape inaccessible as it now falls
behind a double filemark.
Open Tape Format
OTF is EMC | Legato's proprietary tape media format and subscribes to
all of the aforementioned parameters, of which the majority are standard
in the industry. There are several noteworthy distinctions for OTF's
behaviors:
5
Scannable sources of data
EMC NetWorker Usage of the Scanner command
NetWorker uses two tape labels at the beginning of the tape for
redundancy; these appear at file 0 and file 1, and each is 32 KB in
size.
NetWorker embeds label and other information into the header
of every block written; this ensures that even if the label is
accidentally overwritten following a rewind, data can still be
retrieved from viable blocks.
NetWorker encodes all data in XDR format - this solves several
interoperability problems and ensures all data types from any
filesystem or application can be recorded in a consistent format
(see RFC 1014 in http://www.faqs.org/rfcs/rfc1014.html).
Scannable sources of data
This section describes the types of backup data that can and cannot be
recovered by use of the scanner command.
Scannable sources: tape / VTL / FTD / AFTD / DD volumes
The scanner can be used recover data from all supported tape, VTL, FTD,
AFTD, and DD Boost volumes and rebuild the index and media database
for most backups. For Avamar volumes, the scanner can rebuild indexes,
but the recover command must be used to recover the data.
Partial savesets generated with “Checkpoint restart” option
Scanning of partial savesets created once the “Checkpoint restart”
feature is enabled is working as any other savesets but all different parts
need to be scanned sequentially, scanning the data on another order than
it was backed up may result on out-of-sync data and scanner of certain
tapes may need to be done twice (see Usage options and internals).
NDMP data
Scanner of NDMP data is possible but will reintroduce the data into the
Media Database only. Indexes are generated during the backup itself and
known as a "History file"; thus regeneration of those data isn’t possible;
only “saveset recover” will be available to recover them (see man page
for nsrndmp_recover command for further info).
6
Scannable sources of data
EMC NetWorker
Usage of the Scanner Command
Non scannable sources: Avamar indexes (metadata) on AFTD / Cloud /
The AFTD used to store Avamar indexes is a normal AFTD and thus
uses OTF. But the data stored are in fact links referencing the client’s
saveset to Avamar hashes, which are used by Avamar in order to recover
the data from the Avamar Data Store.
Cloud backup are sent on Cloud device which is a specific type of device
not using OTF, data aren’t stored the same way thus scanner isn’t aware
of what/how to scan data.
Usage of t_reader to check formatting
The t_reader tool is an internal support tool that may help in identifying
problems with volumes that scanner fails to read. Essentially, it is
entirely unconcerned with the data itself so the lack of a NetWorker label
will not hinder its ability to report.
To run t_reader, download correct version from
ftp://ftp.legato.com/pub/Private/tools/t_reader. Ensure the volume to
be checked is loaded in a drive, and not being accessed by other
processes.
t_reader may be run from any point on the tape – so rewinding is
necessary to scan the entire volume.
t_reader can be used in cases where scanner fails for several reasons:
To ensure that the volume is physically readable at all by an
application entirely unrelated to and independent from NetWorker.
To confirm that the block sizes for the volume label are as expected,
that is, it should always start with file 0 with 1 32-KB block, and file 1
with 1 32 KB block.
To confirm that the block sizes for the volume data are as expected;
data begins at file 2 and is thereafter a variable number of uniform
block sizes per file.
To expose OTF chunking information. To do so, run t_reader in an
environment with the variable EXPLODE_LEVEL=2.
7
Scannable sources of data
EMC NetWorker Usage of the Scanner command
Consequences of overwritten label / rewind / relabel
Unexpected relabeling of a volume may happen due to external causes
and more rarely, product logic defects leading to relabel of the incorrect
volume. This could happen on various cases such as:
SCSI resets.
Customer mistakes ( manual relabel or manual reset of a suspect
tape to appendable).
Manual movement of volumes outside of NetWorker while
NetWorker is running.
In those cases, once label is overwritten and replaced, data are
considered as lost as there is no way to read over the EOD marker set
after the label or the newly written data.
If the label isn’t affected but some file marks were overwritten, data may
still be accessible and recoverable (see Advanced troubleshooting
below).
In some cases, an extra filemark can be appended to the tape, resulting in
a mismatch between mediaDB filemarks and what is physically on the
tape. In those cases, data is appended to the tape based on the mediaDB
recorded filemark and this could lead to data being overwritten.
Two examples:
Tape device driver issue (HP-UX st driver issue NW120074 /
PHKL_41028 & PHKL_41612).
Tape Firmware issue: HP LTO3 M66S .
NDMP backups are using a specific amount of filemarks and
therefore the mediaDB counter is incremented by three (3)
filemarks each time.
Appending to a NDMP tape that was previously marked as full
by NetWorker will cause data to be overwritten because once the
tape is marked full, NW does not keep track of the next filemark
where data has to be written. This could also cause data loss.
8
Usage options and internals
EMC NetWorker
Usage of the Scanner Command
Usage options and internals
This section describes the various scanner options and provides
examples.
Differences between the –m and the –i options
The major differences between the –m and –I options are:
The -m option rebuilds only the media database entries for the
volume scanned. Index entries corresponding to the data still
need to be recovered in order to browse into the savesets.
Since NetWorker 7.3, the ssflags field no longer shows the
“scanned-in” status; the browse and retention policies (ssbrowse
and ssretent field) are set during the backup and are brought
back by the scanner command.
The -i option rebuilds both the media database and index
database entries for the scanned volume/saveset. This option is
preferred to be used when only the data saveset is available.
If both index and data saveset are residing on the same tape, best
practice is to first run a scanner –m of the tape and then run a
nsrck –L7 of the client that the saveset belongs to.
If the savesets are already expired, you must change them
manually to “not recyclable” and then modify the saveset
retention in order for the nsrck to recover the indexes
successfully.
This option does not have any effect on NDMP backups because
the indexes are generated as part of the backup themselves; see
Scanner usage for NDMP below.
Options available for positioning to scan specific data: –S, –f, –r
In some scenarios, when only a specific saveset is needed, scanning the
whole tape is pointless; especially with large physical tapes such as
LTO4.
In those cases, specifying the saveset id (“-S”), the starting file number
(“-f”) and the record number (“-r”) for this saveset id, will enable the
scanner command to position the tape directly at the beginning of the
saveset you want to scan.
9
Usage options and internals
EMC NetWorker Usage of the Scanner command
All three options can be used separately but the common usage is the
following:
The –f and –r options can also be used without the SSID when it is not
known. Note that one can position anywhere before the saveset in
question (however all data is scanned from the position specified until
the SSID startnote is found, leading to longer scan times).
When launched with those options, the scanner command positions the
tape to the file number and record number specified and shows the
following:
Positioning to a specific file and record number can help troubleshooting
as well; see the “Advance recovery and troubleshooting section”.
Using the -n option
The “-n” option will run the scanner on the tape or saveset specified
without actually committing the data to the media and/or index
database. In conjunction with the “-i” option, the scanner will provide
the most complete checking available.
scanner –Z
The “-Z” option, in conjunction with the “datazone-id” is used when
importing a cloud volume from a different datazone.
A scanner of an external cloud volume without this datazone-id won’t be
possible, the volume will not be found by scanner.
It is possible to scan-in a volume without knowing the datazone-id but
the scanner command has to be done on a freshly installed NetWorker
server without any other devices or volumes defined.
10
Usage options and internals
EMC NetWorker
Usage of the Scanner Command
scanner –z
Usage of the –z switch with scanner suppresses prompting for a
continuation volume with spanned savesets (which is the default). This
may help to facilitate out-of-sequence scanning by requiring less manual
intervention.
Note that failure to scan all volumes into the media database results in
misleading representation via mminfo or the NMC GUI. There are
several permutations of this problem:
NW124740 - Scanning spanned savesets: Incomplete savesets
marked browsable when tail volume is scanned.
NW124741 - Scannering spanned savesets: Incorrect / inferred
fragflags/sumflags segment values when scanning out of
sequence.
NW124743 - Scannering spanned savesets: Incorrect / inferred
last saveset segment values when scanning out of sequence.
Scanner usage with NDMP data
Scanner of NDMP data will import data into the media database only.
The “-i” option isn’t available as the index is generated as part of the
backup itself (also known as a “History” file).
While writing to tape, NDMP data will be written with a different
behavior than normal data. Each NDMP saveset will take three
filemarks instead of one.
NDMP is a different protocol from OTF and is written to tape differently
than OTF formatted data. NDMP does not support interleaving
(multiplexing) of datastreams and each NDMP saveset is separated by
three consecutive filemarks.
Physically, the file numbers are still written to tape and fn2 will be seen
while running a scanner command. Fn2 is a header for the NDMP
saveset that NetWorker recognizes. The filemarks are enumerated in the
same way, and on a NetWorker volume, data still begins at filenumber
two (meaning the second NDMP saveset begins at file 5, third at 8, and
so on).
11
Usage options and internals
EMC NetWorker Usage of the Scanner command
The mminfo command displays this layout as follows:
C:\>mminfo -s nwserver -r client,name,savetime,ssid,mediafile,mediarec -
q"volume=000001"
client name date file rec
nwclient /fs_serv_1 07/06/2010 3 0
nwclient /fs_serv_2 07/06/2010 6 0
nwclient /fs_serv_3 07/06/2010 9 0
nwclient /fs_serv_4 07/06/2010 12 0
nwclient /fs_serv_5 07/06/2010 15 0
nwclient /fs_serv_6 08/06/2010 18 0
nwclient /fs_serv_7 08/06/2010 21 0
nwclient /fs_serv_8 14/06/2010 24 0
nwclient /fs_serv_9 14/06/2010 27 0
nwclient /fs_serv_10 14/06/2010 30 0
This will only be the case for direct NDMP backup. NDMP DSA backup
is a hybridization of NDMP and OTF and retains an OTF structure for
NDMP data – thus separating with a single filemark instead of 3.
Note: When NDMP savesets are discussed in this document, it is
assumed that they are created from direct NDMP backups and not from
NDMP DSA backups, unless otherwise stated.
A NDMP scanned-in media will therefore only be usable for saveset
recoveries.
NDMP and NDMP DSA volumes cannot use the –i switch to rebuild
index data; that is why the only recovery possible is a saveset recovery.
The scanner output will show the following:
12
Usage options and internals
EMC NetWorker
Usage of the Scanner Command
Scanner of NMM savesets
NMM provides an integration of PowerSnap, Replication Manager and
NetWorker in order to accommodate MS Windows server and
application consistent backup.
Due to this integration, some of the PowerSnap specific savesets, such as
the coverset are being backed up along with the data savesets and needs
be recovered in specific order.
Common NMM backups are composed of (at least):
One rollover saveset (containing the actual data (can be G:\ for
example).
One metadata saveset named LG_VSS_CLIENT******.xml.
One display saveset named VSS:\.
One cover saveset (generally hidden).
Scanning of the ssids (scanner –S) needs to be done in the following way
to be successful:
Scanner of the metadata saveset
Scanner of the display saveset
Scanner of the rollover saveset
In case where the tape content is unknown, the whole tape can be
scanned but each metadata savesets contained in the tape will need to be
scanned in one by one when the first scanner is completed
In the following example, the content of the tape wasn’t known, all 4
tapes were then scanned and content appears to be inconsistent
Once done scanning the four tapes, the display and metadata savesets
needs to be re-scanned in order for the mediaDB records to be consistent:
13
Usage options and internals
EMC NetWorker Usage of the Scanner command
Data scanned are set to “recoverable”; those data can then be recovered
via saveset recover only.
To recover them thru the NMM GUI, you must re-introduce the indexes
by using nsrck –L7.
Scanner of checkpoint-restarted savesets
The checkpoint-restart feature was introduced in NW7.6.1 and enables
the user to restart the backup up to the directory or file where the
backup was previously stopped/aborted.
Savesets that were backed up using that option do present a specific
attributes in the ssflags option: “k” and a new attribute in the mminfo:
“checkpoint_id”
Scanner of tapes containing those savesets needs to be done in the order
of backup for all the data to be scanned correctly.
If the tapes aren’t scanned in the correct way, you may end up with out-
of-sync data and some scanners will need to be done once again
Example:
14
Usage options and internals
EMC NetWorker
Usage of the Scanner Command
15
Usage options and internals
EMC NetWorker Usage of the Scanner command
16
Usage options and internals
EMC NetWorker
Usage of the Scanner Command
Mminfo Output after scanner:
bash-3.00# mminfo -av -q "checkpoint_id=1299493802"
volume type client date time size ssid fl lvl name
QXC0WO0X LTO Ultrium-3 racds013 03/07/11 16:00:02 31 GB 7648171 hrk full /aftd3/scannerdata
QXC0WO0Y LTO Ultrium-3 racds013 03/07/11 16:00:02 31 GB 7648171 mrk full /aftd3/scannerdata
QXC0WO0Z LTO Ultrium-3 racds013 03/07/11 16:00:02 31 GB 7648171 mrk full /aftd3/scannerdata
QXC0WO10 LTO Ultrium-3 racds013 03/07/11 16:00:02 31 GB 7648171 mrk full /aftd3/scannerdata
QXC0WO11 LTO Ultrium-3 racds013 03/07/11 16:00:02 31 GB 7648171 mrk full /aftd3/scannerdata
QXC0WO12 LTO Ultrium-3 racds013 03/07/11 16:00:02 31 GB 7648171 mrk full /aftd3/scannerdata
QXC0WO13 LTO Ultrium-3 racds013 03/07/11 16:00:02 31 GB 7648171 mrk full /aftd3/scannerdata
QXC0WO14 LTO Ultrium-3 racds013 03/07/11 16:00:02 24 GB 7648171 trk full /aftd3/scannerdata
All data was successfully recovered.
In the following example, the scanner was done by scanning the same
tapes but randomly and you can see the difference:
bash-3.00# mminfo -av -q "checkpoint_id=1299146028"
volume type client date time size ssid fl lvl name
QXC0WO03 LTO Ultrium-3 racds013 03/03/11 17:04:45 4119 MB 1869577430 ca full /aftd3/scannerdata
QXC0WO03 LTO Ultrium-3 racds013 03/03/11 17:15:14 2344 MB 1852800843 ca full /aftd3/scannerdata
QXC0WO03 LTO Ultrium-3 racds013 03/03/11 17:25:15 3940 MB 1836024229 ca full /aftd3/scannerdata
QXC0WO03 LTO Ultrium-3 racds013 03/03/11 17:35:09 10 GB 1802470391 cak full /aftd3/scannerdata
QXC0WO03 LTO Ultrium-3 racds013 03/03/11 17:55:05 4178 MB 1785694369 cik full /aftd3/scannerdata
QXC0WO0H LTO Ultrium-3 racds013 03/03/11 15:23:48 31 GB 1987011890 hik full /aftd3/scannerdata
17
Advanced recovery and troubleshooting
EMC NetWorker Usage of the Scanner command
QXC0WO0I LTO Ultrium-3 racds013 03/03/11 15:23:48 0 KB 1987011890 tik full /aftd3/scannerdata
QXC0WO0N LTO Ultrium-3 racds013 03/03/11 18:31:46 43 GB 1299157307 cak full /aftd3/scannerdata
QXC0WO0N LTO Ultrium-3 racds013 03/03/11 19:23:12 21 GB 1248828745 hrk full /aftd3/scannerdata
QXC0WO0O LTO Ultrium-3 racds013 03/03/11 19:23:12 31 GB 1248828745 mrk full /aftd3/scannerdata
QXC0WO0P LTO Ultrium-3 racds013 03/03/11 19:23:12 31 GB 1248828745 mrk full /aftd3/scannerdata
QXC0WO0Q LTO Ultrium-3 racds013 03/03/11 19:23:12 31 GB 1248828745 mrk full /aftd3/scannerdata
QXC0WO0R LTO Ultrium-3 racds013 03/03/11 19:23:12 31 GB 1248828745 mrk full /aftd3/scannerdata
QXC0WO0S LTO Ultrium-3 racds013 03/03/11 19:23:12 31 GB 1248828745 mrk full /aftd3/scannerdata
QXC0WO0T LTO Ultrium-3 racds013 03/03/11 19:23:12 31 GB 1248828745 mrk full /aftd3/scannerdata
QXC0WO0U LTO Ultrium-3 racds013 03/03/11 19:23:12 31 GB 1248828745 mrk full /aftd3/scannerdata
QXC0WO0V LTO Ultrium-3 racds013 03/03/11 19:23:12 3331 MB 1248828745 trk full /aftd3/scannerdata
The first tapes must be re-scanned to correct the mediaDB state.
Advanced recovery and troubleshooting
This section provides troubleshooting and advanced recovery techniques
when using the scanner command.
Pre-requisites
The following pre-requisites must be met to use the scanner command:
A pool must exist on NW server and must use same
capitalization as the original one.
The tape to be scanned must be loaded in a device using the
“Load without mount” of the NMC GUI or via the “nsrjb –ln”
command. After the tape is mounted, the device needs to be set
to service mode so that it is not automatically picked up for
other NW activities.
For continued savesets, scanner should be run on volumes in the
original order and sequentially.
Usage of the –z switch prevents the need to cancel out of
continuing savesets. The information as to where the data
continues is displayed (volume name if known or volid if not) in
the media database.
For PS and/or NMM data, refer to the “Scanner of NMM
savesets” section of this document.
18
Advanced recovery and troubleshooting
EMC NetWorker
Usage of the Scanner Command
Index or media database entries deleted, but volume is not yet
overwritten
If savesets have passed their retention policies, normal daily
maintenance removes them from the media and index databases.
The data are not actually removed physically from the media
unless the media is a File or Advanced File Device.
Regardless of media or index database record removal, data
stored on a physical or virtual tape will remain on the tape until
it gets relabeled. Data can still be retrieved by scanning the
volume.
As seen in the command usage, best practice is to scan the tape
and then run nsrck –L7 to recreate the indexes for the client on
which the recovery is needed.
The fastest option is generally to scan only the saveset needed
with the scanner –S command, forwarding to the right location
with the –f and –r switches, and then recover the data needed
via a Saveset Recover.
Importing data from a second datazone
Merging the Media or Index databases isn’t supported and there is no
plan to support it in the near future. The only supported way to import
data from one datazone to another is to run scanner against the tape or
other media that needs to be imported. In that particular case, two other
pre-requisites apply:
Volume name and/or Tape barcode must not exists in the
mediaDB
Client name must not already exists in the mediaDB
Scanner can then be done as mentioned previously; by scanning the
whole tape via scanner –m or by scanning only the needed saveset IDs. If
the pre-requisites cannot be met, scanner should not be done as it could
cause media database corruption. A workaround for the client or volume
name; would be to delete the existing volume or rename the existing
client before scanning the data. Verify data on volume (label, block size,
volid, actual data, etc).
The scanner command can be used as a data integrity checker upon
recovery failure.
19
Advanced recovery and troubleshooting
EMC NetWorker Usage of the Scanner command
Running the scanner command with the –v option will enable you to
verify the status of the tape and will report errors encountered
Example below shows the scanner of a tape, positioning and starting
reading at file number 2 (file number 1 is the tape label), and
encountering file number 99:
This is generally a sign of data loss, the first file number found on the
tape while reading is file number 99 which means that data from file
number 2 to 98 aren’t on the tape anymore. The mminfo commands
needs to be run to determine which savesets where affected (mediafile
and mediarec attributes of the mminfo command, see man mminfo for
more details).
Example below shows the scanner of a tape, positioning to file number
20, and finding file number 14 :
20
Advanced recovery and troubleshooting
EMC NetWorker
Usage of the Scanner Command
Recovering data on volume using scanner –x uasm
In the case where the bootstrap has been lost and where the data needs
to be recovered as soon as possible (or the tape containing the data is
known), data can be recovered directly by running the scanner
command using the –x uasm option.
With this option, the data stream, after being read by the scanner, is sent
to the uasm command (NetWorker module for save and recover) which
then extracts the data and writes it to the location specified (see the uasm
man page for details).
The only pre-requisite for this command is to ensure that sufficient space
is provided on the data destination path ( uasm –m option).
The following example is an extract of all data contained in the tape
loaded on drive /dev/rmt/12cbn to folder /tmp/recov.
# scanner -v /dev/rmt/12cbn -x uasm -rv -m /=/tmp/recov
8909:scanner: using '/dev/rmt/12cbn' as the device name
9000:scanner: /dev/rmt/12cbn: opened for reading
9003:scanner: /dev/rmt/12cbn: rewinding
9067:scanner: Rewinding done
9003:scanner: /dev/rmt/12cbn: rewinding
9067:scanner: Rewinding done
8968:scanner: Reading the label...
8969:scanner: Reading the label done
8936:scanner: scanning LTO Ultrium tape A99001 on /dev/rmt/12cbn
8937:scanner: volume id 2958892 record size 65536
created 1/11/11 22:55:24 expires 1/10/13 22:55:24
9003:scanner: /dev/rmt/12cbn: rewinding
9067:scanner: Rewinding done
8973:scanner: setting position from fn 0, rn 0 to fn 2, rn 0
9000:scanner: /dev/rmt/12cbn: opened for reading
8758:scanner: scanning file 2, record 0
8850:scanner: ssid 4264371869: found beginning of furious:/backuptest
8839:scanner: spawning `uasm -rv -m /=/tmp/recov8840:scanner: ' for ssid
4264371869 (furious:/backuptest)
21
Advanced recovery and troubleshooting
EMC NetWorker Usage of the Scanner command
/tmp/recov/backuptest/nw76_solaris_64.tar
8795:scanner: ssid 4264371869: 952 MB, 2 file(s)
/tmp/recov/backuptest/
29485:scanner: ssid 4264371869: scan complete
/tmp/recov/
8786:scanner: ssid 4264371869: 952 MB, 4 file(s)
9000:scanner: /dev/rmt/12cbn: opened for reading
8758:scanner: scanning file 3, record 0
8850:scanner: ssid 4247594673: found beginning of furious:index:84fcd496-
00000004-4ce6b0e8-4ce6b0e7-00010003-ba9a2323
8839:scanner: spawning `uasm -rv -m /=/tmp/recov8840:scanner: ' for ssid
4247594673 (furious:index:84fcd496-00000004-4ce6b0e8-4ce6b0e7-00010003-
ba9a2323)
29485:scanner: ssid 4247594673: scan complete
8786:scanner: ssid 4247594673: 3 KB, 4 file(s)
/tmp/recov/local2/data/nsr/index/furious/db6/4d2d0000/4d2d2692.rec
/tmp/recov/local2/data/nsr/index/furious/db6/4d2d0000/
/tmp/recov/local2/data/nsr/index/furious/db6/
/tmp/recov/local2/data/nsr/index/furious/
9000:scanner: /dev/rmt/12cbn: opened for reading
8758:scanner: scanning file 4, record 0
8850:scanner: ssid 4230817458: found beginning of furious:bootstrap
8839:scanner: spawning `uasm -rv -m /=/tmp/recov8840:scanner: ' for ssid
4230817458 (furious:bootstrap)
/tmp/recov/nsr
/tmp/recov/local2/data/nsr/res/nsrladb/00/000a4a8c00000000000000004cebb828
0a05a0df
/tmp/recov/local2/data/nsr/res/nsrladb/00/000a42a700000000000000004d181cd0
0a05a0df
/tmp/recov/local2/data/nsr/res/nsrladb/00/000a4bd900000000000000004d2c51e5
0a05a0df
/tmp/recov/local2/data/nsr/res/nsrladb/00/
[…]
/tmp/recov/local2/data/nsr/res/nsrdb/00/000a35fd00000000000000004ce6b0e50a
05a0df
/tmp/recov/local2/data/nsr/res/nsrdb/00/001435fd00000000000000004ce6b0e50a
05a0df
[…]
22
Advanced recovery and troubleshooting
EMC NetWorker
Usage of the Scanner Command
/tmp/recov/local2/data/nsr/res/nsrdb/09/000935fd00000000000000004ce6b0e50a
05a0df
/tmp/recov/local2/data/nsr/res/nsrdb/09/001335fd00000000000000004ce6b0e50a
05a0df
/tmp/recov/local2/data/nsr/res/jobsdb/general/00/e23e020b00000000000000004
d22e2600a05a0df
/tmp/recov/local2/data/nsr/res/jobsdb/general/00/e242020b00000000000000004
d22e2600a05a0df
/tmp/recov/local2/data/nsr/res/jobsdb/indication/00/
/tmp/recov/local2/data/nsr/res/jobsdb/indication/01/e243020b00000000000000
004d22e2600a05a0df
/
/tmp/recov/local2/data/nsr/res/jobsdb/savejobs/00/
/tmp/recov/local2/data/nsr/res/jobsdb/savejobs/01/e23f020b0000000000000000
4d22e2600a05a0df
/tmp/recov/local2/data/nsr/res/jobsdb/ssninfo/00/e248020b00000000000000004
d22e2600a05a0df
/tmp/recov/local2/data/nsr/res/jobsdb/ssninfo/00/
/tmp/recov/local2/data/nsr/res/jobsdb/ssninfo/01/001f4be400000000000000004
d2c51eb0a05a0df
/tmp/recov/local2/data/nsr/res/jobsdb/ssninfo/
/tmp/recov/local2/data/nsr/res/jobsdb/
/tmp/recov/local2/data/nsr/res/servers
/tmp/recov/local2/data/nsr/res/
nsrmmdbasm -r /tmp/recov/local2/data/nsr/mm/mmvolume6/
/tmp/recov/local2/data/nsr/mm/
29485:scanner: ssid 4230817458: scan complete
8786:scanner: ssid 4230817458: 287 KB, 260 file(s)
9000:scanner: /dev/rmt/12cbn: opened for reading
9000:scanner: /dev/rmt/12cbn: opened for reading
9000:scanner: /dev/rmt/12cbn: opened for reading
8761:scanner: done with LTO Ultrium tape A99001
9003:scanner: /dev/rmt/12cbn: rewinding
9067:scanner: Rewinding done
#
23
Principals KBs
EMC NetWorker Usage of the Scanner command
Principals KBs
LGTsc26443 **mminfo query returning more lines for smaller timeframe
This issue is causing some problems when verifying that thru mminfo
after scanning tapes; the result of the mminfo query can be wrong or
report nothing when use with the –a for example.
Conclusion
The scanner command is the best and only supported way, to inject data
from another datazone into your current NetWorker server. It is suited
to rebuilding deleted volumes, restoring index information, direct
recovery, and so on.
24
Conclusion
EMC NetWorker
Usage of the Scanner Command
Copyright © 2009-2015 EMC Corporation. All Rights Reserved.
EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.
THE INFORMATION IN THIS PUBLICATION IS PROVIDED "AS IS." EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.
For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com.
All other trademarks used herein are the property of their respective owners.