![]() ![]() These are settings for one example of such Copy Job: One more interesting thing is that even though incremental file count is now more than 12, jobs don't merge old files to full. Job logs and additional incremental file dates correspond with server restarts. ![]() So we now have around 5 extra incremental files on such copy jobs that should not be there. But now we see that on every Veeam server restart (for windows updates, regular restarts or after some error) it seems that this jobs are starting and doing incrementals, no matter how may days passed from last run. I dismissed this as a one time thing after update. But right after upgrade when I enabled back those jobs I noticed that they went into execution even though less than 30 days have passed since last run. This all worked fine in last 2 major versions. We also have GFS enabled for 1 yearly backup, that should create separate independent full backup on January. ![]() This translates to a chain with one full backup and 11 monthly incrementals, with a process of merging last incremental on every job run once a month. Backup Copy jobs are typically set as forever incremental, that should run every 30 days and should keep 12 backups. We have daily Backup Jobs with different settings, that are input to our Backup Copy Jobs. So I decided to ask here for ideas.Īfter upgrading to V11 we ran into problems with scheduling backup Copy jobs. We have some V11 troubles (behavior we can't explain) and support is strugling. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |