BlueXP is now NetApp Console
Monitor and run hybrid cloud data services
This demonstration will show you snap lock which is a new feature added in onap 9 and its configuration using oncomand system manager 9. Customers challenge includes regulatory compliance and data retention which vary from days to tens of years. Netup snap lock is the worm write once read many offering for data retention with simplicity as the key. The volume for snap lock can be created on any platform. File archival is done via SIFS or NFS protocol. Retention can be set on files or set at the volume. Snap lock prevents tampering with the file until expiration. After this data expires, the files can be deleted. Browse to oncommand system manager by entering the cluster management lift IP address in a supported browser. Log to system manager. This is the onap 9 dashboard. We first need to check that snap lock is licensed. This can be confirmed under configurations licenses. Then we need to initialize compliance clock on a per node basis. When initialized, it aligns with the cluster system time. Once started, it runs independently and will not be affected by the system time. This clock cannot be stopped or modified. Click on initialize compliance clock. This is a one-way initialization. You will now notice that the compliance clock has been initialized. Now let's proceed with creating a snap lock aggregate. Click on create. Provide a name for this snap lock aggregate. Select a disk type for this aggregate. You will be able to select a snap lock type. So you have the option to select snap lock compliance or enterprise. Go ahead and click create to proceed with creating this aggregate. Click on SVMs in the navigation. Select the SVM and click on manage. Click on volumes. Let's go ahead and create a new volume in the snap lock aggregate. Provide a name for this snap lock volume. For aggregate, browse and select the newly created snap lock aggregate. Click on the snap lock tab. You will have parameters for the snap lock volume. Autocommit period is the period after which the file will be in worm state. Then you also have values to set for retention period which is the default retention period minimum and maximum. Click create to proceed with creating this snap lock volume. Once you highlight this volume you will notice that you are able to view snap lock details for this volume. Click on name spaces. You will notice this snap lock volume is automatically mounted under root. Now let's go ahead and create a protection relationship. Click on create. You will receive a popup to select the destination SVM for relationship type. You have the option to select mirror, vault, mirror and vault. Let's go and create vault. In this example, let's go ahead and click on browse to select the source SVM and click on browse to select a volume within this SVM. Click new volume. Let's go ahead and create another new volume in the snap lock aggregate. So select snap lock aggregate from the popup window. Specify a vault policy and a schedule and proceed with clicking on create to create this relationship. Thank you very much for watching this demonstration.
Learn about the SnapLock feature configuration using OnCommand System Manager 9.0 (OCSM) for ONTAP 9.0. NetApp SnapLock is the Write Once Read Many (WORM) offering for regulatory compliance and data retention purposes.