Symbols A B C D E F G I L M N O P R S T U V W
Index
Symbols
- *.bak files
- *.fbk files
- *.trb files
- *.trn files
- *__Mount backup set name
- *__recent Snapshot names
A
- Access LUN in Snapshot
- administration, Microsoft SQL Server
- archives
- disaster recovery guidelines
- recovering SQL Server databases
- restoring databases from
- restoring volumes from SnapManager backups archived with SnapVault
- archiving SnapManager backup sets
- about
- choosing the best way to archive
- guidelines for
- importance of complete backup sets
- scheduling considerations for
- initiated automatically
- after a backup or verification
- using SnapVault
- initiated manually
- using a Windows backup utility
- using NDMP or dump
- unsupported methods
- using CIFS
- using NFS
- authentication method
- SQL Server
- Windows
- Auto Shrink option, SQL Server database
B
- Backup and Verification tab
- Invalid database label
- performing a database verification
- performing a full database backup
- performing a transaction log backup
- scheduling a job to run later
- using the Run Command After Operation feature
- backup management groups
- about
- assigning a new full database backup to a group
- changing the group assignment for an existing full database backup
- using with SnapManager operations
- database verification
- explicit deletion of multiple backup Snapshot copies
- full database backup
- backup method
- Snapshot-based
- stream-based
- backup retention. See Snapshot copies
- backup sets, SnapManager
- archiving a complete backup set
- data organization within
- guidelines for restoring
- how Snapshot copies are used
- labeled SnapLUN
- naming convention for
- Backup Wizard
- Invalid database label
- performing a database verification
- performing a full database backup
- performing a transaction log backup
- scheduling a job to run later
- using the Run Command After Operation feature
- bulk-logged recovery model, SQL Server
- as supported by SnapManager
- definition of
- busy Snapshot
- avoiding after a SnapManager operation
- mounting and attaching a database without restoring it
- restoring to an alternate location using writable Snapshot
- avoiding during a SnapManager operation
- database verification only
- full database backup with verification
- when leaving database attached after verification
- avoiding while archiving SnapManager backups
- using a Windows backup utility
- using NDMP or dump
- using SnapVault
- avoiding while restoring a volume
- from a SnapVault archive
- deleting
- unable to delete using SnapManager
- using Data ONTAP
C
- CIFS protocol, as supported by SnapManager
- access to LUN objects
- cannot be used to archive LUNs
- cannot be used to back up or restore databases
- cluster. See Windows cluster
- color, database icon
- Configuration Wizard
- about
- how it stores databases on volumes
- migrating databases back to local disks
- migrating databases from local disks to LUNs
- moving multiple SnapInfo directories to a single SnapInfo directory
- Reconfig database label
- when to run the Configuration Wizard
- copy-based restore method
D
- Data ONTAP
- compatibility with SnapDrive
- product documentation
- storage system requirement
- database consistency checker. See DBCC
- database icon color
- database label
- Invalid
- Reconfig
- database verification
- avoiding busy Snapshot
- information you need to specify
- running a command after the operation finishes
- scheduling the job to run later
- using the Backup and Verification tab
- using the Backup Wizard
- databases, SQL Server
- backing up after renaming
- backing up before installing SnapManager
- maximum per LUN
- maximum per SQL Server computer
- maximum per SQL Server instance
- restoring from archive
- DBCC
- as used by SnapManager Backup
- as used by SnapManager Restore
- as used by the Configuration Wizard
- as used by the SmSqlBi command (the CLI)
- definition of
- drive letters required for verifying a backup
- specifying settings
- disaster recovery
- general guidelines
- restoring system databases
- using NDMP or dump archives
- general procedure
- guidelines
- using other SQL Server backup sets
- using SnapMirror replication
- general procedure
- guidelines
- using SnapVault archives
- general procedure
- guidelines
- distribution database, definition of
- documentation
- NetApp on the Web (NOW)
- reference documents
- drive letters required for DBCC
- dump command, storage system
- archiving LUNs that contain SnapManager backup sets
- compared with other archive methods
E
- Enterprise Manager.
- See SQL Server Enterprise Manager
F
- FCP
- LUN access protocol
- LUN driver
- filer. See storage system
- filer-side license.
- See per-storage system license
- Fractional space reservation policy settings in SMSQL
- full database backup
- failure of concurrent backup of multiple databases
- information you need to specify
- running a command after the operation finishes
- scheduling the job to run later
- selecting databases at the instance level
- about
- using the Backup and Verification tab
- using the Backup Wizard
- Snapshot copy-based backup method
- stream-based backup files
- stream-based backup method
- using the Backup and Verification tab
- using the Backup Wizard
- volume-wide backups
- what to do if the backup fails
- full recovery model, SQL Server
- as supported by SnapManager
- definition of
- full-text search catalogs, SQL Server
- database
G
- guidelines
- for archiving SnapManager backup sets
- for disaster recovery
- for disaster recovery using archives
- for performing a SnapManager Restore operation
- choosing the type of restore to perform
- preparing to perform a restore operation
- for restoring from a SnapManager backup set
- for volume sizing
I
- installation directory, SnapManager
- specifying during interactive installation
- specifying during unattended installation
- installing SnapManager on a standalone system
- in interactive mode
- in unattended mode
- storage system requirements for
- Windows host system requirements for
- installing SnapManager on a Windows cluster
- and creating a new Windows cluster
- disk requirements for
- storage system requirements for
- system configuration requirements for
- Windows host system requirements for
- interactive mode
- installing SnapManager
- uninstalling SnapManager
- upgrading SnapManager
- Invalid database label
- IP address, setting preferred
- iSCSI
- LUN access protocol
- LUN access protocol documentation
- LUN driver
L
- label, database
- Invalid
- Reconfig
- license requirements
- FCP protocol
- iSCSI protocol
- SnapMirror
- SnapRestore
- licenses
- SnapManager
- storage system requirements
- Windows host system requirements
- log shipped databases
- database restore of
- transaction log backup of
- up-to-the-minute restore of
- LUN access protocol
- iSCSI documentation
- LUN driver
- LUN size calculations
- LUNs not visible in Configuration Wizard
M
- management groups.
- See backup management groups
- Management Studio.
- See SQL Server Management Studio
- master database, definition of
- MDAC (Microsoft Data Access Components) version
- Microsoft SQL Server. See SQL Server
- mirrored volumes
- recovering SQL Server databases from. See SnapMirror replication, restoring from
- replicating SnapManager backups to. See SnapMirror replication of SnapManager backups
- model database, definition of
- mount point
- limitations
- limitations in a clustered environment
- Mounted volume naming conventions
- mounted volumes in SnapManager
- MSCS environment. See Windows cluster
- msdb database, definition of
- multiple-instance cluster
N
- NDMP-based backup utility
- archiving LUNs that contain SnapManager backup sets
- compared with other archive methods
- NearStore, archiving LUNs that contain SnapManager backup sets
- NFS protocol
- cannot be used to archive LUNs
- NOW (NetApp on the Web)
- NTBackup
- NTFS
- NVRAM
O
- online Snapshot. See snapshot-based
- operating system
- storage system requirements
- Windows host system requirements
P
- per-SQL Server license
- per-storage system license
- point-in-time restore
- preferred IP address, setting
- preinstallation
- preparing a Windows host system
- verifying storage system requirements
- verifying Windows host system requirements
- what to read
- protocol
- CIFS
- FCP
- iSCSI
- NDMP
R
- rebuildm.exe (rebuild master)
- Rebuildm.exe utility
- Reconfig database label
- recovery models, Microsoft SQL Server
- as supported by SnapManager
- definition of
- remote administration server
- Microsoft SQL Server requirement for
- other requirements for
- other requirments for
- SnapDrive requirement for
- remote verification server
- connectivity requirements for
- drive letters required for DBCC
- other requirements for
- SnapDrive requirement for
- system requirements
- replicating SnapManager backups.
- See SnapMirror replication 255
- Report directory, SnapManager
- changing the location
- default location
- option to remove during uninstallation
- remote access to
- reports, SnapManager operational
- deleting a report
- printing a report
- types of
- viewing a report
- requirements
- storage system
- transaction log space
- Windows host system
- restore method
- copy-based
- snapshot-based
- stream-based
- restore Snapshot copies
- about
- deleting
- restoring databases
- after renaming a database
- using a point-in-time restore
- using an up-to-the-minute restore
- with log-shipping implemented
- retention of backup Snapshot copies. See Snapshot copies
- rolling snapshots, SnapDrive
- advantages over increased SnapManager backups
- to supplement automatic replication
- Run Command After Operation feature
- and generic backup naming (__recent suffix)
- configuring default values
- running a script from a UNC path
- using
S
- SAN boot LUN
- scheduling
- archival of SnapManager backups
- running a backup or verification job for later
- security authentication. See authentication method
- server-side license. See per-SQL Server license
- service account, SnapManager
- in workgroup mode
- requirements
- setting a preferred IP address
- setup.exe utility
- simple recovery model, SQL Server
- as supported by SnapManager
- definition of
- SMSQLReportFolder share
- SnapDrive
- compatibility with SnapManager and Data ONTAP
- overview
- when to use as opposed to SnapManager
- product documentation
- rolling Snapshots
- storage requirements
- Windows host system requirements
- SnapInfo directory, SnapManager
- moving multiple SnapInfo directories to a single SnapInfo directory
- naming conventions for
- rules for storing
- SnapManager Backup
- specifying the name and location
- Advanced SnapInfo Directories
- Single SnapInfo Directory
- system databases stopped by SnapManager
- transaction log backup file names
- user databases detached by SnapManager
- SnapLUN backup set label
- SnapManager
- application overview
- command- line interface
- graphical user interface
- how it stores databases on volumes
- how it uses Snapshot copies as backups
- how it uses Snapshots as a restore precaution
- how it works with other backup methods
- how it works with SnapDrive
- how you use it
- maximum configurations supported by
- new functionality with this version
- relationship with other Data ONTAP-based components
- relationship with SQL Server components
- what it does
- what it does not do
- when to use it
- when to use SnapDrive instead
- where you install and run it
- application settings
- configurable from the Configuration Wizard
- configurable outside of the Configuration Wizard
- backup sets
- archiving a complete backup set
- data organization within
- guidelines for restoring from
- naming convention for
- installing or upgrading
- compatibility with SnapDrive
- installing on a standalone system
- installing on a Windows cluster
- option to remove Report directory during uninstall
- preparing a Windows host system for
- preparing to install
- reinstalling
- storage system requirements for
- uninstalling
- upgrading
- what to read
- Windows host system requirements for
- terminology
- user interface
- command-line interface (CLI)
- Configuration Wizard
- SnapManager Backup
- SnapManager Reports
- SnapManager Restore
- SnapManager Backup
- deleting oldest Snapshot copies with
- limitations
- managing the number of Snapshot copies and backup sets
- performing a database verification
- about
- default verification settings
- information you need to specify
- using the Backup and Verification tab
- using the Backup Wizard
- performing a full database backup
- about
- default backup settings
- default verification settings
- information you need to specify
- using the Backup and Verification tab
- using the Backup Wizard
- performing a transaction log backup
- about
- default backup settings
- information you need to specify
- using the Backup and Verification tab
- using the Backup Wizard
- remote verification with
- requirements
- starting or scheduling jobs
- database verification
- full database backup
- transaction log backup
- using backup management groups
- what it does
- when to back up your databases
- See also backup sets
- SnapManager Reports
- about
- deleting a report
- printing a report
- Report directory
- changing the location
- default location
- option to remove during uninstall
- viewing a report
- SnapManager Restore
- about
- cluster failure during
- cluster group state during
- preparing to restore a backup set
- restoring from archive with
- Snapshot copies created as a precaution
- SnapManager support
- SnapManager system requirements
- storage system
- Windows host system
- SnapMirror replication of SnapManager backups
- how it works
- overview
- scheduling considerations
- storage system license requrements
- supplementing with rolling Snapshots
- SnapMirror replication, restoring from
- disaster recovery guidelines
- recovering SQL Server databases
- SnapRestore
- Snapshot copies
- backup Snapshot copies
- about
- automatically deleting the oldest
- explicitly deleting multiple
- naming conventions
- maximum allowed per volume
- restore Snapshot copies
- about
- explicitly deleting
- naming convention
- Snapshot copy-based
- backup method
- restore method
- technology provided by Data ONTAP
- SnapVault archives
- archiving SnapManager backup sets
- restoring a storage system volume from
- space requirements for transaction logs
- SQL Browser service
- no LUNs in Configuration Wizard
- Windows host system requirements
- SQL Server
- *.bak files
- *.trn files
- administration
- calculating database size
- full-text search catalogs
- recovery models
- as supported by SnapManager
- definition of
- SnapManager rules for storing databases
- system databases
- definition of
- stopped by SnapManager
- user databases
- definition of
- detached by SnapManager
- Windows host system requirements
- See also SQL Browser service
- See also SQL Server 2000
- See also SQL Server 2005
- See also SQL Server authentication method
- See also SQL Server database
- See also SQL Server Enterprise Manager
- See also SQL Server instance
- See also SQL Server Management Studio
- SQL Server 2000
- Rebuildm.exe utility
- verifying an SQL Server 2005 database
- SQL Server 2005
- MDAC version
- no user databases on root LUN
- setup.exe utility
- SQL Browser service
- verifying an SQL Server 2000 database
- SQL Server authentication method
- described
- for accessing SQL Server
- limitations when connecting to a remote administration server
- limitations when scheduling a remote verification server
- SQL Server database
- Auto Shrink option
- SQL Server Enterprise Manager
- backing up transaction logs in a SnapManager environment
- detecting SnapManager transaction log backups
- viewing SnapManager full database backup files
- SQL Server instance
- as a remote administration server
- other requirements for
- SnapDrive requirement for
- verifying host system requirements
- as a remote verification server
- connectivity requirements for
- drive letters required for DBCC
- other requirements for
- SnapDrive requirement for
- verifying host system requirements
- authentication method used to connect to
- maximum databases per
- maximum per SQL Server computer
- selecting databases at the instance level
- full database backup
- transaction log backup
- verifying host system requirements for
- See also SQL Server
- SQL Server Management Studio
- backing up transaction logs in a SnapManager environment
- detecting SnapManager transaction log backups
- viewing SnapManager full database backup files
- SQL__* SnapInfo subdirectory names
- sqlsnap__* snapshot names
- storage system
- licenses
- requirements for SnapManager
- stream-based operations
- backup file names
- backup method
- restore method
- system databases, Microsoft SQL Server
- backing up
- definition of
- distribution database, definition of
- master database, definition of
- migrating to LUNs
- model database, definition of
- msdb database, definition of
- restoring
- stopped by SnapManager
- tempdb database, definition of
- system requirements for SnapManager
- storage system
- Windows host system
T
- tempdb database, definition of
- transaction log backup
- information you need to specify
- of a log-shipped database
- running a command after the operation finishes
- scheduling the job to run later
- selecting databases at the instance level
- about
- using the Backup and Verification tab
- using the Backup Wizard
- SnapManager backup data
- using the Backup and Verification tab
- using the Backup Wizard
- what to do if the backup fails
- transaction logs
- rules for storing
- space estimation
- volume requirements for
U
- unattended mode
- installing SnapManager
- uninstalling SnapManager
- upgrading SnapManager
- uninstalling SnapManager
- before you uninstall
- in interactive mode
- in unattended mode
- option to remove Report directory
- upgrading SnapManager
- converting VLD-type virtual disks to LUNs
- Data ONTAP requirement
- in interactive mode
- in unattended mode
- Microsoft SQL Server requirement
- storage system requirememts for
- Windows host system requirements for
- up-to-the-minute restore
- user databases, Microsoft SQL Server
- backing up
- definition of
- detached by SnapManager
- migrating to LUNs
V
- VDisk__* SnapInfo subdirectory names
- Virtual Device Interface (VDI)
- VLD-type virtual disks
- volume size
- assessing
- guidelines
- requirements for database files
- requirements for transaction logs
- transaction log sizing
- volumes, storage system
- maximum per single database
- maximum per SQL Server computer
- restoring from archive
- volume-wide backups
W
- Windows authentication method
- described
- for accessing SQL Server
- Windows backup utility
- archiving SnapManager backup sets
- compared with NDMP or dump
- Windows cluster
- cluster failure during a restore
- cluster group state during a restore
- disk requirements for
- installing SnapManager into
- maximum size supported by SnapManager
- multiple-instance
- system configuration requirements
- Windows host system requirements
- drive letters required for DBCC
- Microsoft SQL Server
- operating system
- SnapDrive
- SnapManager in workgroup mode
- SnapManager licenses
- SnapManager service account
- SQL Browser service
- Windows operating systems with SnapManager
- Windows 2000 Server
- Microsoft hotfixes
- SnapManager requirements
- Windows Server 2003
- Microsoft hotfixes
- running a script from a UNC path on
- SnapManager requirements
- Windows XP theme
- Windows XP theme
- workgroup mode, Windows
Symbols A B C D E F G I L M N O P R S T U V W
Copyright © 1994-2006, Network Appliance, Inc. All rights
reserved.
Part No. 215-01752_A0
File: bookix.htm
Last updated: 01-Sep-2006 07:41:34