HP Application Recovery Manager software A.06.10 Concepts guide (March 2008)

operator. This implies that no operator personnel is present to

work with the backup application.

Local Continuous

Replication

(Microsoft Exchange Server specific term) Local continuous

replication (LCR) is a single-server solution that creates and

maintains an exact copy (LCR copy) of a storage group. An LCR

copy is located on the same server as the original storage group.

When an LCR copy is created, it is kept up to date through

change propagation (log replay) technology. The replication

feature in LCR guarantees that logs that have not been replicated

are not deleted. The implication of this behavior is that running

backups in a mode that deletes logs may not actually free space

if replication is sufficiently far behind in its log copying.

An LCR copy is used for disaster recovery because you can

switch to the LCR copy in a few seconds. If an LCR copy is used

for backup and if it is located on a different disk than the original

data, then the I/O load on a production database is minimal.

A replicated storage group is represented as a new instance of

Exchange writer called Exchange Replication Service and can

be backed up (using VSS) as a normal storage group.

See also Cluster Continuous Replication and Exchange

Replication Service.

logging level The logging level determines the amount of details on files and

directories written to the IDB during backup. You can always

restore your data, regardless of the logging level used during

backup. Application Recovery Manager provides four logging

levels: Log All, Log Directories, Log Files, and No Log. The

different logging level settings influence the IDB growth, backup

speed, and the convenience of browsing data for restore.

logical-log files This applies to online database backup. Logical-log files are

files in which modified data is first stored before being flushed

to disk. In the event of a failure, these logical-log files are used

to roll forward all transactions that have been committed as well

as roll back any transactions that have not been committed.

log on to Microsoft SQL Server. A login ID is valid if Microsoft

SQL Server has an entry for that user in the system table syslogin.

to the Oracle

Target Database

(Oracle and SAP R/3 specific term) The format of the login

information is user_name/password@service, where:

Concepts guide 85