Cloud Servers for ERP and Accounting Software

ERP cloud hosting moves ERP and accounting software out of the office server room and into a data center in Turkey, with users connecting to the software over Remote Desktop (RDS). Head office, branches and field staff reach the same database, and the office no longer carries the risks of a physical server. MAV Cloud builds this setup on its VMware-based cloud server platform.

This page covers the typical architecture used in accounting software cloud server projects, the factors that drive performance, the backup and security layers, licensing points to check and the migration approach.

Why ERP and accounting software moves to the cloud

In many Turkish SMEs, the ERP or accounting software runs on a single server in the office. When it fails, invoices, stock checks and payroll stop. The move to the cloud is usually driven by four needs:

• Central access: head office, branches, the warehouse and remote staff connect to the same software with the same data.
• Regular, off-site backup: copies of the database are kept in a separate backup environment, not on an external disk in the office.
• Remote branches: one central system replaces data synchronisation between branches or separate installations.
• No server in the office: hardware refreshes, air conditioning, UPS units and disk replacements drop off the agenda.

Typical architecture: RDS session host plus a separate database server

The most common layout for ERP server hosting is two virtual servers. The first is the RDS session host, where users connect over Remote Desktop and the client side of the software is installed (see RDS in our glossary). The second is a database server that runs only the database engine and cannot be reached directly from outside.

Splitting the roles means session load does not slow database queries and a session host update does not put the database at risk. As the user count grows, the session host is resized or a second one is added, while the database server is planned separately for its own needs.

Session host size depends on the number of concurrent users and how demanding their work is. Microsoft’s session host sizing guidelines group workloads into light, medium, heavy and power, with a different number of users per vCPU for each. It also notes that logons at the start of the day are CPU-intensive, so estimates need headroom.

MAV Cloud’s RDS server sizing calculator takes concurrent users and workload type as inputs and estimates the vCPU and RAM the session host needs. The result is a starting point, reviewed alongside the software vendor’s published system requirements and busy-day usage data from the current server.

The entry cloud server configuration is 4 vCPU, 8 GB RAM and 100 GB SSD, and depending on the customer and the services selected its monthly price starts from approximately 60–100 USD. Server options are on our cloud server rental and VDS server pages.

Three factors that drive performance

When an accounting screen opens slowly over Remote Desktop, the cause is usually not the CPU but one of the items below.

Factor	Why it matters	What planning looks at
Disk latency	A database makes many small reads and writes for every record; SSD storage keeps latency low compared with spinning disks.	Keeping database and log files on SSD
Database RAM	The database engine caches frequently used data in memory; with too little RAM, every query goes to disk.	Allocating RAM by database size and growth rate
Network latency	RDS carries the screen over the network; higher latency makes typing and clicking feel sluggish.	Hosting the server close to users, inside Turkey

MAV Cloud’s cloud servers run in the Equinix Istanbul data center on a VMware-based platform. Allocated vCPU and RAM are isolated, disks live on central storage, and because the platform runs with high availability, a virtual server can be restarted on another host in the cluster if a physical host fails.

Database backup and restore

An ERP database is a file that is written to constantly. A plain file copy taken while it is running can capture half-finished transactions and may not open after a restore. That is why database servers use application-consistent backups: the database engine is brought to a consistent point before the backup, and the copy is taken from that point.

At MAV Cloud, server backups are taken with our Veeam-based cloud backup service, and backup storage is kept in Turkey. Backup frequency and retention are set by how many hours of data loss the business can accept, with separate rules possible for month-end and year-end closing.

Restoring a backup to a test environment at regular intervals and opening the software against it surfaces problems before a real failure does.

Security: access without exposing RDP to the internet

Leaving the Remote Desktop port open directly to the internet is one of the setups most often targeted by password-guessing attacks. In accounting software Remote Desktop deployments, access is planned in layers:

1. VPN or gateway: users connect through a VPN or RD Gateway first; the session host is not directly exposed to the internet.
2. Multi-factor authentication (MFA): a password alone is not enough; a second verification step is added.
3. Database isolation: the database server is reachable only from the session host.
4. Patching and account management: operating system updates, disabling unused accounts and permission reviews are done on a regular schedule.

If there is no in-house team for this work, operating system configuration, patching and monitoring can be handed over to the MAV Cloud team under Windows Server management.

Licensing reminder: RDS CALs and vendor terms

According to Microsoft’s RDS licensing page, each user or device that connects to a Windows Server session host needs an RDS client access license (CAL). CALs are available per user or per device and must be compatible with the Windows Server version.

Licensing terms for ERP and accounting software vary by vendor. Before the migration is planned, the software’s system requirements and its licensing terms for virtual environments are confirmed with the vendor or an authorised reseller.

Migration approach: a weekend cutover example

For accounting systems, the downtime window is usually the weekend. In a typical plan, user logons are closed on Friday evening and a final database backup is taken. On Saturday the backup is restored to the database server in the cloud, the software is configured on the session host and key users test invoicing, stock and reporting screens. On Sunday connection details go out to users, and the old server is kept read-only for a while as a rollback option.

MAV Cloud moved Erler Otomotiv’s on-premises systems and Lets Club’s systems to the cloud, each over a weekend, so working days were not affected. The steps are described on our cloud migration services page.

KVKK, data location, SLA and certifications

Accounting data contains employee, customer and supplier details, so it counts as personal data. Keeping it in a data center in Turkey, with backup storage also in Turkey, is an important input when assessing data location under KVKK, Turkey’s personal data protection law. This is not legal advice; each company’s own obligations should be reviewed with its legal adviser.

MAV Cloud’s service level agreement sets a monthly 99.9% availability target for the cloud server service, with first-response targets of 15 minutes for critical, 1 hour for high, 4 hours for medium and 1 business day for low priority.

MAV Cloud is certified to ISO/IEC 27001, ISO/IEC 27701, ISO 22301, ISO/IEC 20000 and ISO 9001.

Frequently Asked Questions

Which ERP and accounting software can run on a cloud server?

Most software that runs on Windows Server and can be used over Remote Desktop fits this setup. Suitability and virtual-environment licensing are confirmed with the vendor or an authorised reseller before migration.

How large a server is needed for a given number of users?

Concurrent users and workload type are the deciding factors. The RDS server sizing calculator gives a first estimate for the session host, while the database server is planned separately by database size and growth rate.

Can the database and session host run on the same server?

Small setups can start on one server; as users or reporting load grow, the database moves to its own server.

How do branches connect?

Through a VPN or RD Gateway with multi-factor authentication; no server or data synchronisation is needed at the branch.

Is backup included in the price?

Backup is offered as an add-on and shown as a separate line in the quote. Backup frequency and retention are set by how much data loss is acceptable.

If requirements are not clear yet, start with the free assessment; if they are known, the quote form is faster.