Billing is in INR and every invoice shows 18% GST. Email support@webji.services is staffed 24/7 in Hindi and English, with an average first reply under 60 minutes. Phone +91 141 4941811 is the office number, answered in business hours rather than as a support line.
Linux server backup methods compared
Four methods cover almost every Linux server, and the right one depends on what has to come back first. rsync is file-level and scriptable, a filesystem snapshot is instant but fragile, a block-level agent handles cPanel accounts and databases, and BorgBackup keeps long encrypted history.
| Method | Strength | Limitation |
|---|---|---|
| rsync | Fast, bandwidth-efficient, scriptable | Copies files as found — a live MySQL directory copied mid-write is corrupt at restore |
| Snapshots (LVM, ZFS/Btrfs) | Point-in-time image in seconds | Same-disk snapshots survive nothing the disks do not |
| JetBackup / R1Soft CDP | Block-level agents, database modules, incremental-forever, browser restores | Panel-ecosystem bound — JetBackup is native on cPanel |
| BorgBackup | Deduplicated, encrypted, append-only repositories | Admin-scripted; manual discipline |
Most servers end up using two of these: snapshots for a same-hour rollback and an agent or repository for the copy that has to survive the host. If you are deciding between a virtual and a physical server first, the VPS server backup page covers the virtualised case.
What a Linux server backup must include
A Linux backup must capture configuration, application data and the database together. Files alone restore a site that will not start, and a database dump alone loses the TLS certificates, cron jobs and web server rules that made it work.
- /etc — web server, PHP, firewall and SSH configuration, plus cron and systemd units.
- /var/www and /home — application code, uploads and each hosting account's files.
- Databases — mysqldump with --single-transaction for InnoDB, pg_dump for PostgreSQL, or an agent module that keeps a consistent point in time.
- Mail and DNS — mailboxes, aliases and zone files when the server hosts either.
- Certificates and keys — TLS certificates and private keys, which expire silently and break a perfect restore.
Raw copying of database files while MySQL or PostgreSQL is running is the most common cause of a restore that will not open. Use a logical dump or a database-aware module, as the 3-2-1 backup rule guide explains for websites.
Backup schedule, retention and off-site storage
You set the schedule and the retention window; the agent keeps to it. Hourly suits a database with steady transactions, nightly suits most application servers, and the first run is a full copy while later runs move only changed blocks.
Retention is usually 7, 30 or 90 days. Yesterday's copy fixes a deleted file, 30 days covers corruption noticed late, and 90 days covers a dispute or audit window. Longer retention uses more storage, so it is a decision rather than a default.
Every tier stores off-site, in a different failure domain from the server. A backup on the same array as the data it protects dies with the array, which is the gap between a RAID mirror and a real backup.
Restore testing on a Linux server
A backup is only proven by a restore. Setup includes the first full backup and a verified test restore, so you confirm the archive opens and the database starts before an outage forces the question.
File and folder restores run from the console in minutes with no ticket. A lost machine needs bare-metal restore, which writes partitions, bootloader, packages and data back to replacement hardware or a fresh instance instead of a day of reinstalling by hand.
Agree the RPO (how much data you can lose) and the RTO (how long you can be down) before you buy. Those numbers set the schedule and the restore path, and they belong in the plan, not in a sales conversation.
Linux server backup plans and pricing (INR)
Four published plans, billed monthly in INR before 18% GST. Backup.Help is self-service with the agent and 200 GB of remote storage; the Managed Support tiers add assisted restores and server care.
| Plan | What you get | Price (₹/mo) | |
|---|---|---|---|
| Backup.Help App + 200 GB | Automatic backups, 200 GB storage | 1,300 | Order Now |
| Managed Support — 10 queries | Managed server care + 200 GB remote backup | 7,000 | Order Now |
| Managed Support — 25 queries | Managed care + 500 GB remote backup | 11,000 | Order Now |
| Managed Support — 50 queries | Managed care + 500 GB remote backup | 20,000 | Order Now |
Live pricing from billing.webji.in, read 30 October 2026. Backup.Help app also available ₹3,900/quarter or ₹13,000/year.
Who Linux server backup is for
It fits anyone running a Linux VPS, dedicated or cloud server where the data changes daily: cPanel resellers, e-commerce stores, SaaS teams and agencies holding client sites on one machine.
- You manage the server yourself and cannot rebuild it from memory.
- You run MySQL, MariaDB or PostgreSQL that cannot lose a day.
- You need a copy that survives the host, the account or the admin who left.
It is not the right buy for a single WordPress site that only needs its files copied — the WordPress website backup service covers that at a smaller size. It also does not replace a vendor-mandated database export in their own format.
How Linux server backup setup works
- Email the server details to support@webji.services. We confirm the distribution, disk size, database engine and paths in scope.
- We install the agent or configure the job and run the first full backup. That run is the long one.
- You choose the schedule, retention window and RPO. We confirm the storage the plan includes and quote any extra in INR before you pay.
- We run a test restore and show you the result. The schedule goes live only after that.
Why WebJi® for Linux server backup
- Backups have been part of the business since 2005, so a restore is routine work.
- RPO and RTO agreed before the first job runs, not after an outage.
- 24/7 email restore help in Hindi and English, average first reply under 60 minutes.
- Setup covers the agent install, the first backup and a verified test restore.
- INR pricing with GST invoices, and a published plan table you can read before contacting anyone.
The wider server backup solutions range covers Windows, cPanel and cloud server plans if you need to compare them side by side.
Frequently Asked Questions
How do I back up a Linux server properly?
Capture configuration, application data and the database together, then keep one copy off the machine. For a running MySQL or MariaDB instance use mysqldump with --single-transaction, or an agent with a database module, because copying raw data files under load can restore corrupt.
What is the best Linux backup tool?
rsync is enough for files on one server, BorgBackup or Restic add deduplication and encryption for larger sets, and an agent such as JetBackup or R1Soft handles cPanel accounts and databases without scripting. Choose by recovery target and who runs the restore, not by feature list.
Does WebJi® back up Linux servers automatically?
Yes. The agent or scheduled job runs hourly, nightly or weekly as you choose, and later runs copy only changed blocks. You hold the console login and can start a file, database or full-server restore yourself.
Where are Linux backup copies stored?
In WebJi® backup storage in a separate facility from the production server, encrypted with AES-256 at rest. That is the off-site leg of the 3-2-1 rule, and it is what survives a lost array, hypervisor or data centre.
Can a full Linux server be restored after failure?
Yes. Bare-metal restore writes partitions, bootloader, packages and data back to replacement hardware or a fresh instance. Files and databases can also come back individually, which is the faster path for most incidents.
How long are Linux server backups retained?
Retention is set per policy, commonly 7, 30 or 90 days. Daily points cover accidental deletes, 30 days covers corruption found late, and 90 days covers a dispute or audit window. A longer window needs more storage, covered by the plan bundle or an INR quote.
What is the difference between a snapshot and a backup?
A snapshot sits on the same storage volume as the server, so if that volume fails the snapshot fails with it. A backup is a separate, versioned, encrypted copy in another facility. Snapshots shorten rollbacks; backups are what recover a business.