FAQs
Have Questions?
How do you know our backups actually work?
CinchOps verifies backups on a schedule for every managed client. Verification checks that each backup completed and that the copy can actually be used, so a failed job or a full storage target gets caught before you need a recovery. The results are documented so the business owner can see them instead of assuming.
What is the difference between backup and disaster recovery?
Backup is the copy of the data. Disaster recovery is the plan and the systems that get the business operating again after a major outage. A business can have backups and still have no disaster recovery plan. CinchOps treats them as one service because the backup is the foundation of the recovery, but the recovery also needs the documented procedures, the trained team, and the tested timeline.
How do you protect backups from ransomware?
Ransomware now actively looks for backup repositories and tries to encrypt or delete them. CinchOps stores backup copies as immutable, meaning the copy cannot be modified or deleted for a defined retention period regardless of who has the credentials. Backup credentials are separated from production admin user credentials. An offsite copy lives outside the customer network entirely so a full network compromise still leaves a clean copy to restore from.
What recovery time and recovery point can we expect?
It depends on the system. CinchOps writes a recovery time objective and a recovery point objective for each system as part of the plan, then designs the backup approach to meet those objectives. A typical small business gets file server recovery within four hours, business application recovery within eight hours, and full network restoration within one to two business days for a worst-case scenario.
What happens during the first 30 days of engagement?
First week: inventory the current backup approach and identify the gaps. Week two: deploy or configure the immutable backup copies and offsite replication. Week three: write the recovery runbook with the business owner and document the recovery objectives per system. Week four: run the first restore test and review the results. After that, the quarterly cadence takes over.
