I have two D2Ds and they are replication partners but the replication won't start until the job has ended so I am pretty sure that there is no overlap or contention for resources there. The problem I am running into is that it is not completing in time. I'm trying to isolate why the VI backup is taking so darned long. Nothing else is backing up to these appliances at the time of the VI backup. The average for the tape-based backup jobs is anywhere from 1600Mb/s to 2600Mb/s (depending on the job type). The average throughput for those jobs is around 175Mb/s. The AD controller VI job is configured to use GRT and the Exchange backup is not. The media server has a NIC dedicated to the backup appliance's network. The backup appliance is configure with 2 1Gb connections setup in a Link Aggregate configuration and the switch that they are connected is also configured with LACP. The backups are going to a CIFS share on an HP D2D4004i backup appliance. These backups occur on different nights and after the tape-based jobs have finished. One is our AD controller and the other is our Exchange server. We also have the VI agent for Backup Exec 2010 R3 and I have configured only two machines to be backed up using this agent. Most of the machines that are being backed up are virtualized on VMware. I have a dedicated media server attached to an LTO5 tape drive and autoloader that performs the vast majority of our file and folder level backups.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |