2013-12-01 09:47 PM
I have some problem with the build in command "Create Volume" (C-Mode).
1. Create export policy primary - works fine
2. Create export rule primary - works fine
3. Create volume primary (type rw) - works fine
4. Create export policy secondary - works fine
5. Create export rule secondary - works fine
6. Create volume secondary (type dp) - works particular: junction path is not set
Attached you can find a screenshot of the attributes for the Create Volume.
Any ideas on this?
Solved! SEE THE SOLUTION
2013-12-02 01:05 AM
the code of the Create Volume command sets the junction path to $null (so it is not mounted into the namespace) for all volumes that are not of type rw. This is probably based on the assumption that you don't want to to configure access on DR mirrors. However, it is a best practice to pre-mount DR volumes so this should probably be changed in WFA, - I'll try to bring this up with the right people.
There are two possible solutions:
Hope this helps
2013-12-02 03:48 AM
A bug has been filed in this respect, bug number 779918. Kindly create a netapp support case and add it to the same.
In the mean time pls use hendriks second suggestion "Add the Mount Volume command as an additional step to your workflow"
2013-12-03 10:03 PM
I assume you fixed your workflow by adding a "Mount Volume" command to the workflow. Did you do it after the SnapMirror initialization was completed ?
We have seen cases where an immediate mounting after 'dp' volume creation could lead to messages like:
f3270-208-238-239-240-241::> volume mount -vserver vs_name -volume snow1_mirror001 -junction-path /dataflake
Error: command failed: Volume snow1_mirror001 in Vserver "vs_name" is not mountable until a "snapmirror initialize" has been completed.
2013-12-03 10:07 PM
I have the step mount volume after the create snapmirror command.
Sometimes when the snapmirror has not finished the initialization und must resume the workflow.
I have had this only twice.
2013-12-03 10:18 PM
Just curious. How big were your volumes? Will your workflow start failing more often if the volume is big and initialization takes longer? Something to consider and perhaps add "Wait for snapMirror" command in the middle.