Backup and Recovery

Teamcenter 2005 SR1 engineering process management Teamcenter Engineering Backup and Recovery Help
Publication Number ENG00015 C
Teamcenter 2005 SR1 engineering process management Teamcenter Engineering Backup and Recovery Help
This product is intended for use only described in this document. UGS cannot be responsible for the proper functioning of undescribed features and parameters.
Publication Number ENG00015 C
Manual History
Manual Revision A B C
Teamcenter Engineering Version 9.0 2005 (10.0) 2005 SR1
Publication Date December 2003 September 2005 June 2006
This edition obsoletes all previous editions.
2006 UGS Corp. All Rights Reserved. Produced in the United States of America. 2 Backup and Recovery Help ENG00015 C
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Audience . . . . . . . . . . . . . . . . . . . . . . . . . Organization . . . . . . . . . . . . . . . . . . . . . . Conventions . . . . . . . . . . . . . . . . . . . . . . . Teamcenter Engineering Documentation . . . Submitting Comments . . . . . . . . . . . . . . . . Software Copyright and Trademark Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5 5 5 6 9 9 9
Integrated Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 Single File Recovery (SFR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 Single File Recovery Object Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 Single File Recovery in Teamcenter Rich Client . . . . . . . . . . . . . . . . . . . . 2-3 Recovery Management Backup Recommendation . . . . . . . . . . . . . . . . . 3-1 Benets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4 Installing and Using the Cold Backup and Restore Utility . . . . . . . . . . 4-1 Deployment Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the Cold Backup and Restore Utility . . . . . . . . . . . . . Teamcenter Engineering Cold Backup and Restore Utility Usage Verifying Backup and Restore . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 4-1 4-9 4-18 4-19
Using the Teamcenter Hot Backup and Recovery Utility . . . . . . . . . . . . 5-1 Deployment Considerations . . . . . . . . . . . . . . Installing the Hot Backup and Recovery Utility Using the Hot Backup and Recovery Utility . . . Alternate Hot Backup and Recovery Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1 5-2 5-5 5-9
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index-1
Figures
1-1. 2-1. 4-1. 4-2. 4-3. Teamcenter Engineering Third-Party Backup Software Integration Single File Recovery Object Model . . . . . . . . . . . . . . . . . . . . . . . File Download Dialog Window . . . . . . . . . . . . . . . . . . . . . . . . . . Cold Backup and Restore Setup Wizard . . . . . . . . . . . . . . . . . . . Select Installation Folder Dialog Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 2-2 4-3 4-4 4-4
ENG00015 C
Backup and Recovery Help
Contents
4-4. 4-5. 4-6. 4-7. 4-8. 4-9. 4-10. 4-11. 4-12. 4-13. 4-14. 4-15. 4-16. 4-17. 4-18. 4-19. 4-20. 4-21. 5-1. 5-2.
Conrm Installation Dialog Window . . . . . . . . . . . . . Installation Complete Dialog Window . . . . . . . . . . . . Cold Backup and Restore Setup Wizard Reinstallation Installation Complete Dialog Window . . . . . . . . . . . . Cold Backup and Restore Setup Wizard Uninstallation Cold Backup and Restore Utility . . . . . . . . . . . . . . . User Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Incomplete Data . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . Backup Volumes on UNIX Option Message . . . . . . . . List of Volumes on UNIX Disabled . . . . . . . . . . . . . . List of Volumes on UNIX Enabled . . . . . . . . . . . . . . Error Mapping UNIX Path . . . . . . . . . . . . . . . . . . . . Cold Backup and Restore Utility-Source Backup . . . . Add Backup Device Dialog Window . . . . . . . . . . . . . . Backup Complete Message . . . . . . . . . . . . . . . . . . . . Volumes Information for Incomplete Restore . . . . . . . Restore Completed Message . . . . . . . . . . . . . . . . . . . Hot Backup and Recovery Window . . . . . . . . . . . . . . Results Message . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
4-5 4-5 4-6 4-7 4-8 4-9 4-10 4-11 4-11 4-12 4-12 4-13 4-13 4-14 4-16 4-16 4-17 4-18 5-5 5-7
Tables
3-1. 3-2. Comparison Chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2 RMAN Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
ENG00015 C
Preface
This manual describes backup and recovery features of Teamcenter Engineering. Teamcenter Engineering belongs to the UGS portfolio of digital product lifecycle management software and services.
Audience
This manual is intended for users of backup and recovery features. It assumes you are familiar with Teamcenter Engineering volumes and database administration.
Organization
This manual contains the following chapters: Chapter 1 Chapter 2 Chapter 3 Chapter 4 Integrated Backup describes Teamcenter Engineering integrated backup and recovery. Single File Recovery (SFR) describes Teamcenter Engineering single le recovery. Recovery Management Backup Recommendation describes recommendations for recovery backup management. Installing and Using the Cold Backup and Restore Utility describes the planning, installation, and usage of the Teamcenter Engineering Backup and Restore Utility. Using the Teamcenter Hot Backup and Recovery Utility describes the planning, installation, and usage of the Teamcenter Engineering Backup and Recovery Utility.
Chapter 5
ENG00015 C
Preface
Conventions
This manual uses the conventions described in the following sections.
Revision Marks
Technical changes are marked by a bar adjacent to the changed text.
Note, Caution, and Warning Icons

The following icons represent note, caution, and warning messages: A note icon identies general instructions or comments that need to be emphasized. A caution icon identies practices that can either produce results contrary to what you expect or result in damage to software or data. A warning icon identies practices that could result in permanent loss of data or software.
Names and Values

This manual represents system names, le names, and values in fonts that help you interpret the name or value. For example: The le name is pom_schema_server-name_sid. The conventions are: Bold Bold font represents unvarying text or numbers within a name or value. Capitalization is as it appears. In the preceding example, pom_schema_ identies an unvarying portion of the name. Italic Italic font represents text or numbers that vary. The characters in italic text describe the entry. Letters are shown in lowercase, but the varying text may include uppercase letters. In the preceding example, server-name and sid represent varying portions of the name. text-text A hyphen separates two words that describe a single entry. In the preceding example, server-name is a single value. For example, the name of the pom_schema_server-name_sid le may be: pom_schema_Blue5_f731
ENG00015 C
Preface
Command Line Entries, File Contents, and Code

This manual represents command line input and output, the contents of system les, and computer code in fonts that help you understand how to enter text or to interpret displayed text. For example, the following line represents a command entry:
create_change_types -u=user-name -p=password -g=group -f=file-name
The conventions are:

Monospace
Monospace font represents text or numbers you enter on a command line, the computers response, the contents of system les, and computer code. Capitalization and spacing are shown exactly as you must enter the characters or as the computer displays the characters. In the preceding example, create_change_types identies an unvarying portion of the command.
Italic
Italic font represents text or numbers that vary. The words in italic text describe the entry. The words are shown in lowercase letters, but the varying text may include uppercase letters. When entering text, use the case required by the system. In the preceding example, user-name, password, group, and le-name identify varying portions of the command.
text-text
A hyphen separates two words that describe a single entry. In the preceding example, user-name is a single entry in the command.
The following example is a correct entry for the preceding create_change_types command:
create_change_types -u=infodba -p=KLH3b -g=dba -f=change_types.dat
ENG00015 C
Preface
Syntax Denitions
This manual uses a set of conventions to dene the syntax of Teamcenter commands, functions, and properties. Following is a sample syntax format: harvester_jt.pl [bookmark-le-name bookmark-le-name ...] [directory-name directory-name ...] The conventions are: Bold Bold text represents words and symbols you must enter exactly as shown. In the preceding example, you enter harvester_jt.pl exactly as shown. Italic Italic text represents values that you supply. In the preceding example, you supply values for bookmark-le-name and directory-name. text-text A hyphen separates two words that describe a single value. In the preceding example, bookmark-le-name is a single value. [] ... Brackets represent optional elements. An ellipsis indicates that you can repeat the preceding element.
Following are examples of correct syntax for the harvester_jt.pl: command:

harvester_jt.pl harvester_jt.pl assembly123.bkm harvester_jt.pl assembly123.bkm assembly124.bkm assembly125.bkm harvester_jt.pl AssemblyBookmarks
ENG00015 C
Preface
Teamcenter Engineering Documentation

Teamcenter Engineering documentation is provided as online help and as printable manuals: You can access online help by choosing Help from the menu bar of a Teamcenter Engineering rich client application or by clicking one of the links under the Help icon in the Teamcenter Engineering thin client user interface. You can access the printable manuals from the Teamcenter Engineering Documentation CD-ROM. To view the PDF-formatted manuals, use Adobe Acrobat Reader, downloadable free-of-charge from Adobe Systems Incorporated at the following URL: http://www.adobe.com Acrobat Reader allows you to view these manuals online and print selected pages, sections, or the entire manual. UGS grants permission for Teamcenter Engineering users to print, duplicate, and distribute this documentation.
Submitting Comments
Portions of Teamcenter software are provided by third-party vendors. Special agreements with these vendors require UGS to handle all problem reports concerning the software they provide. Please submit all comments directly to UGS. Please feel free to give us your opinion of the usability of this manual, to suggest specic improvements, and to report errors. Mail your comments to: UGS Technical Communications 4233 Lexington Avenue N., Suite 3290 Arden Hills, MN 55126-6198 U.S.A. To submit an incident report, you can use the UGS GTAC online support tools at the following URL: http://support.ugs.com
Software Copyright and Trademark Notices

2006 UGS Corp. All Rights Reserved. This software and related documentation are proprietary to UGS Corp. UGS and Teamcenter are registered trademarks or trademarks of UGS Corp. or its subsidiaries in the United States and in other countries. Java and all Java-based marks are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. All other trademarks or registered trademarks belong to their respective holders.
ENG00015 C
Chapter
Integrated Backup
ENG00015 C
Chapter
Integrated Backup
This chapter describes the Teamcenter Engineering integrated backup and recovery feature.
The integrated backup and recovery feature uses third-party software to enhance Teamcenter Engineering Oracle backup capabilities and allows Teamcenter Engineering to operate continually. This functionality focuses on the area of backing up metadata and math data, and recovering that data in different restoration scenarios. To accomplish this, the integrated backup feature places Teamcenter Engineering in different modes, as illustrated in gure 1-1.
Figure 1-1. Teamcenter Engineering Third-Party Backup Software Integration The following steps describe the process ow shown in gure 1-1. 1. The third-party backup software requests that Teamcenter Engineering freeze all operations on Teamcenter Engineering le system volumes.
ENG00015 C
1-1
Chapter 1
Integrated Backup
2. Teamcenter Engineering sends a cautionary message to the user to save all les. Teamcenter Engineering is placed in read-only mode once there are no open Teamcenter Engineering les in the system. Optionally, Teamcenter Engineering generates SingleFileRecovery instances in the database.
3. Teamcenter Engineering returns okay. 4. The third-party backup software is now ready to take a snapshot of the le system and the Oracle database. 5. The backup of the Oracle database starts in hot mode allowing Teamcenter Engineering to be available in 24-hour/7-day mode. The backup starts for le system volumes on the operating system. Optionally, during the backup, the third-party software can request that Teamcenter Engineering operate in blobby volume mode. 6. The third-party backup software completes the backup operation. 7. The third-party backup software requests that Teamcenter Engineering resume normal mode. 8. Teamcenter Engineering resumes normal mode.
Operation Modes
The integrated backup system operates in four modes: Caution Message, Read-Only, Blobby Volume, and Normal. Mode Caution Message Mode Description Cautions users to save their work to avoid any loss of data during backup. This message is sent before the Teamcenter Engineering volume is set to read-only state for backup. Places Teamcenter Engineering into read-only state. This state holds writing les to the volume during backup. Places Teamcenter Engineering in blobby (temp) volume mode. Teamcenter Engineering can be switched into this mode after the third-party backup software takes a snapshot of the data. Thus, allowing continuous Teamcenter Engineering availability. Places Teamcenter Engineering back in normal mode from caution, read-only, or blobby volume mode.
Read-Only Mode
Blobby Volume Mode
Normal Mode
1-2
ENG00015 C
Chapter
Single File Recovery (SFR)
Single File Recovery Object Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 Single File Recovery in Teamcenter Rich Client . . . . . . . . . . . . . . . . . . . . . . . 2-3
ENG00015 C
Chapter
This chapter describes Teamcenter Engineering single le recovery.
Single le recovery (SFR) allows users to search for and restore purged versions of les from the backup medium. This mechanism also helps restore the les from the backup, if accidentally deleted by a user. The scope of SFR is limited to restoring math data from backup medium. With the current functionality in Teamcenter Engineering, les revised beyond the set revision limit (default is 3) in are eclipsed. These orphaned les are stored in the volume, are typically purged at some point, and are no longer referenced by the dataset once the revision limit is reached. However, the typical day-to-day backup preserves the revision limit (default is 3) versions of the le in the Teamcenter Engineering volume backups. These les may not be referenced in Teamcenter Engineering but are stored on backup media. Because the le is no longer associated in Teamcenter Engineering, a tedious restoration effort must be undertaken to bring the le back into Teamcenter Engineering. SFR uses Teamcenter Engineering to retrieve information from the third-party backup application through the user-level search and restore capability. SFR contains several classes and tables. These tables are installed as a part of the Teamcenter Engineering integrated backup application. SFR also derives attributes from various Teamcenter Engineering classes. These attribute values are copied and therefore do not impact in the base classes from where they were derived.
ENG00015 C
2-1
Chapter 2
Single File Recovery Object Model

Figure 2-1 shows the Single File Recovery Object Model.
Figure 2-1. Single File Recovery Object Model
2-2
ENG00015 C
Single File Recovery in Teamcenter Rich Client

The different modes that are prompted in the Teamcenter Engineering rich client user environment depend on the following preference setting:
IMAN_Fastrax_BkupMode_interval=1
A threaded process checks Teamcenter Engineering for the interval set in the preference for any backup modes. The number set default value for Teamcenter Engineering to check for Fastrax backup and recovery messages every X minutes. You are prompted with the following messages in each mode: Mode Caution Message Mode Message Teamcenter Engineering le system will enter Read Only Mode in a few minutes for backup. Please save all your les. Teamcenter Engineering le system is now available in Read Only Mode. Teamcenter Engineering le system is now available in Normal Mode. Teamcenter Engineering le system is now available in Blobyvolume Mode.
Read-Only Mode Normal Mode BlobbyVolume Mode
Single File Recovery

The SingleFileRecovery query, located in the My Navigator search pane, is used to locate single les for recovery. Once you have run the query, the system displays the following error message:
A Reference of File in the Database OR a Copy of file from Backup will be recovered in the Newstuff folder.
ENG00015 C
2-3
Chapter
Recovery Management Backup Recommendation
Benets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
ENG00015 C
Chapter
This chapter describes recommendations for recovery backup management.
UGS recommends the Oracle Recovery Manager (RMAN) product be used with the Teamcenter Engineering integrated backup application. Recovery Manager (RMAN) is an Oracle utility that can back up, restore, and recover database les. This is a feature of the Oracle database server and does not require separate installation. Recovery Manager uses database server sessions to perform backup and recovery operations. It stores metadata about its operations in the control le of the target database, and optionally, in a recovery catalog schema in an Oracle database. You can invoke RMAN as a command line executable from the operating system prompt or use some RMAN features through the Enterprise Manager interface. The features of Recovery Manager are available using the Oracle Backup Manager interface. This is a command line interface, similar to SQL*DBA. It provides a powerful operating-system- independent scripting language and works in interactive or batch mode. The RMAN environment consists of the utilities and databases that play roles in a backup and recovery strategy. A typical RMAN setup utilizes the following components: RMAN executable Target database Recovery catalog database Media management software
Of these components, only the RMAN executable and target database are required. RMAN automatically stores its metadata in the target database control le, so the recovery catalog database is optional. UGS recommends maintaining a recovery catalog. If you create a catalog on a separate machine and the production machine fails completely, you have all the restore and recovery information you need in the catalog.
ENG00015 C
3-1
Chapter 3
Benets
Table 3-1 lists a comparison between RMAN and user-managed methods. Table 3-1. Comparison Chart Recovery Manager Uses a media management API so that RMAN works seamlessly with third-party media management software. More than 20 vendors support the API. When backing up online les, RMAN rereads fractured data blocks to get a consistent read. You do not need to place online tablespaces in backup mode when performing backups. User-Managed Method Does not have support of a published API.
Requires placing online tablespaces in backup mode before backing them up and then taking the tablespaces out of this mode after the backup is complete. Serious database performance and manageability problems can occur if you neglect to take tablespaces out of backup mode after an online backup is complete.
Performs incremental backups, which Backs up all blocks, not just the changed back up only those data blocks that blocks. Does not allow you to recover a changed after a previous backup. You can NOARCHIVELOG database. recover the database using incremental backups, which means that you can recover a NOARCHIVELOG database. However, you can only take incremental backups of a NOARCHIVELOG database after a consistent shutdown. Computes checksums for each block during a backup and checks for corrupt blocks when backing up or restoring. Many of the integrity checks that are normally performed when executing SQL are also performed when backing up or restoring. Omits never-used blocks from datale backups so that only data blocks that have been written to are included in a backup. Stores RMAN scripts in the recovery catalog. Allows you to easily create a duplicate of the production database for testing purposes or easily create or back up a standby database. Performs checks to determine whether backups on disk or in the media catalog are still available. Does not provide error checking.
Includes all data blocks, regardless of whether they contain data.
Requires storage and maintenance of operating system-based scripts. Requires you to follow a complicated procedure when creating a test or standby database. Requires you to locate and test backups manually.
3-2
ENG00015 C
Table 3-1. Comparison Chart Recovery Manager Performs automatic parallelization of backup and restore operations. User-Managed Method Requires you to parallelize manually by determining which les you need to back up and then issuing operating system commands in parallel. Requires you to actually restore backup les before you can perform a trial recovery of the backups. Cannot failover to an alternative archived log if the backup encounters a problem.
Tests whether les can be backed up or restored without actually performing the backup or restore. Performs archived log failover automatically. If RMAN discovers a corrupt or missing log during a backup, it considers all logs and log copies listed in the repository as alternative candidates for the backup. Uses the repository to report on crucial information, including: Database schema at a specied time. Files requiring backup. Files that have not been backed up in a specied number of days. Backups that can be deleted because they are redundant or cannot be used for recovery. Current RMAN persistent settings
Does not include any reporting functionality.
ENG00015 C
3-3
Chapter 3
Features
Table 3-2 lists features of RMAN. Table 3-2. RMAN Features Feature Incremental backups Description Up to four levels; level 0 and levels 1 and 4. v$backup_corruption, v$copy_corruption Also reported in the databases alert log and trace les.
Corrupt block detection During backup:
Restore Easy Management Performance Distributing database backups, resources, and recoveries across clustered nodes in an Oracle parallel server. Limit le size Recovery Catalog Selective Backups Automatic parallelization of backup, restore, and recovery. Multiplexing prevents ooding any one le with reads and writes while keeping a tape drive streaming. Backups can be restricted to limit reads per le, per second to avoid interfering with OLTP work. No generation of extra redo during open database backups. Easy backup of archived redo logs. Limits number of open les. Size of backup piece.
Automates restore and recovery operations. Backs up an entire database, selected tablespaces, or selected datales.
RMAN was introduced in Oracle version 8.0 and is not compatible with Oracle databases prior to version 8.0. For more information about Oracles RMAN, see the following URL: http://www.oracle.com/ip/deploy/database/features/recovery/
3-4
ENG00015 C
Chapter
Installing and Using the Cold Backup and Restore Utility
Deployment Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 Installing the Cold Backup and Restore Utility . . . . . . . . . . . . . . . . . . . . . Distribution Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites and Settings Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . Preinstallation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Teamcenter Engineering Cold Backup and Restore Interface Installation Installing the Cold Backup and Restore Utility . . . . . . . . . . . . . . . Reinstalling or Repairing the Cold Backup and Restore Utility . . . . Uninstalling the Cold Backup and Restore Utility . . . . . . . . . . . . . Teamcenter Engineering Cold Backup and Restore Utility Usage Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backup Database and Volumes . . . . . . . . . . . . . . . . . . . . . . Restore (Source for Restore) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 4-1 4-2 4-2 4-3 4-3 4-6 4-8 4-9 4-9 4-12 4-17
Verifying Backup and Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
ENG00015 C
Chapter
This chapter describes the planning, installation, and usage of the Teamcenter Engineering Cold Backup and Restore Utility. It performs integrated cold backup and restore operations on MS SQL Server 2000 database and Teamcenter Engineering volumes. The utility supports backup and restore of volumes on both Windows and UNIX machines.
Deployment Considerations
The following are the requirements for setting up the Teamcenter Engineering Cold Backup and Restore Utility: MS SQL Server 2000 Standard Edition with SP3a is required for deployment of Teamcenter Engineering Cold Backup and Restore Utility. UGS recommends Windows Server 2003 as the operating system for installing and running the utility. MS SQL Server 2000 client along with Enterprise Manager must be installed on the system from which the utility is being executed. This is required only if MS SQL Server 2000 is not installed on the machine from which the utility is being run. The utility requires installation of Teamcenter Engineering on the MS SQL Server platform. The path for Teamcenter Data Directory Path must be on the Windows platform.
Installing the Cold Backup and Restore Utility

This section describes the distribution media, provides checklists and description of procedures for installing the Cold Backup and Restore Utility.
Distribution Media
The Cold Backup and Restore Utility can be found under the additional_applications\mssql folder.
ENG00015 C
4-1
Chapter 4
Prerequisites and Settings Checklist

Use the following checklist before installing the Cold Backup and Restore Utility. UGS recommends that you perform the steps in the order given below: 1. Verify hardware and software requirements for MS SQL Server. 2. Check if the MS SQL Server Client along with Enterprise Manager are installed on the host system from which the utility is to be executed. 3. The user should be an authorized Teamcenter Engineering DBA user (for example, user ID infodba) and must have the required privileges to perform backup and restore operations on MS SQL Server and Teamcenter Engineering volumes. 4. The user must use the advanced Teamcenter File Services (TCFS) mode to perform cold backup of Teamcenter Engineering volumes. The advanced mode signies that TCFS owns the les and hence, with consistent ownership, the backup can be created without any permission issues. 5. The user must have the user name and password details, along with Teamcenter Engineering data directory path information, to retrieve the MS SQL Server, database, and Teamcenter Engineering volumes location information. 6. The messenger service for the entire domain should be started to be able to send messages to users before and after the backup and restore process using the Net Send facility of Windows. 7. To perform backup or restore tasks for volumes that are on UNIX machines, a third-party software (such as NSF, SFU, or Samba) is required to allow mounting of the UNIX disks to Windows. This third-party software should be installed on the machine on which the utility is to be executed.
Preinstallation Tasks
Before installing the utility, the following tasks must be performed in the given order: 1. Determine the location where the backup is to be maintained. 2. Prepare a schedule plan for backup operation frequency. The plan should take the following details into consideration: Location Determine the location where the backup is to be maintained. Timing Determine the time when the backup operation is to be performed. As a best practice, perform the backup operation during noncritical time, when there are minimum number of users connected to the database. Frequency Determine how often the backup must be performed.
4-2
ENG00015 C
3. Conrm the path for the Teamcenter Engineering data directory path from the location where Teamcenter Engineering is installed. 4. Conrm the location of the backup set for volumes restore and the device or le path for database restore, in case of restore. Refer to the backup.log le for more information. These tasks are to be planned and decided by the administrator.
Teamcenter Engineering Cold Backup and Restore Interface Installation

This section describes the procedure to be followed for installing and uninstalling the Cold Backup and Restore Utility. Installing the Cold Backup and Restore Utility To install the Cold Backup and Restore Utility for the rst time on your system, perform the following steps: 1. Follow the procedure in Prerequisites and Settings Checklist, earlier in this chapter. 2. Under additional_applications\mssql, expand the Cold_Backup_Restore.zip le. 3. Double-click Cold_Backup_Restore.msi. A File Download dialog window is displayed (gure 4-1).
Figure 4-1. File Download Dialog Window The appearance of this dialog window is dependant on the system settings. 4. Click Open. The Cold_Backup_Restore welcome dialog window is displayed (gure 4-2).
ENG00015 C
4-3
Chapter 4
Figure 4-2. Cold Backup and Restore Setup Wizard 5. Click Next to continue. The Select Installation Folder dialog window is displayed (gure 4-3).
Figure 4-3. Select Installation Folder Dialog Window The Folder eld shows where the Cold Backup and Restore Utility is installed. Click Browse to change it to a location of your choice. 6. Click Next to continue.
4-4
ENG00015 C
The Conrm Installation dialog window is displayed (gure 4-4). 7. Click Next to start the installation.
Figure 4-4. Conrm Installation Dialog Window 8. Once the installation is complete, the Installation Complete dialog window is displayed (gure 4-5).
Figure 4-5. Installation Complete Dialog Window
ENG00015 C
4-5
Chapter 4
9. Click Close to exit. A new application named Cold_Backup_Restore is displayed in the StartAll Programs folder. A new folder for the utility is also created in the C:\Program Files folder (or the path specied) during installation. This folder contains a Logs and Procs folder, as well as the backup_restore.exe le and all the supporting les. Double-click the backup_restore.exe le to start the backup or restore process. Reinstalling or Repairing the Cold Backup and Restore Utility Perform the following steps to repair a corrupted utility: 1. Double-click the Cold_Backup_Restore.msi le. 2. The welcome dialog window for the Cold Backup and Restore Setup Wizard is displayed (gure 4-6).
Figure 4-6. Cold Backup and Restore Setup Wizard Reinstallation 3. Select the Repair Cold_Backup_Restore option and click Finish. The previously installed Cold Backup and Restore is reinstalled with the same settings provided during rst time installation. The restored les also are present at the same location (C:\Program Files\cold_backup_restore). 4. Once repair is complete, the Installation Complete dialog window is displayed (gure 4-7).
4-6
ENG00015 C
Figure 4-7. Installation Complete Dialog Window 5. Click Close to exit.
ENG00015 C
4-7
Chapter 4
Uninstalling the Cold Backup and Restore Utility To uninstall the utility, perform the following steps: 1. Double-click the Cold_Backup_Restore.msi le. The welcome dialog window for the Cold Backup and Restore Setup Wizard is displayed (gure 4-8).
Figure 4-8. Cold Backup and Restore Setup Wizard Uninstallation 2. Select Remove Cold_Backup_Restore and click Finish. All the supporting les that were installed, as a part of the installation for Cold Backup and Restore are removed. The Cold_Backup_Restore folder created in the C:\Program Files folder (or the path specied) during installation is also deleted. After the uninstallation is complete, the Installation Complete dialog window is displayed. 3. Click Close to exit.
4-8
ENG00015 C
Teamcenter Engineering Cold Backup and Restore Utility Usage

This section describes the procedures to be followed for using the Cold Backup and Restore Utility to perform backup and restore of MS SQL Server 2000 database and Teamcenter Engineering volumes.
Getting Started
1. Double-click the backup_restore.exe icon. The Teamcenter Engineering Cold Backup and Restore Utility is displayed (gure 4-9).
Figure 4-9. Cold Backup and Restore Utility 2. Enter a value in the User Id eld. 3. Enter a value in the Password eld. 4. Enter a value in the Teamcenter Data Directory Path eld. 5. Click Browse to select a location.
ENG00015 C
4-9
Chapter 4
6. Select: Source for Backup to back up the database and volumes. For more information, see Backup Database and Volumes, later in this chapter. Source for Restore to restore the database and volumes. For more information, see Restore (Source for Restore), later in this chapter.
Source for Backup is the default selection when the utility opens. This enables all elds related to the backup procedure namely, Source for Backup (including Add, Remove, and Clear), error handling conditions (Continue Backup on Errors and Abort Backup on Errors), database modes (Normal Mode and Single User Mode), and the Backup Device button. All elds related to the restore process are disabled (in gray), as shown in gure 4-9. 7. The User Message eld is used to send a message to all the current users of the database informing them of the maintenance operation. It uses the Windows Net Send utility to send the message. There is a default message in the text box. To change this message, perform the following steps: a. Enter the required text in the text box provided and click Send. b. A message with the specied text pops up on all user machines that are connected to the database that is being backed up (gure 4-10).
Figure 4-10. User Message c. Repeat the procedure to send a message to all users to resume their work after the backup or restore is complete. All these elds are required to get the location of the Teamcenter Engineering volumes, backup device information, or to send a message to perform Teamcenter Engineering data backup or restore.
4-10
ENG00015 C
Note the following: If any of the required eld names are missing, an error message indicating the missing eld is displayed (gure 4-11).
Figure 4-11. Incomplete Data If you enter an incorrect user ID or password, an error message is displayed (gure 4-12).
Figure 4-12. Data Validation Similar error messages are populated if the Teamcenter data directory details given are incorrect. Take care in entering the correct information to perform backup or restore tasks. The server name and database name are obtained by the utility from the iman_prolevars.bat le located at the Teamcenter data directory path. This information is required to establish a connection with the database.
ENG00015 C
4-11
Chapter 4
Backup Database and Volumes

Perform the following steps to back up volumes: 1. Select Source for Backup in the Teamcenter Engineering Cold Backup and Restore Utility dialog window (gure 4-9). This is also the default selection when the utility rst opens. 2. To dene the volumes path, click Add. A message conrming whether the volumes on UNIX machines are to be backed up is displayed (gure 4-13).
Figure 4-13. Backup Volumes on UNIX Option Message 3. Click No to perform backup of volumes on Windows only. A new List of Volumes dialog window with the volumes information is displayed (gure 4-14). The List of Volumes on UNIX panel is disabled.
Figure 4-14. List of Volumes on UNIX Disabled Click Yes to perform backup of volumes on both UNIX and Windows. A new List of Volumes dialog window with the volumes information is displayed (gure 4-15). The List of Volumes on UNIX panel is enabled.
4-12
ENG00015 C
Figure 4-15. List of Volumes on UNIX Enabled 4. In the List of Volumes on Windows panel, select all volumes by checking Select All, or select individual volumes by clicking on each one. 5. Select the volumes on UNIX to be backed up: a. Enter the UNIX volume path in the Enter the Unix path to Map eld as shown in gure 4-15. This can also be selected from the List of Volumes on UNIX panel. b. c. Click Add to List to add the path to the Volumes to be Mapped list. Repeat this step to add multiple volumes to be mapped. Click Remove to remove any item from the Volumes to be Mapped list.
d. Select the volumes paths to be mapped and click Map. e. On successful mapping, the drive to which the path is mapped is displayed under Drive, next to the corresponding path. If an error occurs during the mapping process, a message displaying the path details is displayed (gure 4-16).
Figure 4-16. Error Mapping UNIX Path
ENG00015 C
4-13
Chapter 4
Click OK. The List of Volumes dialog window is displayed. Choose the correct path and repeat the steps listed above to map the path successfully. 6. Click OK on the List of Volumes dialog window. The selected volumes are automatically populated in the Source for Backup pane in the main dialog window (gure 4-17).
Figure 4-17. Cold Backup and Restore Utility-Source Backup 7. Click Remove to remove the individual volumes from the list that need not be backed up. 8. Click Clear to clear the entire list. 9. Enter the Destination path. Click Browse to select a location. 10. Click Continue Backup on Errors to continue backup of volumes even if any errors occur during the process. The details of all the errors encountered is maintained in the log le for the users future reference. This log le is present in the directory where the utility is installed under the Logs folder.
4-14
ENG00015 C
11. Click Abort Backup on Errors to abort the backup operation if any error occurs during the backup process. The utility displays a message to the user indicating the error and aborts the process. 12. In the Database Backup Information panel, select: Normal Mode to perform the database backup in normal mode. This means that all current user connections to the database are retained while backup is performed. As simultaneous updates to the database and volumes are allowed while backup in normal mode is being performed, there is a high possibility of data inconsistency. Select Single User Mode to set the database in single user mode before backup is initiated. By selecting this, all existing user connections to the database are killed. All users of the Teamcenter Engineering application must log off for the backup process to take place. They must log back in after backup is over, as their sessions are killed. 13. Select either Backup Device or File Name path to perform the database backup. When the Backup Device option is chosen, the File Name option is disabled and vice versa. A backup device is a predened location on the server machine on which the backups are stored. It must be created before the backup process. A backup device can be created using the Cold Backup and Restore Utility only when the utility is executed on the machine where MS SQL server is up and running. A File Name entry is a path on the hard disk of the machine where the MS SQL Server is installed. This can be specied prior to the initiation of the backup process. 14. Select the Backup Device option to perform the database backup. 15. Click Choose to select a backup device. The Add Backup Device dialog window opens with the list of backup devices (gure 4-18).
ENG00015 C
4-15
Chapter 4
Figure 4-18. Add Backup Device Dialog Window 16. Select the backup device of choice from the options provided in the Current Backup Devices list. To add a new backup device to the list of backup devices: a. Specify appropriate entries in the Device Name and Device Type elds. b. c. Specify the Physical Location information. Click Add.
Types of devices that can be added are Disk, Tape, or CD ROM. 17. Click Refresh to view the newly added device in the list of devices. Click Remove to remove the selected device from the Current Backup Devices list. This does not remove the device from the physical location on the server machine. 18. Click OK to select the backup device. The selected device name is populated in the main dialog window. Click Cancel to close the selection process and return to the main dialog window. 19. To perform backup on a le, select File Name and browse to the location desired on the server machine and click OK on the browse dialog window. 20. Click Backup. Once backup is successfully completed, a message indicating the same is displayed (gure 4-19).
Figure 4-19. Backup Complete Message
4-16
ENG00015 C
An option to view the log le is also provided in the message. Click Yes to view the log le. As a best practice, click Yes to check the log le to ensure whether the backup process has been successful or it has encountered errors. 21. The backup of volumes is stored in a new folder at the destination specied in the main dialog window. The naming convention followed for this folder is: backup_volumes_ddmmyy_hhmmss dd is day, mm is month, yy is year, hh is hour, mm is minutes, and ss is seconds. 22. If the backup operation is aborted due to the selected Abort Backup on Errors option or any critical errors during the backup process, the entire backup set in the destination folder is deleted. 23. If the database backup is successful whether the Abort Backup on Errors option or Continue Backup on Errors is selected, a le named volumes-path.txt is created at the backup set (the new folder created) at the destination. This le contains the volumes path information from where the volumes are backed up. This information is necessary when restoring the database volumes.
Restore (Source for Restore)

Perform the the following steps to restore data: 1. Select Source for Restore to perform the restore operation. The Source for Backup and other options relevant to the backup procedure such as Continue Backup on Errors, Abort Backup on Errors, Backup Mode are disabled. 2. The Source for Restore is the backup set of Teamcenter Engineering volumes, which is created during the backup process. This is usually a folder named in the backup_volumes_mmddyy_hhmmss structure, where dd is day, mm is month, yy is year, hh is hour, mm is minutes, and ss is seconds. 3. A le called volumes-path.txt is created during the backup process. It contains the volumes path information from where the volumes are backed up, which is essential for restoring the data. If this is not located at the backup set location, a message is displayed (gure 4-20).
Figure 4-20. Volumes Information for Incomplete Restore If the volumespath.txt le contains UNIX volumes to restore, the utility maps these paths to the available drives during the restore operation.
ENG00015 C
4-17
Chapter 4
4. Choose a backup device that contains the backup set to restore the database. This can be either a Backup Device or File Name path. 5. Click Restore to perform the restore operation. 6. If the utility encounters any errors during the database restore, it aborts and does not proceed further. The errors are written to the log le restore.log. 7. Once the restore process is successful, a message is displayed (gure 4-21). Click Yes to view the log le.
Figure 4-21. Restore Completed Message As a best practice, click Yes to check the log le to ensure that the restore process is successful.
Verifying Backup and Restore

Perform the following steps to verify backup and restore: 1. Check for database backup. Browse to the destination location where the backup device and le path are provided during the database backup. The backup le name specied during the backup with the .bak extension should be present at the location. The modied date should be the date on which the backup is performed. This is an indication that the backup operation has been performed successfully. 2. Check for volumes backup. Browse to the destination path specied in the Volumes Information panel of the main dialog window (see gure 4-9). A new folder with the naming convention backup_mmddyy_hhmmss is created. This contains all the volumes that are backed up. Also, refer to the log le to check for any errors encountered.
Backup and Restore Log Files

The Cold Backup and Restore Utility generates two log les, backup.log and restore.log, as it proceeds with the backup and restore process. These log les are stored under the Logs folder at the location where the utility is installed. If an error occurs, follow the instructions in the displayed error messages closely. Check the backup and restore log le for the error details and rectify them manually.
4-18
ENG00015 C
Troubleshooting
If there are problems during backup or restore, error messages display. For a detailed log of the error, open the Logs directory for the utility and examine the Backup.log and Restore.log les.
ENG00015 C
4-19
Chapter
Using the Teamcenter Hot Backup and Recovery Utility
Deployment Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1 Installing the Hot Backup and Recovery Utility . . . . . . . . . . . . . . . . . . . . Distribution Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites and Settings Checklist . . . . . . . . . . . . . . . . . . . . . . . . . Preinstallation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Teamcenter Engineering Hot Backup and Recovery Utility Installation . . . . . . . . . . . . . . . 5-2 5-2 5-2 5-2 5-3
Using the Hot Backup and Recovery Utility . . . . . . . . . . . . . . . . . . . . . . . . . 5-5 Alternate Hot Backup and Recovery Procedure . . . . Backing Up and Restoring Database Files . . . . . Backing Up and Restoring Teamcenter Volumes Virtual Device Interface (VDI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9 5-9 5-11 5-11
ENG00015 C
Chapter
This chapter describes the planning, installation, and usage of the Teamcenter Hot Backup and Recovery Utility. It provides the information required to perform integrated (hot) backup and recovery operations on the MS SQL Server 2000 database and Teamcenter volumes.
Deployment Considerations
The following are the requirements for setting up Teamcenter Hot Backup and Recovery Utility: MS SQL Server 2000 Standard Edition with SP3a (or later) is required for deployment of the Teamcenter Hot Backup and Recovery Utility. UGS recommends Windows Server 2003 as the operating system for installing and running the utility. MS SQL Server 2000 client along with Enterprise Manager must be installed on the system from which the utility is being executed. This is required only if MS SQL Server 2000 is not installed on the machine from which the utility is being run. The utility requires installation of Teamcenter on the MS SQL Server platform. The path for the Teamcenter root and data directory paths must be on the Windows platform.
ENG00015 C
5-1
Chapter 5
Installing the Hot Backup and Recovery Utility

This section describes the distribution media, provides checklists, and describes the procedures for installing the Hot Backup and Recovery Utility.
Distribution Media
The Hot Backup and Recovery Utility can be found in the additional_applications\mssql folder.
Prerequisites and Settings Checklist

Use the following checklist before installing the Hot Backup and Recovery Utility. UGS recommends that you perform the steps in the order given below: 1. Verify hardware and software requirements for MS SQL Server. 2. Verify that MS SQL Server Client and Enterprise Manager are installed on the host system from which the utility will be run. 3. You must be an authorized Teamcenter DBA user (for example, the infodba user) and must have the privileges required to perform backup and recovery operations on MS SQL Server and Teamcenter volumes. 4. You must have the user name, password, and group details, along with the Teamcenter root and data directory path information to retrieve the MS SQL Server database and Teamcenter volumes location information. 5. Set the proper values for the preference variables and restart the Teamcenter File Services service as follows:
IMAN_set_imanfsModes= TRUE IMAN_check_imanfsMode_interval=1 blobbyVolume_NT blobbyVolume_UNX
Preinstallation Tasks
Before installing the utility, perform the following tasks: 1. Prepare a schedule plan for backup operation frequency. The plan should take the following details into consideration: Location Determine the location where the backup is to be maintained. Timing Determine the time when the backup operation is to be performed. As a best practice, perform the backup operation during noncritical times when there are a minimum number of users connected to the database. Frequency Determine how often the backup must be performed.
5-2
ENG00015 C
2. Conrm the path for Teamcenter root and data directory paths from the location where Teamcenter is installed. These tasks must be performed by an administrator.
Teamcenter Engineering Hot Backup and Recovery Utility Installation

This section describes the procedure for installing and uninstalling the Hot Backup and Recovery Utility. Install the Hot Backup and Recovery Utility (rst time installation): 1. Complete the prerequisites described in Prerequisites and Settings Checklist, earlier in this chapter. 2. Under additional_applications\mssql, expand the Hot_Backup_Restore.zip le. 3. Double-click the Hot_Backup_Restore.msi le. The Hot_Backup_Restore wizard is displayed. 4. Click Next. The Select Installation Folder dialog window is displayed. 5. In the Folder eld, specify the location where the Hot_Backup_Recovery utility is to be installed. To view installation locations and available disk space, click the Disk Cost button. 6. Click Next. The Conrm Installation dialog window is displayed. 7. Click Next to start the installation. When the installation is complete, the Installation Complete dialog window is displayed. 8. Click Close. A new Hot_Backup_Restore folder is created on your desktop. This folder contains the Hot_Backup_Restore.exe le and other executable les required to run the utility. In addition, the Hot_Backup_Restore folder is created in your C:\Program Files folder or in the location specied during installation.
ENG00015 C
5-3
Chapter 5
Reinstall or repair the Hot Backup and Recovery Utility: 1. Under additional_applications\mssql, expand the Hot_Backup_Restore.zip le. 2. Double-click the Hot_Backup_Restore.msi le. The Hot_Backup_Restore wizard is displayed. 3. Select the Repair Hot _Backup_Restore option and click Finish. The previously installed Hot_Backup_Restore les are reinstalled with the same options and settings provided during the rst installation. The restored les are placed in the same location (C:\Program Files\ Hot_Backup_Restore or the location specied during installation) as the previous installation. When the repair is complete, the Installation Complete dialog window is displayed. 4. Click Close. Uninstall the Hot Backup and Recovery Utility: 1. Under additional_applications\mssql, expand the Hot_Backup_Restore.zip le. 2. Double-click the Hot_Backup_Restore.msi le. The Hot_Backup_Restore wizard is displayed. 3. Select the Remove Hot_Backup_Restore option and click Finish. All the supporting les that were installed as a part of the installation are removed. The Hot_Backup_Restore folder created during the installation is also deleted. After uninstallation is complete, the Installation Complete dialog window is displayed. 4. Click Close.
5-4
ENG00015 C
Using the Hot Backup and Recovery Utility

This section describes how to use the Hot Backup and Recovery interface to back up and recover the MS SQL Server 2000 database and Teamcenter volumes. When restoring data, you must restore the database before restoring the volumes. Figure 5-1 shows the Teamcenter Backup and Recovery interface.
Figure 5-1. Hot Backup and Recovery Window Use the utility to perform the following tasks: Obtain database and volume information. Set Teamcenter modes. Create an XML le containing volume information.
ENG00015 C
5-5
Chapter 5
Obtain database and volume information: 1. Double-click the Hot_Backup_Restore.exe le located in the Hot_Backup_Restore folder on your desktop. This le can also be found in the C:\Program Files folder or the directory chosen during installation. The Teamcenter Engineering Backup and Recovery window (gure 5-1) is displayed. 2. Enter the required information in the following elds: User Id, Password, Group (this is the group to which the user is assigned), Teamcenter Root Path, and Teamcenter Data Directory Path. This information is required to place Teamcenter in the required mode or to create the XML le containing volume information. The server name and database name are taken from the iman_prolevars.bat le located in the Teamcenter Data directory. This information is required to establish a connection to the database. 3. Click GetInfo to display the volume location, server name, and database name in the Database Information section. Set Teamcenter modes: 1. Double-click the Hot_Backup_Restore.exe le located in the Hot_Backup_Restore folder on your desktop. This le can also be found in the C:\Program Files folder or the directory chosen during installation. The Teamcenter Engineering Backup and Recovery window (gure 5-1) is displayed. 2. Enter the required information in the following elds: User Id, Password, Group (this is the group to which the user is assigned), Teamcenter Root Path, and Teamcenter Data Directory Path. This information is required to place Teamcenter in the required mode or to create the XML le containing volume information. The server name and database name are taken from the iman_prolevars.bat le located in the Teamcenter Data directory. This information is required to establish a connection to the database. 3. You can set Teamcenter to operate in one of the following modes: Caution Mode a. In the Teamcenter Modes section, click Caution Mode and click Go. A results message displays the output of execution (gure 5-2).
5-6
ENG00015 C
Figure 5-2. Results Message b. Click Close. Teamcenter is now in caution message mode. The following message is displayed to all users:
TcFile System will enter Read-Only mode in a few minutes for Backup. Please save all your files.
Read-Only Mode a. In the Teamcenter Modes section, click Read-Only Mode and click Go. Users cannot perform any update operations (save data) to Teamcenter volumes when the system is in read-only mode. A results message displays the output of execution. b. Click Close. Teamcenter is now in read-only mode. The following message is displayed to all users:
TcFile System is now available in read-only mode.
Blobby Mode Before placing Teamcenter in blobby volume mode, ensure that the current mode is Normal Mode. a. In the Teamcenter Modes section, click Blobby Mode and click Go. A results message displays the output of execution. b. Click Close. Teamcenter is now in blobby mode. A message is displayed to all users informing them that Teamcenter is operating in blobby volume mode.
ENG00015 C
5-7
Chapter 5
Normal Mode a. In the Teamcenter Modes section, click Normal Mode and click Go. A results message displays the output of execution. b. Click Close. Teamcenter is now in normal mode. A message is displayed to all users informing them that Teamcenter is operating in normal mode. You can select Current Mode and click Go at any time to determine the current mode in which Teamcenter is operating.
Create an XML le containing volume information: 1. Double-click the Hot_Backup_Restore.exe le located in the Hot_Backup_Restore folder on your desktop. This le can also be found in the C:\Program Files folder or the directory chosen during installation. The Teamcenter Engineering Backup and Recovery window (gure 5-1) is displayed. 2. Enter the required information in the following elds: User Id, Password, Group (this is the group to which the user is assigned), Teamcenter Root Path, and Teamcenter Data Directory Path. This information is required to place Teamcenter in the required mode or to create the XML le containing volume information. The server name and database name are taken from the iman_prolevars.bat le located in the Teamcenter Data directory. This information is required to establish a connection to the database. 3. Click Create XML to create an XML le containing the volume details. A results message displays the output of execution. The following message is displayed:
backup.xml and backup.dtd are created at: <Path>
<Path> is the path to the directory from which the utility is executed.
5-8
ENG00015 C
Alternate Hot Backup and Recovery Procedure

If you do not use third-party storage management systems, UGS recommends that you use the SQL Servers Enterprise Manager or T-SQL backup/restore scripts to perform the hot backup and recovery operations on the database. MS SQL Server 2000 supports online (hot) backups from Enterprise Manager that can back up, restore, and recover database les. This is a feature of the MS SQL 2000 Database Server and does not require separate installation.
Backing Up and Restoring Database Files

This section describes backing up and restoring database les. Back up database les: 1. Open the SQL Enterprise Manager by clicking StartAll ProgramsMicrosoft SQL ServerEnterprise Manager. 2. Expand the SQL Server Group to view all existing servers. 3. Expand the required SQL Server. 4. Expand Databases to list the available databases. 5. Right-click the required database and select All TasksBackup Database/Restore Database. 6. Click Backup Database to start the database backup process. The SQL Server Backup dialog window is displayed. 7. On the General tabbed page, choose a type of backup from the Backup options. After you create a complete database backup (using the Database-complete option), you must also create a Transaction log backup. To do this, open the SQL Server Backup dialog window and select the Transaction log backup option. 8. Select the destination (tape or disk) for the backup. A backup device is a location that stores backup les. A backup le can hold multiple backups. If this is the rst backup of your database, create a backup device by performing the following steps: a. Click Add. The Backup Destination dialog window appears. b. Enter a name for the backup in the Name eld. The database name with a .bak extension is used as the default name for the backup. c. Click File Name (backup device).
d. Dene the appropriate path for the le.
ENG00015 C
5-9
Chapter 5
e.
Click OK. The SQL Server Backup dialog window is displayed again.
f.
Select the device or le you created from the Destination list.
9. Select the appropriate overwrite option for your backup. You can use this option to add multiple backups to le or device or to overwrite previous backups with the most current backup. Selecting the Schedule box automates the database backup process. UGS does not recommend using this option, because it only backs up the database. It does not automate the backup of volumes. 10. Click OK. The SQL Server Backup dialog window is displayed. 11. Click the Options tab. 12. Select the options that are appropriate for your organization. 13. Click OK. A message displays indicating successful completion of the backup operation. Restore a database: 1. Open the SQL Enterprise Manager by clicking StartAll ProgramsMicrosoft SQL ServerEnterprise Manager. 2. Expand the SQL Server Group to view all servers. 3. Expand the required SQL Server. 4. Expand Databases to list the available databases. 5. Right-click the required database and select All TasksBackup Database/Restore Database. 6. Click Restore Database to start the database restoration process. The Restore Database dialog window is displayed. 7. Select the type of restore operation to be performed. The type of restore operation depends on the type of backup operation that was performed. 8. Click Database in the Restore area to perform a full database restoration. This is the rst step in restoring the database. 9. Perform the following steps: a. Click the Options tab in the Restore Database dialog window. b. c. Select the setting as per preferences. Select a recovery completion state.
5-10
ENG00015 C
d. Click OK. A message appears indicating the successful completion of the restore operation. 10. To perform a differential restoration of the database, perform the following steps: a. Perform a full database restoration. b. c. Restore the most recent differential backup. Restore all transaction logs that apply (in the appropriate order).
d. Select full backup for the differential backup. e. Click OK. A message appears indicating the successful completion of the restore operation. 11. To perform a transaction-log restore of the database, follow these steps: a. Perform a full database restoration. b. c. Restore the most recent differential backup. Restore all transaction logs that apply (in the appropriate order).
d. Select the Point In Time option in the Parameters area of the Restore database dialog window. e. Click OK. A message appears indicating the successful completion of the restore operation.
Backing Up and Restoring Teamcenter Volumes

Copy the volumes from the source location to the destination device/location. After completing the backup, return Teamcenter to normal mode.
Virtual Device Interface (VDI)

Microsofts Virtual Device Interface (VDI) is integral to all third-party SQL Server backup solutions, whether hardware or software. Introduced in SQL Server 7.0, the VDI provides third-party vendors access to a collection of high-performance backup-and-restore mechanisms. By writing to the VDI, developers can substitute a virtual device for a servers local disk le or tape. VDIs enable third-party software to control SQL Server backup and restore, which allows vendors to create a seamless interface between their own high-performance technologies and the SQL Server. Third-party applications can use the VDI interface to perform snapshot as well as standard SQL Server backup and restore. However, VDI under the SQL Server 7.0 does not permit true third-party integration. It supports only standard SQL Server backup and restore. SQL Server 2000, through its support for snapshot backups, treats the third-party solutions as true backups.
ENG00015 C
5-11
Chapter 5
In this case, the backup of volumes and databases must be performed in the traditional manner. The ability to back up and restore data in a reliable and timely manner requires the SQL Server 2000 VDI (Virtual Backup Device API). Most third-party independent software vendors use the VDI application programming interface to integrate SQL Server into their products. The advantages and disadvantages of VDI are as follows: Advantages This API is engineered to provide maximum reliability and performance to support the full range of SQL Server backup and restore functionality. This API is used by most third-party vendors to perform backup/recovery operations. The VDI provides parallel high-speed data transfer between the SQL Server and the snapshot provider with minimal overhead.
Disadvantages Only utilities that interact with the SQL Server through the VDI can issue the backup and restore command snapshot option. Users cannot issue the snapshot option directly. SQL Server supports only the backups and restorations saved in the snapshot format. It does not support differential and transaction-log backups saved as snapshots. Backup/restore of the SQL Server database is possible using the SQL Server Enterprise Manager or VDI. However, an integrated solution to back up both the SQL database and volumes is not possible using these approaches. Backup/recovery of Teamcenter volumes must be performed using the traditional copy and paste method. VDI combined with the third-party integrations can effectively back up and restore Teamcenter metadata and math data that require minimal downtime and require SQL Server 2000 to be in hot backup mode. This combination enables you to achieve greater exibility by ensuring 24 X 7 availability.
5-12
ENG00015 C
Index
A Aborting backup . . . . . . . . . . . . . . . . . 4-15 Adobe Acrobat Reader . . . . . . . . . . . . . . . 9 Audience for the manual . . . . . . . . . . . . . 5 B Backup and recovery, setting Teamcenter modes . . . . . . . . . . . . . . . . . . . . . . . . . 5-6 Backup devices . . . . . . . . . . . . . . . . . . 4-15 backup.log le for MS SQL . . . . . . . . . . . 4-3 backup_restore.exe le . . . . . . . . . . . . . 4-9 Blobby mode . . . . . . . . . . . . . . . . . . . . . 5-7 C Caution mode . . . . . . . . . . . . . . . . . . Checking backup and restore . . . . . . . Code conventions . . . . . . . . . . . . . . . Cold Backup and Restore setup wizard Cold_Backup_Restore.msi le . . . . . . Command line entry conventions . . . . Conventions Caution icons . . . . . . . . . . . . . . . . . Code . . . . . . . . . . . . . . . . . . . . . . . Command line entries . . . . . . . . . . File contents . . . . . . . . . . . . . . . . . Names . . . . . . . . . . . . . . . . . . . . . Note icons . . . . . . . . . . . . . . . . . . . Revisions . . . . . . . . . . . . . . . . . . . Syntax denitions . . . . . . . . . . . . . Values . . . . . . . . . . . . . . . . . . . . . . Warning icons . . . . . . . . . . . . . . . . D Database backup . . . . . . . . . . . . . . . . Deployment considerations MS SQL Cold Backup and Restore Utility . . . . . . . . . . . . . . . . . . . MS SQL Hot Backup and Recovery Utility . . . . . . . . . . . . . . . . . . . Distribution media MS SQL Cold Backup and Restore Utility . . . . . . . . . . . . . . . . . . . . 4-12 . . 4-1 . . 5-1 . . 4-1 . . . . . . . . . . . . . . . . . 5-6 4-18 .. 7 . 4-3 . 4-3 .. 7 . . . . . . . . . . . . . . . . . . . . 6 7 7 7 6 6 6 8 6 6
MS SQL Hot Backup and Utility . . . . . . . . . . . Documentation . . . . . . . . . Online help . . . . . . . . . . Organization . . . . . . . . . Printable les . . . . . . . . F
Recovery ........ ........ ........ ........ ........
. . . . .
. . . . .
5-2 . 9 . 9 . 5 . 9
File contents conventions . . . . . . . . . . . . . 7 I Icon conventions . . . . . . . . . . . . . . . . . . . 6 iman_prolevars.bat le . . . . . . . . . 5-6, 5-8 Installation prerequisites MS SQL Cold Backup and Restore Utility . . . . . . . . . . . . . . . . . . . . . 4-2 MS SQL Hot Backup and Recovery Utility . . . . . . . . . . . . . . . . . . . . . 5-2 Installing MS SQL Cold Backup and Restore Utility . . . . . . . . . . . . . . . . . . . . . 4-1 MS SQL Hot Backup and Recovery Utility . . . . . . . . . . . . . . . . . . . . . 5-3 Integrated backup . . . . . . . . . . . . . . . . 1-10 Integrated backup modes . . . . . . . . . . . . 1-2 L Log les for backup and restore . . . . . . 4-18 M Manual organization . . . . . . . . . . . . . . . Manual set . . . . . . . . . . . . . . . . . . . . . . MS SQL Cold Backup and Restore Utility Deployment considerations . . . . . . . . . Distribution media . . . . . . . . . . . . . . . Installation prerequisites . . . . . . . . . . Installing . . . . . . . . . . . . . . . . . . . . . Preinstallation tasks . . . . . . . . . . . . . Reinstalling . . . . . . . . . . . . . . . . . . . . Uninstalling . . . . . . . . . . . . . . . . . . . MS SQL Hot Backup and Recovery Utility Alternate method . . . . . . . . . . . . . . . . . 5 . 9 4-1 4-1 4-2 4-1 4-2 4-6 4-8 5-9
ENG00015 C
Index-1
Index
Blobby mode . . . . . . . . . . . . . . Caution mode . . . . . . . . . . . . . Deployment considerations . . . . Distribution media . . . . . . . . . . Installation prerequisites . . . . . Installing . . . . . . . . . . . . . . . . Normal mode . . . . . . . . . . . . . . Obtaining database and volume information . . . . . . . . . . . . . Preinstallation tasks . . . . . . . . Read-Only mode . . . . . . . . . . . Repairing installation . . . . . . . Setting Teamcenter modes . . . . Uninstalling . . . . . . . . . . . . . . XML les . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
5-7 5-6 5-1 5-2 5-2 5-3 5-7
R Read-Only mode . . . . . . . . . . . . . . . . . . 5-7 Reinstalling the MS SQL Cold Backup and Restore Utility . . . . . . . . . . . . . . . . . . 4-6 Restoring data . . . . . . . . . . . . . . . . . . 4-17 Revision conventions . . . . . . . . . . . . . . . . 6 RMAN, see Oracle Recovery Manager S SFR, see Single le recovery Single le recovery . . . . . . . . . Object model . . . . . . . . . . . . Rich client interface . . . . . . . Single le recovery modes . . . . Software requirements, MS SQL Source for restore . . . . . . . . . . Syntax denition conventions . . U . . . . . .. .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 . 2-2 . 2-3 . 2-3 . 4-1 4-17 .. 8
5-55-6 . . . 5-2 . . . 5-7 . . . 5-4 . . . 5-6 . . . 5-4 . . . 5-8
N Name conventions . . . . . . . . . . . . . . . . . . 6 Normal mode . . . . . . . . . . . . . . . . . 5-75-8 O Online help . . . . . . . . . . . . Oracle Recovery Manager . Benets . . . . . . . . . . . . Features . . . . . . . . . . . . Organization of the manual
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. 9 3-1 3-2 3-1 . 5
Uninstalling MS SQL Cold Backup and Restore Utility . . . . . . . . . . . . . . . . . . . . . 4-8 MS SQL Hot Backup and Recovery Utility . . . . . . . . . . . . . . . . . . . . . 5-4 V Value conventions . . . . . . . . . . Virtual Device Interface (VDI) . Volume backup and restoration Volumes backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 6 5-11 5-11 4-12
P Preinstallation tasks MS SQL Cold Backup and Restore Utility . . . . . . . . . . . . . . . . . . . . . 4-2 MS SQL Hot Backup and Recovery Utility . . . . . . . . . . . . . . . . . . . . . 5-2
Index-2
ENG00015 C

Backup and Recovery

Загружено:

Сведения о документе

Исходное описание:

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Backup and Recovery

Загружено:

Авторское право:

Доступные форматы

Teamcenter 2005 SR1 engineering process management Teamcenter Engineering Backup and Recovery Help

Publication Number ENG00015 C

Publication Number ENG00015 C

Teamcenter Engineering Version 9.0 2005 (10.0) 2005 SR1

Publication Date December 2003 September 2005 June 2006

This edition obsoletes all previous editions.

Backup and Recovery Help

Backup and Recovery Help

Backup and Recovery Help

Note, Caution, and Warning Icons

Names and Values

Backup and Recovery Help

Command Line Entries, File Contents, and Code

The conventions are:

Backup and Recovery Help

Following are examples of correct syntax for the harvester_jt.pl: command:

Backup and Recovery Help

Teamcenter Engineering Documentation

Software Copyright and Trademark Notices

Backup and Recovery Help

Backup and Recovery Help

Backup and Recovery Help

Blobby Volume Mode

Backup and Recovery Help

Single File Recovery (SFR)

Backup and Recovery Help

Single File Recovery (SFR)

This chapter describes Teamcenter Engineering single le recovery.

Backup and Recovery Help

Single File Recovery (SFR)

Single File Recovery Object Model

Figure 2-1. Single File Recovery Object Model

Backup and Recovery Help

Single File Recovery (SFR)

Single File Recovery in Teamcenter Rich Client

Read-Only Mode Normal Mode BlobbyVolume Mode

Single File Recovery

Backup and Recovery Help

Recovery Management Backup Recommendation

Benets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

Backup and Recovery Help

Recovery Management Backup Recommendation

This chapter describes recommendations for recovery backup management.

Backup and Recovery Help

Recovery Management Backup Recommendation

Includes all data blocks, regardless of whether they contain data.

Backup and Recovery Help

Recovery Management Backup Recommendation

Does not include any reporting functionality.

Backup and Recovery Help

Recovery Management Backup Recommendation

Corrupt block detection During backup:

Backup and Recovery Help

Installing and Using the Cold Backup and Restore Utility

Verifying Backup and Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19

Backup and Recovery Help

Installing and Using the Cold Backup and Restore Utility

Installing the Cold Backup and Restore Utility

Backup and Recovery Help

Installing and Using the Cold Backup and Restore Utility

Prerequisites and Settings Checklist

Backup and Recovery Help

Installing and Using the Cold Backup and Restore Utility