SnapDrive makes connecting servers to the SAN a doddle (this can be a PITA in Windows-land, I don't have much experiance on other platforms with SD) and I believe it also provides API's leveraged by some other SnapManager products to take snapshots.
It also makes resizing LUN's, disconnecting and reconnecting LUN's and snapshots really easy.
Cheers, Raj.
On Fri, Apr 9, 2010 at 11:48 AM, Page, Jeremy jeremy.page@gilbarco.comwrote:
It looks like we’re getting funding for our DR project. The bare bones are using snapmirror to replicate an Oracle DB offsite alone with a few dozen front end/infrastructure VMs. Two of the items we’ve been quoted by our vendor are SnapDrive & SnapRestore. I can understand snaprestore but why would I need snapdrive at the DR site? I don’t even use it at our primary site, the Oracle system is very static, we do not have the hardware capacity to run a cloned instance and I’m comfortable with scripting a snapshot. I tried reading NetApp’s SnapDrive documenthttp://media.netapp.com/documents/snapdrive.pdfand it looks like it will do every buzzword under the sun but I have no idea what it really gets me other than the ability to see/control snapshots from the server – which I don’t want. In addition it breaks the KISS idea which is important, especially since this system will be in another geographical location and not have as many eyes on it as a live system would.
Am I missing something?
Please be advised that this email may contain confidential information. If you are not the intended recipient, please notify us by email by replying to the sender and delete this message. The sender disclaims that the content of this email constitutes an offer to enter into, or the acceptance of, any agreement; provided that the foregoing does not invalidate the binding effect of any digital or other electronic reproduction of a manual signature that is included in any attachment.