Reporting Engine / iwfreeze impedance mismatch

Question: why is it, that when we freeze teamsite, presumably to perform backups, the reporting engine stays up?
[TS 5.5.2, Win2000 Server OS]

I ask this, because without doing the freeze, the backup program writes a bunch of messages into the alert log about files being in use by other processes, and therefore I presume the files don't get backed up. So we iwfreeze, and then the backup runs cleanly except for the reporting database, which is still in use.

Does anybody out there freeze their backing store for something other than backups?

Has anybody already written the bat files to stop/start the reporting engine so I can have my backup client fire them off as well?

Thanks.
Len.

Len Jaffe
My Heart Is A Flower

Find more posts tagged with

Comments

james1

iwfreeze is intended to "freeze" the backing store. It is not intended to close any and all file handles open by and and all Interwoven processes. Yes, it would be handy if there were such a tool. You may want to contact tech support and see if they have such a tool available for you, or perhaps file a feature request with them.

-- James

--
James H Koh
Interwoven Engineering