client side dedup issue

Have you tried enabling 'Use Accelerator' on the backup policy?

FYI - after enabling accelerator, the benefit of accelerator will only be seen from the second backup onwards.

My understanding was that Appliance WAN optimization is purely related to MSDP to MSDP Opt-Dup duplication/replication (i.e. NetBackup AIR).

Hi Ram,

Yep, "enable file recovery" is enabled.

Unfortunately it seems I don't have capacity based licence. I've just reviewed them and this is that I've got. Cheking the appliance webpage administrator it seems not be available :-(

Many thanks for your help. I'm going to take a look into blueprints ;-)

BTW, taking advantage of this (and I promise you I read all the documentation I found :-) ) the other problem I have with this policy is Wan Optimization. Although I've got set it up, all the traffic is sent as "Non Optimized"

omgesnetbu.WANOptimization> Status
Network Optimization = ENABLED
TCP connections not optimized (or not appropriate for optimization) = 0
TCP connections optimized = 3

Attached you can see a screen shot of traffic when only this policy is working.

Even I created a Resilent Network between Master server and fileserver with the same result.

Do I have to do anything else?

Good point Ram - @Angel, you may be able to reduce the volume of data picked-up by the VM Backup Host BHserver during any full or cumulative or differential VM style backup... by selecting 'Use Accelerator' on the VM based backup policy.  This may be enough to reduce your WAN traffic without having to look at the options that I've previously covered - but should also vastly reduce the backup duration (following the first initial full backup using accelerator) - depending of course upon the rate of data change within the virtualised file server.

Angel Fontana,

did you enable this option in vmware policy type, Enable file recovery from VM backup.

if yes.. i am only seeing enabling with accelerator feature is the best solution and if you have capacity based licence it does not cost you.

unless you want to go with BMR as suggested by SDO, no more Vmware policy type backups.. its going to be Ms- windows policy type with BMR enabled.

I think several of the Blueprints for NetBackup may help you better understand your options:

https://www-secure.symantec.com/connect/forums/list-netbackup-blueprints

.

Re your questions:

1) If you use plain client backups, then a "NetBackup VM Backup Host" is not involved in backups or restores. I.e. the backup is neither SAN nor NBD based, it will be plain client based.

2) I would expect a plain client backup to be slower because the NetBackup Client software inside the VM is having to walk the file systems.  Whereas your current backup is probably NBD transport based (i.e. the ESX server is reading the local LUNs (data stores)) directly at the block level and so should be quicker.

3) To perform a 'create a VM from a plain backup' requires BMR.  You shoudl easily be able to configure BMR on your master server NetBackup appliance.  You will have very few BMR backups, and so the BMR database side of things will not be very big at all.  Remember to enable BMR and TIR on the backup policy which will backup the file server VM.

HTH.

P.S:  Please do keep coming back with more questions.  We'll try to help :)

Sorry, I think I've got a mess and a lack of knowledge.

So, if my fileserver (which is a vmachine in a stand alone ESX) has installed NB client I don't need BHserver (vmachine in the same ESX), so do I have to select as VMware backup host "Backup Media Server" which is in the main site?

Doing this the copy takes more time (from 80 Mb/s to 50Mb/s) misteriously. I was looking into it with a Symantec support and can't explain me why. But this is other matter.

Coming back to dedup, B site is a small one, I just need be able to enable client side dedup. I can restore full machine without BMR, do you think I need one only for one machine? Can't I avoid to install a BMR server to de-dup?

If you use client side de-dupe from a NetBackup Client inside all VMs then you won't have need for the BHserver.  But then any VM recovery will either be a BMR based approach, or better still a recover to VM - which should make things simpler.

third one