Parallels

Symptoms

OS template synchronization with new Virtuozzo for Windows 4.x node failing with error messages.
From PBAS interface it is not possible to migrate Container running on Virtuozzo for Windows 3.x version to node running Virtuozzo for Windows 4.x version due to unsynchronized templates.

Cause

Virtuozzo for Windows 4.0 version introduced OS template name changes (from w2k3* to Windows_2003_std-5.2.3790* just for example), as result:

• w2k3* templates could be installed and synchronized with Virtuozzo for Windows 3.5 version only
• Windows_2003_std-5.2.3790* templates could be installed and synchronized with Virtuozzo for Windows 4.x version only
• before migration Container is based on w2k3 OS template
• destination node have no such template installed and it is not possible to install it (so PBAS does not allow to start migration at all)
• after manual migration via native Virtuozzo Tools OS template name is converted transparenty into new name and PBAS Conflict resolver could not resolve conflict as the Container is already based on Windows_2003_std-5.2.3790* template according to VZAgent reply from node, but PBAS have only w2k3* template recorded for this Container in subscription and Container properties in PBAS database.

Resolution

To migrate Containers from Virtuozzo 3.x for Windows to Virtuozzo 4.x for Windows it is required to use the following steps:

• upgrade PBAS to the latest available version
• update synchronization state/register new templates from destination Virtuozzo for Windows node:
  • select destination Virtuozzo for Windows 4.x node from the list on Top > Service Director > Virtuozzo Manager > Nodes screen
  • select OS templates tab, click on Register OS templates from node button
  • select Applications tab, click on Register Application templates from node button
• create a new Hosting plan clone for existing plan which the Container is currently based on with changing OS template during cloning process (so new Hosting plan will have exactly the same settings as old one but OS template should be Windows_2003_std-5.2.3790* instead of w2k3):
  • select Hosting plan which the subscription is currently based on Top > Billing Director > Product Manager > Hosting Plans screen
  • select General Settings tab and click on Clone button
  • select new OS template Windows_2003_std-5.2.3790* in the drop-down list for OS template field
  • (optional) select new Hosting plan on Top > Billing Director > Product Manager > Hosting Plans screen, select Applications tab and replace old applications with a new versions
• execute /usr/sbin/hspc_win-vz3-to-vz4.pl script inside PBAS Container to move the Container to new Hosting plan created at previous step, the script will perform the following actions:
  • in ineractive mode it will request Container ID, destination Hosting plan ID
  • plan ID will be changed for the Container to ID of new plan
  • OS template name for the Container will be changed to Windows_2003_std-5.2.3790* in PBAS database
• migrate the Container using native Virtuozzo Tools (PIM, PMC)
  
• execute 'Detected newly appeared Virtuozzo VE conflicts' task on Top > Action Log > Task queue screen
• resolve Container is not registered conflict for migrated Container on Top > Migration director > Conflict Resolver > Containers screen selecting Register the Container option and assigning it to already existing subscription.
• execute 'Detected newly appeared Virtuozzo VE conflicts' task on Top > Action Log > Task queue screen once again to make second conflict about Deleted Container on source node to disappear