Here is the infrastructure and backup plan for your ZATCA intermediary server, designed for OCI Riyadh/Jeddah. This plan includes a 2x safety buffer on all storage to ensure long-term stability and full compliance with Saudi data regulations.
ZATCA Intermediary Server Infrastructure & Backup Plan (OCI Riyadh/Jeddah)
This table provides a comprehensive overview of the requirements for a 5-year operational window. All storage figures already include the 2x Safety Buffer as the default baseline.
Key Explanations for Your OCI Setup
Processor (OCPU): ZATCA Phase 2 requires real-time XML signing (ECDSA) and hashing (SHA-256). At the 100,000/day level, your server handles over 1.1 invoices per second 24/7. High OCPU counts ensure the QR code generation doesn't lag during peak retail hours.
Storage (The 2x Default): This capacity covers the XML files, Database Indexes (for fast searching of 5 years of data), Application Logs, and the OS overhead.
OCI Gold Policy: This is a native OCI feature. You simply "assign" this policy to your storage volume, and it automatically handles the Daily/Weekly/Monthly rotation you requested.
Object Lifecycle Management: For the 10k and 100k tiers, keeping 5 years of data on "Live" disk is expensive. We recommend a rule that automatically moves XMLs older than 1 year to OCI Archive Storage, which costs significantly less while staying compliant.
WORM (Write Once Read Many): To prevent accidental deletion or tampering (a ZATCA audit requirement), OCI enables Retention Rules on your OCI Object Storage buckets for the yearly backups. This "locks" the data for exactly 5 years.
Note: For the sizing above, our technical team is available to sit with your team to finalize the allocation and configuration based on your specific environment needs.
