443 Chapter7.Planning for High Availability in the Enterprise

Planning for High Availability in the Enterprise
Lesson 1:  Assessing Database Availability Requirements
1. Calculating Availability
(1)  A = (F – ( MR + R )) / F
 A: Availability
 F: Mean time between failures
 MR: Mean time to recognize
 R : Mean time to repair
(2) Availability is determined by how quickly you can recover a system after it has suffered a failure. Some people call this disaster recovery. Recovering a system form a failure is both disaster recovery and high availability.
2. High Availability Framework
(1) A basic roadmap for availability that can be found with the framework.
 
3. Availability Requirements
(1) Gather availability requirement is the first step of planning any availability architecture. However, this is the most difficult element in the entire process. The difficulty is in trying to obtain realistic availability requirements.
(2) The interview process that you go through should result in the following pieces of information for each application.
 Average number of users affected
 Type of user affected: internal or external
 How the application is used
 Which segment of the biz is affected
 What percentage of overall biz operation is affected
 Maximum amount of time the application can be offline before the biz is irreparable damaged.
4. Barriers to Availability
(1) Process failure
 The first level of protection is controlling physical access to machines
 The second level of protection is controlling physical access to the server room
 The third level of protect is change control, which is one of the most-often overlooked processes within an IT environment Change control processes exist to ensure that any change to an OS is tested as well as documented. You should test all service pack and hot fixes to ensure compatibility with your system configuration. There are two paths for changing control: planed and emergency.
(2) User Errors. User errors are the second most common cause of system being offline. This is the most difficult category of availability issues to resolve because user errors are not technical issues. The only solution to this type of problem is to restore a backup to a secondary server, extract the data, and merge it back into the database.
(3) Natural and Man-made Disasters
 Tornadoes
 Hurricanes and typhoons
 Earthquakes
 Tidal waves and tsunamis
 Volcanic eruptions
 Fires
 Lightning
 Floods
 Nuclear explosions and meteors
(4) Hardware Failure
(5) Software Failure
(6) Network Failure
(7) Security Failure
5. Cost of Downtime
(1) The total cost of downtime is determined for each application within an environment. This value is derived by evaluating the percentage of the total revenue for which a particular application is responsible.
(2) Calculating downtime cost for applications that are directly responsible for generating revenue is reasonably straightforward.
(3) Cost of downtime for applications that do not directly generate revenue but support biz operations are a bit more difficult to calculate.
(4) After you have the figures for the downtime cost, multiply them by a factor of 3.
(5) By factoring all the intangible aspects – such as loss of image, bad publicity, potential loss of staff, etc – you can better evaluate the costs associated with not having systems available.
6. Budget Restrictions


Lesson 2:  Design Database Storage
1. RAID Configurations
(1) RAID 0
 
(2) RAID 1
 
(3) RAID 5
 
(4) Mirror of stripes
 
(5) Stripe of Mirrors
 
(6) SAN Configuration. You can configure a SAN with any combination of RAID levels previous discussed. You can also configure the storage within the array by using either a file system approach or a full disk approach.
(7) File system configuration. In file system configuration, small portions of many disks drives are combined together into a storage unit, which is then presented to the OS as if it were a single disk drive.
 
(8) Full disk configuration. You can construct a full disk configuration by configuring one or more disks in their entirely into a storage unit.
 
2. Tempdb Placement
(1) The tempdb database is considered by many to be a “throwaway” database. Although you should nerver use tempdb to store persistent data because it is lost when the instance is restarted, it is still critical to the operation of a SQL Server.
(2) If the storage array of a user database were to fail, the database on that storage array would be affected. However, all other database would still be accessible. If the storage array for tempdb or any system databases fails, the entire instance of SQL Server becomes unavailable.
(3) At a minimum, you need to place tempdb on a storage array that has minimum redundancy, such as RAID 5 array.
(4) If tempdb becomes a bottleneck within the system, you should move it to a dedicated storage array to reduce the disk connection.
3. Filegroups
(1) Filegroups are the most overlooked structure within a database.
(2) Add filegroup and move tempdb database

Lesson 3:  Planning a Database Migration Strategy
1. Standby Categories
(1) You can have three different categories of standby technology: hot, warm and cold. The standby category that a particular technology fits into does not have to do with the following:
 Time
 Proximity
 Scalability
 Complexity
 How fast the failover operation is
(2) Cold standby. Is not relevant for high-availability architectures. This is a spare server that you can employ if the primary server fails. It does not necessarily have any software installed or hardware configured and is not receiving any updates or data
(3) Warm standby. If it requires a manual process to fail over. Even if a technology automatically detects an error, if the technology does not have a built-in mechanism to automatically fail over, it is a warm standby
(4) Hot standby. Provides automatic failure detection as well as an automatic failover.
(5) Sample
Mirroring operation state Standby category
High performance Warm  standby
High protection Warm standby
High availability Hot standby
If witness unavailable Warm standby
2. Process Change
(1) The most significant step that can be taken for availability is to continuously evaluate and make improvements to processes and operational procedures.
(2) Continuously reviewing and monitoring security helps ensure that database don’t become unavailable because of security breaches.
 Implement DDL triggers to notify an administrator any time a permission is granted or revoked directly using a GRANT statement or indirectly through role membership
 Implement DDL triggers to notify administrators when logins, database users, schemas, or certificates are created, modified, or dropped.
 All DDL events that enable encryption should trigger a notification so that DBAs can ensure that the proper master keys and certificates are backed up as well as created on any standby system
(3) Tracking the creation, alteration, or deletion of any object within your SQL Server instances ensure that DBAs are always aware of any changes to databases and can address unauthorized changes immediately.
(4) If you do not have change control processes in place, you need to implement at least a system to document the changes as a first step. Your change control procedure needs to undergo periodic review to ensure that current procedures still meet biz objectives.
(5) At a minimum, you need to review all processes and procedure within your environment that allow high availability to occur every three months.
(6) Database backups need to be periodically reviewed to ensure that restore operations can still occur within an acceptable time frames.
3. Technology Implementation
(1) Deploy a log shipping or database mirroring solution
(2) Replication solution
(3) Failover clustering solution
(4) A migration cannot be started unless you already have very detailed documentation. Detailed documentation that lists all the security accounts, security settings, configuration options, databases, instance-level objects, DTS packages, SSIS packages, remote/linked servers, and so on have to be compiled

 

转载于:https://www.cnblogs.com/yang_sy/archive/2009/04/16/1437397.html

Lattice FPGA 开发工具Diamond使用流程总结——工具使用 本文介绍了一般的Diamond开发流程,包括工程创建、文件输入、IP使用、约束、管脚分配、和布线布局等流程 阅读详情

相关推荐

华为云Stack交付实战:从工勘到上线的全流程拆解

本文详细拆解华为云Stack交付全流程,从项目启动、工勘、LLD设计到硬件部署和软件安装,提供实战技巧与避坑指南。重点解析华为云Stack交付流程中的关键环节,如标准化工具使用、规范化文档管理和流程化协作,帮助团队高效完成从工勘到上线的复杂项目交付。

weixin_29243063的博客 157

177.Agent-LangGraph-MCP的构成说明

MCP架构通过MCP主机、客户端与服务器的协同,实现工具、资源与提示词的统一管理。MCP服务器提供Tools、Resources、Prompts能力,MCP客户端则负责发现、调用与读取,使Agent可按需获取上下文。其核心在于将工具从Agent中抽离,封装为可复用的服务,提升灵活性与可维护性,推动AI应用高效协作。

计算机王的博客 315

机械臂的运动学分析-工业机器人

机械臂的运动学是研究机械臂各连杆坐标系之间的运动关系,是对机械臂进行运动控制的基础。本章分析了所设计的六自由度机械臂的运动学。理论上六自由度机械臂的工作空间是一个近似球形区域,能够覆盖机械臂所在的位置,但由于机械臂关节的运动范围受到限制,机械臂末端会存在一些不能到达的工作死区,使得机械臂的工作范围和灵活性受到限制。理论上六自由度机械臂的工作空间是一个近似球形区域,能够覆盖机械臂所在的位置,但由于机械臂关节的运动范围受到限制,机械臂末端会存在一些不能到达的工作死区,使得机械臂的工作范围和灵活性受到限制。

qq_59137727的博客 6650

Docker Compose:搭建本地多服务开发环境

从一个 Java API、PostgreSQL 和 Redis 开始,配置服务名、端口、环境变量、健康检查、数据卷和依赖关系。理解 Compose 文件如何被解析、项目如何隔离,以及哪些数据不能依赖“重建容器”保留,能够把个人开发环境整理成团队可复用的启动入口。

m0_62221377的博客 478

Zephyr OS实战指南:从入门到精通物联网开发

本文提供了一份详尽的Zephyr OS实战指南,涵盖从开发环境搭建到物联网应用开发的全过程。文章详细介绍了如何利用Zephyr OS进行线程管理、设备驱动开发、低功耗设计以及蓝牙通信,并通过具体代码示例帮助开发者快速掌握这一专为物联网设备设计的开源实时操作系统,实现从入门到精通的跨越。

weixin_29201933的博客 547

疫情数据分析的“核武器”!JHU CSSE COVID-19数据集超深度解析与实战指南(附代码)

在面对这场没有硝烟的战争时,除了医护人员在前线与病毒搏斗,还有一群默默的英雄——数据科学家和分析师,他们利用手中的“数据武器”,昼夜不停地监测、分析、预测疫情走势,为政府决策、资源调配、公众科普提供了至关重要的支撑。同时,由于某些国家(如美国、加拿大、澳大利亚、中国等)的数据细化到省/州级别,为了得到国家层面的总数据,我们需要按国家和日期进行聚合。正是在这样的背景下,经过这些步骤,我们已经得到了一个包含了累计数据、每日新增数据和活跃病例数的完整数据集,可以开始进行深入的分析和可视化了!

wylee的博客 1167

AI全栈实战 | 3.9-01 爬虫入门:requests 加 BeautifulSoup 三分钟跑通,但 90% 的人栽在这 4 个“礼貌“问题上

⚠️:本文内容仅用于。请遵守目标站点的服务条款与相关法律法规,不得对目标服务造成负担,不得采集、传播个人隐私数据。技术是中性的,边界在你手里。爬虫的入门技术(requests 发请求 + BeautifulSoup 解析)三分钟就能学会。真正区分"会用爬虫"和"会做爬虫的人"的,是这篇我们跑通"请求→解析→存储"的最小闭环,然后重点把"合规与礼貌"这根弦给你绷上。

源码获取 | 运行部署 | 定制二开修改,如果回复不及时请耐心等待,请见谅。 445

Jetson nano 系列之2—板载摄像头IMX219启动

我选用的是亚博科技jetson nano的开发板。

驽马十驾,功在不舍;锲而不舍,金石可镂。 4276

spring boot 4集成SQLLite,及其SQLLite的建库

spring boot 4集成SQLLite,及其SQLLite的建库

weixin_41463944的博客 239

metahuman 下载材质 脸部灰白 脸部过亮

metahuman 下载材质 脸部灰白 脸部过亮

jacke121的专栏 247

HQChart实战教程54:Renko砖形K线图实现详解

Renko图(砖形图)起源于日本,只关注价格变动而忽略时间和成交量因素: 2.2 算法说明 初始化:使用第一根K线的收盘价创建第一个砖块 变动检测:计算当前价格与最后一个砖块的差值 砖块生成: 当价格变动≥砖块大小时,生成新砖块 当价格变动不足时,更新当前砖块的高低价 方向判断:根据价格变动方向确定砖块颜色 三、完整实现代码 四、Renko图的高级应用 4.1 动态砖块大小调整 4.2 Renko交易策略 三砖反转策略:趋势跟踪策略:本文详细介绍了Renko图的实现原理和在HQChart中的应

QQ_778132974的博客 875

【基于 WebSocket 的多用户网页五子棋】—— 数据管理模块

但行好事,莫问前程

qq_42996461的博客 260

CloudCompare 二次开发(17)——点云添加均匀分布的随机噪声

使用CloudCompare编程实现点云添加随机噪声。

点云侠的博客 840

OpenClaw 深度调查:把 AI 助手做成你自己的控制平面

对 openclaw/openclaw 的完整技术尽调:Gateway 架构、Agent 运行时、工具与沙箱、30 个消息通道、181 个插件、安全信任边界、工程代价与采用建议。17 章 / 10 张图,全部数字标注口径,数据截至 2026-10-31。

厚积薄发 363

LinePhone3.2.7(android端最新版本) sip客户端

SIP客户端For android:LinePhone3.2.7(最新版本),官网地址:http://www.linphone.org/

IEM模型,地表粗糙度模拟

利用微波反演土壤水分时候,利用IEM模型可以实现对随机地表的模拟

IDEA 简介:从零认识 IntelliJ IDEA

IDEA 全称,是由 JetBrains 公司开发的一款主流 Java 集成开发环境(IDE)。它集代码编辑、编译、调试、测试、版本控制、构建管理等功能于一体,被大量 Java 开发者视为日常开发的首选工具。所谓 IDE(Integrated Development Environment,集成开发环境),就是把写代码所需的各类工具整合到同一个界面中。相比只用文本编辑器加命令行编译,IDE 能显著减少重复操作,让开发者把精力集中在业务逻辑上。

ztI10的博客 187

Camera2Demo

在Camera2 的基础上进行封装,使得Camera2一堆初始化逻辑与Activity分离,降低耦合度,完成预览拍照并保存的操作

TransactionInactiveError:await 之后事务已经不活跃了

TransactionInactiveError 出现于 IndexedDB 事务已结束(非 active 状态)时调用 put、get 等操作。常见于 await 后或 setTimeout 中执行请求,因任务已完成,事务已提交或进入 finished 状态。请求必须在创建事务的同一任务中挂起,否则无效。解决方法:在 onsuccess 回调内同步发起后续操作,或提前将所有请求挂入事务。避免在异步上下文中使用事务操作,确保请求在事务活跃期内完成。

qq_40822000的博客 160

锂电池充电器电路设计 里面有电路

锂电池充电器电路设计 里面有电路 3.7V升压到5V电路设计。

Docker部署linkding:HTTPS与数据备份

部署私人书签库,除了让页面能够打开,还需要考虑几个实际问题:重建容器后数据是否保留、登录和保存是否正常、升级前怎样备份,以及出现 502 或 CSRF 错误时从哪里检查。本文使用 Docker Compose 部署 linkding,采用默认 SQLite 数据库,通过 Caddy 提供 HTTPS,并完成账户创建、数据持久化验证和备份。如果重建后账户或书签消失,应先检查是否换了项目目录、改了挂载路径,或者启动了另一套实例,不要急着重新初始化。遇到权限问题,应根据日志确认具体目录和运行用户,再调整权限。

tedcloud123的博客 194

云计算课程小组PPT汇报任务书

36人分为6组,每组6人;形式:生活案例调研 + 理论解读;汇报时长7‑9min;PPT建议10‑14页。

Michelle8023的博客 229

企业官网源码与数据资产交接:四项权利、五组自动检查

企业官网源码交接不仅要看压缩包,还要核域名、云资源、构建脚本、数据库恢复、权限与密钥。

sweetofmine1的博客 187

软件项目交付时,源代码之外还应该交付哪些技术资料?

软件项目交付时,除可运行程序外,还应核对源代码、数据库结构、接口文档、部署运维、测试验收和账号资产。本文从实际交付环节拆解完整资料清单,并说明合同如何约定交付范围、知识产权与维护边界。

chengduyoushu的博客 309

Java 项目实战:交友项目后台系统——网关统一鉴权与 B 端管理后台

本次改造通过引入SpringCloud Gateway实现网关统一鉴权与路由,新建mf-admin管理端复用C端域服务(Dubbo调用),实现管理员登录与用户管理四件查询。核心套路:网关白名单+双体系JWT(同工具不同payload)、管理端零直连业务库、分页形态区分(MySQL自动count/Mongo手动count)、浏览器端独立聚合。踩坑12条,附自检清单与后续改造方向,可复用于多角色后台系统。

Wang的专栏 73

大表 ALTER TABLE 怎么做?NineData OnlineDDL 配置与执行实践

介绍NineData OnlineDDL大表变更实践,涵盖执行策略、切表控制、拷贝批次与可视化进度追踪。

dbasenewbie的博客 296

Axum 初步入门学习笔记

)自定义错误实现后,可以直接作为Result的ErrAxum 是一个构建在 Tokio、Tower、Hyper 之上的 Rust Web 框架,核心能力是:Router 路由、Extractor 提取器、Tower 中间件、IntoResponse 响应机制、State 共享状态。那张分层架构图是“地图”不是“说明书”:它帮你建立全局观,但 Service、Repository、数据库、Redis、MQ 都是你自己在 Handler 内部调用的业务/基础设施层,不是 Axum 自带的。

weixin_43219667的博客 206

MySQL报Too many open files?句柄耗尽的排查与参数配置

文章讲清 max_connections 与 open_files_limit 两个额度、句柄被谁占走、分区表为什么最容易踩,给出从 error log 到 /proc/pid/limits 的定位顺序与句柄预算算法。

「一个在数据库赛道上边学边分享的学妹」——聚焦国产数据库/信创方向、分享学习笔记、踩坑经验和行业观察。 338

SQL Server 数据库双备份:简化配置,兼顾本地留存与异机归档

本文针对中小企业SQLServer数据库备份难题,提出简化配置与本地+异机双副本方案。传统原生备份依赖手动脚本,存在配置复杂、传输易中断、日志分散、静默失败等问题。推荐使用图形化工具实现备份、本地留存与异机同步一体化管理,支持断点续传、加密传输、自动清理与版本控制,降低运维负担。双副本策略提升数据安全性,本地快速恢复,异地防硬件故障。建议定期验证恢复流程,确保备份可用性。

2501_93776716的博客 314

Redis 入门详解:核心特性、重要文件与全局命令实战

本文系统介绍了Redis的核心特性、重要文件及全局命令。Redis凭借内存存储、C语言实现和单线程设计,具备极高的读写性能;支持持久化(RDB/AOF)、主从复制与集群架构,适用于缓存、排行榜、计数器等场景,但不适合存储海量冷数据。文中还解析了常见面试题,如为何快速、单线程原理、持久化机制、KEYS *禁用原因及过期键处理策略,强调其在高并发场景下的优势与局限。

2303_77004089的博客 208
上一篇: 443 Chapter6.Designing Database Security
下一篇: 443 Chapter9.Database Mirroring
aoding8407
博客等级 码龄11年 2粉丝 0原创
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符  | 博主筛选后可见
 
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付:10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值