VMWare policy - Incremental and Full backups the same size

[Andy_A]

We have recently changed some of our policies from Flashbackup to VMWare and have noticed that the incremental daily backups are the same size as the full backups. As we then duplicate these to tape, we are now having issues where our tape dives are constantly working to finish the duplications. Any ideas on this would be greatly appreciated.

[Marianne]

Did you run a FULL after the change?

Always best to make changes just before a FULL is due.

If this is not the issue, please show us VMware policy config:

bppllist <policy-name> -L

[Andy_A]

Thanks for the swift reply. Yes, fulls were run. Here's the output from the bppllist:

Policy Name:       lon-vmguests-cdms
Options:           0x0
template:          FALSE
audit_reason:         ?
Names:             (none)
Policy Type:       VMware (40)
Active:            yes
Effective date:    03/09/2011 18:00:25
File Restore Raw:  yes
Application Consistent:  yes
Mult. Data Stream: no
Perform Snapshot Backup:   yes
Snapshot Method:           VMware_v2
Snapshot Method Arguments:

Virtual_machine_backup=2,nameuse=0,snapact=2,file_system_optimization=1,trantype=san:hotadd:nbd:nbdssl,exclude_swap=1,disable_quiesce=0,drive_selection=0,skipnodisk=0,post_events=1,multi_org=0,ignore_irvm=1,

rLim=10,rTO=0,rHz=10,serverlist=,enable_vCloud=0
Perform Offhost Backup:    yes
Backup Copy:               0
Use Data Mover:            no
Data Mover Type:           -1
Use Alternate Client:      no
Alternate Client Name:     lon-nbumed-01
Use Virtual Machine:      1
Hyper-V Server Name:     (none)
Enable Instant Recovery:   no
Policy Priority:   0
Max Jobs/Policy:   4
Disaster Recovery: 0
Collect BMR Info:  no
Keyword:           (none specified)
Data Classification:       -
Residence is Storage Lifecycle Policy:    yes
Client Encrypt:    no
Checkpoint:        no
Residence:         SLP_lon-nbumed-01_Daily
Volume Pool:       NetBackup
Server Group:      *ANY*
Granular Restore Info:  no
Exchange Source attributes:              no
Exchange DAG Preferred Server: (none defined)
Application Discovery:      no
Discovery Lifetime:      28800 seconds
ASC Application and attributes: (none defined)
Generation:      85
Ignore Client Direct:  no
Enable Metadata Indexing:  no
Index server name:  NULL
Use Accelerator:  yes
Client/HW/OS/Pri/DMI/CIT:  lon-cdmsap-01.xxx.xxx vmx-08 windows7Server64Guest 0 0 0 0 ?
Client/HW/OS/Pri/DMI/CIT:  lon-cdmswb-02.xxx.xxx vmx-08 windows7Server64Guest 0 0 0 0 ?
Client/HW/OS/Pri/DMI/CIT:  lon-cdmswb-01.xxx.xxx vmx-08 windows7Server64Guest 0 0 0 0 ?
Client/HW/OS/Pri/DMI/CIT:  lon-cdmsap-02.xxx.xxx vmx-08 windows7Server64Guest 0 0 0 0 ?
Client/HW/OS/Pri/DMI/CIT:  lonpp-cdmsap-01.xxx.xxx vmx-08 windows7Server64Guest 0 0 0 0 ?
Client/HW/OS/Pri/DMI/CIT:  lonpp-cdmsap-02.xxx.xxx vmx-08 windows7Server64Guest 0 0 0 0 ?
Client/HW/OS/Pri/DMI/CIT:  lonpp-cdmswb-01.xxx.xxx vmx-08 windows7Server64Guest 0 0 0 0 ?
Client/HW/OS/Pri/DMI/CIT:  lonpp-cdmswb-02.xxx.xxx vmx-08 windows7Server64Guest 0 0 0 0 ?
Include:           ALL_LOCAL_DRIVES
Schedule:              Monthly
  Type:                FULL (0)
  Frequency:           25 day(s) (2160000 seconds)
   Excluded Dates----------
      No specific exclude dates entered
      No exclude days of week entered
  Retention Level:     1 (2 weeks)
  u-wind/o/d:          0 0
  Incr Type:           DELTA (0)
  Alt Read Host:       (none defined)
  Max Frag Size:       0 MB
  PFI Recovery:        0
  Maximum MPX:         1
  Number Copies:       1
  Fail on Error:       0
  Residence:           SLP_lon-nbumed-01_Monthly
  Volume Pool:         (same as policy volume pool)
  Server Group:        (same as specified for policy)
  Residence is Storage Lifecycle Policy:         1
  Schedule indexing:   0
  Daily Windows:
   Day         Open       Close       W-Open     W-Close
   Sunday      000:00:00  000:00:00
   Monday      000:00:00  000:00:00
   Tuesday     000:00:00  000:00:00
   Wednesday   000:00:00  000:00:00
   Thursday    000:00:00  000:00:00
   Friday      023:50:00  078:00:00   143:50:00  198:00:00 030:00:00
   Saturday    000:00:00  000:00:00
Schedule:              Weekly
  Type:                FULL (0)
  Frequency:           4 day(s) (345600 seconds)
   Excluded Dates----------
      No specific exclude dates entered
      No exclude days of week entered
  Retention Level:     1 (2 weeks)
  u-wind/o/d:          0 0
  Incr Type:           DELTA (0)
  Alt Read Host:       (none defined)
  Max Frag Size:       0 MB
  PFI Recovery:        0
  Maximum MPX:         1
  Number Copies:       1
  Fail on Error:       0
  Residence:           SLP_lon-nbumed-01_Weekly
  Volume Pool:         (same as policy volume pool)
  Server Group:        (same as specified for policy)
  Residence is Storage Lifecycle Policy:         1
  Schedule indexing:   0
  Daily Windows:
   Day         Open       Close       W-Open     W-Close
   Sunday      000:00:00  000:00:00
   Monday      000:00:00  000:00:00
   Tuesday     000:00:00  000:00:00
   Wednesday   000:00:00  000:00:00
   Thursday    000:00:00  000:00:00
   Friday      023:50:00  078:00:00   143:50:00  198:00:00 030:00:00
   Saturday    000:00:00  000:00:00
Schedule:              Daily
  Type:                INCR (1)
  Frequency:           0+ day(s) (57600 seconds)
   Excluded Dates----------
      No specific exclude dates entered
      No exclude days of week entered
  Retention Level:     1 (2 weeks)
  u-wind/o/d:          0 0
  Incr Type:           DELTA (0)
  Alt Read Host:       (none defined)
  Max Frag Size:       0 MB
  PFI Recovery:        0
  Maximum MPX:         1
  Number Copies:       1
  Fail on Error:       0
  Residence:           SLP_lon-nbumed-01_Daily
  Volume Pool:         (same as policy volume pool)
  Server Group:        (same as specified for policy)
  Residence is Storage Lifecycle Policy:         1
  Schedule indexing:   0
  Daily Windows:
   Day         Open       Close       W-Open     W-Close
   Sunday      000:00:00  000:00:00
   Monday      023:50:00  030:00:00   047:50:00  054:00:00 
   Tuesday     023:50:00  030:00:00   071:50:00  078:00:00 
   Wednesday   023:50:00  030:00:00   095:50:00  102:00:00 
   Thursday    023:50:00  030:00:00   119:50:00  126:00:00 
   Friday      000:00:00  000:00:00
   Saturday    000:00:00  000:00:00

[Nicolai · Accepted solution]

Duplication to tape from accelerated VMware backup will ALWAYS be full volume.

Its per design to protect integrity.

See; 

https://www-secure.symantec.com/connect/blogs/netbackup-accelerator-vmware-whole-new-world

https://www-secure.symantec.com/connect/forums/duplication-incrementals-msdp-tape

[ontherocks · Accepted solution]

Using Accelarator option Full & Incremental backups of VMs, filesystems will show the same size.

But if you check the number of files backed up in incremental VM Backup will be lesser than the number of files backed up or written in Full Backup.

Accelerator feature is best suitable for the environments where there are no tape outs or duplication is happening.

When duplication to tape scenario comes in it will write complete VM image on tape and tapes consumption becomes too high.

To avoid this you can avoid duplicating incremental backups to Tape. And retain incrementals on disk for some longer duration.

[Andy_A]

May I say, this is the first time I have used this forum and I would like to thank all who responded for both their speed and knowledge. Thanks again.