Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Restic 0.13.0

restic.net

Post reply on HN
Print view View original

31–40 of 68 posts

Re: Restic 0.13.0

#31

Post by silon42 »

cma wrote: post #12
mekster wrote: post #3

Unless it's for experimenting, I've stopped caring for backup solutions other than borg and zfs as the only way to prove their stability is to have them exist for a while without big complaints and new ones all seem to have complaints. Just having no data loss isn't enough which is the absolute base point but huge memory consumption and other operational issues are also showstoppers.

Borg being single-threaded is painful in the era of consumer 12 and 16 core CPUs, and even prosumer 64-core.

I like that it runs in the background without heating my laptop much.

Re: Restic 0.13.0

#32

Post by crecker »

lucgommans wrote: post #29
crecker wrote: post #27

Earlier quoted context omitted.

I wonder if you can obtain that behavior with a bash script, but it's boring to write scripts and I do not know if SIGTERM can exit Restic gracely.

If you've ever ctrl+c'd restic, you'll know the message > signal interrupt received, cleaning up

Thanks! Will try tonight to play with Restic

Re: Restic 0.13.0

#33

Post by teaudel »

timmg wrote: post #21

I have a hand-coded backup system for my photo library that writes to S3. It runs every night at 2AM. The one feature I have that's important to me is this: it will figure out what files need to be uploaded and then upload as many as possible for an hour then stop. That means that it runs for at-most an hour a night. The reason I need/wanted this feature is that I might come home from a trip with (eg) 30G worth of ph…

My internet upload speed is bad so I do want something like that.

I would also like to be able to "stage" a backup: figure out what needs to be transmitted and then create the data files that need to be transmitted without actually immediately transmitting it.

That would allow me to do things like backup my laptop to another computer in my house that can upload the files over my slow connection overnight when my laptop isn't on; and to let me bring the backup files to a place (work/university/library) with a fast connection so large backups don't take days or weeks (especially initial backup).

Re: Restic 0.13.0

#34

Post by wedowhatwedo »

Mo3 wrote: post #19
tome wrote: post #17

Earlier quoted context omitted.

These seem to be the supported backends Local directory sftp server (via SSH) HTTP REST server (protocol, rest-server) Amazon S3 (either from Amazon or using the Minio server) OpenStack Swift BackBlaze B2 Microsoft Azure Blob Storage Google Cloud Storage And many other services via the rclone Backend https://github.com/restic/restic#backends=

I saw that, I was specifically wondering about different regular S3 implementations like Linode object storage, Digitalocean spaces, Wasabi, etc

Did you try your back end to see if it works? It's not that hard to download the executable and try it.

Re: Restic 0.13.0

#35

Post by [deleted] »

timmg wrote: post #21

I have a hand-coded backup system for my photo library that writes to S3. It runs every night at 2AM. The one feature I have that's important to me is this: it will figure out what files need to be uploaded and then upload as many as possible for an hour then stop. That means that it runs for at-most an hour a night. The reason I need/wanted this feature is that I might come home from a trip with (eg) 30G worth of ph…

[deleted]

Re: Restic 0.13.0

#36

Post by seized »

timmg wrote: post #21

I have a hand-coded backup system for my photo library that writes to S3. It runs every night at 2AM. The one feature I have that's important to me is this: it will figure out what files need to be uploaded and then upload as many as possible for an hour then stop. That means that it runs for at-most an hour a night. The reason I need/wanted this feature is that I might come home from a trip with (eg) 30G worth of ph…

Rclone will do exactly what you want, upload to S3 and the --max-duration will stop new transfer from starting after a given duration.

There are also throttle options for bandwidth. I use that combined with Node-Red and a smart plug on my monitors, if monitor power draw exceeds a threshold then the upload throttle is changed via the rclone API.

Re: Restic 0.13.0

#37

Post by Mo3 »

wedowhatwedo wrote: post #34
Mo3 wrote: post #19

Earlier quoted context omitted.

I saw that, I was specifically wondering about different regular S3 implementations like Linode object storage, Digitalocean spaces, Wasabi, etc

Did you try your back end to see if it works? It's not that hard to download the executable and try it.

Yes, just now. Here's the piece of information I was looking for - rclone supports S3

Re: Restic 0.13.0

#38

Post by sydney6 »

lykron wrote: post #30
timmg wrote: post #21

I have a hand-coded backup system for my photo library that writes to S3. It runs every night at 2AM. The one feature I have that's important to me is this: it will figure out what files need to be uploaded and then upload as many as possible for an hour then stop. That means that it runs for at-most an hour a night. The reason I need/wanted this feature is that I might come home from a trip with (eg) 30G worth of ph…

You could do this with the `timeout` command. `timeout -s SIGINT 1h restic...` That would let restic run for one hour, and then once the hour elapses send a SIGINT which will stop the process (see https://github.com/restic/restic/blob/a29777f46794ea4e35548f... )

And restic would then resume the backup next time it runs.

[1] https://restic.readthedocs.io/en/latest/faq.html#will-restic...

Re: Restic 0.13.0

#39

Post by sydney6 »

timmg wrote: post #21

I have a hand-coded backup system for my photo library that writes to S3. It runs every night at 2AM. The one feature I have that's important to me is this: it will figure out what files need to be uploaded and then upload as many as possible for an hour then stop. That means that it runs for at-most an hour a night. The reason I need/wanted this feature is that I might come home from a trip with (eg) 30G worth of ph…

Restic has support for rate limiting built-in.

Re: Restic 0.13.0

#40

Post by timmg »

seized wrote: post #36
timmg wrote: post #21

I have a hand-coded backup system for my photo library that writes to S3. It runs every night at 2AM. The one feature I have that's important to me is this: it will figure out what files need to be uploaded and then upload as many as possible for an hour then stop. That means that it runs for at-most an hour a night. The reason I need/wanted this feature is that I might come home from a trip with (eg) 30G worth of ph…

Rclone will do exactly what you want, upload to S3 and the --max-duration will stop new transfer from starting after a given duration. There are also throttle options for bandwidth. I use that combined with Node-Red and a smart plug on my monitors, if monitor power draw exceeds a threshold then the upload throttle is changed via the rclone API.

Ok, that looks like a nice tool. Thanks!
Post reply on HN