@scottalanmiller said in Automated NextCloud Backup to Wasabi or Amazon S3:

@VoIP_n00b said in Automated NextCloud Backup to Wasabi or Amazon S3:

@scottalanmiller said in Automated NextCloud Backup to Wasabi or Amazon S3:

It is indeed. It's running now.

How much data? How long is it taking?

Note: Use the -P/--progress flag to view real-time transfer statistics :)

260GB or so, nothing crazy. Not sure, ran it overnight.

Also, WTF... Who watches backups real time?

@scottalanmiller said in Bookstack Backup to S3:

@wrx7m said in Bookstack Backup to S3:

@dbeato said in Bookstack Backup to S3:

@wrx7m said in Bookstack Backup to S3:

@dbeato Are you running bookstack in AWS?

Not at the moment. I am just backing up to S3.

Look at Wasabi for S3 compatible object storage. Significantly cheaper.

Yup, can't think of any reason to use S3 unless you are hosted on AWS and aren't using it for backup but for production storage. And even then, not the majority of the time. S3 is too expensive and doesn't really offer anything except locality that is of any specific value. B2 and Wasabi beat it a lot.

Sorry, I posted this as S3 but I should change it to Wasabi. It is the same Idea for both.

@scottalanmiller said in Tech Field Day Stairway to Cloud:

@KOOLER said in Tech Field Day Stairway to Cloud:

Do you guys like my T-shirt?

LOL, I definitely noticed it.

I hope it's not something most valuable on this video :)

@scottalanmiller said:

@Dashrender said:

What's your take on this java utility?

If I recall previous discussions, you're completely fine with server side Java things, it's client side that are horrible.

Considering this is an admin tool, is this good or bad that it requires Java?

Admin Tool = Client Side

So for me, I think it's a bit of crap there. As an admin tool I'd find it one step better than if it was for "generic" users. But in this role, it is still for an end user, just a power user (me.) And I think that any use of client side Java is rather bad. Not the end of the world, but not good. This isn't a new utility, so we can excuse the choice more than we could with a new one. But I'm certainly not planning to deploy it. There has to be better options.

I feel exactly the same way. Was mainly wondering if you did too - and well, you do ;)