question

Gogolo avatar image
Gogolo asked

Restore of full database backup

Today I faced a problem of restoring database backup, consist about 20GB, before a week, I restored backup simple and fast as usually, today it takes hours and hours to restore, what can be problem in here? I faced some errors like: FCD::Cannot open file..
sql-server-2005backup-restore
11 comments
10 |1200

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

ThomasRushton avatar image ThomasRushton ♦♦ commented ·
Has your underlying storage changed?
0 Likes 0 ·
Gogolo avatar image Gogolo commented ·
Nothing changed form previous situation, norupdate where installed
0 Likes 0 ·
Fatherjack avatar image Fatherjack ♦♦ commented ·
do you use a 3rd party backup solution or is this a native backup?
0 Likes 0 ·
Gogolo avatar image Gogolo commented ·
its a native backup
0 Likes 0 ·
Kev Riley avatar image Kev Riley ♦♦ commented ·
is it a physical or virtualised server?
0 Likes 0 ·
Show more comments
Kev Riley avatar image
Kev Riley answered
OK Comment list getting a little long..... Can you confirm that the file does actually exists in the location you think it is? Could there be any other process accessing the file (NAS/disk/tape backups, anti-virus scans, etc)? Is the backup from the same server that it is being restored on or another server?
2 comments
10 |1200

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Gogolo avatar image Gogolo commented ·
There's no other backup restore on server, and for accessing process I'm not sure, There is a McAfee installed on server.
0 Likes 0 ·
KenJ avatar image KenJ commented ·
Check the McCafee settings and verify it is not set to scan the D: and F: drives and that real-time scanning is disabled. Running anti-virus on a database server can be problematic and takes some extra configuration.
0 Likes 0 ·
ThomasRushton avatar image
ThomasRushton answered
Can you write files to the locations given in the error messages? D: and F: would appear to be the target drives...
10 comments
10 |1200

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

ThomasRushton avatar image ThomasRushton ♦♦ commented ·
You might also want to check the state of the drive / array controller. And make sure that all drivers are up-to-date. It definitely feels like something's not happy at the storage / IO level.
2 Likes 2 ·
Gogolo avatar image Gogolo commented ·
Yes, I can write in that locations, but it takes too long.. Ex. for restore which before a week.. toked 10 min, now I need 2-3 h
0 Likes 0 ·
Kev Riley avatar image Kev Riley ♦♦ commented ·
What are D: and F: - are they local drives to the server, drives on a SAN?
0 Likes 0 ·
Gogolo avatar image Gogolo commented ·
Yes sir, they are local drives in same server.
0 Likes 0 ·
Fatherjack avatar image Fatherjack ♦♦ commented ·
Are D: and F: on the same physical drives? If they are an array, have you checked that the array is in good order? If it has lost a drive and is rebuilding the IO will suffer. Check the hardware is in good order
0 Likes 0 ·
Show more comments
Blackhawk-17 avatar image
Blackhawk-17 answered
Based on the errors it looks like you are trying to restore to the root of the drives. Create folders on the drives to restore into and ensure that the SQL Server service has full NTFS access permissions.
3 comments
10 |1200

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Gogolo avatar image Gogolo commented ·
I restored on C drive and goes very well, that means I have problem with RAID!?? (Server is not clustered)
1 Like 1 ·
Blackhawk-17 avatar image Blackhawk-17 commented ·
@Gogolo - that is a possibility. Are you seeing any events in the Windows logs or in the Array logs? Have you tried my suggestion? It is to determine if permissions are a factor. By changing your restore to C: you have identified that there is an issue on the other drives but not what it is yet.
1 Like 1 ·
Gogolo avatar image Gogolo commented ·
Yeah I understand, I tried your suggestion, but looks like everything is OK with permissions.
0 Likes 0 ·
Tim avatar image
Tim answered
From all the other comments it sounds like your RAID array is taking a hit. Is Drive C: a different array, possibly RAID 10, then you have another set of disks for D: and F:. When I first started reading your post I was thinking maybe you had a bad drive and the array was having to rebuild a spare, but with the errors you are getting trying to write to the disk makes me think you have bad sectors. I would recommend running a scan disk on the drive to rule that out. Are you pretty familiar with RAID and can look at the RAID Manager software to check for errors? If not get your systems guy to take a look. Windows Event Viewer might also contain some good information as to what is going on with the disk subsystem.
3 comments
10 |1200

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Tim avatar image Tim commented ·
Since you can restore to C: your backup file is good. The errors you are getting is trying to write to D: and F: which wreaks of corruption on your RAID 5 array. Is your database even accessible or is it having issues which is what is causing you to have to restore from backup? Your RAID management software should have more information about the root of the error and quite possibly the windows event log. Do you have physical access to the server to see if you have amber lights on the disks? I assume this is local raid with hot swap drives.
1 Like 1 ·
Gogolo avatar image Gogolo commented ·
As per information, drives are in RAID 5
0 Likes 0 ·
Gogolo avatar image Gogolo commented ·
Operating system is RAID1, and storage its RAID5, also operating system is mirror.
0 Likes 0 ·

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.