Backup job was modified successfully.
General ------------------------------------------
Backup job name: Media Backup
Backup job description: M:\ drive backup
Source -------------------------------------------
Backup mode: volume level backup
Included items: Media (M:)
Destination --------------------------------------
Local folder: F:\VeeamBackup\
Keep restore points for the last 1 cycles
Compression level: Optimal (recommended)
Storage optimization: Local target
Storage encryption: disabled
Guest processing ---------------------------------
Application-aware processing: [disabled]
Guest file system indexing: [disabled]
Script processing: [disabled]
Schedule -----------------------------------------
Schedule: server
On [Wednesday] at [6:30 AM]
Retry failed job 3 times
Wait before each retry attempt for: 10 minutes
Create active full backups weekly on Wednesday
All of a sudden, every time I hit Backup Now (incremental expected), a new destination folder is created with _1, then _2, then _3 appended (F:\VeeamBackup\Media Backup_1 etc) and a new full in that folder.
Right now I already have:
F:\VeeamBackup\Media Backup
F:\VeeamBackup\Media Backup_1
F:\VeeamBackup\Media Backup_2
I've deleted and recreated the job from scratch a few times. The destinations were deleted as well. Same behavior.
Any chance the original backup was mapped to the job (i.e. you've used existing backup file for seeding)? Thanks!
Hi Dima,
I am not entirely sure what you mean by "mapping" and "seeding".
So far I was able to reproduce the same behavior three times in a row. Every single time I delete the job and all backup destinations, then recreate the job from scratch.
Upon first [Backup Now] the destination folder "Media Backup" is created. The next manual [Backup Now] is supposed to create an incremental + merge inside the same folder (retention: 1 recovery point). However, a new folder Media Backup_1 is created and a new Full is performed. The next manual [Backup Now] creates Media Backup_2 and again a new Full. Then the weird behavior stops and all following [Backup Now] create incrementals + merge inside Media Backup_2. Assuming that the weirdness has stopped, I delete this job, all previous destinations and recreate the job from scratch. But the weirdness comes back again.
I have a feeling destination folder ain't cleared completely.
Can you please check backup job log under C:\ProgramData\Veeam\Endpoint\Media Backup\Job.Media_Backup.Backup.log - search for string "Checking whether file or folder" - that is the line where Veeam Agent checks target storage path for existing folders from previous jobs(folder created = job name), and enumerates leftover backup chains in them. Next few lines will clearly stand if we have found existing folder structure on the destination path, and thus creating a new folder with _N nearby, to avoid conflicts. If you are 100% sure that destination path is empty, but log says we found something - that might be a bug and is worth investigation with support team.
Remember, new job = new job ID, even if name is the same. If target folder with said name exists, we will create _N not to screw up with existing data.
Thanks for the follow up. After numerous reproductions of the issue I gave up with troubleshooting and I ended up deleting the job again, deleting all destination folders (_n included), rebooting the server, and then recreating the job same as before. The problem went away. So far so good.
That being said, I will check the logs as per your suggestion and report back if I find anything unusual. Thanks!
Update:
[03.10.2020 15:32:46] <01> Info [BOX] [FC] Checking whether file or folder F:\VeeamBackup\ exists.
[03.10.2020 15:32:46] <01> Info [Repository] Creating backup dir 'Media Backup', don't use existing folder if exists
[03.10.2020 15:32:46] <01> Info [BOX] [FC] Checking whether file or folder F:\VeeamBackup\Media Backup exists.
[03.10.2020 15:32:46] <01> Info [BOX] [FC] Checking whether file or folder F:\VeeamBackup\Media Backup_1 exists.
[03.10.2020 15:32:46] <01> Info [BOX] [FC] Checking whether file or folder F:\VeeamBackup\Media Backup_2 exists.
[03.10.2020 15:32:46] <01> Info [BOX] [FC] Creating directory 'F:\VeeamBackup\Media Backup_2'
I found the entries that you mentioned. But I also wanted to bring some more clarity. The destination folder in question does exist when the new Incremental or Active Full is initiated manually.
But the expected behavior is reusing the destination and continue placing the backup chain in the existing destination.
For example I created a full in the "Media Backup" destination. Once I launch [Backup Now], I expect to see an incremental in the same "Media Backup" folder. Instead, I get Media Backup_1 created and a new full started. As if the Agent has forgotten it's ties to previous destination and started treating it as a foreign folder. So therefore it creates Media Backup_1 and starts creating a new chain.
If backup job wasn't re-created in your last case example, than it does seem abnormal. Backup Job shall use same folder for Active Fulls and incremental "Backup now" runs and not generate additional folders. However if job id changes(delete job, create with same name, target same destination with backup chain from old job), new folder _N is expected to come, with all following incremental runs and active fulls sitting in it.
We could not reproduce the case in the labs, so it must be something specific to your configuration. Feel free to pop a ticket from agent UI and share its ID here.