Now that this has been brought back up with new information I figure I will inquire about something slightly different…
In my case we have two servers (Yea, I read 30 and I was like “WOW”… although by the end of the year we will be up to four! oh boy!!) and on these two servers we have MS Exchange on one and then we have both act as file servers.
We used to do tape backups via the three jobs: SRVR1, SRVR2 and Exchange. SRVR1 is where exchange is on, but we would only backup the other files on the first job. Since we moved over to a new device so that everything could fit on one tape I decided to consolidate it because I was lazy, (hey! I work hard, leave me alone!!), and also because I thought it would be nice to keep it clean and tidy (Yea, I know… they’re just jobs… I told you, leave me alone!)
My problem? I’m not sure there is one. We have had this thing implemented about a week and a half now and I have yet to get a backup job that says “successful.” If I fix one thing, the next night something else is wrong either from SRVR1, SRVR2 or mostly Exchange. I may have an “Access is Denied” error one night on SRVR1 and so the entire “SRVR1 and SRVR2” job I have created will fail while the next night after I have figured out the problem I will get Exchange to say some stupid consistency check failed and then fail the whole job.
Now this would be a huge deal to me but I noticed that if I go under the restore jobs wizard I can see the jobs from all these nights and the different files and it appears (I haven’t tried), that I can simply select what I want and then boom, it’ll restore it, regardless of the fail. My question is really a two-parter.
1.) Is it a good idea to consolidate all jobs of a single tape backup into one or should they be separated out? Does it matter? If it does, why?
2.) If a job is deemed to have failed (I am running BackupExec 11d but I imagine this question would possibly pertain to any tape backup program), then does that mean the entire thing is corrupt or only the files in which the failure occurred?
—> If #2 is what I think it is and that is that only files are affected if they are directly related to what the failure was, then I would feel much more at ease because most of the errors (or possibly all after I fixed the Access is Denied errors I was receiving), are of files we don’t truly care about anyway. For example I will get Access is Denied on the exchange server because a porn junk mail is corrupt! Don’t think we care about that anyway!!!
Anyway… I just ran back into the office to switch out a tape and got overly pissed because a job I tried running today failed yet again… hope my boss doesn’t see the dent in the wall!! Haha, j/k, but… well, ouch now that I look I’m not kidding.
I’m going home now…