Following error can be seen when you edit Backup schedule.
Error in method invocation module ‘util.Messages’ has no attribute ‘ScheduleLocationDoesNotExist’
Backup now (Immediate backup) fails with error. “SMB location is invalid”
Following lines can be seen in applmgmt.log (/var/log/vmware/applmgmt/)
2019-06-07T22:12:28.673 [15209]ERROR:backupRestoreAPI:Failed to mount the cifs share //ad.gsslabs.org/ at /storage/remote/backup/cifs/fs.labs.org/h3CYi0qm/g5dWY4YQ; Err: rc=32, stdOut:, stdErr: mount error(112): Host is down Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) 2019-06-07T22:12:28.673 [15209]ERROR:backupRestoreAPI:Couldn't mount the cifs share //ad.gsslabs.org/ at /storage/remote/backup/cifs/fs.labs.org/h3CYi0qm/g5dWY4YQ 2019-06-07T22:12:28.689 [15209]ERROR:vmware.appliance.vapi.impl:pint.Error('com.vmware.applmgmt.err_invalid_remote_loc', '%(0)s location is invalid.', **{'args': LocationType(string='SMB')})
This issue happens when SMB1 is disabled on File Server OR blocked in network. If you are using windows as file server then run following PowerShell to see current status of SMB version 1 & 2.
Get-SmbServerConfiguration |select EnableSMB1Protocol, EnableSMB2Protocol
Typical Output
Get-SmbServerConfiguration |select EnableSMB1Protocol, EnableSMB2Protocol EnableSMB1Protocol EnableSMB2Protocol ------------------ ------------------ False True
Enabling SMB1 version may help to fix this issue.
Set-SmbServerConfiguration -EnableSMB1Protocol $true
Typical Output
Confirm, Are you sure you want to perform this action? Performing operation 'Modify' on Target 'SMB Server Configuration'. [Y] Yes [A] Yes to All [N] No [L] No to All [S] Suspend [?] Help (default is "Y"): Y
Please note, if SMB1 is disabled deliberately due to security concern as it considered weaker protocol compare to SMB2/3 then use alternate protocol (HTTP, FTP, NFS..ETC) to take vCenter backup via VAMI.