Bobcares

Jetbackup Disaster Recovery: Configuration and Setup.

by | Oct 31, 2022

 Let us take a closer look at how the jetbackup disaster recovery works. With the support of our Server management support services, we can give you a complete note on the whole process.

What does “Disaster Recovery” mean?

jetbackup disaster recovery

The “Disaster Recovery” method allows the users to recover a whole server following a disaster. Consider the fact that our server crashed. We also need to restore all accounts from the backup. We must take the following action to set up the jetbackup disaster recovery:

1: Firstly, Disable orphan backup deletion:

  • To do this go to the JetBackup.
  • After that, go to Settings.
  • Under the General Settings section of the jetbackup, set “Days to keep orphan backups” to 0.

2:Create a new backup destination – Point it precisely where it was on the previous server.

3: Under “Choose indexing type,” select “incremental” and “others” for the newly formed backup location.

4: Create a new “indexing only” task and point it to the backup location we just set up. We have to ensure the appropriate setups of the backups folder location.

5: Clearing the indexing cache and re indexes all backups. From the server’s command line interface, enter “jetcli backup -vfR clear cache.”

6: Go to “Restore Manager” by going to JetBackup -> Disaster Recovery. Backups are shown as “Orphaned” for all accounts. We can choose the accounts to restore and add them to the restoration queue.

After that, we can restore the orphan backup deletion – JetBackup -> Settings -> General Settings, adjust “Days to keep orphan backups.” The default is seven days.

Restore From Disaster Recovery

JetBackup can do disaster recovery by keeping the JetBackup internal database at the location. First, JetBackup must restore the internal database so that it has all of the necessary account information.

  • Firstly, we have to provide the backup location details for the Jetbackup to work on the info.
  • Following that, we must select the database backup (JetBackup option) from which we wish to restore.
  • As the Jetbackup database is encrypted, the root Master, Private Key, from the prior installation or old server is necessary.
  • After this process, JetBackup is ready to restore the accounts. This completes the jetbackup disaster recovery process.
  • Simply choose the accounts to restore them and click “Next Page” to proceed. Finally, the accounts are in the recovery queue; we have to wait while it restores the accounts.

We will have control over the number of restore actions operating at the same time since JetBackup v4.0.12. This should reduce total restore time on the basis of the server’s performance.

Setting the “Concurrent processes” to three. For example, will result in three active restorations until the reasoning of all the accounts. This field’s value is actively chaged.

At this moment, we can go to the WHM by clicking the ‘Finish & Login to Panel’ button; accounts are being restored in the background. We may always return to the queue to check on its status.

[Need assistance with similar queries? We are here to help]

Conclusion

To sum up we have now learned how to set up the jetbackup disaster recovery. With the support of our Server management support services, we have gone through all of the steps necessary to set up the jetbackup disaster recovery.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF