May 31, 2010 at 1:01 am
Hey
Because a hard disk was running out of space, I've moved the backup-folder to another disk.
In the database maintenance plan of the instance I went to the tab 'Complete backup' and changed the backup directory to a dir on my G-drive.
Now I see the error that you can find below in my windows application log.
I don't understand why that restart-checkpoint file can be situated on the E-drive (where the backupfolder was located before), since I've changed the backupfolder to the G-drive.
When I look to my backupfolder, everything seems to be OK.
Do I've got to change another parameter?
"Event Type: Error
Event Source: MSSQL$CEVI
Event Category: (2)
Event ID: 17055
Date: 26/05/2010
Time: 4:08:11
User: WINGEGRP\superuser
Computer: WINGENE01
Description:
18272 :
I/O error on backup or restore restart-checkpoint file 'e:\sql2k\MSSQL$CEVI\backup\model4IDR.ckp'. Operating system error 3(The system cannot find the path specified.). The statement is proceeding but is non-restartable.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 60 47 00 00 10 00 00 00 `G......
0008: 0f 00 00 00 57 00 49 00 ....W.I.
0010: 4e 00 47 00 45 00 4e 00 N.G.E.N.
0018: 45 00 30 00 31 00 5c 00 E.0.1.\.
0020: 43 00 45 00 56 00 49 00 C.E.V.I.
0028: 00 00 07 00 00 00 6d 00 ......m.
0030: 61 00 73 00 74 00 65 00 a.s.t.e.
0038: 72 00 00 00 r...
"
June 16, 2010 at 8:36 am
I'll take a guess ... If you right-click on your database and select properties (in Enterprise manager) and then select the Transaction Log tab. Does location point to the previous location?
Even as a mother protects with her life
Her child, her only child,
So with a boundless heart
Should one cherish all living beings;
June 17, 2010 at 2:42 am
yep MothInTheMachine, you're right.
I only moved the backupfiles, because that is very easy while the databases are online.
Moving the transactionlogs seems to me more complicated (like moving the datafiles).
I've recreated an empty backupfolder on the old location and the error is gone.
I've made a note that datafiles and transactionlogs have to be moved in the near future.
Thanks for your help.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply