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 19942009 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 systemwithout 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, NetAppthe 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

Table of Contents
Whats New in SnapManager for Oracle?. SnapManager overview . . . . . . . . Release Notes 3.0.1 update. . . . . . . New features . . . . . . . . . . . . . . CLI changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1 1 2 3

System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Confirming system requirements. . . . . . . . . . . . . . . . . . . . . . 8 System setup required to use SnapManager . . . . . . . . . . . . . . . . 8 SnapManager installation. . . . . . . . . . . . . . . . . . . . . . . . . . . 10 SnapManager components . . . . . . . . . . . . . . . . . . . . . . . . 10 Installing SnapManager . . . . . . . . . . . . . . . . . . . . . . . . . 10 Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Finding information on troubleshooting tips . . . . . . . . . . . . . . . . 12 Issues resolved in SnapManager 3.0.1 for Oracle . . . . . . . . . . . . . . 13 Known issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Accessing information about bugs . . . . . . . . . . . . . . . . . . . . 16 Known issues and workarounds . . . . . . . . . . . . . . . . . . . . . 16 Documentation issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Obtaining the latest version of the NetApp software . . . . . . . . . . . . 25 Getting the most up-to-date SnapManager software . . . . . . . . . . . 25 Obtaining the software from NOW . . . . . . . . . . . . . . . . . . . 25 Starting the graphical user interface. . . . . . . . . . . . . . . . . . . . Starting the GUI from the Command Line Interface. . . . . . . . . . Downloading and starting the GUI using Java Web Start (UNIX) . . Downloading and starting the GUI using Java Web Start (Windows). . . . . 26 26 26 29

Obtaining other NetApp documentation. . . . . . . . . . . . . . . . . . . 32

Table of Contents

vi

Table of Contents

Whats New in SnapManager for Oracle?

SnapManager overview

SnapManager 3.0 for Oracle empowers database administrators with the tools necessary to perform policy-driven data management, schedule and create regular database backups with minimal impact, restore data from these backups in the event of data loss or disaster, and create database clones for non-disruptive testing. With SnapManager, you can create backups on primary storage and create protected backups on secondary storage.

Release Notes 3.0.1 update

The SnapManager 3.0.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. See Restrictions on page 11. The Restrictions section indicates that SnapManager for Oracle Java Web Start client requires Java 1.5 and does not support Java 1.6. See Restrictions on page 11. 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. A workaround is also included. These release notes describe the issues in V3.0 that were fixed in V3.0.1. See Issues resolved in SnapManager 3.0.1 for Oracle on page 13. Using SnapManager 3.0.1 for Oracle, you can backup and clone Oracle 10gR2 (10.2.0.4) physical standby databases created using Oracle Data Guard services. Using Data Guard, DBAs can switch a primary database to a standby mode and vice versa. See Issues resolved in SnapManager 3.0.1 for Oracle on page 13. This edition of the release notes lists the minimum 4K block size requirement for the tablespace into which SnapManager 3.0.1 for Oracle is installed. See System requirements on page 8. Snapshot copies created in SnapManager 3.0 and 3.0.1 for Oracle on the primary node are being deleted incorrectly by the Protection Manager retention policy. See Known issues on page 15.

Whats New in SnapManager for Oracle?

This edition of the release notes includes a section listing documentation issues in the SnapManager 3.0 for Oracle Installation and Administration Guide. See Documentation issues on page 23. The SnapManager 3.0 for Oracle Installation and Administration Guide should be used, along with the changes cited in the 3.0.1 Release Notes, for the 3.0.1 release.

New features

SnapManager 3.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. 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 feature is accomplished by integration with Protection Manager, which uses datasets and policies to provide data protection on SnapVault and SnapMirror destinations. With data protection enabled, DBAs can leverage this new feature and also create clones of databases on secondary storage, helping DBAs create test and development environments easily and apart from their primary production storage. However, data protection and fast restore features are not available in SnapManager on a Windows host. Backup scheduling: DBAs can now schedule their backups to occur on a regular basis using SnapManagers scheduling feature in the graphical user interface (GUI). DBAs no longer need to rely on CRON jobs to execute scripts for automating backups. Volume-based restore of the database: SnapManager now offers two methods of restoring the database: file-based restore and a faster, volumebased restore. 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. Cloning and use of your custom plugin scripts: You can now create and use custom scripts that execute before or after a cloning operation. SnapManager includes an additional command and option in the graphical user interface to check the custom script installation. For example, you might create a custom script that determines whether the complete application using the target database is shut down. 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. With SnapManagers plugin check, you can execute your custom scripts as part of the regular clone process.

Whats New in SnapManager for Oracle?

Custom Snapshot copy names: With this version, you can now specify a naming convention or pattern to describe the Snapshot copies related to the profile you create or update. Graphical user interface updates: The SnapManager graphical user interface includes many enhancements, including the display of repositories, profiles within the repository, and backups and clones within profiles.

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. DBAs can execute multiple actions concurrently by backgrounding backup and clone operations and can update settings on multiple profiles at once. The GUI can be launched from multiple platforms. The GUI is installed at the same time as the host software. You can launch the GUI using Java Web Start. You can also launch it using a command.

Command line interface: Many commands include additional parameters to support policy-driven data protection and volume-based restore operations. Role-based access control for features: With Operations Manager integration, SnapManager provides additional security for features. Access is now governed by user roles. Broader platform and host environment support: SnapManager supports all platforms and host environments that SnapDrive 4.1 for UNIX and SnapDrive 6.0.2 for Windows support. Support for multiple file systems per disk group: Previously, SnapManager supported only one file system per disk group.

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. SnapManager offers a cloning plugin, which you can use to automate your custom scripts before and after you clone a database backup. Before you use the cloning plugin, use the plugin check command to verify the installation of plugin scripts on the SnapManager server. Custom scripts are stored in three directories: policy (for scripts that should always be run before the clone operation occurs), pre (for preprocessing scripts), and post (for post-processing scripts). This command applies to the server-side installation of SnapManager.

protection-policy list This command lists the protection policies that can be applied to a profile. The protection policy can be applied when a new profile is being created or

Whats New in SnapManager for Oracle?

updated on an existing profile. 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. Note Protection Manager and SnapDrive need to be installed in the server to enable SnapManager to use this command. The following commands have changed:

abort This command was removed. backup create A new -protect option has been added. This option indicates whether the backup should be protected to secondary storage. The -noprotect option specifies that the backup should not be protected to secondary storage. Only full backups are protected. If neither option is specified, SnapManager protects the backup as the default, if the backup is a full backup and the profile specifies a protection policy. The -retain-forever and -retain-normal options have been removed from this command. Instead of -retain-forever option, the -retain -unlimited option can be applied. Also, if the -retain option is not specified, then the retention class defaults to -hourly.

backup delete The -retain option has been removed from this command because the single retention count has been replaced by several retention classes.

backup free The -retain option has been removed from this command because the single retention count has been replaced by several retention classes.

backup list The list displays information about all backups for a specified profile. If the -verbose option is specified, 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

Whats New in SnapManager for Oracle?

This command has new options: -from-secondary -copy-id id and -host. If there is more than one copy on secondary storage, use the -copy-id parameter to specify which copy on secondary storage should be used to mount the backup.

backup restore This command has new options for how to restore protected data. A new -restorespec option or -from-secondary option can be specified. 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. You can specify one of the following options. If you dont specify an option, 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. -from-secondary: Tells SnapManager to restore the data from secondary storage.

You cannot use this option if the backup exists on primary storage; the primary backup must be freed before a backup can be restored from secondary storage. If there is more than one backup copy, you can specify which backup copy to use with the -copy-id option. If you use a temporary volume, specify the volume using the -temp-volume option. When restoring from secondary storage, SnapManager first attempts to restore data directly from the secondary storage system to the primary storage system (without involving the host). If SnapManager cannot perform this type of restore (for example, if files not part of the restore exist in a file system), then SnapManager attempts a host side file copy restore. SnapManager has two methods of performing a host side file copy restore from secondary. The method SnapManager selects is configured in the smo.config file:

If restore.secondaryAccessPolicy is set to direct, SnapManager clones the data on secondary storage, mounts the cloned data from the secondary storage system to the host, and then copies data out of the clone into the active environment. This is the default secondary access policy. If restore.secondaryAccessPolicy is set to indirect, SnapManager first copies the data to a temporary volume on primary storage, mounts the data from the temporary volume to the host, and then copies data out of the temporary volume into the active environment. This secondary access policy should be used only if the host does not have direct access to the secondary storage system.

Whats New in SnapManager for Oracle?

Restores using this method take twice as long as the direct secondary access policy because two copies of the data are made. In addition to the above options, a -fast option can be specified. This option enables the administrator to choose the process for the restore operation. Database administrators can force SnapManager to use the volume-based fast restore process rather than other restore processes, if all mandatory restore eligibility conditions are met. 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, if all restore eligibility conditions are met. If you specify the -fast option, but do not specify any parameter for -fast, SnapManager uses the -require parameter as a default. -override: Enables the database administrator, who knows that all overridable conditions can be overridden without negative consequences, to override non-mandatory eligibility checks and perform the volume-based fast restore. -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 you do not specify -fast, SnapManager uses the default backup restore -fast fallback. -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. This option prevents the restore from using the fast restore process.

backup show The list displays detailed information about a backup, including its protection status, backup retention class, and backups on primary and secondary storage.

clone create A new option -from-secondary can be specified. This option indicates that SnapManager should clone a copy of a backup that has been protected to secondary storage. If this option is not specified, SnapManager clones the copy from primary storage. Use the -copy-id option to specify which protected backup to use, if more than one copy exists.

clone show This command now indicates if the clone was created using the backup on primary or secondary storage.

Whats New in SnapManager for Oracle?

profile create New options like -comment, -protect -protection-policy and -retain can be specified. The -comment option specifies the comment for a profile describing the profile domain. The -protect and -protection-policy options govern whether backups can be protected to secondary storage. The -retain option specifies retention policy for backups created from the profile. You can set a retention count or a retention duration for a retention class (hourly, daily, weekly, monthly) or both. The duration is in units of the class (for example, hours for hourly, days for daily). If this option is not specified, then the retention class defaults to -hourly.

profile update New options like -comment, -protect -protection-policy and -retain can be specified. The -comment option specifies the comment for a profile describing the profile domain. The -protect and -protection-policy options govern whether or not backups can be protected to secondary storage. The -retain option specifies the retention policy for backups created from the profile. For each retention class (hourly, daily, weekly, monthly), you can specify a retention count or a retention duration or both. The duration is in units of the class (for example, hours for hourly, days for daily). If this option is not specified, then the retention class defaults to -hourly. If a retention class is specified and only a count or a duration is specified, then the field not specified defaults to 0.

profile show The output now displays the profile comment and new data protection attribute information such as associated dataset name, protection status, protection policy, conformance status (conformant, conforming, nonconformant, or none), and retention values.

smo_server restart The host credentials have been eliminated for this command. smo_server start The host credentials have been eliminated for this command.

Whats New in SnapManager for Oracle?

System requirements

Confirming system requirements

The most current information on SnapManagers requirements is available in the compatibility matrices on the NOW site. Because NetApp adds new components and updates products on an ongoing basis, it is a good practice to check these matrices. Details on SnapManager 3.0.1 for Oracle support are captured in the NetApp Interoperability Matrix (IMT) under the SnapManager perspective available at http://now.netapp.com/NOW/products/interoperability.

System setup required to use SnapManager

While setting up the host system, consider the following issues:

SnapManager for Oracle and SnapManager for SAP cannot run concurrently on the same host. SnapManager supports the following host platforms. See the Interoperability Matrix for details about supported protocols for each.

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.2.4 or higher for Protection Manager protection policy support. Install SnapDrive for UNIX or SnapDrive for Windows on the host platform, including the products required, such as the NetApp Host Utilities. Follow the instructions provided with the kit to set up the storage systems to work with the host. The SnapManager server requires 128 MB of memory. Each operation run by the SnapManager server requires 48 MB of additional memory while it is running.

System requirements

SnapManager requires a minimum 4K block size for the tablespace into which it is installed. SnapManager also operates in virtualized environments, such as VMware ESX and Windows Hyper-V. See the Interoperability Matrix for details. To use the SnapManager graphical user interface, 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. Starting the graphical user interface on page 26 explains how to download the SnapManager graphical user interface software and the required JRE.

SnapManager runs successfully with JRE 1.5; JRE 1.6 is not supported.

System requirements

SnapManager installation

SnapManager components

SnapManager 3.0.1 for Oracle is available only as software that you can download from the NetApp NOW site (http://now.netapp.com/). SnapManager 3.0 for Oracle is available both from CD-ROM or from the NetApp NOW site. You can also download SnapManager prerequisites, such as SnapDrive for UNIX or SnapDrive for Windows, from their product locations on the NOW site. The media kit includes the following items:

SnapManager Installation and Administration Guide CD-ROM, which contains the SnapManager for Oracle software in standard, installable package formats.

Installing SnapManager

Detailed instructions for installing SnapManager are in the SnapManager for Oracle Installation and Administration Guide. You must install SnapDrive for UNIX or SnapDrive for Windows on your host before installing SnapManager. See the SnapDrive documentation for installation instructions. Both the host and the client software are included in the SnapManager installation. There is no separate graphical user interface installation with this release. The following upgrade paths are supported for SnapManager 3.0.1 for Oracle:

3.0 to 3.0.1 2.2 to 3.0.1 2.1 to 3.0.1

In SnapManager 3.0 and 3.0.1 for Oracle perform these steps: 1. Install SnapManager. 2. Start the SnapManager server. 3. Verify the SnapManager system. 4. Upgrade the SnapManager repository.

10

SnapManager installation

Restrictions
SnapManager 3.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. Backups containing RAW tablespaces or ASM disks on Linux created with SnapManager 2.0 for Oracle or earlier cannot be cloned using SnapManager 2.1 for Oracle and later. SnapManager supports databases on the V-Series gateway storage systems, 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. 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.

Neither SnapDrive nor SnapManager support reverting to a previous version. SnapManager can be configured to catalog database backups with RMAN. If an RMAN recovery catalog is being used, the recovery catalog must be in a different database than the database that is being backed up. The SnapDrive for UNIX product supports more than one type of file system and/or volume manager on certain platforms. 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. See the SnapDrive for UNIX Installation and Administration Guide for more information about using this file. 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). The default port number must be the same for all port numbers involved in remote operations. 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, then the clone will fail. An error message appears describing why it failed. Protection Manager controls the secondary transfer schedules. In this case, 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. Alternatively, you might want to contact the storage administrator and ask for the backup to be transferred.

Restrictions

11

All LUNs within a volume should reside at the volume level or inside qtrees, but not in both. This is because if the data is residing on the qtrees and the user mounts the volume, then the data inside the qtrees is not protected. SnapManager operates within a Microsoft Clustering (MSCS) environment. However, 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. Backup creation might fail if SnapManager operations are run concurrently on the same host against a different ASM database. With regard to restoring from secondary storage system, in the smo.config file, the restore.secondaryAccessPolicy option can be set only to direct. The restore.secondaryAccessPolicy cannot be set to -indirect until the release of Protection Manager for use with DataFabric Manager 3.8 is available. SnapManager fails to delete a clone after the host name is changed for the host on which the clone is running. To fix this issue, rename the old host name to the same IP address in the client and server hosts file, and try to delete the clone again. In RedHat and Oracle Enterprise Linux 5.0, 5.1, and 5.2, the ext3 filesystem is not supported when deploying Oracle over raw devices using dynamic multipathing (DMMP) in a multipathing IO (MPIO) environment. The issue will be resolved in a forthcoming release of RedHat Enterprise Linux.

For more deployment considerations, limitations and restrictions, see the SnapManager for Oracle Installation and Administration Guide.

Finding information on troubleshooting tips

At the time of this release, there are some known problems and limitations for SnapManager. To locate information on known issues, check the following places:

The Troubleshooting chapter of the SnapManager for Oracle Installation and Administration Guide. The NetApp Bugs Online system, which is available on the NOW site.

12

Finding information on troubleshooting tips

Issues resolved in SnapManager 3.0.1 for Oracle

The following table describes issues that were resolved in SnapManager 3.0.1 for Oracle. Bug ID 321002, 321009, 333200, 333202 Description and resolution

Using SnapManager 3.0.1 for Oracle, you can backup and clone Oracle 10gR2 (10.2.0.4) physical standby databases created using Oracle Data Guard services. Using Data Guard, DBAs can switch a primary database to a standby mode and vice versa. Only full offline backups and clones of physical standby (standalone and RAC) databases are supported. Online backups of standby databases are not supported. Partial backups of standby databases are not supported. Restore of standby databases are not supported. Logical standby databases are not supported.

330059

In SnapManager 3.0 for Oracle, the Automatic Storage Management support library (ASMLib) was required when you were provisioning ASM disks with iSCSI or FCP on Linux. ASMLib applies only to SAN environments. Resolution: In SnapManager 3.0.1 for Oracle, ASMLib is no longer required when provisioning ASM disks with iSCSI or FCP on Linux.

330106

Attempting to connect to a remote SnapManager service running on HP-UX Itanium sometimes caused the remote service to unexpectedly terminate. In SnapManager for Oracle 3.0, you should use the SnapManager command line interface or graphical user interface from the same host running the SnapManager service. Resolution: In SnapManager 3.0.1 for Oracle, you no longer have to use the SnapManager command line interface or graphical user interface from the same host running the SnapManager service. You can connect to a remote SnapManager service running on HP-UX Itanium.

Issues resolved in SnapManager 3.0.1 for Oracle

13

Bug ID 330696

Description and resolution In SnapManager 3.0 for Oracle, backup schedules failed if the host name, service name, or user name contained a dash or hyphen. Resolution: SnapManager 3.0.1 for Oracle now supports dashes or hyphens in the host name, service name, and user name. For a repository to support SnapManager scheduling, the repository user name and service name must consist of only the following characters: alphabetic characters (A-Z), digits (0-9), minus sign (-), underscore (_), and period (.). The repository port can be any valid port number and the repository host name can be any valid host name. In other words, the host name must consist of alphabetic characters (A-Z), digits (0-9), minus sign (-), and period (.), but not an underscore (_). The backup schedules created in this repository run successfully.

330905

In SnapManager 3.0 for Oracle, the clone operation failed if the specified database instance name, referred to as the SID, contained more than 8 characters. A workaround involved editing the smo.config file. Resolution: SnapManager 3.0.1 for Oracle no longer restricts the length of the SID.

331276

In SnapManager 3.0 for Oracle, you could not preview a restore operation using the graphical user interface (GUI) when you were restoring a backup from secondary storage. Resolution: In SnapManager 3.0.1 for Oracle, you can preview all types of restore operations in the GUI, including a restore from secondary storage.

14

Issues resolved in SnapManager 3.0.1 for Oracle

Bug ID 335474

Description and resolution For a database running in a Microsoft Clustered Services (MSCS) active/standby cluster, SnapManager for Oracle backup schedules might not initiate backups when the database failed over to another node of the cluster. In SnapManager for Oracle 3.0, the workaround was to use the native Windows scheduler to define your backup schedules. Resolution: In SnapManager 3.0 for Oracle, for MSCS active/active clusters, you must also use the native Windows scheduler. However, for MSCS active/standby clusters in SnapManager 3.0.1 for Oracle, 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, 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. For instance, if SnapManager for Oracle is installed in the default directory, 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, create just one database profile. When you create the profile and are prompted to specify the host name for the target database, 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). Whenever the cluster switches activity from one node to the other, the SnapManager for Oracle schedules automatically start on the newly active node.

337107

In SnapManager 3.0 for Oracle, if you created a clone on a remote Windows host, the clone operation might fail. Resolution: In SnapManager 3.0.1 for Oracle, this is no longer an issue. You can create clones on remote Windows hosts.

342451

When you attempted to restore an ASM database using SnapManager 3.0 for Oracle and the database contained an ASM file that was larger than 4 GB, an error occurred. Resolution: In SnapManager 3.0.1 for Oracle, you can successfully restore an ASM database that contains a file larger than 4 GB.

Known issues

Known issues

15

Accessing information about bugs

For the latest information about workarounds, launch your Web browser, navigate to http://now.netapp.com/NOW/cgi-bin/bol, 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.0.1 for Oracle.

Bug ID 303285

Description and workaround SSL ZAPI exceptions occur on HPUX for SnapManager. Description: On HPUX machines connected to a storage system running certain versions of Data ONTAP, 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. Workaround: 1. Change http to https in SnapDrive and make the same change in the smo.config file in SnapManager 3.0.1 for Oracle. 2. Set use-https-to-filer option to off in the SnapDrive snapdrive.conf file. 3. Set use https option to false in the smo.config file.

300532

smo credential set command gives an error when /tmp is full. Description: While executing the smo credential set command, an error message appears as follows:
Error invoking command: SMO-20030: Credentials cannot be encoded as input by the user. Please ensure there are no trailing spaces or special characters in any credential fields.

This error occurs if you have an input with a trailing white space or if /tmp is full. Workaround: 1. To check if /tmp is full, run the command df -h /tmp. 2. If /tmp is full, create some space by deleting some unwanted files. 3. Run the smo credential set command again.
16 Known issues

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. 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. An error message appears as follows:
Invalid resource specified. Unable to find its ID on Operations Manager server <server_name>.

Workaround: 1. Log onto DataFabric Manager (DFM) using the NetApp Management Console (NMC). 2. Check if the DFM storage system entries are updated with the domain 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. 3. If the DFM storage system entries reflect host name instead of domain name, change it to the domain name. For example, consider the host name is rhine and domain name is rhine.rtp.netapp.com. If the DFM storage system entries are updated as rhine, change it to rhine.rtp.netapp.com.

Known issues

17

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. Sometimes, SnapManager might incorrectly show the protection state as Not Protected even when a copy of the backup exists on secondary storage. SnapManager cannot retrieve the necessary information to know that the backup exists on secondary storage. The cause of the problem is not presented via the CLI or GUI directly. To see the cause of the problem, look in the operation logs of the SnapManager server. Workaround: 1. Check the server operation logs for the specific error message that is preventing SnapManager from retrieving the locations of the backup. For example,
[DEBUG]: Unable to retrieve backup locations of backup "8abc01521c5082c6011c5082cbad0001" "backup304"

2. Then, 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. For example:
[DEBUG]: SD-10027: SnapDrive Message ID=2330 Code=xxx Category=null Source=null Message= ....error message....

3. Fix the problem that is causing the error message found in the SnapManager log file. 324973 Profile creation fails when ASM instance is not initiated. Description: If an ASM instance exists in the oratab file and the ASM instance is not initiated, then profile creation will fail. Workaround: There are two options.

Start the ASM instance. Else, change the line in the oratab file for the ASM instance into a comment.

325359

The command smo repository show may show incomplete operations. Description: The command smo repository show might show records for incomplete operations. Such records can be created when the SnapManager process dies unexpectedly while performing an operation such as system reboot or kill -9. Workaround: The system detects these operation records and marks them as FAILED during normal processing.

18

Known issues

Bug ID 325703

Description and workaround The backup delete operation fails intermittently. Description: SnapManager might intermittently report an error similar to the following (with possibly different values for some of the fields):
---- Debugging information ---cause-exception : java.lang.NullPointerException cause-message : null class : com.netapp.snapfile.model.Connection required-type : com.netapp.common.platform.windows.UserImpl path : /com.netapp.snapfile.model.Connection/ rootStorageComponent Map/entry/com.netapp.snapfile.model.HostMountedFileSystemFile/fileSecurityDes criptor/fileOwner/user line number : 1 -------------------------------

This error is reported by a library that is used internally by SnapManager. Workaround: This error occurs rarely. Try the backup delete operation again. 326171 Successful operations might appear as if they were terminated abnormally, if the system is under heavy load. Description: The command line interface or the graphical user interface might indicate operations as terminated abnormally, even though they completed successfully. This effect might occur if the system is under heavy load or out of computing resources. The following log entries or command line interface output might indicate such a situation:
Operation Id [8abc01a31d82ce5f011d82ce8c170001] failed. Error: "Operation abnormally terminated" Operation [MISSING ID] not found. Operation [Na67e68b33620ef3a4981bcb0a8d3c332] not found.

Workaround: 1. Edit the smo.config file. 2. Set the server.operationTimeout option to 3600000. 3. Check to see that the operation completed. In the Monitor tab in the graphical user interface. For the command line interface, use the operation list command. 4. Check the sizing of the system. The smo.config file is located in the properties subdirectory of SnapManagers installation directory.

Known issues

19

Bug ID 328882

Description and workaround SnapManager fails to discover ASM disks when using a version of oracleasm-support at or above 2.1.0. Description: On systems with a version of oracleasm-support that is at or above 2.1.0, 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. Error: Disk "<diskname>" is a valid ASM disk com.netapp.oracle.platform.asmlib.ASMLibException: ASM-10001: ASMLib disk identifier <diskname> is unknown to ASMLib. at com.netapp.oracle.platform.asmlib.ASMLib.queryDisk(ASMLib.java:86) at com.netapp.snapfile.discovery.ASMLibDeviceDiscoveryStep.map (ASMLibDeviceDiscoveryStep.java:77) at com.netapp.snapfile.discovery.OneToOneDiscoveryStep.discover (OneToOneDiscoveryStep.java:21) at com.netapp.snapfile.discovery.DiscoverySession.discover (DiscoverySession.java:168) ...

Workaround: Edit the file /etc/init.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.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>, <minor number>]

331847

Snapshot copies created in SnapManager 3.0 and 3.0.1 for Oracle on the primary node are being deleted incorrectly by the Protection Manager retention policy. If the protection policys retention policy in Protection Manager is shorter than the retention policy defined in SnapManager, then Protection Manager deletes the Snapshot copies on the primary node. After the Snapshot copies are deleted, if you attempt to perform SnapManager operations (such as restore, clone, or mount), 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 policys retention policy in Protection Manager to values greater than the retention policy defined in SnapManager.
20 Known issues

Bug ID 331855

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

Known issues

21

Bug ID 333558

Description and workaround Starting with Oracle 11g, passwords are case sensitive. Although Oracle provides an option to make case insensitive, incorporation of this option would have had adverse affects on other SnapManager for Oracle options. Therefore, passwords in SnapManager for Oracle cloning operations are case sensitive. Placing an spfile on a different volume might prevent creation of a clone. See the NetApp Knowledge Base article KB7518 about NFS mount options. Workaround: 1. Move the database directory from Oracle_home to another volume. 2. In Oracle_home, create a soft link to the database.

338437

347763

The SnapManager GUI fails to display the Help button. When the user launches the SnapManager GUI via Java Web Start, in some cases the GUI never displays the Help button in the wizards. This problem occurs only if the all of the following conditions are true:

The GUI is launched via Java Web Start. The GUI host is running on Windows, Linux, or Solaris. The GUI host has Java 5 update 16 or 17 installed.

Workaround: Two workarounds are available:

Instead of launching the GUI via Java Web Start, install SnapManager on the client host and then launch the GUI via the command line (UNIX) or the Start menu (Windows). On the GUI host, uninstall Java 5 and reinstall Java 5 update 11 (the same Java version used by the SnapManager server).

348164

When Protection Manager restores copies of the primary data, Data ONTAP adds a restore_symboltable file in the destination directory. This restore_symboltable file prevents SnapManager for Oracle from performing volume-based snapshot restores in the future. Workaround: After you successfully restore the data from secondary storage, you can delete this file from the directory. This enables SnapManager for Oracle to perform a volume-based restore upon request.

22

Known issues

Documentation issues
The following issues have been found in the SnapManager 3.0 for Oracle Installation and Administration Guide. 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. However, the statement should read: SnapManager does support OS-authentication for RAC databases for both ASM and non-ASM environments. 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. These statements were removed. 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 systems local administrator group, the local administrators group of this system, and the Oracle DBA. The Oracle DBA was listed as ORA_SID_DBA. However, this should have stated ORA_DBA. 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. However, the example included an additional asterisk (*). ASM_DISKSTRING = '/mnt/my-asm-disks/dir1/*,/opt/NetApp/smo/mnt/*/*/*' However, given the example information, this should be:
ASM_DISKSTRING = '/mnt/my-asm-disks/dir1/*,/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, this requirement is actually a minimum of 4K block space.

Documentation issues

23

Page 225

Description and resolution Chapter: SnapManager command reference The credential delete command shows incorrect syntax information. The command has four distinct sections: host, repository, profile, and quiet/verbose. 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. The command has four distinct sections: host, repository, profile, 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. However, the list option should not include a dash preceding the option. Use protection-policy list instead without the dash.

24

Documentation issues

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. SnapManager 3.0.1 for Oracle is available only as software that you can download from the NetApp NOW site (http://now.netapp.com/). SnapManager 3.0 for Oracle is available both from CD-ROM or from the NetApp NOW site. The CD and the download site each contain the server software and the graphical user interface client software. To download the software from the NOW site, complete the following steps. Step 1 Action Log into the NOW site at http://now.netapp.com. In the fields on the right side of the page, complete the following steps: 1. Enter your user name and password. Click Login. 2. From the Software Download section, click Download 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. Review the information on this page. At the bottom of this page, click Continue to go to the Software Download page. If you need to download the SnapDrive product, go to the row in the Software Download page for the product. Then follow the links to the Software Description page for the product. Download the documentation from the Software Description page. For instructions to install the software, see the SnapManager for Installation and Administration Guide.

Obtaining the software from NOW

Obtaining the latest version of the NetApp software

25

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, you can easily start the SnapManager GUI by using a command (UNIX) or by selecting the program from a list of programs (Windows). Note Before starting the SnapManager GUI, ensure that the SnapManager server is already started. To start the GUI from a host on which the SnapManager server is already installed, 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. Before downloading the graphical user interface, complete the following tasks:

Start the SnapManager server. Open a Mozilla Firefox web browser window.

The GUI requires JRE 5.0. More specifically, JRE 5.0 updates 11 through 15 are recommended. Use of JRE 5.0 updates 16 and 17 prevents the online Help button from displaying in the web-started GUI. See Bug ID 347763 in the Known issues and workarounds on page 16.

26

Starting the graphical user interface

Step 1

Action If you have not already installed the Java Runtime Environment (JRE) on the client, install the JRE 5.0 Update 11. The JRE can be downloaded from Suns web site: http://java.sun.com. Verify that Java is installed by running the following command: java -version. The output should indicate Java 1.5 (which is Java 5.0). (The output varies based on platform.) For Linux and Solaris, the version should be 1.5.0_11. Verify that Java Web Start is accessible by running the following command: which javaws. The output should display the exact path to javaws. In the Mozilla Firefox web browser window, go to the following: https://smo-server.domain.com:port where smoserver.domain.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, by default) .

If you see a popup dialog box with the title Unable to verify the identity of SnapManager as a trusted site, click Accept this certificate. If you then see a popup dialog box with the title Security Error: Domain Name Mismatch, click OK. Click the link labeled Launch SnapManager for Oracle.

6 7

Starting the graphical user interface

27

Step 8

Action If you see a popup dialog box with the title Opening application.jnlp, perform the following steps:

Select Open with and then click Browse. In the file chooser popup window, specify the path to javaws as determined previously and click Open. The file chooser popup window closes. In the Opening application.jnlp window, click the checkbox labeled Do this automatically for files like this from now on. In the Opening application.jnlp window, click OK. The window closes.

While downloading SnapManager on either a Windows or UNIX client, you might see one or several of the following popup dialog boxes. The message contents and button labels vary based on platform.

If you see a popup dialog box with the title Warning - Security and a message about the certificate of the SnapManager web site, click Yes. If you see a popup dialog box with a message about a hostname mismatch, click Yes or Run. If you see a popup dialog box with the title Warning - Security and a message about the signature of the SnapManager application, click Yes or Run. If you see a popup dialog box with the title Java Platform SE binary - Security Warning and the message Do you want to run this software?, click 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. Java 1.4+ is required for HTTPS support, then the client has an older version of Java 1.4 or 1.5. Download Java 1.5 Update 11.

10

The browser downloads and starts the SnapManager for Oracle graphical user interface.

28

Starting the graphical user interface

Downloading and starting the GUI using Java Web Start (Windows)

This procedure explains how to start the SnapManager graphical user interface on Windows. Before downloading the graphical user interface, complete the following tasks:

Start the SnapManager server. Open a Microsoft Internet Explorer web browser window.

The GUI requires JRE 5.0. More specifically, JRE 5.0 updates 11 through 15 are recommended. Use of JRE 5.0 updates 16 and 17 prevents the online Help button from displaying in the web-started GUI. See Bug ID 347763 in the Known issues and workarounds on page 16.

Step 1

Action In the Microsoft Internet Explorer web browser window, go to the following: https://smo-server.domain.com:port where smoserver.domain.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, by default).

If you see a popup dialog box with the message There is a problem with the sites security certificate...Do you want to proceed?, click Yes or Continue. If you see a link labeled Click here to download and install JRE 5.0 and the application, click that link.

Starting the graphical user interface

29

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.5... Click here to install, perform the following steps:

Click the message labeled Click here to install... In the menu that appears, select Install ActiveX Control... Internet Explorer displays Internet Explorer - Security Warning containing the following text: Do you want to install this software? Name: Java Plug-in 1.5." Click Install. A window for the installer for J2SE Runtime Environment 5.0 opens. The name of the window is Java Plug-in 1.5." Click Install.

If a window appears requesting that you install J2SE Runtime Environment 5.0, perform the following steps:

On the License Agreement page, select I accept the terms in the license agreement and click Next. On the Setup Type page, select Typical and click Next. The installation begins. On the Installation Completed window, click Finish. SnapManager starts to download and opens.

If you see a popup dialog box with the title File Download and the message Do you want to save this file? application.jnlp, perform the following steps:

Install JRE 5.0. The JRE can be downloaded from Sun's web site: http://java.sun.com Verify that Java is installed by running the following command: java -version. The output should indicate Java version 1.5.0_11 (which is Java 5.0 Update 11). Change your Windows configuration settings to always open files with extension jnlp with the program Java Web Start Launcher. The exact mechanism to do this varies based on the version of Windows you are using. Go back to Step 1 and re-enter the SnapManager URL in Internet Explorer.

30

Starting the graphical user interface

Step 7

Action While downloading SnapManager on either a Windows or UNIX client, you might see one or several of the following popup dialog boxes. The message contents and button labels vary based on platform.

If you see a popup dialog box with the title Warning - Security and a message about the certificate of the SnapManager web site, click Yes. If you see a popup dialog box with a message about a hostname mismatch, click Yes or Run. If you see a popup dialog box with the title Warning - Security and a message about the signature of the SnapManager application, click Yes or Run. If you see a popup dialog box with the title Java Platform SE binary - Security Warning and the message Do you want to run this software?, click 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. Java 1.4+ is required for HTTPS support, then the client has an older version of Java 1.4 or 1.5. Download Java 1.5 Update 11.

The browser downloads and starts the SnapManager for Oracle graphical user interface.

Starting the graphical user interface

31

Obtaining other NetApp documentation

The NetApp NOW site contains the most current documentation for SnapManager, SnapDrive for UNIX or SnapDrive for Windows, FCP and iSCSI Host Utilities, SAN storage system components, and various interconnect methods. See the following:

The online Interoperability Matrix (IMT) under the SnapManager perspective at http://now.netapp.com/NOW/products/interoperability/ The online Compatibility and Configuration Guide for NetApps FCP and iSCSI Products at http://now.netapp.com/NOW/knowledge/docs/san/fcp_iscsi_config/ The online NOW Description Pages for SnapManager 3.0 for Oracle and SnapDrive for UNIX or SnapDrive for Windows. The SnapManager for Oracle Installation and Administration Guide (available as a downloadable HTML files or PDF file from the NOW site).

The documentation for SnapDrive for UNIX or SnapDrive for Windows, Data ONTAP, and DataFabric Manager (including Operations Manager, Protection Manager, and Provisioning Manager) is available from the Access & Order Product Documentation page at: http://now.netapp.com/NOW/knowledge/docs/docs.cgi.

32

Obtaining other NetApp documentation