3. 1. During the standard installation of NetBackup 6.5 you will need to select a Custom install. 2. A valid License Key to install the Windows Media server.

4. 1. Application installs go to the D:\.

5. 1. Provide the name of the hostname of the Media server, and the correct Master server for the environment you are adding this Proxy for. 2. We do not use LiveUpdate at this time.

6. 1. The EMM server is always the same as the Master server in our environments.

8. 1. This phase of the installation is very basic and straightforward.

9. 1. Next you will need to upgrade your Media server to the same level as the Master server. In this case, 6.5.3. 2. There is nothing out of the ordinary about this patching.

10. 1. The process is now complete.

11. 1. There is a critical hot fix for 6.5.3 which address several operational issues with the VCB Proxy which you will need to install. 2. There are 4 files which go on the Media server and 1 file which goes on the Master server. All of which can be found on the Team NAS Share.

12. 1. On the Media server make a directory called backup and copy these 4 files into it, just in case.

13. 1. Stop the Netbackup services on the Media server.

14. 1. Copy these 3 files to the Install Path\bin on the Media server. Yes, you want to overwrite them. 2. Make a backup copy of vfm_master.conf then copy to the Master server.

15. 1. Start the Netbackup services on the Media server.

16. 1. Next you will need to add these two registry keys to the Media server. 2. Under \HKEY_LOCAL_MACHI NE\SOFTWARE\Verita s\NetBackup\Current Version\Config\BACK UP add: SNAP_LOCK_TI MEOUT as a DWORD with an INTEGER value of 1800. UseDisplayNa me as a KEY. Please note case sensitivity.

17. 1. Next you’ll need to add Virtual Center user credentials to the Master server.

18. 1. A change has to be made under the client properties for this Media server in the BAR. Remove the option for Perform incrementals based on archive bit.

19. 1. Now you are ready to add new Policies. There are a few configuration considerations which we will cover. The policy name should contain the VMWare reference name of the DataStore this policy will cover. For example: IN- FISHERS-DEV- VCB- CDDFI010I-01. This identifies it as DataStore 01 on the CDDFI010I unit.

20. 1. Policy Type must be set to FlashBackup- Windows. 2. Limit jobs per policy to 4 to limit the impact to the DataStore. 3. Change it to Perform off-host backup with the User virtual machine proxy option. 4. Select this Media server as the Off-host backup machine. 5. Now you are ready to set the Snapshot Client Options.

21. 1. In the Snapshot Client Options you need to set: Snapshot mount point = E:\vcbsnaps Virtual Machine Backup = 3

22. 1. In the Snapshot Client Options you need to set: Monolithic export = 0

23. 1. Now you can add Schedules which should follow standard configuration. 2. 1 day a week a full backup and 6 days a week a cumulative incremental. 3. The Retention should be set to level 3. 4. Time windows should be open for all days weather you plan to run backups on that day or not.

24. 1. The full should probably to set to the same day of the week as the day you are creating or plan to activate the policy. 2. The cumulative should be set for the other 6 days of the week.

25. 1. Adding clients to the policy is slightly different. You can add the machine name as it is known to the Virtual Center, or you can browse the Virtual Center and select the machines you want to add.

26. 1. Verify your client selection. 2. Default ALL_LOCAL_DRIVES should be appropriate in most all cases.

27. 1. Your policy is now complete. When you click OK you should see the policy validation notification. 2. During the proof of concept I ran into issues of multiple policy validations stepping on each other. This is one of the things resolved in the hotfix files that were applied, however it is probably good procedure to exercise patience and wait a few minutes for this to complete before creating/editing another VCB policy.

28. 1. These Proxy servers have been built with 2 dedicated Backup Network connections. 2. Each of our target Data Domain devices also has 2 dedicated Backup Network connections, so we will create a storage unit for each and then use storage unit groups for the policies. 3. It is also important to note that each policy name ends with an index number. The index number tells us which Data Domain to target based on it’s odd or even status.

29. 1. The policy name index is odd (01) so the storage unit group you assign to it should also be odd (05x).

30. 1. In order to correctly access the CIFS shares on the Data Domain devices, the Netbackup Services should be changed to run under the USAGNT domain account ZDDP01. This could probably be done during the initial 6.5 install, but has not been tested as of this time. 2. This account should also be added to the local administrators group.

31. 1. Your setup should be completed. You can verify that you can correctly access and write to the CIFS share paths you have configured via Windows Explorer prior to starting your backup.