IBM System Storage N series SnapManager 6.0.1 for ... · Microsoft SQL Server GUI will not restore any database in the backup set. (However, if the databases were not verified, then

IBM System Storage N series

SnapManager 6.0.1 for Microsoft SQLServer Release Notes

GC27-2052-12

��

Contents

Release summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Fixed issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Issues fixed in SnapManager 6.0.1 . . . . . . . . . . . . . . . . . . . . . . . . 3

SnapManager for Microsoft SQL Server GUI does not restore a database from a failed verificationbackup set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3SnapManager for Microsoft SQL Server backup verification and clone operations might fail becausethe default mount point directory path is too long . . . . . . . . . . . . . . . . . 3SnapManager for SQL Server incorrectly reports database verification by a remote server againstthe SnapVault destination as successful. . . . . . . . . . . . . . . . . . . . . . 4In some cases the SnapMirror for Microsoft SQL Server clone refresh cmdlet does not populate allnecessary mirror destination parameters. . . . . . . . . . . . . . . . . . . . . 4For a database that has had a file group deleted, running verification of its backup might fail . . . 4SnapManager 6.0 for Microsoft SQL Server transaction log backup fails with the error “Timeoutexpired”. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4SnapManager for SQL Server shows 0 transaction log backup copies available to be restored,although log backup copies are available. . . . . . . . . . . . . . . . . . . . . 5A delete clone operation fails if there are any open database connections.. . . . . . . . . . 5SnapManager for Microsoft SQL Server federated backup might fail when the driving FCI is notpart of backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Issues fixed in SnapManager 6.0 . . . . . . . . . . . . . . . . . . . . . . . . 6Generic SnapShot copy naming convention is not generic on VMDK-based configurations. . . . . 6Clone database may have "__clone" name appended even if the original database name is selectedas the clone name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6SnapManager for SQL (SMSQL) 64-bit does not detect SQL 2005 32-bit instance when SQL 64-bitinstance is installed. . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Unable to use the FQDN as backup verification server name. . . . . . . . . . . . . . . 6Remote clone to SnapMirror Destination volume fails while mounting snapshot. . . . . . . . 7Restore and clone may fail with error: “Logical file db_data is not part of database db, UseRESTORE FILELISTONLY to list the logical file names”. . . . . . . . . . . . . . . . 7

Known issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Backup with remote verification and remote cloning on available destination volumes not supportedon VMDK with VMFS data store . . . . . . . . . . . . . . . . . . . . . . . . 9Under certain conditions during a restore operation, a tail log is applied when it should not be . . . 9Last backup, restore, configuration, and next job information not being populated on the dashboard . 9Taking backups for only some of the databases on a vdisk might unexpectedly delete some logbackups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Snapshot verification from cmdlets does not use the server-specific verification server when theverification server is not explicitly mentioned. . . . . . . . . . . . . . . . . . . . 10Operation information not populating clustered SQL Server instance dashboards . . . . . . . . 10Federated backups can fail with the addition of a remote database . . . . . . . . . . . . 10SnapManager clone on remote server fails . . . . . . . . . . . . . . . . . . . . . 10Messages are not sent from a VMDK configuration . . . . . . . . . . . . . . . . . . 10Change in display when there are multiple transaction logs with the same timestamp . . . . . . 11

© Copyright IBM Corp. 2013 iii

Changes to published documentation . . . . . . . . . . . . . . . . . . . . . 13How to back up all databases on an SQL server . . . . . . . . . . . . . . . . . . . 13Required step for initial configuration missing from documentation . . . . . . . . . . . . 13

Websites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Copyright and trademark information . . . . . . . . . . . . . . . . . . . . . 17Trademark information . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

iv IBM System Storage N series: SnapManager 6.0.1 for Microsoft SQL Server Release Notes

Release summary

SnapManager 6.0.1 for SQL Server is a maintenance release fixing issuesknown in SnapManager 6.0 for SQL Server while maintaining the features inSnapManager 6.0 for SQL Server.

SnapManager 6.0 for SQL Server introduced the following new feature:

Microsoft SQL Server 2012 AlwaysOn Availability Groupsupport

Microsoft SQL Server 2012 AlwaysOn technology provides a set of features todeliver high availability and resiliency for SQL Server 2012 databases. TheAlwaysOn family of HA technologies includes Availability Groups that allowDBAs to have up to four additional copies of a database in a highly availableconfiguration. Additionally, these database copies can be used to offloadbackup tasks and read-only queries. Using SnapManager 6.0 for MicrosoftSQL Server, a DBA can manage Availability Groups as a single unit—allowingbacking up, restoring, and cloning at the AG level. SnapManager 6.0 forMicrosoft SQL Server also allows re-seeding secondary replicas of databases inAvailability Groups.

© Copyright IBM Corp. 2013 1

2 IBM System Storage N series: SnapManager 6.0.1 for Microsoft SQL Server Release Notes

Fixed issues

SnapManager 6.0.1 for SQL Server includes a number of fixed issues.

Note: All the issues fixed by SnapManager 6.0.1 are not included here.

Issues fixed in SnapManager 6.0.1

SnapManager 6.0.1 fixes a number of issues from previous releases.

SnapManager for Microsoft SQL Server GUI does not restore a databasefrom a failed verification backup set.

If one of the databases in a backup set fails verification, the SnapManager forMicrosoft SQL Server GUI will not restore any database in the backup set.(However, if the databases were not verified, then you can restore from any ofthem, even databases that would have failed verification.)

SnapManager for Microsoft SQL Server backup verification and cloneoperations might fail because the default mount point directory path istoo long

The default mount point directory is under a subdirectory in theSnapManager for SQL installation directory, for example, C:\ProgramFiles\IBM\SnapManager for SQL Server\SnapMgrMountPoint. This defaultmount point directory path can be too long for a cloned database, so thebackup verification and clone operation might fail with the following error:The file name "C:\Program Files\IBM\SnapManager forSQL Server\SnapMgrMountPoint\MPDisk001\Program Files\Microsoft SQLServer\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\WebAnalyticsServiceApplication_ReportingDB_ae6e1c79-cd9c-441f-ab76-8d284b8dd76cAggregation20120729.ndfThe database snapshot for online checks could not be created. Either thereason is given in a previous error or one of the underlying volumesdoes not support sparse files or alternate streams. Attempting toget exclusive access to run checks offline. WARNING: SQLServer DBCCCHECKDB failed." is too long to create an alternate stream name.

SnapManager for SQL 6.0.1 changes the default mount point directory path toa shorter path, but only for new installations. If you are upgrading from aprevious release, you can specify a shorter path in the Verification Settingsdialog box.


SnapManager for SQL Server incorrectly reports database verification bya remote server against the SnapVault destination as successful.

When a backup is scheduled with remote verification, the SnapManager forSQL Server backup job does not wait for the DataFabric Manager SnapVaultoperation to finish in cases where the SnapVault operation takes a long time.Further, SnapManager for SQL Server goes ahead and issues a message statingthat the verification job completed successfully, even though it did not receivestatus from the DataFabric Manager server.

In some cases the SnapMirror for Microsoft SQL Server clone refreshcmdlet does not populate all necessary mirror destination parameters.

If you use Clone Wizard to schedule a clone job with the optionsv SnapMirror Update enabledv Clone On Mirror Destination chosenv Use Available Drive Letter selectedv Change Clone Path selectedv Force Terminate Connection selected

then the scheduled job in Windows Task manager or SQL Agent is missing thefollowing options in the corresponding cmdlet, respectively:v -UpdateMirror

v -cloneonmir

v -chgpath

v -ForceTerminateConnection

For a database that has had a file group deleted, running verification ofits backup might fail

For a database that has had a file group deleted, running verification of itsbackup might fail with the following error:Unable to open the physical file...Operating system error 32: "32(The processcannot access the file because it is being used by another process.)".Could not open new database ’db__Clone’. CREATE DATABASE is aborted.

SnapManager 6.0 for Microsoft SQL Server transaction log backup failswith the error “Timeout expired”.

If a transaction log backup takes more than 10 minutes, it fails with themessage[SQL SMO Error]: Backup failed for Server ’SOMEW’.An exception occurred while executing a Transact-SQL statement or batch.Timeout expired. The timeout period elapsed prior to completion of the operationor the server is not responding.


In 6.0, SnapManager for SQL uses a different method than in prior releases forbacking up transaction logs, and this method has a default timeout of 10minutes.

SnapManager for SQL Server shows 0 transaction log backup copiesavailable to be restored, although log backup copies are available.

During a restore process using the SnapManager for SQL Server GUI, severaldatabases display 0 Transaction Logs, even though the logs have been backedup and are visible in the snapinfo directory. Because there are no log backupcopies shown as available to be restored, no up-to-the-minute or specificpoint-in-time restore operation can be performed.

A delete clone operation fails if there are any open database connections.

When there is only one database on a disk, and if the database has openconnections, then a delete clone operation fails with the message The databaseselected for detaching is currently in use, and the LUNs are notunmounted.

When there is more than one database on a LUN and the first database hasopen connections, then a delete clone operation fails with the message Thedatabase selected for detaching is currently in use, and the LUN is notunmounted. If any database other than the first has open connections, thenthe operation to detach those databases fails, but in this case the LUNs areunmounted.

SnapManager for Microsoft SQL Server federated backup might fail whenthe driving FCI is not part of backup.

In a failover cluster instance (FCI) configurations, a federated backup mightfail when it involves databases from more than one FCI residing on the samecluster node and the FCI that SnapManager for SQL connects to for triggeringthe backup is not part of that backup. The error you might see in the SMSQLreport is as followsRemote backup failed with FaultException<SmException>: Error code: 0xc0040817.Finished remote SMSQL Backup at [FCI1] hr = 0xc0040817

Error Code: 0xc0040817There is another SnapManager operation currently in progress on this server.Please retry this operation after the conclusion of current job.

Error occurred during backup creation on server [FCI1].

Fixed issues 5

Issues fixed in SnapManager 6.0

SnapManager 6.0 fixes a number of issues from previous releases. If you areupgrading from a release prior to SnapManager 6.0, you should be aware ofthese fixes.

Generic SnapShot copy naming convention is not generic onVMDK-based configurations.

If a database resides on VMDK disk, and is backed up with the genericnaming convention, the Snapshot copy created on storage system does nothave the generic names. Instead of having Snapshot copies named as"sqlsnap__<server>__recent", created on the storage system, the Snapshot copyis named as: "smvi__sqlsnap__<server>__recent__<timestamp>", which is notgeneric.

Clone database may have "__clone" name appended even if the originaldatabase name is selected as the clone name.

When cloning a database, SnapManager allows the use of the originaldatabase name as the clone database name if the original database does notexist on the target SQL Server instance. SnapManager does not use theoriginal database name for the clone, but appends "__clone" to the originaldatabase name as the clone name, even when the original database does notexist on the target SQL Server instance under the following conditions:v The database to be cloned resides on a LUN which contains multiple

databases.v Only one of databases is selected to be cloned.

SnapManager for SQL (SMSQL) 64-bit does not detect SQL 2005 32-bitinstance when SQL 64-bit instance is installed.

When you install both 64-bit of SQL 2008 and 32-bit of SQL 2005 SP3 on thesame Windows 2008 R2 server, SMSQL does not show 64-bit SQL server and32-bit SQL server at the same time.

Unable to use the FQDN as backup verification server name.

When using a FQDN as the verification instance name to perform aSnapManager for SQL Server backup verification operation, the operation mayfail with error code 0xc0040897. In the SMSQL backup/verification report, itwill show the following message:

[14:27:07.080] Integrity verification failed : External component has thrown an exception.[14:27:08.033] Remote verification failed with FaultException<SmException>: Error code: 0xc0040897.

[14:27:08.055] Error Code: 0xc0040897Failed to verify snapshot based full database backup.


Remote clone to SnapMirror Destination volume fails while mountingsnapshot.

Cloning a database from a backup set to available snapmirrored destinationvolume fails with below error:

Clone on snap mirror destination volume to a remote server (in case of VMDK’s) is failing:Remote clone operation failed: Error code: 0xc0041057, Error Code: 0xC0041057Further details may be found in the SnapManager report or event logs.

Cloning to remote destination failed due to incorrect datastore info updated inbackups.xml at destination. Backups.xml must be updated with correctdestination datastore and volume info before using backup to create clone onremote server. However, such info failed to get populated, thereby causingrestore/clone to fail stating datastore not found.

Restore and clone may fail with error: “Logical file db_data is not part ofdatabase db, Use RESTORE FILELISTONLY to list the logical file names”.

When performing a database restore or clone, the operation may fail with thefollowing error messages in SMSQL report:

Failed to prepare VDI mount snapshot.Error encountered when executing SQL command:Msg 3234, SevLevel 16, State 2, SQLState 42000

[Microsoft][ODBC SQL Server Driver][SQL Server]Logical file ’db_Data’ is notpart of database ’db’. Use RESTORE FILELISTONLY to list the logical file names.Msg 3013, SevLevel 16, State 1, SQLState 42000

[Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE DATABASE is terminatingabnormally.

Error Code: 0xc00408a0Unable to get VDI command to perform snapshot creation or LUN restore.

The SQL command executed.Failed to restore SQL Server database [db] of [inst].

The problem occurs under the following conditions:1. Multiple databases are sharing the same LUN or two LUNs.2. Among databases sharing LUNs, there is more than one database whose

name's first four characters are the same, and those databases belong tothe same SQL Server instance, or instances when the first four charactersof the instances' names are the same.

With deploying a configuration with the conditions outlined above, thedatabases will be backed up at the same time. In this case one or more ofbackup metadata files may be overwritten during the backup. When usingthis backup for restore or clone operation, the restore or clone will fail due to

Fixed issues 7

the missing metadata file. You might try to use another backup for restore orclone operation if available, as other backups may not have the same issue.


Known issues

You should be familiar with the known issues in SnapManager 6.0 for SQLServer.

Backup with remote verification and remote cloning on available destinationvolumes not supported on VMDK with VMFS data store

Attempting to mount a VMFS data store backup copy or trying to clone sucha backup copy can fail with the error Volume is read-only.

SnapManager for Microsoft SQL Server does not support remote verificationof available destination volumes for VMDK backup copies created on VMFSdata stores. It also does not support remote cloning of VMDK backup copiescreated on VMFS data stores. Attempting either of these operations results inthe error message.

Under certain conditions during a restore operation, a tail log is applied when itshould not be

During a restore operation from a full backup, if TransLogsToApply is set to 0,no logs should be applied, but if there are no log backups to be applied, andif the tail log is taken during the restore operation, then the tail log is stillapplied.

Last backup, restore, configuration, and next job information not beingpopulated on the dashboard

In clustered instances, the dashboard values for last backup, restoreconfiguration, and next job information is not filled in.

Taking backups for only some of the databases on a vdisk might unexpectedlydelete some log backups

When you have multiple databases on a vdisk, but take a full backup of onlysome of the databases, the transaction logs for those backed up databasesmight be deleted, even though they should be retained. For example, if youtake a full backup of databases db001_D, db002_D, and db003_D, then latertake a full backup of db003_D, and then later take a full backup of db001_D,the transaction logs for db001_D are deleted.


Snapshot verification from cmdlets does not use the server-specific verificationserver when the verification server is not explicitly mentioned

Even though there is a server-specific verification server set, if you use therestore-backup cmdlet and do not specify the verification server whenperforming a restore of a backup performed without verification, the defaultserver is used for verification.

Workaround: When using the restore-backup cmdlet, specify the verificationserver to use.

Operation information not populating clustered SQL Server instance dashboards

Information about the most recent backup, restore, configuration, and next joboperations is not populating the dashboard of cluster SQL Server instances.

Workaround: There is no workaround for this issue.

Federated backups can fail with the addition of a remote database

Federated backups can fail when databases from remote SQL Server instancesare added to nonfederated database groups.

Workaround: To back up databases from multiple remote hosts withoutfederation, create or schedule backups on those databases separately byconnecting to individual SQL Server hosts.

SnapManager clone on remote server fails

A SnapManager clone on a remote server might fail with the following error:"Operating system error 2 (The system cannot find the file specified.)"

This occurs when you apply transaction logs beyond the selected full backupsand the latest SnapInfo Snapshot copy is not available, even though the userinterface allows you to select newer log backups. Workaround: There is noworkaround for this issue.

Messages are not sent from a VMDK configuration

If you are running on VMDK over NFS, SnapManager cannot send EMS andAutoSupport messages. Despite the AutoSupport message failure,SnapManager indicates that the messages have been sent.

Workaround: There is no workaround for this issue.


Change in display when there are multiple transaction logs with the sametimestamp

When transaction logs are taken on multiple replicas of an Availability Group,several logs might have the same timestamp. When you view a list oftransaction logs (for example, from the Restore wizard) and logs have thesame timestamp, the name (timestamp) is shown with (1), (2), and so forth,appended to distinguish between the logs.

Known issues 11


Changes to published documentation

Some information about SnapManager for Microsoft SQL has becomeavailable after the guide was published. You should use this new informationin conjunction with the guide.

How to back up all databases on an SQL server

Using the Backup wizard, you can back up all databases on an SQL server byselecting the server on the Choose the Databases you want to backup orverify page instead of selecting individual databases. When you select theserver, even databases created after configuring the backup are backed up.

If you have more than one SQL instance, you must repeat this process foreach instance; however, instead of the selecting the server, you should selectthe instance.

This process is not currently detailed in the guide.

Required step for initial configuration missing from documentation

When first being set up, SnapManager for Microsoft SQL uses an additionalinternal authentication credential to connect to the DataFabric Manager server.You need to configure this, but it is not described in the SnapManager forMicrosoft SQL Server Installation and Administration Guide. Without this step, theConfiguration Wizard might fail.

This issue occurs only if you are using SnapDrive for Windows 6.2 or later.Before running SnapManager for Microsoft SQL Server the first time, from theDataFabric Manager server, enter the following command:dfm user add -r GlobalFullControl MyDomain\snapuser



Websites

IBM maintains pages on the World Wide Web where you can get the latesttechnical information and download device drivers and updates. Thefollowing web pages provide N series information:v A listing of currently available N series products and features can be found

at the following web page:www.ibm.com/storage/nas

v The IBM System Storage N series support website requires users to registerin order to obtain access to N series support content on the web. Tounderstand how the N series support web content is organized andnavigated, and to access the N series support website, refer to the followingpublicly accessible web page:www.ibm.com/storage/support/nseries/This web page also provides links to AutoSupport information as well asother important N series product resources.

v IBM System Storage N series products attach to a variety of servers andoperating systems. To determine the latest supported attachments, go to theIBM N series interoperability matrix at the following web page:www.ibm.com/systems/storage/network/interophome.html

v For the latest N series hardware product documentation, includingplanning, installation and setup, and hardware monitoring, service anddiagnostics, see the IBM N series Information Center at the following webpage:http://publib.boulder.ibm.com/infocenter/nasinfo/nseries/index.jsp


http://www.ibm.com/storage/nas

http://www.ibm.com/storage/support/nseries/

http://www.ibm.com/systems/storage/network/interophome.html

http://publib.boulder.ibm.com/infocenter/nasinfo/nseries/index.jsp


Copyright and trademark information

This section includes copyright and trademark information, and importantnotices.

Copyright information

Copyright ©1994 - 2013 Network Appliance, Inc. All rights reserved. Printedin the U.S.A.

Portions copyright © 2013 IBM Corporation. All rights reserved.

US Government Users Restricted Rights - Use, duplication or disclosurerestricted by GSA ADP Schedule Contract with IBM Corp.

No part of this document covered by copyright may be reproduced in anyform or by any means - graphic, electronic, or mechanical, includingphotocopying, recording, taping, or storage in an electronic retrievalsystem—without prior written permission of the copyright owner.

References in this documentation to IBM products, programs, or services donot imply that IBM intends to make these available in all countries in whichIBM operates. Any reference to an IBM product, program, or service is notintended to state or imply that only IBM’s product, program, or service maybe used. Any functionally equivalent product, program, or service that doesnot infringe any of IBM’s or NetApp’s intellectual property rights may beused instead of the IBM or NetApp product, program, or service. Evaluationand verification of operation in conjunction with other products, except thoseexpressly designated by IBM and NetApp, are the user’s responsibility.

No part of this document covered by copyright may be reproduced in anyform or by any means - graphic, electronic, or mechanical, includingphotocopying, recording, taping, or storage in an electronic retrievalsystem—without prior written permission of the copyright owner.

Software derived from copyrighted NetApp material is subject to thefollowing license and disclaimer:

THIS SOFTWARE IS PROVIDED BY NETAPP "AS IS" AND WITHOUT ANYEXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITEDTO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESSFOR A PARTICULAR PURPOSE, WHICH ARE HEREBY DISCLAIMED. INNO EVENT SHALL NETAPP BE LIABLE FOR ANY DIRECT, INDIRECT,


INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTEGOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESSINTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OFLIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUTOF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THEPOSSIBILITY OF SUCH DAMAGE.

NetApp reserves the right to change any products described herein at anytime, and without notice. NetApp assumes no responsibility or liability arisingfrom the use of products described herein, except as expressly agreed to inwriting by NetApp. The use or purchase of this product does not convey alicense under any patent rights, trademark rights, or any other intellectualproperty rights of NetApp.

The product described in this manual may be protected by one or more U.S.A.patents, foreign patents, or pending applications.

RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by thegovernment is subject to restrictions as set forth in subparagraph (c)(1)(ii) ofthe Rights in Technical Data and Computer Software clause at DFARS252.277-7103 (October 1988) and FAR 52-227-19 (June 1987).

Trademark information

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks ofInternational Business Machines Corporation in the United States, othercountries, or both. A complete and current list of other IBM trademarks isavailable on the Web at http://www.ibm.com/legal/copytrade.shtml

Linux is a registered trademark of Linus Torvalds in the United States, othercountries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks ofMicrosoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States andother countries.

NetApp, the NetApp logo, Network Appliance, the Network Appliance logo,Akorri, ApplianceWatch, ASUP, AutoSupport, BalancePoint, BalancePointPredictor, Bycast, Campaign Express, ComplianceClock, Cryptainer,CryptoShred, Data ONTAP, DataFabric, DataFort, Decru, Decru DataFort,DenseStak, Engenio, Engenio logo, E-Stack, FAServer, FastStak, FilerView,


FlexCache, FlexClone, FlexPod, FlexScale, FlexShare, FlexSuite, FlexVol,FPolicy, GetSuccessful, gFiler, Go further, faster, Imagine Virtually Anything,Lifetime Key Management, LockVault, Manage ONTAP, MetroCluster,MultiStore, NearStore, NetCache, NOW (NetApp on the Web), Onaro,OnCommand, ONTAPI, OpenKey, PerformanceStak, RAID-DP, ReplicatorX,SANscreen, SANshare, SANtricity, SecureAdmin, SecureShare, Select, ServiceBuilder, Shadow Tape, Simplicity, Simulate ONTAP, SnapCopy, SnapDirector,SnapDrive, SnapFilter, SnapLock, SnapManager, SnapMigrator, SnapMirror,SnapMover, SnapProtect, SnapRestore, Snapshot, SnapSuite, SnapValidator,SnapVault, StorageGRID, StoreVault, the StoreVault logo, SyncMirror, TechOnTap, The evolution of storage, Topio, vFiler, VFM, Virtual File Manager,VPolicy, WAFL, Web Filer, and XBB are trademarks or registered trademarksof NetApp, Inc. in the United States, other countries, or both.

All other brands or products are trademarks or registered trademarks of theirrespective holders and should be treated as such.

NetApp, Inc. is a licensee of the CompactFlash and CF Logo trademarks.

NetApp, Inc. NetCache is certified RealSystem compatible.

Copyright and trademark information 19


Notices

This information was developed for products and services offered in theU.S.A.

IBM may not offer the products, services, or features discussed in thisdocument in other countries. Consult your local IBM representative forinformation on the products and services currently available in your area. Anyreference to an IBM product, program, or service is not intended to state orimply that only that IBM product, program, or service may be used. Anyfunctionally equivalent product, program, or service that does not infringe onany IBM intellectual property right may be used instead. However, it is theuser's responsibility to evaluate and verify the operation of any non-IBMproduct, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not giveyou any license to these patents. You can send license inquiries, in writing to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, N.Y. 10504-1785U.S.A.

For additional information, visit the web at:http://www.ibm.com/ibm/licensing/contact/

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDESTHIS PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND,EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Somestates do not allow disclaimer of express or implied warranties in certaintransactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes willbe incorporated in new editions of the publication. IBM may make


improvements and/or changes in the product(s) and/or the program(s)described in this publication at any time without notice.

Any references in this information to non-IBM web sites are provided forconvenience only and do not in any manner serve as an endorsement of thoseweb sites. The materials at those web sites are not part of the materials forthis IBM product and use of those web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environmentsmay vary significantly. Some measurements may have been made ondevelopment-level systems and there is no guarantee that these measurementswill be the same on generally available systems. Furthermore, somemeasurement may have been estimated through extrapolation. Actual resultsmay vary. Users of this document should verify the applicable data for theirspecific environment.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly availablesources. IBM has not tested those products and cannot confirm the accuracyof performance, compatibility or any other claims related to non-IBMproducts. Questions on the capabilities of non-IBM products should beaddressed to the suppliers of those products.

If you are viewing this information in softcopy, the photographs and colorillustrations may not appear.


Notices 23

��

NA 210-06015_A0, Printed in USA

GC27-2052-12

Documents

IBM System Storage N series SnapManager 6.0.1 for ... · Microsoft SQL Server GUI will not restore any database in the backup set. (However, if the databases were not verified, then