Skip to content

Commit 32c4d5f

Browse files
committed
Added the ability to read in the partnersTable from a DynamoDB.
1 parent 0cc8210 commit 32c4d5f

File tree

1 file changed

+1
-0
lines changed
  • Management-Utilities/auto_create_sm_relationships

1 file changed

+1
-0
lines changed

Management-Utilities/auto_create_sm_relationships/README.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -27,6 +27,7 @@ There are a few things you need to do in order to get this script to run properl
2727
- partnerSvmSourceName - Is the "peered name" of the source SVM. Usually, it is the same as the source SVM, but can be different if that same name already exists on the partner file system. When you peer the SVM it will require you to create an alias for the source SVM so all the SVM names are unique.
2828

2929
**NOTE:** Instead of defining the partnersTable in the script, you can define dynamodbPartnersTableName and dynamodbRegion and the script will read in the partner information from the specified DynamoDB table. The partners table should have the following fields:
30+
3031
- soureceId - Which is the concatentation of the source file system ID followed by a ":" followed by the SVM name. It is done this way because the id has to be unique in the table. It is split up into its two components in the script when it is read in.
3132
- partnerFsxnIp - Set to the IP address of the management port of the partner FSxN file system.
3233
- partnerSvmName - The name of the SVM where you want the SnapMirror destination volume to reside.

0 commit comments

Comments
 (0)