cancel
Showing results for 
Search instead for 
Did you mean: 

Steps to restore 2nd and 3rd copies of image from a different media server

ericmagallanes
Level 3

Hi all,

 

Need some clarification regarding my NBU backup architecture, please see below:

I have a,

1. Primary Copy - Located on Primary Site MSDP (NBU Master Server) 

2. 2nd Copy - Located on Offsite MSDP (NBU Media Server B)

3. 3rd Copy - Located Offsite as well - Tape Out (LTO4) (NBU Media Server B)

I wanted to test restoration from the Tape Media which is my 3rd copy. Can you guys help how to do this?

 

Thanks a lot! 

1 ACCEPTED SOLUTION

Accepted Solutions

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

If restore media is LTO4 and tape drives are LTO5, change one of the tape drives in robot where tape is to hcart.

...BUT....

The tape is in robot 8.
You gave us device output of robot 0, 1 and 2.

Which media server have access to robot 8?
Have you changed media ownership? Or added Force_Restore_Media entry?

Media 'belongs' to PRUXBK11_bk. Restore requests will be sent to that media server by default - unless you have done 'something' to send restore request to another media server.

View solution in original post

20 REPLIES 20

RamNagalla
Moderator
Moderator
Partner    VIP    Certified

you just need to make your 3rd copy as a primary copy .. and trigger the restore..

it will automatically pick the data from the 3rd copy as it is a primary copy..

 

to make the 3 rd copy as primary copy..

Netbackup GUI--> catalog ..> select copy as 3 and provide client name and required dates..

it will list you the all avalaible copy 3 images , and right click on the required image and select "set as primary" 

then trigger the restore for the data that is on image that you set copy3 as primary copy from BAR window.

 

hope this helps.. 

Deepak_G
Level 6
Certified

There is documented technote on how to do it. You need to set the copy which you want to restore as primary copy. Using GUI seemed as a better option.

http://www.symantec.com/docs/TECH64592

Please check and let us know if you have any questions or issues on it.

Extract from it

Via the GUI:

1. Go to the Catalog section of the GUI.
2. Select 'verify' and the top right the copy number of the current image you wish to use.
3. For the Date/Time Range From: value, enter the Start Date: used in the Backup, Archive and Restore GUI
4. For the Date/Time Range To: value, enter the End Date: used in the Backup, Archive and Restore GUI
5. Click Search Now
6. Right click on image you wish to restore from and click 'Set primary copy'.
Now when you go back to Restore GUI you can restore as normal and it will default to this copy

ericmagallanes
Level 3

Hi Nagalla/Deepak,

Thanks for the info. But another thing I want to clarify is can I bring the Tape Media (Copy 3) on the primary site? Can it be done? Because my problem is that I have a 450Gb data on a 20mbps wan link, if the Tape Media (3rd copy) cannot be brought to the Priamry site then it'll take ages to restore the files.

 

Deepak_G
Level 6
Certified

When you make an copy as primary copy the information gets updated on the netbackup EMM database. So you dont have to move them manually to any sites.

Since you took data to disk it would have been faster and when you recover them from LTO4 media's it will be much slower.

Deepak_G
Level 6
Certified

If you just wanted to test the alternate copy restore, you can try it from second copy which is on the MSDP.

RamNagalla
Moderator
Moderator
Partner    VIP    Certified

 


ericmagallanes,
 
 
do you have media server in remote site?
are you using Remote media server to make the copy 3 ?
 
if yes, 
you have the answer for your question "But another thing I want to clarify is can I bring the Tape Media (Copy 3) on the primary site? Can it be done? Because my problem is that I have a 450Gb data on a 20mbps wan link, if the Tape Media (3rd copy) cannot be brought to the Priamry site then it'll take ages to restore the files."
 
when you bring the tape media (3rd copy) to primary site, you need to use alternate media server restore
 
for that you need to use the FORSE RESTORE option.. once you bring the tape to Primary site..
 
check the below tech note for details.. 
 
http://www.symantec.com/business/support/index?page=content&id=TECH7582
 
hope this helps.. 
 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Easier solution:

1. Use bprestore with '-copy #'

2. Create ALT_RESTORE_COPY_NUMBER touch file in netbackup folder on master server. Put copy number to restore from in this file.

See http://www.symantec.com/docs/TECH64592 for details.

ericmagallanes
Level 3

Hi All,

 

Thanks for your valuable comments, actually my approach is that I will be having a different retention periods on all the copies. Like 1st copy will have 2 weeks retention, 2nd copy 1 month retention, and say 1 year for 3rd copy.

So when 1st and 2nd copy expires I will use the 3rd copy to restore to my Primary site and will need to bring the Tape Media to the Primary site itself. I will try this technote as suggested by Nagalla http://www.symantec.com/business/support/index?page=content&id=TECH7582 and let you guys know.

 

Thanks a lot..

 

 

ericmagallanes
Level 3

Hi all,

 

I have tried to bring the tape media to my primary site and set the 3rd copy to primary but I faced the below issue, can please help on this?

 

12/18/2012 21:23:11 - begin Restore
12/18/2012 21:23:14 - number of images required: 3
12/18/2012 21:23:14 - media needed: 0004L4
12/18/2012 21:23:45 - restoring from image SourceImage_1354975113
12/18/2012 21:23:46 - Info bpbrm (pid=10223730) DestinationHost_bk is the host to restore to
12/18/2012 21:23:46 - Info bpbrm (pid=10223730) telling media manager to start restore on client
12/18/2012 21:23:47 - Info bpbrm (pid=10223730) spawning a brm child process
12/18/2012 21:23:47 - Info bpbrm (pid=10223730) child pid: 18022510
12/18/2012 21:23:47 - connecting
12/18/2012 21:23:47 - requesting resource 0004L4
12/18/2012 21:23:48 - Error bptm (pid=10420388) NBJM returned an extended error status: No drives are available (2001)
12/18/2012 21:23:48 - Info bpbrm (pid=10223730) got ERROR 252 from media manager
12/18/2012 21:23:48 - Info bpbrm (pid=10223730) terminating bpbrm child 18022510 jobid=8423
12/18/2012 21:23:48 - restored from image SourceImage_1354975109; restore time: 0:00:03
12/18/2012 21:23:48 - Error nbjm (pid=11206716) NBU status: 830, EMM status: No drives are available
12/18/2012 21:23:48 - Error nbjm (pid=11206716) NBU status: 830, EMM status: No drives are available
12/18/2012 21:23:48 - Info bpbrm (pid=18022510) start tar on client

RamNagalla
Moderator
Moderator
Partner    VIP    Certified

hi,

did you check , the media server that you are using have the dirves for the same robot , that was actaully used for backup.(duplicataion)

what is the media server that you are using?

please provide the tpconifg -d and vmoprcmd -d outputs from the media server

and also for vmquery -m <mediaid>

it would help to compare the Drives avaliablity..

 

 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Please show us output of the following:

nbemmcmd -listmedia -mediaid 0004L4 

as well as output of the following on the media server at the primary site that needs to perform the restore:

tpconfig -l.

You need to ensure that the same density drives are available that matches media density.

ericmagallanes
Level 3

Hi Marianne,

Below is the output:

root@PRUXBK11:/ #nbemmcmd -listmedia -mediaid 0004L4
NBEMMCMD, Version: 7.5.0.3
====================================================================
Media GUID:                     5c16ed4a-4194-11e2-8000-94bfe7ba140e
Media ID:                       0004L4
Partner:                        -
Media Type:                     HCART
Volume Group:                   001_00008_TLD
Application:                    Netbackup
Media Flags:                    1
Description:                    Added by Media Manager
Barcode:                        A00004L4
Partner Barcode:                --------
Last Write Host:                PRUXBK11_bk
Created:                        12/08/2012 16:07
Time Assigned:                  12/08/2012 16:12
First Mount:                    12/08/2012 16:13
Last Mount:                     12/09/2012 18:45
Volume Expiration:              -
Data Expiration:                12/23/2012 14:08
Last Written:                   12/09/2012 19:02
Last Read:                      -
Robot Type:                     TLD
Robot Control Host:             PRDWDM01
Robot Number:                   8
Slot:                           11
Side/Face:                      -
Cleanings Remaining:            -
Number of Mounts:               10
Maximum Mounts Allowed:         0
Media Status:                   ACTIVE
Kilobytes:                      380175101
Images:                         16
Valid Images:                   16
Retention Period:               1
Number of Restores:             0
Optical Header Size Bytes:      1024
Optical Sector Size Bytes:      0
Optical Partition Size Bytes:   0
Last Header Offset:             5940273
Adamm Guid:                     00000000-0000-0000-0000-000000000000
Rsm Guid:                       00000000-0000-0000-0000-000000000000
Origin Host:                    NONE
Master Host:                    PRUXBK11_bk
Server Group:                   NO_SHARING_GROUP
Upgrade Conflicts Flag:
Pool Number:                    12
Volume Pool:                    Novena_Tape_Pool
Previous Pool Name:             -
Vault Flags:                    -
Vault Container:                -
Vault Name:                     -
Vault Slot:                     -
Session ID:                     -
Date Vaulted:                   -
Return Date:                    -
Media on Hold:                  0
====================================================================
Command completed successfully.
 

root@PRUXBK11:/usr/openv/volmgr/bin #./tpconfig -l
Device Robot Drive       Robot                    Drive                Device
Type     Num Index  Type DrNum Status  Comment    Name                 Path
robot      0    -    TLD    -       -  -          -                    /dev/smc0
  drive    -    1 hcart2    1      UP  -          IBM.ULT3580-HH5.000  /dev/rmt1.1
  drive    -    2 hcart2    2      UP  -          IBM.ULT3580-HH5.001  /dev/rmt2.1
robot      1    -    TLD    -       -  -          -                    /dev/smc2
  drive    -    3 hcart2    1      UP  -          IBM.ULT3580-TD5.000  /dev/rmt3.1
  drive    -    4 hcart2    2      UP  -          IBM.ULT3580-TD5.001  /dev/rmt4.1
  drive    -    7 hcart2    3      UP  -          IBM.ULT3580-TD5.014  /dev/rmt7.1
  drive    -    8 hcart2    4      UP  -          IBM.ULT3580-TD5.015  /dev/rmt9.1
robot      2    -    TLD    -       -  -          -                    /dev/smc3
  drive    -    5 hcart2    1      UP  -          IBM.ULT3580-TD5.002  /dev/rmt5.1
  drive    -    6 hcart2    2      UP  -          IBM.ULT3580-TD5.003  /dev/rmt6.1
  drive    -    9 hcart2    4      UP  -          IBM.ULT3580-TD5.020  /dev/rmt10.1
  drive    -   10 hcart2    3      UP  -          IBM.ULT3580-TD5.021  /dev/rmt8.1
 

 

Andy_Welburn
Level 6

Per Mariannes' earlier post:

You need to ensure that the same density drives are available that matches media density.

From your output:

root@PRUXBK11:/ #nbemmcmd -listmedia -mediaid 0004L4
....
Media Type:                     HCART

and

root@PRUXBK11:/usr/openv/volmgr/bin #./tpconfig -l
...
  drive    -    1 hcart2    1      UP  -          IBM.ULT3580-HH5.000  /dev/rmt1.1
  drive    -    2 hcart2    2      UP  -          IBM.ULT3580-HH5.001  /dev/rmt2.1
...
  drive    -    3 hcart2    1      UP  -          IBM.ULT3580-TD5.000  /dev/rmt3.1
  drive    -    4 hcart2    2      UP  -          IBM.ULT3580-TD5.001  /dev/rmt4.1
  drive    -    7 hcart2    3      UP  -          IBM.ULT3580-TD5.014  /dev/rmt7.1
  drive    -    8 hcart2    4      UP  -          IBM.ULT3580-TD5.015  /dev/rmt9.1
...
  drive    -    5 hcart2    1      UP  -          IBM.ULT3580-TD5.002  /dev/rmt5.1
  drive    -    6 hcart2    2      UP  -          IBM.ULT3580-TD5.003  /dev/rmt6.1
  drive    -    9 hcart2    4      UP  -          IBM.ULT3580-TD5.020  /dev/rmt10.1
  drive    -   10 hcart2    3      UP  -          IBM.ULT3580-TD5.021  /dev/rmt8.1

....so no HCART drives hence the error: NBU status: 830, EMM status: No drives are available

Now we know 0004L4 is LTO4 (type HCART), but what are your drives? Could be LTO2 or LTO5 - hopefully the latter & you'll be able to change (temporarily) the designation to allow the restore.

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

If restore media is LTO4 and tape drives are LTO5, change one of the tape drives in robot where tape is to hcart.

...BUT....

The tape is in robot 8.
You gave us device output of robot 0, 1 and 2.

Which media server have access to robot 8?
Have you changed media ownership? Or added Force_Restore_Media entry?

Media 'belongs' to PRUXBK11_bk. Restore requests will be sent to that media server by default - unless you have done 'something' to send restore request to another media server.

ericmagallanes
Level 3

Hi Andy/Marianne,

The Drive I am using for restore now is LTO5(Primary Site) and the previous drive we have is LTO4(Off Site).

Can you please let me know how to change it temporarily to HCART I am running NBU 7.5.0.3?

Also, the tape now is in Robot 0 and the Media Server that has a current access to the tape is PRUXBK11_bk. I also did add the  Force_Restore_Media entry on the bp.conf and changes media ownership as well.

 

Thanks..

ericmagallanes
Level 3

I managed to change the type to HCART, but when I tried to update volume I got this error:

 

Generating list of recommended changes ...

Proposed Change(s) to Update the Volume Configuration
=====================================================
Logically add new media 0018L4 (barcode A00018L4) to robot slot 34.
Logically add new media 0004L4 (barcode A00004L4) to robot slot 38.
Logically add new media 0012L4 (barcode A00012L4) to robot slot 42.
Logically add new media 0009L4 (barcode A00009L4) to robot slot 44.
Updating volume configuration ...

Processing new media added to the robotic library by logically
adding media with new media IDs as follows...
 Media ID Slot
 ======== ====
 

Update failed: could not add new media ID '0018L4' into slot 34
Insert media failed:
media ID not unique in database (34)

 


 

Andy_Welburn
Level 6

You could use tpconfig but probably easier to use the GUI - double-click or right-click>change the drive under Media & Device Management>Devices>Drives (will prompt to restart service).

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Easiest is to change device properties in the GUI. Else, use tpconfig (text-based menu) to select a drive and change density. Else, all-in-one command: 'tpconfig -update -drive <index-number> -type <drvtype>'

 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Did you move the tapes to 'Standalone' after removing it from original robot?