SQL 7.0 Backup Failure

[ghalied]

Hi

Anyone know how to overcome this backup failure.

Warning: The file \MSSQL7\Data\master.mdf in use - skipped.
Warning: The file \MSSQL7\Data\mastlog.ldf in use - skipped.
Warning: The file \MSSQL7\Data\model.mdf in use - skipped.
Warning: The file \MSSQL7\Data\modellog.ldf in use - skipped.
Warning: The file \MSSQL7\Data\msdbdata.mdf in use - skipped.
Warning: The file \MSSQL7\Data\msdblog.ldf in use - skipped.
Warning: The file \MSSQL7\Data\northwnd.ldf in use - skipped.
Warning: The file \MSSQL7\Data\northwnd.mdf in use - skipped.
Warning: The file \MSSQL7\Data\pubs.mdf in use - skipped.
Warning: The file \MSSQL7\Data\pubs_log.ldf in use - skipped.
Warning: The file \MSSQL7\Data\TEMPDB.MDF in use - skipped.
Warning: The file \MSSQL7\Data\TEMPLOG.LDF in use - skipped

I've tried editing the registry but no success.
SQL pro's please assist.

 

[skydog]

Hi

Anyone know how to overcome this backup failure.

Warning: The file \MSSQL7\Data\master.mdf in use - skipped.
Warning: The file \MSSQL7\Data\mastlog.ldf in use - skipped.
Warning: The file \MSSQL7\Data\model.mdf in use - skipped.
Warning: The file \MSSQL7\Data\modellog.ldf in use - skipped.
Warning: The file \MSSQL7\Data\msdbdata.mdf in use - skipped.
Warning: The file \MSSQL7\Data\msdblog.ldf in use - skipped.
Warning: The file \MSSQL7\Data\northwnd.ldf in use - skipped.
Warning: The file \MSSQL7\Data\northwnd.mdf in use - skipped.
Warning: The file \MSSQL7\Data\pubs.mdf in use - skipped.
Warning: The file \MSSQL7\Data\pubs_log.ldf in use - skipped.
Warning: The file \MSSQL7\Data\TEMPDB.MDF in use - skipped.
Warning: The file \MSSQL7\Data\TEMPLOG.LDF in use - skipped

I've tried editing the registry but no success.
SQL pro's please assist.

stop the SQL service maybe then backup
I'm not a pro in this field so i would suggest waiting for more answers

 

[bekdik]

Someone has left an application running, while the backup was running.

Close the application and these files will be backed up.

Alternately, if your backup software requires a SQL add-in, purchase it.

 

[ghalied]

MSSQL Server stopped and then disabled.
SQL Server Agent stopped and disabled.

Running on MS 2000 Server box. I've stopped them before I started the backup. This is a new built machine so I'm just migrating the Database from the old server to this one, users still access the database from the old server.

SQL add-in, can your clarify?.

 

[bekdik]

OK. To start with, unless I was using specialized backup software with the appropriate add-in e.g. Netbackup, I wouldn't try and backup the SQL files and logs. I would use enterprise manager to schedule SQL to make a backup into a folder other than that where the mdb files reside, and then I would back up that folder.

Applications such as SQL and Exchange don't take kindly to having their databases backed up by msbackup or somesuch. In the case of exchange I would exmerge to export the mail folders to pst's and then backp up the pst's. Again the alternative being to purchase something like Netbackup with the Exchange add-in.

Hope this helps.

 

[vinesh]

Create a maintenace plan to backup the databases to a specific location and then backup those files.

 

[savage]

Yup. Dump the databases to disk backup in SQL, then backup the dumps.

You can't backup a live database externally to SQL if it is in use... And it's also potentially dangerous to do so with possibilities of database corruptions

 

[ghalied]

Resolved the skipped files by using a different regedit option.

HKEY_CURRENT_USER\Software\Microsoft\Ntbackup\User Interface Name: Skip open files
Type: REG_SZ
Default: 0
Definition:
0 = do not skip, wait
1 = skip files that are opened unreadable
2 = wait on open files for "Wait time"

Name: Wait time
Type: REG_SZ
Data: 30
Definition:
Maximum time (seconds) to wait for open files. Default is 30 seconds.
Maximum value is 65535


We do have three full backup runs that start at 21H00 in the evening, for these we use ArchServe.

The backups I created today was just to allow me to restore the system to a state before importing/restoring the database on the new server. Just incase it goes tits up tomorrow, I can at least get to a plain "vanilla" install point.

Thanks all for the help, at least I got some hands on experience today with SQL. Tomorrow it's restore day.