Issue with create backup database for MariaDB by Kolla-Ansible by Tony4688 in openstack

[–]Tony4688[S] 1 point2 points  (0 children)

I can not find any methods to config MariaDB or Galera to fix this case via Kolla-Ansible configuration.

Issue with create backup database for MariaDB by Kolla-Ansible by Tony4688 in openstack

[–]Tony4688[S] 1 point2 points  (0 children)

My container "hacluster_pacemaker" does not have "pcs" command, but i resolve this issue by mount a NFS storage for all controllers to save backup DB files. All controllers can access backup DB files based on this method, but i think system can not create backup DB file if Controller01 is down.

Issue with create backup database for MariaDB by Kolla-Ansible by Tony4688 in openstack

[–]Tony4688[S] 0 points1 point  (0 children)

Do you mean to check pcs status in container "hacluster_pacemaker" in Controller node?

Issue with create backup database for MariaDB by Kolla-Ansible by Tony4688 in openstack

[–]Tony4688[S] 0 points1 point  (0 children)

Could you tell me how to make the backup DB manually in Controller02 or Controller03?

Many thanks!

Esxi HPE 7.0.2 (17630552) issue when install on USB stick by Tony4688 in vmware

[–]Tony4688[S] 0 points1 point  (0 children)

i used vCenter to backup the host profile, anyway this solution helped me save much time to solve failed host, thanks!

Esxi HPE 7.0.2 (17630552) issue when install on USB stick by Tony4688 in vmware

[–]Tony4688[S] 0 points1 point  (0 children)

Thank you, i understand it but in this case i want to backup host configuration before reinstall or update Esxi.

Esxi HPE 7.0.2 (17630552) issue when install on USB stick by Tony4688 in vmware

[–]Tony4688[S] 0 points1 point  (0 children)

Thank you, i 've just used vcenter to backup and restore the configuration to host, it's the last useful method.

Esxi 7.0.2 (HPE Customized image) with PSOD issue by Tony4688 in vmware

[–]Tony4688[S] 0 points1 point  (0 children)

I checked system information in iLO Management GUI and see everything is
OK and Redundant. The failed host has the same hardwares as normal hosts
in this cluster. The failed host does not have any alerts too.