 Hi guys, welcome back to Daniel's Tech World on YouTube medium DanielRosal.Tech. So for today's video I want to demonstrate the process of backing up a Linux Ubuntu computer using CliteBerry and creating an offsite backup. Now I've discussed in my previous videos about backups and Ubuntu, the 3.2.1 rule which I will not miss this opportunity to talk about, 3.2.1 rule of course being that you have your primary data source such as this Linux computer. You want to always create two backup copies of that primary data source. The next part of that rule is two. So for the two backup copies you want to keep them on different storage media. It really means from one another, in other words that you wouldn't have let's say two backups on a single hard drive because if that hard drive fails then you would lose both backups. You can also interpret it and I'm pretty sure that it's open to interpretation just based on the various ways I've seen it described. You could also interpret that to mean that every single, the primary and the two data backups should all be on different storage media and that of course would make it a bit more secure. So let's take an instance where you have your Ubuntu or your Windows or your Mac machine on a certain drive. So take the best thing you could do would be to have that first backup, your onsite backup on a different drive so that if the primary drive fails the backup will not go with it and of course your offsite needless to say is going to be on a different drive because it's going to be physically in a different location and that's the final one part of the rule is offsite that you will have one copy so two different two backup copies those two backup copies on two different storage media and finally one of them offsite. So offsite just means some are physically located it can be in the cloud which is what we're going to be demonstrating here or it can be you can even take a hard drive shove it into the boot of your car and drive it to a friend's house it actually doesn't matter I mean it's some people will say it shouldn't be in the same city because if an asteroid hit but I think if you're dealing with that asteroid strikes then your non-functional computer or you're missing backup is not going to be your chief your chief problem but that's what offsite means so basically for back plays I think it makes sense I mean I'm not pushing back plays from any commercial affiliation I just know that a lot of the data storage and backup enthusiast communities in inverted commas really like back plays as well just because compared to s3 it is actually really really easy to use it's really easy to use and it's intended for backup storage backup is what they do so you can actually go now I search for back plays Linux just to kind of run through again what back plays themselves actually recommend Linux users do so they have this FAQ which is actually only written a few months ago Linux applications for B2 so the one they push it seems to be duplicity and if you go into their tutorial for how to configure B2 with duplicity so duplicity is a command line interface and it'll let you create encrypted offsite backup so you can see basically you install it via a PPA a third-party PPA and once you have that installed you create your bucket up in B2 and then it's just a case of their showing here how to back up your home directory so you can see the tilt for home duplicity and then this is the syntax you need your key ID enclosed in the square brackets then a semicolon then your application I your application key again enclosed in square brackets and then your B2 bucket name so that's fairly straightforward and duplicity is nice but I'm demonstrating Clydeberry here because I like using a GUI where it's available I don't see any point really in using command line interfaces terminal programs just for the sake of it particularly when I think Clydeberry is a nice tool as well so basically to get it just type in Clydeberry download and you can see now it's a bit confusing don't ask me exactly what's gone on here the website is called msp360.com I change name from Clydeberry but they still keep the old branding the old name and inverted in brackets here you just download this now if I switch in here to Ubuntu Debian what you would not understand is that there is from the landing page in my opinion is that there is a fully functional free version it just says free trial and request a demo for it is about $30 a year if you want to subscribe to the premium version I personally didn't see anything in the premium version I lacked in the free version and I'm certainly paying for enough stuff as it is in the cloud that I didn't feel a compelling need to buy the license but I believe encryption was one of those features so you can go in for free trial and let's just go back to this one click for a bunch of Debbie and Ubuntu and just you know provide them with a couple of details click on the download button and that will get you the program installed now I'm just going to be using this for a file system backup you could actually also use this to backup here's an idea to backup clonezilla so I talked about in a previous video clonezilla creating those disk images bare metal backups and I've never I did actually once moved one up to the cloud that's an option but it would be a bit cumbersome because you'd need to download that from the cloud you know on to a external media and then run clonezilla connect that to the external media and then restore it that way so I basically for this computer for my Ubuntu Linux I've talked about this previously and gone through this in all these different videos I use time shift for simple incremental that's my first savior that's just kind you know I have daily weekly monthly and I just roll back the system quickly I've demonstrated clonezilla before on this channel and I've even demonstrated a clonezilla restore and that's number two that if that kind of softer backup that file backup doesn't work clonezilla will save the day so clonezilla and that actually brings me on to something about Clydeberry to point out and that's that it actually supports both file system backups and block level backup so when you do clonezilla you're backing up the data in blocks you're actually bypassing the file system so instead of syncing up files you are syncing up chunks compressed chunks of files which you can then use to restore so it actually Clydeberry has that option data data block level backup is I believe lighter I'm saying I believe because I'm not sure lighter but also quicker so without further ado so basically in B2 over here I have gone let me just go into my B2 and you can see I have created a new bucket and I've called it Clydeberry demo DR so I just need to remember that and now I'm going to go into Clydeberry and show you how to set up that backup job so this is Clydeberry and you can see the build version down in the bottom left hand corner of the window now what I really like about Clydeberry is that it's a very logical way at least in my mind of setting up backup so the language they use is backup plan so you can see create backup plan is your first first option and of course any true backup enthusiast one of their first questions would be well how are we going to back up the backup plans so you can see there is this export configuration button here which which lets you actually back up the backup plans so create backup plan and the first thing it shows me is all the different cloud and remote storages and actually the NAS is not really a remote storage I showed in a previous video that you can actually use Clydeberry to back up the your your your system to the NAS so that's on your local area network and that was really simple to configure these are other B2 backlays B2 buckets that I've already set up and I've created some backup plans none of them I'm really using except for this one the full disc to B2 so that's running but I'm going to just kind of do a dummy dummy replication so click on the little plus icon in order to attach another former cloud storage now as I said about Clydeberry the strength here is really I mean look at this for the the what sort I'm looking for the list of heavy hitters the the dream team of object storage is that they have available here just to highlight some classics you have S3 and Glacier so if you are backing up you're backing up and your object your cloud backup source is Amazon S3 then go for that one they have a different one for China I've no idea what that's about as I said I don't use S3 for Clyde backups anymore and by the way if you want to migrate between S3 and B2 check out a tool called Flexify it's crazy crazy quick moves it over the over the wire directly cloud to cloud and I moved over you know tens if not hundreds of gigabytes in a few minutes so if you want to just do that migration check out flexify.io and so besides S3 you have Azure as well as I said file system here as you can see can be used to either use a local container and you also have Oracle cloud you also have I mean the ones consumers would care about really would be I guess wasabi Ali Baba cloud S3 compatible is an interesting one you're seeing like B2 rolled out these S3 compatible end points now and Google cloud but I'm gonna go for back back plays B2 and it was cloud berry demo DR now just before I do this I want to just jump quickly and I'm I'm sorry for losing the logical flow of this video a little bit here just to say that this is not the only option for if you want to back up your system to Clyde Berry back plays also have an integrations listing on their website and you can basically filter by use case so I can go use case backup and archive the little Linux penguin the tux penguin is here and I've tried out a few of these tools there's not really much to say except that you have duplicati which is another front end for I believe for duplicity duplicity itself flexify as I've just mentioned free NAS good sync there's a few of them and they actually do mention MSP360 aka Clyde Berry lab so you can check out this list I checked the rest it as well check out this list if you're not satisfied by this methodology of course analogy but this works pretty nicely so back to the backup okay so I'm I put in the display name and I'm just going to quickly go ahead and put in my key ID and application key for B2 okay so I've gone ahead and done that and immediately after I put in the key ID and application key I got my whole list of buckets there and then I just went in and selected Clyde Berry demo DR I know I can click on okay so after I've done that it then appears in this list of cloud storage and I can give it a custom name as well which I will do later just to make it easier to pick up now is before I have the option to give the backup backup name a plan so I'm going to call this demo full system B2 backup now here is the block level backup selector that I discussed before so I'm currently actually using file file based backup but if you want to go for a block level backup then that's where you have the option and also interesting that as a kind of form backup you can you have this option ticked by default to save the backup plan configuration to the backup storage so you kind of automatically get at least that backup plans own mapping built into the backup itself the next screen is selecting your backup store so I have not figured out yet exactly what all these strange numbers are but basically by open going into the file system which is of course has this route over here I can go into the primary file system I want to back up and one thing to quickly point out is other drives on your system show up here too so I do know what this one is backups is my SDB it's a separate drive just just that I use just for backups which has clonezilla and time shifts this is where I actually store my local timeshift backup so my clonezilla backup so that's what those others I still don't know what all these numbers are but let's go into the backup file system and see what's in there so the next question is what do you not need and what what do you need so firstly tick your local file system and then go through what you don't need so this is a little bit you know it depends from system to system but there are certain things that really don't that users do not need so the first one of these now you can firstly look up there are a few different lists I've come across I'm actually drawing this list from an ask a bun to form what is safe to exclude for a full system backup and I'm looking at the leading answer for what this guy excludes with our sync and so some of these are for example virtual folders that are generated during the system run state so one of these let's actually go alphabetically instead the first one I tick off is dev media mounts let's see and also proc now you can do more reading into which folders because there are some differences of opinion and I think some people will say more some people say less the second thing you want to do is look at your own system so my system is not your standard system so I have this folder here called backup in which from the root in which in which time at one point I've dumped in clones that images so I wouldn't want to be dumping an entire backup of the system into a backup of the system because I then I would then be duplicating the backup so again this is my system and not standard so I would not want this then there are other things that I would manually disable so I'm just now running through my my user on the system and one thing that I don't back up so there's a few things here firstly p-cloud and again I think of the rationale here so I'm running this on cloudberry runs on a live system right so on my life system p-cloud I'm using just the default p-cloud client that actually mounts and creates a file system here so if I ran this backup and I included p-cloud I would end up including the my p-cloud which is a few gigabytes in the backup now I'm already backing up my p-cloud with its own methodology so I would not want to capture p-cloud in this backup because it would just be a waste of gigabytes of data for an unnecessary additional backup the same thing for Google Drive I use the OCaml refuse to mount Google Drive here so I don't want to back up take my Google Drive in this backup git I don't want to I don't want to you know I could use this as a way to back up my git repositories but I don't really want to actually I'm going to take it because in the event of a system restore not to back up the repositories per se but just to have the system set up that might be useful and get my git repositories aren't that heavy the other thing I would want would be to take off would be VMware so this is where VMware workstation player stores all its virtual machine files and those are heavy so that's really the only reason I wouldn't be backing those up because I think it's better to you know find backup component by component so if I backed up those virtual machines in their own way I would not want to capture them in this backup so I think that's really enough in terms of what I want to back up so I can go on to the next screen now and now it automatically has this option for do not backup hidden files ticked that's just something to point out I've always unticked this because some of the hidden files of starting with a dot in their file name are things like configuration files for example the redshift you know there's a few files hidden files that I have changed and made edits to so therefore in the interest of making this backup as thorough as possible even though this will entail collecting a bunch of hidden files I don't need I always actually untick this option before going on to the next screen now you don't get this in the free edition so remember I said there was this was this is really what's missing two things are missing two major things at least compression and encryption if you do pay for $30 is not that expensive so if it's $30 for per computer and you really like to look at this tool and you want to encrypt the backup and to compress the backup then you can go for this option you have the option to go for a to set a custom retention policy for the backup files but I'm just going for default not to enforce retention policy and finally you can create a schedule so this is actually because this runs incrementally by which I mean that when you back up your your files it's going to run the first time if you have an internet connection like me and you're backing up the whole file system you know it's going to take but essentially days in order for this to run so that's the bad news the good news is that once you run this the first time the more often you run this the smaller the chunks are naturally going to be and the quicker that will take so basically the first time prepared to leave your computer turned on for potentially days or if you have a good upload or symmetrical internet then you know you might be lucky and it might only take a day but after that then it makes sense to put this on some kind of schedule a daily schedule or run it at midnight or something and that will move up the small chunks of the file system only that were changed since the last run finally you have the backup plan notification option it'll send you a you know the output of how the backup went so I recommend tinkering with a few options here and I would say something as important as backup I don't like skimping on the notifications so I would go for in all cases so it's by default it'll only send you notification when it fails I would like I would personally if this were me I would like to know every single time it ran it doesn't bother me to get one to keep you know and then I would attach a Gmail a Gmail filter based on the pattern here and just put those in just gather a log in my inbox of exactly what went on you actually have a nice option here multiplying node of notifying multiple email addresses and I would also take this option here to generate a detailed report because I think more logging is usually better than less and you can check each day to see exactly make sure that your system backup to an off-site source ran appropriately after that's done it gives you it gives you this this output over here just a summary of the backup plan and you it's you know it's worth having a quick read through this backup storage is our cloudberry bucket at cloudberry demo DR it's going to create the backup with so it's going to create this file this folder in the backup source at the root and then the backup will be inside this the plan name I've given this its own custom name demo full system b2 backup what's included it includes the root folder so that's the whole file system and then I've excluded backup dev I've excluded my google drive p-cloud and vmware and media mountain proc and I probably you know if this were a real backup I'd probably want to actually exclude more than that and I'm not using these well that wasn't really a choice because this is the free plan schedules once daily and this is my notification option and if you want to start the backup now tick the run plan now option and then click on done so that's it I did click the run sorry the run now option and as you can see the backup is initiating so this is what it looks like when the job is in progress you have your info up here the last runtime save on cloud is yes the schedule and source and destination and there's not really much to do here but I mean this is why I prefer this tool to using something like you know our clone or or you know duplicity you can just basically keep this program running have a running on schedule and you can just go in and check exactly what's going on you can see the current file it's working on how many files are copied and it estimates total file size this updates periodically so there's no way that this whole system backup only comes to four gigabytes but you know once I checked my current cloudberry backup at the cloud and certainly it contains a copy of the file system and up to the copy so this does work so that's basically it if you have any questions about cloudberry or any aspects of Linux backups I'd always be happy to hear them my website can be accessed through danielrosil.com at 2Ls in Rosa and I look forward to making the next video