Arcserve Backup Services Fail to Initialize

Valid on Windows platforms.

Symptom:

Why are my Arcserve Backup services failing to initialize?

Solution:

Arcserve Backup requires a portmapper for its RPC engines. The Windows service, Arcserve Remote Procedure Call Server, provides the portmapper functionality and uses the standard portmap, port 111.

If Arcserve Backup detects port 111 conflicts, indicating that it is using the same port number for the CA Remote Procedure call server service as a previously installed portmapper, Arcserve Backup automatically switches to another port number.

If you want other computers to be able to communicate with your computer, we recommend that you configure a specific port. To do so, use the file labeled portsconfig.cfg file located in the directory that follows:

C:\Program Files\CA\SharedComponents\ARCserve Backup

Arcserve Backup can work with external portmappers (Microsoft Services for UNIX (SFU), Noblenet Portmapper, StorageTek LibAttach, and so on). However, during the machine boot up sequence, Arcserve Backup services may try to initialize before the external portmapper has fully initialized. Under these circumstances, Arcserve Backup services then fail to initialize. To avoid this problem, perform the following steps:

1. Create the following registry key:

   HKEY_LOCAL_MACHINE\Software\ComputerAssociates\CA ARCserve Backup\Base\Portmap
   

2. Create the DWORD DelayedRegistration under this key.
3. Assign a decimal value for this key, indicating the number of minutes Arcserve Backup services wait before initializing portmapper registration. For example, DelayedRegistration=1 causes all Arcserve Backup services to start but not register with the portmapper for one minute after startup.