Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people, just like you, are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
Solved

Backup Exec Job runs longer than 24 hours causing the other jobs to be missed

Posted on 2009-06-26
6
2,673 Views
Last Modified: 2013-12-01
I am using BE 12.5 and have modified the standard Grandfather Rotation policy to create the jobs.  I have 5 selection lists to add clarity on what is being backed up and where any errors are occurring.  This problem is that when I do the weekly full backup then the first job it takes is to back up our network storage area which typically takes 35 hours, once it has finished that job then it is outside the scheduled time-window for the other 4 jobs to run.  

Is there a way to make the time-window greater than 24 hours, or any other work-around?
0
Comment
Question by:ictdoulos
6 Comments
 
LVL 23

Expert Comment

by:Rahul Misra
ID: 24726642
Setting the time window for a scheduled job                            
http://support.veritas.com/docs/309498

How to configure a job to run within a specified time frame                            
http://support.veritas.com/docs/269240
0
 

Author Comment

by:ictdoulos
ID: 24726745
Thank you for those guides, that tells me that the time-window cannot be greater than 23 hours 59 minutes.  So if I am using a Policy and 5 Selection lists to create the jobs, the policy is where I set the time-window but then the same time window is given to all the jobs created with that policy.

So in order to solve my problem I either need a way to have all 5 jobs run sequentially regardless of time and taking priority over other scheduled jobs, or I need a way to have policy-created jobs running with different time-windows.

Thanks
0
 
LVL 25

Expert Comment

by:Tony Giangreco
ID: 24727537
My first question is why it takes so long to perform a backup/. I would look into replacing the drive used for backups and look for increased speed and hardware compression.

Second, can you run the backups with less services and resources being used? If so, this might sped up the process and get you back into your backup window. I changed one of my backups so it was directed to a hard drive on one of my extra servers. The backup time was reduced by 75%. You might want to something like that to reduce the elapsed time of the backups.
0
Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

 

Author Comment

by:ictdoulos
ID: 24741899
It is backing up 1.3Tb directly to Tape from our disk array (at 765Mb/min).  I am using the AFO option (this might have be a reason?), hardware compression, Full-backup using archive bit, verify after completion, no encryption...

The media server is the same as the file server and the server is also running AD, WSUS, DNS, DHCP, Antivirus update mirror, SQL 2005.

I could potentially create a backup to disk folder on another server or NAS and then duplicate it to tape, but apart from that I can't really play around with the server configurations.

What would you recommend for speeding it up?
0
 
LVL 1

Expert Comment

by:ebeheler
ID: 25778181
How about having the BE server retry the job if it errors out because it's out of the backup window?

Tools / Error handling rules

Add a new rule
Checkmark the error code (E000E020)
Tell it to retry the job 24 times every 60 minutes (maybe?  Not sure on this)

I believe this will effectively give you longer than the 23:59:59 that backup exec normally gives you.
0
 

Accepted Solution

by:
ictdoulos earned 0 total points
ID: 25893909
We have changed our backup strategy so that we are no longer using so many different backup jobs for our full montly backup. Now when our one full monthly backup job runs it backs up all the files we need it to backup so when the job runs 48 hours we don't need to worry about the other monthly full backup jobs giving us issues since we don't have them any more.
0

Featured Post

Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

Question has a verified solution.

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

Suggested Solutions

Title # Comments Views Activity
NTBack up cannot recover data 2 63
FREENAS 9.3 - Can't join AD 11 390
How to calculate the current use of PVU on my TSM server. 4 80
Open Encryption Software Advice needed 4 68
Create your own, high-performance VM backup appliance by installing NAKIVO Backup & Replication directly onto a Synology NAS!
A Bare Metal Image backup allows for the restore of an entire system to a similar or dissimilar hardware. They are highly useful for migrations and disaster recovery. Bare Metal Image backups support Full and Incremental backups. Differential backup…
This tutorial will walk an individual through the steps necessary to enable the VMware\Hyper-V licensed feature of Backup Exec 2012. In addition, how to add a VMware server and configure a backup job. The first step is to acquire the necessary licen…
This tutorial will show how to configure a new Backup Exec 2012 server and move an existing database to that server with the use of the BEUtility. Install Backup Exec 2012 on the new server and apply all of the latest hotfixes and service packs. The…

856 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