Documentation
The instructions on how to migrate sites from IIS 6 host to IIS 8.5 host
Obtaining
The migration script can be downloaded here.
Changes
Version 0.1.5
- Initial release
Version 0.1.13
- Fixed Bug: POA-103335 New DotNetNuke installations doesn't work after migration
Key notes
- Migration from IIS 6 to IIS 8.5 only.
- Migration from Windows Server 2003 to Window Server 2012 R2 only.
- Service Automation 6.0.5 and later.
- Content of each W2K3 server will be duplicated on another Windows Server 2012 R2. So for each w2k3 server new 2012 R2 server should be deployed and registered in POA.
- Migration of IIS data is performed by MS Web Deploy tool (including content, permissions, bindings, ssl certificates, application pools, config, etc.).
- Migration is performed by entire node.
- IP addresses are migrated to the new node.
- Source node will be automatically shut down after migration.
- During migration subscriptions will be switched to another service template. Plan switch order will be generated for each subscription hosted on migration node.
- Dedicated service templates and plans is created per each migrating node.
Migration scenario:
- Deployment new Windows Server 2012 R2.
- Preparation of source Windows Server 2003 node
- Preparation of dedicated service templates/plans.
- Switch subscriptions to dedicated plans
- Pre-migration content sync
- Second content sync
- Source shutdown
- Transfer IPs to the new node
- Operation Automation database update.
On Steps 1-6, customers’ content is not affected.
Real switch of customer’s services is performed on steps 7-9
Rollback is possible and it can revert changes of step 7-9 fast.
Known Issues and Limitations
The following issues and limitations should be taken into consideration before the migration procedure:
- A migration is possible only after upgrade to version 6.0.5.
- A content of each Windows Server 2003 node will be duplicated on another Windows Server 2012 R2 node. So for each Windows Server 2003 node a new Windows Server 2012 R2 node should be deployed and registered in Operations Automation.
- The migration is performed by entire node (there is a problem to migrate by a single subscription because it requires changing of used shared IPs and DNS updating).
- IP addresses are migrated to the new node.
- A source node will be automatically shut down after migration.
- During the migration process, a subscription is switched to another Service Template. The switch order is generated for each subscription hosted on the migrating node.
- Dedicated service templates and service plans are created per each migrating node.
- The destination node has the same location of the CustomerData folder as source node.
- In case of migration from the 32-bit OS:
- Running of 32-bit IIS Web Applications on 64-bit OS is not supported by Operations Automation. Thus, during the migration process, the ASP.NET 32-bit extensions will be switched to 64-bit mode.
- After the migration is completed, the Perl 64-bit CGI extension will we used instead of 32-bit ones.
- ASP.NET 1.1 is not supported on Windows Server 2012 R2. Such webspaces can be switched to ASP.NET 2 before or after the migration in CCP.
- Migration of WebMatrix, ColdFusion, FrontPage and SharePoint is not supported.
- Web statistics is not updated in AWStats for migrated sites.
- DotNetNuke aps package cannot be updated to the latest version as DotNetNuke 7.0.6-1 doesn't support ASP.NET4.5