Reference: The existing/ current server in use will be referred as Server A
The new server to be used with Veeam Backup & Replication will be referred as Server B
This document outlines the detailed steps for migrating Veeam Backup & Replication from the current server (Server A) to the new server (Server B). The operating system to be used on the new server is Windows Server 2025, and the Veeam version to be installed and migrated is Veeam 12.3.2.3617
Prerequisites:
• RAID Block Size: 256 KB
• Storage Formatting: New storage must be RAID10 formatted with:
o REFS (Resilient File System) with a 64KB block size, or
o XFS (for Linux repositories) with block clone enabled.
• Storage Capacity: The new storage should be 2.5x the size of the production storage to ensure sufficient capacity for future growth and backup requirements.
Pre-Outage Tasks:
1. Install Windows Server 2025 on Server B:
• Action: Install Windows Server 2025 on the new server (Server B).
• Details:
o Use the Windows Server 2025 installation media and follow the steps for installation.
o Choose the appropriate edition (Standard or Datacenter).
o Ensure the server is configured with the required partitions and disk setup.
o Set up the network with a static IP address, DNS, and gateway configuration.
o Important: Do not join the domain as per request.
2. Perform OS Updates and Antivirus Installation:
• Action: Ensure that the server is fully updated and protected.
• Details:
o Run Windows Update from Settings -> Update & Security to install all available updates, including critical security patches.
o Install antivirus software compatible with Windows Server 2025 (e.g. Microsoft Defender for Endpoint).
o Configure AV exclusions for Veeam processes and backup storage locations to avoid performance issues.
3. Install Veeam Backup & Replication on Server B:
• Action: Install the same version of Veeam that is currently running on Server A.
• Details:
o Download the installation files for Veeam 12.3.0.310
o Install Veeam Backup & Replication using the same components and configuration as on Server A.
o Do not configure new backup jobs at this point, as the configuration will be restored from Server A.
4. Install NTFS Deduplication Role (if applicable):
• Action: If NTFS deduplication is used in the network, install the role on Server B.
• Details:
o Open Server Manager -> Add Roles and Features.
o Select the File and Storage Services role, then under File and iSCSI Services, ensure that Data Deduplication is selected.
o Complete the installation.
o This ensures that the server will be capable of restoring files from deduplicated NTFS volumes during backup or recovery operations.
5. Check and Update your Firewall Rules:
• Action: Review and update any firewall rules to reflect the new server (Server B) and ensure that all required Veeam services are allowed.
• Details:
o Verify that all relevant ports (e.g., ports for Veeam services like 9401 for backup proxies, 10001 for backup jobs, and ports for the Veeam Backup & Replication Console) are open between the necessary components (backup repositories, proxies, etc.).
o If there are any rules specific to Server A’s IP address, update them to match the new IP address or hostname of Server B.
6. Configure Disk-Level SMART Monitoring:
• Ensure disk-level SMART checking is enabled for the new storage.
• Set up email notifications to alert administrators to any disk health issues such as potential failures or performance degradation.
• This proactive approach ensures issues can be addressed before impacting backup operations.
7. Plan an Outage Window:
• Plan for an outage window of 1 hour per 250GB of data being copied to minimize disruption to backup jobs.
• Copying data during the migration process will cause backups to fail while the operation is in progress.
________________________________________
During the Outage:
1. Take a Veeam Configuration Backup on Server A:
• Action: Take a final configuration backup of Veeam on Server A and shut it down.
• Details:
o On Server A, open Veeam Backup & Replication Console, stop and disable all jobs.
o Go to Main Menu -> Configuration Backup.
o Perform a final backup of the configuration and store the file in a safe location.
2. Client copies the data from iSCSI Storage to the new storage on Server B:
• Action: After shutting down Server A, client starts the copy of data from iSCSI storage to the new storage.
• Details:
o Client initiates the data transfer process.
o Monitor transfer progress and performance.
o The estimated time for the copy to complete is ~ 32 hours
o Confirm data copy has completed successfully
3. Restore Veeam Configuration on Server B:
• Action: Restore the configuration backup from Server A to Server B.
• Details:
o Transfer the final configuration backup file from Server A to Server B.
o On Server B, open Veeam Backup & Replication Console, go to Main Menu -> Configuration Restore.
o Restore the configuration backup to bring over all job settings, repositories, proxies, and other components.
4. Rescan the Veeam Service Provider and Local Storage Repository:
• Action: After restoring the Veeam configuration, rescan the Veeam service provider and the new local storage repository to ensure all components are correctly recognized.
• Details:
o In the Veeam console, go to Backup Infrastructure -> Service Providers, right-click the service provider, and select Rescan.
o Similarly, rescan the new local storage repositories by going to Backup Infrastructure -> Backup Repositories, right-click the repository, and select Rescan.
o This ensures that all storage resources and service providers are available and properly connected.
5. Verify Veeam Components:
• Action: Check that all Veeam components (Backup Repositories, Proxies, etc.) are available and working after the rescan.
• Details:
o Verify that all backup repositories, backup proxies, WAN accelerators (if applicable), and other Veeam components are listed as online and healthy in the Veeam console.
o Check the status of all configured jobs and ensure no issues are reported with the infrastructure setup.
6. Update Veeam to the Latest Version (if applicable):
• Action: Once the configuration restore is complete, update Veeam to the latest version.
• Details:
o Download the latest update for Veeam Backup & Replication (if a newer version is available than Veeam 12.3.0.310).
o Follow the update process, ensuring that all Veeam components (including backup proxies and repositories) are updated as well.
o Reboot the server if required and confirm that the update has been applied by checking Help -> About in the Veeam console.
7. Test Backup and Replication Jobs:
• After restoring the configuration, rescanning repositories, and updating Veeam, test all critical backup and replication jobs.
• Run a few selected replication and backup jobs manually to ensure they start and complete successfully.
________________________________________
Post-Outage Tasks:
1. Final Verification and Sign-Off:
• Action: Perform final checks and obtain client sign-off after successful migration.
• Details:
o Review the Veeam logs for any warnings or errors.
o Ensure that all scheduled backup jobs are working without issues.
o Confirm that the new storage is functioning correctly and deduplication (if applicable) is handled properly.
o Hold a wrap-up meeting between TIMG and Client
o Obtain final sign-off to close the migration project.
________________________________________
Important Considerations:
• Check for any deduplicated data that may require additional configuration.
• Update all Veeam components (proxies, repositories, etc.) if any version change occurs.
• Rescan storage and service provider components post-migration to ensure full functionality.
• Backup Impact: Evacuating storage will temporarily cause backup job failures. Schedule a sufficient outage window to minimize disruptions.
• Outage Window Planning: Plan for 1 hour of outage per 250GB of data to be moved during the evacuation process.
• Storage Sizing: Ensure that new storage is 2.5x the size of production storage to accommodate future growth and maintain optimal performance.
• Proactive Monitoring: Enable SMART disk monitoring on new storage and configure email alerts to detect any issues early.