File or Folder locked by the following process
After having moved to 2012, existing jobs are failing with the above error. The pattern seems to relate to files which, by default, are on the C drive but I have moved them to another drive - My C drive is a ssd.
Examples are outlook PST file and the MSS.log file used by SearchIndexer.exe. Workaround is to close down Outlook and use task manager to kill SearchIndexer.exe - not brilliant! [Since moved the MSS.log file to another drive - a work/temp one.]
Using Windows 7 SP1 (32 bit)
- Accedi per poter commentare
Hi
Outlook 2010 is open at the start of the process. When the error occurs, I close Outlook, click re-try a couple of times and the backup then sucessfuly concludes.
Outlook is not connected to MS exchange - POP accounts only
- Accedi per poter commentare
I have a similar problem. My Outlook .PST files are on my data drive (D:) and ATIH2012 will always stop with the above error until I close Outlook and 'retry'. ATIH2011 never had this problem and would happily backup the .PST files with Outlook open. This wouldn't be a problem if the backup was attended at all times but a full backup of my D: drive takes about 10 hours (450GB) and the system waits for a reply.
Because of this I did not select the email folder when I re-created the backup job after a re-install. ATIH2012 still attempts to backup the folder.
- Accedi per poter commentare
@adxltd,
Try it before you've opened Outlook, I wonder if Outlook is performing either some sort of maintenance on the PST file or maintains a lock if it has been used.
@Norman,
Is that 10 hours from within Windows? What compression are you using and are you sure, assuming your back up drive is USB, that you are running at USB2.0/3.0 speed?
- Accedi per poter commentare
Hi Colin.
Yes 10 hours within Windows 7 64 bit to a NAS drive connected through a gigabit Ethernet connection. I'm using Normal compression and Low priority.
Norman
- Accedi per poter commentare
Hi Colin
Image created ok if Outlook is not running when job is started. Not sure what that proves ;-) as it is a locking issue which occurs when the backup encounters the file in question. See attached.
| Allegato | Dimensione |
|---|---|
| 74995-97048.pdf | 38.98 KB |
- Accedi per poter commentare
Hi adxltd,
It narrows down the problem to being Outlook locking the file even if it has been closed during a log on session prior to 2012 running a schedule, hopefully it'll give the programmers an idea of what needs to be fixed.
- Accedi per poter commentare
Thanks Colin
Additional update is that this behavior differs slightly when backing up a disk or files. With backing up a disk, the issue occurs during the job, with backing up files, it occurs immediately.
- Accedi per poter commentare
My understanding is that it shouldn't happen at all with 'Disk/Partition' backups. These use a technology that 'snapshots' a drive so that you can continue to use it whilst the backup is working. It allows the process to backup open files.
Norman
- Accedi per poter commentare
Hi Norman
that's what happened in 2011. It is only since installing 2012 that this behavior occurs. I wander if the s/w does something different when dealing with the c: drive. i.e. the operating system drive where you would expect to have locking issues, as opposed to other drives.
Bob
- Accedi per poter commentare
Bob
I have three backups configured. All of them set to be 'incremental'.
1. C: drive (disk/partition) backing up to a folder in my D: (data) drive.
2. Email (Outlook) data held on my D: drive backing up to a NAS folder.
3. D: drive full file/folder backup (except email and C: drive backup folders) to NAS folder.
The 1st two operate with absolutely no problems. The D: drive always stops with the file in use message for my email .PST file(s) even though I haven't included it in the backup. Also it never does an incremental backup for the D: drive, always performing a 'full' backup. This was never a problem with 2011.
I'm about to try an experiment of using a 'disk/partition' backup of my D: drive and exclude .TIB files.
Norman
- Accedi per poter commentare
Hi Norman
confusion on my part - my backups are file based - just checked backing by disk and that works ok with Outlook running - you are correct.
Bob
- Accedi per poter commentare
I am also an early adopter of version 2012 and I now have exactly the same problem as ADXLTD.
All my backups work perfectly, except the one involving Outlook.
The backup in question backs up the entrie C drive (SSD) and will invariable fail on one of the microsoft files being declared as locked. This backup of the C drive was carried over from version 2011, where is worked flawlessly.
Time for the programmers to get their skates on and resolve this obvious bug?
- Accedi per poter commentare
To be fair, this Outlook backup issue isn't entirely a TIH problem by any means.
Even Outlook's own backup utility (the freebie MS Office add-on available from Mickeysoft) will often fail due to exclusive *.PST file locking that sometimes persists after the main Outlook application has been closed. The problem is even worse if the so-called "Outlook Connector Pack" from Windows Live Essentials is in use as it seems to prolong the processes involved in shutting down Outlook's background tasks. Thus the exclusive *.PST file locking remains in effect for even longer periods. Sometimes a full system restart is the only way to get rid of it.
- Accedi per poter commentare
The point here though is that this behavior did not happen on 2011. It came with 2012
- Accedi per poter commentare
I can only speak for my own experience, of course, but I've seen it happen with both TIH versions depending on event sequences and circumstances. That is not to question or cast any doubt on your findings. But the file handling factors involving both applications would seem to make "coincidence" as likely an explanation as "versioning" for differing individual experiences.
In any case, I'm just suggesting that, if Mickeysoft's own "solution" for Outlook backups has similar limitations, and it certainly does, perhaps we shouldn't be too hasty in attributing this particular problem to Acronis product development.
P.S.: I'm no fan of TIH2012. It's a really crappy premature Acronis release (and not the first one) so far as I'm concerned.
- Accedi per poter commentare