Unsolved
This post is more than 5 years old
18 Posts
1
15418
How to restore backup index from PROD Networker 7.4.4 to DR networker 7.6.1
Hi, Brothers
How to restore all client backup indexes from PROD Networker to DR networker
Production Networker
Networker Server : 7.4.4
OS : Sun SPARC Solaris 10
DR Networker
Networker Server : 7.6.1
OS : Windows 2008 R2
I need to perform all Production data restore in the DR site.
However, I will not prefer the method of client backup index rebuild from tape media using scanner one by one. I would like to recover the backup index quickly in the DR networker.
How to quick do it?
So I can follow normally procedure to restore all data. Create all backup clients....
Mike
lee6
68 Posts
0
June 2nd, 2011 12:00
are you backing up your index's now?
I have used the doc
I do mine with the command
Disaster Recovery Guide
this has worked well for me
savegrp -v -O -l full -G metadata
metadata is a group in groups with all of the clients selected
this should give you one tape of all of your index's
from the install of 7.6.1
Task 1: Prepare to update the NetWorker software to release 7.6 and later
To update the NetWorker software to release 7.6 and later:
1. Before updating, make notes of the current database location and port numbers
used before removing the current installation.
2. Verify that the target computer satisfies the requirements.
“UNIX requirements”
on page 16
provides details.
3. Make a copy of the current database and store it in a safe location.
4. Back up all client file indexes and generate a bootstrap for the server. If a current
bootstrap does not exist, or a backup of all client file indexes, perform scheduled
backups on all clients before updating the software. For example, to save the
bootstrap information, type this command:
savegrp -O group
Note:
Ensure that all clients are included in the groups to be backed up.
5. Record the latest bootstrap save set ID and its associated volume label. To obtain
this information, type this command:
mminfo -B
6. If the NetWorker software is not currently installed in the default location, record
the location of the client file indexes.
then for the restore
Task 4: Recover the server bootstrap
from Windows or UNIX systems
This task describes how to recover the bootstrap save set from within either a
Windows or UNIX system. Recovering the bootstrap overwrites the media database
and recovers the resource files.
Recovering a NetWorker server
35
Recovering a NetWorker Server
Note:
The mmrecov command is used to recover only the media database and resource files. To
recover the client file indexes (including the NetWorker server’s own client file index), use the
nsrck
command. The NetWorker Command Reference Guide provides details about the mmrecov
and
nsrck commands.
To recover the bootstrap save set:
Note:
Steps 1 and 2 are required when using the -N option with the mmrecov command.
1. Unmount all volumes including tape, file type, advanced file type devices, and
cloud volumes.
a. In the NetWorker Administration interface, click
Devices.
b. Select
Devices in the navigation tree. The Devices detail table appears.
c. Right-click a device and select
Unmount.
2. Enable the CDI (Common Device Interface) attribute on all tape devices.
Note: NDMP, AlphaStor, and optical devices do not support CDI.
a. In the NetWorker Administration interface, click
Devices.
b. From the View menu, select
Diagnostic Mode.
c. Select
Devices in the navigation tree. The Devices detail table appears.
d. Double-click a device in the Devices table (or right-click the device and select
Properties
).
e. Select the
Advanced tab. In the Device Configuration area, locate the CDI
settings and select
SCSI commands.
The
EMC NetWorker Administration Guide provides more details about CDI
considerations.
f. Stop and restart the NetWorker server services/daemons.
3. Run the
mmrecov -N command.
Note: Using the
-N option sets the Scan Needed flag on ALL volumes to protect against the
possibility of overwriting data that was backed up after the last bootstrap was created. The
–F
flag can be used in conjunction with the –N flag to protect only advanced file type
devices (AFTDs). When the
-N flag is set and you attempt to recover data from a tape
volume that has newer save sets than what is recorded in the bootstrap, a message displays
explaining how to update the bootstrap, to avoid the possibility of overwriting the newer
data. The message will identify the starting file and record number to scan into the media
database (and client file index if desired).
In the case of an AFTD, the device will be marked read-only and the entire AFTD must be
scanned in to avoid the possibility of overwriting newer data. Because the
-N option works
only with tape devices that support CDI on CDI-enabled devices, the Scan Needed flag is
ignored on NDMP, AlphaStor, optical drives, or any tape device that has had CDI disabled.
Although AFTDs do not use CDI, the Scan Needed flag will be set if the
–N (and –F) option
is used for these devices. For more information on CDI usage restrictions, refer to the
Configuring Tape Devices for EMC NetWorker
EMC NetWorker Release 7.6 Service Pack
36 2 Disaster Recovery Guide
Recovering a NetWorker Server
If, within a Windows environment, you use clone volumes and have not loaded
all of the necessary volumes,
mmrecov prompts you for the original volume. In
that case:
a. Press
Ctrl - c to exit mmrecov.
b. Restart the NetWorker Backup and Recovery Service and the NetWorker
Remote Exec Service.
c. Run the
mmrecov -N command to recover the bootstrap.
Note: The
mmrecov command overwrites the server’s media database. However,
mmrecov
does not overwrite the resource database. Instead, mmrecov recovers the
resource database to an alternate location.
If, in a UNIX environment, the predisaster resource database was located in the
default directory, which is /nsr/res, it is recovered to /nsr/res.R.
If the predisaster resource database was linked, then the resource database will be
recovered to the link’s target directory. For example, if
/nsr/res was linked to a
directory named
/bigres, then the resource database will be recovered to a
directory named
/bigres.
4. If the server has devices configured and enabled, this message appears.
What is the name of the device you plan on using [xxxx]?
Where
xxxx identifies the default device name. If you receive this message, enter
the name of the device you are using for the recovery.
5. When this message appears, enter the save set ID for the latest bootstrap.
Enter the latest bootstrap save set ID []:
20076
If you are recovering a cloned version of the bootstrap, specify the save set ID
associated with the clone.
6. When this message appears, enter the file number to begin the recovery.
Enter starting file number (if known) [0]:
130
If you do not know the correct file number, press
Return. to accept the default of
zero.
7. When this message appears, enter the first record number to begin the recovery.
Enter starting record number (if known) [0]:
0
If you do not know the correct record number, press
Return. to accept the default
of zero.
8. When prompted, insert the volume containing the appropriate save set ID, as
entered
20076 in step 3.
Once you have loaded the appropriate volume, this message appears:
Scanning xxx for save set 20076; this might take a while...
Note: In both of these examples,
xxx represents the device name previous entered in step 2.
NetWorker then scans the volume for the appropriate save set and recovers it. Use
the NetWorker Management Console to monitor the recovery.
Recovering a NetWorker server
37
Recovering a NetWorker Server
The NetWorker media database and resource database are recovered when this
message appears:
If your resource files were lost, they are now recovered in the
‘res.R’
directory. Copy or move them to the ‘res’ directory, after you have
shut
down the service. Then restart the service.
Otherwise, just restart the service.
If the on-line index for the server-name was lost, it can be
recovered
using the nsrck command.
Task 4: Recover the server bootstrap
from Windows or UNIX systems
This task describes how to recover the bootstrap save set from within either a
Windows or UNIX system. Recovering the bootstrap overwrites the media database
and recovers the resource files.
Recovering a NetWorker server
35
Recovering a NetWorker Server
Note:
The mmrecovcommand is used to recover only the media database and resource files. To
recover the client file indexes (including the NetWorker server’s own client file index), use the
nsrck
command. The NetWorker Command Reference Guide provides details about themmrecov
and
nsrck commands.
To recover the bootstrap save set:
Note:
Steps 1 and 2 are required when using the -N option with the mmrecovcommand.
1. Unmount all volumes including tape, file type, advanced file type devices, and
cloud volumes.
a. In the NetWorker Administration interface, click
Devices.
b. Select
Devicesin the navigation tree. The Devices detail table appears.
c. Right-click a device and select
Unmount.
2. Enable the CDI (Common Device Interface) attribute on all tape devices.
Note: NDMP, AlphaStor, and optical devices do not support CDI.
a. In the NetWorker Administration interface, click
Devices.
b. From the View menu, select
Diagnostic Mode.
c. Select
Devicesin the navigation tree. The Devices detail table appears.
d. Double-click a device in the Devices table (or right-click the device and select
Properties
).
e. Select the
Advancedtab. In the Device Configuration area, locate the CDI
settings and select
SCSI commands.
The
EMC NetWorker Administration Guideprovides more details about CDI
considerations.
f. Stop and restart the NetWorker server services/daemons.
3. Run the
mmrecov -N command.
Note: Using the
-N option sets the Scan Needed flag on ALLvolumes to protect against the
possibility of overwriting data that was backed up after the last bootstrap was created. The
–F
flag can be used in conjunction with the –Nflag to protect only advanced file type
devices (AFTDs). When the
-Nflag is set and you attempt to recover data from a tape
volume that has newer save sets than what is recorded in the bootstrap, a message displays
explaining how to update the bootstrap, to avoid the possibility of overwriting the newer
data. The message will identify the starting file and record number to scan into the media
database (and client file index if desired).
In the case of an AFTD, the device will be marked read-only and the entire AFTD must be
scanned in to avoid the possibility of overwriting newer data. Because the
-Noption works
only with tape devices that support CDI on CDI-enabled devices, the Scan Needed flag is
ignored on NDMP, AlphaStor, optical drives, or any tape device that has had CDI disabled.
Although AFTDs do not use CDI, the Scan Needed flag will be set if the
–N (and –F) option
is used for these devices. For more information on CDI usage restrictions, refer to the
Configuring Tape Devices for EMC NetWorker
technical note on Powerlink.
EMC NetWorker Release 7.6 Service Pack
36 2 Disaster Recovery Guide
Recovering a NetWorker Server
If, within a Windows environment, you use clone volumes and have not loaded
all of the necessary volumes,
mmrecovprompts you for the original volume. In
that case:
a. Press
Ctrl - c to exit mmrecov.
b. Restart the NetWorker Backup and Recovery Service and the NetWorker
Remote Exec Service.
c. Run the
mmrecov -N command to recover the bootstrap.
Note: The
mmrecov command overwrites the server’s media database. However,
mmrecov
does not overwrite the resource database. Instead, mmrecovrecovers the
resource database to an alternate location.
If, in a UNIX environment, the predisaster resource database was located in the
default directory, which is /nsr/res, it is recovered to /nsr/res.R.
If the predisaster resource database was linked, then the resource database will be
recovered to the link’s target directory. For example, if
/nsr/reswas linked to a
directory named
/bigres, then the resource database will be recovered to a
directory named
/bigres.
4. If the server has devices configured and enabled, this message appears.
What is the name of the device you plan on using [xxxx]?
Where
xxxxidentifies the default device name. If you receive this message, enter
the name of the device you are using for the recovery.
5. When this message appears, enter the save set ID for the latest bootstrap.
Enter the latest bootstrap save set ID []:
20076
If you are recovering a cloned version of the bootstrap, specify the save set ID
associated with the clone.
6. When this message appears, enter the file number to begin the recovery.
Enter starting file number (if known) [0]:
130
If you do not know the correct file number, press
Return. to accept the default of
zero.
7. When this message appears, enter the first record number to begin the recovery.
Enter starting record number (if known) [0]:
0
If you do not know the correct record number, press
Return. to accept the default
of zero.
8. When prompted, insert the volume containing the appropriate save set ID, as
entered
20076in step 3.
Once you have loaded the appropriate volume, this message appears:
Scanning xxx for save set 20076; this might take a while...
Note: In both of these examples,
xxxrepresents the device name previous entered in step 2.
NetWorker then scans the volume for the appropriate save set and recovers it. Use
the NetWorker Management Console to monitor the recovery.
Recovering a NetWorker server
37
Recovering a NetWorker Server
The NetWorker media database and resource database are recovered when this
message appears:
If your resource files were lost, they are now recovered in the
‘res.R’
directory. Copy or move them to the ‘res’ directory, after you have
shut
down the service. Then restart the service.
Otherwise, just restart the service.
If the on-line index for th
e server-name was lost, it can be
recovered
using the nsrck command.
Task 8a: Recover the NetWorker server’s client file indexes
After the NetWorker server’s bootstrap save set is recovered, you can recover the
client file indexes in any order; it is not necessary to recover the server’s own client
file index before recovering the index of any other client.
Recovering a NetWorker server
47
If the clients have the NetWorker client software installed, you can run manual and
scheduled backups as soon as the NetWorker server bootstrap is recovered. You also
can recover complete save sets. You cannot, however, browse a client’s save sets until
you recover the client file index.
To recover the client file indexes:
1. To recover the client file indexes, run one of these commands from the NetWorker
server:
• For
all clients enternsrck -L7
• For a
specific client enter nsrck -L7client_name
2. If you are recovering the client file indexes from a clone volume, you may be
prompted to load the original volume. In that case:
a. Press
Ctrl - c to exit nsrck.
b. Restart these NetWorker services:
– NetWorker Backup and Recovery Service
– NetWorker Remote Exec Service
c. Recover the client file indexes by running one of these commands:
– For
all clients enternsrck -L7
– For a
specific client enter nsrck -L7client_name
Recovering a NetWorker Server
technical note on Powerlink.ble1
14.3K Posts
0
June 2nd, 2011 13:00
Hi Mike,
Your DR should reflect original state. By saying that, I see that you use different OS and versions between original site and DR. That doesn't make sense as it makes restore either hard and at certain points even not possible.
dugans1
186 Posts
0
June 2nd, 2011 16:00
https://community.emc.com/message/489442#489442
This is when i made my Networker server a VM.
Tip.
Clone the VM and move it to your DR site and leave it shutdown. if you have a Virtual environment.
https://community.emc.com/message/444734#444734
This is when i made my Networker server NSR directory a mount point and then replicated it to my DR Site.
Easy. Only thin to remember is to delete your clone DR VM when you do SP installs or updates and re-create.
in a DR, fire up the VM and attach the month point. DR Complete. All indexes and bootstrap info will be there.
ASL-Mike
18 Posts
0
June 2nd, 2011 19:00
Under the budget constraint, we would like to consolidate both testing environment and DR environment into one. Maybe virtual environment instead.