Veritas-bu

[Veritas-bu] whats wrong with my calendar basedbackupschedule.bppllist included.

2006-06-13 12:26:25
Subject: [Veritas-bu] whats wrong with my calendar basedbackupschedule.bppllist included.
From: Patrick.Whelan at colt.net (Whelan, Patrick)
Date: Tue, 13 Jun 2006 17:26:25 +0100
You could always set the time on the master server ahead, so midnight
matches your normal start time. :-)

 

Regards,

 

Patrick Whelan 
NetBackup Specialist 
Architect & Engineering 
+44 20 7863 5243 

Of all the things I've lost, I miss my mind the most! - Unknown 

-----Original Message-----
From: veritas-bu-bounces at mailman.eng.auburn.edu
[mailto:veritas-bu-bounces at mailman.eng.auburn.edu] On Behalf Of Bob
Stump
Sent: 13 June 2006 17:21
To: Jonathan - Fort Collins CO Marks; veritas-bu at mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] whats wrong with my calendar
basedbackupschedule.bppllist included.

 

goofy isn't the word I was thinking of....bad prcatice to do backups
from 6PM to 6AM????

 

anyhow. I should have included that I am using NB5.1_MP4

 

 

 



>>> "Marks, Jonathan - Fort Collins, CO" <Jonathan.Marks at ftc.usda.gov>
6/13/2006 12:02 PM >>>

If you are using Netbackup 6.0 you can not have your start window cross
midnight.  I was told that it is bad practice.  I think Netbackup has
gone goofy.

 

-Jonathan Marks (970)295-5362

 

 

________________________________

From: Bob Stump [mailto:stumpb at michigan.gov] 
Sent: Monday, June 12, 2006 4:02 PM
To: veritas-bu at mailman.eng.auburn.edu
Subject: [Veritas-bu] whats wrong with my calendar based backup
schedule.bppllist included.

I have years of experience with frequency based scheduling but I have
always shied away from calendar based. Today I made my first attempt and
I cannot see where I made a mistake. Please review this and help me if
you can. Thanks.

 

 

Here is the problem
The calendar based backup started on the first day that I made this
policy active even though it is not suppose to be active until the last
Monday of the month.

 

Here is the strategy
1. full backup every monday night excluding last monday of the month
with 1 month retention
   allow tuesday full for any failures that may occur on monday
3. last monday of each month run a calendar full backup with 3 month
retention
   retries allowed after runday which would be tuesday night.
2. incremental backup every night except monday nights with 1 month
retention

 

Here is the bppllist:
Policy Name:       groupwise01-09

 

  Policy Type:         Standard
  Active:              yes
  Effective date:      06/12/2006 08:00:00
  Client Compress:     no
  Follow NFS Mounts:   no
  Cross Mount Points:  no
  Collect TIR info:    no
  Block Incremental:   no
  Mult. Data Streams:  yes
  Client Encrypt:      no
  Checkpoint:          no
  Policy Priority:     25
  Max Jobs/Policy:     Unlimited
  Disaster Recovery:   0
  Residence:           dssu_grp
  Volume Pool:         Novell
  Keyword:             (none specified)

 

  HW/OS/Client:  Novell        NetWare       gw01
                 Novell        NetWare       gw02
                 Novell        NetWare       gw03
                 Novell        NetWare       gw04
                 Novell        NetWare       gw05
                 Novell        NetWare       gw06
                 Novell        NetWare       gw07
                 Novell        NetWare       gw08
                 Novell        NetWare       gw09

 

  Include:  /FS

 

  Schedule:          17.30_mon_calendar
    Type:            Full Backup
    Maximum MPX:     10
    Synthetic:       0
    PFI Recovery:    0
    Retention Level: 5 (3 months)
    Number Copies:   1
    Fail on Error:   0
    Residence:       dssu04
    Volume Pool:     (same as policy volume pool)
    Calendar sched: Enabled
      Allowed to retry after run day
      SPECIFIC DATE 0 - 06/26/2006
      SPECIFIC DATE 1 - 07/31/2006
      SPECIFIC DATE 2 - 08/28/2006
      SPECIFIC DATE 3 - 09/25/2006
      SPECIFIC DATE 4 - 10/30/2006
      SPECIFIC DATE 5 - 11/27/2006
      SPECIFIC DATE 6 - 12/25/2006
      Monday, Week 5
    Daily Windows:
          Monday     18:30:00  -->  Tuesday    04:00:00
          Tuesday    17:30:00  -->  Wednesday  04:00:00

 

  Schedule:          17.30_mon_full
    Type:            Full Backup
    Frequency:       every 5 days
    Maximum MPX:     10
    Synthetic:       0
    PFI Recovery:    0
    Retention Level: 3 (1 month)
    Number Copies:   1
    Fail on Error:   0
    Residence:       dssu04
    Volume Pool:     (same as policy volume pool)
      EXCLUDE DATE 0 - 06/26/2006
      EXCLUDE DATE 1 - 07/31/2006
      EXCLUDE DATE 2 - 08/28/2006
      EXCLUDE DATE 3 - 09/25/2006
      EXCLUDE DATE 4 - 10/30/2006
      EXCLUDE DATE 5 - 11/27/2006
      EXCLUDE DATE 6 - 12/25/2006
    Daily Windows:
          Monday     17:20:00  -->  Tuesday    04:00:00
          Tuesday    17:30:00  -->  Wednesday  04:00:00

 

  Schedule:          17.30_mon_inc
    Type:            Differential Incremental Backup
    Frequency:       every 12 hours
    Maximum MPX:     10
    Synthetic:       0
    PFI Recovery:    0
    Retention Level: 3 (1 month)
    Number Copies:   1
    Fail on Error:   0
    Residence:       (specific storage unit not required)
    Volume Pool:     (same as policy volume pool)
    Daily Windows:
          Sunday     17:30:00  -->  Monday     04:00:00
          Tuesday    17:30:00  -->  Wednesday  04:00:00
          Wednesday  17:30:00  -->  Thursday   04:00:00
          Thursday   17:30:00  -->  Friday     04:00:00
          Friday     17:30:00  -->  Saturday   04:00:00
          Saturday   17:30:00  -->  Sunday     04:00:00



*************************************************************************************
The message is intended for the named addressee only and may not be disclosed 
to or used by anyone else, nor may it be copied in any way. 

The contents of this message and its attachments are confidential and may also 
be subject to legal privilege.  If you are not the named addressee and/or have 
received this message in error, please advise us by e-mailing security at 
colt.net and delete the message and any attachments without retaining any 
copies. 

Internet communications are not secure and COLT does not accept responsibility 
for this message, its contents nor responsibility for any viruses. 

No contracts can be created or varied on behalf of COLT Telecommunications, its 
subsidiaries or affiliates ("COLT") and any other party by email Communications 
unless expressly agreed in writing with such other party.  

Please note that incoming emails will be automatically scanned to eliminate 
potential viruses and unsolicited promotional emails. For more information 
refer to www.colt.net or contact us on +44(0)20 7390 3900.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20060613/72d13a71/attachment-0001.html

<Prev in Thread] Current Thread [Next in Thread>
  • [Veritas-bu] whats wrong with my calendar basedbackupschedule.bppllist included., Whelan, Patrick <=