Search <book_title>...

NetBackup™ Backup Planning and Performance Tuning Guide

Last Published: 2024-04-16

Product(s): NetBackup & Alta Data Protection (10.4, 10.3.0.1, 10.3, 10.2.0.1, 10.2, 10.1.1, 10.1, 10.0.0.1, 10.0, 9.1.0.1, 9.1, 9.0.0.1, 9.0, 8.3.0.2, 8.3.0.1, 8.3)

How to analyze your backup requirements

Many factors can influence your backup strategy. You should analyze these factors and then make backup decisions according to your site's priorities.

When you plan your installation's NetBackup capacity, ask yourself the following questions:

Table: Questions to ask as you plan NetBackup capacity

Questions	Actions and related considerations
Which systems need to be backed up?	Identify all systems that need to be backed up. List each system separately so that you can identify any that require more resources to back up. Document which computers have disk drives or tape drives or libraries attached and write down the model type of each drive or library. Identify any applications on these computers that need to be backed up, such as Oracle, DB2, VMware, MySQL, or MS-Exchange. In addition, record each host name, operating system and version, database type and version, network technology (for example, 10 gigabits), and location.
How much data is to be backed up?	Calculate how much data you need to back up and the daily/weekly/monthly/yearly change rate. The change rates affect the deduplication ratio and therefore the amount of data that need to be written to the disk group. Include the total disk space on each individual system, including that for databases. Remember to add the space on mirrored disks only once. By calculating the total size of all clients, you can design a system that takes future growth into account. Try to estimate how much data you will need to back up in 6 months to a few years from now. Consider the following: Do you plan to back up databases or raw partitions? To back up databases, identify the database engines, their version numbers, and the method to back them up. NetBackup can back up several database engines and raw file systems, and databases can be backed up while they are online or offline. To back up a database that is online, you need a NetBackup database agent for your particular database engine. With a Snapshot Client backup of databases using raw partitions, you back up as much data as the total size of your raw partition. Also, remember to add the size of your database backups to your final calculations when figuring out how much data you need to back up. Do you plan to back up special application servers such as MS-Exchange or Lotus Notes? To back up application servers, identify their types and application release numbers. As previously mentioned, you may need a special NetBackup agent to back up your particular servers.
Should Accelerator be enabled for VMware virtual machine backup?	In subsequent full backups and incremental backups, only changed data would be backed up when Accelerator is enabled in the NetBackup policy. This case would greatly shorten the backup time and reduce the backup size. It's strongly recommended enabling Accelerator for VMware VMs backup. With Accelerator for VMware, the type of data matters less. What matters the most is the change rate, (how much data changes from one full to the next). In most typical workloads, the change rate is quite small, therefore a large benefit can be achieved using Accelerator. The biggest benefit of enabling Accelerator is realized for full backup schedules. A full backup image is created at the cost of an incremental (that is, time and data transfer). An incremental schedule backup for VMware with Accelerator produces a full image of the VM, but only changed files are cataloged. This approach helps in use cases such as Instant Restore/Instant Access can be done from an incremental image as well as simplifies optimized duplication (opt-dup) replication. Tape-out and non-opt-dup replication can have an adverse effect, as the size of such an image can be as big as a full image.
What types of backups are needed and how often should they take place?	The frequency of your backups has a direct effect on your: Disk or tape requirements Data transfer rate considerations Restore opportunities. To properly size your backup system, you must decide on the type and frequency of your backups. Will you perform daily incremental and weekly full backups? Monthly or bi-weekly full backups?
How much time is available to run each backup?	What is the window of time that is available to complete each backup? The length of a window dictates several aspects of your backup strategy. For example, you may want a larger window of time to back up multiple, high-capacity servers. Or you may consider the use of advanced NetBackup features such as synthetic backups, a local snapshot method, or FlashBackup.
Should the scheduling windows for backups overlap with those of duplication or replication jobs or should they be separated?	If the windows of backup and duplication or replication jobs (including Auto Image Replication (A.I.R.)) overlap, performance of these jobs would be affected. Carefully design the scheduling of backups and duplication or replication jobs to try to avoid overlapping. For more information, see the following documents: Auto Image Replication (A.I.R.) slow performance, particularly for small images: https://www.veritas.com/support/en_US/article.100045506 How to tune NetBackup Auto Image Replication (A.I.R.) operations for maximum performance: https://www.veritas.com/support/en_US/article.100046559
Is archiving to the cloud supported?	NetBackup supports various cloud archive technologies including AWS Glacier options, Snowball, and Snowball Edge, along with Microsoft Azure Archive.
How long should backups be retained?	An important factor while you design your backup strategy is to consider your policy for backup expiration. The amount of time a backup is kept is also known as the retention period. A fairly common policy is to expire your incremental backups after one month and your full backups after 6 months. With this policy, you can restore any daily file change from the previous month and restore data from full backups for the previous 6 months. The length of the retention period depends on your own unique requirements and business needs, and perhaps regulatory requirements. However, the length of your retention period is directly proportional to the number of tapes you need and the size of your NetBackup image database. Your NetBackup image database keeps track of all the information on all your disk drives and tapes. The image database size is tightly tied in to your retention period and the frequency of your backups.
If backups are sent off site, how long must they remain off site?	If you plan to send tapes off-site as a disaster recovery option, identify which tapes to send off site and how long they remain off-site. You might decide to duplicate all your full backups, or only a select few. You might also decide to duplicate certain systems and exclude others. As tapes are sent off site, you must buy new tapes to replace them until they are recycled back from off-site storage. If you forget this detail, you may run out of tapes when you most need them.
What is your network technology?	If you plan to back up any system over a network, note the network types. The next section explains how to calculate the amount of data you can transfer over those networks in a given time. Based on the amount of data that you want to back up and the frequency of those backups, consider using 10-GB network interfaces, linking aggregation/teaming, or installing a private network for backups.
What systems do you expect to add in the next 6 months?	Plan for future growth when you design your backup system. Analyze the potential growth of your system to ensure that your current backup solution can accommodate future requirements. Remember to add any resulting growth factor that you incur to your total backup solution.
Will user-directed backups or restores be allowed?	Allow users to do their own backups and restores, to reduce the time it takes to initiate certain operations. However, user-directed operations can also result in higher support costs and the loss of some flexibility. User-directed operations can monopolize disk pools and tape drives when you most need them. They can also generate more support calls and training issues while the users become familiar with the new backup system. Decide whether user access to some of your backup systems' functions is worth the potential cost.
What data types are involved?	What are the types of data: text, graphics, database, virtual machines? How compressible is the data? What is the typical deduplication rate of data to be backed up? How many files are involved? Will NetBackup's Accelerator feature be enabled for VMware virtual machine or NDMP backups? (Note that only changed data is backed up with Accelerator for both full and incremental backup.) Will the data be encrypted? (Note that encrypted backups may run slower.)
Where is the data located?	Is the data local or remote? Is it tape, JBOD (just a bunch of disks), or disk array? What are the characteristics of the storage subsystem? What is the exact data path? How busy is the storage subsystem?
How to test the backup system?	Because hardware and software infrastructure can change over time, create an independent test backup environment. This approach ensures that your production environment can work with the changed components.