08-13-2014 02:02 PM
I just got back my autoloader after sending it in to be fixed. Also during the troubleshooting I had to uninstall/reinstall 2010 BEX. I followed the instructions provided by Symantec on how to manually backup the Catalog and Data directories (e.g. shut down services and sql, copy to different location, etc.). However, while all the tapes (100+) show up in the correct Media Sets when viewed on the Media tab, all the tapes in the autoloader are listed as "Discarded Media". I've tried repairing the dB using BEUtility.exe to no avail. I've also simply dragged each tape in the autoloader to the correct Media Set - which seems to work but now I have multiple entries for the same tape within the Media Sets.
What can I do to fully restore these catalogs and db?
08-13-2014 02:42 PM
has a inventory and catalog been run on these tapes?
08-13-2014 06:39 PM
08-14-2014 06:58 AM
An inventory has been run. But not a catalog. Wasn't the backed up dB suppose to contain all the tape catalogs?
08-14-2014 08:10 AM
08-14-2014 08:26 AM
Ok, but when I reinstalled BEX (to be more precise) I replaced both the Data and the Catalog directories with the versions I backed up from the initial installation. Shouldn't the catalogs have been contained there?
08-14-2014 08:36 AM
08-14-2014 10:31 AM
Yes, I did restart both the BE services as well as the SQL instance for BEX.
I have not deleted the media.
08-14-2014 06:46 PM
What makes you think that the catalogs are gone?
08-15-2014 05:56 AM
They are not gone but they're obviously corrupt in some way. Previously utilized media should be recognized correctly. Why else would you be suggesting to catalog the media unless the existing catalogs are not optimal?
Again, what I'm trying to accomplish here is to reinstall BEX and bring all my jobs, lists and catalogs back from 10 years of continuous backups.
08-15-2014 08:15 AM
08-18-2014 07:55 AM
My apologies. I thought it was clear I had backed up my Catalog and Data directories in my first post but perhaps not.
I believe the Catalogs (or dB) is corrupt because all of the media loaded is marked at Discarded Media within the autoloader - but within the Media Catalogs, the same tape is listed as being in the correct Media Group. How is it a tape can be in two places with out some data being corrupt?
08-18-2014 08:13 AM
08-18-2014 08:31 AM
Thanks. I did try to repair the BEDB using the BEutility.exe to no avail. Is there another way to try and resolve this corruption or is that my only option?
08-18-2014 08:37 AM
08-18-2014 11:27 AM
all the tapes in the autoloader are listed as "Discarded Media".
I am assuming that "discarded media" is a media set that you have created? I am not aware of a factory media set called "discarded media".
If you ignore the tapes in the "discarded media" set, does everything else look OK?
BE can appear to show two of the same tape as BE doesn't require the bar codes to be unique. Therefore, you may not have anything corrupt, just something confusing. The "media ID" is what is used to keep things uniquely identified in the database. If you compare two tapes in the UI with the same bar code, do they have the same media ID?
08-27-2014 10:23 AM
Larry,
I did not create the "Discarded Media" group - it just appeared.
Everything does look ok (all jobs are listed, user defined media sets are there and populated with the correct tapes).
All my barcodes are unique and the tapes with the same name (barcode number) have the same media ID.
I was slow in responding because I had to remove the autoloader from the server to trouble shoot some issues there - it's been sent back to a repair service.
In the meantime I've tried upgrading my BEX 2010 build 2896 to R3 (same server, same credentials). I've applied all the Live Update fixes and have run BEMIG.exe. However, I'm getting hung up on starting the Backup Exec Server Service. From the Windows Application Log...
"The Backup Exec Server Service did not start. An internal error (1627652097) occurred in object -1."
I cannot find any reference to this particular error. Any advice?
08-27-2014 12:44 PM
Working through the problem a bit more and I've come to the following two errors in the Windows Application log.
=================
Windows Application log notes:
The Backup Exec Server Service detected a schema version mismatch.
The Backup Exec Server Service did not start. An internal error (-536813108) occurred in object 1.
=================
I've looked through about 20 forum notes and tech articles, none of which solved the issue.
08-27-2014 02:15 PM
Finally found a tech note that helped.
Using BEMIG to manually upgrade BEDB from a previous version;
http://www.symantec.com/business/support/index?page=content&id=TECH50537
I also tried extensive db repair and cleanup with;
http://www.symantec.com/business/support/index?page=content&id=TECH67239
All the steps were successful except the Consistency Check.
Repair (ok) Rebuild Indices (ok) Compact (ok) Age (ok) Check Consistency (failed)
Since the autoloader has been sent away I can't really do much more for now.