v6 synthetic full and template issues.

[ashleyw]

Hi,

We had a couple of issues with our v6 backups over the weekend and noticed a few quirks;

* The realtime stats option under v5 used to previously allow us to look at previous runs of the job - which was particularly useful when jobs would first fail and then go through on the retry. I see under V6 we only see the current or last run status on the jobs. Is this by design?

* When we look at the job report, it shows "VMware Backup job: jobname (Full)" for the full report but there is nothing to distinguish between a normal full and a synthetic full which makes it difficult to tell exactly what sort of backup went through. Can the wording synthetic full be added after the jobname on a synthetic full cycle?

* We had all our jobs set to do synthetic fulls on a Friday night. Most of them failed the first time with a message
"CompileFIB failedv Client error: Cannot allocate memory for an array. Array size: 2097152"
We were running our 2x 2 thread proxies on 2gb ram each - we have now increased the ram on each proxy to 4gb in the hope this message will go away (we used to get similar errors on v5 when memory was insufficient during synthetic fulls). Are there any recommendations/known issues here?

* Problems with backups of templates. We have a job for our templates - daily incremental etc. We saw messages from the realtime summary for the job saying "VM xxxx is outdated and will be deleted", then if we look at the details of the template we see a message "Skipping task because backup already exists for this template". So we are left in a position whereby if we look at the templates backup file,there is nothing in it - which is unfortunate! This looks like a bug to me. Is the best way to work around this to create a job specifically for the templates that is simply a full backup job once per week?

thanks!

[Gostev]

Hi,

1. Use cursor keys to go between the sessions.
2. This is not really specific to v6, but I will note your request.
3, 4. Please open a support case to investigate.

Thanks.

[ashleyw]

thanks - that's great.
* The arrow keys work fine, but couldn't the UI be modified to just provide a button for previous/next as the arrow keys aren't obvious at all from within the realtime stats page.
* On our templates job, we just had a look at the exclusions and see the default is to exclude templates from incremental backup - so it must have been this that was causing issues with this job during our full synthetic backup on Friday. I'll monitor what happens during the week and if we hit issues, then we'll raise with the support team.

thanks again for your very fast response!