Troubleshooting Director Issues

Product version: 11.0

Last modified: 04 July 2024

Problem

Director fails to start after upgrade or cannot be accessed.

Solution

Director cannot be accessed

If you haven’t performed any system updates or changes, but the Director service is unresponsive, follow these steps:

  1. Check the NAKIVO Director Service. Ensure the Director service is running on the machine.

  2. Restarting the service may restore access if it had stopped unexpectedly. For more information refer to Starting and Stopping Product Services.

  3. Verify Network Connection and Required Ports. Confirm the Director host is reachable and that all necessary ports are open. Common issues include blocked ports or firewall misconfigurations. For more information, refer to: Deployment Requirements – Required Ports.

Director fails to start after upgrade

Director fails to start after NAKIVO Backup & Replication upgrade. The following error message is displayed:

System could not start

This typically indicates a startup failure due to a database issue. To resolve this issue, follow these steps:

Note

This applies only if NAKIVO Backup & Replication's self-backup feature is enabled. Reverting to the last database backup will also restore all previous configurations.

  1. Stop the Director service, and go to the userdata/db folder. For more information refer to Starting and Stopping Product Services.

  2. Rename the current database file from product01.h2 to product01x.h2 (for example).

  3. Extract the self backup and edit the name to product01.h2.db.

  4. Start the Director service again.

  5. Optional. If no self-backup is available, please send the product01.h2.db file to the NAKIVO support team.