VMware Cloud Community
AllBlack
Expert
Expert

VDR: Trouble writing to destination disk. Error -1115 (disk full)

Hey guys,

I am seeing this error in my logs

7/27/2009 9:49:34 AM: Normal backup using Backup Servers

7/27/2009 9:49:39 AM: Copying dev2

7/27/2009 9:52:34 AM: Performing full back up of disk "[data2] dev2/dev2-flat.vmdk" using "SCSI Hot-Add"

7/27/2009 10:10:30 AM: Trouble writing to destination volume, error -1115 ( disk full)

7/27/2009 10:10:50 AM: Task incomplete

7/27/2009 10:10:50 AM: Remaining: 7 files, 31.6 GB

7/27/2009 10:10:50 AM: Completed: 0 files, 18.5 GB

7/27/2009 10:10:50 AM: Performance: 1033.3 MB/minute

7/27/2009 10:10:50 AM: Duration: 00:21:17 (00:03:00 idle/loading/preparing)

When I try to backup a VM by selecting "Backup now" I get the message that backup did not start

because destination is busy. I tried unmouting and mapping it again but no go.

There is 700 Gb out of 1Tb free. Any ideas?

Please consider marking my answer as "helpful" or "correct"

Please consider marking my answer as "helpful" or "correct"
Tags (2)
0 Kudos
16 Replies
admin
Immortal
Immortal

For some reason, the VDR appliance thinks that the destination is full. Some questions

1) Is the destination a CIFS share or a vmdk? I

2) When you say that 700 Gb out of 1Tb free, does this map to what is reported in VDR Configuration/Destination/Free column?

0 Kudos
AllBlack
Expert
Expert

It is a CIFS share and the 700Gb free is reported by the VDR GUI.

Apparently this is a known bug and engineering have been investigating it

Please consider marking my answer as "helpful" or "correct"
0 Kudos
b4401023
Contributor
Contributor

Me too. . . . Smiley Sad

Best regards from Germany

0 Kudos
Asset
Contributor
Contributor

Same problem.... QNap with 6,02 Tb free and two 1115 error on a backup job of 11 vm.

Best regards

0 Kudos
RParker
Immortal
Immortal

Same problem.... QNap with 6,02 Tb free and two 1115 error on a backup job of 11 vm.

You using CIFS as well? I would try using ESX server to mount the destination rather than use the appliance directly.

So instead of adding a disk to the appliance, you add the disk via ESX, and then add a VM on that disk that you can use for your appliance. You have to do your backups again, but at least you won't get the error.

0 Kudos
AllBlack
Expert
Expert

I am using CIFS. Tried DAS, ISCSI SAN storage

Fails for both but not all the time

I have an SR open with vmware but so far no result.

I was about to try using a vmdk as destination but I would prefer CIFS

I noticed another issue with vdr. A machine that had been backed up with vdr was unable to vmotion.

Please consider marking my answer as "helpful" or "correct"
0 Kudos
pkurnaev
Contributor
Contributor

Yesterday, i've got the same issue (destination is busy). I am using vmdk.

0 Kudos
dustinn3
Contributor
Contributor

Same issue here now. I just had to delete almost all of my backups because it said they were corrupt. Then I started getting this error on two of my guests.

0 Kudos
AllBlack
Expert
Expert

VDR is not a mature product yet in my opinion Smiley Sad

I'd say open an SR with vmware, a lot of people have this problem and no solution yet.

cheers

Please consider marking my answer as "helpful" or "correct"
0 Kudos
AllBlack
Expert
Expert

Hey guys,

Problem seem to be solvable with workaround. Make sure your destination is less than a Terrabyte when using CIFS. I have created a 0.5TB one and so far so good.

Great de-dupe ratio too.

Vmware has acknowledged this a a bug and a fix will be available in U1.

Cheers

Please consider marking my answer as "helpful" or "correct"

Please consider marking my answer as "helpful" or "correct"
0 Kudos
b4401023
Contributor
Contributor

Ich bin bis einschließlich den 11/09/2009 im Urlaub. Ihre Emails werden nicht weitergeleitet. Bitte wenden Sie sich an meine Kollegen.

Vielen Dank.

Mit freundlichen Grüßen

T. Büsching

0 Kudos
dustinn3
Contributor
Contributor

Yeah what he said Smiley Wink

0 Kudos
gusverde
Contributor
Contributor

Same problem here.

I am testing VDR on a local drive, 50 GB vmdk. I did about 5 backups with no problem and then starting to get the error: The backup job did not start because its destination is busy.

The destination still has 40 GB free space. I tried restarting the VDR and still no go.

Before I started getting this error I tested the file level restore. That worked just fine, but I am wondering if that has anything to do with this error.

0 Kudos
AllBlack
Expert
Expert

Have you upgraded versions lately? There may be a datastore lock file still there.

If you haven't upgraded make sure you do so to v1.0.2. All my woes seem to have disappeared

Please consider marking my answer as "helpful" or "correct"
0 Kudos
gusverde
Contributor
Contributor

I am using 1.0.2.562. It is a fresh install I did today. Also using the latest ESX4 and vCenter. Just ran a few test backups and started having the problem.

0 Kudos
b4401023
Contributor
Contributor

Thats right.

The new Version 1.0.2.562 running great. Everything works fine....No Problems.

Hint:

If problems appeared, please rename the backup destination store, for example if you use a network share.

Afterward erverything has to work... Smiley Happy because the appliance create an new one...

Best Regrads from Germany

0 Kudos