Avamar: PDM konnte den Proxy in Version 7.3 mit dem Fehler "Error deleting proxy" nicht aktualisieren

Summary: Proxy Deploy Management (PDM) konnte den Proxy in Version 7.3 mit dem Fehler "Error deleting proxy" nicht aktualisieren.

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.
Check out other resources

Symptoms

Das PDM-Tool (Proxy Deploy Management) konnte den Avamar-Proxy nicht von der alten Version (7.2) auf die neue Version (7.3) aktualisieren, wobei der folgende Fehlerbericht in der Konsole angezeigt wird.

Error deleting proxy
Fehler in der PDM-Konsole

 

Cause

Der Fehler kann im Bereitstellungsmanagementprotokoll gefunden werden, was darauf hinweist, dass die Proxyfestplatten über mehrere Datenspeicher hinweg dieses Problem verursacht haben.

/usr/local/avamar/var/log/vcs/deploymentmanager.log

2017-02-03T05:57:24.229+0530 TRACE [pool-3-thread-6][ impl.ConnectionManagerService#   releaseSession]: Releasing connection manager session: id=...1dc854f2ba11
2017-02-03T05:57:24.229+0530 TRACE [pool-3-thread-6][ impl.ConnectionManagerService# waitForVcSession]: Requesting connection manager vsphere session
2017-02-03T05:57:24.299+0530 TRACE [pool-3-thread-6][ impl.ConnectionManagerService# waitForVcSession]: Acquired vsphere session: ...03d7372986e8
2017-02-03T05:57:24.329+0530 ERROR [pool-3-thread-6][                 domain.Update#  getUpdateParams]: Unsupported configuration (proxy disks over multiple datastores)
2017-02-03T05:57:26.351+0530 TRACE [pool-3-thread-6][             util.VcConnection#            close]: Logging out of VC session
2017-02-03T05:57:26.351+0530 TRACE [pool-3-thread-6][ impl.ConnectionManagerService#   releaseSession]: Releasing connection manager session: id=...03d7372986e8
2017-02-03T05:57:26.352+0530 ERROR [pool-3-thread-6][           worker.UpdateWorker#              run]: Error updating proxy
java.lang.NullPointerException
        at com.emc.avamar.vmware.deploymanager.domain.Update.update(Update.java:68)
        at com.emc.avamar.vmware.deploymanager.worker.UpdateWorker.run(UpdateWorker.java:139)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.util.concurrent.FutureTask.run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
2017-02-03T05:57:26.352+0530 DEBUG [pool-3-thread-6][             worker.TaskWorker#teTaskDescription]: Updating task description:
2017-02-03T05:57:26.358+0530 INFO  [pool-3-thread-6][             worker.TaskWorker#    sendTaskError]: Sending fault com.emc.avamar.vmware.vcs.deploymanager.delete_proxy_fault

Beispiel für Avamar-Proxyfestplatten in verschiedenen Datenspeichern

Attached Disk  : [VMFS-Production-Tier2-12] proxydisk.vmdk
Attached Disk  : [VMFS-Production-Tier2-70] proxydisk_3.vmdk

 

Resolution

Schlagen Sie vor, den vCenter-Administrator einzubeziehen, um Storage vMotion in einen komplett anderen Datenspeicher für diese Proxy-VM durchzuführen.

 

Affected Products

Avamar

Products

Avamar, Avamar Client for VMware
Article Properties
Article Number: 000170538
Article Type: Solution
Last Modified: 18 ذو القعدة 1447
Version:  7
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.