Restoring Profits And Confidence With Big Data

October 12, 2012

“Retail and commercial banks should be simple and they should be boring,” Lloyds Banking Group’s chief executive said last week. “The industry must change,” António Horta-Osório told the CBI Scotland annual dinner.

Tempting as it may be for the capital markets to laugh at such navel gazing four years after the financial crisis began, Horta-Osório’s words ring true in electronic trading as well.

The market has been losing confidence in computerized trading, from the Flash Crash of 2010 through last month’s Knight Capital scandal, with many other indignities in between.

The financial services industry — including banks and the capital markets — does have to change, returning to fundamentals, as Horta-Osório advocates. But it must also look forward, preparing for future calamity and searching for new opportunities.

Taken By Storm

“A successful business must be thoroughly prepared for unexpected disasters,” wrote Bob Guilbert, managing director of marketing and products at Boston-based investment IT firm Eze Castle Integration. “Even just a few moments of downtime could be extremely costly, so it is essential that firms implement sound business continuity and disaster recovery procedures.”

Systematic protection of a firm’s data is more than a safety net. The business continuity plan (BCP) and disaster recovery (DR) systems that Guilbert discussed last week can safeguard a firm’s business and an industry’s reputation if disaster strikes.

“The one positive aspect of hurricanes and other weather-related disaster scenarios from a BCP perspective is that businesses typically have advanced warning of their arrival,” Guilbert said.

“A firm that is ill-prepared for inclement weather is going to face serious challenges when an unannounced incident, such as a building fire, occurs.”

Keeping such humdrum fundamentals strong will keep the industry’s foundation strong. And that can serve as a mighty launchpad for further, more exciting technological strides in the pursuit of new trading prospects.

Big Data Trading Strategy

Citi announced upgrades for its equity options algorithms in the U.S. last week, letting traders choose how forcefully to seek liquidity. Aggressive settings incline the algorithm to cross the spread during a trade, while milder settings tend toward mid-market orders and cross the spread less often.

Other market participants are looking to gain their advantage through high-frequency trading (HFT) technologies.

Some of these firms are seeking new trading opportunities via Big Data and complex event processing (CEP) technologies, alongside data analytics engines.

Part of the trick exploiting Big Data is to adopt solutions that provide insight without losing speed. The rest of the trick is to adopt those solutions without going broke. That not only keeps firms in business, it avoids another scandal that could further spoil the industry’s reputation.

On to the Basics

The U.S. Department of Treasury announced Sunday that it will sell half of its stake in AIG. The $18 billion sale means the end of the Uncle Sam’s four-year tenure as the New York firm’s majority shareholder.

This also means that the capital markets have a tremendous opportunity to demonstrate mastery of the basics. But that mastery will mean little without a responsible vision for the future.

So getting back to basics won’t be boring. It will require innovative strategies and technologies to weather storms and conquer new frontiers.

Thanks to http://blogs.sap.com/innovation/big-data/restoring-profits-and-confidence-with-big-data-017431


Gartner Report: Backup and Disaster Recovery Modernisation

June 7, 2012

55% of Gartner’s 2011 CIO Survey respondents are currently pursuing modernization, suggesting that the CIO focus enabled funding and implementation of IT DRM modernization.

Once considered an afterthought or a very expensive insurance policy for a low-probability event, IT DRM is increasingly becoming an important data center initiative and an ongoing optimization priority for many client organizations.

In this report, you will find a thorough analysis of Gartner’s findings from their 2011 CIO survey and Gartner’s business recommendations which include:

  • Invest in IT disaster recovery management (IT DRM) modernization to meet increasingly stringent business resilience requirements.
  • Invest in classifying applications and services based on mission-critical requirements to develop appropriate recovery tiers that balance risk mitigation with affordability.
  • Charter a backup modernization initiative to assess current recovery capabilities, scope present and future recovery requirements, and prepare enhancement service options to be addressed.
  • Look to deploy, or more fully deploy, recent proven backup products, such as incremental forever or synthetic full processing, de-duplication, server virtualization improvements, and snapshot and replication integration.

 


Gartner Report: Does Intergrated Backup and Archiving make sense?

May 28, 2012

“By 2015, only 15% of organizations will attempt to converge backup and archiving policies and processes, up from 5% today.”  – Gartner

Backup and archiving has long been thought of as complementary, yet few organizations have effectively implemented these technologies together. Deciding whether or not to unify backup and archiving is a tough decision that many organizations face. This complimentary Gartner research report outlines the pros and cons. You’ll learn the impacts of not implementing these technologies together effectively including:

  • Continuously increasing storage costs and increased governance risk
  • Failing to address users’ requirements
  • Not able to support legal, compliance and user objectives efficiently.

Check out the report to learn the top recommendations for integrated backup and archiving.


Cloud Security and offsite back up

May 3, 2012

When looking for an enterprise-class Cloud Backup solution, you’ll need to understand what you want to achieve and the elements that are important to your organization. It’s definitely more than just backing up your data. There are many software offerings in the marketplace that boast their ability to restore at lightening speeds, but what often appears to be missing in the equation is the inability to provide a guarantee that data is restorable in its full integrity.

Below are some things to consider when looking at cloud data protection solutions:

Your data has to be conditioned constantly to ensure restorability. The following factors can cause data corruption:

  1. Disc malfunction
  2. Disc controller malfunction
  3. Bad sectors on the disc
  4. File system corruption

You should ensure the following data integrity and consistency check functionality is embedded in the software to ensure, data restorability:

  1. Data consistency – this process should ensure that all the data components have been collected sequentially by the data collector at the enterprise customer’s premises before sending the data to offsite storage in the cloud.
  2. Data has arrived offsite before storage – the online data repository should write all the data being backed up offsite to a temporary location, checks and ensures that all the data has arrived before storing it.
  3. Restore validation – this is an actual restore simulation that conducts an actual data restore to a temporary location to ensure data restorability. Think of it as the data restore dry run to prepare for the actual disaster.
  4. Autonomic healing – this automated process will run in the background and scan storage in its entirety to ensure data integrity. Data that leaves your firewall should always be encrypted, the “Autonomic Healing“ process will check links between data blocks and compare digital signatures between different components for inconsistencies. When corrupted data is uncovered, it is noted and a notification is sent to the originating database to resend the portion of that data that was marked corrupted. This ensures that the data is always recoverable in its entirety in case of a disaster.

When you’re shopping for a data protection solution, inquire with your vendor to ensure that the functionality they provide will restore your data, not just during a Disaster Recovery (DR) drill but in the event of an actual disaster (accidently deleted file, damaged hard drive, machine loss or lost site). There’s a lot you can outsource to the cloud, but responsibility isn’t one of them. Make sure you do your research and due diligence before choosing a cloud data protection solution.

For further information ref cloud back up please contact C24 at www.c24.co.uk


The modernisation of backup

April 30, 2012

The data protection market has changed considerably over the past decade. There has been a fundamental shift away from relying solely on tape for backup and recovery to using cloud-based backup solutions to address challenges that include backup performance, reliability, and recovery time objectives.

With the proliferation of virtualised infrastructure, big data, the Consumerisation of IT, growth in remote and branch office data and the need for high availability, has introduced a new set of requirements for the software responsible for data protection and recovery.

While we’re in the cloud backup business, we understand the role tape may play as part of an overall backup strategy, especially for large enterprise organizations. With data that requires significant periods of retention; it makes sense to move backups onto lesser expensive devices – including tape.

With that being said, we don’t believe tape should be the primary method of backup for any organization of any size. There are significant drawbacks with using tape, especially in the SMB market where it is used as the primary means of backup. Here are some examples:

Limited Time for Backup

Tape is slow. It’s common to see once per day incremental or differential backups that follow a once per week full backups. Organizations don’t want to see backup operations significantly impact production resources, so these backup operations are pushed to the wee house of the morning and to weekends.

Slow Recovery

To put it bluntly, recovering from tape can be absolute hell. It’s slow, error-prone and can be difficult depending on the number of tapes for which data has to be recovered.

Equipment Challenges

It is not uncommon for tapes to be useable only in the drives that wrote the data in the first place with the software that did it. So, recovering with a new tape unit might not be possible.

Tape was once the de facto standard for backup and as a result of its many challenges and with functional needs increasing, the next generation of data protection and recovery options became available including both disk and cloud backup.

Here’s where I sell you on the cloud, right? Not quite, that’s the not the purpose of this post. I’m more interested in determining if you’re comfortable using outdated backup technology to keep your company going after disaster strikes? I also want to tell you that it’s important to modernize your data backup infrastructure if it is out of date.

How much of your business is at stake if you’re unable to recover your organization’s most important data assets after a disaster?

By looking at the marketplace, it appears that organizations of all sizes tend to be conservative when it comes to making large scale changes to backup infrastructure even though there are new processes and opportunities (deduplication, continuous data protection, incremental forever, etc.) that can be exploited to improve disaster recovery and streamlined operations.

I hope that by reading this post you’ll start to think more about your backup infrastructure. Interested in learning more about managed cloud backup services?

If you need further information please visit http://www.c24.co.uk


Its all about the recovery

April 4, 2012

Enterprises and vendors alike often focus so much on data backup that sometimes they forget about the reason that they backup the data. Customer’s focus should be on data Recovery not data backup.

All vendor solutions in the marketplace backup customer data but it requires real data stewardship to ensure that the data can be restored when needed. Over our 24-year history, Asigra has developed best practices around data stewardship to ensure data restorability if the customer looses a file, disk, machine or the entire facility.

The data has to be conditioned constantly to ensure restorability. The following factors can cause data corruption:

  1. Disc malfunction
  2. Disc controller malfunction
  3. Bad sectors on the disc
  4. Filesystem corruption

Access to metadata is not sufficient because bad sector on a disc can render metadata unreadable.

Following data integrity and consistency check functionality is embedded in Asigra software to ensure, data restorability:

  1. Ensuring data consistency – this process ensures that all the data components have been collected sequentially by the DS-Client (the data collector at the enterprise customer’s premises) before sending the data to the DS-System.
  2. Ensuring all data has arrived offsite before storage – Asigra’s DS-System (the online data repository) writes all the data being backed up offsite to a temporary location, checks and ensures that all the data has arrived before storing it.
  3. Restore validation – this is an actual restore simulation that conducts an actual data restore to a temporary location to ensure data restorability. Think of it as the data restore dry run to prepare for the actual disaster.
  4. Autonomic healing – this automated process runs on the DS-System in the background, scans the entire storage to ensure data integrity. Since the data at the DS-System is encrypted, the “Autonomic Healing“ process checks links between the data blocks, compares digital signatures between different components for inconsistencies. When corrupted data is uncovered, it is marked as corrupted and a notification is sent to the DS-Client to resend the portion of that data that was marked corrupted. This ensures that the data is always recoverable in case of a disaster.
  5. Backing up the DS-Client database to the DS-System – this ensures that if the DS-Client is lost it can easily be rebuilt with the appropriate backup structure.

When you’re shopping for a backup solution, please inquire from your vendor to ensure that the functionality they provide will restore your data, not just during a Disaster Recovery (DR) drill but in the event of an actual disaster (accidently deleted file, damaged hard drive, machine loss or lost site). If you require further information please contact C24 or visit www.c24.co.uk

 

http://www.blogdash.com/blogger_steps/blog_claim/blog_claim.png?s=4e342e624b346cff0fe9bccbc2cce61f


The Difference Between Backup and Replication

March 2, 2012

What’s right for your business – a data backup solution, replication or both? There are advantages and disadvantages to both.  This post will review the considerations that you need to make before reaching a decision on which approach is best for your business.

It’s important to determine your business objectives for choosing a replication or backup strategy and in order to do so, you’ll need a clear understanding around the differences between disaster recovery and business continuity.

Disaster Recovery (DR) is the process by which you resume business after a disruptive event. This could include a natural disaster, such as an earthquake or a hurricane, or could be something less significant, such as malfunctioning software caused by a computer virus.

Business Continuity (BC) describes the processes and procedures an organization puts in place to ensure that essential business functions can continue during and after a disaster. The goal is to prevent interruption of mission-critical services and to re-establish full functioning as swiftly and as smoothly as possible.

If your organization suffers from a failed RAID array or a geographical disaster, for example a hurricane hits one of your regional offices, and you were using a replication strategy with no “point in time” backup, you would be able to restore from replicated storage to get things up and running quickly – translating into seamless business continuance.

It is atypical for something like the above to happen, but it does occur. Let’s look at a few more likely scenarios as it relates to replication. Whenever humans are involved mistakes are bound to happen. If a user accidentally deletes a file from the primary server, the deletion will be replicated across all subsequent secondary and tertiary storage. Another example is that of a corrupted file at the primary site that is replicated – making it impossible to recover.

With more than 90% of restores stemming from user error (accidental deletion) and corruption rather than data loss, replication and snapshots can’t provide the level of protection that is required as part of a comprehensive BC/DR strategy.

Keeping alternative copies of data in multiple locations is a great idea, reducing the risk of data loss and potentially enabling enhanced access, but fails to address recovery point objectives or RPOs that are addressed with data backup—managing multiple historical copies of a data set.

With a proper backup procedure in place you can refer back to a point in time, for example, when the last scheduled backup was run. If  there are multiples sets of backup stored, you can refer back to a version of the file/database, before the corruption/deletion occurred.

Adding basic data protection techniques like snapshots or replication to a storage system doesn’t make it a backup solution. Replication can leverage storage capabilities, but a backup management solution will always be required for complete data protection.

Having both replication and a backup system in place is the ideal scenario – achieving both  high availability for business continuity and the ability to restore for a point in time backup, but it can be expensive.  If the ideal situation is cost prohibitive for your organization, the best solution is to utilize a service based on a backup platform that can create a virtual replica of your environment versus replication.


Common backup mistakes in virtualisation

December 15, 2011

Not Backing up Virtual Machines

Seems crazy, right? Failing to backup regardless of environment is an extremely risky proposition but generally, a majority of virtual machines aren’t backed up.

Here’s why:

  • Virtual Machine (VM) Sprawl: Most organizations don’t plan for enough storage when starting virtualisation projects and rarely consider rapid adoption and disaster recovery. Because virtual machines can be built with a few clicks of a mouse, they will be – especially in development labs for testing purposes, but also for full use in production environments. Often IT doesn’t have knowledge of all the VMs that exist or have knowledge but are unfamiliar with assets on their Recovery Point Objectives (RPO)/Recovery Time Objectives (RTO) requirements.
  • Backup Agents: The costs associated with backup agents can be prohibitive and quickly reduce the savings incurred through virtualisation. Every time a new backup software version is made available – there is usually an update required to every agent on every server.
  • Bandwidth Impact: There is often concern over dragging down the host machine and/or network by moving a lot of data for backup. The whole idea of virtualisation is to increase server utilisation/CPU utilisation/network utilisation and if you are successful, there is less “slack in the system” to handle backup loads.

Installing a Backup Agent on Every Guest

Many companies still backup virtual machines by installing a backup agent on every guest – a common strategy because of uncertainty about the ability to recover granularly, as well as other limitations. However, the impact of this approach is significantly higher costs from backup agents and unnecessary management complexity.

Today, virtualisation vendors (VMware, EMC, Microsoft) have improved APIs to support centralized backup with granular restore, and many vendors have the ability to backup at the hypervisor level – all making it unnecessary to install a backup agent on every guest for backup purposes.

Failing to Protect Applications

Failing to protect key applications is the easiest mistake and solution, yet is oddly still a common issue for many IT professionals. Backup is not just for files and data, but also key applications. If a disaster happens, the ability to restore the data in the application state will be important in terms of business continuity. Enterprise end users need applications and databases so when IT virtualizes these applications, it should also ensure they are backed up properly.

Failing to Consider Restore

Backup without the ability to ensure recovery means absolutely nothing – backup is nothing without recovery. In virtualised environments there are considerably more options to restore then in physical environments, so it’s not uncommon the backup of virtualised environments for recovery to be an after-thought.

When considering restore, IT needs to take into account what it wants to restore and its granularity. It’s also wise to consider where to restore to physical or virtual, onsite or offsite, etc.. IT needs to work with key stakeholders to consider objectives and the associated process for restore. It’s also a good idea to have a written plan that all stakeholders agree to, and to test that plan regularly.

Do you have disaster recovery plan? Is virtualisation part of your plan?


How companies lose data – infographic

October 28, 2011

What would your small business do if your computers were stolen or destroyed? Would your important data still exist? In April, Carbonite surveyed small businesses with between two and 20 employees to study their disaster recovery and data backup methods. We found that almost half of small businesses have already lost irreplaceable data.

Although this survey was only done for small companies, most mid market companies would be in the same situation…..


Cloud types, Private, Public and Hybrid – team C24

October 7, 2011

Cloud computing comes in three forms: public clouds, private clouds, and hybrids clouds. Depending on the type of data you’re working with, you’ll want to compare public, private, and hybrid clouds in terms of the different levels of security and management required.

Cloud Model

Public Clouds

A public cloud is basically the internet. Service providers use the internet to make resources, such as applications (also known as Software-as-a-service) and storage, available to the general public, or on a ‘public cloud. Examples of public clouds include Amazon Elastic Compute Cloud (EC2), IBM’s Blue Cloud, Sun Cloud, Google AppEngine and Windows Azure Services Platform.

For users, these types of clouds will provide the best economies of scale, are inexpensive to set-up because hardware, application and bandwidth costs are covered by the provider. It’s a pay-per-usage model and the only costs incurred are based on the capacity that is used.

There are some limitations, however; the public cloud may not be the right fit for every organization. The model can limit configuration, security, and SLA specificity, making it less-than-ideal for services using sensitive data that is subject to compliancy regulations.

Private Clouds

Private clouds are data center architectures owned by a single company that provides flexibility, scalability, provisioning, automation and monitoring. The goal of a private cloud is not sell “as-a-service” offerings to external customers but instead to gain the benefits of cloud architecture without giving up the control of maintaining your own data center.

Private clouds can be expensive with typically modest economies of scale. This is usually not an option for the average Small-to-Medium sized business and is most typically put to use by large enterprises. Private clouds are driven by concerns around security and compliance, and keeping assets within the firewall.

Hybrid Clouds

By using a Hybrid approach, companies can maintain control of an internally managed private cloud while relying on the public cloud as needed. For instance during peak periods individual applications, or portions of applications can be migrated to the Public Cloud. This will also be beneficial during predictable outages: hurricane warnings, scheduled maintenance windows, rolling brown/blackouts.

The ability to maintain an off-premise disaster recovery site for most organizations is impossible due to cost. While there are lower cost solutions and alternatives the lower down the spectrum an organization gets, the capability to recover data quickly reduces. Cloud based Disaster Recovery (DR)/Business Continuity (BC) services allow organizations to contract failover out to a Managed Services Provider that maintains multi-tenant infrastructure for DR/BC, and specializes in getting business back online quickly.


Follow

Get every new post delivered to your Inbox.

Join 752 other followers