Skip to main content

Managing migration hell with Virtualization

Somewhere near the top of the list of activities that storage people like doing least is data migration. Slow, time-consuming, and often scheduled at convenient times such as 3 a.m. Sunday morning, it has to rank up there with tasks like disaster recovery testing and SAN reconfiguration. To make matters worse, the process often seems to be a prime candidate for Murphy's Law, often exceeding scheduled windows or needing to be rolled back and rescheduled due to unforeseen problems.

The methods used to perform migrations can vary considerably depending on what, where and how much data is being migrated, and in recent years, the number of technology options has increased significantly. In addition to traditional approaches (for example, host-based migration tools and like-to-like storage-array-based replication), a growing trend is toward applying virtualization technologies for data-migration purposes.

Virtualization appliances than sit in the SAN or LAN are one category of the new breed of data-migration tools that are quietly finding a place in environments where data migration is a regularly occurring activity. They can be leveraged to enable transparent data movement without affecting server data access. As a result, service outages are significantly shortened, with downtime only needed for the mounting, cutover and validation of the new storage targets.


Check out CW's opinion.
Labels:

Comments

Post a Comment

Popular posts from this blog

Security: VMware Workstation 6 vulnerability

vulnerable software: VMware Workstation 6.0 for Windows, possible some other VMware products as well type of vulnerability: DoS, potential privilege escalation I found a vulnerability in VMware Workstation 6.0 which allows an unprivileged user in the host OS to crash the system and potentially run arbitrary code with kernel privileges. The issue is in the vmstor-60 driver, which is supposed to mount VMware images within the host OS. When sending the IOCTL code FsSetVoleInformation with subcode FsSetFileInformation with a large buffer and underreporting its size to at max 1024 bytes, it will underrun and potentially execute arbitrary code. Security focus
Post a Comment
Read more

Splunk that!

Saw this advert on Slashdot and went on to look for it and found the tour pretty neat to look at. Check out the demo too! So why would I need it? WHY NOT? I'd say. As an organization grows , new services, new data comes by, new logs start accumulating on the servers and it becomes increasingly difficult to look at all those logs, leave alone that you'd have time to read them and who cares about analysis as the time to look for those log files already makes your day, isn't it? Well a solution like this is a cool option to have your sysadmins/operators look at ONE PLACE and thus you don't have your administrators lurking around in your physical servers and *accidentally* messing up things there. Go ahead and give it a shot by downloading it and testing it. I'll give it a shot myself! Ok so I went ahead and installed it. Do this... [root@tarrydev Software]# ./splunk-Server-1.0.1-linux-installer.bin to install and this (if you screw up) [root@tarrydev Software]# /op
Post a Comment
Read more