Backup Running for Over 48 hours...and Still Going
I have a daily backup that is scheduled to run at 3:00 AM. It's been working fine for months.
At 3:00 AM on the 26th (it's now almost Mar 1), the backup started.
The log file shows some updates to the database and other preliminary tasks.
It then clones the database.
It then deletes a whole bunch of "backup files"
It then renames a whole bunch of "temporary backup files"
It then does a whole bunch of updates to the backup database.
That process takes about 18 hours.
And then the cycles repeats: clone, delete, rename, update database.
It is currently well into the 3rd cloning.
This doesn't seem right to me.
Does anyone know what might be happening?
The hard disk where the backup is stored has plenty of space.
Thanks,
John
(log file attached)
- Log in to post comments
I don't know about manual backups, since I mainly use only this scheduled backup. It is a single partition disk backing up to an external drive on my home network. It never takes this long. I think I will cancel it and try a manual backup. I'll let you know what happens.
Thanks for the reply.
- Log in to post comments
I tried running this backup manually and it ran forever, just as the scheduled backup did. I created a new backup and that ran fine. Another ATIH2012 mystery solved by scrapping the backup and starting over. :-(
- Log in to post comments
Sometimes you can watch for the hdisk actitivy light and if it stops for a long time and ati operation doens't progress, safe bet that it's hung.
Sometimes a new task will help. Sometimes a reboot will help.
- Log in to post comments
I could tell that the backup was actively doing something because the files on the backup drive kept getting larger. Rebooting did not help. Creating a new backup seems to be OK, though now I have a different problem that I'll post separately.
- Log in to post comments
One thing, and not necesarily the prob in your case, that can cause backups to become very slow is weak spots on a hard disk or a bad datacable connection. These cause retries of reads/writes, and can substantially slow down the process. If backups suddenly take longer than usual, it's probably a good idea to run chkdsk /r on the hdisk, just to be sure it's not acting up.
In your case it sounds like the ati task script, or a related registry entry became corrupted and there was no error handling routine in ati to deal with it.
- Log in to post comments
I agree that could be a cause o this type o problem, but the me backup I created works fine, as do other applications usin th same drive.
- Log in to post comments