emc vmaxs10K 划盘容灾配置

1 在主存储划分磁盘

C:\Program Files\EMC\SYMCLI\bin>symconfigure -sid 111 -cmd "create dev count=1,size=218456,emulation=FBA,meta_member_size=54614,meta_conf

striped,config=TDEV,binding to pool VP_FC600_R53, preallocate size=ALL;" prepare

Execute a symconfigure operation for symmetrix ‘000298701526‘ (y/[n]) ? y

A Configuration Change operation is in progress. Please wait...

Establishing a configuration change session...............Established.

Processing symmetrix 000298701526

Performing Access checks..................................Allowed.

Checking Device Reservations..............................Allowed.

Validating configuration changes..........................Validated.

New symdevs: 05F4:05F7 [Thin Striped meta, head 05F4, member_size 54614 cyl]

Closing configuration change request......................Closed.

Terminating the configuration change session..............Done.

The configuration change session has completed successfully.

C:\Program Files\EMC\SYMCLI\bin>symconfigure -sid 111 -cmd "create dev count=1,size=218456,emulation=FBA,meta_member_size=54614,meta_conf=

striped,config=TDEV,binding to pool VP_FC600_R53, preallocate size=ALL;" commit

Execute a symconfigure operation for symmetrix ‘000298701526‘ (y/[n]) ? y

A Configuration Change operation is in progress. Please wait...

Establishing a configuration change session...............Established.

Processing symmetrix 000298701526

Performing Access checks..................................Allowed.

Checking Device Reservations..............................Allowed.

Initiating COMMIT of configuration changes................Started.

Committing configuration changes..........................Queued.

COMMIT requesting required resources......................Obtained.

Step 008 of 071 steps.....................................Executing.

Step 040 of 071 steps.....................................Executing.

Step 053 of 110 steps.....................................Executing.

Step 065 of 110 steps.....................................Executing.

Step 070 of 111 steps.....................................Executing.

Step 072 of 111 steps.....................................Executing.

Step 097 of 111 steps.....................................Executing.

Step 097 of 111 steps.....................................Executing.

Local:  COMMIT............................................Done.

Binding devices...........................................Done.

Allocating devices........................................Started.

New symdevs: 05F4:05F7 [Thin Striped meta, head 05F4, member_size 54614 cyl]

Terminating the configuration change session..............Done.

The configuration change session has successfully completed.

2  在备存储划分与主存储同样大小的磁盘

symconfigure -sid 222 -cmd "create dev count=1,size=218456,emulation=FBA,meta_member_size=54614,meta_conf=

striped,config=TDEV,binding to pool VP_FC600_R53, preallocate size=ALL;" prepare

Execute a symconfigure operation for symmetrix ‘000298701605‘ (y/[n]) ? y

A Configuration Change operation is in progress. Please wait...

Establishing a configuration change session...............Established.

Processing symmetrix 000298701605

Checking for reserved devices failed:

The operation failed because another process has the device reservation exclusive lock on the Symmetrix

Skipping reservation check

Performing Access checks..................................Allowed.

Checking Device Reservations..............................Allowed.

Validating configuration changes..........................Validated.

New symdevs: 0248:024B [Thin Striped meta, head 0248, member_size 54614 cyl]

Closing configuration change request......................Closed.

Terminating the configuration change session..............Done.

The configuration change session has completed successfully.

symconfigure -sid 222 -cmd "create dev count=1,size=218456,emulation=FBA,meta_member_size=54614,meta_conf=

striped,config=TDEV,binding to pool VP_FC600_R53, preallocate size=ALL;" commit

Execute a symconfigure operation for symmetrix ‘000298701526‘ (y/[n]) ? y

A Configuration Change operation is in progress. Please wait...

Establishing a configuration change session...............Established.

Processing symmetrix 000298701526

Performing Access checks..................................Allowed.

Checking Device Reservations..............................Allowed.

Initiating COMMIT of configuration changes................Started.

Committing configuration changes..........................Queued.

COMMIT requesting required resources......................Obtained.

Step 008 of 071 steps.....................................Executing.

Step 040 of 071 steps.....................................Executing.

Step 053 of 110 steps.....................................Executing.

Step 065 of 110 steps.....................................Executing.

Step 070 of 111 steps.....................................Executing.

Step 072 of 111 steps.....................................Executing.

Step 097 of 111 steps.....................................Executing.

Step 097 of 111 steps.....................................Executing.

Local:  COMMIT............................................Done.

Binding devices...........................................Done.

Allocating devices........................................Started.

New symdevs: 0248:024B [Thin Striped meta, head 0248, member_size 54614 cyl]

Terminating the configuration change session..............Done.

The configuration change session has successfully completed.

3  将划好的磁盘加入磁盘组

symaccess -sid 111 add -name node1_SG -type storage -devs 05f4

symaccess -sid 111 add -name node2_SG -type storage -devs 05f4

symsg -sid 111 show  node1_SG

symsg -sid 111 show  node1_SG

4  主备存储之间做SRDF

symrdf -g nodedg disable

symrdf set mode acp_disk -g nodedg

symrdf -g nodedg query

symrdf -sid 111 createpair -file c:\emcsrdf\addpair2_fwskjhcx.txt -type rdf1 -rdfg 8 -invalidate R2 -rdf_mod acp_disk -nowd -nop

### c:\emcsrdf\addpair2_fwskjhcx.txt内容为  05F4 0248

symld -sid 111 -g fwskjhcxdg  add dev 05F4

symrdf -sid 111 -file c:\emcsrdf\addpair2_fwskjhcx.txt establish -full  -rdfg 8

symrdf set mode async  -g fwskjhcxdg

完事

时间: 2024-12-13 06:24:32

emc vmaxs10K 划盘容灾配置的相关文章

GaussDB 200集群容灾管理

GaussDB 200的高可用容灾目标是在任何故障场景,数据不丢失,业务不停机.为达到这样的目标,GaussDB 200设计了双集群容灾的方案:分别部署两套同构的集群,集群间通过容灾任务进行周期性的物理数据同步.其中主集群提供正常的业务,灾备集群(亦称"备集群")在恢复期间不可用,非恢复期间提供只读服务.当主集群不可用时,灾备集群可以代替主集群正常提供业务,从而实现数据库的高可用.双集群容灾的约束限制见下图: 1.环境信息 如下图所示,两个同构集群环境(Gauss1和Gauss2)都是

存储容灾的相关限制

我们常常说存储容灾包括同城容灾和异地容灾,同时也包括同步容灾和异步容灾. 我们常说的同步容灾最大为100公里.该数值指的实际光纤长度是100公里,而不是物理距离,因为你不可能确保两个物理地之间恰巧有一根直线连接的光纤,一般经验中常选择的同步容灾站点物理距离在50-80公里之间.具体还需要根据应用对时延的要求和两地之间的实际测量时延为依据,100公里只是理论值. 存储的同步容灾只能在100公里的范围内实现.这是IT系统容灾界的标准法则. 该法则的计算理论依据为: 1)同步容灾需要任何一个I/O要同

容灾备份技术的分类概述

容灾备份技术在企业的数据丢失或者遇到了重大灾难的时候会发挥相当强劲的作用.企业完全可以不必担心由于数据丢失而无法正常运作.下面多备份带您一起了解一下容灾备份技术的具体分类. 一.选取容灾备份技术的依据 容灾备份的目的是确保灾难发生后业务立即恢复,应用功能能够尽快投入使用,采用的各种技术不论是数据备份,数据复制,还是容灾备份技术,无非都是围绕着业务连续来进行,这些技术是容灾备份的关键环节.衡量这些技术标准无非是RPO(恢复点目标)和RTO(恢复时间目标),也就是出现灾难的时候多长时间可以让业务继续

今日头条在消息服务平台和容灾体系建设方面的实践与思考

mPass 企业租户微服务开发平台 业务背景 今日头条的服务大量使用微服务,容器数目巨大,业务线繁多, Topic 的数量也非常多.另外,使用的语言比较繁杂,包括 Python,Go, C++, Java, JS 等,对于基础组件的接入,维护 SDK 的成本很高. 引入 RocketMQ 之前采用的消息队列是 NSQ 和 kafka , NSQ 是纯内存的消息队列,缺少消息的持久性,不落盘直接写到 Golang 的 channel 里,在并发量高的时候 CPU 利用率非常高,其优点是可以无限水平

甩掉运维黑锅,容灾部署如何该怎么做

现如今本地负载均衡技术已经解决服务器集群的高可用问题,但是断电.施工挖断光缆.自然灾害等依然可以导致整个数据中心无法工作.另外,中国网络由多家运营商组成,各运营商之间互联互通质量差已是不争的事实.因此大型互联网企业早已不满足于单一.或者双活数据中心提供网站服务,越来越多的互联网企业开始考虑在不同地区.不同运营商部署多个数据中心集群,以实现用户访问就近接入.负载均衡和故障容灾. 现如今本地负载均衡技术已经解决服务器集群的高可用问题,但是断电.施工挖断光缆.自然灾害等依然可以导致整个数据中心无法工作

容灾、备份、存储

百度词条---王建成解读 容灾:一般是异地,否则如何容得了灾?==>是不是本地.不同机房就不算容灾,究竟是地方还是技术本身才是关键? 经典语录:容灾系统是数据存储备份的最高层次. [数据级容灾]是指通过建立异地容灾中心,做数据的远程备份,在灾难发生之后要确保原有的数据不会丢失或者遭到破坏,但在数据级容灾这个级别,发生灾难时应用是会中断的.在数据级容灾方式下,所建立的异地容灾中心可以简单地把它理解成一个远程的数据备份中心.数据级容灾的恢复时间比较长,但是相比其他容灾级别来讲它的费用比较低,而且构建

主从集群搭建及容灾部署redis

redis主从集群搭建及容灾部署(哨兵sentinel) Redis也用了一段时间了,记录一下相关集群搭建及配置详解,方便后续使用查阅. 提纲 l  Redis安装 l  整体架构 l  Redis主从结构搭建 l  Redis容灾部署(哨兵sentinel) l  Redis常见问题 Redis安装 发行版:CentOS-6.6 64bit 内核:2.6.32-504.el6.x86_64 CPU:intel-i7 3.6G 内存:2G 下载redis,选择合适的版本 [[email prot

容灾与集群(1)

容灾与集群(1) 在上一篇:微软分布式云计算框架Orleans(1):Hello World,我们大概了解了Orleans如何运用,当然上一篇的例子可以说是简单且无效的,因为用了Orleans不可能只写一个Hello World吧,Orleans是为分布式和云计算而生的框架,那么今天我们就简单说一说容灾.集群.容灾与集群在Orleans中的运用. 集群是什么? 下面摘抄自百度百科: 集群(cluster)技术是一种较新的技术,通过集群技术,可以在付出较低成本的情况下获得在性能.可靠性.灵活性方面

跨园区容灾,升级不停服——高可用负载均衡集群实践

对于云计算行业来说,云服务的可用性和可扩展性是的检测其服务质量的重要标准,也是最受用户关注的两大难题.各云计算厂商针对容灾.升级等需求的解决方案,最能够体现其底层架构的实力.腾讯云基于基础架构的优势,为分期乐.微信红包等平台提供技术支持,可以完美满足如下三点需求: 1. 高可用能力,容灾能力强,升级不停服 2. 可扩展性强,功能丰富,性能超高 3. 避免重复造轮子,性价比之王 近期,针对一些客户对腾讯云产品可用性的问询,腾讯云基础产品团队对负载均衡产品的原理做出详细阐述,并希望通过对腾讯负载均衡