Best practices for blocking access to backed up items with GDPR Guard

Last published : Apr 02, 2026
Review the following best practices before you block access to backed up items:
  • While specifying the blocked item in the CSV file for import, ensure that you use '' related wildcards to specify a set of items within a folder. For example, H:\Folder1\\.txt and E:\\. can be used for blocked items path in the CSV file to block all text files under H:\Folder1 or to block all files in the E: directory.
  • For the blocked items that belong to a non-Windows computer, the file path is case-sensitive. Ensure that you provide a file path with the correct case.
  • Ensure that the server names mentioned for blocked item entry in the CSV file match with the server name appearing in the Servers list on the Media server (Backup and restore Tab > Servers Column). If the fully qualified domain (FQDN) server name is used for a blocked item entry in the CSV file and the server appears with a different name in the Servers list, ensure that the remote agent of that server publishes itself on the media server. If the server name does not match, entries are skipped.
  • Run the export BEMCLI command after the import operation is complete. The exported file is your backup for all the blocked items that are imported.
  • Enter the reason for restoring blocked items when you create a restore job with the Allow restore of blocked items option. The reason is recorded in the audit logs and appears in the audit reports. The reports can be referred for compliance and audit purposes.
  • Run the import command again when a media is moved to a new media server and this media has backup sets that contain blocked items. If you do not run the import command again, the blocked items will be available for restore.
  • In a CASO environment, run CAS and all MBES with Backup Exec 20.3 or later version for items to be blocked across all media servers. When you run the import command on the CAS server, the information is automatically synced on the MBES server.
  • Run the audit log report regularly to keep a record of all the operations related to blocked items.
  • Ensure that the CSV used for specifying blocked items during import operation is with one of the following character encodings:
    • Locale encoding which corresponds to the ANSI and the OEM code pages.
    • UTF-8 with Byte-Order-Mark (BOM).
    • UTF-16 Little-Endian with BOM.
    • UTF-16 Big-Endian with BOM.
The import command does not function properly if the input CSV file contains strings from multiple locales.
  • If you are restoring a virtual machine or doing a local restore of your computer using Simplified Disaster Recovery, ensure that you delete the blocked items manually or using a post-processing script once the restore is complete. Otherwise, blocked items are restored in such cases.
Related information