NW 7.6 seems to give an error on *FULL* VCB backup savesets if the client contains non-ASCII characters as detailed in issue NW105265.

The resolution is to revert back to ALLVMFS backups, which seems quite a step back in terms of quick recovery (given ALLVMFS backups are essentially just OS level).

Has anyone else run into this before and were there any clever workarounds to maintain *FULL* backups?

For me it seems quite dangerous to have *FULL* selected as presumably you can never predict when a non-ASCII character filename may find it's way onto a client volume, and when it does you silently lose your ability to have browsable save sets (ok - it mentions it in the log, but the backups are still "successful"), and the incremental instances of these backups will switch to full (which admittedly may be more noticeable)