I'm starting to think I need an eye test. In our office I'm the only one with good eyesight that doesn't already wear glasses. Amazingly though, I think that may have to change.
My rationale is that this morning I've opened the old Backup Exec status window, yet there isn't a Server Paused, Loading Media, Queued or other failure at all, and over the past 24 hours we have just 13 out of 250 odd jobs failed, and the 13 are largely "missed" backups which just mean I need to refine the windows so there is enough time for them all to run (I never get that far normally as it crashes so everything's "missed".
So yeah, either my eyes are playing tricks on me, or Backup Exec has performed a minor miracle.
Just some Sysadmin's view of the world of Backups for Small/Medium Businesses using Backup Exec and Microsoft Data Protection Manager. Experiences, tips, problems, rants and ideas. We eventually gave up with Backup Exec, so while this was "Backup Exec Hell - The Daily Torture of making Backup Exec 10d, 12d and 12.5 work..." it's now "The Joy of Microsoft DPM. Although it isn't perfect, it's a damn sight better.
Showing posts with label general. Show all posts
Showing posts with label general. Show all posts
Thursday, 15 November 2007
Monday, 12 November 2007
A new day and new problems...
Ah it's a good feeling today, why? Because only 6 jobs have failed (sort of) at the first site over the last 24 hours. Of course, it isn't quite that simple, as most of those were re-run 2-3 times to make them run, and we haven't got any real backups from the other 2 sites to talk about, but it's progress symantec-style.
Today's first problem (and it's only 10 past 9...) is that despite rebuilding Site 2, it's now developed a new problem - the first backup job, (to one distinct backup to disk volume with it's own media set) is running, but subequent jobs joining the queue cause the job to move to "loading media" and there it just sits... good stuff. So don't schedule jobs either maybe? It's practically a manual setup anyway I guess, so sitting there like a hawk looking for an opportunity to backup won't hurt.
Today's first problem (and it's only 10 past 9...) is that despite rebuilding Site 2, it's now developed a new problem - the first backup job, (to one distinct backup to disk volume with it's own media set) is running, but subequent jobs joining the queue cause the job to move to "loading media" and there it just sits... good stuff. So don't schedule jobs either maybe? It's practically a manual setup anyway I guess, so sitting there like a hawk looking for an opportunity to backup won't hurt.
Subscribe to:
Posts (Atom)