Forum Discussion

nbustarter380's avatar
nbustarter380
Level 6
11 years ago
Solved

extending retention period for backups using the console Gui

Hi,

Question - If we wanted to extend the retention period of backups/images using the GUI is it just a matter of going into the policy and just choosing say the selection let's just say 9 months and clicking ok?

Just had to ask because everything I have read tells instructs how to do this comman line.

 

Thanks in advance!

 

 

7.6
Backup and Recovery
NetBackup
Tip-How to
Windows Server (2003-2008)
  • Nicolai's avatar
    Nicolai
    11 years ago

    http://www.symantec.com/docs/HOWTO43656

    There are some examples on the usage of bpexpdate in the end of the technote.

  • Marianne's avatar
    Marianne
    11 years ago

    You need to specify the option along with a value.

    Have another look at bpexdate options: 

    bpexpdate -recalculate [-backupid backup_id] [-copy number] [-d date | 0 | infinity] [-client name] [-policy name] [-ret retention_level] [-schedtype] [-M master_server,...]

    So, let us try to apply it to your environment (Full schedules):

     bpexpdate  -recalculate -policy Oramw80k-y.mges.mycompany.com -sched 0 -ret 4

    You can find backup id's with bpimagelist command.

  • Marianne's avatar
    Marianne
    11 years ago

    You need to issue the commands on the Master server where the image catalog is kept. Or else on a media server with the additional -M master_server option.
    The admincmd folder only exists on NBU master and media servers, not on NBU clients.

    If you also want to extend images for incremental schedules, you can run the command again for that schedule type. Just double-check Incremental schedule type - differential or cummulative.

  • RonCaplinger's avatar
    RonCaplinger
    11 years ago

    You have two things you have to consider for your request: backup images that were already created before now, and backup images that will be done in the future.

    bpexpdate only changes the expiration date of BACKUP IMAGES that have already been created in the past.  It will NOT change the backup policy.  Once a backup image is created, its expiration date is set using the information contained in the policy, but further changes to the policy do NOT affect prior images.

    bppllist is not the command you want to use to check the exipration date of prior backup images.  It only lists how the policy is set for FUTURE backups, not for previous backup images.  If you want to change the policy for future backups, go into the GUI to make changes to the policy.

    If you want to see the exipration date of previous backup images, try bpimagelist instead of bppllist.

    Changing the expiration date of backup images does NOT change the policy used to back them up.

  • Will_Restore's avatar
    Will_Restore
    Level 6
    11 years ago

    Changing the retention in the GUI will affect future backups.  To change existing images you have to use CLI.

     

  • nbustarter380's avatar
    nbustarter380
    Level 6
    11 years ago

    Hi Will,

    Thanks for your quick response, ok I have to check the commands I found.

     

  • Nicolai's avatar
    Nicolai
    Moderator
    11 years ago

    http://www.symantec.com/docs/HOWTO43656

    There are some examples on the usage of bpexpdate in the end of the technote.

  • nbustarter380's avatar
    nbustarter380
    Level 6
    11 years ago

    Thanks Nicolai for your response,

    I took a look at the technote,

     

    Can I extend the backup of a specific policy for 2 more months?  For both the incremental and full backups? for example

     bpexpdate  -recalculate  -0 -1  -Oramw80k-y.mges.mycompany.com –ret 4

     Oramw80k-y.mges.mycompany.com = policy name

     

    -0   =full backup policy

    -1   = differential backups

    -ret 4 = retention level

     

    This is my first time using this command and I want to make sure its correct.  I haven’t found an example of the command being used on a specific policy however from what I read it can be done.

    I do see an example of using a backup ID however I don’t know how to find the backup ID for this policy

     

    Fyi = the policy is currently deactivated

  • Marianne's avatar
    Marianne
    Level 6
    11 years ago

    You need to specify the option along with a value.

    Have another look at bpexdate options: 

    bpexpdate -recalculate [-backupid backup_id] [-copy number] [-d date | 0 | infinity] [-client name] [-policy name] [-ret retention_level] [-schedtype] [-M master_server,...]

    So, let us try to apply it to your environment (Full schedules):

     bpexpdate  -recalculate -policy Oramw80k-y.mges.mycompany.com -sched 0 -ret 4

    You can find backup id's with bpimagelist command.

  • nbustarter380's avatar
    nbustarter380
    Level 6
    11 years ago

    Hi Marianne thanks for your response,

    So for my situation the command would be for Full backups to be kept for 2 months

    bpexpdate -recalculate -policy Oramw80k-y.mges.mycompany.com -sched 0 -ret 4

    I would also have to re-enter that command for the incrementals to be kept correct?

    bpexpdate -recalculate -policy Oramw80k-y.mges.mycompany.com -sched 1 -ret 4

    and just to verify these commands are done on the Master server correct only? I don't see in anywhere in the technote i can be done on the client server itself.

     

     

     

     

  • Marianne's avatar
    Marianne
    Level 6
    11 years ago

    You need to issue the commands on the Master server where the image catalog is kept. Or else on a media server with the additional -M master_server option.
    The admincmd folder only exists on NBU master and media servers, not on NBU clients.

    If you also want to extend images for incremental schedules, you can run the command again for that schedule type. Just double-check Incremental schedule type - differential or cummulative.

  • nbustarter380's avatar
    nbustarter380
    Level 6
    11 years ago

    Great, Thanks Marianne,

    I issued the commands for the full and incremental backups on the master server to be retained for 6 months and they seemed to have worked  (the policy is deactived that should not matter correct?)

    here are the results

     [root@nbuserver3 admincmd]# bpexpdate -recalculate -policy Oramw80k-y.mges.mycompany.com-sched 1 -ret 6

    Are you SURE you want to recalculate expiration dates on all images

    that meet the following criteria:

      policy           Oramw80k-y.mges.mycompany.com

      scheduletype     1

      retention will be changed to 6(6 months)

    Continue?(y/n)y

    [root@nbuserver3 admincmd]#

     

     [root@nbuserver3 admincmd]# bpexpdate -recalculate -policy Oramw80k-y.mges.mycompany.com-sched 0 -ret 6

    Are you SURE you want to recalculate expiration dates on all images

    that meet the following criteria:

      policy           Oramw80k-y.mges.mycompany.com

      scheduletype     0

      retention will be changed to 6(6 months)

    Continue?(y/n)y

    [root@nbuserver3 admincmd]#

    Also, is there a way to verify thru the admin GUI that the backups will be retained for 6 months other then what I see  when I enter the command? or do I have to enter in a command such as  >>> bppllist <policyname> -U

    Thanks again for your help!

     

     

  • nbustarter380's avatar
    nbustarter380
    Level 6
    11 years ago

    update - I used the bppllist command below and the policy still shows the following

    Retention Level:     11 (56 days)

    root@nbuserver3 admincmd]# bppllist -byclient Oramw80k-y.mges.mycompany.com -U

    Policy Name:       Oramw80k-y.mges.mycompany.com

      Policy Type:         MS-Windows

      Active:              no

      Effective date:      06/05/2013 23:59:59

      Backup network drvs: no

      Collect TIR info:    no

      Mult. Data Streams:  yes

      Client Encrypt:      no

      Checkpoint:          no

      Policy Priority:     0

      Max Jobs/Policy:     6

      Disaster Recovery:   0

      Collect BMR info:    no

      Residence:           nbuserver3-hcart3-robot-tld-1

      Volume Pool:         NetBackup

      Server Group:        *ANY*

      Keyword:             deactivated 8/25/14 (per email)  server down

      Data Classification:       -

      Residence is Storage Lifecycle Policy:    no

      Application Discovery:      no

      Discovery Lifetime:      0 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:  no

      Optimized Backup:  no

      HW/OS/Client:  Windows-x64   Windows2003   Oramw80k-y.mges.mycompany.com

     

      Include:  ALL_LOCAL_DRIVES

     

      Schedule:              full

        Type:                Full Backup

        Calendar sched: Enabled

         Included Dates-----------

          SPECIFIC DATE 0 - 06/06/2013

          SPECIFIC DATE 1 - 08/29/2013

          SPECIFIC DATE 2 - 11/21/2013

          SPECIFIC DATE 3 - 02/13/2014

          SPECIFIC DATE 4 - 05/08/2014

          SPECIFIC DATE 5 - 07/31/2014

          SPECIFIC DATE 6 - 10/23/2014

          SPECIFIC DATE 7 - 01/15/2015

          SPECIFIC DATE 8 - 04/09/2015

          SPECIFIC DATE 9 - 07/02/2015

             No days of week entered

         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:     11 (56 days)

        Number Copies:       1

        Fail on Error:       0

        Residence:           (specific storage unit not required)

        Volume Pool:         (same as policy volume pool)

        Server Group:        (same as specified for policy)

        Residence is Storage Lifecycle Policy:         0

        Schedule indexing:   0

        Daily Windows:

              Sunday     00:00:00  -->  Sunday     06:00:00

              Monday     00:00:00  -->  Monday     06:00:00

              Tuesday    00:00:00  -->  Tuesday    06:00:00

              Wednesday  00:00:00  -->  Wednesday  06:00:00

              Thursday   00:00:00  -->  Thursday   06:00:00

              Friday     00:00:00  -->  Friday     06:00:00

              Saturday   00:00:00  -->  Saturday   06:00:00

     

      Schedule:              incremental

        Type:                Differential Incremental Backup

        Frequency:           every 1 day

         Excluded Dates----------

          EXCLUDE DATE 0 - 06/06/2013

          EXCLUDE DATE 1 - 08/29/2013

          EXCLUDE DATE 2 - 11/21/2013

          EXCLUDE DATE 3 - 02/13/2014

          EXCLUDE DATE 4 - 05/08/2014

          EXCLUDE DATE 5 - 07/31/2014

          EXCLUDE DATE 6 - 10/23/2014

          EXCLUDE DATE 7 - 01/15/2015

          EXCLUDE DATE 8 - 04/09/2015

          EXCLUDE DATE 9 - 07/02/2015

            No exclude days of week entered

        PFI Recovery:        0

        Maximum MPX:         1

        Retention Level:     11 (56 days)

        Number Copies:       1

        Fail on Error:       0

        Residence:           (specific storage unit not required)

        Volume Pool:         (same as policy volume pool)

        Server Group:        (same as specified for policy)

        Residence is Storage Lifecycle Policy:         0

        Schedule indexing:   0

        Daily Windows:

              Sunday     00:00:00  -->  Sunday     06:00:00

              Monday     00:00:00  -->  Monday     06:00:00

              Tuesday    00:00:00  -->  Tuesday    06:00:00

              Wednesday  00:00:00  -->  Wednesday  06:00:00

              Thursday   00:00:00  -->  Thursday   06:00:00

              Friday     00:00:00  -->  Friday     06:00:00

              Saturday   00:00:00  -->  Saturday   06:00:00

     

    [

  • RonCaplinger's avatar
    RonCaplinger
    Level 6
    11 years ago

    You have two things you have to consider for your request: backup images that were already created before now, and backup images that will be done in the future.

    bpexpdate only changes the expiration date of BACKUP IMAGES that have already been created in the past.  It will NOT change the backup policy.  Once a backup image is created, its expiration date is set using the information contained in the policy, but further changes to the policy do NOT affect prior images.

    bppllist is not the command you want to use to check the exipration date of prior backup images.  It only lists how the policy is set for FUTURE backups, not for previous backup images.  If you want to change the policy for future backups, go into the GUI to make changes to the policy.

    If you want to see the exipration date of previous backup images, try bpimagelist instead of bppllist.

    Changing the expiration date of backup images does NOT change the policy used to back them up.