Topic: Backup broken

[Peasant]

I've hit a problem with the built in backup with DAR. To cut a long story short, I had to add /etc/dehydrated to my backup, and did the following:

Code: [Select]

mkdir -p /etc/e-smith/templates-custom/etc/dar/DailyBackup.dcf
nano -w /etc/e-smith/templates-custom/etc/dar/DailyBackup.dcf/41go-into
In the 41go-into file, I added the following line:

Code: [Select]

--include  etc/dehydrated
Then:

Code: [Select]

expand-template /etc/dar/DailyBackup.dcf
I ran a backup (which was an incremental), and /etc/dehydrated was in it.

However, when I now run a full backup, only a small portion of my files are being backed up (usually the backup is around 157GB, but it is now 202MB). Backup says it is completing fine. If I run verify backup from the server-manager it tells me that the backup file was incomplete.

Two questions, is there a log file I can view somewhere, and can I 'undo' what I did to see if I can get it working again.

Thanks.

[Peasant]

Doh!!

Just for fun I tried running a backup using the exact instructions that are in the wiki - ie to add /opt to the backup, and so far it seems to be running (previously I got a message within a minute to say the backup had completed).

So I then went and had a look at /etc/dehydrated and saw it was a directory, not a file. The code I should have put in the file 41go-into is

Code: [Select]

--go-into etc/dehydrated
Once this backup has run I'll change the code and try it again.

[ReetP]

Let us know what happens - we can mod the wiki if needs be.

We probably ought to automate adding the dehydrated certs to backups I guess.

[Peasant]

The backup completed successfully, and verifies from the server manager. The /etc/dehydrated directory tree is in the backup.

[Peasant]

Let us know what happens - we can mod the wiki if needs be.

There are two things that have tripped me up in my adventures with letsencrypt. Firstly, although the letsencrypt wiki says I should add the /etc/dehydrated tree to the buit in backup there should perhaps also be a warning that if you don't do this, then when you restore to a new server httpd will complain, and you will have a server you cannot boot into.
Secondly, the letsencrypt wiki gives instructions for affa, but only a link for the built in backup. My mistake was I did not realise that /etc/letsencrypt was a directory tree, and I thought it was a file. I therefore used --include instead of --go-into. It might be worth specifying the code to put into the 41go-into file talked about in the backup with DAR instructions.

Apart from these small glitches I have got on fine. And I've learned a bit more about SME Server in the process of sorting them out, which is all the better