There is no logic to create full backups in the new location right after the upgrade. Your jobs should continue running normally. The only reason why you might see this behavior is that your v5 backup jobs were not in successful state at the time when you decided to perform the upgrade to v6.sekellow wrote:The first job run following the upgrade created a sub-folder with the jobs's name, "Backup", and began to place the new VBM and VBK files in that location. As there were no existing backups in this new folder location, B&R performed a full backup causing a new, very large VBK file to be created and filling up the allocated storage until there was none left.
Anyway, it's good to know that you're up and running now, but I would suggest to show the job log files to your support engineer, so we could figure out why you have observed such behavior.