![]() ![]() ![]() Please try this command again later.ĮRROR - FLOW-11008: Operation failed: Backup is already in use. ABR-182313 Local backup usage size is duplicated after reconnecting a locally attached storage (LAS) to a new Agent for VMware (Virtual Appliance). 15:39:52,214 INFO - Backup backup_job_name is already in use. ABR-183764 Local backup usage is not updated for all virtual machine backups after deleting and re-adding a network location. For example, jobs that show 'success' in the 'backups' pane of VSC but still show 'running' in the 'recent tasks' pane of vCenter are unrelated to this issue.Įxamination of the server logs ' smvi\server\log\server.log' (typically residing in folder C:\Program Files\NetApp\Virtual Storage Console\SMVI\server\log) shows one of the following errors: This article only describes how to recover from a locked or hung backup or restore job with VSC when evidence of locking issues are found. If the Error messages below are not seen and there is no evidence of a stuck lock, see KB VSC/SMVI jobs remain in a 'running' or 'failed' state and cannot be edited using the GUI.Īlso, this article does not deal with 'stale' VMware vSphere tasks or issues with the vSphere client as that is outside of the scope of the VSC product. This issue affects only a subset of jobs that are 'stuck' with a 'Running' status in the VSC GUI. The procedure described in this article applies to VSC 4.x and above Host Client. This article describes the process on how to recover from a locked or hung backup or restore job in VSC for VMware. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |