-----Original Message----- From: Odhner, Christian Sent: Wednesday, April 07, 2004 11:00 AM To: Gole, Abhijeet; c-dl-snapmirror Subject: RE: SnapMirror and Qtrees
renamed /vol/vol1/MySpace (or My_Space) for snapmirror to work. Before I change the names of 86 qtrees and their corresponding DFS share pointers, I'm hoping that someone can tell me that NetApp was incorrect
While Colin or someone else can comment on the current state of the bug and any workarounds, I should point out that even if there is no current workaround, the customer does NOT need to change his DFS pointers.
Just change the qtree names, and change the CIFS share mappings on the filer side so that the same (old) share names point to the new (no-space) qtree names. Share names and Qtree names don't have to match, so client reconfiguration of any sort can be avoided pretty easily.
-Chris
-----Original Message----- From: Haber, David J. [mailto:david.haber@fahc.org] Sent: Wednesday, April 07, 2004 10:34 AM To: toasters@mathworks.com Subject: SnapMirror and Qtrees
I have been told by NetApp support that you cannot, at this time, snapmirror qtrees that have spaces in their name. That is, a qtree with the path /vol/vol1/My Space cannot be snapmirrored. It would have to be renamed /vol/vol1/MySpace (or My_Space) for snapmirror to work. Before I change the names of 86 qtrees and their corresponding DFS share pointers, I'm hoping that someone can tell me that NetApp was incorrect and there is a way to snapmirror qtrees with spaces in their names. Or, can someone at NetApp who might be readin this give me an idea when the bug (86447) will be fixed.