Sponsored Lightning Talk: How to Follow the 3-2-1 Backup Rule in Kubernetes

Sharing of Personal Information with Sponsors In order to facilitate networking and business relationships at the event, you may choose to visit a third partyʼs virtual booth or to access sponsored content. You are never required to visit third party booths or to access sponsored content. When visiting a booth (e.g. by clicking on a third partyʼs logo in the Solutions Showcase or exhibitor directory, and any actions within the booth thereafter including viewing resources), when accessing sponsored sessions in the Sponsor Theater, or by participating in sponsored activities, the third party will receive some of your registration data. This data includes your first name, last name, title, company, address, email, standard demographics questions (i.e. job function, industry), and details about the sponsored content or resources you interacted with. If you choose to interact with a virtual booth or access sponsored content, you are explicitly consenting to receipt and use of such data by the third-party recipients, which will be subject to their own privacy policies.Every admin should have a backup. This principle works for any platform including Kubernetes.One of the timeless rules that can effectively address any failure scenario is called the3-2-1 backup rule. This approach helps to answer two important questions: How many backup files should I have and where should I store them?There are two groups of people: those who have already had a storage failure andthose who will have one in the future. In other words, the 3-2-1 backup rule means you should:- Have at least three copies of your data.- Store the copies on two different media.- Keep one backup copy offsite.