VCB Directive

Hello,

I found some Answer.

1.

Note: The skips in the VCB directive are handled internally. An empty directive

specification when viewing the directive resource in the NetWorker Console or the

nsradmin interface is expected behavior.

2. still

3. I update my ressource with an input file.

show name;save set;directive;client OS type

. type:NSR client;save set:*FULL*;client OS type:Windows NT Server on Intel

update directive:VADP directive Windows

Thaks for your help

Hello,

1) I don't have anything in my vcb directive either. I'm running 7.6.3.4 and am not sure if when you update to at least 7.6.2 it "blanks" out the directive because vadp is used now instead of vcb.  I never used that directive when we used vcb though.

2) Networker tells vcenter to take a snapshot of the linux vm, then your proxy mounts the snapshot and backs it up.  Still won't be able to do a file level restore with linux vm's though.

3)I don't get prompted whenever I update clients in bulk using nsradmin.  I just give the field an "update" command.

If you're updating all clients in your environment you could use something like this (if you were updating something like browse and retention policy) and wanted to run an nsradmin -i FILENAME:

. type: NSR client
show Name:
show retention policy:
print
update browse policy: 2 Weeks
update retention policy: 2 Weeks

If you're updating a group you can do something like this and wanted to run an nsradmin -i FILENAME::

print type: NSR client;name:CLIENTNAME

update comment:COMMENTFIELDTEXT

update Proxy backup host:VADPPROXYHOST

Hope this helps..

Hello,

Thanks for your answer.

Well, I still have my question with this VCB directive.

Cause as we have a lot of Windows VM, I guess with what I 've reading until now, that's exclusion still possible on VADP Backup with Windows VM (cause there it's possible to doing file level recovery).

Am I wrong?

Thanks.

Greg

Hello,

Anybody to help me?

Thanks in advance.

Greg

Hi Gregoire,

The NetWorker-VMWare Integration Guide p. 20 states that the VCB directive is still valid:

Extract:

"

VCB directive

The VCB directive is supported in the following two scenarios:

◆ When the save set is *FULL* and the backup level is either incremental or any non

level-0 backup.

◆ When the save set is ALLVMFS, irrespective of the level of backup.

Note: This directive is only applicable for VMs running the Microsoft Windows operating

system.

For the backup, the directive can be specified in the VM client properties.

The VCB directive skips the following files and folders:

◆ pagefile.sys

◆ hiberfil.sys (Hibernation file)

◆ WINDOWS\system folder

◆ WINDOWS\System32 folder

"

Does this answer your question?  If not, please describe exactly what you need to know.

-Bobby

Hi,

I don't have any direct experience with this directive, but I'd presume that you need to assign this for it to work - if it's blank, then it won't be in operation.  In order to check what files exactly are backed up in your backup, you should run a dummy recover:

recover -s [nw_server_name_here] -n -S [ssid_here] > dummy_recover 2>&1 

the '-n' means that it will not recover any data but will output to the file what would have been recovered by a recover of the entire saveset.  By checking the file dummy_recovery, you can see exactly what is backed up for this saveset and make sure it is what you expect.  Be sure to run this against a full backup, so you are sure that you have everything.

-Bobby

Hello Bobby,

Thanks for your answer. The two last points of my question are:

- In my case, the directive field in VCB directive is empty in Networker. Is that correct, or schould we put anything in?

- Who can I check that this File are really skipped in my backup.

Thanks again.

Greg

Hi,

No it's not has I do a dummy restore based on a saveset ID. So i cannot be from a previous one.

Greg

Hi,

I have tries the dummy recover and I get a C:\pagefile.sys, C:\windows\System32 and system folder in the list. So it seem that my directive is not working...

I 'll try to update the directive this way:

<>

skip: pagefile.sys

skip:hiberfil.sys

< >

+skip:system

+skip:System32

Do you think it could work? And what happen if I launch the backup mnually thru the savegrp command... Will the directive be applied or it is working only with scheduled backup?

Thanks.

Greg

Check backup date if it is not from previous backups…

Ok, some update now:

After editing the VCB directive with this parameter:

<>

skip: pagefile.sys

skip:hiberfil.sys

< >

+skip:system

+skip:System32

I 've start a full backup of one VM who had the VCB directive in this configuration:

savegrp -l full -c [client name] [savegroup name]

Once the backup was finished, I've try a dummy restore.

Still having pagefile.sys, c:\Windows\system32 and system in it...

So....I'm disapointed.

Thanks for your help.

Greg

Yes it was. What I mean is that in the direcive filed of the vcb directive, there was nothing. But in client property, the directive was associated.

Was that a bit clearer?

Greg

Sorry Greg - I don't understand what you mean by 'it was associated but with directive field blank'.  When you look in the client configuration 'General' tab and you look at the drop-down next to the word 'Directive:', does it show the directive in there or not?

-Bobby

Hi Bobby,

Yes it was associated but with directive field blank. I'll try with the savegrp command then and write the result as soon as I get it.

Thanks for your help.

Greg