RE: NetApp SnapManager for Oracle

From: Andre van Winssen <>
Date: Thu, 22 Jan 2009 09:18:40 +0100
Message-ID: <006b01c97c6a$088d10d0$19a73270$_at_com>

Hi Alex,

I believe that version 2 is not very good, the guy next to me had been testing it last year and I heard lots of complaints from him about integration with rman and restoring the archive logs from online backups. Version 3, which is not out there I believe, seems more promising. Below's a list of new features in version 3.0 of snap manager for oracle:

Policy-based data protection via integration with Protection Manager (UNIX only)
Automates replicating backups from Primary to Secondary/DR storage via SnapMirror/SnapVault
Automates restoring backups from Secondary/DR storage Automates cloning of protected backups on Secondary/DR storage RBAC integration (UNIX only)
Implemented via integration with Operations Manager/DFM Fast restores using volume-based SnapRestore (UNIX only) Ability to perform full volume restores of volumes containing datafiles Built-in scheduler to schedule backups from the GUI User defined Snapshot naming support
Cloning policies and pre/post tasks
Automates implementing business policies, running scripts before and after the cloning process
Simplified clone wizard
Multiple profiles update capability
Ability to do parallel operations in the GUI Most operation wizards have a new button to allow that operation to run in the background.
This will help DBAs perform multiple operations in parallel when using the GUI
New tab to monitor operations
Support for Oracle ASM on NFS
Support for Oracle ASM on AIX and HP-UX
Previous restriction of single file system per volume group removed SnapManager GUI can now be launched on all supported platforms


-----Original Message-----

From: [] On Behalf Of Alex Gorbachev
Sent: donderdag 22 januari 2009 1:30
To: ORACLE-L Freelists
Subject: NetApp SnapManager for Oracle

Hi all,

Any experience with subject product from NetApp? How stable? How useful you found it?


-- Received on Thu Jan 22 2009 - 02:18:40 CST

Original text of this message