Backing up and restoring HP Insight Management 7.3 Central Management Server (Windows)

Technical white paper | HP Insight Management 7.3
Appendix H: Matrix infrastructure orchestration resynchronization
In some cases, infrastructure orchestration may not be able to fully recover a server definition when changes are made after
the backup.
Matrix infrastructure orchestration resynchronization limitations
• If, as a post-backup activity, a data disk was added to a physical server, this will result in the attachment of an
additional storage pool entry. After recovery, the disk will exist and be operational as part of the server, but it will
not be in the server definition reported by infrastructure orchestration. When the service is deleted from
infrastructure orchestration, all disks, including the newly added data disk, will be deallocated.
• If, as a post-backup activity, a data disk was added to a virtual server, this will result in another disk being added to
the virtual server definition on the VM host. After recovery, the disk will exist and be operational as part of the
server, but it will not be in the server definition reported by infrastructure orchestration.
A. If you add the disk to the server in infrastructure orchestration using the original name, this reconnects the
existing disk to the virtual server. In this case, ensure that you use the same disk attributes specified when
the disk was created. Otherwise, the new attributes will be displayed in the server definition instead of the
actual attributes of the existing disk.
B. When the service or server is deleted from infrastructure orchestration, all disks, including the newly added
data disk, will be deallocated.
• For post-backup activity for infrastructure orchestration services provisioned to an external cloud provider, the
post-restore behavior is similar to the behavior for virtual servers.
A. If, as a post-backup activity, a server was added to an existing service, the restored service definition will
contain only the original server(s). If a new service was added as a post-backup activity, the service will not
exist in infrastructure orchestration after the restore. Enter the following command to identify the missing
servers:
ioassist –c unknown_cloud_servers
Note:
For server pools created as a post-backup activity, ioassist will not list the missing servers for those pools until the
server pool is reconfigured.
B. When the service is deleted from infrastructure orchestration, clean up the orphaned servers from the cloud
provider console.
• For post-backup changes to security groups (firewall definitions) for cloud provisioned services and
servers, the changes will not be recovered by infrastructure orchestration. Servers in the cloud will
use these definitions, but the definitions will no longer exist in infrastructure orchestration. Enter
the following command to list the orphaned security groups:
ioassist –c firewallrulegroups
• For post-backup changes to load balancer configurations managed by infrastructure orchestration,
the changes will be unknown to infrastructure orchestration after the restore. Some load balancers
registered in the HP IO inventory may be out of sync. To address this, follow these steps:
A. HP IO will attempt to automatically synchronize its internal state with the state of the load
balancers in its inventory. The synchronization task will begin when the Matrix infrastructure
orchestration service is started, and then repeat at a configurable interval. The default interval
is 86400 (seconds). You set the synchronize.loadbalancer.resources.timer
value in the <HPIO>\conf\hpio.properties file.
B. Manually update the load balancer configurations in the IO inventory to reflect the changes
made after the backup.
85