Over the recent month or so, our ServiceDesk CABI experts have dealt with several issues in regards the core ServiceDesk CABI Universe and Derived Universes.
We thought we would pass on simple best practices and ideas that all CABI clients should follow. These steps could be become "live savers" if issues occur with the CABI Universes
1. Regularly take a backup of CABI server's file system AND the CABI CMS databas backup. You must ensure that you have both since having one and not the other will not help in a restore/recovery process.
2. Before importing or exporting Universes via the CABI Designer utility, take a backup of this directory on the CABI server: C:\Users\<Your User Name>\AppData\Roaming\Business Objects
3. Perform a BIAR file backup using the Import Wizard utility regularly. This will ensure that your reports are protected without having to depend on DBAs or system admins for backups/restores. When performing a BIAR backup, ensure you select the 'Import All Instances' option. This way all of your scheduled reports and history gets exported to the BIAR file. If you do not select this option, you will only export the latest copy of the report.
For those of you who would like additional information and like reading :smile, attached to this post is a document from SAP regarding best practices for backup and recovery of BOXI/CABI.
By following these best practices, you will be in a much better position to recover from any CABI/BOXI issue.
As always, if you have any further questions or need assistance, do not hesitate to contact CA Support.