Symantec netbackup installation and configuration

Editor's Notes

• #1: Welcome to the second lesson of the NetBackup 6.x Administration course: Installing and Configuring NetBackup
• #2: Knowing what to address before, during, and after installing NetBackup helps you to ensure a successful installation and to avoid potential problems.
• #3: This lesson is divided into 5 topics. First, you’ll see some considerations you should address before installing NetBackup. Then, you’ll see how to install NetBackup. The third topic covers NetBackup configuration. Next, we’ll talk about some things you should consider if upgrading from 5.x to 6. Finally, you will be able to troubleshoot the most common installation issues.
• #4: This topic presents you with considerations you should address before installing NetBackup. The next several slides illustrate the default installation paths for NetBackup, list some general considerations to be aware of before installing NetBackup, and provide some information on NetBackup license keys.
• #5: This slide shows you where the various NetBackup components are installed by default. The first bullet on the right side shows the default path on Windows. The second bullet reflects the default installation path on UNIX servers.
• #6: Preparation is the key to a successful NetBackup installation. When you prepare your servers, keep the following things in mind: Your hardware and software must be compatible with NetBackup. You can verify compatibility by using the compatibility matrix. You must have sufficient memory and hard disk space. Reference the release notes for memory and disk requirements. It’s also a best practice to remove any other vendor’s software. Conflicts may occur if two different backup products are trying to access the same device. Our support Web site contains the compatibility matrix, the release notes, and many other helpful resources. The next step is to prepare the environment. First, you want to make sure that NetBackup supports whatever tape and disk devices that you’re using. Again, the compatibility matrix is useful in this case. Also ensure that the devices are operational. This includes installing any device drivers and verifying that the devices are recognized by the operating system. If the operating system can’t see the devices, NetBackup won’t be able to see the devices. Finally, verify that network and name services are operating correctly. Use ping or some other utility to verify that the systems can communicate with one another. The last step is to prepare yourself. Gather the software and the documentation. Be sure to read the release notes, as they contain information vital to a successful installation. Make sure you have your license key. During the installation process, you are required to enter a a license key, and you won’t be able to proceed without one. Finally, be sure that you have administrative privileges for all the servers on which you’ll be installing NetBackup.
• #7: Now let’s look at some of the things you need to consider in your environment before you install NetBackup. First we’ll look at memory. Installing NetBackup Server software on a UNIX servers requires 1 gigabyte of physical memory, with at least 256 megabytes of memory available to the application. It is recommended however, that you have at least 2 gigabytes of physical memory on UNIX NetBackup servers in most production environments. Windows hosts require a minimum of 1 gigabyte of memory. You also need to look into the software requirements for NetBackup. For UNIX, gzip and gunzip must be installed on the server. Windows NetBackup installation requires a minimum browser level of Internet Explorer 5.0.
• #8: This table shows the approximate binary size of the NetBackup and Media Server software, and the NetBackup client disk space requirements for each platform and operating system supported by NetBackup. For more specific information on these requirements, check out the NetBackup Release Notes.
• #9: The largest part of the NetBackup metadata is the image database, or the images catalog. The images database holds the metadata for all the files that have been backed up. So it’s really important to determine if the proposed master server has enough disk space available for the image database. >>>To determine the size the image database: >>>Estimate the number of files per backup and multiply that by the number of backups per retention period to get the maximum number of files. >>>To get the number of bytes, multiply the number of files by the average length of the file’s name. For a binary catalog you should estimate about 100 MB per file. >>>You should also add about 10 or 15 megabytes if you are running debug logs. >>>Finally, you should take steps to ensure that the whole image database sits on a single partition.
• #10: Let’s look at an example to try to get a better grasp of what the size of the Images catalog might be. Let’s say that 100,000 files are backed up every day, and kept for about a month. You keep weekly backups for 2 weeks; monthly backups for 12 months; and quarterly backups for 7 years. Using what we just learned, we get a total number of about 222 million files. To get the number of bytes, we just multiply this number by the average length of the file’s full path name. Remember that we said that for binary catalogs, we should use about 100 bytes. Adding another GB for the logs we arrive at a final estimated size of 22GB.
• #11: (compatibility_0010.gif, compatibility_0020.gif) The Symantec Support Web site maintains all of the compatibility lists. However, compatibility has two different meanings in NetBackup. First, software compatibility enables NetBackup to work with specific operating systems, databases, and other applications. Then, there is device compatibility, which means that devices have been tested and proven to work with NetBackup. You can get all this information off of the support Web site. These lists are prone to change, so you should visit the site regularly to review the latest and most complete compatibility lists.
• #12: (hcl_0010.gif) Here we see an example of the results you might get when searching for the phrase “compatibility list” on the Symantec Support Web site.
• #13: During the installation process, you are required to enter a license key. The license key is an alpha-numeric string, which you may enter in upper case, or lower case. The license key does not contain any zeros, the number one, the number five, Qs, spaces, or blanks. If there is any ambiguity between the characters, the alphabet always takes precedence. So you would use an O or an L instead of typing zero or one. During installation, you will be prompted to enter all keys for options and agents. If you purchase an agent or option at a later date, you can still enter new license keys by using the NetBackup Administration Console, the NetBackup License Key utility, or from the command-line. Evaluation keys are valid for thirty days. At the end of the evaluation period, all daemons or services are shut down; however, if you add a permanent license key to an evaluation version of NetBackup, you can continue to operate normally.
• #14: At this point, we can talk about administering license keys in a little more detail based on the platform that you will be using. To see how to administer license keys on UNIX from the GUI or using the License Key Utility click the UNIX button at the bottom of the slide. To see how to manage license keys on Windows using the GUI, click the Windows button.
• #15: (license_keys_0015_u.gif, license_keys_0020_u.gif) There are two ways to administer license keys on UNIX. The first way is by using the NetBackup Administration Console. In the GUI, select Help and then License keys. This brings up the NetBackup License Keys window. This window shows you the license key, the server, the date and time the license key was installed, and the features enabled with the license key. This window would be very helpful if you thought that you had purchased an agent, such as Oracle, but weren’t able to access the agent’s configuration options. The first thing you should do is view this window to determine if the agent is enabled. To enter a new key click New and enter the license key. Then, restart all NetBackup utilities, including the NetBackup Administration Console.
• #16: (licnese_keys_0030_u.gif) The second way to administer license keys on UNIX is by using the license key utility. This utility is located in the directory on the slide. Entering the get underscore license underscore key command from the command line invokes the license key utility. There are many options available with the license key utility. Commonly used options include adding a key, deleting a key, and listing keys. Click the Return button to go back to the lesson.
• #17: (license_keys_0015.gif, license_keys_0020.gif) To administer license keys on Windows, use the NetBackup Administration Console. In the GUI, select Help and then License keys. This brings up the NetBackup License Keys window. This window shows you the license key, the server, the date and time the license key was installed, and the features enabled with the license key. This window would be very helpful if you thought that you had purchased an agent, such as Oracle, but weren’t able to access the agent’s configuration options. The first thing you should do is view this window to determine if the agent is enabled. To enter a new key click New icon highlighted in the slide and enter the license key. Then, restart all NetBackup utilities, including the NetBackup Administration Console. Click the Return button to go back to the lesson.
• #18: Now that you are familiar with NetBackup installation prerequisites, you can proceed with the installation. This topic covers installation and verification. The content within this topic is dependent upon the platform on which you install NetBackup. If installing on a UNIX server, click the UNIX button at the bottom on the slide. If installing on Windows click the Windows button.
• #19: Installing NetBackup is a straightforward process. >>>Log on to the server where you will be installing NetBackup as root. >>>NetBackup 6.x requires PBX (Private Branch Exchange) software to be loaded on the media server prior to installing the master server software. To install the PBX software on UNIX, run the installics script from the NetBackup ICS (Infrastructure Core Services) CD. >>>Insert the NetBackup CD in the drive. >>>Run the installation script to install the master server. You must run the install command from root, as opposed to the working directory that contains the NetBackup software. >>>Enter the license key. >>>On the master server, you’ll be prompted to enter the configured name of the master server, the names of the media servers, the name of the EMM (Enterprise Media Manager) server, and whether want to start processes. You will also have the option of creating sample policies and schedules and entering additional license keys. >>>Next, you need to install the media server.
• #20: Installing the media server is very similar to installing the master server. >>>As with the master server installation, to start, you log on as root on the media server where you are installing NetBackup. >>>Install PBX. >>>Run the install script. >>>Install the media server. >>>Enter the license keys. >>>On the media server: Enter the configured name of the media server. Type n when prompted if this is the master server. Enter the name of the master server. Enter the name of the EMM server. >>>After your initial installation is complete, install any other NetBackup agents and options (such as NetBackup for Oracle) by following the instructions in the NetBackup guide that comes with that particular product.
• #21: The installation script places the name of the host in the bp.conf file on the server. In a clustered environment, it places the virtual host name in the file. >>>The script then, adds entries to the services file for NetBackup and Media Manager services (for example, robotic daemons). This file contains UNIX system information. The script also checks to see if your server is running Network Information System (NIS), the UNIX directory service utility. If it is running, you should add entries to your NIS services map at this point. >>>Then, the script adds automatic startup and shutdown scripts to the appropriate directories on the various supported platforms. >>>Finally, the install script adds entries to the inetd.conf server file or the xinetd.d server directory to facilitate networking. Entries are added for bpcd, vnetd, vopied, and bpjava-msvc. Then, the script sends inetd (or xinetd) a signal, causing it to read the updated file.
• #22: (install_verify_0010_u.gif) There is no single way to verify a successful NetBackup or Media Manager installation. One technique is to start NetBackup and Media Manager and check that the processes are running. This verifies that the binaries were installed successfully and are operational. You can also verify that the daemons and processes are running using the NetBackup Administration Console. This method is displayed on the slide. Click the Return button to go back to the lesson.
• #23: Installing NetBackup on the master server on Windows is a straightforward process. >>>Log on to the server where you will be installing NetBackup as an administrator. >>>Insert the NetBackup CD in the drive and launch Windows Explorer, locate the software CD or installation path, and double-click the launch.exe file. >>>Enter the license keys. >>>Select NetBackup Master Server. >>>Enter the configured name of the master server. >>>Enter the name of the EMM (Enterprise Media Manager) server >>>Click Install to install the master server. >>>Next, we’ll install the media server on Windows.
• #24: Installing the media server is very similar to installing the master server. >>>As with the master server installation, to start, you log on as admin on the media server where you are installing NetBackup. >>>Insert the NetBackup Server software CD in the drive and double-click the launch.exe file. >>>Enter the license keys. >>>Select NetBackup Media Server. >>>Enter the configured name of the media server. >>>Enter the configured name of the master server. >>>Enter the name of the EMM (Enterprise Media Manager) server. >>>Click Install to install the media server.
• #25: Let’s look at what the installation script does on Windows. >>>First, it places the host name into the Windows registry. >>>Then the script adds entries to the services directory for NetBackup and Media Manager services (for example, robotic services). >>>Finally, it adds automatic startup and shutdown scripts to the appropriate directories on the various supported platforms.
• #26: (install_verify_0010.gif) There is no single way to verify a successful NetBackup or Media Manager installation. One technique is to start NetBackup and Media Manager and check that the processes are running. This verifies that the binaries were installed successfully and are operational. You can also verify that the services and processes are running using the NetBackup Administration Console. This method is displayed on the slide. Click the Return button to go back to the lesson.
• #27: Once NetBackup is installed, there is some initial configuration you may want to complete. This topic covers configuring system startup and shutdown scripts and master server and media server host properties.
• #28: There are three basic areas of your environment that you will want to configure right after you install NetBackup: The NetBackup directories Startup and shutdown scripts And environment variables
• #29: You can configure most NetBackup settings using the Host Properties section of the NetBackup Administration Console. Each of the component machines (the master server, media servers, and clients) has its own set of properties. If configuring NetBackup Host Properties on a UNIX server, click the UNIX button at the bottom on the slide. If configuring Host Properties on Windows click the Windows button.
• #30: (host_props_0015.gif) You can modify the Host Properties for any server or client within your NetBackup environment from the master server. To access the Host Properties from within the NetBackup Administration Console, select NetBackup Management, Host Properties, and then Master Servers. Double-click the desired machine in the details pane, or right-click the desired machine in the details pane, and select Properties from the shortcut menu. To see the properties of a different master server, select File—>Change Server. For UNIX servers, you can also configure NetBackup by editing the bp.conf file and the vm.conf file. The vm.conf file is not created until devices are added. Most of the master server host properties correspond to bp.conf settings. Many of the host properties related to the media servers correspond to vm.conf settings on that particular host.
• #31: (master_props_0010.gif) Here we see the master server host attributes that can be configured in the Global Attributes Properties window. The Global Attributes properties affect all operations for all policies and clients. The default values are adequate for most installations but can be changed. Changes to Global Attributes properties cascade across all component systems in the backup environment. The Global Attributes properties apply to the currently selected master server. For UNIX, the Global Attributes properties are stored on that master server in the /usr/openv/netbackup/db/config directory. See the “Host Properties” appendix for a description of the remaining master server host properties. Click the Return button to go back to the lesson.
• #32: (host_props_0015.gif) You can modify the Host Properties for any server or client within your NetBackup environment from the master server. To access the Host Properties from within the NetBackup Administration Console, select NetBackup Management, Host Properties, and then Master Servers. Double-click the desired machine in the details pane, or right-click the desired machine in the details pane, and select Properties from the shortcut menu. To see the properties of a different master server, select File—>Change Server. In the Windows environment, attributes correspond to registry settings.
• #33: (master_props_0010.gif) Here we see the master server host attributes that can be configured in the Global Attributes Properties window. The Global Attributes properties affect all operations for all policies and clients. The default values are adequate for most installations but can be changed. Changes to Global Attributes properties cascade across all component systems in the backup environment. The Global Attributes properties apply to the currently selected master server. See the “Host Properties” appendix for a description of the remaining master server host properties. Click the Return button to go back to the lesson.
• #34: The NetBackup Administration Console contains a group of NetBackup configuration wizards in the right window pane that enable you to perform the following tasks: Configure Storage Devices for NetBackup. Before configuring NetBackup, you must have the storage devices attached to the server and perform all configuration steps specified by the device and operating system vendor (including installation of any required device drivers) Configure Media. Configure the Catalog Backup. And create a Backup Policy. This slide also shows you the lessons in this course where these tasks are discussed in more detail. If you are configuring NetBackup for the first time, you should click the Getting Started icon and use this set of wizards to guide you through the process. You should also look at the NetBackup System Administrator’s Guide for more details on configuring NetBackup.
• #35: With the many new features included in NetBackup 6.x, some new upgrade requirements have been put in place to make your transition to this version of NetBackup easier. This topic identifies supported server upgrade paths.
• #36: Symantec only supports server upgrades from NetBackup 5.0 MP4 (or later) and NetBackup 5.1 >>>If you currently have a pre-NetBackup 5.0 MP4 version installed, you must perform an intermediate upgrade to NetBackup 5.x first, and then you can upgrade to NetBackup 6.0. There are some other points about upgrading that you should consider: Changing a master server into a media server is not an allowable upgrade. It is considered a downgrade. To make this change, you must first uninstall the earlier version of NetBackup and perform a new installation. Make certain that the NetBackup release level on the server is at least equal to that on the clients. Older versions of server software can encounter problems with newer clients. Add-on products must be at the same level as the NetBackup client or server on which the add-on is installed. The final consideration relates to NetBackup-Enterprise-only. NetBackup does not support converting an existing nonfailover server to a highly available failover NetBackup server.
• #37: Mixed patch-level support enables NetBackup servers to run a mixture of NetBackup major releases and patches in the same environment. In a mixed environment, the master server must be running the latest version of NetBackup in use in that configuration. This slide illustrates an example of a supported mixed environment. Consider the following guidelines: A master server can interoperate with a media server that is running a level of NetBackup from one major release earlier. Servers that are running NetBackup 5.x cannot be used as a Volume Database host, global device database host, or vmd/DA host. Always upgrade NetBackup 5.x servers that are performing these roles first. Only then can media servers, and finally client machines, be upgraded. Client backward compatibility extends only one major release prior to the master server. This includes database clients. Applying a NetBackup maintenance pack (or MP) does not alter the version of the release for NetBackup 5.1. However, for NetBackup 5.0 media servers, this does not apply. In NetBackup versions 5.0 GA, MP1, MP2, and MP3, if the media server and the client are the same machine, you cannot restore on the client. Any media server with which you want to coexist in a NetBackup 6.0 configuration must be at a version level of 5.0 MP1 or later. All components (the master server, media server, client, console, and agent) on an individual system must run the same version. Finally, backup images created under an older version of NetBackup are always recoverable with a newer version of NetBackup.
• #38: In this topic you learn how to troubleshoot the most common installation issues.
• #39: When troubleshooting NetBackup installation, There may be network or communication issues. Ways to isolate these types of problems include pinging, by name, between the master server, media servers, and all clients, starting or communicating with NetBackup services, and ensuring that the port and service entries on each media server and client match the master server. Another thing to check is the host communications setup. Misspelled or incorrect host names will also cause installation failures. NetBackup requires reverse name lookup.
• #40: The next section is a quiz. In this quiz, you will be asked a series of questions related to installing and configuring NetBackup. After you try to answer each question, click the Answer button to see the correct answer to the question.
• #51: Well, that just about wraps up this lesson. You now know how to prepare for a NetBackup installation. You know how to configure NetBackup, verify the installation, and troubleshoot the most common installation issues. For more information about the topics discussed in this lesson, refer to the Resources listed on the slide. And don’t forget to check the support Web site frequently.