Reason for duplicating selections in two separate jobs?
Updated: 21 May 2010 | 4 comments
I have two backup jobs that run Monday through Thursday. Both of these jobs are incremental jobs. One job would be classified as backing up the C drive and any other drives an application might use. The second job backups SQL databases. Upon reviewing both jobs I have noticed that the C drive and other drives (Logs, backups, etc.) on the database servers are being backed up by both jobs. To me this seems like data duplication and unnecessary. Should this be done or do the drives only need to be backed up once in one job?
Discussion Filed Under:
Comments
Duplications
Are both your jobs being backed up to tape or disk? Personally, I don't see any point in duplicating the backups (unless you're duplicating from disk to tape, but that's another matter) - you're only taking up valuable disk or tape space, and increasing the backup window too.
Hope this helps
Doug.
Both of the jobs are going to
Both of the jobs are going to disk first and then to tape right after.
Does anybody else have any
Does anybody else have any thoughts on this?
RE: Reason for duplicating selections in two separate jobs?
Upon reviewing both jobs I have noticed that the C drive and other drives (Logs, backups, etc.) on the database servers are being backed up by both jobs. To me this seems like data duplication and unnecessary. Should this be done or do the drives only need to be backed up once in one job?
Sounds like you are correct and are backing up your flat file data twice. Try editing the Selection List for the Database backups, select "Text Mode" and delete everyting except the databases (or create a new Selection List containing only the DBs)
If this response answers your concern, please mark it as a "solution"
Would you like to reply?
Login or Register to post your comment.