Answer

CommVaultRegistryBackups

Forum|Forum|6 months ago
June 6, 2025
6 replies
60 views

+15

Egor Skepko
Byte

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

Best answer by Egor Skepko

Hello,

We are created symlink to /opt

stop commvault
mv /etc/CommvaultRegistryBackups /opt/commvault
ln -s /opt/commvault/CommVaultRegistryBackups /etc/
start commvault

+7

CV_GK
Vaulter
Forum|Forum|5 months ago
June 9, 2025

Hi @Egor Skepko

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

Like

P

+12

Pradeep
Vaulter
Forum|Forum|5 months ago
June 9, 2025

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.