Forum Discussion

Amaan's avatar
Amaan
Level 6
13 years ago

SLP duplications are not starting after activating

Hi,

 

I have a question regarding SLP behavor. Can anybody tell how long does it take to duplications to get started after activating them. All SLPs were in inactive state as we had problem with the tape drive. Now tape drive fixed and i have activated them, but no duplication jobs are running. Is there anything in the guide which says how long does it take them to start.

Appologies for my bad english. :)

  • I worked with Support and we resolved it. Here is the solution:

    When i configured new robotic and drives i have created same STU with the same name, but i was assuming so. previous STU was orofp01-... and i created Orofp01-... which was the root cause of the issue. We ran this command to fix the issue:

    E:\Veritas\NetBackup\bin\admincmd>nbstl Oro_NOEXPIRE_SLP -L
                                    Name: Oro_NOEXPIRE_SLP
                     Data Classification: (none specified)
                Duplication job priority: 0
                                   State: active
                                 Version: 0
     Destination  1              Use for: backup
                            Storage Unit: Orofp01_Disk_Quantum
                             Volume Pool: (none specified)
                            Server Group: (none specified)
                          Retention Type: Expire After Duplication
                         Retention Level: 0 (30 days)
                   Alternate Read Server: (none specified)
                   Preserve Multiplexing: false
                                   State: active
                                  Source: (client)
                          Destination ID: (none specified)
     Destination  2              Use for: duplication
                            Storage Unit: orofp01-hcart2-robot-tld-3
                             Volume Pool: NetBackup
                            Server Group: Any
                          Retention Type: Fixed
                         Retention Level: 0 (30 days)
                   Alternate Read Server: (none specified)
                   Preserve Multiplexing: true
                                   State: active
                                  Source: (primary)
                          Destination ID: (none specified)

    F:\Veritas\NetBackup\bin\admincmd>nbstl Oro_NOEXPIRE_SLP -modify_version -version 0 -residence Orofp01_Disk_Quantum,Orofp01-hcart2-robot-tld-3

    -modified Oro_NOEXPIRE_SLP

    F:\Veritas\NetBackup\bin\admincmd>nbstl Oro_NOEXPIRE_SLP -L
                                    Name: Oro_NOEXPIRE_SLP
                     Data Classification: (none specified)
                Duplication job priority: 0
                                   State: active
                                 Version: 0
     Destination  1              Use for: backup
                            Storage Unit: Orofp01_Disk_Quantum
                             Volume Pool: (none specified)
                            Server Group: (none specified)
                          Retention Type: Expire After Duplication
                         Retention Level: 0 (30 days)
                   Alternate Read Server: (none specified)
                   Preserve Multiplexing: false
                                   State: active
                                  Source: (client)
                          Destination ID: (none specified)
     Destination  2              Use for: duplication
                            Storage Unit: Orofp01-hcart2-robot-tld-3
                             Volume Pool: NetBackup
                            Server Group: Any
                          Retention Type: Fixed
                         Retention Level: 0 (30 days)
                   Alternate Read Server: (none specified)
                   Preserve Multiplexing: true
                                   State: active
                                  Source: (primary)
                          Destination ID: (none specified)
     

    Duplications started after 5 minute after we ran this command. Issue has been resolved. :)