Knowledgebase

Backup Agent Fails to Start when Booting

Return to Knowledgebase

Note: "Backup Agent" for purposes of this article refers to any backup program supported by OFM.

When a machine running a System Component and a Backup Agent boots, the Backup Agent may start or perform a process used for reading files during backup. This causes the System Component to attempt synchronization, interfering with the Backup Agent startup.   Backup Agents known to be affected at reboot include:

Yosemite TapeWare Agent

Backup Exec Agent

Tivoli Backup Agent

The solution is to adequately delay boot-time synchronization of OFM v9.3 and later, allowing normal startup of the Backup Agent.  This delay will not affect normal backup synchronization.

Delaying OFM v9.3+ Synchronization

Delaying OFM v9.3+ synchronization requires:

1. Stopping the System Component, edit BootSyncDelay (see below), and starting the System Component

   
   

or

2. Edit BootSyncDelay (see below), reboot the System Component machine

   
   

Edit BootSyncDelay

The BootSyncDelay value is a DWord and is set in minutes, delaying any OFM sync attempt for the number of minutes configured. Keep in mind DWords default to hexadecimal so use the decimal radio button if necessary.

• Launch REGEDIT and browse to the following registry key on the machine running the OFM v9.3 (or later) System Component:

  
  

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\OFMFsDrv\Parameters

• In the right panel of REGEDIT, double-click on the BootSyncDelay value.

  
  

• Select the Decimal or Hexadecimal radio button and enter 5 as a value (representing a 5 minute delay), and exit REGEDIT.

  
  

This will delay OFM synchronization 5 minutes, which should allow the Backup Agent to load normally. If this fails, try increasing the BootSyncDelay value to 10 minutes.