How Do I Restart Backup Exec Services?

To restart Backup Exec services, the recommended and safest method is to use the dedicated Backup Exec Services Manager within the administration console. This ensures services are stopped and started in the correct, specific order to prevent errors or hang-ups. A less-recommended but still viable method for experienced administrators is to use the standard Windows Services console (services.msc), following the correct restart order manually.

Warning: Before you begin, ensure no backup or restore jobs are running. Restarting services will interrupt and fail any active jobs.

Method 1: Using the Backup Exec Administration Console (Recommended)

This method is the most reliable because Backup Exec automatically handles the dependencies and the correct order of operations, preventing potential issues.

Step-by-step instructions

1. Open the Backup Exec Administration Console.
2. Click the yellow icon in the upper-left corner of the console.
3. Navigate to Configuration and Settings > Backup Exec Services.
4. In the Backup Exec Services Manager window, you will see a list of all Backup Exec services and their status.
5. Click the Restart All Services button.
6. A warning will appear confirming that active jobs will be canceled. Click Yes to proceed.
7. The console will show the services stopping and then starting again. You may receive pop-up messages indicating a loss of communication with the server, which is normal and can be ignored.
8. Wait for the process to complete and for all services to show a "Running" status.

Method 2: Using the Windows Services Console (Manual)

This method gives you granular control but carries a higher risk of error if the services are not stopped and started in the precise sequence. Use this method only when the Backup Exec console is inaccessible.

The correct service restart order

1. Stop the services in this order:
   • Backup Exec Job Engine
   • Backup Exec Management Service
   • Backup Exec Agent Browser
   • Backup Exec Server
   • Backup Exec Device & Media Service
   • Backup Exec Remote Agent for Windows
2. Start the services in the reverse order.

Step-by-step instructions

1. Open the Windows Services console. Press the Windows Key + R, type services.msc, and press Enter.
2. Stop the services in order.
   • Right-click the Backup Exec Job Engine service and select Stop.
   • Repeat this process for each service in the stop order list above.
3. Start the services in the reverse order.
   • Right-click the Backup Exec Remote Agent for Windows service and select Start.
   • Repeat for each service in the start order list above.
4. Confirm all services are running. Check the "Status" column to ensure all services are in the "Running" state.

Troubleshooting: When services are stuck

In rare cases, a service may become stuck in a "Stopping" or "Starting" state. If this occurs, you may need to intervene more forcefully.

Step-by-step instructions

1. Use the Task Manager:
   • Open the Windows Task Manager (Ctrl+Shift+Esc).
   • Go to the Details tab.
   • Find the process name associated with the stuck service (e.g., bengine.exe for the Job Engine). You can find a full list of service process names on Veritas's website.
   • Right-click the process and select End Process Tree to terminate all related processes.
2. Re-attempt the restart:
   • Return to the Backup Exec Services Manager or the Windows Services console and attempt to restart the services again.

Why the restart order is critical

Backup Exec is a complex application with tightly integrated services that depend on one another. The correct restart order is designed to handle these dependencies gracefully.

• Stopping Order: You must stop the high-level operational services, like the Job Engine, before stopping the foundational services, like the Device & Media Service.
• Starting Order: When starting, the process is reversed. The foundational services must be active before the dependent operational services can start properly.

Failing to follow this order can cause services to hang, requiring more drastic actions and potentially a server reboot to resolve.