Why OceanStor BCManager Fails to Start After Installed On Virtual Machines

19

1.Set the memory and CPU resources allocated to the OceanStor BCManager virtual machine to fixed sizes instead of dynamic allocation. For details about how to set sizes of memory and CPU resources, see the OceanStor BCManager standard configuration.
2.Restart the virtual machine and shut down all virtual machines that are not in use.

Other related questions:
Why OceanStor ReplicationDirector Fails to Start After Installed On Virtual Machines?
Set the memory and CPU resources allocated to the OceanStor ReplicationDirector virtual machine to fixed sizes instead of dynamic allocation. For details about how to set sizes of memory and CPU resources, see the OceanStor ReplicationDirector standard configuration. Restart the virtual machine and shut down all virtual machines that are not in use.

Login to OceanStor BCManager After OceanStor BCManager Server Was Installed, the Add Host Page Is Not Displayed
Reinstall OceanStor BCManager Server and select Application DR management components. For details, refer to Installing OceanStor BCManager Server.

Whether the UC2.3 could be installed in virtual machine
Cannot Support Virtual machine

Install the OceanStor BCManager eBackup software
The OceanStor BCManager eBackup software can be deployed on physical machines and virtual machines (VMs). In V200R001C10SPC300 and later versions, the eBackup public cloud scenario supports DMK deployment. For details, see the user guide of the corresponding version. The eBackup user guide can be obtained from the following paths: - OceanStor BCManager V200R001C00 eBackup User Guide. - OceanStor BCManager V200R001C10 CSBS User Guide (Private Cloud, for FusionCloud 6.0.0). - OceanStor BCManager V200R001C10 Cloud Host Backup User Guide (Private Cloud, for FusionCloud NFVI 6.10.1 & FusionCloud V100R002C00SPC500). - OceanStor BCManager V200R001C10 VBS User Guide (Private Cloud, for FusionCloud 6.0.0). - OceanStor BCManager V200R001C10 eBackup Installation and Commissioning Guide (Public Cloud).

What can I do if the embedded GK fails to start after the SMC2.0 is installed?
Since C02, the authentication password of the embedded GK is changed. The default password is changed from 123456 to Change_Me. You need to open the gkcfg.ini file in D:\Huawei Technologies Co., Ltd\Switch System\SwitchCentre, set GKM-AUTH-PWD to Change_Me, and restart the SC.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top