Pivotal Knowledge Base

Follow

Backing up PivotalVRP/MoreVRP repository

The PivotalVRP/MoreVRP repository can be easily backed up & restored into MoreVRP through an included utility called RepoRepli.

Due to the amount of information that is stored within PivotalVRP, the repository in large environments can take vast amounts of storage.  If you are interested in keeping all historical information, you can backup periodically through the Reporepli app.

It is important to know that when you restore a repository into PivotalVRP you dump the present one. Therefore it is important to back up your current repository before you restore a previous one.

The backed up repository is compressed and prior to import should be placed in the MoreDB folder.

Once exported the backup will be placed in the MoreDB folder.

Exporting steps:

  1. Stop the MoreVRP service (services: MoreVRP Service -stop)

  2. Open a command window and navigate to the MoreDB folder. ( C:\Program Files\MoreDB)

  3. Enter the following: CMD>reporepli.exe export

 
 

Figure 1 - RepoRepli path

  1. You will notice the process of the export. When completed the following it will alert you it is done.

 

Figure 2 - Completed export procedure
  1. Once completed the exported file is in the MoreDB folder under the name: backup.bac

  2. Restart the MoreVRP Service (services: MoreVRP Service – start)

    Tip - For your records you should move it to a dated file in order to maintain backup chronology.

Importing steps:

  1. Stop the MoreVRP service (services: MoreVRP Service -stop)

  2. Place the backup.bac file in the MoreDB folder.

  3. Open a command window and navigate to the MoreDB folder. ( C:\Program Files\MoreDB)

  4. Enter the following: CMD>reporepli.exe import

Figure 3 - Repository import

     5. During the import you might get error messages at the beginning saying :

    pg_restore: dropping TABLE dbnames

       pg_restore: [archiver (db)] Error from TOC entry 1490; 1259 25074 TABLE dbnames postgres

       pg_restore: [archiver (db)] could not execute query: ERROR: table "XXX" does not exist

These messages are OK and it just means that the import process makes sure there are no identical tables and that it tries to delete them but they do not exist.

 

Figure 4 - Completed import

     6. Restart the MoreVRP Service (services: MoreVRP Service – start)

Please note : RepoRepli.exe always read or writes form a file called backup.bac that should be placed under the same directory as RepoRepli.exe

 

Below is the simplified usage and path of the RepoRepli command

   CMD>reporepli

RepoRepli Usage: reporepli [export/import] [PostgreSQL Path]

Example: reporepli export "c:\program files\moredb\postgresql"

1.1. Import

The import process consists of the following stages :

1. Dropping existing Database (make sure you do not need it – or Export it first)

  1. Creating a new empty DB

  2. Performing the import.

Command example :

CMD>reporepli import "C:\program files\moredb\postgresql"

1.2. Export

Just run as follows :

CMD>reporepli export "C:\program files\moredb\postgresql"

A backup file called backup.bac will be created.

Comments

Powered by Zendesk