HP Data Protector A.06.11, Руководство по интеграции

Страница: 228 / 500

On Windows, use the Unicode format for the file.
Localized SAP R/3 objects
Oracle Server uses its own encoding, which may differ from the encoding used by
the filesystem. In the Backup context, Data Protector displays the logical structure of
the Oracle database (with Oracle names) and in the Restore context, the filesystem
structure of the Oracle database. Therefore, to display non-ASCII characters correctly,
ensure that the Data Protector encoding matches with the Oracle Server encoding
during backup and with the filesystem encoding during restore. However, the incorrect
display does not impact the restore.
UNIX: To be able to switch between the Data Protector encodings, start the GUI in
UTF-8 locale.
Windows: If the current values of DBCS and the default Windows character set for
non-Unicode programs do not match, problems arise. See “ ZDB, restore, or instant
recovery sessions fail due to invalid characters in filenames ” on page 240.
Monitoring sessions
You can monitor currently running sessions in the Data Protector GUI. When you run
an interactive backup or a restore session, a monitor window shows you the progress
of the session. Closing the GUI does not affect the session.
You can also monitor sessions from any Data Protector client with the
User
Interface
component installed, using the Monitor context.
On how to monitor a session, see the online Help index: “viewing currently running
sessions”.
System messages generated during backups are sent to both the SAP R/3 and the
Data Protector monitor. However, mount requests are sent only to the Data Protector
monitor.
Troubleshooting
This section lists general checks and verifications plus problems you might encounter
when using the Data Protector SAP R/3 integration.
For general Data Protector troubleshooting information, see the HP Data Protector
troubleshooting guide.
Data Protector SAP R/3 ZDB integration 228