tag:blogger.com,1999:blog-42703464971836434942024-03-15T18:11:07.168-07:00Cosonok's IT BlogUnknownnoreply@blogger.comBlogger1154125tag:blogger.com,1999:blog-4270346497183643494.post-75458891327884254162024-03-14T02:20:00.000-07:002024-03-14T02:20:09.232-07:00Does SnapMirror Support Interval Schedules? No<p style="text-align: left;">I was curious to see if I can use an interval schedule for SnapMirror but it is not possible.<br /><br />Below are my lab notes.<br /><br /><b>1) Create a 15 minute interval schedule</b><br /><br /><span style="font-family: courier;">cluster1::> job schedule interval create -cluster cluster1 -vserver cluster1 -name int_15mins -minutes 15</span><br /><br /><b>2) Can we use the 15 minute interval schedule in a snapshot policy? Yes</b><br /><br /><span style="font-family: courier;">cluster1::> snapshot policy create -policy snappol_15mins -vserver cluster1 -enabled true -comment "Snaps every 15 mins x 1000" -schedule1 int_15mins -count1 1000</span><br /><br /><b>3) Snapmirror test setup (SVMs already peered).</b><br /><br /><span style="font-family: courier;">cluster1::> volume create -vserver svm1_cluster1 -volume vol_test_1 -size 10g -aggregate cluster1_01_SSD_1</span><br /><span style="font-family: courier;"><br /></span><span style="font-family: courier;">cluster1::> volume create -vserver svm2_cluster1 -volume vol_test_1 -size 10g -aggregate cluster1_01_SSD_1 -type DP</span><br /><br /><b>4) Can we create a snapmirror relationship with an interval schedule? No</b><br /><br /><span style="font-family: courier;">cluster1::> snapmirror create -source-path svm1_cluster1:vol_test_1 -destination-path svm2_cluster1:vol_test_1 -policy MirrorAllSnapshots -schedule int_15mins</span><br /><span style="font-family: courier;"><br /></span><b style="color: red; font-family: courier;">Error: command failed: Schedule "int_15mins" is an interval schedule. SnapMirror does not support interval schedules.</b><br /><br /></p><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgCxKqOKY6cOXGWV7nv61jhPXXZr5ot1dEF4XNDwrQTqWZnPrRJfkZYwSsNJNieH6C_DIJqjWABq74gPm7ckw1QT37XwyMvx6A1wCiNuwbHLH7U6p_2H2FcIwPDMt4JPJegT3cUfZqi5HCElOHa-k5xwbcIsD7_d7I_5E3VWHrNURd8TKIhkVjieKB_JE0M/s568/ONTAP%209%20-%20Continuous%20Innovation.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="493" data-original-width="568" height="174" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgCxKqOKY6cOXGWV7nv61jhPXXZr5ot1dEF4XNDwrQTqWZnPrRJfkZYwSsNJNieH6C_DIJqjWABq74gPm7ckw1QT37XwyMvx6A1wCiNuwbHLH7U6p_2H2FcIwPDMt4JPJegT3cUfZqi5HCElOHa-k5xwbcIsD7_d7I_5E3VWHrNURd8TKIhkVjieKB_JE0M/w200-h174/ONTAP%209%20-%20Continuous%20Innovation.png" width="200" /></a></div>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-4270346497183643494.post-61412687874620133182024-03-13T12:14:00.000-07:002024-03-13T12:14:33.226-07:00ONTAP 9.14.1: Default SnapMirror Policies<p>There are 16 default SnapMirror Policies. Descriptions are below:</p><p style="text-align: left;"><span style="font-family: courier;">cluster1::> snapmirror policy show -fields policy,comment<br />policy: comment<br />---------------<br /><span style="background-color: #fcff01;">Asynchronous</span>: A unified Asynchronous SnapMirror and SnapVault policy for mirroring the latest active file system and daily and weekly Snapshot copies with an hourly transfer schedule.<br /><span style="background-color: #fcff01;">AutomatedFailOver</span>: Policy for SnapMirror Synchronous with zero RTO guarantee where client I/O will not be disrupted on replication failure.<br /><span style="background-color: #fcff01;">CloudBackupDefault</span>: Vault policy with daily rule.<br /><span style="background-color: #fcff01;">Continuous</span>: Policy for S3 bucket mirroring.<br /><span style="background-color: #fcff01;">DPDefault</span>: Asynchronous SnapMirror policy for mirroring all Snapshot copies and the latest active file system.<br /><span style="background-color: #fcff01;">DailyBackup</span>: Vault policy with a daily rule and a daily transfer schedule.<br /><span style="background-color: #fcff01;">MirrorAllSnapshots</span>: Asynchronous SnapMirror policy for mirroring all Snapshot copies and the latest active file system.<br /><span style="background-color: #fcff01;">MirrorAllSnapshotsDiscardNetwork</span>: Asynchronous SnapMirror policy for mirroring all Snapshot copies and the latest active file system excluding the network configurations.<br /><span style="background-color: #fcff01;">MirrorAndVault</span>: A unified Asynchronous SnapMirror and SnapVault policy for mirroring the latest active file system and daily and weekly Snapshot copies.<br /><span style="background-color: #fcff01;">MirrorAndVaultDiscardNetwork</span>: A unified Asynchronous SnapMirror and SnapVault policy for mirroring the latest active file system and daily and weekly Snapshot copies excluding the network configurations.<br /><span style="background-color: #fcff01;">MirrorLatest</span>: Asynchronous SnapMirror policy for mirroring the latest active file system. <br /><span style="background-color: #fcff01;">SnapCenterSync</span>: Policy for SnapMirror Synchronous for Snap Center with Application Created Snapshot configuration.<br /><span style="background-color: #fcff01;">StrictSync</span>: Policy for SnapMirror Synchronous where client access will be disrupted on replication failure.<br /><span style="background-color: #fcff01;">Sync</span>: Policy for SnapMirror Synchronous where client access will not be disrupted on replication failure.<br /><span style="background-color: #fcff01;">Unified7year</span>: Unified SnapMirror policy with 7year retention. <br /><span style="background-color: #fcff01;">XDPDefault</span>: Vault policy with daily and weekly rules.<br /> <br />16 entries were displayed.</span></p><p>Details of the specific SnapMirror policies are below (for the comments, please see above):</p><p style="text-align: left;"><span style="font-family: courier;">cluster1::> snapmirror policy show -instance</span><br /><span style="font-family: courier;"><br /></span><span style="font-family: courier;"> Vserver: cluster1</span><br /><span style="font-family: courier;"> SnapMirror Policy Name: </span><span style="background-color: #fcff01; font-family: courier;">Asynchronous</span><br /><span style="font-family: courier;"> SnapMirror Policy Type: </span><span style="background-color: #01ffff; font-family: courier;">mirror-vault</span><br /><span style="font-family: courier;"> Policy Owner: cluster-admin</span><br /><span style="font-family: courier;"> Tries Limit: 8</span><br /><span style="font-family: courier;"> Transfer Priority: normal</span><br /><span style="font-family: courier;">Ignore accesstime Enabled: false</span><br /><span style="font-family: courier;"> Transfer Restartability: always</span><br /><span style="font-family: courier;">Ntwrk Compression Enabled: false</span><br /><span style="font-family: courier;"> Create Snapshot: true</span><br /><span style="font-family: courier;"> Total Number of Rules: 3</span><br /><span style="font-family: courier;"> Total Keep: 60</span><br /><span style="font-family: courier;"> Transfer Schedule Name: hourly</span><br /><span style="font-family: courier;"> Throttle: unlimited</span><br /><span style="font-family: courier;"><br /></span><span style="font-family: courier;">Rules:</span><br /><span style="font-family: courier;">SM Label Keep Preserve Warn Schedule Prefix Retention</span><br /><span style="font-family: courier;">---------- ---- -------- ---- -------- ------ ---------</span><br /><span style="font-family: courier;">sm_created 1 false 0 - - -</span><br /><span style="font-family: courier;">daily 7 false 0 - - -</span><br /><span style="font-family: courier;">weekly 52 false 0 - - -</span><br /><span style="font-family: courier;"><br /></span><span style="font-family: courier;"> Vserver: cluster1</span><br /><span style="font-family: courier;"> SnapMirror Policy Name: <span style="background-color: #fcff01;">AutomatedFailOver</span></span><br /><span style="font-family: courier;"> SnapMirror Policy Type: <span style="background-color: #01ffff;">automated-failover</span></span><br /><span style="font-family: courier;"> Policy Owner: cluster-admin</span><br /><span style="font-family: courier;"> Tries Limit: 8</span><br /><span style="font-family: courier;"> Transfer Priority: normal</span><br /><span style="font-family: courier;"> Ignore accesstime Enabled: false</span><br /><span style="font-family: courier;"> Transfer Restartability: always</span><br /><span style="font-family: courier;"> Ntwrk Compression Enabled: false</span><br /><span style="font-family: courier;"> Create Snapshot: true</span><br /><span style="font-family: courier;"><span style="color: #2b00fe;">Always Replicate Snapshots: false</span></span><br /><span style="font-family: courier;"> Total Number of Rules: 1</span><br /><span style="font-family: courier;"> Total Keep: 1</span><br /><span style="font-family: courier;"> Transfer Schedule Name: -</span><br /><span style="font-family: courier;"> Throttle: unlimited</span><br /><span style="font-family: courier;"><br /></span><span style="font-family: courier;">Rules:</span><br /><span style="font-family: courier;">SM Label Keep Preserve Warn Schedule Prefix Retention</span><br /><span style="font-family: courier;">---------- ---- -------- ---- -------- ------ ---------</span><br /><span style="font-family: courier;">sm_created 1 false 0 - - -</span><br /><span style="font-family: courier;"><br /></span><span style="font-family: courier;"> Vserver: cluster1</span><br /><span style="font-family: courier;"> SnapMirror Policy Name: <span style="background-color: #fcff01;">CloudBackupDefault</span></span><br /><span style="font-family: courier;"> SnapMirror Policy Type: <span style="background-color: #01ffff;">vault</span></span><br /><span style="font-family: courier;"> Policy Owner: cluster-admin</span><br /><span style="font-family: courier;"> Tries Limit: 8</span><br /><span style="font-family: courier;"> Transfer Priority: normal</span><br /><span style="font-family: courier;">Ignore accesstime Enabled: false</span><br /><span style="font-family: courier;"> Transfer Restartability: always</span><br /><span style="font-family: courier;">Ntwrk Compression Enabled: false</span><br /><span style="font-family: courier;"> Create Snapshot: false</span><br /><span style="font-family: courier;"> Total Number of Rules: 1</span><br /><span style="font-family: courier;"> Total Keep: 7</span><br /><span style="font-family: courier;"> Transfer Schedule Name: -</span><br /><span style="font-family: courier;"> Throttle: unlimited</span><br /><span style="font-family: courier;"><br /></span><span style="font-family: courier;">Rules:</span><br /><span style="font-family: courier;">SM Label Keep Preserve Warn Schedule Prefix Retention</span><br /><span style="font-family: courier;">---------- ---- -------- ---- -------- ------ ---------</span><br /><span style="font-family: courier;">daily 7 false 0 - - -</span><br /><span style="font-family: courier;"><br /></span><span style="font-family: courier;"> Vserver: cluster1</span><br /><span style="font-family: courier;"> SnapMirror Policy Name: <span style="background-color: #fcff01;">Continuous</span></span><br /><span style="font-family: courier;"> SnapMirror Policy Type: <span style="background-color: #01ffff;">continuous</span></span><br /><span style="font-family: courier;"> Policy Owner: cluster-admin</span><br /><span style="font-family: courier;"> Tries Limit: 8</span><br /><span style="font-family: courier;"> Transfer Priority: normal</span><br /><span style="font-family: courier;">Ignore accesstime Enabled: false</span><br /><span style="font-family: courier;"> Transfer Restartability: always</span><br /><span style="font-family: courier;">Ntwrk Compression Enabled: -</span><br /><span style="font-family: courier;"> Create Snapshot: -</span><br /><span style="font-family: courier;"> Total Number of Rules: 0</span><br /><span style="font-family: courier;"> Total Keep: 0</span><br /><span style="font-family: courier;"> Recovery Point Objective: 3600</span><br /><span style="font-family: courier;"> Transfer Schedule Name: -</span><br /><span style="font-family: courier;"> Throttle: unlimited</span><br /><span style="font-family: courier;"><br /></span><span style="font-family: courier;">Rules:</span><br /><span style="font-family: courier;">SM Label Keep Preserve Warn Schedule Prefix Retention</span><br /><span style="font-family: courier;">---------- ---- -------- ---- -------- ------ ---------</span><br /><span style="font-family: courier;">- - - - - - -</span><br /><span style="font-family: courier;"><br /></span><span style="font-family: courier;"> Vserver: cluster1</span><br /><span style="font-family: courier;"> SnapMirror Policy Name: <span style="background-color: #fcff01;">DPDefault</span></span><br /><span style="font-family: courier;"> SnapMirror Policy Type: <span style="background-color: #01ffff;">async-mirror</span></span><br /><span style="font-family: courier;"> Policy Owner: cluster-admin</span><br /><span style="font-family: courier;"> Tries Limit: 8</span><br /><span style="font-family: courier;"> Transfer Priority: normal</span><br /><span style="font-family: courier;">Ignore accesstime Enabled: false</span><br /><span style="font-family: courier;"> Transfer Restartability: always</span><br /><span style="font-family: courier;">Ntwrk Compression Enabled: false</span><br /><span style="font-family: courier;"> Create Snapshot: true</span><br /><span style="font-family: courier;"> Total Number of Rules: 2</span><br /><span style="font-family: courier;"> Total Keep: 2</span><br /><span style="font-family: courier;"> Transfer Schedule Name: -</span><br /><span style="font-family: courier;"> Throttle: unlimited</span><br /><span style="font-family: courier;"><br /></span><span style="font-family: courier;">Rules:</span><br /><span style="font-family: courier;">SM Label Keep Preserve Warn Schedule Prefix Retention</span><br /><span style="font-family: courier;">---------- ---- -------- ---- -------- ------ ---------</span><br /><span style="font-family: courier;">sm_created 1 false 0 - - -</span><br /><span style="font-family: courier;">all_source_snapshots 1 false 0 - - -</span><br /><span style="font-family: courier;"><br /></span><span style="font-family: courier;"> Vserver: cluster1</span><br /><span style="font-family: courier;"> SnapMirror Policy Name: <span style="background-color: #fcff01;">DailyBackup</span></span><br /><span style="font-family: courier;"> SnapMirror Policy Type: <span style="background-color: #01ffff;">vault</span></span><br /><span style="font-family: courier;"> Policy Owner: cluster-admin</span><br /><span style="font-family: courier;"> Tries Limit: 8</span><br /><span style="font-family: courier;"> Transfer Priority: normal</span><br /><span style="font-family: courier;">Ignore accesstime Enabled: false</span><br /><span style="font-family: courier;"> Transfer Restartability: always</span><br /><span style="font-family: courier;">Ntwrk Compression Enabled: false</span><br /><span style="font-family: courier;"> Create Snapshot: false</span><br /><span style="font-family: courier;"> Total Number of Rules: 1</span><br /><span style="font-family: courier;"> Total Keep: 7</span><br /><span style="font-family: courier;"> Transfer Schedule Name: daily</span><br /><span style="font-family: courier;"> Throttle: unlimited</span><br /><span style="font-family: courier;"><br /></span><span style="font-family: courier;">Rules:</span><br /><span style="font-family: courier;">SM Label Keep Preserve Warn Schedule Prefix Retention</span><br /><span style="font-family: courier;">---------- ---- -------- ---- -------- ------ ---------</span><br /><span style="font-family: courier;">daily 7 false 0 - - -</span><br /><span style="font-family: courier;"><br /></span><span style="font-family: courier;"> Vserver: cluster1</span><br /><span style="font-family: courier;"> SnapMirror Policy Name: <span style="background-color: #fcff01;">MirrorAllSnapshots</span></span><br /><span style="font-family: courier;"> SnapMirror Policy Type: <span style="background-color: #01ffff;">async-mirror</span></span><br /><span style="font-family: courier;"> Policy Owner: cluster-admin</span><br /><span style="font-family: courier;"> Tries Limit: 8</span><br /><span style="font-family: courier;"> Transfer Priority: normal</span><br /><span style="font-family: courier;">Ignore accesstime Enabled: false</span><br /><span style="font-family: courier;"> Transfer Restartability: always</span><br /><span style="font-family: courier;">Ntwrk Compression Enabled: false</span><br /><span style="font-family: courier;"> Create Snapshot: true</span><br /><span style="font-family: courier;"> Total Number of Rules: 2</span><br /><span style="font-family: courier;"> Total Keep: 2</span><br /><span style="font-family: courier;"> Transfer Schedule Name: -</span><br /><span style="font-family: courier;"> Throttle: unlimited</span><br /><span style="font-family: courier;"><br /></span><span style="font-family: courier;">Rules:</span><br /><span style="font-family: courier;">SM Label Keep Preserve Warn Schedule Prefix Retention</span><br /><span style="font-family: courier;">---------- ---- -------- ---- -------- ------ ---------</span><br /><span style="font-family: courier;">sm_created 1 false 0 - - -</span><br /><span style="font-family: courier;">all_source_snapshots 1 false 0 - - -</span><br /><span style="font-family: courier;"><br /></span><span style="font-family: courier;"> Vserver: cluster1</span><br /><span style="font-family: courier;"> SnapMirror Policy Name: <span style="background-color: #fcff01;">MirrorAllSnapshotsDiscardNetwork</span></span><br /><span style="font-family: courier;"> SnapMirror Policy Type: <span style="background-color: #01ffff;">async-mirror</span></span><br /><span style="font-family: courier;"> Policy Owner: cluster-admin</span><br /><span style="font-family: courier;"> Tries Limit: 8</span><br /><span style="font-family: courier;"> Transfer Priority: normal</span><br /><span style="font-family: courier;">Ignore accesstime Enabled: false</span><br /><span style="font-family: courier;"> Transfer Restartability: always</span><br /><span style="font-family: courier;">Ntwrk Compression Enabled: false</span><br /><span style="font-family: courier;"> Create Snapshot: true</span><br /><span style="font-family: courier;"> Discard Configs: network</span><br /><span style="font-family: courier;"> Total Number of Rules: 2</span><br /><span style="font-family: courier;"> Total Keep: 2</span><br /><span style="font-family: courier;"> Transfer Schedule Name: -</span><br /><span style="font-family: courier;"> Throttle: unlimited</span><br /><span style="font-family: courier;"><br /></span><span style="font-family: courier;">Rules:</span><br /><span style="font-family: courier;">SM Label Keep Preserve Warn Schedule Prefix Retention</span><br /><span style="font-family: courier;">---------- ---- -------- ---- -------- ------ ---------</span><br /><span style="font-family: courier;">sm_created 1 false 0 - - -</span><br /><span style="font-family: courier;">all_source_snapshots 1 false 0 - - -</span><br /><span style="font-family: courier;"><br /></span><span style="font-family: courier;"> Vserver: cluster1</span><br /><span style="font-family: courier;"> SnapMirror Policy Name: <span style="background-color: #fcff01;">MirrorAndVault</span></span><br /><span style="font-family: courier;"> SnapMirror Policy Type: <span style="background-color: #01ffff;">mirror-vault</span></span><br /><span style="font-family: courier;"> Policy Owner: cluster-admin</span><br /><span style="font-family: courier;"> Tries Limit: 8</span><br /><span style="font-family: courier;"> Transfer Priority: normal</span><br /><span style="font-family: courier;">Ignore accesstime Enabled: false</span><br /><span style="font-family: courier;"> Transfer Restartability: always</span><br /><span style="font-family: courier;">Ntwrk Compression Enabled: false</span><br /><span style="font-family: courier;"> Create Snapshot: true</span><br /><span style="font-family: courier;"> Total Number of Rules: 3</span><br /><span style="font-family: courier;"> Total Keep: 60</span><br /><span style="font-family: courier;"> Transfer Schedule Name: -</span><br /><span style="font-family: courier;"> Throttle: unlimited</span><br /><span style="font-family: courier;"><br /></span><span style="font-family: courier;">Rules:</span><br /><span style="font-family: courier;">SM Label Keep Preserve Warn Schedule Prefix Retention</span><br /><span style="font-family: courier;">---------- ---- -------- ---- -------- ------ ---------</span><br /><span style="font-family: courier;">sm_created 1 false 0 - - -</span><br /><span style="font-family: courier;">daily 7 false 0 - - -</span><br /><span style="font-family: courier;">weekly 52 false 0 - - -</span><br /><span style="font-family: courier;"><br /></span><span style="font-family: courier;"> Vserver: cluster1</span><br /><span style="font-family: courier;"> SnapMirror Policy Name: <span style="background-color: #fcff01;">MirrorAndVaultDiscardNetwork</span></span><br /><span style="font-family: courier;"> SnapMirror Policy Type: <span style="background-color: #01ffff;">mirror-vault</span></span><br /><span style="font-family: courier;"> Policy Owner: cluster-admin</span><br /><span style="font-family: courier;"> Tries Limit: 8</span><br /><span style="font-family: courier;"> Transfer Priority: normal</span><br /><span style="font-family: courier;">Ignore accesstime Enabled: false</span><br /><span style="font-family: courier;"> Transfer Restartability: always</span><br /><span style="font-family: courier;">Ntwrk Compression Enabled: false</span><br /><span style="font-family: courier;"> Create Snapshot: true</span><br /><span style="font-family: courier;"> Discard Configs: network</span><br /><span style="font-family: courier;"> Total Number of Rules: 3</span><br /><span style="font-family: courier;"> Total Keep: 60</span><br /><span style="font-family: courier;"> Transfer Schedule Name: -</span><br /><span style="font-family: courier;"> Throttle: unlimited</span><br /><span style="font-family: courier;"><br /></span><span style="font-family: courier;">Rules:</span><br /><span style="font-family: courier;">SM Label Keep Preserve Warn Schedule Prefix Retention</span><br /><span style="font-family: courier;">---------- ---- -------- ---- -------- ------ ---------</span><br /><span style="font-family: courier;">sm_created 1 false 0 - - -</span><br /><span style="font-family: courier;">daily 7 false 0 - - -</span><br /><span style="font-family: courier;">weekly 52 false 0 - - -</span><br /><span style="font-family: courier;"><br /></span><span style="font-family: courier;"> Vserver: cluster1</span><br /><span style="font-family: courier;"> SnapMirror Policy Name: <span style="background-color: #fcff01;">MirrorLatest</span></span><br /><span style="font-family: courier;"> SnapMirror Policy Type: <span style="background-color: #01ffff;">async-mirror</span></span><br /><span style="font-family: courier;"> Policy Owner: cluster-admin</span><br /><span style="font-family: courier;"> Tries Limit: 8</span><br /><span style="font-family: courier;"> Transfer Priority: normal</span><br /><span style="font-family: courier;">Ignore accesstime Enabled: false</span><br /><span style="font-family: courier;"> Transfer Restartability: always</span><br /><span style="font-family: courier;">Ntwrk Compression Enabled: false</span><br /><span style="font-family: courier;"> Create Snapshot: true</span><br /><span style="font-family: courier;"> Total Number of Rules: 1</span><br /><span style="font-family: courier;"> Total Keep: 1</span><br /><span style="font-family: courier;"> Transfer Schedule Name: -</span><br /><span style="font-family: courier;"> Throttle: unlimited</span><br /><span style="font-family: courier;"><br /></span><span style="font-family: courier;">Rules:</span><br /><span style="font-family: courier;">SM Label Keep Preserve Warn Schedule Prefix Retention</span><br /><span style="font-family: courier;">---------- ---- -------- ---- -------- ------ ---------</span><br /><span style="font-family: courier;">sm_created 1 false 0 - - -</span><br /><span style="font-family: courier;"><br /></span><span style="font-family: courier;"> Vserver: cluster1</span><br /><span style="font-family: courier;"> SnapMirror Policy Name: <span style="background-color: #fcff01;">SnapCenterSync</span></span><br /><span style="font-family: courier;"> SnapMirror Policy Type: <span style="background-color: #01ffff;">sync-mirror</span></span><br /><span style="font-family: courier;"> Policy Owner: cluster-admin</span><br /><span style="font-family: courier;"> Tries Limit: 8</span><br /><span style="font-family: courier;"> Transfer Priority: normal</span><br /><span style="font-family: courier;"> Ignore accesstime Enabled: false</span><br /><span style="font-family: courier;"> Transfer Restartability: always</span><br /><span style="font-family: courier;"> Ntwrk Compression Enabled: false</span><br /><span style="font-family: courier;"> Create Snapshot: true</span><br /><span style="font-family: courier;"><span style="color: #2b00fe;">Always Replicate Snapshots: false</span></span><br /><span style="font-family: courier;"> Total Number of Rules: 2</span><br /><span style="font-family: courier;"> Total Keep: 3</span><br /><span style="font-family: courier;"> Transfer Schedule Name: -</span><br /><span style="font-family: courier;"> Throttle: unlimited</span><br /><span style="font-family: courier;"><br /></span><span style="font-family: courier;">Rules:</span><br /><span style="font-family: courier;">SM Label Keep Preserve Warn Schedule Prefix Retention</span><br /><span style="font-family: courier;">---------- ---- -------- ---- -------- ------ ---------</span><br /><span style="font-family: courier;">sm_created 2 false 0 - - -</span><br /><span style="font-family: courier;">app_consistent 1 false 0 - - -</span><br /><span style="font-family: courier;"><br /></span><span style="font-family: courier;"> Vserver: cluster1</span><br /><span style="font-family: courier;"> SnapMirror Policy Name: <span style="background-color: #fcff01;">StrictSync</span></span><br /><span style="font-family: courier;"> SnapMirror Policy Type: <span style="background-color: #01ffff;">strict-sync-mirror</span></span><br /><span style="font-family: courier;"> Policy Owner: cluster-admin</span><br /><span style="font-family: courier;"> Tries Limit: 8</span><br /><span style="font-family: courier;"> Transfer Priority: normal</span><br /><span style="font-family: courier;"> Ignore accesstime Enabled: false</span><br /><span style="font-family: courier;"> Transfer Restartability: always</span><br /><span style="font-family: courier;"> Ntwrk Compression Enabled: false</span><br /><span style="font-family: courier;"> Create Snapshot: true</span><br /><span style="font-family: courier;"><span style="color: #2b00fe;">Always Replicate Snapshots: false</span></span><br /><span style="font-family: courier;"> Total Number of Rules: 1</span><br /><span style="font-family: courier;"> Total Keep: 2</span><br /><span style="font-family: courier;"> Transfer Schedule Name: -</span><br /><span style="font-family: courier;"> Throttle: unlimited</span><br /><span style="font-family: courier;"><br /></span><span style="font-family: courier;">Rules:</span><br /><span style="font-family: courier;">SM Label Keep Preserve Warn Schedule Prefix Retention</span><br /><span style="font-family: courier;">---------- ---- -------- ---- -------- ------ ---------</span><br /><span style="font-family: courier;">sm_created 2 false 0 - - -</span><br /><span style="font-family: courier;"><br /></span><span style="font-family: courier;"> Vserver: cluster1</span><br /><span style="font-family: courier;"> SnapMirror Policy Name: <span style="background-color: #fcff01;">Sync</span></span><br /><span style="font-family: courier;"> SnapMirror Policy Type: <span style="background-color: #01ffff;">sync-mirror</span></span><br /><span style="font-family: courier;"> Policy Owner: cluster-admin</span><br /><span style="font-family: courier;"> Tries Limit: 8</span><br /><span style="font-family: courier;"> Transfer Priority: normal</span><br /><span style="font-family: courier;"> Ignore accesstime Enabled: false</span><br /><span style="font-family: courier;"> Transfer Restartability: always</span><br /><span style="font-family: courier;"> Ntwrk Compression Enabled: false</span><br /><span style="font-family: courier;"> Create Snapshot: true</span><br /><span style="font-family: courier;"><span style="color: #2b00fe;">Always Replicate Snapshots: false</span></span><br /><span style="font-family: courier;"> Total Number of Rules: 1</span><br /><span style="font-family: courier;"> Total Keep: 2</span><br /><span style="font-family: courier;"> Transfer Schedule Name: -</span><br /><span style="font-family: courier;"> Throttle: unlimited</span><br /><span style="font-family: courier;"><br /></span><span style="font-family: courier;">Rules:</span><br /><span style="font-family: courier;">SM Label Keep Preserve Warn Schedule Prefix Retention</span><br /><span style="font-family: courier;">---------- ---- -------- ---- -------- ------ ---------</span><br /><span style="font-family: courier;">sm_created 2 false 0 - - -</span><br /><span style="font-family: courier;"><br /></span><span style="font-family: courier;"> Vserver: cluster1</span><br /><span style="font-family: courier;"> SnapMirror Policy Name: <span style="background-color: #fcff01;">Unified7year</span></span><br /><span style="font-family: courier;"> SnapMirror Policy Type: <span style="background-color: #01ffff;">mirror-vault</span></span><br /><span style="font-family: courier;"> Policy Owner: cluster-admin</span><br /><span style="font-family: courier;"> Tries Limit: 8</span><br /><span style="font-family: courier;"> Transfer Priority: normal</span><br /><span style="font-family: courier;">Ignore accesstime Enabled: false</span><br /><span style="font-family: courier;"> Transfer Restartability: always</span><br /><span style="font-family: courier;">Ntwrk Compression Enabled: false</span><br /><span style="font-family: courier;"> Create Snapshot: true</span><br /><span style="font-family: courier;"> Total Number of Rules: 4</span><br /><span style="font-family: courier;"> Total Keep: 144</span><br /><span style="font-family: courier;"> Transfer Schedule Name: -</span><br /><span style="font-family: courier;"> Throttle: unlimited</span><br /><span style="font-family: courier;"><br /></span><span style="font-family: courier;">Rules:</span><br /><span style="font-family: courier;">SM Label Keep Preserve Warn Schedule Prefix Retention</span><br /><span style="font-family: courier;">---------- ---- -------- ---- -------- ------ ---------</span><br /><span style="font-family: courier;">sm_created 1 false 0 - - -</span><br /><span style="font-family: courier;">daily 7 false 0 - - -</span><br /><span style="font-family: courier;">weekly 52 false 0 - - -</span><br /><span style="font-family: courier;">monthly 84 false 0 monthly - -</span><br /><span style="font-family: courier;"><br /></span><span style="font-family: courier;"> Vserver: cluster1</span><br /><span style="font-family: courier;"> SnapMirror Policy Name: <span style="background-color: #fcff01;">XDPDefault</span></span><br /><span style="font-family: courier;"> SnapMirror Policy Type: <span style="background-color: #01ffff;">vault</span></span><br /><span style="font-family: courier;"> Policy Owner: cluster-admin</span><br /><span style="font-family: courier;"> Tries Limit: 8</span><br /><span style="font-family: courier;"> Transfer Priority: normal</span><br /><span style="font-family: courier;">Ignore accesstime Enabled: false</span><br /><span style="font-family: courier;"> Transfer Restartability: always</span><br /><span style="font-family: courier;">Ntwrk Compression Enabled: false</span><br /><span style="font-family: courier;"> Create Snapshot: false</span><br /><span style="font-family: courier;"> Total Number of Rules: 2</span><br /><span style="font-family: courier;"> Total Keep: 59</span><br /><span style="font-family: courier;"> Transfer Schedule Name: -</span><br /><span style="font-family: courier;"> Throttle: unlimited</span><br /><span style="font-family: courier;"><br /></span><span style="font-family: courier;">Rules:</span><br /><span style="font-family: courier;">SM Label Keep Preserve Warn Schedule Prefix Retention</span><br /><span style="font-family: courier;">---------- ---- -------- ---- -------- ------ ---------</span><br /><span style="font-family: courier;">daily 7 false 0 - - -</span><br /><span style="font-family: courier;">weekly 52 false 0 - - -</span></p><p><br /></p><p><b><u><span style="font-size: large;">Creating SnapMirror Policies</span></u></b></p><p style="text-align: left;"><span style="font-family: courier;">cluster1::} snapmirror policy create ?</span><br /><span style="font-family: courier;"> -vserver {vserver name}</span><br /><span style="font-family: courier;"> [-policy] {snapmirror policy}</span><br /><span style="font-family: courier;"> [[-type] {SEE[1]}] Snapmirror Policy Type</span><br /><span style="font-family: courier;"> [ -comment {text} ]</span><br /><span style="font-family: courier;"> [ -tries {{integer}|unlimited} ]</span><br /><span style="font-family: courier;"> [ -transfer-priority {low|normal} ]</span><br /><span style="font-family: courier;"> [ -ignore-atime {true|false} ]</span><br /><span style="font-family: courier;"> [ -restart {always|never|default} ]</span><br /><span style="font-family: courier;"> [ -is-network-compression-enabled {true|false} ]</span><br /><span style="font-family: courier;"> [ -rpo {integer} ]</span><br /><span style="font-family: courier;"> [ -always-replicate-snapshots {true|false} ]</span><br /><span style="font-family: courier;"> [ -retention-period {SEE[2]}, ... ]</span><br /><span style="font-family: courier;"> [ -transfer-schedule-name {text} ]</span><br /><span style="font-family: courier;"> [ -throttle {{integer}|unlimited} ]</span><br /><span style="font-family: courier;"><br /></span><span style="font-family: courier;">[1] vault|async-mirror|mirror-vault|strict-sync-mirror|sync-mirror|automated-failover|continuous</span><br /><span style="font-family: courier;">[2] {{integer} seconds|minutes|hours|days|months|years} | infinite</span></p><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgy8RLcSiCJaogaadyMQZu4hoFZkPNHiBp89_SQHIE9xKbrNA4hbL5BemBrtHoj_M3kwnZdKmwDDqn43FvKhdjrPuFjS5SPjTb-6HUKB4iw7uhCiZTf9zc8WKKNpEdiIjvKFjXgIhIQZI-dfVu1xG3xL8xPhWk3EYYSLJBlE2W_VzhVf7wE4m1uUylLiZbg/s568/ONTAP%209%20-%20Continuous%20Innovation.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="493" data-original-width="568" height="174" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgy8RLcSiCJaogaadyMQZu4hoFZkPNHiBp89_SQHIE9xKbrNA4hbL5BemBrtHoj_M3kwnZdKmwDDqn43FvKhdjrPuFjS5SPjTb-6HUKB4iw7uhCiZTf9zc8WKKNpEdiIjvKFjXgIhIQZI-dfVu1xG3xL8xPhWk3EYYSLJBlE2W_VzhVf7wE4m1uUylLiZbg/w200-h174/ONTAP%209%20-%20Continuous%20Innovation.png" width="200" /></a></div>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-4270346497183643494.post-76675105698621994972024-03-12T10:43:00.000-07:002024-03-12T10:43:17.558-07:00ONTAP 9.14.1: Default Schedules and Snapshot Policies<p style="text-align: left;"><b><u><span lang="EN-US" style="font-size: 16.0pt; mso-ansi-language: EN-US;">Default Schedules</span></u></b><br /> <br />There
are 31 default schedules in ONTAP 9.14.1 as seen from the output of::><br /> <br /><span style="font-family: "Courier New";">job schedule show</span><br /> <br />28 are
cron type and 3 are schedule type.<br /> <br />Only 3
of the cron type ones are used in the default Snapshot Policies β hourly, daily
and weekly. These 3 default job schedules are detailed here:<br /> <br /><span style="font-family: "Courier New";">cluster1::> job schedule show -name hourly
-instance</span><br /><span style="font-family: "Courier New";"> </span><br /><span style="font-family: "Courier New";"> </span><span style="font-family: "Courier New";">Cluster:
cluster1</span><br /><span style="font-family: "Courier New";"> </span><span style="font-family: "Courier New";">Vserver:
cluster1</span><br /><span style="background-color: yellow; font-family: "Courier New";">Schedule Name:
hourly</span><br /><span style="background-color: yellow; font-family: "Courier New";">Schedule Type:
cron</span><br /><span style="font-family: "Courier New";"> </span><span style="background-color: yellow; font-family: "Courier New";">Description: @:05</span><br /><span style="font-family: "Courier New";"> </span><br /><span style="font-family: "Courier New";">cluster1::> job schedule show -name daily -instance</span><br /><span style="font-family: "Courier New";"> </span><br /><span style="font-family: "Courier New";"> </span><span style="font-family: "Courier New";">Cluster:
cluster1</span><br /><span style="font-family: "Courier New";"> </span><span style="font-family: "Courier New";">Vserver:
cluster1</span><br /><span style="background-color: yellow; font-family: "Courier New";">Schedule Name:
daily</span><br /><span style="background-color: yellow; font-family: "Courier New";">Schedule Type:
cron</span><br /><span style="font-family: "Courier New";"> </span><span style="background-color: yellow; font-family: "Courier New";">Description: @0:10</span><br /><span style="font-family: "Courier New";"> </span><br /><span style="font-family: "Courier New";">cluster1::> job schedule show -name weekly
-instance</span><br /><span style="font-family: "Courier New";"> </span><br /><span style="font-family: "Courier New";"> </span><span style="font-family: "Courier New";">Cluster:
cluster1</span><br /><span style="font-family: "Courier New";"> </span><span style="font-family: "Courier New";">Vserver:
cluster1</span><br /><span style="background-color: yellow; font-family: "Courier New";">Schedule Name:
weekly</span><br /><span style="background-color: yellow; font-family: "Courier New";">Schedule Type:
cron</span><br /><span style="font-family: "Courier New";"> </span><span style="background-color: yellow; font-family: "Courier New";">Description: Sun@0:15</span><br /><span style="font-family: "Courier New";"> </span><br />CLI
commands to create similar:<br /> <br /><span style="font-family: "Courier New";">job schedule cron create -cluster cluster1 -vserver
cluster1 -name </span><span style="background: yellow; font-family: "Courier New";">hourly_v2</span><span style="font-family: "Courier New";">
-minute </span><span style="background: yellow; font-family: "Courier New";">5</span><br /><span style="font-family: "Courier New";"> </span><br /><span style="font-family: "Courier New";">job schedule cron create -cluster cluster1 -vserver
cluster1 -name </span><span style="background: yellow; font-family: "Courier New";">daily_v2</span><span style="font-family: "Courier New";">
-hour </span><span style="background: yellow; font-family: "Courier New";">0</span><span style="font-family: "Courier New";"> -minute </span><span style="background: yellow; font-family: "Courier New";">10</span><br /><span style="font-family: "Courier New";"> </span><br /><span style="font-family: "Courier New";">job schedule cron create -cluster cluster1 -vserver
cluster1 -name </span><span style="background: yellow; font-family: "Courier New";">weekly_v2</span><span style="font-family: "Courier New";">
-dayofweek </span><span style="background: yellow; font-family: "Courier New";">sun</span><span style="font-family: "Courier New";">
-hour </span><span style="background: yellow; font-family: "Courier New";">0</span><span style="font-family: "Courier New";"> -minute </span><span style="background: yellow; font-family: "Courier New";">15</span><br /> <br /><b><span lang="EN-US">Job
Schedule Cron Create</span></b><span lang="EN-US">
parameters:</span><br /> <br /><span style="font-family: "Courier New";">cluster1::} job schedule cron create ?</span><br /><span style="font-family: "Courier New";"> </span><span style="font-family: "Courier New";">[ -cluster
{cluster_name} ]</span><br /><span style="font-family: "Courier New";"> </span><span style="font-family: "Courier New";">[ -vserver
{vserver name} ]</span><br /><span style="font-family: "Courier New";"> </span><span style="font-family: "Courier New";">[-name] {text
(size 1..256)}</span><br /><span style="font-family: "Courier New";"> </span><span style="font-family: "Courier New";">[ -month
{cron_month}, ... ]</span><br /><span style="font-family: "Courier New";"> </span><span style="font-family: "Courier New";">[ -dayofweek
{cron_dayofweek}, ... ]</span><br /><span style="font-family: "Courier New";"> </span><span style="font-family: "Courier New";">[ -day
{cron_dayofmonth}, ... ]</span><br /><span style="font-family: "Courier New";"> </span><span style="font-family: "Courier New";">[ -hour
{cron_hour}, ... ]</span><br /><span style="font-family: "Courier New";"> </span><span style="font-family: "Courier New";">[-minute]
{cron_minute}, ...</span><br /> <br /><b><span lang="EN-US">Job
Schedule Interval Create</span></b><span lang="EN-US"> parameters:</span><br /> <br /><span style="font-family: "Courier New";">cluster1::} job schedule interval create ?</span><br /><span style="font-family: "Courier New";"> </span><span style="font-family: "Courier New";">[ -cluster
{cluster_name} ]</span><br /><span style="font-family: "Courier New";"> </span><span style="font-family: "Courier New";">[ -vserver
{vserver name} ]</span><br /><span style="font-family: "Courier New";"> </span><span style="font-family: "Courier New";">[-name] {text
(size 1..256)}</span><br /><span style="font-family: "Courier New";"> </span><span style="font-family: "Courier New";">[[-days]
{integer}]</span><br /><span style="font-family: "Courier New";"> </span><span style="font-family: "Courier New";">[ -hours
{integer} ]</span><br /><span style="font-family: "Courier New";"> </span><span style="font-family: "Courier New";">[ -minutes
{integer} ]</span><br /><span style="font-family: "Courier New";"> </span><span style="font-family: "Courier New";">[ -seconds
{integer} ]</span><br /> <br /><b><u><span lang="EN-US" style="font-size: 16.0pt; mso-ansi-language: EN-US;">Default Snapshot Policies</span></u></b><br /> <br />There are 3 default Snapshot Policies β none, default
and default-1weekly. As detailed below:<br /> <br /><span style="font-family: "Courier New";">cluster1::> snapshot policy show -policy none
-instance</span><br /><span style="font-family: "Courier New";"> </span><br /><span style="font-family: "Courier New";">Vserver: cluster1</span><br /><span style="font-family: "Courier New";">Snapshot Policy Name: </span><b style="font-family: "Courier New";"><span style="background: yellow; mso-highlight: yellow;">none</span></b><br /><span style="font-family: "Courier New";">Snapshot Policy Enabled: </span><span style="background: yellow; font-family: "Courier New";">false</span><br /><span style="font-family: "Courier New";">Policy Owner: cluster-admin</span><br /><span style="font-family: "Courier New";">Comment: </span><span style="background: yellow; font-family: "Courier New";">Policy for no automatic snapshots.</span><br /><span style="font-family: "Courier New";"> </span><br /><span style="font-family: "Courier New";">Total Number of Schedules: 0</span><br /><span style="font-family: "Courier New";">Schedule</span><span style="font-family: "Courier New";">
</span><span style="font-family: "Courier New";">Count</span><span style="font-family: "Courier New";"> </span><span style="font-family: "Courier New";">Prefix</span><span style="font-family: "Courier New";"> </span><span style="font-family: "Courier New";">SnapMirror Label</span><span style="font-family: "Courier New";"> </span><span style="font-family: "Courier New";">Retention Period</span><br /><span style="font-family: "Courier New";">--------</span><span style="font-family: "Courier New";">
</span><span style="font-family: "Courier New";">-----</span><span style="font-family: "Courier New";"> </span><span style="font-family: "Courier New";">------</span><span style="font-family: "Courier New";"> </span><span style="font-family: "Courier New";">----------------</span><span style="font-family: "Courier New";"> </span><span style="font-family: "Courier New";">----------------</span><br /><span style="font-family: "Courier New";">-</span><span style="font-family: "Courier New";">
</span><span style="font-family: "Courier New";">-</span><span style="font-family: "Courier New";"> </span><span style="font-family: "Courier New";">-</span><span style="font-family: "Courier New";"> </span><span style="font-family: "Courier New";">-</span><span style="font-family: "Courier New";"> </span><span style="font-family: "Courier New";">-</span><br /><span style="font-family: "Courier New";"> </span><br /><span style="font-family: "Courier New";">cluster1::> snapshot policy show -policy default
-instance</span><br /><span style="font-family: "Courier New";"> </span><br /><span style="font-family: "Courier New";">Vserver: cluster1</span><br /><span style="font-family: "Courier New";">Snapshot Policy Name: </span><b style="font-family: "Courier New";"><span style="background: yellow; mso-highlight: yellow;">default</span></b><br /><span style="font-family: "Courier New";">Snapshot Policy Enabled: true</span><br /><span style="font-family: "Courier New";">Policy Owner: cluster-admin</span><br /><span style="font-family: "Courier New";">Comment: </span><span style="background: yellow; font-family: "Courier New";">Default policy with hourly, daily & weekly schedules.</span><br /><span style="font-family: "Courier New";"> </span><br /><span style="font-family: "Courier New";">Total Number of Schedules: 3</span><br /><span style="font-family: "Courier New";">Schedule</span><span style="font-family: "Courier New";">
</span><span style="font-family: "Courier New";">Count</span><span style="font-family: "Courier New";"> </span><span style="font-family: "Courier New";">Prefix</span><span style="font-family: "Courier New";"> </span><span style="font-family: "Courier New";">SnapMirror Label</span><span style="font-family: "Courier New";"> </span><span style="font-family: "Courier New";">Retention Period</span><br /><span style="font-family: "Courier New";">--------</span><span style="font-family: "Courier New";">
</span><span style="font-family: "Courier New";">-----</span><span style="font-family: "Courier New";"> </span><span style="font-family: "Courier New";">------</span><span style="font-family: "Courier New";"> </span><span style="font-family: "Courier New";">----------------</span><span style="font-family: "Courier New";"> </span><span style="font-family: "Courier New";">----------------</span><br /><span style="background-color: yellow; font-family: "Courier New";">hourly</span><span style="font-family: "Courier New";"> </span><span style="background-color: yellow; font-family: "Courier New";">6</span><span style="font-family: "Courier New";">
</span><span style="background-color: yellow; font-family: "Courier New";">hourly</span><span style="font-family: "Courier New";"> </span><span style="background-color: yellow; font-family: "Courier New";">-</span><span style="font-family: "Courier New";"> </span><span style="background-color: yellow; font-family: "Courier New";">0 seconds</span><br /><span style="background-color: yellow; font-family: "Courier New";">daily</span><span style="font-family: "Courier New";"> </span><span style="background-color: yellow; font-family: "Courier New";">2</span><span style="font-family: "Courier New";">
</span><span style="background-color: yellow; font-family: "Courier New";">daily</span><span style="font-family: "Courier New";"> </span><span style="background-color: yellow; font-family: "Courier New";">daily</span><span style="font-family: "Courier New";"> </span><span style="background-color: yellow; font-family: "Courier New";">0 seconds</span><br /><span style="background-color: yellow; font-family: "Courier New";">weekly</span><span style="font-family: "Courier New";"> </span><span style="background-color: yellow; font-family: "Courier New";">2</span><span style="font-family: "Courier New";">
</span><span style="background-color: yellow; font-family: "Courier New";">weekly</span><span style="font-family: "Courier New";"> </span><span style="background-color: yellow; font-family: "Courier New";">weekly</span><span style="font-family: "Courier New";"> </span><span style="background-color: yellow; font-family: "Courier New";">0 seconds</span><br /><span style="font-family: "Courier New";"> </span><br /><span style="font-family: "Courier New";">cluster1::> snapshot policy show -policy
default-1weekly -instance</span><br /><span style="font-family: "Courier New";"> </span><br /><span style="font-family: "Courier New";">Vserver: cluster1</span><br /><span style="font-family: "Courier New";">Snapshot Policy Name: </span><b style="font-family: "Courier New";"><span style="background: yellow; mso-highlight: yellow;">default-1weekly</span></b><br /><span style="font-family: "Courier New";">Snapshot Policy Enabled: true</span><br /><span style="font-family: "Courier New";">Policy Owner: cluster-admin</span><br /><span style="font-family: "Courier New";">Comment: </span><span style="background: yellow; font-family: "Courier New";">Default policy with 6 hourly, 2 daily & 1 weekly schedule.</span><br /><span style="font-family: "Courier New";"> </span><span style="font-family: "Courier New";"> </span><br /><span style="font-family: "Courier New";">Total Number of Schedules: 3</span><br /><span style="font-family: "Courier New";">Schedule</span><span style="font-family: "Courier New";">
</span><span style="font-family: "Courier New";">Count</span><span style="font-family: "Courier New";"> </span><span style="font-family: "Courier New";">Prefix</span><span style="font-family: "Courier New";"> </span><span style="font-family: "Courier New";">SnapMirror Label</span><span style="font-family: "Courier New";"> </span><span style="font-family: "Courier New";">Retention Period</span><br /><span style="font-family: "Courier New";">--------</span><span style="font-family: "Courier New";">
</span><span style="font-family: "Courier New";">-----</span><span style="font-family: "Courier New";"> </span><span style="font-family: "Courier New";">------</span><span style="font-family: "Courier New";"> </span><span style="font-family: "Courier New";">----------------</span><span style="font-family: "Courier New";"> </span><span style="font-family: "Courier New";">----------------</span><br /><span style="background-color: yellow; font-family: "Courier New";">hourly</span><span style="font-family: "Courier New";"> </span><span style="background-color: yellow; font-family: "Courier New";">6</span><span style="font-family: "Courier New";">
</span><span style="background-color: yellow; font-family: "Courier New";">hourly</span><span style="font-family: "Courier New";"> </span><span style="background-color: yellow; font-family: "Courier New";">-</span><span style="font-family: "Courier New";"> </span><span style="background-color: yellow; font-family: "Courier New";">0 seconds</span><br /><span style="background-color: yellow; font-family: "Courier New";">daily</span><span style="font-family: "Courier New";"> </span><span style="background-color: yellow; font-family: "Courier New";">2</span><span style="font-family: "Courier New";">
</span><span style="background-color: yellow; font-family: "Courier New";">daily</span><span style="font-family: "Courier New";"> </span><span style="background-color: yellow; font-family: "Courier New";">-</span><span style="font-family: "Courier New";"> </span><span style="background-color: yellow; font-family: "Courier New";">0 seconds</span><br /><span style="background-color: yellow; font-family: "Courier New";">weekly</span><span style="font-family: "Courier New";"> </span><span style="background-color: yellow; font-family: "Courier New";">1</span><span style="font-family: "Courier New";">
</span><span style="background-color: yellow; font-family: "Courier New";">weekly</span><span style="font-family: "Courier New";"> </span><span style="background-color: yellow; font-family: "Courier New";">-</span><span style="font-family: "Courier New";"> </span><span style="background-color: yellow; font-family: "Courier New";">0 seconds</span><br /> <br />CLI commands to create similar:<br /> <br /><span style="font-family: "Courier New";">snapshot policy create -vserver cluster1 -policy </span><span style="background: yellow; font-family: "Courier New";">default_v2</span><span style="font-family: "Courier New";"> -enabled true
-comment "Default policy with hourly, daily & weekly schedules."
-schedule1 hourly -count1 6 -prefix1 hourly -schedule2 daily -count2 2 -prefix2
daily -snapmirror-label2 daily -schedule3 weekly -count3 2 -prefix3 weekly
-snapmirror-label3 weekly</span><br /><span style="font-family: "Courier New";"> </span><br /><span style="font-family: "Courier New";">snapshot policy create -vserver cluster1 -policy </span><span style="background: yellow; font-family: "Courier New";">default-1weekly_v2</span><span style="font-family: "Courier New";">
-enabled true -comment "Default policy with 6 hourly, 2 daily & 1
weekly schedule." -schedule1 hourly -count1 6 -prefix1 hourly -schedule2
daily -count2 2 -prefix2 daily -schedule3 weekly -count3 1 -prefix3 weekly</span><br /> <br /><i><span lang="EN-US">Note: You cannot recreate the βnoneβ snapshot policy
as the CLI expects at least one schedule.</span></i><br /> <br /><b><span lang="EN-US">Snapshot Policy Create</span></b><span lang="EN-US"> parameters:</span><br /> <br /><span style="font-family: "Courier New";">cluster1::} snapshot policy create ?</span><br /><span style="font-family: "Courier New";">[ -vserver {vserver name} ]</span><br /><span style="font-family: "Courier New";"> </span><span style="font-family: "Courier New";">[-policy]
{snapshot policy}</span><br /><span style="font-family: "Courier New";"> </span><span style="font-family: "Courier New";">[-enabled]
{true|false}</span><br /><span style="font-family: "Courier New";">[ -comment {text} ]</span><br /><span style="font-family: "Courier New";"> </span><span style="font-family: "Courier New";">[-schedule1]
{text}</span><br /><span style="font-family: "Courier New";"> </span><span style="font-family: "Courier New";">[-count1]
{0..1023}</span><br /><span style="font-family: "Courier New";">[ -prefix1 {text} ]</span><br /><span style="font-family: "Courier New";">[ -snapmirror-label1 {text (size 0..31)} ]</span><br /><span style="font-family: "Courier New";">[ -retention-period1 {SEE BELOW} ]</span><br /><span style="font-family: "Courier New";">[ -schedule2 {text} ]</span><br /><span style="font-family: "Courier New";">[ -count2 {0..1023} ]</span><span style="font-family: "Courier New";"> </span><br /><span style="font-family: "Courier New";">[ -prefix2 {text} ]</span><span style="font-family: "Courier New";"> </span><br /><span style="font-family: "Courier New";">[ -snapmirror-label2 {text (size 0..31)} ]</span><span style="font-family: "Courier New";"> </span><br /><span style="font-family: "Courier New";">[ -retention-period2 {SEE BELOW} ]</span><br /><span style="font-family: "Courier New";">[ -schedule3 {text} ]</span><span style="font-family: "Courier New";"> </span><br /><span style="font-family: "Courier New";">[ -count3 {0..1023} ]</span><span style="font-family: "Courier New";"> </span><br /><span style="font-family: "Courier New";">[ -prefix3 {text} ]</span><span style="font-family: "Courier New";"> </span><br /><span style="font-family: "Courier New";">[ -retention-period3 {SEE BELOW} ]</span><br /><span style="font-family: "Courier New";">[ -snapmirror-label3 {text (size 0..31)} ]</span><span style="font-family: "Courier New";"> </span><br /><span style="font-family: "Courier New";">[ -schedule4 {text} ]</span><br /><span style="font-family: "Courier New";">[ -count4 {0..1023} ]</span><span style="font-family: "Courier New";"> </span><br /><span style="font-family: "Courier New";">[ -prefix4 {text} ]</span><span style="font-family: "Courier New";"> </span><br /><span style="font-family: "Courier New";">[ -retention-period4 {SEE BELOW} ]</span><br /><span style="font-family: "Courier New";">[ -snapmirror-label4 {text (size 0..31)} ]</span><span style="font-family: "Courier New";"> </span><br /><span style="font-family: "Courier New";">[ -schedule5 {text} ]</span><span style="font-family: "Courier New";"> </span><br /><span style="font-family: "Courier New";">[ -count5 {0..1023} ]</span><span style="font-family: "Courier New";"> </span><br /><span style="font-family: "Courier New";">[ -prefix5 {text} ]</span><span style="font-family: "Courier New";"> </span><br /><span style="font-family: "Courier New";">[ -retention-period5 {SEE BELOW} ]</span><br /><span style="font-family: "Courier New";">[ -snapmirror-label5 {text (size 0..31)} ]</span></p><p style="text-align: left;"><span style="font-family: Courier New;"><br /></span><span style="font-family: inherit;"><i>Note: Options for retention-period:</i></span></p><p style="text-align: left;"><span style="font-family: "Courier New";">{{integer} seconds|minutes|hours|days|months|years} |
infinite</span></p><p style="text-align: left;"> </p><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiehMVkKtG4-JaJXbcUogZszd6qglkleG1RogkyeUe61YAXOvRwe_Yz-bYS4s4wnC67-R-fkwMUMohVdUnw7csFiSWl2U5IM-blsOns3mBxRb_D-CG8vSGxA0yFBcEc3rej4Tzklplw3tSNb1SmUVr36E96b3nHl4pi_uvIkvXuwLqTst3lKU9uAKiv0nsx/s568/ONTAP%209%20-%20Continuous%20Innovation.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="493" data-original-width="568" height="174" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiehMVkKtG4-JaJXbcUogZszd6qglkleG1RogkyeUe61YAXOvRwe_Yz-bYS4s4wnC67-R-fkwMUMohVdUnw7csFiSWl2U5IM-blsOns3mBxRb_D-CG8vSGxA0yFBcEc3rej4Tzklplw3tSNb1SmUVr36E96b3nHl4pi_uvIkvXuwLqTst3lKU9uAKiv0nsx/w200-h174/ONTAP%209%20-%20Continuous%20Innovation.png" width="200" /></a></div><p></p>
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-4270346497183643494.post-81045767647273650642024-02-29T22:10:00.000-08:002024-02-29T22:10:15.879-08:00New Features in ONTAP 9.5 up to 9.14.1<p><span style="font-family: inherit;">This post comes from a reading of the ONTAP 9.14.1 release notes from here: <a href="https://docs.netapp.com/us-en/ontap/">ONTAP 9 Documentation
(netapp.com)</a> β looking for new features (mostly - not enhancements) and perhaps the odd enhancement that I was curious about. With highlights. Always good to try and keep up with the new features and enhancements in new versions of ONTAP.</span></p><p><i>Note: To get the full output of new features and enhancements, please check out the release notes. This post is a summary to highlight a few things that I thought important or of particular interest.</i></p><p style="text-align: left;"><b>ONTAP 9.14.1</b></p><p style="text-align: left;"></p><ul style="text-align: left;"><li>Data protection:</li><ul><li>Support for SCSI3 persistent reservations and Windows Failover Clustering with SnapMirror Business Continuity</li></ul><li>File access protocol:</li><ul><li>Support for NFSv4.1 session trunking.</li></ul><li>MetroCluster configuration:</li><ul><li>Support for multiple MetroCluster IP configurations on the same NVIDIA switches.</li><li>Support for an S3 object storage server on an SVM in a mirrored or unmirrored aggregate in MetroCluster IP and FC configurations.</li><li>Support for nondisruptive transitions of workloads and data from an existing MetroCluster FC configuration to a new MetroCluster IP configuration using a shared switch.</li></ul><li>S3 object:</li><ul><li>Automatic resizing enabled on new and existing S3 FlexGroup volumes.</li></ul><li>Storage efficiency:</li><ul><li>Support for scan tracking in File System Analytics</li></ul><li>Storage resource management:</li><ul><li>Support for proactively rebalancing FlexGroups by non-disruptively moving growing files within a directory toremote constituents.</li><li>Support for writing directly to the cloud with FabricPool.</li></ul><li>SVM:</li><ul><li>Support for migrating SVMs containing user and group quotas and qtrees with SVM data mobility.</li><li>Support for a maximum of 400 volumes per SVM, a maximum of 12 HA pairs, and pNFS with NFS 4.1 using SVM data mobility.</li></ul></ul><br /><b>ONTAP 9.13.1</b><br /><ul style="text-align: left;"><li>Data protection:</li><ul><li><span style="background-color: #fcff01;">Support for multi-admin verification</span>.</li><li>Support for NDMP restore with SnapMirror Synchronous</li></ul><li>File access protocol:</li><ul><li>Support for managing NFSv4.x storepool resources.</li></ul><li>MetroCluster configuration:</li><ul><li>Support for four-node MetroCluster IP configuration upgrades using switchover and switchback.</li></ul><li>S3 object storage:</li><ul><li>Support for S3 bucket lifecycle management.</li></ul><li>Security:</li><ul><li>Multifactor authentication with time-based one-time password.</li><li>Support for automatic transition from learning to active mode with Autonomous Ransomware Protection</li></ul><li>Storage resource management:</li><ul><li>Support for SVM DR fanout relationships with FlexGroup volumes.</li><li>Support for SVM-wide throughput floor enhancement.</li></ul><li>Upgrade:</li><ul><li>Support for upgrading ONTAP and firmware from BlueXP.</li></ul></ul><br /><b>ONTAP 9.12.1</b><br /><ul style="text-align: left;"><li>Data protection:</li><ul><li>SnapMirror Synchronous NDO</li><li>SnapMirror Business Continuity (SM-BC) support</li><li>Data warehouse rebuild indicator for SnapMirror synchronous</li><li><span style="background-color: #fcff01;">Tamper-proof Snapshot copies</span></li></ul><li>File access protocol:</li><ul><li><span style="background-color: #fcff01;">S3 client access to NAS data</span></li></ul><li>MetroCluster configuration:</li><ul><li>MetroCluster automatic forced switchover feature in a MetroCluster IP configuration</li><li>S3 on an SVM on an unmirrored aggregate in a MetroCuster IP configuration.</li></ul><li>Storage resource management:</li><ul><li>FlexGroup rebalancing support</li></ul><li>System Manager:</li><ul><li>Hardware visualization of cabling.</li></ul></ul><br /><b>ONTAP 9.11.1</b><br /><ul style="text-align: left;"><li>Data Protection:</li><ul><li>SVM-DR support in MetroCluster configuration</li></ul><li>SAN:</li><ul><li>iSCSI LIF failover</li><li>Non-destructive migration from LUN toNVMe namespace and vice versa.</li></ul><li>Security:</li><ul><li>Autonomous Ransomware protection enhancement todetect additional malware threats.</li><li>Multi-admin verification support.</li></ul><li>Storage Efficiency:</li><ul><li>View physical footprint savings.</li></ul><li>Storage resource management:</li><ul><li>Enable file access time updates.</li><li>File System Analytics: Activity Tracking at SVM level.</li></ul><li>SVM:</li><ul><li><span style="background-color: #fcff01;">SVM data mobility support</span></li></ul></ul><br /><b>ONTAP 9.10.1</b><br /><ul style="text-align: left;"><li>Data Protection:</li><ul><li><span style="background-color: #fcff01;">Consistency groups</span> support</li><li>Public cloud data archiving of backups</li><li>Ability to create <span style="background-color: #fcff01;">SnapLock and non-SnapLock volumes on the same aggregate</span>.</li></ul><li>MetroCluster configuration:</li><ul><li>Configuration of layer 3 MetroCluster IP address in MetroCluster IP configurations.</li></ul><li>Networking and security protocol:</li><ul><li>Automatic detection and repair recommendations for network wiring issues.</li></ul><li>S3 object sorage:</li><ul><li><span style="background-color: #fcff01;">S3 SnapMirror backup and disaster recovery protection</span>.</li><li>S3 audit functionality.</li></ul><li>Security:</li><ul><li><span style="background-color: #fcff01;">Autonomous Ransomware protection support</span> that alerts about abnormal activity that might indicate a ransomware attach.</li></ul><li>Storage resource management:</li><ul><li><span style="background-color: #fcff01;">Activity tracking for hot objects with File System Analytics (FSA)</span></li><li>Global file read locking.</li></ul><li>SVM:</li><ul><li>Ability to non-disruptively move SVMs between clusters.</li></ul><li>System Manager:</li><ul><li><span style="background-color: #fcff01;">Simplified licensing with NetApp License Files (NLFs)</span></li><li>Update firmware automatically using System Manager.</li><li>View historical use of capacity and predict future capacity needs using System Manager.</li><li>Back up data to StorageGRID using the Cloud Backup Service</li></ul></ul><br /><b>ONTAP 9.9.1</b><br /><ul style="text-align: left;"><li>Data Protection:</li><ul><li>Support for configuring different Snapshot policies on SVM DR source and destination.</li></ul><li>File access protocol:</li><ul><li>Mandatory Access Control (MAC) labelled NFS is supported when NFSv4.2 is enabled.</li></ul><li>MetroCluster configuration:</li><ul><li>MetroCluster IP support for IP-routed (layer 3) backend connections</li><li>MetroCluster IP support for 8-node configurations</li></ul><li>S3 Object storage:</li><ul><li>S3 metadata and tags support</li></ul><li>SAN:</li><ul><li>Foreign LUN import using IMT.</li><li>Support for 12-node clusters on ASAs</li><li>NVMe-oF protocol on ASASs</li><li>Support for 8-node MCC-IP on ASAs</li></ul><li>Storage resource management:</li><ul><li>SnapMirror cascade and fanout support for FlexGroup volumes</li><li>SVM DR support for FlexGroup volumes</li></ul><li>System manager:</li><ul><li>Ansible Playbooks support with System Manager</li><li>Hardware Visualization support in System Manager</li><li>Active IQ integration in System Manager</li><li>Cloud Manager integration in System Manager</li></ul></ul><br /><b>ONTAP 9.8</b><br /><ul style="text-align: left;"><li>Data protection:</li><ul><li>NVE support for root volume encryption to protect root volume.</li><li>Support for moving a SnapLock volume to a destination aggregate of the same type.</li><li><span style="background-color: #fcff01;">SnapMirror Cloud</span> using qualified vendor applications.</li></ul><li>File access protocol:</li><ul><li>Encryption support between ONTAP and domain controllers</li><li>Improved NFSv4.1 performance with nconnect support</li><li>Support for NFSv4.2</li></ul><li>MetroCluster configuration:</li><ul><li><span style="background-color: #fcff01;">Unmirrored aggregates</span></li></ul><li>Networking and security protocol:</li><ul><li>Switch CLI simplification.</li></ul><li>SAN:</li><ul><li><span style="background-color: #fcff01;">SnapMirror Business Continuity (SMBC)</span> is a new business continuity solution available in public preview.</li><li>NVMe protocol co-existence</li></ul><li>Storage efficiency enhancements:</li><ul><li><span style="background-color: #fcff01;">Temperature sensitive storage efficiency</span></li></ul><li>Storage resource management:</li><ul><li><span style="background-color: #fcff01;">ONTAP File System Analytics</span> for FlexGroup and FlexVol volumes</li><li>Fast Directory Delete</li><li><span style="background-color: #fcff01;">Tiering to ONTAP S3 object storage</span></li><li>Promotion of data to the performance tier</li><li>FabricPool tiering from HDD</li><li>QoS support for Qtrees</li><li>QoS support for SVM administrator</li></ul><li>System Manager:</li><ul><li>Term βquiesceβ has been changed to βpauseβ in System Manager</li><li>View active NFS clients with System Manager</li></ul><li>Upgrade:</li><ul><li>MAINT Start/Stop AutoSupport message for ANDU</li><li>Upgrade both cluster in a MetroCluster configuration</li></ul></ul><br /><b>ONTAP 9.7</b><br /><ul style="text-align: left;"><li>File access protocol:</li><ul><li>Keytab files for SVM authentication with Active Directory (AD) servers</li></ul><li>MetroCluster configuration:</li><ul><li>ONTAP Mediator is supported in MetroCluster IP configurations.</li><li>FabricPool mirrors on MetroCluster configurations</li></ul><li>Networking and security protocol:</li><ul><li>Automatic portmap service support</li></ul><li>S3 object storage:</li><ul><li><span style="background-color: #fcff01;">S3 object storage support</span></li></ul><li>SAN:</li><ul><li>Symmetric Active-Active host access</li></ul><li>Storage resource management:</li><ul><li>QoS floors</li><li><span style="background-color: #fcff01;">FabricPool mirror</span></li></ul><li>Upgrade:</li><ul><li>Upgrade from ONTAP 9.3 directly to 9.7</li></ul></ul><br /><b>ONTAP 9.6</b><br /><ul style="text-align: left;"><li>API changes in ONTAP 9 releases:</li><ul><li><span style="background-color: #fcff01;">Support for an ONTAP REST API</span></li></ul><li>Data protection:</li><ul><li><span style="background-color: #fcff01;">SnapLock volume</span></li><li>Key management at the SVM scope</li><li><span style="background-color: #fcff01;">NetApp Aggregate Encryption</span></li></ul><li>MetroCluster configuration:</li><ul><li>Private layer 2 network sharing</li></ul><li>Networking and security protocol:</li><ul><li>LIF service policies replace LIF roles</li></ul></ul><br /><b>ONTAP 9.5</b><br /><ul style="text-align: left;"><li>Data protection:</li><ul><li><span style="background-color: #fcff01;">SnapMirror synchronous</span> technology</li></ul><li>Networking and security protocol:</li><ul><li>Virtual IP (VIP) LIFs and border gateway protocol (BGP) support</li></ul><li>Storage resource management:</li><ul><li>Logical space enforcement for FlexVol volumes</li><li><span style="background-color: #fcff01;">FabricPool functionality</span></li><li><span style="background-color: #fcff01;">FlexCache volumes support</span></li></ul></ul><p></p><p></p><div><br /></div><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjGe7MEztrjLXGaGE_HSAiw_q52RCDtTDSbODRlp326IUAE3CiaxAoch1oENguIIBiTCdkyClbeOY6LLuKMmInspcB1IzvGcSFZeB01tXLyq8_wUSuQswYOKJJ3gp0Fa5iFYQurq8BLGssfFSsN3F-UzU_uifoCNPe-me_mEfd7cLXHPHviilf8S2RRjsWY/s568/ONTAP%209%20-%20Continuous%20Innovation.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="493" data-original-width="568" height="174" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjGe7MEztrjLXGaGE_HSAiw_q52RCDtTDSbODRlp326IUAE3CiaxAoch1oENguIIBiTCdkyClbeOY6LLuKMmInspcB1IzvGcSFZeB01tXLyq8_wUSuQswYOKJJ3gp0Fa5iFYQurq8BLGssfFSsN3F-UzU_uifoCNPe-me_mEfd7cLXHPHviilf8S2RRjsWY/w200-h174/ONTAP%209%20-%20Continuous%20Innovation.png" width="200" /></a></div><br /><div><br /></div>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-4270346497183643494.post-46639530818545948702024-02-28T00:50:00.000-08:002024-02-28T00:50:42.673-08:00How You Should Rack Your SG6060<p>A random post from having done a few of these StorageGRID SG6060 installs. Based on having the minimal 4 storage nodes for a new StorageGRID deployment, this is the optimal way to rack your SG6060:</p><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg5v8az34n5BsYI5RhZTL-2RG5TFRE3QyPAJAPU8-iZPJgUo7zAXwfWo8SWUNcbt5a4_0O-Uxb2LN5KggETvvKVKXIs_ohMvIZwe-UXheZuW7eOA2bnJGTy0IGkTAgn_s-Bkz6xi1QM0fHAa4vzL6e3BJ9E2W9SebQd5EM25SZ-CvGPAGmSZi48aEuLIEGn/s715/Optimal%20Racking%20of%20SG6060.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="715" data-original-width="458" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg5v8az34n5BsYI5RhZTL-2RG5TFRE3QyPAJAPU8-iZPJgUo7zAXwfWo8SWUNcbt5a4_0O-Uxb2LN5KggETvvKVKXIs_ohMvIZwe-UXheZuW7eOA2bnJGTy0IGkTAgn_s-Bkz6xi1QM0fHAa4vzL6e3BJ9E2W9SebQd5EM25SZ-CvGPAGmSZi48aEuLIEGn/w256-h400/Optimal%20Racking%20of%20SG6060.png" width="256" /></a></div><p><br /></p><p>That is (from bottom to top): E2860, SG6000-CN, SG6000-CN, E2860 ... and repeat.</p><p>The 1U SG6000-CN (Compute controller) is a little shorter than the E2860 controller shelf, so if you rack E2860, SG6000-CN, E2860, SG6000-CN ... and repeat, then you only have 1U to do the cabling, which can be a bit fiddly (it is still perfectly fine though.)</p><p>Image for illustration from <a href="https://docs.netapp.com/us-en/storagegrid-117/installconfig/hardware-description-sg6000.html">https://docs.netapp.com/us-en/storagegrid-117/installconfig/hardware-description-sg6000.html</a>:</p><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh1EIDSPXtY9cdEHsBRH5n5MFpiDjBwU93jCfHJhJsNu3nLmXYJ7zE9OzirdM8AaK1B9vPpfXciEXVgiXwE9emB0RgMJsQGiJlSXME_9GUhDiwLXB3sQH5OWC5B08YrL3hyphenhyphentCirVGk7RQJd8O2xbq-RTukzp70OiQ3vIQxRmXCoAK3BLfc4M8wCBDIsuuSp/s847/SG6060%20rear%20view.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="550" data-original-width="847" height="260" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh1EIDSPXtY9cdEHsBRH5n5MFpiDjBwU93jCfHJhJsNu3nLmXYJ7zE9OzirdM8AaK1B9vPpfXciEXVgiXwE9emB0RgMJsQGiJlSXME_9GUhDiwLXB3sQH5OWC5B08YrL3hyphenhyphentCirVGk7RQJd8O2xbq-RTukzp70OiQ3vIQxRmXCoAK3BLfc4M8wCBDIsuuSp/w400-h260/SG6060%20rear%20view.png" width="400" /></a></div>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-4270346497183643494.post-32096956329359223522024-01-30T02:38:00.000-08:002024-01-30T02:38:57.365-08:00SG1000 and SG6060CN StorageGRID Appliance Installer Screenshots<p>I am a bit forgetful, so last time I did a StorageGRID install, I thought I'd do <u>some</u> screenshots to remind about some of the options in the StorageGRID Appliance Installer. These are running PGE 3.7 (for StorageGRID 11.7).</p><p><b><u><span style="font-size: large;">SG1000 StorageGRID Appliance Installer</span></u></b></p><p>This screenshot illustrate the available Node type options. These days we don't use "<b>Gateway</b>" much anymore. It's "<b>Primary Admin (with Load Balancer)</b>" if you don't yet have a Primary Admin node, otherwise it is "<b>Non-primary Admin (with Load Balancer)</b>".</p><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj-Iaj1oBtibMLkja1vS-O8o6-5osy0AIqPx5B33pM6uQAmIOi0vpmHICgdJcCSxt_3dfhqLtneuVr-K2xHLYDN4UFXfoOaciVimzbQWB05gvUROkj0BwpNBsEel_ZVoP0EWAYT-F50qXMQgQhZdUtE20sYBTPj-YflPANYFUM0NTkNDojvxbdS9v9l7Krh/s787/SG1000-1.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="711" data-original-width="787" height="361" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj-Iaj1oBtibMLkja1vS-O8o6-5osy0AIqPx5B33pM6uQAmIOi0vpmHICgdJcCSxt_3dfhqLtneuVr-K2xHLYDN4UFXfoOaciVimzbQWB05gvUROkj0BwpNBsEel_ZVoP0EWAYT-F50qXMQgQhZdUtE20sYBTPj-YflPANYFUM0NTkNDojvxbdS9v9l7Krh/w400-h361/SG1000-1.png" width="400" /></a></div><div><br /></div><div><b><u><span style="font-size: large;">SG6000CN StorageGRID Appliance Installer</span></u></b></div><div><br /></div><div><b><u>Home</u></b></div><div><br /></div><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhf8I51_zJg9wOAOIZ1ulXw15WO-PmfZOySoIkHT81sZLx1uc4b7qVx3CsGKNM3_ruPu0HebOOzqIBZod_mk3jdjcywSYD_liOwX4-mefCPBRZLvNdzS_o8GKEZrcDHjWPQT8xHVQguHzGskEMXa-fqTpcfHFtLGFkEjg9UyFicNOfxMkxs0zpDe-0LMrOy/s1002/SG6000CN-1.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="1002" data-original-width="823" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhf8I51_zJg9wOAOIZ1ulXw15WO-PmfZOySoIkHT81sZLx1uc4b7qVx3CsGKNM3_ruPu0HebOOzqIBZod_mk3jdjcywSYD_liOwX4-mefCPBRZLvNdzS_o8GKEZrcDHjWPQT8xHVQguHzGskEMXa-fqTpcfHFtLGFkEjg9UyFicNOfxMkxs0zpDe-0LMrOy/w329-h400/SG6000CN-1.png" width="329" /></a></div><div><br /></div><div><b><u>Configure Networking - Network Link Configuration</u></b></div><div><br /></div><div><i>Note: When you choose LACP (802.3ad) you can only specify one VLAN each for Grid and (optional) Client networks.</i></div><div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiaTkTs2Ov4JFwh2121YGklyEXDqIdhyphenhyphen7ZJco5nvm0a-ollj6bFzxLO9YyqlBWuW-yAgFTfnj4a0R2UTWSdXnjOw6XdezGP8-zJ_m9B_G5Q_OZNx9qXO5OgsVEQH5HwqYE4v0EKKBKuH6RDvW3WNrwkLApY_FYUa1nEBvKwk_6uy_IvX-xbdLidADDrYHd-/s970/SG6000CN-2.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="970" data-original-width="847" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiaTkTs2Ov4JFwh2121YGklyEXDqIdhyphenhyphen7ZJco5nvm0a-ollj6bFzxLO9YyqlBWuW-yAgFTfnj4a0R2UTWSdXnjOw6XdezGP8-zJ_m9B_G5Q_OZNx9qXO5OgsVEQH5HwqYE4v0EKKBKuH6RDvW3WNrwkLApY_FYUa1nEBvKwk_6uy_IvX-xbdLidADDrYHd-/w349-h400/SG6000CN-2.png" width="349" /></a></div><div><br /></div></div><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi-S-euLzzsUa61ScAbYRTh5I6HG9RT_JV_U4l6WVL1e35tlHH1MfEYtgefQlgUIS_tj_oXu8qmX5cxRlFifqwu-qHq2LptR-nejozl4atyg0NcJ14oEQu0hoaYfmD43jL7t2p16pD8a4K4f8JLah3L4775bSW8Sav7eqJDgXqO_84JZEZvO855jVrybd4F/s1081/SG6000CN-3.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="558" data-original-width="1081" height="206" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi-S-euLzzsUa61ScAbYRTh5I6HG9RT_JV_U4l6WVL1e35tlHH1MfEYtgefQlgUIS_tj_oXu8qmX5cxRlFifqwu-qHq2LptR-nejozl4atyg0NcJ14oEQu0hoaYfmD43jL7t2p16pD8a4K4f8JLah3L4775bSW8Sav7eqJDgXqO_84JZEZvO855jVrybd4F/w400-h206/SG6000CN-3.png" width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgnnLreIahCpReDvhGj9NjJrYHygAYwqb6LgxtC2lQ6hyphenhyphen0UyGxdkSWLZ3KNGWMlKybUs5dbN-H779GoUZTnibdjJFv2kdZOi-0Xq7DUQVxhbcMGPAATCE5PSCokwduEdlROmtf9unlHF390T_Tl8oKuRb_RciUoh1ozlUbOdclg4GE7rSBlB7WQYTA3V7L8/s1099/SG6000CN-4.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="523" data-original-width="1099" height="190" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgnnLreIahCpReDvhGj9NjJrYHygAYwqb6LgxtC2lQ6hyphenhyphen0UyGxdkSWLZ3KNGWMlKybUs5dbN-H779GoUZTnibdjJFv2kdZOi-0Xq7DUQVxhbcMGPAATCE5PSCokwduEdlROmtf9unlHF390T_Tl8oKuRb_RciUoh1ozlUbOdclg4GE7rSBlB7WQYTA3V7L8/w400-h190/SG6000CN-4.png" width="400" /></a></div>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-4270346497183643494.post-56805725395748752362024-01-29T07:49:00.000-08:002024-02-07T13:51:39.953-08:00ONTAP Cluster Switch: BES-53248 3.8.0.2 to 3.11.1.2 Upgrade<p>Some preparatory notes from BES-53248 upgrade from 3.8.0.2 to 3.11.1.2.</p><p>1) Check this page - <a href="https://mysupport.netapp.com/site/info/broadcom-cluster-switch">NetApp Support Site - BES-53248 EFOS Software Download</a> - and the switch compatibility matrix to verify your EFOS and RCF file versions.</p><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgSVDtqn2G6hkr1QBEXs2dtZRamLMoS70poZeP-tAYmgInmQSmltmvdEGe-Z46SGGX9QcMM1DVK7pOs8AlQILEurc73yKL-wAEppRaDQsl-1tVa1pcqpXtV6D3TOhJHKeNztsviKQIv28N9KBL58FUaUFCb9__njS_myMLRSZ5b5fSdkME2QiWEVFcbUc2E/s1879/BES-53248%20EFOS%20Software%20Download.png" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="738" data-original-width="1879" height="158" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgSVDtqn2G6hkr1QBEXs2dtZRamLMoS70poZeP-tAYmgInmQSmltmvdEGe-Z46SGGX9QcMM1DVK7pOs8AlQILEurc73yKL-wAEppRaDQsl-1tVa1pcqpXtV6D3TOhJHKeNztsviKQIv28N9KBL58FUaUFCb9__njS_myMLRSZ5b5fSdkME2QiWEVFcbUc2E/w400-h158/BES-53248%20EFOS%20Software%20Download.png" width="400" /></a></div><div><br /></div><div>Currently, EFOS 3.11.1.2 and ClusterRCF_v1.10 are the recommended EFOS and RCF (Reference Configuration File) versions.</div><div><br /></div><div>2) Download the EFOS version and RCF.</div><div><br /></div>Download the RCF from here: <a href="https://mysupport.netapp.com/site/products/all/details/broadcom-cluster-switches/downloads-tab">https://mysupport.netapp.com/site/products/all/details/broadcom-cluster-switches/downloads-tab</a><div><br /></div><div>Download EFOS from here: <a href="https://www.broadcom.com/support/bes-switch">https://www.broadcom.com/support/bes-switch</a></div><div><br /></div><div><i>Note: You will need a HTTP server (other protocols allowed) which the switch can reach, to download the software and RCF files.</i></div><div><br /></div><div>3) Review the latest NetApp BES-53248 documentation:</div><div><br /></div><div><div><a href="https://docs.netapp.com/us-en/ontap-systems-switches/switch-bes-53248/upgrade-switch-overview.html">https://docs.netapp.com/us-en/ontap-systems-switches/switch-bes-53248/upgrade-switch-overview.html</a></div><div><a href="https://docs.netapp.com/us-en/ontap-systems-switches/switch-bes-53248/replace-upgrade.html">https://docs.netapp.com/us-en/ontap-systems-switches/switch-bes-53248/replace-upgrade.html</a></div><div><a href="https://docs.netapp.com/us-en/ontap-systems-switches/switch-bes-53248/configure-efos-software.html">https://docs.netapp.com/us-en/ontap-systems-switches/switch-bes-53248/configure-efos-software.html</a></div><div><a href="https://docs.netapp.com/us-en/ontap-systems-switches/switch-bes-53248/configure-install-rcf.html">https://docs.netapp.com/us-en/ontap-systems-switches/switch-bes-53248/configure-install-rcf.html</a></div></div><div><br /></div><div>It's also worth checking on kb.netapp.com if there are any KBs relating to the EFOS version you want to go to (as of writing there is nothing for 3.11.1.2.)</div><div><br /></div><div><b><u><span style="font-size: large;">Walkthrough</span></u></b></div><div><br /></div><div><i>Note 1: Using the above documentation and my previous post <a href="https://www.cosonok.com/2023/05/bes-53248-upgrade-from-3446-to-31003.html">BES-53248 Upgrade from 3.4.4.6 to 3.10.0.3 (cosonok.com)</a>.</i></div><div><i>Note 2: Assuming you're <u>not using the FIPS compliant version</u> and are not changing to a FIPS compliant version (which came out with EFOS 3.7.) That is "show fips status" says "Invalid input" and not "System running in FIPS mode."</i></div><div><i>Note 3: ONTAP version is 9.8 or greater.</i></div><div><br /></div><div><b>1) Prepare</b></div><div><br /></div><div><div><span style="font-family: courier;">CLU::> set adv</span></div><div><span style="font-family: courier;">CLU::*> cluster ping-cluster -node ANODENAME</span></div><div><span style="font-family: courier;">CLU::*> network device-discovery show</span></div><div><span style="font-family: courier;">CLU::*> system switch ethernet show</span></div><div><span style="font-family: courier;">CLU::*> network port show -ipspace Cluster</span></div><div><span style="font-family: courier;">CLU::*> network interface show -vserver Cluster</span></div><div><span style="font-family: courier;">CLU::*> cluster show</span></div><div><span style="font-family: courier;">CLU::*> system node autosupport invoke -node \* -type all -message MAINT=4h</span></div><div><br /></div><div><b>2) Install the EFOS software</b></div><div><br /></div><div>See: <a href="https://docs.netapp.com/us-en/ontap-systems-switches/switch-bes-53248/configure-efos-software.html">https://docs.netapp.com/us-en/ontap-systems-switches/switch-bes-53248/configure-efos-software.html</a></div><div><br /></div><div>Firstly on switch 2:</div><div><br /></div><div><span style="font-family: courier;">CS2# ping HTTP_SERVER_IP</span></div><div><span style="font-family: courier;">CS2# show bootvar</span></div><div><span style="font-family: courier;">CS2# show version</span></div><div><span style="font-family: courier;">CS2# copy http://HTTP_SERVER_IP/EFOS-3.11.1.2.stk active</span></div><div><span style="font-family: courier;">CS2# show bootvar</span></div><div><span style="font-family: courier;">CS2# write mem</span></div><div><span style="font-family: courier;">CS2# reload</span></div><div><span style="font-family: courier;">CS2# show version</span></div><div><br /></div><div>Verify cluster ports are healthy (LIFs should have returned home):</div><div><br /></div><div><span style="font-family: courier;">CLU::*> network port show -ipspace Cluster</span></div><div><span style="font-family: courier;">CLU::*> network interface show -vserver Cluster</span></div><div><span style="font-family: courier;">CLU::*> cluster show</span></div><div><br /></div><div>Then repeat on switch 1:</div><div><br /></div><div><span style="font-family: courier;">CS1# ping HTTP_SERVER_IP</span></div><div><span style="font-family: courier;">CS1# show bootvar</span></div><div><span style="font-family: courier;">CS1# show version</span></div><div><span style="font-family: courier;">CS1# copy http://HTTP_SERVER_IP/EFOS-3.11.1.2.stk active</span></div><div><span style="font-family: courier;">CS1# show bootvar</span></div><div><span style="font-family: courier;">CS1# write mem</span></div><div><span style="font-family: courier;">CS1# reload</span></div><div><span style="font-family: courier;">CS1# show version</span></div><div><br /></div><div>Verify cluster ports are healthy (LIFs should have returned home):</div><div><br /></div><div><span style="font-family: courier;">CLU::*> network port show -ipspace Cluster</span></div><div><span style="font-family: courier;">CLU::*> network interface show -vserver Cluster</span></div><div><span style="font-family: courier;">CLU::*> cluster show</span></div><div><br /></div><div><b>3) Install the RCF</b></div><div><br /></div><div>See: <a href="https://docs.netapp.com/us-en/ontap-systems-switches/switch-bes-53248/configure-install-rcf.html">https://docs.netapp.com/us-en/ontap-systems-switches/switch-bes-53248/configure-install-rcf.html</a></div><div><br /></div><div><span style="font-family: courier;">CLU::*> network interface modify -vserver Cluster -lif * -auto-revert false</span></div><div><br /></div><div>Firstly we do cluster switch 2.</div><div><br /></div><div><span style="font-family: courier;">CS2# config t</span></div><div><span style="font-family: courier;">CS2(Config)# interface 0/1-0/16</span></div><div><span style="font-family: courier;">CS2(Interface 0/1-0/16)# shutdown</span></div><div><span style="font-family: courier;">CS2(Interface 0/1-0/16)# exit</span></div><div><span style="font-family: courier;">CS2(Config)# exit</span></div><div><span style="font-family: courier;"><br /></span></div><div><span style="font-family: courier;">CLU::*> network interface show -vserver Cluster</span></div><div><span style="font-family: courier;">CLU::*> cluster show</span></div><div><span style="font-family: courier;"><br /></span></div><div><span style="font-family: courier;">CS2# show running-config</span></div><div><br /></div><div>Then to remove the previous configuration (could use the previous "clear config" method if have onsite console access): Copy and paste the following commands to remove the previous RCF configuration (depending on the previous RCF version used, some commands might generate an error if a particular setting is not present):</div><div><br /></div><div><span style="color: red;"><i>NOTE: This procedure did not work for me. Since I was on site I was able to use the "clear config" method instead. I have escalated to NetApp.</i></span></div><div><br /></div><div><span style="font-family: courier;">clear config interface 0/1-0/56</span></div><div><span style="font-family: courier;">y</span></div><div><span style="font-family: courier;">clear config interface lag 1</span></div><div><span style="font-family: courier;">y</span></div><div><span style="font-family: courier;">configure</span></div><div><span style="font-family: courier;">deleteport 1/1 all</span></div><div><span style="font-family: courier;">no policy-map CLUSTER</span></div><div><span style="font-family: courier;">no policy-map WRED_25G</span></div><div><span style="font-family: courier;">no policy-map WRED_100G</span></div><div><span style="font-family: courier;">no class-map CLUSTER</span></div><div><span style="font-family: courier;">no class-map HA</span></div><div><span style="font-family: courier;">no class-map RDMA</span></div><div><span style="font-family: courier;">no classofservice dot1p-mapping</span></div><div><span style="font-family: courier;">no random-detect queue-parms 0</span></div><div><span style="font-family: courier;">no random-detect queue-parms 1</span></div><div><span style="font-family: courier;">no random-detect queue-parms 2</span></div><div><span style="font-family: courier;">no random-detect queue-parms 3</span></div><div><span style="font-family: courier;">no random-detect queue-parms 4</span></div><div><span style="font-family: courier;">no random-detect queue-parms 5</span></div><div><span style="font-family: courier;">no random-detect queue-parms 6</span></div><div><span style="font-family: courier;">no random-detect queue-parms 7</span></div><div><span style="font-family: courier;">no cos-queue min-bandwidth</span></div><div><span style="font-family: courier;">no cos-queue random-detect 0</span></div><div><span style="font-family: courier;">no cos-queue random-detect 1</span></div><div><span style="font-family: courier;">no cos-queue random-detect 2</span></div><div><span style="font-family: courier;">no cos-queue random-detect 3</span></div><div><span style="font-family: courier;">no cos-queue random-detect 4</span></div><div><span style="font-family: courier;">no cos-queue random-detect 5</span></div><div><span style="font-family: courier;">no cos-queue random-detect 6</span></div><div><span style="font-family: courier;">no cos-queue random-detect 7</span></div><div><span style="font-family: courier;">exit</span></div><div><span style="font-family: courier;">vlan database</span></div><div><span style="font-family: courier;">no vlan 17</span></div><div><span style="font-family: courier;">no vlan 18</span></div><div><span style="font-family: courier;">exit</span></div><div><br /></div><div><span style="font-family: courier;">CS2# write memory</span></div><div><span style="font-family: courier;">CS2# reload</span></div><div><br /></div><div>Note: If additional port licenses have been installed on the switch, you must modify the RCF to configure the additional licensed ports. See Activate newly licensed ports for details.</div><div><br /></div><div><span style="font-family: courier;">CS2# copy http://HTTP_SERVER_IP/BES-53248-RCF-v1.10-Cluster-HA.txt nvram:script BES-53248-RCF-v1.10-Cluster-HA.scr</span></div><div><span style="font-family: courier;">CS2# script list</span></div><div><span style="font-family: courier;">CS2# script apply BES-53248-RCF-v1.10-Cluster-HA.scr</span></div><div><span style="font-family: courier;">CS2# show clibanner</span></div><div><span style="font-family: courier;">CS2# show port all | exclude Detach</span></div><div><span style="font-family: courier;">CS2# show running-config</span></div><div><span style="font-family: courier;">CS2# write memory</span></div><div><span style="font-family: courier;">CS2# reload</span></div><div><span style="font-family: courier;"><br /></span></div><div><span style="font-family: courier;">CS2# config t</span></div><div><span style="font-family: courier;">CS2(Config)# interface 0/1-0/16</span></div><div><span style="font-family: courier;">CS2(Interface 0/1-0/16)# no shutdown</span></div><div><span style="font-family: courier;">CS2(Interface 0/1-0/16)# exit</span></div><div><span style="font-family: courier;">CS2(Config)# exit</span></div><div><span style="font-family: courier;"><br /></span></div><div><span style="font-family: courier;">CLU::*> network port show -ipspace Cluster</span></div><div><span style="font-family: courier;">CLU::*> network interface show -vserver Cluster</span></div><div><span style="font-family: courier;">CLU::*> cluster show</span></div><div><br /></div><div>The repeat the above for cluster switch 1.</div><div><br /></div><div>Once switch 2 and switch 1 are complete.</div><div><br /></div><div><span style="font-family: courier;">CLU::*> system switch ethernet show</span></div><div><span style="font-family: courier;">CLU::*> network interface modify -vserver Cluster -lif * -auto-revert true</span></div><div><br /></div><div>Finally, verify all is good:</div><div><br /></div><div><span style="font-family: courier;">CSW# show interfaces status all | exclude Detach</span></div><div><span style="font-family: courier;">CSW# show port-channel 1/1</span></div><div><span style="font-family: courier;"><br /></span></div><div><span style="font-family: courier;">CLU::*> network port show -ipspace Cluster</span></div><div><span style="font-family: courier;">CLU::*> network interface show -vserver Cluster</span></div><div><span style="font-family: courier;">CLU::*> cluster show</span></div><div><span style="font-family: courier;">CLU::*> system node autosupport invoke -node * -type all -message MAINT=END</span></div></div><div><br /></div>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-4270346497183643494.post-19368799962750391382024-01-27T08:12:00.000-08:002024-01-27T08:12:45.476-08:00ONTAP Design and Implementation: Documentation Headings<p><i>** This is intended to be continual work in-progress! **</i></p><p><i>I'm often writing NetApp ONTAP Design and Implementation / Low-Level-Design documentation. The following post lists out common documentation headings. The headings and sub-headings are partly based on NetAppDocs outputs (which are very useful post implementation to capture the "as-built" configuration.)</i></p><p>TABLE OF CONTENTS</p><p></p><ul style="text-align: left;"><li>Overview</li><li>General Information</li><ul><li>Hardware</li><li>Software</li></ul><li>Rack Elevation / Configuration Diagrams</li><li>Networking Requirements</li><li>Cluster Base Build Information</li><ul><li>Cluster & Node Naming</li><li>Cluster & Node IP Configuration</li><li>AutoSupport Configuration</li></ul><li>Storage Layout</li><ul><li>Aggregates</li><li>Aggregate Encryption (NAE)</li><li>Fabric Pool Configuration</li></ul><li>Network Configuration (Physical/Cluster)</li><ul><li>IFGRPs</li><li>VLANs</li><li>Network IPspaces</li><li>Network Port Broadcast Domains</li><li>Intercluster LIFs</li></ul><li>SVM Configuration</li><ul><li>Storage Virtual Machines (SVMs)</li><li>SVM Host-Name Resolution</li><li>SVM Name Services</li><li>Logical Interfaces (LIFs)</li><li>Network Routes</li><li>Protocol Configuration (NAS)</li><li>Protocol Configuration (SAN)</li></ul><li>SVM Storage Configuration</li><ul><li>Volumes (FlexVols)</li><li>FlexGroups</li><li>Qtrees</li><li>LUNs</li></ul><li>Storage Efficiency And Space Management</li><ul><li>Storage Efficiency</li><li>Space Management</li></ul><li>Job Schedules and Policies</li><ul><li>Job Schedules</li><li>Policies</li></ul><li>Storage QoS</li><ul><li>Policy Groups</li><li>Workloads</li></ul><li>Data Protection</li><ul><li>Cluster Peer Relationships</li><li>SVM Peer Relationships</li><li>SnapMirror</li><li>SVM Disaster Recovery</li><li>NDMP</li></ul><li><i>Appendices</i></li><ul><li><i>References</i></li></ul><li><i>Document Control</i></li><ul><li><i>Version Control</i></li><li><i>Contact Information</i></li></ul><li><i>Copyright, Confidentiality and Disclaimer</i></li></ul><div><br /></div><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEidQWS3XnxUkA94CvOEuC25j3ASTlzVxKSv19lJHQv2krlaX4dMknW7z55eKZQFQWShXxsVJzBf4ADEOgZSFGpj1JOkgVpgRdIqA1VxoiRlAzLu44_mOJ6clBHI2BCREkvWC5sKcN-QWWDBZxg_0TGje8pQik6lsHxVWJHI1VJq3aO8FV3DS2PZEH5w4SHs/s568/ONTAP%209%20-%20Continuous%20Innovation.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="493" data-original-width="568" height="174" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEidQWS3XnxUkA94CvOEuC25j3ASTlzVxKSv19lJHQv2krlaX4dMknW7z55eKZQFQWShXxsVJzBf4ADEOgZSFGpj1JOkgVpgRdIqA1VxoiRlAzLu44_mOJ6clBHI2BCREkvWC5sKcN-QWWDBZxg_0TGje8pQik6lsHxVWJHI1VJq3aO8FV3DS2PZEH5w4SHs/w200-h174/ONTAP%209%20-%20Continuous%20Innovation.png" width="200" /></a></div><p></p>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-4270346497183643494.post-38913185733682716752024-01-22T12:16:00.000-08:002024-01-22T12:16:01.859-08:00ONTAP: Naming Conventions<p style="text-align: left;">An ONTAP Naming Convention example.</p><p style="text-align: left;"><span style="font-family: courier;"> CLUSTER_NAME : {</span><b style="font-family: courier;">Loc</b><span style="font-family: courier;">ation}{</span><b style="font-family: courier;">Env</b><span style="font-family: courier;">ironment}{</span><b style="font-family: courier;">Typ</b><span style="font-family: courier;">e}-</span><b style="font-family: courier;">XXX</b><br /><span style="font-family: courier;"> NODE_NAME : {CLUSTER_NAME}-</span><b style="font-family: courier;">XX</b><br /><span style="font-family: courier;"> CLUSTER_SWITCH_NAME : {CLUSTER_NAME}-SW</span><b style="font-family: courier;">X</b><br /><span style="font-family: courier;"> IFGRP_NAME : a0</span><b style="font-family: courier;">a/b/c/d/...</b><br /><span style="font-family: courier;"> CLUSTER_LIF_NAME : {NODE_NAME}_clus1/2</span><br /><span style="font-family: courier;"> CLUSTER_MGMT_LIF_NAME : </span><span style="font-family: courier;">{CLUSTER_NAME}_mgmt</span><br /><span style="font-family: courier;"> NODE_MGMT_LIF_NAME : {NODE_NAME}_mgmt</span><br /><span style="font-family: courier;"> INTERCLUSTER_LIF_NAME : </span><span style="font-family: courier;">{NODE_NAME}_icl</span><br /><span style="font-family: courier;"> AGGREGATE_NAME (root) : </span><span style="font-family: courier;">{NODE_NAME}_root</span><br /><span style="font-family: courier;"> AGGREGATE_NAME (data) : </span><span style="font-family: courier;">{NODE_NAME}_{SSD/HDD}_aggr<b>X</b></span><br /><span style="font-family: courier;"> SVM_NAME : {</span><b style="font-family: courier;">AppLevel1</b><span style="font-family: courier;">}-</span><b style="font-family: courier;">XXX</b><br /><span style="font-family: courier;"> NAS_LIF_NAME : NAS/CIFS/NFS_n</span><b style="font-family: courier;">X</b><br /><span style="font-family: courier;"> SAN_LIF_NAME : FCP/iSCSI_</span><span style="font-family: courier;">n</span><b style="font-family: courier;">X_</b><span style="font-family: courier;">{</span><b style="font-family: courier;">port</b><span style="font-family: courier;">}</span><br /><span style="font-family: courier;"> SVM_MGMT_LIF_NAME : {SVM_NAME}_mgmt</span><br /><span style="font-family: courier;"> SVM_ROOTVOL_NAME : rootvol</span><br /><span style="font-family: courier;"> LS_MIRROR_NAME : rootvol_LS</span><br /><span style="font-family: courier;"> FLEXVOL_NAME : v_{</span><b style="font-family: courier;">AppLevel2</b><span style="font-family: courier;">}_</span><b style="font-family: courier;">XXX</b><br /><span style="font-family: courier;"> QTREE_NAME : q_{<b>AppLevel3</b></span><span style="font-family: courier;">}_<b>XXX</b></span><br /><span style="font-family: courier;"> LUN_NAME : l_</span><span style="font-family: courier;">{<b>AppLevel3</b></span><span style="font-family: courier;">}_<b>XXX</b></span><br /><span style="font-family: courier;"> INITIATOR_GROUP_NAME : i_{</span><b style="font-family: courier;">Host_Group</b><span style="font-family: courier;">}</span><br /><span style="font-family: courier;"> PORTSET_NAME : p_{</span><b style="font-family: courier;">Portset_Group</b><span style="font-family: courier;">}</span><br /><span style="font-family: courier;"> QoS_POLICY_GROUP_NAME : qos_{</span><b style="font-family: courier;">Service_offering</b><span style="font-family: courier;">}</span><br /><span style="font-family: courier;"> SCHEDULE_NAME : {...}</span><br /><span style="font-family: courier;"> SNAPSHOT_POLICY_NAME : {...}</span><br /><span style="font-family: courier;">SNAPMIRROR_POLICY__NAME : {...}</span></p><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgj_jDJ3U92rJFWX57Zahwo-sb1xnTQqW24htFmVSvEiigKqxOEDtl17xmCcx5n54T8nT7hkrQkYKI8ps_ZJqtqz_YVY2Qfd5WUoVfKOoaQYfW4WKxuIYA6ut1_6t-BdTK0h8MFgpLBfQaojslXEk_LruP5H9sJ0O_FlFgcue4JVC5UhNKDJ6ygTmqaWtj8/s568/ONTAP%209%20-%20Continuous%20Innovation.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="493" data-original-width="568" height="174" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgj_jDJ3U92rJFWX57Zahwo-sb1xnTQqW24htFmVSvEiigKqxOEDtl17xmCcx5n54T8nT7hkrQkYKI8ps_ZJqtqz_YVY2Qfd5WUoVfKOoaQYfW4WKxuIYA6ut1_6t-BdTK0h8MFgpLBfQaojslXEk_LruP5H9sJ0O_FlFgcue4JVC5UhNKDJ6ygTmqaWtj8/w200-h174/ONTAP%209%20-%20Continuous%20Innovation.png" width="200" /></a></div>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-4270346497183643494.post-70961106662536605442024-01-21T12:56:00.000-08:002024-01-21T12:56:11.136-08:00Load-Sharing Mirrors Best Practice<p><i>It is clear from:</i></p><p><a href="https://docs.netapp.com/us-en/ontap/data-protection/create-load-sharing-mirror-task.html"><i>Create and initializing load-sharing mirror relationships (netapp.com)</i></a></p><p><span style="font-size: large;">You should create a load-sharing mirror (LSM) for <span style="background-color: #fcff01;">each SVM root volume that serves NAS data</span> in the cluster. <span style="background-color: #fcff01;">For clusters consisting of two or more HA pairs</span>, you should consider load-sharing mirrors of SVM root volumes to ensure the namespace remains accessible to clients in the event that both nodes of an HA pair fail. <span style="background-color: #fcff01;">Load-sharing mirrors are not suitable for clusters consisting of a single HA pair.</span></span></p><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjgpxitWTJokawD30fXxPlALuO_r6xVnoW-R2ZF-Tri2edCHZK9U3LUKwoHRVdNcJmeiuCln8CzXQ2212tV5nUKbYCgSbh-4nBuap2O3EQvII4xmV6D5xRu9x-OcC0QHDXYMVE_vpwsW2Rnrh39Ao6sqvBaZrhcPygHIl5p4aW-_pjo36lqNmQeG8HcVT4_/s826/Load%20Sharing%20Mirror.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="765" data-original-width="826" height="370" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjgpxitWTJokawD30fXxPlALuO_r6xVnoW-R2ZF-Tri2edCHZK9U3LUKwoHRVdNcJmeiuCln8CzXQ2212tV5nUKbYCgSbh-4nBuap2O3EQvII4xmV6D5xRu9x-OcC0QHDXYMVE_vpwsW2Rnrh39Ao6sqvBaZrhcPygHIl5p4aW-_pjo36lqNmQeG8HcVT4_/w400-h370/Load%20Sharing%20Mirror.png" width="400" /></a></div>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-4270346497183643494.post-17003966315886206892024-01-20T14:22:00.000-08:002024-01-20T14:22:39.211-08:00Performing an ONTAP Health Check Analysis<p>Here are 5 health check / analysis / assessment tools for ONTAP:</p><p></p><ul style="text-align: left;"><li>ActiveIQ (web browser)</li><ul><li><a href="https://activeiq.netapp.com/">https://activeiq.netapp.com/</a></li></ul><li>Config Advisor (run either locally or over VPN to ActiveIQ)</li><li>NetApp Docs (run either locally or over VPN to ActiveIQ)</li><li>Using a script in ONTAP (run locally)</li><ul><li><a href="https://kb.netapp.com/onprem/ontap/os/How_to_perform_a_cluster_health_check_with_a_script_in_ONTAP">How to perform a cluster health check with a script in ONTAP - NetApp KB</a></li></ul><li>ActiveIQ Unified Manager (AIQUM) (run locally)</li></ul><div>For performance metrics analysis and monitoring:</div><ul style="text-align: left;"><li>NetApp Harvest (run locally)</li><ul><li>See: <a href="https://netapp.github.io/harvest">https://netapp.github.io/harvest</a></li></ul></ul><div>Other tools in the <a href="https://mysupport.netapp.com/site/tools">NetApp Toolchest</a> include:</div><div><ul style="text-align: left;"><li>ActiveIQ OneCollect</li><li>MetroCluster Data Collector (MCDC)</li><li>NFS cDOT Showmount tool</li><li>Performance and Statistics Collector (perfstat for Clustered Data ONTAP)</li><li>SnapGathers</li><li><a href="https://mysupport.netapp.com/site/bugs-online/syslog-translator">Syslog Translator</a></li></ul></div><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjKO92bnDPSCAmAESWY6LV52yslRmyLBYIZ_XcLJwkHrJJBs7jBjFI8YimIogouoWuOTTqd7sYj9pr4KramEaf-ZJasiixxz16Mbl-ynC3q1sh4zqJFwa6icSaKMVlyecS9w5W-DIMESCDFJcBKVV2Os1j28fGOlzrFm9XE1rYM8jHA33t4AFEmziZu7yLs/s568/ONTAP%209%20-%20Continuous%20Innovation.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="493" data-original-width="568" height="174" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjKO92bnDPSCAmAESWY6LV52yslRmyLBYIZ_XcLJwkHrJJBs7jBjFI8YimIogouoWuOTTqd7sYj9pr4KramEaf-ZJasiixxz16Mbl-ynC3q1sh4zqJFwa6icSaKMVlyecS9w5W-DIMESCDFJcBKVV2Os1j28fGOlzrFm9XE1rYM8jHA33t4AFEmziZu7yLs/w200-h174/ONTAP%209%20-%20Continuous%20Innovation.png" width="200" /></a></div><p><br /></p><i>Additional Notes:</i><p></p><p>The 3 main remote (via ActiveIQ) health checks:<br /></p><div><br /></div><div>1) ActiveIQ Storage Health sub-sections:</div><div><ul style="text-align: left;"><li><b>Dashboard</b></li><ul><li><i>Useful for risks and Keystone (if using)</i></li></ul><li>AutoSupport</li><li><b>Performance</b></li><ul><li><i>Especially interesting is node CPU utilization (also latency if not SSD)</i></li></ul><li>ClusterView</li><li>Sustainability (NEW) (available only at customer, watchlist, group or site level)</li><li><b>Capacity and Efficiency</b></li><ul><li><i>Worth looking at Node Aggregate space utilization. Also Storage Efficiency to see the Data Reduction levels being achieved.</i></li></ul><li>Keystone Advisor (BETA) (available only at a customer level)</li><li>Health Check</li><ul><li><i>Essentially a summary of the risks from the Dashboard.</i></li></ul><li>Health Assessment (a paid for service)</li><li>Cloud Recommendations</li><ul><li><i>Covers: Migration, Backup & Archive, Disaster Recovery, Tiering</i></li></ul><li>Valuable Insights</li></ul><div>2) Config Advisor</div></div><div><br /></div><div>3) NetAppDocs</div><div><br /></div><div>Commands to run in PowerShell></div><div><br /></div><div><span style="font-family: courier;">Import-Module NetAppDocs</span></div><div><span style="font-family: courier;"><br /></span></div><div><span style="font-family: courier;">$ClusterName = "CLUSTERNAME"</span></div><div><span style="font-family: courier;">$SerialOfNode = "SERIALNUMBER"</span></div><div><span style="font-family: courier;"><br /></span></div><div><span style="font-family: courier;">[String]$ClusterID = (Find-NtapAsupClusterId -ClusterName $ClusterName -NodeSerialNumber $SerialOfNode).cluster_identifier</span></div><div><span style="font-family: courier;"><br /></span></div><div><span style="font-family: courier;">Get-NtapClusterAsupData -Cluster ($ClusterName + ":" + $ClusterID) | Format-NtapClusterData | Out-NtapDocument -WordFile ("C:\Output\" + $ClusterName + ".Docx") -ExcelFile ("C:\Output\" + $ClusterName + ".xlsx")</span></div><div><br /></div><p></p>Unknownnoreply@blogger.com2tag:blogger.com,1999:blog-4270346497183643494.post-50361404572223835082024-01-15T01:25:00.000-08:002024-01-15T01:25:50.835-08:00Lots of vserverdr snapshots<p><span style="font-family: Aptos, sans-serif;">Apart from not
doing the snapmirror release -</span></p><p></p><p class="MsoNormal"><o:p></o:p></p>
<p class="MsoNormal"><a href="https://kb.netapp.com/onprem/ontap/dp/SnapMirror/Snapshot_copy_is_currently_used_as_a_reference_Snapshot_copy_by_one_or_more_SnapMirror_relationships">Snapshot
delete fails "Snapshot copy is currently used as a reference Snapshot copy
by one or more SnapMirror relationships" - NetApp Knowledge Base</a><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family: "Aptos",sans-serif;">- thereβs
another possible reason for lots of vserverdr snaps:</span><o:p></o:p></p>
<p class="MsoNormal"><a href="https://kb.netapp.com/onprem/ontap/dp/SnapMirror/SnapMirror_SVM_DR_snapshots_accumulate_due_to_invalid_owner_tag">SnapMirror
SVM DR snapshots accumulate due to invalid owner tag - NetApp Knowledge Base</a><o:p></o:p></p>
<p class="MsoNormal">VMware SRM test uses flexclone.<o:p></o:p></p>
<p class="MsoNormal">Once it is confirmed the snapshot is not used anywhere β
i.e. it is not the refence snapshot for vserverdr or snapmirror (vault)
relationships β then (from the kb above):<o:p></o:p></p>
<p class="MsoNormal" style="background: white; margin-left: 18.0pt;"><span style="color: black; font-family: "Lato",sans-serif; font-size: 12.0pt;">Manually
delete the oldest snapshot<br />
</span><span style="background: #F2F2F2; border: none windowtext 1.0pt; color: black; font-family: Courier; font-size: 10.0pt; mso-border-alt: none windowtext 0cm; padding: 0cm;">::> set advanced</span><span style="background: #F2F2F2; border: none windowtext 1.0pt; color: black; font-family: Courier; font-size: 12.0pt; mso-border-alt: none windowtext 0cm; padding: 0cm;"><br />
</span><span style="background: #F2F2F2; border: none windowtext 1.0pt; color: black; font-family: Courier; font-size: 10.0pt; mso-border-alt: none windowtext 0cm; padding: 0cm;">::*> volume snapshot delete -vserver xxx -volume xxx
-snapshot xxx </span><span style="background: yellow; border: none windowtext 1.0pt; color: black; font-family: Courier; font-size: 10.0pt; mso-border-alt: none windowtext 0cm; padding: 0cm;">-ignore-owners true -force true</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family: Aptos, sans-serif;">Whilst
aggregate space is not an issue, the snapshots are not doing any harm being there, so no
rush to tidy them up. From ONTAP 9.4 we allow 1023 snapshots per volume:</span></p><p class="MsoNormal"><o:p></o:p></p>
<p class="MsoNormal"><a href="https://kb.netapp.com/onprem/ontap/os/Maximum_number_of_snapshots_supported_by_ONTAP#:~:text=Beginning%20with%20ONTAP%209.4%2C%20a%20volume%20can%20contain,follows%3A%20255%20Snapshot%20copies%20of%20a%20FlexVol%20volume.">Maximum
number of snapshots supported by ONTAP - NetApp Knowledge Base</a><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family: Aptos, sans-serif;">There is a
quick way to delete lots of snapshots:</span></p><p class="MsoNormal"><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family: "Courier New";">set -confirmations
off</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family: "Courier New";">snapshot delete
{-vserver SVM1 -volume VOLUMENAME -snaphot PREFIX* -create-time <30d}</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family: "Courier New";">set -confirmations
on</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family: "Aptos",sans-serif;">That would
delete all snapshots older than 30 days for volume = VOLUMENAME and all
snapshots with PREFIX at the start. If you want to be prompted at every
snapshot delete, then donβt do the βset -confirmations offβ.</span></p><p class="MsoNormal"><span style="font-family: "Aptos",sans-serif;">Once snapshots are
deleted on the source, a resync will tidy them up on the destination.</span><o:p></o:p></p><p></p><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhoQ-QVMyJ9t0v_Efm63bRjPu4yIN8kCaPPCasSNjJ3nn2lmzbWTUp_C3ovF5hG5C4hrcpTeZR1D2vRzE4P6J-DEw97xd1niOetoQ7Ao-JT3WvtY3hX3QNyB2eUV0Ih1BCt-iRAt1tZL49c324uJEjRjDT8siXkp1R9KCKabKiWomHJ2D1lzKlp1k8liuJ8/s1024/SVMDR1.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="536" data-original-width="1024" height="210" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhoQ-QVMyJ9t0v_Efm63bRjPu4yIN8kCaPPCasSNjJ3nn2lmzbWTUp_C3ovF5hG5C4hrcpTeZR1D2vRzE4P6J-DEw97xd1niOetoQ7Ao-JT3WvtY3hX3QNyB2eUV0Ih1BCt-iRAt1tZL49c324uJEjRjDT8siXkp1R9KCKabKiWomHJ2D1lzKlp1k8liuJ8/w400-h210/SVMDR1.png" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><i><br /></i></div><div class="separator" style="clear: both; text-align: left;"><i>Additional reading:</i></div><div class="separator" style="clear: both; text-align: left;"><i><br /></i></div><div class="separator" style="clear: both; text-align: left;"><i>I actually forgot I did this post over 10 years ago now, but it is still relevant:</i></div><div class="separator" style="clear: both; text-align: left;"><i><br /></i></div><div class="separator" style="clear: both; text-align: left;"><a href="https://www.cosonok.com/2013/12/snapmirror-snaps-how-many-ok-to-delete.html"><i>SnapMirror Snaps - How Many? Ok to Delete? Resync on Other Snaps? & More β¦ (cosonok.com)</i></a></div>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-4270346497183643494.post-23475657100174589092023-12-09T04:48:00.000-08:002023-12-09T04:48:02.100-08:00Re-Initialize an MCIP with Less Shelves<p><i>Recently I had to re-initialize an IP MetroCluster. Reason being that the aggregate layout required a certain size of partitioned disks - partitioning across 2 shelves per site but I'd initialized it with 3 shelves attached, so the root partitions were not to the customers standard. Never mind, these things happen.</i></p><p><i>Note: In AFF IP MetroCluster you can have partitioning across 4 shelves (96 disks) because we mirror from site to site (still maximum of 48 disk per pool can be partitioned.)</i></p><p><b><u><span style="font-size: large;">Preparation Steps:</span></u></b></p><p>1) Make sure there is no data (no data SVMs) on both sides of the MetroCluster you are going to re-initialize.</p><p><span style="font-family: courier;">vserver show </span></p><p>2) Power off the entire MetroCluster as per:</p><p><a href="https://docs.netapp.com/us-en/ontap-metrocluster/maintain/task_power_off_an_entire_mcc_ip_configuration.html">Powering off an entire MetroCluster IP configuration</a></p><p>Essentially (taking precautions for encryption and tie breaker):</p><p><span style="font-family: courier;">system node halt -node * -inhibit-takeover true -ignore-quorum-warnings true</span></p><p><b><u><span style="font-size: large;">Re-Initialization Steps (going for 3 to 2 shelves):</span></u></b></p><p></p><ol style="text-align: left;"><li>Wait for all nodes to be at the ADP menu (option 9 at the boot menu)</li><li>Run 9a on all nodes</li><li>Return to main boot menu and go into maintenance mode</li><li>Check everything has been blown away (disk show - all disks should have been unassigned)</li><li>halt the nodes</li><li>disconnect 3rd shelf</li><li>boot to boot menu again</li><li>Run 9a and 9b on all nodes</li><li><i>[Optional] Disable disk auto assign and hot add the 3rd shelf if desired.</i></li></ol><div><i><br /></i></div><p></p><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhbP5awPah7k2ngIfl0LVGLNcvBBeAHB0UV3JHYLUI_hLdy_CrS_Q_rVjHO9ufPtKNKX0E1AQXCqSTcW3NIHIEz-vRhhwTO9wFNMoY8sax_XBiovAtbFpDl55yof_GUEFwXOPW-0ETz2x6anrbhEOiyQTgfLkf-CYwjXhSZB1U3ZW3qHBiKdagfFtCy4i2Q/s231/NetApp.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="231" data-original-width="200" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhbP5awPah7k2ngIfl0LVGLNcvBBeAHB0UV3JHYLUI_hLdy_CrS_Q_rVjHO9ufPtKNKX0E1AQXCqSTcW3NIHIEz-vRhhwTO9wFNMoY8sax_XBiovAtbFpDl55yof_GUEFwXOPW-0ETz2x6anrbhEOiyQTgfLkf-CYwjXhSZB1U3ZW3qHBiKdagfFtCy4i2Q/s16000/NetApp.png" /></a></div>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-4270346497183643494.post-48138726844217189842023-12-05T03:08:00.000-08:002024-01-06T04:08:52.579-08:00AFF A300 to A400 ARL Headswap: Lessons Learned<p><i>Two interesting things encountered whilst doing an AFF A300 to A400 ARL Headswap on 9.10.1P12.</i></p><p><i>I was using the official procedure (I have a cut down version that I print out and take with me to site - I'll have to share this at some point):</i></p><p></p><ul style="text-align: left;"><li><b><i>Manually upgrade controller hardware running ONTAP 9.8 or later</i></b></li><li><a href="https://docs.netapp.com/us-en/ontap-systems-upgrade/upgrade-arl-manual-app/index.html"><i>https://docs.netapp.com/us-en/ontap-systems-upgrade/upgrade-arl-manual-app/index.html</i></a></li></ul><p></p><p><b><u><span style="font-size: large;">Issue 1) Ports on the X1147A card did not come up</span></u></b></p><p>This had me scratching my head. I'd headswapped one node, so we had an A300 and A400 in the cluster, but could not get the temporary cluster connection (from onboard ports on the A300 to X1147A card in slot 1 on the A400) to come up. I tried a few things - different cables, different SFPs - but could not get the temporary cluster network link to come up. I contemplated needing to roll-back the headswap. Then I went and got a cup of tea, got on the wifi and found this in kb.netapp.com:</p><p></p><ul style="text-align: left;"><li><a href="https://kb.netapp.com/onprem/ontap/hardware/Port_on_the_expansion_card_X1147A_do_not_link_up">Port on the expansion card X1147A do not link up - NetApp Knowledge Base</a></li><li><a href="https://mysupport.netapp.com/site/bugs-online/product/ONTAP/BURT/1347483">NetApp Support Site - BURT - 1347483</a></li></ul><p></p><p>Running the "<b>system power cycle</b>" on the new A400 did the trick. And we were able to proceed.</p><p><i>Note: When I did this a second time (for second head swap) I had to get the default BMC credentials from NetApp. The usual BMC credentials did not work. There is an article on KB.NetApp.Com accessible internal only, entitled "What are the Default Passwords for Service Processors and BMCs?"</i></p><p><b><u><span style="font-size: large;">Issue 2) X1133A and X1135A ports are physically reversed</span></u></b></p><pre style="background-color: white; box-sizing: border-box; font-size: 13px; margin-bottom: 0px; margin-top: 0px; padding: 0px;"><ul style="text-align: left;"><li>A300: slot 2 OK: X1133A: Broadcom LPe16004 rev. A0</li><li>A400: slot 5 OK: X1135A: HBA,4-Port FCP Target 32Gb PCIe</li></ul></pre><p><span>I dutifully moved the fibre channel connections from e2a/b/c/d to e5a/b/c/d, or I thought I did, but I hadn't actually done that, I'd moved them to to e5d/c/b/a. The X1133A and X1135A ports are physically reversed even though the LC/LC cable tab is pointing downwards on both cards.</span></p><p><span>I'd been checking the output of -</span></p><p><span style="font-family: courier;">vserver fcp initiator show</span></p><p><span>- before downing the node 2 FC LIFs, but I wasn't seeing any initiators on node 1, so didn't want to down the node 2 FC LIFs as this would have caused an outage.</span></p><p><span>Once I'd corrected cabling, all was good :)</span></p><p><span><i>Image: X1133A and X1135A ports are reversed from left to right (2a/b/c/d on A300, 5d/c/b/a on A400):</i></span></p><p></p><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiaw12qvQuTGZdH5yukh9VvU2XP3ujlYQM0IeQm5MqYrt7fVvXWONjLcWQ_rRmoXJNBiPUBLk9ftLJFXMwlJEP-E8n9OiJ34LJKqzNCtFt5WFL9nZkn_4Qr7CSaZ73pOCwQEYE1IL0ShJJF_8SDcQTdoiS8sS-FP_eVh5eC8ODET8j8Glm7Z0BnhAAgZvUx/s694/A300%20X1133A%20and%20A400%20X1135A%20reversed.png" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="315" data-original-width="694" height="181" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiaw12qvQuTGZdH5yukh9VvU2XP3ujlYQM0IeQm5MqYrt7fVvXWONjLcWQ_rRmoXJNBiPUBLk9ftLJFXMwlJEP-E8n9OiJ34LJKqzNCtFt5WFL9nZkn_4Qr7CSaZ73pOCwQEYE1IL0ShJJF_8SDcQTdoiS8sS-FP_eVh5eC8ODET8j8Glm7Z0BnhAAgZvUx/w400-h181/A300%20X1133A%20and%20A400%20X1135A%20reversed.png" width="400" /></a></div><p></p>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-4270346497183643494.post-35423676448771939732023-12-04T08:21:00.000-08:002023-12-05T01:21:00.625-08:00E-Series: Lessons Learned Deploying E2812<p>Must have been a while since I deployed an E-Series as things have changed.</p><p>The default IPs (when DHCP has timed out) for the management ports used to be (/24 subnet mask):</p><p></p><ul style="text-align: left;"><li><b>192.168.128.101 / 102 </b>(Controller A / B Port 1)</li><li><b>192.168.129.101 / 102</b> (Controller A / B Port 2)</li></ul><p></p><p>But this is no longer the case. Now it is (/16 subnet mask):</p><p></p><ul style="text-align: left;"><li><b>169.254.128.101 / 102</b> (Controller A / B Port 1)</li><li><b>169.254.129.101 / 102</b> (Controller A / B Port 2)</li></ul><p></p><p>Anyway, I'd tried both sets of IPs and simply couldn't get a connection to the controller (turns out I probably didn't wait long enough - I have seen a 10 minute DHCP timeout mentioned.) So I used the serial to find out the IP address. The procedure is detailed here:</p><p><a href="https://kb.netapp.com/onprem/E-Series/Hardware/How_to_log_into_an_E-Series_controller_serially">How to log into an E-Series controller serially</a></p><div class="separator" style="clear: both; text-align: left;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiNEPOL4YUksGqLDIvC2EfkUdloCYtI-UjlGy2vrpEfTxOjf3Axqnip8mNZn-_HZ6D74az1y5YByfMiGW96XXgSDZ7uA3gx5iGeVKacUgpl82g3RF0SshSgtF-tbWBSNMgUwFy2caXmxI-6HrVThpmMOH79GaYs9rn1lSjdtDUt9H6j4XdsHsOHUtE2T8x1/s927/Default%20Baud%20Rate%20and%20Connection%20Type%20for%20E-Series%20Serial.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="288" data-original-width="927" height="124" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiNEPOL4YUksGqLDIvC2EfkUdloCYtI-UjlGy2vrpEfTxOjf3Axqnip8mNZn-_HZ6D74az1y5YByfMiGW96XXgSDZ7uA3gx5iGeVKacUgpl82g3RF0SshSgtF-tbWBSNMgUwFy2caXmxI-6HrVThpmMOH79GaYs9rn1lSjdtDUt9H6j4XdsHsOHUtE2T8x1/w400-h124/Default%20Baud%20Rate%20and%20Connection%20Type%20for%20E-Series%20Serial.png" width="400" /></a></div><div><br /></div><i>For 2812, Baud 115200 with micro-USB to USB cable.</i><div><br /></div><div>The shell passwords are listed here (I cannot share):</div><div><br /></div><div><a href="https://kb.netapp.com/onprem/E-Series/Hardware/What_are_the_E_Series_Controller_Shell_Passwords">What are the E-Series Controller Shell Passwords?</a></div><div><br /></div><div><i>(I can't remember which user name I used, but the username and password is in the above link.)</i><br /><p>Once I'd connected, the command to see what the IP address is:</p><p><span style="font-family: courier;">netCfgShow</span></p><p>This is detailed here:</p><p><a href="https://kb.netapp.com/onprem/E-Series/Management_Apps/Cannot_connect_the_default_IPs_of_E-series_controllers">Cannot connect the default IPs of E-series controllers</a></p></div>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-4270346497183643494.post-54676866270450836662023-12-04T01:55:00.000-08:002023-12-04T01:55:04.495-08:00NetApp IMT: ONTAP SAN Host Simplified<p>Something changed - <i>for the better</i> - with NetApp's Interoperability Matrix Tool (IMT) some 60 days ago. The IMT for SAN Host is now massively simplified.</p><p><b>ONTAP SAN Host Simplified:</b></p><div class="separator" style="clear: both; text-align: left;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg8FPBTH_KuRcf7hUDZDP23subwZ6uu9YgXxATjwrXskcgtC2rEmp6ZiZgWZJFZniXTWTxAj8UX7wyHu-hHTwzYAx4XgLanm3EM6HbjL7iBcQb4QC3dNqcWS3rhz3jSNnPV7MHF5lJurmca2K_WnTGW8WpDphqmEPQ4hVzsUrc3C4Q-McCvGuKaTJLRDyXh/s1399/ONTAP%20SAN%20Host%20Simplified.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="367" data-original-width="1399" height="105" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg8FPBTH_KuRcf7hUDZDP23subwZ6uu9YgXxATjwrXskcgtC2rEmp6ZiZgWZJFZniXTWTxAj8UX7wyHu-hHTwzYAx4XgLanm3EM6HbjL7iBcQb4QC3dNqcWS3rhz3jSNnPV7MHF5lJurmca2K_WnTGW8WpDphqmEPQ4hVzsUrc3C4Q-McCvGuKaTJLRDyXh/w400-h105/ONTAP%20SAN%20Host%20Simplified.png" width="400" /></a></div><div class="separator" style="clear: both; text-align: left;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><i>New simplified βONTAP SAN Hostβ solution will be only Host Interoperability support matrix for ONTAP SAN going forward.</i></div><div class="separator" style="clear: both;"><i><span style="background-color: #fcff01;">There are only 3 components (ONTAP OS, Host OS & Protocol)</span> listed in this new simplified solution compared to the 13 components in the previous solution. <span style="background-color: #fcff01;">Remaining 10 components would have blanket support from NetApp i.e. if those 10 component versions are actively supported by the respective vendors, then NetApp would also implicitly support them.</span></i></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Essentially, NetApp is no longer concerned about versions from other vendors as-long-as they are actively supported versions. This makes total sense to me π</div></div>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-4270346497183643494.post-40973141588037460072023-09-13T01:55:00.001-07:002023-12-21T09:06:44.564-08:00SVM-DR/SnapMirror for SVM Express Guide and Notes<p style="text-align: left;"><i>Continuing from the <a href="http://www.cosonok.com/2016/03/svm-drsnapmirror-for-svm-super-short.html">SVM-DR/SnapMirror for SVM Super (Short) Express Guide (8.3.1)</a> from 2016 (yes, really 7 years ago) a few more notes.</i></p><p style="text-align: left;"><br /><span style="font-family: courier;">##########################################<br />## SVM-DR EXPRESS (based on above link) ##<br />##########################################<br /><br />## Preparation ##<br /><br />BOTH::> cluster peer show<br />BOTH::> system license show<br />BOTH::> job schedule cron show # <span style="background-color: #fcff01;">IMPORTANT: Create the same custom schedules on the destination cluster!</span><br />BOTH::> storage aggregate show<br /><br />## Creating a destination SVM ##<br /><br />CLU2::> vserver create -vserver SVM1-DR -subtype dp-destination<br />CLU2::> vserver show -vserver SVM1-DR<br /><br />## Create the SVM peer relationship ##<br /><br />CLU2::> vserver peer create -vserver SVM1-DR -peer-vserver SVM1 -applications snapmirror -peer-cluster CLU1<br />CLU1::> vserver peer accept -vserver SVM1 -peer-vserver SVM1-DR<br />BOTH::> vserver peer show<br /><br />## Creating a SnapMirror Relationship ##<br /><br />CLU2::> snapmirror create -source-vserver SVM1 -destination-vserver SVM1-DR -policy MirrorAllSnapshots -schedule hourly -identity-preserve true<br />CLU2::> snapmirror show -destination-vserver SVM1-DR<br />CLU2::> snapmirror initialize -destination-vserver SVM1-DR<br />CLU2::> snapmirror show -destination-vserver SVM1-DR<br /><br />#######################<br />## CONVERT TO SVM-DR ##<br />#######################<br /><br /><a href="http://www.cosonok.com/2023/04/ontap-convert-to-svm-dr-research.html">http://www.cosonok.com/2023/04/ontap-convert-to-svm-dr-research.html</a></span></p><p style="text-align: left;"><span style="font-family: courier;">A page for research/notes/lessons-learned on converting a primary/DR SVM pair from volume snapmirror relationships to an SVM-DR (or SnapMirror for SVM) relationship.<br /><br />Key link from the ONTAP 9 documentation:<br />Convert volume replication relationships to an SVM replication relationship</span></p><p style="text-align: left;"><span style="font-family: courier;">Notes from the above:<br /></span></p><ul style="text-align: left;"><li><span style="font-family: courier;"><span style="font-family: courier;">Each volume (except SVM root) is being replicated</span></span></li><li><span style="font-family: courier;"><span style="font-family: courier;">Each volume on the source (including SVM root) has same name as on destination</span></span></li><ul><li><span style="font-family: courier;"><span style="font-family: courier;">use volume rename when SnapMirror is idle</span></span></li><li><span style="font-family: courier;"><span style="font-family: courier;">use snapmirror resync after rename</span></span></li></ul></ul><p></p><p style="text-align: left;"><span style="font-family: courier;">Create SVM replication as per: Replicate an entire SVM configuration<br />snapmirror create ... -identity-preserve true<br />Stop destination SVM: vserver stop -vserver SVMB<br />snapmirror resync -source-path SVMA: -destination-path SVMB: -type DP|XDP -schedule SCHEDULE -policy POLICY</span></p><p style="text-align: left;"><span style="font-family: courier;">Q&A<br /><br />Q: What does identity-preserve preserve?<br />A: See: About SnapMirror SVM replication #configurations-replicated-in-svm-dr-relationships<br /><br />Q: DP or XDP?<br />A: XDP (it is the default from ONTAP 9.4)<br /><br />Q: What policy options?<br />A: async-mirror (SnapMirror DR) or mirror-vault (Unified Replication)<br /><br />Q: Can you SVM-DR Flexgroups?<br />A: Yes, beginning ONTAP 9.9.1. See: Create an SVM disaster recovery relationship for FlexGroup volumes.<br /><br />Q: What about SnapMirror Business Continuity?<br />A: NetApp SnapMirror Business Continuity (SM-BC) is a continuously available storage. solution with application-level granularity Note: SnapMirror Business Continuity offers application-level granularity for SAN workloads only.<br /><br />Notes from #configurations-replicated-in-svm-dr-relationships:<br /><br />The key thing is that SVM-DR isn't super useful for SAN (still useful for replicating an entire SVM for DR purpose) as we see if we look at the things that are not replicated with -identity-preserve true (updated 11/11/2022):<br />Not replicated with -identity-preserve true:<br />Network: SAN LIFs, Broadcast domain, Subnet, IPspace<br />Root volume: User data, Qtrees, Quotas, File-level QoS, Attributes<br />Fibre Channel (FC): No<br />iSCSI: No<br />LUNs: igroups, portsets, Serial numbers<br /><br />####################<br />## SVM-DR CUTOVER ##<br />####################<br /><br /><a href="https://docs.netapp.com/us-en/ontap/data-protection/make-svm-destination-volumes-writeable-task.html">https://docs.netapp.com/us-en/ontap/data-protection/make-svm-destination-volumes-writeable-task.html</a><br /><br />If you set -identity-preserve true when you created the SVM replication relationship, stop the source SVM:<br />cluster_src::> <span style="background-color: #fcff01;">vserver stop svm1</span></span></p><p style="text-align: left;"><span style="font-family: courier;">cluster_dst::> snapmirror quiesce -source-path svm1: -destination-path svm_backup:<br />cluster_dst::> snapmirror abort -source-path svm1: -destination-path svm_backup:<br />cluster_dst::> <span style="background-color: #fcff01;">snapmirror break -source-path svm1: -destination-path svm_backup:</span><br /><br />cluster_dst::> <span style="background-color: #fcff01;">vserver start svm_backup</span><br /><br />Then:<br /><br />cluster_dst::> snapmirror delete -source-path svm1: -destination-path svm_backup:<br />cluster_src::> snapmirror release -source-path svm1: -destination-path svm_backup:<br /><br />#####################################################<br />## DISABLING CIFS SESSIONS BEFORE THE FINAL UPDATE ##<br />#####################################################<br /><br />If you're doing an SVM-DR cutover of a CIFS enabled SVM, you really want to have no CIFS sessions running before your final update.<br /><br /><a href="https://kb.netapp.com/onprem/ontap/da/NAS/How_to_terminate_CIFS_or_close_a_specific_session_for_a_volume_in_ONTAP">https://kb.netapp.com/onprem/ontap/da/NAS/How_to_terminate_CIFS_or_close_a_specific_session_for_a_volume_in_ONTAP</a><br /><br />Examples of what you can do in ONTAP 9:<br /><br />cluster_src::> <br /><br />vserver cifs session close -node NODE<br />vserver cifs session close βvserver VSERVER<br />vserver cifs session close βsession-is SESSION_ID<br />vserver cifs session close βconnection-id CONNECTION_ID<br />vserver cifs session close βlif-address INCOMING_LIF_IP<br />vserver cifs session close βauth-mechanism AUTH_MECHANISM<br />vserver cifs session close βwindows-user WIN_USER <br />vserver cifs session close βunix-user UNIX_USER<br />vserver cifs session close βprotocol-version PROTOCOL_VERSION<br />vserver cifs session close βcontinuously-available {CIFS Open File Protection}<br />vserver cifs session close βis-session-signed {true|false}</span></p><p style="text-align: left;"><span style="font-family: inherit;">Or you could just do it really quickly (update SnapMirror, stop source vserver, break) and no one will probably notice.</span></p><p style="text-align: left;"><span style="font-family: inherit;">You can also do SVM-DR cutovers in ONTAP System Manager.</span></p><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj__GL1moBgXrwFkoZRuBZBVjyuN8f6ZwhLJK2jmfPFTG7I95gZdd9bUm0yJdZaGLrvQTe_bz1StELmx0xu2uB2DTgfnLZffbVnSziF8n5Ojgg8jXOUajybzJVSfpDjWZoJRXX6vbREaP9weqXhzzyOFpnjRot9fdvoArX4OgiqbyVmR3ITWdoOtAzHIUjQ/s474/SVM-DR.jpg" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="236" data-original-width="474" height="199" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj__GL1moBgXrwFkoZRuBZBVjyuN8f6ZwhLJK2jmfPFTG7I95gZdd9bUm0yJdZaGLrvQTe_bz1StELmx0xu2uB2DTgfnLZffbVnSziF8n5Ojgg8jXOUajybzJVSfpDjWZoJRXX6vbREaP9weqXhzzyOFpnjRot9fdvoArX4OgiqbyVmR3ITWdoOtAzHIUjQ/w400-h199/SVM-DR.jpg" width="400" /></a></div><div class="separator" style="clear: both; text-align: left;"><br /></div><div class="separator" style="clear: both; text-align: left;"><b><u>Other Notes</u></b></div><div class="separator" style="clear: both; text-align: left;"><br /></div><div class="separator" style="clear: both; text-align: left;"><b>SVM DR can not create the second destination relationship</b></div><div class="separator" style="clear: both; text-align: left;"><a href="https://kb.netapp.com/onprem/ontap/dp/SnapMirror/SVM_DR_can_not_create_the_second_destination_relationship">https://kb.netapp.com/onprem/ontap/dp/SnapMirror/SVM_DR_can_not_create_the_second_destination_relationship</a></div><div class="separator" style="clear: both; text-align: left;"><i>Note: Starting with ONTAP 9.4 can fan-out to two destinations only. By default, only one -identity-preserve true relationship is allowed per source SVM.</i></div><div class="separator" style="clear: both; text-align: left;"><br /></div><div class="separator" style="clear: both; text-align: left;"><b>When attempting to create a fan-out of an SVM the process fails</b></div><div class="separator" style="clear: both; text-align: left;"><a href="https://kb.netapp.com/onprem/ontap/dp/SnapMirror/When_attempting_to_create_a_fan-out_of_an_SVM_the_process_fails">https://kb.netapp.com/onprem/ontap/dp/SnapMirror/When_attempting_to_create_a_fan-out_of_an_SVM_the_process_fails</a></div><div class="separator" style="clear: both; text-align: left;"><i><span style="color: red;">Note: You can create a duplicate SVM DR relationship with the -identity-preserve variable using the same settings while in diag mode <b>for the purpose of migration only!</b></span></i></div><div class="separator" style="clear: both; text-align: left;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><b>Change a misconfigured SVM DR -identity-preserve setting to either True or False</b></div><div class="separator" style="clear: both;"><a href="https://kb.netapp.com/onprem/ontap/dp/SnapMirror/Change_a_misconfigured_SVM_DR_-identity-preserve_setting_to_either_True_or_False">https://kb.netapp.com/onprem/ontap/dp/SnapMirror/Change_a_misconfigured_SVM_DR_-identity-preserve_setting_to_either_True_or_False</a></div><div class="separator" style="clear: both;"><i>Solution = Delete the destination SVM.</i></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><b>Can I use Fan-out to migrate an Identity preserve SVM-DR to a new Cluster?</b></div><div class="separator" style="clear: both;"><a href="https://kb.netapp.com/onprem/ontap/dp/SnapMirror/Can_I_use__Fan-out_to_migrate_an_Identity_preserve_SVM_DR_to_a_new_Cluster">https://kb.netapp.com/onprem/ontap/dp/SnapMirror/Can_I_use__Fan-out_to_migrate_an_Identity_preserve_SVM_DR_to_a_new_Cluster</a></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><b>Can I use SVM-DR in a cascade configuration?</b></div><div class="separator" style="clear: both;"><a href="https://kb.netapp.com/onprem/ontap/dp/SnapMirror/Can_I_use_SVM-DR_in_a_cascade_configuration">https://kb.netapp.com/onprem/ontap/dp/SnapMirror/Can_I_use_SVM-DR_in_a_cascade_configuration</a></div><div class="separator" style="clear: both;"><i>Answer = No! Volume SnapMirror relationships can be used to replicate SVMDR destination volumes in ONTAP 9.3 and later.</i></div></div><div class="separator" style="clear: both; text-align: left;"><br /></div>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-4270346497183643494.post-68990081335961456942023-09-04T12:46:00.000-07:002023-09-04T12:46:02.570-07:00ONTAP Tools for VMware 9.12 NFS v3 Export Rules<p>If you use ONTAP Tools for VMware 9.12 to provision a new NFS v3 datastore, it will create a rule per host like the below (where we have two ESXi hosts in the VMware Cluster we are provisioning into) in the default export policy:</p><p style="text-align: left;"><span style="font-family: courier;">cluster1::> export-policy rule show -vserver svm2 -instance</span><br /><span style="font-family: courier;"><br /></span><span style="font-family: courier;">Vserver: svm2</span><br /><span style="font-family: courier;">Policy Name: default</span><br /><span style="font-family: courier;">Rule Index: 1</span><br /><span style="font-family: courier;">Access Protocol: nfs</span><br /><span style="font-family: courier;">List of ...: 192.168.0.51</span><br /><span style="font-family: courier;">RO Access Rule: sys</span><br /><span style="font-family: courier;">RW Access Rule: sys</span><br /><span style="font-family: courier;">User ID To Which Anonymous Users Are Mapped: 65534</span><br /><span style="font-family: courier;">Superuser Security Types: sys</span><br /><span style="font-family: courier;">Honor SetUID Bits in SETATTR: true</span><br /><span style="font-family: courier;">Allow Creation of Devices: true</span><br /><span style="font-family: courier;"><br /></span><span style="font-family: courier;">Vserver: svm2</span><br /><span style="font-family: courier;">Policy Name: default</span><br /><span style="font-family: courier;">Rule Index: 2</span><br /><span style="font-family: courier;">Access Protocol: nfs</span><br /><span style="font-family: courier;">List of ...: 192.168.0.52</span><br /><span style="font-family: courier;">RO Access Rule: sys</span><br /><span style="font-family: courier;">RW Access Rule: sys</span><br /><span style="font-family: courier;">User ID To Which Anonymous Users Are Mapped: 65534</span><br /><span style="font-family: courier;">Superuser Security Types: sys</span><br /><span style="font-family: courier;">Honor SetUID Bits in SETATTR: true</span><br /><span style="font-family: courier;">Allow Creation of Devices: true</span></p><p>And the default export policy is applied the the SVM rootvol (by default) and the newly provisioned volumes.</p><p>To create the same rule in the CLI, the command is (in this case we create it for a subnet) (replace highlighted items as required):</p><p><span style="font-family: courier;">export-policy rule create -vserver <span style="background-color: #fcff01;">svm2</span> -policyname default -ruleindex <span style="background-color: #fcff01;">3</span> -protocol nfs -clientmatch <span style="background-color: #fcff01;">192.168.0.0/24</span> -rorule sys -rwrule sys -anon 65534 -superuser sys -allow-suid true -allow-dev true</span></p><p><i>Note: If all your ESXi hosts are in a private subnet, you don't need a rule per host, you can have a rule for that subnet as above.</i></p><table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto;"><tbody><tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiHm3zdGlVuy1GoUyWPCAJQxI6dZh1tdsOE2mpoOdI1qWjLglhosMeMBo5mLBIIKlXwccRtGdNNtUp4sOnQFy0AGNRH7NUaYNmDS7rSEsSn7_VKvQx5QSAp919PQcSnmlmpJ_GhPnm7YwWuYy-pSHHhahpusHK1Ux3QiY79RhYUG9HiNkSSB4kFFlD1Lu5x/s1188/OTV%20Created%20Rule.png" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" data-original-height="967" data-original-width="1188" height="325" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiHm3zdGlVuy1GoUyWPCAJQxI6dZh1tdsOE2mpoOdI1qWjLglhosMeMBo5mLBIIKlXwccRtGdNNtUp4sOnQFy0AGNRH7NUaYNmDS7rSEsSn7_VKvQx5QSAp919PQcSnmlmpJ_GhPnm7YwWuYy-pSHHhahpusHK1Ux3QiY79RhYUG9HiNkSSB4kFFlD1Lu5x/w400-h325/OTV%20Created%20Rule.png" width="400" /></a></td></tr><tr><td class="tr-caption" style="text-align: center;">Export Rule Create by OTV 9.12</td></tr></tbody></table>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-4270346497183643494.post-27106385163478257862023-08-23T01:09:00.008-07:002023-08-27T00:50:58.514-07:00New FabricPool configuration wizard in StorageGRID 11.7<p>A big up to this YouTube video:</p><div class="separator" style="clear: both; text-align: center;"><iframe allowfullscreen="" class="BLOG_video_class" height="266" src="https://www.youtube.com/embed/La8DEv_hXZw" width="320" youtube-src-id="La8DEv_hXZw"></iframe></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: center;"><a href="https://www.youtube.com/watch?v=La8DEv_hXZw">New FabricPool configuration wizard in StorageGRID 11.7 - YouTube</a></div><p>It takes you through all the steps to configure a standard best practice FabricPool setup with StorageGRID:</p><p></p><i><u><b>Before starting you might like to do (consideration for 11.6 too) if this is a new deployment:</b></u></i><br /><ul style="text-align: left;"><li><i>StorageGRID Hotfix / upgrade</i></li><li><i>Create a Storage Pool for your site</i></li><li><i>(11.6) Configuration > Grid Options > Stored Object Encryption (if desired)</i></li><li><i>(11.7) Configuration > Security settings > Network and objects > Stored Object Encryption (if desired)</i></li><li><i>Support > AutoSupport</i></li><ul><li><i>Also do for any E-Series storage arrays in SANtricity System Manager.</i></li></ul><li><i>(11.6) Create Tenant. Create Bucket (with Read-after-new-write (default) consistency). Create Access Key.</i></li></ul><div><b><u>The Wizard Walkthrough</u></b></div><p></p><p></p><ol style="text-align: left;"><li>HA group - Create HA group (or choose existing)</li><ol><li>HA group name (?)</li><li>Add interfaces to the HA group</li><li>Determine the priority order</li><li>Virtual IP address</li></ol><li>Load balancer - Create endpoint (or choose existing)</li><ol><li>Endpoint details - name (?) - port (10443) - Client (S3) - Protocol (HTTPS)</li><li>Binding mode - Virtual IPs of HA groups</li><li>Tenant access - All tenants / Select Tenants / Block Tenants</li><li>Attach certificate - Upload certificate / Generate Certificate (see below)</li></ol><li>Tenant and bucket</li><ol><li>Tenant name (?)</li><li>Tenant root user password (?)</li><li>Bucket name (?) <i>(start and end with lowercase letter or number)</i></li><li>Region (us-east-1)</li></ol><li>Download data</li><li>ILM storage pool</li><ol><li>Choose Storage Pool for the <b>site</b>.</li></ol><li>ILM rule</li><ol><li>2+1 erasure coding at your <b>site</b>.</li></ol><li>ILM policy</li><ol><li>Activate rule in policy</li></ol><li>Traffic classification</li><li>Summary</li></ol><div style="text-align: left;"><b><u>APPENDIX: Generate Certificate:</u></b><br /><ul style="text-align: left;"><li>Domain name (e.g. lb.example.com)</li><li>IP</li><li>Subject (optional)</li><li>Days valid</li><li>YES - Add key usage extensions</li><li>Click Generate</li></ul><div><b><u>APPENDIX: ONTAP System Manager (9.13.1) add cloud tier:</u></b></div><ul style="text-align: left;"><li>Storage > Tiers + Add Cloud Tier - StorageGRID</li><ul><li>Name (?)</li><li>Path-Style URL</li><li>Server Name FQDN</li><li>SSL - YES</li><li>Object store certificate - YES</li><li>Paste your certificate</li><li>Port (10443)</li><li>Access Key (?)</li><li>Secret Key (?)</li><li>Bucket Name (System Manager can create a new bucket)</li><li>Add as Primary to aggregates...</li><ul><li><b>Update volume cloud tier properties</b> lets you set the tiering policy on volumes in the aggregate(s) to be FabricPool enabled.</li></ul><li>Network for Cloud Tier (verify)</li></ul></ul></div><p></p>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-4270346497183643494.post-58644838390856038182023-08-18T11:00:00.009-07:002023-08-21T01:18:35.026-07:00[Brief Notes] FabricPool & StorageGRID Best Practices & More...<p><i><span style="color: red;">** Work in progress ** </span></i></p><p><i>A place for some FabricPool notes.</i></p><p><i>Note: These are just personal notes from reading documentation. By reading I mean skimming through a document trying to pick out the most important bits.</i></p><p></p><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj7D7PrGcwM1MDFY7SbBgjhgn0XcFIVLwRlbUDw5tCdxMMzbkbjJtL6y15xsh3b_ig4KR3jggZ5UyzAczQvwzqFQBszenQQOkjXitDihjq8q56V4ETyvvN5kAmajry4997ZVicVflBzf9Kz1aDb7Kst3lelNjuzCBpFig-6-MWyTzgx60sf1h4yeNzIfaEH/s591/cloud-fabricpool_image5.png" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="481" data-original-width="591" height="261" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj7D7PrGcwM1MDFY7SbBgjhgn0XcFIVLwRlbUDw5tCdxMMzbkbjJtL6y15xsh3b_ig4KR3jggZ5UyzAczQvwzqFQBszenQQOkjXitDihjq8q56V4ETyvvN5kAmajry4997ZVicVflBzf9Kz1aDb7Kst3lelNjuzCBpFig-6-MWyTzgx60sf1h4yeNzIfaEH/w320-h261/cloud-fabricpool_image5.png" width="320" /></a></div><p></p><p><b><u><span style="font-size: large;">[1] FabricPool Best Practices - ONTAP 9.13.1 - TR 4598 (July 2023)</span></u></b></p><p>Requirements:</p><p></p><p></p><p></p><p></p><ul style="text-align: left;"><li>In releases earlier than ONTAP 9.8, FabricPool is only supported on SSD local tiers.</li></ul><p>Volume Tiering Policies:</p><p></p><ul style="text-align: left;"><li>By default, volumes use the <span style="background-color: #fcff01;">None</span> volume tiering policy. The exception to this are newly created FlexVol volumes on FabricPool aggregates which use the Snapshot-Only volume tiering policy. <span style="background-color: #fcff01;"></span></li><li><span style="background-color: #fcff01;">Auto</span> - moves all cold blocks in the volume to the cloud tier.</li><li><span style="background-color: #fcff01;">Snapshot-Only</span> - cold Snapshot copy blocks in the volume are moved to the cloud tier.</li><li><span style="background-color: #fcff01;">All</span> - primarily used with secondary data and data protection volumes. NetApp does not recommend using the All volume tiering policy with primary data (read/write volumes).</li></ul><p></p><p>Intercluster LIFs:</p><p></p><div><ul style="text-align: left;"><li><i>No specific best practice (i.e. if you already have for SnapMirror, you could use the same)</i></li><li>If you are using more than one intercluster LIF on a node with different routing, NetApp recommends placing them in different IPspaces. <span style="background-color: #fcff01;">During configuration, FabricPool can select from multiple IPspaces,</span> but it is unable to select specific intercluster LIFs within an IPspace.</li><li><i>Note: Disabling or deleting an intercluster LIF interrupts communication to the cloud tier.</i></li></ul><div>Volumes (must use <span style="background-color: #fcff01;">space-guarantee none</span>):</div></div><p></p><div><ul style="text-align: left;"><li>FabricPool cannot attach a cloud tier to a local tier that contains volumes by using a space guarantee other than None.</li><li><span style="background-color: #fcff01;">FlexGroup</span> constituent volumes on heterogenous local tiers is not recommended.</li><li><span style="background-color: #fcff01;">QoS Min must be turned off</span> on volumes in FabricPool local tiers. Alternatively, tiering must be turned off (-tiering-policy none) on volumes that require QoS Min.</li></ul><div>Cloud Tiering license:</div></div><div><ul style="text-align: left;"><li>A Cloud Tiering license is <span style="background-color: #fcff01;">not required when using StorageGRID</span> or ONTAP S3 as the cloud tier or when using Amazon S3, Google Cloud Storage, or Microsoft Azure Blob Storage as the cloud tier for Cloud Volumes ONTAP.</li><li>Tiering to the cloud tier stops when the amount of data (used capacity) stored on the cloud tier reaches the licensed capacity.</li></ul><div><div>Certificate authority certification:</div><div><ul style="text-align: left;"><li>When FabricPool uses StorageGRID or some other private clouds as a cloud tier, it must use a TLS. Using FabricPool without TLS configuration is supported but not recommended.</li><li><i>Note: Beginning in ONTAP 9.4, CA certificates are no longer required. However, <span style="background-color: #fcff01;">using signed certificates from a third-party certificate authority remains the recommended best practice.</span></i></li><li>For more, see page 12</li><li><a href="https://docs.netapp.com/us-en/storagegrid-115/admin/using-storagegrid-security-certificates.html">Using StorageGRID security certificates (from 11.5 documentation)</a></li><li><a href="https://docs.netapp.com/us-en/storagegrid-117/admin/using-storagegrid-security-certificates.html">Manage security certificates: Overview (from 11.7 documentation)</a></li></ul><div>Data Movement:</div></div></div></div><div><ul style="text-align: left;"><li><span style="font-family: courier;">volume object-store tiering show</span></li><li>Tiering fullness threshold:</li><ul><li>By default, tiering to the cloud only happens if the local tier is >50% full.</li><li>Setting the threshold to a lower number may be useful for large local tiers that contain little hot/active data.</li><li>Setting the threshold to a higher number may be useful for solutions designed to tier only when local tiers are near maximum capacity.</li><li><i>Note: The All volume tiering policy ignores the tiering fullness threshold.</i></li><li><span style="font-family: courier;">storage aggregate object-store modify βaggregate AGGR βtiering-fullness-threshold (0%-99%) -object-store-name NAME</span></li></ul><li><i>SnapMirror: Cascading SnapMirror relationships are not supported when using the All volume tiering policy. Only the final destination volume should use the All volume tiering policy.</i></li><li>Volume move:</li><ul><li>If a volume moveβs <span style="background-color: #fcff01;">destination local tier uses the same bucket as the source local tier</span>, data on the source volume that is stored in the bucket does not move back to the local tier.</li><li>Incompatible with optimized volume moves:</li><ul><li>Source and destination aggregates use different encryption keys</li><li>FlexClone volumes and FlexClone parent volumes</li></ul><li>If a volume tiering policy is not specified when performing a volume move, the destination volume uses the tiering policy of the source volume. If a different tiering policy is specified when performing the volume move, the destination volume is created with the specified tiering policy.</li><li><i>Note: When in an SVM DR relationship, source and destination volumes must use the same tiering policy.</i></li><li>Moving a volume to another local tier resets the inactivity period of blocks on the local tier.</li></ul></ul></div><div>FabricPool Mirror:</div><div><ul style="text-align: left;"><li>Enables the attachment of two cloud tiers to a single local tier (allowing you could move from one cloud tier to another.)</li><li>When both buckets are in a mirrored state, newly tiered data is synchronously tiered to both buckets. Because data is being tiered to two buckets synchronously, the effective throughput is half of standard single-bucket tiering.</li><li>FabricPool Mirror can be used to tier data to multiple cloud vendors for an additional level of resiliency as the likelihood that multiple cloud providers experiences outages at the same time is extremely rare.</li><li><i>Although essential for FabricPool with NetApp MetroCluster, FabricPool Mirror is a stand-alone feature that does not require MetroCluster to use.</i></li></ul><div>Unreclaimed space threshold (no specific reason to change):</div></div><div><ul style="text-align: left;"><li>StorageGRID 40%</li><li><span style="font-family: courier;">storage aggregate object-store modify βaggregate AGGR -object-store-name OBJSTORE βunreclaimed-space-threshold (0%-99%)</span></li></ul></div><div>ONTAP storage efficiencies:</div><div><ul style="text-align: left;"><li>Storage efficiencies are preserved when moving data to the cloud tier.</li><li>Aggregate inline deduplication is supported on the local tier, but associated storage efficiencies are not carried over to objects stored on the cloud tier.</li><li>When using the All volume tiering policy, storage efficiencies associated with background deduplication processes may be reduced as data is likely to be tiered before the additional storage efficiencies can be applied.</li><li><i style="background-color: #fcff01;">Note: Third-party deduplication has not been qualified by NetApp.</i><br /></li></ul></div><div>Temperature-sensitive storage efficiency:</div><div><ul style="text-align: left;"><li>Beginning in ONTAP 9.10.1:</li><ul><li>TSSE supports with FabricPool. More efficient, but smaller blocks will require smaller GETs, reducing GET performance from the Cloud Tier.</li><li>AFF volumes are created using adaptive compression by default (-storage-efficiency-mode default)</li><li>TSSE must be manually enabled on volumes (-storage-efficiency-mode efficient)</li></ul></ul></div><div>Configuration - see page 21.</div><div><ul style="text-align: left;"><li>Attaching a single cloud tier to multiple local tiers in a cluster is the general best practice. NetApp does not recommend attaching a single cloud tier to local tiers in multiple clusters.</li><li><i>Note: Attaching a cloud tier to all FabricPool local tiers is the general best practice and provides significant benefits to environments that value manageability over public object store cloud tier performance.</i></li><li><i>Note: ONTAP and StorageGRID system clocks must not be out of sync by more than a few minutes. Significant clock skew prevents the StorageGRID bucket from being attached to the local tier.</i></li><li><i>Note: Attaching a cloud tier to a local tier is a permanent action. A cloud tier cannot be unattached from a local tier after being attached. (Using FabricPool Mirror, you can attach a different cloud tier.)</i></li></ul><div>More on volume tiering:</div></div><div><ul style="text-align: left;"><li>It takes approximately 31 days for inactive blocks to become cold. The Auto cooling period is adjustable between 2 days and 183 days by using <span style="background-color: #fcff01;">tiering-minimum-cooling-days</span></li><li>When cold blocks in a volume with a tiering policy set to <b>Auto are read randomly</b>, they are made hot and written to the local tier.</li><li>When cold blocks in a volume with a tiering policy set to <b>Auto are read sequentially</b>, they stay cold and remain on the cloud tier. They are not written to the local tier.</li></ul></div><div>Cloud Retrieval Policies:</div><div><ul style="text-align: left;"><li>Default</li><li>Never</li><li>On-Read</li><li>Promote - Setting the cloud retrieval policy to Promote immediately queues tiered data to return to the local tierβprovided the tiering policy allows it<i> (e.g. when changing tiering policy from Auto to None, or Auto to Snapshot-Only)</i></li></ul></div><div>Default Volume tiering-minimum-cooling-days:</div><div><ul style="text-align: left;"><li>For the <b>Auto</b> tiering policy is <b>31</b> days.</li><li>For the <b>Snapshot-Only</b> tiering policy is <b>two</b> days.</li></ul></div><div>Security:</div><div><ul style="text-align: left;"><li>FabricPool supports NetApp Storage Encryption (NSE), NetApp Volume Encryption (NVE), and NetApp Aggregate Encryption (NAE). </li><li>NetApp highly recommends using client-side <span style="background-color: #fcff01;">NVE or NAE encryption - encrypting data at rest is the recommended best practice</span>. If required to disable on cloud tier: <span style="font-family: courier;">storage aggregate object-store config modify -serverside-encyption false</span></li></ul></div><div>Interoperability - see page 39.</div><div><br /></div><div>StorageGRID:</div><div><ul style="text-align: left;"><li>NetApp recommends provisioning enough StorageGRID nodes to meet or exceed capacity and performance requirements</li><li>You can use high-availability (HA) groups to provide highly available data connections for S3 client. You can also use HA groups to provide highly available connections to the Grid Manager and the Tenant Manager. HA groups use virtual IP addresses (VIPs) to provide active-backup access to Gateway Node or Admin Node services.<br /></li><li>NetApp recommends disabling stored object compression in StorageGRID.</li><li>NetApp recommends disabling stored object encryption in StorageGRID.</li><li>Intrasite <span style="background-color: #fcff01;">erasure coding using a 2+1 scheme is the recommended best practice</span> for cost efficient data protection. Erasure coding uses more CPU, but significantly less storage capacity, than replication. 4+1 and 6+1 schemes use even less capacity than 2+1, but at the cost of lower throughput and less flexibility when adding storage nodes during grid expansion.</li><li>FabricPool also supports advanced ILM rules such as filtering based on object tags when StorageGRID is used as the cloud tier. ILM rules can be used in conjunction with tags to direct objects to specific nodes, change data protection policies (from replication to erasure coding), etc.</li><li>ONTAP supports up to four tag key=value pairs per volume: <span style="font-family: courier;">volume modify VOLNAME -tiering-object-tags KEY1=VALUE1,KEY2=VALUE2...</span></li><li>NetApp recommends using the default, read-after-new-write, consistency control for buckets used as FabricPool targets. <i>Note: <span style="color: red;">Do not use the available consistency control</span> for buckets used as FabricPool targets.</i></li></ul></div><div>Performance:</div><div><ul style="text-align: left;"><li>Object Store Profiler:</li><ul><li>You must add the cloud tier to ONTAP before you can use it with the object store profiler.</li><li>Start the object store profiler:</li><ul><li><span style="font-family: courier;">storage aggregate object-store profiler start -object-store-name OSNAME -node NODE</span></li></ul><li>View the results:</li><ul><li><span style="font-family: courier;">storage aggregate object-store profiler show</span></li></ul></ul><li>Sequential read performance: Beginning in <b>ONTAP 9.13.1</b>, FabricPool performance was improved by increasing the concurrency and parallelism of byte-ranged GETs during sequential reads.</li><li>PUT throttling:</li><ul><li>FabricPool PUT operations do not compete for resources with other applications. FabricPool PUT operations are automatically placed at a lower priority (bullied) by client applications and other ONTAP workloads, such as SnapMirror.</li><li>storage aggregate object-store put-rate-limit modify -node NODE -default TRUE|FALSE -put-rate-bytes-limit X[KB|MB|GB|TB|PB]</li></ul></ul></div><div>Loss of Connectivity (p44):</div><div><ul style="text-align: left;"><li>If for any reason connectivity to the cloud is lost, the FabricPool local tier remains online, but applications receive an error message when attempting to get data from the cloud tier. Cold blocks that exist exclusively on the cloud tier remain unavailable until connectivity is reestablished.</li><li>NetApp recommends using the following guidance when tiering data in volumes hosting LUNs:</li><ul><li>Snapshot-Only is an acceptable tiering policy for most SAN use cases.</li><li>Auto should only be used for non-critical applications. </li><li>All should not be used on volumes hosting LUNs.</li></ul></ul></div><div>Sizing (p45):</div><div><ul style="text-align: left;"><li>Writes from the cloud tier to the local tier are disabled if local tier capacity is greater than 90%. If this occurs, blocks are read directly from the cloud tier.</li><li>Inactive data reporting (IDR):</li><ul><li>Enabled by default on non-FabricPool SSD local tiers. Enable on HDD using CLI.</li><li>Uses a 31-day cooling period. Adjust with the volume -tiering-minimum-cooling-days</li><li>To enable: storage aggregate modify -aggregate AGGRNAME -is-inactive-data-reporting-enabled true</li></ul><li>Tiering during data migrations</li><ul><li>Because of the difference in ingress and egress rates, it is possible run out of space on a small local tier when attempting to migrate more data to it than it has capacity to hold. Data is usually coming into the local tier at a faster rate than it can be converted into objects and tiered out.</li><li><i>For example, if a volume move takes place at 2GBps but tiering takes place at 500MBps, 50TB completes the volume move to the local tier in ~7 hours. However, ~28 hours are required for tiering to an object store. The local tier must have enough capacity to store the data before it is tiered.</i></li></ul><li>Do not host virtualized object stores (e.g. virtual StorageGRID storage nodes) in volumes that tier inactive data. Set the tiering policy on those volumes to None.</li></ul></div><div>ONTAP CLI</div><div><ul style="text-align: left;"><li><span style="font-family: courier;">storage aggregate object-store show-space</span></li><li><span style="font-family: courier;">volume show-footprint</span></li></ul></div><div><b><u><span style="font-size: large;">[2] StorageGRID 11.6 Documentation - April 14, 2023</span></u></b></div><div><br /></div><div><i>This is a 2288 page PDF. I've skimmed by searching for Best Practice.</i></div><div><ul style="text-align: left;"><li>If you do not have gateway, the best practice is to set the gateway address to be the IP address of the network interface.</li><li>The best practice is to specify at least two DNS servers.</li><li>Default Grid CA certificate:</li><ul><li>Although you can use the Grid CA certificate for a non-production environment, the best practice for a production environment is to use custom certificates signed by an external certificate authority. </li></ul><li>Global/other certificates:</li><ul><li>The best practice for a production environment is to use custom certificates signed by an external certificate authority.</li></ul><li>Best practices for StorageGRID load balancing:</li><ul><li>As a general best practice, each site in your StorageGRID system should include two or more nodes with the Load Balancer service.</li><li>You must configure a StorageGRID load balancer endpoint to define the port that Gateway Nodes and Admin Nodes will use for incoming and outgoing FabricPool requests.</li></ul><li>Best practices for the load balancer endpoint certificate:</li><ul><li>When creating a load balancer endpoint for use with FabricPool, you should use HTTPS as the protocol. Communicating with StorageGRID without TLS encryption is supported but not recommended.</li><li>You can then either upload a certificate that is signed by either a publicly trusted or a private certificate authority (CA), or you can generate a self-signed certificate. The certificate allows ONTAP to authenticate with StorageGRID.</li><li>As a best practice, you should use a CA server certificate to secure the connection. <span style="background-color: #fcff01;">Certificates signed by a CA can be rotated nondisruptively.</span></li></ul><li>Best practices for high availability (HA) groups:</li><ul><li>Before attaching StorageGRID as a FabricPool cloud tier, you should use the StorageGRID Grid Manager to configure a high availability (HA) group.</li><li>If you plan to use FabricPool with <b>primary workload data</b>, you must create an HA group that includes at least two load-balancing nodes to prevent data retrieval interruption.</li></ul><li>The best practices for creating a traffic classification policy for FabricPool depend on the workload, as follows:</li><ul><li>If you plan to tier FabricPool primary workload data to StorageGRID, you should ensure that the FabricPool workload has the majority of bandwidth.</li><li>You can create a traffic classification policy to limit all other workloads.</li><li>In general, FabricPool read operations are more important to prioritize than write operations. You should not impose quality of service limits on any FabricPool workload; you should only limit the other workloads.</li></ul><li>Other best practices for StorageGRID and FabricPool:</li><ul><li>Object encryption: not required (already encrypted)</li><li>Object compression: not required (already compressed)</li><li>Consistency level: recommended is <b>Read-after-new-write</b> (default). <u><span style="color: red;">Do not use available or any other consistency level</span></u></li><li>Never use FabricPool to tier any data related to StorageGRID back to StorageGRID itself.</li></ul></ul><div><br /></div></div><div><b><u><span style="font-size: large;">[3] FabricPool S3 Compatible Test Guide - April 2020</span></u></b></div><div><ol style="text-align: left;"><li>Pre-requisites</li><ol><li>Install and Setup ONTAP Cluster</li><li>Create SSD aggregate</li><ol><li><span style="font-family: courier;">::> storage aggregate create</span></li></ol><li>Configure dedicated intercluster LIF per node</li><ol><li><span style="font-family: courier;">::> net int create -service-policy default-intercluster</span></li></ol><li>Verify LIF connectivity to Cloud Object-storage::></li><ol><li><span style="font-family: courier;">::> network ping</span></li></ol><li>Create volumes</li><ol><li><span style="font-family: courier;">::> stor aggr object-store modify -aggr AGGR -tiering-fullness-threshold X%</span></li></ol><li>Adding data to volumes</li><ol><li><span style="font-family: courier;">::> set d</span></li><li><span style="font-family: courier;">::> run local mkfile 1g /vol/VOLNAME/FILE [x files]</span></li><li><span style="font-family: courier;">::> run local ls -l /vol/VOLNAME</span></li><li><span style="font-family: courier;">::> snapshot create</span></li><li><span style="font-family: courier;">::> ...</span></li></ol></ol><li>Configuring FabricPool</li><ol><li>FabricPool license (not required if StorageGRID is used)</li><li>Install CA certificates in ONTAP</li><ol><li><span style="font-family: courier;">% openssl s_client -connect <object-server-ip>:<port> -showcerts</span></li><li><span style="font-family: courier;">::> security certificate install -type server-ca</span></li><li>(Optional) Configure Proxy (when using different cloud providers)</li><li>Add a Cloud Tier to ONTAP</li><li>Configuring other S3 compliant object storage</li><ol><li><span style="font-family: courier;">::> object-store config create</span></li></ol><li>Attach external capacity tier to an aggregate:</li><ol><li><span style="font-family: courier;">::> storage aggr object-store attach</span></li></ol><li>Validate FabricPool aggregate:</li><ol><li><span style="font-family: courier;">::> stor aggr show</span></li></ol></ol></ol><li>Test Plans</li><ol><li>Understand IDR in a non-FabricPool Aggregate</li><li>Auto Tiering Workflows</li><li>Snapshot-only Tiering Workflows</li><li>Archive a volume using vol move</li><li>Recovery from local / backup / DR volume snapshot</li></ol></ol><div>Capture ONTAP Statistics:</div></div><div><ul style="text-align: left;"><li><span style="font-family: courier;">set d</span></li><li><span style="font-family: courier;">node run -node * "wafl composite stats show"</span></li><li><span style="font-family: courier;">node run -node * "wafl composite stats counter show FPAGGR"</span></li><li><span style="font-family: courier;">node run -node * "walf cloudio_stats"</span></li><li><span style="font-family: courier;">statistics show -object object_store_client_conn -instance *</span></li><li><span style="font-family: courier;">statistics show -object object_store_client_op -instance * -raw</span></li><li><span style="font-family: courier;">statistics show -object ktls_global -instance ktls_global -raw</span></li><li><span style="font-family: courier;">statistics show -object ktls_session -raw</span></li><li><span style="font-family: courier;">snapmirror show -instance</span></li><li><span style="font-family: courier;">df -aggregates -composite -aggregate AGGR</span></li><li><span style="font-family: courier;">volume show-footprint</span></li><li><span style="font-family: courier;">aggregate show-space</span></li></ul><div><b><u><span style="font-size: large;">[4] NetApp FabricPool with StorageGRID - Recommendation Guide - TR-4826</span></u></b></div></div><div><br /></div><div><i>Additional to the above.</i></div><div><ul style="text-align: left;"><li><b>High-availability groups</b></li><ul><li>In StorageGRID, high-availability<span style="background-color: #fcff01;"> (HA) groups use virtual IP addresses (VIPs)</span> to provide active-backup access. HA groups can consist of a combination of admin nodes, gateway nodes, or both. Gateway nodes are dedicated load balancer nodes, whereas admin nodes run both management and Amazon Simple Storage Service (Amazon S3) load-balancing services. You assign one node in the group to be the active primary. <span style="background-color: #fcff01;">When admin nodes are configured in an HA group, ports 443 and 80 cannot be configured for Amazon S3 access because they are reserved for the Grid Manager and Tenant Manager UIs. </span></li></ul><li><b>Load balancer endpoints</b></li><ul><li>The load balancer service in StorageGRID provides Layer-7 load balancing. It also performs Transport Layer Security (TLS) termination of client requests, inspects the requests, and establishes new secure connections to the storage nodes. <span style="background-color: #fcff01;">First, create a load balancer endpoint to be used for the FabricPool workload with the display name (for example, S3.netapp.com) and the port to be used (for example, 10443). When selecting HTTPS, you must upload or generate a certificate.</span> Make sure to upload the certificate to the ONTAP cluster, as well as the root and any subordinate certificate authority (CA) certificates.</li></ul><li><b>Load balancer topology</b></li><ul><li>A general <span style="background-color: #fcff01;">best practice is to use two load-balancing nodes in each site in an HA group with at least one load balancer endpoint configured.<br /></span></li></ul></ul></div><div><b><u><span style="font-size: large;">[5] StorageGRID Design and Implementation - Guidelines and Best Practices: TR-4889 - January 2023</span></u></b></div><div><i><br /></i></div><div><i>Additional to the above.</i></div><div><ul style="text-align: left;"><li>Abbreviations:</li><ul><li><b>Administrative Domain Controller (ADC).</b> Maintains topology and grid-wide configuration. Typically exists only on 3 Storage Nodes at each site. Requires a minimum of three ADCs per site.</li><li><b>Configuration Management Node (CMN).</b> Manages system-wide configuration, <span style="background-color: #fcff01;">exists on a primary Admin Node only</span>.</li><li><b>Connection Load Balancer (CLB)</b>. Provides layer 3 and 4 load balancing of S3 and Swift traffic from clients to Storage Nodes. This service exists on every Gateway Node. <span style="color: red;">The CLB service is deprecated</span>. The <span style="background-color: #fcff01;">Load Balancer</span> service on a Gateway or Admin Node is <span style="background-color: #fcff01;">recommended</span>, which provides a layer 7 load-balancing mechanism.</li><li><b>Local Distribution Router (LDR).</b> Processes object storage protocol (S3 or Swift) requests and manages object data on disk. This service runs on every Storage Node.</li></ul><li>DDP:</li><ul><li>For SG5760/SG6060/SGF6024, <span style="background-color: #fcff01;">DDP8 is the recommended RAID</span> volume configuration and is our default. <span style="color: red;">For DDP16, there is a performance decrease compared to DDP8 for certain object sizes</span>. <i>DDP16 allows greater capacity.</i></li></ul><li>StorageGRID topology notes:</li><ul><li>You can deploy a grid with two logical sites at the same physical data center.</li><li> Understand the trade-offs between a multisite grid and independent grids. StorageGRID provides redundancy for object metadata by storing the metadata for all objects in the system on Storage Nodes at each site. <span style="background-color: #fcff01;">Each site must support the full metadata load of the entire grid.</span></li><li>A grid must have one <b>primary Admin Node.</b> You cannot promote a non-primary Admin Node to primary Admin Node. Each additional Admin Node generates extra management-related traffic and activities. The general guideline is one primary and one non-primary Admin Node in a single grid regardless of the number of sites</li><li>Each grid site must have a <b>minimum of three Storage Nodes</b>. The general recommendation is one extra node above minimum in case one Storage Node requires maintenance.</li><li><b>Cassandra database size.</b> StorageGRID reserves space on an object store volume 0 of each Storage Node for the Cassandra database. On a Storage Node with greater than or equal to 128G RAM, 4TB is reserved. The total grid metadata capacity is limited by the smallest site.</li></ul><li>Network topologies:</li><ul><li><b>Grid Network. </b>All nodes on the Grid Network must be able to talk to all other nodes. The Grid Network can consist of multiple subnets. You can also add networks containing critical grid services, such as Network Time Protocol (NTP), as grid subnets. When the Grid Network is the only StorageGRID network, it is also used for all admin traffic and all client traffic. <span style="background-color: #fcff01;">The Grid Network gateway is the node default gateway unless the node has the Client Network configured.</span></li><li><b>Admin Network</b> (optional). Using the Admin Network is recommended if the grid includes StorageGRID appliances.</li><li><b>Client Network</b> (optional). Client network is an external facing network to allow S3 clients to access the grid. <i>Using a Client Network, you can configure a Grid Network that is private and not externally routable or use it for FabricPool data, while using an external network for other application/client access.</i> You can configure Client Network interfaces to interface with untrusted networks, exposing only the ports configured for the S3 endpoint (typically 443)</li><li><i>Note: Each type of network must be on a different subnet with no overlap.</i></li><li><i>Note: You can enable admin and client networks later, as a post-deployment maintenance task.</i></li></ul><li><b>StorageGRID Implementation Best Practices: Planning and Preparation</b></li><ul><li>Understand proposed solution details.</li><li>Review sales orders.</li><li>Complete StorageGRID installation workbook from ConfigBuilder.netapp.com.</li><li>If you plan to setup a high-availability group (HA group), the Admin and/or Gateway Nodes in same group must have at least one interface (Grid or Client) on same subnet and you must configure this interface with a static IP.</li><li>Download StorageGRID software and latest hotfix,</li><li>Download StorageGRID software licenses (grid serials from SO)</li><li><i>Download SGA firmware - supported SANtricity and disk firmware (as required)</i></li></ul><li><b>StorageGRID Implementation Best Practices: Grid Installation</b></li><ul><li>Configure SGA networks and DDP mode, Verify network connectivity.</li><li>SG100/1000 Admin Node, confirm time within 15 mins of UTC. SSH to 8022, login as admin, su - to root, and enter <span style="font-family: courier;">date</span>. To set: <span style="font-family: courier;">date --set ="yyyy-mm-dd hh:mm:ss"</span></li><li><span style="color: red;"><i>The StorageGRID appliance serial port must not be connected before you click Start Installation.</i></span></li><li>On the primary Admin Node grid installation interface, <b>confirm</b> that the <b>grid name</b>, <b>site name</b>, <b>node name</b> entries are correct and have no errors. <span style="color: red;"><i>There is no procedure to change these names after you select Start Install.</i></span></li><li>The Grid Network subnets list includes subnets for NTP, DNS, and LDAP if you want to access them through the Grid Network gateway.</li><li><i>Node approval page - all present and correct, and in the correct site?</i></li><li>Admin Network - if NTP is not accessible through the Grid Network, add the NTP server subnet.</li><li>NTP Role and ADC Service Settings. NetApp recommends leaving these as Automatic for new grid install.</li><li>NTP servers must be accessible either on the Grid Network or Admin Network during grid installation. </li><li>Passwords:</li><ul><li><b>Provisioning Passphrase - </b>used for grid maintenance and topology changes.</li><li><b>Grid Management Root User</b> - a superuser login to the Grid Manager UI.</li><li><span style="color: red;"><i>For production deployment, <u>do not clear</u> <b>Create Random Command Line Passwords</b> for security reasons.</i></span></li></ul><li><span style="color: red;"><i>Make sure that the recovery package is kept in a secure place because it contains a login password </i></span><i style="color: red;">to each grid node.</i></li><li><span style="color: red;"><i>Do not reboot any grid node if you observe a node stuck at same status for over 30 minutes.</i></span></li><li>Use SANtricity Management UI to configure DNS, NTP, and SMTP to receive email alerts. To configure AutoSupport Delivery Method and test the configuration, go to Support > AutoSupport.</li><li>Using the Grid Manager UI, perform basic installation verification:</li><ul><li>Alerts, Capacity, Nodes, Support > Diagnostics</li><li>AutoSupport - and confirm it is sent successfully</li></ul></ul><li><b>Grid Configuration: Grid Options</b></li><ul><li><b style="background-color: #fcff01;">Compress Stored Object: NO</b> for FabricPool (<i>FabricPool compresses objects before tiering out to StorageGRID.)</i></li><li><b style="background-color: #fcff01;">Stored Object Encryption: NO</b> for FabricPool (<i>FabricPool encrypts objects when tiering out data to StorageGRID, it is not necessary to enable encryption on the StorageGRID side.)</i></li><li><b>Stored Object Hashing.</b> By default, object data is hashed using the SHA-1 algorithm. The SHA-256 algorithm requires additional CPU resources and is generally not recommended for integrity verification.</li><li><b>Enable HTTP Connection.</b> This option does not apply if client applications connect to the gridβs Load Balancer service on the Gateway Node or Admin Node. You can configure HTTP or HTTPS on each load balancer endpoint. Internally, the Load Balancer service connects to Storage Nodeβs LDR using HTTPS regardless of whether the endpoint is using HTTP or HTTPS.</li></ul><li><b>ILM configuration best practices:</b></li><ul><li>Create a storage pool per site and use the site-specific storage pool in the rule. Even if there is one site in the grid, create a site-specific storage pool instead of the All Storage Nodes pool.</li><li>Recommendation of ILM rule for FabricPool. NetApp recommends using local EC, for example, EC 2+1 or 4+1 (depending on the number of Storage Nodes installed at the site).</li></ul><li><b>TLS Certificate Configuration: </b><i>(from page 28)</i></li><ul><li>1) Submit a certificate signing request (CSR) to a publicly known certificate authority (CA) (for a fee). <u>Recommended</u>. <u>Must</u> use this option if the grid is intended for external clients.</li><li>2) Submit a CSR to the internal IT security department. <u>Recommended if</u> your customer prefers not to pay for a public CA and all clients are internal within the company. Example commands: <a href="https://github.com/NetApp-StorageGRID/SSL-Certificate-Configuration">https://github.com/NetApp-StorageGRID/SSL-Certificate-Configuration</a></li><li>3) Use the self-signed certificate generated by StorageGRID. Suitable for short-term testing with no external client connections. Only available when you create a load balancer endpoint.</li></ul><li><b>Install custom server certificate:</b></li><ul><li>Management Interface Server Certificate ...</li><li>Object Storage API Service Endpoints Certificate</li><ul><li><i>Note: This certificate is not used by the grid Load Balancer service. <span style="background-color: #fcff01;">Skip if all client connections are made through the load balancer endpoint.</span></i></li></ul><li>Load balancer endpoint ...</li></ul><li><b>TLS Certificate Renewal</b></li><ul><li>Most TLS server certificates expire within 1 year.</li><li>Using a public/internal CA issued server certificate streamlines the renewal process as the new certificate only needs to be installed on the StorageGRID side, not on the client's side.</li></ul><li><b>Load Balancer endpoints:</b></li><ul><li>The Load Balancer service runs on the Admin Node and Gateway Node. You create load balancer endpoints for client connections.</li><li>When creating a load balancer endpoint, you specify a port number, whether the endpoint accepts HTTP or HTTPS connections, S3 or swift, and the certificate to be used for HTTPS connections.</li></ul><li><b>High Availability Groups:</b></li><ul><li>You can create a HA group of Gateway Nodes or Admin Nodes to create an active-backup configuration, or you can use round-robin DNS or a third-party load balancer and multiple HA groups to achieve a HA configuration. Client connections are made using the virtual IP addresses of HA groups.</li><li>If an HA group includes different node types such as an Admin Node and Gateway Nodes, only services common in both nodes can failover to a standby Node when the preferred master fails.</li></ul><li><b>Alert notification:</b></li><ul><li>Metadata storage and object data storage are two major attributes to monitor.</li><li>In addition to alert email notifications, you can configure the SNMP agent to send SNMP notifications.</li></ul><li><b>S3 bucket consistency guidelines:</b></li><ul><li>StorageGRID stores object metadata in a Cassandra database; each Storage Node hosts an instance of Cassandra. StorageGRID stores 3 replicas of the metadata per site.</li><li>Consistency controls:</li><ul><li>all</li><li>strong-global</li><li>strong-site(M)</li><li>read-after-new-write (default)</li><li>available</li><li>weak (not recommended)</li></ul></ul><li><b>What to monitor:</b></li><ul><li>(D) The system health data show on the Grid Manager Dashboard</li><li>(D) Verify that there is no attention/caution warning on the Diagnostics page</li><li>(W) Rate at which Storage Node object and metadata capacity is being consumed</li><li>(W) ILM operations on Grid Manager Dashboard</li><li>(W) Performance, networking and system resources</li><li>(W) Tenant activity</li><li>(M) Availability of software hotfixes and software upgrades</li><li>(C) Load balancing operations after a configuration change</li></ul></ul></div><div><b><u><span style="font-size: large;">Additional Notes</span></u></b></div><div><br /></div><div><a href="https://www.youtube.com/watch?v=La8DEv_hXZw">New FabricPool configuration wizard in StorageGRID 11.7 - YouTube</a></div><div><a href="https://docs.netapp.com/us-en/storagegrid-117/fabricpool/use-fabricpool-setup-wizard.html">Use FabricPool setup wizard: Considerations and requirements (netapp.com)</a></div><div><br /></div><div><i>To be continued...</i></div>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-4270346497183643494.post-76081818925477627502023-08-07T02:27:00.006-07:002023-08-10T01:28:48.743-07:00Do You Know Your ONTAP Encryption Passphrase?<div><i>This post was prompted by a question:</i></div><div><i><br /></i></div><div><i>"Q: I think we know the passphrase, but how do I check it is correct?"</i></div><div><br /></div><u>Remembering the ONTAP encryption passphrase is very important!</u> If you need to add new nodes to a cluster - or maybe for a headswap - you will need to know the encryption passphrase. And you can only change the passphrase if you know what it is.<div><br /></div><div>When we setup the onboard key-manager, we need to create a passphrase:</div><div><br /></div><div><div><span style="font-family: courier;">cluster1::*> security key-manager onboard enable</span></div><div><span style="font-family: courier;"><br /></span></div><div><span style="font-family: courier;">Enter the cluster-wide passphrase for the Onboard Key Manager:</span></div></div><div><br /></div><div>The above also outputs the backup key (which cannot be deciphered to tell you what the passphrase is.)</div><div><br /></div><div>If we do an update-passphrase but enter the wrong passphrase, it errors:</div><div><br /></div><div><div><span style="font-family: courier;">cluster1::*> security key-manager onboard update-passphrase</span></div><div><span style="font-family: courier;"><br /></span></div><div><span style="font-family: courier;">Warning: This command will reconfigure the cluster passphrase for the Onboard Key Manager.</span></div><div><span style="font-family: courier;">Do you want to continue? {y|n}: y</span></div><div><span style="font-family: courier;">Enter current passphrase:</span></div><div><span style="font-family: courier;">Error: command failed: Cluster-wide passphrase is incorrect.</span></div></div><div><br /></div><div>And you can run a show-backup to see the backup key is unchanged:</div><div><br /></div><div><span style="font-family: courier;">cluster1::*> security key-manager onboard show-backup</span></div><div><br /></div><div>When you successfully change the passphrase (this does not affect encryption keys - it's just the passphrase to make changes with the OKM) you will get a slightly different backup key (see appendix for complete output.)</div><div><br /></div><div><div><span style="font-family: courier;">cluster1::*> security key-manager onboard update-passphrase</span></div><div><span style="font-family: courier;"><br /></span></div><div><span style="font-family: courier;">Warning: This command will reconfigure the cluster passphrase for the Onboard Key Manager.</span></div><div><span style="font-family: courier;">Do you want to continue? {y|n}: y</span></div><div><span style="font-family: courier;">Enter current passphrase:</span></div><div><span style="font-family: courier;">Enter new passphrase:</span></div><div><span style="font-family: courier;">Reenter the new passphrase:</span></div><div><span style="font-family: courier;">After updating the Onboard Key Manager passphrase...</span></div></div><div><br /></div><div><i>Note: If you just want to check the passphrase, do a Ctrl-C when it asks you for the new passphrase.</i></div><div><br /></div><div>I think it was ONTAP 9.11.1 where the command become onboard sync when adding new nodes to the cluster:</div><div><br /></div><div><div><span style="font-family: courier;">cluster1::*> security key-manager onboard sync</span></div><div><span style="font-family: courier;"><br /></span></div><div><span style="font-family: courier;">Enter the cluster-wide passphrase for the Onboard Key Manager:</span></div></div><div><br /></div><div>Before it was setup -node NEWNODE:</div><div><br /></div><div><div><span style="font-family: courier;">cluster1::*> security key-manager setup -node NODE-03</span></div><div><span style="font-family: courier;"><br /></span></div><div><span style="font-family: courier;">Enter the cluster-wide passphrase for the Onboard Key Manager. To continue the configuration, enter the passphrase, otherwise type "exit":</span></div></div><div><br /></div><div><b><u>Another Way</u></b></div><div><br /></div><div>There is another way of checking, this is to get the backup from:</div><div><br /></div><div><span style="font-family: courier;">security key-manager onboard show-backup</span></div><div><br /></div><div>And verify the key with the passphrase:</div><div><br /></div><div><span style="font-family: courier;">security key-manager onboard verify-backup</span></div><div><br /></div><div><b><u>APPENDIX: Output showing changing passphrase also subtlety changes the backup key.</u></b></div><div><br /></div><div><span style="font-family: courier;">cluster1::*> security key-manager onboard enable</span></div><div><div><span style="font-family: courier;"><br /></span></div><div><span style="font-family: courier;">Enter the cluster-wide passphrase for the Onboard Key Manager:</span></div><div><span style="font-family: courier;"><br /></span></div><div><span style="font-family: courier;">Re-enter the cluster-wide passphrase:</span></div><div><span style="font-family: courier;"><br /></span></div><div><span style="font-family: courier;">After setting up the Onboard Key Manager, <span style="background-color: #fcff01;">save the encrypted backup data</span>, displayed below, <span style="background-color: #fcff01;">along with the cluster passphrase in a safe location</span> so that you can use it if you need to perform a manual recovery operation. To view the encrypted backup data again, use the "security key-manager onboard show-backup" command.</span></div><div><span style="font-family: courier;"><br /></span></div><div><span style="font-family: courier;">--------------------------BEGIN BACKUP--------------------------</span></div><div><span style="font-family: courier;">TmV0QXBwIEtleSBCbG9iAAEBAAAEAAAAcAEAAAAAAABdVC5yAAAAACEAAAAAAAAA</span></div><div><span style="font-family: courier;">QAAAAAAAAAC/ZeDCAAAAAJ34J+/VvtAh0wk5lAU0+jhaIJ6Orkm6FGd6n+konw/g</span></div><div><span style="font-family: courier;">ZizyzPDJnDWOmQgVGprx7r1Rk2ksRKhYYdczvGvX0DgiAAAAAAAAACgAAAAAAAAA</span></div><div><span style="font-family: courier;">3WTh7gAAAAAAAAAAAAAAAAIAAAAAAAgAZJEIWvdeHr5RCAvHGclo+wAAAAAAAAAA</span></div><div><span style="font-family: courier;">IgAAAAAAAAAoAAAAAAAAAEOTcR0AAAAAAAAAAAAAAAACAAAAAAAJAGr3tJA/LRzU</span></div><div><span style="font-family: courier;">QRHwv+1aWvAAAAAAAAAAACQAAAAAAAAAgAAAAAAAAABxoLxtAAAAACUkeGbrchD4</span></div><div><span style="font-family: courier;">7BH5aVCplZGwAY8wkY7t5BtMJX+lAofU8WPO4heyzQ4AAAAAAAAAAAAAAAAAAAAA</span></div><div><span style="font-family: courier;">AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA</span></div><div><span style="font-family: courier;">AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA</span></div><div><span style="font-family: courier;">AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA</span></div><div><span style="font-family: courier;">AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA</span></div><div><span style="font-family: courier;">AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA</span></div><div><span style="font-family: courier;">AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA</span></div><div><span style="font-family: courier;">AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA</span></div><div><span style="font-family: courier;">AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABOZXRBcHAgS2V5IEJsb2IA</span></div><div><span style="font-family: courier;">AQEAAAMAAAAYAQAAAAAAAJviFLQAAAAAIgAAAAAAAAAoAAAAAAAAAEOTcR0AAAAA</span></div><div><span style="font-family: courier;">AAAAAAAAAAACAAAAAAAJAGr3tJA/LRzUQRHwv+1aWvAAAAAAAAAAACIAAAAAAAAA</span></div><div><span style="font-family: courier;">KAAAAAAAAAAMRKsgAAAAAAAAAAAAAAAAAgAAAAAAAQB5fUTU2XW+lj52CLbqH6LC</span></div><div><span style="font-family: courier;">AAAAAAAAAAAkAAAAAAAAAIAAAAAAAAAAsa45qQAAAACbJ9JQZkf6kUF3U+4ylCGH</span></div><div><span style="font-family: courier;">77+Sa5KqIgMguIJJki25zmkdf9arNx0RAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA</span></div><div><span style="font-family: courier;">AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA</span></div><div><span style="font-family: courier;">AAAAAAAAAAAAAAAAAAAAAE5ldEFwcCBLZXkgQmxvYgABAQAAAwAAABgBAAAAAAAA</span></div><div><span style="font-family: courier;">FIOghQAAAAAiAAAAAAAAACgAAAAAAAAAQ5NxHQAAAAAAAAAAAAAAAAIAAAAAAAkA</span></div><div><span style="font-family: courier;">ave0kD8tHNRBEfC/7Vpa8AAAAAAAAAAAIgAAAAAAAAAoAAAAAAAAADYPMfoAAAAA</span></div><div><span style="font-family: courier;">AAAAAAAAAAACAAAAAAABALMT+5l0RdWD42S2pp5MUIwAAAAAAAAAACQAAAAAAAAA</span></div><div><span style="font-family: courier;">gAAAAAAAAADqr1mzAAAAADTKt3sd2v9PX+xxruZh/IHMKYgHX+ZpIB3KoXERgnmD</span></div><div><span style="font-family: courier;">2XfqVrwhMRUAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA</span></div><div><span style="font-family: courier;">AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA</span></div><div><span style="font-family: courier;">---------------------------END BACKUP---------------------------</span></div></div><div><br /></div><div><div><span style="font-family: courier;">cluster1::*> security key-manager onboard update-passphrase</span></div><div><span style="font-family: courier;"><br /></span></div><div><span style="font-family: courier;">Warning: This command will reconfigure the cluster passphrase for the Onboard Key Manager.</span></div><div><span style="font-family: courier;">Do you want to continue? {y|n}: y</span></div><div><span style="font-family: courier;"><br /></span></div><div><span style="font-family: courier;">Enter current passphrase:</span></div><div><span style="font-family: courier;"><br /></span></div><div><span style="font-family: courier;">Enter new passphrase:</span></div><div><span style="font-family: courier;"><br /></span></div><div><span style="font-family: courier;">Reenter the new passphrase:</span></div><div><span style="font-family: courier;"><br /></span></div><div><span style="font-family: courier;">After updating the Onboard Key Manager passphrase, save the encrypted backup data, displayed below, along with the cluster passphrase in a safe location so that you can use it if you need to perform a manual recovery operation. To view the encrypted backup data again, use the "security key-manager onboard show-backup" command.</span></div><div><span style="font-family: courier;"><br /></span></div><div><span style="font-family: courier;">--------------------------BEGIN BACKUP--------------------------</span></div><div><span style="font-family: courier;">TmV0QXBwIEtleSBCbG9iAAEBAAAEAAAAcAEAAAAAAAAHjw78AAAAACEAAAAAAAAA</span></div><div><span style="font-family: courier;">QAAAAAAAAAAcg4CIAAAAAHTwH17QRb4oO63uim3uAOVhZtUCNbl6AtzloJZIQBoT</span></div><div><span style="font-family: courier;">Qai3h+Ubw9nzXPAWwXGPMo6l4x8bIDZNIKBtLuRcMyUiAAAAAAAAACgAAAAAAAAA</span></div><div><span style="font-family: courier;">3WTh7gAAAAAAAAAAAAAAAAIAAAAAAAgAZJEIWvdeHr5RCAvHGclo+wAAAAAAAAAA</span></div><div><span style="font-family: courier;">IgAAAAAAAAAoAAAAAAAAAEOTcR0AAAAAAAAAAAAAAAACAAAAAAAJAGr3tJA/LRzU</span></div><div><span style="font-family: courier;">QRHwv+1aWvAAAAAAAAAAACQAAAAAAAAAgAAAAAAAAAB+E2ZBAAAAANy/gsa01f0a</span></div><div><span style="font-family: courier;">h0qip2a9biwbMVO/Yl7imJxHykN69867NwFi1jrSJuQAAAAAAAAAAAAAAAAAAAAA</span></div><div><span style="font-family: courier;">AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA</span></div><div><span style="font-family: courier;">AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA</span></div><div><span style="font-family: courier;">AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA</span></div><div><span style="font-family: courier;">AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA</span></div><div><span style="font-family: courier;">AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA</span></div><div><span style="font-family: courier;">AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA</span></div><div><span style="font-family: courier;">AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA</span></div><div><span style="font-family: courier;">AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABOZXRBcHAgS2V5IEJsb2IA</span></div><div><span style="font-family: courier;">AQEAAAMAAAAYAQAAAAAAAJviFLQAAAAAIgAAAAAAAAAoAAAAAAAAAEOTcR0AAAAA</span></div><div><span style="font-family: courier;">AAAAAAAAAAACAAAAAAAJAGr3tJA/LRzUQRHwv+1aWvAAAAAAAAAAACIAAAAAAAAA</span></div><div><span style="font-family: courier;">KAAAAAAAAAAMRKsgAAAAAAAAAAAAAAAAAgAAAAAAAQB5fUTU2XW+lj52CLbqH6LC</span></div><div><span style="font-family: courier;">AAAAAAAAAAAkAAAAAAAAAIAAAAAAAAAAsa45qQAAAACbJ9JQZkf6kUF3U+4ylCGH</span></div><div><span style="font-family: courier;">77+Sa5KqIgMguIJJki25zmkdf9arNx0RAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA</span></div><div><span style="font-family: courier;">AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA</span></div><div><span style="font-family: courier;">AAAAAAAAAAAAAAAAAAAAAE5ldEFwcCBLZXkgQmxvYgABAQAAAwAAABgBAAAAAAAA</span></div><div><span style="font-family: courier;">FIOghQAAAAAiAAAAAAAAACgAAAAAAAAAQ5NxHQAAAAAAAAAAAAAAAAIAAAAAAAkA</span></div><div><span style="font-family: courier;">ave0kD8tHNRBEfC/7Vpa8AAAAAAAAAAAIgAAAAAAAAAoAAAAAAAAADYPMfoAAAAA</span></div><div><span style="font-family: courier;">AAAAAAAAAAACAAAAAAABALMT+5l0RdWD42S2pp5MUIwAAAAAAAAAACQAAAAAAAAA</span></div><div><span style="font-family: courier;">gAAAAAAAAADqr1mzAAAAADTKt3sd2v9PX+xxruZh/IHMKYgHX+ZpIB3KoXERgnmD</span></div><div><span style="font-family: courier;">2XfqVrwhMRUAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA</span></div><div><span style="font-family: courier;">AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA</span></div><div><span style="font-family: courier;">---------------------------END BACKUP---------------------------</span></div></div><div><br /></div><div>It is not the most obvious thing, but the backup keys are different.</div><div><br /></div><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjWs6dmq1kM1_aqOVYyLzdS_an8cWN2dGLudBE0ClViktLY2Sq1Prm1Wm36SXHPKcJ0FuLoWHV07Sdn4OWWWY7_fhv1wkZDVe96omct2tgiIy_0nNk2gVEWJoXOfdtqxda1TgN4WoiPn9bpct0KkJ0IhYFGaWN8wRHBpZtPmIf2bnC_d_2o-XZaWmwgfCWU/s637/ONTAP-9-Continuous-Innovation.png" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="561" data-original-width="637" height="176" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjWs6dmq1kM1_aqOVYyLzdS_an8cWN2dGLudBE0ClViktLY2Sq1Prm1Wm36SXHPKcJ0FuLoWHV07Sdn4OWWWY7_fhv1wkZDVe96omct2tgiIy_0nNk2gVEWJoXOfdtqxda1TgN4WoiPn9bpct0KkJ0IhYFGaWN8wRHBpZtPmIf2bnC_d_2o-XZaWmwgfCWU/w200-h176/ONTAP-9-Continuous-Innovation.png" width="200" /></a></div>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-4270346497183643494.post-21898475319594966272023-07-30T14:50:00.004-07:002023-07-31T02:31:04.727-07:00Microsoft SQL on ONTAP with SnapCenter<p><i><span style="color: red;">** Work in progress **</span></i></p><p><i>A place to put some researches.</i></p><p>Key sources of information:</p><p></p><ol style="text-align: left;"><li><a href="https://www.netapp.com/pdf.html?item=/media/8585-tr4590.pdf">TR-4590 | Best practice guide for Microsoft SQL Server with ONTAP</a></li><li><a href="https://www.netapp.com/pdf.html?item=/media/12400-tr4714pdf.pdf">TR-4714: Best Practices Guide for Microsoft SQL Server using NetApp SnapCenter</a></li><li><a href="https://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/UCS_CVDs/mssql2019_flexpod.html">FlexPod Datacenter for Microsoft SQL Server 2019 and VMware vSphere 6.7 - Cisco</a></li><li><a href="https://kb.vmware.com/s/article/1020652">Maximum supported volumes reached (1020652) (vmware.com)</a></li><li><a href="https://hwu.netapp.com/">NetApp Hardware Universe</a></li><li><a href="https://kb.vmware.com/s/article/1003497">ESXi/ESX Configuration Maximums (1003497) (vmware.com)</a></li></ol><div>Also see:</div><div><ul style="text-align: left;"><li><a href="http://www.cosonok.com/2023/07/types-of-always-on-microsoft-sql-server.html">Types of Always-On Microsoft SQL Server and Supported Storage (cosonok.com)</a></li></ul></div><div>Some maximums to consider (in the below I focused on NFS because I'm researching a deployment of MSSQL using VMDKs on NFS datastores):</div><div><ul style="text-align: left;"><li><i>[4] <span style="background-color: #fcff01;">(Maximum Number of NFS Datastores)</span> The default value (32 in ESXi 7.0) can can be increased to a maximum value of <span style="background-color: #fcff01;">256</span></i></li><ul><li><i>Note: This maximum applies since ESXi 5.x</i></li><li><i>[6] 256 NFS3 datastores per host as well as 256 NFS4.1 datastores per host are supported.</i></li></ul><li><i>[5] Examples with AFF A400 on ONTAP 9.13.1:</i></li><ul><li><i>Max number of flexible volumes - NAS:</i></li><ul><li><i>Node: 2500 (much higher than 256)</i></li><li><i>HA Pair: 5000</i></li><li><i>Cluster: 30000</i></li></ul><li><i>NFS Cluster Limits:</i></li><ul><li><i>Max number of export rules - Cluster: 200000</i></li></ul><li><i>WAFL Cluster Limits:</i></li><ul><li><i style="background-color: #fcff01;">Max size of 64-bit aggregate (TiB): 800</i></li><li><i style="background-color: #fcff01;">Max size of 64-bit volume (TiB): 300</i></li><li><i>Max file size in a 64-bit volume (TiB): 128</i></li><li><i style="background-color: #fcff01;">Max number of volume snapshot copies:</i></li><ul><li><i style="background-color: #fcff01;">Volume: 1023</i></li><li><i>Node: 1023000</i></li><li><i>HA-Pair: 2046000</i></li></ul></ul></ul><li><i>[6] </i><i style="background-color: #fcff01;">VMFS5 / VMFS-6: Maximum </i><i><span style="background-color: #fcff01;">File size 62TB</span> (less than the ONTAP max file size)</i></li></ul></div><div><br /></div><div><b><u>[2][3] Microsoft SQL Server Database Storage Layout with SnapCenter</u></b></div><div><b><u><br /></u></b></div><div><div><i>SnapCenter best practice considerations for Microsoft SQL Server database layout are aligned with the suggested Microsoft SQL Server deployment. SnapCenter supports backup only of user databases that reside on a NetApp storage system. Along with the performance benefit of segregating user database layout into different volumes, SnapCenter also has a large influence on the time required to back up and restore. <span style="background-color: #fcff01;">Separate volumes for data and log files significantly improve the restore time as compared to a single volume hosting multiple user data files.</span> Similarly, user databases with I/O-intensive applications might experience increased backup time.</i></div><div><i><br /></i></div><div><i>When backing-up databases with SnapCenter, take the following considerations into account:</i></div><div><ul style="text-align: left;"><li><span style="background-color: #fcff01;"><i><b>Databases with I/O intensive queries</b> throughout the day should be isolated in different volumes and eventually have separate jobs to back them up.</i></span></li><li><span style="background-color: #fcff01;"><i><b>Large databases and databases that have minimal RTO</b> should be placed in separate volumes for faster recovery.</i></span></li><li><i><span style="background-color: #fcff01;"><b>Small to medium-size databases</b> that are less critical or that have fewer I/O requirements should be consolidated into a single volume.</span> Backing up many databases residing in the same volume results in fewer Snapshot copies to be maintained. NetApp also recommends consolidating Microsoft SQL Server instances to use the same volumes to control the number of backup Snapshot copies taken.</i></li><li><i>Create separate LUNs to store full text-related files and file-streaming-related files.</i></li><li><span style="background-color: #fcff01;"><i>Assign a separate LUN for each instance to store Microsoft SQL server log backups. The LUNs can be part of the same volume.</i></span></li><li><i>System databases store database server metadata, configurations, and job details; they are not updated frequently. <span style="background-color: #fcff01;">System databases and tempdb should be placed in separate drives or LUNs.</span> <span style="background-color: #fcff01;">Do not place system databases in same volume as user databases.</span> User databases have different backup policies and the frequency of user database backups is not same as for system databases.</i></li><li><i>With Microsoft SQL Server AG setup, the data and log files for replicas should be placed in an identical folder structure on all nodes.</i></li></ul></div></div><div><b><u>[2][3] Best Practices</u></b></div><div><br /></div><div>Note: Not listing all the best practices from [3].</div><div><br /></div><div><div><i>The following are (some) NetApp recommendations on volume design for optimal performance:</i></div><div><ul style="text-align: left;"><li><i>Use flexible volumes to store Microsoft SQL Server <span style="background-color: #fcff01;">database files</span> and <span style="background-color: #fcff01;">do not share volumes between hosts.</span></i></li><li><i>Use NTFS mount points instead of drive letters to avoid the 26-drive letter limitation in Microsoft Windows Server. </i><i>When using volume mount points, NetApp recommends giving the volume label the same name as the mount point.</i></li><li><i>Disable storage Snapshot copy schedules and retention policies. Instead, use the SnapCenter for SQL Server plug-in to coordinate Snapshot copies of the Microsoft SQL Server data volumes.</i></li><li><i>Microsoft SQL Server uses the system database <span style="background-color: #fcff01;">tempdb</span> as a temporary workspace, especially for I/O intensive database consistency checker (DBCC) CHECKDB operations. Therefore, <span style="background-color: #fcff01;">place this database on a dedicated volume with a separate set of spindles. In large environments where volume count is a challenge, you can consolidate tempdb into fewer volumes and store it in the same volume as other system databases</span>. This procedure requires careful planning. Data protection for tempdb is not a high priority because this database is re-created every time the SQL Server is restarted.</i></li><li><i><span style="background-color: #fcff01;">Place user data files (.mdf) on separate volumes because they are random read/write workloads. It is common to create transaction log backups more frequently than database backups. For this reason, place transaction log files (.ldf) on a separate volume or VMDK from the data files so that independent backup schedules can be created for each.</span> This separation also isolates the sequential write I/O of the log files from the random read/write I/O of data files and significantly improves Microsoft SQL Server performance.</i></li></ul></div><div><b><u>Database layout considerations and best practices:</u></b></div><div><br /></div><div>1 - Database layout considerations</div><div><br /></div><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg1lIKR66aDsTATUOPz8yCswrywJilHJ9wYJCDZEp2CCY5BvWY-UYwimxDX5KCdOP_ZXXCDr4LexLZD-U0nq140uqqY69Nj-JQoKtf2i5ofqNbVOn_ekEwDiZCMr8KZ9Ad_200czo-4LPddmyFO_FcYNoq9-sOHcb_VtnBy5dWU5VGxiW8rFSgL2uljllvl/s1804/1%20-%20Database%20layout%20considerations.png" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="757" data-original-width="1804" height="168" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg1lIKR66aDsTATUOPz8yCswrywJilHJ9wYJCDZEp2CCY5BvWY-UYwimxDX5KCdOP_ZXXCDr4LexLZD-U0nq140uqqY69Nj-JQoKtf2i5ofqNbVOn_ekEwDiZCMr8KZ9Ad_200czo-4LPddmyFO_FcYNoq9-sOHcb_VtnBy5dWU5VGxiW8rFSgL2uljllvl/w400-h168/1%20-%20Database%20layout%20considerations.png" width="400" /></a></div><div class="separator" style="clear: both; text-align: left;"><ul style="text-align: left;"><li><i>Having data and log on same volume reduces administrator complexity.</i></li><ul><li><i>Data and log should still be places on separate LUNs (or VMDKs)</i></li></ul><li><i>For mission-critical database, spread multiple data files and log files across individual volumes; this increases overall IOPS and reduces latency.</i></li><li><i>Having dedicated volumes helps faster restore with ONTAP Snapshot-based backup/recovery.</i></li><li><i>Log backup directory should be placed on separate volume.</i></li></ul></div><div class="separator" style="clear: both; text-align: left;">2 - Database layout best practices</div><div><br /></div><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgDOxSYT7MkWlMm-yLygYB2zGoHjrsEApLEUK9CP03NRjBUOFOn17Ahzn70laUnUHbssRCDFsiindpV4Xa3RCpsV0xzzX_Xhe5PYfO_U8HujwL7fdkTn4SbhwXL5I6zDqs0Z2Q40kWnRgG_as-E474wWY9aVZQFokpkrfgMKLr4r3yUQdG-_2B1-SemlqzT/s1372/2%20-%20Database%20layout%20best%20practices.png" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="832" data-original-width="1372" height="243" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgDOxSYT7MkWlMm-yLygYB2zGoHjrsEApLEUK9CP03NRjBUOFOn17Ahzn70laUnUHbssRCDFsiindpV4Xa3RCpsV0xzzX_Xhe5PYfO_U8HujwL7fdkTn4SbhwXL5I6zDqs0Z2Q40kWnRgG_as-E474wWY9aVZQFokpkrfgMKLr4r3yUQdG-_2B1-SemlqzT/w400-h243/2%20-%20Database%20layout%20best%20practices.png" width="400" /></a></div><div><ul style="text-align: left;"><li><i>Data File and Log File on different flexvols = Faster restores + eases disaster recovery and cloning purpose.</i></li><li><i>Data File and Log File on different LUNs in same flexvol - Faster restores + fast disaster recovery and cloning purpose & better consolidation</i></li><li><i>Data Files on same LUN and Log Files on same LUN in same flexvol - Better manageability and consolidation + not recommended for large production databases + in-place restore is not as fast.</i></li></ul><div><b><u>Old Articles of Small Interest</u></b></div></div></div><div><ul style="text-align: left;"><li><a href="https://kb.vmware.com/s/article/1002951">Tips for configuring Microsoft SQL Server in a virtual machine (1002951) (vmware.com)</a></li><ul><li><i>In a virtual machine, create one (or more) .vmdk(s) for data and another for logs.</i></li></ul><li><a href="https://community.netapp.com/t5/Data-Backup-and-Recovery/Volume-and-Datastore-configuration-for-SQL-Server-VM-s-using-VMDK-s/m-p/72895">Volume and Datastore configuration for SQL Server VM's using VMDK's - NetApp Community</a></li><ul><li><i>"If we mix the VMDK's for several SQL Servers into a single Datastore, then we will need to offset the snapshot schedules for those SQL Servers, so they do not conflict with each other."</i></li></ul></ul><div><b><u>My Take</u></b></div></div><div><i><br /></i></div><div>If you're going to end up with one datafile in one VMDK in one VMware NFS datastore, consuming 1 of your 256 datastores, it seems a bit pointless, and using in-guest iSCSI would make more sense.</div><p></p>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-4270346497183643494.post-84177881936872751032023-07-24T03:16:00.002-07:002023-07-24T03:16:38.440-07:00Disable Automatic Broadcast Domain Creation?<p>Q: Can you disable Automatic Broadcast Domain creation?</p><p>A: No.</p><p><i>Automatic Broadcast Domain creation - actually - Auto Port Placement - was introduced in ONTAP 9.8. Whilst I never had any problem creating Broadcast Domains manually, I understand why the feature was introduced, and it is a cool feature if you can learn to work with it (which is something I've not got used to yet, I just <b>broadcast-domain delete</b> the auto generated stuff - I'm a bit of dinosaur! π)</i></p><p><b><u><span style="font-size: large;">ONTAP 9.8: Auto Port Placement</span></u></b></p><p><a href="https://docs.netapp.com/us-en/ontap/networking/network_features_by_release.html">Network features by release</a></p><p><i>ONTAP can automatically configure broadcast domains, select ports, and help configure network interfaces (LIFs), virtual LANs (VLANs), and link aggregation groups (LAGs) based on <span style="background-color: #fcff01;">reachability</span> and network topology detection.</i></p><p><i>When you first create a cluster, ONTAP automatically discovers the networks connected to ports and configures the needed broadcast domains based on layer 2 reachability. You no longer have to configure broadcast domains manually.</i></p><p><i>... depending on your network topology, ONTAP configures additional broadcast domains as needed: Default-1, Default-2, and so on. You can rename these broadcast domains if desired, but do not modify which ports are configured in these broadcast domains.</i></p><p><i>When you configure network interfaces, the home port selection is optional. If you do not manually select a home port, ONTAP will attempt to assign an appropriate home port in the same broadcast domain as other network interfaces in the same subnet.</i></p><p><i>When creating a VLAN or adding the first port to a newly created LAG, ONTAP will attempt to automatically assign the VLAN or LAG to the appropriate broadcast domain based on its layer 2 reachability.</i></p><p><i>By automatically configuring broadcast domains and ports, ONTAP helps to ensure that clients maintain access to their data during failover to another port or node in the cluster.</i></p><p><b><u><span style="font-size: large;">Skip Broadcast Domain Placement</span></u></b></p><p>If you are creating VLAN ports, there is this flag for:</p><p><span style="font-family: courier;">network port vlan create</span></p><p><span style="font-family: courier;">[-<span style="background-color: #fcff01;">skip-broadcast-domain-placement</span> [true]] - Skip Placement Into Broadcast Domain (privilege: advanced) When specified, the VLAN will not be placed into any broadcast domain.</span></p><div><b><u><span style="font-size: large;">Monitor the Reachability of Network Ports in ONTAP 9.8 and Later</span></u></b></div><div><br /></div><div><a href="https://docs.netapp.com/us-en/ontap/networking/monitor_the_reachability_of_network_ports.html">Monitor the reachability of network ports in ONTAP 9.8 and later</a></div><div><br /></div><div>Useful commands in the above article:</div><div><br /></div><div><span style="font-family: courier;">network reachability show</span></div><div><span style="font-family: courier;">network port reachability repair -node -port</span></div><div><br /></div><div><b><u><span style="font-size: large;">Repair port reachability</span></u></b></div><div><br /></div><div><a href="https://docs.netapp.com/us-en/ontap/networking/repair_port_reachability.html#lifs">Repair port reachability</a></div><div><br /></div><div>Useful commands in the above article:</div><div><br /></div><div><span style="font-family: courier;">network port reachability show -detail -node -port</span></div><div><span style="font-family: courier;"><br /></span></div><div><span style="font-family: courier;">displaced-interface show</span></div><div><span style="font-family: courier;">displayed-interface restore</span></div><div><span style="font-family: courier;">displayed-interface delete</span></div><div><span style="font-family: courier;"><br /></span></div><div><span style="font-family: courier;">displaced-vlans restore</span></div><div><span style="font-family: courier;">displaced-vlans delete</span></div><div><br /></div><div><b><u><span style="font-size: large;">In Reflection</span></u></b></div><div><br /></div><div>I may have learned to love automatic broadcast domain creation. Recently, I added a load of VLANs to some IFGRPs, and they magically auto-created the perfect broadcast domains, all I had to do was rename them π</div><div><br /></div><div class="separator" style="clear: both; text-align: left;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgZlT9uoU-cb7gI7lAn2b6UBCvMX_s5ISSdb0cBXCv9nZLeeKvzisZHhZup8K4UDbxIygibrHJiXS59t8R-qptXy0G-78RdUajkKfO-TlsjuXf5JFNL4gaQMBTAGMRBkCBGGKiVRseDkn6qY9o-mC_N5XkCcgbnzw2RiTMLYaOTIKucpRAB2HOdS_Rz5bEV/s637/ONTAP-9-Continuous-Innovation.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="561" data-original-width="637" height="176" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgZlT9uoU-cb7gI7lAn2b6UBCvMX_s5ISSdb0cBXCv9nZLeeKvzisZHhZup8K4UDbxIygibrHJiXS59t8R-qptXy0G-78RdUajkKfO-TlsjuXf5JFNL4gaQMBTAGMRBkCBGGKiVRseDkn6qY9o-mC_N5XkCcgbnzw2RiTMLYaOTIKucpRAB2HOdS_Rz5bEV/w200-h176/ONTAP-9-Continuous-Innovation.png" width="200" /></a></div>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-4270346497183643494.post-72323303179100801722023-07-17T07:32:00.000-07:002023-07-17T07:32:09.775-07:00Comparing ONTAP P Releases<p>A more recent <a href="https://docs.netapp.com/us-en/ontap/upgrade/concept_upgrade_paths.html#types-of-upgrade-paths">NetApp Best Practice</a> states:</p><p><i>βIt is a best practice to <span style="background-color: #fcff01;">upgrade first to the latest patch release in the same ONTAP release family</span> and then upgrade to the next supported major release. This will ensure that any issues in your current version of ONTAP are resolved before upgrading.β</i></p><p>The minimum recommended ONTAP releases are listed <a href="https://kb.netapp.com/Support_Bulletins/Customer_Bulletins/SU2">here</a>.</p><p><i>As of June 22, 2023, the published minimum recommended ONTAP/Data ONTAP releases on the NetApp Support Site for releases still in full support are as follows:</i></p><p></p><ul style="text-align: left;"><li><i>For ONTAP 9.12x, the minimum recommended version is <b>9.12.1P4.</b></i></li><li><i>For ONTAP 9.11x, the minimum recommended version is <b>9.11.1P8.</b></i></li><li><i>For ONTAP 9.10x, the minimum recommended version is <b>9.10.1P12.</b></i></li><li><i>For ONTAP 9.9x, the minimum recommended version is <b>9.9.1P15.</b></i></li><li><i>For ONTAP 9.8x, the minimum recommended version is <b>9.8P18.</b></i></li><li><i>For ONTAP 9.7x, the minimum recommended version is<b> 9.7P22.</b></i></li></ul><div>Say you're on 9.10.1P9. You're thinking<i> "do I really need to upgrade to P12 before I start my upgrade to 9.12.1P4!?"</i></div><div><br /></div><div>Personally, I don't think it's necessary. 9.10.1P9 is just over 6 months old (at the time of writing), so the cluster has had an upgrade in the last year or so. The best practice statement feels more geared towards systems that haven't been upgraded for well over a year. And it makes sense in those cases to do the ONTAP upgrade to the latest P-release first.</div><div><br /></div><div>If you want to check there aren't any upgrade related bugs in the interim releases, you can do like this:</div><div><br /></div><div><div><i>Compare 9.10.1P9 and 9.10.1P12 bug fixes:</i></div><div><i><br /></i></div><div><i><a href="https://mysupport.netapp.com/site/bugs-online/release-comparison/product/ONTAP?version1=9.10.1P9&version2=9.10.1P12&type=fixed">https://mysupport.netapp.com/site/bugs-online/release-comparison/product/ONTAP?version1=<span style="background-color: #fcff01;">9.10.1P9</span>&version2=<span style="background-color: #fcff01;">9.10.1P12</span>&type=fixed</a></i></div></div><div><br /></div><div><div><i>You can also compare bundled firmware from 9.10.1P9 versus 9.10.1P12:</i></div><div><i><br /></i></div><div><i><a href="https://aiq.netapp.com/system-firmware/patch/9.10.1P9">https://aiq.netapp.com/system-firmware/patch/<span style="background-color: #fcff01;">9.10.1P9</span></a></i></div><div><i><a href="https://aiq.netapp.com/system-firmware/patch/9.10.1P12">https://aiq.netapp.com/system-firmware/patch/<span style="background-color: #fcff01;">9.10.1P12</span></a></i></div></div><div><br /></div><div><br /></div><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgQzvf-Jc1DfBwg1_gk_amo7TLxLRlxLKOWJjpPJ4evYOkynnughdHeN-TcjsMzdXjSkDIrN4_nDy2rZw866wgxxwNDGjW2Y2HVufa90dSbOuF6oATYp266n6HBjVMo23n35rzNF5ABTrLDvs6F9_7-HrQiQD0R-mBHFJlYF_l2yyLoR2AfFbGQtGN6P6Fj/s637/ONTAP-9-Continuous-Innovation.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="561" data-original-width="637" height="176" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgQzvf-Jc1DfBwg1_gk_amo7TLxLRlxLKOWJjpPJ4evYOkynnughdHeN-TcjsMzdXjSkDIrN4_nDy2rZw866wgxxwNDGjW2Y2HVufa90dSbOuF6oATYp266n6HBjVMo23n35rzNF5ABTrLDvs6F9_7-HrQiQD0R-mBHFJlYF_l2yyLoR2AfFbGQtGN6P6Fj/w200-h176/ONTAP-9-Continuous-Innovation.png" width="200" /></a></div><p></p>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-4270346497183643494.post-19758389739507940162023-07-17T01:54:00.001-07:002023-07-17T03:04:39.839-07:00Types of Always-On Microsoft SQL Server and Supported Storage<p>There are two types of Always-On Microsoft SQL Server:</p><p></p><ol style="text-align: left;"><li>Always-On FCI (Failover Cluster Instance)</li><li>Always-On Availability Group</li></ol><p></p><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhnJl_kPsmgi26OkeSZhRAKsWInR5YGQnvxVz-_wE5gJGoG1nu1ZynYtjSz4vJ7sZfSsCvGwDcnOm1iAdLc-HJgNUXp5xVLP2iHz9fqil01Kqi9ztFRA_MYH9n9kFl80CGFZY5VRPewioEmzTuwOg_Q9F1tuh0iCURGCwiIwvWwzsnj-Ml5aQ-mzJiC8a9i/s901/Microsoft%20SQL%20Server%20Always-On.png" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="568" data-original-width="901" height="253" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhnJl_kPsmgi26OkeSZhRAKsWInR5YGQnvxVz-_wE5gJGoG1nu1ZynYtjSz4vJ7sZfSsCvGwDcnOm1iAdLc-HJgNUXp5xVLP2iHz9fqil01Kqi9ztFRA_MYH9n9kFl80CGFZY5VRPewioEmzTuwOg_Q9F1tuh0iCURGCwiIwvWwzsnj-Ml5aQ-mzJiC8a9i/w400-h253/Microsoft%20SQL%20Server%20Always-On.png" width="400" /></a></div><br /><p>From a storage perspective, the key point is:</p><ol style="text-align: left;"><li>Always-On FCI (Failover Cluster Instance)</li><ul><li><span style="background-color: #fcff01;">Uses shared disk.</span></li></ul><li>Always-On Availability Group</li><ul><li><span style="background-color: #fcff01;">Does not use shared disk.</span></li></ul></ol><div><br /></div><div>1) If using the "shared disk" model, then, according to this VMware KB -</div><div><br /></div><div><a href="https://kb.vmware.com/s/article/79616">Microsoft Windows Server Failover Clustering (WSFC) with shared disks on VMware vSphere 7.x: Guidelines for supported configurations (79616)</a></div><div><br /></div><div>And the table in the Storage Configuration section - <span style="background-color: #fcff01;">Clustered VMDKs are only supported on FC</span>; and vVols or RDM physical mode, only with FC, FCoE and iSCSI.</div><div><br /></div><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgj4hwMyc_QmyBYYqZIhD4nffIInE_lprkdES23mE_-7H0nCsaXxzRKc3SDthYKZu4Wg7tsBZJl4f6kq23Cl66NLV0UqJL9A_oMYqV8dilT4TdocrEg_-pv1Ico0mCqeysNj5Kt31WIYLJiKL_YxMqQPxsdC6V9PcT2Jr3XfOT8DFl3IoLJQGZQmoZktUHW/s1008/Supported%20Storage%20Configuration%20Options.png" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="424" data-original-width="1008" height="169" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgj4hwMyc_QmyBYYqZIhD4nffIInE_lprkdES23mE_-7H0nCsaXxzRKc3SDthYKZu4Wg7tsBZJl4f6kq23Cl66NLV0UqJL9A_oMYqV8dilT4TdocrEg_-pv1Ico0mCqeysNj5Kt31WIYLJiKL_YxMqQPxsdC6V9PcT2Jr3XfOT8DFl3IoLJQGZQmoZktUHW/w400-h169/Supported%20Storage%20Configuration%20Options.png" width="400" /></a></div><div><br /></div><div><i>Note: In-quest iSCSI is not mentioned in this table (since it is storage external to VMware), but it is another option and very commonly used, if you want a clustered/shared disk.</i></div><div><br /></div><div>2) If using the "no shared disk" model, then any storage (VMware datastore type) is fine - NFS, iSCSI and FC. And this has been true for a long time. See this March 4, 2015 article:</div><div><br /></div><div><a href="https://www.joshodgers.com/2015/03/04/sql-alwayson-availability-group-support-in-vmdks-on-nfs-datastores/">SQL AlwaysOn Availability Group support in VMDKs on NFS Datastores | CloudXC (joshodgers.com)</a></div><div><br /></div><div><i>"As a result, <span style="background-color: #fcff01;">SQL Always-On Availability Group non shared disk deployments are supported by VMware when deployed in VMDKs on NFS datastores</span> (as are Exchange DAG deployments).</i></div><div><i><br /></i></div><div><b><u>NetApp SnapCenter Support</u></b></div><div><ul style="text-align: left;"><li>SnapCenter supports the shared-disk model (1) with Virtual Machines with in-guest iSCSI.</li><li>SnapCenter supports the non-shared disk model (2) with VMDKs on NFS/iSCSI/FC datastores, and in-guest iSCSI.</li></ul></div><div><i>Note: Please check with NetApp if I've not mentioned your specific setup above.</i></div>Unknownnoreply@blogger.com0