-
- Novice
- Posts: 7
- Liked: never
- Joined: May 19, 2009 8:27 am
- Full Name: tom
- Contact:
Trying to backup large disks - Failed to parse error
Hello,
I have recently started getting the following error on a 500gb disk with the scsi ID scsi0:2. The LUN has 130gb of spare space on it. Could anyone advise me of what it could be, running out of ideas. Is the vmdk corrupt, the machine is running fine, is it lack of space on the LUN? There are 5 500gb disks in total and there are no problems with the others, however they reside on another LUN.
I have tried looking for more detailed log files however have been unable to find any on the date of the backup.
Any advice would be greatly appreciated.
Creating snapshot
Failed to perform Veeam VSS freeze: VMware tools status is "Old"
Failed to parse "#scsi0:2.fileName"
I have recently started getting the following error on a 500gb disk with the scsi ID scsi0:2. The LUN has 130gb of spare space on it. Could anyone advise me of what it could be, running out of ideas. Is the vmdk corrupt, the machine is running fine, is it lack of space on the LUN? There are 5 500gb disks in total and there are no problems with the others, however they reside on another LUN.
I have tried looking for more detailed log files however have been unable to find any on the date of the backup.
Any advice would be greatly appreciated.
Creating snapshot
Failed to perform Veeam VSS freeze: VMware tools status is "Old"
Failed to parse "#scsi0:2.fileName"
-
- Novice
- Posts: 7
- Liked: never
- Joined: May 19, 2009 8:27 am
- Full Name: tom
- Contact:
Re: Trying to backup large disks - Failed to parse error
Furthermore there are no agent logs on the server it's running on for that particular VM, it's like it's just ommited when Veeam can't parse that particular disk.
-
- Novice
- Posts: 7
- Liked: never
- Joined: May 19, 2009 8:27 am
- Full Name: tom
- Contact:
Re: Trying to backup large disks - Failed to parse error
Found the log files, nothing in there of any help, I assume the failed to parse comes from the vmx file
scsi0:2.fileName = "/vmfs/volumes/47a22a85-a59dbd18-87a9-00188b2e8a45/GE-FILESVR/GE-FILESVR_2.vmdk"
Not sure what it's unable to parse.
Error appears even when excluding that disk.
scsi0:2.fileName = "/vmfs/volumes/47a22a85-a59dbd18-87a9-00188b2e8a45/GE-FILESVR/GE-FILESVR_2.vmdk"
Not sure what it's unable to parse.
Error appears even when excluding that disk.
-
- Novice
- Posts: 7
- Liked: never
- Joined: May 19, 2009 8:27 am
- Full Name: tom
- Contact:
Re: Trying to backup large disks - Failed to parse error
The disk was not formatted, appeared as unallocated in disk management, formatted with NTFS but get the same error, maybe it needs a reboot, sadly I was hoping to take an image of it before rebooting it.
-
- Novice
- Posts: 7
- Liked: never
- Joined: May 19, 2009 8:27 am
- Full Name: tom
- Contact:
Re: Trying to backup large disks - Failed to parse error
Next attempt was to remove the entries from the vmx file, it appears veeam has issues reading commented # lines.
-
- Novice
- Posts: 7
- Liked: never
- Joined: May 19, 2009 8:27 am
- Full Name: tom
- Contact:
Re: Trying to backup large disks - Failed to parse error
After removing the commented lines from the vmx file and quickly hitting the backup button it worked fine. Odd.
Can anyone explain this behaviour?
Can anyone explain this behaviour?
-
- Chief Product Officer
- Posts: 31645
- Liked: 7139 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: Trying to backup large disks - Failed to parse error
Sounds like VMX files with commented lines are not supported?
-
- Chief Product Officer
- Posts: 31645
- Liked: 7139 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: Trying to backup large disks - Failed to parse error
Fixed in version 4.1
Who is online
Users browsing this forum: Baidu [Spider] and 42 guests