cancel
Showing results for 
Search instead for 
Did you mean: 

VxSvc starting too late ?

Carsten_Hennig
Level 4
Certified
StorageFoundationHA 4.2 on Windows 2003 (without SP1)

After a reboot of the server the VCS agents for MountV and VMDg are trying to probe the resources and fail. The problem is obviously, that the VERITAS Enterprise Administrator Service (VxSvc / vxob) is started approximately 30 seconds after the last failed probe.

Therefore, service groups which should be auto-started, are not started.

Did anyone see this problem before ?

Thanks,
Carsten
1 REPLY 1

Carsten_Hennig
Level 4
Certified
Correction: The service groups that should auto-start will do so after some minutes, as soon as the volumes and diskgroups are probed again. I still think that this is not a good behaviour.

Carsten