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.
I would appreciate any portion of info.