Veeam Agent reports Success but failed

[Citylight]

I made a backup to a CIFS share with insufficient store capacity.
Round about 2GB were missing to achieve the backup job.
However, Veeam Agend reported Status: Success but the file
.vbk is to small and .vbm is empty.

I tried it again and at this time more then 5GB were missing.
This time Veeam reported Failed.


If you need further information please let me know.

[PTide]

Hi,

Round about 2GB were missing to achieve the backup job.

That's a known bug with backups to CIFS. I'm also curious how did you find out the exact amount of GBs missing, do you mean that the size of a full backup to CIFS was 2Gb smaller than the size of the backup that you did previously?

Thanks

[boatmn810]

Backup to CIFS Share dies when trying to run same job again
Removed and reconnected share / deleted all backup and re-created / same issues
States:
Retrieved less bytes from storage than expected....

Veeam Agent for Linux BETA (expires in 56 days)

Backup session on agatha.mccad.mcc.edu [0] % Status: Failed
Summary Data
Duration: 00:00:43 Processed: ---
Processing rate: --- Read: ---
Bottleneck: --- Transferred: ---
Time Action Duration
2016-07-07 14:23:32 Job started at 2016-07-07 14:23:32
2016-07-07 14:23:32 Starting backup
2016-07-07 14:23:32 Creating volume snapshot 00:00:17
2016-07-07 14:24:15 [error] Retrieved less bytes from the storage [0] than required [5246976]. Offs...
2016-07-07 14:24:15 [error] Failed to perform backup
Veeam Support - Case # 01846935 - Veeam Agent for Linux Beta

[nielsengelen]

Can you upload the logs to a fileshare system (dropbox, onedrive,...) and post them here ?

[PTide]

Also please do not open cases with support team as technical support for Beta is provided on this forum only. Official support will be available in future releases.

Thanks

[Bennon Maina]

The issue is caused by missing or corrupted backup files. It's not the end of the world, even though to resolve the issue you have to delete some of the 'unavailable' backup files.

In order to resolve this issue, please delete 'nodename.long.number.vib' restore point by doing the following:

1. Disable the job;

2. Open job's repository location and delete (or move) 'nodename.longnumber.vib' file;

3. Rescan the repository (https://helpcenter.veeam.com/docs/backu ... l?ver=95u4);

4. Remove missing restore points (https://helpcenter.veeam.com/docs/backu ... l?ver=95u4);

5. Enable job and wait for its next run to finish.

There's little you can do about the files in red that will be deleted. You will just have to rebuild your retentions as the jobs run.