Your Browser is Out of Date

Nytro.ai uses technology that works best in other browsers.
For a full experience use one of the browsers below
Dell PowerScale OneFS: Writable Snapshots
Executive summary Overview Writable snapshots prerequisite Configuring and managing writable snapshots Monitoring and reporting Writable snapshots and OneFS domains
Overview
Nested writable snapshots Symbolic and hard links with writable snapshots Licensing requirements Writable snapshots performance Writable snapshots and OneFS data services Writable snapshots and data replication Writable snapshots workflows Best practices and considerations Conclusion Technical support and resources

Overview

Home > Storage > PowerScale (Isilon) > Product Documentation > Data Protection > Dell PowerScale OneFS: Writable Snapshots > Overview

Overview

  • Writable snapshots use the OneFS policy domain manager, or PDM, for domain membership checking and verification. For each writable snapshot, a ‘WSnap’ domain is created on the target directory. The ‘isi_pdm’ CLI utility can be used to report on the writable snapshot domain for a particular directory.

    # isi_pdm -v domains list --patron Wsnap /ifs/test/wsnap1

    Domain          Patron          Path

    b.0700          WSnap           /ifs/test/wsnap1

    Other details of the backing domain can also be displayed with the following CLI syntax:

    # isi_pdm -v domains read b.0700

    ('b.0700',):

    { version=1 state=ACTIVE ro store=(type=RO SNAPSHOT, ros_snapid=650, ros_root=5:23ec:0011)ros_lockid=1) }

    Domain association does have some ramifications for writable snapshots in OneFS 9.3  and later, and there are a couple of notable caveats. For example, files within the writable snapshot domain cannot be renamed outside of the writable snapshot to allow the file system to track files in a simple manner.

    # mv /ifs/test/wsnap1/file1 /ifs/test

    mv: rename file1 to /ifs/test/file1: Operation not permitted