BackupExec 12.5- full backups 50 hours!
I have posted about this before but am still no closer to a solution.
I have inherited a backup solution which uses BackupExec 12.5 and I am having trouble with extremely slow backup times. Currently full backups are taking 50 hours including verify and differentlial backups are taking about 25 hours. The backup time has only increased despite trying to decrease the amount of data by implementing quotas (still in progress however) and I could do with a little help to try and get the backup times down to a more realistic time.
Firstly I shall explain the solution:
Software: BackupExec 12.5 media server running on Windows Server 2008 64-bit. This server is also the main file server.
Hardware: BackupExec 12.5 Media/File server -
Spec: Intel Xeon E5310 1.60 GHz, 8GB RAM and 1 Gbps NIC.
Storage: HP SAN configured by a hardware RAID and formatted as one 5 ish TB NTFS partition. This is used for the main data storage.
HP Disk Array configured by a Windows software RAID (as it wouldn't work in a hardware RAID) and formatted as one 5 ish TB NTFS partition. This is used for backup storage.
HP Tape LT03 drive.
BackupExec 12.5 software configuration: Media server has been configured with one daily backup selection list. This currently includes the data files stored on the locally connected HP SAN (currently 1.5 TB), system states for two DC's, system state of an exchange server, exchange database (currently about 80 GB), system state of print server, shadow copy components of print server (not sure what this does and if its needed?), and a few shared folders on a couple of other servers.
Two folders have been created on the HP disc array. One called Full and the other Differentials. Both of these have corresponding backup to disc folders under devices. Both were are configured with over right protection of 27 days but recently I have had to decrease these to 3 weeks and 1 week respectively due to low disc space, but I know this can be rectified by increasing the storage.
Backup jobs have been created and use the selection list I described above:
Mon, Tues, Weds, Thurs Differential daily backups to the Differential folder.
Fri 1 Full monthly backup to the Full folder. These is then duplicated to tape.
Fri 2, fri 3 and fri 4 Differential weekly backups to the Differential folder. These are then duplicated to tape.
So the server is configured to do daily differential backups and a monthly full backup. I believe this is suppose to be the fastest method as diffs only backup the changes made since the last full. Full backups are currently around 1.7 TB's and is taking nearly 50 hours to complete, including verify. Diff backups are currently between 100 - 200 GB and are taking about 25 hours to complete, including verify. This also means our daily backups are now overlapping. Duplication to tape is around a few hours and isn't a problem. One thing that I am confused by is the job rate which after checking the job logs varies for each resource. Overall for full backups its around 700MB/min and for diffs is between 70 - 150 MB/min. Backups generally do complete successfully but the backup to disc completion time has done nothing but increase since I started here. I have tried one suggestion from a previous post to increase the .bkf file size as these were set to 1GB but I have increased them up to 50 GB and this only made a minor improvement. I have also tried breaking down the backup selection list to find the slow points and it appears its the data the data files stored on the locally connected HP SAN (currently 1.5 TB) which took around 20 hours on a full backup and also the exchange database (currently about 80 GB) which took around 23 hours on a full backup. All other resources on the selection list (system states, shadow copy components, shared folders, etc completed quickly in a few hours in total). So if the problem is with my users data and exchange database - what can I do to improve these? I have considered excluding multimedia files but not tried this yet. As mentioned earlier we are implementing quotas but this is a slow process as staff change here. As for the exchange database I am not too sure as my knowledge on exchange isn't extensive. I am aware the it does maintained every night on schedule and inbox's are restricted to 2GB per user.
I think in the long run I would like to replace the backup solution with some sort of snapshot backup as the network is in use nearly 24/7. However, if anyone could offer any suggestions for troubleshooting the data and exchange db elements I would greatly appreciate it. Let me know if I have been unclear above too.