v6r2013与恢复学习目标在本模块结束时您应该能够.pdfVIP

Learning Objectives At of this module, you should be able to: Describe the best practices for data cement in ENOVIA V6 Describe the backup procedures for ENOVIA V6 Describe the main scenarios for failure and the associated recovery procedure Contents Data cement and Backup Backup Procedures Cold Hot Failure Scenarios and Data Restoration Loss of the Central Database (DB) Loss of the Central Data Store (FCS) Loss of a Remote FCS Loss of an Autonomy IDOL Server Loss of a 3D Index Server Recovery and Verification Tools Introduction S e it rests at the heart of a product development effort, the P ystem must be robust and secure for the IP that is stored in it To fulfill this requirement, hat ase of a machine crash or the loss of a disk drive, the data must be able to be restored as close as possible to when the crash occurred to minimize data loss Typically, the DATA and the BINARIES of an application are separated to allow for backup of the data without affecting the performance of the production system On the bottom of the next slide, the pieces of the ENOVIA V6 architecture which have volatile DATA S e the STORE DATA is tied inextricably to the Database METADATA, these must be backed-up nearly simultaneously because otherwise there will be STORE DATA that is no longer referenced by the METADATA or METADATA that points to non-existent STORE DATA V6 Multi-Tier Architecture Pr iple Webtop s n Ex.: ENOVIA Collaborative o i