Issue Description Because of some reasons, we need to reinstall the Backup Server, the original backup information and License information have lost. Alarm Information None. Stop the service of the SQL Server; 2. Restart the server, and reinstall the Backup Exec.
Stop the service of the SQL server; 7. Start all the services of the Backup Exec. Root Cause The backup information and License information are saved in some certain catalog and files, while reinstalling the Backup Exec, we will delete these catalog and files while deleting the software. So we need to make backup of these information before implementing the reinstallation. If the media is not found then only data in the available media can be restored. Note 2: The same error is reported if the Catalog of Media where the backup set spanned, but next media was not provided and the backup job was cancelled for lack of tapes.
The error is reported on the last set it is cataloging, as Backup Exec thinks it spanned but cannot find the next tape media as it was never inserted. This issue is more likely to be found with Tape media. On Disk, this issue can occur as well, but only when the next media to span the set does not get created due to space filling up on the disk storage and job is cancelled. Yes, from a Disaster Recovery perspective, the Data and Catalog folder present in the BE Install Path or where they exist in case these are kept at different locations of the BE server should be backed up.
It is most helpful when a Disaster Recovery situation arises in the data center and all servers need to be restored. If a Backup Exec server is restored to its pre-disaster state, then the time to catalog the media is saved which helps allow for a faster recovery of other servers in the environment.
For this reason, a Full backup of the Data and Catalog folder is recommended every day. This is the bare minimum required to restore Backup Exec Jobs, catalog Info, settings etc. Please note that this document is a translation from English, and may have been machine-translated.
It is possible that updates have been made to the original version after this document was translated and published. Veritas does not guarantee the accuracy regarding the completeness of the translation.
You may also refer to the English Version of this knowledge base article for up-to-date information. Support Knowledge base Article: Last Published: Ratings: 7 5.
Product s : Backup Exec. What is the difference between Inventory and Catalog? What are the Contents of the Catalogs folder? Can Backup Exec Catalog Files be truncated automatically? Backup Exec Catalog terminology. What is the correct way to run a Catalog Job? Is backing up the Backup Exec Catalog Files helpful? How is it done? In an edge case there could be an old folder with a previous BE server name present. This can be the case if catalog movement from the old BE server name Folder to the new BE server name folder failed.
Backup Exec automatically adjusts the catalog entries in the Backup Exec database and also moves the catalog files to its new location i. SDR The. The XML file can be opened in a web browser or file viewer to check the backup set info. What if the Tape is encrypted using a pass phrase and is being cataloged on a new Backup Exec Server? This Alert can be seen when the pass phrase does not match what it was when the backup was taken: The encryption key required by this set key name: Key1 cannot be retrieved.
Request all media in the sequence MIS for catalog operations: If selected along with Use media based catalog , the catalog process starts from the last media in media family and then works its way backwards till the first set of first media. If this option MIS is cleared, then use media based catalog remains selected if it was selected earlier and becomes greyed out.
If the admin wants to start the catalog from a particular media, then that particular media can be selected and the catalog will then start from this media.
It will pick up the media you selected for the catalog job and then later pick up the last media in the media family for catalog operation and work its way backwards last media used by backup to first media used by backup. If request media in sequence is cleared along with use storage based catalog , then the catalog job starts cataloging from the first media or the media which was selected to start the catalog operation, then moves from lowest used media to the last media in media family.
Some important info that Backup Exec gets from Inventory Job: It helps to understand the family sequence number and which Medias are part of same media family etc. How to find the Family Sequence Number of a particular set The Family Sequence Number is the order in which the media is picked and used by Backup Exec during a backup operation. Catalog Job Failures 1.
Note the following details in the Job Log: Did the catalog job fail on several media or only on one specific media which has some inconsistency? This can be easily found by reviewing the failed catalog job. Check the places in the job log where the error is seen.
Just before this error in the Job Log, check the media which was mounted. Normally, this problem is seen when a media contains an abruptly ended backup set. It can happen that a backup job was aborted midway by ending the bengine. The errors will be received as the issue occurred during backup time, hence the error can be regarded as a message to inform the admin of an inconsistent set of Media.
Take note of the device name where the catalog was run Eg: Disk Storage in the case seen above. A chkdsk can be run to ensure the drive file system is fine, just in case any NTFS errors are seen on the disk holding the disk storage. Performing an Inventory operation on this media and rerunning the Catalog operation should resolve the problem As the error suggests, the media was not found during the catalog operation.
Note: This is the default path where Data and Catalog exist. The information about earlier sets will be lost. If Catalog files are deleted, earlier backup media will need to be recataloged to regenerate the catalog files. Backup Exec is now integrated with Veritas Information Map. Metadata from the catalogs are sent to InfoMap for IM to be able to understand the type, age etc. Veritas does not guarantee the accuracy regarding the completeness of the translation. You may also refer to the English Version of this knowledge base article for up-to-date information.
Support Knowledge base How to reinstall Backup Exec on the same server while saving settings, jobs definitions and current catalog information How to reinstall Backup Exec on the same server while saving settings, jobs definitions and current catalog information.
Article: Last Published: Ratings: 2 2. Product s : Backup Exec. Problem The information in this article applies to the following scenarios: How to reinstall Backup Exec on the same server while saving settings, job definitions and catalog information.
0コメント