Data protection terminology

The following terminology is frequently used when describing data protection in this guide:

Host based backup involves backing up data over the network to a storage device such as a repository. The backup and restore operations are implemented by Protector software processes that utilise the smallest possible amount of the computing, memory and disk resources on the node being backed up or restored to.

Repositories are data stores implemented by Protector software processes that hold backup data. Repositories utilise disk volumes mounted on the host where the repository is located. They have built-in capabilities for data reduction, such as block differentials and de-duplication, as well as the capability to record point-in-time snapshots of captured data. Backup and restore operations may utilise significant amounts of the computing, memory and disk resources of the node where the repository is located.

Block hardware storage devices use snapshotting and replication technologies implemented by the storage device itself. Proxies running Protector software orchestrate backup and restore functions on these devices but are not directly involved in capturing or transferring backup data. Examples of these devices include Hitachi Block storage arrays.

File hardware storage devices use snapshotting and replication technologies implemented by the storage device itself. Proxies running Protector software orchestrate backup and restore functions on these devices but are not directly involved in capturing or transferring backup data.

Application nodes are existing application servers or clusters that require Protector and additional third party software to be installed. Protector software discovers application data paths and coordinates backup and restore operations. Applications can be placed in the correct state to ensure consistent backup and restore processing. Example application nodes include:

• Oracle Database