We know how difficult it can be to evaluate Wi-Fi vendors, so we created this helpful Wi-Fi Buyer's Guide to help you find the Wi-Fi vendor that's right for your business! Download the guide and get started on our checklist today!
Solved
Backup Failures - what goes wrong
Posted on 2013-01-02
Can I ask regardless of what backup solution you use:
1) Have you ever had backup jobs fail? If so what caused them to fail, and is it quite common for them to fail? Or a once a year type scenario?
2) What mechanisms do you have in place to identify a backup job that didnt complete successfully, and what can you do about a failed backup job? i.e. if it failed it failed, theres no much you can do about it?
1) Have you ever had backup jobs fail? If so what caused them to fail, and is it quite common for them to fail? Or a once a year type scenario?
2) What mechanisms do you have in place to identify a backup job that didnt complete successfully, and what can you do about a failed backup job? i.e. if it failed it failed, theres no much you can do about it?
[X]
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
-
3
2
2- +1
8 Comments
Active 1 day ago
1) Yes. Various reasons. Not enough space left in the backup pool. Files being locked that should not be locked. I would say a few times a year we may have jobs fail.
2) Any good backup tool should provide you with something to says "backup failed." On our z/OS mainframe the jobs end with a non-zero condition code. On our distributed systems I'm not sure about today, but they used to produce a report that showed that everything was good or if there was a problem. This was reviewed by our operations group to verify.
It depends on the reason the backup failed, but typically if it is a very important file (or group of files) we do what is needed to get the backup run. If it was a not so important file we would just make sure it worked the next backup.
2) Any good backup tool should provide you with something to says "backup failed." On our z/OS mainframe the jobs end with a non-zero condition code. On our distributed systems I'm not sure about today, but they used to produce a report that showed that everything was good or if there was a problem. This was reviewed by our operations group to verify.
It depends on the reason the backup failed, but typically if it is a very important file (or group of files) we do what is needed to get the backup run. If it was a not so important file we would just make sure it worked the next backup.
Active 1 day ago
If you are using Win the low-cost solution is the built-in. The preferred solution is Symantec Backup Exec. Backups are no different from many other things in IT: analyze, test, set, check. If backups fail you usually receive an advice. If backups do not fail you should run a restore periodically and check the restored data.
Active 5 days ago
>.1) Yes. Various reasons. Not enough space left in the backup pool. Files being locked that should not be locked. I would say a few times a year we may have jobs fail.
Re files being locked, can you provide an example? I.e. users with files open? Or something else (please keep answers management / low tech freindly)...
Re files being locked, can you provide an example? I.e. users with files open? Or something else (please keep answers management / low tech freindly)...
Active 1 day ago
Answer to question one has a few answers
Media Failure - if you are writing to tapes then these can fail, it doesn't happen very often due to tape but can happen due to tape drives. This depends on age of hardware and media and its a linear relationship between the age of them and the likelyhood of them failing.
If you are using Disk as a primary backup medium then freespace can cause regular failures if capacity planning has not been undertaken or budget it tight then regular failures due to this can happen frequently
this is something you can control with maintenance and correct budgeting
Backup Configuration Issue
This is dependant on application you are backing up and changes to the backup routines.
If you regularly change backups i.e. adding and removing sources and destinations then this can lead to failure
Some applications are less reliable than others and often have problems with backing up this is down to system admins to document the common errors and frequency of the them
i.e. file share backups file in use errors
Question 2
Alerting is common to almost all (if not all) backup applications and and scripted ones should have alerts built in so you can note when backups fail
mechanisms for dealing with it need to be weighed up with the follow (not exhaustive but just the ones i can think of)
Nature of the error - i.e. hardware error that needs to be fixed, issue with the application being backed up, issue with the backup application
criticality of the error i.e. with the file server example used could potentially be ignored
Importance of data - i.e. audit, regulatory, disaster recovery requirement
Time since last backup/last full backup
time it would take to rerun the backup
impact of re-running the backup at a particular time
time to re-run the backup
Media Failure - if you are writing to tapes then these can fail, it doesn't happen very often due to tape but can happen due to tape drives. This depends on age of hardware and media and its a linear relationship between the age of them and the likelyhood of them failing.
If you are using Disk as a primary backup medium then freespace can cause regular failures if capacity planning has not been undertaken or budget it tight then regular failures due to this can happen frequently
this is something you can control with maintenance and correct budgeting
Backup Configuration Issue
This is dependant on application you are backing up and changes to the backup routines.
If you regularly change backups i.e. adding and removing sources and destinations then this can lead to failure
Some applications are less reliable than others and often have problems with backing up this is down to system admins to document the common errors and frequency of the them
i.e. file share backups file in use errors
Question 2
Alerting is common to almost all (if not all) backup applications and and scripted ones should have alerts built in so you can note when backups fail
mechanisms for dealing with it need to be weighed up with the follow (not exhaustive but just the ones i can think of)
Nature of the error - i.e. hardware error that needs to be fixed, issue with the application being backed up, issue with the backup application
criticality of the error i.e. with the file server example used could potentially be ignored
Importance of data - i.e. audit, regulatory, disaster recovery requirement
Time since last backup/last full backup
time it would take to rerun the backup
impact of re-running the backup at a particular time
time to re-run the backup
Active 5 days ago
>>If you regularly change backups i.e. adding and removing sources and destinations then this can lead to failure
Can you elaborate a little on this? Especially what you mean by sources/destinations?
Can you elaborate a little on this? Especially what you mean by sources/destinations?
Active 1 day ago
"Files being locked that should not be locked."
This is typically on our z/OS system. Under z/OS when you open a file you can open it "exclusive" use only. Meaning no other process can open the file while your process has it open. This is because when you open a file the system has no clue if you are going to open the file for read only or write. This prevents two process from trying to update the same file at the same time.
Unfortunately there is no real equivalent of this on most distributed systems. Which is why you can have two, or more, processes update the same file.
This is typically on our z/OS system. Under z/OS when you open a file you can open it "exclusive" use only. Meaning no other process can open the file while your process has it open. This is because when you open a file the system has no clue if you are going to open the file for read only or write. This prevents two process from trying to update the same file at the same time.
Unfortunately there is no real equivalent of this on most distributed systems. Which is why you can have two, or more, processes update the same file.
Active 1 day ago
you have a backup job that does file server backups from fileserver1
changing the source means adding filesserver2 into that backup job
changing the destination means writing to different disks, different tape drive
this can lead to errors if its not been tested fully.
Some of the less enterprise level backup solutions can give more issues that others.
Using backup exec in previous roles there were no end of issues that caused mutliple failures across multiple job.
changing the source means adding filesserver2 into that backup job
changing the destination means writing to different disks, different tape drive
this can lead to errors if its not been tested fully.
Some of the less enterprise level backup solutions can give more issues that others.
Using backup exec in previous roles there were no end of issues that caused mutliple failures across multiple job.
Featured Post
Before moving to the cloud, it is important to carefully define your db needs, plan for the migration & understand prod. environment. This wp explains how to define what you need from a cloud provider, plan for the migration & what putting a cloud solution into practice entails.
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
This article shows how to use a free utility called 'Parkdale' to easily test the performance and benchmark any Hard Drive(s) installed in your computer. We also look at RAM Disks and their speed comparisons.
- Storage Software
- Windows OS
- Mac OS X
- Storage Hardware
- Hardware
- Android, *Memory
Backups and Disaster RecoveryIn this post, we’ll look at strategies for backups and disaster recovery.
- Server Hardware
- IT Administration
- Disaster Recovery
- Storage Software
- Databases
- Storage Hardware, MySQL Server, Hardware, Percona, *Backups
Viewers will learn how to connect to a wireless network using the network security key. They will also learn how to access the IP address and DNS server for connections that must be done manually.
After setting up a router, find the network security…
Michael from AdRem Software outlines event notifications and Automatic Corrective Actions in network monitoring. Automatic Corrective Actions are scripts, which can automatically run upon discovery of a certain undesirable condition in your network.…
Suggested Courses
Course of the Month11 days, 8 hours left to enroll
718 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.