October 18, 2002 at 8:14 am
I have a restore that is very slow. It has taken 1.5 hours for the STATS to be printed. The STATS are at 2 percent. The two datafiles total about 16 GB. Shouldn't be a big deal. Anyway, I noticed that the Restore process had a WAIT TYPE of ASYNC_IO_COMPLETION. Any ideas???
RESTORE DATABASE i3_eic
FROM DISK = 'g:\gf_dba\backups\i3_eic'
WITH RECOVERY,
MOVE 'i3 database ' TO 'E:\Data\i3_eic\i3_eic_Data_01.mdf',
MOVE 'i3_database_2' TO 'F:\Data\i3_eic\i3_eic_Data_02.mdf',
MOVE 'i3 log' TO 'G:\xLogs\i3_eic\i3_eic_Log_01.mdf',
MOVE 'i3_log_2' TO 'H:\xLogs\i3_eic\i3_eic_Log_02.mdf',
REPLACE,
STATS = 2
GO
"Keep Your Stick On the Ice" ..Red Green
October 23, 2002 at 12:00 am
This was removed by the editor as SPAM
October 23, 2002 at 8:07 pm
Not really sure but I see this with 4Gb restores taking 45mins to an Hour. I believe it is an IO related coming from my Tape Drive. However when I do from a file it does take a bit based on how big the file is. I think it has to seperate the files somewhere temporarily (memory of temp folder) then moves them to their final location but never really took anytime to check. Look at disk queue length and read/writes in Performance Monitor. Also, keep in mind with things like a RAID 5 array not only does the data get written it has to be striped and the parity written and stripped to the proper drives so when writing queue lengths can go up waiting for free time on the drives. RAID 10 does better because it is mirrored stripes without need for parity. Theory, you need to look at PerfMon to validate. As for STATS this is done based on division of time and percentage, meaning quick restores will print less stats and output more often than larger restores.
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply