4.7.2. Procedure – Creating a backup policy using SMB/CIFS

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

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.


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 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 Backup policies section to create a new backup policy.

  2. Enter a name for the backup policy (for example config-backup).

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

  4. Enter the IP address or the hostname of the remote server into the Target server field (for example backup.example.com).

    Use an IPv4 address.

  5. Select SMB/CIFS from the Target settings radio buttons.

    Figure 4.27. Policies > Backup & Archive/Cleanup > Backup policies — Configuring backups through SMB/CIFS

    Policies > Backup & Archive/Cleanup > Backup policies — Configuring backups through SMB/CIFS
  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. Backups 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. To receive e-mail notification of the backup, 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.

    To include the list of files in the e-mail, select Send notification on all events and enable the Include file list option. However, note that if list is very long (for example, PSM stores over 20000 audit trails), the PSM web interface might become unaccessible. In this case, set the Maximum number of files in notification lower. After this number has been reached, file names will be omitted from the notification.


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

  12. Click .

  13. To assign the backup policy to a connection, see Procedure 4.7.5, Creating data backups.