Four ways to hope for the best, but plan for the worst when it comes to your EDI.
EDI connects you to your largest customers and suppliers. So, what happens if it just stops working? Disaster, right?
You know that disasters go well beyond hurricanes and fires to include power outages, viruses, malware attacks, or even human error. And since it’s well documented that it’s tough for businesses to rebound from a disaster, planning is your best bet—not only for disaster recovery, but also business continuity.
But before you plan, let’s first understand what disaster recovery means in the EDI world. It’s a total loss of a data center and can encompass not only data, but also systems. It typically includes access to communications (i.e. AS2, FTP, etc.), accessible and intact database, and functional EDI and application servers.
Here are four key considerations when including EDI in both your disaster recovery and business continuity plans:
- Financial implications. How will downtime impact your organization including costs of being down, fines and loss of both business and customers? And, how long can your business afford to be down?
- Risk assessment. Fully understand your recovery point objective (RPO), which is the maximum period of time data can be lost; and recovery time objective (RTO), the amount of time business can be without service.
- Physical recovery (planning) approaches. This includes disaster recovery installation with failover capability, replication of system to off-site facility, database backup to disk/tape, or a combination of them all.
- Documenting and testing. Once you’ve done all that, don’t forget to make sure your maps, archive and scripts/programs directories, as well as AS2 system and certificates are included in the backups. Be sure to identify, document, test and validate your plan.
Don’t be caught unprepared. Our client management and services teams are here to assist you in developing a plan that’s right for you. Contact us today.