cancel
Showing results for 
Search instead for 
Did you mean: 

Struggling with server backups

IMassey
Level 2

After being asked to restore a file on one of our remote servers and finding the only version available was five days old, I have been trying to sort out how and when the server gets backed up.

The server is virtual, with C:, D: and H: drives configured as virtual disks and I: and J: drives as Raw Mapped Lun.

Originally, the server was being backed up by both a VMWARE policy and a MS-WINDOWS policy, both of which were set to backup ALL LOCAL DRIVES. However, this seemed to be missing teh I: and J: drives so last week I specifically added those drives to the backup selection of the MS-WINDOWS policy and ran a manual backup.

Both policies are configured to ran Daily Incrementals, Weekly Full and Monthly Full backups, with no excluded days.

Looking at the activity log for the server, though, I can see that a Daily Incremental from the MS-WINDOWS policy ran on 6/2 but hasn't run since, while the Daily Incremental from the VMWARE policy ran on the 6th, 7th and 8th.

I have looked through the configurations and can't see anything wrong - what am I missing?

(Also, if anybody wants to comment on whether or not the above set-up is best practice for backing up this server, please feel free...)

1 ACCEPTED SOLUTION

Accepted Solutions

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Since I and J are not getting backed up by VMware policy, put those 2 drive letters as only entries in Backup Selection of the MS-Windows policy.

Leave client in VMware policy with ALL_LOCAL_DRIVES to backup vmdk files.

The above will ensure the RDM disks are backed up by normal MS-Windows policy and vmdk's backed up by VMware policy without any 'overlaps'/dual backups of the same data.

View solution in original post

7 REPLIES 7

Yasuhisa_Ishika
Level 6
Partner Accredited Certified

Please attatch output of "bppllist your_MS_Windows_policy -L".

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

More readable schedule output will be 
bppllist <policy-name> -U 
Do this for both policies.

You should be backing up ALL_LOCAL_DRIVES with VMware policy OR MS-Windows. Not both.
VMware is not an option as RDM disks are not supported (options for RDM disks are documented in NBU for VMware Guide).

In MS-Windows policy, enable 'Allow multiple data streams' before next Full backup - individual jobs will be created for each drive letter, making troubleshooting a lot easier.
Create bpbkar log folder on client for troubleshooting of missing/skipped data or problematic backups.

IMassey
Level 2

Thanks for the responses so far.

bppllist output is attached below (I tried to attach as files, but the website crashed twice).

I'm getting there - the Daily Incremental is now running (I had no start windows configured) but is taking backups of I: and J: twice. I have removed the I: drive from the Backup Selections tab to see what happens tonight.

However, I have now noticed that the Weekly Full backup in the MSWindows policy is still not backing up the I: and J: drives. Presumably the Monthly will be the same.

MSWINDOWS Policy:

------------------------------------------------------------

Policy Name:       tr_mswindows

  Policy Type:         MS-Windows
  Active:              yes
  Effective date:      06/24/2013 17:48:41
  Backup network drvs: yes
  Collect TIR info:    no
  Mult. Data Streams:  yes
  Client Encrypt:      no
  Checkpoint:          yes
       Interval:       15
  Policy Priority:     5
  Max Jobs/Policy:     Unlimited
  Disaster Recovery:   0
  Collect BMR info:    no
  Residence:           TR_DAILY_SLP
  Volume Pool:         NetBackup
  Server Group:        *ANY*
  Keyword:             (none specified)
  Data Classification:       -
  Residence is Storage Lifecycle Policy:    yes
  Application Discovery:      no
  Discovery Lifetime:      28800 seconds
  ASC Application and attributes: (none defined)

  Granular Restore Info:  no
  Ignore Client Direct:  no
  Enable Metadata Indexing:  no
  Index server name:  NULL
  Use Accelerator:  yes
  Optimized Backup:  no
  HW/OS/Client:  Windows-x64   Windows2008   trnts8001-b.tr.wal-mart.com

  Include:  ALL_LOCAL_DRIVES
            J:\

  Schedule:              Monthly_Full
    Type:                Full Backup
    Frequency:           every 28 days
     Excluded Dates----------
        No specific exclude dates entered
        No exclude days of week entered
    Synthetic:           0
    Checksum Change Detection: 1
    PFI Recovery:        0
    Maximum MPX:         1
    Retention Level:     0 (1 day)
    Number Copies:       1
    Fail on Error:       0
    Residence:           TR_MONTHLY_SLP
    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:
          Sunday     08:00:00  -->  Monday     08:00:00
          Monday     18:00:00  -->  Tuesday    08:00:00
          Tuesday    18:00:00  -->  Wednesday  08:00:00
          Wednesday  18:00:00  -->  Thursday   08:00:00
          Thursday   18:00:00  -->  Friday     08:00:00
          Friday     18:00:00  -->  Saturday   08:00:00
          Saturday   08:00:00  -->  Sunday     08:00:00

  Schedule:              Weekly_Full
    Type:                Full Backup
    Frequency:           every 1 hour
     Excluded Dates----------
        No specific exclude dates entered
        No exclude days of week entered
    Synthetic:           0
    Checksum Change Detection: 0
    PFI Recovery:        0
    Maximum MPX:         1
    Retention Level:     0 (1 day)
    Number Copies:       1
    Fail on Error:       0
    Residence:           TR_WEEKLY_SLP
    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:
          Sunday     18:00:00  -->  Monday     07:00:00
          Monday     18:00:00  -->  Tuesday    07:00:00
          Tuesday    18:00:00  -->  Wednesday  07:00:00
          Wednesday  18:00:00  -->  Thursday   07:00:00
          Thursday   18:00:00  -->  Friday     07:00:00
          Friday     18:00:00  -->  Saturday   18:00:00
          Saturday   18:00:00  -->  Sunday     18:00:00

  Schedule:              Daily_Differential-Inc
    Type:                Differential Incremental Backup
    Frequency:           every 1 day
     Excluded Dates----------
        No specific exclude dates entered
        No exclude days of week entered
    PFI Recovery:        0
    Maximum MPX:         1
    Retention Level:     0 (1 day)
    Number Copies:       1
    Fail on Error:       0
    Residence:           TR_DAILY_SLP
    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:
          Sunday     18:00:00  -->  Monday     05:00:00
          Monday     18:00:00  -->  Tuesday    05:00:00
          Tuesday    18:00:00  -->  Wednesday  05:00:00
          Wednesday  18:00:00  -->  Thursday   05:00:00
          Thursday   18:00:00  -->  Friday     05:00:00
          Friday     18:00:00  -->  Saturday   05:00:00
          Saturday   18:00:00  -->  Sunday     05:00:00

============================================================================

VMWARE Policy

------------------------------------------------------------

Policy Name:       tr_vmware

  Policy Type:         VMware
  Active:              yes
  Effective date:      06/24/2013 19:49:06
  File Restore Raw:    yes
  Application Consistent:    yes
  Mult. Data Streams:  no
  Client Encrypt:      no
  Checkpoint:          no
  Policy Priority:     0
  Max Jobs/Policy:     Unlimited
  Disaster Recovery:   0
  Collect BMR info:    no
  Residence:           (specific storage unit not required)
  Volume Pool:         NetBackup
  Server Group:        *ANY*
  Keyword:             (none specified)
  Data Classification:       -
  Residence is Storage Lifecycle Policy:    no
  Application Discovery:      no
  Discovery Lifetime:      28800000 seconds
  ASC Application and attributes: (none defined)

  Granular Restore Info:  no
  Ignore Client Direct:  no
  Enable Metadata Indexing:  no
  Index server name:  NULL
  Use Accelerator:  yes
  HW/OS/Client:  vmx-07        windows7Serve TRNTS0010.EMEA.Wal-Mart.com
                 vmx-07        windows7Serve TRNTS5001.EMEA.Wal-Mart.com
                 vmx-07        windows7Serve TRNTS1001.EMEA.Wal-Mart.com
                 vmx-07        windows7Serve TRNTS7001.EMEA.Wal-Mart.com
                 vmx-07        windows7Serve TRNTS8001.EMEA.Wal-Mart.com

  Include:  ALL_LOCAL_DRIVES

  Schedule:              Monthly_Full
    Type:                Full Backup
    Frequency:           every 28 days
     Excluded Dates----------
        No specific exclude dates entered
        No exclude days of week entered
    PFI Recovery:        0
    Maximum MPX:         1
    Retention Level:     0 (1 day)
    Number Copies:       1
    Fail on Error:       0
    Residence:           TR_MONTHLY_SLP
    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:
          Sunday     18:00:00  -->  Monday     06:00:00
          Monday     18:00:00  -->  Tuesday    06:00:00
          Tuesday    18:00:00  -->  Wednesday  06:00:00
          Wednesday  18:00:00  -->  Thursday   06:00:00
          Thursday   18:00:00  -->  Friday     06:00:00
          Friday     18:00:00  -->  Saturday   06:00:00
          Saturday   18:00:00  -->  Sunday     06:00:00

  Schedule:              Weekly_Full
    Type:                Full Backup
    Frequency:           every 7 days
     Excluded Dates----------
        No specific exclude dates entered
        No exclude days of week entered
    PFI Recovery:        0
    Maximum MPX:         1
    Retention Level:     0 (1 day)
    Number Copies:       1
    Fail on Error:       0
    Residence:           TR_WEEKLY_SLP
    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:
          Sunday     18:00:00  -->  Monday     06:00:00
          Monday     18:00:00  -->  Tuesday    06:00:00
          Tuesday    18:00:00  -->  Wednesday  06:00:00
          Wednesday  18:00:00  -->  Thursday   06:00:00
          Thursday   18:00:00  -->  Friday     06:00:00
          Friday     18:00:00  -->  Saturday   06:00:00
          Saturday   18:00:00  -->  Sunday     06:00:00

  Schedule:              Daily_Incr
    Type:                Differential Incremental Backup
    Frequency:           every 1 day
     Excluded Dates----------
        No specific exclude dates entered
        No exclude days of week entered
    PFI Recovery:        0
    Maximum MPX:         1
    Retention Level:     0 (1 day)
    Number Copies:       1
    Fail on Error:       0
    Residence:           TR_DAILY_SLP
    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:
          Sunday     18:00:00  -->  Monday     05:00:00
          Monday     18:00:00  -->  Tuesday    05:00:00
          Tuesday    18:00:00  -->  Wednesday  05:00:00
          Wednesday  18:00:00  -->  Thursday   05:00:00
          Thursday   18:00:00  -->  Friday     05:00:00
          Friday     18:00:00  -->  Saturday   05:00:00
          Saturday   18:00:00  -->  Sunday     05:00:00

 

 

Yasuhisa_Ishika
Level 6
Partner Accredited Certified

Weekly_Full schedule of tr_mswindows policy has shorter frequency than Daily_Differential-Inc. Following this configuration, Weekly_Full runs everyday. Can you see such jobs in activity monitor?

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified
Remove this server from VMware policy and get MS-Windows backup to work. Remove J:\ from Backup Selection as ALL_LOCAL_DRIVES already includes all drive letters. Frequency of Weekly Full is every hour? Why is that? You may want to double-check that client-side dedupe is enabled for this client in Host Properties -> Master -> Client Attribute. Add/Select this client name and select dedupe option that will try Client first.

IMassey
Level 2

Hmmm - not sure when/how the monthly schedule was set to run hourly. It wasn't like that a couple of days ago... I have reset that to run weekly.

As to removing the server from the VMWARE policy - we use that policy for Virtual Machine Backups, backing up the vmdk files. Is there a way to leave the server in both policies, using MSWindows for file backups and VMWare for virtual machine backups?

Apologies if this is a basic question - I am relavtively new to NetBackup and have inherited an installation from somebody who didn't know much about it when he set it all up.

Thanks for the help so far.

 

 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Since I and J are not getting backed up by VMware policy, put those 2 drive letters as only entries in Backup Selection of the MS-Windows policy.

Leave client in VMware policy with ALL_LOCAL_DRIVES to backup vmdk files.

The above will ensure the RDM disks are backed up by normal MS-Windows policy and vmdk's backed up by VMware policy without any 'overlaps'/dual backups of the same data.