Blim2
asked on
SQL Server backup failed - 2 media families expected
Our automated backup is failing. When I try to create a backup manually I get the error message below which refers to media families. The SQL server is 2008 standard (version 10.0.2714.0 according to the properites window). It is running in a virtual environment. Automated backup was crteated using the maintenance plan wizard. By manually I mean from the Tasks | Backup option in Management Studio.
This is the message:
Sysentem.Data.SqlClient.Sq lError: The media loaded on "F:\Backup\Links of London\Links of London_backup_2012_03_23_0 60000_8777 321.trn" is formatted to support 1 media families, but 2 media families are expected according to the backup device specification. (Microsoft.SqlServer.Smo)
This is the message:
Sysentem.Data.SqlClient.Sq
ASKER
I may have solved this myself. I think the problem was that I did not delete an existing file name from the Backup To window. When I added another of my own I got the 1/2 media families supported error. When I left the filename that was already there, presumably created by the maintenance plan automated backup, I got the I/O error. When I deleted the file name that was already there and added a single, new, name, the backup started and is now still running.
I'm guessing the filename that was already there was for an existing backup file and the I/O error meant that the system could not overwrite this file. Possibly a more meaningful error message would have helped here!
How do I end this Experts-Exchange question. I don't think I should give the points to myself - doesn't seem fair?
I'm guessing the filename that was already there was for an existing backup file and the I/O error meant that the system could not overwrite this file. Possibly a more meaningful error message would have helped here!
How do I end this Experts-Exchange question. I don't think I should give the points to myself - doesn't seem fair?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
System.Data.SqlClient.SqlE
I think the previous error may have been due to having two backup file names in the Backup To window. Sorry for the confusion.