cancel
Showing results for 
Search instead for 
Did you mean: 

How can I backup a PROGNOSIS Database Collection?

Support_Sydney
Moderator

How can I backup a PROGNOSIS Database Collection?

In some cases, you might wish to backup/copy a PROGNOSIS database. Most often this will be to keep a backup copy of the database, but it may also be necessary if Integrated Research support personnel request a copy of a database.

1 ACCEPTED SOLUTION

Accepted Solutions
Support_Sydney
Moderator

Re: How can I backup a PROGNOSIS Database Collection?

In some cases, you might wish to backup/copy a PROGNOSIS database. Most often this will be to keep a backup copy of the database, but it may also be necessary if Integrated Research support personnel request a copy of a database.
PROGNOSIS databases are stored in a directory (or subvolume on NonStop). There are usually many individual files in that area that together make up the database. This article provides some steps to accomplish this backup.
Method 1 - Manually copying the data

Step 1 - Gather the current information about the database

1. Right click on the database to be copied and click “Properties”.
2. Click “OK” in the “Database Properties” dialog & then click "OK" in properties dialog that appears.
3. Note the value for “Location” of this database in the resulting PROGNOSIS dialog.
4. Close the database PROGNOSIS dialog.
5. (Recommended) Stop the database. (Right click on the database to be copied and select “Stop…”)

Note: If you are creating this database copy to send to Integrated Research, do not perform this step. This will stop the database. While the database is stopped it will not collect the data it is configured to collect while running. Stopping the database will cause the loss of at least one interval of data. It is not strictly necessary to stop the database but it is possible for the copy to be corrupt if it is not stopped. If you wish to guarantee integrity of the copy but do not wish to stop the source database, please refer to other method of backing up a database described in this document.

6. If you receive a dialog asking if you wish to stop the database, click “OK”
7. Use the PROGNOSIS directory along with the location determined earlier to copy (or create a compressed copy of) the files that make up the database.

• On NonStop the files are in “$<volume>.<location>”, where <volume> is the name of the volume where PROGNOSIS was installed and <location> is the location determined earlier.

• For Unix/Linux the files are in “<PROGNOSIS directory>/server/configuration/<location>”, where <PROGNOSIS directory> is the directory that PROGNOSIS was originally installed into and <location> is the location determined earlier.

• For Windows the files are in “<PROGNOSIS directory>\Server\Configuration\<location>” where <PROGNOSIS directory> is the directory that PROGNOSIS was originally installed into and <location> is the location determined earlier.


Note: If you wish to FTP these files to another machine (for example, to get the files to a Windows machine and create a zip file), please make sure you FTP the files in binary mode, otherwise the files will be corrupted.
If you do not wish to restart the database, the process has now been completed. Otherwise, please refer to the “Restarting a Stopped Database” KB article. If you need to send this database to Integrated Research, please place the files into a Zip or Tar archive before sending

Once the files are in the new location (note that database files should only be placed in an empty location, and not 'added' to an area where a database already exists), simply add this to the database section of the applicable node using the node navigator in your GUI with the following steps:

1. Right click on the 'Databases' group icon below the applicable node and select Properties
2. Insert the name and location of the new Database files
3. Click OK


Method 2 - Backing up the Database Collection to a Database Summary

There are a couple methods of creating a Database Summary but for this example we will use the GUI and assume you do not have access to the original Database Collection document.

1. Right click the database and select properties
2. Click ok on the first dialogue box and you will be presented with the details of your database collection
3. Once step 2 is complete, you will notice 3 yellow cylinder shaped icons become available on the icon bar. Click on the icon with a 'S' inside it.
4. This will load a new Database Collection document with most of the database properties prefilled from the existing database. The only options that require configuration here is the Name field in the General tab, and the 'Destination Database Storage Details'.
5. Click Save after configuring the details above and select an appropriate location to save the document.
6. Opening this document and clicking 'Start' will copy the contents of the Database collection to a new Database Summary database.

View solution in original post

3 REPLIES 3
Support_Sydney
Moderator

Re: How can I backup a PROGNOSIS Database Collection?

In some cases, you might wish to backup/copy a PROGNOSIS database. Most often this will be to keep a backup copy of the database, but it may also be necessary if Integrated Research support personnel request a copy of a database.
PROGNOSIS databases are stored in a directory (or subvolume on NonStop). There are usually many individual files in that area that together make up the database. This article provides some steps to accomplish this backup.
Method 1 - Manually copying the data

Step 1 - Gather the current information about the database

1. Right click on the database to be copied and click “Properties”.
2. Click “OK” in the “Database Properties” dialog & then click "OK" in properties dialog that appears.
3. Note the value for “Location” of this database in the resulting PROGNOSIS dialog.
4. Close the database PROGNOSIS dialog.
5. (Recommended) Stop the database. (Right click on the database to be copied and select “Stop…”)

Note: If you are creating this database copy to send to Integrated Research, do not perform this step. This will stop the database. While the database is stopped it will not collect the data it is configured to collect while running. Stopping the database will cause the loss of at least one interval of data. It is not strictly necessary to stop the database but it is possible for the copy to be corrupt if it is not stopped. If you wish to guarantee integrity of the copy but do not wish to stop the source database, please refer to other method of backing up a database described in this document.

6. If you receive a dialog asking if you wish to stop the database, click “OK”
7. Use the PROGNOSIS directory along with the location determined earlier to copy (or create a compressed copy of) the files that make up the database.

• On NonStop the files are in “$<volume>.<location>”, where <volume> is the name of the volume where PROGNOSIS was installed and <location> is the location determined earlier.

• For Unix/Linux the files are in “<PROGNOSIS directory>/server/configuration/<location>”, where <PROGNOSIS directory> is the directory that PROGNOSIS was originally installed into and <location> is the location determined earlier.

• For Windows the files are in “<PROGNOSIS directory>\Server\Configuration\<location>” where <PROGNOSIS directory> is the directory that PROGNOSIS was originally installed into and <location> is the location determined earlier.


Note: If you wish to FTP these files to another machine (for example, to get the files to a Windows machine and create a zip file), please make sure you FTP the files in binary mode, otherwise the files will be corrupted.
If you do not wish to restart the database, the process has now been completed. Otherwise, please refer to the “Restarting a Stopped Database” KB article. If you need to send this database to Integrated Research, please place the files into a Zip or Tar archive before sending

Once the files are in the new location (note that database files should only be placed in an empty location, and not 'added' to an area where a database already exists), simply add this to the database section of the applicable node using the node navigator in your GUI with the following steps:

1. Right click on the 'Databases' group icon below the applicable node and select Properties
2. Insert the name and location of the new Database files
3. Click OK


Method 2 - Backing up the Database Collection to a Database Summary

There are a couple methods of creating a Database Summary but for this example we will use the GUI and assume you do not have access to the original Database Collection document.

1. Right click the database and select properties
2. Click ok on the first dialogue box and you will be presented with the details of your database collection
3. Once step 2 is complete, you will notice 3 yellow cylinder shaped icons become available on the icon bar. Click on the icon with a 'S' inside it.
4. This will load a new Database Collection document with most of the database properties prefilled from the existing database. The only options that require configuration here is the Name field in the General tab, and the 'Destination Database Storage Details'.
5. Click Save after configuring the details above and select an appropriate location to save the document.
6. Opening this document and clicking 'Start' will copy the contents of the Database collection to a new Database Summary database.

JP_Toutenhoofd
05 Base Camper

Re: How can I backup a PROGNOSIS Database Collection?

Thanks for your clear 'How To'.

But now that I've got my back-ups of my Collections and Summaries, how do I read/display them on a new machine?

Our Prognosis installment, has to go from WIN/SQL-2012 to WIN/SQL-2016. (with also a different servername).

I would like to have some history available to view on the new machine after the 2012-machine is completely dismanteled.

My snapshots I could do (thanks to @ArthrexGmbH_Moor) but Report do not show on the new machine.

Mvg Jappie Toutenhoofd
Rabobank Netherlands
GeraldC1
Community Manager

Re: How can I backup a PROGNOSIS Database Collection?

Hi, 

 

Here's how to access a Prognosis database after its folder has been copied into the server file system:

01.png

 

02.png

 

HTH