场景:早上来上班,突然发现COGNOS服务器挂掉了,比如硬盘彻底坏掉了,不能恢复了,那该怎么办?前提是肯定要有备份啊。
备份内容:
A:FM模型备份OK
B:Cognos内容库备份OK
恢复过程:
1:首先在一台服务器上把备份的数据库还原过来
2:在一台电脑上面装一个Cognos Server,版本最好和之前保持一致,或者更高.打开cognos configuration,新建内容库,内容库配置为原来还原过来的内容库
配置成功,启动服务
在做过了上面的操作之后,进入Cognos connection中我们大概可以看到之前的报表内容了,如果没有做权限认证的话
那么如果如何恢复做了权限认证的cognos服务器呢?比如恢复用户,恢复个人文件夹下面的东西
3:为cognos配置第三方用户认证,无论是ldap,还是cjap的认证方式,最好和原来的认证方式保持一致
4:保证认证空间的ID和之前的保持一致,保证用户ID和之前的用户ID保持一致
5:如果恢复的时候认证空间的ID和之前的不一样,那么系统会添加新的ID原来的ID也还是存在的,之后改为原来ID即可,特贴出一段启动日志
[Launching a JVM using 'Maximum memory in MB']
Successfully launched a test JVM with the memory setting of '768'. Note that this does not guarantee that the IBM Cognos service will start and run successfully.
To see which JVM options are based on this setting, view ibmcognos_location/bin/bootstrap_<OS>.xml and see your JVM documentation for an explanation of those options.
[Start Service]
17:45:00, 'LogService', 'StartService', 'Success'.
17:45:01, CAF input validation enabled.
17:45:01, CAF Third Party XSS checking disabled.
17:46:16, CM-SYS-2215 A Content Manager internal PRECACHEINITACTIONS task started.
17:46:17, CM-SYS-2216 A Content Manager internal POSTINITACTIONS task is complete.
17:46:17, CM-SYS-5104 Content Manager detected the unconfigured security namespace "SZCH" (ID "SZCH") in the content store database.
17:46:18, CM-SYS-5100 Content Manager has added security namespace "SZETYY" (ID "SZERYY") due to a configuration change.
17:46:18, CM-SYS-2215 A Content Manager internal CMUPGRADESCRIPT task started.
17:46:16, CM-SYS-2216 A Content Manager internal PRECACHEINITACTIONS task is complete.
17:46:17, CM-SYS-2215 A Content Manager internal POSTINITACTIONS task started.
17:46:19, 'ContentManagerService', 'StartService', 'Success'.
17:46:19, CM-SYS-5159 Content Manager is running in active mode.
17:46:20, DPR-DPR-1002 Successfully registered the dispatcher http://wangxuejing:9300/p2pd in Content Manager.
17:46:25, Start a CAM_LPSvr because the active process count 0 is less than the limit 1.
17:46:27, 'camAsyncService', 'StartService', 'Success'.
17:46:45, 'BatchReportService', 'StartService', 'Success'.
17:46:44, 'Fragment Server Service', 'StartService', 'Success'.
17:47:30, 'QueryService', 'StartService', 'Success'.
17:49:34, 'QueryService', 'StartService', 'Success'.
17:49:34, 'SystemService', 'StartService', 'Success'.
17:49:39, 'RepositoryService', 'StartService', 'Success'.
17:49:39, 'BUX Service', 'StartService', 'Success'.
17:49:48, 'GraphicsService', 'StartService', 'Success'.
17:49:48, 'ReportDataService', 'StartService', 'Success'.
17:50:07, 'PresentationService', 'StartService', 'Success'.
17:50:07, 'CacheService', 'StartService', 'Success'.
17:50:07, 'ContentManagerCacheService', 'StartService', 'Success'.
17:50:07, 'IBM Cognos Enhanced Search Service', 'StartService', 'Success'.
17:50:07, 'camAsyncAA', 'StartService', 'Success'.
17:50:07, 'idVizService', 'StartService', 'Success'.
17:50:07, 'relationalMetadataService', 'StartService', 'Success'.
17:50:12, 'IndexSearchService', 'StartService', 'Success'.
17:50:12, 'JobService', 'StartService', 'Success'.
17:50:12, 'HumanTaskService', 'StartService', 'Success'.
17:50:12, 'IndexUpdateService', 'StartService', 'Success'.
17:50:12, 'AnnotationService', 'StartService', 'Success'.
17:50:12, 'AgentService', 'StartService', 'Success'.
17:50:12, 'IndexDataService', 'StartService', 'Success'.
17:50:12, 'ReportService', 'StartService', 'Success'.
17:50:12, 'DimensionManagementService', 'StartService', 'Success'.
17:50:12, 'MonitorService', 'StartService', 'Success'.
17:50:12, 'DeliveryService', 'StartService', 'Success'.
17:50:14, 'EventService', 'StartService', 'Success'.
17:50:14, 'MetadataService', 'StartService', 'Success'.
17:50:16, 'CPS Producer Registration Service', 'StartService', 'Success'.
17:50:20, 'Dispatcher', 'Start', 'Success'.
黄色和绿色的翻译是:
17:46:17,cm-sys-5104内容管理器检测到未配置安全空间”szch”(ID为“szch”)在内容存储数据库。
17:46:18,cm-sys-5100内容管理增加了安全空间”szetyy”(ID为“szeryy”)由于配置更改。
要注意的是如果想要恢复原来的用户体系,用户权限,个人文件夹等内容,则恢复的时候必须保持Namespace ID和原来的ID保持一致。
效果1:原来的管理员还存在系统中
效果2:原来用户的个人文件夹也被恢复了
效果3:报表可以正常执行