VMware vCenter Server Appliance: Error in method invocation module ‘util.Messages’ has no attribute ‘ScheduleLocationDoesNotExist’ beim Anlegen eines Backup-Zeitplans

Beim Anlegen eines Backup-Zeitplans mit SMB-Ziel wird die folgende Fehlermeldung zurückgegeben: Error in method invocation module ‘util.Messages’ has no attribute ‘ScheduleLocationDoesNotExist’.

Etwas Aussagekräftiger hätte die Fehlemeldung ausfallen können… Das Backup-Log auf der VCSA bringt uns weiter:

# cat /var/log/vmware/applmgmt/backupRestoreProgress.log
2019-04-29T10:31:09.938 [47907]INFO:vmware.appliance.vapi.auth:Authorization request for service_id: com.vmware.appliance.recovery.backup.schedules, operation_id: create
2019-04-29T10:31:09.938 [47907]DEBUG:vmware.appliance.extensions.authorization.authorization_sso:Required privileges = ['ModifyConfiguration']
2019-04-29T10:31:10.62 [47907]DEBUG:vmware.appliance.extensions.authorization.authorization_sso:User=VSPHERE.LOCAL\Administrator, groups={'vsphere.local\\Administrators', 'vsphere.local\\SystemConfiguration.BashShellAdministrators', 'vsphere.local\\ComponentManager.Administrators', 'vsphere.local\\SystemConfiguration.Administrators', 'vsphere.local\\Everyone', 'vsphere.local\\LicenseService.Administrators', 'vsphere.local\\CAAdmins', 'vsphere.local\\Users'}
2019-04-29T10:31:10.62 [47907]DEBUG:root:Validated user privileges in localstore or SSO
2019-04-29T10:31:10.62 [47907]DEBUG:vmware.vherd.transport.vapi:Only [] block []
2019-04-29T10:31:10.63 [47907]ERROR:vmware.appliance.update.update_functions:Can't read JSON file /etc/applmgmt/appliance/software_update_state.conf [Errno 2] No such file or directory: '/etc/applmgmt/appliance/software_update_state.conf'
2019-04-29T10:31:10.63 [47907]DEBUG:vmware.appliance.update.update_state:No update state file. Will create a new one
2019-04-29T10:31:10.63 [47907]ERROR:vmware.appliance.update.update_functions:Can't read JSON file /etc/applmgmt/appliance/software_update_state.conf [Errno 2] No such file or directory: '/etc/applmgmt/appliance/software_update_state.conf'
2019-04-29T10:31:10.63 [47907]DEBUG:vmware.appliance.update.update_state:Unable to fetch latest query time KeyError('latestUpdateQueryTime',)
2019-04-29T10:31:10.63 [47907]DEBUG:vmware.vherd.transport.vapi:State 'UP_TO_DATE'
2019-04-29T10:31:10.64 [47907]DEBUG:vmware.appliance.backup_restore.ScheduleManager:Schedule data file /storage/applmgmt/backup_restore/backup_schedule.json does not exist.
2019-04-29T10:31:10.64 [47907]DEBUG:vmware.appliance.backup_restore.schedule_impl:Validating schedule spec.
2019-04-29T10:31:10.80 [47907]ERROR:vmware.appliance.backup_restore.schedule_impl:Failed to mount the cifs share //filer/share/ at /storage/remote/backup/cifs/filer/iFdgBmPr/JIahT4mW; Err: rc=32, stdOut:, stdErr: mount error(13): Permission denied
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
.
2019-04-29T10:31:10.93 [47907]ERROR:vmware.appliance.backup_restore.schedule_impl:Failed to mount the cifs share //filer/ at /storage/remote/backup/cifs/filer/iFdgBmPr/JIahT4mW; Err: rc=32, stdOut:, stdErr: mount error(13): Permission denied
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
.
2019-04-29T10:31:10.94 [47907]ERROR:vmware.appliance.backup_restore.schedule_impl:Couldn't mount the cifs share //filer/ at /storage/remote/backup/cifs/filer/iFdgBmPr/JIahT4mW
2019-04-29T10:31:10.94 [47907]DEBUG:vmware.appliance.backup_restore.schedule_impl:
Exception:
Traceback (most recent call last):
File "/usr/lib/applmgmt/backup_restore/py/vmware/appliance/backup_restore/plugins/backupRestoreDispatchSMB.py", line 36, in validate
self.mount()
File "/usr/lib/applmgmt/backup_restore/py/vmware/appliance/backup_restore/plugins/backupRestoreMountedFS.py", line 159, in mount
(self.fsName, shareLocation, self.localMountPath))
Exception: Couldn't mount the cifs share //filer/ at /storage/remote/backup/cifs/filer/iFdgBmPr/JIahT4mW

2019-04-29T10:31:10.98 [47907]ERROR:vmware.vapi.provider.local:Error in invoking com.vmware.appliance.recovery.backup.schedules in create - module 'util.Messages' has no attribute 'ScheduleLocationDoesNotExist'
Traceback (most recent call last):
File "/usr/lib/vmware-vapi/lib/python/vapi_runtime-2.100.0-py2.py3-none-any.whl/vmware/vapi/provider/local.py", line 277, in invoke
service_id, operation_id, input_value, ctx)
File "/usr/lib/vmware-vapi/lib/python/vapi_runtime-2.100.0-py2.py3-none-any.whl/vmware/vapi/provider/local.py", line 248, in _invoke_int
method_result = iface.invoke(ctx, method_id, input_value)
File "/usr/lib/vmware-vapi/lib/python/vapi_runtime-2.100.0-py2.py3-none-any.whl/vmware/vapi/bindings/skeleton.py", line 365, in invoke
meth_output = method(**meth_args)
File "/usr/lib/applmgmt/base/py/vmware/vherd/base/thread_utils.py", line 43, in wrapper
return sync_call_from_thread(func, *args, **kw)
File "/usr/lib/applmgmt/base/py/vmware/vherd/base/thread_utils.py", line 13, in sync_call_from_thread
return threads.blockingCallFromThread(reactor, func, *args, **kw)
File "/usr/lib/python3.5/site-packages/twisted/internet/threads.py", line 122, in blockingCallFromThread
result.raiseException()
File "/usr/lib/python3.5/site-packages/twisted/python/failure.py", line 372, in raiseException
raise self.value.with_traceback(self.tb)
AttributeError: module 'util.Messages' has no attribute 'ScheduleLocationDoesNotExist'

Interessant ist folgende Zeile:

2019-04-29T10:31:10.80 [47907]ERROR:vmware.appliance.backup_restore.schedule_impl:Failed to mount the cifs share //filer/share/ at /storage/remote/backup/cifs/filer/iFdgBmPr/JIahT4mW; Err: rc=32, stdOut:, stdErr: mount error(13): Permission denied
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
.

Die Anmeldedaten für den SMB-Share wurden zurückgewiesen. In meinem Fall liegt es daran, dass der Kunde als Benutzernamen den UPN (backupuser@ad.domain.name) angegeben hatte, mount.cifs kann dies nicht eigenständig in Benutzer- und Domänenpart aufteilen.

Workaround ist, falls dies Möglich ist, nur den Benutzernamen (sAMAccountName) anzugeben oder auf ein anderes Protokoll fürs Backup (SCP, SFTP, FTPS, HTTPS) auszuweichen.

One thought on “VMware vCenter Server Appliance: Error in method invocation module ‘util.Messages’ has no attribute ‘ScheduleLocationDoesNotExist’ beim Anlegen eines Backup-Zeitplans”

  1. vCenter server has version 6.7 Update2a
    Backup from VAMI works if I have SMB1 enabled on Windows Server (SMB1 is disabled by default in Windows 8.1 and Windows 2012 Server and higher)
    Backup doesn’t work if I have SMB1 disabled and I’m using SMB2
    The following is in “applmgmt.log”
    ERROR: vmware.appliance.backup_restore.schedule_impl: Failed to mount the cifs share //ak-srv.hpedu.cz/ at /storage/remote/backup/cifs/ak-srv.hpedu.cz/mnj8BOw5/PjtqOBI7; Err: rc = 32, stdOut :, stdErr: mount error (112): Host is down

    How to check from command line mount cifs smb:
    Mount smb share
    mount -t cifs ///c$ /storage/remote/backup/cifs -o username=
    Password for @///c$: ************

    Unmount smb share
    umount ///c$

    For server in Workgroup use username only username (e.g. administrator)

Leave a Reply

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.