By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,576 Members | 1,399 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,576 IT Pros & Developers. It's quick & easy.

Backup for one new DB failing in regular maintenance job Error 3201

P: n/a
Recently I created a new db in production and restored it from test. I
have a nightly backup job that backs up all user databases. The backup
for this new db is failing.

The message in the error log is
2005-10-04 00:13:47.65 backup
BACKUP failed to complete the command BACKUP DATABASE [MTUDD_GEMINI

I notice that the file name seems to have a space in it between the
database name and the end of the backup _db and a space also appears at
the end of the directory name.

I can perform a backup successfully using the backup task under all
tasks under the database via Enterprise Manager.

Anyone seen this? Any suggestions other than backuping up the db
manually, dropping the database, recreating it, and restoring it from
the backup?

-- Mark D Powell --

Oct 7 '05 #1
Share this Question
Share on Google+
3 Replies

P: n/a
I understand you can manually backup the database from EM. But can you
manually kick off the scheduled job without a problem? Go to EM /
management / SQL Server Agent / Jobs .... and look for the scheduled
package. Right click, Run, and see what happens. If it fails after a
manual run, try recreating the backup scheduled job. If it runs
successfully, the SQL Server Agent login doesn't have the right

Oct 7 '05 #2

P: n/a
If I submit the all user database backup manually via jobs under EM the
jobs run successfully for all databases except this one. The error
message claims the backup devise is unavailable but it is the same disk
all the other backups write to. The OS file directory security seems
to match the other folders when I check the properties tab.

If I cannot find the problem I am going to drop and recreate the entire
maintenance job.

-- Mark D Powell --

Oct 10 '05 #3

P: n/a
Update - I have backed up the db, dropped the database, recreated the
db, backed up the empty db, and then restored the db from the backup
made at the start of this process. Hopefully with tonight's
maintenance job the backup will work.

-- Mark D Powell --

Oct 12 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.