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

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

• SQL Server VDI.LOG file contains an entry similar to:
2000/03/15 13:19:31 pid(2112)
Error at BuildSecurityAttributes: SetSecurityDescriptorDacl
Status Code: 1338, x53A Explanation: The security descriptor
structure is invalid.
SQL Server service and
Data Protector Inet
are running under different
accounts. The integration cannot access SQL Server due to security problems.
Action
Restart the
Data Protector Inet
service under the same account as the SQL
Server service is running.
Problem
Backup fails if the appropriate drive letter on the backup system does not exist
Backup fails with an error, similar to:
[Major] From: SSEA@computer1.com "" Time: 02-Feb-08 14:07:54
Filesystem \\.\Volume{ef58fe0e-b2b8-11db-aa08-000802804af6} could not be mounted
to Q:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\.
([87] The parameter is incorrect. ).
Backup fails because SSE agent tries to mount the filesystem to the drive letter which
does not exist on the backup system. The drive letter must be the same as on the
application system. SSE or SMIS agents always mount the filesystems to the same
drive letters on the backup systems as if the
ZDB_PRESERVE_MOUNTPOINTS omnirc
variable is set to
1
.
Action
For source volumes to be successfully replicated, create the same drive letters on the
backup system as they are used on the application system for mounting the source
volumes.
Problem
Database is left in unrecovered state after “Invalid value specified for STOPAT
parameter” is reported
The database remains in an unrecovered state as if the
RESTORE LOG
operation
was run with
Leave the database non-operational
.
Zero downtime backup integration guide 279