Solved

Backup exec 12.5 takes long time to run full backup.

Posted on 2014-03-25
2
560 Views
Last Modified: 2014-04-18
Then backing up MS SQL databases with backup exec with the SQL agent, is it necessary to also select the "microsoft SQL server" folder or can I omit that?

The reason I ask is because I have a small business server 2003 that runs a differential backup in about 1 hour.  115GB of data.

When running a full backup it takes 24+ hours.  580GB of data.  

On both the differential and full jobs:
the SQL options the backup method is "Full".
Exchange is also set to "Full"

The backup is run to external eSATA drives.
the job rate on the differential backup is 2,522 MB/min
on the full backup it is 334 MB /min (That's a big drop!)

The two jobs are essentially identical except one backup method is set to differential and one is set to full.

I am thinking about splitting up the full backup to smaller jobs to see if I can tell where the hang up is.
EX,
Job 1 - exchange
job 2 - sql
job 3 - C drive and system state
job 4 - D drive


Any suggestions?
0
Comment
Question by:jpgillivan
2 Comments
 
LVL 21

Accepted Solution

by:
SelfGovern earned 250 total points
ID: 39955925
Splitting the job up is a good way to find a potential bottleneck.
If the differential is trying to determine the row-level differences since
the last full it's no wonder it might take a long time.  It may simply be
easier and faster to run your SQL backups separately from the rest of
the system, and make them all full backups.
0
 
LVL 12

Assisted Solution

by:ktaczala
ktaczala earned 250 total points
ID: 39956100
Symantec always recommends backing up exchange separately.
As far as the others, I always separate them, easier to troubleshoot, easier to restore(Faster)
I also run them one at a time, because I've seen where running several jobs at once cause VSS Snapshot errors.
0

Featured Post

Comprehensive Backup Solutions for Microsoft

Acronis protects the complete Microsoft technology stack: Windows Server, Windows PC, laptop and Surface data; Microsoft business applications; Microsoft Hyper-V; Azure VMs; Microsoft Windows Server 2016; Microsoft Exchange 2016 and SQL Server 2016.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

By default, Carbonite Server Backup manages your encryption key for you using Advanced Encryption Standard (AES) 128-bit encryption. If you choose to manage your private encryption key, your backups will be encrypted using AES 256-bit encryption.
Microsoft will be releasing the Windows 10 Creators Update in just a matter of weeks. Are you prepared? Follow these steps to ensure everything goes smoothly and you don't lose valuable data on your PC.
This tutorial will walk an individual through locating and launching the BEUtility application to properly change the service account username and\or password in situation where it may be necessary or where the password has been inadvertently change…
This tutorial will walk an individual through setting the global and backup job media overwrite and protection periods in Backup Exec 2012. Log onto the Backup Exec Central Administration Server. Examine the services. If all or most of them are stop…

821 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question