Video Screencast Help

AOFO option with SQL and File Jobs

Created: 13 Nov 2013 | 2 comments

I just read an article which states that you should seperate you file jobs from the database jobs because of the AOFO, as AOFA should not be configured on SQL jobs. Then it says:

"Have your file job with AOFO enabled and then move the SQL selections in to a seperate job with the SYSTEM State and maybe exchange."

My questions are:

1) Why should you seperate the system state be seperated from the file job?

2) If you do not have any SQL instances on that server and you need to take a full backup of that server, is it bad to have the system state on the same job as the C: and Shadow Copy Components with the AOFO option switched on? If it is bad what shall you do?

Thanks and regards.

Operating Systems:

Comments 2 CommentsJump to latest comment

SuperBrain's picture

Leaving System State with your C:,D:, etc drives and Shadow Copy Components with AOFO ON should not be a problem.

However, it is still recommended to have the databases (SQL, Exchange, Lotus, Oracle, etc) on a separate job if AOFO need to be used for file backups.

ejdrijin's picture

Thanks for your reply.  

I think that also the ADAM/LDS Instance should be done with databases and without AOFO. Am i right?