Forum Discussion

shanuintouch's avatar
8 years ago

How to perform cascade OPT-DUP Between 3 storage device?

Hi All,

Thanks for your always help!!

Currently i am performing a test scenario, which includes cascade OPT-DUP operation.

Here is the operation which i need to perform.

Cascade Opt-dup from Storage_Server_A to Storage_Server_B, and then Storage_Server_B to Storage_Server_C.

Below is the way which i am thinking to proceed for this test.

ON NBU Server:

  1. For Storage_Server_A:
    • Create Storage Server
    • Create Disk Pool
    • Create Storage Unit -> STU_A
  2. For Storage_Server_B:
    • Create Storage Server
    • Create Disk Pool
    • Create Storage Unit -> STU_B
  3. For Storage_Server_C:
    • Create Storage Server
    • Create Disk Pool
    • Create Storage Unit -> STU_C
  4. Create SLP(SLP_1) for opt-dup with residence STU_A to STU_B.
  5. For Storage_Server_A:
    • Create police(POL_1) and include residence as SLP_1.
    • Create Schedule and include backup data.
  6. Create SLP(SLP_2) for opt-dup with residence STU_B to STU_C.(confusion about it, what kind of SLP should i create)
  7. Initiate backup for policy POL_1

After this images will be backed up to Storage_Server_A and then first opt-dup will be performed automatically through SLP_1 and images will be copied to Storage_Server_B.

Now my confusion is, whether the above steps will initiate the SLP_2 automatically for coping the images(second opt-dup) from Storage_Server_B to Storage_Server_C?

Or my understanding is wrong and there is some other way to initiate the second opt-dup?

 

Please give your valuable suggestion over this.

Thanks in advance

 

 

 

 

  • sdo's avatar
    sdo
    8 years ago

    i.e. Marianne is saying that with an SLP you can do this...

    ...a three layer cascade:

    --> Backup to STU-A
    --> --> Duplication to STU-B
    --> --> --> Duplication to STU-C

    ...or this, which uses STU-A as the source to duplicate from for both copies/duplications:

    --> Backup to STU-A
    --> --> Duplication to STU-B
    --> --> Duplication to STU-C

    .

    N.B:  The only simple automated way to do this is using one SLP.  You cannot use two SLPs, i.e. this will not work:

    SLP1:
    --> Backup to STU-A
    --> --> Duplication to STU-B
    
    SLP2:
    --> Duplication

    ...because an SLP has to start with a "backup" stage.

  • Marianne's avatar
    Marianne
    8 years ago

    bpduplicate is one of those 'trial and error' commands.

    I would personally try with less parameters, e.g.

    bpduplicate -backupid jpvm126_1485283746  -cn <copy_number> -dstunit Test_Su2_temp   

    PS: 
    I am curious about the type of disk pools and storage units you are using?
    'Opt-dup' seems to indicate that this is some kind of dedupe storage? 

    You may want to try bpimmedia with these parameters (again - trial and error): 

    bpimmedia -stype <Storage Server Type> -dp <disk pool name>

     

11 Replies

  • Sounds like one SLP with three stages:

    --> Backup
    --> --> Duplication
    --> --> --> Duplication

     

    • Marianne's avatar
      Marianne
      Level 6
      I agree.
      One SLP with backup and 2 duplications.

      You can choose the source of duplication to Storage_Server_C - either the backup to Storage_Server_A or the duplicate on Storage_Server_B.
      • sdo's avatar
        sdo
        Moderator

        i.e. Marianne is saying that with an SLP you can do this...

        ...a three layer cascade:

        --> Backup to STU-A
        --> --> Duplication to STU-B
        --> --> --> Duplication to STU-C

        ...or this, which uses STU-A as the source to duplicate from for both copies/duplications:

        --> Backup to STU-A
        --> --> Duplication to STU-B
        --> --> Duplication to STU-C

        .

        N.B:  The only simple automated way to do this is using one SLP.  You cannot use two SLPs, i.e. this will not work:

        SLP1:
        --> Backup to STU-A
        --> --> Duplication to STU-B
        
        SLP2:
        --> Duplication

        ...because an SLP has to start with a "backup" stage.

  • Hi All,

     

    Thank you for your suggestion.

    From your valuable suggestion, i have been able to perfrom the cascade opt-dup.

    Now i need to do the reverse.

    below is my requirement:

    Currently there are Copy1 on STS-A, Copy2 on STS-B, and Copy3 on STS-C.

    (1) Create another disk pool/STU for STS-A and STS-B.
    (2) Perform Opt-dup from STS-C to STS-B (Copy4 is created on STS-B)
    (3) Perform Opt-dup from STS-B to STS-A (Copy5 is created on STS-A)
    (4) Set primary on Copy5

    (5) Then, Restore data from Copy5

    can you please help me in this too?

    • sdo's avatar
      sdo
      Moderator

      You will have to use the "NetBackup Management / Catalog" functionality, and select "Action:" of "Duplicate", then search correctly, and then perform/request the duplication... all within the Admin Console GUI to perform a manual duplication... or use the CLI command bpduplicate.

      To be able to restore from Copy 5, then you will need to ensure that during the last duplication, or in fact during each duplication, that you choose to make the new copy the primary copy.

      Remember, NetBackup only ever restores from the primary copy.

      • Dear sdo,

         

        Thanks for your suggetsions.

        Unfortunately, i am not able to use the NBU GUI, and have to perform through CLI only.

        Here i performed the few steps:

        1. Created New DP and STU for STS_A and STS_B
        2. Make the COPY_3(On STS_C) as primary with below command
          • /usr/openv/netbackup/bin/admincmd/bpduplicate -npc 3 -backupid jpvm126_1485283746
          • Here is the output of bpimmedia
            Initially
            
            --------------------------------------------------------------------------------
            Backup-ID:            jpvm126_1485283746
             Policy:              pqr1
             Schedule Type:       FULL
             Retention Level      1
             Number of Files:     3
             Compression:         N
             Encryption:          N
             Image Type:          Regular
             Primary Copy:        1
             Expires:             Wed 08 Feb 2017 12:19:06 AM IST
             Image on Hold:       0
            
              Copy Number:        1
              Fragment Number:    1
              Fragment Size (KB): 2097184
              Media Type:         Disk
              Density:            -
              File Number:        -
              Offset:             -
              Host:               jpvm126
              Device Written On:  -
              MPX:                N
              Expires:            Wed 08 Feb 2017 12:19:06 AM IST
              Retention Level:    1
              MediaID:            @aaagq
              Copy on Hold:       0
            
              Copy Number:        2
              Fragment Number:    1
              Fragment Size (KB): 2097184
              Media Type:         Disk
              Density:            -
              File Number:        -
              Offset:             -
              Host:               jpvm126
              Device Written On:  -
              MPX:                N
              Expires:            Wed 08 Feb 2017 12:19:06 AM IST
              Retention Level:    1
              MediaID:            @aaagr
              Copy on Hold:       0
            
              Copy Number:        3
              Fragment Number:    1
              Fragment Size (KB): 2097184
              Media Type:         Disk
              Density:            -
              File Number:        -
              Offset:             -
              Host:               jpvm126
              Device Written On:  -
              MPX:                N
              Expires:            Wed 08 Feb 2017 12:19:06 AM IST
              Retention Level:    1
              MediaID:            @aaags
              Copy on Hold:       0
            
            After changing to primary copy
            
            Backup-ID:            jpvm126_1485283746
             Policy:              pqr1
             Schedule Type:       FULL
             Retention Level      1
             Number of Files:     3
             Compression:         N
             Encryption:          N
             Image Type:          Regular
             Primary Copy:        3
             Expires:             Wed 08 Feb 2017 12:19:06 AM IST
             Image on Hold:       0
            
              Copy Number:        1
              Fragment Number:    1
              Fragment Size (KB): 2097184
              Media Type:         Disk
              Density:            -
              File Number:        -
              Offset:             -
              Host:               jpvm126
              Device Written On:  -
              MPX:                N
              Expires:            Wed 08 Feb 2017 12:19:06 AM IST
              Retention Level:    1
              MediaID:            @aaagq
              Copy on Hold:       0
            
              Copy Number:        2
              Fragment Number:    1
              Fragment Size (KB): 2097184
              Media Type:         Disk
              Density:            -
              File Number:        -
              Offset:             -
              Host:               jpvm126
              Device Written On:  -
              MPX:                N
              Expires:            Wed 08 Feb 2017 12:19:06 AM IST
              Retention Level:    1
              MediaID:            @aaagr
              Copy on Hold:       0
            
              Copy Number:        3
              Fragment Number:    1
              Fragment Size (KB): 2097184
              Media Type:         Disk
              Density:            -
              File Number:        -
              Offset:             -
              Host:               jpvm126
              Device Written On:  -
              MPX:                N
              Expires:            Wed 08 Feb 2017 12:19:06 AM IST
              Retention Level:    1
              MediaID:            @aaags
              Copy on Hold:       0
        3. After that i executed bpduplicate to get the images on second storage server STS_B from STS_C, using below command
          • /usr/openv/netbackup/bin/admincmd/bpduplicate -number_copies 1 -dstunit Test_Su2_temp -dp Test_Dp2_temp -backupid jpvm126_1485283746 -pt Standard -st FULL
            Although this did work but not as expected, it didn't copy the images from STS_C to STS_B, then i mentioned the media id for third storage server as -id @aaags but this time it was failed as
            [root@jpvm126 ~]# /usr/openv/netbackup/bin/admincmd/bpduplicate -number_copies 1 -dstunit Test_Su2_temp -dp Test_Dp2_temp -id @aaags  -backupid jpvm126_1485283746 -pt Standard -st FULL
            Duplicate started 01/25/2017 18:40:05
            Activity monitor job id = 14
            INF - found no images or media matching the selection criteria

         So can you please let me know, where i am going wrong and missing some crucial procedure.

        One more thing bpimmedia is displaying the images, but when i am using mediaid, it is showing no image found

        [root@jpvm126 ~]# /usr/openv/netbackup/bin/admincmd/bpimmedia -mediaid @aaagq
        no entity was found
        [root@jpvm126 ~]# /usr/openv/netbackup/bin/admincmd/bpimmedia -mediaid @aaagr
        no entity was found
        [root@jpvm126 ~]# /usr/openv/netbackup/bin/admincmd/bpimmedia -mediaid @aaags
        no entity was found
        [root@jpvm126 ~]#

        Sorry for my lack of knowledge.