BP0045 unclear datastore's usage/provisioning space increase during (and after) migration on the 9th of July

Last post 08-12-2020, 9:15 AM by scottmvy01. 0 replies.
Sort Posts: Previous Next
  • BP0045 unclear datastore's usage/provisioning space increase during (and after) migration on the 9th of July
    Posted: 08-12-2020, 9:15 AM

    It is necessary to check on commvault/3PAR level what was going on with snapshots made on bp0045 VM (datastore: TFLBP_D-3PPB3_8091)

    Space usage/provisioning increased a lot during migration itself (VM was powered off and app couldn’t cause such behaviour)

    Migration start: 08.0720 at 16.44 CEST

    Migration end: 09.07.20 at 1:33:44 a.m. CEST

     

    As seen from screen below snapshot creation has been initiated 2 times by Commvault (it’s technical for commvault).

    TFLBP_D-3PPB2_0055 datastore’s (where bp0045 lived before migration) backup scheduled at midnight and this coincides with 1st snap according to logs.

    Current datastore TFLBP_D-3PPB3_8091 is not in commvault (so, no new snaps were possible after migration completed at 01:33, 09.07.20 (on screen below)

     

    Actually JobID 646842 is our target. It’s necessary why snap of big disk was initiated (taking into account that this disk was excluded from backups).

     

     

     

    Snapshots were removed at 10:00 a.m. CEST on the 13th of July.

    Provisioned space was reduced only after Virtual Machine disks consolidation started at 10:55 a.m. CEST on the 13th of July.

     

     

    Attached screeshots.

     

    I would appreciate any portion of info.

     

     

     

     

     

The content of the forums, threads and posts reflects the thoughts and opinions of each author, and does not represent the thoughts, opinions, plans or strategies of Commvault Systems, Inc. ("Commvault") and Commvault undertakes no obligation to update, correct or modify any statements made in this forum. Any and all third party links, statements, comments, or feedback posted to, or otherwise provided by this forum, thread or post are not affiliated with, nor endorsed by, Commvault.
Commvault, Commvault and logo, the “CV” logo, Commvault Systems, Solving Forward, SIM, Singular Information Management, Simpana, Commvault Galaxy, Unified Data Management, QiNetix, Quick Recovery, QR, CommNet, GridStor, Vault Tracker, InnerVault, QuickSnap, QSnap, Recovery Director, CommServe, CommCell, SnapProtect, ROMS, and CommValue, are trademarks or registered trademarks of Commvault Systems, Inc. All other third party brands, products, service names, trademarks, or registered service marks are the property of and used to identify the products or services of their respective owners. All specifications are subject to change without notice.
Close
Copyright © 2020 Commvault | All Rights Reserved. | Legal | Privacy Policy