UNSOLVED

dd1980

updated

18 years ago

D

dd1980

46 Posts

0

1008

December 22nd, 2008 03:00

Incremental retention time

Hi,

I have a customer complaining that backup retention periods for one particular client are not behaving as they should. He says that AFT backups to disk have a full backup retention policy of three months, and an incremental policy of one month. However when he checks the volume the incremental backups are being kept longer than one month.

I thought that this would be correct and that backups on one volume would be kept for the longest retention period applied to that volume, however he says that this isn't the case for all their other backups, and that because it's AFT to disk the 3 month full, 1 month incremental combination should work together, as it does for all other clients.

Any help in this matter would be much appreciated.
  • ble1

    6 Operator

    •

    14354 Posts

    •

    56186 Points

    495

    0

    Posted December 22nd, 2008 06:00

    Well, incremental won't expire until youngest incremental has expired that has dependency on it. Now the only questions is would incremental which is the part of full 1 backup cycle expire if full didn't expire. I guess it would as it does for other clients which means that you need to dig into configuration and mminfo to see what is really going on.
  • 2dam

    85 Posts

    495

    0

    Posted December 22nd, 2008 07:00

    Are the full backup actually completing successfully?

    If not your INC will not expire until the youngest has expired. Like the previous post points out you need to see what is happening with mminfo.
  • Hari5

    443 Posts

    495

    0

    Posted December 22nd, 2008 16:00

    On AFT, unlike tape, this should not be a problem. Savesets in the AFT will get removed as and when they expire. However, as mentioned earlier, look at the mminfo outputs on the actual retention dates getting set on the savesets. This would help to narrow down the problem. Since your problem is for only on of the clients, check the configuration for this client to ensure that the retention is correctly configured. I know that's very basic, but you never know where the problem is cropping up from.
  • neilp2

    8 Posts

    495

    0

    Posted December 23rd, 2008 01:00

    Hi,

    I posted this query under a colleagues login but have my own now...

    Many thanks for your response. I have the output of one such mminfo command; mminfo ¿p ¿c clientname

    date browse retent ssid client name
    01/10/2008 05/11/2008 06/11/2008 2145645625 pdgbdc1offbk02.prod.local E:\SAN_Backups\Prod_Bis\DB01\LDrive

    If there's a better mminfo comomand to use please let me know. I'm quite a novice with Networker and need all the help I can get....

    In fact if you want to tell me exactly what to ask the customer and i'll just act as a middle-man that's ok with me! :)
  • ble1

    6 Operator

    •

    14354 Posts

    •

    56186 Points

    495

    0

    Posted December 23rd, 2008 04:00

    I'm quite sure your customer will be happy to see his support is asking questions here ;)

    I'm not clear with this output as it does say nothing really (I actually have no idea if the format is DD/MM/YYYY or MM/DD/YYYY).

    What you need is mminfo output which would show savetime,srowse and retention time along with saveset flags for this client and for the other client. Then you could easily point out where the difference is.
  • Hari5

    443 Posts

    495

    0

    Posted December 23rd, 2008 06:00

    Looks like MM/DD to me ... but then I am just guessing. In any case, in addition to the flags, having the output for at least one incr backup and one full backup would help.
  • neilp2

    8 Posts

    495

    0

    Posted December 24th, 2008 01:00

    Here's the output from a different mminfo command (and the command itself first);

    mminfo -avot -q client=pdgbdc1offbk02.prod.local -r name,savetime,level,ssretent,ssflags(10),volume

    E:\SAN_Backups\Prod_Bis\DB01\LDrive 16/09/2008 incr 22/10/2008 vF DDGBDWBK01.001
    E:\SAN_Backups\Prod_Bis\DB01\LDrive 16/09/2008 incr 22/10/2008 vF DDGBDWBK01.001.RO
    E:\SAN_Backups\Prod_Bis\DB01\IDrive 17/09/2008 incr 23/10/2008 vF DDGBDWBK01.001
    E:\SAN_Backups\Prod_Bis\DB01\IDrive 17/09/2008 incr 23/10/2008 vF DDGBDWBK01.001.RO
    E:\SAN_Backups\Prod_Bis\DB01\LDrive 17/09/2008 incr 23/10/2008 vF DDGBDWBK01.001
    E:\SAN_Backups\Prod_Bis\DB01\LDrive 17/09/2008 incr 23/10/2008 vF DDGBDWBK01.001.RO

    With the headers being; name date lvl retent ssflags volume

    I'm not sure what the vF means...?

    Again, thanks to all for the help so far, much appreciated.
  • ble1

    6 Operator

    •

    14354 Posts

    •

    56186 Points

    495

    0

    Posted January 2nd, 2009 07:00

    So where is full here?
  • neilp2

    8 Posts

    495

    0

    Posted January 5th, 2009 04:00

    To confirm, I believe the question is; why haven't the below incremental backups (and several others from this group) expired?


    name date lvl retent ssflags volume
    E:\SAN_Backups\Prod_Bis\DB01\LDrive 15/09/2008 incr 21/10/2008 vF DDGBDWBK01.001
    E:\SAN_Backups\Prod_Bis\DB01\LDrive 15/09/2008 incr 21/10/2008 vF DDGBDWBK01.001.RO
    E:\SAN_Backups\Prod_Bis\DB01\IDrive 15/09/2008 incr 21/10/2008 vF DDGBDWBK01.001
    E:\SAN_Backups\Prod_Bis\DB01\IDrive 15/09/2008 incr 21/10/2008 vF DDGBDWBK01.001.RO

    ¿When previous and subsequent full backups have apparently completed:

    E:\SAN_Backups\Prod_Bis\DB01\IDrive 13/09/2008 full 14/09/2028 vF CL2039
    E:\SAN_Backups\Prod_Bis\DB01\IDrive 13/09/2008 full 14/09/2028 vF CLS859
    E:\SAN_Backups\Prod_Bis\DB01\IDrive 13/09/2008 full 14/09/2028 vF CLS989
    E:\SAN_Backups\Prod_Bis\DB01\LDrive 13/09/2008 full 14/09/2028 vF CLS989

    E:\SAN_Backups\Prod_Bis\DB01\LDrive 24/11/2008 full 24/11/2028 vF CLS905
    E:\SAN_Backups\Prod_Bis\DB01\LDrive 24/11/2008 full 24/11/2028 vF DDGBDWBK01.001
    E:\SAN_Backups\Prod_Bis\DB01\LDrive 24/11/2008 full 24/11/2028 vF DDGBDWBK01.001.RO
    E:\SAN_Backups\Prod_Bis\DB01\IDrive 24/11/2008 full 24/11/2028 vF CLS905
    E:\SAN_Backups\Prod_Bis\DB01\IDrive 24/11/2008 full 24/11/2028 vF DDGBDWBK01.001
    E:\SAN_Backups\Prod_Bis\DB01\IDrive 24/11/2008 full 24/11/2028 vF DDGBDWBK01.001.RO
  • neilp2

    8 Posts

    135

    0

    Posted January 5th, 2009 05:00

    Resolved!!

    Running nsrim -X cleared the expired incremental save sets.

    Thanks to all for the help, much appreciated.