HP OpenView Storage Data Protector B6960-96008 Manual De Usuario
G-25
Glossary
of the logging level used during backup.
Data Protector 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.
Data Protector 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.
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.
login ID (MS SQL Server specific term)
The name a user uses to 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.
The name a user uses to 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.
login information to the Oracle Target
Database (Oracle and SAP R/3 specific
term)
The format of the login information is
<user_name>/<password>@<service>,
where:
Database (Oracle and SAP R/3 specific
term)
The format of the login information is
<user_name>/<password>@<service>,
where:
•
<user_name> is the name by which
a user is known to Oracle Server and
to other users. Every user name is
associated with a password and both
a user is known to Oracle Server and
to other users. Every user name is
associated with a password and both
have to be entered to connect to an
Oracle Target Database. This user
must have Oracle SYSDBA or
SYSOPER rights.
Oracle Target Database. This user
must have Oracle SYSDBA or
SYSOPER rights.
•
<password> must be the same as the
password specified in the Oracle
password file (orapwd), which is
used for authentication of users
performing database administration.
password specified in the Oracle
password file (orapwd), which is
used for authentication of users
performing database administration.
•
<service> is the name used to
identify an SQL*Net server process
for the target database.
identify an SQL*Net server process
for the target database.
login information to the Recovery
Catalog Database (Oracle specific
term)
The format of the login information to
the Recovery (Oracle) Catalog Database
is <user_name>/
<password>@<service>, where the
description of the user name, password,
and service name is the same as in the
Oracle SQL*Net V2 login information
to the Oracle target database. In this
case, <service> is the name of the
service to the Recovery Catalog
Database, not the Oracle target database.
Catalog Database (Oracle specific
term)
The format of the login information to
the Recovery (Oracle) Catalog Database
is <user_name>/
<password>@<service>, where the
description of the user name, password,
and service name is the same as in the
Oracle SQL*Net V2 login information
to the Oracle target database. In this
case, <service> is the name of the
service to the Recovery Catalog
Database, not the Oracle target database.
Note that the Oracle user specified here
must be the owner of the Oracle
Recovery Catalog.
must be the owner of the Oracle
Recovery Catalog.
Lotus C API (Lotus Domino Server
specific term)
An interface for the exchange of backup
specific term)
An interface for the exchange of backup