• Back up Content
  • Back up Content
  • "acf5954c-94f2-4ed3-9e5f-3e1a0036ff76
  • A well-executed backup plan is your only defense against losing all your data in the event of a disaster. Your company's system administrator should review any backup and disaster recovery plan before it is implemented.
  • Any backup process should be evaluated against the following criteria:
  • Back up as often as you feel is necessary or your company dictates.
  • Back up frequency should be based on the amount of data you are willing to lose if disaster strikes.
  • Backups should be verified to ensure that the process was successful.
  • Backups should be tested periodically to ensure that data can be recovered.
  • There are different types of Development environment installations to consider when establishing a backup plan. These installation types are not mutually exclusive; a company's backup plan should address each type that is in use.
  • Single User Environment
  • The following items must be considered for a single user installation where the Developer and the content are installed on a local workstation:
  • Export the outline(s) you are currently developing on a daily basis.
  • Export your entire Library on a routine basis to backup all of your content.
  • Use backup software to backup your entire file structure on a routine basis.
  • Multi-user Environment
  • The following items must be considered for a multi-user installation where the Developer is installed on client machines and the Library is installed on a server:
  • Ensure that all content authors have checked in all documents.
  • Ensure that all content authors have logged out of the Developer.
  • Perform a routine backup of the SQL or Oracle database.
  • Encourage authors to back up their new and checked out documents by exporting the content.