Moving data center from India to US

Wow, looks challenging and it's indeed.

So, we have finally decided to move our DR data center from India to US. The location I cannot disclose however its almost 50% of the original data center at Atlanta. The designing phase is over except for the data center power and cabling and I believe it happens given the short time frame of 45 days (don't laugh, it got extended by 6 months and I feel another 3 months more it deserves).

There are few things which I don't know why it happens every time we try to do something big.

1. Specification keeps on changing, regarding the list of applications for which we are building our DR.
2. RPO and RTO is not decided and simply we are doing an infrastructure DR not true DR. There is no BCP.
3. We are trying new technology Cisco UCS vs discrete Dell servers and going for full virtualization at DR. We are simply doing too many things and rather experimenting new technologies at data center.
4. How the data will get replicated was decided post design phase?

Technically, if there is any issue with the application we would be rather trouble shooting the technology that the actual issue.

The orders have been placed or in the process of getting placed. Some issues related to licenses is shooting the budget over the roof like oracle licenses for DR, whether to go for full DR license or get only replication license and in case of a DR move the licenses over to the other end.

Let see...

Comments

  1. Online Document ManagementFebruary 15, 2012 at 2:46 PM

    Thanks for nice blog.We can use data for file storage.We should have some idea of what it means to manage data files and overview idea of database storage schemes.You are right that this list of recycled ids should also be kept in storage that can be used if needed.

    ReplyDelete

Post a Comment

Popular posts from this blog

zpool and power path partial compatibility

Is power path fully supported with zpools, no. It's partial. You can have the pseudo devices assigned to a pool but it uses the native ctd disk only. Recently I lost 2 paths from the vnx array to m9000 server running Solaris 11.1. When I ran the zpool status -x command some of the pools were online while some of them were un available. Power path was reporting 2 paths only but it was active. So ideally the zpools should be online. But it's not. I enabled the remaining 2 paths and all became online. Internally the pools were pointing to one of the ctd devices that belonged to dead path and it was not coming online. Also few of the emcpower devices were renamed, so I had to do zpool import -d with the alternate disk. It seems power path is not completely supported now but may become in future.
Read more

Recoverpoint replication reporting with vmax splitter

Guys, Have you ever thought of automating the RP replication status and send status via email or post it to any reporting platform. Since the splitter impacts the VMAX FA's and there is an overhead of 13% on the utilization its good idea to see if the replication is driving the utilization of vmax FA. There are ways of pulling iops/read/write using symstat but its utilization (Director CPU utilization etc) which plays a significant role. As it crosses 80% we start seeing the increase in device response time. However, to measure FA utilization we will have to go through SMAS UI then pull out the reports. Its manual effort. But there is a way to automate it through REST API. You can get the details what type of objects are supported by pointing to : https://smc server :8443/univmax/restapi Coming to the point, getting recoverpoint consistency group status fully automated doesn't seems to be tough. Lets get through the steps. 1. Hash your SSH keys of the unix host to ...
Read more

Weird problem post power maintenance, no Powerpath pseudo name for Luns

We had the scheduled power maintenance activity in our data center. Every team was notified and we powered doen the servers through cron job. The servers were powered down first then storage (CX-380). And the reverse was followed during startup. After the power shutdown, the SAN was booted up. we forgot to disable the the snapshots. They were still active. Once it came up, the sessions were not there, but snapshot was active. Tried to deactivate the snapshot, failed with the error the "Failing Command: K10SnapCopyAdmin DBid 0 Op 1051. 71 00 80 43" Tried to create a session and attach the snapshot to the session, still unable to deactivate it, neither was able to attach to any other session. Looked at powerlink: It says the command issued to the snapshot is not owned by the SP. I trespassed all the snapshot source lun to SPA, and then tried to deactivate, nothing happened. Rebooted the SP's one by one through the management console. (http:/SP-IP/setup) Then I was able to...
Read more