6.1 Portmapper Conflicts with BrightStor ARCserve Backup. If BrightStor 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, BrightStor ARCserve Backup automatically switches to another port number. To avoid having other software affected by a similar problem change the Automatic status of the CA Remote Procedure Call server service to Manual. If you have installed BrightStor ARCserve Backup in a Microsoft Cluster Services environment change the Automatic status of the CA Remote Procedure Call server service to Disabled. This enables you to avoid similar port conflicts after the system has completed the boot process. BrightStor ARCserve Backup can work with external portmappers (SFU 3.0 Noblenet Portmapper, StorageTek, Libattach and so on). However, during the machine boot up sequence BrightStor ARCserve Backup services may try to initialize before the external portmapper has fully initialized. Under these circumstances, BrightStor ARCserve Backup services then fail to initialize. To avoid this problem perform the following steps:
In the following:
HKEY_LOCAL_MACHINE\Software\ComputerAssociates\BrightStor ARCserve Backup\Base\Portmap
Create the DWORD DelayedRegistration.
Assign a decimal value for this key indicating the number of minutes BrightStor ARCserve Backup services wait before initializing portmapper registration. For example DelayedRegistration=2 causes all BrightStor ARCserve Backup services to start but not register with the portmapper for 2 minutes after startup.
provides information related to this event.