Backup Command - Intergraph Smart 3D - Administration & Configuration - Hexagon PPM

Intergraph Smart 3D Global Workshare (Oracle)

Language
English
Product
Intergraph Smart 3D
Subproduct
Global Workshare
Search by Category
Administration & Configuration
Smart 3D Version
13

Creates a single folder of backup files for the selected model databases and their associated site and catalog databases. In addition, the command duplicates symbol definition data associated with the catalog. In the event of a system failure or database corruption, or if you need the databases in another location, you can use the backup files to restore the databases with the Restore Command.

You can use Submit Job on the Backup Dialog to access batch services to back up your data when the server may be less busy. See Schedule Project Management tasks with Batch Services.

Set up the backup

The Backup Dialog identifies the model by name, database size, and description, and allows you to specify the folder location (server and folder or UNC location) in which to store the backup files. If necessary, you can save more than one model to a single folder location. If several models refer to the same catalog database, the software saves the catalog database only once. You can also configure the client computer to work with only one site database at a time.

  • To transfer model configurations to another office, perform a complete backup in Project Management. Include new and modified files in the SharedContent folder, as well as any customized .dll files.

  • The folder in which the backup configuration file (.bcf) is stored must be shared and write permissions given to users and all accounts used as logon for Oracle services. In addition, if you are running Oracle on Linux, the .bcf file must be saved on a Windows-based computer.

Backup location

The software saves the site, model, and catalog databases to the same folder. The reports and reports schema databases are not included in the backup set. If the model is restored on-site (that is, restored in the same server location and the schema of the restored catalog database has not changed), you can continue to use the original reports databases without incident. If, however, the model is restored off-site (at a different location), or the structure of the restored catalog database is different, you must use Edit > Regenerate Reports Database to recreate the reports databases. A log file recording the results of the backup process and describing any problems is created in the backup location.

When using an Oracle Linux environment, the database backup location must be on the Linux computer where the Oracle service is running. The account used to run the Oracle service must have write permission to the backup location. Linux is a case-sensitive environment. Make sure that you use the correct case when typing the path for the database in the database backup utility.

Backup schedule

An established backup plan is mandatory for your databases for performance and as a means of disaster recovery. If the databases are never backed up, the log file will continue to grow until no more drive space is available, thus causing the database to come to a halt. The full recovery model is the SQL server default and the one recommended for production systems.

Refer to the Backing Up and Restoring Databases chapter of the SQL server books online for information about what backup option is right for you. The chapter contains Analyzing Availability and Recovery Requirements that presents several viable options. The following recommendation is adequate for a pilot project and system monitoring:

"Back up the log file on a regular basis. A log file is truncated after it is backed up, and backing up the log file is the only way to keep the transaction log file size in check with a full recovery model."

Full database backup is a heavy operation and should be planned on a regular basis, such as once a week. The right backup strategy depends on your business requirements and the activity on the database. Perform regular differential backups to save all changes since the last full backup. A typical backup schedule might be as follows:

Backup Type

Schedule

Full

Weekly

Differential

Nightly

Transaction log

Hourly

  • Hexagon PPM recommends that you back up the log file once every 24 hours.

  • Using SQL Server to back up and restore your project data is not supported. Backup and restore functionality is limited to the tools provided in the Database Wizard and in Project Management.

Backup Dialog

Schedule Backup Dialog

Optional Schedule Properties Dialog