Switching WHM Backup from AWS Glacier to Backblaze B2
All someone has to do is look at the pricing model above to see why Backblaze is a no brainer for long term storage (not to mention the first 10GB of storage is free. With its recent inclusion as a destination for web server’s WHM backup, Farmhouse Networking has been recommending our hosting provider customers to make the switch from AWS Glacier. Here is the steps to make the switch:
Setup Backblaze Buckets
Login to Backblaze account
Click on the Create Bucket button in the B2 Cloud Storage Buckets section
3. Give the Bucket a name and keep the bucket private for the backups. Click on the Create a Bucket button.
4. Copy down your Backblaze Bucket name and Backblaze Bucket ID
Setup Backblaze Application Key
Click on the App Keys section
Click on Add a New Application Key
3. Give the Backblaze Application Key a name, chose the newly created bucket from the list and make sure to leave the Type of Access as “Read and Write”. Click the Create Key button.
4. Make sure to copy down the Backblaze Application keyID and Backblaze Application applicationKey. This will be the only time they are both shown. If you lose the Backblaze Application applicationKey then you will have to delete the current one and create a new one.
Setup WHM Backup to Backblaze
Connect to WHM as root user and choose Backup Configuration from the menu. The specific WHM backup settings are not discussed here, but feel free to contact us for advise on how to do so.
2. Click on Additional Destinations. Chose Backblaze B2 from the Destination Type and click on the Create New Destination button.
3. Enter in a backup name. Click on the “System Backups” if that is desired. Leave the Backup Directory blank. Enter in the Backblaze Bucket ID and Backblaze Bucket Name copied down earlier. Enter in the Backblaze Application Key ID and Backblaze Application Key. Click on the Save and Validate Destination button.
Make sure to disable your old AWS Glacier backup destination. All backups on Glacier should be set to auto delete according to a lifecycle, but if not then wait 120 days from creation to remove them to avoid any penalties. Speaking of lifecycles, it is a good idea to change the lifecycle settings on the Backblaze bucket to auto delete after a determined number of days since they do charge for total storage utilized.
If your company is would like to discuss the layers of security you have in place, then contact us for assistance.