cancel
Showing results for 
Search instead for 
Did you mean: 

Multiplexing does not work with storage unit group

iclcz01
Level 4

Hello, I have a problem with storage unit groups in NetBackup 7.5.0.6 on Solaris 10.

Some policy configured with storage unit, multiplexing=4, max. jobs=unlimited uses one drive.

The same policy configured with failover storage unit group uses 4 drives. On storage units there is set multiplexing=20. It looks like the information about multiplexing is not transfered to the storage unit group.

The same configuration was working on NetBackup 6.5.4.

I did not find anything about this problem, so maybe I am doing something wrong.

Coould you help me please?

Thank you

 

3 REPLIES 3

Quindor2
Level 2
Partner Accredited Certified

I don't really grasp your question, but from what I can see is that you are saying that you have your drives configured with a multiplexing level of 20 (which is VERY high) and your policy schedule set to 4.

To me what would cause the backup to use 4 streams and go to the first drive? Other backups will go to another drive since you specified in the schedule a maximum multiplex of 4.

I don't know what is in the policy, how many clients and how many streams each client can deliver, so it's kind of looking into the dark.

Can you clarify the situation a bit better? And also what your desired result would be?

 

 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

I have not seen any customer environment where MPX got 'broken' as a result of upgrade to 7.x.

We need to see your config for a better understanding of your environment - 

STU output:
bpstulist -g -U

Policy output:
bppllist <policy-name> -U 

iclcz01
Level 4

Here are the outputs form the commands. It is one of policies for backup of archive logs (in this case the multiplexing is 8). Number of streams is controlled by RMAN and could be different on each client (usually 2-8). Backup is directed to DD670 with failover to SL8500 in case of DD670 is unreachable.

If the policy is configured with STU, it works good, every 8 streams goes to one drive but if the policy is configured with STU group, each stream takes separate drive. Similar behaviour I see with other policies too.

acs-1 is SL8500

tld-3 is DataDomain 670

On STU we have configured multiplexing 20 but in fact we use maximum of 8.

bpstulist -g -U

...

Label:                sxxxxx-hcart3-robot-acs-1
Storage Unit Type:    Media Manager
Host Connection:      sxxxxx.domain.cz
Number of Drives:     15
On Demand Only:       yes
Max MPX/drive:        20
Density:              hcart3 - 1/2 Inch Cartridge 3
Robot Type/Number:    ACS / 1
Max Fragment Size:    1048575 MB
 

Label:                sxxxxx-hcart3-robot-tld-3
Storage Unit Type:    Media Manager
Host Connection:      sxxxxx.domain.cz
Number of Drives:     6
On Demand Only:       yes
Max MPX/drive:        20
Density:              hcart3 - 1/2 Inch Cartridge 3
Robot Type/Number:    TLD / 3
Max Fragment Size:    1048575 MB
...

__GROUPS__
sxxxxx-hcart3-group-tld-3 3 sxxxxx-hcart3-robot-tld-3 sxxxxx-hcart3-robot-acs-1

...

 

 bppllist Oracle_ARC_LOG_sxxxxx-1C -U
------------------------------------------------------------

Policy Name:       Oracle_ARC_LOG_sxxxxx-1C

  Policy Type:         Oracle
  Active:              yes
  Effective date:      09/16/2013 10:04:15
  Block Incremental:   no
  Mult. Data Streams:  no
  Client Encrypt:      no
  Checkpoint:          no
  Policy Priority:     5
  Max Jobs/Policy:     Unlimited
  Disaster Recovery:   0
  Collect BMR info:    no
  Residence:           sxxxxx-hcart3-group-tld-3
  Volume Pool:         DD670_BKP
  Server Group:        *ANY*
  Keyword:             (none specified)
  Data Classification:       -
  Residence is Storage Lifecycle Policy:    no
  Application Discovery:      no
  Discovery Lifetime:      0 seconds
ASC Application and attributes: (none defined)

  Granular Restore Info:  no
  Ignore Client Direct:  no
Enable Metadata Indexing:  no
Index server name:  NULL
  Use Accelerator:  no
  HW/OS/Client:  Solaris       Solaris10     saaaaa
                 Solaris       Solaris10     sbbbbb
                 Solaris       Solaris10     sccccc
                 Solaris       Solaris10     sddddd
                 Solaris       Solaris10     seeeee

  Include:  /ora01/oracle/rman/scripts/db_archive_logs.sh

  Schedule:              Oracle-Backup
    Type:                Automatic Full Backup
    Frequency:           every 2 hours
    Maximum MPX:         8
    Synthetic:           0
    Checksum Change Detection: 0
    PFI Recovery:        0
    Retention Level:     2 (3 weeks)
    Number Copies:       1
    Fail on Error:       0
    Residence:           (specific storage unit not required)
    Volume Pool:         (same as policy volume pool)
    Server Group:        (same as specified for policy)
    Residence is Storage Lifecycle Policy:         0
    Schedule indexing:     0
    Daily Windows:
          Sunday     00:00:00  -->  Saturday   23:59:59

  Schedule:              Default-Application-Backup
    Type:                Application Backup
    Maximum MPX:         10
    Synthetic:           0
    Checksum Change Detection: 0
    PFI Recovery:        0
    Retention Level:     2 (3 weeks)
    Number Copies:       1
    Fail on Error:       0
    Residence:           (specific storage unit not required)
    Volume Pool:         (same as policy volume pool)
    Server Group:        (same as specified for policy)
    Residence is Storage Lifecycle Policy:         0
    Schedule indexing:     0
    Daily Windows:
          Sunday     00:00:00  -->  Sunday     24:00:00
          Monday     00:00:00  -->  Monday     24:00:00
          Tuesday    00:00:00  -->  Tuesday    24:00:00
          Wednesday  00:00:00  -->  Wednesday  24:00:00
          Thursday   00:00:00  -->  Thursday   24:00:00
          Friday     00:00:00  -->  Friday     24:00:00
          Saturday   00:00:00  -->  Saturday   24:00:00