Backup Exec 2010 R3 Catalog Error
Contents |
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers backup exec 2010 r3 sp2 Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español backup exec 2010 r3 admin guide USA Site: Veritas Veritas PartnerNet Catalog job fails with error: "0xe0000900 The requested media is not listed in the media
Upgrade Backup Exec 2010 R3 To 2012
index and could not be mounted." Article:000030280 Publish: Article URL:http://www.veritas.com/docs/000030280 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last
Backup Exec 2010 R3 Deduplication
Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem WARNING: DO NOT follow these steps for Backup Exec 2012, 2014, 15 or later versions. As Data Lifecycle Management (DLM) depends on the catalog content this document is only for versions of symantec backup exec 2010 r3 server suite Backup Exec that do not use DLM. When running a catalog, the following error is returned: "0xe0000900 - The requested media is not listed in the media index and could not be mounted. To add the media's catalog information to the disk-based catalogs, run an inventory operation on the media and resubmit the catalog operation." Error Message 0xe0000900 - The requested media is not listed in the media index and could not be mounted. To add the media's catalog information to the disk-based catalogs, run an inventory operation on the media and resubmit the catalog operation. UMI code: V-79-57344-2304 Cause This issue could be due to a number of problems: corrupt catalogs in the Catalogs folder, catalogs/tapes overwritten, or bad tapes. Solution Run an inventory of the device and try the catalog job again. If the issue still persists, then follow the steps below. If the tape is salvageable and the catalogs are still intact, perform the following steps to resolve this issue:1. Open Windows Services applet Start>Run>services.msc, and stop all Backup Exec services.2. Rename the C:\Program Files\VERITAS\Backup Exec\NT\Catalogs folder to Catalogs_old, and recreate a new Catalogs folder. or C:\Program Files\Symantec\Backup
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom
Backup Exec 2010 R3 Download
Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français backup exec 2010 r3 download iso Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet An alert 'ODBC access error' is observed backup exec 2010 r3 sp1 download every time the Backup Exec services start and the restore selections are not complete. Article:000040371 Publish: Article URL:http://www.veritas.com/docs/000040371 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas https://www.veritas.com/support/en_US/article.TECH44676 Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem Every time Backup Exec (BE) services start, the following Errors are observed in the Alerts tab. (Figure 1). In addition, https://www.veritas.com/support/en_US/article.TECH75279 the restore selections may not be able to be browsed or may not be displayed at all when trying to create a new restore job. Error Message ODBC access error. Possible lost connection to database or unssuccessful access to catalog index in the database Figure 1: Cause This can occur due to connection issues to the Backup Exec database or corrupt catalogs in the Catalog folder. It can also occur after an upgrade of Backup Exec if the catalogs have not been upgraded completely from the past version. Solution 1. Backup Exec Database (BEDD) is hosted on an invalid SQL Instance. Solution: First make sure the SQL instance being used for the BEDB is a valid Instance. This by default is SQL Express but could be a full version of SQL. If the instance is a SQL MSDE 2000 instance that was not upgraded to SQL Express, this is the problem. Install another instance with SQL Express installer. Located in the BE install files WINNT\Install\SQLExpress\ Then use BEUtility to move BEDB to the SQL Express instance, Open BEUtility,Select A
account only takes a few minutes. Join Now i am getting this error when running an inventory and catalog on backup exec 2014 The requested media is not listed in the media index and could not be mounted. To add the media's catalog information to https://community.spiceworks.com/topic/719915-backup-exec-2014-inventory-and-catalog-error the disk-based catalogs, run an inventory operation on the media and resubmit the Catalog operation. I have catalog each tape individually and only 1 of the 7 tapes on the media failed given the error messages as above. i have associated https://www.experts-exchange.com/questions/27546621/Backup-Exec-Will-Not-Catalog-External-Drive-Physical-Volume-Library-Drive-Not-Found.html the media with the retired media set that keeps failing, deleted it and then re-inventory the robotic library. Although at a point it appeared to have solved the problem, it still failed with the error message above. Reply Subscribe View Best Answer backup exec RELATED TOPICS: Introducing Backup Exec 2014 Backup Exec 2014 - Thoughts? Backup Exec 2014   8 Replies Habanero OP Bottman Jan 4, 2015 at 10:24 UTC It's probable that the tape is either faulty or damaged. You should not try using it anymore as it might cause drive issues. Tapes don't last forever and they should be replaced; the cycle depends upon the type of tape and frequency of use. 0 Thai Pepper OP technetos Jan 4, 2015 backup exec 2010 at 2:17 UTC How old is the failing tape? Or, rather, how many hours of use is on the failing tape? 0 Poblano OP benben4 Jan 4, 2015 at 2:22 UTC it's an LT05 tape I have only backed up to it only once. it's the same age as the other tape on the media 0 Thai Pepper OP technetos Jan 4, 2015 at 2:34 UTC I've seen new tapes bad out of the box. Perhaps that is what has happened. 0 Serrano OP Vivek (Symantec) Jan 5, 2015 at 5:27 UTC Brand Representative for Symantec Try creating a Disk Storage and duplicate the existing backup sets from tape to disk. Check if the catalog of this disk device fails or not. And then check if you are able to view the appropriate restore selections or not. 1 Chipotle OP LMosla (Symantec) Jan 5, 2015 at 4:44 UTC Brand Representative for Symantec try deselecting 'Use storage-based catalogs' by clicking the Backup Exec button, click Configuration and Settings, and then click Backup Exec Settings. In the left pane, click Catalog. deselect: Use storage-based catalogs here is an explanation of the catalog media settings http://www.symantec.com/docs/HOWTO23126 1 Poblano OP benben4 Jan 5, 2015 at 5:11 UTC Hi I have done that earlier. but that didn't work either 0 Poblano OP Best Answer benben4 Jan 11, 2015 at 11:31 UTC Removed the faulty tapes and it worked 0 This dis
Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Backup Exec Will Not Catalog External Drive - Physical Volume Library Drive Not Found Want to Advertise Here? Solved Backup Exec Will Not Catalog External Drive - Physical Volume Library Drive Not Found Posted on 2012-01-20 Storage Software 1 Verified Solution 7 Comments 1,523 Views Last Modified: 2013-12-01 Hello, I am attempting to recover some data from a removable hard drive we use for our backups. I have installed Backup Exec 11d on a new machine and I have connected the external drive. Backup Exec finds it and I am able to inventory it with no issues and it sees the b2 files on the drive. However, when I attempt to catalog it so I can restore the data it almost immediately gives me an error saying "The job failed with the following error; Physical Volume Library not found." Any ideas how I may get the data from it? Thank you 0 Question by:daskas27 Facebook Twitter LinkedIn Google LVL 6 Best Solution byrpassero What's the actual error code and text from the job log? Are you using the drive as a "removable backup to disk folder" or a regular b2d folder? Have you tried rebooting the server with the drive attached? Go to Solution 7 Comments LVL 8 Overall: Level 8 Storage Software 2 Message Expert Comment by:PaulD772012-01-20 take a look at the symantec support page below. http://www.symantec.com/business/support/index?page=content&id=TECH4925 0 Message Active 3 days ago Author Comment by:daskas272012-01-20 I ma trying to restore, not backup. Thanks anyways. 0 LVL 8 Overall: Level 8 Storage Software 2 Message Expert Comment by:PaulD772012-01-20 midway down it mentions the error ocurring on a restore 0 Message Active 3 days ago Author Comment by:daskas272012-01-20 Oops, my apologies. No joy. 0 LVL 6 Overall: Level 6 Storage Software 1 Message Accepted Solution by:rpassero2012-01-20 What's the actual error code and text from the job log? Are you using the drive as a "removable backup to disk folder" or a regular b2d folder? Have you tried rebooting the server with the drive attached? BE 11d isn't nearly as good at handling removable disk media as the newer versions are, there