Home All Groups Group Topic Archive Search About

File in use. Can't back it up

Author
29 Aug 2005 10:12 AM
Hank Arnold
We are running into an intermittent problem with our Roaming Profiles. We
use a backup program from Veritas called Backup Exec 9.1. On occasion, a
file is marked as "in use" on the server where the profile resides and it is
skipped by the backup program. The file remains "in use" until we re-boot
the server. It's always a *.tmp file and in various parts of the
profile.This creates a problem in that the user can't use the roaming
profile until the file is freed. They get the message that the profile is
not available and they end up using a temp profile. This causes problems
with Outlook. So far, the only way I've found is to re-boot the server.
Since this server has all the network drives as well as the roaming
profiles, it's no small deal to re-boot it. If I try to delete the profile
from the server, I get a message that I can't delete that file.

Right now, I have to go into AD and disable Roaming Profiles until I have a
chance to re-boot. I'd appreciate any ideas on how to trouble shoot this and
find out what is causing this. Or a way to get the damned file freed up so
that I can avoid messing around with AD and re-booting the server....

--
Regards,
Hank Arnold

Author
29 Aug 2005 10:55 AM
Andrew Mitchell
Show quote Hide quote
"Hank Arnold" <rasi***@aol.com> said

> We are running into an intermittent problem with our Roaming Profiles.
> We use a backup program from Veritas called Backup Exec 9.1. On
> occasion, a file is marked as "in use" on the server where the profile
> resides and it is skipped by the backup program. The file remains "in
> use" until we re-boot the server. It's always a *.tmp file and in
> various parts of the profile.This creates a problem in that the user
> can't use the roaming profile until the file is freed. They get the
> message that the profile is not available and they end up using a temp
> profile. This causes problems with Outlook. So far, the only way I've
> found is to re-boot the server. Since this server has all the network
> drives as well as the roaming profiles, it's no small deal to re-boot
> it. If I try to delete the profile from the server, I get a message that
> I can't delete that file.
>
> Right now, I have to go into AD and disable Roaming Profiles until I
> have a chance to re-boot. I'd appreciate any ideas on how to trouble
> shoot this and find out what is causing this. Or a way to get the damned
> file freed up so that I can avoid messing around with AD and re-booting
> the server....
>

The first thing you need to do is to determine which process is locking the
file. You can use Process Explorer from SysInternals
(http://www.sysinternals.com/Utilities/ProcessExplorer.html) to find what is
locking the file. Just use the Find menu, enter the filename you are looking
for and it will show you which process is locking the file. (you can use the
same utility to free the file handle as a workaround)

Once you have the name of the process you will need to start investigating
why the process is locking the file. How you do this will depend on which
process is the culprit.

--

Andy.
Are all your drivers up to date? click for free checkup

Author
30 Aug 2005 6:22 AM
Hank Arnold
Thanks for the reminder..... I actually have the programs, just forgot about
them.....

--
Regards,
Hank Arnold

Show quoteHide quote
"Andrew Mitchell" <amitch***@removecasey.vic.gov.au> wrote in message
news:Xns96C1D50437C68AA12F32EDB83F@207.46.248.16...
> "Hank Arnold" <rasi***@aol.com> said
>
>> We are running into an intermittent problem with our Roaming Profiles.
>> We use a backup program from Veritas called Backup Exec 9.1. On
>> occasion, a file is marked as "in use" on the server where the profile
>> resides and it is skipped by the backup program. The file remains "in
>> use" until we re-boot the server. It's always a *.tmp file and in
>> various parts of the profile.This creates a problem in that the user
>> can't use the roaming profile until the file is freed. They get the
>> message that the profile is not available and they end up using a temp
>> profile. This causes problems with Outlook. So far, the only way I've
>> found is to re-boot the server. Since this server has all the network
>> drives as well as the roaming profiles, it's no small deal to re-boot
>> it. If I try to delete the profile from the server, I get a message that
>> I can't delete that file.
>>
>> Right now, I have to go into AD and disable Roaming Profiles until I
>> have a chance to re-boot. I'd appreciate any ideas on how to trouble
>> shoot this and find out what is causing this. Or a way to get the damned
>> file freed up so that I can avoid messing around with AD and re-booting
>> the server....
>>
>
> The first thing you need to do is to determine which process is locking
> the
> file. You can use Process Explorer from SysInternals
> (http://www.sysinternals.com/Utilities/ProcessExplorer.html) to find what
> is
> locking the file. Just use the Find menu, enter the filename you are
> looking
> for and it will show you which process is locking the file. (you can use
> the
> same utility to free the file handle as a workaround)
>
> Once you have the name of the process you will need to start investigating
> why the process is locking the file. How you do this will depend on which
> process is the culprit.
>
> --
>
> Andy.
Author
29 Aug 2005 10:50 PM
Joshua Bolton
This is why BE has a open file module.  I highly advise you purchase it since
these are files you are aware of.  There are many system files that are also
not backed up due to being open.
Author
30 Aug 2005 6:21 AM
Hank Arnold
The problem is not that the files are not backed up. These are TMP files and
are really not critical at all. The problem is that the locked files are
preventing the users from loading their roaming profiles. If I catch it
early enough, I can switch them to local profiles until the files are
unlocked. But most of the time we get a call about their being getting error
messages, not seeing the correct desktop (we use Citrix MetaFrame) and
e-mail not working (profile is  missing).

--
Regards,
Hank Arnold

Show quoteHide quote
"Joshua Bolton" <JoshuaBol***@discussions.microsoft.com> wrote in message
news:67F7B9A6-8E96-4FCB-B66C-1E26A9108DBF@microsoft.com...
> This is why BE has a open file module.  I highly advise you purchase it
> since
> these are files you are aware of.  There are many system files that are
> also
> not backed up due to being open.
Author
30 Aug 2005 1:33 PM
Arek Iskra [MVP]
Show quote Hide quote
"Hank Arnold" <rasi***@aol.com> wrote in message
news:eiygQsSrFHA.716@TK2MSFTNGP10.phx.gbl...
> The problem is not that the files are not backed up. These are TMP files
> and are really not critical at all. The problem is that the locked files
> are preventing the users from loading their roaming profiles. If I catch
> it early enough, I can switch them to local profiles until the files are
> unlocked. But most of the time we get a call about their being getting
> error messages, not seeing the correct desktop (we use Citrix MetaFrame)
> and e-mail not working (profile is  missing).
>
> --
> Regards,
> Hank Arnold


How about making an exclusion for all .tmp files in your job definition?

--
Arek Iskra
MVP for Windows Server - Software Distribution

Bookmark and Share