Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

5350

June 11th, 2012 01:00

VCB Directive

Hi,

As we are using VADP Backup with SaveSet *FULL*, we would like to use the VCB directive.

Three question about that:

  1. In Networker, in the Directive field of VCB directive, there is nothing. Is that normal? Would the directive working like that? Should we write the file that we want to skip?
  2. What will hapenning with Linux VM?
  3. As we have 300 VM to update, I would like to do it thru the Command Line. I've already found who to do that. I just don't know how to force the yes answer for every client I want to update. Is ther a way?

Thanks a lot for your help.

Regards,

Greg

736 Posts

June 18th, 2012 06:00

Hi Gregoire,

Was the 'VCB Directive' associated with the client when you ran the backup?  I have the impression from your updates that this field was blank, in which case I would expect those files not to be skipped.   You should associate the directive 'VCB Directive' with the client and run the backup again and test with the dummy recover (unless you've already done this).  Running this through scheduled backup or with the savegrp command makes no difference.

-Bobby

173 Posts

June 18th, 2012 07:00

As far as I know windows requires double quotes in path…

<<”/”>>

<<”c:\Windows”

June 18th, 2012 07:00

Hi,

I think you right, except for the <> who's indicate in this case "any disk"

So now my directive looking like that:

<>

skip: pagefile.sys

skip:hiberfil.sys

<<"C:\Windows">>

+skip:system

+skip:System32

Thanks for your help

Greg

June 20th, 2012 02:00

Hello everybody,

I'm continue with test about this directive. An other question now:

  • Could it be that this directive only work with incremental VADP Backup?

        In my understanding, as Networker has to browse the vmdk file to doing the incremental backup, I would say yes.         But I'm not sure of that. Any one to confirm?

@Bobby Cogan:

Could you kindly precise me what the text in bold make in your dummy recover command line?

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

Thanks in advance.

Greg

June 20th, 2012 05:00

Hello Bobby,

Thanks for your answer.

[...and incremental backups of ALLVMFS and *FULL* incremental.]


In this case what would be the difference between *FULL* and ALLVMFS saveset?

Greg

736 Posts

June 20th, 2012 07:00

Hi,

Check out the NetWorker VMWare Integration Guide:

"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."

"

As regards the difference between *FULL* and ALLVMFS - same document, page 52:

"

8. In the Save Set attribute, type the name of the files or directories to be backed up.

Note: Due to limitations with VADP, only one entry is allowed for the Save Set attribute.

a. To specify a file or directory for backup such as C drive, type c:\.

b. To back up a specific directory such as Documents and Settings, type

c:\Documents and Settings.

c. To backup all virtual machine file systems, type ALLVMFS.

d. To backup up the entire VM image, type *FULL*.

"

-Bobby

736 Posts

June 20th, 2012 07:00

Sorry - forgot the link to the NetWorker VMWare Integration Guide.

-Bobby

June 21st, 2012 06:00

Hi Bobby,

Thanks a ot for your help. Now we have to choose a way to backup up our Vm (and it's not the esiaest part)

Thanks again.

Greg

No Events found!

Top