Comments
Sort by recent activity
Peter,
Apologies for not getting back to you, I have been off sick for a cpl of weeks and just piling through all the logs etc now, in summary our verification is looking healthier than it had been in the past.
I will monitor this again this week and speak to colleagues and see if they are still seeing an issue, if so I will post the details you require.
many thanks,
Eddy / comments
Peter,
Apologies for not getting back to you, I have been off sick for a cpl of weeks and just piling through all the logs etc now, in summary our verification is looking healthier than it had been...
I have run the RESTORE VERIFYONLY myself and luckily all the database backups that were reporting validation errors have reported the backup set is valid.
This is good but I still have a problem that everyday the scheduled backup job reports verification errors and whoever is doing the morning checks for us shouldn't have to go through the process of doing a RESTORE VERIFYONLY every morning to prove the backup is ok.
Is there anything else you know i could look at regarding this?
thanks
Eddy / comments
I have run the RESTORE VERIFYONLY myself and luckily all the database backups that were reporting validation errors have reported the backup set is valid.
This is good but I still have a problem th...
I am receiving a similar problem when backing up several databases using the same version of SQL Backup, the largest one of 105Gb uncompressed is failing on the verify. This is a test system and i was getting it on other backup jobs that were being backed up to a UNC path on a NAS. I have moved this job to backup to a RAID 5, again to a UNC path.
The errors i get reported are:
SQL error 3013: SQL error 3013: VERIFY DATABASE is terminating abnormally.
SQL error 3241: SQL error 3241: The media family on device 'SQLBACKUP_DE229A8D-A138-4280-99C9-5B95C8865005' is incorrectly formed. SQL Server cannot process this media family.
13/11/2007 00:39:39: Validation of all backup files failed.
And in the application log:
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17055
Date: 13/11/2007
Time: 00:39:39
Description:
18210 :
BackupIoRequest::WaitForIoCompletion: read failure on backup device 'SQLBACKUP_DE229A8D-A138-4280-99C9-5B95C8865005'. Operating system error 38(error not found).
Can anyone help either of us why the verify is reporting a failure??? / comments
I am receiving a similar problem when backing up several databases using the same version of SQL Backup, the largest one of 105Gb uncompressed is failing on the verify. This is a test system and i...
Jason,
Thanks for the reply.
Something else i have just noticed whilst restoring through this wizard is the physical name has been changed of the database on the standby server for a particular database being log shipped with more than one datafile associated with it.
i.e. i have a database on my primary server with 2 data files:
<DatabaseName>_Live_Data.MDF
<DatabaseName>_Live_1_Data.NDF
This has been created on the stand by server as:
<DatabaseName>_Live_1.MDF
<DatabaseName>_Live_3.NDF
Is this another known bug that exists within using this option?
Eddy / comments
Jason,
Thanks for the reply.
Something else i have just noticed whilst restoring through this wizard is the physical name has been changed of the database on the standby server for a particular dat...
Thanks for that Petey, the multiple COPYTO command should do the job for the requirment i have.
E / comments
Thanks for that Petey, the multiple COPYTO command should do the job for the requirment i have.
E