Backup Exec 2010 R3 slow backups

Hello,

We recently migrated a server and since then we have been having issues with Backup Exec on it.
It is running SBS 2011 and has a tape drive built in.

Before we did the migration the backups started at 9pm and finished at around 1am.  
Now they start at 9 pm and the daily ends at 09:30 am and the Friday at 09:30 am the following Monday. All backups are full backups, so the weekend should only last the same time as the daily.

Looking through the latest Job Log, the last item was backing up the system state, this finished at 01:05:50 however the whole job didn't finish till 09:19:53  

What could be causing the backups to not finish until 8 Hours later?
afflik1923Asked:
Who is Participating?
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.

wshtyCommented:
after the backup is finished, the backup is being checked by backup exec - means that file integrity is being verified that is why the job itself finishes later - BUT this should only take at max the same amount of time as the real backup.

please do a B2D backup of the same files (if possible) and see if the backup is being processed faster.
0
pgm554Commented:
How much data are you backing up?
0
Tony GiangrecoCommented:
1. How much disk space is used that is being backed up?

2. What type of device is being used to backup to?

3. if you are backing up to an external USB, is it 2.0 or 3.0?

4. if 3.0 USB is being used, are you using a 3.0 USB card connected to the USB 3.0 drive?

5. is there a defrag process running sometime during the backup time period?

6. If Windows Update is set to automatic, I'd turn that off so it does not try downloading updates during a backup.

7. Is there an anti virus scan or live update process scheduled during the backup period? If so, schedule it to run an hour before the backup.

8. Are the hard drives being backed up Sata or SAS?

9. What speed are the drives? 5900, 7200, 10K or 15K?

All these things make a difference in performance.

Hope this helps!
0
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

afflik1923Author Commented:
wshty - Hopefully I will get a chance today to try a b2d backup today.

pgm44 - Last night's backup was Byte Count 492,322,412,269.  Job Rate 2,010.00 MB/min

TG-TIS
1 - Byte Count 492,322,412,269
2 - IBM ULTRIUM-HH4, backing up onto LTO3 tapes.
3 - N/A
4 - N/A
5 - Nope
6 - Not set to automatic
7 - Nothing else is running in that window
8 - 2 SAS and 4 Sata
9 - SAS 10k.  Sata 7.2k
0
Gerald ConnollyCommented:
Have you changed generation of tape drive.

ie have you gone from say LTO3 to LTO4 (or whatever)

Its often a problem when this happens as the different tape generations have different minimum backup speeds, so if your backup only generates about 30MB/s and you are going from a LTO3 (Min speed 20-27MB/s depending on model) so the tape run fine, to a LTO4 (min speed 33-40MB/s depending on model) where you are now not meeting the minimum speed and the tape goes into "Shoe-Shining" mode, your backup then performs very badly and can take much longer to complete.

The only way to solve this is to improve the read performance of your backup so that it reaches the minimum speed of the tape drive you are using (of course you could try your old drive)
0
afflik1923Author Commented:
Yes we have gone from using LTO3 tapes in an LTO3 drive to using LTO3 tapes in an LTO4 drive.

According to Backup exec the jobs are running at 2,010.00 MB/min

I had a look into the last 5 backups as you can see below.  The difference seems to be 8 hours give or take.  Could there be a reason for this pattern?

Last resource finished         Whole job Finished         Difference
01:03:43                                        09:05:35                  08:01:52
01:05:50                                        09:19:53                  08:14:03
00:47:09                                        08:50:09                  08:03:00
00:58:31                                        08:50:17                  07:51:46
00:53:53                                        09:05:47                  08:11:54
0
Gerald ConnollyCommented:
2010MB/min = 33.5MB/sec
Is this before or after the change?
If before then its right on the cusp of dropping into shoe-shining

Of course another way to reduce backup times is to reduce what you backup- have you considered incrementals forever and synthetic fulls?

Have you tried a lto4 tape?
0
afflik1923Author Commented:
That is the speed it is currently backing up at, I'm not sure what it was before we changed server.

How come the Weekly/monthly backups take so much longer than the daily's when they are backing up identical data?

No we have not tried an LTO4 tape.
0
Tony GiangrecoCommented:
Try a backup to disk job to see if its tape drive related
0
afflik1923Author Commented:
I will try this first thing in the morning.

Thank you
0
pgm554Commented:
Is the tape drive attached directly to the server that is being backed up ,or is it backing up over the network?
0
afflik1923Author Commented:
It is attached directly to the server.
0
pgm554Commented:
0
afflik1923Author Commented:
I have run a B2D.

It took 12 hours just as before.  But it ran much slower than the tape backup.

467,929,242,071 bytes.  627 MB/min

Last resource finished at 22:36:28.  Whole job finished 5 seconds later 22:26.33

I will look into what pgm554 has suggested and look at the tape diagnostics.
0
afflik1923Author Commented:
Quick question RE the B2D.  Is it okay for me to delete the files? or do I need to delete it within BackupExec?
0
Gerald ConnollyCommented:
In an earlier post in this thread you asked "why the weekly/monthly backups take longer than the dailies when they are backing up the same data"
Are you sure they have the same parameters? Weekly/monthlies tend to be fulls, whereas dailies are often differentials or incrementals and therefore backup a lot less data
0
afflik1923Author Commented:
Because of the size of the data, all backups are fulls.
0
Gerald ConnollyCommented:
Sorry missed that in the OP - Reading this thread on my phone at the time didnt help.


How many tapes are these backups using ? more than 1?

I just find it a bit suspicious that all these jobs appear to finish just after the normal start of the next working day. Mon-Thu - next day, Friday on the following Monday


re the D2D - what were you backing up too? extra disks? what were they and how were they connected?
0
afflik1923Author Commented:
Just 1 tape.

Me too

Was to an Internal disk.  SATA 2TB 7.2K disk
0
Gerald ConnollyCommented:
So through the same controller and channels? If so that's why it was slow!

Shame Windows doesn't have the equivalent of nix's Null device
0
Gerald ConnollyCommented:
What does the end of the log file actually look like?

Re my suspicion - it's not waiting for some kind of user input is it?
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
afflik1923Author Commented:
Backup exec
This is the end of last nights backup.
0
Gerald ConnollyCommented:
Well from what I can see the backup only ran for about 35 minutes 00:11-00:46 the job obviously ran for a lot longer
0
afflik1923Author Commented:
The screen shot is just showing the end of the log, shows the last resource finishing, then at the bottom the whole job finishing.  Around 8 hours difference.
0
Gerald ConnollyCommented:
It also seemed to be waiting from 21:00 to Midnight!

Is there something in the job params or in the script that is running?
0
afflik1923Author Commented:
No it's not waiting, as I said that is the last resource to be backed up.  The other resources before this are between 9pm and midnight.
0
wshtyCommented:
are you running backup exec 2012? if so, you can separate the job into the backup part itself and the verify part afterwards - so effectively having 2 jobs - then you would be able to determine, if the job is hanging at the verify or at the backup.
0
Gerald ConnollyCommented:
What happens about 0900 on a working day?

Is this when you take out/eject tape  to put in fire safe/ send to backup site?
0
afflik1923Author Commented:
We are running 2010
I have switched off the Verify as part of my testing and not switched it back on.

Nothing happens at 9am as far as I am aware, they only swap the tape when it auto ejects after the job is complete.

connollyg - I think your right, I think it may be waiting for user intervention.  I noticed that the automatically clear box was not set.  I have made this change and set it to 1 minute.  Fingers crossed tonight the backups will end at a sensible time.  I'll keep you posted.
0
afflik1923Author Commented:
It was waiting for user intervention.  Now working
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.