Firefox

[busterb]

IEXPLORE.EXE is internet. explorer.exe is windows explorer, as in right click start and explore.

27

[BigV]

mbpark, Undertoad, others:

I have ProcessExplorer and I'm stuck. I am using BackupExec and there are a couple of files that are not being backed up since they're "in use". They're worthless files to me, just tmp files. But I can't delete them, I can't back them up. They're that itch I can't scratch.

I got ProcessExplorer for just this reason, to find what process is "using" the files, and then proceed from there. Probably by stopping (temporarily) the service, then deleting the files, then restarting the service/process.

But I'm stuck, I can't seem to find out how to use PE to determine what's using the files in question. I need a clue, do you have one or more to spare? How do I find out what process/service is using a given file/handle?

Thanks very much in advance.

[Undertoad]

Hit ctrl-F in Process Explorer and type part of the filename in. It should find which process is using it, or any other resource with a similar name.

[BigV]

Thanks. So, the upper part of the screen displays the current Processes, neh?

I did find the file, and it (?) revealed that the System process was the controlling process. I can choose "Close handle" and "Properties". I am certain I do not want to stop the System process (maybe evar) during the day. So that leaves me with the choice to "Close handle". I doubt anything else is using/needing that file (except *me* who wants a clean head shot on it).

I think I want to close the handle. Would you concur? Of course, I know there's no warranty on your advice, I'm just getting a reality check.

btw there's a "scary" dialog box confirmation check when I select close handle. I haven't yet said yes I really want to close the handle and tempt the fates of system instability...

[Undertoad]

If the system is using a file actually named "tmp" or with a .tmp extension or in a tmp directory/folder, then my suggestion would be that you not close it AND that you not back it up. A system should understand that tmp files may cease to exist and don't have any permanent meaning to the OS.

[BigV]

I keeled it.

But I think I'm ok. I killed, no, closed the handle. I did this on three of the five files that are giving me trouble. The other two are parts of the SQL service, and I'm loathe to do that while everything's live and hot and during business hours. Maybe this weekend.

Thanks for the help.

btw, I have expressed my appreciation at the tip jar. Although I suppose I could "expense" this kind of charge, I don't. This is a personal donation, a small acknowledgment of how I value the cellar. I would strongly urge other dwellars to do likewise. I can't pay as much as I would like, but I can pay some. If you like it, if you use it, a little money would help. Money's fungible and except Jaquelita, I think this is the best way to show your love for what we have here. [/PSA]

[BigV]

Originally Posted by Undertoad

If the system is using a file actually named "tmp" or with a .tmp extension or in a tmp directory/folder, then my suggestion would be that you not close it AND that you not back it up. A system should understand that tmp files may cease to exist and don't have any permanent meaning to the OS.

I have been expansive in my definition of the files I back up. I have the space, and I have sought to keep the definitions simple, and to err on the side of inclusiveness. I suppose it would be a fairly simple rule to exclude *.tmp, but I haven't. In fact, the only rule I have created beyond the defaults has been to exclude the pagefile.sys. The reasoning is the same as you described above, but the return to me is much much greater. One rule, one file (per server) and I save mega megabytes... well not literally, but you understand.

[mbpark]

Hello,

You REALLY don't want to touch those files while SQL Server is running. SQL Server/MSDE has its own ways of backing those files up, which you have to use.

You can shut down the SQL Service and then back those files up .

From what I remember, Backup Exec does have the ability (in the full version) to run scripts before and after your backups.

A simple before script that has the line net stop mssqlserver and an after script with the line net start mssqlserver will work wonders.

Thanks,

Mitch

[Torrere]

Apparently there used to be an about: page for all of the Netscape employees, which redirected to each person's home page on the netscape website. This went on until a reporter found the someone's page, and thought that the web page, including it's pictures and politics, were all bundled in with Netscape.

jwz explains

[BigV]

Originally Posted by BigV

I have been expansive in my definition of the files I back up. I have the space, and I have sought to keep the definitions simple, and to err on the side of inclusiveness. I suppose it would be a fairly simple rule to exclude *.tmp, but I haven't. In fact, the only rule I have created beyond the defaults has been to exclude the pagefile.sys. The reasoning is the same as you described above, but the return to me is much much greater. One rule, one file (per server) and I save mega megabytes... well not literally, but you understand.

crap.

so the processexplorer revealed the who and the how of the open file handle closing task, which I boldly undertook. yay me.

then the next day the same thing happened, different files, same namestyles, same directory. crap.

so I added a rule and excluded that directory. :tongue out:

Tanks agin.

[BigV]

Originally Posted by mbpark

Hello,

You REALLY don't want to touch those files while SQL Server is running. SQL Server/MSDE has its own ways of backing those files up, which you have to use.

You can shut down the SQL Service and then back those files up .

From what I remember, Backup Exec does have the ability (in the full version) to run scripts before and after your backups.

A simple before script that has the line net stop mssqlserver and an after script with the line net start mssqlserver will work wonders.

Thanks,

Mitch

yes, oh yes.

I have in mind to show the mdb and ldb files to the local db admin and ask her to 'splain why they're perpetually open. I'm not optomistic, though.

thanks for the warning.

[milkfish]

There is also about:license for licensing info readable by lawyers. (At least in my Firefox version 2.0.0.1 browser this works.)