Thursday, July 18, 2024
Thinware Forums
 
ForumsForumsThinware vBacku...Thinware vBacku...DiscussionsDiscussionsCRITICAL vBackup errorCRITICAL vBackup error
Previous Previous
 
Next Next
New Post
 9/13/2017 4:28 AM
 
 Modified By AdamW  on 9/13/2017 3:12:13 AM
Hello,

On 9 September at 13:41 Thinware vBackup job failed with the error below.
Irrelevant info skipped for brevity.

Version: 4.0.1.2747 (Version 4.0, Update 1)
Process Started: 09/09/2017 14:41:26
Execution Arguments:
- Virtual Machine = guest1
- Server = host1:22
- Job Type = Backup-Image-SSH
- Backup Root = D:\
- Disk Exclusion = None
- Backups to Keep = 1
- Quiesce Guest File System = True
- Snapshot Virtual Machine Memory = False
- Create Snapshot Task Timeout = 15
- Remove Snapshot Task Timeout = 15
- Encrypt Temporary Password File = True
- Compression Level = Advanced
- Maximum Log Size = 1024
- Backup Type = Image-Full
Server Platform: VMware ESXi 6.0.0 3620759
Virtual Machine Guest OS: Microsoft Windows 7 (64-bit)
License:
- Type: Perpetual
- Status: Active
- Edition in Use: Professional
Backup Folder: D:\\guest1
Backup: 170909_144141
No existing temporary snapshots found.
Temporary Snapshot: vBackup-TMP-170909_144141
VMware Virtual Disk Manager: VMware Virtual Disk Manager - build 2248791
VMware Virtual Disk Manager response for Hard disk 1: [datastore2-SATA] guest1/guest1.vmdk:
SSL_VerifyCbHelper: Certificate verification is disabled, so connection will proceed despite the error
[NFC ERROR] NfcNet_Recv: requested 264, recevied only 0 bytes
[NFC ERROR] NfcFile_Receive: Failed to get message
[NFC ERROR] NFC_NETWORK_ERROR
Failed to convert disk: Operation completes asynchronously (0x300004650).
i Tip: Even though an SSL certificate error was encountered, certificate verification is disabled causing the error to be ignored. To correct certificate verification error(s), install a valid CA-signed certificate on your host server and install a valid CA-signed root certificate on your vBackup server.
E Unable to complete backup. Unable to verify successful transfer of virtual machine virtual disk file D:\\guest1\170909_144141\guest1.vmdk.
e Unable to remove temporary snapshot vBackup-TMP-170909_144141. Unable to retrieve snapshot ID. Error while creating 'snapshot' file. Failed to login: Operation timed out.
Temporary files successfully removed.
Backup data folder deleted in cleaning up after job failure.
Process Completed: 09/09/2017 16:17:19
Elapsed Time: 1 hour, 35 minutes and 53 seconds

This has left me with the following files on host1 (VMware ESXi, 6.0.0, 3620759):

drwxr-xr-x 1 root root 2660 Sep 12 04:20 .
drwxr-xr-t 1 root root 3780 Apr 19 09:47 ..
-rw------- 1 root root 31391404032 Sep 12 14:37 guest1-000001-delta.vmdk
-rw------- 1 root root 329 Sep 9 13:41 guest1-000001.vmdk
-rw------- 1 root root 12884901888 Apr 19 19:57 guest1-3d58c3bf.vswp
-rw------- 1 root root 20346 Sep 9 13:41 guest1-Snapshot19.vmsn
-rw-r--r-- 1 root root 131 Sep 9 13:41 guest1-aux.xml
-rw------- 1 root root 644245094400 Sep 9 13:41 guest1-flat.vmdk
-rwx------ 1 root root 398 Sep 9 13:41 guest1-vss_manifests19.zip
-rw------- 1 root root 503 Sep 2 19:25 guest1.vmdk
-rw-r--r-- 1 root root 583 Sep 9 13:41 guest1.vmsd
-rw-r--r-- 1 root root 3324 Sep 9 13:41 guest1.vmx
-rw------- 1 root root 0 Apr 19 19:57 guest1.vmx.lck
-rw-r--r-- 1 root root 3317 Sep 9 13:41 guest1.vmx~
-rw------- 1 root root 8684 Sep 9 13:42 old-guest1.nvram
-rw------- 1 root root 3855 Sep 12 04:20 old-guest1.vmxf
-rw-r--r-- 1 root root 1252233 Jun 24 14:06 vmware-1.log
-rw-r--r-- 1 root root 725229 Sep 12 12:10 vmware.log
-rw------- 1 root root 1047527424 Apr 19 19:57 vmx-guest1-1029227455-1.vswp

Questions:

1. Was it a temporary network error or some more fundamental issue?
2. Is changing:
Create Snapshot Task Timeout
Remove Snapshot Task Timeout
from 15 to 60 (minutes?) a good idea and likely to improve next backup success chances?
3. Is it possible to configure vBackup to continue backing up subsequent VMs (12 in total in my case) rather than completely terminating on failure?
4. Do my VMware files (above) look healthy and need any actions apart from deleting "vBackup-TMP-170909_144141" snapshot still sitting there?
5. After manually deleting the snapshot - would you recommend to consolidate snapshots on guest1 even though vSphere says "no" in Needs Consolidation column?

Please advise.

Thanks
Adam
Previous Previous
 
Next Next
ForumsForumsThinware vBacku...Thinware vBacku...DiscussionsDiscussionsCRITICAL vBackup errorCRITICAL vBackup error

Thinware Community
Membership Membership:
Latest New User Latest: eklipa
New Today New Today: 0
New Yesterday New Yesterday: 1
User Count Overall: 41211

People Online People Online:
Visitors Visitors: 37
Members Members: 0
Total Total: 37

Privacy Statement  |  Terms Of Use
Copyright 2007-2019 Thinware, Inc.