Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 2 replies
  • Subscribers 1 subscriber
  • Views 5238 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Warehouse Directory Question

LouGoddard

Greetings,

I have an administrator that stored an important file in \\servername\sophosupdate\warehouse\ The file is not related to Sophos and it has now disappeared.

Does Sophos clean this directory or purge it somehow?

I also noticed in the Event Viewer that an updated version of Sophos Update Manager was installed briefly before the file went missing. "An updated version of Sophos Update Manager has been installed successfully."

Could this have cleaned out the warehouse directory?

I know this sounds really ridiculous. I appreciate any answers.

Thanks, Lou

:23529


This thread was automatically locked due to age.
Parents
  • 0

    "Simply curiosity: Just why would one store are file in this location especially when it is not related to Sophos?"

    I think that majority would agree that putting random things in a program's private data directory is a bad idea.  Doubly so if that directory also happens to be a staging or scratch area for updates and downloads.  The administrator was creating an image of a machine and needed a Windows file share to store the image during the creation process.  He tried two shares that didn't work until he settled on the Warehouse share.  Then a few days later Sophos ate his backup.

    The boss does not like mysteries which brings us to the motivation behind my post!  I was looking for an unbiased party to confirm my educated guess that Sophos ate the file (and rightfully so).

    PS:  I wasn't the guy that put the file there.  :P

    :23581
Reply
  • 0

    "Simply curiosity: Just why would one store are file in this location especially when it is not related to Sophos?"

    I think that majority would agree that putting random things in a program's private data directory is a bad idea.  Doubly so if that directory also happens to be a staging or scratch area for updates and downloads.  The administrator was creating an image of a machine and needed a Windows file share to store the image during the creation process.  He tried two shares that didn't work until he settled on the Warehouse share.  Then a few days later Sophos ate his backup.

    The boss does not like mysteries which brings us to the motivation behind my post!  I was looking for an unbiased party to confirm my educated guess that Sophos ate the file (and rightfully so).

    PS:  I wasn't the guy that put the file there.  :P

    :23581
Children
No Data