Backup doesn't do Catalog
I started this under another thread about where the log says everything was fine but the email says it failed. The reason is that it isn't cataloging after the backup. There are no errors in the log it just isn't cataloging. The email knows it.
What isn't it cataloging? Even when I go in to the catalog view on the vault and tell it to Catalog Now it doesn't do anything. Runs for 2 seconds and that is it. I have to change the view to archive view and refresh. The go back to catalog view and catalog now. Then it actually re-catalogs.
It won't, however, catalog after a backup and it won't create the xml file for the backup. The two have to be related. Any ideas? Since it won't catalog the retention rules don't implement and as a result the drive is filling up.
Hello Jim,
First, lets separate the concepts of catalogs the XML file meta-data. These are two completely different things used for different purposes in the product.
The catalog database is kept in specific folders (different folders depending on vault) as described here. The catalog data is used exclusively for the Data view and related operations like searching.
The XML file is archive meta-data used for personal and unmanaged vaults that is kept in the same folder as the backup files. This file is used to track and display backups in our GUI.
There is one XML file per archive, with the same name as the archive. This file contains, along with a lot of other things, a list of all the backup files that belong to this archive. For example: you configure a backup task for a machine to a local personal vault, destination "F:\Backups", the archive is called "Machine_Archive(1)" and you run 10 full backups.
As a result, you will have 10 backup files in the folder and one XML file called Machine_Archive(1).xml. No other XML files will be created in this folder unless you change the name of the archive in your plan settings or point other backup plans into this same folder.
This XML file is very important and is one of the first things created when a backup to an empty folder starts. In fact, if this file cannot be created, the backup will fail. Once the backup is finished successfully, the XML file is updated: information about the just-completed backup is added to it. Most other operations use this file to recognize and then act on TIB files. For example, retention rules track creation dates and number of backups through this file.
With this in mind, it is very probable that something is indeed happening to the XML files in your environment. However, the description does not provide enough details to say anything specific. For example, you say that " it won't create the xml file for the backup", but as you can see from the information above, it's not the way our process works anyway. And if the XML file for the entire archive cannot be created, your backups would fail. Could you clarify what exactly is happening?