Forum Discussion

Andrew_Madsen's avatar
11 years ago

Automated DB2 redirected restore.

Environment:

 

Master Server - SLES 11

Media Server 1 - NBU5220

Media Server 2 - NBU5220

Clients:

Client 1 - SLES 11

Client 2 - SLES 11

PDDO - NBU5020

Situation:

Client 1 is a production DB2 server sitting in a DMZ serviced by Media Server 1. Client 2 is a development DB2 server sitting in a different DMZ serviced by Media Server 2. The backup of Client 1 is a User Directed (Application Backup type) backup.  Every week there is a refresh of Client 2 from the latest backup of Client 1. The image is stored in the PDDO and both Media Servers have access to the PDDO. Our DBA's want to automate the restore but what seem to break down is the media server ownership. Client 2 and Media Server 1 are not accessible. to each other. 

 

How do I automate the image ownership so Client2 can do a restore of an image from Client 1 through Media Server 2?

 

  • I am not sure FORCE_RESTORE_MEDIA_SERVER is the right choice when only single images need modification and not a entire media server.

    I found this command - I think it can do the job:

    bpimage -newserver <new_servername> -oldserver <old_servername> -id {backupid}

    This command will change the media server ownership so a restore can take place on the media server located in the DMZ.

    https://www-secure.symantec.com/connect/forums/changing-backup-owner

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

    Best Regards

    Nicolai

  • by any chance did you try with FORCE_RESTORE_MEDIA_SERVER in bp.conf

    i am not sure how it works with PDDO but just though of checking it... 

  • If DB2 resides on SAN storage:

    Have you tried to use snapshot methods, or advanced SAN client with off-host funcionality?

    This could incredibly speed up your procedure.

  • Hi

     

    You have to open Netbackup ports between Master, media servers and clients

     

    The TCP port requirements for the default configuration; without overriding connect options in the Client Attributes (bpclient), or Firewall (CONNECT_OPTIONS) settings, or separate master and EMM servers, or legacy security considerations are as follows:
     
    Master server to client requires the TCP port for 13724 .

    Client to master server requires the TCP port for 13724 for client-initiated, not server-initiated, operations.

    Media server to client requires the TCP port for 13724 and PBX/1556.

    Master server to/from media servers requires the TCP ports for 13724 and PBX/1556,

    Media server to media server requires the TCP port for 13724 and PBX/1556, bi-directional. ยท     

    Note: traffic will be bidirectional

  • Ask your firewal team to write a firewall rule to netbackup open ports between
    Master server, Media servers and Clients

     

     

  • I am not sure FORCE_RESTORE_MEDIA_SERVER is the right choice when only single images need modification and not a entire media server.

    I found this command - I think it can do the job:

    bpimage -newserver <new_servername> -oldserver <old_servername> -id {backupid}

    This command will change the media server ownership so a restore can take place on the media server located in the DMZ.

    https://www-secure.symantec.com/connect/forums/changing-backup-owner

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

    Best Regards

    Nicolai

  • Thanks Nicoli. That should do it. I will see if we cannot implement that in the script. I knew FORCE_RESTORE would be bad because that affects all images backed up by the old media server not just the targeted one.