Server for Tally or ERP in India: How to Size It
By Rohit, Founder ·
Quick answer: A server for Tally or an ERP should be sized from how many people use it at the same time and how large your data is, not from your headcount. Tally's own help pages list a 2 GHz 64-bit processor, Windows Server 2012 or later and SSD or NVMe storage for TallyPrime Server, with RAM chosen from user count and data size, and an example of about 20 GB when 20 users each run two instances through remote desktop on the same machine. For an ERP such as Odoo, the vendor's own rule of thumb is about 6 concurrent users per worker process, with workers set from the CPU count. Whatever you run, protect the data with a tested backup, a UPS and, ideally, ECC memory. This guide walks through each decision using the vendors' published figures, and shows where a custom-built Intel Xeon server from ProStation Systems fits.
This guide is for accountants, CA firms, traders, distributors, small manufacturers and IT managers in India who run TallyPrime or an ERP and are deciding what to buy or upgrade. Nothing here is a ProStation benchmark: ProStation publishes no Tally or ERP performance figures, so every number is either quoted from the software vendor's documentation (and named as such) or is arithmetic we label as illustrative. Vendors change their requirements between releases, so check the linked pages for your version before you buy.
What Does a Server for Tally or ERP Actually Do?
A business server for accounting or ERP software does three jobs, and each one points to different hardware:
- It holds the shared data. Company data sits in one place so everyone works on the same books. This is mainly a storage and reliability question.
- It serves several people at once. Depending on the product, the server runs only a data service (TallyPrime Server) or the whole application and its database (most ERPs). This is a CPU and memory question.
- It protects the data. Backups, power protection and error-correcting memory decide whether one bad day costs minutes or a month of entries.
Two terms are worth defining. TallyPrime is Tally Solutions' accounting and business management software for Windows. TallyPrime Server is a separate add-on that Tally describes as offering "powerful data server capabilities over the Gold license", so that several users can work on the same company data at the same time. An ERP (enterprise resource planning) system is a larger suite covering accounting, inventory, sales and often manufacturing, usually backed by a database such as PostgreSQL or SQL Server.
Do You Need a Server at All?
Not always. Tally publishes a standalone configuration for a single computer, and the pages we reviewed do not state a user count above which a server becomes mandatory. So decide by your situation:
| Your situation | What the vendor documentation points to | Practical hardware implication |
|---|---|---|
| One or two people use Tally, nothing else runs on the machine | Tally's standalone requirement applies: 1.8 GHz 64-bit processor, 4 GB or more RAM | A good desktop with SSD storage, a UPS and a tested backup can be enough |
| Several people enter data in the same company at the same time | TallyPrime Server is designed for multiple users on the same company data | A dedicated machine with reliable storage and backup is worth the cost |
| Staff connect by remote desktop and run Tally on the server | Tally's RAM guidance multiplies memory per user by instances per user | Size RAM generously; Windows Server and remote desktop licences are also needed |
| You run an ERP with a database | The vendor sizes workers and memory by concurrent users | A server with ECC memory, NVMe storage and headroom for the database |
| Accounting and other systems (file shares, CCTV, backups) must share hardware | Each role adds its own load | Consider one virtualization host; see our office virtualization host guide |
What Tally's Own Documentation Recommends
These figures come from Tally Solutions' help pages ("Recommended System Configuration for TallyPrime" and "Recommended Hardware Configuration for TallyPrime Server"). They are published recommendations and minimums, not a performance guarantee.
| Machine | Processor | RAM | Storage | Operating system |
|---|---|---|---|---|
| Standalone computer or client-server system (Silver and Gold editions) | 1.8 GHz 64-bit; Core 2 Duo, Dual Core, Core i3, i5, i7 equivalent or above | 4 GB or more | 150 MB free to install, excluding company data | 64-bit Windows 7, Windows Server 2008 R2 or above, including Windows 11; 64-bit MS Office for Excel and Word |
| TallyPrime Server | 2 GHz 64-bit; Core i3, i5 equivalent or above | Chosen from the number of users and the data size | SSD or SSD NVMe, sufficient for the number of users; keep the data path and the scheduled backup path on separate storage | Microsoft Windows Server 2012 or above (64-bit) |
| Client machine for TallyPrime Server | 1.8 GHz 64-bit; Core i3, i5 equivalent or above | 8 GB or more for smoother operation | SSD or SSD NVMe for better performance | Microsoft Windows 7 or above (64-bit); continuous internet connection |
Tally also states that TallyPrime can currently be installed only on Microsoft Windows, so a Linux server cannot run Tally itself. Notice how modest the processor floor is. For Tally the case for a server-grade machine is mostly about reliability, storage, memory protection and sharing the box with other roles, not raw clock speed.
How Much RAM? Tally's Own Method
Tally's guidance is to choose RAM from the number of users and the data size. If TallyPrime and TallyPrime Server run on the same machine and users connect by remote desktop, multiply the average RAM per user by the average number of instances per user. Tally's worked example uses 500 MB per user, 20 users and 2 instances each: 500 x 40 is about 20 GB of RAM, as a minimum. If TallyPrime runs on the users' own machines instead, Tally notes that server RAM use is lower because each user machine supplies its own memory.
The table applies that same method to other team sizes. The 500 MB per user figure is Tally's example, not a measurement of your data, so check your own usage in Task Manager during a busy period before you rely on it. This is illustrative arithmetic.
| Users on the server | Instances per user | Tally's method (500 MB each) | Next step |
|---|---|---|---|
| 5 | 1 | 2.5 GB | Add the operating system and other roles, then round up to the next standard memory size |
| 10 | 1 | 5 GB | Same |
| 20 | 1 | 10 GB | Same |
| 20 | 2 | 20 GB (Tally's own example) | Same |
These figures cover Tally only. Windows Server, antivirus, backup jobs, a file share or any virtual machine you add on the same server all need their own memory on top. When in doubt, choose more ECC memory than the sum, because upgrading later means another outage. Our guide to ECC vs non-ECC RAM explains why server memory with error correction matters for accounting data.
Sizing an ERP: The Vendor's Rule of Thumb
ERPs differ, so ask your vendor for a sizing sheet at your number of concurrent users. As one published example, Odoo's deployment documentation gives these rules for its application server:
- Workers: "(#CPU * 2) + 1" as a rule of thumb.
- Capacity: "1 worker ~= 6 concurrent users".
- Memory: Odoo assumes 20 percent of requests are heavy (about 1 GB of RAM per worker) and the rest light (about 150 MB), assuming the database queries and computed fields are well designed.
Applied to a machine with 4 CPUs, as illustrative arithmetic: 4 x 2 + 1 gives 9 workers, which by the vendor's rule serves roughly 54 concurrent users. The workers alone need about 9 x (0.2 x 1,000 MB + 0.8 x 150 MB) = 9 x 320 MB, which is about 2.9 GB. The database, the operating system, file caching and backups all need memory beyond that, and a badly customised ERP will use far more than the rule assumes. Treat the result as a floor for discussion with your ERP partner, not as a quote.
CPU, Storage and Network Choices
- CPU: Tally's floor is a modest 2 GHz 64-bit processor, so you are not buying a server for Tally's sake alone. A current Intel Xeon platform makes sense when the server also runs an ERP database, file shares or virtual machines, and because Xeon platforms support ECC memory.
- Storage: Tally lists SSD or SSD NVMe for TallyPrime Server and wants the data path and the backup path on separate storage. Use mirrored drives so one disk failure does not stop work (see RAID levels explained) and read NVMe, SAS and SATA compared when choosing the drive type. RAID keeps the server running; it is not a backup.
- Network: Office clients reach the server over the LAN, and Tally recommends a continuous internet connection for clients, so keep the router and switch on the same UPS as the server. For switch and cable choices see 1GbE, 10GbE and 25GbE explained.
- Form factor: A tower server fits an ordinary office room without a rack; compare in tower vs rack servers in India.
Backups: What Tally Recommends
An accounting server is only as good as its last restorable backup. Tally's own guidance includes:
- Take daily backups, and schedule automatic backups multiple times a day when transaction volume is high.
- Keep copies in more than one place: a local drive, an external hard disk and cloud storage. TallyDrive, Tally's cloud backup, is available from Release 7.0 and needs an active TSS subscription.
- Use incremental backups for daily runs, keep several versions rather than overwriting, and verify backups weekly.
- Test the restore process; Tally lists not testing restores as a common mistake. When restoring, take care with the Replace option, which permanently deletes the existing data.
- In a standard backup, users cannot enter data while the backup runs, so schedule it for a quiet period. Tally states that TallyPrime Server lets users keep working during a backup.
The CISA-recommended 3-2-1 rule (three copies, on two kinds of media, with one copy off site) is a good frame for all of this. A NAS as a backup target is a common second copy for small offices. Remember that backing up to a different folder on the same disk does not survive that disk failing.
Power and Uptime
An unclean shutdown in the middle of writing accounting data is the most avoidable cause of trouble. Tally's help page for data error 1392 lists causes such as a corrupted temporary file, antivirus interference, malware and bad sectors on the hard disk, and recommends a repair of the company data, a malware scan or a system file check, depending on the cause. Take a backup before any repair. Beyond software, protect the hardware:
- UPS: size it from the server's measured draw, not the power supply label; our UPS sizing guide shows how.
- Redundant power supplies: worth the cost when an hour of downtime costs more than the second supply; see the dual PSU guide.
- Work out what downtime costs you: use the method in the real cost of server downtime to decide how much redundancy is sensible.
Operating System and Licensing
Tally lists Windows Server 2012 or above for TallyPrime Server, but Microsoft's lifecycle page shows that Windows Server 2012 R2 reached the end of its extended support in October 2023, with only paid Extended Security Updates after that. For a new purchase choose a version Microsoft still supports. According to Microsoft's lifecycle pages, Windows Server 2022 has mainstream support until October 2026 and extended support until October 2031, and Windows Server 2025 has mainstream support until November 2029 and extended support until November 2034.
Windows Server is a separate purchase from the hardware. It is licensed per physical core with Client Access Licences for users or devices, and staff who work in remote desktop sessions on the server also need Remote Desktop Services CALs. Our guide to Windows Server licensing for a custom server explains the counting rules, and you should confirm the final count with an authorised Microsoft reseller.
Which ProStation Build Fits?
ProStation Systems builds new, custom-assembled tower servers with Intel Xeon processors and ECC DDR4 memory, in three tiers. The table shows the published specifications of the two tiers that matter for accounting and ERP; the Ultra tier (dual Xeon Scalable with GPUs) is built for AI and rendering and is not needed for Tally or a typical ERP.
| Tier | Processor | Memory | Storage | Network | Operating system | Typical fit |
|---|---|---|---|---|---|---|
| Starter | Intel Xeon E (entry) | 16 to 64 GB ECC DDR4 | 1 TB NVMe SSD | 1GbE or 10GbE | Ubuntu or Windows Server | TallyPrime Server for a small team, file shares, light business applications |
| Pro | Intel Xeon Scalable | 64 to 256 GB ECC DDR4 | 2 TB NVMe SSD plus HDD options | 10GbE or 25GbE | Ubuntu, Windows, VMware or Proxmox | An ERP with its database, several virtual machines, a growing team |
The right tier depends on your measured memory need from the sections above, not on headcount. Every ProStation system is built to a specification agreed with you and tested before dispatch (see how every ProStation server is built, stress-tested and delivered), and the hardware carries a one-year warranty with extended plans available at additional cost; the warranty page has the terms. Free consulting is available through ProStation consulting. If budget is the main constraint, our sister brand Serverwale sells tested refurbished tower servers and AMC plans; the new vs refurbished comparison explains the trade-off. For an overview of planning for a bigger team, read the medium-sized business server guide and the small business server guide.
Checklist Before You Order
- Count concurrent users and instances. Write down who uses Tally or the ERP at the same time, and whether they connect by remote desktop or from their own PCs.
- Measure memory. Check real usage in Task Manager during a busy period, then apply Tally's method (RAM per user x instances) or your ERP vendor's sizing sheet.
- Decide the architecture. Standalone, TallyPrime Server, remote desktop, or an ERP application and database on one machine.
- Settle the software licences. Windows Server edition, core licences, CALs and RDS CALs, plus the TallyPrime Server add-on where relevant.
- Separate the data path and the backup path onto different storage, as Tally advises.
- Plan the backup. Daily at minimum, copies in more than one place, one off site, and a restore test before you rely on it.
- Protect the power. UPS sized from measured load, and the router and switch on a UPS as well.
- Write down who owns support. Hardware warranty, Windows administration and Tally or ERP partner support are three different things.
The small business use case page and the enterprises and SMB solutions page show how ProStation approaches these deployments, and the servers page lists the tiers in detail.
Frequently Asked Questions
Q1. What server do I need for TallyPrime?
It depends on how many people use it at once and how big your data is. Tally lists a 2 GHz 64-bit processor, Windows Server 2012 or above and SSD or NVMe storage for TallyPrime Server, with RAM chosen from user count and data size. Apply Tally's method of RAM per user multiplied by instances per user, then add memory for the operating system and any other roles.
Q2. How much RAM does a Tally server need?
Tally's own example is 500 MB per user across 20 users with 2 instances each, about 20 GB as a minimum, when TallyPrime and TallyPrime Server run on the same machine and users connect by remote desktop. If TallyPrime runs on each user's own PC, server RAM use is lower. Measure your real usage rather than relying on the example.
Q3. Can I run TallyPrime on a Linux server?
No. Tally states that TallyPrime can currently be installed only on Microsoft Windows. You can still run Tally inside a Windows virtual machine on a host that uses another hypervisor, as long as the Windows licensing is in order.
Q4. How should I back up Tally data?
Tally recommends daily backups, more often when transactions are heavy, with copies on a local drive, an external hard disk and cloud storage such as TallyDrive, plus weekly verification and restore tests. Follow the 3-2-1 rule: three copies, two kinds of media, one copy off site. RAID alone is not a backup.
Q5. How many users can one ERP server handle?
It depends on the ERP and how it is customised. As one published example, Odoo's documentation gives a rule of thumb of about 6 concurrent users per worker and (CPU count x 2) + 1 workers, which on a 4-CPU machine is roughly 54 concurrent users by that rule. Ask your ERP partner for a sizing sheet based on your own concurrent users.
Q6. Do I need ECC memory for an accounting server?
ECC memory detects and corrects single-bit memory errors, which suits a server holding financial records that run all day. Every ProStation tier uses ECC DDR4 memory with Intel Xeon processors. It does not replace backups, but it removes one cause of silent data corruption.
Q7. Is a new or a refurbished server better for Tally and ERP?
A new custom-built server lets you specify the exact memory, storage and warranty, which matters for a production accounting system. Tested refurbished servers from ProStation's sister brand Serverwale are a reasonable option when budget is tight or for a secondary or test machine. Compare them on the new vs refurbished page and ask for warranty terms in writing.
Final Recommendation
Size from concurrent users and measured memory, put the data on SSD or NVMe storage separate from the backups, and treat the backup, the UPS and the Windows licence as part of the server's cost, not afterthoughts. A single well-specified Intel Xeon tower with ECC memory is a sensible home for TallyPrime Server or a small ERP; step up to a larger tier only when your own numbers say so. For help working out the figures, contact ProStation Systems or call +91 87962 44410 (WhatsApp: wa.me/918796244410) for free consulting, or build a configuration in the configurator.
Sources: Tally Solutions help, Recommended System Configuration for TallyPrime and Recommended Hardware Configuration for TallyPrime Server; TallyPrime Server product page; Tally help, Backup and Restore and Data Management Errors and Resolutions; Tally Solutions, How to Keep Your TallyPrime Data Safe; Odoo documentation, Deploying Odoo (worker and memory rules of thumb); Microsoft Learn lifecycle pages for Windows Server 2012 R2, 2022 and 2025; CISA, "Data Backup Options" (3-2-1 rule); Microsoft Windows Server licensing documentation as summarised in our licensing guide. Vendor requirements change between releases, so check the current pages before purchase.