SnapManager® 3.0.

1 for Oracle® Release Notes

NetApp, Inc. 495 East Java Drive Sunnyvale, CA 94089 USA Telephone: +1 (408) 822-6000 Fax: +1 (408) 822-4501 Support telephone: +1 (888) 4-NETAPP Documentation comments: doccomments@netapp.com Information Web: http://www.netapp.com Part number 215-04592_A0 March 19, 2009

Copyright and trademark information

Copyright information

Copyright © 1994–2009 NetApp, Inc. All rights reserved. Printed in the U.S.A. No part of this document covered by copyright may be reproduced in any form or by any means— graphic, electronic, or mechanical, including photocopying, recording, taping, or storage in an electronic retrieval system—without prior written permission of the copyright owner. Software derived from copyrighted NetApp material is subject to the following license and disclaimer: THIS SOFTWARE IS PROVIDED BY NETAPP “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL NETAPP BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. NetApp reserves the right to change any products described herein at any time, and without notice. NetApp assumes no responsibility or liability arising from the use of products described herein, except as expressly agreed to in writing by NetApp. The use or purchase of this product does not convey a license under any patent rights, trademark rights, or any other intellectual property rights of NetApp. The product described in this manual may be protected by one or more U.S. patents, foreign patents, or pending applications. RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.277-7103 (October 1988) and FAR 52-227-19 (June 1987).

Trademark information

NetApp, the NetApp logo, the bolt design, NetApp–the Network Appliance Company, DataFabric, Data ONTAP, FAServer, FilerView, FlexVol, Manage ONTAP, MultiStore, NearStore, NetCache, SecureShare, SnapDrive, SnapLock, SnapManager, SnapMirror, SnapMover, SnapRestore, SnapValidator, SnapVault, Spinnaker Networks, SpinCluster, SpinFS, SpinHA, SpinMove, SpinServer, SyncMirror, Topio, VFM, and WAFL are registered trademarks of NetApp, Inc. in the U.S.A. and/or other countries. Cryptainer, Cryptoshred, Datafort, and Decru are registered trademarks, and Lifetime Key Management and OpenKey are trademarks, of Decru, a NetApp, Inc. company, in the U.S.A. and/or other countries. gFiler, NetApp, SnapCopy, Snapshot, and The evolution of storage are trademarks of NetApp, Inc. in the U.S.A. and/or other countries and registered trademarks in some other countries. ApplianceWatch, BareMetal, Camera-to-Viewer, ComplianceClock, ComplianceJournal, ContentDirector, ContentFabric, EdgeFiler, FlexClone, FlexShare, FPolicy, HyperSAN, InfoFabric, LockVault, NOW, NOW NetApp on the Web, ONTAPI, RAID-DP, RoboCache, RoboFiler, SecureAdmin, Serving Data by Design, SharedStorage, Simplicore, Simulate ONTAP, Smart SAN, SnapCache, SnapDirector, SnapFilter, SnapMigrator, SnapSuite, SohoFiler, SpinMirror, SpinRestore, SpinShot, SpinStor, StoreVault, vFiler, Virtual File

ii

Copyright and trademark information

Manager, VPolicy, and Web Filer are trademarks of NetApp, Inc. in the United States and other countries. NetApp Availability Assurance and NetApp ProTech Expert are service marks of NetApp, Inc. in the U.S.A. Apple is a registered trademark and QuickTime is a trademark of Apple Computer, Inc. in the United States and/or other countries. Microsoft is a registered trademark and Windows Media is a trademark of Microsoft Corporation in the United States and/or other countries. RealAudio, RealNetworks, RealPlayer, RealSystem, RealText, and RealVideo are registered trademarks and RealMedia, RealProxy, and SureStream are trademarks of RealNetworks, Inc. in the United States and/or other countries. All other brands or products are trademarks or registered trademarks of their respective holders and should be treated as such. NetApp is a licensee of the CompactFlash and CF Logo trademarks. NetApp NetCache is certified RealSystem compatible.

Copyright and trademark information

iii

iv Copyright and trademark information .

. . . . . . . . . . . . . . . . . 13 Known issues. 16 Known issues and workarounds .0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Downloading and starting the GUI using Java Web Start (Windows). . . . SnapManager overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Installing SnapManager . . . . . . .1 for Oracle . . . . . . . . . . . . . . . . . . . 16 Documentation issues . . . CLI changes . . . . . . . . . . . . . 11 Finding information on troubleshooting tips . . . . 8 Confirming system requirements. . . 23 Obtaining the latest version of the NetApp software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Accessing information about bugs . . . . . 25 Obtaining the software from NOW . . . . . . . . . . . . Release Notes 3. . . . . . . . . . . . . . . . . . . . . 25 Getting the most up-to-date SnapManager software . . . . . . . . . . . . . . . . . . . . . . 32 Table of Contents v . . . . . . . . . . . . . . . Downloading and starting the GUI using Java Web Start (UNIX) . . . . . . . . . .0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 SnapManager components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Issues resolved in SnapManager 3. . . . . . . . . . . . . . . . . . 8 System setup required to use SnapManager . . . . . Starting the GUI from the Command Line Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Table of Contents What’s New in SnapManager for Oracle?. 1 1 1 2 3 System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Starting the graphical user interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Restrictions . . . . . . . . . . . . . . New features . . . . . . 26 26 26 29 Obtaining other NetApp documentation. . . . . .1 update. . . . . . . . . 8 SnapManager installation. . . . . .

vi Table of Contents .

See “System requirements” on page 8.0.1. See “Known issues” on page 15.1 update The SnapManager 3. See “Issues resolved in SnapManager 3.0. Snapshot copies created in SnapManager 3.0.1 for Oracle is installed. DBAs can switch a primary database to a standby mode and vice versa.0 for Oracle® empowers database administrators with the tools necessary to perform policy-driven data management.0. you can backup and clone Oracle 10gR2 (10.6. ◆ ◆ ◆ ◆ ◆ ◆ What’s New in SnapManager for Oracle? 1 . Using SnapManager 3. This edition of the release notes lists the minimum 4K block size requirement for the tablespace into which SnapManager 3.1 for Oracle.0. These release notes describe the issues in V3. Using Data Guard. A workaround is also included.1 for Oracle” on page 13.2.4) physical standby databases created using Oracle Data Guard services.What’s New in SnapManager for Oracle? SnapManager overview SnapManager® 3.1 for Oracle on the primary node are being deleted incorrectly by the Protection Manager retention policy. you can create backups on primary storage and create protected backups on secondary storage.0 that were fixed in V3.1 for Oracle” on page 13. See “Restrictions” on page 11.0. Release Notes 3.1 for Oracle® Release Notes update includes the following items: ◆ The Restrictions section of the Release Notes includes information about RedHat and Oracle Enterprise Linux and the ext3 filesystem that is not supported when deploying Oracle over raw devices using dynamic multipathing (DMMP) in a multipathing IO (MPIO) environment. With SnapManager. See “Restrictions” on page 11. and create database clones for non-disruptive testing.0. The Restrictions section indicates that SnapManager for Oracle Java Web Start client requires Java 1. See “Issues resolved in SnapManager 3.5 and does not support Java 1.0 and 3. schedule and create regular database backups with minimal impact. restore data from these backups in the event of data loss or disaster. The Known Issues section now includes information about how the retention class of a backup might be different on a secondary node than on the primary node.0.0.

However.0 for Oracle supports the following new features and enhancements: ◆ Policy-driven data protection: This feature enables database administrators to protect their data to secondary storage. you might create a custom script that determines whether the complete application using the target database is shut down. With data protection enabled. New features SnapManager 3. DBAs can take advantage of a new restore preview option to review a file-by-file analysis of a restore operation before it takes place. for the 3. which uses datasets and policies to provide data protection on SnapVault and SnapMirror destinations. helping DBAs create test and development environments easily and apart from their primary production storage. See “Documentation issues” on page 23. along with the changes cited in the 3. For example. With SnapManager’s plugin check. Cloning and use of your custom plugin scripts: You can now create and use custom scripts that execute before or after a cloning operation. The SnapManager 3. SnapManager now enables you to create backups on primary (local) storage and assign protection to those backups on secondary (remote) storage using storage administratorgoverned protection policies.◆ This edition of the release notes includes a section listing documentation issues in the SnapManager 3. This feature is accomplished by integration with Protection Manager. Backup scheduling: DBAs can now schedule their backups to occur on a regular basis using SnapManager’s scheduling feature in the graphical user interface (GUI).0. ◆ ◆ ◆ 2 What’s New in SnapManager for Oracle? .0 for Oracle Installation and Administration Guide. volumebased restore. data protection and fast restore features are not available in SnapManager on a Windows host. If you want certain data in the clone database to be sanitized for data security reasons. you can create a script that performs the necessary updates within the clone database. Volume-based restore of the database: SnapManager now offers two methods of restoring the database: file-based restore and a faster.1 release.0. SnapManager includes an additional command and option in the graphical user interface to check the custom script installation. you can execute your custom scripts as part of the regular clone process. DBAs can leverage this new feature and also create clones of databases on secondary storage.1 Release Notes. DBAs no longer need to rely on CRON jobs to execute scripts for automating backups.0 for Oracle Installation and Administration Guide should be used.

Support for multiple file systems per disk group: Previously. Access is now governed by user roles. ◆ protection-policy list This command lists the protection policies that can be applied to a profile. SnapManager offers a cloning plugin. SnapManager provides additional security for features. SnapManager supported only one file system per disk group.2 for Windows support. including the display of repositories. and post (for post-processing scripts). ❖ ◆ ◆ Command line interface: Many commands include additional parameters to support policy-driven data protection and volume-based restore operations. Custom scripts are stored in three directories: policy (for scripts that should always be run before the clone operation occurs). pre (for preprocessing scripts). ◆ ◆ CLI changes The following commands have been added: ◆ plugin check SnapManager provides the ability for you to install and use custom scripts to perform various operations. which you can use to automate your custom scripts before and after you clone a database backup. The protection policy can be applied when a new profile is being created or What’s New in SnapManager for Oracle? 3 .◆ Custom Snapshot copy names: With this version. use the plugin check command to verify the installation of plugin scripts on the SnapManager server. You can launch the GUI using Java Web Start. ❖ ❖ ◆ The GUI displays a Monitor tab that you can use to monitor operations and a Schedule tab that you can use to view all scheduled backups. profiles within the repository. Broader platform and host environment support: SnapManager supports all platforms and host environments that SnapDrive 4.0. DBAs can execute multiple actions concurrently by backgrounding backup and clone operations and can update settings on multiple profiles at once. This command applies to the server-side installation of SnapManager. Graphical user interface updates: The SnapManager graphical user interface includes many enhancements. Role-based access control for features: With Operations Manager integration. Before you use the cloning plugin. The GUI can be launched from multiple platforms. You can also launch it using a command. you can now specify a naming convention or pattern to describe the Snapshot copies related to the profile you create or update. The GUI is installed at the same time as the host software.1 for UNIX and SnapDrive 6. and backups and clones within profiles.

The -retain-forever and -retain-normal options have been removed from this command. it also displays the following information for each backup: ❖ ❖ ❖ ❖ ❖ Retention class for the backup (instead of NORMAL or FOREVER) ID for the backup Comment entered when creating the backup Whether the backup is protected to secondary storage Whether the backup exists on primary storage ◆ backup mount 4 What’s New in SnapManager for Oracle? . SnapManager protects the backup as the default. ◆ backup free The -retain option has been removed from this command because the single retention count has been replaced by several retention classes. if the backup is a full backup and the profile specifies a protection policy. The following commands have changed: ◆ ◆ abort This command was removed. This option indicates whether the backup should be protected to secondary storage. Instead of -retain-forever option. Note Protection Manager and SnapDrive need to be installed in the server to enable SnapManager to use this command. then the retention class defaults to -hourly. If the -verbose option is specified. backup create A new -protect option has been added. If neither option is specified. The -noprotect option specifies that the backup should not be protected to secondary storage. ◆ backup delete The -retain option has been removed from this command because the single retention count has been replaced by several retention classes. This can also be set to a profile by the storage administrator through Protection Manager. The option -list specifies the list of protection policies that can be set to a profile. Also. Only full backups are protected. if the -retain option is not specified. ◆ backup list The list displays information about all backups for a specified profile.updated on an existing profile. the -retain -unlimited option can be applied.

config file: ❖ If restore.secondaryAccessPolicy is set to indirect. then SnapManager attempts a host side file copy restore. SnapManager restores the data from the Snapshot copies on primary storage: ❖ ❖ -restorespec: Specifies the path to an XML file that details the data to restore and the restore format. This is the default secondary access policy. mounts the cloned data from the secondary storage system to the host.secondaryAccessPolicy is set to direct. SnapManager first copies the data to a temporary volume on primary storage. If you use a temporary volume. the primary backup must be freed before a backup can be restored from secondary storage. SnapManager clones the data on secondary storage. you can specify which backup copy to use with the -copy-id option. mounts the data from the temporary volume to the host. If restore. The method SnapManager selects is configured in the smo. If SnapManager cannot perform this type of restore (for example. This option enables you to manually restore the data to an active file system and restore from the specified data by providing a mapping of each original Snapshot copy to its active file system. ◆ backup restore This command has new options for how to restore protected data. You can specify one of the following options. specify the volume using the -temp-volume option. and then copies data out of the temporary volume into the active environment. SnapManager has two methods of performing a host side file copy restore from secondary. If there is more than one backup copy. This secondary access policy should be used only if the host does not have direct access to the secondary storage system. if files not part of the restore exist in a file system). If you don’t specify an option. A new -restorespec option or -from-secondary option can be specified. You cannot use this option if the backup exists on primary storage. and then copies data out of the clone into the active environment. use the -copy-id parameter to specify which copy on secondary storage should be used to mount the backup. ❖ What’s New in SnapManager for Oracle? 5 . -from-secondary: Tells SnapManager to restore the data from secondary storage. If there is more than one copy on secondary storage. When restoring from secondary storage.This command has new options: -from-secondary -copy-id id and -host. SnapManager first attempts to restore data directly from the secondary storage system to the primary storage system (without involving the host).

If this option is not specified. -fallback: Restores the database using any method that SnapManager determines and enables the administrator to provide as little information as necessary on the command line. if all mandatory restore eligibility conditions are met. ◆ clone show This command now indicates if the clone was created using the backup on primary or secondary storage. -override: Enables the database administrator. The -fast option cannot be used while restoring from secondary storage The -fast option includes the following parameters: ❖ -require: Forces SnapManager to perform a volume restore. This option enables the administrator to choose the process for the restore operation. ◆ clone create A new option -from-secondary can be specified. If you specify the -fast option. but do not specify any parameter for -fast.Restores using this method take twice as long as the direct secondary access policy because two copies of the data are made. backup retention class. Use the -copy-id option to specify which protected backup to use. ❖ ❖ ❖ ◆ backup show The list displays detailed information about a backup. In addition to the above options. 6 What’s New in SnapManager for Oracle? . If you do not specify -fast. Database administrators can force SnapManager to use the volume-based fast restore process rather than other restore processes. This option prevents the restore from using the fast restore process. This option indicates that SnapManager should clone a copy of a backup that has been protected to secondary storage. -off: Enables the database administrator who knows that a volume restore cannot be performed on the database backup and wants to avoid the time required for restore to perform all the eligibility checks. and backups on primary and secondary storage. a -fast option can be specified. to override non-mandatory eligibility checks and perform the volume-based fast restore. if more than one copy exists. SnapManager uses the -require parameter as a default. including its protection status. who knows that all overridable conditions can be overridden without negative consequences. SnapManager uses the default backup restore -fast fallback. if all restore eligibility conditions are met. SnapManager clones the copy from primary storage.

nonconformant. you can specify a retention count or a retention duration or both. The duration is in units of the class (for example. If a retention class is specified and only a count or a duration is specified. smo_server start The host credentials have been eliminated for this command. protection policy. hours for hourly. monthly). conforming. The -comment option specifies the comment for a profile describing the profile domain. If this option is not specified. then the field not specified defaults to 0. weekly. The -protect and -protection-policy options govern whether backups can be protected to secondary storage. hours for hourly. ◆ profile update New options like -comment. For each retention class (hourly. daily. daily. What’s New in SnapManager for Oracle? 7 . -protect -protection-policy and -retain can be specified. weekly. then the retention class defaults to -hourly. The -comment option specifies the comment for a profile describing the profile domain. days for daily). You can set a retention count or a retention duration for a retention class (hourly. -protect -protection-policy and -retain can be specified. The -protect and -protection-policy options govern whether or not backups can be protected to secondary storage. protection status. The -retain option specifies the retention policy for backups created from the profile. ◆ profile show The output now displays the profile comment and new data protection attribute information such as associated dataset name. The -retain option specifies retention policy for backups created from the profile. monthly) or both. conformance status (conformant. then the retention class defaults to -hourly. and retention values. The duration is in units of the class (for example.◆ profile create New options like -comment. ◆ ◆ smo_server restart The host credentials have been eliminated for this command. days for daily). If this option is not specified. or none).

Details on SnapManager 3. ❖ ❖ ❖ ❖ ❖ ❖ ❖ ❖ Windows Server® 2008 Windows Server® 2003 Red Hat® Enterprise Linux® Oracle® Enterprise Linux® SUSE® Enterprise Linux® Solaris® SPARC and x86 IBM® AIX® HP-UX® Itanium® and PA-RISC ◆ ◆ SnapManager requires Data ONTAP 7. SnapManager supports the following host platforms. Follow the instructions provided with the kit to set up the storage systems to work with the host. System setup required to use SnapManager While setting up the host system. The SnapManager server requires 128 MB of memory.netapp.System requirements Confirming system requirements The most current information on SnapManager’s requirements is available in the compatibility matrices on the NOW™ site. See the Interoperability Matrix for details about supported protocols for each.2.0. Because NetApp adds new components and updates products on an ongoing basis.com/NOW/products/interoperability. it is a good practice to check these matrices. 8 System requirements .1 for Oracle support are captured in the NetApp Interoperability Matrix (IMT) under the SnapManager perspective available at http://now. consider the following issues: ◆ ◆ SnapManager for Oracle and SnapManager for SAP cannot run concurrently on the same host. such as the NetApp™ Host Utilities. including the products required. Install SnapDrive for UNIX or SnapDrive for Windows on the host platform.4 or higher for Protection Manager protection policy support. Each operation run by the SnapManager server requires 48 MB of additional memory while it is running.

you must have a host running one of the following: ❖ ❖ ❖ ❖ ❖ ❖ ❖ ❖ ❖ ❖ Windows Vista Windows® XP Windows Server® 2008 Windows Server® 2003 Red Hat® Enterprise Linux® Oracle® Enterprise Linux® SUSE® Enterprise Linux® Solaris® SPARC and x86 IBM® AIX® HP-UX® Itanium® and PA-RISC The graphical user interface has the following requirements: ❖ ❖ ❖ Minimum 128 MB available disk space for the application Minimum 512 MB RAM to run the application Java runtime environment (JRE) version 1.5.◆ ◆ ◆ SnapManager requires a minimum 4K block size for the tablespace into which it is installed. See the Interoperability Matrix for details.5. To use the SnapManager graphical user interface. “Starting the graphical user interface” on page 26 explains how to download the SnapManager graphical user interface software and the required JRE. JRE 1. SnapManager runs successfully with JRE 1. System requirements 9 . SnapManager also operates in virtualized environments. such as VMware ESX and Windows Hyper-V.6 is not supported.

0.1 to 3. Start the SnapManager server.1 In SnapManager 3. You must install SnapDrive for UNIX or SnapDrive for Windows on your host before installing SnapManager.0. installable package formats. See the SnapDrive documentation for installation instructions.1 2.2 to 3.0 and 3.0 for Oracle is available both from CD-ROM or from the NetApp NOW site.1 2. SnapManager 3. The following upgrade paths are supported for SnapManager 3.SnapManager installation SnapManager components SnapManager 3. from their product locations on the NOW site. Verify the SnapManager system.0 to 3.0. You can also download SnapManager prerequisites.0.0.1 for Oracle is available only as software that you can download from the NetApp NOW site (http://now.1 for Oracle perform these steps: 1. Installing SnapManager Detailed instructions for installing SnapManager are in the SnapManager for Oracle Installation and Administration Guide. Upgrade the SnapManager repository. There is no separate graphical user interface installation with this release.netapp. such as SnapDrive for UNIX or SnapDrive for Windows. Install SnapManager. Both the host and the client software are included in the SnapManager installation. which contains the SnapManager for Oracle software in standard.0. 3. 4.1 for Oracle: ◆ ◆ ◆ 3. 2. The media kit includes the following items: ◆ ◆ SnapManager Installation and Administration Guide CD-ROM. 10 SnapManager installation .com/).

The default port number must be the same for all port numbers involved in remote operations.Restrictions SnapManager 3.1 for Oracle and later. SnapManager for Oracle does not support accessing two SnapManager for Oracle servers running on different ports from a single client (both for the graphical user interface or when using commands). ◆ ◆ ◆ Restrictions 11 .0 for Oracle has the following restrictions: ◆ ◆ SnapManager supports control files on a file system or in ASM and does not support control files on raw devices. The SnapDrive product cannot create a Snapshot copy of a LUN or file residing in a qtree in a V-Series gateway storage system if the underlying volume is not in the same V-Series gateway storage system. Protection Manager controls the secondary transfer schedules. An error message appears describing why it failed. The SnapDrive for UNIX product supports more than one type of file system and/or volume manager on certain platforms. ◆ ◆ ◆ Neither SnapDrive nor SnapManager support reverting to a previous version. you might want to take another backup and wait for it to be transferred to secondary storage by Protection Manager during its regular transfer schedule. the recovery catalog must be in a different database than the database that is being backed up. you might want to contact the storage administrator and ask for the backup to be transferred. See the SnapDrive for UNIX Installation and Administration Guide for more information about using this file. If an RMAN recovery catalog is being used. SnapManager supports databases on the V-Series gateway storage systems. If a user tries to clone a database from secondary storage and a Snapshot copy in the backup happens to be the last Snapshot copy transferred to secondary storage for that qtree or volume. Alternatively. SnapManager can be configured to catalog database backups with RMAN. The file system and/or volume manager used for database files must be specified in the SnapDrive configuration file as the default file system/volume manager. then the clone will fail. In this case.0 for Oracle or earlier cannot be cloned using SnapManager 2. with the following requirements: You must configure SnapDrive to set passwords for V-Series gateway storage systems as is the current requirement with other NetApp storage systems. Backups containing RAW tablespaces or ASM disks on Linux created with SnapManager 2.

and 5. 5. SnapManager fails to delete a clone after the host name is changed for the host on which the clone is running. check the following places: ◆ ◆ The “Troubleshooting” chapter of the SnapManager for Oracle Installation and Administration Guide.8 is available. rename the old host name to the same IP address in the client and server hosts file.◆ All LUNs within a volume should reside at the volume level or inside qtrees. Finding information on troubleshooting tips At the time of this release. SnapManager operates within a Microsoft Clustering (MSCS) environment. Backup creation might fail if SnapManager operations are run concurrently on the same host against a different ASM database. This is because if the data is residing on the qtrees and the user mounts the volume. and try to delete the clone again. 12 Finding information on troubleshooting tips .2. the ext3 filesystem is not supported when deploying Oracle over raw devices using dynamic multipathing (DMMP) in a multipathing IO (MPIO) environment. However. there are some known problems and limitations for SnapManager. The NetApp Bugs Online system. The issue will be resolved in a forthcoming release of RedHat Enterprise Linux.secondaryAccessPolicy option can be set only to direct. The restore. To locate information on known issues. To fix this issue. In RedHat and Oracle Enterprise Linux 5.1. ◆ ◆ ◆ ◆ ◆ For more deployment considerations. but not in both. the restore. SnapManager does not recognize an MSCS active/passive configuration and will not transfer active management of a repository to a standby server in an MSCS cluster. in the smo. which is available on the NOW site.config file.secondaryAccessPolicy cannot be set to -indirect until the release of Protection Manager for use with DataFabric Manager 3. With regard to restoring from secondary storage system.0. limitations and restrictions. see the SnapManager for Oracle Installation and Administration Guide. then the data inside the qtrees is not protected.

4) physical standby databases created using Oracle Data Guard services. Restore of standby databases are not supported. ◆ ◆ ◆ ◆ 330059 In SnapManager 3.0 for Oracle. Resolution: In SnapManager 3. Partial backups of standby databases are not supported. In SnapManager for Oracle 3.0. DBAs can switch a primary database to a standby mode and vice versa. ASMLib applies only to SAN environments.0. 333200.0. Logical standby databases are not supported.2. you can backup and clone Oracle 10gR2 (10. 333202 Description and resolution ◆ Using SnapManager 3. 321009. Issues resolved in SnapManager 3.1 for Oracle. 330106 Attempting to connect to a remote SnapManager service running on HP-UX Itanium sometimes caused the remote service to unexpectedly terminate.1 for Oracle. Using Data Guard. Bug ID 321002.1 for Oracle.1 for Oracle.0. Only full offline backups and clones of physical standby (standalone and RAC) databases are supported.0.0. ASMLib is no longer required when provisioning ASM disks with iSCSI or FCP on Linux.Issues resolved in SnapManager 3. you should use the SnapManager command line interface or graphical user interface from the same host running the SnapManager service. you no longer have to use the SnapManager command line interface or graphical user interface from the same host running the SnapManager service. Resolution: In SnapManager 3. Online backups of standby databases are not supported. the Automatic Storage Management support library (ASMLib) was required when you were provisioning ASM disks with iSCSI or FCP on Linux.0.1 for Oracle 13 . You can connect to a remote SnapManager service running on HP-UX Itanium.0.1 for Oracle The following table describes issues that were resolved in SnapManager 3.

the clone operation failed if the specified database instance name.Bug ID 330696 Description and resolution In SnapManager 3. The backup schedules created in this repository run successfully. Resolution: In SnapManager 3. digits (0-9). service name. the host name must consist of alphabetic characters (A-Z).”). The repository port can be any valid port number and the repository host name can be any valid host name. 330905 In SnapManager 3. but not an underscore (“_”). referred to as the SID.1 for Oracle.0. contained more than 8 characters. you could not preview a restore operation using the graphical user interface (GUI) when you were restoring a backup from secondary storage. the repository user name and service name must consist of only the following characters: alphabetic characters (A-Z).1 for Oracle . including a restore from secondary storage. you can preview all types of restore operations in the GUI. 331276 In SnapManager 3.0. Resolution: SnapManager 3. backup schedules failed if the host name.0 for Oracle. minus sign (“-”). and user name.”).0 for Oracle.config file. and period (“. service name. For a repository to support SnapManager scheduling.0 for Oracle. underscore (“_”). minus sign (“-”). Resolution: SnapManager 3. or user name contained a dash or hyphen. A workaround involved editing the smo. and period (“. 14 Issues resolved in SnapManager 3.1 for Oracle no longer restricts the length of the SID.0. In other words. digits (0-9).0.1 for Oracle now supports dashes or hyphens in the host name.

then you should copy the contents of the following directory to the inactive node of the cluster: c:\Program Files\NetApp\SnapManager for Oracle\repositories For a given database that is running on the cluster. 342451 When you attempted to restore an ASM database using SnapManager 3. you must copy the contents of directory <installdir>\repositories from the active node of the cluster to the same directory on the inactive node of the cluster. the SnapManager for Oracle schedules automatically start on the newly active node. When you create the profile and are prompted to specify the host name for the target database. this is no longer an issue. for MSCS active/standby clusters in SnapManager 3.0 for Oracle and the database contained an ASM file that was larger than 4 GB. SnapManager for Oracle backup schedules might not initiate backups when the database failed over to another node of the cluster. Known issues Known issues 15 . provide the virtual IP address or virtual host name of the cluster (instead of the physical IP address or physical host name of one particular node in the cluster). Resolution: In SnapManager 3. ◆ 337107 In SnapManager 3. You can create clones on remote Windows hosts. you can successfully restore an ASM database that contains a file larger than 4 GB. Whenever the cluster switches activity from one node to the other.0 for Oracle. Resolution: In SnapManager 3.0.0. the clone operation might fail. if SnapManager for Oracle is installed in the default directory. an error occurred.1 for Oracle. For instance. However. for MSCS active/active clusters.1 for Oracle. the workaround was to use the native Windows scheduler to define your backup schedules. In SnapManager for Oracle 3. you must also use the native Windows scheduler.0. if you created a clone on a remote Windows host.0 for Oracle.Bug ID 335474 Description and resolution For a database running in a Microsoft Clustered Services (MSCS) active/standby cluster.1 for Oracle.0. Resolution: In SnapManager 3. you can use the SnapManager for Oracle scheduler with the following conditions: ◆ ◆ You must configure the cluster so that the SnapManager for Oracle server runs on the active node of the cluster but does not run on the inactive node of the cluster. Whenever you create a new repository. create just one database profile.

This error occurs if you have an input with a trailing white space or if /tmp is full. run the command df -h /tmp. Run the smo credential set command again. To check if /tmp is full. Change http to https in SnapDrive and make the same change in the smo.1 for Oracle. an error message appears as follows: Error invoking command: SMO-20030: Credentials cannot be encoded as input by the user.conf file. If /tmp is full. type the bug ID into the Enter Bug IDs field. and click Go! Known issues and workarounds The following table describes issues known to exist in SnapManager 3. navigate to http://now.config file.netapp. Bug ID 303285 Description and workaround SSL ZAPI exceptions occur on HPUX for SnapManager.0. launch your Web browser.1 for Oracle.Accessing information about bugs For the latest information about workarounds. Set use https option to false in the smo. 2. 3. Workaround: 1. Set use-https-to-filer option to off in the SnapDrive snapdrive. Workaround: 1.com/NOW/cgi-bin/bol. Please ensure there are no trailing spaces or special characters in any credential fields. ZAPI messages sent over HTTPS will fail with an error similar to the following: ZAPI call “nfs-exportfs-storage-path” to “stonefish” threw exception: Remote host closed connection during handshake. 2.config file in SnapManager 3.0. 300532 smo credential set command gives an error when /tmp is full. 16 Known issues . create some space by deleting some unwanted files. Description: While executing the smo credential set command. 3. Description: On HPUX machines connected to a storage system running certain versions of Data ONTAP.

netapp. change it to rhine. 2. Check if the DFM storage system entries are updated with the domain name.com.com. If the DFM storage system entries reflect host name instead of domain name. Description: In case the NFS entry in the DFM server is the host name instead of the domain name. SnapDrive attempts to find a match to the domain name and fails.Bug ID 314901 Description and workaround SnapDrive fails to find a match if there is domain name entry mismatch in the NFS entry in the DFM server.rtp. 3. For example. Log onto DataFabric Manager (DFM) using the NetApp Management Console (NMC). change it to the domain name. consider the host name is rhine and domain name is rhine.rtp. Workaround: 1. Unable to find its ID on Operations Manager server <server_name>. It might take some time to update. depending on the number of LUNs and volumes associated with the respective storage system in DFM server. Known issues 17 .netapp. If the DFM storage system entries are updated as rhine. An error message appears as follows: Invalid resource specified.

Sometimes.. To see the cause of the problem. SnapManager cannot retrieve the necessary information to know that the backup exists on secondary storage. look in the operation logs of the SnapManager server. Workaround: The system detects these operation records and marks them as FAILED during normal processing. Workaround: There are two options. ◆ ◆ Start the ASM instance.Bug ID 316666 Description and workaround The protection state of a backup should show as “Protected” if a copy of the backup exists on secondary storage. Then. The cause of the problem is not presented via the CLI or GUI directly. 18 Known issues . Fix the problem that is causing the error message found in the SnapManager log file. For example: [DEBUG]: SD-10027: SnapDrive Message ID=2330 Code=xxx Category=null Source=null Message= . SnapManager might incorrectly show the protection state as “Not Protected” even when a copy of the backup exists on secondary storage.. change the line in the oratab file for the ASM instance into a comment.error message. Else.. Description: The command smo repository show might show records for incomplete operations.. Workaround: 1. 324973 Profile creation fails when ASM instance is not initiated. 325359 The command smo repository show may show incomplete operations. Description: If an ASM instance exists in the oratab file and the ASM instance is not initiated. look at the last few messages above that line for the specific error message that is preventing SnapManager from retrieving the locations of the backup. Such records can be created when the SnapManager process dies unexpectedly while performing an operation such as system reboot or kill -9. then profile creation will fail. For example... Check the server operation logs for the specific error message that is preventing SnapManager from retrieving the locations of the backup. 3. [DEBUG]: Unable to retrieve backup locations of backup "8abc01521c5082c6011c5082cbad0001" "backup304" 2.

snapfile.config file is located in the properties subdirectory of SnapManager’s installation directory.operationTimeout option to 3600000. if the system is under heavy load.netapp. Check to see that the operation completed.NullPointerException cause-message : null class : com.model. Operation [Na67e68b33620ef3a4981bcb0a8d3c332] not found. In the Monitor tab in the graphical user interface. Check the sizing of the system. 3. For the command line interface. This effect might occur if the system is under heavy load or out of computing resources. 326171 Successful operations might appear as if they were terminated abnormally. Set the server. use the operation list command. Workaround: This error occurs rarely.netapp. Known issues 19 .model.netapp.windows.platform. Description: SnapManager might intermittently report an error similar to the following (with possibly different values for some of the fields): ---. The following log entries or command line interface output might indicate such a situation: Operation Id [8abc01a31d82ce5f011d82ce8c170001] failed. The smo.Connection required-type : com.UserImpl path : /com. Try the backup delete operation again.model. Workaround: 1.Debugging information ---cause-exception : java. Error: "Operation abnormally terminated" Operation [MISSING ID] not found.Bug ID 325703 Description and workaround The backup delete operation fails intermittently. Edit the smo.netapp.Connection/ rootStorageComponent Map/entry/com.HostMountedFileSystemFile/fileSecurityDes criptor/fileOwner/user line number : 1 ------------------------------- This error is reported by a library that is used internally by SnapManager.config file. 2.lang.snapfile.snapfile. Description: The command line interface or the graphical user interface might indicate operations as terminated abnormally. 4. even though they completed successfully.common.

<minor number>] 331847 Snapshot copies created in SnapManager 3.discovery.1.d/oracleasm and replace the following line: "${ORACLEASM}" querydisk -l "${ORACLE_ASMMANAGER}" "$@" with: "${ORACLEASM}" querydisk -d -l "${ORACLE_ASMMANAGER}" "$@" Verify the change by running the following command where <diskname> is a valid ASM disk: /etc/init.OneToOneDiscoveryStep.java:86) at com. or mount).platform. After the Snapshot copies are deleted.discover (OneToOneDiscoveryStep.snapfile. Description: On systems with a version of oracleasm-support that is at or above 2. if you attempt to perform SnapManager operations (such as restore.java:168) .discover (DiscoverySession. then SnapManager issues the following error: 0001-089 Command error: snapshot <snapname> doesn't exist on a storage system volume <storagesystem>:/vol/<volume> Workaround: Increase the retention values in the protection policy’s retention policy in Protection Manager to values greater than the retention policy defined in SnapManager. 20 Known issues .netapp.DiscoverySession. Error: Disk "<diskname>" is a valid ASM disk com.asmlib.discovery..ASMLibDeviceDiscoveryStep.netapp.discovery.0.netapp. Workaround: Edit the file /etc/init.0.Bug ID 328882 Description and workaround SnapManager fails to discover ASM disks when using a version of oracleasm-support at or above 2.ASMLibException: ASM-10001: ASMLib disk identifier <diskname> is unknown to ASMLib.netapp. SnapManager fails with an error similar to the following on profile create and other operations: [ERROR]: FLOW-11008: Operation failed: ASM-10001: ASMLib disk identifier <diskname> is unknown to ASMLib.1 for Oracle on the primary node are being deleted incorrectly by the Protection Manager retention policy.java:77) at com.oracle. at com.map (ASMLibDeviceDiscoveryStep.snapfile.d/oracleasm querydisk <diskname> The output should include the major and minor numbers of the raw device as follows: Disk <diskname> is a valid ASM disk on device [<major number>.1..java:21) at com.ASMLib. clone.queryDisk(ASMLib. If the protection policy’s retention policy in Protection Manager is shorter than the retention policy defined in SnapManager.oracle.netapp.platform.0.snapfile.0 and 3.asmlib. then Protection Manager deletes the Snapshot copies on the primary node.

set up a schedule in SnapManager to create hourly backups at: 19:30. say you have a schedule defined in Protection Manager like the following: 20:00 hourly. The reason for the discrepancy is that Protection Manager assigns the retention class of the backup on secondary storage based on when it is transferred. when the backup is automatically transferred to secondary via the transfer schedule defined in Protection Manager. monthly. The retention class of a backup might be different on a secondary node than on the primary node. keep daily backups for 5 days. you create a backup with a monthly retention class. and 23:00 daily. 21:00 hourly. SnapManager assigns a backup a retention class of hourly. The retention class for the backup on secondary storage determines how long the Protection Manager will retain the backup on secondary storage. 21:30 and to create daily backups at: 22:30 Then. 22 will have hourly retention class on secondary. keep weekly backups for 4 weeks. the backups on primary storage should have the same retention class as the backups on secondary storage. weekly. For example. or unlimited. 21:00 hourly. For example. and keep monthly backups for 52 weeks.Bug ID 331855 Description and workaround Description. This is regardless of the retention class defined when the backup was taken with SnapManager. Assuming the backups take less than 30 minutes to complete. 22:00 hourly. The schedules that Protection Manager uses define at which times backups are transferred. but the backup on secondary storage might have a different retention class. all of the backups transferred at 20. Workaround. such as daily. Synchronize your primary backup schedule in SnapManager with your transfer schedule in Protection Manager such that transfer events of the correct retention class occur after backups with the retention class. set up the transfer schedule in Protection Manager as: 20:00 hourly. Say you have a backup that is designated as monthly on primary storage. 22:00 hourly. and all of the backups transferred at 23 will have daily retention class on secondary. daily. Known issues 21 . Then. If protection is enabled for the backup. 20:30. 21. The backup on primary storage has the monthly retention class. To continue. the retention class of the copy of the backup on secondary storage might be different than what was specified when the backup was created. 23:00 daily Then. but daily on secondary. say your retention policy for secondary storage in Protection Manager is: Keep hourly backups for 8 hours. the backup on secondary storage will be deleted after 5 days (as opposed to 52 weeks). For example.

uninstall Java 5 and reinstall Java 5 update 11 (the same Java version used by the SnapManager server). Workaround: 1. incorporation of this option would have had adverse affects on other SnapManager for Oracle options. or Solaris. 338437 347763 The SnapManager GUI fails to display the Help button. passwords in SnapManager for Oracle cloning operations are case sensitive. Workaround: Two workarounds are available: ◆ ◆ Instead of launching the GUI via Java Web Start. See the NetApp Knowledge Base article KB7518 about NFS mount options. This problem occurs only if the all of the following conditions are true: ◆ ◆ ◆ The GUI is launched via Java Web Start. Placing an spfile on a different volume might prevent creation of a clone. create a soft link to the database. This restore_symboltable file prevents SnapManager for Oracle from performing volume-based snapshot restores in the future. you can delete this file from the directory.Bug ID 333558 Description and workaround Starting with Oracle 11g. install SnapManager on the client host and then launch the GUI via the command line (UNIX) or the Start menu (Windows). passwords are case sensitive. 22 Known issues . The GUI host has Java 5 update 16 or 17 installed. Workaround: After you successfully restore the data from secondary storage. In Oracle_home. This enables SnapManager for Oracle to perform a volume-based restore upon request. Linux. 2. On the GUI host. When the user launches the SnapManager GUI via Java Web Start. in some cases the GUI never displays the Help button in the wizards. Data ONTAP adds a restore_symboltable file in the destination directory. Therefore. Although Oracle provides an option to make case insensitive. Move the database directory from Oracle_home to another volume. 348164 When Protection Manager restores copies of the primary data. The GUI host is running on Windows.

57 Chapter: Configuring SnapManager The “Ensuring that ASM can discover imported disks” topic included an example for changing the ASM_DISKSTRING parameter to ensure that ASM can discover disks imported by SnapManager./opt/NetApp/smo/mnt/*/* 70 Chapter: SnapManager workflow and quick start The “Creating repositories” topic stated that SnapManager requires 4K block space for the tablespace into which it is installed.” However.0 for Oracle Installation and Administration Guide. the statement should read: “SnapManager does support OS-authentication for RAC databases for both ASM and non-ASM environments. ASM_DISKSTRING = '/mnt/my-asm-disks/dir1/*. this should be: ASM_DISKSTRING = '/mnt/my-asm-disks/dir1/*. given the example information. 49 Chapter: Installing or upgrading SnapManager Step 9 of the “Installing or upgrading SnapManager on a Windows host” topic stated that the Windows service account must be a member of the storage system’s local administrator group. this requirement is actually a minimum of 4K block space. this should have stated ORA_DBA. These statements were removed. However.” 43 Chapter: SnapManager deployment considerations The “General restrictions” topic included V-Series statements that applied to all NetApp products and were not specific to SnapManager. the example included an additional asterisk (*). However./opt/NetApp/smo/mnt/*/*/*' However. Page 42 Description and resolution Chapter: SnapManager deployment considerations The following statement appears in the topic “Requirements for using RAC databases with SnapManager”: “SnapManager does not support OS-authenticated database connections for RAC databases. and the Oracle DBA. The Oracle DBA was listed as ORA_SID_DBA.Documentation issues The following issues have been found in the SnapManager 3. the local administrator’s group of this system. Documentation issues 23 . However.

The command has four distinct sections: host. repository. and quiet/verbose. and quiet/verbose. The correct syntax is: smo credential set [-host -name host_name -username username [-password password]] | [-repository -dbname repo_service_name -host repo_host -port repo_port -login -username repo_username [-password repo_password]] | [-profile -name profile_name [-password password]] [-quiet | -verbose] 247 Chapter: SnapManager command reference The topic describing the protection-policy command included a -list option. Use protection-policy list instead without the dash. The command has four distinct sections: host. The correct syntax is: smo credential delete [-host -name host_name -username username] [-repository -dbname repo_service_name -host repo_host -port repo_port -login -username repo_username ] | [-profile -name profile_name] [-quiet | -verbose] 227 Chapter: SnapManager command reference The credential set command shows incorrect syntax information. However. profile. repository. profile.Page 225 Description and resolution Chapter: SnapManager command reference The credential delete command shows incorrect syntax information. 24 Documentation issues . the list option should not include a dash preceding the option.

complete the following steps: 1. click Download Software. Enter your user name and password. Review the information on this page. SnapManager 3. Then follow the links to the Software Description page for the product. Step 1 Action Log into the NOW site at http://now. Click Login.0. Obtaining the software from NOW 6 Obtaining the latest version of the NetApp software 25 . see the SnapManager for Installation and Administration Guide.0 for Oracle is available both from CD-ROM or from the NetApp NOW site. From the Software Download section. go to the row in the Software Download page for the product.com.com/). SnapManager 3. To download the software from the NOW site.Obtaining the latest version of the NetApp software Getting the most up-to-date SnapManager software SnapManager installation includes both the host server software and the graphical user interface client software for UNIX and Windows operating systems. 2.netapp.netapp. click Continue to go to the Software Download page. If you need to download the SnapDrive product. The CD and the download site each contain the server software and the graphical user interface client software. 2 3 4 5 Go to the SnapManager product row of the Software Download table and select from the Select Platform list and click Go! Follow the prompts until you reach the Description Page.1 for Oracle is available only as software that you can download from the NetApp NOW site (http://now. For instructions to install the software. At the bottom of this page. Download the documentation from the Software Description page. complete the following steps. In the fields on the right side of the page.

ensure that the SnapManager server is already started. complete the following tasks: ◆ ◆ Start the SnapManager server. perform the following action: Operating System Windows host Action Select Start > All Programs > NetApp > SnapManager for Oracle > Start SMO GUI Enter the command: smogui UNIX host Downloading and starting the GUI using Java Web Start (UNIX) The following procedure explains how to download and start the SnapManager graphical user interface on UNIX platforms. Note Before starting the SnapManager GUI. you can easily start the SnapManager GUI by using a command (UNIX) or by selecting the program from a list of programs (Windows). 26 Starting the graphical user interface . JRE 5. Open a Mozilla Firefox web browser window.0 updates 16 and 17 prevents the online Help button from displaying in the web-started GUI.0. To start the GUI from a host on which the SnapManager server is already installed.Starting the graphical user interface You can start the graphical user interface (GUI) in one of the following ways: ◆ ◆ Start the GUI from the command line interface Download and start the GUI using Java Web Start (with UNIX or Windows instructions) Starting the GUI from the Command Line Interface If SnapManager is installed on the host. Use of JRE 5.0 updates 11 through 15 are recommended. The GUI requires JRE 5. See Bug ID 347763 in the “Known issues and workarounds” on page 16. More specifically. Before downloading the graphical user interface.

The output should display the exact path to javaws.) For Linux and Solaris.” click Accept this certificate. go to the following: https://smo-server.com:port where smoserver.sun. by default) . In the Mozilla Firefox web browser window. 2 3 4 5 If you see a popup dialog box with the title “Unable to verify the identity of SnapManager as a trusted site.domain. Verify that Java Web Start is accessible by running the following command: which javaws.domain.Step 1 Action If you have not already installed the Java Runtime Environment (JRE) on the client.” click OK. the version should be 1. The JRE can be downloaded from Sun’s web site: http://java.5. The output should indicate Java 1.5 (which is Java 5. install the JRE 5.com is the fully qualified host name and domain on which you installed SnapManager and port is the listening port for the SnapManager server (27214. If you then see a popup dialog box with the title “Security Error: Domain Name Mismatch.com.0). 6 7 Starting the graphical user interface 27 . Click the link labeled Launch SnapManager for Oracle. (The output varies based on platform. Verify that Java is installed by running the following command: java -version.0_11.0 Update 11.

” click Run. The window closes.” perform the following steps: ❖ ❖ Select Open with and then click Browse. If you see a popup dialog box with a message about a hostname mismatch. ◆ ◆ ◆ ◆ 10 The browser downloads and starts the SnapManager for Oracle graphical user interface.” then the client has an older version of Java 1.4+ is required for HTTPS support.Security Warning” and the message “Do you want to run this software?. Java 1. specify the path to javaws as determined previously and click Open.jnlp. you might see one or several of the following popup dialog boxes.Security” and a message about the certificate of the SnapManager web site. ❖ ❖ 9 While downloading SnapManager on either a Windows or UNIX client.5 Update 11. click Yes.jnlp” window. click OK. The message contents and button labels vary based on platform. 28 Starting the graphical user interface . click the checkbox labeled “Do this automatically for files like this from now on.jnlp” window. ◆ If you see a popup dialog box with the title “Warning . click Yes or Run.” In the “Opening application. If you see a popup dialog box with the title “Java Web Start Launch File Error” and the message “The field <jnlp> has an invalid value: https. If you see a popup dialog box with the title “Warning .5.Step 8 Action If you see a popup dialog box with the title “Opening application. The file chooser popup window closes. In the “Opening application. In the file chooser popup window. Download Java 1. If you see a popup dialog box with the title “Java Platform SE binary .4 or 1. click Yes or Run.Security” and a message about the signature of the SnapManager application.

Before downloading the graphical user interface. JRE 5. More specifically. Use of JRE 5.0 and the application. complete the following tasks: ◆ ◆ Start the SnapManager server. Open a Microsoft Internet Explorer web browser window. See Bug ID 347763 in the “Known issues and workarounds” on page 16.. If you see a link labeled “Click here to download and install JRE 5.0. The GUI requires JRE 5.Downloading and starting the GUI using Java Web Start (Windows) This procedure explains how to start the SnapManager graphical user interface on Windows.com:port where smoserver. go to the following: https://smo-server.domain.Do you want to proceed?.com is the fully qualified host name and domain on which you installed SnapManager and port is the listening port for the SnapManager server (27214. 2 If you see a popup dialog box with the message “There is a problem with the site’s security certificate.domain.” click Yes or Continue.” click that link. by default).0 updates 11 through 15 are recommended.0 updates 16 and 17 prevents the online Help button from displaying in the web-started GUI.. 3 Starting the graphical user interface 29 . Step 1 Action In the Microsoft Internet Explorer web browser window.

jnlp." Click Install.” In the menu that appears. The output should indicate Java version “1.sun. perform the following steps: ◆ ◆ ◆ On the License Agreement page. The exact mechanism to do this varies based on the version of Windows you are using. ◆ 5 If a window appears requesting that you install J2SE Runtime Environment 5.. Change your Windows configuration settings to always open files with extension “jnlp” with the program Java Web Start Launcher. 6 If you see a popup dialog box with the title “File Download” and the message “Do you want to save this file? application.5. select Typical and click Next...5. click Finish. select “I accept the terms in the license agreement” and click Next. On the Installation Completed window.0 opens.. A window for the installer for J2SE Runtime Environment 5.. Click here to install. ◆ ◆ 30 Starting the graphical user interface . SnapManager starts to download and opens. The JRE can be downloaded from Sun's web site: http://java.Step 4 Action If you see a link labeled “Download Java Web Start” and a banner with the message “This site might require the following ActiveX control: Java Plug-in 1. Go back to Step 1 and re-enter the SnapManager URL in Internet Explorer. The installation begins.0 Update 11). On the Setup Type page.Security Warning” containing the following text: “Do you want to install this software? Name: Java Plug-in 1.5. select Install ActiveX Control." Click Install.com Verify that Java is installed by running the following command: java -version.0.” perform the following steps: ◆ ◆ Install JRE 5.” perform the following steps: ◆ ◆ ◆ Click the message labeled “Click here to install. Internet Explorer displays “Internet Explorer .. The name of the window is “Java Plug-in 1.0_11” (which is Java 5.0.5.

4 or 1. The message contents and button labels vary based on platform.5. If you see a popup dialog box with the title “Java Platform SE binary . If you see a popup dialog box with the title “Warning .4+ is required for HTTPS support.” click Run.Security Warning” and the message “Do you want to run this software?. Starting the graphical user interface 31 . click Yes.Security” and a message about the certificate of the SnapManager web site. Download Java 1. you might see one or several of the following popup dialog boxes.” then the client has an older version of Java 1.Step 7 Action While downloading SnapManager on either a Windows or UNIX client. ◆ If you see a popup dialog box with the title “Warning . If you see a popup dialog box with a message about a hostname mismatch.5 Update 11. click Yes or Run. If you see a popup dialog box with the title “Java Web Start Launch File Error” and the message “The field <jnlp> has an invalid value: https. ◆ ◆ ◆ ◆ 8 The browser downloads and starts the SnapManager for Oracle graphical user interface. Java 1.Security” and a message about the signature of the SnapManager application. click Yes or Run.

32 Obtaining other NetApp documentation .com/NOW/products/interoperability/ The online Compatibility and Configuration Guide for NetApp’s FCP and iSCSI Products at http://now.netapp.cgi. ◆ ◆ ◆ The documentation for SnapDrive for UNIX or SnapDrive for Windows. Data ONTAP. and various interconnect methods.netapp. and Provisioning Manager) is available from the Access & Order Product Documentation page at: http://now.com/NOW/knowledge/docs/san/fcp_iscsi_config/ The online NOW Description Pages for SnapManager 3.Obtaining other NetApp documentation The NetApp NOW site contains the most current documentation for SnapManager.netapp. FCP and iSCSI Host Utilities. The SnapManager for Oracle Installation and Administration Guide (available as a downloadable HTML files or PDF file from the NOW site). and DataFabric Manager (including Operations Manager. SnapDrive for UNIX or SnapDrive for Windows. SAN storage system components.com/NOW/knowledge/docs/docs. See the following: ◆ The online Interoperability Matrix (IMT) under the SnapManager perspective at http://now.0 for Oracle and SnapDrive for UNIX or SnapDrive for Windows. Protection Manager.