Hello, to enable SnapLock with the "ability to create SnapLock and non-SnapLock volumes on the same aggregate" we need to upgrade our system (now 9.9.1P16) at minimum to 9.10.1, we have now in place SDU and SMO on Solaris (both 10 and 11) and all works fine... because SDU is EOS from 30-Mar-2020 and SMO from 31-Aug-2022 the IMT doesn't show me nothing.... "Based on your criteria, IMT could not find any results" Someone have been tested the compatibility with latest version of SDU and SMO with Ontap 9.10.1 or better 9.11.1 ? I have already post a question regarding the IMT... why, even if the products is EOF, Netapp have removed the "old" compatibility of SDU and SMO? someone like me still use these products !!! Many thanks Federico
... View more
All, When attempting an Exchange restore operation in SnapCenter, does the original DB get overwritten in the end? If yes, is it possible to mount the DB from snapshot as an RDB (Recovery Database) to restore content, as opposed to having to replay logs (that may not be available), etc? Thanks!
... View more
Hello, During SC 4.4P1 installation, SC package installation was successful and in later step MySQL installation also successful however, it is filed to "SET PASSWORD: Exception: Can't connect to MySQL server on 'localhost' (10061): No connection could be made because the target machine actively refused it 127.0.0.1:3306" and rolled back the installation. Port 3306 is opened on the server, I have tested by installing the MySQL separately on the server and it was installed successfully. But when it come during SC installation, fails with the above error. I have attached the installation log for your reference. any clue on the issue here.?
... View more
Sometimes SnapCenter SQL Server DB clone fails on: Activity 'Application Clone' failed with error: Failed to refresh the clone. Only user processes can be killed.
... View more
First I would like to say that SVM-DR is the greatest thing since slided bread. (Okay, sandwich bread). When I first read and implemented it, it made life so much easier, because, it automated the entire business continuance and backup and recovery process. (Having to clone to a new RW volume wasn't as much trouble with FlexClones and I've been able to recover data for my users and admin groups perfectly). Now I've come to the Lifecycle end of the source SVM. Wouldn't you know management wants to, a) end volume lifecycle in a staggered fashion, b) they want to maintain an archive in the destination for the volumes at end-of-life for a year or two. Here is the issue: SVM-DR does not allow you to take destination volumes out of the cycle. With SVM-DR, it is all or nothing according to Support. That is not very smart; after committing to SVM-DR's promises we find that it is a bear. Support suggests moving the source-volume to a new archival SVM and creating a new volume SnapMirror. Kind of defeats the purpose of having a single point of Backup/DR-BC. Now, I did find that you can get around that, but no thanks to NetApp. It is a process I discovered after a few weeks of playing around. But I think the Project Manager should be made aware that SVM-DR is positioned as a single point of DR, BC, SnapVault-Backup. It should allow for movement of both source and destination volumes, even if that means converting from an SVM-DR to a Volume-SM policy. I hope this message reaches the proper ONTAP Protection Managers.
... View more
