To avoid a disaster or to go back in time, we must have the most recent copies of our data that includes the content store (database), configurations (cogstartup<date/time-stamp>.xml
), the cryptographic key directories, framework manager projects, images stored in web contents, logfiles, and so on.
Performing regular backups is mandatory, and it is the responsibility of the Cognos administrator to save backups of each of the preceding items in a secure place. The developers also need to have a backup copy of all their projects (packages and reports). This will prevent loss of data. Once a problematic machine is replaced, the data can be easily restored back to the server.
To back up the content store database, the DBA (Database Administrator) may schedule the backup depending upon the frequency required. The content store may also be automatically backed up and replicated if there is more than one Content Manager in the environment. Of course one Content Manager will be working...