Primary Storage

 View Only
  • 1.  Safeguarded copies and child pool sizing

    Posted Sat February 17, 2024 08:34 AM

    We are starting to implement Safeguarded Copy on our customer's SVC, and I am wondering about the right child pool sizing. Assuming I am to protect 10x 5TB volumes, in a 24h/5d retention schedule, which results in a maximum of 5 backups per volume, hence 50 backups total... how would you size the child pool? the aim is to not overshoot it, but also not falling short (with the risks associated to the pool getting filled up). Any advice?



    ------------------------------
    Sergio Pardos
    ------------------------------


  • 2.  RE: Safeguarded copies and child pool sizing

    IBM Champion
    Posted Sat February 17, 2024 08:56 AM

    The space required by the child pool is directly proportional to the daily change rate of the data to be copied. 



    ------------------------------
    Nezih Boyacioglu
    ------------------------------



  • 3.  RE: Safeguarded copies and child pool sizing
    Best Answer

    IBM Champion
    Posted Sat February 17, 2024 09:07 AM
    Edited by Sergio Pardos Sat February 17, 2024 03:36 PM

    If you have 10x5TB volumes and the daily change is around 1%, you will need 500GB of space for each day you keep your copies. If you keep your copies for 5 days, you'll need about 2.5TB of space to store your safeguarded copies. If you have access to the StorM tool (IBM Storage Modeller) there is a calculation for SGC. 



    ------------------------------
    Nezih Boyacioglu
    ------------------------------



  • 4.  RE: Safeguarded copies and child pool sizing

    Posted Sat February 17, 2024 03:42 PM
    Edited by Sergio Pardos Sat February 17, 2024 03:43 PM

    Thanks Nezih. The daily change is low and very steady so far, around 2-3%, depending on the volumes. My fear is if one day the change rate abruptly deviates from the usual rate, or, being most of those volumes vmware datastores, a vmware admin starts moving VMs around datastores without warning us, not giving us time to expand the child pool...

    Regarding the StorM tool, I believe I have access to it, so I'll take a look.



    ------------------------------
    Sergio Pardos
    ------------------------------



  • 5.  RE: Safeguarded copies and child pool sizing

    Posted Sun February 18, 2024 12:51 PM

    Sergio,

    What you should also take into account:
    - Recovery Volume Space. Recovery Volumes are typically the same size & structure as the Source Volumes
    - Loss of Compression from Ransomware: 
      • Most common form of attack is encryption
     • Encryption will neutralize compression and eliminate capacity savings at both source and target volumes
     • Can impact Recovery Volumes. Will impact Source Copies


    ------------------------------
    TMasteen
    ------------------------------