Troubleshooting

 

Troubleshooting Backup and Restore Sessions

 

Data Protector Backup sessions are not started at all

 

(UNIX-specific)

Action

Run the crontab -lcommand to check whether the omnitrig program

 

is included in the crontab file. If the following line does not appear, the

 

omnitrig entry was automatically added by Data Protector:

 

0,15,30,45 * * * * /opt/omni/sbin/omnitrig

 

Stop and start the Data Protector daemons by running the omnisv

 

-stop and the omnisv -start commands in the /opt/omni/sbin

 

directory.

 

Data Protector Fails to Start an Interactive Session

 

Every time a backup is started, permission to start a backup session is

 

required and checked for the user who is currently running Data

 

Protector. If the user does not have sufficient permission, the session

 

cannot be started.

Action

Check and change the user rights for the particular user. Refer to

 

Chapter 3, “Configuring Users and User Groups,” on page 81.

 

Poor Backup Performance on Novell NetWare Server

 

Backup performance on a Novell NetWare Server may be poor. Backup

 

does not run continuously, but intermittently. This is a well-known

 

problem caused by the system TCPIP.NLM.

Action

Set the following parameters:

 

• NW5.1/NW6.0: SET TCP DELAYED ACKNOWLEDGEMENT = OFF

 

• NW5.0: SET TCP DELAYED ACK = OFF

 

This increases backup performance without any secondary effects.

 

Data Protector Fails to Start Parallel Restore Media

 

Agent on Novell NetWare Clients

 

Data Protector UNIX session manager sometimes fails to start restore

 

media agents in parallel on Novell NetWare clients with an error

 

message like, for example, Could not connect to inet or Connection

Chapter 12

585

Page 615
Image 615
HP B6960-90078 Data Protector Fails to Start an Interactive Session, Poor Backup Performance on Novell NetWare Server