Replication Director

Transcription

NETBACKUP 7.6 BEST PRACTICE DOCUMENT
REPLICATION DIRECTOR
NetBackup 7.6 – Replication Director
Installation and Best Practice Overview
Version number: 1.1
Publication date: April 2014
Review by date: April 2015
Please mail any feedback or questions about this document to [email protected].
Be sure to mention the document title for reference.
This document is provided for informational purposes only. All warranties relating to the information
in this document, either express or implied, are disclaimed to the maximum extent allowed by law.
The information in this document is subject to change without notice. Copyright © 2014 Symantec
Corporation. All rights reserved. Symantec, the Symantec Logo, and the Checkmark Logo are
trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other
countries. Other names may be trademarks of their respective owners.
NetBackup 7.6 - Replication Director Installation and Best Practice Overview
Contents
DOCUMENT PURPOSE ..................................................................................................................................... 2
CONFIGURATION OPTIONS ............................................................................................................................. 3
PRE-CONFIGURATION TOOLS .........................................................................................................................................3
NETAPP CONFIGURATION ............................................................................................................................... 7
ONCOMMAND (DFM) INFORMATION ..............................................................................................................................8
Configuring the OnCommand Server for Replication Director .........................................................................8
Plug-in Installation ........................................................................................................................................................... 8
Configuring communications between the OnCommand Server and the Filers ....................................................... 10
FILER CONFIGURATION ................................................................................................................................................12
Unicode configuration .......................................................................................................................................13
NetApp Licensing Configuration.......................................................................................................................13
Filer Disk Configuration ....................................................................................................................................14
Resource Pool Configuration ............................................................................................................................16
DFM Configuration for a vFiler .........................................................................................................................20
NETBACKUP CONFIGURATION .......................................................................................................................21
NETBACKUP TO DFM CREDENTIAL CONFIGURATION ......................................................................................................21
NETBACKUP DISK POOL CREATION ..............................................................................................................................22
NETBACKUP STORAGE UNIT CREATION .........................................................................................................................24
ADDITIONAL NETBACKUP CONFIGURATION – “TARGET” DISK AND STORAGE UNIT ............................................................24
STORAGE LIFECYCLE POLICY CONFIGURATION ...............................................................................................................27
POLICY CREATION .......................................................................................................................................................30
VMware Protection with Replication Director .............................................................................................................. 32
Configuring the NetBackup Service on the client used for the Mount Point on Windows ....................................... 34
NETAPP SIZING ADVISOR .............................................................................................................................................36
SYMANTEC REPLICATION DIRECTOR AND NETAPP ONCOMMAND – JOINT BACKUP AND RESTORE SEQUENCE.......................38
Page 1
Document Purpose
Replication Director was introduced in NetBackup 7.5 and enhanced in NetBackup 7.6. Installing the
feature could pose challenges because the installation requires NetApp and NetBackup configuration
knowledge.
This document is intended to supplement the NetBackup and NetApp manuals and to provide a sort of
cheat sheet for installing and configuring Replication Director. It is a “getting-started” type of guide that
includes best practices based on what we have learned from the customers who have installed and
configured Replication Director.
While the information is based on Replication Director in NetBackup 7.6, it also pertains to NetBackup
7.5. NetBackup 7.6 screen shots are used and may differ slightly from those in NetBackup 7.5. Symantec
recommends that any customer installing Replication Director use the latest NetBackup version.
Note: In this document NetApp “OnCommand” and “DFM” are used interchangeably.
Page 2
Configuration Options
The following information should be consulted before and during the installation process to assist with
Replication Director configuration.
Pre-Configuration Tools
Prior to installation, please visit the following link for tools created by Symantec to make the Replication
Director installation and configuration easier.
http://www.symantec.com/docs/DOC5240
This page contains three items provided by Symantec engineering: a checklist document, the “NetApp
Readiness Checker” (NARC) tool and the “Dry Run” tool.
Checklist
The checklist is a document that can be printed and then used to check off the completed steps. By
completing the checklist the environment is more likely to be ready for Replication Director to be
successful. Steps for determining some of the items in this checklist are included in the other topics in
this document. For example, as the administrator goes through this Installation document, they should
be able to check off the boxes in the checklist thus ensuring the steps have been followed.
NARC Script
This script (found at the link above) has been created to automatically verify the information found in
the checklist. It examines the environment to determine if each item on the checklist is complete. If run
before any configuration has been started most of the line items will “fail.” As the installation proceeds,
the NARC tool will return fewer failures and more successes. The NARC tool runs on the DFM server and
must be run as a privileged user.
Note: The NARC tool requires PERL 5.10 be installed on the DFM server. This is a free download, however
instructions for obtaining and installing PERL is beyond the scope of this document.
To use the NARC tool, simply unzip the .zip file to a subdirectory on the DFM server. After PERL is
installed, the tool can be run by typing the following at a command line:
narc.pl
There are no command line options associated with the script and the script can take up to 30 minutes
to run. Once a run is successful and any failures have been troubleshot, the Replication Director
environment should be ready to continue to the NetBackup configuration covered later in this
document.
While the script is running, you will see a “Working!” note on the screen as noted in Figure 1.
Page 3
Figure 1 – NARC Script – Working
The results of a NARC run are shown in Figure 2. (This is an example only. There are errors in this due to
a semi-configured testing environment).
Figure 2 – NARC Output
Page 4
Best Practice Tip: If the NARC tool has failures, this is a good indication that Replication Director will not
run successfully, therefore any failures require troubleshooting before Replication Director is ready for
use.
Dry Run Tool
Once the NetApp portion of the configuration has been completed (outlined later in this document), the
Dry Run Tool can be run on the NetBackup master. The requirements for the Dry Run script are similar
to the NARC script (PERL must be installed) however the functionality is different. The Dry Run script is
run on the NetBackup master (thus PERL must be installed on the NetBackup master) and will create
things like storage units, policies, SLPs and the disk pool temporarily to test the NetBackup portion of
Replication Director. Again – this script can only be run AFTER the NetApp setup has been completed.
Note: If the script fails, it will not “clean up” so that troubleshooting is easier. If it is successful it will
clean up the NetBackup functionality it created so you can continue on with the NetBackup configuration
as described later in this document.
Once the dryrun.zip has been downloaded, simply unzip it on the NetBackup master into a temporary
directory and run the following at the command line:
dryrun.pl <command line options>
There are a number of command line switches that must be used.
-storageserver (-sts): The fully qualified domain name of the
OnCommand server to use
-username (-user): The username of the OnCommand server admin
-password (-pw): [OPTIONAL] The password of the OnCommand server
admin.
-mountpoint (-mp): The mountpoint of which a snapshot can be
made.
-no_cleanup (-noclean): [OPTIONAL] The artifacts created by this
script will not be removed upon completion.
An example command line to run would be:
perl dryrun.pl –storageserver –mountpoint –user -password
Best Practice Tip: If a password is not entered, the script will prompt for it and mask the input.
Please refer to the “dryrun_users_guide.docx” file that is included in the .zip file for full instructions.
An example of the dryrun script output is noted in Figure 3 based on the command line above.
The output “fails” because the environment is not fully configured.
Page 5
Figure 3 – Dryrun Script Output
Page 6
NetApp Configuration
The NetApp OnCommand server and filers should be configured prior to the NetBackup environment.
NetBackup requires certain parts of the NetApp environment to be preconfigured – such as the
NetBackup Plug-in installation – to allow communication between the NetBackup master and the
OnCommand server. Also, authentication between the OnCommand Server and the filers must be
correctly configured and disk space on the filers needs to be configured for use by NetBackup. The
volumes that will be protected by Replication Director on the filers need to be configured if they aren’t
already. An area to replicate the data to on the secondary filer also needs to be configured.
Best Practice Tip: Most customers will set up a large aggregate on the secondary filer and set all
replication from the primary filer to this aggregate, rather than creating separate smaller aggregates on
the secondary filer. For example, if the primary filer has 10 x 1 TB volumes to be protected, a 15 TB
aggregate can be set up on the secondary filer as a replication target vs. configuring 10 separate 1.5 TB
aggregates as targets.
If the volumes are being used as DataStores to protect virtual machines and/or Exchange the volumes
need to be set up on the ESX host. These steps typically require the assistance of a NetApp administrator
and possibly the VMware administrator as they require privileges that the NetBackup administrator may
not have.
Best Practice Tip: This guide is meant for use by an administrator who may not be 100% familiar with
NetApp options. It lists a number of configuration options and commands, however there may be other
ways to obtain data and configure the systems that are not covered here. Use whichever method you are
comfortable with.
Best Practice Tip: It is highly recommended that the NetBackup administrator and the NetApp
administrator work very closely together to get this configured. Once the NetApp portion is complete, the
NetApp administrator may not need to be involved in the day to day processing of Replication Director
snapshots.
Best Practice Tip: Once Replication Director snapshots start processing, the NetApp administrator should
examine the snapshots on the filers - and how they appear in the NetApp admin console or on the filer
itself so they do not manually delete them thinking they are fragments or leftover files as shown in Figure
4. The NetApp administrator can show the snapshots by using the following command on the filer:
snaplist <vol-name>
Figure 4 – How Replication Director snapshots appear on a filer
Page 7
OnCommand (DFM) Information
Many customers are new to OnCommand – formerly called the DFM Server. NetBackup communicates
with the OnCommand server directing it to perform operations on the NetApp filers. The NetBackup
master does not communicate directly with the NetApp filers. This can make the DFM server a
bottleneck if too many requests are sent to it.
Note: Consider the following when sizing the OnCommand physical server: the DFM application is a 64bit application when using the supported OnCommand versions (higher than 5.0). The number of CPUs
and the amount of RAM directly impact the ability of the DFM server to process requests from
NetBackup. Refer to the sizing considerations at the end of this document when sizing the OnCommand
server for Replication Director use.
Best Practice Tip: When architecting the Replication Director environment, the number of Qtrees that a
single DFM server can manage is limited to approximately 2500. Therefore a large filer with 10,000
Qtrees would require 4 DFM servers.
Note: NetBackup Replication Director can communicate with more than one DFM server.
The DFM server is the most critical part of the Replication Director environment. Since it is sending
requests to the filers – and the number of requests it can send are limited – performance could be an
issue in a large environment. In many cases multiple OnCommand Servers could be required. Refer to
sizing advisor at the end of this document to understand more on this.
Best Practice Tip: When configuring the OnCommand Server the number of storage systems – volumes,
relationships like SnapMirror, SnapVault, the number of operations that will be performed etc. need to
be considered. This is where the OnCommand Sizing Guide can come in handy so the server can be
properly sized.
Configuring the OnCommand Server for Replication Director
Follow these steps to make certain the NetBackup master can communicate with the OnCommand
Server.
Plug-in Installation
The NetApp Plug-in for Symantec NetBackup is the piece that enables the communication between
NetBackup and the OnCommand Server (this is the OST plug-in). Use these steps to install the Plug-in.
Note: There is no configuration needed for the Plug-in beyond installing it.
1. Install the NetBackup Plug-in v 1.1 on the OnCommand Server using a privileged user (steps
shown are for a Windows server):
a. Can be downloaded from the NetApp NOW site (requires an account).
b. Review the Release Notes:
i. https://library.netapp.com/ecm/ecm_get_file/ECMP1140478
Page 8
c. Go to Downloads > Software and choose NetApp Plug-in for Symantec NetBackup.
d. Choose Platform (Windows or Linux) and click GO!
e. Choose version 1.1 for NetBackup RD 7.6 and click “View and Download.”
f.
Read the information, scroll to the bottom of the page and click CONTINUE.
g. Accept the agreement, and then download the Plug-in as shown in the box below.
2. Once downloaded, simply click on the executable to install the Plug-in:
a. For the 1.1 version of the Plug-in, a note will pop up indicating that all NetBackup
masters, media servers and clients need to be at NetBackup 7.6.
Please note that this only pertains to media servers and clients that will be used with
Replication Director. NetBackup masters support “down-rev” media servers and clients
and mixed revision environments therefore you can simply upgrade the media server and
clients that will be used for Replication Director if you choose to do so.
b. Installation will take approximately 3 minutes.
3. Once the Plug-in finishes, one way to determine if it is installed is to use the NetApp
Management Console.
a. Data > Groups and look under “Global” for the NetBackup group (Figure 4).
This Group is created when the Plug-in is installed.
Page 9
Figure 5 – NetBackup Group created by Plug-in Installation
4. Another way to check is by typing the following command line on the OnCommand Server:
dfm group list –m NetBackup
Best Practice Tip: NetBackup must be authenticated to talk to the OnCommand Server, therefore the
“root” or “administrator” password will be required for this system. The OnCommand administrator will
need to either provide this to the NetBackup administrator or will need to type it in during the NetBackup
configuration process. It only needs to be entered a single time unless the password changes. The steps
to authenticate are covered later in the NetBackup configuration portion of this manual.
Configuring communications between the OnCommand Server and the Filers
The OnCommand Server needs higher level access to the filers than is typically granted by default. The
OnCommand Server sends information to the filer via HTTP therefore it must be granted the ability to do
so.
Page 10
To configure the OnCommand Server to be allowed access to the filers perform the following steps:
1. On the filer type the following command line and compare it to the information below:
options http
2. The output might look similar to the information below depending on the configuration in your
environment:
httpd.access
legacy
httpd.admin.access
legacy
httpd.admin.enable
off
httpd.admin.hostsequiv.enable off
httpd.admin.max_connections 512
httpd.admin.ssl.enable
on
httpd.admin.top-page.authentication on
httpd.autoindex.enable
off
httpd.bypass_traverse_checking off
httpd.enable
off
httpd.ipv6.enable
off
httpd.log.format
common
httpd.method.trace.enable off
httpd.rootdir
/vol/vol0/home/http
httpd.timeout
300
httpd.timewait.enable
off
This may or may not allow OnCommand the required permissions depending on other options in
your environment.
3. To make certain that OnCommand has enough privileges, the access should be configured as
shown in the following screen shot:
Page 11
httpd.access
all
httpd.admin.access
all
httpd.admin.enable
on
httpd.admin.hostsequiv.enable off
httpd.admin.max_connections 512
httpd.admin.ssl.enable
on
httpd.admin.top-page.authentication on
httpd.autoindex.enable
off
httpd.bypass_traverse_checking off
httpd.enable
on
httpd.ipv6.enable
on
httpd.log.format
common (value might be overwritten in takeover)
httpd.method.trace.enable on
httpd.rootdir
/vol/vol0/home/http
httpd.timeout
300
(value might be overwritten in takeover)
httpd.timewait.enable
off
(value might be overwritten in takeover)
4.
If you are not able to set the access to “all” due to security restrictions (and you choose to use
Legacy), you can simply add the OnCommand Server to the hosts.equiv file on each filer by
performing the following steps: NOTE: These commands below will overwrite the current file –
if you do this incorrectly you could disable your current environment. These commands should
ONLY be used if you know what you are doing with modifying filer files.
a. On the filer - log in as root.
b. See if the OnCommand Server is already added by typing the following at the command
line.
rdfile /etc/hosts.equiv
c. if the OnCommand server is not in the file, type the following command line to add it:
wrfile /etc/hosts.equiv –a <ONCOMMAND SERVER NAME>
Hit “Control – C” to save and exit
Type rdfile /etc/hosts.equiv to make sure the information was saved
Best Practice Tip: One need not enable “httpd.admin.enable” although for features such as SnapDiff that
uses ZAPI it is better to turn it on.
After making these changes the DFM server should have the correct permissions to properly
communicate with the filers to make Replication Director work properly.
Filer Configuration
There are a number of options that need to be checked on each filer that will be used for Replication
Director. These options may or may not already be configured depending on the standards in the
customer environment. These configuration options are required and therefore may require the
customer to change a standard configuration and possibly a security policy.
Page 12
Unicode configuration
Unicode must be turned on for all filers that will have Replication Director snapshots.
From the DFM server type the following command line to determine if Unicode is already set correctly:
dfm run cmd <name of filer> vol status
The result – if the ucode is set correctly, will display similar to the screen shot below.
If the ucode is set to off, it can be enabled on each filer by logging in as root and typing:
vol options [VOLUME TO BE MODIFIED] convert_ucode on
vol options [VOLUME TO BE MODIFIED] create_ucode on
Best Practice Tip: The ucode must be configured to on for each volume that will be protected by
Replication Director.
NetApp Licensing Configuration
Replication Director requires a number of licenses from a NetApp perspective. From a NetBackup
perspective simply unlocking Replication Director with a license key (automatically unlocked when using
capacity licensing) will allow for all RD related options. However the NetApp licensing is more granular.
The following licenses are required based on the source and target filers. This guide may not be
comprehensive and depending on what processes the customer is performing some of these licenses
may not be needed. It is always recommended to check with a NetApp Sales team to determine license
needs.
 SnapMirror
 SnapVault ONTAP primary
 SnapVault ONTAP secondary
 SnapRestore
 FlexClone
 CIFS
 NFS
 iSCSI
 NDMP
 SnapDrive for Windows Client license if using block storage on Windows
Page 13
Best Practice Tip: Some of the licenses are optional depending on what the customer wants to do.
To check to see if the licenses are properly installed, run the following commands from the DFM server:
dfm run cmd <filer name> license
This will show whether licenses are installed and/or enabled and can be compared to the list above.
Best Practice Tip: The NARC script will confirm if the licenses on the filers are installed. Any licensing
error needs to be corrected for Replication Director to work.
If you are missing a license, obtain the license from your NetApp sales rep and install it by typing the
following on the filer:
license add <license key>
Best Practice Tip: If you are missing a license, it is a recommendation that you purchase a permanent
license key from NetApp vs. installing a temporary key unless you are simply evaluating the Replication
Director feature. A number of customers have used temporary keys and have forgotten to add
permanent keys resulting in support calls.
Filer Disk Configuration
The NetApp filer plays a key role in Replication Director. NetBackup simply tells the DFM server to tell
the filers to do what they do best – take hardware snapshots and make replicas of them. For this reason,
configuring the Volumes that will be used as “source” and “targets” correctly before getting started is
critical to a proper architecture.
Best Practice Tip: The filer does not need to be dedicated to Replication Direction. NetBackup – using the
NetBackup Plug-in – will have disk space from the filer added to a Resource Group that only NetBackup
can use as was shown in Figure 4 earlier in this document and NetBackup will not touch or modify any
disk that it has not been granted access to using the Resource Group.
The volumes that will be used for the primary snapshot should already be configured and do not require
any special consideration. They are simply mounted using CIFS or NFS to a host which is specified in the
NetBackup Policy (outlined later in this document) and are snapped. However the target volumes may
require additional privileges so that the data can be written to them.
The information shown here will use the OnCommand System Manager GUI to perform the steps. They
can also be done using the filer command line however that detail is beyond the scope of this document.
To configure a target volume for use by Replication Director, perform the following steps:
1. After logging into the System Manager, choose the filer that will be used for the replication
targets as shown in Figure 6 (this will require root login password to the filer).
Page 14
Figure 6 – System Manager – Choosing the Filer for Targets
2. Once logged in, disks will need to be added to an aggregate that can then be used for a Volume.
3. Click on Storage > Disks to make certain there are disk available.
Note: In many cases on existing filers all disks have been used to create existing aggregates.
Replication Director requires an aggregate and volume dedicated to it, therefore on “full” filers,
disks will need to be freed up from existing aggregates so they can be used for NetBackup.
Explaining how to do this is beyond the scope of this document.
4. Click on Aggregates > Create - which will open a Wizard > Click Next.
5. Name the aggregate and choose the RAID type > Click Next.
Note: From a Replication Director perspective the Raid Type and “Enable Synchronous Mirroring”
have no impact – use the settings you are most comfortable with or simply leave the defaults.
Best Practice Tip: When naming the aggregate for use as the Replication Director target it is a good idea
to make the name descriptive enough that it indicates it is for use by NetBackup or Replication Director.
6. Select the disks for use in the target and click Create.
Best Practice Tip: If you are not familiar with creating aggregates and volumes you should seek help
from a NetApp administrator or Sales Engineer.
Best Practice Tip: When creating the aggregate for use by the Target for Replication Director, make the
name descriptive enough that it can be found in the list of aggregates in the next step.
Once the aggregate has been created it is ready to be added into the Resource Pool that was created
when the Plug-in was installed. This will require the use of the NetApp Management Console. For the
purposes of this document version 3.1 was used therefore any screen shots are from this version.
Page 15
Resource Pool Configuration
Logging into the NetApp Management Console will require a root password for the OnCommand Server.
Once logged in. You should see the screen in Figure 7:
Figure 7 – NetApp Management Console for Resource Pool Configuration
Once on this screen, perform the following steps to add the aggregate to the Resource Pool:
1. Click on Data on the left hand side.
2. Click on Resource Pools.
3. Click on Add. This will open a Wizard.
4. Click Next.
5. Under “Name” type in the name you want to use. Make the name descriptive enough that you
know this will be the Resource Pool target used for Replication Director.
Best Practice Tip: When naming things, always make sure to make them descriptive enough that the
NetBackup administrator and the NetApp administrator will know these are for Replication Director.
Otherwise an administrator could delete them if they are unfamiliar.
Page 16
6. You can either fill out the rest of the information on the page or simply leave them at default,
then click Next.
7. Change the Resource Type to “Aggregates” as shown in Figure 8.
Note: This step is often missed by the admin configuring Replication Director.
Figure 8 – Resource Pool Wizard
8. At this point you should see the aggregate you created in the previous section. Choose it and
click the > button to move it into the “Resources in this resource pool” box on the right.
Page 17
9. Note: To enable Dedupe on the resource pool add #dedupe# in the resource pool label.
10. Depending on your environment, you can change the information on the Space Thresholds page
shown in Figure 9, or you can simply leave them at default and click Next, then Finish.
Figure 9 – Space Thresholds Screen
Page 18
A Data Resource Pool has now been created so it can be used by NetBackup – however we still need to
add this Resource Pool into the NetBackup Group that was created when the Plug-in was installed.
Follow these steps to perform this action.
1. Click on Groups on the left hand navigation bar (under the Data tab).
2. Select “NetBackup” under “Global” and click Edit.
Best Practice Tip: Do not click Add. We are “editing” the NetBackup Group that was created by the Plugin, not creating a new Group. This step is often done incorrectly which can lead to failures.
3. Click the Members tab.
4. Change the Category to “Resource Pools” as shown in Figure 10.
Figure 10 – Members Selection of a Resource Pool
5. Find the Resource Pool that was just created and use the > button to move it to Selected
Resources on the right. Then click OK.
Performing these steps allows NetBackup to see the aggregate as a Resource Pool Member. This is what
keeps NetBackup from utilizing any part of the filer that has not specifically been allocated to it.
At this point, the NetApp configuration is complete. The remaining steps will be done on the NetBackup
master.
Page 19
DFM Configuration for a vFiler
vFiler is supported only as source in the Replication Director solution. Add the pfiler (Physical-filer) IP to
your DFM under the Hosts tab. Make sure NDMP is enabled on the vFiler. vFiler units will be
automatically detected as shown below.
In the NetBackup configuration add the vFiler IP as the client while configuring Replication Director
backups.
The rest of the configuration remains the same.
Page 20
NetBackup Configuration
Once the filers have been configured and the communication between the OnCommand Server and the
filers has been completed, the next steps are performed on the NetBackup master. These include
authenticating the master to give it permission to talk to the OnCommand Server, creating Storage
Units, creating Storage Lifecycle Policies and a Policy. These steps are outlined in this section.
NetBackup to DFM Credential Configuration
The NetBackup master must be able to communicate with the DFM server at an “administrator” or
“root” level. Therefore the administrator/root password is required to complete this step. To create this
authentication, perform the following steps using the NetBackup GUI on the master server that will be
used to “talk” to the OnCommand Server.
1. Using the NetBackup GUI click Credentials on the left hand bar under Media and Device
Management, then click on Storage Servers.
2. Right click and choose “New.”
This will open a Storage Server Configuration Wizard.
3. Click Next to proceed.
4. Under Select the type of disk storage to configure, choose “OpenStorage” and click Next.
Best Practice Tip: By choosing this option, it limits the following choices to only those that use the OST
Plug-in Options which include the NetBackup Plug-in from NetApp.
5. Enter the name of the OnCommand Server under “Storage Server Name.”
6. Using the dropdown for Storage Server Type, choose “NetApp OnCommand Server.”
7. Under the Media Server dropdown choose the media server that will be used for moving data.
8. Under the “Enter storage server credentials enter the OnCommand user name (typically root or
administrator) and the password and click Next.
This will validate the information and will then take you automatically to the Disk Pool Configuration
Wizard.
Best Practice Tip: If this step fails, the password may be incorrect. This password only needs to be
entered one time (unless it changes later) therefore the NetBackup admin may need to have the
OnCommand admin available to type the password in. If Replication Director works for a period of time
then suddenly stops this should be the first thing to check when troubleshooting.
Page 21
NetBackup Disk Pool Creation
Once authentication is finished, the Wizard will continue automatically to the Disk Pool creation wizard.
Complete these steps to create the Primary snapshot area.
Best Practice Tip: The NetBackup Plug-in provides logic to understand where to create the primary
snapshot. This is done on the primary filer – however you must configure a Disk Pool for it even though
you have not created Resources for it. When the initial snapshot is run it will be created on the primary
filer. Secondary replication will be on the Target that was created earlier.
Continuing with the wizard, perform the following steps:
1. Click Next to start the wizard.
2. Under “Type” of disk pool choose “OpenStorage (Network_NTAP) and click Next.
a. Depending on what options have been configured within NetBackup this may be the
only option.
3. Under Select Storage Server choose the OnCommand Server that was configured in the previous
step and click Next.
4. In this step, refer to Figure 10. Choose “Primary Snapshot” in the white box which will then grey
out the options above the selection. Then choose Next.
Page 22
Figure 11 – Primary Snapshot
Best Practice Tip: As noted, this step tells the filer to create the Primary Snapshot on the Primary filer. No
storage was “configured” for this step; however a Disk Pool still needs to be created so NetBackup can
use it as a “step” in the SLP.
5. Give this disk pool a name – something descriptive for Replication Director so that it will be easy
to identify as a Primary Disk Pool snapshot for Replication Director.
The Comments are optional and the Limit I/O streams can be left at default.
6. Click Next twice. The disk pool will be authenticated and created.
Best Practice Tip: Any error at this stage will mean that Replication Director will not run successfully.
Each of these steps validates the environment for a correct configuration therefore any error needs to be
troubleshot before configuration can continue.
Page 23
NetBackup Storage Unit Creation
The next step in the wizard is to create a Storage Unit. Follow these steps to create the Primary Storage
Unit for the initial snapshot.
Best Practice Tip: The Storage Unit is what the Storage Lifecycle Policy uses to perform its “steps”.
Naming them should indicate they are a Replication Director Storage Unit and whether they are for
Primary, Secondary or other storage.
1. The wizard will automatically choose the Disk Pool that was created in the previous section.
Click Next.
2. Choose a name that follows the Best Practice Tip above and click Next.
a. Maximum concurrent jobs should be limited to 1 until after testing is complete then this
can be revisited.
Best Practice Tip: Under the Media Server screen there is an option (default) to use “any available Media
Server to transport data.” Typically when configuring Replication Director for the first time, a single
media server should be chosen. Additional media servers can be chosen after RD is working properly and
needs to be scaled.
3.
The Storage Unit is now created. Again, if any errors are noted they must be corrected before
moving on.
Additional NetBackup Configuration – “Target” Disk and Storage Unit
Now that the Primary snapshot area has been configured, the target must be created. This will utilize
the Resource Pool that was created previously. Perform the following steps on the NetBackup GUI to
create this area for use as a Replication Target.
1. Refer to Figure 12 and choose the master at the top of the GUI on the left. Then click on
Configure Disk Pool to start the wizard again.
Page 24
Figure 12 – Starting the Disk Pool Wizard
2. Click Next to start the wizard.
3. Choose the Type of “OpenStorage (Network_NTAP)” similar to the section above and click Next.
4. Select the Storage Server that was configured earlier and click Next.
5. Choose the Resource Pool that was configured in the NetApp section. Other options will be
greyed out (see Figure 13) then click Next.
a. As noted, this is where using descriptive names for all Replication Director options will
come in handy.
Page 25
Figure 13 – Selecting the Replication Target
6. Choose a name for the Disk Pool that is indicative of the fact it is a Replication Target disk pool
and click next.
Information about the other options on the page was provided in the previous section.
7. The Wizard will create the disk pool.
As noted in the previous section – if this fails Replication Director will not run. Troubleshooting
is needed.
8. The wizard will then move to the Storage Unit configuration that was covered in the section
above.
At this point, the disk and storage units are complete and the Storage Lifecycle Policy can be created by
following the steps in the next section.
Page 26
Storage Lifecycle Policy Configuration
The Storage Lifecycle Policy (SLP) is used to create “steps” for performing tasks. For example, the first
step creates the Snapshot, the second step creates the Replication of this snapshot and the third step
creates a copy to tape, disk, dedupe disk etc. This is all done automatically based on the SLP
configuration. In NetBackup 7.6 “SLP Windows” can be used to schedule these steps.
Best Practice Tip: An SLP can be used for more than one Policy. If the customer is doing a simple
Snapshot > Replication > Disk or Tape Copy for the majority of the data, a single SLP can be configured to
perform these steps and each Policy can use it. Creating a new SLP for every Policy creates management
issues.
Best Practice Tip: Configuring the SLP will be the last step before Policy configuration. By this time, all
other configuration besides the Policy should be complete and the checklist should be finished. The SLP
does a validation step and if the rest of the configuration is not complete it will fail.
Configure the Storage Lifecycle Policy by following the steps below:
1.
On the left side of the NetBackup GUI click on Storage > Storage Lifecycle Policies.
2. Right click > New Storage Lifecycle Policy.
3. Give it a name – something that will let the administrator know it is an SLP for Replication
Director.
4. Click on Add to create the first “step.”
Note: Clicking on OK will close the window.
5. For the first process a Snapshot will be created – select Snapshot using the dropdown next to
Operation.
6. Change the Storage Unit to the Primary Storage Unit created earlier in this document.
7. Set the retention of the primary snapshot based on the needs of the environment and click OK
a. “Maximum Snapshot Limit” is configured in the Policy as noted below.
b. “Expire after copy” will delete the primary snapshot after it has been replicated.
c. “Fixed” allows a time based retention to be configured and a Retention Period option
will be available.
Best Practice Tip: Most customers choose the default of Maximum Snapshot Limit or Expire after Copy.
Using the “fixed” retention can cause the primary filer disk to fill up thus causing failures. Use this setting
with caution.
8. With the first step highlighted, choose Add again to create the secondary copy.
Page 27
By highlighting the first step, the next action will be a “child” of the “parent job.” If the first step
is not highlighted it will be an independent action.
9. Under Operation choose Replication.
Best Practice Tip: If the environment does not require a replicated copy – for example if there is only one
filer in the environment – then the other options could be chosen. “Backup from Snapshot” will send the
data to disk or tape and “Index from Snapshot” will create the NetBackup Catalog entries so that
Operational Restore from OpsCenter can find single files.
10. Choose the Target Storage Unit created earlier.
11. Select the Retention Type as required by the environment.
a. “Fixed” allows a retention period to be selected.
b. “Mirror” will make the replicated copy expire when the primary copy expires.
c. “Expire after copy” will delete the replicated copy when the data has been sent to
tertiary storage such as disk or tape.
Best Practice Tip: One of the frequently asked questions with regards to Replication Director is “how do
you choose between SnapMirror and SnapVault and why are both licenses required”. This choice is based
on the replication retention option chosen in the SLP. When “Mirror” is chosen, SnapMirror is used and
the replicated copy expires when the snapshot expires. When “Fixed” or “Expire After Copy” is selected,
SnapVault is used and the replicated copy expires independent of the snapshot.
12. If this step should not be run until a later time, choose the “Window” tab as shown in Figure 14.
Figure 14 – SLP Window Tab
13. Once chosen, a window – similar to the NetBackup Schedule Window – can be chosen for when
this step should run. If no window is chosen, the step will run immediately after the first step –
Page 28
depending on the time parameter that is configured in the Host Properties (default is five
minutes).
14. The other option is to wait for the primary copy to be close to expiration before creating a copy.
This can be accomplished by choosing the “Postpone creation of this copy until the source copy
is about to expire” check box in the middle of the screen.
a. When this box is checked, by default the process will start four hours before the primary
copy is set to expire. However the primary copy will not expire until the copy finishes. If
the copy fails, it will retry again and the primary will not expire until it completes
successfully. This could fill up the Primary disk therefore any failures should be
troubleshot immediately.
15. Once this step is finished the GUI will show the step “tabbed” under the first step as shown in
Figure 15 below. This makes it easy to determine if the SLP is configured correctly.
16. Finally, add a tertiary step to the SLP by clicking the Add button again. In the example shown in
Figure 15, an “Index from snapshot” option was chosen.
Best Practice Tip: A destination storage must be chosen for this step. Typically it is a recommendation
that the Secondary Storage Unit (where the Target has been produced) is the best option. This
determines which copy is used (mounted) for creating the Index step. There is some overhead on the
system while Indexing is taking place, therefore it should be done from the replicated copy vs. the
Primary copy. This can be achieved by choosing the Storage Unit used to create the secondary copy. If
there is no secondary copy (a single filer in the environment) then there is no choice but to choose the
primary copy.
Page 29
Figure 15 – Completed SLP
17. Click OK. A short Validation process will run. Any failures must be addressed before moving on
to the Policy creation.
Policy Creation
Creating a Policy for Replication Director is the same as creating a Policy for NetBackup therefore only
the parts that change from a Replication Director perspective will be covered in this guide. Choosing the
“Use Replication Director” check box will change some of the options available in the Policy. Follow
these steps to create a RD Policy that will utilize the Storage Lifecycle Policy that was created in the
previous section.
1. From the NetBackup GUI on the left side, choose Policies, right click, and choose New Policy.
2. Name the Policy based on the naming conventions of the environment.
Best Practice Tip: While the naming conventions of the environment must be considered, a name should
be chosen that indicates this is a Replication Director Policy to make troubleshooting when looking at log
files easier.
3. On the Policy Attributes Tab as shown in Figure 15, choose the SLP that was created under
Policy Storage.
4. Place a check next to the Use Replication Director box.
a. Note that by doing so, some of the options become greyed out.
Page 30
Figure 16 – Policy Options
5. Under the Options box next to the “Use Replication Director” the number of Maximum
Snapshots can be configured as was discussed in the Storage Lifecycle Policy creation above.
Be careful with this number. Creating too many snapshots can fill up the disk on the Primary filer
if too many are saved, or snapshots are taken too often.
6. Configure the Schedules tab to determine when this job should start like you would a normal
NetBackup Policy.
7. Under the Clients tab, choose the client that will have the NFS or CIFS mount point mounted.
Best Practice Tip: In most cases, customers have found that using a single system – such as a media
server – to mount up the NFS and CIFS mount points is a better option that using the system that has
them mounted. This reduces overheard on the primary system while the snapshot is taken. If this option
is chosen, the media server (or other client) will need permissions to mount the volumes from the filers as
read/write. One thing to note – CIFS mounts on Windows will mount automatically to this client system;
Page 31
however NFS mounts on UNIX will need to be mounted manually. This is a limitation of NFS and not of
Replication Director. In most cases customers who have used NFS mounts have simply left them mounted
on this client system and the primary system.
8. Under the Backup Selections tab choose the mount point that will be snapped. Typically the
format is similar to the following based on a Windows CIFS mount:
a. \\FILER_NAME\VOLUME_NAME
Best Practice Tip: To make certain that NetBackup will have access to the mount point, manually mount
it to the client that will be used in the Policy Clients tab, navigate to it and make certain that a file can be
created and removed. If it will not mount, or a “permission denied” is show when attempting to
manipulate files this means there are insufficient permissions on the mount point and NetBackup will be
unable to create the snapshot.
9. When the mount point is added, a warning box will pop up indicating that the NetBackup client
used must have sufficient permissions including increased privileges on the NetBackup Service.
Changing this permission level for this server is covered below.
10. Click Yes.
11. A “Validate Policy” box will appear. Validation can take up to five minutes.
Best Practice Tip: Running a “Complete” check is the best way to determine if the environment is ready
for Replication Director. Any failures must be addressed. Even if the check passes, there could still be
issues in the environment therefore the NARC script should be run again to make certain all checklist
steps have been completed.
VMware Protection with Replication Director
To protect virtual machines – including those containing an Exchange or SQL database requires
additional configuration steps in the Policy. By choosing the Policy Type of “VMware” additional options
will be created. This section covers those options.
Knowledge of the VMware Policy and Virtual Intelligent Policy (VIP) is required to configure this option.
This document does not cover this part of the configuration.
Note: It is beyond the scope of this document to provide steps for creating a NFS mounted Datastore on
an ESX server from a NetApp filer – however this needs to be accomplished before NetBackup and
Replication Director can protect the machines. Only VMs created within a NetApp NFS mounted
Datastore can be protected using this method.
1. Use the steps above to create a new Policy, choose Policy Type of “VMware.”
This will create an additional tab at the top called “VMware.” Refer to Figure 16.
2. Check the Use Replication Director check box.
Page 32
a. The “Use Accelerator” box becomes greyed out due to the fact that NetBackup
Accelerator is not supported with RD and VMware backup types at this time.
Figure 17 – VMware Policy Type with Replication Director
3. Configure the Schedule as required by the environment.
4. The Client tab must be configured based on the VIP as noted above. This is the option that
chooses which Virtual Machines will be protected in the environment.
Note: The information for configuring the clients in a VM environment is documented in the
NetBackup Manuals which can be found at the following link:
http://www.symantec.com/docs/HOWTO66296
5. The Backup Selections tab will be configured automatically depending on choices made in the
Client and VMware tabs.
Page 33
6. In order to protect Exchange or SQL in a NFS Mounted Datastore, the button(s) must be checked
in the VMware Tab as shown in Figure 18:
Figure 18 – Protecting Exchange and/or SQL in a VM with a NFS mounted Datastore
Best Practice Tip: To protect Exchange and SQL in a Datastore, the entire machine must be installed in
the Datastore itself – not just the database. From a NetBackup perspective we are simply protecting
another VM in a Datastore.
Configuring the NetBackup Service on the client used for the Mount Point on Windows
Elevated privileges are required for the client running the Replication Director mount points on
Windows. Typically it will require “administrator” privileges rather than the default “Service” account.
Use these steps to change the Log On Account on Windows.
1. From the Windows Start button under Run type “services.msc” and click OK.
2. Locate the NetBackup Client Service.
Page 34
3. Right click and choose “Properties.”
4. Choose Properties.
5. Change the “Log on as” from the Local System Account to “This Account.”
6. Type in “administrator” and type in the administrator password for the client and click OK.
7. Click on the NetBackup Client Service again, and choose “Restart” to start the Client service with
the elevated permissions.
Page 35
Appendix A
Information is provided in this section to assist with sizing and other options. It is intended to provide
preliminary information and point to links to other documents to provide deeper dive information.
NetApp sizing Advisor
RD Sizing Advisor (Netapp)
1
6
SNAPVAULT
SNAPMIRROR
2
3
DFM Sizing
7
8
ONTAP/SnapVault Sizing
DFM Sizing
ONTAP/SnapMirror Sizing
4
9
Snapvault Sizing
Rapid SnapVault/OSSV Space
Estimator APR13
5
Concurrent streams allowed for a hardware platform
for SnaapMirror and SnapVault Concurrent Streams
SnapMirror Sizing
Calculator
To calculate the SnapMirror/SnapVault throughput required to achieve the desired backup window-Network Throughput
Calculator
1. SnapVault Workflow
Page 36
2.
DFM Sizing will help you decide on how many DFM servers you would you need in your
environment to configure RD. A single DFM can manage up-to 3000 relationships. Number of
relationships within RD is equal to number of qtrees to be protected.
For example: Consider X number of qtrees to be protected by RD, as stated earlier X is equal to
Number of relationships. We know 3000 relationships can be protected via a single DFM, hence
X/3000 will give you number of DFM required to configure RD in your environment.
For further information of DFM sizing please refer to the following link:
https://kb.netapp.com/library/CUSTOMER/solutions/1013266/OnCommand%205.0Sizing%20Guide.pdf
3. ONTAP sizing: Size your ONTAP infrastructure to meet the needs of backup.
4. SnapVault sizing: Size your SnapVault infrastructure using the sizing tool Rapid SnapVault/OSSV
Space Estimator APR13
5. Concurrent streams allowed for a hardware platform will help to schedule jobs in NetBackup to
achieve parallelism in your backups Concurrent Streams Calculator
6. SnapMirror Workflow.
7. DFM Sizing will help you decide on how many DFM servers one would need in their environment
to configure RD. A single DFM can manage up-to 3000 relationships.
For SnapMirror,
relationships are at volume level, so number of relationships is directly proportional to number
of volumes to be protected. Hence, X number of volumes correspond to number of relationships
managed and X/3000 will give number of DFM required to setup RD.
8. ONTAP Sizing: Size your ONTAP infrastructure accordingly to establish mirror relationships
9. SnapMirror Sizing: Always make sure the destination (target) resource pool has enough free
space as your source so that DFM can provision the storage.
10. Concurrent streams allowed for a hardware platform will help to schedule jobs in NetBackup to
achieve parallelism in your backups Concurrent Streams Calculator
For more information on sizing please contact your respective Symantec or NetApp SE.
Page 37
Symantec Replication Director and NetApp OnCommand – Joint Backup and
Restore Sequence
Backup Sequence:
1. Ensure that database backups are scheduled when there are no jobs running in NetBackup and
OnCommand (DFM).
2. Backup DFM Database
Use the standard DFM database backup procedure as described in the OnCommand Unified
Manager – Operations Manager Administration Guide.
3. Backup NetBackup Database
Use standard NetBackup backup procedures.
Restore sequence:
1. Restore DFM environment and its database.
Use standard DFM database restore procedure as described in the OnCommand Unified
Manager – Operations Manager Administration Guide.
2. Install the NetApp Plug-in for NetBackup.
3. Restore the NetBackup environment and its database
Use standard NetBackup procedures.
Page 38
About Symantec:
Symantec is a global leader in
providing security, storage, and
systems management solutions to
help consumers and organizations
secure
and
manage
their
information-driven world. Our
software and services protect
against more risks at more points,
more completely and efficiently,
enabling confidence wherever
information is used or stored.
Headquartered in Mountain View,
Calif., Symantec has operations in
40 countries. More information is
available at www.symantec.com.
For specific country offices and
Symantec Corporation
contact numbers, please visit our Web
World Headquarters
site: www.symantec.com
350 Ellis Street
Mountain View, CA 94043 USA
+1 (650) 527 8000
+1 (800) 721 3934
Copyright © 2014 Symantec
Corporation. All rights reserved.
Symantec and the Symantec logo
are trademarks or registered
trademarks of Symantec
Corporation or its affiliates in the
U.S. and other countries. Other
names may be trademarks of their
respective owners.

Replication Director

Transcription

Similar documents

dcVAST — Symantec Appliance / NetBackup Media Server

Storage and Information Management Brief VERITAS and Network

NetBackup How-To Guide Configuring MSCS N+1 Environments to Work with the NetBackup

Atlantis Energy Systems Inc.

NetBackup Self Service Installation Guide

3 MTSS Hexagon Assessment Tool - Clare

Enterprise Vault How To Guide Setting up Enterprise Vault Migrations with NetBackup

AFconf2016_PrelProg_21June16

NetBackupâ¢ Commands Reference Guide: UNIX, Windows, and