Archiving Data: Are You Vulnerable?

Archiving of your important data is something a lot of people and companies overlook.  Data is probably one of the most vital assets of any company and is the lifeblood that keeps your business moving.

Data loss is usually not on the radar until it happens. And, once it does happen, the importance of good backup/archiving becomes brutally apparent. Are you prepared?

As a simple experiment, imagine that a certain system within your organization was subject to a small fire, all the machines and data on those machines lost. Also any machines / tapes / drives that were stored in the vicinity of the fire have also been lost. You could also be vulnerable if you are dependent on a single cloud based provider, as such an event within their environment could have a large impact on your systems and data. What are your next steps, have you put data protection procedures in place?

 

s3_brungin_disk

 

Hopefully you’ve set up a archiving process where all your databases and data are replicated to a second location every couple of hours. If this is the case,  in the above situation, you’ll be down for a while but you have the ability to rebuild your system with only the loss of the data being due to the fact that there was a latency in the back-up/archiving of the data.

If you’ve set up a good archiving process, then you’ve got a big win on your hands: a fire in the comms room but, due to your diligence and the fact that you had a archiving system in place, you were able to get back up and running with only minimal loss of data. Big cheers and slap on the back for a job well done.

After celebrating your big win, you proceed to forget about it…it was just a minor hiccup, thanks to you, right? Fast forward a month: a client is complaining that a certain action they had requested had never been processed, even though they received a visual confirmation through your site. They’re holding your company liable for the failure to act. That confirmation and the associated action? Unfortunately it looks like it happened right in the middle of your archiving latency blackout.

Despite your best plans, key data was lost. How can you validate that this or didn’t happen?

By using Logentries as your logging service you can capture any major event within your system and log it to our system. This means that you have an audit trail of all the key internal, incoming and outgoing events from your system. Due to the fact that our system is real-time means that you can be sure that events are not lost.

By combining this with our new S3 archiving you would have a copy of the logs for as long as you were required to keep them.  This way you can be sure your compliant with any data prerequisites or compliance requirements your company may have as well as being safe in the knowledge that your data is stored in triple redundancy storage in a SOC 2 compliant data center.

Now you have a way to go back and check the logs at the exact time of the incident, you can verify if the transaction actually happened or if the customer is mistaken. You can validate if they ever received a visual confirmation or just assumed they had, and hence protect your company from possible litigation.

Again due to your keen insight in having used Logentries and our S3 backup you have proven yourself to be one of the smartest people in your company.













    Share This Post


    Posted in AWS, Cloud, Feature

    Leave a Reply

    Your email address will not be published. Required fields are marked *

    *

    You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> <p>

     

    Subscribe to the Blog