netbackup 7.6 replication director a hands on...

NetBackup 7.6 Replication Director A Hands On Experience

Description Through this hands on lab you can test drive Replication Director and experience for yourself this easy to use, powerful feature.

Once finished with this lab you will have a much better understanding of the power of Replication Director and how it can augment your backup and restore options in NetApp environments.

For successful completion of this lab it is assumed that you have a basic knowledge of backup and NetApp storage array concepts.

NOTE: This lab is self-guided if you want to get started. Otherwise, wait for the instructor and follow along.

At the end of this lab, you should be able to

Configure NetApp based snapshots using Replication Director wizards

Backup array-based data using NetApp’s snapshot technologies including SnapVault and SnapMirror

Protect Virtual Machines using Snapshots Implement NetBackup Storage Lifecycle Policies across multiple

backup destinations Restore single files from multiple backup destinations Use OpsCenter’s Operational Restore feature to better

understand every restore option

Notes This lab uses a Beta version of NetBackup 7.6. The full GA release of NetBackup 7.6 is expected sometime in 2013

You can either get started or wait for the instructor. The lab is self-guided however if you get stuck it may be hard to figure out where you are to help you. The recommendation is to walk through the Lab at the same time as the instructor

The instructor will be walking through these steps on the main projector as well in case you get stuck

Carefully follow the instructions outlined in this document. Skipping steps or not performing a step correctly can prevent you from successfully completing this lab

Be sure to ask the lab assistants any questions you may have by raising your hand

Symantec Vision 2013

NetBackup 7.6 Replication Director Hands On Lab Student Guide

2 of 14

Lab Configuration

This VMware Workstation based hands on lab is designed to simulate an actual NetBackup and NetApp Replication Director configuration however it is simplified for the purposes of the lab so it will run in VM’s. It is comprised of 5 images. They are described as follows: NBU1_Vision2013 - This is the NetBackup master server, media server and client. This system is also the OnCommand server and the vSphere Client controller as well as the OpsCenter Master. It is NOT recommended that in your environment you attempt to put this many applications on a single system.

Note: The LTO4_TAPE storage unit on the NetBackup Master (used later in the lab) is actually a Disk Storage Unit named LTO4 for a tape-out example. These machines are NOT connected to any external storage

ONCOMMAND1_Vision2013 – The OnCommand system that controls the NetApp Filers ESX1_Vision2013 – This is an ESXi that contains five VM’s (VM001- VM005) for use to demonstrate VMware protection with Replication Director and NetApp ONTAP1_Vision2013 and ONTAP2_Vision2013 – These are two software based NetApp Simulators. These images accurately simulate a NetApp Filer running NetApp’s Data ONTAP operating system.

Lab Overview

The purpose of this lab is to introduce you to the powerful capabilities that the combination of NetBackup Replication Director and NetApp technologies provide in the data protection space.

The lab will walk you through the following steps:

1. Using existing NetApp Aggregates to configure a new NetBackup Resource Pool that will be visible to NetBackup. This storage will be used to create Storage Pools and Storage Units to be used as Primary and Secondary storage (Snapshot Target and Replication Target)

2. Defining NetApp OnCommand system as a storage server and creating NetBackup Credentials so that NetBackup can “talk” to the OnCommand server and control the NetApp Filers via this communication. This is doing via the NetBackup Plugin created and maintained by NetApp via OST

3. Configure a NetApp SnapMirror-based disk pool and storage unit

4. Creating the NetBackup Storage Lifecycle Policy (SLP)

5. Protecting the data by creating a NetBackup Policy

6. Creating a snapshot of the data

7. Replicating that snapshot to a secondary filer using NetApp tools (managed by NetBackup)

8. Creating a disk based tertiary copy of the data which includes an Indexing step to create the NetBackup Catalog “.f” file

9. Protecting VMware machines using the same method (available in NetBackup 7.6)

10. Various restore options for the data



3 of 14

To get started, we need to have some storage from the NetApp Filer configured for use by NetBackup. There has already been some pre-work done to get to this stage, but it is beyond the scope of this lab to show all the NetApp configuration. So we will start with something simple – adding an Aggregate into the NetBackup Resource Pool.

Lab Exercise 1: Exploring the NetApp Configuration

Before protecting data that is hosted on the NetApp filer, the storage administrator needs to perform a few simple tasks as follows:

1. Define the storage to be protected 2. Define the storage location and space to be used for snapshots 3. Place the storage location to be used for snapshots within the proper

NetApp Group and Resource Pool

5 minutes

To log into the Windows VM, use the following: o Username: Administrator o Password: symc4now

We need to log into the OnCommand Application using the NetApp Management Console 3.1 link on the desktop to complete these tasks.

1. Double-click on the NetApp Management Console 3.1 icon located on the desktop 2. Login to the NetApp Management Console using the following entries:

a. Server = oncommand1 b. User = administrator c. Password = symc4now

3. Click on Connect

You should be able to see the NetApp Management Console

4. Click on the Hosts tab on the bottom left

You will see “ontap1” and “ontap2” listed. One of these filers may not have correctly logged into the OnCommand system. If it hasn’t logged in, it will show as offline.

5. If either of the filers status is Offline, right-click on that filer and select Refresh a. The filer should now show as Online.

6. On the NetApp Management Console on the left side, click on the Data button 7. Now click on Resource Pools

At this time, no Resource Pools have been created for NetBackup to use so that will be our first step in the process. We need to create a single Resource Pools for our basic replication target.

Note: The NetBackup Plug-in from NetApp has already been installed on the OnCommand server. When installed it creates a NetBackup Group under Data > Groups > Global

For this lab, the NetApp Aggregates have already been created using the NetApp tools. We will use these Aggregates to create the Resource Pool in the steps below.



4 of 14

Be careful during these steps. Follow the instructions exactly. Make sure you complete each step before moving on to the next, otherwise the lab will not work.

8. On the Resource Pool page, click Add 9. This opens up a Resource Pool Wizard. Click Next 10. Type in NBU_SnapMirror_RP in the Name field. Leave the rest at default and click Next 11. Change the Resource Type from Hosts to Aggregates using the dropdown 12. Select ontap2:aggr_OT2_SM and then click on the top right single arrow (>) to move that

aggregate into the box on the right side, then click Next 13. The Resource pool label is optional – At this time do not add a label for the purposes of this lab.

Click Next 14. This screen allows you to set some thresholds. Leave them all at default and click Next, then

Finish

Note: Your screen should now show a Resource Pool Now we need to add this newly created Resource Pool into the NetBackup Group so that it can be seen and used by NetBackup to create disk pools and storage units

15. Click on Groups on the left side navigation bar under the Data tab 16. Click on NetBackup under the Global group to highlight it. You will note that there are no

members listed at this time. 17. With NetBackup highlighted, click on Edit 18. Click on the Members tab next to the Group Name tab 19. Under Select a Category use the dropdown to select Resource Pools 20. You should see the NBU_SnapMirror_RP pool that we created in the last step. Highlight it using

and use the > button to move it to the right under Selected Resources 21. Click on OK.

a. You will notice that it now shows up under Members for the NetBackup Group. This means that NetBackup will now “see” this Resource Pool via the OST interface.

Our NetApp configuration portion is complete. You can now close the NetApp Management Console.

This completes Lab exercise 1. Now let’s take a look at how NetBackup creates the storage for use by Replication Director.

Lab Exercise 2: Authentication and Storage Creation

As part of the backup process the NetApp administrator has previously configured storage that is designated for use as space for snapshots. The snapshots created within this space will be created and controlled by NetBackup for use as part or whole of a data protection strategy. In this section we will define access to the NetApp environment through the OnCommand system by entering the OnCommand credentials

7 minutes

You should still be logged into the NBU1 Master Server. Open the NetBackup Admin Console shortcut located on the desktop.



5 of 14

1. Highlight the nbu1 (Master Server) entry at the top left of the NetBackup Admin Console (as seen in the picture) to open the Wizard screen on the right.

2. Double-click on the Configure Disk Storage Servers configuration wizard 3. Click on Next in the Storage Server Configuration Wizard 4. From the Select the type of disk storage to configure pull-down menu, select the OpenStorage

option 5. Select Next

The Add Storage Server interface is where we define the NetApp OnCommand hostname and credentials. We also tell NetBackup that the Storage Server type is NetApp. As described below, provide the following entries:

1. In the box titled Storage Server Name, enter ONCOMMAND1 2. For the Storage server type use the dropdown to select NetApp OnCommand Server 3. Media server is NBU1 (use the pull-down menu). 4. User name is administrator 5. Password: is symc4now 6. Click Next 7. Review the entries and make sure the match the information above exactly, then click Next

If everything was entered correctly you will not see any errors. If something is incorrect hit the Back button to fix it. Most errors at this step occur due to incorrect passwords

8. Click Next

When you click Next, the Disk Pool creation wizard will start. Read the contents of the splash screen and click Next

9. Choose OpenStorage (Network_NTAP) 10. Select Next 11. Verify that the name of the Storage Server is ONCOMMAND1 and that the Type is

Network_NTAP 12. Select Next

The next step will define the primary volume where the snapshot will be stored when RD fires off the snap

13. Select the checkbox next to the PrimarySnapshot entry in the WHITE box under Volume Name as shown in the picture below (do not select Primary at the top)



6 of 14

a. Note that by selecting this checkbox it automatically selects the proper selections for “Primary” and “Replication Source” and greys them out

Note that the primary snapshot location is also considered as the “source” for subsequent snapshots that are created using either NetApp’s SnapVault or SnapMirror technologies.

14. Select Next 15. Here we name the disk pool for the primary NetApp-based storage. Type Primary_DP 16. Click Next 17. Make certain that the Summary screen matches the options you chose, then click Next 18. Verify that the Disk Pool creation was successful 19. If you encounter an error, use the Back button to make corrections otherwise click Next

Now the wizard will walk us through creating a NetBackup Storage Unit that will use the disk pool we have just created

20. Click Next 21. Type Primary_STU in the Storage Unit Name area

a. Do not change any other settings but notice the options. In a Production environment you would have more Media Servers to choose from however you must read the Replication Director manual before choosing additional media servers

22. Click Next 23. Click Finish

We’ve successfully configured the NetApp data location to use for our initial snapshots. We’ve configured this storage in a disk pool and a storage unit. NetBackup can now use this NetApp-based storage as part of a larger data protection plan. This completes Lab Exercise2. Now let’s take a look at configuring the storage to be used for the Replication step that will replicate the data from ONTAP1 to ONTAP2 with NetBackup controlling the process.



7 of 14

Lab Exercise 3: Configure NetApp SnapMirror-based disk pools and storage units

At this point we’ve configured one of the three backup targets (storage units) that will be used as part of our NetApp and NetBackup data protection strategy. Now we will configure our second storage units that involves our second array and NetApp’s powerful SnapMirror technology. The third target was already created for this lab (LTO4_Tape) as noted in the Notes section

5 minutes

1. If the NetBackup GUI is not still open, open it 2. Highlight the nbu1 (Master Server) entry at the top left of the NetBackup Admin Console to

open the Wizard pane on the right like you did in the last Exercise

3. This time, open the Configure Disk Pool configuration wizard

4. Click on Next

5. Select the OpenStorage (Network_NTAP) disk pool type. 6. Select Next

a. Our storage server named ONCOMMAND1 is automatically selected as it is the only storage server in this demo lab environment.

7. Select Next

We’ve previously defined the primary storage. Now we will define the replication targets which are going to utilize the NetApp SnapMirror technology. In our case we are using the Resource pools we created in Lab Exercise 1 to create two Targets – thus we will need to go through this twice.

8. In the bottom white box click on the entry NBU_SnapMirror_RP a. Note that once we’ve selected the checkbox next to the SnapMirror designated storage,

the “Replication Target” checkbox is automatically selected for us and the other options are greyed out

9. Once you’ve verified that your interface is correctly defined, select Next

Now we need to name the Disk Pool we will be using. Let’s make it descriptive.

10. Name the disk pool Snapmirror_DP

11. Select Next 12. Review the Disk Pool Summary screen, then click Next 13. Make sure that the Disk Pool Creation was successful and click Next

From here we need to create the Storage Unit that will use the disk pool we just created

14. Click Next from the Storage Unit Creation screen 15. Name this storage unit Snapmirror_STU

a. Again, note the Media Server option (in this case only one) but do not change the default

16. Click Next, then Finish

We are done creating the storage we will use for Replication Director.



8 of 14

NOTE: Due to a glitch in the NetBackup installation on these VM’s, you now need to close the NetBackup Console GUI and reopen it. Otherwise the LTO4 Disk Storage Unit may not show up in the next Exercise.

This concludes Exercise 3. Now we will take a look at creating the SLP’s and Policy’s that will make use of the storage we have just set up.

Lab Exercise 4: Creating the NetBackup Storage Lifecycle Policy (SLP)

The NetBackup Storage Lifecycle Policy feature is used to automate the movement of backed up data from one storage area to another. Replication Director uses Storage Lifecycle Policies to automatically replicate data between filers and to copy it to traditional backup targets including (but not limited to) tape libraries or deduplication targets. Once configured, Storage Lifecycle Policies can automatically control the entire lifecycle of backed up data including the automatic expiration of NetApp snapshots or data placed on tape.

7 minutes

In this exercise we will create the NetBackup Storage Lifecycle Policy’s that use all three of these storage units in a cascade of automatic transfers. The end result will be three separate copies of the primary data where any one of these copies can be used for restores. If any of these copies has been destroyed or is otherwise unavailable, any one of the remaining copies can easily be used to restore your data. Each of these copies will also have their own retention period that is also automatically administered by NetBackup. Time to create our first Storage Lifecycle Policy for our basic file snapshots and replication.

1. Open the NetBackup Admin Console if you haven’t already a. You should have closed it at the end of Exercise 3. If you didn’t please restart it

2. From the GUI, expand the Storage icon on the left and select Storage Lifecycle Policies 3. Right-click on the empty pane to the right and select New 4. Name the SLP Replication_Director_SLP 5. Click ADD at the bottom left - NOTE: DO NOT click “OK” – this will close the GUI 6. Since our first operation will be a Snapshot, use the dropdown next to Operation to choose

Snapshot 7. Under Destination Storage choose the Primary_STU we created earlier as the Storage Unit 8. Do not change the default on the Retention Type

a. Note: Retention of snapshots is typically managed from the Filer and NetBackup can set the maximum to a higher level than the default of 1, however this is done in another area of the GUI.

9. Click OK 10. Now we need to create the second step – Replication of the Snapshot 11. Highlight the Snapshot operation we just created (it should be highlighted by default) and click

Add a. The purpose of highlighting it is to make this step the “next step” of the SLP process

under the Snapshot step 12. Click Add



9 of 14

13. Under the Operation pull down choose Replication 14. The Snapmirror_STU created earlier since the other Storage will be used for our VM protection 15. Change the Retention Type to Mirror 16. Click OK

Note: In NetBackup 7.6 SLP Windows have been added so if you are familiar with RD from 7.5 you will notice a few new options such as the check box on the screen below. Based on the fact that we only have an hour for this lab we cannot explore SLP Windows however in your production environment they may be very useful

17. Finally, we want to create a Tape Out step (to a simulated tape drive which is actually a disk storage unit) so that an Index will be created

18. Highlight the second step in the SLP if it is not already highlighted, then click Add 19. Choose Backup From Snapshot in the Operation drop down 20. Select LTO4_TAPE as the Storage Unit

a. Note: if this Storage Unit is not showing up, click OK to save the SLP you are working on, close the NBU GUI and reopen it, then go to Storage > SLP and choose the SLP we are working on to get finish this step.

21. Change the Retention Type to Fixed 22. Change the Retention Period to 1 week 23. Click OK 24. Click OK again to close the window

Note: The Index process that happens when we send the data to tape out is what sets this feature apart from using the NetApp Tools. Once the Index is created we can use Operational Restore to “search” for a file name inside the snapshot. There are two ways to create an Index (build a catalog file). First is to send the data to tape or disk using “Backup from Snapshot” which is the method we have chosen for this lab. The second is using a “Index from Snapshot” step which creates the Index but does not move the data to storage.

We also need to create an SLP to protect our Virtual Machines. For the VM protection we are only going to be able to do a snapshot due to the size of the VM’s. Replication (the first one) would take quite a while in our simulated environment. So for the SLP we will do a simple snapshot.

1. With Storage Lifecycle Policies highlighted, right-click on the pane to the right and select New 2. Name the SLP VM_Snaps_SLP 3. Click ADD at the bottom left



10 of 14

4. Since our first operation will be a Snapshot, use the dropdown next to Operation to choose Snapshot

5. Under Destination Storage choose the Primary_STU 6. Do not change the default on the Retention Type 7. Click OK 8. Click OK again to close the window

This completes Lab Exercise 4. In the next Exercise we will create a Policy that uses the SLP we have just created.

Lab Exercise 5: Protecting our data – creating a basic NetBackup Policy for RD

At this point we’ve created all of the components we need to backup our important data. We will put all of these components together by creating and using a NetBackup policy

10 minutes

Many new customers use the Policy creating Wizard. Older NetBackup customers may not use it. For the purposes of this HOL, we will use the Wizard for creating the first Policy and do it manually for the second.

1) In the NetBackup GUI Highlight the nbu1 (Master Server) entry at the top left to open the Wizard pane on the right

2) Select the Create a Policy configuration wizard 3) Make sure that the top option File systems, databases, applications radio button is selected

a. Since we are using RD and SLP’s, we do not choose the Snapshots backup type 4) Click Next 5) Enter Replication_Director as the Policy Name 6) Leave the Policy Type as MS-Windows 7) Click Next 8) Click Add then type in NBU1 as the Client Name and hit Enter – this should auto-discover

the Hardware and OS of the Client (in this case, the Master) 9) Click Next

For the Files, we need to specify a path to a CIFS share that has been created on the filers for our use. Windows will automatically CIFS mount our selection.

10) Click Add then type \\ONTAP1\vol_OT1_PRI and hit Enter a. Note that the character in vol_OT1_PRI is a capital O and not a zero (0). Make sure you

type this path in EXACTLY. In the various runs of this HOL this has been the primary cause of failures.

Note: You will see a warning message that describes how the NetBackup client service needs to be configured. This is related to proper permissions for accessing the CIFS share from the NetBackup application. Since we have already configured permissions, simply click YES to Continue



11 of 14

11) Continue clicking Next three times until the Wizard finishes and then click Finish. Leave settings at default

Now we need to make a few modifications to our Policy that were not part of the Wizard

12) From the NBU Console double click on the Policy we just created by expanding Policies 13) Double click on the Replication_Director Policy 14) Change the Policy Storage to the SLP we created Replication_Director_SLP 15) At the bottom left of the screen, put a check mark next to Use Replication Director

a. You will notice that this changes your available options 16) Click on Options next to the Perform snapshot backups to open an Options pop up window 17) Change the Maximum Snapshots to 5 by clicking on the 1 field and typing 5 18) Click on OK to close the Options window 19) Click on OK to close the Policy window 20) Leave the Validate Policy check box at default of Complete and click OK

At this point the Policy will perform a Validation check. If you have configured everything correctly, this will be successful and you will not get any pop-up windows. If you do get an error window, you may need to go back and figure out which step was not done correctly. Now, let’s start the backup so it will run while we work on the VMware protection snapshots.

1) Choose the Policy we created 2) Right click 3) Select Manual Backup 4) Choose the Full schedule 5) Click OK

This will fire off a snapshot first, then a Replication of the data, then a copy of the data to the disk storage unit and should take about 5 minutes.

This completes Lab Exercise 5. Now let’s go configure the Policy for the VMware backups.

Lab Exercise 6: Protecting Virtual Machines using Replication Director

We have our storage and our SLP configured, now let’s look at the Policy that is used to protect VM’s

5 minutes

There are a number of VM’s that have been created on an ESXi server. Two of them reside on a NetApp NFS share. We will be protecting them using Replication Director and will create the Policy manually. Due to the time it takes in this lab environment to replicate an entire VM the first time, we will simply be doing a snapshot of the VM’s. This is based on the SLP we created for them earlier.

1. Create a new Policy by highlighting Policies in the NBU GUI and clicking Actions > New > New Policy

2. In the Policy Name type VM_RD_Snap. Do not check the Use Policy Configuration Wizard 3. Change the Policy Type to VMware 4. Change Policy Storage to the VM_Snaps_SLP we created earlier 5. On the bottom left put a check box next to Use Replication Director



12 of 14

6. Click on Options and change the Maximum Snapshots to 5 7. Now click on the Schedules tab 8. Click New 9. Under Name type Full 10. Click OK 11. Now move to the last tab titled VMware 12. Change the Primary VM Identifier to VM Display Name using the dropdown box

a. Don’t change anything else on this screen 13. Now, click the Clients tab

a. This is the tab where the mechanics of the VMware backup Policy are created. You will need to consult the NetBackup Manual to understand all the options but this screen is a very powerful way to backup VM’s beyond what we can show you in this small Lab environment

14. Under Field, select Displayname a. Note all the other option

15. Under Operator, choose AnyOf 16. Click on the Folder Icon at the end of the Query Builder row 17. You should see 7 VM’s including NetApp_VM001 and NetApp_VM002 18. Place a check next to these two NetApp machines and click OK 19. Click on the blue + next to the folder icon and click OK

a. This will create a Query for you 20. Now click on the Test Query button on the bottom left

a. Once the Test finishes you will see the two NetApp VM’s “INCLUDED” in our query 21. Click Close 22. Click on the tab Backup Selections – you will notice that this has been filled in for you based on

the Query we just completed 23. Click OK

The Policy check will run again. Now let’s start a manual backup of these systems using the same steps as before for a manual backup

1) Select the VM_RD_Snap Policy 2) Right click and select Manual Backup 3) Choose the Full schedule 4) Click OK

Now, open the Activity Monitor to watch the progression of the Snapshots and the Replication. You will see that the Snapshots are very fast, the replication is a bit slower, and the backup from snapshot takes the longest amount of time. In a Production environment this would be similar however after the storage is seeded, the replication step would only send changed data which would great speed up this process.

While we wait for the processes to finish, let’s take a look at restore options.



13 of 14

Lab Exercise 8: Restoring Files – Basic steps

Now that we have data backed up, let’s do a quick restore just to show the process 5 minutes

At this point we have three copies of our data. But what advantages does this provide us?

With NetBackup, we can easily select and restore from any one of these copies. NetBackup knows about every copy and can process restores from any copy.

Each copy of this data can have an independent retention period that is completely controlled by NetBackup. For example, when a copy of data on a NetApp snapshot expires, NetBackup will automatically delete that snapshot and remove the entry for that data from within the NetBackup catalog. It will no longer show up as a possible restore option and the space used by that snapshot is available for subsequent snapshots.

When a restore is required, the restore copy can be selected based on its ability to provide the fastest possible restore. For example, it would likely be much faster to restore files from a NetApp snapshot than restore from tape. Any copy of protected data can easily be selected for purposes of restore

We don’t really have time to do an actual restore however at the end of the lab you are welcome to mount \\ONTAP1\vol_OT1_PRI on the Master, delete a few files, then use one of the GUI’s to restore the data. There are two ways to do restores depending on what your needs are. First, let’s look at the “old” way – the NBU BAR GUI.

1) Open the NetBackup console 2) Click on File in the top left 3) Select “Backup, Archive and Restore” from the menu 4) Under “Select for Restore” use the drop down and choose “Restore from Normal Backup”

This will show the basic snapshot we just completed (not the VM snapshots). You can click on the interface to browse the files we backed up from the snapshot. Browsing for files in a small environment is fine, but what if you had millions of files in thousands of subdirectories? For that, we need to search for a file. That requires using Operational Restore which is part of the free version of OpsCenter. Let’s check out OpsCenter Operational Restore. Do this by following the steps below.

1) Open OpsCenter by clicking on the WebUI Login icon on the desktop a. You may get the “Untrusted” page. If so, use I Understand the Risks and Confirm the

Security Exception 2) Log in using “admin” and “password” 3) Click on the Manage tab then Restore below it 4) Click on Restore Files and Directories 5) Click on the Browse and select clients hyperlink on the right side



14 of 14

6) Because our Master and Client are the same system this is a bit confusing, but click on the + next to the NBU1 master, then choose nbu1 as the client and put a check next to it

7) Click OK 8) In the File or Directory Name box, type control*.ctl 9) Click Search

a. You should see one instance of the file in your results 10) Click on the Backup History Selection hyperlink under Backup History

a. You will see the options for restore under the “Copies of Selected Backup” area. In this case we have three copies of the file – two from the snapshot/replication and one from the copy to tape

11) The top one should be selected, leave the defaults, and click on Add to Restore Cart and Close

12) Click on Restore Cart 13) Click on Restore Now (you may need to scroll down on the window) 14) Leave the selections at the defaults and click on Next 15) Verify the file you want is there (it is the only file) then Select the file and click Restore then

OK to close the pop up window 16) Go to the Activity Monitor or watch the OpsCenter Jobs interface for the Restore to show up

and notice when the restore is done

As mentioned, the main differentiator of this solution is the ability to use this “search” feature to find files vs. having to browse for them. This is huge in the snapshot world.

Final Thoughts - So now you should be back at the Activity Monitor and all the process should have completed. We have used Replication Director to protect standard files that were CIFS mounted to a Client by creating a snapshot, replicating that snapshot and then creating a copy to “tape”. We have also created snapshots of two VM’s that were mounted on NetApp NFS storage on an ESX server. We could have done a replication and copy to tape of these systems as well but we don’t have time or space on the VM’s to do it. Replication Director can solve a lot of problems in shops that have NetApp or other supported storage and want to be able to manage the snap/replication/copy to tape process from a single pane of glass. If you have further questions about the Replication Director feature, please reach out to your Symantec Sales team.

netbackup 7.6 replication director a hands on...

Documents