To me it sounds pretty obvious;
“…but it happens every 3 schedules“
Lets say you have 1 vm @ 300GB, and your backup store is 800GB in total. The first two will backup – no problem. 3rd will fail due to lack of space, yet still remove the oldest – bringing the store usage back down to 300-ish GB. 4th will then work, and remove the 2nd. 5th will then work and remove the 3rd (faulty) one. 6th will then fail again because of lack of space - the store can’t handle 3 simultaneous backups.
And I’m not even certain that a 3 rotation backup will hold only 3 copies. AFAIK ghetto will only remove the latest backup after a fresh one completes. I.e. you would need space for a total of 4 times the vm your backing up at 3 rotations, if I’m getting it right.
Disks are cheap though. Get another terabyte disk and play it safe
Med Vänlig Hälsning
cid:image001.jpg@01CE5BA5.47E78610<http://www.linford.se/>
Daniel Jokinen
Dir: 019-15 67 43
Vxl: 019-15 67 40
Fax: 019-15 67 49
daniel.jokinen@linford.se<mailto:daniel.jokinen@linford.se>
www.linford.se<http://www.linford.se/>
cid:image002.jpg@01CE5BA5.47E78610<http://www.soliditet.se/> cid:image003.png@01CE5BA5.47E78610<http://www.rlicens.se/rlicenser/linford-communication-ab/> cid:image004.png@01CE5BA5.47E78610<http://www.dagensindustri.se/gasell>
Från: Luca_P communities-emailer@vmware.com
Skickat: den 28 maj 2013 11:38
Till: Daniel Jokinen
Ämne: New message: "Failed to clone disk: There is not enough space on the file system for the selected operation (13)"
VMware Communities<http://communities.vmware.com/index.jspa>
Failed to clone disk: There is not enough space on the file system for the selected operation (13)
created by Luca_P<http://communities.vmware.com/people/Luca_P> in ghettoVCB - View the full discussion<>