Best Practices for Running Dassault SystÃ¨mes ENOVIA ... - Microsoft

More documents

Recommendations

Info

log is available, it is possible to get up-to-the-minute recovery and point-in-time restoreif the end of the transaction log is backed up and restored. The trade-off for the fullrecovery model is that it requires more administrator attention and a more complexbackup/restore strategy.Bulk-logged recovery model. For databases that have critical data, but for which theDBA wants to minimize storage or performance impact of bulk operations (e.g., bulkdata loads, table copies, index maintenance). It provides nearly the recovery power ofthe full recovery model but with some limitations.Simple recovery model. Appropriate if the data backed up is not critical, data is static ordoes not change often, or if data loss is not a concern for the organization. If an activedatabase is lost with the simple recovery model, the organization loses all transactionssince the last full or last differential backup. This model is typical for test environmentsor production databases that are not mission critical or have very light activity.In general, ENOVIA databases are frequently updated and hold information that is of highimportance to the organization. Especially for large ENOVIA databases, full backups may not befeasible with high frequency (e.g., daily or more often). For these reasons, Dassault Systèmesrecommends using the full recovery model with ENOVIA databases.Administrators must be aware of the management implications of the full and bulk-loggedrecovery models. In particular, under these recovery models, transaction logs must be backedup regularly to prevent them from filling up or exhausting available disk space.Ongoing ManagementThe following sections describe best practices for ongoing database management.The Database Backup PlanOne of the most important ongoing maintenance tasks for a business-critical database such asENOVIA is managing backups. Dassault Systèmes recommends you carefully plan, document,and test the backup and recovery strategy for the ENOVIA database.The types of database backups allowed in SQL Server 2008 are:Full database backup. Contains all the data in the database plus enough transaction loginformation to allow for recovering that data.Differential database backup. Contains all the data changed since the last full backup.Differential backups make it possible for a smaller, faster backup to be taken, which canlater be combined with the full backup to restore the database to the time of thedifferential backup.Transaction log backup. Contains all the database changes since the last (full ordifferential) database or log backup. Periodically backing up the transaction log lets yourestore the last database backup followed by subsequent log backups to recover to thelatest point in time needed.30
Database file or filegroup backup. Contains only data from specified file(s) orfilegroups(s) to allow quick, piecemeal restores if only part of the database is lost. Thesetypes of backup are not recommended for ENOVIA deployments.The different types of backup let you back up with the frequency appropriate to your businessrequirements, even if your databases are very large. A typical backup strategy for a largedatabase (for example, several hundred gigabytes) might include a weekly full backup, nightlydifferential backups, and transaction log backups every 30 minutes.If the database was lost, the DBA would:1. Perform a log backup if the log file is still accessible (this is referred to as a “tail of thelog” backup).2. Restore the last full backup.3. Restore the last differential backup.4. Restore all the transaction log backups since the last differential backup, in sequence.If properly executed, this returns the database to operation with at most 30 minutes of worklost.For small databases, it is perfectly valid to simply perform full backups once a day or even morefrequently. This approach is simple, but is practical only for databases that can be backed upvery quickly.It is important to remember that for databases using the full or bulk-logged recovery model,regular transaction log backups are required to keep the log from growing out of control.The right backup strategy depends on the database size and level of change activity in yourinstallation. This can vary greatly, even across deployments of ENOVIA, so there is no “one-sizefits-all”recommendation. However, keep the following in mind as you plan your backupstrategy:If you choose the full recovery model, the transaction log can grow very quickly andshould be scheduled for backup at multiple times throughout the day. Performingmultiple backups ensures that the log is truncated frequently and provides for improveddata recoverability.If you choose the simple recovery model, schedule full database backups for at leastonce per day. With this method, data recoverability is limited to the last full databasebackup.Database backups should be stored off site when possible and appropriate.Back up a database immediately after you make extensive changes or perform nonloggedoperations.31
Page 2 and 3: DisclaimerThis document is provided
Page 4 and 5: CHECKLIST .........................
Page 6 and 7: Best Practices for Running ENOVIA o
Page 8 and 9: installing the equivalent x64 (64-b
Page 10 and 11: It is important to note that for EN
Page 12 and 13: Note that in Figure 4, svc-EnoviaSq
Page 14 and 15: Dassault Systèmes ENOVIA is design
Page 16 and 17: Figure 8: Choose server collation f
Page 18 and 19: Note: While the startup for a stand
Page 20 and 21: Table 5: Tempdb FILEGROW increment
Page 22 and 23: Use Multiple, Dedicated DisksIf you
Page 24 and 25: Configure RAM on 32-bit Servers (V6
Page 26 and 27: Table 8: Recommendations for placem
Page 28 and 29: You should only take on the extra a
Page 32 and 33: Be sure to include regular backups
Page 34 and 35: fragmentation may occur depends on
Page 36 and 37: amount of time spent on this type o
Page 38 and 39: Note that if you are using a named
Page 40 and 41: Use the full recovery model for the
Page 42: Links for Further InformationFor ge

Best Practices for Running Dassault SystÃ¨mes ENOVIA ... - Microsoft

Create successful ePaper yourself

Delete template?

Save as template?