There's much more to making backups than just copying files, as you probably know, you need a backup strategy. In this post, I'm not going to enter in detail on the strategic part. Anyway, I'm going to abide by the most basic and indispensable elements of a backup strategy, that is so, if you ever need your data, you have a certain guarantee that your data will remain available to you when most needed.
I'm going to start with a little bit of theory, I know it's boring, but it will let you understand what you're doing in the second part when we start using the console and giving instructions to the server.
Here are some basic guidelines for GDPR compliance in general. This information is not exclusive to Mautic, it applies to any company that wants to be GDPR compliant.
The basic data privacy rights of an EU citizen that we have to respect:
- The company is responsible for any data breach - We have to obtain explicit consent to store and use data. - Consent to store and use my personal data within or outside the EU. - Inform users of where the data is stored
Installing Mautic plugins or Mautic Mixins (as only God knows why they are officially named now) is really simple... most of the time... But there's always some obscure unofficial plugin that you really need so badly, and those always have little or no instructions and hence they refuse to install.
Don't worry, it really is very simple, if you know a couple of tricks... Let's start with the basics:
SaaS is all the rage in every industry and Marketing Automation is no exception, tools like Hubspot, Marketo, Pardot, Eloqua and many others to the count of more than a hundred MA SaaS tools! However, SaaS tends to use a "one size fits all" service model (or better said, 3 sizes fits all), which tends to leave a big chunk of companies out of their offerings. Your company might be one of the special outliers that don't perfectly fit in the SaaS model. The good news is, most probably, Mautic will cover all of your needs.
You know what NTFS is, that's your windows file system, right? You probably also know that Linux uses several different file systems, the most extended one being ext4...
Here's the thing.... there's an old file system called ZFS, originally designed by SUN Microsystems in 2001 and delivered for the first time as a Solaris product on 2005. At the time, it was a very specific tool designed to serve the needs of a reduced number of companies running large pools of disks sitting in a server room.
What happened between then and now we all know, the Internet became mainstream, allowed cloud computing, then DevOps emerged and then containers exploded; as a consequence of those changes, the needs of system administrators and users alike have completely changed. What used to be a strange and relatively complex file system, tailored for very specific needs and used exclusively by just a few people, might be the best option nowadays and because it was so well architected, 15 years after it's now shining more than ever, rapidly growing in adoption and menacing to become mainstream.