Delphix Products

We have been adding storage to one of our engines and I have a question on how we can reduce the increase as much as possible.

We have a dsource that is 2.7TB. We have 4 TEST and QA VDBs that are between 200-700gb.
We have another VDB from that dsource that is refreshed daily. 

Since we refresh the VDB daily from the dsource, I would expect the VDB storage to be very low but if you look at the attachment, you can see it was minimal on Dec 12 & 16 but the other days are taking up alot or space.

Hi Joseph,

Initially when you provision or refresh a VDB, it will be sharing most if not all of its blocks with the dSource and so it uses very little capacity.

As users start to make changes in the database (INSERT/UPDATE/DELETE), the VDB will start to grow. Could it be that the users didn't make any changes to the VDB on the 12th or the 16th?

You can get granular, historical capacity for a single database. Maybe you could look at when the VDB started to grow and compare it to SQL audit logs?

• Dxtoolkit can do this: https://github.com/delphix/dxtoolkit/wiki/dx_get_capacity_history

You can also use the Delphix Command Line Interface (CLI):

echo "capacity consumer historical; list container=PineTree display=container,timestamp,breakdown.activeSpace,breakdown.actualSpace,breakdown.unvirtualizedSpace" | ssh admin@my_delphixEngine.com
HIMCO_TGT_DEV_RESEARCH/PineTree                 2017-10-20T16:33:15.532Z  30.73MB                31.89MB                1.79TB
HIMCO_TGT_DEV_RESEARCH/PineTree                 2017-10-20T16:33:15.532Z  30.73MB                31.89MB                1.79TB
HIMCO_TGT_DEV_RESEARCH/PineTree                 2017-10-20T17:33:15.464Z  31.16MB                32.44MB                1.79TB
HIMCO_TGT_DEV_RESEARCH/PineTree                 2017-10-20T18:03:15.431Z  34.22MB                36.87MB                3.59TB
HIMCO_TGT_DEV_RESEARCH/PineTree                 2017-10-20T18:33:15.398Z  2.43MB                 3.36MB                 1.80TB

...etc...

Thanks,

Neal

We have been adding storage to one of our engines and I have a question on how we can reduce the increase as much as possible.

We have a dsource that is 2.7TB. We have 4 TEST and QA VDBs that are between 200-700gb.
We have another VDB from that dsource that is refreshed daily. 

Since we refresh the VDB daily from the dsource, I would expect the VDB storage to be very low but if you look at the attachment, you can see it was minimal on Dec 12 & 16 but the other days are taking up alot or space.

Hi Joseph,

Initially when you provision or refresh a VDB, it will be sharing most if not all of its blocks with the dSource and so it uses very little capacity.

As users start to make changes in the database (INSERT/UPDATE/DELETE), the VDB will start to grow. Could it be that the users didn't make any changes to the VDB on the 12th or the 16th?

You can get granular, historical capacity for a single database. Maybe you could look at when the VDB started to grow and compare it to SQL audit logs?

• Dxtoolkit can do this: https://github.com/delphix/dxtoolkit/wiki/dx_get_capacity_history

You can also use the Delphix Command Line Interface (CLI):

echo "capacity consumer historical; list container=PineTree display=container,timestamp,breakdown.activeSpace,breakdown.actualSpace,breakdown.unvirtualizedSpace" | ssh admin@my_delphixEngine.com
HIMCO_TGT_DEV_RESEARCH/PineTree                 2017-10-20T16:33:15.532Z  30.73MB                31.89MB                1.79TB
HIMCO_TGT_DEV_RESEARCH/PineTree                 2017-10-20T16:33:15.532Z  30.73MB                31.89MB                1.79TB
HIMCO_TGT_DEV_RESEARCH/PineTree                 2017-10-20T17:33:15.464Z  31.16MB                32.44MB                1.79TB
HIMCO_TGT_DEV_RESEARCH/PineTree                 2017-10-20T18:03:15.431Z  34.22MB                36.87MB                3.59TB
HIMCO_TGT_DEV_RESEARCH/PineTree                 2017-10-20T18:33:15.398Z  2.43MB                 3.36MB                 1.80TB

...etc...

Thanks,

Neal

We have been adding storage to one of our engines and I have a question on how we can reduce the increase as much as possible.

We have a dsource that is 2.7TB. We have 4 TEST and QA VDBs that are between 200-700gb.
We have another VDB from that dsource that is refreshed daily. 

Since we refresh the VDB daily from the dsource, I would expect the VDB storage to be very low but if you look at the attachment, you can see it was minimal on Dec 12 & 16 but the other days are taking up alot or space.