We use cookies on our website to ensure we provide you with the best experience on our website. By using our website, you agree to the use of cookies for analytics and personalized content.This website uses cookies. More Information
It seems like your browser didn't download the required fonts. Please revise your security settings and try again.

Attention

Starting May 1st, 2018, we will no longer offer the ArchiveOne family of products. This includes all editions of ArchiveOne, ArchiveOne for Files, Max Compression, and Access Security Manager. For more information, please visit: https://campus.barracuda.com/product/archiveone/

Understanding Scripting Events

  • Last updated on

This is the list of events including their arguments. The list and the arguments are also included in comments in the Scripts.INI file, created on installation. The default name for each script is the event name with .VBS appended, and they must be in the Scripts subdirectory of the service installation directory. You can change the name or script extension by editing Scripts.INI.

Event NameDescriptionArgument 1Argument 2Argument 3Argument 4
ServiceStartService Start    
ServiceEndService End    
Phase1StartNowStart

Start of Start now policies

list of policies (each name in quotes)

   
Phase1StartNowEnd

End of Start now policies

hit count

XML results filename

  
Phase1StartNowAbort

Aborted Start now policies

reasonhit count

XML results filename

 
Phase1ScheduledStart

Start of scheduled policy

policy name   
Phase1ScheduledEnd

End of scheduled policy

policy namehit count

XML results filename

 
Phase1ScheduledAbort

Aborted scheduled policy

policy namereasonhit count

XML results filename

Phase2Start

Start of phase 2 archiving

repository name

   
Phase2End

End of phase 2 archiving

repository name

count of messages archived

  
Phase2Abort

Aborted phase 2 archiving

repository name

reason  
MonitorDetectHung

Monitor service detected main service unresponsive

    
MonitorDetectAbort

Monitor service detected main service aborted unexpectedly

    
ZipNotFound

Zip file not found in archive

path to directory

name of zip file

  

ZipNotFound

The ZipNotFound event works as follows: during retrieval of a message, if the ZIP file containing the message is not found in the archive, this event is raised and the script called (if it exists). It is given the name of the missing ZIP file and the directory where it should reside. This is so that the script can retrieve the ZIP file, if it was previously stored on some other storage medium. ArchiveOne Service waits for up to five minutes or until the script ends, then checks for the presence of the ZIP file, and use it for retrieval if it is present.

 

 

Last updated on