12-21-2009 10:24 AM - edited 12-24-2009 02:28 PM
The backup task does not give a warning if an attempt is made to shut down the PC whilst it is running.
Next time run after mid-task reboot, the last partially created increment file "n" is left on the server. The backup task then gets it's file numbers numbers mixed up and (i believe) tries to recreate the last incremental file "n" on the server and fails with a file I/O error.
Manual deletion of the last increment "n" fails as its in use.
Workaround is to validate increment "n - 1" and that releases increment "n" which can be deleted. The next backup and any valaidation then runs OK.
The backup task should survive a reboot, comments on how to avoid this please
12-25-2009 03:24 AM - edited 12-25-2009 03:28 AM
The file lock part of the problem on the last incremental backup from the PC rebooting during backup is as per This post
Rebooting the 440 frees the incorrect file lock.
12-28-2009 04:33 PM
They say it's a sign of madness talking to oneself!! But I'm not talking to myself am I? That nice man from Seagate is going to answer my question (I think).
After all I bought the Seagate kit as the support from Norton (Ghost) was not up to my expectation to say the least. I mean it can't be as bad here - or can it ??
12-31-2009 12:21 PM - edited 12-31-2009 12:24 PM
In the meantime whilst I continue to wait for suggestions on the reboot problem our readers may be interested to know I had to use the beast in earnest today.
Got an MFT bitmap corrupted error today on the other PC after a BSOD. Chkdsk would not sort it even from a boot CD. Could not run the backup as I got the above error. Copied 'My Docs' onto the blackarmor. blatted the HDD partition (mirror raid), reformatted and restored from the last good image on the Blackarmor, then copied the 'My Docs' back (includes OE filestore).
Have to say it was very easy, relatively quick and simpler than Ghosting back a network image, so well done Seagate!!
How about a reply to the original problem and the file-lock??
01-03-2010 04:47 AM
Another four days pass and not even an acknowledgement from Seagate, and I used to think Norton was bad.
Now 3rd Jan 2010 and original post was 21st December 2009.
01-04-2010 02:14 PM
Bit more testing on this in the total absence of a reply from Seagate
This is just an extension of the file lock problem. PC dies during backup then target backup increment is left with a lock on it. Run the backup again and it dies as the NAS440 still has the file down as being open, reboot the NAS440 and it releases the file and the backup runs to completion next time.
Need a firmware fix as the first backup of a sequence can take a couple of hours.
To quote the song
While I'm sitting here, I'm wondering what went wrong
You'll find your empty arms will tell you
You belong to me, you'll come to me
And see how I've been waiting everyday
Just hoping that you'll come back to stay
But I don't know when I'll ever see you again
Where are you now my love
Where are you now my love