Solved

FIleSystem backup converts files to .gz format

  • 29 November 2021
  • 11 replies
  • 66 views

Userlevel 2
Badge +8

Team,

We had an issue with application today when started file-system backup for directory mounted on host. The underlying storage for that directory is an NFS export .

We started fil-system backup of specific directory from commvault through an on-demand sub client and observed that log files are started converting to .gz format .

Is this something expected behavior when CV backups up lot of small log/bin files with underlying storage as NFS ?  

Should i not take file-system backup for NFS through unix idataagent ? I understand that by-default it is excluded from default subclient.

Let me know if i did something wrong here ? 

 

See these messages in log , what does this mean ?

86695 152a7 11/29 11:12:33 5082624 SdtBase::cfgComp() - gzip comp level set to [-1]

5456  2d48  11/29 03:12:48 ####### [DSBACKUP   ] DsBackup received a Init Signature Message (SIDBStoreId - 22) (compressed - 1 ) (Source Side Deduplication - 0)
5456  2d48  11/29 03:12:48 ####### [DSBACKUP   ] signature initialization success Type: 16 SubType: 319 Status: 0 EventErrorCode: 0
5456  2d48  11/29 03:12:48 ####### [DSBACKUP   ] signature initialization success Has been Sent
5456  1c10  11/29 03:12:48 5082624 10894745-8674684 [DM_BASE    ] Trying to create archive file : afileId = 78168573, ArchiveFileSeqNo = 0,FirstChunkSeqNo= 0, logical_offset = 0, physical_offset = 0 UsedIndexing = 1
5456  a1c   11/29 03:12:48 5082624 10894746-8674685 [DM_BASE    ] Trying to create archive file : afileId = 78168574, ArchiveFileSeqNo = 0,FirstChunkSeqNo= 0, logical_offset = 0, physical_offset = 0 UsedIndexing = 1
5456  1ee0  11/29 03:12:48 5082624 10894744-8674683 [DM_BASE    ] Trying to create archive file : afileId = 78168575, ArchiveFileSeqNo = 0,FirstChunkSeqNo= 0, logical_offset = 0, physical_offset = 0 UsedIndexing = 1

5456  1c10  11/29 03:12:48 ####### [DSBACKUP   ] Archive File creation succeeded Type: 16 SubType: 131 Status: 0 EventErrorCode: 0
5456  1c10  11/29 03:12:48 ####### [DSBACKUP   ] Archive File creation succeeded Has been Sent
5456  a1c   11/29 03:12:48 ####### [DSBACKUP   ] Archive File creation succeeded Type: 16 SubType: 131 Status: 0 EventErrorCode: 0
5456  a1c   11/29 03:12:48 ####### [DSBACKUP   ] Archive File creation succeeded Has been Sent
5456  1ee0  11/29 03:12:48 ####### [DSBACKUP   ] Archive File creation succeeded Type: 16 SubType: 131 Status: 0 EventErrorCode: 0
5456  1ee0  11/29 03:12:48 ####### [DSBACKUP   ] Archive File creation succeeded Has been Sent

icon

Best answer by Gowri Shankar 29 November 2021, 17:41

View original

11 replies

Userlevel 4
Badge +7

Hello @Mohit Chordia 

 

During backups we actually do back up the Commvault log files and troubleshooting files/folders.

While browsing if you go to “advanced options” on the browse and check off the “include troubleshooting folders” you can see what it is backing up.

 

This is likely what you are seeing!

Userlevel 2
Badge +8

@Dan White 

Thanks . But my original question is that does Commvault converts  small log/bin files with underlying storage as NFS to gzip before backing up through unix idataagent ?

We have observed that original files are converted to gzip format and caused application issues.

Userlevel 2
Badge +6

@Mohit Chordia We do not convert files to .tar format during the backup but we use either gtar or lzo compression algorithm if compression is enabled for the backups. The files are written to the storage as chunks 

 

Let us know if this help?

 

 

 

 

Userlevel 2
Badge +8

@Gowri Shankar 

To be clear , if a file name system.log  is present on NFS mount which is presented to host under /apps.

If i take backup of /apps using Unix idataagent , by any chance CV will rename the file /apps/system.log to /apps/system.gzip during the backup process ? 

Userlevel 2
Badge +6

@Mohit Chordia  No we don't rename

We just read the file and write it to the backup media.

Userlevel 2
Badge +8

@Gowri Shankar 

Thank you . So the conversion to .gzip format would have happened due to some other issue. 

Regards,Mohit

Userlevel 2
Badge +6

Yes.

Can we mark this forum as resolved ?

Userlevel 2
Badge +8

@Gowri Shankar Yes

Userlevel 7
Badge +23

@Mohit Chordia can you share the cause?

Userlevel 2
Badge +8

@Mike Struening : I still don't know the root cause , i want to ensure that this behavior is not caused from file-system backups as application team informed that they are observing this issue while backup was in progress . I will update here if get the root cause from application team.

Userlevel 7
Badge +23

Thanks, @Mohit Chordia !!  If/when you do, I’ll mark that reply as the Best Answer!

Reply