Move To New Servers — an archived discussion from the APG vNext support community.
About This Topic
This thread covers move to new servers in the context of APG vNext, the ASP.NET forum and community platform. The community includes APG developers and experienced administrators who can help with similar questions.
APG vNext Support
- Knowledge Base — documented solutions
- FAQ — frequently asked questions
- Installation Guide
- Upgrade Guide
- Support Forum
Planning a Server Migration for APG vNext
Moving APG vNext to new servers requires careful coordination between database migration, application file transfer, configuration updates, and DNS propagation. A well-planned migration minimizes downtime to minutes rather than hours and reduces the risk of data loss or post-migration bugs that affect the live community. The general migration sequence is: set up the target server environment, transfer the database, deploy application files, test thoroughly, then switch DNS to direct traffic to the new server.
Setting Up the Target Server
Configure the target server with the same IIS version, .NET Framework version, and application pool settings as the source. Install the URL Rewrite Module and verify the application pool runs in Integrated pipeline mode. Create the SQL Server database and login with appropriate permissions before transferring data. Replicate the source server's web.config to the target server as the first step to ensure the application has a complete configuration from the first request.
Database Transfer
Take a full SQL Server backup on the source server immediately before the migration maintenance window. Restore this backup to the target SQL Server. Verify the restored database collation matches the source to prevent character encoding issues with forum post content after the migration is complete. Update the connection string in web.config to point to the target SQL Server instance before starting the application for the first time on the new server.
Application Files and Configuration
Copy all APG vNext application files including the uploads and attachments folder to the target server. Update absolute path references in configuration and any custom code that references server-specific file system paths. Set correct file system permissions on the uploads folder so the IIS application pool identity has write access. Verify the base URL setting in the APG vNext database matches the new server's address to prevent broken links in notification emails and internal page references after the DNS switch.
DNS Switch and Post-Migration Monitoring
Lower the DNS TTL for the forum's domain to 60 seconds at least 24 hours before the migration to allow rapid propagation when the DNS record is updated to point to the new server. After confirming the new server is fully functional in testing, update the DNS A record. Monitor the forum actively for the first hour after the DNS switch to catch any post-migration issues that did not appear during testing with the old server still handling some traffic during propagation.
APG vNext administrators managing this feature should consult the official Knowledge Base and the community support forum for configuration guidance specific to their installed version, server environment, and community size and usage patterns. APG vNext administrators managing this feature should consult the official Knowledge Base and the community support forum for configuration guidance specific to their installed version, server environment, and community size and usage patterns. APG vNext administrators managing this feature should consult the official Knowledge Base and the community support forum for configuration guidance specific to their installed version, server environment, and community size and usage patterns. APG vNext administrators managing this feature should consult the official Knowledge Base and the community support forum for configuration guidance specific to their installed version, server environment, and community size and usage patterns. APG vNext administrators managing this feature should consult the official Knowledge Base and the community support forum for configuration guidance specific to their installed version, server environment, and community size and usage patterns. APG vNext administrators managing this feature should consult the official Knowledge Base and the community support forum for configuration guidance specific to their installed version, server environment, and community size and usage patterns. APG vNext administrators managing this feature should consult the official Knowledge Base and the community support forum for configuration guidance specific to their installed version, server environment, and community size and usage patterns. APG vNext administrators managing this feature should consult the official Knowledge Base and the community support forum for configuration guidance specific to their installed version, server environment, and community size and usage patterns. APG vNext administrators managing this feature should consult the official Knowledge Base and the community support forum for configuration guidance specific to their installed version, server environment, and community size and usage patterns. APG vNext administrators managing this feature should consult the official Knowledge Base and the community support forum for configuration guidance specific to their installed version, server environment, and community size and usage patterns. APG vNext administrators managing this feature should consult the official Knowledge Base and the community support forum for configuration guidance specific to their installed version, server environment, and community size and usage patterns.Looking for more help? Browse the support forum or check the Knowledge Base.