What is image-based backup and how is it different from file backup?
File backup copies individual files — your documents, spreadsheets, photos. Image-based backup copies the entire server (operating system, applications, configurations, drivers, and all data) as a single bootable image. If a server dies, the image can be virtualized — meaning we boot the entire failed server inside our backup appliance and have your staff working again in minutes, not the days it would take to rebuild Windows, reinstall applications, restore data, and reconfigure everything from a file backup.
What is the 3-2-1-1-0 backup rule?
The modern industry standard for ransomware-resistant backup. Three copies of your data, on two different media types, with one copy off-site, one copy immutable (cannot be modified or deleted, even by an administrator with the encryption key), and zero errors verified through testing. The old 3-2-1 rule was good enough before ransomware groups started targeting backups themselves. The added "1" (immutable) and "0" (verified) are what stop a 2 AM ransomware event from also taking out your safety net.
How do you protect backups from ransomware?
Modern ransomware crews delete your backups first — that's how they force the ransom payment. Our backup stack defends against that with: immutable cloud storage (S3 Object Lock and equivalents that physically cannot be modified or deleted for the retention window), separate authentication realms (so a domain-admin compromise doesn't grant access to the backup console), MFA on the backup admin portal, anomaly detection that pages us when backup change-rates spike (a ransomware-encryption signature), and air-gapped retention for our highest-tier clients. The result: even if your production environment is fully encrypted, your backup is still there to restore from.
Do you actually test the restores or just claim you do?
We test. Quarterly. Documented. For every protected server and every workstation policy, we perform a real restore-and-boot test inside our backup environment and capture the results in a written quarterly report you receive by email. If a backup fails its test, we fix it immediately — not next quarter. Verizon's 2024 Data Breach Investigations Report found that "untested backups" was the single biggest reason ransomware victims still paid the ransom. We don't ship untested backups.
What is RTO and RPO and what are mine?
Recovery Time Objective (RTO) is how long it takes to get you running again after a failure. Recovery Point Objective (RPO) is how much data you can afford to lose, measured in time (e.g., "we run overnight backups so the most you'd lose is yesterday's transactions"). Both are documented in writing in your backup agreement. For most Arkansas SMB clients, we run overnight backups — that's the safe cadence for the many line-of-business applications that aren't VSS-aware and can't be captured during business hours. RTO under 4 hours for full server failure is standard thanks to instant virtualization. More frequent capture is available for compatible workloads (databases with native dump or snapshot capability).
Where is the cloud copy stored?
Your offsite copy is replicated to U.S.-based, SOC 2 Type II audited datacenters with at-rest encryption (AES-256), in-transit encryption (TLS 1.3), and geographic redundancy across two regions. For HIPAA-covered clients, we use HIPAA-compliant infrastructure with signed Business Associate Agreements. For CJIS-scoped clients, FBI-CJIS-compliant infrastructure with FIPS 140-3 validated cryptography.
What backup platforms do you use?
We deploy enterprise-grade backup platforms in three categories depending on your environment: image-based BCDR appliances with local hardware plus immutable cloud replication and instant virtualization (most common for SMBs with on-prem servers); virtualization-platform-integrated backup (for clients running their own hypervisor); and cloud-to-cloud backup for Microsoft 365 and Google Workspace tenants — because Microsoft and Google do not back up your tenant. That's your responsibility. We pick the right platform for the use case, not whatever the vendor pays us best.
How much does backup & disaster recovery cost?
Backup & DR covers three moving parts — workstations, servers, and cloud (M365 / Google Workspace) — scoped together so there are no gaps. Workstation tiers scale with retention (30-day file recovery at the entry tier; 1-year image-based with instant-virtualization at the top tier). Server tiers scale with data volume and recovery-time objective. Cloud-to-cloud backup is the only fix for M365 deletions and ransomware — Microsoft does not back up your tenant. Your number is scoped on the free 10-minute discovery call — no commitment, no pitch.