Symantec Backup Exec Guru's, please help, keep getting backup failures

Kaka said:
When was the last successful backup?
Click to expand...

Any successful backups would have been archived, IIRC end of 2012 when we started looking in to this project, long and short of it is, there entire backup plan had to be stripped down and re-built, because they were trying to send a a huge amount of data on backups, but all their backup volumes on the backup server & any external 1TB drives were completely saturated and out of space, so we had to do a shift and archive, free up space. Look at their servers and see whats being backed up and what we could do without, it turns out that they were backing up the entire C: partition on most servers along with some very heavy data drives, SQL data etc.

So yeah, its basically a strip down and rebuild project but we do have some old archive backups and some more recent ones but in terms of when did it last backup?

I am creating a job one by one full backup to ensure it runs smoothly on the server and to make sure we dont run in to any disk capacity issues as their backup server volume has a disk of 500GB, but we are attaching a 1TB drive to this also, but this is intended for the weekly full backups from the backup volume on the server.

so far I have their Domain controller aka Data server which runs fine

Exchange server also runs fine, then I am running in to these issues with their application servers which are obviously throwing up issues.
 
Last edited:
Sounds a bit messy, good luck. :p

The only thing I can suggest at the moment really is try and flat file the databases and then back those up in the interim. Also make sure the main Backup Exec program is fully up to date (both the console and remote agents).
 
We just use sql backup to a network disk (using the sql backup itself) and then backup the sql backups to tape or in your case backup disk.

I had problems with backup exec and modifying the options on the properties of the job solved. For example it kept having problems on exchange backup and after modifying the exchange backup options it eventually worked.
 
The VSS writer error:

http://www.symantec.com/business/support/index?page=content&id=TECH38007

Check all of those but the logs are clearly telling you there is a space issue somewhere.

How big are all the SQL databases together?

Do you do backups locally from within SQL? If you do, you may want to just backup those flat files and the system state.
There is an option in Netbackup to change the writer to the Symantec VSS writer, not sure if that option is in Backup exec, but you could try changing it if it is.
 
Hi, I am a Backup Support Tech. Here are some more suggestions: Are your SQL backups combined with other types of jobs? If so, create new jobs to back up SQL alone. Even if it is being backed up seperately create a new job with a newly created selection list.
Disable the Advanced Open File option and make sure the Volume Shadow copy service is set to manual and in a not running state. try the backup job and if it fails look at the Windows application event logs and see if there are any errors happening at the time of the backup job.
 
You must log in or register to reply here.
Back
Top Bottom