Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
How do I specify an existing SnapShot Policy with the Create CM Volume command? It expects a reference to Snapshot_Policy. I see CM Snapshot policy in the dictionary, but there are no filters for it. I tried to create one, but I get a message that table "cm_storage.snapshot_policy" doesn't exist.
So how do I map from the name of an existing SnapShot policy to a reference to use on the Create command?
Thanks.
Solved! See The Solution
1 ACCEPTED SOLUTION
migration has accepted the solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Currently in WFA, Snapshot Policies are not cached(in the dictionary you can see none of attributes are selected for caching), as OCUM does not discover these objects, and that's why you are seeing this "table doesn't exist" error.
In future releases, we will try to cache this if there is support from OCUM..!
But for now, to use the existing snapshot policy follow the below steps,
1) Clone the command "No-Op Cluster-Mode" and add the below piece of code in that
[parameter(Mandatory=$false, HelpMessage="Snapshot Policy Name")]
[string]$SnapshotPolicyName
2) And, map this parameter to cm_storage.Snapshot_Policy.name in the Parameters Mapping tab and save it
3) Use this command in your workflow before the "Create CM Volume" command
4) Provide your Snapshot_Policy name in "No_Op Cluster-Mode" command details, as shown in attachment.
5) Use the above reference in your create volume command details.
For your reference I have attached the DAR file here..!
Hope this helps..!
Warm Regards
Sivaprasad K
2 REPLIES 2
migration has accepted the solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Currently in WFA, Snapshot Policies are not cached(in the dictionary you can see none of attributes are selected for caching), as OCUM does not discover these objects, and that's why you are seeing this "table doesn't exist" error.
In future releases, we will try to cache this if there is support from OCUM..!
But for now, to use the existing snapshot policy follow the below steps,
1) Clone the command "No-Op Cluster-Mode" and add the below piece of code in that
[parameter(Mandatory=$false, HelpMessage="Snapshot Policy Name")]
[string]$SnapshotPolicyName
2) And, map this parameter to cm_storage.Snapshot_Policy.name in the Parameters Mapping tab and save it
3) Use this command in your workflow before the "Create CM Volume" command
4) Provide your Snapshot_Policy name in "No_Op Cluster-Mode" command details, as shown in attachment.
5) Use the above reference in your create volume command details.
For your reference I have attached the DAR file here..!
Hope this helps..!
Warm Regards
Sivaprasad K
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
That worked. Thank you very much.
