Example of using multiplexing with schedules

Figure: Multiplexing process scenario provides an example of how schedules are affected when multiplexing is active.

Figure: Multiplexing process scenario

Assume the following about Figure: Multiplexing process scenario.

Schedule A begins first.
Schedules can be in the same or in different policies.
Allow Multiple Data Streams is enabled.
Consequently, a client can have multiple data streams.
See Allow multiple data streams (policy attribute).

Table: Description of the multiplexing process scenario

Event	Description
1 and 2	Jobs A1 and A2 from client DOG start on Drive 1. For Schedule A, the Media Multiplexing limit of 2 is reached for Drive 1.
3 and 4	Jobs A3 and A4 from client CAT start on Drive 2. For Schedule A, the Media Multiplexing limit of 2 is reached for Drive 2.
5 and 6	Jobs B1 and B2 for client FOX start on Drive 1. The Maximum streams per drive storage unit setting is reached for Drive 1.
7 and 8	Jobs B3 and B4 from client OTTER start on Drive 2. All jobs are now running for Schedule B. The Maximum streams per drive storage unit setting is reached for Drive 2.
9 and 10	Jobs A1 and A2 from client DOG finish on Drive 1. However, jobs B1 and B2 for client FOX continue to run. For Schedule A, the Media Multiplexing limit of 2 prevents job A5 from starting on Drive 1
11 and 12	Job A3 from client CAT finishes on Drive 2. Job B1 from client FOX finishes on Drive 1. Job B2 is the only job currently running on Drive 1.
13	Job A5 from client CAT starts on Drive 1. Job A5 is the last job for Schedule A. For Schedule A, the Media Multiplexing limit of 2 prevents job A5 from starting on Drive 2. Therefore, job A5 starts on Drive 1.

NetBackup attempts to add multiplexed jobs to drives that already use multiplexing. If multiplexed jobs are confined to specific drives, other drives are available for non-multiplexed jobs.

If the backup window closes before NetBackup can start all the jobs in a multiplexing set, NetBackup completes only the jobs that have started.

For example, Figure: Multiplexing process scenario assumes that the Activity Monitor shows jobs A1 through A5 as queued and active.

If only jobs A1 and A2 start before the window closes, NetBackup does not perform the other jobs that are in the set. If the window closes before any jobs start, only the first queued and active job starts and completes. In this example: Job A1.

Example of using multiplexing with schedules

Feedback

Feedback