Brandon Olivares

@jbd7 You’ll want to lower that maximum execution time to 30 seconds or so. That’s likely your issue. Please let us know if that works for you.

Hi @tiotrom, yes, you can set up multiple destinations in a single job.

I hope this answers your question.

Hi @cpm9, what time is it running for the other times it runs after 3AM? Is it the same time each day or does it differ?

Hi @nextstep99,

As explained above, this was changed for security reasons.

You’re of course free to add whatever you want to the filename. But the hash will be added somewhere.

Actually it’s only partially random. It is also encoded with the actual job hash. It’s base32 encoded along with 2 random bytes to prevent unauthorized users from guessing what the backup file might be.

So it’s not superfluous at all, and the functionality is working as expected.

Is there any specific problem you have with it, or simply cosmetic?

Hi @teatrodellelce, I’d try contacting your host and ask them why this might happen. It sounds like something specific to your server configuration.

Hi @peoplesgeek, this region is going to be added in 3.4.3, which we will be releasing today. I hope that helps.

Hi @gabrielgomez,

Just to update you, your fix will be included in 3.4.3.

Thanks for letting us know about the issue and for patching it yourself. That was helpful. ??

@dsl225, are you saying that 3.4.2 does not delete old backups prior to 3.4.2?

If that is the case, 3.4.3 should fix this. I’d appreciate if you could test that so we know it is ready for release.

Hi @alizesonline,

I’ve tested the fix with all old naming conventions from 3.4.0 and after and all work fine.

I did have to make a few changes today, so feel free to download again and test: https://github.com/inpsyde/backwpup/archive/master.zip

But for me old archives are being deleted just fine.

Also we’ve change the archive name preview to still show the %hash% so there’s no confusion. It will just generate the proper hash at the time of backup.

Let us know if that works for you.

We plan on releasing tomorrow if all goes well.

@nextstep99, can you please test again? I’ve just committed some changes that should fix the issues you were seeing.

@dsl225, no, I personally ensured that all old formats from 3.4.0 and later will be deleted appropriately. I had some leftover ones from a while ago to test with, and all were handled fine with the fix that was posted here.

Again here’s the link: https://github.com/inpsyde/backwpup/archive/master.zip

Hey @independence_day,

Haha, I totally get the frustration. But I’m glad you understand the reason for the solution, and that it’s acceptable for you.

Yep, we’ll leave well enough alone after this fix is implemented. ??

Since this seems to be resolved, I’m going to mark it as such. ??

Thanks. It shouldn’t need to be tested. Plus the new release should be out tomorrow.

Hi @alizesonline,

I understand your concern.

Again the only reason we changed the hashes was because of a security concern that had to be addressed.

And I think with this solution, it’ll actually give you more flexibility to name them however you want.

The naming format prior to 3.4.0 was basically whatever you wanted it to be. We are going back to that, but will append the hash to the end of the filename, where it shouldn’t have any affect whatsoever.

Hopefully that’s agreeable to you.

I did upload another fix to Github because it wasn’t working the way I wanted it to for new jobs. With the newest version, you’ll see that if you create a new job, the default is this:

%Y-%m-%d_%H-%i-%s_%hash%

That first part you can make whatever you want just like prior to 3.4.0.

Hope that makes sense.

Hi @alizesonline, the new default is no longer backwpup_%hash%_. It’s only because your job already had backwpup_ plus the hash in your archive name.

In the future the %hash% will automatically be placed at the end, but it can be anywhere in the string.

I’m not sure why it is bothering you that the string keeps changing? The string is only ever there for BackWPup to identify it as part of that job. It still does that, just now the string is encoded with some random bytes as well, due to a security issue that was found.

We just wanted to abstract that from the user a bit, and so have the %hash% placeholder, just like there are other placeholders in that string.

I’d like to know that if you don’t like this solution, what do you think is better?

@hyriamb, please try this beta and see if it works for you: https://github.com/inpsyde/backwpup/archive/master.zip