Slow BACKUP EXEC 12.5

There have been diskussion on this earlier, but thes questions are closed, so I try again.

We use Backup Exec 12.5. We use Backup-to-disk and Dupplicate.

The Bacup-to-disk files is set to maximum of 4Gb/file. We are backup up about 850GB data.

When the backup has run about two weeks, it is slowing down pretty much (normally 8 hours each, but after two weeks about 12 hours). When we erase the files in the Backup-to-disk (only the files, not the folder), it is getting recreated at next backup and is speeding up again.

We can see that the disk is very fragmentet, but a defrag does not help very much - only an erase/recreation.
Is there a better way?

(NB: earlier, we had the Bacup-to-disk files set to maximum of 100Gb/file - but with 4gb/file it is fastelr...
VinumAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Rodney BarnhardtServer AdministratorCommented:
I found where others had posted the same problem. The person in the link below basically says the Symantec engineer told him the fragmentation is normal and he needed to keep his server defraged to prevent the backup fragmentation.
http://www.pronetworks.org/forums/anyone-familiar-using-backup-exec-t105041.html
 Although I am sure you have probably seen this, these are the recommendations for reducing this fragmentation on the support site. It does seem they find this normal.
Suggested Workarounds for Backup Exec include;
1. Avoid hosting multiple backup-to-disk (B2D) folders on the same volume.
2. Minimize the number of concurrent operations when backing up to disk by leaving the Concurrent operations" setting on the B2D folders "Configuration" screen at a value of 1.
3. Maintaining at least 30% free space is recommended on volumes with B2D folders located on them. Avoid letting the volume that is hosting the B2D folder from becoming completely full.
4. Avoid hosting files from other applications that also regularly grow and shrink repeatedly on the same volume as the B2D folders such as database files or their associated log files.
5. Adjust your Backup Exec Overwrite and Append Period media management settings to preserve media as much as possible. This will force the use of available space and limit premature overwriting.
6. Use existing Windows or 3rd party disk defragment tools to regularly defragment volumes containing B2D target locations. Please be sure to defragment the volumes when there is no backup activity taking place.

Symantec is also currently investigating long term solutions to improve how cluster allocations are managed for its B2D files to further reduce the possible fragmentation resulting from backup-to-disk operations with Backup Exec on NTFS volumes. Please check this document frequently for updated information on this topic as it becomes available.

Please also note that the new Backup Exec Continuous Protection Server (BECPS) application does not contribute to increased fragmentation of NTFS volumes and can also be used to backup data to disk. For more information on the new Backup Exec Continuous Protection Server, please see the website http://backupexec.com/ 
 
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Michael_DuebnerCommented:
Here is something else we came up with using BackupExec 12.5 and 2010.

1) Create a Backup To Disk Folder for image backups or backups that are less frequently.
2) Create a Backup to Disk Folder for daily, differential or frequent backups.
3) Increase the size of the B2D files from the standard 4GB to 10GB on B2D folders that will be used for image or less frequent backups.
4) Don't create B2D backup folders on drives that will be shared with application data files.  Pick a volume, or even a set of drives that are solely used for this purpose.

The best advise that I can give you is test, test and test. It may take a little bit of tuning to get the best performance over the long run.
0
VinumAuthor Commented:
Did not give a solution, just an explanation...
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Storage Software

From novice to tech pro — start learning today.