BakBone Blog

News & Views from BakBone® Software

Posts Tagged ‘NetVault: Backup’

What Does “Best-of-Breed” Actually Mean?

Posted by BakBone on March 2, 2010

Andrew Martin

When it comes to choosing “best-of-breed” in data protection the choice is neither simple nor obvious.

What does best-of-breed actually mean? Do we mean best-of-breed vendors that can provide total solutions from the ground up? Or do we mean the best technology for a given purpose?

An interesting analogy to use might be the financial services industry and how we buy insurance. We can go directly to an advisor from a large reputable insurance company or at the other extreme we can work with a third party insurance broker.

We get peace of mind when dealing with the big insurance company advisor, however they can only offer products from their own company. Whilst some of their offerings might be great, quite simply they will not have the best product available for every type of insurance requirement. On the other extreme is the third party broker – they can offer you a choice of products in every field and allow you to select the best one for your needs. However, you may have questions about the broker’s stability or even ethics. And, you may not have heard of some of the products that they offer you.

On balance I have always taken the “broker” approach. Initially it carries slightly more risk, but as an individual broker proves themselves to be trustworthy and stable over time, that risk diminishes. Ultimately, the broker is able to identify and offer me more individualised products that are better for me.

If we bring this back to data protection we see the “one stop shops” that offer solutions on every aspect of data protection including primary storage, storage management, backup and recovery, high availability, provisioning and archive. We also have companies that offer a range of closely linked solutions in specific areas of data protection. My own company, BakBone Software, fits into this category with a range of solutions all closely linked to protection and recovery of data across a wide variety of applications and platforms. Finally, there are point solution companies; more usually (though not always) these are start-up companies and often they get consumed by bigger companies over time. An example would be Asempra. This was a company with a targeted solution for fast recovery of windows applications, acquired last year by BakBone and integrated into the wider portfolio. However, these “point” solution companies need not be small. Another example might be Data Domain, who had developed a global business by the time they were acquired.

The large “one stop shop companies” are often labeled “best-of-breed” by default. They offer integrated total solutions and peace of mind that comes with working with a trusted, established player. However, no one truly believes that every solution on the books of a large player is the best-of-breed in its class.

The other option is to place your trust in the advice of a true value added systems integrator. A good SI will have strong knowledge of offerings from various vendors and assesses what they believe are the best products and build them into a single integrated solution that they vouch for, implement and provide first line support. As a company that works closely with SI’s we often see this happen at BakBone. As an example, it is not uncommon to see our FASTRecover technology integrated into an environment often already using another company’s backup software.

In principle this SI led approach should ensure you get “best-of-breed” for your own precise requirements. However, much depends on the quality and real knowledge of the SI that you work with. As with the insurance broker analogy, this risk is minimised as the SI gains your trust over time by delivering proven projects.

My personal view is that working with a knowledgeable, reputable SI is the best way to get “best-of-breed.” I subscribe to this way of thinking for a number of reasons:

  1. No single requirement is the same, therefore no one company can offer the best solution for every data protection requirement that presents itself.
  2. New technologies and new ways of doing things are often brought to the market by newer companies.
  3. By definition “one stop shops” need to steer customers towards “their view of the data protection world.” By contrast an SI works harder to find solutions that meet how their customer wants to operate.

I understand and accept that “one stop shops” can sometimes be the best option for some companies. However when it comes to choosing “best-of-breed” for your own requirements, it actually comes down to understanding and meeting your own specific needs and the answer will rarely be the same from one company to the next. For that reason, choice and differentiation will always remain vital in choosing what’s best for you.

Posted in BakBone Asia | Tagged: , , , , , , | Comments Off

Duplicating Backups – Selecting between Duplication and Data Copy

Posted by steveadler on February 25, 2010

Steve Adler, Technical Support & Operations Lead

We back up our data so that in case of a data loss event, we have the ability to restore that data. But how do you protect the data that you’ve backed up. You can send it offsite, but what happens if that offsite location is affected by a catastrophic event? It’s simple really. Make another copy!

NetVault: Backup provides two different ways to make additional copies of your backups. Duplication and Data Copy. What’s the difference?

The Duplication method creates an exact secondary copy which is linked to the original primary backup. During duplication, the copy is broken into segments and stored on the secondary backup device. During restore, segments from the primary copy and the secondary copy are interchangeable. This means that even if you no longer have all of the original tapes, as long as the media that contains the duplicates of that data is available, you’ll be able to restore that data. You can basically “fill in the blanks” with the duplicated data.

However, encrypting that data for added security can pose a problem. It is impossible to unencrypt the primary backup and encrypt the secondary copy because it is not possible to mix unencrypted segments with encrypted segments during restore. If the original saveset is encrypted, the Duplicate method will create an encrypted secondary copy. If you have no encryption for the primary backup, the secondary copy will also be unencrypted.

The Data Copy method is recommended when you want to create a secondary copy for offsite storage. Data Copying a backup breaks the backup into segments and copies the segments onto the targeted backup device. During restore, NetVault: Backup only restores the primary copy or the secondary copy. Backup segments from the primary and the secondary are not interchangeable. This means that if you are missing part of the original backup, you will need the entire secondary copy available to perform a restore. You can’t just “fill in the blanks.” However, this enables the ability to encrypt the Data Copy, or secondary copy, while the primary copy remains unencrypted such as with deduplicated primary backups.

By incorporating one or both of these strategies to copy your data, you can decrease the chance of losing your backups to a catastrophic event so you can recover your data when you need it

Posted in BakBone North America | Tagged: , , , , , , , , , , , | Comments Off

Calculating NetVault: SmartDisk Licensed Capacity

Posted by Dawn renee Campbell on February 17, 2010

Dawn renee Campbell

You have chosen which data you want to deduplicate with NetVault: SmartDisk (NVSD), and now you are tasked with calculating how much capacity to license.

NVSD is licensed based on the logical capacity (or total size) before deduplication of ALL backups that are stored in NVSD.

NVSD provides the ability to deploy multiple instances that can be targeted for backup from multiple NVBU Servers. When calculating the licensed capacity for NVSD, the capacity across all deployed NVSD instances must be included. For example, if two NVBU Servers are targeting backups to one or more NVSD instances, the capacity of the backups from both NVBU Servers must be included in the calculations.

Understand that NVSD licensed capacity is NOT based upon any of the following:

  • Actual size of the storage pool, staging store, or chunk store
  • Actual size of the backups after deduplication

Calculating NVSD capacity requires the collection of the following values for each NVBU Server that will target backups to NVSD. When inserting these values into the calculations, be sure to include the sum of the values across ALL the NVBU Servers that will target backups to NVSD. For example, if NVBU Server 1’s size of weekly backups is 40GB and NVBU Server 2’s is 60GB, use 100GB as the size of the weekly full backups.

If separate NVSD instances for non-deduplicated and deduplicated data will be used, perform the calculations below separately for the backups that will not be deduplicated versus the backups that will be deduplicated. This will enable you to know exactly how much NVSD non-deduplicated capacity needs to be licensed and how much capacity needs to be licensed for the NVSD deduplication option.

If a single NVSD instance will be used for both non-deduplicated and deduplicated data, include both the values for non-deduplicated and deduplicated data in the single calculation.

Size of Weekly Full Backups

Size of all the full backups that will be targeted to NVSD. For example, if  SQL Server, Exchange, Oracle and File System backups will be targeted for NVSD, calculate the total size of ALL the full backups for SQL Server, Exchange, Oracle and File System.

Weekly Full Backup Growth Rate

Average weekly growth rate of the full backups, which are included in the size of weekly full backup calculation. Weekly full backup growth rate is a critical factor in accurately determining NVSD sizing. For example, the average of all of the full backups is growing 10% each week. Another convenient method to calculate this is to base it on annual data growth.  For example, an annual growth rate of 100%, or an annual doubling of data, would represent a weekly growth rate of 1.333%.

Weekly Full Backup Retention Period in Weeks

Number of weeks that full backups will be retained in NVSD. Restores are faster when being performed from disk-based media than when being performed from tape-based media. Increasing the amount of protected data that is available on disk-based media increases the number of restore scenarios that can be performed from disk-based media.  Requiring tapes to be located, retrieved and loaded in order to perform a restore slows down the restore speed and increases downtime.

Additionally when performing deduplication, the longer the data is retained in NVSD, the better the deduplication ratios will be because more duplicate chunks are found, thereby enabling the ability to pack more data into the same storage footprint. This enables even more protected data to be available via disk-based media.

To obtain the most ideal deduplication ratios, we recommend a retention period of 12 weeks or more.

Size of Daily Backups

Size of all the daily backups that will be targeted to NVSD.  For example, if SQL Server, Exchange, Oracle and File System backups will be targeted for NVSD, calculate the total size of ALL the daily backups for SQL Server, Exchange, Oracle and File System.

Daily backups are interim backups between the weekly full backups. These are anticipated to be incremental or differential backups, and as such, will generally be much smaller than the weekly full backups.

Daily Backup Growth Rate

Average daily growth rate of the daily backups that are included in the size of daily backups.  For example, the average of all the daily backups is growing 1% each week.

Number of Daily Backups between Full Backups

Number of daily backups that are performed between full backups. For example, if full backups are performed on Sunday and daily backups are performed each day, Monday thru Saturday, the number of daily backups would be six.

Daily Backup Retention Period in Weeks

Number of weeks that daily backups will be retained in NVSD. Daily Backups provide the ability to perform fixed-point-in-time restores, thereby reducing the recovery time objective. Daily backups can be retained for the same period of time as full backups, which enables fixed-point-in-time restores for the entire weekly full backup retention period.  Fixed-point-in-time restores are typically performed using backups taken within the last four weeks. As such, it is possible to retain weekly full backups for one retention period and daily backups for a shorter retention period. This would allow you access to daily backups for a set period of time, such as four weeks, while providing you with access to full backups to a longer period of time, such as 12 weeks.

NVSD Sizing Calculator

With the NetVault: SmartDisk Sizing Calculator, you simply enter all the above values.  It will calculate not only the amount of NVSD capacity to license but also tell you the number of NVSD instances and the amount of memory for each NVSD instance. The NVSD Sizing Calculator can be obtained from your BakBone representative.

In my next NVSD blog, we will learn how to calculate how much physical capacity is required.

Posted in BakBone North America | Tagged: , , , , , , , , , | Comments Off

Selecting the SQL Server Backup Type to use with NetVault: Backup – Part 1

Posted by Mike Daniels on February 3, 2010

Mike Daniels, Product Manager

Before deploying the NetVault: Backup APM for SQL Server, you must first define your SQL Server backup strategy. The purpose of creating a SQL Server backup strategy is to be able to recover a database that has been damaged or become corrupted. When creating a backup strategy, you define the type and frequency of backups to meet the data protection requirements of the database or application.

First, it is important to understand the VDI-based backup types that can be performed with SQL Server in order to give you an idea of what each one does. The NetVault: Backup APM for SQL Server offers several types of backups including

  • Full database
  • Differential database
  • Copy-only
  • Incremental transaction log
  • Tail-log
  • Full file and filegroup
  • Differential file and filegroup
  • Partial database
  • Differential partial database

With full database backups, you are backing up the entire database. This type of backup also includes part of the transaction log so that the full database backup can be completely recovered. A full database backup represents the database at the time that the backup was completed. These backups are typically easy to use because they contain all the data in the database. For smaller databases that can be backed up quickly, this is the recommended method for backups due to the simplicity of the recovery process. As databases become larger and the full database backups take longer, you probably want to consider supplementing full database backups with differential database backups.

Differential database backups only record the data that has changed since the last full database backup. These backups are smaller and faster than a full database backup, which saves time but does start to increase the complexity of the backup scheme. For large databases, it is Microsoft’s best practice to follow full database backups with a series of differential database backups. Since each differential will get larger than the previous, it is also recommended that you schedule a new full database backup on an appropriate schedule.      There are special situations where you might want to have a database or a backup of the database, but do not want to impact the regular backup rotation or scheme. A typical SQL Server backup will change the database by updating the differential bitmap. This change affects how future backups and restores are done. By using copy-only backup, you can create a backup that is independent of the regular SQL Server backup sequence. This means that the differential bitmaps are not changed and your regular backup sequence will not be affected. Typically these backups are ideal for circumstances where you require the database, but do not want to affect you production system, such as creating a test environment, or for standby databases.

Transaction logs contain the data for all of the actual transaction that have occurred on the database. In SQL Server, taking routine transaction log backups are essential to be able to fully recover the data. With transaction log backups, you have the ability to recover a database to a specific point in time or to the point of a database failure. With incremental transaction log backups, you capture all of the transaction logs including transaction logs that have been generated since the last full database/file or filegroup, differential database/file or filegroup, or incremental transaction kog backup. These backups are also the means by with the SQL Server logs are typically truncated in order to reduce the amount of space required by the SQL Server logs.

Tail-log backups are backups that capture the logs that have not been backed up yet. These are typically the last backup restored in a SQL Server recovery sequence because it completes the log chain. With SQL Server 2005 and 2008, it is required that you run a tail-log backup prior to restoring any database that is currently attached to the SQL Server Instance. Because of this, the tail-log backup is typically the first step in any recovery process.

While restores are the primary consideration when creating a backup strategy, you have to understand what the different types of backups are actually doing so that you can make a conscious and informed decision.

In my next Blog we will continue the discussion on different types of SQL Server backups and their purpose.

Posted in BakBone North America | Tagged: , , , , , , | Comments Off

Encrypting all Backups vs. Job-Level Encryption with NetVault: Backup

Posted by Dawn renee Campbell on January 27, 2010

Dawn renee Campbell

  

You have selected the encryption algorithm you are going to use with the NetVault: Backup (NVBU) Encryption Plugin and have decided whether to encrypt your primary or secondary backups, but now you are not sure if you should encrypt all of your backups or use NVBU 8.5’s new job-level encryption feature.  

Prior to NVBU 8.5, your only option was to encrypt all the backups for the NVBU Server or a Heterogeneous Client where the NVBU Encryption Plugin is installed, but NVBU 8.5 gives you the ability to only enable encryption for specific jobs.  Understanding the benefits of both options will help you choose the best strategy for your environment.  

Encrypt all Backups  

The NVBU Server or Heterogeneous Client should only be configured to encrypt all its backups when  

  • All the NVBU Plugins installed on the NVBU Server or Heterogeneous Client are compatible with the Encryption Plugin
  • All backups from the NVBU Server or Heterogeneous Client require encryption
  • Primary and secondary backups require encryption
  • Backups will be targeted to NetVault: SmartDisk (NVSD) devices for deduplication

For a list of NVBU Plugins that are not compatible with the Encryption Plugin, refer to the NetVault: Backup Encryption Plugin Release Notes.  

Job-Level Encryption  

Job-level encryption for primary backups is beneficial when  

  • Not all the NVBU Plugins installed on the NVBU Server or Heterogeneous Client are compatible with the NVBU Encryption Plugin
  • Not all backups from the same NVBU Server or Heterogeneous Client require encryption
  • Primary backups do not require encryption while secondary backups for offsite protection do require encryption
  • Primary backups are targeted to NVSD devices for deduplication

Posted in BakBone North America | Tagged: , , , , , , | Comments Off