The following terms are used with these meanings in the Oracle MaxRep documentation.
- access control group (ACG)
- A method that restricts the exported copy to a host or a group of hosts. Specifying an ACG is the equivalent of LUN host mapping on the Oracle FS System.
- application consistency
- Application data can be spread across multiple LUNs. Application consistency provides a synchronized copy of all LUNs that are associated with the application.
- asynchronous replication
- The process of providing time lagged copies of data. Asynchronous replication uses a combination of three protection schemes to ensure data integrity: a data change map, a write journal, and a drive cache on the Oracle FS System.
Application performance of asynchronous replication is better than that of synchronous replication because asynchronous replication I/O is blocked only until the primary storage acknowledges the write.
- bitmap mode
- The Oracle MaxRep Replication Engine cache switches to bitmap mode when, due to WAN connectivity issues or other replication performance bottlenecks, the DRAM cache is full, and the Replication Engine cache is close to becoming full. In bitmap mode the Replication Engine keeps track of the changed data blocks so that, when connectivity is restored, the changed block can be replicated.
- block-based replication
- Replicates raw blocks of data regardless of the file system or application.
- bookmarks
- Application consistency markers that are created within a LUN that are used in the retention log to create a synchronized copy.
- cache LUN
- See home LUN.
- Continuous Data Protection (CDP)
- Real-time data protection that provides the ability for a backup administrator to restore the data to any point in time.
- control service
- The service that is used to configure the replication process and policies.
- data cache
- Temporary storage of replication data in memory on the replication engine.
- differential sync
- Replicates only the data that has changed since the last successful full synchronization.
- FX agent
- A host-based file system splitter that enables application protection and data replication.
- home LUN
- A LUN on the Oracle FS System that stores the configuration data and cache for the Replication Engine. Also called cache LUN.
- initial sync
- The initial copy of the data sent from the source LUN to the target LUN.
- initiator ports
- The SAN ports that initiate I/O to a storage device. On a Replication Engine, at least one port must be an initiator port. The initiator port for the source LUN is designated as AIS, and the designator for the target LUN initiator is AIT.
- local replication
- Replication that occurs only on the primary site.
- MaxRep agent
- An application specific agent that provides time sequenced application consistency.
- multi-hop replication
- Two-stage replication that provides a synchronous replication, which is then asynchronously replicated to a third location. Multi-hop replication uses a synchronous and an asynchronous replication license.
- Node Port ID Virtualization (NPIV)
- A method to provide multiple virtual node ports (also called N_Ports) to be presented over a single, physical fiber channel port.
- Oracle FS System
- The Oracle FS System is a complete and integrated full-featured network storage system.
- Oracle MaxRep for SAN
- (1) A block-based replication solution that provides the following benefits:
- (2) The graphical user interface (GUI) that provides the configuration, control, and monitoring operations for Oracle MaxRep for SAN.
- physical snapshot
- A point-in-time full volume snapshot, or copy, of a source LUN. The full replicated copy can be accessed directly from the Oracle FS System.
- primary LUN
- see source LUN.
- process service
- The utility that runs on the active Replication Engine and manages the replication of protection plans.
- profiler tool
- Provides an estimate for the size of the target copy and event journal, and for the amount of bandwidth that is required between the source and target Oracle FS Systems to meet requested retention windows and recovery point objectives (RPOs).
- protection plan
- The collection of specific policies and configurations that define the replication and retention policies for one or more replication pairs in the Oracle MaxRep software.
- recovery point objective (RPO)
- The maximum time period of acceptable data loss before a disaster has an adverse impact on data recovery.
The maximum desired time period prior to a failure or disaster during which changes to data might be lost as a consequence to attempts of data recovery. Data changes preceding the failure or disaster by at least this time period are preserved by recovery actions. The RPO default value is Zero and is equivalent to a "zero data loss" requirement.
- recovery snapshot
- A mechanism for recovering, or copying, data on a LUN. An administrator creates a recovery snapshot in a physical or virtual capacity.
- recovery time objective (RTO)
- The maximum acceptable amount of time to become fully operational after an interruption of service.
- remote replication
- The replication that takes place between a primary and secondary site.
- Replication Engine
- Oracle FS System hardware required for Oracle MaxRep.
- Replication Engine cache
- The memory available on the replication engine for staging the data that is associated with replication operations.
- Replication Engine target ports
- The ports on the Replication Engine that receive I/O commands from any initiator, usually from the Oracle FS System. Each Replication Engine must have at least one target port.
- replication pair
- The association of a source LUN and a target LUN for recovery purposes.
- resync
- The operation that re-synchronizes the replication data to achieve parity between the LUNs in a replication pair after an interruption occurs.
- retention journal
- The time indexed replication events that allows the data to be rolled back to any point in time.
- retention LUNs
- The LUNs on the Oracle FS System that hold the retention journal for a protection plan.
- retention period
- The configurable period of time for which the retention logs should attempt to keep all the changes for a given replication pair. Data recovery is limited to the time period defined in the retention logs.
- reverse replication
- Replicating data from the remote site back to the primary site during a service interruption. The primary site becomes the remote site until the original remote site comes back online after a service interruption.
- rollback
- The restoration of data to a specified earlier point in time.
- scheduled checkpoint
- The mechanism to automate the creation of periodic recovery points to roll back to.
- scheduled physical snapshot
- Mechanism to automate periodically creating recovery points to which data can be rolled back.
- secondary LUN
- see target LUN.
- source LUN
- The LUN designated for replication that is located on the primary Oracle FS System. The source LUN is also called a primary LUN.
- sparse retention
- Retains fewer bookmarks (recovery fall back points) for older data in specified retention period. The feature that backs up older data less frequently than new data.
- synchronous replication
- Ensures that a write operation to the primary Oracle FS System will not be acknowledged until it has been written to both the primary Oracle FS System and the Replication Engine.
- target LUN
- The LUN on the Oracle FS System that is identified as a destination for replication. The target LUN must be created on the Oracle FS System prior to configuring replication. A target LUN is also called a secondary LUN.
- virtual snapshot
- A virtual snapshot, also called a Vsnap, is a type of recovery mechanism that provides a point-in-time, virtual copy of a source LUN. Virtual snapshots are created on the Replication Engine, and require no disk space on the primary or secondary Oracle FS System. Creating a virtual snapshot does not interfere with the current replication.
- VX agent
- Host-based volume splitter that enables application protection and replication.
- write splitter
- The Oracle FS System feature that controls the data write operations by splitting the write data between the primary Oracle FS System and the Replication Engine. The write splitter runs on the Controller.