Ok folks try this one on.  Each night during our Tape

backup the following error occurs in SQL logs



I/O error on backup or restore restart-checkpoint

file 'd:\MSSQL\backup\model4IDR.ckp'. Operating system

error 3(The system cannot find the path specified.). The

statement is proceeding but is non-restartable.



The kicker?  We do not have a database called model4IDR.



In sysdatabases there is no such thing and we do not

understand where the backup is getting this info (veritas)



Any ideas to point me in the right direction?



thanks



JTS

It is probably a Veritas specific issue, I haven't seen it before. Worth

speaking to Veritas support.

--

HTH,

Vyas, MVP (SQL Server)

http://vyaskn.tripod.com/

Is .NET important for a database professional?

http://vyaskn.tripod.com/poll.htm









"Jeffrey Sheldon" <jsheldon@projecthope.org> wrote in message

news:356301c4293f$602b5eb0$a101280a@phx.gbl...

Ok folks try this one on.  Each night during our Tape

backup the following error occurs in SQL logs



I/O error on backup or restore restart-checkpoint

file 'd:\MSSQL\backup\model4IDR.ckp'. Operating system

error 3(The system cannot find the path specified.). The

statement is proceeding but is non-restartable.



The kicker?  We do not have a database called model4IDR.



In sysdatabases there is no such thing and we do not

understand where the backup is getting this info (veritas)



Any ideas to point me in the right direction?



thanks



JTS

In Enterprise Manager, expand to Management > SQL Server Agent > Jobs, and look for your job that is backing up to your tape drive (you may also try under Management > Database Maintenance Plans).



Have a look in the Steps tab of this jobs Properties, and there should be a Step referring to model4IDR.ckp. 



Alternatively, if your maintenance plan gets its instructions from a text file, find that text file and search it for references to your erroneous database.



I have the same error right now, but it's for databases that do exist. It turns out that when we had a crash the other week, the CD ROM was removed from my server, resulting in my secondary HDD moving from F:\ to E:\. Obviously the files for some of my existing databases cannot be found. It just shows that this error message usually means exactly what it says.



If you cannot find the file it is looking for, I suggest creating a text file of the same name and location (it couldn't hurt!!), and let it find that.



Lastly, that DB name looks TOO MUCH like the model db that all SQL Servers have, so exercise CAUTION. Cheers.

This has to do with the Intelligent Disaster Recovery feature of Backup Exec.  The fix, detailed here, is creating a directory named 'backup' under the MSSQL$BKUPEXEC directory.