Avamar: Så här återskapar du certifikat

Сводка: Så här återställer eller återskapar du certifikat på grund av förfallodatum (eller felkonfiguration).

Данная статья применяется к Данная статья не применяется к Эта статья не привязана к какому-либо конкретному продукту. В этой статье указаны не все версии продуктов.
Ознакомьтесь с другими ресурсами

Инструкции

Användningsområden:

  • Återskapa certifikat på begäran.
  • När Avamar-tjänsterna är nere och inte kan startas om på grund av utgångna eller felkonfigurerade certifikat.
Kommentarer:
  • Flera av dessa procedurer kräver att tjänster som körs startas om. Detta kan störa säkerhetskopieringar och replikeringsjobb som körs. Tjänsterna bör inte startas om medan Avamar-underhåll (kontrollpunkt (cp), kontrollpunktsvalidering (hfscheck) eller skräpinsamling körs).
  • Du kan återskapa nyckelarkivet och uppdatera Data Domain-certifikatarkivet automatiskt med verktyget GoAV. Mer information finns i följande artikel: Avamar: Så här använder du Goav-säkerhetsnyckellagret
  • En kontrollpunkt MÅSTE vidtas innan några uppdateringar utförs.

Granska de befintliga förfallodatumen för att avgöra vilka uppdateringar som krävs:

  1. Logga in på Avamar-verktygsnoden som administratör.

  2. Höj till rotprivilegium.

  3. Ange variabeln "storepath":

    För Avamar v19.7 och senare:

    storepath=/home/tomcat/.keystore

    För Avamar v19.4 och tidigare:

    storepath=/home/admin/.keystore

  4. Kör följande kommando för att skriva ut certifikatets förfallodatum:

    storepass=`ask_pass -r keystore_passphrase` && echo "MC Root certificates: " && keytool -list -keystore /usr/local/avamar/lib/avamar_keystore -storepass $storepass -v | egrep "Alias name|Valid from" && echo && echo "MCSDK certificate: " && keytool -list -keystore /usr/local/avamar/lib/rmi_ssl_keystore -storepass $storepass -v | egrep "Alias name|Valid from" && echo && echo "Admin/DTLT certificate: " && keytool -list -alias tomcat -keystore $storepath -storepass $storepass -v | egrep "Alias name|Valid from" && echo && echo "Avi certificate: " && keytool -list -alias tomcat -keystore /usr/local/avamar/lib/avi/avi_keystore -storepass $storepass -v | egrep "Alias name|Valid from" && echo && echo "Apache certificate: " && openssl x509 -in /etc/apache2/ssl.crt/server.crt -noout -dates

    Exempel på utdata (baserat på kommandon som körs den 18 februari 2026):

    MC Root certificates:
Alias name: mcectls
Valid from: Thu Feb 13 20:21:48 PST 2025 until: Tue Feb 12 20:21:48 PST 2030
Alias name: mcrsatls
Valid from: Thu Feb 13 20:21:50 PST 2025 until: Tue Feb 12 20:21:50 PST 2030
Alias name: mcecroot
Valid from: Thu Feb 13 20:21:48 PST 2025 until: Tue Feb 12 20:21:48 PST 2030
Alias name: mcrsaroot
Valid from: Thu Feb 13 20:21:49 PST 2025 until: Tue Feb 12 20:21:49 PST 2030

MCSDK certificate:
Alias name: mcssl
Valid from: Thu Feb 13 20:21:43 PST 2025 until: Sun Feb 11 20:21:43 PST 2035
Alias name: mcjwt
Valid from: Thu Feb 13 20:21:45 PST 2025 until: Sun Feb 11 20:21:45 PST 2035

Admin/DTLT certificate:
Alias name: tomcat
Valid from: Thu Feb 13 20:22:02 PST 2025 until: Sun Feb 11 20:22:02 PST 2035

Avi certificate:
Alias name: tomcat
Valid from: Thu Feb 13 20:22:00 PST 2025 until: Sun Feb 11 20:22:00 PST 2035

Apache certificate:
notBefore=Feb  1 04:49:34 2022 GMT
notAfter=Jan 31 04:49:34 2027 GMT

    (Utdata ovan visar att ingenting har upphört att gälla)

    MC Root certificates:
Alias name: mcectls
Valid from: Thu Feb 13 20:21:48 PST 2025 until: Tue Mar 12 20:21:48 PST 2026
Alias name: mcrsatls
Valid from: Thu Feb 13 20:21:50 PST 2025 until: Tue Mar 12 20:21:50 PST 2026
Alias name: mcecroot
Valid from: Thu Feb 13 20:21:48 PST 2025 until: Tue Mar 12 20:21:48 PST 2026
Alias name: mcrsaroot
Valid from: Thu Feb 13 20:21:49 PST 2025 until: Tue Mar 12 20:21:49 PST 2026

MCSDK certificate:
Alias name: mcssl
Valid from: Thu Feb 13 20:21:43 PST 2025 until: Sun Feb 11 20:21:43 PST 2035
Alias name: mcjwt
Valid from: Thu Feb 13 20:21:45 PST 2025 until: Sun Feb 11 20:21:45 PST 2035

Admin/DTLT certificate:
Alias name: tomcat
Valid from: Thu Feb 13 20:22:02 PST 2025 until: Sun Feb 11 20:22:02 PST 2035

Avi certificate:
Alias name: tomcat
Valid from: Thu Feb 13 20:22:00 PST 2025 until: Sun Feb 11 20:22:00 PST 2035

Apache certificate:
notBefore=Feb  1 04:49:34 2022 GMT
notAfter=Jan 31 04:49:34 2027 GMT

    (Utdata ovan visar att MC-rotcertifikaten upphör att gälla inom en månad)

    MC Root certificates:
Alias name: mcectls
Valid from: Thu Feb 13 20:21:48 PST 2025 until: Tue Feb 12 20:21:48 PST 2026
Alias name: mcrsatls
Valid from: Thu Feb 13 20:21:50 PST 2025 until: Tue Feb 12 20:21:50 PST 2026
Alias name: mcecroot
Valid from: Thu Feb 13 20:21:48 PST 2025 until: Tue Feb 12 20:21:48 PST 2026
Alias name: mcrsaroot
Valid from: Thu Feb 13 20:21:49 PST 2025 until: Tue Feb 12 20:21:49 PST 2026

MCSDK certificate:
Alias name: mcssl
Valid from: Thu Feb 13 20:21:43 PST 2025 until: Sun Feb 11 20:21:43 PST 2035
Alias name: mcjwt
Valid from: Thu Feb 13 20:21:45 PST 2025 until: Sun Feb 11 20:21:45 PST 2035

Admin/DTLT certificate:
Alias name: tomcat
Valid from: Thu Feb 13 20:22:02 PST 2025 until: Sun Feb 11 20:22:02 PST 2035

Avi certificate:
Alias name: tomcat
Valid from: Thu Feb 13 20:22:00 PST 2025 until: Sun Feb 11 20:22:00 PST 2035

Apache certificate:
notBefore=Feb  1 04:49:34 2022 GMT
notAfter=Jan 31 04:49:34 2027 GMT

    (Utdata ovan visar att MC-rotcertifikaten har upphört att gälla)

    MC Root certificates:
Alias name: mcectls
Valid from: Thu Feb 13 20:21:48 PST 2025 until: Tue Feb 12 20:21:48 PST 2030
Alias name: mcrsatls
Valid from: Thu Feb 13 20:21:50 PST 2025 until: Tue Feb 12 20:21:50 PST 2030
Alias name: mcecroot
Valid from: Thu Feb 13 20:21:48 PST 2025 until: Tue Feb 12 20:21:48 PST 2030
Alias name: mcrsaroot
Valid from: Thu Feb 13 20:21:49 PST 2025 until: Tue Feb 12 20:21:49 PST 2030

MCSDK certificate:
Alias name: mcssl
Valid from: Thu Feb 13 20:21:43 PST 2025 until: Sun Feb 11 20:21:43 PST 2035
Alias name: mcjwt
Valid from: Thu Feb 13 20:21:45 PST 2025 until: Sun Feb 11 20:21:45 PST 2035

Admin/DTLT certificate:
Alias name: tomcat
Valid from: Thu Feb 13 20:22:02 PST 2025 until: Sun Feb 11 20:22:02 PST 2035

Avi certificate:
Alias name: tomcat
Valid from: Thu Feb 13 20:22:00 PST 2025 until: Sun Feb 11 20:22:00 PST 2035

Apache certificate:
notBefore=Feb  1 04:49:34 2021 GMT
notAfter=Jan 31 04:49:34 2026 GMT

    (Utdata ovan visar att Apache-certifikatet har upphört att gälla.)

Uppdatera lämpliga certifikat från tillämpligt avsnitt i bilagan nedan:

Utför verifieringar efter ändring:

  1. Kontrollera att alla Avamar-tjänster körs:

    dpnctl status
  2. Utför en testsäkerhetskopiering
  3. Utför en säkerhetskopiering, bläddra efter återställning

Bilaga:

Återskapa endast Apache-certifikaten:

Apache-certifikaten lagras som vanliga PEM-formaterade (Privacy Enhanced Mail) certifikatfiler.

  1. Logga in på Avamar-verktygsnoden som administratör.

  2. Höj till rotprivilegium.

  3. Gör en säkerhetskopia av de befintliga certifikatfilerna:

    cp -p /etc/apache2/ssl.crt/server.crt /etc/apache2/ssl.crt/server.crt.`date +%y%m%d`
cp -p /etc/apache2/ssl.key/server.key /etc/apache2/ssl.key/server.key.`date +%y%m%d`

  4. Kontrollera att säkerhetskopiorna finns:

    ls -al /etc/apache2/ssl.crt/server.crt*
ls -al /etc/apache2/ssl.key/server.key*

  5. Apache-certifikatet kan uppdateras med GoAV (v18.4 och senare) ELLER genom att köra ett Avamar-kommando:
    "GoAV"-kommando (och exempelutdata):
    ./goav security certificate apache regenerate

    ╔════════════════════════════════════════════════════════╗
║ GoAV                                             v2.02 ║
╟────────────────────────────────────────────────────────╢
║ Build : 02 Feb 2026 19:03 UTC                          ║
║ Date  : 18 Feb 2026 04:52 UTC                          ║
║ Avamar: 19.4.100-124                                   ║
╟────────────────────────────────────────────────────────╢
║ Command:./goav security certificate apache regenerate  ║
╟────────────────────────────────────────────────────────╢
║ NOTE: This tool was created and is maintained          ║
║       by the ISG Support Tools team.                   ║
╚════════════════════════════════════════════════════════╝
┃ Select a Key Size in bits:
┃ > 2048
┃   3072
┃   4096

    (Välj önskad nyckelstorlek eller använd standardvärdet 2048)

    Apache x509 Certificate Configuration
-------------------------------------

Apache Private Key
------------------
Location            /etc/apache2/ssl.key/server.key
Modulus MD5sum      0d35d9c14239093d4f5e28bd5f2f98c8
Key Size            2048

Apache Server Cert
------------------
Location            /etc/apache2/ssl.crt/server.crt
Serial              129741042722659803976190762572696306257
Subject             C=US, ST=Texas, L=Round Rock, O=Dell Technologies, CN=server.company.com
Issuer              C=US, ST=Texas, L=Round Rock, O=Dell Technologies, CN=server.company.com
Valid Range         YYYY/MM/DD - valid from: 2026/02/18, valid to: 2028/02/18
Modulus MD5sum      0d35d9c14239093d4f5e28bd5f2f98c8
Key Size            2048
Subject Alt Names   server.company.com

    -- Eller --
    Avamar Kommando (och exempelutmatning):
    gen-ssl-cert --updateapache --noupdateavi --keystorepwd=$(avlockbox.sh -r keystore_passphrase) --verbose

           openssl genrsa -out /tmp/gen-ssl-cert-server.key.9085 3072
Generating RSA private key, 3072 bit long modulus
e is 65537 (0x10001)
        openssl req -new -key /tmp/gen-ssl-cert-server.key.9085 -out /tmp/gen-ssl-cert-server.csr.9085 < /tmp/gen-ssl-cert-answers.9085
You are about to be asked to enter information that will be incorporated
into your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN.
There are quite a few fields but you can leave some blank
For some fields there will be a default value,
If you enter '.', the field will be left blank.
...

           |-30200 /usr/sbin/httpd-prefork -DSYSCONFIG -DSSL -C PidFile /var/run/httpd.pid -C Include /etc/apache2/sysconfig.d//loadmodule.conf -C Include /etc/apache2/sysconfig.d//global.conf -f /etc/apache2/httpd.conf -c Include /etc/apache2/sysconfig.d//include.conf -DSYSTEMD -DFOREGROUND -k start
           `-30206 /usr/sbin/httpd-prefork -DSYSCONFIG -DSSL -C PidFile /var/run/httpd.pid -C Include /etc/apache2/sysconfig.d//loadmodule.conf -C Include /etc/apache2/sysconfig.d//global.conf -f /etc/apache2/httpd.conf -c Include /etc/apache2/sysconfig.d//include.conf -DSYSTEMD -DFOREGROUND -k start

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
        /sbin/service apache2 stop
        /sbin/service apache2 start

Återskapa endast Tomcat-certifikaten:

  • Tomcat-nyckelarkivet lagrar Tomcat-certifikaten.
  • Den återskapar "/home/tomcat/.keystore" eller "/home/admin/.keystore" beroende på Avamar-version.

  1. Logga in på Avamar-verktygsnoden som administratör.

  2. Höj till rotprivilegium.

  3. Gör en säkerhetskopia av den befintliga nyckelbehållaren:

    cp -p /home/tomcat/.keystore /home/tomcat/.keystore.`date +%y%m%d`

    (Ersätt "/home/admin/.keystore" med "/home/tomcat/.keystore" i Avamar 19.4 och tidigare)

  4. Kontrollera att säkerhetskopian finns:

    ls -al /home/tomcat/.keystore*

    (Ersätt "/home/admin/.keystore" med "/home/tomcat/.keystore" i Avamar 19.4 och tidigare)

  5. Nyckelbehållaren kan uppdateras med GoAV OR genom att köra kommandon på Avamar:

    Kommandot "GoAV" (och exempel på utdata):
    ./goav security keystore regenerate

    ╔════════════════════════════════════════════════════════╗
║ GoAV                                             v2.02 ║
╟────────────────────────────────────────────────────────╢
║ Build : 02 Feb 2026 19:03 UTC                          ║
║ Date  : 18 Feb 2026 05:37 UTC                          ║
║ Avamar: 19.4.100-124                                   ║
╟────────────────────────────────────────────────────────╢
║ Command:/home/admin/20260218/goav security keystore    ║
║         regenerate                                     ║
╟────────────────────────────────────────────────────────╢
║ NOTE: This tool was created and is maintained          ║
║       by the ISG Support Tools team.                   ║
╚════════════════════════════════════════════════════════╝

┃ Select Keystore to Regenerate
┃   RMI_SSL_KEYSTORE
┃   AVAMAR_KEYSTORE
┃   AVI_KEYSTORE
┃ > TOMCAT_KEYSTORE

    (Välj "TOMCAT_KEYSTORE")

    ⣯  Fixing any Tomcat issues
...
══════════════════ Fixing Keystore Issues ══════════════════

Regenerated Tomcat Keystore                               ✓

═══════════════════ Restarting Services ═══════════════════

┃ Tomcat restart required, restart Tomcat?
┃
┃               yes     no

    (Välj "ja")

    ═══════════════════ Restarting Services ═══════════════════

⣻  Restarting Tomcat...
...

Tomcat restarted

    -- eller --
    avamar-kommandon:

    1. Ställ in variabeln "tomcat_keystore":
      För Avamar v19.7 och senare: 
      storepath=/home/tomcat/.keystore
      För Avamar v19.4 och tidigare: 
      storepath=/home/admin/.keystore
    2. Återskapa Tomcat-nyckelbehållaren genom att köra följande kommandon: 
      mv $TOMCAT_KEYSTORE /home/admin/tomcat_keystore.bak
      keytool -genkeypair -v -alias tomcat -keyalg RSA -sigalg SHA256withRSA -keysize 3072 -keystore $TOMCAT_KEYSTORE -storepass $(avlockbox.sh -r keystore_passphrase) -validity 3650 -dname "CN=$(hostname -f), OU=Dell EMC, O=Dell Technologies, L=Irvine, ST=California, C=US"
      keytool -import -file /tmp/mcssl.pem -alias mcssl -keystore $TOMCAT_KEYSTORE -storepass $(avlockbox.sh -r keystore_passphrase)
      keytool -import -file /tmp/mcssl.pem -alias mcssl -keystore $TOMCAT_KEYSTORE -storepass $(avlockbox.sh -r keystore_passphrase)
    3. Uppdatera behörigheter och ägarskap för nyckelbehållaren:
      För Avamar v19.7 och senare: 
      chmod 640 $TOMCAT_KEYSTORE
      chown root:tomcat $TOMCAT_KEYSTORE
      För Avamar v19.4 och tidigare: 
      chmod 740 $TOMCAT_KEYSTORE
      chown admin:admin $TOMCAT_KEYSTORE

Endast återskapa AVI-certifikaten:

Återskapar "/usr/local/avamar/lib/avi/avi_keystore"

  1. Logga in på Avamar-verktygsnoden som administratör.

  2. Höj till rotprivilegium.

  3. Gör en säkerhetskopia av den befintliga nyckelbehållaren:

    cp -p /usr/local/avamar/lib/avi/avi_keystore /usr/local/avamar/lib/avi/avi_keystore.`date +%y%m%d`

  4. Kontrollera att säkerhetskopian finns:

    ls -al /usr/local/avamar/lib/avi/avi_keystore*

  5. Nyckelbehållaren kan uppdateras med GoAV OR genom att köra kommandon på Avamar:

    Kommandot "GoAV" (och exempel på utdata):
    ./goav security keystore regenerate

    ╔════════════════════════════════════════════════════════╗
║ GoAV                                             v2.02 ║
╟────────────────────────────────────────────────────────╢
║ Build : 02 Feb 2026 19:03 UTC                          ║
║ Date  : 18 Feb 2026 05:37 UTC                          ║
║ Avamar: 19.4.100-124                                   ║
╟────────────────────────────────────────────────────────╢
║ Command:/home/admin/20260218/goav security keystore    ║
║         regenerate                                     ║
╟────────────────────────────────────────────────────────╢
║ NOTE: This tool was created and is maintained          ║
║       by the ISG Support Tools team.                   ║
╚════════════════════════════════════════════════════════╝

┃ Select Keystore to Regenerate
┃   RMI_SSL_KEYSTORE
┃   AVAMAR_KEYSTORE
┃ > AVI_KEYSTORE
┃   TOMCAT_KEYSTORE

    (Välj "AVI_KEYSTORE")

    ...
══════════════════ Fixing Keystore Issues ══════════════════

Regenerated Avi Keystore                                  ✓

═══════════════════ Restarting Services ═══════════════════

┃ Avinstaller restart required, restart AVI?
┃
┃                yes     no

    (Välj "ja")

    ═══════════════════ Restarting Services ═══════════════════
  
⣽  Restarting Avinstaller...
...
Avinstaller restarted

    -- Eller --
    Avamar kommandon (och exempelutdata):
    (Tjänsten startas om automatiskt)

    1. Flytta den aktuella nyckelbehållaren åt sidan: 
      mv /usr/local/avamar/lib/avi/avi_keystore /usr/local/avamar/lib/avi/avi_keystore-$(date -I)
    2. Återskapa certifikatet: 
      gen-ssl-cert --norestart --noupdateapache --updateavi --keystorepwd=$(avlockbox.sh -r keystore_passphrase) --verbose
      gen-ssl-cert: INFO: Regenerating avinstaller SSL certifcate
        keytool -genkey -alias tomcat -keyalg RSA -sigalg SHA512withRSA -keysize 3072 -keypass ######### -storepass ########## -keystore /usr/local/avamar/lib/avi/avi_keystore -validity 3650 -dname "CN=server.company.com, O=Dell Technologies, OU=Dell EMC, L=Irvine, S=CA, C=US"
gen-ssl-cert: INFO: Successfully created tomcat in java keystore
gen-ssl-cert: INFO: Restarting avinstaller service
gen-ssl-cert: INFO: avinstaller service restart complete
gen-ssl-cert: INFO: Restarting LDLS service
gen-ssl-cert: INFO: LDLS service restart complete
    3. Exportera aliaset från "rmi_ssl_keystore": 
      keytool -export -file /tmp/mcssl.pem -alias mcssl -keystore /usr/local/avamar/lib/rmi_ssl_keystore -storepass $(avlockbox.sh -r keystore_passphrase)
      Certificate stored in file </tmp/mcssl.pem>
    4. Importera aliaset till "avi_keystore": 
      keytool -import -file /tmp/mcssl.pem -alias mcssl -keystore /usr/local/avamar/lib/avi/avi_keystore -storepass $(avlockbox.sh -r keystore_passphrase)
      Owner: CN=server.company.com, OU=Avamar, O=Dell, L=Irvine, ST=California, C=US
Issuer: CN=server.company.com, OU=Avamar, O=Dell, L=Irvine, ST=California, C=US
Serial number: d93e3be
Valid from: Wed Feb 18 16:11:15 PST 2026 until: Sat Feb 16 16:11:15 PST 2036
Certificate fingerprints:
         SHA1: 82:82:81:B4:C9:BD:03:E1:8A:E0:AE:8A:59:55:EF:B5:1F:3B:27:5F
         SHA256: AC:E7:AE:CE:04:13:E0:86:88:1E:3E:FA:17:DA:B6:A5:3D:3D:74:F3:EB:70:57:63:58:B1:74:B3:50:28:EA:01
Signature algorithm name: SHA512withRSA
Subject Public Key Algorithm: 3072-bit RSA key
Version: 3
Trust this certificate? [no]:
      (Välj "y") 
      Certificate was added to keystore
    5. Uppdatera behörighet och ägarskap (och verifiera): 
      chmod 644 /usr/local/avamar/lib/avi/avi_keystore
      chown avi:avi /usr/local/avamar/lib/avi/avi_keystore
      ls -al /usr/local/avamar/lib/avi/avi_keystore

Återskapa MCSDK-certifikat (Management Console Server) Developer Kit (MCSDK):

  • Detta uppdaterar Avamar RMI Keystore som innehåller "MCSDK"-certifikatet och "JWT"-signeringsnyckeln
  • Det återskapar "/usr/local/avamar/lib/rmi_ssl_keystore"
  • MCSDK-certifikatet hanterar RMI-kommunikation (Java Remote Method Invocation) med Data Protection Central (DPC), Avamar Administrator Console, Proxy Deployment Manager (PDM) och Client Manager (AAM).
  • Tomcat-certifikatet bör också uppdateras. Tomcat-nyckelarkivet lagrar Tomcat-certifikaten.
    • Den återskapar "/home/tomcat/.keystore" eller "/home/admin/.keystore" beroende på Avamar-versionen
  • AVI-certifikaten bör också uppdateras
    • Den återskapar "/usr/local/avamar/lib/avi/avi_keystore"

  1. Logga in på Avamar-verktygsnoden som administratör.

  2. Höj till rotprivilegium.

  3. Gör en säkerhetskopia av de befintliga nyckellagren:

    cp -p /usr/local/avamar/lib/rmi_ssl_keystore /usr/local/avamar/lib/rmi_ssl_keystore.`date +%y%m%d`
    cp -p /usr/local/avamar/lib/avi/avi_keystore /usr/local/avamar/lib/avi/avi_keystore.`date +%y%m%d`
    cp -p /home/tomcat/.keystore /home/tomcat/.keystore.`date +%y%m%d`

    (Ersätt "/home/admin/.keystore" med "/home/tomcat/.keystore" i Avamar 19.4 och tidigare)

  4. Kontrollera att säkerhetskopiorna finns:

    ls -al /usr/local/avamar/lib/rmi_ssl_keystore*
    ls -al /usr/local/avamar/lib/avi/avi_keystore*
    ls -al /home/tomcat/.keystore*

    (Ersätt "/home/admin/.keystore" med "/home/tomcat/.keystore" i Avamar 19.4 och tidigare)

  5. Säkerhetskopiera MCS:

    1. Växla till admin
    2. Kör följande kommando för att utföra MCS-säkerhetskopieringen (även kallad tömning):
      mcserver.sh --flush 
      === BEGIN === check.mcs (preflush)
check.mcs                        passed
=== PASS === check.mcs PASSED OVERALL (preflush)
Flushing Administrator Server...
Administrator Server flushed.
    3. Skriv exit för att återgå till rotsessionen.

  6. Nyckelbehållaren kan uppdateras med GoAV OR genom att köra kommandon på Avamar:

    "GoAV"-kommandon (och exempelutdata):

    1. MCSDK:
      ./goav security keystore regenerate 
      ╔════════════════════════════════════════════════════════╗
║ GoAV                                             v2.02 ║
╟────────────────────────────────────────────────────────╢
║ Build : 02 Feb 2026 19:03 UTC                          ║
║ Date  : 18 Feb 2026 05:37 UTC                          ║
║ Avamar: 19.4.100-124                                   ║
╟────────────────────────────────────────────────────────╢
║ Command:/home/admin/20260218/goav security keystore    ║
║         regenerate                                     ║
╟────────────────────────────────────────────────────────╢
║ NOTE: This tool was created and is maintained          ║
║       by the ISG Support Tools team.                   ║
╚════════════════════════════════════════════════════════╝

┃ Select Keystore to Regenerate
┃ > RMI_SSL_KEYSTORE
┃   AVAMAR_KEYSTORE
┃   AVI_KEYSTORE
┃   TOMCAT_KEYSTORE
      (Välj "RMI_SSL_KEYSTORE") 
      ⣯  Stopping MCS...
...
══════════════════ Fixing Keystore Issues ══════════════════

Regenerated RMI Keystore                                  ✓

══════ Loading vCenter Certificates into RMI Keystore ══════


═══════════════════ Restarting Services ═══════════════════

┃ MCS restart required, restart MCS?
┃
┃            yes     no
      (Välj "ja") 
      ═══════════════════ Restarting Services ═══════════════════

┃ Do you wish to restart the backup scheduler?
┃
┃            yes     no
      (Välj "ja")
      Om följande tas emot under MCS-omstarten: 
      unable to take mcs flush:
The Administrator Server is not running.
ERROR: Cannot flush the Administrator Server while it is not running.
Start the Administrator Server first.
      1. Starta om MCS:
        dpnctl start MCS
      2. Starta om schemaläggaren för säkerhetskopiering:
        dpnctl start sched
    2. Tomcat:
      ./goav security keystore regenerate 
      ╔════════════════════════════════════════════════════════╗
║ GoAV                                             v2.02 ║
╟────────────────────────────────────────────────────────╢
║ Build : 02 Feb 2026 19:03 UTC                          ║
║ Date  : 18 Feb 2026 05:37 UTC                          ║
║ Avamar: 19.4.100-124                                   ║
╟────────────────────────────────────────────────────────╢
║ Command:/home/admin/20260218/goav security keystore    ║
║         regenerate                                     ║
╟────────────────────────────────────────────────────────╢
║ NOTE: This tool was created and is maintained          ║
║       by the ISG Support Tools team.                   ║
╚════════════════════════════════════════════════════════╝

┃ Select Keystore to Regenerate
┃   RMI_SSL_KEYSTORE
┃   AVAMAR_KEYSTORE
┃   AVI_KEYSTORE
┃ > TOMCAT_KEYSTORE
      (Välj "TOMCAT_KEYSTORE") 
      ⣯  Fixing any Tomcat issues
...
══════════════════ Fixing Keystore Issues ══════════════════

Regenerated Tomcat Keystore                               ✓

═══════════════════ Restarting Services ═══════════════════

┃ Tomcat restart required, restart Tomcat?
┃
┃               yes     no
      (Välj "ja") 
      ═══════════════════ Restarting Services ═══════════════════

⣻  Restarting Tomcat...
...

Tomcat restarted
    3. AVI:
      ./goav security keystore regenerate 
      ╔════════════════════════════════════════════════════════╗
║ GoAV                                             v2.02 ║
╟────────────────────────────────────────────────────────╢
║ Build : 02 Feb 2026 19:03 UTC                          ║
║ Date  : 18 Feb 2026 05:37 UTC                          ║
║ Avamar: 19.4.100-124                                   ║
╟────────────────────────────────────────────────────────╢
║ Command:/home/admin/20260218/goav security keystore    ║
║         regenerate                                     ║
╟────────────────────────────────────────────────────────╢
║ NOTE: This tool was created and is maintained          ║
║       by the ISG Support Tools team.                   ║
╚════════════════════════════════════════════════════════╝

┃ Select Keystore to Regenerate
┃   RMI_SSL_KEYSTORE
┃   AVAMAR_KEYSTORE
┃ > AVI_KEYSTORE
┃   TOMCAT_KEYSTORE
      (Välj "AVI_KEYSTORE") 
      ...
══════════════════ Fixing Keystore Issues ══════════════════

Regenerated Avi Keystore                                  ✓

═══════════════════ Restarting Services ═══════════════════

┃ Avinstaller restart required, restart AVI?
┃
┃                yes     no
      (Välj "ja") 
      ═══════════════════ Restarting Services ═══════════════════
  
⣽  Restarting Avinstaller...
...
Avinstaller restarted

    -- Eller --
    Avamar-kommandon (och exempelutdata):

    1. MCSDK:
      1. Flytta den aktuella nyckelbehållaren åt sidan::
        mv /usr/local/avamar/lib/rmi_ssl_keystore /usr/local/avamar/lib/rmi_keystore-$(date -I)
      2. Återskapa nyckelbehållaren: 
        keytool -genkeypair -v -alias mcssl -keyalg RSA -sigalg SHA512withRSA -keysize 3072 -keystore /usr/local/avamar/lib/rmi_ssl_keystore -validity 3650 -dname "CN=$(hostname -f), OU=Avamar, O=DELL-EMC, L=Irvine, ST=California, C=US" -storepass `ask_pass -r keystore_passphrase` -keypass `ask_pass -r keystore_passphrase` -noprompt
        keytool -genkeypair -v -alias mcjwt -keyalg RSA -sigalg SHA512withRSA -keysize 3072 -keystore /usr/local/avamar/lib/rmi_ssl_keystore -validity 3650 -dname "CN=$(hostname -f), OU=Avamar, O=DELL-EMC, L=Irvine, ST=California, C=US" -storepass `ask_pass -r keystore_passphrase` -keypass `ask_pass -r keystore_passphrase` -noprompt
      3. Uppdatera behörighet och ägarskap (och verifiera): 
        chown root:admin /usr/local/avamar/lib/rmi_ssl+keystore
        chmod 660 /usr/local/avamar/lib/rmi_ssl+keystore
        ls -al /usr/local/avamar/lib/rmi_ssl+keystore
      4. Som administratör startar du om MCS och startar schemaläggaren för säkerhetskopiering: 
        mcserver.sh --stop
        mcuserver.sh --start
        dpnctl start sched
    2. Tomcat:
      1. Ställ in variabeln "tomcat_keystore":
        För Avamar v19.7 och senare: 
        storepath=/home/tomcat/.keystore
        För Avamar v19.4 och tidigare: 
        storepath=/home/admin/.keystore
      2. Återskapa Tomcat-nyckelbehållaren genom att köra följande kommandon: 
        mv $TOMCAT_KEYSTORE /home/admin/tomcat_keystore.bak
        keytool -genkeypair -v -alias tomcat -keyalg RSA -sigalg SHA256withRSA -keysize 3072 -keystore $TOMCAT_KEYSTORE -storepass $(avlockbox.sh -r keystore_passphrase) -validity 3650 -dname "CN=$(hostname -f), OU=Dell EMC, O=Dell Technologies, L=Irvine, ST=California, C=US"
        keytool -export -file /tmp/mcssl.pem -alias mcssl -keystore /usr/local/avamar/lib/rmi_ssl_keystore -storepass $(avlockbox.sh -r keystore_passphrase)
        keytool -import -file /tmp/mcssl.pem -alias mcssl -keystore $TOMCAT_KEYSTORE -storepass $(avlockbox.sh -r keystore_passphrase)
      3. Uppdatera behörigheter och ägarskap för nyckelbehållaren:
        För Avamar v19.7 och senare: 
        chmod 640 $TOMCAT_KEYSTORE
        chown root:tomcat $TOMCAT_KEYSTORE
        För Avamar v19.4 och tidigare: 
        chmod 740 $TOMCAT_KEYSTORE
        chown admin:admin $TOMCAT_KEYSTORE
    3. AVI:
      1. Flytta den aktuella nyckelbehållaren åt sidan:
        mv /usr/local/avamar/lib/avi/avi_keystore /usr/local/avamar/lib/avi/avi_keystore-$(date -I)
      2. Återskapa nyckelbehållaren:
        gen-ssl-cert --norestart --noupdateapache --updateavi --keystorepwd=$(avlockbox.sh -r keystore_passphrase) --verbose 
        gen-ssl-cert: INFO: Regenerating avinstaller SSL certifcate
        keytool -genkey -alias tomcat -keyalg RSA -sigalg SHA512withRSA -keysize 3072 -keypass ######### -storepass ########## -keystore /usr/local/avamar/lib/avi/avi_keystore -validity 3650 -dname "CN=server.company.com, O=Dell Technologies, OU=Dell EMC, L=Irvine, S=CA, C=US"
gen-ssl-cert: INFO: Successfully created tomcat in java keystore
gen-ssl-cert: INFO: Restarting avinstaller service
gen-ssl-cert: INFO: avinstaller service restart complete
gen-ssl-cert: INFO: Restarting LDLS service
gen-ssl-cert: INFO: LDLS service restart complete
      3. Exportera aliaset från "rmi_ssl_keystore": 
        keytool -export -file /tmp/mcssl.pem -alias mcssl -keystore /usr/local/avamar/lib/rmi_ssl_keystore -storepass $(avlockbox.sh -r keystore_passphrase)
        Certificate stored in file </tmp/mcssl.pem>
      4. Importera aliaset till "avi_keystore":
        keytool -import -file /tmp/mcssl.pem -alias mcssl -keystore /usr/local/avamar/lib/avi/avi_keystore -storepass $(avlockbox.sh -r keystore_passphrase) 
        Owner: CN=server.company.com, OU=Avamar, O=Dell, L=Irvine, ST=California, C=US
Issuer: CN=server.company.com, OU=Avamar, O=Dell, L=Irvine, ST=California, C=US
Serial number: d93e3be
Valid from: Wed Feb 18 16:11:15 PST 2026 until: Sat Feb 16 16:11:15 PST 2036
Certificate fingerprints:
         SHA1: 82:82:81:B4:C9:BD:03:E1:8A:E0:AE:8A:59:55:EF:B5:1F:3B:27:5F
         SHA256: AC:E7:AE:CE:04:13:E0:86:88:1E:3E:FA:17:DA:B6:A5:3D:3D:74:F3:EB:70:57:63:58:B1:74:B3:50:28:EA:01
Signature algorithm name: SHA512withRSA
Subject Public Key Algorithm: 3072-bit RSA key
Version: 3
Trust this certificate? [no]:
        (Välj "y") 
        Certificate was added to keystore
      5. Uppdatera behörighet och ägarskap (och verifiera): 
        chmod 644 /usr/local/avamar/lib/avi/avi_keystore
        chown avi:avi /usr/local/avamar/lib/avi/avi_keystore
        ls -al /usr/local/avamar/lib/avi/avi_keystore

Återskapa rotcertifikaten för Management Console Service (MCS):

  • Det här steget uppdaterar alla MCS-rotcertifikat.
  • Den återskapar "/usr/local/avamar/lib/avamar_keystore"
  • Dessa certifikat bör endast uppdateras om de har upphört att gälla eller snart kommer att upphöra.
  • Det påverkar klientsäkerhetskopiering, återställning och replikering om sessionssäkerhet är aktiverat.
  • Det globala SAN-nätverket (GSAN) måste också återskapas.

  1. Logga in på Avamar-verktygsnoden som administratör.

  2. Höj till rotprivilegium.

  3. Gör en säkerhetskopia av de befintliga nyckellagren:

    cp -p /usr/local/avamar/lib/avamar_keystore /usr/local/avamar/lib/avamar_keystore.`date +%y%m%d`

  4. Kontrollera att säkerhetskopiorna finns:

    ls -al /usr/local/avamar/lib/avamar_keystore*

  5. Säkerhetskopiera MCS:

    1. Växla till admin
    2. Kör följande kommando för att utföra MCS-säkerhetskopieringen (även kallad tömning):
      mcserver.sh --flush 
      === BEGIN === check.mcs (preflush)
check.mcs                        passed
=== PASS === check.mcs PASSED OVERALL (preflush)
Flushing Administrator Server...
Administrator Server flushed.
    3. Skriv exit för att återgå till rotsessionen.

  6. Nyckelbehållaren kan uppdateras med GoAV OR genom att köra kommandon på Avamar:

    Kommandot "GoAV" (och exempel på utdata):
    ./goav security keystore regenerate

    ╔════════════════════════════════════════════════════════╗
║ GoAV                                             v2.02 ║
╟────────────────────────────────────────────────────────╢
║ Build : 02 Feb 2026 19:03 UTC                          ║
║ Date  : 18 Feb 2026 05:37 UTC                          ║
║ Avamar: 19.4.100-124                                   ║
╟────────────────────────────────────────────────────────╢
║ Command:/home/admin/20260218/goav security keystore    ║
║         regenerate                                     ║
╟────────────────────────────────────────────────────────╢
║ NOTE: This tool was created and is maintained          ║
║       by the ISG Support Tools team.                   ║
╚════════════════════════════════════════════════════════╝

┃ Select Keystore to Regenerate
┃   RMI_SSL_KEYSTORE
┃ > AVAMAR_KEYSTORE
┃   AVI_KEYSTORE
┃   TOMCAT_KEYSTORE

    (Välj "AVAMAR_KEYSTORE")

    ⣯  Stopping MCS...
...
══════════════════ Fixing Keystore Issues ══════════════════

⢿  Fixing any AVAMAR_KEYSTORE issues...

Regenerated Avamar Keystore                               ✓

═══════════════════ Restarting Services ═══════════════════

┃ MCS restart required, restart MCS?
┃
┃            yes     no

←/→ toggle • enter submit • y yes • n no

    (Välj "ja")

    ═══════════════════ Restarting Services ═══════════════════

┃ Do you wish to restart the backup scheduler?
┃
┃            yes     no

    (Välj "ja")

    Om följande tas emot under MCS-omstarten:

    unable to take mcs flush:
The Administrator Server is not running.
ERROR: Cannot flush the Administrator Server while it is not running.
Start the Administrator Server first.
    1. Starta om MCS:
      dpnctl start MCS
    2. Starta om schemaläggaren för säkerhetskopiering:
      dpnctl start sched

    -- Eller --
    Avamar-kommandon (och exempelutdata):

    1. Flytta den aktuella nyckelbehållaren åt sidan:
      mv /usr/local/avamar/lib/avi/avi_keystore /usr/local/avamar/lib/avi/avi_keystore-$(date -I)
    2. Återskapa nyckelbehållaren:
      mcrootca all 
      INFO: Executing mcrootca...
INFO: Initializing, may take a few moments...
INFO: Generating, saving and verifying MC EC root key and certificate...
INFO: Successfully generated, saved and verified MC EC root key and certificate.
INFO: Generating and saving EC TLS key and certificate...
INFO: Successfully generated and saved EC TLS key and certificate.
INFO: Verifying EC TLS certificate...
INFO: Successfully verified EC TLS certificate.
INFO: Test loading EC CA certificate(s)...
INFO: Successfully loaded EC CA certificate(s)...
INFO: Verifying EC CA certificate(s)...
INFO: Successfully verified EC CA certificate(s)...
INFO: Setting EC root key and certificate as new...
INFO: Successfully set EC root key and certificate as new.
INFO: Generating, saving and verifying MC RSA root key and certificate...
INFO: Successfully generated, saved and verified MC RSA root key and certificate.
INFO: Generating and saving RSA TLS key and certificate...
INFO: Successfully generated and saved RSA TLS key and certificate.
INFO: Verifying RSA TLS certificate...
INFO: Successfully verified RSA TLS certificate.
INFO: Test loading RSA CA certificate(s)...
INFO: Successfully loaded RSA CA certificate(s)...
INFO: Verifying RSA CA certificate(s)...
INFO: Successfully verified RSA CA certificate(s)...
INFO: Test loading TLS certificate...
INFO: Successfully loaded TLS certificate.
INFO: Verifying TLS certificate...
INFO: Successfully verified TLS certificate.
INFO: Setting RSA root key and certificate as new...
INFO: Successfully set RSA root key and certificate as new.
INFO: mcrootca exited with return value = 0
    3. Som administratör startar du om MCS och startar schemaläggaren för säkerhetskopiering: 
      mcserver.sh --stop
      mcuserver.sh --start
      dpnctl start sched

  7. Återskapa GSAN-certifikaten:

    1. Gör en säkerhetskopia av katalogen "/usr/local/avamar/etc/directory":
      tar -cvf /home/admin/avamar_etc_bk.`date +%y%m%d` /usr/local/avamar/etc/
    2. Kör följande kommando:
      enable_secure_config.sh --certs

  8. Uppdatera Data Domain-certifikatarkivet (DD):

    Detta kan återigen göras med hjälp av GoAV-verktyget eller utföras manuellt
    ." GoAV"-kommandot (och exempelutdata):
    ./goav dd check-ssl --fix

    ╔════════════════════════════════════════════════════════╗
║ GoAV                                             v2.02 ║
╟────────────────────────────────────────────────────────╢
║ Build : 02 Feb 2026 19:03 UTC                          ║
║ Date  : 18 Feb 2026 05:37 UTC                          ║
║ Avamar: 19.4.100-124                                   ║
╟────────────────────────────────────────────────────────╢
║ Command:/home/admin/20260218/goav dd check-ssl --fix   ║
╟────────────────────────────────────────────────────────╢
║ NOTE: This tool was created and is maintained          ║
║       by the ISG Support Tools team.                   ║
╚════════════════════════════════════════════════════════╝
Session Security Enabled                                              PASSED
DDR Security Feature Manual Flag                                      PASSED
DDR Host Cert Auto Refresh Flag                                       PASSED
GSAN Cert Chain Expiration                                            PASSED
GSAN Server Cert Expiration                                           PASSED
Get Attached Data Domains                                             PASSED
Check DDR Key exists                                                  PASSED
Test Port 22: dl003.company.com                                       PASSED
Test ddr_key ssh auth: dl003.company.com                              PASSED
DD/Avamar time difference: dl003.company.com                          PASSED
DD SCP enabled: dl003.company.com                                     PASSED
DD NFS enabled: dl003.company.com                                     PASSED
DD system passphrase is set: dl003.company.com                        PASSED
DD imported-host ddboost: dl003.company.com                           PASSED
DD host issuer is attached: dl003.company.com                         PASSED
Av chain.pem imported to DD: dl003.company.com                        FAILED
avamar gsan chain.pem does not exist on Data Domain
TASK: Delete imported-host ddboost                                    DONE
TASK: Load gsan chain depth 0                                         DONE
TASK: Delete imported ca/login auth                                   DONE
TASK: Restart ddboost                                                 DONE
TASK: Stop MCS                                                        DONE
TASK: Start MCS                                                       DONE
TASK: Sync Data Domain                                                DONE
Backup Scheduler Status                                               FAILED
Removed /usr/local/avamar/etc/10.n.n.16                ✓
Removed /usr/local/avamar/etc/client/10.n.n.16         ✓

Generating new certificates...

"/usr/local/avamar/var/.avagent"
avagent Info <19803>: Ignoring the --service flag.
avagent Info <5702>: Command Line: avagent.bin --gencerts=true --mcsaddr=10.n.n.16
avagent Info <5703>: Parsed Flags: avagent.bin --gencerts=true --mcsaddr=10.n.n.16
2025/01/18-18:20:51.46677 [avagent]  <1291> FIPS mode enabled
avagent Info <42249>: Checking for stale certificate lock
avagent Info <19805>: Creating directory '/usr/local/avamar/etc/10.n.n.16' for certificates
avagent Info <19807>: Creating certificates in '/usr/local/avamar/etc/10.n.n.16'
avagent Info <43701>: agent_message::resolve_client_ip ping to MCS 10.n.n.16:10.n.n.16 using local IP:(none) failed, Program malfunction, Parse bind IP failed for IP: (none)

avagent Info <18918>: Registration: Processing secure registration with the MCS.
avagent Info <18921>: Registration: Requesting root CA from the MCS.
avagent Info <18926>: Registration: Saving root CA.
avagent Info <18928>: Registration: Creating certificate signing request.
avagent Info <18930>: Registration: Sending the certificate signing request to the MCS.
avagent Info <18932>: Registration: Saving client certificate.
avagent Info <18934>: Registration: Secure registration complete.
avagent Info <41048>: Requesting network configuration from the MCS.
avagent Info <5405>: avagent returning with exitcode 0
2026/02/18-18:20:52.13501 [avagent]  Config: VARDIR=/usr/local/avamar/var, HOMEDIR=/root
2026/02/18-18:20:52.13506 [avagent]  Looking for flag file "/usr/local/avamar/var/avamar.cmd"
2026/02/18-18:20:52.13509 [avagent]  Looking for flag file "/usr/local/avamar/var/avagent.cmd"
2026/02/18-18:20:52.13517 [avagent]  Looking for flag file "/usr/local/avamar/var/.avagent"
avagent Info <19803>: Ignoring the --service flag.
avagent Info <5702>: Command Line: avagent.bin --gencerts=true --mcsaddr=10.n.n.16 --sysdir=/usr/local/avamar/etc/client
avagent Info <5703>: Parsed Flags: avagent.bin --gencerts=true --mcsaddr=10.n.n.16 --sysdir=/usr/local/avamar/etc/client
2026/02/18-18:20:52.14446 [avagent]  <1291> FIPS mode enabled
avagent Info <42249>: Checking for stale certificate lock
avagent Info <19805>: Creating directory '/usr/local/avamar/etc/client/10.n.n.16' for certificates
avagent Info <19807>: Creating certificates in '/usr/local/avamar/etc/client/10.n.n.16'
avagent Info <43701>: agent_message::resolve_client_ip ping to MCS 10.n.n.16:10.n.n.16 using local IP:(none) failed, Program malfunction, Parse bind IP failed for IP: (none)

avagent Info <18918>: Registration: Processing secure registration with the MCS.
avagent Info <18921>: Registration: Requesting root CA from the MCS.
avagent Info <18926>: Registration: Saving root CA.
avagent Info <18928>: Registration: Creating certificate signing request.
avagent Info <18930>: Registration: Sending the certificate signing request to the MCS.
avagent Info <18932>: Registration: Saving client certificate.
avagent Info <18934>: Registration: Secure registration complete.
avagent Info <41048>: Requesting network configuration from the MCS.
avagent Info <5405>: avagent returning with exitcode 0

Generated certificates for 10.n.n.16                 ✓

Testing Avtar connection...

avtar Info <5551>: Command Line: /usr/local/avamar/bin/avtar.bin --flagfile=/usr/local/avamar/etc/usersettings.cfg --server=avacrk003 --vardir=/usr/local/avamar/var --bindir=/usr/local/avamar/bin --id=root --password=**************** --vardir=/usr/local/avamar/var --bindir=/usr/local/avamar/bin --sysdir=/usr/local/avamar/etc --backups --account=/MC_BACKUPS --count=10 --encrypt=tls
avtar Info <7977>: Starting at 2026-02-18 18:20:53 GMT [avtar Dec  8 2023 07:07:43 19.10.100-135 Linux-x86_64]
avtar Info <6555>: Initializing connection
avtar Info <5552>: Connecting to Avamar Server (avacrk003)
avtar Info <5554>: Connecting to one node in each datacenter
avtar Info <5583>: Login User: "root", Domain: "default", Account: "/MC_BACKUPS"
avtar Info <5580>: Logging in on connection 0 (server 0)
avtar Info <5582>: Avamar Server login successful
avtar Info <10632>: Using Client-ID='6638d648ef621aa9dc20be40ab49e0820dac9b39'
avtar Info <5550>: Successfully logged into Avamar Server [19.10.0-135]
avtar Info <19849>: Selecting 10 backups
avtar Info <7377>: Backups for /MC_BACKUPS as of 2025-11-25 18:20:53 GMT
avtar Info <5314>: Command completed (exit code 0: success)
    Date      Time    Seq       Label           Size     Plugin    Working directory         Targets

2026-02-18 18:15:56  3726                     2034984K Linux    /usr/local/avamar     var/mc/server_data
2026-02-17 18:08:30  3725                     2034952K Linux    /usr/local/avamar     var/mc/server_data
2026-02-16 17:31:43  3724                     2033952K Linux    /usr/local/avamar     var/mc/server_data
2026-02-15 08:00:31  3723                     1035390K Linux    /usr/local/avamar     var/mc/server_data
2026-02-14 07:45:20  3722                     1035346K Linux    /usr/local/avamar     var/mc/server_data
2026-02-13 08:00:29  3721                     1035313K Linux    /usr/local/avamar     var/mc/server_data
2026-02-12 07:45:19  3720                     1035269K Linux    /usr/local/avamar     var/mc/server_data
2026-02-11 08:00:30  3719                     1035419K Linux    /usr/local/avamar     var/mc/server_data
2026-02-10 07:45:18  3718                     1035377K Linux    /usr/local/avamar     var/mc/server_data
2026-02-09 08:00:30  3717                     1035511K Linux    /usr/local/avamar     var/mc/server_data

    -- Eller --
    Manuella steg (och exempelutdata):

    1. Följ "Scenario 1" i artikeln om lösningssökväg Avamar: DD visar rött i Avamar AUI
    2. Generera en ny uppsättning klientcertifikat för "avtar" om sådana finns.
      Sök efter klientcertifikat i BÅDE "/usr/local/avamar/etc" och "/usr/local/avamar/etc/client": 
      cd /usr/local/avamar/etc/$(hostname -i)
      cd /usr/local/avamar/etc/client/$(hostname -i)
      • Om båda kommandona rapporterar "Ingen sådan fil eller katalog" innebär det att Avamar inte använder klientcertifikatet. Gå till steg 9.
      • Om det finns någon av katalogerna följer du steg c-e nedan.
    3. Ta bort den befintliga klientcertifikatkatalogen:
      Försiktighet: Kopiera kommandona nedan enligt bilden. ÄNDRA DEM INTE. 
      rm -r /usr/local/avamar/etc/$(hostname -i)
      rm -r /usr/local/avamar/etc/client/$(hostname -i)
    4. Generera en ny uppsättning klientcertifikat för "avtar" endast för de befintliga katalogerna ovan: 
      avagent.bin --gencerts=true --mcsaddr=$(hostname -i)
      avagent.bin --gencerts=true --mcsaddr=$(hostname -i) --sysdir=/usr/local/avamar/etc/client
    5. Testa en anslutning för att bekräfta om avtar kan ansluta till "GSAN": 
      avtar --backups --path=/MC_BACKUPS --count=5 --encrypt=tls

  9. Registrera om alla klienter och VMware-proxyservrar:

    1. Registrera om de agentbaserade klienterna:
      mccli client re-register-all
    2. Registrera om VMware-proxyservrar genom att starta om dem centralt från Avamar:
      mccli mcs reboot-proxy --all

Återskapa ALLA certifikat:

Alla certifikat och nyckelbehållare som dokumenteras ovan återskapas

  1. Logga in på Avamar-verktygsnoden som administratör.

  2. Höj till rotprivilegium.

  3. Gör en säkerhetskopia av de befintliga nyckellagren:

    cp -p /usr/local/avamar/lib/rmi_ssl_keystore /usr/local/avamar/lib/rmi_ssl_keystore.`date +%y%m%d`
cp -p /usr/local/avamar/lib/avi/avi_keystore /usr/local/avamar/lib/avi/avi_keystore.`date +%y%m%d`
cp -p /home/tomcat/.keystore /home/tomcat/.keystore.`date +%y%m%d`
cp -p /etc/apache2/ssl.crt/server.crt /etc/apache2/ssl.crt/server.crt.`date +%y%m%d`
cp -p /etc/apache2/ssl.key/server.key /etc/apache2/ssl.key/server.key.`date +%y%m%d`
cp -p /usr/local/avamar/lib/avamar_keystore /usr/local/avamar/lib/avamar_keystore.`date +%y%m%d`

  4. Kontrollera att säkerhetskopiorna finns:

    ls -al /usr/local/avamar/lib/rmi_ssl_keystore*
ls -al /usr/local/avamar/lib/avi/avi_keystore*
ls -al/home/tomcat/.keystore*
ls -al /etc/apache2/ssl.crt/server.crt*
ls -al /etc/apache2/ssl.key/server.key*
ls -al/usr/local/avamar/lib/avamar_keystore*

    (Ersätt "/home/admin/.keystore" igen med "/home/tomcat/.keystore" i Avamar 19.4 och tidigare)

  5. Säkerhetskopiera MCS:

    1. Växla till admin
    2. Kör följande kommando för att utföra MCS-säkerhetskopieringen (även kallad tömning):
      mcserver.sh --flush 
      === BEGIN === check.mcs (preflush)
check.mcs                        passed
=== PASS === check.mcs PASSED OVERALL (preflush)
Flushing Administrator Server...
Administrator Server flushed.
    3. Skriv exit för att återgå till rotsessionen.

  6. GOAV kan användas för att återskapa alla nyckelbehållare på en gång, ELLER genom att köra kommandon på Avamar:

    GoAV-kommando (och exempelutdata):

    1. Återskapa alla nyckelbehållare:
      ./goav security keystore regenerate all 
      ╔════════════════════════════════════════════════════════╗
║ GoAV                                             v2.02 ║
╟────────────────────────────────────────────────────────╢
║ Build : 02 Feb 2026 19:03 UTC                          ║
║ Date  : 19 Feb 2026 05:33 UTC                          ║
║ Avamar: 19.4.100-124                                   ║
╟────────────────────────────────────────────────────────╢
║ Command:./goav security keystore regenerate --all      ║
╟────────────────────────────────────────────────────────╢
║ NOTE: This tool was created and is maintained          ║
║       by the ISG Support Tools team.                   ║
╚════════════════════════════════════════════════════════╝

⣯  Stopping MCS...
...
Regenerated RMI Keystore                                  ✓
Regenerated Avamar Keystore                               ✓
Regenerated Avi Keystore                                  ✓
Regenerated Tomcat Keystore                               ✓
══════ Loading vCenter Certificates into RMI Keystore ══════

═══════════════════ Restarting Services ═══════════════════

┃ MCS restart required, restart MCS?
┃
┃            yes     no
      (Välj "ja") 
      ═══════════════════ Restarting Services ═══════════════════

┃ Do you wish to restart the backup scheduler?
┃
┃            yes     no
      (Välj "ja")
      Om följande tas emot under MCS-omstarten: 
      unable to take mcs flush:
The Administrator Server is not running.
ERROR: Cannot flush the Administrator Server while it is not running.
Start the Administrator Server first.
      1. Starta om MCS:
        dpnctl start MCS
      2. Starta om schemaläggaren för säkerhetskopiering:
        dpnctl start sched
    2. Återskapa Apache-certifikat:
      ./goav security certificate apache regenerate 
      ╔════════════════════════════════════════════════════════╗
║ GoAV                                             v2.02 ║
╟────────────────────────────────────────────────────────╢
║ Build : 02 Feb 2026 19:03 UTC                          ║
║ Date  : 18 Feb 2026 04:52 UTC                          ║
║ Avamar: 19.4.100-124                                   ║
╟────────────────────────────────────────────────────────╢
║ Command:./goav security certificate apache regenerate  ║
╟────────────────────────────────────────────────────────╢
║ NOTE: This tool was created and is maintained          ║
║       by the ISG Support Tools team.                   ║
╚════════════════════════════════════════════════════════╝
┃ Select a Key Size in bits:
┃ > 2048
┃   3072
┃   4096
      (Välj önskad nyckelstorlek eller använd standardvärdet 2048) 
      Apache x509 Certificate Configuration
-------------------------------------

Apache Private Key
------------------
Location            /etc/apache2/ssl.key/server.key
Modulus MD5sum      0d35d9c14239093d4f5e28bd5f2f98c8
Key Size            2048

Apache Server Cert
------------------
Location            /etc/apache2/ssl.crt/server.crt
Serial              129741042722659803976190762572696306257
Subject             C=US, ST=Texas, L=Round Rock, O=Dell Technologies, CN=server.company.com
Issuer              C=US, ST=Texas, L=Round Rock, O=Dell Technologies, CN=server.company.com
Valid Range         YYYY/MM/DD - valid from: 2026/02/18, valid to: 2028/02/18
Modulus MD5sum      0d35d9c14239093d4f5e28bd5f2f98c8
Key Size            2048
Subject Alt Names   server.company.com

    -- Eller --
    Avamar-kommandon (och exempelutdata):

    1. MCS-rotcertifikat:
      1. Flytta den aktuella nyckelbehållaren åt sidan:
        mv /usr/local/avamar/lib/avi/avi_keystore /usr/local/avamar/lib/avi/avi_keystore-$(date -I)
      2. Återskapa nyckelbehållaren:
        mcrootca all 
        INFO: Executing mcrootca...
INFO: Initializing, may take a few moments...
INFO: Generating, saving and verifying MC EC root key and certificate...
INFO: Successfully generated, saved and verified MC EC root key and certificate.
INFO: Generating and saving EC TLS key and certificate...
INFO: Successfully generated and saved EC TLS key and certificate.
INFO: Verifying EC TLS certificate...
INFO: Successfully verified EC TLS certificate.
INFO: Test loading EC CA certificate(s)...
INFO: Successfully loaded EC CA certificate(s)...
INFO: Verifying EC CA certificate(s)...
INFO: Successfully verified EC CA certificate(s)...
INFO: Setting EC root key and certificate as new...
INFO: Successfully set EC root key and certificate as new.
INFO: Generating, saving and verifying MC RSA root key and certificate...
INFO: Successfully generated, saved and verified MC RSA root key and certificate.
INFO: Generating and saving RSA TLS key and certificate...
INFO: Successfully generated and saved RSA TLS key and certificate.
INFO: Verifying RSA TLS certificate...
INFO: Successfully verified RSA TLS certificate.
INFO: Test loading RSA CA certificate(s)...
INFO: Successfully loaded RSA CA certificate(s)...
INFO: Verifying RSA CA certificate(s)...
INFO: Successfully verified RSA CA certificate(s)...
INFO: Test loading TLS certificate...
INFO: Successfully loaded TLS certificate.
INFO: Verifying TLS certificate...
INFO: Successfully verified TLS certificate.
INFO: Setting RSA root key and certificate as new...
INFO: Successfully set RSA root key and certificate as new.
INFO: mcrootca exited with return value = 0
      3. Som administratör startar du om MCS och startar schemaläggaren för säkerhetskopiering: 
        mcserver.sh --stop
        mcuserver.sh --start
        dpnctl start sched
    2. MCSDK:
      1. Flytta den aktuella nyckelbehållaren åt sidan:
        mv /usr/local/avamar/lib/rmi_ssl_keystore /usr/local/avamar/lib/rmi_keystore-$(date -I)
      2. Återskapa nyckelbehållaren: 
        keytool -genkeypair -v -alias mcssl -keyalg RSA -sigalg SHA512withRSA -keysize 3072 -keystore /usr/local/avamar/lib/rmi_ssl_keystore -validity 3650 -dname "CN=$(hostname -f), OU=Avamar, O=DELL-EMC, L=Irvine, ST=California, C=US" -storepass `ask_pass -r keystore_passphrase` -keypass `ask_pass -r keystore_passphrase` -noprompt
        keytool -genkeypair -v -alias mcjwt -keyalg RSA -sigalg SHA512withRSA -keysize 3072 -keystore /usr/local/avamar/lib/rmi_ssl_keystore -validity 3650 -dname "CN=$(hostname -f), OU=Avamar, O=DELL-EMC, L=Irvine, ST=California, C=US" -storepass `ask_pass -r keystore_passphrase` -keypass `ask_pass -r keystore_passphrase` -noprompt
      3. Uppdatera behörighet och ägarskap (och verifiera): 
        chown root:admin /usr/local/avamar/lib/rmi_ssl+keystore
        chmod 660 /usr/local/avamar/lib/rmi_ssl+keystore
        ls -al /usr/local/avamar/lib/rmi_ssl_keystore
      4. Som administratör startar du om MCS och startar schemaläggaren för säkerhetskopiering: 
        mcserver.sh --stop
        mcuserver.sh --start
        dpnctl start sched
    3. Tomcat:
      1. Ställ in variabeln "tomcat_keystore":
        För Avamar v19.7 och senare: 
        storepath=/home/tomcat/.keystore
        För Avamar v19.4 och tidigare: 
        storepath=/home/admin/.keystore
      2. Återskapa Tomcat-nyckelbehållaren genom att köra följande kommandon: 
        mv $TOMCAT_KEYSTORE /home/admin/tomcat_keystore.bak
        keytool -genkeypair -v -alias tomcat -keyalg RSA -sigalg SHA256withRSA -keysize 3072 -keystore $TOMCAT_KEYSTORE -storepass $(avlockbox.sh -r keystore_passphrase) -validity 3650 -dname "CN=$(hostname -f), OU=Dell EMC, O=Dell Technologies, L=Irvine, ST=California, C=US"
        keytool -export -file /tmp/mcssl.pem -alias mcssl -keystore /usr/local/avamar/lib/rmi_ssl_keystore -storepass $(avlockbox.sh -r keystore_passphrase)
        keytool -import -file /tmp/mcssl.pem -alias mcssl -keystore $TOMCAT_KEYSTORE -storepass $(avlockbox.sh -r keystore_passphrase)
      3. Uppdatera behörigheter och ägarskap för nyckelbehållaren:
        För Avamar v19.7 och senare: 
        chmod 640 $TOMCAT_KEYSTORE
        chown root:tomcat $TOMCAT_KEYSTORE
        För Avamar v19.4 och tidigare: 
        chmod 740 $TOMCAT_KEYSTORE
        chown admin:admin $TOMCAT_KEYSTORE
    4. AVI: (Tjänsten startar om automatiskt)
      1. Flytta den aktuella nyckelbehållaren åt sidan:
        mv /usr/local/avamar/lib/avi/avi_keystore /usr/local/avamar/lib/avi/avi_keystore-$(date -I)
      2. Återskapa nyckelbehållaren:
        gen-ssl-cert --norestart --noupdateapache --updateavi --keystorepwd=$(avlockbox.sh -r keystore_passphrase) --verbose 
        gen-ssl-cert: INFO: Regenerating avinstaller SSL certifcate
        keytool -genkey -alias tomcat -keyalg RSA -sigalg SHA512withRSA -keysize 3072 -keypass ######### -storepass ########## -keystore /usr/local/avamar/lib/avi/avi_keystore -validity 3650 -dname "CN=server.company.com, O=Dell Technologies, OU=Dell EMC, L=Irvine, S=CA, C=US"
gen-ssl-cert: INFO: Successfully created tomcat in java keystore
gen-ssl-cert: INFO: Restarting avinstaller service
gen-ssl-cert: INFO: avinstaller service restart complete
gen-ssl-cert: INFO: Restarting LDLS service
gen-ssl-cert: INFO: LDLS service restart complete
      3. Exportera aliaset från "rmi_ssl_keystore": 
        keytool -export -file /tmp/mcssl.pem -alias mcssl -keystore /usr/local/avamar/lib/rmi_ssl_keystore -storepass $(avlockbox.sh -r keystore_passphrase)
        Certificate stored in file </tmp/mcssl.pem>
      4. Importera aliaset till "avi_keystore":
        keytool -import -file /tmp/mcssl.pem -alias mcssl -keystore /usr/local/avamar/lib/avi/avi_keystore -storepass $(avlockbox.sh -r keystore_passphrase) 
        Owner: CN=server.company.com, OU=Avamar, O=Dell, L=Irvine, ST=California, C=US
Issuer: CN=server.company.com, OU=Avamar, O=Dell, L=Irvine, ST=California, C=US
Serial number: d93e3be
Valid from: Wed Feb 18 16:11:15 PST 2026 until: Sat Feb 16 16:11:15 PST 2036
Certificate fingerprints:
         SHA1: 82:82:81:B4:C9:BD:03:E1:8A:E0:AE:8A:59:55:EF:B5:1F:3B:27:5F
         SHA256: AC:E7:AE:CE:04:13:E0:86:88:1E:3E:FA:17:DA:B6:A5:3D:3D:74:F3:EB:70:57:63:58:B1:74:B3:50:28:EA:01
Signature algorithm name: SHA512withRSA
Subject Public Key Algorithm: 3072-bit RSA key
Version: 3
Trust this certificate? [no]:
        (Välj "y") 
        Certificate was added to keystore
      5. Uppdatera behörighet och ägarskap (och verifiera): 
        chmod 644 /usr/local/avamar/lib/avi/avi_keystore
        chown avi:avi /usr/local/avamar/lib/avi/avi_keystore
        ls -al /usr/local/avamar/lib/avi/avi_keystore
    5. Apache:
      gen-ssl-cert --updateapache --noupdateavi --keystorepwd=$(avlockbox.sh -r keystore_passphrase) --verbose 
             openssl genrsa -out /tmp/gen-ssl-cert-server.key.9085 3072
Generating RSA private key, 3072 bit long modulus
e is 65537 (0x10001)
        openssl req -new -key /tmp/gen-ssl-cert-server.key.9085 -out /tmp/gen-ssl-cert-server.csr.9085 < /tmp/gen-ssl-cert-answers.9085
You are about to be asked to enter information that will be incorporated
into your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN.
There are quite a few fields but you can leave some blank
For some fields there will be a default value,
If you enter '.', the field will be left blank.
...

           |-30200 /usr/sbin/httpd-prefork -DSYSCONFIG -DSSL -C PidFile /var/run/httpd.pid -C Include /etc/apache2/sysconfig.d//loadmodule.conf -C Include /etc/apache2/sysconfig.d//global.conf -f /etc/apache2/httpd.conf -c Include /etc/apache2/sysconfig.d//include.conf -DSYSTEMD -DFOREGROUND -k start
           `-30206 /usr/sbin/httpd-prefork -DSYSCONFIG -DSSL -C PidFile /var/run/httpd.pid -C Include /etc/apache2/sysconfig.d//loadmodule.conf -C Include /etc/apache2/sysconfig.d//global.conf -f /etc/apache2/httpd.conf -c Include /etc/apache2/sysconfig.d//include.conf -DSYSTEMD -DFOREGROUND -k start

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
        /sbin/service apache2 stop
        /sbin/service apache2 start

  7. Återskapa GSAN-certifikaten:

    1. Gör en säkerhetskopia av katalogen "/usr/local/avamar/etc/directory":
      tar -cvf /home/admin/avamar_etc_bk.`date +%y%m%d` /usr/local/avamar/etc/
    2. Kör följande kommando:
      enable_secure_config.sh --certs

  8. Uppdatera Data Domain-certifikatarkivet (DD):

    Detta kan återigen göras med hjälp av GoAV-verktyget eller utföras manuellt
    ." GoAV"-kommandot (och exempelutdata):
    ./goav dd check-ssl --fix

    ╔════════════════════════════════════════════════════════╗
║ GoAV                                             v2.02 ║
╟────────────────────────────────────────────────────────╢
║ Build : 02 Feb 2026 19:03 UTC                          ║
║ Date  : 18 Feb 2026 05:37 UTC                          ║
║ Avamar: 19.4.100-124                                   ║
╟────────────────────────────────────────────────────────╢
║ Command:/home/admin/20260218/goav dd check-ssl --fix   ║
╟────────────────────────────────────────────────────────╢
║ NOTE: This tool was created and is maintained          ║
║       by the ISG Support Tools team.                   ║
╚════════════════════════════════════════════════════════╝
Session Security Enabled                                              PASSED
DDR Security Feature Manual Flag                                      PASSED
DDR Host Cert Auto Refresh Flag                                       PASSED
GSAN Cert Chain Expiration                                            PASSED
GSAN Server Cert Expiration                                           PASSED
Get Attached Data Domains                                             PASSED
Check DDR Key exists                                                  PASSED
Test Port 22: dl003.company.com                                       PASSED
Test ddr_key ssh auth: dl003.company.com                              PASSED
DD/Avamar time difference: dl003.company.com                          PASSED
DD SCP enabled: dl003.company.com                                     PASSED
DD NFS enabled: dl003.company.com                                     PASSED
DD system passphrase is set: dl003.company.com                        PASSED
DD imported-host ddboost: dl003.company.com                           PASSED
DD host issuer is attached: dl003.company.com                         PASSED
Av chain.pem imported to DD: dl003.company.com                        FAILED
avamar gsan chain.pem does not exist on Data Domain
TASK: Delete imported-host ddboost                                    DONE
TASK: Load gsan chain depth 0                                         DONE
TASK: Delete imported ca/login auth                                   DONE
TASK: Restart ddboost                                                 DONE
TASK: Stop MCS                                                        DONE
TASK: Start MCS                                                       DONE
TASK: Sync Data Domain                                                DONE
Backup Scheduler Status                                               FAILED
Removed /usr/local/avamar/etc/10.n.n.16                ✓
Removed /usr/local/avamar/etc/client/10.n.n.16         ✓

Generating new certificates...

"/usr/local/avamar/var/.avagent"
avagent Info <19803>: Ignoring the --service flag.
avagent Info <5702>: Command Line: avagent.bin --gencerts=true --mcsaddr=10.n.n.16
avagent Info <5703>: Parsed Flags: avagent.bin --gencerts=true --mcsaddr=10.n.n.16
2025/01/18-18:20:51.46677 [avagent]  <1291> FIPS mode enabled
avagent Info <42249>: Checking for stale certificate lock
avagent Info <19805>: Creating directory '/usr/local/avamar/etc/10.n.n.16' for certificates
avagent Info <19807>: Creating certificates in '/usr/local/avamar/etc/10.n.n.16'
avagent Info <43701>: agent_message::resolve_client_ip ping to MCS 10.n.n.16:10.n.n.16 using local IP:(none) failed, Program malfunction, Parse bind IP failed for IP: (none)

avagent Info <18918>: Registration: Processing secure registration with the MCS.
avagent Info <18921>: Registration: Requesting root CA from the MCS.
avagent Info <18926>: Registration: Saving root CA.
avagent Info <18928>: Registration: Creating certificate signing request.
avagent Info <18930>: Registration: Sending the certificate signing request to the MCS.
avagent Info <18932>: Registration: Saving client certificate.
avagent Info <18934>: Registration: Secure registration complete.
avagent Info <41048>: Requesting network configuration from the MCS.
avagent Info <5405>: avagent returning with exitcode 0
2026/02/18-18:20:52.13501 [avagent]  Config: VARDIR=/usr/local/avamar/var, HOMEDIR=/root
2026/02/18-18:20:52.13506 [avagent]  Looking for flag file "/usr/local/avamar/var/avamar.cmd"
2026/02/18-18:20:52.13509 [avagent]  Looking for flag file "/usr/local/avamar/var/avagent.cmd"
2026/02/18-18:20:52.13517 [avagent]  Looking for flag file "/usr/local/avamar/var/.avagent"
avagent Info <19803>: Ignoring the --service flag.
avagent Info <5702>: Command Line: avagent.bin --gencerts=true --mcsaddr=10.n.n.16 --sysdir=/usr/local/avamar/etc/client
avagent Info <5703>: Parsed Flags: avagent.bin --gencerts=true --mcsaddr=10.n.n.16 --sysdir=/usr/local/avamar/etc/client
2026/02/18-18:20:52.14446 [avagent]  <1291> FIPS mode enabled
avagent Info <42249>: Checking for stale certificate lock
avagent Info <19805>: Creating directory '/usr/local/avamar/etc/client/10.n.n.16' for certificates
avagent Info <19807>: Creating certificates in '/usr/local/avamar/etc/client/10.n.n.16'
avagent Info <43701>: agent_message::resolve_client_ip ping to MCS 10.n.n.16:10.n.n.16 using local IP:(none) failed, Program malfunction, Parse bind IP failed for IP: (none)

avagent Info <18918>: Registration: Processing secure registration with the MCS.
avagent Info <18921>: Registration: Requesting root CA from the MCS.
avagent Info <18926>: Registration: Saving root CA.
avagent Info <18928>: Registration: Creating certificate signing request.
avagent Info <18930>: Registration: Sending the certificate signing request to the MCS.
avagent Info <18932>: Registration: Saving client certificate.
avagent Info <18934>: Registration: Secure registration complete.
avagent Info <41048>: Requesting network configuration from the MCS.
avagent Info <5405>: avagent returning with exitcode 0

Generated certificates for 10.n.n.16                 ✓

Testing Avtar connection...

avtar Info <5551>: Command Line: /usr/local/avamar/bin/avtar.bin --flagfile=/usr/local/avamar/etc/usersettings.cfg --server=avacrk003 --vardir=/usr/local/avamar/var --bindir=/usr/local/avamar/bin --id=root --password=**************** --vardir=/usr/local/avamar/var --bindir=/usr/local/avamar/bin --sysdir=/usr/local/avamar/etc --backups --account=/MC_BACKUPS --count=10 --encrypt=tls
avtar Info <7977>: Starting at 2026-02-18 18:20:53 GMT [avtar Dec  8 2023 07:07:43 19.10.100-135 Linux-x86_64]
avtar Info <6555>: Initializing connection
avtar Info <5552>: Connecting to Avamar Server (avacrk003)
avtar Info <5554>: Connecting to one node in each datacenter
avtar Info <5583>: Login User: "root", Domain: "default", Account: "/MC_BACKUPS"
avtar Info <5580>: Logging in on connection 0 (server 0)
avtar Info <5582>: Avamar Server login successful
avtar Info <10632>: Using Client-ID='6638d648ef621aa9dc20be40ab49e0820dac9b39'
avtar Info <5550>: Successfully logged into Avamar Server [19.10.0-135]
avtar Info <19849>: Selecting 10 backups
avtar Info <7377>: Backups for /MC_BACKUPS as of 2025-11-25 18:20:53 GMT
avtar Info <5314>: Command completed (exit code 0: success)
    Date      Time    Seq       Label           Size     Plugin    Working directory         Targets

2026-02-18 18:15:56  3726                     2034984K Linux    /usr/local/avamar     var/mc/server_data
2026-02-17 18:08:30  3725                     2034952K Linux    /usr/local/avamar     var/mc/server_data
2026-02-16 17:31:43  3724                     2033952K Linux    /usr/local/avamar     var/mc/server_data
2026-02-15 08:00:31  3723                     1035390K Linux    /usr/local/avamar     var/mc/server_data
2026-02-14 07:45:20  3722                     1035346K Linux    /usr/local/avamar     var/mc/server_data
2026-02-13 08:00:29  3721                     1035313K Linux    /usr/local/avamar     var/mc/server_data
2026-02-12 07:45:19  3720                     1035269K Linux    /usr/local/avamar     var/mc/server_data
2026-02-11 08:00:30  3719                     1035419K Linux    /usr/local/avamar     var/mc/server_data
2026-02-10 07:45:18  3718                     1035377K Linux    /usr/local/avamar     var/mc/server_data
2026-02-09 08:00:30  3717                     1035511K Linux    /usr/local/avamar     var/mc/server_data

    -- Eller --
    Manuella steg (och exempelutdata):

    1. Följ "Scenario 1" i artikeln om lösningssökväg Avamar: DD visar rött i Avamar AUI
    2. Generera en ny uppsättning klientcertifikat för "avtar" om de finns:
      Sök efter klientcertifikat i BÅDE "/usr/local/avamar/etc" och "/usr/local/avamar/etc/client": 
      cd /usr/local/avamar/etc/$(hostname -i)
      cd /usr/local/avamar/etc/client/$(hostname -i)
      • Om båda kommandona rapporterar "Ingen sådan fil eller katalog" innebär det att Avamar inte använder klientcertifikatet. Gå till steg 9.
      • Om det finns någon av katalogerna följer du steg c-e nedan.
    3. Ta bort den befintliga klientcertifikatkatalogen:
      Försiktighet: Kopiera kommandona nedan enligt bilden. ÄNDRA DEM INTE. 
      rm -r /usr/local/avamar/etc/$(hostname -i)
      rm -r /usr/local/avamar/etc/client/$(hostname -i)
    4. Generera en ny uppsättning klientcertifikat för "avtar" endast för de befintliga katalogerna ovan: 
      avagent.bin --gencerts=true --mcsaddr=$(hostname -i)
      avagent.bin --gencerts=true --mcsaddr=$(hostname -i) --sysdir=/usr/local/avamar/etc/client
    5. Testa en anslutning för att bekräfta om avtar kan ansluta till GSAN: 
      avtar --backups --path=/MC_BACKUPS --count=5 --encrypt=tls

  9. Registrera om alla klienter och VMware-proxyservrar:

    1. Registrera om de agentbaserade klienterna: 
      mccli client re-register-all
    2. Registrera om VMware-proxyservrar genom att starta om dem centralt från Avamar: 
      mccli mcs reboot-proxy --all

 

Затронутые продукты

Avamar, Avamar Server

Продукты

Data Domain
Свойства статьи
Номер статьи: 000188770
Тип статьи: How To
Последнее изменение: 14 Jul 2026
Версия:  44
Получите ответы на свои вопросы от других пользователей Dell
Услуги технической поддержки
Проверьте, распространяются ли на ваше устройство услуги технической поддержки.