DB Full Backup showing high size in CommVault from original size

Hello Team,

Have any update about solution?

Hi Zumshedul, 

can you validate the attempts of the job “593323” , you might see a failed attempt of that job that might lead to displaying an incremented size. Double click the job, and navigate to attempts, verify if there is a failed attempt available. 

Hello ​@sbhatia 

There have showing some attempts in this job. 

I have attached some images. Please check this.

Hello ​@sbhatia,

No failed attempts in this job. Please check and give update to us.. What is the next procedure to solve this problem.

​@Zumshedul Abedin Chowdhury It seams you’re using compression with the native backup (3rd screenshot) but with Commvault the compression is disabled. Question is why?

Hello @Ralph

Sorry for late reply.

Software compression is enabled. I have shard one screenshot. Please check.

None of the Date Modified entries seem to match. Can you post screenshots with complete file names? 

Hi ​@Zumshedul Abedin Chowdhury,

and how is the setting on your DB subclient?

And how is the Deduplication setting?

Hi ​@Ralph 

Good day to you.

I am sharing information settings  of DB sub client. Please check below attachments.

Thanks.

Hi ​@Zumshedul Abedin Chowdhury,

ADIC Scalar i2000 is not a Disk Library; it’s tape.

Is the database using encryption on the SQL side? 

​@Zumshedul Abedin Chowdhury 

This is most likely you have TDE enabled on the MSSQL side.

There are various queries you can run if you search the web to confirm its enabled. Here is MS reference.
https://learn.microsoft.com/en-us/sql/relational-databases/security/encryption/transparent-data-encryption?view=sql-server-ver16

If you can confirm that it's not enabled, please open a case with support to review.

Hello ​@Scott Reynolds & ​@SANAdmins 

Good day to you.

There were no encryption algorithm enabled from SQL end.

Thanks.

If your SQL Server .BAK file was previously compressed using SQL Server’s backup compression feature (WITH COMPRESSION), it may actually increase in size when written to tape. This is because compressed data doesn’t typically compress well again, and tape systems often have built-in hardware compression that could make the file larger rather than smaller due to compression inefficiencies.   Does the T-SQL statement contain the WITH COMPRESSION option when backing up to a BAK file?  Now you have me curious.  

Hello ​@SANAdmins 

I understood this.

But 15-03-2025 date it happened and showing larger size. Before and after 15-03-2025 date it is not being happened. I have uploaded some pictures. Please check and give me solution.

Every job history showing attempts option no failed. All are showing like as previous.

​@Zumshedul Abedin Chowdhury 
You might want to open a case with support so everything can be reviewed in depth.