sdeath wrote:Veeam support is telling me that is as designed, using the Data Locality policy will write the increment jobs to the same extent as the full backup file until it runs out of space and will then fail the job.
DaveWatkins wrote:It also doesn't seem to automatically move existing per VM chains off an extent to free up space on it so other VM chains on that extent can continue to backup, which is again, something i expected it to do.
2016-04-07 09:28:58 :: Error: There is not enough space on the disk.
Failed to write data into file [E:\Backups\definition.erm].
--tr:Error code: 0x00000070
--tr:Failed to call DoRpc. CmdName: [FcWriteFileEx] inParam: [<InputArguments><FilePath value="E:\Backups\definition.erm" /><DesiredAccess value="1073741824" /><ShareMode value="0" /><CreationDisposition value="3" /><FlagsAndAttrs value="0" /><Offset value="0" /><BytesToWrite value="5400" /></InputArguments>].
There is not enough space on the disk.
Failed to write data into
foggy wrote:Mårten, this looks like exactly the case I was talking about. Thanks for contacting support and sharing the case ID.
Users browsing this forum: Bing [Bot] and 31 guests