Is your backup solution running on a Raspberry Pi?
We’ve all tinkered with DIY tech—but when it comes to business data, even a Raspberry Pi has its limits. Let’s explore business backup and disaster recovery plan options for Enterprise Resource Planning (ERP) workloads.
DIY Backups Can Be Fun—But Are They Enough?
Many businesses struggle to figure out how to properly back up their data. We all know that backup is important to prevent data being lost. Many things can happen such as ransomware attacks, natural disasters, data breaches, or even internal attacks on your backup system. With this in mind, it is of utmost importance to ensure your company is making proper backups. A well-built business backup and disaster recovery plan protects data, ensures uptime, and gives your team the confidence to handle the unexpected.
You never know when disaster might strike, whether it be something like flooding, an earthquake, or even something as simple as a hard drive failing in your NAS or an employee accidentally deleting a file. These things can greatly affect the productivity of your team, and cause your business to lose money, data, and time.
Common threats that make a business backup and disaster recovery plan essential:
Ransomware and cyberattacks targeting small businesses
Natural disasters like floods, tornadoes, and fires
Employee error, accidental deletions, or insider threats
Hardware failure, aging on-premise servers, or NAS crashes
Data breaches requiring fast compliance-driven restoration
Why Professional Backup and Disaster Recovery Solutions Matter
When it comes to data backup and disaster recovery, small businesses and enterprises alike need robust solutions that go beyond basic file storage. Professional backup and disaster recovery services, which are built into business application cloud hosting solutions, ensure business continuity by providing automated backups, version control, and rapid data recovery capabilities. Without a comprehensive backup strategy, companies risk losing critical business data, customer information, and years of operational history that can never be recovered.
Enterprise-Grade Data Protection Features
In light of this, as a business owner, you must ask yourself the important question, is your backup solution running on a Raspberry Pi? Is your team making trips to the bank on a weekly basis to put a LTO tape backup of your data into a safe deposit box that is intended for rare coins and jewelry? Or, even worse, is all of your data stored in a cabinet in the basement of your office, making all of your data stored on-site?
The True Chaos (and Cost) of Data Loss for Businesses
The old saying goes “don’t put all your eggs in one basket” and this absolutely applies to backups. If all your data is stored on one site, what will you do if your building gets swept away by a tornado or broken into in the night? Will you call Sherlock Holmes and try to find your Linear Tape-Open (LTO) backup tapes or hard disk drives?
LTO Tape vs. Modern Cloud Solutions
While simple solutions like a Raspberry Pi can be great for ensuring the coffee pot in the break room is never empty, your backups are the backbone of consistent service for customers. Your business deserves better than a solution designed for hobbyists, or even something like a NAS (Network Attached Backup), which only really ensures a secure backup if it is located off-site.
Thankfully, EstesGroup is here to help, with our dedicated team which will help you analyze your current business backup and disaster recovery solution, and help you improve your business continuity plan. Our on-premise and cloud-based solution suites make disaster recovery of your important data fast, secure and available 24/7/365.
Our team works hard to meet your advanced cybersecurity and compliance needs, and will help you ensure everything from your customer data to your email accounts are backed up to allow for recovery in case of a disaster.
Integrate, Automate, Report — And Prepare for Disaster
Modern backup solutions should include features like cloud storage integration, automated scheduling, encryption, and compliance reporting. Enterprise-grade backup systems provide redundancy across multiple geographic locations, ensuring your data remains accessible even during widespread outages or natural disasters.
Automated Business: Backup and Disaster Recovery Plan Scheduling and Monitoring
The best backup and disaster recovery services offer both on-premises and cloud-based options, giving businesses the flexibility to choose the right mix of speed, security, and cost-effectiveness for their specific needs.
What to look for in a business backup and disaster recovery solution:
Automated backups with customizable scheduling
Cloud-based redundancy across secure, geo-distributed locations
End-to-end encryption and ransomware protection
24/7/365 support with SLA-driven recovery
Compliance-ready reporting for audits and regulations
Scalability to grow with your business needs
Business owners often underestimate the true cost of data loss until it’s too late. Studies show that 60% of small businesses that lose their data shut down within six months of a disaster, and few IT departments leverage expert network and security assessments.
3-2-1 Backup Rule
Professional IT services and managed backup solutions can help prevent this scenario by implementing industry best practices for data protection, including the 3-2-1 backup rule: three copies of your data, stored on two different types of media, with one copy kept off-site.
Don’t let your business become another statistic – invest in professional backup services that scale with your growth and protect your most valuable digital assets.
So, what are you waiting for? Reach out to our team today at [email protected] or call us at (888) 300-2340 (if you prefer the old-fashioned telephone). Let us help you ensure your business is prepared for anything.
ERP Platforms That Require a Strong Backup and Recovery Plan
EstesGroup supports a wide range of ERP systems for manufacturers, distributors, and service-based businesses. Our team provides consulting, optimization, and secure cloud hosting for leading platforms, including:
Infor SX.e and Infor SyteLine (CloudSuite Industrial)
Whether you’re running a legacy ERP system or planning a cloud migration, EstesGroup can help you build a disaster recovery plan that aligns with your technology, operations, and compliance needs.
Wondering if your backup strategy is really enough? Whether you’re running Epicor, Prophet 21, Sage, SYSPRO, Infor, or another ERP system, your business depends on consistent uptime and data protection.
Below are some of the most common questions we hear about backup and disaster recovery (BDR) for ERP users—along with expert answers to help you protect your systems, your data, and your future.
What is a business backup and disaster recovery plan?
A business backup and disaster recovery plan is a set of strategies, tools, and processes that protect your company’s data and systems. It ensures you can recover quickly from threats like ransomware, hardware failure, or natural disasters—minimizing downtime and loss.
Is a DIY (like Raspberry Pi) backup good enough for business?
Not really. A Raspberry Pi can handle basic backups for personal use or lab environments, but it lacks the redundancy, encryption, automation, and compliance features needed for enterprise-grade disaster recovery. Think of your DIY business backup and disaster recovery plan as the Raspberry Pi of the current digital landscape.
What’s the difference between a NAS and cloud backup?
A NAS (Network Attached Storage) is a local device for storing files, while cloud backups replicate your data to secure, remote servers. Private and hybrid cloud solutions provide better scalability, offsite redundancy, and disaster resilience.
How does the 3-2-1 backup rule work?
The 3-2-1 rule means keeping three copies of your data, on two different types of storage, with one copy stored off-site. It’s a proven strategy for avoiding data loss during unexpected events.
How can EstesGroup help with disaster recovery?
EstesGroup offers fully managed backup and disaster recovery solutions tailored to small and mid-sized businesses. From secure cloud hosting to compliance reporting and rapid restore capabilities, our team helps you prepare for anything. Schedule a free IT assessment with a vCIO today.
Stay ahead of system failures, ransomware threats, and compliance risks with expert insights about enterprise-grade backup and disaster recovery plans and more.
Subscribe to our newsletter for practical tips on ERP performance, backup and disaster recovery planning, cloud hosting strategies, artificial intelligence (AI), and IT best practices—tailored for manufacturers, distributors, and business leaders who depend on reliable technology.
In today’s global economy, tariffs can shift overnight — and for distributors, those changes ripple quickly across pricing models, supplier relationships, and customer expectations. While tariffs are nothing new, the pace and complexity of trade updates in recent years have made it harder for teams to react quickly and plan confidently.
Strategy: Establish contingency plans for sourcing and logistics
Strategy: Collaborate closely with trade compliance experts and consultants
The Tariff Challenge: Limited Visibility, High Stakes
Tariff exposure often hides in plain sight. Vendor records might show countries of origin or product categories, but few ERP systems offer a clean, consolidated view of which suppliers are likely to be impacted by new tariffs — and what those impacts could mean financially.
Procurement and finance teams are often left piecing together spreadsheets, customs data, and supplier intel to make urgent decisions. And by the time a potential risk becomes clear, the cost implications may already be felt.
Oversight, Strategy, and Control: Three Ways to Get Ahead of Tariff Risk
1) Invest in Strategic Supplier Diversity
By diversifying your supplier base across multiple countries or regions, you reduce reliance on any one source that may become tariffed. Your ERP system should help track and categorize suppliers by region, and your team should regularly audit where your critical parts or products are coming from.
2) Improve Cross-Functional Visibility
Tariff risk isn’t just a procurement issue — it touches pricing, forecasting, inventory, and even customer experience. Integrating trade visibility into dashboards accessible to operations and finance leadership is key. This means making tariff exposure a regular part of your supply chain reporting, not a fire drill when changes hit.
3) Use Purpose-Built Tools for Trade Risk Management
Rather than rely solely on generic ERP reports, modern distributors are turning to specialized tools that augment their ERP environment. These tools often bring in external data, enrich vendor records with AI insights, and suggest actionable strategies like pre-purchasing inventory or temporarily shifting pricing models.
If you use Epicor Prophet 21, there’s a new solution available that may be worth exploring: the Recurrency Tariff Manager.
This lightweight dashboard plugs directly into your P21 system and uses AI to analyze your vendor list for likely tariff exposure. In under 15 minutes, it can show you where you’re at risk — and help you take action, whether that means sourcing alternatives, adjusting purchasing, or planning pricing changes.
It’s a smart way to bring clarity into a complex challenge — without requiring months of development or a full system overhaul.
Managing tariff risk isn’t just about compliance or cost control. It’s about building resilience into your operations — so that when change comes, you’re prepared. By improving visibility, sharing insights across teams, and using the right tools, you can turn tariff challenges into strategic opportunities.
If you don’t want to explore things like how to manage tariff risk in distribution ERP without industry experts helping you the mitigate risks, our team at EstesGroup is always available to help you make sense of your data and identify the right tools for your ERP and business strategy.
Get valuable cloud technology & ERP insights delivered directly to your inbox. Receive exclusive updates, practical guidance, and expert tips tailored specifically for your business.
As of version 2026.1, Epicor’s Kinetic ERP will no longer contain a smart client deployment, and the user base will communicate with the application exclusively through a web browser.
Depending on the extent of customizations to the UI and to components like dashboards, conversions may take a significant amount of time in modification and testing.
That said, what are key differences?
The user communicates with Epicor in a new User Interface (UI)
Runs in a browser instead of a fat client
Runs on web-centric devices—not limited to a traditional computer screen and now available on tablets, phones, etc.
Epicor components and business objects can be accessed through a mobile app—not limited to Epicor’s own apps
UI can be customized, but has no C# code, so heavy lifting must be off-loaded to BPMs and Functions
So you want to know more Epicor Kinetic UI tips and tricks for when the rubber meets the road? The EstesGroup Epicor Kinetic consulting team recently covered some technical areas of concern that can help you migrate to a better place moving forward.
In helping customers move to Kinetic, we’ve encountered countless requests for various items of the Epicor Kinetic UI “tips and tricks” variety—something like: “Can Classic dashboards be automatically converted to Kinetic?”
The answer is “yes, but…”
An easy way to generate the Kinetic application is via the Tools/Deploy Dashboard option. You can preview the dashboard or generate the application when you’re satisfied with it. This does convert a lot of things well, but you’ll notice something immediately with the trackers when you preview the Kinetic dashboard.
The filter field(s) in the very first tracker will appear in a slide-out panel when the dashboard opens. Filtering may or may not actually work. Notice there is no OK button in this example.
Other panels have had different issues. And once the panel is discarded, the user can never access it again until the dashboard is restarted. Also, if there are multiple queries/trackers on the dashboard, the subsequent trackers will never fire. It might seem disheartening at first blush, but there are workarounds.
A relatively easy way to do this is this procedure in Dashboard Entry:
Copy the dashboard to avoid changing the original, perhaps add a “K” to the end of the dashboard ID, or some other scheme
Load the new copy of the dashboard
Delete all trackers on the dashboard
Preview the dashboard and make sure it runs okay, other than the missing trackers
Save the dashboard
Create the Kinetic application (Tools/Deploy/Application)
Open the new Kinetic application and add the trackers back in
Adding the trackers manually may sound like a lot of work, but it’s not too bad. Plus, you can add some nice functionality.
Need more guidance? Sign up to get our Ultimate Epicor Kinetic UI Tips and Tricks Guide!
GET THE GUIDE
Fill out the form below to receive your copy of Uplift Epicor Classic UI to Kinetic UI – Questions and Answers. We’ll send our help guide straight to your inbox so you can start planning your upgrade with confidence.
"*" indicates required fields
Stay Ahead with EstesGroup Insights
Get valuable cloud technology & ERP insights delivered directly to your inbox. Receive exclusive updates, practical guidance, and expert tips tailored specifically for your business.
No Native Handshake, No Problem: Making Epicor Kinetic and Prophet 21 Work Together
Running both manufacturing and distribution operations? You might find yourself juggling Epicor’s two flagship systems: Epicor Kinetic (for manufacturing) and Prophet 21 (for distribution). While these platforms weren’t designed to talk to each other out of the box, getting them to communicate doesn’t have to give your IT team nightmares.
Different ERP Systems, Different Strengths
Think of Epicor Kinetic as your manufacturing maestro – handling production schedules, materials, and shop floor activities with robust features for BOMs and shop floor control.
Meanwhile, Prophet 21 excels at distribution – managing inventory, supply chains, and sales orders with streamlined workflows designed specifically for distributors.
They’re like siblings raised in different households – related but with distinct personalities and skill sets. Both use Microsoft SQL Server behind the scenes but speak somewhat different languages when it comes to sharing information. Epicor Kinetic uses a service-oriented architecture with a comprehensive REST API, while Prophet 21 operates through its Middleware API with OData services for queries and transaction processing. So, how do you get Epicor Kinetic and Prophet 21 to join forces?
Option 1: Use Epicor’s Own Toolbox
Automation Studio: This low-code platform is embedded in both systems and lets you build “recipes” that automatically sync data between systems without heavy programming.
Integration Cloud: Epicor’s cloud solution offers pre-built connectors for both platforms, though P21’s connector has some limitations with filtering capabilities.
Option 2: Bring in a Mediator
Third-party platforms like DCKAP Integrator can bridge the gap with drag-and-drop simplicity and pre-built error handling.
Custom API integrations work well for companies with technical resources who need complete control over their data mapping.
Traditional EDI exchanges can handle batch transfers of orders and invoices when real-time sync isn’t required.
Best Practices for Using Kinetic and P21 Systems Together
If you’re taking on this integration project, keep these best practices in mind:
Divide and conquer: Let each system do what it does best – Epicor Kinetic for manufacturing, P21 for distribution.
Start simple: Use Epicor’s built-in tools before diving into custom development.
Establish clear rules: Decide which system “owns” which data (your “source of truth” for customers, inventory, etc.).
Map your journey: Document which fields need to sync, how frequently, and in which direction.
Test thoroughly: Simulate real-world scenarios to ensure the integration handles both successful transactions and errors gracefully.
Roll out gradually: Start with master data sync before tackling complex transactions.
Keep an eye out: Monitor your integration points and optimize as needed.
Case Study: Seamless Order-to-Manufacturing Flow
A metals distributor using Prophet 21 for sales and inventory acquired a fabrication company running Kinetic. Rather than forcing everyone onto one system, they integrated the two platforms:
Customer orders entered in P21 automatically create work orders in Kinetic.
As manufacturing progresses, status updates flow back to P21.
When products are completed, inventory is updated in both systems.
The sales team can provide real-time production updates without switching applications.
They used Epicor’s Automation Studio to build this workflow, allowing each division to keep using the software best suited for their operations while maintaining a single view of the customer order.
Result: Order fulfillment time decreased by 35%, and customer satisfaction scores jumped by 22%.
Case Study: Building Business Intelligence
A building materials company with manufacturing (Kinetic) and distribution (P21) divisions struggled with inconsistent reporting until they integrated their systems:
Sales data from P21 now automatically feeds production planning in Kinetic.
Inventory levels stay synchronized across both platforms.
Financial reporting consolidates data from both systems for accurate forecasting.
Result: Inventory carrying costs decreased by 18%, and the time to generate company-wide reports dropped from days to minutes.
Do you have a good reason to use Epicor Kinetic and Prophet 21 together?
EstesGroup is here to help! While Epicor didn’t design these systems to seamlessly integrate, new tools make connecting them entirely achievable. With the right approach, you can create a unified ecosystem that handles both manufacturing and distribution without missing a beat. The result? Less manual data entry, fewer errors, and a smoother operation from production floor to customer door.
It’s a natural human tendency to put off unpleasant tasks like mowing the yard, taking out the trash, or addressing the deadline to move entirely from Epicor’s Classic user interface to their new browser-based Kinetic framework.
Entirely understandable, the attachment to years’ worth of carefully tailoring the ERP environment to your company’s needs is hard to give up. Just when you’ve gotten it “just right,” you’re being reset back to level 1, like a video game that suddenly loses all the lives you’ve built with great effort and ingenuity.
But like a lot of things in life, change doesn’t have to be bad. For one, it gives us a chance to reevaluate the choices we’ve made in the past.
That process you installed ten years ago—is it still meeting your needs? Could it be ditched or improved? Is there a better way?
And some of the modifications done to your system might have been tortured into the old user interface in ways that weren’t optimal, but were a way you COULD get what you wanted. And that code was often s-l-o-w.
Since the latter days of ERP10, Epicor has been introducing new tools like the REST API and Epicor Functions that give us better ways to interact with Epicor Business Objects and better places to put heavy-lifting development on the server side where it belongs.
And all your old work isn’t lost. BPMs still work the same way. Dashboards, and even some screen customizations, can be converted with some tweaking. Yes, all that C# code will disappear, but you can convert most all of its functionality to better forms in the new customization layers and functions.
The secret weapon in this fight?
prep·a·ra·tion – the action or process of making ready or being made ready for use or consideration
The time to begin the journey is likely not a month before the deadline, for several reasons.
The learning curve for transitioning from old to new can be steep. Although many of the concepts are the same or similar between the two environments, they can be expressed in very different ways.
Before starting to convert a Classic application’s customization that has very much complexity, you’ll likely want to document what the old one does and how it does it, complete with data accessed, UD fields added, C# script processes, and so on. Many Epicor ERP installations are not well documented, and this is a good excuse to do a good thing.
Evaluating the old processes and decisions about whether to promote them or instigate some redesign will take a while.
And then, the actual conversion work can be a slow slog if you have a lot of it to do.
All this might seem insurmountable, if not merely daunting. But there’s still time—the first deadline is still over a year away at this writing.
Gather your resources. Identify your team. Get support from management. Make a plan—and realize it might evolve. And as if eating an elephant, take one bite at a time.
Epicor has good documentation for their Application Studio environment via the Help information accessed from the Kinetic menu. Going to Insights will help, as will joining online user groups like www.epiusers.help.
As always, we’re here you help when you need it. The EstesGroup ERP and IT teams will extend assistance in whatever form you need, a jumpstart, specific application conversions, or project management.
Just give us a shout when you need us.
What does Epicor 2026.1 mean for your business?
EstesGroup is a leading Epicor ERP consultancy that blends elite Epicor Kinetic expertise with cutting-edge technology, AI, and cloud services. There are a bundle of technical challenges to work through and decisions to make when uplifting any custom elements of your Epicor Classic UI to Kinetic. Get your questions about Epicor 2026.1 answered now by our ERP experts. Don’t miss out on insights gained in our “Uplifting Epicor Classic UI to Kinetic” webinar with industry experts.
GET THE GUIDE
Fill out the form below to receive your copy of Uplift Epicor Classic UI to Kinetic UI – Questions and Answers. We’ll send our help guide straight to your inbox so you can start planning your upgrade with confidence.
What are the hardware system requirements for Epicor Prophet 21?
Enterprise Resource Planning (ERP) systems like Epicor Prophet 21 (P21) play a crucial role in streamlining operations and driving business growth in the distribution industry. However, the hardware requirements for on-premise ERP deployments present an ongoing challenge, constantly evolving with technological advancements and software updates.
Epicor P21 – Background and Evolving Capabilities
Epicor positions Prophet 21 as a solution “made by distributors for distributors.” As the distribution industry continues to change, P21’s capabilities expand to meet new challenges. These include advanced Customer Relationship Management (CRM), Order Management, eCommerce integration, and Business Intelligence features. With each new version and feature set, the demands on hardware infrastructure often increase.
The Moving Target of Hardware Requirements
The performance of on-premise Epicor P21 systems is intrinsically tied to the underlying hardware infrastructure. As the software evolves, so do its hardware needs. This presents a significant challenge for IT teams, who must continually reassess and potentially upgrade their hardware to maintain optimal performance.
Key Things to Consider When Addressing Hardware System Requirements for Epicor Prophet 21
While specific requirements may shift, some general hardware considerations for P21 deployment include the following:
Servers: Both database and application servers need regular evaluation to ensure they meet the latest requirements.
Processing Power: The demand for more powerful, multi-core processors (such as the Intel Xeon series) tends to increase over time.
Storage: The shift towards faster storage solutions like SSDs and advanced RAID configurations is ongoing.
Memory: RAM requirements typically trend upwards with each major software release.
Networking: As more features become web-based or cloud-integrated, network infrastructure becomes increasingly critical.
Back to the Basics of P21
Servers
Database Server: Responsible for managing and storing data that the ERP system uses; key features for optimal functionality and performance include robust storage and memory, ensuring users can quickly access and process data
Middleware/Web Applications Server: Essential for organizations that utilize P21’s web-based components; requires minimal to moderate processing capability and memory, depending on the number of users
Processing
Server CPU capabilities determine performance
Multi-core processors are recommended
Storage
Solid-State Drives (SSDs) perform the best
Redundant Array Independent Disks (RAID 10) enhance data processing
Memory
Adequate RAM is essential for operation
For the Database Server, 32 GB RAM or greater is recommended
For the Web Server, 8 GB RAM or more is needed, depending on the number of users
Networking
Web-based or cloud-integrated network infrastructure becomes necessary
Scalability has become one of the greatest challenges when addressing hardware system requirements for Epicor Prophet 21.
One of the biggest challenges in on-premise ERP deployment is planning for scalability. As businesses grow and P21 capabilities expand, the hardware infrastructure must be able to scale accordingly. This often requires significant foresight and investment, as upgrading hardware can be costly and disruptive.
Cloud vs. On-Premise ERP: A Shifting Landscape
The evolving nature of hardware requirements is pushing many organizations to reconsider the total cost of ownership for on-premise deployments. Cloud-based solutions, which offload the burden of hardware management and upgrades, are becoming increasingly attractive. However, this shift introduces new considerations around data security, customization, and control.
Staying Ahead of the Cloud
To manage the ever-changing hardware requirements for on-premise P21 deployments, organizations should do the following:
Maintain close communication with Epicor about upcoming releases and their potential hardware impacts.
Regularly audit current hardware against the latest requirements.
Develop a long-term hardware upgrade strategy that aligns with both business growth projections and P21’s development roadmap.
Consider hybrid approaches that leverage both on-premise and cloud resources to balance performance, cost, and flexibility.
The hardware system requirements for Prophet 21 deployments are not static.
They represent an ongoing challenge that requires constant attention and adaptation. While this document outlines some general considerations, it’s crucial to recognize that these may change rapidly. Organizations must stay informed about the latest requirements, plan proactively for hardware upgrades, and continually evaluate their deployment strategy to ensure they’re maximizing the benefits of their P21 system while managing the complexities of evolving hardware needs.
