I had a instance of vCOPS 5.8 and decided to deploy vROps 6.1 to try out some of the new features. As I didn't want the system to spend a lot of time to gather data again I thought I would just import/migrate the data from my 5.8 environment. It turns out from the release notes that this option is not available anymore and you have to follow a two-step process.
Extract from release notes
"Migrations require vRealize Operations Manager 6.0.x You cannot migrate vCenter Operations Manager directly to this version of vRealize Operations Manager. Instead, you follow a two-step process to migrate and import vCenter Operations Manager 5.8.x into vRealize Operations Manager 6.0.x, then use the vRealize Operations Manager Software Update option to upgrade vRealize Operations Manager 6.0.x to this version."
So we would need to first deploy vROps 6.0.x first, then using the import data function and then use the upgrade .pak file to bring the appliance up to 6.1. So remember to move to 6.1 you need to do it in two-steps.
Subscribe to:
Post Comments (Atom)
New Azure KMS IP and domain Addresses for activation
For Windows virtual machines deployed into Azure using marketplace images you may have created rules in your NSG or firewalls to allow the s...
-
For Windows virtual machines deployed into Azure using marketplace images you may have created rules in your NSG or firewalls to allow the s...
-
If you have Azure AD Premium P2 licences one of the reasons would of been to use Privileged Identity Management (PIM) as its a great tool to...
-
There is an article by Microsoft that lists all the URLs that Visual Studio requires to install or interaction with Azure services if you wa...
No comments:
Post a Comment