Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Archiving Secure Meetings (NSM Procedure)

    The Secure Access device enables you to archive Secure Meeting instances. You can:

    • Set up a recurring archival process.
    • Perform a one-time archive.
    • Archive the deleted meetings into an XML file for later download or deletion. One file is created for each archive run.
    • Define the number of days a SecureMeeting instance remains on the device before archiving (instances older than x number of days are archived).
    • Define which node in a cluster performs the archive.

    To archive secure meetings:

    1. In the navigation tree, select Device Manager > Devices. Click the Device Tree tab, and then double-click the Secure Access device for which you want to archive secure meetings.
    2. Click the Configuration tab. Select System > Maintenance > Archiving > Secure Meetings.
    3. Add or modify settings as specified in Table 1.
    4. Click one:
      • OK—Saves the changes.
      • Cancel—Cancels the modifications.

    Table 1: Archiving Secure Meetings Details

    OptionFunctionYour Action

    Perform automatic cleanup

    Schedules a recurring archival process and specifies how often the archiving process should run.

    Select the Perform automatic cleanup option to enable this feature.

    Frequency of automatic cleanup

    Specifies how often the archiving process should run.

    Select either Month or Week.

    Delete meetings older than this number of days (days)

    Specifies the status of the old meetings before they are being archived.

    Enter the number of days.

    Archive meeting records before deleting

    Archives secure meetings in a cluster configuration.

    Select the Archive meeting records before deleting option to enable this feature.

    Archive meeting records on node

    Specifies the node that performs the archive.

    Enter the node.

    Published: 2013-01-03