4.8.3. Procedure – Creating an archive policy using NFS

The NFS archive method connects to a shared directory of the target server with the Network File Share protocol.

The version of NFS used is automatically detected. All versions of NFS, up to and including NFS version 4 protocol, are supported.

  1. Navigate to Policies > Backup & Archive/Cleanup and click in the Archive/Cleanup policies section to create a new archive policy.

  2. Enter a name for the archive policy.

  3. Enter the time when the archive process should start into the Start time field in HH:MM format (for example 23:00).

  4. To archive the data collected on PSM more than once a day, click . You can schedule multiple archive times.

    Note

    In case an archive process is not finished before the next one would start, the next archive process waits for the previous process to be completed.

  5. Select NFS from the Target settings radio buttons.

    Figure 4.26. Configuring cleanup and archiving

    Configuring cleanup and archiving
  6. Enter the domain name of the remote server into the Target server field.

  7. Enter the name of the NFS export into the Export field.

    PSM saves all data into this directory, automatically creating the subdirectories.

  8. The remote server must also be configured to accept connections from PSM.

    Add a line that corresponds to the settings of PSM to the /etc/exports file of the remote server. This line should contain the following parameters:

    • The path to the archive directory as set in the Export field of the PSM archive policy.

    • The IP address of the PSM interface that is used to access the remote server. For more information on the network interfaces of PSM, see Section 4.3, Network settings.

      Use an IPv4 address.

    • The following parameters: (rw,no_root_squash,sync).

    Example 4.2. Configuring NFS on the remote server

    For example, if PSM connects the remote server from the 192.168.1.15 IP address and the data is saved into the /var/backups/PSM directory, add the following line to the /etc/exports file:

    /var/backups/PSM 192.168.1.15(rw,no_root_squash,sync)
  9. On the remote server, execute the following command:

    exportfs -a

    Verify that the rpc portmapper and rpc.statd applications are running.

  10. PSM organizes the audit trails into directories based on the date or the protocol. The subdirectories are created directly into the archive directory. Select one of the following directory structures:

    • Protocol/Connection/Archive Date/

    • Archive Date/Connection/Protocol/

    • Connection Date/Protocol/Connection/

    • Archive Date/

    • Connection Date/

    For example, the Protocol/Connection/Archive Date template will have create subdirectories for the audited protocols (that is, ssh, rdp, telnet, vnc), for the name of the connection policy, and finally, for the date (YEAR-MONTH-DAY in YYYY-MM-DD format).

    Note

    Connection Date refers to the time the connection started, while Archive Date to the time it was archived. The difference between the two dates depends on the retention time set for the archiving policy.

  11. Fill the Retention time in days field. Data older than this value is archived to the external server.

    Note

    The archived data is deleted from PSM.

  12. To receive e-mail notifications, select the Send notification on errors only or the Send notification on all events option. Notifications are sent to the administrator e-mail address set on the Management tab, and include the list of the files that were backed up.

    Note

    This e-mail notification is different from the one set on the Alerting & Monitoring tab. This notification is sent to the administrator's e-mail address, while the alerts are sent to the alert e-mail address (see Section 4.6, Configuring system monitoring on PSM).

  13. Click .

  14. To assign the archive policy to the connection you want to archive, see Procedure 4.8.4, Archiving or cleaning up the collected data.