FAQ Hub · Backup & Recovery · Disaster Recovery

Got questions? We've answered them — by role.

Find answers to the exact questions your role cares about — whether you're a business owner worried about cost, a CTO setting RTO targets, or an IT admin who just needs restores to work.

SME

SME Owner / Business Owner

You want protection that's simple, affordable, and doesn't require a dedicated IT team to manage.

Yes — and small businesses are often the most exposed. Large enterprises have IT teams, insurance, and workarounds. As an SME, a serious data loss or a week of downtime can be business-ending. The good news is protection doesn't have to be expensive. Our Essential plan starts with what you actually need right now, at a cost that scales with your business.

Our Essential plan is designed for 1–5 servers and covers daily automated backups, 7-day retention, and AES-256 encryption. We price transparently — no hidden restore fees, no surprise overage charges. The Business plan adds hourly backups and 30-day retention for growing SMEs. Talk to our team or ask our AI Advisor for a ballpark based on your server count and data volume.

Yes — that's exactly what our managed service is. We configure the backup schedules, monitor health daily, send you alerts if something needs attention, and handle restores when you need them. You don't need to understand the technical details to stay protected.

External drives fail, get lost, and are stolen — and they only protect against data loss, not against the location where the drive is stored (fire, flood, theft). Cloud-based backup keeps a separate, encrypted copy off-site automatically, without anyone having to remember to plug in a drive. It's not more complex — it's actually simpler, because it runs itself.

It depends on what went wrong and what plan you're on. A single file or database table can typically be restored in minutes from a snapshot. A full server restoration takes longer and depends on data size. If you need to be back up and running within hours — not days — you'd want to add our Disaster Recovery plan on top of backup, which maintains a live standby environment ready to take over.

CEO

Chief Executive Officer

You need to know the business risk, the cost of inaction, and what you're buying — without the technical deep-dive.

The cost of downtime almost always exceeds the cost of prevention. For a business with 50 employees, even a single day of downtime can cost more in lost productivity, missed orders, and recovery effort than a year of backup and DR protection. The real question isn't "can we afford backup?" — it's "can we afford not to have it?" Our team can model a simple cost-of-inaction estimate for your business size.

Backup protects your data. Disaster Recovery protects your operations. Backup answers: "Can we recover the data?" DR answers: "Can we keep the business running?" If losing data for a few hours is your main risk, backup may be enough. If being offline for even an hour costs significant revenue or violates customer SLAs, you need DR on top. Most growing businesses need both — starting with backup, adding DR as the stakes increase.

Yes — if your backups are isolated from your primary systems. Ransomware increasingly targets connected backup drives and network shares. Our backup environment is kept isolated and encrypted, so an attacker who compromises your primary systems cannot reach your backup copies. Recovery from a clean backup means you can decline the ransom and restore to a point before the infection.

RTO — Recovery Time Objective — is how long your business is allowed to be offline before recovery. It's not a technical number; it's a business decision. An e-commerce business might set an RTO of 1 hour because every hour offline loses orders. An internal HR system might tolerate 24 hours. Defining your RTO tells us which DR plan fits you — and what it costs to meet that target.

CIO

Chief Information Officer

You need documented controls, audit-ready retention, governance alignment, and a plan that passes scrutiny.

Our Enterprise plan includes compliance reporting — backup job logs, retention policy documentation, recovery test reports after each DR drill, and encryption certification. These are formatted to support IT audits, client security questionnaires, and regulatory submissions. We can also provide a written DR plan document that meets the typical requirements of ISO 27001 and DPDP (India's data protection framework).

Retention is tiered: 7 days (Essential), 30 days (Business), and multi-year archival on Enterprise with custom policy definition. You can set different retention tiers for different workloads — shorter for transactional logs, longer for critical business records. All retention policies are documented and can be provided in writing for policy registers.

All data is stored in our Madurai data center — India-based, on Indian soil. Access is restricted to authorised Cloud iCRM personnel under a defined access control policy. Your data is AES-256 encrypted at rest, and keys are scoped per customer. We do not share or co-mingle data across customers. Data does not leave India unless you specifically request a geo-redundant copy, which remains within our managed infrastructure.

We run DR drills on a schedule matching your plan tier: annually (Standard), quarterly (Business), or monthly (Enterprise). Each drill involves simulating a failover to the standby environment, verifying that critical systems and databases respond correctly, and documenting the result. You receive a written drill report that includes what was tested, what passed, any gaps identified, and remediation steps. These reports are suitable for governance presentations and audit files.

CTO

Chief Technology Officer

You need technical specifics — RPO, RTO, replication mechanics, encryption standards, and how this integrates with your stack.

We support full, incremental, differential, archive, and replication-based backup modes. Schedules are configurable: hourly, 6-hourly, 12-hourly, daily, and weekly. Incremental backups track changed blocks only, so hourly backup doesn't mean hourly full-disk reads. Replication-based backup gives the lowest RPO — as low as 15 minutes — by continuously copying changed data to the standby environment.

We support MySQL, PostgreSQL, and Microsoft SQL Server — both agent-based and agentless snapshot methods depending on the workload. For application-level consistency (ERP, CRM, custom apps), we support pre/post-snapshot hooks to quiesce the application before taking the backup. VPS and dedicated server images are supported for OS-level recovery alongside application-layer backup.

Both modes are available depending on your plan and preference. Automated failover uses health monitor triggers — if your primary environment fails a defined health check threshold, the standby is promoted and DNS/routing is updated automatically, with notification sent immediately. Guided manual failover provides a documented runbook with step-by-step instructions for your team to execute, with our support team available throughout. Enterprise plans can also configure a hybrid: automated detection with human-confirmed promotion.

Backup data is encrypted at rest using AES-256 with per-customer key scoping. Data in transit between your infrastructure and our data center uses TLS 1.2/1.3. Replication traffic is encrypted in transit as well. Encryption keys are managed within our infrastructure and are not exposed to external systems. Key rotation policies are available on Enterprise plans.

Yes. Restores can be targeted to an isolated environment — a separate VM or test directory — without touching production. This is the standard method we use for DR drills. You can verify data integrity, run application smoke tests, and confirm the restore is clean before deciding whether to promote it. We recommend scheduling test restores quarterly at minimum, and our Business and Enterprise plans include assisted test restore sessions.

FIN

Finance / Purchase Team

You need predictable costs, clear ROI justification, and no surprise charges on invoices.

Plans are tiered by server count and feature set: Essential (1–5 servers), Business (5–25 servers), Enterprise (custom). Storage usage within the plan is included up to a defined limit, after which tiered storage pricing applies. We tell you the limit upfront — no surprise overages on your invoice without prior notification. DR plans are priced separately based on RTO tier and infrastructure complexity.

Standard restores are included in your plan — you can request restores without a per-event charge. Support is included at a tier matching your plan: email (Essential), priority queue (Business), dedicated manager (Enterprise). There are no per-call support fees. The only additional charges that could apply are for storage overages or out-of-plan DR services, which we discuss before activating.

The simplest frame is cost of downtime vs. cost of protection. Calculate your revenue per hour, multiply by your likely maximum outage window without protection (often 24–72 hours for a serious incident), and compare to the annual plan cost. For most businesses, one avoided incident pays for years of protection. We can also provide a one-page cost-of-inaction document formatted for board-level review on request.

Yes on both. Annual payment is available and typically comes with a discount compared to monthly billing. All invoices include GST — our GSTIN is 33ALOPD0613R1Z0. We provide tax-compliant invoices monthly or annually depending on your billing cycle. Invoices are itemised by service for straightforward expense accounting.

IT

IT Admin / Operations

You need reliable backup jobs, fast restores, clear monitoring, and as little manual overhead as possible.

You receive email alerts for any failed or incomplete backup job, including the error reason and which specific job or dataset was affected. Business and Enterprise plans include a monitoring dashboard showing backup status, last successful run time, and verification results per job. If a failure is on our infrastructure side, our team is alerted simultaneously and begins remediation before you need to take action.

Restore requests are raised through our support portal or via email to your account's support queue. For Business and Enterprise plans, restores go to a priority queue — response typically within the hour during business hours. A single file or database table restore from a recent snapshot is usually completed within 30–60 minutes. Full-server restores depend on data volume. We communicate ETAs before starting.

We provide a lightweight agent for Linux and Windows servers that is installed once per server. Installation takes under 10 minutes per server. For virtual environments, agentless snapshot-based backup is also available — no software installed on the guest VM. After initial setup, the agent runs fully autonomously. Remote installation assistance is available from our team if needed.

Granular file-level restore is supported — you can browse the backup snapshot and select individual files, folders, or database tables for restore to the original or an alternate location. Full-image restore is also available for scenarios requiring a complete server rebuild. Granular restore is typically much faster and is the default first approach for most recovery requests.

We coordinate the drill schedule with you to choose a low-traffic window. Before the drill, you provide a list of critical applications and services to verify post-failover. Our team handles the failover execution to the standby environment, and you (or we, jointly) verify that each application responds correctly — database queries, application login, key workflows. The whole drill typically takes 2–4 hours including verification. We document the results and you receive a written report same day.

Glossary

Key terms — plain language

Backup and DR come with a lot of acronyms. Here's what the important ones actually mean.

RPO

Recovery Point Objective

How much data you're allowed to lose. An RPO of 1 hour means you could lose up to 1 hour of data in a worst-case incident. Lower RPO = more frequent backup or replication.

RTO

Recovery Time Objective

How long you're allowed to be offline. An RTO of 4 hours means your business needs to be back running within 4 hours of an incident. Lower RTO = more infrastructure investment (DR, replication).

Failover

Switching to Standby

The process of moving operations from a failed primary environment to a standby one. Can be automatic (triggered by health checks) or manual (following a runbook).

Standby Env.

Standby Environment

A pre-configured, continuously updated copy of your infrastructure that sits ready to take over. The heart of Disaster Recovery — without it, failover means rebuilding from scratch.

Incremental

Incremental Backup

Only backs up data that has changed since the last backup. Much faster and smaller than a full backup each time — used for frequent schedules (hourly, 6-hourly).

AES-256

AES-256 Encryption

The encryption standard used to protect your backup data at rest. The same standard used by banks and government systems — practically unbreakable with current technology.

Still Have Questions?

Talk to a human — or our AI Advisor

Our team can answer role-specific questions, model a cost-of-inaction estimate for your business, and recommend the right plan — no obligation, no sales pressure.

Have a Question ?

Contact our Customer Support team to get answers.
Contact US