Redefining robotic library partitions

You can reassign slots to different partitions or even create or delete partitions from a partition drive pool by repeating the steps for creating partitions and providing different beginning slot parameters. For example, if your current set-up is a 6-slot robotic library with two partitions (partition 1 = slots 1-3 and partition 2 = slots 4-6), but you want to have three partitions with slots 1-2 in partition 1, slots 3-5 in partition 2, and slot 6 in partition 3, you would select slots 1, 3, and 6.

Because the first two partition drive pools maintain the same identity, even though the slots have been reassigned, jobs submitted to those partition drive pools will not have to be retargeted.

However, if you change from three partitions to two partitions, any jobs submitted to the third partition must be retargeted since that third partition no longer exists. Also, if you create a new partition that completely contains two or more of the old partitions, jobs submitted to the old partition must be retargeted.

For example, if a robotic library that had been partitioned with the following:

Table: Robotic library partition example

Partition

Slot

Partition 1

Slots 1 - 2

Partition 2

Slots 3 - 4

Partition 3

Slots 5 - 10

The library is repartitioned as follows:

Table: Robotic library repartition example

Partition

Slot

Partition 1

Slots 1 - 4

Partition 2

Slots 5 - 6

Partition 3

Slots 7 - 10

Then any jobs targeted to the old partition 2 (slots 3-4) must be retargeted.

Note:

If a job is targeted to a particular robotic library drive (or a device pool that is not a partition drive pool), the job defaults to the first partition in the robotic library.

More Information

Creating robotic library partitions

Retargeting a scheduled job from a deleted device pool or media set

500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.