![]() Check that your tape drives are not connected to a SCSI RAID controller.Īmong the other possible problems with SCSI are improper cabling, loose or bad termination and incorrect SCSI BIOS settings. For example, an LTO-3 tape drive requires a SCSI 320 network. Make sure your controller is rated for the speed of your tape drive. If the verify speeds are low, check the SCSI subsystem for possible bottlenecks. Check the performance by examining the logs of jobs with verify operations in them. ![]() The verify operation is generally limited by the speed of the SCSI system. Use the 'verify' option to check the health of the SCSI system Disk can handle intermittent slowdowns in the data rate better than tape can because it writes randomly. Tape needs data fed at a nice even speed that matches the speed of the tape unit for best performance. They can do the same thing when backing up to disk, but because of the random write nature of disk, it doesn't have the problem to the same degree tape does. The verify option should give you a good overall picture of the condition of the SCSI system. Check the documentation and compare the values there with your settings. The SCSI part (controllers, cables, terminators, etc.) of your backup system can sap performance if the parameters are set incorrectly when backing up to tape. This may remedy everything from a problem caused by a power glitch to some incorrectly set parameters. This re-initializes the tape system and resets the tape system's state. If you're backing up to tape, power cycle the tape drive or library and the server. Also, the newer versions of Backup Exec have a feature called Tamper Protection that can cause problems with antivirus software. For more on the interaction between Backup Exec and Norton Antivirus, see Symantec's Backup Exec Forum. ![]() Checking every file being backed up for viruses is unnecessary and slows backup performance. IBM Tivoli Storage Manager backup software tipsĪntivirus software can be a particular problem in Backup Exec. Using custom data backup scripts in a modern backup environmentĭata security concerns with online backup Make sure your backup software isn't getting in the way If you suspect the problem may be in the compression, try switching from hardware to software compression, or vice versa. Some files, like mpegs and jpegs, can't be compressed. Tell the Backup Exec to compress any files which can be compressed. Check to see how fragmented your disks are and defragment if necessary. This will slow down backups in much the same way fragmentation does by requiring a lot of reads to get the information off the disk for backup.ĭisk fragmentation can slow performance of Backup Exec significantly. You should also check that there aren't a lot of small files or directories on the disk. (This assumes you're examining a drive rather than an agent for a program like Microsoft Exchange.) Check for disk fragmentation Compare the logs of the Backup Exec backup and the Windows backup. If remote backups aren't working, try backing up from one drive to another on the remote server. If you are backing up over a network, you can test the system throughput by comparing the Backup Exec logs with the logs of Windows backup (NTBackup) If the Backup Exec logs reflect a lot of conditions that don't show up in the NTBackup logs, further analysis is called for. This can slow down the entire backup process. Some file systems allow a directory to include data from a file on another server in the backup. If one disk or agent seems unusually slow, drill down to determine the cause by examining the job in detail.Ĭheck that the data is not being redirected elsewhere. To do this, set up separate jobs for each disk or agent being backed up and back them up separately. If there's a significant slowdown, you'll need to look more closely for possible causes.īreak the process down and examine the speed of each disk or agent being backed up. (Go to the "job monitor" tab in Backup Exec and select "job history.") Compare this to the current speed and total time it takes to complete the job. Start by looking at your old backup job logs and note both the total time required to back up, the size of the backups, and the overall speed.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |