Wednesday, February 15, 2012

Error message

Hi all ,
We are using MicrosoftSQL Server in Window 2000 server OS .
However , we are having some problem and display error messages below :
"The volume on device "C:\fgfg" is not part of a multiple family media set.
Backup with format can be used to form a new media set.
Backup database is terminating abnormally."
Anybody have any ideas or suggestion how to solve it ? Cause it stop our
program from running.
Thanks.Someone did a striped backup against that backup file, and now someone is trying to either do a
single file backup or restore against that file name. You need to use the FORMAT option of the
backup command to split up a media set.
Why this causes "your program from running", you have to ask the developers of that program.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"weetat" <test@.wavex-tech.com> wrote in message news:e$zLpLbqEHA.1300@.TK2MSFTNGP12.phx.gbl...
> Hi all ,
> We are using MicrosoftSQL Server in Window 2000 server OS .
> However , we are having some problem and display error messages below :
> "The volume on device "C:\fgfg" is not part of a multiple family media set.
> Backup with format can be used to form a new media set.
> Backup database is terminating abnormally."
> Anybody have any ideas or suggestion how to solve it ? Cause it stop our program from running.
> Thanks.|||Hi Tibor ,
Thanks for your response.
I am new in MicrosoftSQL server .
What is the proper way to do a schedule database backup in
microsoftSQL server ? i would like to automate the backup thus no
interferences from end users. Any suggestions are much appreciated .
Thanks.
Tibor Karaszi wrote:
> Someone did a striped backup against that backup file, and now someone is trying to either do a
> single file backup or restore against that file name. You need to use the FORMAT option of the
> backup command to split up a media set.
> Why this causes "your program from running", you have to ask the developers of that program.
>|||The quickest, easiest, most convenient way to schedule your backups is by
creating a DB Maintenance Plan using SQL Enterprise Manager (Management |
Maintenance Plans). It's also a fairly tried and tested and commonly used
method so there are many DBAs out there who can help with questions about
it.
The way it works is there is some config data is stored in some system
tables in the msdb database. One or more SQLAgent jobs are automatically
created by the maint plan wizard (a maint plan normally does more than just
full DB backups - like integrity checks, index optimisation, transaction log
backups, full DB backups). The SQLAgent job for backups runs an external
program called SQLMaint.exe. That exe makes a connection to the SQL server,
does the backup to the chosen backup location, optionally verifies the
integrity of the backup file (does a RESTORE VERIFYONLY), optionally deletes
old backup files and optionally writes a log (text) file to a specified
location.
It's pretty much set-and-forget. However, even though it tends to work so
well, you should regularly test your backup files. Once a month or so, copy
a recent full backup (and log backups if you're doing them) to another SQL
server instance and restore them. A backup is completely useless if it
can't be restored.
HTH
--
Cheers,
Mike
"weetat" <test@.wavex-tech.com> wrote in message
news:ef8$67dqEHA.3424@.TK2MSFTNGP12.phx.gbl...
> Hi Tibor ,
> Thanks for your response.
> I am new in MicrosoftSQL server .
> What is the proper way to do a schedule database backup in microsoftSQL
> server ? i would like to automate the backup thus no interferences from
> end users. Any suggestions are much appreciated .
> Thanks.
> Tibor Karaszi wrote:
>> Someone did a striped backup against that backup file, and now someone is
>> trying to either do a single file backup or restore against that file
>> name. You need to use the FORMAT option of the backup command to split up
>> a media set.
>> Why this causes "your program from running", you have to ask the
>> developers of that program.

No comments:

Post a Comment