Pools if you want data from a job or group of jobs to reside on the same tape family. Jobs, or to make sure a large backup job will complete without operator intervention. Use cascaded drive pools to run unattended backup Or when the next job requires a different media (such as an overwrite job). The next tape drive in the cascaded drive pool is used only when a backup job fills the current media, Tape drives in a cascaded drive pool are not available for concurrent operations. Although multiple tapeР”Вrives are linked to form the cascaded drive pool, only the name of the cascaded drive pool is listed as the destination device By cascading the tape drives,Р”В«ackup jobs can automatically 'roll' to the media in the next tape drive when the media is filled. You can cascade (link) multiple stand-alone tape drives together to create one logical drive. The Guide says this about РІР‚Вcascaded drive poolsРІР‚в„ў. For example, you may want to separate high-performanceР”Вevices from lower performance devices in a separate device pool in order to send high-priority jobs to the fast device pool Particular requirements, and assign and reassign devices to these pools. You can create other device pools to meet your All devices recognized by BackupР”В®xec at startup are automatically assigned to All Devices (Server Name). Oldest recyclable media in the device that has the highest priority.Р”Р„ll Devices (Server Name) is the default device pool, created when Backup Exec is installed. The requirements is found, Backup Exec then searches the devices in a device pool according to device priority and uses the Selects the oldest recyclable media in all of the devices in the device pool to use first.

On hold, and the other jobs are automatically routed to the working devices in the device pool. For example, if a device pool contains four stand-alone drivesР”Р„nd the first device fails because of a hardware error, the job that was running on the failed device is resubmitted and placed Device pools also provide automatic job rescheduling. When a specific device is assigned, the job cannot be automatically routed to the next availableР”Вevice. However, if that device is busy, the job must wait until theР”Вevice becomes available. You can send backup jobs to specific devices in a device pool. Device 1 can have a high priority in Device Pool A and a low priority in Device Pool B.

ForР”В®xample, if Device 1 is placed in both Device Pool A and Device Pool B, you can assign different priorities to it in eachР”Вevice pool. The priority assigned to a device in one device pool is unrelated to that deviceРІР‚в„ўs priority in any other device pool. You can assign priorities to devices in a device pool so that a specific device is used before other devices in the device

Device pools can contain different types of devices, including specific devices in multi. Devices can belong to more than one device pool, unless aР”Вevice is in a cascaded drive pool. By dynamically allocating devices as jobsР”Р„re submitted, Backup Exec processes jobs quickly and efficiently. As other jobs areР”В¬reated and started, they can run concurrently on other devices in the device pool. When you submit aР”В«ackup job to a device pool, the job is automatically sent to the first available device in that device pool. The jobs are spread among the devices in a pool so that the workload is shared among the devices. Their answer was simply 'NO' and they provided the following as documented proof:Р”Р„ device pool is a group of devices that enables load-balancing of Backup Exec jobs sent to the same device pool for At that moment, can job-2 utilize both drive-1 and 2 thereby increasing performance?' ' Regarding BUE 11d, can we have 1 job running on multiple drives? Scenario: job-1 is writing to drive-1 and job-2 is writing to drive-2 and then job-1 finishes. When we inquired with Symantec Level-2 Support, we asked: Actually, I believe all of you missed a very important fact:Р”В«ackupExec (BUE) version 11D and prior is unable to write to more than 1 drive simultaneously for any particular backup job.

Veeam vs backup exec