1C on a VPS: How to Host It and What to Consider

Moving 1C to a server solves the office’s biggest headache: the database no longer depends on a single computer, and employees can work with it from anywhere.

File mode or client-server mode

File mode is simpler and cheaper but copes poorly with concurrent use — from roughly five active users onward, locks and slowdowns appear. Client-server mode with a DBMS is more robust and designed for more users, but it requires a 1C server license and a more powerful configuration.

How many resources to plan for

For terminal access, size memory by the number of concurrent users: Windows Server itself takes 3–4 GB, plus roughly 1 GB per active user. CPU — from 4 vCPU. Leave headroom on the disk: the database grows, and logs and backups are added to it.

How employees will connect

This is usually terminal access (RDP). Don’t expose it directly to the internet — it’s the first target for password brute-forcing. The right approach is to let employees in through a VPN, restrict the list of IP addresses and enable lockout after several failed login attempts.

Backups

Use 1C’s own tools to export the database on a schedule, and protect the server itself separately — with a snapshot before configuration updates and regular backups of the virtual machine. Backups must be stored off the server itself: in cloud storage or on a separate VPS.

What not to do

• Keep the only copy of the database on the same disk it runs on.
• Update the configuration without a snapshot.
• Give every user administrator rights.
• Turn off Windows updates “so they don’t get in the way.”

Our support team can help you choose a configuration for your number of users — just tell us how many people work in the database and how large it is.