dbaSQL
asked on
The system cannot find the file specified.
Merry Christmas!
The backups on ONE of my servers failed last night. It happens to be on the server that has two enclosures on it. I'm fairly crertain I know what the problem is already, I'm just curious about one thing.
I've got two enclosures on this box; SATA (yuck) and HP. The SATA promise enclosure is faulty right now, taking IT forever and a day to backup, and we had already intended to bounce it this weekend.
the problem has been in affect for a couple weeks, maybe, and my backups have never failed..... until now.
I'm just trying to confirm the source of the failure is in fact the enclosure. The backup target directory is 'G\MSSQL\Backup\*.*', and this is on the sata.
I can see the target drive, where the BAK files are written. But maybe SQL can't - these are the errors I received from the backup failure, in the order of receipt:
BackupIoRequest::ReportIoE rror: write failure on backup device 'G:\MSSQL\BACKUP\dbname\db name_20091 224.BAK'. Operating system error 2(The system cannot find the file specified.).
BACKUP failed to complete the command BACKUP DATABASE dbname. Check the backup application log for detailed messages.
The operating system returned the error '2(The system cannot find the file specified.)' while attempting 'SetEndOfFile' on 'G:\MSSQL\BACKUP\dbname\db name_20091 224.BAK'.
The operating system returned the error '2(The system cannot find the file specified.)' while attempting 'FlushFileBuffers' on 'G:\MSSQL\BACKUP\dbname\db name_20091 224.BAK'.
SQL Server Scheduled Job 'User Database Maintenance' (0xEAA8B9AE5C368446BAD522B E8692D7DE) - Status: Failed - Invoked on: 2009-12-24 22:00:01 - Message: The job failed. The Job was invoked by Schedule 18 (User Database Maintenance Schedule). The last step to run was step 3 (Send Notification - Failure).
I just now tried it manually (separate from the agent job). It failed immediately, with this:
Msg 3201, Level 16, State 1, Line 1
Cannot open backup device 'G:\MSSQL\BACKUP\dbname\db name_20091 225.BAK'. Operating system error 2(The system cannot find the file specified.).
Msg 3013, Level 16, State 1, Line 1
BACKUP DATABASE is terminating abnormally.
so i am thinking maybe the enclosure issue is just escalating... but, here's the query - i saved a test.txt file to the root of G, no problems. I just tried to save the test.txt file to the backup target directories -- these are just the 'dbname' subdirectories within G:\MSSQL\Backup -- it failed w/this:
test.txt
Path does not exist.
Verify the correct path was given.
Anybody seen this before?
The backups on ONE of my servers failed last night. It happens to be on the server that has two enclosures on it. I'm fairly crertain I know what the problem is already, I'm just curious about one thing.
I've got two enclosures on this box; SATA (yuck) and HP. The SATA promise enclosure is faulty right now, taking IT forever and a day to backup, and we had already intended to bounce it this weekend.
the problem has been in affect for a couple weeks, maybe, and my backups have never failed..... until now.
I'm just trying to confirm the source of the failure is in fact the enclosure. The backup target directory is 'G\MSSQL\Backup\*.*', and this is on the sata.
I can see the target drive, where the BAK files are written. But maybe SQL can't - these are the errors I received from the backup failure, in the order of receipt:
BackupIoRequest::ReportIoE
BACKUP failed to complete the command BACKUP DATABASE dbname. Check the backup application log for detailed messages.
The operating system returned the error '2(The system cannot find the file specified.)' while attempting 'SetEndOfFile' on 'G:\MSSQL\BACKUP\dbname\db
The operating system returned the error '2(The system cannot find the file specified.)' while attempting 'FlushFileBuffers' on 'G:\MSSQL\BACKUP\dbname\db
SQL Server Scheduled Job 'User Database Maintenance' (0xEAA8B9AE5C368446BAD522B
I just now tried it manually (separate from the agent job). It failed immediately, with this:
Msg 3201, Level 16, State 1, Line 1
Cannot open backup device 'G:\MSSQL\BACKUP\dbname\db
Msg 3013, Level 16, State 1, Line 1
BACKUP DATABASE is terminating abnormally.
so i am thinking maybe the enclosure issue is just escalating... but, here's the query - i saved a test.txt file to the root of G, no problems. I just tried to save the test.txt file to the backup target directories -- these are just the 'dbname' subdirectories within G:\MSSQL\Backup -- it failed w/this:
test.txt
Path does not exist.
Verify the correct path was given.
Anybody seen this before?
do the sql server clustered?
ASKER
nope
so... check the permissions on the drive forlders...
You would be having some builtin SQL Server user groups named SQLServerMSSQLUser$Compute rName$MSSQ LSERVER or SQLServerMSSQLUser$Compute rName$Inst anceName .. if this does not exists you should add this user and give enough permissions.
You would be having some builtin SQL Server user groups named SQLServerMSSQLUser$Compute
ASKER
it's not a permissions issue. the backups, and all my maint jobs, are run under the sql server service account, which is most definitely an administrative account.
and, as i said, this failure only occurred on one server last night. they're all using the same account.
and, as i said, this failure only occurred on one server last night. they're all using the same account.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
of course it could be. but it isn't. is 6TB
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I will split the points, and thank you both for looking, rk and tigin.
it was a problem with the enclosure. having booted it, all data and functions are fine. i knew the sata was flawed... i guess this is just a reminder
thank you for looking
it was a problem with the enclosure. having booted it, all data and functions are fine. i knew the sata was flawed... i guess this is just a reminder
thank you for looking
ASKER
It wasn't perms, or anything of that nature. It was a problem with the enclosure. No need to reformat it, just a restart was sufficient.