The High availability and disaster recovery article in the PowerVC Knowledge Center explains how to capture a backup of the PowerVC database on the primary server and restore it to a backup server.

Please note that PowerVC services typically won't be running on the standby server until the primary fails, but PowerVC services can run on both servers simultaneously. However, system administrators should avoid using both servers simultaneously.

As noted in the cited article, run '/usr/bin/powervc-services stop' to stop all PowerVC services and run '/usr/bin/powervc-services start' to start all PowerVC services.

It might be desirable to prevent PowerVC services from starting at boot time on the standby server.

The following command can be used to list all of the PowerVC services:

 [root@cldvpvc1 system]# /usr/bin/powervc-services status | grep '●'
 ● openstack-swift-account.service - OpenStack Object Storage (swift) - Account Server
 ● openstack-swift-object.service - OpenStack Object Storage (swift) - Object Server
 ● openstack-swift-proxy.service - OpenStack Object Storage (swift) - Proxy Server
 ● openstack-swift-container.service - OpenStack Object Storage (swift) - Container Server
 ● memcached.service - Memcached
 ● clerk-api.service - clerk API Server
 ● powervc-bumblebee.service - PowerVC Bumblebee
 ● ttv-validation-api.service - TTV API Server
 ● powervc-cinder-ibm-health.service - PowerVC cinder monitor service
 ● powervc-nova-ibm-health.service - PowerVC nova monitor service
 ● openstack-ceilometer-api.service - OpenStack ceilometer API service
 ● openstack-ceilometer-collector.service - OpenStack ceilometer collection service
 ● openstack-ceilometer-notification.service - OpenStack ceilometer notification agent
 ● openstack-ceilometer-polling.service - OpenStack ceilometer polling agent
 ● openstack-nova-api.service - OpenStack Nova API Server
 ● openstack-nova-conductor.service - OpenStack Nova Conductor Server
 ● openstack-nova-scheduler.service - OpenStack Nova Scheduler Server
 ● openstack-nova-consoleauth.service - OpenStack Nova VNC console auth Server
 ● openstack-nova-novncproxy.service - OpenStack Nova NoVNC Proxy Server
 ● openstack-nova-compute-828422A_218ABCV.service - OpenStack Nova Compute Server
 ● openstack-nova-compute-828422A_218AB8V.service - OpenStack Nova Compute Server
 ● neutron-server.service - OpenStack Neutron Server
 ● openstack-nova-ibm-notification.service - OpenStack Nova IBM Notification
 ● openstack-nova-ibm-ego-ha-service.service - OpenStack Nova IBM EGO HA Service
 ● openstack-nova-ibm-ego-resource-optimization.service - OpenStack Nova IBM EGO Resource Optimization
 ● openstack-cinder-api.service - OpenStack Cinder API Server
 ● openstack-cinder-scheduler.service - OpenStack Cinder Scheduler Server
 ● openstack-cinder-volume-cldv9000.service - OpenStack Cinder Volume Server
 ● powervc-cinder-conductor.service - PowerVC Cinder Conductor Server
 ● openstack-glance-api.service - OpenStack Image Service (code-named Glance) API server
 ● openstack-glance-registry.service - OpenStack Image Service (code-named Glance) Registry server
 ● rabbitmq-server.service - RabbitMQ broker
 ● httpd.service - The Apache HTTP Server
 ● memcached.service - Memcached
 ● mariadb.service - MariaDB database server
 [root@cldvpvc1 system]#

Please note that grep is looking for the bullet character ('●') produced by the 'powervc-services status' at the start of each stanza.

The command above was run on PowerVC at the 1.3.2.0 level (as shown by the 'cat /opt/ibm/powervc/version.properties' command). The set of services will vary with the level of PowerVC.

From the output above, one can obtain the service file names (the first token following the bullet character in each line), all of which should be found in the list generated by 'systemctl list-unit-files' RHEL command.

For each service file name, run the RHEL command 'systemctl disable ' to prevent the service from being started at boot time.

If/when the standby server is brought into production, it might be a good idea to again enable PowerVC services to start at boot time. For each service file name, run the RHEL command 'systemctl enable ' to reenable the service to start at boot time.