KB labels


Ticket Product Version

Ticket Category

Ticket Assignee


Hot Fixes

Published Fixes
Your Arcserve Support User Profile
First Name:
Last Name:
email:
Phone:
Company:*
Customer Type:
Language:

Country:
Region:

Time zone:
Follow

arcserve-KB : Failed to generate catalog. This is error is seen when arcserve D2D catalog job fails.

Last Update: 2016-11-23 15:18:57 UTC

Error Message:

Catalog job would fail with the following error message,
Failed to generate catalog file for volume C:.
Failed to generate catalog.


Image-xxxxxxxx-xxxxxx.log
Image log would have more information about the specific error code like 104, 109.

Description:

ARCserve D2D File System Catalog job would fail with the following error message,
Failed to generate catalog file for volume C:.
Failed to generate catalog.

In ARCserve D2D r16.5 the File System Catalog Generation is disabled by default. With this feature you can choose not to generate a catalog file with every backup, and still be able to do a file level restore. For more details refer,

What is Catalog Less Backup in CA ARCserve D2D r16.5? How to enable\disable File System Catalog? 
https://arcserve.zendesk.com/hc/en-us/articles/202770845

Solution:

  1. Make sure that the latest version of ARCserve D2D and latest update version is installed.
  2. Make sure the following Microsoft hotfix is applied. This hotfix is for a VSS snapshot Data Corruption issue. Symptoms, Causes and Resolution are explained in detail in the Microsoft KB. http://support.microsoft.com/kb/976329
  3. Check if there are any disk or controller related errors in the Windows Event Logs. 
    Example of an Ntfs Error. File System Structure on the disk is corrupt.
    EventID ::: 262199
    Event Log Type ::: Error
    Event Source ::: Ntfs
    The file system structure on the disk is corrupt and unusable.
    Please run the chkdsk utility on the volume D:.
  4. Run CHKDSK /R on the source volume on which the catalog generation is failing. Make sure the data corruption issues are fixed. If the disk still has data corruption, then exclude this volume from the backup and check if catalog can be generated for remaining volumes.
  5. 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 we can read data from the Recovery Points. This does not mean that there could be no corruption in the Recovery Points, as the corruption could be on specific blocks.  For steps on how to Mount a Recovery Point to a Drive letter refrer :https://arcserve.zendesk.com/hc/en-us/articles/201983349 
  6. If the backup destination is on a Windows Share. Check if there are any NTFS, Disk or Controller errors. Run CHKDSK /R on the backup destination volume.
  7. Run a full backup and check if catalog can be generated for the full backup. If full backup also fails to generate catalog, try to rename the existing backup destination folder and then try to run another full backup.
  8. If the problem continues, then the D2D logs would be required by support for analyzing this problem further . The following knowledge document provides the list of logs to be collected for analysis,
    https://arcserve.zendesk.com/hc/en-us/articles/201983549
Was this article helpful?
1 out of 1 found this helpful
Have more questions? Submit a request

Comments

  • Avatar
    Gregory Lagarde

    Warning, this hotfix does not work on a VM...