Availability of JB 5.3.13 in the Stable Branch

[Morais]

Hy there!

Do we have an ETA on when Jetbackup's 5.3.13 will be available in the Stable tier? We have several cPanel servers running are regularly affected by those "There is no valid destination assigned to this backup job" warnings, which appear to have been addressed by JB5-Base #1983 rated Critical and fixed in 5.3.13 (RC), yet our servers are unable to upgrade from 5.3.12 as they run the Stable tier.

This issue often requires manual intervention (Reindex followed by a manual start of the failed backup job) every week late at night at least five times a week across our fleet, so it's a bit annoying.

Thanks!

[JetAppsKevin]

Hello Morais,

For our standard release cycle, we move a version to ALPHA > EDGE > RELEASE CANDIDATE > RELEASE with at least 1 month between each tier. We also may choose a stable candidate depending on internal and external feedback we receive for each release, so a version may be released to ALPHA/EDGE/RC but not move to RELEASE. With this in mind, 5.3.13 will not be moving forward to the RELEASE tier. Instead, 5.3.14 (Currently on ALPHA) has been selected as a stable candidate and will be promoted through each of the tiers within the month according to the feedback received. For further insight, 5.3.14 is a hotfix version in response to the reports and feedback we received from 5.3.13 and is being promoted on an expedited release schedule (rather than our usual monthly tier promotion).

Please note that we thoroughly perform internal QA before release as well as when we promote a version to a new tier.

To access the fixes in later versions, it is possible to switch to the desired tier, update JetBackup, and then change back to the RELEASE tier to receive future updates in the RELEASE tier. The following commands will do so: (replace {panel} with the panel your server is using i.e. jetbackup5-cpanel)

Code: Select all

# Change tier to RELEASE CANDIDATE (rc)

jetapps -t jetbackup5-{panel} rc

# Update JetBackup to v5.3.13

jetapps -u jetbackup5-{panel}

# Change tier back to RELEASE to receive RELEASE tier updates in the future

jetapps -t jetbackup5-{panel} release

If you have any questions or concerns regarding an update, our Tech Support team is always ready to assist, and you can reach them by emailing [email protected] or through your JetApps Client Area.

Best Regards,

[Morais]

Thank you, @JetAppsKevin! Sounds great. I pulled the v5.1.13 from the RC in one of our servers that were affected the most and then switched back to Release/Stable tier as intended. It's been a couple of days and we haven't experienced neither new issues with v5.1.13 nor further reports of the original bug, so I will replicate these steps in the remainder of our impacted fleet.

Appreciated!

[Juliet34278]

Hi there!Unfortunately, there’s no official ETA for Jetbackup 5.3.13 in the stable tier yet.I totally get how annoying those "no valid destination" warnings are.I know it takes extra work, but keep an eye on the forum for updates.Hopefuly, well hear something soon!

[JetAppsKevin]

Hi there!Unfortunately, there’s no official ETA for Jetbackup 5.3.13 in the stable tier yet.I totally get how annoying those "no valid destination" warnings are.I know it takes extra work, but keep an eye on the forum for updates.Hopefuly, well hear something soon!

Hello Juliet34278,

Just to clarify, v5.3.13 will not be moving forward to the RELEASE tier. From the feedback we received, we decided to push 5.3.14 on an expedited release cycle. In addition to this, we have reformatted the naming scheme for the versions in order to allow the release of hotfix versions for critical issues. With this in mind, the current versions on each tier are:

* RELEASE - 5.3.14.1
* RC (RELEASE CANDIDATE) - 5.3.14.1
* EDGE - 5.3.14.3
* ALPHA - 5.3.14.3

If you are encountering the "No valid destination" error while using a SSH (Legacy) destination type, please take a look at the following KB article for steps on how to troubleshoot the issue.

https://billing.jetapps.com/index.php?r ... cters.html

If the error is occurring on a different destination type or persists after following the steps in the KB article, please contact our Tech Support team by emailing [email protected] or via your Client Area.

Thank you,