Data Domain: How BoostFS for Windows Handle File Permission When Switching Security Method

Summary: This article explains how file permissions behave in BoostFS for Windows when switching between the default DDBoost‑based security and local‑user‑security. It also outlines the resulting access implications when remounting a BoostFS storage‑unit after changing the security method. ...

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Instructions

  1. Default Permission Behavior

By default, BoostFS for Windows writes all data using the DDBoost user stored in the BoostFS lockbox.
All files created under this configuration inherit permissions associated with that DDBoost account

  1. Behavior When Enabling Local‑User‑Security

If BoostFS is reconfigured to enable local‑user‑security, and the storage‑unit is remounted:

    • Files previously written using the default DDBoost security model become inaccessible.
    • This occurs because the permission model changes, and the original file ownership no longer aligns with the local‑user‑security context.
  1. Behavior When Disabling Local‑User‑Security

If local‑user‑security is disabled, and the storage‑unit is remounted:

    • All files on the storage‑unit—regardless of how they were written—display their owner as Everyone.
    • This is expected behavior when reverting to the default DDBoost‑based security model.
  1. Additional Documentation

For further details on BoostFS for Windows default permissions and security behavior, refer to the BoostFS for Windows Configuration Guide.

Affected Products

Data Domain, Data Domain Boost – File System
Article Properties
Article Number: 000008971
Article Type: How To
Last Modified: 06 Mar 2026
Version:  6
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.