Your business depends on technology every day. But what happens when that technology suddenly stops working?
Imagine arriving at work on a Monday morning to discover that your company's servers are down. Employees can't access important files, customers can't reach your team, and critical business applications are completely unavailable.
Whether the cause is a cyberattack, hardware failure, power outage, or natural disaster, the result is the same: your business is losing valuable time, productivity, and money.
For small and medium-sized businesses (SMBs), even a few hours of downtime can create serious financial and operational challenges.
That's where Business Continuity and Disaster Recovery (BCDR) comes in.
What Is BCDR?
Business Continuity and Disaster Recovery (BCDR) is a combination of technology, processes, and planning designed to keep your business operational during unexpected disruptions and restore critical systems as quickly as possible.
Although the terms are often used together, they serve two different purposes.
Business Continuity: Keeping Your Business Running
Business continuity focuses on maintaining essential operations when something goes wrong. This includes ensuring employees can continue working, customers can still receive support, and critical business functions remain accessible.
Disaster Recovery: Getting Your Systems Back Online
Disaster recovery focuses on restoring your IT infrastructure, applications, and data following an outage or cyberattack. This includes recovering servers, restoring files, and bringing business-critical applications back online.
Think of it this way: Business continuity keeps your business moving, while disaster recovery gets everything back to normal.
Together, they create a safety net that helps protect your organization from unexpected IT disasters.
Why Is BCDR So Important for Small Businesses?
Many small businesses assume that major IT disasters only happen to large corporations. Unfortunately, smaller organizations are just as vulnerable to cyberattacks, hardware failures, and accidental data loss.
The difference? Smaller businesses often have fewer resources available to recover from these incidents.
Here are some of the biggest reasons BCDR should be a priority for every SMB.
1. Downtime Is More Expensive Than You Think
When your systems go offline, the financial impact extends far beyond the cost of repairing the problem.
Consider everything your business relies on technology to accomplish:
Employees accessing files and completing daily tasks
Processing invoices, payments, and payroll
Communicating with customers and vendors
Managing projects and meeting deadlines
Accessing critical business applications
When these systems become unavailable, productivity slows or stops entirely.
For example, imagine a construction company that loses access to its project management software, accounting platform, and shared documents for an entire day.
Project managers can't access schedules, accounting teams can't process invoices, and employees are left waiting for systems to come back online.
Even if the company eventually restores its data, the lost productivity and missed opportunities cannot always be recovered.
BCDR helps minimize downtime, reducing the financial impact of unexpected disruptions.
2. Cyberattacks Can Bring Your Business to a Standstill
Ransomware remains one of the most serious cybersecurity threats facing businesses today.
During a ransomware attack, cybercriminals can encrypt critical business data and demand payment in exchange for restoring access.
In some cases, attackers specifically target backup systems to make recovery even more difficult.
Without a reliable disaster recovery solution, businesses may face days or weeks of downtime, expensive recovery efforts, and potentially permanent data loss.
A properly designed BCDR solution helps protect against these scenarios by maintaining recoverable copies of critical systems and data.
If ransomware compromises your primary environment, your IT team may be able to restore clean backups or transition operations to a protected recovery environment.
BCDR doesn't prevent every cyberattack, but it can dramatically reduce the damage when one occurs.
3. Traditional Backups Aren't Always Enough
One of the biggest misconceptions among small businesses is that having a backup means having a disaster recovery plan.
Unfortunately, that's not necessarily true.
Traditional backups are designed to preserve copies of your data. While essential, they don't always provide a fast way to restore the applications and systems your business needs to operate.
For example, imagine your company's main server fails.
With traditional backups, your IT team may need to obtain replacement hardware, reinstall software, restore files, and reconfigure applications before employees can resume working.
Depending on the situation, this process could take hours or even days.
A comprehensive BCDR solution goes further.
Depending on the technology deployed, BCDR can provide capabilities such as:
Automated backups: Regularly protecting critical systems and business data.
Rapid system recovery: Restoring servers and applications without rebuilding everything from scratch.
Cloud failover: Temporarily running critical systems in a cloud environment if primary infrastructure becomes unavailable.
Off-site data protection: Maintaining recoverable data outside your primary business location.
Recovery testing: Verifying that backups and recovery procedures actually work.
The key difference is simple:
Backups protect your data. BCDR protects your ability to keep doing business.
4. Hardware Failures and Human Errors Happen Every Day
Not every IT disaster involves hackers or extreme weather.
Sometimes, the biggest disruptions come from everyday problems.
A server's hard drive fails. An employee accidentally deletes an important folder. A software update causes an application to stop working. A power outage damages critical equipment.
These incidents can happen to any business, regardless of size or industry.
Without a recovery strategy, even a relatively minor technical issue can turn into a major operational problem.
BCDR helps businesses prepare for these common disruptions by establishing a reliable process for restoring systems and recovering lost information.
Rather than scrambling to determine what to do after something breaks, your business has a recovery plan already in place.
5. BCDR Supports Cybersecurity and Compliance
Cybersecurity isn't just about preventing threats. It's also about ensuring your organization can recover when preventative measures fail.
Firewalls, antivirus software, endpoint protection, and employee security training all play important roles in defending your business.
However, no security solution can guarantee complete protection.
BCDR provides an additional layer of resilience by helping businesses recover from incidents that bypass their existing defenses.
For organizations with regulatory or contractual obligations, documented backup and disaster recovery procedures may also be necessary to meet compliance requirements.
Additionally, many cyber insurance providers evaluate backup practices, disaster recovery capabilities, and security controls when assessing coverage.
A documented and regularly tested BCDR strategy can help demonstrate that your organization takes cybersecurity and operational resilience seriously.
How Quickly Could Your Business Recover?
Not every business has the same recovery requirements.
A small office might be able to tolerate several hours without access to certain applications. A construction company managing multiple active job sites, however, may need critical project and financial systems restored much sooner.
Two important measurements help businesses determine their recovery needs.
Recovery Time Objective (RTO)
How long can your business afford to be offline?
For example, an RTO of four hours means your recovery strategy should be designed to restore a critical system within four hours of a disruption.
Recovery Point Objective (RPO)
How much data can your business afford to lose?
For example, if your systems are backed up once every 24 hours, a failure just before the next backup could result in nearly a full day's worth of lost information.
An RPO of one hour means your backup strategy should be designed to limit data loss to no more than one hour.
Understanding these two measurements allows businesses to build a recovery strategy around their actual operational needs rather than relying on a one-size-fits-all solution.
Don't Wait Until Disaster Strikes
The worst time to discover that your backups aren't working is when you desperately need them.
Unfortunately, many businesses never test their recovery procedures until an actual emergency occurs.
A strong BCDR strategy should include regular backup monitoring, recovery testing, documented procedures, and periodic reviews as your technology environment changes.
Businesses should also identify which applications and systems are most critical to their operations so recovery efforts can prioritize what matters most.
The goal isn't simply to recover your data. It's to make sure your business can recover with it.
Protect Your Business With myCREcloud
At myCREcloud, we understand how important reliable technology is to your daily operations.
Whether your business relies on cloud-hosted applications, on-premises servers, or a combination of both, having the right backup and disaster recovery strategy is essential to protecting your operations.
Our Managed IT Services team helps businesses evaluate their existing IT environments, identify potential vulnerabilities, and implement backup and recovery solutions aligned with their operational needs.
From protecting critical business data to planning for unexpected outages, we help organizations take a proactive approach to business continuity.
Because when disaster strikes, having a recovery plan shouldn't be optional.
Is Your Business Prepared for an IT Disaster?
If your primary server failed tomorrow, how long would it take to get your business running again?
If you're unsure of the answer, it may be time to review your backup and disaster recovery strategy.
Contact myCREcloud today to learn how our Managed IT Services can help protect your business, minimize downtime, and prepare your organization for the unexpected.
If your company bought a year of Windows 10 security updates last fall, that year just ran out. Here's what it means for the laptops in your job trailers and the PCs running Sage back at the office.
A year ago, Microsoft ended support for Windows 10. Most construction companies we talk to didn't replace every machine. Instead, many paid for Microsoft's Extended Security Updates (ESU) to keep older PCs patched while they figured out a plan.
That bridge just hit its first toll booth. Year one of business ESU coverage ended with the October 13, 2026 Patch Tuesday updates. Year two doesn't renew on its own, and it costs twice as much.
If you still have Windows 10 machines on the network, now is the time to decide what to do with each one.
What changed this week
Business ESU is sold one year at a time, and the price doubles each year. Year one covered security updates through October 13, 2026. A PC that isn't licensed for year two gets no more Windows security patches starting this month.
ESU year
Coverage ends
Price per PC
Year 1
October 13, 2026
$61
Year 2
October 12, 2027
$122
Year 3 (final)
October 10, 2028
$244
A few details catch people off guard:
Nothing renews automatically. Year two is a new purchase, and the new key has to be activated on every machine.
The years are cumulative. If you skipped year one, you have to pay for it before you can buy year two.
It's patches only. ESU doesn't include new features, technical support, or fixes for problems that aren't security-related.
Windows 10 keeps running. Nothing shuts off. The PC just stops getting fixes, and every new vulnerability stays open.
Run the math across a fleet. Ten Windows 10 laptops cost $1,220 for year two alone, and $3,660 to cover years two and three together. That's real money toward replacing the machines instead.
Why construction firms have more Windows 10 than they think
In most offices, Windows 10 is gone from the front desk. It's hiding in the machines nobody thinks of as "the computers." On a typical construction network, we usually find it on:
Job trailer laptops that get passed between supers and rarely come back to the office for updates
The plotter or large-format printer PC, kept on Windows 10 because the driver works and nobody wants to touch it
Estimating and takeoff workstations running older software that was never tested on Windows 11
Time clock and badge kiosks at the yard or shop
The accounting PC that still runs Sage locally, or the old server it talks to
These are exactly the wrong machines to leave unpatched. Field laptops connect over hotspots and job-site Wi-Fi you don't control. Many of them log into your accounting system, your project files, and email. An attacker only needs one weak device to get a foothold, and from there your payroll, vendor payments and bid data are on the same network.
There's a business side too. Many cyber insurance applications now ask whether you run unsupported operating systems. And new plotters and peripherals are being released with Windows 11 drivers first, so the "don't touch it" PC gets harder to keep working every month.
A practical plan for the next 90 days
You don't need to replace everything this week. You do need to know what you have and make a decision for each machine.
Take inventory. List every Windows device, including the ones in trailers, shops and yards. Note the Windows version, age, who uses it, and what software it runs.
Sort each machine into one of three buckets.
Upgrade: hardware that meets Windows 11 requirements. The upgrade itself is free.
Replace: machines too old for Windows 11. Paying ESU on these just delays a purchase you'll make anyway.
Bridge: the few machines with a real reason to wait, such as specialty software. Buy ESU year two for these only, and put a retirement date on each one.
Check your Windows 11 machines, too. Windows 11 version 24H2 (Home and Pro) also reached end of support on October 13, 2026. Make sure those PCs have moved to a newer version.
Plan around year-end. Upgrade field laptops now. Leave the accounting PC and anything tied to payroll alone until after your year-end close, then schedule it for January.
Get Sage off the desk. If Sage still lives on a local PC or an aging server, that machine becomes a single point of failure every time it needs an update. Hosting Sage in the cloud takes it off your hardware entirely, and Windows 10 virtual machines in Microsoft's cloud services (like Windows 365 and Azure Virtual Desktop) receive ESU at no extra cost.
Not sure what's still running Windows 10?
We help construction companies find the forgotten machines, sort out what to upgrade, replace or bridge, and time the work so it never lands on top of year-end close. If Sage is part of the picture, we can show you what it looks like hosted in the cloud instead of on a PC that needs babysitting.
If you priced a new server for your office this year, you already know: the same box costs far more than it did in 2025. A memory-heavy server that cost $10,000 in January 2025 would run roughly $20,000 today, according to an industry price index tracking a standard two-socket build.
For construction companies, that timing hurts. Many firms still run Sage 300 CRE or Sage 100 Contractor on a server in a back closet, and plenty of those servers are due for replacement. Laptops for estimators and project managers are going up too.
Here is what is driving the increase, how long it is likely to last, and what you can do about it without blowing up your IT budget.
What's driving the increase: AI ate the memory supply
The short answer is memory. Samsung, SK hynix and Micron make nearly all of the world's DRAM, and all three have shifted factory capacity toward high-margin memory for AI data centers. That left less for the ordinary servers, PCs and laptops everyone else buys.
The result has been the steepest run-up in memory prices on record:
Late 2025: server memory contract prices rose about 45–50% in a single quarter.
Early 2026: conventional DRAM jumped another 90–95% in one quarter, per market analyst TrendForce.
Spring 2026: another 58–63% on DRAM, with SSD flash storage up 70–75%.
Summer 2026: TrendForce forecast a further 13–18% rise in server memory for the third quarter.
Hardware makers passed those costs straight through. Dell raised list prices about 17% across its business lineup, including OptiPlex desktops, Latitude laptops and PowerEdge servers, effective March 30, 2026. Memory-heavy configurations went up as much as 30%. Gartner expects average PC prices to rise about 17% this year.
Memory used to be a minor line on a server quote. In a well-equipped server, it is now more than half the cost.
Why construction firms feel it more than most
Big cloud providers negotiated multi-year supply contracts that cap what they pay. TrendForce says the price increases are now landing hardest on buyers without those agreements. That means small and mid-size businesses buying one or two servers at a time.
Construction companies tend to fit that profile exactly:
On-premises accounting servers. Sage 300 CRE and its SQL database like plenty of RAM and fast storage, the two components that rose fastest.
Refresh cycles that can't slip forever. A five- or six-year-old server running your job costing and payroll is a real risk. Deferring the upgrade trades a cost problem for a downtime problem.
Field and office laptops. Estimators, PMs and superintendents need capable machines, and PC prices are rising alongside servers.
Tight margins. An unplanned $10,000 jump in a hardware line item is money that comes straight out of overhead.
Lead times have stretched too. Ordering a server today does not guarantee today's price at delivery, which makes budgeting harder still.
The cloud alternative: stop buying servers
The most direct way to sidestep a server price spike is to not buy a server. When your Sage applications run in a hosted environment, the hardware is the provider's problem. You pay a predictable monthly fee instead of a large, unpredictable upfront purchase.
To be clear, cloud providers pay more for hardware now too, and nobody is fully immune. But the economics are different. A hosting provider spreads each server across many customers, plans capacity continuously and doesn't need to buy a whole new box when your company adds three users.
With myCREcloud, your Sage 300 CRE, Sage 100 Contractor, Sage Estimating and Sage Paperless run on our infrastructure, not in your closet. That includes:
Access from anywhere, on any device, including from a web browser
SOC 2 certified infrastructure with 256-bit encryption
Multi-factor authentication and automated daily backups
Migration handled by our team, so moving off your old server isn't a project you manage alone
There is a side benefit to hosting your heavy applications: your staff's laptops no longer need to be as powerful. When the processing happens on the hosted server, a mid-range machine does the job, which matters when every extra gigabyte of RAM costs more.
Five ways to manage hardware costs right now
Whether or not you move to the cloud, these steps help:
Don't wait for prices to fall. Analysts expect server memory prices to keep rising through 2027, with meaningful relief unlikely before late 2027. Waiting usually means paying more.
Right-size before you buy. Memory is now the most expensive part of a server. Buying only the RAM you'll actually use is the biggest single lever on a quote.
Extend what still works. A well-maintained server or laptop that meets your needs can often run another year or two. Just confirm it still gets security updates.
Move heavy workloads off local machines. Hosting Sage and other demanding applications lets you buy lighter, cheaper endpoints for your team.
Budget for volatility. Build a cushion into next year's IT budget and get quotes in writing with clear delivery terms, since vendors are declining to lock prices.
The bottom line
Hardware costs are not coming back to 2024 levels anytime soon. For construction companies with an aging Sage server, the real question is whether to spend a much bigger check on a new one or move those applications somewhere the hardware is someone else's job.
If your server is due for replacement in the next 12 months, now is a good time to compare the numbers. Request a quoteand our team will walk you through what hosting your Sage environment would cost, side by side with a new on-prem server.
If you had to guess the answer, would you feel confident saying yes?
For a lot of construction firms, the honest answer is "it depends." It depends on whose laptop has the VPN client installed correctly. It depends on whether IT set up that laptop before the person left the office. It depends on whether the hotel Wi-Fi will even let the VPN connect. It depends on a dozen small things that have nothing to do with getting the job done, and everything to do with getting into the software that runs the job.
Construction doesn't happen at a desk. Your team is scattered across jobsites, home offices, client meetings, and airport terminals, and every one of them eventually needs the same thing: their Sage data. If getting there requires a VPN, a specific device, or a call to IT, you don't have remote access. You have remote friction.
The VPN Problem
VPNs were built for a world where "remote" meant occasional. They weren't designed for a workforce that's remote by default. In practice, that mismatch shows up as:
Setup headaches. Every new laptop, tablet, or replacement device needs to be configured before someone can use it in the field.
Fragile connections. Jobsite Wi-Fi, cellular hotspots, and hotel networks don't always play nice with VPN tunnels.
Slow performance. Tunneling a full desktop connection through spotty bandwidth makes Sage feel sluggish exactly when your team needs it to be fast.
A single point of failure. If the VPN server has an issue, nobody gets in. The PM, the controller, and the estimator are all locked out at once.
None of that is a Sage problem. It's an access problem.
What Remote Access Should Actually Look Like
The fix isn't asking your team to work around technology. It's removing the technology that gets in the way. That's the idea behind cloud-hosting Sage 100 Contractor, Sage 300 CRE, Sage Estimating, and Sage Paperless instead of running them on a VPN back to an office server.
Done right, remote access means:
Browser-based access, from anywhere. No app installs, no VPN client, no "let me remote into my office computer first." Your team opens Chrome, Safari, Firefox, or Edge and their Sage environment is right there, on a jobsite tablet, a home laptop, or an airport kiosk.
One central, always-on environment. Instead of syncing files between machines or hoping the office server stays up, everyone works from the same hosted environment. Updates and software changes happen in one place, for everyone, automatically.
Enterprise-grade security that doesn't depend on a VPN tunnel. SOC 2 certified data centers, 256-bit encryption, multi-factor authentication, and daily automated backups protect your data whether your team is logging in from the office or from 30,000 feet.
Support that actually knows Sage. Cloud hosting for construction software isn't generic IT — it's Sage-specific. That means US-based support that understands the difference between a printing issue in Sage 100 Contractor and a job-cost sync issue in Sage 300 CRE, not a generic help desk ticket queue.
So, Can They All Get In Right Now?
With the right setup, the answer stops being "it depends" and starts being "yes, obviously." The PM pulls up job costs from the jobsite. The controller runs payroll from the kitchen table. The estimator finalizes a bid between flights. Same data, same permissions, same Sage — no VPN, no waiting on IT, no excuses.
That's what myCREcloud builds for construction businesses: Sage 100 Contractor, Sage 300 CRE, Sage Estimating, and Sage Paperless, hosted in the cloud with 99.99% uptime, in-house US-based support, and browser-based access from anywhere. It's already how more than 500 construction businesses run Sage today.
It's the Monday of a payroll week. Your controller comes in early to process certified payroll for three prevailing wage jobs, opens Sage, and gets an error. The server in the back office won't boot. IT thinks it's the RAID controller. Parts are two days out.
Now the question that actually matters: how much work is gone, and how long until people can work again?
Most contractors have never answered those two questions precisely. They have "backups", a job someone set up years ago, a external drive that gets swapped on Fridays, a checkbox in a utility nobody has opened since. What they don't have is a recovery plan they've tested. Those are very different things, and the difference only shows up on the worst day of the year.
What's actually at risk
Construction accounting data is unusually painful to lose, because so much of it is unreproducible and time-sensitive at the same time.
Think about what lives in Sage 300 CRE, Sage 100 Contractor, your estimating databases, and Paperless:
Job cost history going back years, the only record of what things actually cost you, and the basis for every future estimate.
Work in progress and over/under billings that your bonding company and lender expect on a schedule.
AIA pay applications and lien waivers tied to hard contractual deadlines. A missed G702 can push a draw a full month.
Certified payroll and compliance records you're legally required to retain and produce on demand.
Subcontract records, change orders, and commitments: the documentation you'd need if a dispute ever went to arbitration.
Estimating databases and price lists representing years of accumulated cost knowledge and crew production rates.
Scanned invoices, contracts, and RFIs in Paperless, often the only copy left after the paper went in the shredder.
You can rebuild a workstation in an afternoon. You cannot rebuild eight years of job cost history.
Backup is not disaster recovery
These get used interchangeably, and it causes real damage. A simple way to keep them straight is to think in two numbers.
RPO : Recovery Point Objective. How much data can you afford to lose, measured in time? If your backup runs at 10 p.m. nightly and the server dies at 4 p.m., your RPO is 18 hours. That's a full day of AP entry, timecards, and job cost postings that someone has to re-key from paper, assuming the paper still exists.
RTO : Recovery Time Objective. How long until people are working again? This is where most plans quietly fall apart. Having the data on a drive is not recovery. You still need hardware, an operating system, the database engine, the correct Sage version and service pack, licensing, printer and third-party integrations, and user permissions. For a typical on-premise contractor, honest RTO after a total server loss is three to seven days.
Backup answers "do we still have the data." Disaster recovery answers "when can the team work again." You need both, and you need to know your numbers before you're asked.
Why the server-in-the-closet plan usually fails
When contractors do discover their backups didn't work, it's almost always one of these five reasons.
1. Nobody ever tested a restore. A backup job that reports "success" is only telling you it finished writing a file. Whether that file can be restored into a functioning system is a completely separate question, and the only way to know is to actually do it.
2. The backup was on the same network. This is the ransomware problem. Modern attacks specifically hunt for and encrypt connected backup targets and mapped drives before they trigger. If your backup drive is plugged into the server or reachable over the LAN, assume it goes down with everything else.
3. The database was live when the copy ran. This one is specific to your software and it's the most common technical failure we see. Copying database files while the database engine is running frequently produces a corrupt, unrestorable backup. Sage 100 Contractor (v20 and later) runs on Microsoft SQL Server. Sage Estimating uses SQL Server as well. Sage 300 CRE runs on Actian Zen/Pervasive PSQL. Each requires a proper application- or engine-aware backup, a SQL backup job, or a stop of the services during the copy window. File-level copies of open database files are not backups.
4. Paperless documents and the Paperless database drifted apart. Paperless keeps document images in one place and the index in a database. Back up one without the other, or back them up hours apart, and you can end up with documents you can't find or index entries pointing at nothing.
5. Retention was too short to matter. Corruption and quiet data problems often aren't discovered for weeks. If you keep seven days of backups and a bad payroll import happened three weeks ago, all seven copies contain the problem. You need enough depth to go back past the mistake.
What good actually looks like
The standard worth aiming for is often written as 3-2-1-1-0: three copies of your data, on two different types of media, with one copy offsite, one copy immutable, and zero errors on your last verified restore test.
The two additions to the classic 3-2-1 rule are the ones that matter most right now. Immutable means the backup cannot be altered or deleted for a set retention window — not by an attacker, not by ransomware, not by an administrator with stolen credentials. Zero errors on a verified restore means someone actually performed a test restore and confirmed the application opened and the data was intact. If that hasn't happened in the last twelve months, you don't have a recovery plan. You have a hope.
It's also worth noting that cyber insurance carriers have caught up here. Offsite immutable backups, MFA, and documented recovery testing increasingly show up as conditions of coverage rather than nice-to-haves and a claim can be denied over a control you attested to but didn't actually have in place.
How hosting changes the math
This is the part where the on-premise model struggles most, because a good backup and DR posture is expensive and labor-intensive to build for one office. Hosting spreads that infrastructure across many contractors.
When your Sage 300 CRE, Sage 100 Contractor, Estimating, and Paperless environments run in a hosted datacenter, several things change at once:
Backups are engine-aware and automatic. Databases are backed up correctly for their platform, on schedule, without anyone remembering to swap a drive.
Copies live offsite and geo-redundant by default. A fire, flood, or burst pipe at your office has zero effect on your data, because your data was never at your office.
RTO drops dramatically. There's no server to rebuild and no software to reinstall. Your team needs internet access and a device a laptop at home, a tablet in a jobsite trailer, a machine at a temporary office. People are working the same day, not the same week.
The office itself stops being a single point of failure. For a business where the accounting office may be nowhere near the work, that's a meaningful structural improvement.
Hosting doesn't remove your responsibility to understand the plan, it just means you're inheriting one that's professionally maintained instead of building one on nights and weekends.
Five questions to ask this week
Whether your systems are hosted or in the closet, get real answers to these:
What is our RPO? If we lose the system at 3 p.m. Thursday, what's the last moment of work we still have?
What is our RTO? Realistically, when is the accounting team fully productive again?
When did we last complete a test restore, and who watched the application open afterward?
How far back can we go? Thirty days? Ninety? Enough to get behind a problem discovered late?
Can our backups be deleted by someone with admin credentials? If yes, they are not protected from ransomware.
If any answer is "I'd have to check," that's worth an hour of somebody's time this week rather than a week of everyone's time later.
Want to know what your recovery picture actually looks like? myCREcloud hosts Sage 300 CRE, Sage 100 Contractor, Sage Estimating, and Paperless environments in secure datacenters with managed, application-aware backups and offsite redundancy built in. We're happy to walk through your current setup and tell you honestly where the gaps are. Contact us to schedule a conversation.
