- Nightly
- backups for everything ALCO hosts, kept off-site
- Tested
- restores on a schedule, results written down
- 2
- copies at least, one away from the source
- Written
- recovery steps, so a bad day has a plan
What is included.
What ALCO does for you under backup, in plain terms.
Automated, off the machine
Backups run on their own, every night at least, and land somewhere the source machine and its credentials cannot reach.
Immutable or separated copies
Where ransomware is the worry, a copy is locked so nobody, including an attacker with your password, can change or delete it inside the window.
Microsoft 365 and Google Workspace
Mail, OneDrive, SharePoint, Drive and shared drives backed up outside the provider. Microsoft and Google keep the service up; they do not keep your deleted mailbox.
Laptops and desktops
The documents folder on the sales manager's laptop is company data too. Endpoints are backed up quietly in the background.
Agreed recovery objectives
How much data you can lose and how long you can be down, decided per system, written down, and matched to a design that can meet it.
Scheduled test restores
A green job light is not a restore. We restore real files and systems on a schedule, time it, and record what worked and what did not.
A recovery runbook
Step by step, in what order, with whose credentials and from which copy. Kept where you and we can both read it when the office is dark.
Hosting included
Every site and application on the ALCO server is backed up nightly and the copies kept off-site, as standard.
Someone to call
Deleted the wrong folder at 4:55 PM? Call the help desk. Restores are a request, not a project.
How it works.
Four steps, each one written down as we go.
- 1
Rank what must come back
We list your systems and data with you, and decide for each how much loss and how much downtime is acceptable.
- 2
Protect it
Jobs, retention, encryption, off-site and immutable copies and alerting are set up. Then we do a first restore to prove it, not just watch the job finish.
- 3
Test on a schedule
Restores of real files and systems, timed and recorded. Gaps go on the list and get fixed.
- 4
Keep it current
New systems get added, old ones retired, and the runbook is reviewed each quarter with you.
Who this is for.
The one-copy business
Your only backup is a drive plugged into the server, or the cloud provider's own recycle bin. That is one failure away from nothing.
Insurers and customers asking
Cyber insurance forms and client questionnaires now ask for separated, tested, immutable backups. This is how you answer yes.
Anyone who has been hit before
Ransomware, a dead RAID, a leaver who emptied a shared drive. You know what it costs; this is the plan for next time.
Providers we can source for you
161 providers available through ALCO and our Telarus partnership. We compare them for you and stay your point of contact after the order.
Frequently asked questions.
Is Microsoft 365 or Google Workspace not already backed up?
The service is resilient; your data in it is not backed up for you. Deleted items age out, retention policies are not restores, and a compromised account can empty a mailbox. We back it up separately.
How often do you test?
On a schedule we agree per system, typically quarterly for the important ones, and every restore we do for a real request counts as evidence too. You can see the results.
Where are the copies kept?
Off the source machine and, for ALCO-hosted systems, off-site in the United States. For other systems we agree the destination with you and write it in the plan.
What does disaster recovery add to backup?
Backup is the copy. Disaster recovery is the order you bring things back in, where you run them while the office is down, who does what, and how long it takes. We write that down and rehearse it.
Can you take over backups we already have?
Yes. We review what you run, keep what is sound, fix what is not, and add the test restores and the runbook that are usually missing.
Explore ALCO
- The client area
Everything ALCO does for you, in one place.
Requests, your team, invoices, documents, shared credentials and sign-in security. One sign-in, any device. Take the tour.
Tour myALCO - New · Our work
See the sites we have built.
A newspaper rebuilt headless, a parts storefront, two Boise nonprofits, a crochet brand and our own site. Every screenshot is the full page, scrolling live.
Browse our work
Clients we’ve worked with
We’ve worked with businesses, nonprofits and community organizations on managed hosting, website development and everyday IT support. These are some of the current and past clients we’ve supported, each with different systems, priorities and people. Explore their stories to see what working with ALCO looks like.
Make recovery a business decision before there is an outage
Backups exist, but recovery has not been tested
Confirm what can be restored, from which point and by whom. A completed backup job alone does not show that the business application will work.
The business cannot agree what must come back first
List the systems that support essential work and the recovery priorities before choosing retention or infrastructure.
What to bring to the conversation
Scope and cost depend on protected workloads, data volume, retention, backup locations, restore tests and support responsibilities. Existing providers and application owners may need to participate.
An illustrative engagement
An illustrative engagement could inventory an application and its database, agree recovery priorities and test a restore in an isolated environment. Recovery targets and the test scope must be written down first.
What affects the cost?
The systems and locations included, technical complexity, current condition, access, migration work and continuing support responsibilities all affect scope. We confirm the work and price in a written proposal.
One-time project or ongoing support?
A project defines a particular outcome and handover. Ongoing support defines continuing coverage. We can discuss either, including working alongside an existing IT employee or provider.
Keep the handover clear
Identify owners, authorized access, current contracts, documentation and acceptance checks before changes begin. An introductory conversation helps define the work; it is not a completed assessment.
Provider handover checklistExisting signed agreements control their scope and commitments. ALCO’s published standard terms do not silently replace them. Read the standard service terms, including client-owned credentials, data and transition responsibilities.
Before you choose a service.
Is backup the same as business continuity?
Backup supplies recoverable data. Continuity also covers people, equipment, connectivity, applications and the steps needed to resume work.
Can you guarantee a recovery time from a sales conversation?
A useful recovery target needs an agreed architecture, dependencies and a representative test. The contract should state the actual commitment.
How should we test without putting live data at risk?
Agree an isolated test destination, authorized access and acceptance checks. Do not overwrite production data as a routine test.
Will changing providers disrupt our work?
A transition needs an inventory, approved access, a cutover window, acceptance checks and a fallback plan. We discuss likely interruption and dependencies before agreeing the work; no migration is assumed to be disruption-free.
What if we still have an agreement with another provider?
Check its notice dates, ownership provisions and handover obligations with the appropriate decision-maker. ALCO can help identify technical dependencies, but a new enquiry does not cancel your agreement or authorize removing the current provider.
How do we avoid losing access when switching?
Inventory the domain, email, hosting, backups, licenses and their authorized owners before the handover. Transfer documentation and approved access securely, check critical workflows and obtain approval before removing old accounts or canceling dependent services.
Can remote support work for our business?
We review the systems, users and access needed before agreeing coverage. Many tasks can be handled remotely; hardware or site-specific work may need a scheduled visit. Our headquarters and office are in Caldwell, with technicians serving Idaho and scheduled on-site work within agreed scope.















































































































































































