UNSOLVED
NW 7.6 - VCB *FULL* Backups
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)
Hmm the documentation certainly does suggest that it automatically does not backup the system32 directory - I had assumed there was a sensible reason for this (like it backed up the System State separately). If not it kind of puts a nail if the coffin of VCB backups... ?
EDIT: re-reading the documentation it does sound like the system32 directory is only excluded if you use the VCB Directive. However I take your point about not having a system state being problematic for DC's.
cmartinjr
40 Posts
379
1
Posted October 12th, 2010 14:00
Somebody please correct me if I'm wrong, but I don't think the ALLVMFS includes system state data. We ran into this issue with 7.5.x when we were needing to restore active directory info and found it out the hard way. Needless to say we use *FULL* now..