Skip to main content
Skip table of contents

Back up your PeerGFS configuration manually

Overview

We recommend that you manually back up your PeerGFS configuration whenever you upgrade or downgrade PeerGFS.  Backing up your PeerGFS configuration includes not only job configurations, preferences, databases, but also internal options stored in various .ini files.  Previous PeerGFS configuration information and logs are automatically retained during the installation of Peer Management Center; however, manually backing up PeerGFS provides an added layer of protection.  See the Step-by-step guide below for detailed instructions.

Update versus upgrade

Although update and upgrade are often used interchangeably in the technology world, an update (or patch) is typically an enhancement to the current version of the software, while an upgrade is typically a whole new version of the software.  Overall, the processes for updating and upgrading are very similar;  however, an upgrade requires a new version license and a few additional steps.

Step-by-step guide


Manually back up your PeerGFS configuration on Windows

To manually back up your PeerGFS configuration on Windows, follow these steps:

  1. Open the Peer Management Center web interface or rich client.
  2. Stop all running jobs.
  3. Close the client.
  4. Open Windows Service Manager (services.msc).
  5. Stop Peer Management Broker Service.

    The Stop Other Services dialog appears.
  6. Click Yes to stop all Peer Services.
  7. Navigate to the Peer Management Center installation directory (typically C:\Program Files\Peer Software\Peer Management Center):

  8. Back up the following files and folders by copying them to a backup location (such as a folder on the Desktop):

    PMC installation folder

    • PL-Hub.vmoptions (if present)
    • PL-Hub-Service.vmoptions (if present)
    • PL-Hub-Web-Service.vmoptions (if present)

    API subfolder

    • \API\PMC-API-Service.vmoptions (only with PeerGFS v4.6 and later)

    Broker subfolder

    • \Broker\PL-Broker.vmoptions

    Hub subfolder

    • \Hub\workspace\jobs\*
    • \Hub\workspace\prefs\*
    • \Hub\workspace\fc.ini (if present)
    • \Hub\workspace\hub.ini (if present)
    • \Hub\workspace\backup.ini (only with PeerGFS v4.5 and later)
    • \Hub\workspace\db\peerlink\*
    • \Hub\workspace\db\backup\* (only with PeerGFS v4.5 and later)
    • \Hub\workspace\db\dfs\* (only with PeerGFS v4.3 and later)
    • \Hub\workspace\db\filecollaboration\*  

    Before backing up the Hub\workspace\db\filecollaboration subfolder, check its size.  If it is greater than 1 GB, we recommend NOT backing it up.  This particular database folder will be automatically rebuilt when you start your PeerGFS jobs.

  9. Open Windows Service Manager (services.msc).
  10. Start Peer Management Broker Service.
  11. Repeat for the following services, in this order:
    1. Peer Management Center Service
    2. Peer Management Center Web Service (if you are using the web interface)
    3. Peer Management API Service (if you are using the PeerGFS API)
    4. Peer Management Topology Service
  12. Open the Peer Management Center web interface or rich client.
  13. Start jobs as necessary.
Manually back up your PeerGFS configuration on Linux

To manually back up your PeerGFS configuration on Linux, follow these steps:

  1. Open the Peer Management Center web interface.
  2. Stop all running jobs.
  3. Use SSH to connect to the Linux server where the Peer Management Center is installed.

  4. Run the following commands in order to shut down the Peer Management Center service stack:

    CODE 
    sudo systemctl stop PL-Hub-Web-Service.service
sudo systemctl stop PMC-API-Service.service
sudo systemctl stop Peer-Management-Topology-Service.service
sudo systemctl stop PL-Hub-Service.service
sudo systemctl stop PL-Broker.service
  5. Navigate to the Peer Management Center installation directory (typically /opt/peersoftware/peer-management-center):

  6. Back up the following files and folders by copying them to a backup location (such as a folder under ~/):

    PMC installation folder

    • ./PL-Hub.vmoptions (if present)
    • ./PL-Hub-Service.vmoptions (if present)
    • ./PL-Hub-Web-Service.vmoptions (if present)

    API subfolder

    • ./API/PMC-API-Service.vmoptions (only with PeerGFS v4.6 and later)

    Broker subfolder

    • ./Broker/PL-Broker.vmoptions

    Hub subfolder

    • ./Hub/workspace/jobs/*
    • ./Hub/workspace/prefs/*
    • ./Hub/workspace/fc.ini (if present)
    • ./Hub/workspace/hub.ini (if present)
    • ./Hub/workspace/backup.ini (only with PeerGFS v4.5 and later)
    • ./Hub/workspace/db/peerlink/*
    • ./Hub/workspace/db/backup/* (only with PeerGFS v4.5 and later)
    • ./Hub/workspace/db/dfs/* (only with PeerGFS v4.3 and later)
    • ./Hub/workspace/db/filecollaboration/*  

    Before backing up the ./Hub/workspace/db/filecollaboration subfolder, check its size.  If it is greater than 1 GB, we recommend NOT backing it up.  This particular database folder will be automatically rebuilt when you start your PeerGFS jobs.

  7. Run the following commands in order to start the Peer Management Center service stack:

    CODE 
    sudo systemctl start PL-Broker.service
sudo systemctl start PL-Hub-Service.service
sudo systemctl start Peer-Management-Topology-Service.service
sudo systemctl start PMC-API-Service.service
sudo systemctl start PL-Hub-Web-Service.service
  8. Open the Peer Management Center web interface.
  9. Start jobs as necessary.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.

Contact Support Close