09-13-2013 11:11 AM
we are trying to generate some client count and backup capacity historic reports. But we found all history got lost before the time we rebuilt the master. The master rebuild was caused by a diaster, we recovered full catalog and database. Is there any way we can fix it?
NBU master: HP-UX 11.31 IA64, 7.1.0.4
OpsCenter: 7.5.0.6 on windows 2008 R2, with OpCenter Analytics licensed.
thanks in advance
Solved! Go to Solution.
10-10-2013 07:19 AM
finally understand OpsCenter will only start holding data from first Sync with master and hold the time period which OpsCenter set on purge (420days by default). Without OPA license, this time period will only be 60 days.
For "search & hold" function, it talks to catalog throug index server instead of other DBs, it doesn't need OPA license.
thanks for all your help
09-13-2013 11:27 AM
From the OpsCenter Guide
Backing up the OpsCenter database
OpsCenter is shipped with a database backup script that performs backup of the
database without interrupting its operations, which is referred to as hot backup.
On UNIX as well as Windows platforms, the script overwrites existing database
(db) files before backing up or restoring the database. The database files are as
follows: vxpmdb.db, symcOpscache.db, and vxpmdb.log. The script backs up or
restores the vxpmdb.db, symcOpscache.db, and vxpmdb.log file (if it exists).
Note: Regular file system backups are not sufficient for backing up the OpsCenter
database. You must schedule periodic hot backups for the OpsCenter database to
avoid losing any important data.
Restoring the OpsCenter database
After you back up the database, you can restore it. On Windows and UNIX hosts,
the restore operation automatically stops the database, restores the backup
database files, and restarts the database. The dbbackup script overwrites existing
database (db) files before backing up or restoring the database. The database files
are as follows: vxpmdb.db, symcOpscache.db, and vxpmdb.log. The script backs
up or restores the vxpmdb.db, symcOpscache.db, and vxpmdb.log file (if it exists).
09-13-2013 11:41 AM
Thanks for reply.
We did rebuild and upgrade OpsCenter a few times and we assume the OpsCenter database should sync with master itself to catch up everything.
our issue looks not on OpsCenter itself. Looks after we rebuilt the master, then the OpsCenter only reported from this point.
09-17-2013 06:22 AM
Unless you have separate backup and restore of OpsCenter you will not get the old data back. It does not go back in time to 'sync with master'.
10-10-2013 07:19 AM
finally understand OpsCenter will only start holding data from first Sync with master and hold the time period which OpsCenter set on purge (420days by default). Without OPA license, this time period will only be 60 days.
For "search & hold" function, it talks to catalog throug index server instead of other DBs, it doesn't need OPA license.
thanks for all your help