What a planned move preserves
A planned server move relocates the existing OneView installation. With a complete coordinated recovery set, the new server retains the license, client database, users, branding, vendor connections, activity history, verification history, and installed software version.
Do not use a planned move to operate the same installation on two servers at once.
Requirements
Prepare:
- a maintenance window in which the old services can be stopped;
- a supported new host with the required network access;
- a current database backup and tested database restore owner;
- the complete protected OneView installation backup;
- client-managed certificates when applicable;
- the exact installed OneView version; and
- an approved DNS, hostname, proxy, and firewall change plan.
Move protected material only through the client's approved encrypted backup or host-transfer process. Do not email it, commit it, attach it to a ticket, or place it in an ordinary shared drive.
Planned migration
- Record the installed version, architecture, hostname, access mode, and database recovery point.
- Stop integrations and begin the maintenance window.
- Stop the old OneView installation and prevent automatic restart.
- Back up the database and complete protected installation as one coordinated recovery set.
- Prepare the new host and restore the selected coordinated set using the approved procedure for the exact version.
- Apply the approved DNS, hostname, certificate, proxy, and firewall changes.
- Start OneView on the new host.
- Validate database connectivity, license status, users, branding, vendor connections, activity history, and safe synthetic verifications.
- Reopen integrations only after acceptance.
- Keep the old host stopped and securely retire its protected copies after the rollback window.
Do not run initial activation over restored data, start both hosts concurrently, restore only part of the coordinated set, or edit application records to bypass a failed check.
Lost-server recovery
If the old host is unavailable, use the Disaster-recovery runbook. Recovery may require a replacement-license or installation-transfer process. Do not create a new installation against an existing client database without that approved process.
Checklist
- Maintenance window, owners, target host, and exact version confirmed.
- Integration traffic stopped and old installation shut down.
- Coordinated database and protected installation backup completed.
- New host restored through the approved exact-version procedure.
- DNS, HTTPS, proxy, and firewall changes validated.
- License, users, configuration, activity history, and synthetic verification passed.
- Old host remains stopped and protected copies are retired after acceptance.