To browse the HDFS directories to view snapshot activity:

1. From the Clusters tab, select your CDH 5 HDFS service.
2. Go to the File Browser tab.

As you browse the directory structure of your HDFS, basic information about the directory you have selected is shown at the right (owner, group, and so on).

Minimum Required Role: Cluster Administrator (also provided by Full Administrator)

For snapshots to be created, HDFS directories must be enabled for snapshots. You cannot specify a directory as part of a snapshot policy unless it has been enabled for snapshots.

Enabling an HDFS Directory for Snapshots

1. From the Clusters tab, select your CDH 5 HDFS service.
2. Go to the File Browser tab.
3. Go to the directory you want to enable for snapshots.
4. In the File Browser, click the drop-down menu next to the full file path and select Enable Snapshots:
   
   

  Note: Once you enable snapshots for a directory, you cannot enable snapshots on any of its subdirectories. Snapshots can be taken only on directories that have snapshots enabled.

Minimum Required Role: BDR Administratorr (also provided by Full Administrator)

To manage HDFS snapshots, first enable an HDFS directory for snapshots.

Taking Snapshots

  Note: You can also schedule snapshots to occur regularly by creating a Snapshot Policy.

1. From the Clusters tab, select your CDH 5 HDFS service.
2. Go to the File Browser tab.
3. Go to the directory with the snapshot you want to restore.
4. Click the drop-down menu next to the full path name and select Take Snapshot.

   The Take Snapshot screen displays.

5. Enter a name for the snapshot.
6. Click OK.

   The Take Snapshot button is present, enabling an immediate snapshot of the directory.

7. To take a snapshot, click Take Snapshot, specify the name of the snapshot, and click Take Snapshot. The snapshot is added to the snapshot list.

   Any snapshots that have been taken are listed by the time at which they were taken, along with their names and a menu button.

1. From the Clusters tab, select your CDH 5 HDFS service.
2. Go to the File Browser tab.
3. Go to the directory you want to restore.
4. In the File Browser, click the drop-down menu next to the full file path (to the right of the file browser listings) and select one of the following:
   • Restore Directory From Snapshot
   • Restore Directory From Snapshot As...

   The Restore Snapshot screen displays.

5. If you selected Restore Directory From Snapshot As..., enter the username to apply when restoring the snapshot.
6. Select one of the following:
   • Use HDFS 'copy' command - This option executes more slowly and does not require credentials in a secure cluster. It copies the contents of the snapshot as a subdirectory or as files within the target directory.
   • Use DistCp / MapReduce - This options executes more quickly and requires credentials (Run As) in secure clusters. It merges the target directory with the contents of the source snapshot. When you select this option, the following additional fields, which are similar to those available when configuring a replication, display under More Options:
     • MapReduce Service - The MapReduce or YARN service to use.
     • Scheduler Pool - The name of a resource pool. The value you enter is used by the MapReduce Service you specified when Cloudera Manager executes the MapReduce job for the replication. The job specifies the value using one of these properties:
       • MapReduce - Fair scheduler: mapred.fairscheduler.pool
       • MapReduce - Capacity scheduler: queue.name
       • YARN - mapreduce.job.queuename
     • Run As Username - The user to run the job. By default this is hdfs. If you want to run the job as a different user, enter the user name here. If you are using Kerberos, you must provide a user name here, and it must be one with an ID greater than 1000. (You can also configure the minimum user ID number with the min.user.id property in the YARN or MapReduce service.) Verify that the user running the job has a home directory, /user/username, owned by username:supergroup in HDFS. This user must have permissions to read from the source directory and write to the destination directory.
     • Log path - An alternate path for the logs.
     • Maximum Map Slots and Maximum Bandwidth - Limits for the number of map slots and for bandwidth per mapper. The default for Maximum Bandwidth is 100 MB.
     • Abort on Error - Whether to abort the job on an error. If selected, files copied up to that point remain on the destination, but no additional files are copied. Abort on Error is off by default.
     • Skip Checksum Checks - Whether to skip checksum checks (the default is to perform them). If checked, checksum validation will not be performed.
       You must select the this property to prevent failure when restoring snapshots in the following cases:

       • Restoring a snapshot within a single encryption zone.
       • Restoring a snapshot from one encryption zone to a different encryption zone.
       • Restoring a snapshot from an unencrypted zone to an encrypted zone.

       See HDFS Transparent Encryption.

     • Delete Policy - Whether files that were deleted on the source should also be deleted from the destination directory. This policy also determines the handling of files in the destination location that are unrelated to the source. Options include:
       • Keep Deleted Files - Retains the destination files even when they no longer exist at the source. (This is the default.).
       • Delete to Trash - If the HDFS trash is enabled, files are moved to the trash folder.
       • Delete Permanently - Uses the least amount of space; use with caution.
     • Preserve - Whether to preserve the block size, replication count, permissions (including ACLs), and extended attributes (XAttrs) as they exist on the source file system, or to use the settings as configured on the destination file system. By default source system settings are preserved. When Permission is checked, and both the source and destination clusters support ACLs, replication preserves ACLs. Otherwise, ACLs are not replicated. When Extended attributes is checked, and both the source and destination clusters support extended attributes, replication preserves them.
         Note: To preserve permissions, you must be running as a superuser on the destination cluster. Use the "Run As Username" option to ensure that is the case.