BartPe Backup File Locks

[skisteep]

I have been using IFW for many years, most recent version 2.74. My recent encounter with was Microsoft SBS 2008 on a HP DL360 with a Raid Array using WinPE/BartPE to perform an offline SYSTEM DISK full backup. I've used this setup for several years on this computer, both online and offline, NO Problems.

My task last night was to image the system partition OFFLINE(WinPE/BartPE) for a Hard Drive upgrade. No sooner than I tried to start the Full Backup, I would get a 'Drive C locked' error. No problem right, just restart SBS 2008, run a chkdsk offline, clear locks, back to imaging, wrong, no matter what I have tried I CANNOT get C-Drive(system) to unlock. Keep in mind IFW is being run OFFLINE with WinPE, thus there shouldn't be any locks at all.

So my question to anyone that might have had this issue, when the notice "Abort, Ignore, Retry" comes up, is it safe to use Ignore because we are OFFLINE, SBS2008 is not running, and all locks should be clear.

I would appreciate any perspectives on this issue.

Wayne

[TeraByte Support]

byte-for-byte validation would tell you if anything got changed. something
you added or loaded to the disk you created/booting is using something on
the internal drive, try creating one without any additional items added
(including any default items they may want to install on the disc).

"skisteep" wrote in message news:3266@public.image...

I have been using IFW for many years, most recent version 2.74. My recent
encounter with was Microsoft SBS 2008 on a HP DL360 with a Raid Array using
WinPE/BartPE to perform an offline SYSTEM DISK full backup. I've used this
setup for several years on this computer, both online and offline, NO
Problems.

My task last night was to image the system partition OFFLINE(WinPE/BartPE)
for a Hard Drive upgrade. No sooner than I tried to start the Full Backup,
I would get a 'Drive C locked' error. No problem right, just restart SBS
2008, run a chkdsk offline, clear locks, back to imaging, wrong, no matter
what I have tried I CANNOT get C-Drive(system) to unlock. Keep in mind IFW
is being run OFFLINE with WinPE, thus there shouldn't be any locks at all.

So my question to anyone that might have had this issue, when the notice
"Abort, Ignore, Retry" comes up, is it safe to use Ignore because we are
OFFLINE, SBS2008 is not running, and all locks should be clear.

I would appreciate any perspectives on this issue.

Wayne

[skisteep]

Thanks for the quick response, I hadn't thought that BartPE could be causing the lock, strange, anyway, I'll build a slim version and test it.

Best,
Wayne

[TeraByte Support(PP)]

Even just a Command Prompt open and sitting at the C:\ directory can block locking the C: partition.

[skisteep]

Thanks for the additonal perspective, but now you have me spooked, I'm concerned that I'll run into this Locked Drive issue during a disaster recovery, which is what I have plan to use IFW.

To eliminate any such surprises what is the recommend offline backup/restore setup?

Note: I'm using HP DL360/380 servers, so I would normally use Windows Raid Drivers, thus DOS is probably out, but maybe Linux!

Thanks,
Wayne

[TeraByte Support(PP)]

There's not really anything different to do. When I run into that problem I usually have a program open that's locked the partition. In those cases, closing the program fixes the problem. In the case of the Command Prompt, closing it or changing to a different drive (changing directory to X:\ instead of C:\, for example) will unlock C:.

Did you try a plain BartPE build in case something in your regular build is causing the lock?