hold'er... actually no. I'm not saying that at all. I believe that's how the disconnect occured in the first place (someone manipulated the archives or streams directly on the backend, without actually performing those tasks through VSOM).
It actually sounds as though someone either:
1 - Manually removed archives/streams from the VSMS instance /outside/ of VSOM.
2 - Perged or otherwise re-imaged the VSMS server wiping all the user data (less likely if the entire suite exists on the same MSP)
Bulletproof Solutions Inc.
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...