Seamless Windows Server Migration to New Hardware Using Carbonite Migrate - Oman Healthcare Success Story
Aug 19, 2025
Client Overview
- Organization: Al Noor Healthcare Solutions
- Industry: Healthcare IT
- Location: Muscat, Oman
- Existing Infrastructure: Windows Server 2012 R2 on aging HPE ProLiant DL380 Gen8
- Purpose: Hosting Electronic Medical Records (EMR), Active Directory, File Shares
- Users Served: 300+ across 4 clinics in Muscat, Sohar, Salalah, and Nizwa
Objective
To seamlessly migrate Windows Server workloads to HPE ProLiant DL380 Gen11 running Windows Server 2019 using Carbonite Migrate, (https://dataguardnxt.com/vendors/carbonite.html) achieving zero downtime for 24/7 healthcare operations.
Challenges in the Oman Context
| Constraint |
Description |
| 24/7 Healthcare Operations |
Continuous uptime essential for patient services |
| Limited IT Support in Branches |
Migration required full remote orchestration |
| Regulatory Compliance |
Align with Oman Data Protection Law (RD 6/2022) |
| Legacy Applications |
Ensure EMR software compatibility on new OS |
Why Carbonite Migrate?
- Real-time replication for minimal downtime
- Zero-disruption cutover
- Remote orchestration capabilities
- Physical-to-Physical (P2P) & Physical-to-Virtual (P2V) support
- Encrypted data transfers for compliance
New Environment
- Server: HPE DL380 Gen11
-
OS: Windows Server 2019 Standard
-
Hypervisor: VMware ESXi (future virtualization)
-
Roles: Active Directory, File Services, EMR System
Migration Strategy
Approach: Physical-to-Physical migration using Carbonite Migrate
Tools Used:
- Carbonite Migrate Console (Windows)
-
Veeam Backup (pre-migration image)
-
Windows Admin Center (post-migration)
-
SolarWinds/Pingdom (downtime monitoring)
Step-by-Step Migration Plan
1. Pre-Migration Planning
- Inventory current roles, IPs, and applications
-
Verify new hardware readiness
-
Backup using Veeam
-
Create rollback plan
2. Carbonite Migrate Setup
- Install Carbonite Migrate on source (2012 R2) and target (2019) servers
-
Configure secure, encrypted replication
3. Real-Time Replication
- Initial sync outside working hours
-
Continuous mirroring of live changes
4. Cutover Planning
- Schedule Friday 11 PM cutover
-
Test boot on target server
-
Validate AD, DNS, and file services
5. Cutover Execution
- Final sync + hostname/IP updates
- Health checks and validation
-
Decommission old server after observation period
Results
| Metric |
Result |
| Downtime |
Less than 15 minutes |
| User Impact |
Zero reported disruptions |
| Performance |
50% faster EMR response |
| Compliance |
Fully aligned with Oman Data Protection Law |
| Support |
Ongoing remote monitoring & patching
|
Challenges & Solutions
| Challenge |
Solution |
| Legacy EMR compatibility |
Sandbox testing on new OS |
| Firewall blocking Carbonite |
Opened TCP ports 443 & 3037 temporarily |
| DNS conflicts |
Cleared stale records & flushed caches
|
Lessons Learned
- Test cutover 24-48 hours before go-live
-
Real-time replication prevents sync bottlenecks
-
Encrypted replication is critical for compliance
Next Steps
- Migrate branch servers to virtual environments
-
Implement high availability clustering
-
Integrate with Azure AD for hybrid identity
Client Testimonial
"We were extremely satisfied with the seamless migration using Carbonite. The DataguardNXT team ensured zero business disruption, and the new setup is significantly faster and more secure."
— IT Manager, Al Noor Healthcare, Muscat
