1. Please help support our sponsors by considering their products and services.
    Our sponsors enable us to maintain high-speed Internet connection and fast webservers.
    They support this free information and knowledge exchange forum service at no cost to you.

    Please welcome our latest sponsor Tectrade . We can show our appreciation by learning more about Tectrade Solutions

TDP For VMware changing retension

Discussion in 'TDP/Application Layer Backup' started by balaji419, Dec 6, 2017 at 2:12 AM.

  1. balaji419

    balaji419 Active Newcomer

    Joined:
    Nov 17, 2017
    Messages:
    5
    Likes Received:
    0
    Currently we are using TSM for V.E 6.4 to backup our VM's and we maintain an retention of nolimit,nolimit,28,28. We have configured VM forever incremental backups based on VM folder created from vcenter. Right now we have 6 VM folder and 6 datamovers created for each VM folder and now client wants to reduce the retention's of some VM's to 3 days(nolimit,nolimit,3,3). We suggested to create an vm folder and put all the VM's for which retension needed to be changed in that folder .For that new VMfolder we have created an new datamover in existing Vstorage backup server end. My doubt is Is it possible to attach the existing VM's to an new management class or Do i need to take new full backups of VM using newly created datamover and then only the backups will be assigned to those management class.?. This is the first time I am doing this. I know there is an option include.vm in option file end. But we didnt go fot this options since it wont change the vmctl pool retention's. we want both to be changed and applied with new retention's. Is there any other way to do this. Kindly advice
     
  2.  
  3. RajeshR

    RajeshR ADSM.ORG Member

    Joined:
    May 11, 2016
    Messages:
    55
    Likes Received:
    1
  4. balaji419

    balaji419 Active Newcomer

    Joined:
    Nov 17, 2017
    Messages:
    5
    Likes Received:
    0
    Rajesh thanks for your reply. If I associate the VM backup management class to a new management class with reduced retention using include.vm mgmtclass-name, what will happen to VMCTL data, will it get associated to new VMCTL Management class(which has reduced retention) , because we have two different management class for VM data and VMCTL data because VM backup goes to filepool and VMCTL data goes to DISK pool. Right now we have created an datamover and in the options file of that data mover we have given the new VM management class and VM control pool management class in parameter vmmc and vmctlmc. Even then if we run backups , we could see the VM's not getting associated to the new management class. Kindly suggest me an best possible way of doing this or is there any thing wrong in the procedure that we followed,
     
  5. marclant

    marclant ADSM.ORG Moderator

    Joined:
    Jun 16, 2006
    Messages:
    2,641
    Likes Received:
    372
    Occupation:
    Accelerated Value Specialist for Spectrum Protect
    Location:
    Canada
    source: https://www.ibm.com/support/knowled...ibm.itsm.ve.doc/c_ve_bup_mgmtclscenarios.html
     
  6. balaji419

    balaji419 Active Newcomer

    Joined:
    Nov 17, 2017
    Messages:
    5
    Likes Received:
    0
    Marclant much thanks for your clarifications I am clear about this. Still one thing not clear, if i change the retention from 28 days to 3 days, and then if i trigger backups. Will all versions remaining to last 3 version will be removed immediately. I am asking this because now even after associating the backups to new management class using include.vm command , I could see the old version still existing(old mgmt class-28 days, new mgmt class-3 days). kindly advice
     
  7. RajeshR

    RajeshR ADSM.ORG Member

    Joined:
    May 11, 2016
    Messages:
    55
    Likes Received:
    1
    check this, did you see your new management class listed here?
    select distinct(class_name) from backups where node_name='NODE_NAME'
    Then check this did you see include.vm mentioned vm's mentioned twice in your output
    select distinct node_name,filespace_name,class_name from backups where node_name='NODE_NAME'
     

Share This Page