arcserve-KB : Failed to generate File System Catalog for arcserve D2D for Windows

Last Update: 2016-11-23 10:50:44 UTC

Error Message:

Failed to map an index block to the correct volume block. An IndexAlloc Error has occurred. Cannot locate VCN. (VCN=[virtual cluster number])

Failed to generate catalog file for Volume X: (where X: is a placeholder for drive letter)

Failed to generate catalog




CA ARCserve D2D stores the catalog files in the CA ARCserve D2D destination machine/disk under the
catalog folder. CA ARCserve D2D creates a catalog file after the backup job is complete, each catalog file has a unique session
name. The number of catalog files created depends on the recovery points configured. After the specified number of catalog
files are created, the older files are merged.

The following lines can be found in the log file "Image-20150105-032713.log"
2015-01-05 04:05:46.889 Processing File Name FILENAME parent Directory sec low = 378904 sec high = 0
2015-01-05 04:05:46.889 Processing File Name FILENAME parent Directory sec low = 378904 sec high = 0
2015-01-05 04:05:46.889 parsing FileRef low = 379347 high = 0
2015-01-05 04:05:46.920 IndexAllocError : Cannot Locate VCN 7667761
2015-01-05 04:05:46.920 TraverseIndexAllocation returns error 104
2015-01-05 04:05:46.920 TraverseIndexRoot Fails 104
2015-01-05 04:05:47.107 backup Backup Dir struct failed 104
2015-01-05 04:05:47.107 NtfsBackupVolume returns [104]
2015-01-05 04:05:47.107 BackupVolume returned 104
2015-01-05 04:05:47.107 Backup Volume Failes with error 104
2015-01-05 04:05:47.107 Leaving VMImageBackupEntry ret value 104
The following lines can be found in the log file "CAT_20150105_032530.512_2592.Log"
[2015/01/05 04:05:47:123   01   7684   9752   0X00000068] [WAR] Failed to parse catalog because some internal error. (Volume Name=[D:])
[2015/01/05 04:05:47:138   00   7684   9752   0X00000068] [ERR][CCatalogScriptReader::GenerateCatalogFile] Failed to generate catalog file for volume D:.
[2015/01/05 04:05:47:138   00   7684   9752   0Xa100001a] [ERR][CCatalogScriptReader::GenerateCatalogFile] Skip any other catalog generation because some volume's catalog failed.
[2015/01/05 04:05:47:138   00   7684   9752   0X00000068] [ERR][CCatalogScriptReader::GenerateCatalogFile] Failed to generate catalog for file system.



Because of some environmental circumstances it might happen that generating the file system catalog failed with the error above.

The root cause of this error is different but environmental.

The following steps will describe basic troubleshooting to enclose or resolve the problem:


1. Try to mount the Recovery Point to a drive letter and see if you can restore some files and folder.
This is to make sure the data can be read from the Recovery Points and to check if the Recovery Points are usable.
It does not mean that there could be no corruption in the Recovery Points, as the corruption could be on specific blocks!

   1.1 Run a full backup and check if the backup completes sucessfully

   1.2 Alternatively run the full backup to a new backup destination folder


2. For Windows Operating Systems Windows 2008 R2, Windows 2008, Windows 2003, Windows 2003 SP2, Windows 7 and Windows Vista it is mandatory to apply the following Hotfix to prevent VSS Data corruption 
when VSS Snapshot is invoked on an extented Volume. Please apply on Arcserve D2D Backup Proxy and VM Guest system backed up!

Note: a restart is required applying the Microsoft Hotfix


3. Run Chkdsk /F /R on the source volume on which the catalog generation is failing. See the error message to get the drive letter seeing this error.
If any problems detected on source volume try to fix the data corruption.

Note: please be aware that running the parameter of the chkdsk command might take a long time to proceed


4. If the backup destination is on a Windows Share. Check if there are any NTFS, Disk or Controller errors in Windows System and Application Event logs.
Run Chkdsk /F /R on the backup destination volume too 

Note: please be aware that running the parameter of the chkdsk command might take a long time to proceed


5. Remove generic VSS snapshots from the problematic server. This is the backed up server or VM Guest machine.
The following command help to determine the snapshot location and helps to delete if any orphaned snapshots are still available:

vssadmin list shadows
vssadmin delete shadows

You will find more information on how using VSS here:
   - VShadow tool
   - VSSDiagnostic
   - VSSTrace


6. An initial restart of the backed up respectively VM Guest system is a basic troubleshooting step if the above steps do not enclose the problem or find an error.
    The reboot will initialize Cache, Memory, VSS subsystem and locked drivers and system files of the server

    Note: please schedule a maintenance plan for the system as per business requirements


If this is a VMWare environment check the following steps additionally:

1. Consolidate snapshots for the VM Guest. (link for description)

2. Reset Change Block Tracking (CBT) before running a new full backup (reboot required)
    - Steps to reset CBT



More Information:


Logs and other information required to troubleshoot the problem:

- MSINFO32 or other system NFO file from backup proxy and backed up machine seeing the problem
- Activity log export with the error message
- CAT*.log files
- Image*.log files
- vssadmin command out on backup machine for parameters
  list writers
  list providers
  list shadows
  list shadowstorage
- Output of the result of chkdsk command on the volume seeing the problem


Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request