这里会显示出您选择的修订版和当前版本之间的差别。
两侧同时换到之前的修订记录前一修订版后一修订版 | 前一修订版后一修订版两侧同时换到之后的修订记录 | ||
02-工程实践:cmdb:首页 [2020/07/06 16:47] – [mgr 测试] annhe | 02-工程实践:cmdb:首页 [2021/06/12 03:50] – [理论] annhe | ||
---|---|---|---|
行 1: | 行 1: | ||
====== CMDB ====== | ====== CMDB ====== | ||
+ | |||
+ | - [[.: | ||
+ | |||
+ | ## 理论 | ||
+ | |||
+ | 1. bmc Step-by-Step guide to build a cmdb | ||
+ | |||
+ | 打算自己开发自己的CMDB产品的话,个人建议可以参考以下的参考[文档](https:// | ||
+ | |||
+ | 1. 必读的规范文档 [《Configuration Management Database (CMDB) Federation Specification》](https:// | ||
+ | 2. BMC系列的 | ||
+ | 3. BMC的 《BMC_CMDB_Data_Modeling_Guide》 | ||
+ | 4. HP的uCMDB技术白皮书 | ||
+ | |||
+ | --- | ||
+ | |||
+ | 1. CMDB调研报告:https:// | ||
+ | 2. https:// | ||
===== iTop ===== | ===== iTop ===== | ||
+ | |||
+ | |||
==== 链接 ==== | ==== 链接 ==== | ||
* {{http:// | * {{http:// | ||
行 26: | 行 46: | ||
#### cron | #### cron | ||
- | 分别在 1,2 号节点部署 cron 任务,2号有报错日志: | + | 分别在 1,2 号节点部署 cron 任务,1号2号都可能有报错日志: |
``` | ``` | ||
ERROR: ' | ERROR: ' | ||
``` | ``` | ||
+ | |||
+ | > Please note, that in general this error is an expected behavior of Group Replication plugin, when it finds conflicting transactions on different nodes, if Multi Primary mode is used. Application should be able to handle this type of errors based on application logic. The following sections can only applied in those cases, when this error is caused by multiple updates on the same node. | ||
+ | |||
+ | 参考: https:// | ||
+ | |||
+ | 可能最好只在一个节点上运行 cron | ||
+ | |||
+ | - 升级响应时间 Task: | ||
+ | - 邮件发送,正常接收邮件,多节点跑cron未重复发送邮件。 | ||
+ | |||
+ | ### mysqldump | ||
+ | 全新安装,新增 4 个 Server 对象,一个 业务流程 对象 | ||
+ | |||
+ | 备份命令 | ||
+ | |||
+ | ``` | ||
+ | mysqldump --opt --skip-lock-tables --default-character-set=" | ||
+ | ``` | ||
+ | |||
+ | 恢复命令 | ||
+ | |||
+ | ``` | ||
+ | mysql -uroot -proot cmdb < itop.sql | ||
+ | ``` | ||
+ | |||
+ | 结论:未发现异常 |