Trois-Rivières, serving all of Quebec 450 231-3836 info@oktosolutions.ca
FR

Saint-Hyacinthe

IT services in Saint-Hyacinthe for businesses that cannot stop

When production, orders or payroll sit on a server, what matters is how fast you are running again. OKTO Solutions manages your systems remotely from Trois-Rivières, about 113 km away, and puts the effort where it gets you back on your feet: copies that are checked, a plan on paper, and restores that have really been done.

Backup plan shown on a screen to the manager of a small business

For a Saint-Hyacinthe SMB, OKTO Solutions provides managed IT remotely from Trois-Rivières, about 113 km away, with business continuity first: daily backups, an off-site copy, a written recovery plan and a full restore test twice a year from the Standard plan up. On-site visits are scheduled.

Who looks after business continuity for a Saint-Hyacinthe SMB?

OKTO Solutions offers managed IT to small and mid-sized businesses in Saint-Hyacinthe with one clear priority: getting the company running again quickly after an outage, a ransomware attack or a human mistake. The office is in Trois-Rivières, about 113 km away, and the service is remote first. Servers, workstations and Microsoft 365 are backed up every day, one copy is kept off site, and the jobs are monitored every day instead of being taken on faith. A written recovery plan states who does what and in which order systems come back. From the Standard plan up, a full restore is carried out twice a year in an isolated environment and timed. Acceptable data loss and tolerable downtime are set with management, one system at a time. OKTO has no office and no technician stationed in Saint-Hyacinthe, so visits are scheduled when hardware requires them.

Where it starts

How many hours can your business run without its systems?

Ask around the table and you will hear three answers. Accounting says two days. Shipping says one hour. The person taking orders says she has no idea, and she is often the one who is right. Until that number is written down, nobody can tell whether your backups are good enough.

So that is the first job. For each system, two decisions: how much work you are willing to redo, and how long you are willing to wait. A company that prepares deliveries every morning will not answer like a service office that can get through a day on the phone and on paper. The answers then go into a recovery plan covering restart order, owners, numbers to call and the decisions that belong to management.

The recovery plan as it is read on the day it matters, restart order first.

  • Daily backups of servers, workstations and Microsoft 365
  • One copy off site, encrypted
  • Jobs checked every day
  • A recovery plan in writing

Recovery objectives

Two numbers to settle before anyone talks about hardware

One measures lost work, the other measures time down. Each plan starts from a target, which is then adjusted with you for every system.

PlanMaximum data loss targetedReturn to service targetedRestore test
Base24 hours1 business dayNot included
Standard24 hours8 business hoursTwice a year
Complet4 hours on critical systems4 hoursTwice a year

These figures are targets written into the contract, not a guarantee, except in the Complet plan where they are contractual. They describe how long a system takes to come back, not travel time to Saint-Hyacinthe. Each level is laid out on our Base, Standard and Complet plans.

The proof

How do you know your backups will really restore?

A report that says “success” proves one thing: the job finished. To find out whether the business can restart, you have to restore something. Here is how a test runs.

  1. Pick what would hurt most. The file server, the accounting database or a whole mailbox. Never a small file chosen because it is quick.
  2. Restore away from production. The test runs in an isolated environment.
  3. Open the content. The database mounts, the application starts, the files open without errors.
  4. Compare real time with the target. If the restore took six hours against a four-hour objective, that gap gets fixed now.
  5. Update the plan. A forgotten dependency, an encryption key nobody wrote down, a contact who has changed: all of it goes into the next revision.
What a first test tends to turn up. Jobs that have been green for ages while protecting a drive that no longer exists, a seven-day retention set by a provider long gone, a failure email landing in a mailbox nobody opens. None of it shows until someone tries to restore.

Plainly

What can be done from 113 km away when a server goes down?

Nearly everything that concerns data. The copies do not sit in your server room. They are off site, encrypted, and protected against deletion so ransomware cannot reach them. A restore is therefore started from our screens, back to the original machine if it is healthy or to another location if it is not.

Hardware is the exception. A failed disk or a burnt-out switch needs hands on site, and we have nobody in Saint-Hyacinthe. When that happens we say so on the first call and arrange the trip. No arrival time is published, because we have not measured one. That is one more reason for the plan to spell out how the business keeps going in the meantime: which system restarts elsewhere, and who makes the call.

A restore launched from the console: the restore point, the machine booting, the time measured.

The ground

Saint-Hyacinthe, a city built around agri-food

Statistics Canada counted 57,239 residents in Saint-Hyacinthe in the 2021 census. The city belongs to the Maskoutains regional county municipality, in Montérégie.

57,239residents, 2021 census
113 kmor so between Saint-Hyacinthe and our office
Twicea year, a full restore, from the Standard plan up

It is nicknamed the agri-food technopolis and is home to the only faculty of veterinary medicine in Quebec. For IT, that kind of activity has a plain consequence: many businesses here handle products that will not wait. An order to get out, traceability records to keep, payroll due on Thursday. When the system behind those tasks stops, the cost is counted in hours, which is why this page talks about recovery before it talks about workstations.

The rest of the service is the same as anywhere else: user support, patching, monitoring, Microsoft 365 and managed cybersecurity, in English and in French.

Around Saint-Hyacinthe

Which neighbouring areas do we also cover?

A local company sometimes has a warehouse, a major customer or a second address further west in Montérégie. One recovery plan can cover every site.

Every territory is listed on the service areas page. To describe your systems and what an outage costs you, use the contact page.

Questions and answers

Your questions about our services in Saint-Hyacinthe

Do you have an office or a technician in Saint-Hyacinthe?
No. We work out of Trois-Rivières, about 113 km away by road, and nobody is stationed in the Saint-Hyacinthe area. Backup monitoring, patching and user support all run through our remote management tools. A visit is booked when the job calls for one, such as installing a server or a backup appliance.
Can a server in Saint-Hyacinthe be restored without anyone travelling?
Usually, yes. The copies live off site and a restore can be started remotely, either back to the original server or into an isolated environment. Travel becomes necessary when the hardware itself has failed: a dead disk, a server that will not power on, a network device to replace. We tell you so on the first call.
How often are restores actually tested?
Twice a year, starting with the Standard plan. A full set is restored in an isolated environment, someone checks that the application really opens, the run is timed, and you receive the result in writing. The scenario changes from one test to the next: file server, accounting database, a complete mailbox.
Our plant runs evenings and weekends. Who picks up?
Regular support is open on weekdays from 8 a.m. to 5 p.m. After hours, a 24/7 emergency line takes the outages that bring the business to a stop. The Complet plan includes it, and Base or Standard clients can take it as an option. If an evening shift depends on a system, sort this out before you sign.
Our files are in Microsoft 365. Is a backup still needed?
Yes. Synchronization copies mistakes too: a file deleted or encrypted in one place is gone everywhere within minutes. Microsoft 365 data is not protected against that kind of loss by default, so it goes into the daily backup alongside servers and workstations.
Who sets the recovery objectives, you or us?
You do. How much data you can afford to lose and how long you can stay down are business decisions, not technical settings. We ask the questions one system at a time and explain what each answer costs. Management decides, and we build the backup to match.

Let us talk about keeping your Saint-Hyacinthe business running

Tell us which systems you cannot lose and when a backup was last restored. We will tell you where you stand, straight.

Reviewed by , president of OKTO Solutions · updated