agent

A software program that is typically used to back up databases when they are running or "hot." Agent software is available for several popular databases, including Microsoft SQL, Oracle, and Oracle Rdb, mail applications such as Microsoft Exchange and Lotus Domino, SAN devices, and NAS devices that use NDMP.

See also client.

archive

The process of copying one or more files to another location, where they will be retained for a specific (typically lengthy) period of time in order to comply with corporate, governmental, or other requirements. When files are archived to the STORServer appliance, you control which files get archived, where they are stored, and the length of time they are retained. Archived files can be retrieved by archive date, file name, or description.

automatic DR plan

A disaster recovery plan that is generated automatically based on business policy settings on the STORServer Backup Appliance.

automatic file expiration

The ability to set expiration dates and delete old files, then subsequently reclaim storage pool and tape space on the STORServer Backup Appliance.

automatic tape reclamation

The process of determining when data has expired (according to policies set on the STORServer Backup Appliance), then deleting the expired data and reusing the space for recording new data. This technology saves time and reduces media consumption.

backup

The process of copying one or more files to another location to ensure against data loss. STORServer backup appliances are preconfigured to automate the daily backup of registered clients. Client data is backed up to disk, migrated to tape (as predefined usage thresholds are reached), and copied to removable media for disaster recovery. (Configuration may vary by appliance model.) Appliances are sized to accommodate recent client data on disk, ensuring quick restores of client data when necessary.

STORServer backup appliances use a unique backup method called progressive incremental backup to minimize network traffic, storage requirements, and backup windows. Data retention parameters control which files are backed up, how many versions are retained, and how long these versions are retained—down to the individual file level.

See also disk-to-disk-to-tape (D2D2T), progressive incremental backup, and data retention.

bare machine recovery

Enables systems recovery following a disaster or catastrophic server failure, regardless of operating system.

business continuity appliance

See STORServer Backup Appliance.

business policies

Settings within the STORServer Backup Appliance that specify backup, archive and disaster recovery parameters such as data hierarchy, backup schedules, data expiration and tape reclamation parameters, and disaster recovery plans.

client

Any system that uses the services of a STORServer appliance. A client can be a workstation, PC, or file server from a variety of vendors and running a variety of operating systems. To take advantage of the backup, restore, archive, and retrieve services of the appliance, a client system must be running the TSM backup-archive client software and, in some cases, a TSM agent software utility.

client option set

A set of client options that you define on the STORServer backup appliance to enforce enterprise-wide policies upon multiple client nodes. Client option sets can be defined to override options specified in the individual client options files.

client options file

A file that resides on each client and contains processing options that identify the address of the STORServer appliance, the communications protocol to be used for client/server sessions, and optionally, settings that affect backup, archive, space management, and scheduling processes. The STORServer appliance provides a customized template client options file for use on clients at your site. You can further customize this file as necessary to meet business requirements.

copy storage pool

The storage pool to which primary storage pools are copied. The copy storage pool basically provides a backup copy of your backup copy. Copy storage pools use sequential access devices only. Copy storage pool volumes are intended for off-site storage. In the event of a disaster or media failure in the primary storage pool, you can use copy storage pool data to restore original files. (Under normal circumstances, you would restore or retrieve data from your primary storage pools.)

STORServer backup appliances are preconfigured to copy primary storage pool data to a copy storage pool (the DRPOOL) each day. Customers are advised to check out the copy pool volumes and move them to an off-site location for safekeeping.

Contrast with primary storage pool.

daily processing schedule

An administrative schedule that is predefined by STORServer Manager (SSM) on most STORServer backup appliances to automate a series of daily administrative tasks, including backup and migration of storage pool data, TSM database backup, generation and backup of DR files, and expiration and reclamation processing. (Tasks vary by appliance type.)

data protection

A set of functions that ensure against the loss of electronically stored data due to corruption, accidental or premature deletion, or an on-site disaster. STORServer business continuity appliances achieve complete data protection with their full-featured backup, restore, archive, retrieve, and disaster recovery functions.

See also STORServer Backup Appliance.

data replication

Copying data from a host computer to another computer, which may be at a remote location, to establish redundant copies and ensure business continuity. When data replication is done over a computer network, changed data is copied to the remote location as soon as it changes.

data retention

The period of time that backed up or archived files are retained. Your data retention parameters can significantly impact storage pool usage and dictate storage requirements.

STORServer backup appliances use a predefined set of data retention parameters that control:

• The maximum number of versions to keep of files that still exist on client systems
• The maximum number of versions to keep of files that no longer exist on client systems
• The maximum number of days to keep inactive files
• The maximum number of days to keep the last version of a file that has been deleted from the client

database

A collection of records organized to permit quick access to individual records by another computer program. An agent utility is required for database backups, to capture individual records, tables, and files within the database and ensure database consistency. STORServer offers agents for a variety of databases, including Microsoft SQL, Oracle, and Oracle Rdb.

See also agent and TSM database.

database backup

In the STORServer environment, refers to a full backup of the TSM database, which resides on the STORServer appliance. The Daily Processing schedule on STORServer appliances causes a full backup of the TSM database to occur each day. This backup is written to removable media. Customers are advised to remove the database backup volume each day and move it to an off-site location for safekeeping. Data on a database backup volume is typically expired after 7 days.

See also Daily Processing schedule and TSM database.

deduplication

The process of weeding out and deleting duplicate blocks of data. The STORServer Backup Appliance’s incremental backup technology significantly reduces the need for deduplication. Storage Pool deduplication will be available in 1H2010.

device class

A named set of characteristics for a group of storage devices that have similar availability, performance, and storage characteristics. The device class identifies to TSM the library being addressed and the type of media it uses. STORServer backup appliances purchased with a library have a predefined device class for the library. You can define additional device classes for other media types or libraries as required. Every storage pool on the appliance must be associated with a single device class, which defines the media type used by the storage pool.

device configuration file

A file containing the latest device configuration information from the TSM database, including library, drive, and server definitions, device class definitions, and volume location information. Information in this file is needed to restore the TSM database should it become necessary.

The device configuration file is named devconfig.out and resides in the TSM installation directory on the STORServer appliance. Information in this file is included in the daily disaster recovery plan file. On appliances that are not licensed to use DRM, the device configuration file itself is backed up to a predefined location. Customers are instructed to move the backup copy to an off-site location for safekeeping.

See also disaster recovery plan file and TSM database.

disaster recovery (DR)

The ability to restore backup data after a disaster such as a flood, hurricane, or earthquake. This includes not only your client systems, which are backed up to the STORServer appliance, but also the STORServer appliance itself. (The STORServer appliance has the ability to execute an automated, script-driven recovery of the backup server from DR media.)

Traditional STORServer appliances are preconfigured to produce daily DR media, including a copy of the current data in your primary storage pools, a full backup of the TSM database, and an up-to-date disaster recovery plan file (the latter on appliances licensed to use the DRM function of TSM). Customers are instructed to remove DR media from the appliance each day, move it to an off-site location for safekeeping, and load the appropriate number of tapes to accommodate the next day's DR media.

NOTE: Appliances purchased without a tape library/loader are not configured to produce DR media.

If your enterprise requires multiple, physically separate STORServer appliances, these appliances can be linked together for server-to-server communications. When combined with the DRM function, this configuration allows the appliances to serve as remote, electronic vaults for each other.

See also disaster recovery plan file and DRM.

disaster recovery plan file

A file produced by the disaster recovery manager (DRM) function of TSM that contains information necessary for recovering the TSM database and clients of the STORServer appliance. On appliances that are licensed to use DRM, STORServer Manager (SSM) is preconfigured to execute generation of the disaster recovery plan file on a daily basis.

The disaster recovery plan file identifies the location of the latest recovery media (DR volumes), contains copies of critical log files, identifies database and recovery log space requirements, and even provides a recovery procedure for your site. Customers are advised to store the daily copy of this file at an off-site facility for safekeeping.

disk-to-disk-to-tape backup (D2D2T)

The backup technique used by most STORServer appliances to back up client data. With D2D2T, files are sent across the network from the client disk to the server disk (on the STORServer appliance) and then migrated to tape (in a tape library, for example). This process is extremely fast and efficient. The number of simultaneous client backups is limited only by your network bandwidth.

Because client backups are progressive incremental and data can be compressed, disk cache can be small. As the disk cache fills, the STORServer appliance automatically mounts a tape and moves files from disk to tape. Full tape and disk bandwidth can be used for file movement because the files are already in disk cache. Tape drives are not tied up waiting on slow networks or client delays.

See also progressive incremental backup.

disk-to-disk-to-x

A backup technique whereby data is transferred over the network from the client disk to the server disk (the STORServer appliance, for example) to another media, such as tape, CD-ROM, DVD-RAM, or WORM.

disk-to-tape backup

A more traditional backup technique, whereby the data being backed up is copied from disk (on the client machine) directly to tape for disaster recovery protection. This type of backup is typically slower than disk-to-disk, and simultaneous backups are limited to the number of available tape drives. Restoring data that is primarily stored on tape can be labor-intensive and time consuming.

This backup technique also limits your ability to easily adopt new storage media. The migration of previously backed up data from old to new storage media requires a tremendous amount of effort and loss of data is possible.

disk storage pool

A primary storage pool that stores data on disks. The disk storage pool is the initial destination for client data that is being backed up to the STORServer appliance. This storage pool is sized to accommodate the projected amount of daily changed data in your environment (that is, one cycle of incremental backups of client systems).

The disk storage pool on traditional STORServer backup appliances is configured to migrate to the next storage pool in the hierarchy—the tape storage pool. Cached copies of client files remain in the disk pool after migration. When space is needed for new data, cached copies are erased and replaced with newer backup copies. Use of this cache feature on the primary disk pool allows a rapid restore of recently backed up data when necessary.

Disk storage pools typically use random access storage. However, on STORServer D-Series appliances, the primary disk storage pool (which is the only primary storage pool) is configured to use sequential access disk storage. All data is stored on disk and no migration occurs.

See also sequential access disk storage and storage pool.

DR files

(disaster recovery files) One or more files generated by the STORServer appliance each day that are critical to restoring the STORServer appliance and its clients after a disaster. All of the following are DR files:

• A disaster recovery plan file (generated on STORServer appliances that are licensed to use the DRM function of TSM; plan includes volume history and device configuration file information)
• A copy of the latest volume history file (for appliances that do not use DRM)
• A copy of the latest device configuration file (for appliances that do not use DRM)

Customers are strongly advised to retain copies of the daily DR files in an off-site location for 7 days.

See also disaster recovery plan file, volume history file, and device configuration file.

DR testing

The ability to test disaster recovery plans prior to an actual disaster.

DR volumes

Any media containing copy storage pool data and/or TSM database backups. Most STORServer backup appliances are preconfigured to produce a set of DR volumes each day: one (or more) containing copy storage pool data and one containing a full backup of the TSM database. Customers are advised to check out the DR volumes each day and move them to an off-site location for safekeeping. When the data on a DR volume expires, the volume status changes to VAULTRETRIEVE (visible in STORServer Manager), indicating that the volume can be retrieved from off-site storage and checked back in to the library for reuse.

DRM

(disaster recovery manager) An acronym for the disaster recovery manager function of the TSM server in IBM Tivoli Storage Manager Extended Edition (EE). DRM is included and licensed for use on most STORServer backup appliances. STORServer Manager uses DRM to prepare the disaster recovery plan file and manage off-site recovery media.

encryption

The transformation of data from plaintext into ciphertext, which renders it almost impossible to read without a secret key, which is required to reverse the transformation. TSM Version 5.3 and higher supports the use of AES 128-bit encryption during backup and archive operations.

expiration processing

A process that eliminates references to expired files from the TSM database and determines where space can be reclaimed on sequential access storage pool volumes. Expiration processing is scheduled and automated on most STORServer backup appliances. Active client data is expired according to data retention parameters.

See also data retention.

first response services

A STORServer services providing an on-site consultant in the event a customer declares a disaster. This service is coupled with other DR Planning services.

full backup

A type of backup whereby all data is copied, regardless of whether it has changed since the last backup. Client machines that are backing up data to a STORServer appliance do a full backup initially, then use the progressive incremental backup method thereafter.

Contrast with incremental backup. See also progressive incremental backup.

include-exclude list

A method for controlling which client files are eligible for backup and archive services. By default, all files on a backup-archive client's locally mounted drives are eligible for daily backups unless specifically excluded. You can use an include-exclude list to exclude single files or groups of files from backup. The include-exclude list can reside within the client options file or in a separate file that is identified by an entry in the client options file. (A separate file is used on UNIX clients.) The template client options file provided with your STORServer backup appliance contains a predefined include-exclude list. You can modify this list on individual clients as appropriate.

For more information on include-exclude lists, see the STORServer knowledge base. (An active STORServer support contract is required for access.)

incremental backup

A type of backup during which only new or changed client data is backed up. STORServer backup appliances use a backup method (progressive incremental backup) that takes incremental backup one step further.

Contrast with full backup. See also progressive incremental backup.

migration

The movement of data from one storage pool to another storage pool. Migration can occur automatically (when the space used in a storage pool exceeds the percentage defined by the pool's high migration threshold) or selectively (when an administrator or administrative schedule lowers the migration threshold, forcing an immediate migration). On traditional STORServer appliances, migration is scheduled to occur as part of a daily administrative schedule. Data is migrated from the primary disk storage pool to the primary tape storage pool, according to the preconfigured storage pool hierarchy.

open registration

A registration mode set on the backup appliance during which multiple clients can register for appliance services with minimal administrative support. STORServer backup appliances use open registration by default. While open registration is in effect, the TSM server on the STORServer appliance prompts client users for their node name, password, and contact information the first time the client system connects to the TSM server on the STORServer appliance. Customers are advised to change the registration mode to closed after the majority of clients have registered for services, and register subsequent clients manually thereafter.

point-in-time restores

A function that detects a specific date and time of data that is to be restored, thus bypassing unwanted versions of the same file.

policy

A set of rules defined on the TSM server to manage client data. TSM policies specify how files are backed up, archived, migrated, and managed in storage. Policy domains, policy sets, management classes, backup copy groups, and archive copy groups are all components of a TSM policy.

STORServer backup appliances have predefined policies to set forth a general set of rules that apply to all client nodes and all data types. Additional policies can be created to govern different data in different ways—to retain one group of client's data longer than another's, or to archive accounting data but not engineering data, for example. TSM policies can be defined down to the individual file level. These granular policies allow the storage administrator to set parameters that meet their specific business requirements as opposed to adapting the business to meet technology restraints.

policy-based retention

the ability to set expiration dates and tape reclamation policies on the STORServer Backup Appliance.

primary storage pool

Where client data that is being backed up, archived, or migrated is stored. A primary storage pool can use random access storage (DISK device class) or sequential access storage (TAPE or FILE device class, for example). .Both disk and tape storage pools on the STORServer backup appliance are primary storage pools. These storage pools are always located onsite.

Contrast with copy storage pool.

progressive incremental backup

The unique and efficient backup method used by STORServer backup appliances. Clients perform an initial, full backup to the STORServer appliance and thereafter, back up only changed or new files in their entirety. Progressive incremental backup methodology has the following benefits:

• No additional full backups are required after the first client backup.
• Only changed or new files are backed up daily. (A maximum of only 5 to 10 percent of client files change on a daily basis.)
• Backup windows are reduced dramatically—as much as 90 percent in some cases.
• Both network traffic and tape usage are significantly reduced.
• Because files are backed up in their entirety, restores are fast and simple. (The backup server does not need to maintain references to base file versions and restore a base file, followed by incremental backups, multiple required tape mounts, and so on).

reclamation

The process of reclaiming space on sequential access storage pool volumes. Space becomes reclaimable when files are expired or deleted (as identified by expiration processing). Reclamation processing consolidates the remaining active data from multiple sequential access volumes onto fewer volumes.

reduced network overhead

When less bandwidth is required for data transfer; thereby, lowering the impact on network speed.

STORServer appliances use a predefined and scheduled reclamation process, which allows you to identify, retrieve from off-site storage, and reuse tape volumes in your library.

registered clients

Client systems that have been assigned a node name and password on the TSM server and are running the TSM backup-archive software. These clients are eligible for the services provided by the STORServer appliance. The TSM server on the appliance supports two registration methods: open and closed. STORServer appliances are preconfigured to use open registration. This simplifies the registration process during the initial installation of multiple client systems. Customers are advised to change the registration method to closed after the majority of clients have been registered. Additional clients can be registered manually as necessary.

replication

See data replication.

restore

The process of copying information from its backup location to another location for active use. The backup copy remains in the storage pool and is not affected by the restore.

Restoring client data that has been backed up by a STORServer appliance is quick and simple. In most cases, the files you need to restore are available on disk (no tapes to locate and mount).Explorer-style graphical user interfaces make is easy to search for or browse to the file you are seeking. You can direct the restore copy to its original location (default) or to a location of your choice. STORServer appliances can also restore storage pools, storage pool volumes, and even the appliance's own [TSM] database.

server virtualization

A technology for consolidating servers, whereby multiple virtual machines with heterogeneous operating systems can run side-by-side on the same physical machine.

sequential access disk storage

A technique for emulating a tape device on a random access device. The primary disk storage pool on STORServer D-Series appliances uses sequential access disk storage. Client data is stored on disk in storage pool volumes that are actually files. Because data is stored sequentially, automated expiration and reclamation processes manage file space within these files.

See also expiration and reclamation.

STORServer Manager (SSM)

A utility produced by STORServer, Incorporated that interacts with the TSM software on a STORServer backup appliance to automate administrative tasks and simplify the administration of your appliance.

storage pool

A named collection of storage volumes on which the STORServer appliance stores backup, archive, and space-managed client data. Each storage pool is associated with a single device class, which defines its media type. A storage pool can use disk, tape, or optical media. A key benefit of storage pools is the ability to move data from one storage media to another

Traditional STORServer appliances have two primary storage pools: a disk storage pool (which uses random-access storage) and a tape storage pool (which uses sequential access storage). When a client backs up data to the STORServer appliance, the data is copied to the disk pool first, then migrated to the tape pool. This data path is referred to as the storage pool hierarchy.

Primary storage pools on the STORServer backup appliance are also copied to a copy storage pool each day for disaster recovery. The copy storage pool uses removable media, which can be removed and stored off-site for safekeeping.

See also device class, disk storage pool, tape storage pool, copy storage pool, and sequential access disk storage.

storage virtualization

The pooling of physical storage from multiple network storage devices into what appears to be a single storage device that is managed from a central console. Storage virtualization is commonly used in storage area networks (SANs) to simplify data storage and management by disguising the complexity of the SAN.

tape storage pool

A storage pool that stores data on tape. Traditional STORServer backup appliances have a primary tape storage pool named ONLINEPOOL. It is the second storage pool in the hierarchy (the disk storage pool is the first). The Daily Processing schedule that is preconfigured in STORServer Manager causes data to migrate from the disk storage pool to the tape storage pool each day. Data is also copied from the tape storage pool to the copy storage pool for disaster recovery.

See also storage pool and disk storage pool.

STORServer Backup Appliance

A fully integrated combination of hardware and software designed to provide a superior backup, archive, and disaster recovery solution. STORServer business continuity appliances integrate the Microsoft® Windows Storage Server 2003 operating system (designed specifically for storage environments) with state-of-the-art, heterogeneous backup, archive, and disaster recovery technologies. For more information, check out the Business Continuity Appliance Tour on the STORServer Web site.

tapeless DR

The ability to send DR data to either Internal or External Cloud storage thereby minimizing or bypassing the use of tape media.

TDP

(Tivoli Data Protection) An acronym for IBM Tivoli Data Protection software. Several TDP agent software kits are typically provided with STORServer appliances, on the hard drive and on CD-ROM. These include TDP for Microsoft Exchange, Microsoft SQL, and Oracle, to name a few. (Kits may vary by appliance and are subject to change. Ask your reseller for details.)

traditional STORServer backup appliance

A term used to differentiate between D-Series STORServer appliances and other STORServer appliances. The D-Series appliances use a different storage pool hierarchy (a single primary storage pool with no migration) and storage method (sequential access disk storage as opposed to a combination of random access disk storage and sequential access tape storage.

TSM

(Tivoli Storage Manager) An acronym for IBM Tivoli Storage Manager software. TSM provides automated, policy-based storage management services to clients.

TSM database

The database used by the TSM server on the STORServer appliance to maintain information about client systems, user files, business policies, disaster recovery, and scheduling of client and administrative tasks. The TSM database is a relational database (B+- tree) specifically designed to manage a data storage environment. It operates transparently, requiring minimal administrative oversight.

The TSM database maintains extensive detail on each file that has been backed up to the STORServer appliance — where the file came from, who owns it, what its permissions are, where the backup copies reside (disk or tape), and even the specific location on a specific tape. The STORServer appliance uses this information to quickly locate any file requested for restore.

To maintain data integrity, the TSM database uses a recovery log to roll back any changes made if a storage transaction is interrupted before it completes. This is known as a two-phase commit. Both the TSM database and recovery log can be mirrored for availability, providing automatic volume switching after a media failure. In the unlikely event of a TSM database recovery, the database can be restored to the exact point of failure by rolling the recovery log forward after restoring from the latest database backup.

Your STORServer appliance is preconfigured to do a full backup of TSM database each day, and copy that information to removable media for off-site storage.

VAULTRETRIEVE

A status for DR volumes that appears in STORServer Manager when those volumes no longer contain valid data. Volumes outside the library with a VAULTRETRIEVE status can be returned from off-site storage and reused in your library.

The disaster recovery manager (DRM) assigns this status when TSM determines (during expiration processing and based on data retention parameters) that all data on these volumes has expired.

See also expiration processing, data retention, and DR volumes.

virtualization

See server virtualization and storage virtualization.

volume history file

A file containing the latest volume history information (the location, status, and consumption of storage pool volumes) from the TSM database. Information in this file is needed to restore the TSM database should it become necessary.

The volume history file is named volhist.out and resides in the TSM installation directory on the STORServer appliance. Information from this file is included in the daily disaster recovery plan file. On appliances that are not licensed to use DRM, the volume history file itself is backed up to a predefined location. Customers are advised to move the backup copy to an off-site location for safekeeping.