Sequential power cycle backup exec

How do I perform a sequential power cycle?

To perform a sequential power cycle and resolve any communications issues between a Tape library or Tape drive and Backup Exec server, follow these steps: Shut down (Turn Off/Power Off) the Backup Exec server to which the Tape Drive or Tape Library is connected. Then, Turn off (Power Off) the Tape Library or Tape Drive.

How to connect tape library to Backup Exec server?

Connect all the cables between the tape library and Backup Exec server. Power on the tape library and wait till all the lights on the tape library go stable. Wait for it to get completely initialized and until it shows a ready status. Once all the lights are stable, power on the Backup Exec server.

Does Backup Exec support multiple tape drives?

Backup Exec 12.5 and earlier versions include support for single tape drives within the first robotic library and support for multiple standalone tape drives. See the Library Expansion Option (LEO) article for more information on LEO. For Windows 2008: Right-click Computer > Manage, expand Server Manager > Diagnostics, then select Device Manager.

Why is Backup Exec not able to communicate with tape devices?

Backup Exec may not be able to communicate properly with tape devices if another vendor's backup application is installed, even if the services for that application are disabled. Do not install tape diagnostic tools when Backup Exec Services are running. Remove the tape diagnostic tools after the diagnostic tests are complete.

What factors affect the performance of a backup & restore?

Many variables can affect throughput performance of backups and restores. These can include: The speed of the disk controller and hardware errors caused by the disk drive, the tape drive, the disk controller, the SCSI bus, or improper cabling/termination can slow performance. Confirm that the controller is rated for the tape backup hardware.

Can a Backup Exec database cause performance problems?

Backup Exec Database Installing the Backup Exec Database (BEDB) into an existing SQL instance that is used by other applications can also cause performance issues. This is particularly observed in a Central Administration Server Option (CASO) environment.