_____About the Customer…
Tabuk Cement Company (TCC) is one of Saudi Arabia’s major cement manufacturers.
- TCC relied on ageing SPARC/Solaris infrastructure to run its mission‑critical Oracle E‑Business Suite (EBS) R12 and Oracle Database 19c workloads. Hardware limitations, extensive EBS customisations, and constrained budgets prevented TCC from performing a full production migration or an on‑premise infrastructure refresh.
Cloudwrxs, leveraging its AWS expertise and partnership with Stromasys, designed a cloud‑based DR solution using Charon‑SSP SPARC emulation on Amazon Web Services (AWS).The combined solution consisted of a successful Proof of Concept (PoC), full DR migration, and the creation of a modern User Acceptance Testing (UAT) environment on AWS.
The Customer__ Challenge.
The entire production environment operated from a single physical site, creating a high‑risk dependency with no Disaster Recovery (DR) capability.
Key issues included the following:
Single Point of Failure for Mission‑Critical ERP
Production workloads were operated from a single data centre, creating high vulnerability in the event of system or facility failure.
Ageing, High‑Maintenance SPARC Hardware
Legacy servers required specialised maintenance and had limited vendor support, driving both operational and financial risk.
Solaris OS Incompatibility with Cloud Providers
Native migration was impossible due to Solaris constraints, requiring specialised SPARC emulation.
Complexity of Highly Customised Oracle EBS
Heavy customisation demanded careful validation, sizing, and performance tuning to ensure DR performance.
Requirement to Preserve Existing Capital Investment
SPARC hardware remained under vendor support until 2034, meaning TCC needed a DR strategy without forced re‑platforming.
If left unaddressed, these problems would increase downtime, risk of data loss, and operational costs, as well as restricting the company’s ability to adopt new capabilities.
Migration ___Approach.
IAM guardrails, logging, encryption baselines, and compliance controls.
deployed for the application tier, database tier, and license server.
to replicate the customer’s on-premise Solaris environment.
to mirror production state and maintain continuous synchronisation.
RTO validation, rollback enablement, failover execution, and performance benchmarking.
Using Docker-based controlled builds, enabling TCC to test future changes.
The Partner__Solution.
Cloudwrxs and AWS delivered a modern, resilient DR solution for TCC without requiring immediate platform migration or replacement of production SPARC servers. This successful engagement demonstrates a proven pathway for organisations operating legacy Solaris workloads.
How AWS Service were used:
Amazon EC2 Dedicated Hosts (m6i)
Provided scalable compute for Charon‑SSP SPARC emulation.
AWS CloudFormation
Automated consistent infrastructure deployment.
Amazon S3
Delivered durable backup storage for Oracle workloads.
Amazon CloudWatch
Provided real‑time operational monitoring and alerting.
Amazon VPC
Ensured isolated, secure network architecture.
Elastic instance sizing
Allowed DR workloads to scale on demand.
AWS IAM & AWS KMS
Enforced encryption for DR data at rest and enforced strict access governance.
AWS CloudTrail, AWS Config & Amazon GuardDuty
Enabled for continuous compliance and change tracking.
How Services Were Delivered
Cloudwrxs handled the full lifecycle of the migration, including:
- Assessment workshops
- Architecture design
- Cost modeling
- Migration to AWS
Post-migration Cloudwrxs provided:
- 24×7 managed services—patching
- Backup monitoring
- DR drills
- Security audits
These services ensured the environment remained secure, compliant, and continuously optimised.
Business__Outcomes.
TCC’s leadership reported increased confidence in operational stability:
“Now the business feels more confident because the disaster recovery process can reduce potential downtime and keep systems running smoothly.”
Business Continuity & Resilience
Before Migration
Single‑site hosting with no DR capability
After AWS Migration
AWS‑based DR ensures rapid recovery and uninterrupted operations.
Cost Efficiency
Before Migration
High hardware maintenance costs
After AWS Migration
Lowered operational costs and eliminated hardware dependency.
Modernisation Readiness
Before Migration
Legacy Solaris constrained transformation initiatives.
After AWS Migration
Cloud‑based workloads enable phased Solaris‑to‑Linux modernisation.
Enhanced IT Productivity
Before Migration
Manual processes and limited monitoring.
After AWS Migration
CloudWatch, automation, and managed services.
Compliance & Audit Improvement
Before Migration
Legacy infrastructure created audit and resilience gaps.
After AWS Migration
AWS governance, encryption, and validated DR procedures.
_____About Cloudwrxs
…
