Skip to main content
commvault.com commvault.com

Hello,

 

After each linux update i am seeing this msg belove, what is this exacly and can i store it on /opt/hds location instead at etckeeper??

 

39 files changed, 130 insertions(+), 23 deletions(-)
 delete mode 100644 CommVaultRegistryBackups/Instance001/20250121082400.gz
 delete mode 100644 CommVaultRegistryBackups/Instance001/20250128033422.gz
 delete mode 100644 CommVaultRegistryBackups/Instance001/20250128042923.gz
 delete mode 100644 CommVaultRegistryBackups/Instance001/20250128052422.gz
 delete mode 100644 CommVaultRegistryBackups/Instance001/20250128061923.gz
 delete mode 100644 CommVaultRegistryBackups/Instance001/20250128071422.gz
 delete mode 100644 CommVaultRegistryBackups/Instance001/20250128085924.gz
 delete mode 100644 CommVaultRegistryBackups/Instance001/20250128095423.gz
 delete mode 100644 CommVaultRegistryBackups/Instance001/20250129025925.gz
 delete mode 100644 CommVaultRegistryBackups/Instance001/20250129030925.gz
 delete mode 100644 CommVaultRegistryBackups/Instance001/20250129031425.gz
 delete mode 100644 CommVaultRegistryBackups/Instance001/20250129031924.gz
 delete mode 100644 CommVaultRegistryBackups/Instance001/20250129032425.gz
 delete mode 100644 CommVaultRegistryBackups/Instance001/20250129032925.gz
 delete mode 100644 CommVaultRegistryBackups/Instance001/20250129033425.gz
 rename CommVaultRegistryBackups/Instance001/{20250129023424.gz => 20250129035925.gz} (100%)
 rename CommVaultRegistryBackups/Instance001/{20250129023925.gz => 20250129045424.gz} (100%)
 rename CommVaultRegistryBackups/Instance001/{20250129024425.gz => 20250129054424.gz} (100%)
 rename CommVaultRegistryBackups/Instance001/{20250129024924.gz => 20250129063925.gz} (100%)
 rename CommVaultRegistryBackups/Instance001/{20250129025425.gz => 20250129073424.gz} (100%)
 create mode 100644 CommVaultRegistryBackups/Instance001/20250129082925.gz
 create mode 100644 CommVaultRegistryBackups/Instance001/20250129092424.gz
 create mode 100644 CommVaultRegistryBackups/Instance001/20250129095425.gz
 create mode 100644 CommVaultRegistryBackups/Instance001/20250129095924.gz
 create mode 100644 CommVaultRegistryBackups/Instance001/20250129100425.gz
 create mode 100644 CommVaultRegistryBackups/Instance001/20250129100925.gz
 create mode 100644 CommVaultRegistryBackups/Instance001/20250129101424.gz
 create mode 100644 CommVaultRegistryBackups/Instance001/20250129101925.gz
 create mode 100644 CommVaultRegistryBackups/Instance001/20250129102425.gz
 create mode 100644 CommVaultRegistryBackups/Instance001/20250129102924.gz
 create mode 100644 CommVaultRegistryBackups/Instance001/20250129103425.gz
 create mode 100644 CommVaultRegistryBackups/Instance001/20250129103925.gz
 create mode 100644 CommVaultRegistryBackups/Instance001/20250129104424.gz
 create mode 100644 CommVaultRegistryBackups/Instance001/20250129104925.gz
 create mode 100644 CommVaultRegistryBackups/Instance001/20250129105425.gz
 create mode 100644 scoutfs/archset-d.yaml-from-cron

Hi ​@Egor Skepko 

After which version to which Linux update, this issue is observed and what is the CV version on affected clients?

Hi ​@Egor Skepko ,

From the above logs. it looks like the update is currently processing a backup of the registry and will clean up the backup once the installation is complete.

​@Pradeep ,

 

Can we move it to the installation location instead keeping at etckeeper location? 

 

​@CV_GK  We are running CV on 11.36.55 and mostly on solr i am seeing it 

​@Egor Skepko ,

Etckeeper will help track changes to configuration files, Hence moving them outside is not recommended for now.

​@Pradeep Why not recommended?? 

Reply


Terms & ConditionsCookie settings