Maintenance Backup hiccup?

  • I have a standard Ent Mgr maintenance plan doing full backups every morning. It does a customer database and distribution. A couple days ago the distribution full backup failed with reason the filename Distribution_db_yyyymmddtimestamp.bak already exists. The next day it ran fine again. Has anyone seen a maintenance plan do that? I have no other errors on the system at the time the failure occurred that I can tell, and I've never seen a plan fail like that before.

  • That's strange. Are you sure someone didn't run a manual backup? Did the server time change and the job run twice?

    I'd dig in more to the logs and scheduler to see if this is a system created file or a manually created one.

  • I'm positive someone didn't run a manual backup, the server doesn't have space for more than the scheduled backups and the customer knows that. They wouldn't have hit this database anyway, if they did a manual backup it would have had a different name, no timestamp in the filename. A server time change makes some sense. They might have been clicking around on the server and did something inadvertent. The server didn't look like it'd been manually touched in several days, though. I'll look at the logs again and see if there's anything else in there. They looked normal to me apart from the job failure.

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply