Backing Up The Partner System

Overview

You should establish formal procedure for periodic backups of the Partner System. The most important part of the system to backup is the Partner Hub, preferably daily. The configuration for the Map Publisher (or if applicable, Map Translator) should be backed up whenever changes are made. Finally, backing up the configuration for a field computer when it is first installed is a good idea.

Customers are responsible for backups of their installation of the Partner System. Partner does not provide backups as part of standard support service.

We advise you to sometimes use an additional and different backup mechanism for additional redundancy. Also, remember this important saying: “If you haven’t test restoring from backup, you don’t really have a backup.”

For a quick checklist of the tasks involved in backup, see the following page Checklist: Backing Up The Partner System

Less Frequent Backups

The following should be backed up whenever changes are made to them.

  • MasterInstall

  • Configuration for the Map Translator

  • Configuration for a client Field Designer (optional, as settings aren’t usually hard to redo).
    • If your field technicians make extensive use of job or header templates in the Field Designer, this may be a higher priority. See Field Design client below for more information.
  • Additionally, monthly or quarterly backups of the CentralHub/reports is recommended. The frequency here depends on how many reports your company does per day/month/quarter.

Detailed Backup Recommendations

The sections below list the most important components to backup. These are our recommendations; an individual customer may choose to perform more or less frequent backups as appropriate to their situation and policies.

Each section lists a directory path based on standard installation practices; your root installation paths may differ slightly. These directories should be backed up in their entirety at the recommended interval.

Master Install

The majority of configuration for the Partner System is stored in the MasterInstall. The Master Install should be backed up every time a configuration change is made. Loss of the Master Install could mean requiring a complete reconfiguration of the system, which is expensive and time-consuming.

  • PartnerHub/MasterInstall/ (monthly)

Central Hub Data

The CentralHub is a copy of the MasterInstall with working data and maps. Since the CentralHub can mostly be recreated from the the MasterInstall, you only need to backup the data directory in the Central Hub. This directory contains the central data repository for most applications, and is therefore very important. We recommend backing it up on at least a daily basis.

  • PartnerHub/CentralHub/data/ (daily)

Central Hub Field Designer Jobs

For Field Designer customers only, you must also back up the staking job data on the Central Hub. These are very important and should be backed up frequently, preferably on a daily basis.

  • PartnerHub/CentralHub/v3x/Hub/data (daily)

Central Hub Reports

For Field Designer customers, each staking job can have a number of reports. These are important, but also very large. They can be regenerated in the Partner Web, but this is time consuming. Therefore, we recommend that you back up these directories on at least a monthly basis:

  • PartnerHub/CentralHub/v3x/Reports (monthly)

Central Hub Map Packages

It is a good idea to store an extra set of map packages and checksum in the update folder (CentralHubupdatepackages) in case of an emergency. The easiest way to do this is to copy or back up the entire update/ folder of the CentralHub installation. This should be done when the configuration and maps are known to be in a good and working state.

This is highly recommended for a utility with the Forced Update feature enabled. Force Update is configured in Preferences (the Platform/Preferences menu item) in the Update section. If this is standard policy for a customer’s site, Partner recommends having at least one Map Viewer installation that has it disabled. This further ensures that if bad or broken maps are posted, at least one known-good copy will remain available for restoration.

  • PartnerHub/CentralHub/update/ (ad-hoc, with known good maps)

Map Translator

This only applies to customers using the older Map Translator application to process maps for the Partner System. Other customers should use the procedure for Map Publisher, described next.

The MapTranslator/config/preferences contains most of the information necessary to recreate the Map Translator from scratch; however, there are a few other files needed. It is easiest to run either Zip Up Config from the main Map Translator menu or run Platform/resources/ZipUpConfig.bat in the translator install. This creates a zip file with the current date in the root of the Map Translator install. Put this file somewhere safe, and be sure to update it whenever changes are made to the Map Translator. For extra precaution back up the the entire Map Translator folder, when you are confident that the maps are in working order, to another machine in case of computer failure.

  • MapTranslator/MapTranslator/config/preferences/ (daily)
  • MapTranslator/ (monthly)

Map Publisher

The MapPublisher/config directory contains all the files necessary for rebuilding a MapPublisher. There is also a ZipUpConfig.bat located in MapPublisher/os/windows/tools that will create a date-stamped zip file in the MapPublisher/archive/ZipUpConfig folder. You can also Zip Up Config using the Workbench by clicking the File menu and choosing Zip Up Config.

  • MapPublisher/config/seat/ (daily)
  • MapPublisher/modules/seat/ (daily)
  • MapPublisher/ (monthly)

User Installations

Field computers and other end-user installations running Partner update the majority of their files from the Central Hub. This includes most configuration and maps.

Furthermore, all working application data is synchronized routinely back to the Central Hub. This includes staking jobs, inspections, etc.

Therefore, it is not critical to backup end user installations as long as they routinely synchronize and check in to the Central Hub.

An exception is if any seat-only software or configuration is installed. This would reside in the config/seat and config/modules directories. This is not standard practice for Partner-supported installations, so you will have to back these up on based on your own judgment.

  • Partner/config/seat (if appropriate)
  • Partner/modules/seat (if appropriate)

Field Designer User Installations

An exception to the above is Field Designer client installations.

Custom Field Designer job and header templates are stored under config/seat on a Field Designer user installation. If your users make extensive use of these, you should schedule routine backups of config/seat on these installs.

  • Partner/config/seat (monthly)

Development Installations

Any installations that are being used for testing or development may need to be backed up in their entirety, or at least have their config/seat and modules/seat directories backed up on a routine basis. These are nonstandard cases and you will have to consider their needs before setting backup procedures.

  • Partner/config/seat (if appropriate)
  • Partner/modules/seat (if appropriate)