JetBackup

Dear customer,

What kind of errors you’ve faced? Have you already tried to contact us with those questions? Have you asked our help regarding that? Finally, it’s easy just say “many failures occurred and give 1 star” without mentioned the exact reason. We really hope you understood what we meant.

This’s the one of few plugins which provider everything for Free users without bothering them with upgrades or ads. So, please clarify why exactly you gave one star, otherwise we’re supposed to think all this 1 stars thrown recently are planted and no one is real.

Thank you,
Backup Guard

Yes, you can!

Dear @willychirinos,

We use our own format because of several reasons:

1) The zip format has limitations that we don’t have. For example, a zip file cannot be larger than 4GB or have more than 65535 files.
2) We have removed a lot of unused headers, making that way our file smaller and faster to generate or extract.
3) As you already know, many of WordPress based websites are hosted in shared hostings that have small execution time limit for PHP scripts. We have figured out a way to surpass that issue thanks to our reloading mechanism, and that could not be possible if we didn’t have our own format.

So we think these reasons are good enough to allow us create and use our own custom archive format. Also, we are also offering you an extraction software, so there is no issue for extracting your files (although we believe that manual extraction is not necessary at all).

We are not trying to control anybody in any way, but we would like to talk with you and understand your point of view, because it’s very important for us.

Thank you!

Dear jennya1,

Could you please indicate what’s your exact problem? What does it mean “it’s not suitable for WordPress”? To be honest we didn’t understand your issue. Could you please open a support ticket here for the issue: https://backup-guard.com/tickets/. So one of our experts will get in touch with you soon.

Thank you,
Backup Guard

Dear @theemeraldtablet,

We use our own format because of several reasons:

1) The zip format has limitations that we don’t have. For example, a zip file cannot be larger than 4GB or have more than 65535 files.
2) We have removed a lot of unused headers, making that way our file smaller and faster to generate or extract.
3) As you already know, many of WordPress based websites are hosted in shared hostings that have small execution time limit for PHP scripts. We have figured out a way to surpass that issue thanks to our reloading mechanism, and that could not be possible if we didn’t have our own format.

So we think these reasons are good enough to allow us create and use our own custom archive format. Also, we are also offering you an extraction software, so there is no issue for extracting your files (although we believe that manual extraction is not necessary at all).

We are not trying to control anybody in any way, but we would like to talk with you and understand your point of view, because it’s very important for us.

Thank you!

We just sent you an email with v1.1.9 attachment. Please check it out and keep us update if something is still wrong there!

Regards,
Backup Guard

Hi,

We’ve already answered your ticket and sent the mentioned package as an attachment there. Haven’t you received any message from us?

Regards,
Backup Guard

We just updated the php script mentioned above which is supposed to extract plugin generated archives. Desktop application doesn’t suppose to extract archives generated by plugin. We have another platform for offsite backups (Cloud Backup Service) and the desktop version extracts archives generated by service, but not by plugin at this moment.

Note: Here you’ll always find the latest version of extractor which aims to extract archives generated by the latest up to date Backup Guard plugin (https://backup-guard.com/tools/extractor/). If you need older versions (e.g. v2), you can download it like https://backup-guard.com/tools/extractor/?v=2.

Thanks,
Backup Guard

Could you please try it again now. Please make sure you’re using WordPress installer/wizard this time.

Could you please open a support ticket here https://backup-guard.com/tickets/ and provide us your restoration logs? We’ll investigate the issue for you.

FYI: The latest Backup Guard versions ( v1.1.10 and upper ) generate v3 archives, whereas your archive might be v2 generated by older version. If so, you should use v1.1.9 to restore the mentioned archive.

Regards,
Backup Guard

There was a bug in v1.1.10. So, we just released a new update v1.1.11 where the issue was resolved. Could you please checkout Backup Guard v1.1.11 instead of. We apologize for all kind inconveniences we’ve caused!

Regards,
Backup Guard

Please open a support ticket here for this specific case (https://backup-guard.com/support). So, one of our developer will help you to figure it out.

Regards,
Backup Guard

This error could happen if only you’re trying to restore old sgbp archive using the latest available Backup Guard versions. If so, please open a support ticket here (https://backup-guard.com/support). So, we’ll provide you the respective package for unpacking the archive.

Regards,
Backup Guard

Could you please list the plugins you’ve installed on your dashboard. So we’ll try to replicate the issue on our side. We checked it on the clean WordPress installation, but didn’t found the mentioned issue there.

Regards,
Backup Guard

Hi,

Which version you’re running at this moment? Also, is it Free or Pro package? This issue was resolved in the latest available version or it’s something new we’re not aware about it.

Regards,
Backup Guard