Avamar: Deaktivieren von Proxy ändert vc_id mit mehreren vCenter-Integrationen
Summary: In diesem Artikel wird erläutert, wie die Deaktivierung eines Proxys in einem Avamar-Server mit mehreren integrierten vCentern die vc_id ändert.
This article applies to
This article does not apply to
This article is not tied to any specific product.
Not all product versions are identified in this article.
Symptoms
In diesem Artikel wird Goav-Skript verwendet. Verwenden Sie diesen Artikel Avamar: GoAV-Tool für weitere Informationen
In diesem Szenario verfügt der Avamar-Server (av-server) über zwei vCenter:
- vcenter01.lab.com
- vcenter02.lab.com
Jedes vCenter enthält einige Proxys. In diesem Artikel wird die Proxy av-proxy-08.lab.com verwendet.
1. Stellen Sie eine Verbindung zum Avamar-Server als Administrator her und listen Sie die Proxys auf:
./goav proxy show
admin@av-server:~/>: ./goav proxy show
===========================================================
GoAv : 1.91
Avamar : 19.10
Date : 27 Dec 2024 10:02 EST
===========================================================
COMMAND : ./goav proxy show
NOTE: This is not an official tool
===========================================================
+---------------------------+------------+-------------------------------+------------------------------------------+-----------+---------------+------------------------+
| name | domainFqdn | vcenterHost | id | activated | autoDsMapping | clientVersion |
+---------------------------+------------+-------------------------------+------------------------------------------+-----------+---------------+------------------------+
| av-proxy-01.lab.com | /clients | vcenter01.lab.com | 451e50d90593232b55ead709d7c150c222c73357 | true | false | 19.10.100-166 |
| av-proxy-02.lab.com | /clients | vcenter02.lab.com | 4c521927efd418d29ea054b983aa98cdaba0164f | true | false | 19.10.100-135_HF338865 |
| av-proxy-03.lab.com | /clients | vcenter01.lab.com | bbf88da2fca1f51234b86348f02bd5530229e734 | true | false | 19.7.100-82_HF338743 |
| av-proxy-04.lab.com | /clients | vcenter01.lab.com | 22a31e18f995a442a2dc745a28ffff3ee82b627b | true | false | 19.9.100-78 |
| av-proxy-05.lab.com | /clients | vcenter01.lab.com | 90c3058d07f43532d41ea4fc82d07be6f5eecdbb | true | false | 19.10.100-166 |
| av-proxy-06.lab.com | /clients | vcenter02.lab.com | 907da738167186a952d78850c366ba6efbed578f | true | false | 19.10.100-135_HF338865 |
| av-proxy-07.lab.com | /clients | vcenter02.lab.com | f685ef4e7497eadf67e8e683898c9996ffffde11 | true | false | 19.10.100-135_HF338865 |
| av-proxy-08.lab.com | /clients | vcenter01.lab.com | 170fecda603b533247db21c1c5f536f6d2bf4c1b | true | false | 19.4.100-116 |
+---------------------------+------------+-------------------------------+------------------------------------------+-----------+---------------+------------------------+
admin@av-server:~/>:
2. Überprüfen Sie die Client-ID (cid) für die beiden vCenter:
psql -p 5555 mcdb -c 'select mgmt_client.cid, clients.descr, mgmt_client.uuid from mgmt_client, clients where mgmt_client.cid=clients.cid;'
admin@av-server:~/>: psql -p 5555 mcdb -c 'select mgmt_client.cid, clients.descr, mgmt_client.uuid from mgmt_client, clients where mgmt_client.cid=clients.cid;' cid | descr | uuid ------------------------------------------+--------------------------------------------------------------+-------------------------------------- 70556d54b3eb4831d3e1a75742b9973fc930c1ca | /vcenter01.lab.com/vcenter01.lab.com | 1e414dc1-3107-4f05-8159-5a5beaf8f9ab 1e1825c377e14943e6c0ec7921ceb4efc21a1934 | /vcenter02.lab.com/vcenter02.lab.com | 0ed1532e-13d2-41cb-b437-cdd244af42f8 (2 rows) admin@av-server:~/>:
3. Überprüfen Sie die Proxy-CID und die entsprechende vCenter-CID. Die Proxy-av-proxy-08.lab.com gehört zu vCenter vcenter01.lab.com:
psql -p 5555 mcdb -c 'select * from proxy_mgmt_mapping order by vc_cid asc ;'
admin@av-server:~/>: psql -p 5555 mcdb -c 'select * from proxy_mgmt_mapping order by vc_cid asc ;'
proxy_cid | vc_cid
------------------------------------------+------------------------------------------
4c521927efd418d29ea054b983aa98cdaba0164f | 1e1825c377e14943e6c0ec7921ceb4efc21a1934
907da738167186a952d78850c366ba6efbed578f | 1e1825c377e14943e6c0ec7921ceb4efc21a1934
f685ef4e7497eadf67e8e683898c9996ffffde11 | 1e1825c377e14943e6c0ec7921ceb4efc21a1934
170fecda603b533247db21c1c5f536f6d2bf4c1b | 70556d54b3eb4831d3e1a75742b9973fc930c1ca --> Testing this proxy
bbf88da2fca1f51234b86348f02bd5530229e734 | 70556d54b3eb4831d3e1a75742b9973fc930c1ca
451e50d90593232b55ead709d7c150c222c73357 | 70556d54b3eb4831d3e1a75742b9973fc930c1ca
22a31e18f995a442a2dc745a28ffff3ee82b627b | 70556d54b3eb4831d3e1a75742b9973fc930c1ca
90c3058d07f43532d41ea4fc82d07be6f5eecdbb | 70556d54b3eb4831d3e1a75742b9973fc930c1ca
(8 rows)
admin@av-server:~/>:
4 – Starten der Avamar Administrator-Konsole (Java-GUI)
Hinweis: Dieses Verhalten kann nicht mithilfe der Avamar-Benutzeroberfläche (AUI) reproduziert werden, da sie keine Deaktivierung des Proxys zulässt.
5. Wechseln Sie zur Registerkarte >Policy > Clients Bearbeiten Sie den Proxy av-proxy-08.
- Clear: Aktiviert, Client-initiierte Backups zulassen, Dateiauswahl bei Client-initiierten Backups zulassen
- Prüfen: Alle Backups deaktivieren
6. Klicken Sie auf OK und kehren Sie zur Befehlszeilenschnittstelle (CLI) zurück.
7. Überprüfen Sie, ob der Proxy av-proxy-08 die vc_cid von "70556d54b3eb4831d3e1a75742b9973fc930c1ca" auf "1e1825c377e14943e6c0ec7921ceb4efc21a1934" umstellt.
psql -p 5555 mcdb -c 'select * from proxy_mgmt_mapping order by vc_cid asc ;'
admin@av-server:~/>: psql -p 5555 mcdb -c 'select * from proxy_mgmt_mapping order by vc_cid asc ;'
proxy_cid | vc_cid
------------------------------------------+------------------------------------------
170fecda603b533247db21c1c5f536f6d2bf4c1b | 1e1825c377e14943e6c0ec7921ceb4efc21a1934 --> Proxy vc_cid changed after de-activate it
907da738167186a952d78850c366ba6efbed578f | 1e1825c377e14943e6c0ec7921ceb4efc21a1934
f685ef4e7497eadf67e8e683898c9996ffffde11 | 1e1825c377e14943e6c0ec7921ceb4efc21a1934
4c521927efd418d29ea054b983aa98cdaba0164f | 1e1825c377e14943e6c0ec7921ceb4efc21a1934
bbf88da2fca1f51234b86348f02bd5530229e734 | 70556d54b3eb4831d3e1a75742b9973fc930c1ca
22a31e18f995a442a2dc745a28ffff3ee82b627b | 70556d54b3eb4831d3e1a75742b9973fc930c1ca
90c3058d07f43532d41ea4fc82d07be6f5eecdbb | 70556d54b3eb4831d3e1a75742b9973fc930c1ca
451e50d90593232b55ead709d7c150c222c73357 | 70556d54b3eb4831d3e1a75742b9973fc930c1ca
(8 rows)
admin@av-server:~/>:
8 - Melden Sie sich bei av-proxy-08 als Admin an und wechseln Sie zum root
9 - Registrieren Sie den Proxy erneut av-proxy-08:
./initproxyappliance.sh --start
Beispiel:
av-proxy-08:/usr/local/avamarclient/etc # ./initproxyappliance.sh --start
=== Client Registration and Activation ===
This script will register and activate the client with the Administrator server.
Enter the Administrator server address (DNS text name or numeric IP address, DNS name preferred): 192.168.1.110
Enter the Avamar server domain [/clients]:
avagent.d Info: Stopping Avamar Client Agent (avagent)...
avagent.d Info: Client Agent stopped.
avagent Info <5008>: Logging to /usr/local/avamarclient/var/avagent.log
avagent Error <7531>: Unable to register /clients/av-proxy-08 with Administrator 192.168.1.110:28001
'vCenter id(s) changed from [1e1825c377e14943e6c0ec7921ceb4efc21a1934] to [70556d54b3eb4831d3e1a75742b9973fc930c1ca]' (203)
avagent.d Info: Client activation error.
avagent Info <5008>: Logging to /usr/local/avamarclient/var/avagent.log
avagent Info <5417>: daemonized as process id 2410
avagent.d Info: Client Agent started.
Registration Failed.
Updating rpms from /extra...
Mounting CDROM...
mount: /mnt/cdrom: no medium found on /dev/sr0.
Updating rpms from /mnt/cdrom...
Public key[/mnt/cdrom/avpkgkey.pub] not exist
Verify the list of gpg public keys in RPM DB
----------------
gpg-pubkey-39db7c82-5847eb1f --> gpg(SuSE Package Signing Key <build@suse.de>)
gpg-pubkey-50a3dd1c-50f35137 --> gpg(SuSE Package Signing Key (reserve key) <build@suse.de>)
gpg-pubkey-b37b98a9-4be01a1a --> gpg(SUSE PTF Signing Key <support@suse.com>)
gpg-pubkey-7c601e3e-5d26445f --> gpg(DellEMC Avamar (https://support.emc.com) <avamar.certificate.support@emc.com>)
gpg-pubkey-cbf00d5c-54de52e3 --> gpg(RSA Security LLC - SA RPM Signer (2015 key for SA) <RSASupport@emc.com>)
gpg-pubkey-ec551f03-53619141 --> gpg(Oracle OSS group (Open Source Software group) <build@oss.oracle.com>)
----------------
Patching OS...
No security patch found on /mnt/cdrom
Checking if this script has been updated...
Nope.
av-proxy-08:/usr/local/avamarclient/etc #
10 – Der erneute Registrierungsprozess ist mit dem folgenden Fehler fehlgeschlagen:
avagent Error <7531>: Unable to register /clients/av-proxy-08 with Administrator 192.168.1.110:28001
'vCenter id(s) changed from [1e1825c377e14943e6c0ec7921ceb4efc21a1934] to [70556d54b3eb4831d3e1a75742b9973fc930c1ca]' (203)
11. Gehen Sie zurück zur Konsole Administration >Account Management, wählen Sie den Proxy av-proxy-08 aus und löschen Sie ihn.
12 - Gehen Sie nach dem Löschen zum Proxy av-proxy-08 und registrieren Sie sich erneut:
./initproxyappliance.sh --start
Beispiel:
av-proxy-08:/usr/local/avamarclient/etc # ./initproxyappliance.sh --start Please press a key now if you want to re-register this proxy with Avamar Administrator. Continuing in 10 seconds... Please press a key now if you want to re-register this proxy with Avamar Administrator. Continuing in 9 seconds... === Client Registration and Activation === This script will register and activate the client with the Administrator server. Enter the Administrator server address (DNS text name or numeric IP address, DNS name preferred): 192.168.1.110 Enter the Avamar server domain [/clients]: avagent.d Info: Stopping Avamar Client Agent (avagent)... avagent.d Info: Client Agent stopped. avagent Info <5008>: Logging to /usr/local/avamarclient/var/avagent.log avagent.d Info: Client activated successfully. avagent Info <5008>: Logging to /usr/local/avamarclient/var/avagent.log avagent Info <5417>: daemonized as process id 2746 avagent.d Info: Client Agent started. Registration Complete. Initialize Avamar Services, Please wait... Do you want this proxy to be managed by PDM(Proxy Deploy Manager) in AVE [192.168.1.110][Y/N]?N av-proxy-08:/usr/local/avamarclient/etc #
13 – Die Registrierung wurde erfolgreich abgeschlossen.
14 – Der Avamar-Server erstellt eine neue CID für den Proxy av-proxy-08 und legt die richtige vc_id fest:
psql -p 5555 mcdb -c 'select * from proxy_mgmt_mapping order by vc_cid asc ;'
admin@av-server:~/>: psql -p 5555 mcdb -c 'select * from proxy_mgmt_mapping order by vc_cid asc ;'
proxy_cid | vc_cid
------------------------------------------+------------------------------------------
4c521927efd418d29ea054b983aa98cdaba0164f | 1e1825c377e14943e6c0ec7921ceb4efc21a1934
907da738167186a952d78850c366ba6efbed578f | 1e1825c377e14943e6c0ec7921ceb4efc21a1934
f685ef4e7497eadf67e8e683898c9996ffffde11 | 1e1825c377e14943e6c0ec7921ceb4efc21a1934
bbf88da2fca1f51234b86348f02bd5530229e734 | 70556d54b3eb4831d3e1a75742b9973fc930c1ca
0bf1203540d3136125f44c102556c1d201c22d25 | 70556d54b3eb4831d3e1a75742b9973fc930c1ca --> this is the proxy av-proxy-08
451e50d90593232b55ead709d7c150c222c73357 | 70556d54b3eb4831d3e1a75742b9973fc930c1ca
22a31e18f995a442a2dc745a28ffff3ee82b627b | 70556d54b3eb4831d3e1a75742b9973fc930c1ca
90c3058d07f43532d41ea4fc82d07be6f5eecdbb | 70556d54b3eb4831d3e1a75742b9973fc930c1ca
(8 rows)
admin@av-server:~/>:
./goav proxy show
admin@av-server:~/>: ./goav proxy show
===========================================================
GoAv : 1.91
Avamar : 19.10
Date : 27 Dec 2024 10:25 EST
===========================================================
COMMAND : ./goav proxy show
NOTE: This is not an official tool
===========================================================
+---------------------------+------------+-------------------------------+------------------------------------------+-----------+---------------+------------------------+
| name | domainFqdn | vcenterHost | id | activated | autoDsMapping | clientVersion |
+---------------------------+------------+-------------------------------+------------------------------------------+-----------+---------------+------------------------+
| av-proxy-01.lab.com | /clients | vcenter01.lab.com | 451e50d90593232b55ead709d7c150c222c73357 | true | false | 19.10.100-166 |
| av-proxy-02.lab.com | /clients | vcenter02.lab.com | 4c521927efd418d29ea054b983aa98cdaba0164f | true | false | 19.10.100-135_HF338865 |
| av-proxy-03.lab.com | /clients | vcenter01.lab.com | bbf88da2fca1f51234b86348f02bd5530229e734 | true | false | 19.7.100-82_HF338743 |
| av-proxy-04.lab.com | /clients | vcenter01.lab.com | 22a31e18f995a442a2dc745a28ffff3ee82b627b | true | false | 19.9.100-78 |
| av-proxy-05.lab.com | /clients | vcenter01.lab.com | 90c3058d07f43532d41ea4fc82d07be6f5eecdbb | true | false | 19.10.100-166 |
| av-proxy-06.lab.com | /clients | vcenter02.lab.com | 907da738167186a952d78850c366ba6efbed578f | true | false | 19.10.100-135_HF338865 |
| av-proxy-08.lab.com | /clients | vcenter01.lab.com | 0bf1203540d3136125f44c102556c1d201c22d25 | true | false | 19.4.100-116 |
| av-proxy-07.lab.com | /clients | vcenter02.lab.com | f685ef4e7497eadf67e8e683898c9996ffffde11 | true | false | 19.10.100-135_HF338865 |
+---------------------------+------------+-------------------------------+------------------------------------------+-----------+---------------+------------------------+
admin@av-server:~/>:Cause
Obwohl dies ungewöhnlich ist, repariert oder aktualisiert das Engineering die Avamar Administrator-Konsole (Java-GUI) nicht mehr.
Resolution
Deaktivieren Sie den Proxy unter keinen Umständen über die Avamar Administrator-Konsole. Es wird empfohlen, AUI so weit wie möglich zu verwenden.
Affected Products
Avamar, Avamar Client for VMware, Avamar ServerArticle Properties
Article Number: 000265232
Article Type: Solution
Last Modified: 02 Dec 2025
Version: 4
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.