Hi syedmahdiali, 
could you please upload the image in a higher resolution. The warnings are unfortunately very difficult to identify. Is there a reason why you have configured a file to tape job and not a backup to tape job?

What data do you want to move to tape? Backup data? 

best regards, Thomas

https://1drv.ms/i/s!AnBrcABR3EYUhqJgtkHP93ksUOXoCg?e=HcHqgO

Thanks for the response.!

Its a small setup with not enough space on the backup storage, also these physical servers were not being backed up as original requirement.

The source files are volumes on the Physical Windows server with some flat files.

Hope the image file is accessible from the link above.

Hi,

Please note the following information (https://helpcenter.veeam.com/docs/backup/vsphere/file_to_tape_before_you_begin.html?ver=120):

• Make sure that files and folders that you want to back up do not contain certain Unicode symbols, including but not limited to the symbols with the following codes: U+D800 – U+DFFF, U+FFFE, U+FFFF (55296 – 57343, 65534, 65535), U+007C (124). Also the file and folder names must contain only symbols that are supported by the source file system. Files and folders with unsupported names will be skipped from processing.
• Make sure that files and folders that you want to back up are not symlinks. Backup of symlinks is not supported.
• You can back up only files and directories whose names are written in all locales in the UTF-8 encoding. If the encoding is other than UTF-8, you can back up only files and directories whose names are written in the English locale.

And also, please make sure that all files you want to move to tape are not in use by another process/application or by a user.
Please also check whether the server JSISFS1 is accessible from your VBR server via port 6210.

Did the job ever run without warnings or did you create the job again?

best regards, Thomas

Thanks for the detailed information.

Some of the sections are difficult to confirm like files should no be accessed / in use.. not sure how to guarantee that.!?

The job was recreated. as we moved to version 12 and realized its going to be requiring additional instance licenses. These jobs have worked normally before the upgrade if I am not mistaken.

The new server was prepared / downgraded and agents were downgraded too.

Additional to the points mentioned by @Thomson :

the agent generates a list of files to backup prior to the backup. If there are changes in the file system it’s possible that files from this list are not found anymore.

Thank you everyone for your time and valuable feedback on this post.!

So are we saying that Open file backup is not supported.?

Does anyone here have access to case directly, case number was shared earlier?

@JMeixner can we not have VBR build a fresh list of the files to be backed up, I remember a new job was created and not cloned or otherwise. wonder how to get to the end of this..

Wising you all a great day ahead and hope to hear back..

The list is not created at the time the job is created, but every time the job is started.
So some files cannot be found, if they are renamed or deleted within the runtime of the job.