Latest Blog Posts
When it comes to the cloud, banks, insurance companies, wealth management firms, and the like have been a little late to the party. It’s not that the financial services industry isn’t big on adopting new technologies. After all, this is the industry that introduced ATMs back in 1969 and is driving today’s proliferation of mobile payment options.
Between the educational resources provided by IT services vendors, pushes by government agencies, and the media’s reporting on the negative effects of manmade and natural disasters on some of the most well-known companies, there’s been almost a full-court press to get companies to make DR planning a priority.
There are many business and tech blogs and articles on the topic of “words not to use” — those cringe-inducing, over-used industry buzzwords. Many of them are often not reflective of what the company using them does or delivers. That’s the case with “white glove treatment.” It’s a phrase you probably hear a lot from IT service providers.
On February 23, the Technology Executives Club®, a leadership community for executives committed to driving corporate growth through technology innovation, hosts the Cyber Security & Risk Management for CIOs and Technology Leaders Summit – 2017 in Chicago. Billed as “not just another CISO event,” the event promises to provide actionable, practical IT security strategies and frameworks for CIOs and senior technology executives.
Nothing lasts forever, including servers. The dilemma for IT professionals is what to do with them as they near the end of their lifespan.
While security fears remain among the leading obstacles to cloud adoption, the regulatory and governance requirements specific to many industries also play a role. After all, the failure of a company’s IT infrastructure to comply with those requirements could put it at risk for costly penalties and fines, as well as do irreparable damage to its brand and reputation.
Given the stringent IT security controls associated with many regulatory requirements and industry standards, you’d think that compliance with those requirements and standards would signify that an organization is operating a highly secure IT environment and its data is well protected. In some cases, that’s true…but not always.
It’s one thing to talk about moving to the cloud; it’s another to do it. As one of US Signal’s customers noted, data migration is not a matter of “packing up a truck and moving.”
IT staffs have their hands full staying on top of constantly changing technologies, keeping their user base happy (and equipped with the latest applications, software, and updates), and just maintaining normal day-to-day IT operations. Managing the security and compliance of their organizations’ IT infrastructure consumes even more time and can add greater complexity. Many companies lack the in-house expertise to battle constantly emerging security threats or to keep pace with new or changing regulatory requirements.
There are always “those” projects — the ones you try to plan for but often find you really don’t have the time or in-house expertise to take on. Maybe it’s your initial foray into cloud computing, requiring the migration of a few workloads to a new cloud environment. Perhaps you’ve finally received budget approval for putting a DR plan in place. Or maybe you’ve been tasked with examining your entire IT environment to identify opportunities to improve operations.
If you read part 1, part 2, and part 3 of US Signal’s three-part blog series on data migration, you probably have a good understanding of what is involved in moving workloads to the cloud. As the 1968 hit by Marvin Gaye and Tammi Terrell says, however, “there ain’t nothing like the real thing.” You can’t fully understand all the in’s and out’s of a data migration project until you’ve been through one. Even then, the “gotchas” and “where-did-that-come-from’s” will vary from project to project.
In blog #1 and #2 of this three-part series, we covered what you need to think about prior to moving your data to the cloud and some of the methodologies to choose from for the data migration. Now it’s time to plan the move and execute it.