So, I was working on my scb backup script; that uses lnd's grpc interface to receive each new static channel backup update and save them somewhere else.

As a reminder, static channel backup is the sum of information saved by lnd about your channels, that can be used if you were to lose access to your node, by giving them to another lnd node so it can propagate properly the channel close requests, so you can recover funds. You HAVE to backup this somewhere else than on your node in case it dies

And on some random google search, I see that RTL (Ride the Lightning) apparently saves them too? Indeed, that's on their website. I look in my lnd instance, and yes I see the option. It is even enabled by default. Indeed, in the configured folder, there is the backup file! Well, my first impression looking at the interface was still 'it looks like a backup that has to be triggered by a user in the UI'. Not really usefull if you want to be sure you have up to date backup for all channels. But no, the backup file date changes regularly, so it is actually regularly re saved! I didn't find information on what's the saving period; does anyone know about it, before I have to go look it up in the source code?

Well anyways; I will keep my current backup mechanism, but it's great to know that I have another different running backup method in tools that I had already installed!

If you're not confortable with console and scripts, maybe you should consider installing RTL on another separate computer and connect it to your node. Even if you only use the tool for this it is worth it imo.

Oh and one last thing. It's one thing to have some tool that generates some file it tells you is your backup. But you should also setup a testnet node, where you also test restoring a scb backup, to make sure you know what to do in case of an emergency, AND to check that it actually allows you to recover your channels balance. Don't trust, verify!