4.8.2. Procedure – Creating an archive policy using SMB/CIFS

The SMB/CIFS archive method connects to a share on the target server with Server Message Block protocol. SMB/CIFS is mainly used on Microsoft Windows Networks.


Backup and archive policies only work with existing shares and subdirectories.

If a server has a share at, for example, archive and that directory is empty, when the user configures archive/scb1 (or similar) as a backup/archive share, it will fail.

When deployed from the Azure Marketplace, you can use Azure File storage shares in your for Backup and Archive Policies. This is very useful as the quota for the files storage can be changed dynamically, so the cumulative size of the audit trails is not limited to the OS disk size. You can set up this share as a normal SMB shares in your Backup and Archive policies. The parameters for the policy can be obtained from the Azure portal.


When you try to create backups and archives from PSM to NetApp devices using the CIFS protocol, the operation may fail with a similar error message: /opt/scb/mnt/14719217504d41370514043/reports/2010": Permission denied (13) '2010/day/' rsync: failed to set times on.

To overcome this problem, grant the PSM user "Full Control" access rights to the CIFS share on the NetApp device.


When using the CIFS protocol to backup or archive files to a target server running Windows 2008 R2 that uses NTLMv2 authentication, the operation may fail with a similar error message:

CIFS VFS: Unexpected SMB signature
Status code returned 0xc000000d NT_STATUS_INVALID_PARAMETER
CIFS VFS: Send error in SessSetup = -22
CIFS VFS: cifs_mount failed w/return code = -22
CIFS VFS: Server requires packet signing to be enabled in /proc/fs/cifs/SecurityFlags.
CIFS VFS: cifs_mount failed w/return code = -95
CIFS VFS: Server requires packet signing to be enabled in /proc/fs/cifs/SecurityFlags.
CIFS VFS: cifs_mount failed w/return code = -95

To overcome this problem, either:

  • use the NFS protocol to access your Windows 2008 R2 servers, or

  • edit the registry of the Windows 2008 R2 server or apply a hotfix. For details, see Article 957441 in the Microsoft® Support site.

  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).

    You can add the start time for additional archive processes.


    When specifying an additional start time, ensure that the previous archive process finishes before the new archive process starts.

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


    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 SMB/CIFS from the Target settings radio buttons.

    Figure 4.30. Policies > Backup & Archive/Cleanup — Configuring cleanup and archiving

    Policies > Backup & Archive/Cleanup — Configuring cleanup and archiving
  6. Enter the username used to log on to the remote server into the Username field, or select the Anonymous login option.

    Usernames can contain space.

  7. Enter the password corresponding to the username into the Password field.


    PSM accepts passwords that are not longer than 150 characters. The following special characters can be used: !"#$%&'()*+,-./:;<=>[email protected][\]^-`{|}

  8. Enter the name and directory path of the share into the Share field. Use the following format:


    You can use backslashes and forward slashes as well.

    PSM saves all data into this directory, automatically creating the subdirectories. Archives of audit-trails are stored in the data, configuration backups in the config subdirectory.

  9. Enter the domain name of the target server into the Domain field.

  10. Select which SMB protocol to use when PSM connects to the server in the Protocol version field. Servers are usually backwards compatible with earlier protocol versions (for example, a server that supports version 2.1 supports versions 2.0 and 1.0 as well).

  11. 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).


    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.

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


    The archived data is deleted from PSM.

  13. 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.


    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).

  14. Click .

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