Backup design
We plan backups for the computers, servers and online information included in your agreement, based on the work your business needs to keep doing.
Email and online files need their own review; read our Microsoft 365 backup guide.
Managed IT services
Business backup and disaster recovery on Long Island.
Plan how to recover the information and systems your business needs, then check that the plan is usable.
Free business resource
What needs to come back first?
Set business recovery priorities and keep a usable record of restore-test results, missing dependencies and next actions.
Know how recovery will work before you need it.
A message saying the backup finished does not tell you whether your business can use it. We identify the information and applications your staff need, check the agreed backups and test recovery. You can see what is protected and what needs attention.
Backup services for servers, computers and Microsoft 365.
For example, an office may keep most documents online while its accounting application still depends on a local server. Backing up staff folders would leave that dependency unresolved. We identify where the working information actually lives and include the application, access and recovery requirements in the proposed protection.
Monitoring and follow-up
Someone needs to investigate a failed or incomplete backup. Your agreement identifies who checks the results and follows up on problems.
Restore testing
We check whether backed-up files or systems can be recovered and used. You receive a record of what worked and anything still needed before normal work could resume.
Business continuity planning
We discuss which work must restart first, how long it can be interrupted, how much recent work could be lost and who will help get the business working again.
What else has to be ready for a recovery?
A usable backup is one dependency. Your business may also need somewhere to restore it, access to an application and people who can confirm that the recovered work is right. We discuss those requirements before relying on a recovery plan.
A working system to restore onto
A failed server can leave the office without the hardware needed to use its backup. We discuss whether recovery requires replacement equipment, an available cloud environment or another supported destination. The options depend on your setup and platform; a storage subscription alone does not supply a ready-to-use office.
Application and supplier availability
An accounting database or specialist application may need its vendor, licensing service or a compatible version before staff can use it again. We identify those dependencies with the business and relevant provider. That gives the owner a fuller view of the work beyond copying files back.
Access when the main accounts are unavailable
An incident affecting ordinary administrator access can also make recovery harder. We review the approved recovery arrangements, the people authorized to use them and how essential supplier information would be reached. Those details are handled securely; they should not depend on the affected computer being available.
A practical sequence for resuming work
Restoring everything at once is not always the useful first step. We discuss which activities must resume first and the staff or suppliers needed to check them. Our backup, recovery and continuity guide provides context; your own plan identifies the actual priorities and any interim working arrangements.
Which version of your work would you need back?
The most recent backup is not always the copy a business needs. A damaged file may go unnoticed for weeks, while a server failure may require the latest available transactions. We discuss those situations when choosing how often information is protected and how long recovery copies are kept.
The conversation starts with the working day: orders entered, appointments booked, documents revised and information held by different applications. Your staff can explain what would have to be recreated if that work were missing. We translate those needs into proposed protection and recovery expectations, with any limitations made clear.
Keeping more history and keeping more systems protected can affect storage and subscription costs. Retention should reflect the business requirement you and your advisers identify, rather than being chosen only because a product offers a convenient default.
Understand local copies, cloud recovery and storage charges.
Local and cloud backup arrangements have different dependencies. A nearby recovery copy can be useful for a large restore, but the plan also needs to consider an incident that affects the premises or the equipment holding that copy. Cloud recovery depends on access to the service, available connections and somewhere suitable to restore the information.
We explain the options supported by the proposed backup platform. Local recovery is not assumed to be available with every subscription, and having an offsite copy does not by itself provide a replacement server or restore an application. Those requirements belong in the recovery plan.
The quote should distinguish protected computers and servers, included storage, additional capacity and any separately scoped recovery work. Growing data, longer retention and newly protected applications can change the cost. We discuss the basis for those charges so an increase is understandable before it appears on the bill.
Keep backup coverage aligned with business changes.
A new server, a different accounting application or staff saving work in a new location can change what needs protection. During agreed reviews and changes, we check whether the backup scope still matches the business systems being used. Important exclusions should be visible rather than discovered during a restore.
The same applies when you replace an IT provider. We establish who controls the existing copies, which subscriptions continue and whether historical information remains recoverable. You can then make an informed decision about retaining the current service or moving to a different arrangement.
Who decides what gets restored?
Recovering information can involve a business decision as well as technical work. Restoring yesterday’s version of a shared folder could replace changes made this morning. An older accounting database may be usable, but someone needs to decide how the missing transactions will be checked and entered again.
Approve the recovery point
We explain the available recovery points, the affected work and any risk of replacing newer information before an authorized person approves the restore. Where the system supports it, recovering a separate copy can let your team check the contents before deciding what should replace the working version.
Confirm the business can use the result
The finish matters too. A file opening successfully is useful evidence, but the employee who uses it needs to confirm that the required information is there. For an application or server, we agree how the business will check that essential work can resume.
Before you get started
Questions about backup and business recovery.
Have a question about your own setup? Talk with Charles.
Can you check whether our current backups are useful?
Yes. We review which systems and information are included, how far back recovery is available and what happened when someone last tried a restore. The business question is whether you could use the recovered work, not simply whether a job completed. We identify missing evidence or coverage and discuss an appropriate test before claiming the arrangement meets your needs.
Can you guarantee a recovery time?
A recovery target needs to be based on your actual systems and the work needed to resume business. Restoring files may also require a working server, application, internet connection or another vendor. We review those dependencies and the available backups before agreeing any commitment. The backup and disaster recovery guide explains how a recovery-time target differs from the amount of work you might lose.
Can Microsoft 365 data be included?
Yes. We discuss the email and files your business needs, the people who use them and the circumstances in which you would need them restored. That establishes the workloads, accounts and recovery history to include. Microsoft 365 backup can be part of the agreed arrangement; it should be distinguished from server or workstation backup so an important location is not assumed to be covered.
Do we need backups for servers, employee computers and cloud files?
Start with where the business keeps the information it needs. A server backup may cover shared applications while important work remains on a laptop or in Microsoft 365. We review those locations with you, identify what is already protected and propose coverage for the gaps. The scope explains which systems, data and retention are included.
Could we recover from ransomware using our existing backups?
That depends on whether the incident could also reach the backup copies, what those copies contain and whether they can be restored to a usable system. We review the protections and test agreed recovery scenarios. A successful backup notification alone does not establish that your business could resume work after an attack.