Date: Feb 11
Product & Version: SmartDisk 1.2.1
OS Version: Any
Module & Version: N/A
Application version: N/A
SmartDisk's diskmanager trace directory suddenly has many trace files, potentially filling the disk. On analysis the following errors are in the deduplicator trace files;
0 FILESYS -559 1298281208875338 Failed to open file '\\?\D:\Staging\diskmanager\data\0e05000086545e4d81317318600b0000a2523200'
On checking it is found that these files do not exist.
Check system logs to see if any disk issues have occurred. A possible scenario is that a disk issue was 'fixed' by chkdsk (or fschk) by removing files from the staged volume. In this case, the backup has been lost and is not recoverable, but SmartDisk cannot be left in this state.
One solution is to un-install and re-install, this will remove all backups from SmartDisk and is not ideal.
An alternative is to locate the backup details for the missing data and retire these in NetVault Backup.
The procedure for this is:
1. Locate the filename of the missing file. In the above example, this is '0e05000086545e4d81317318600b0000a2523200'
2. Search the Disk Index files for a file that has this string/filename inside the file.
a. Locate the disk index by looking at the output from 'smartdisk config --show' which is a command that is available in the foundation/bin directory where SmartDisk is installed.
b. Study the volume information and locate the favoured location for "Disk Index".
c. In this location, the directory to search is ..\diskmanager\index\.
d. Search this directory and all subdirectories for a file that has the hex string/filename in it's contents.
3. Open the file that has the hex string inside it. You can read in plain text the job and instance numbers that created the backup.
4. Using the job number and instance number, locate the backup in NVBU and retire the backup.
Repeat the above for each file that is reported as 'failed to open file'.