Yes, I more or less expected it. FIle clone (as opposed to LUN clone) requires FlexClone license in 7-Mode as well (but at least you see it clearly stated in documenation). Looks like you are stuck; the only remaining option is to snapmirror to another volume to make LUN writable. There is small chance you will be able to mount LUN on read-only device; I think it may work, but I do not know how to present LUN inside snapshot to host directly ...
... View more
I am afraid I do not quite understand what you try to do. Could you outline your config, like "you have volume A that is snap mirrored to volume B and you want to SnapVault B to C" or similar. At least, that is how I understood you initially.
... View more
In 7-Mode you can create writable LUN clone using "LUN clone" command; it does not require any additional license. In C-Mode equivalent command would be "volume file clone"; unfortunately, cDOT documentation leaves much to be desired and manages to never say whether it needs FlexClone license. Give it a try.
... View more
In 7-mode you configure primary SnapVault schedule on SnapMirror source (assuming VSM). SnapVault secondary does not care, where snapshots come from - it simply fetches snapshots with specific name(s). Of course you need adjust schedules so SnapVault transfer runs after SnapMirror transfer in complete.
... View more
SID history requires trusted relationships between domains; at least that is written in all documents I have seen. I am curious whether this is hard requirement or simply limitation of existing tools.
... View more
The procedure given in 1013517 seems too simple. It basically boils down to Loader option 7. ("Install new software first.") No. It boils down to setting correct environment variables and reinstalling. Eveything else are extra steps. If you do not know whether you can skip them - follow article to the letter.
... View more
There are version checks in the install scripts, so even going the destructive route and running it all from option 7 some of those hops are probably going to be enforced. Now I became really curious. What can be checked here? The only dependency could be against firmware (LOADER); I had the case when FAS3170 could not netboot 8.2.1. But firmware can be updated from really any version of Data ONTAP, it is done before it loads anyway. When you netboot and go into 7, you are running exactly the same version that you are going to install so there could be no incompatibility here. Next step will be 4 where you wipe disks clean so there is nothing left to check. Could you explain what do you mean? Not arguing, just trying to learn something new 🙂
... View more
I don't need to preserve any of the data. Then I do not understand the question. You will be wiping filers clean anyway, how does it matter which version was there originally?
... View more
This thread (and others it references) may be of interest. https://social.technet.microsoft.com/Forums/windowsserver/en-US/741fd4e1-be15-46df-a052-ecd3616176cc/add-sid-to-sidhistory-ad-attribute?forum=winserverDS
... View more
You have triple disk failure. Your only option is to try to bring disk that failed last online and hope it will allow reconstruction to complete. Do not attempt to unfail disk from Data ONTAP. It will make it spare and unsuitable for reconstruction. Open case with NetApp and let them guide you. It is very easy to lose data in this situation.
... View more
I am trying to manually create a snapmirror relationship between a 7-mode 8.01 array and an CDoT 8.3RC1 array. It is not supported except for transition. And yes, 8.3 does not support 32 bit aggregates so you must convert source to 64 bit first before you can initiate transitional relationship.
... View more