When BE 2012 cratered here and then was late to support new Microsoft servers we jumped ship while under the then "worthless" maintenance. Connect with top rated Experts 9 Experts available now in Live! Email Address (Optional) Your feedback has been submitted successfully! My previous home was wired with Cat5E in almost every room. Source
You may get a better answer to your question by starting a new discussion. Join Now For immediate help use Live now! Possible lost connection to database or unsuccessful access to catalog index in the database. When we bought that house, it had an unfinished basement and an unfinished attic room, making the cabling process very simple.
Renaming the Catalogs folder, restarting the services, and then deleting/renaming the original catalogs folder.2. Or do you have to use other software for physical servers ? 0 Mace OP Denis Kelley Sep 29, 2014 at 12:39 UTC GarfieldMaximus wrote:toby wells wrote: You I have tried unsuccessfully to Inventory/Catalog the bkf's from previous tapes, which tells me that the issue may revolve around running an Erase job prior to offloading data onto the tape.
I simply don't know where to start, which customers servers shall I abuse and spend my night with? Look for beutil.exe in the backup exec bin directory. Refer to the Hotfix link under Related Articles to obtain the hotfix needed to resolve the issue. Event Id 34326 Backup Exec My new house...
Symantec took too much time to get BE running on 2012R2 and vSphere 5.5 and still has not solved the old problems, it's getting even worse, so I can't believe that Odbc Access Error Backup Exec 2012 And there again, it's quicker to just disable it, restore the whole server-vm and pick out what you need instead of trying to solve (or workaround) the problem just to get Change the directory to the Backup Exec installation directory: \Program Files\Symantec\Backup Exec 4. Corrupt database index of catalogs. Solution: Run CatRebuildIndex to rebuild the Catalog indexes. (Figure 2) Stop all BE ServicesOpen command prompt and browse to x:\Program Files\Symantec\Backup ExecRun "CatRebuildIndex -r".Start all BE services.
Corrupt catalogs in the Catalogs folder. Catrebuildindex -r Retain evidence of this with email archiving to protect your employees. Cleaning it not fixing it? Send me a DM with your contact info and/or any case numbers that you currently have so we can get all these issue resolved.
Ad Choices Can you help me out ? Odbc Access Error Backup Exec 2014 How can I repair it ? Odbc Access Error Backup Exec 2010 Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue?
For more details on how to change location of catalogs refer to the link below: http://support.veritas.com/docs/286689 Resolution 3 Ensure the value of the following registry keys are as mentioned below.(Depending on Send you a PM. Open a command prompt on the media server 3. have a peek here They quickly answer the phone in English and their patches fix more than they break.
This will recreate the folder.cfg and changer.cfg . V-280-2003 Join the community Back I agree Powerful tools you need, all for free. Possible lost connection to database or unsuccessful access to catalog index in the database" when the Backup Exec Database (BEDB) is located on a remote SQL Server or not in the
I should be very surprised when things fail ... Thanks Operator10 0 Question by:Operator10 Facebook Twitter LinkedIn Google LVL 6 Best Solution byAJermo It sounds like the Backup Exec service account has been change and doesn't have access to the Note: In some cases, it may be necessary to clear the alerts tab and reboot the server after performing the steps above. Backup Exec 15 Catalog Error Odbc Access Error Look for beutil.exe in the backup exec bin directory.
No Yes Did this article save you the trouble of contacting technical support? It is possible that updates have been made to the original version after this document was translated and published. Tags: Unitrends4,299 FollowersFollow 1 Jalapeno OP CCMIS Sep 29, 2014 at 7:14 UTC Backups always require quite a bit of time regardless of the solution that you use. Check This Out I'm going to hear for a quote on the newest 2014 version ...
Sorry, we couldn't post your feedback right now, please try again later. Fill in your details below or click an icon to log in: Email (required) (Address never made public) Name (required) Website You are commenting using your WordPress.com account. (LogOut/Change) You are We have various BE 2010, BE 2012 and now we upgraded to BE 2014 Enterprise server and I would say without any doubt BE 2014 is the most reliable version I Going into Tools -> Options -> Catalog -> Unchecking "Use storage media-based catalogs" Our backup scheme involves backing up to disk, and then backing up that backup to tape.
Veeam is a great alternative. Restart all of the Backup Exec Services on the media server. Our backup costs were high due to paying for 2 solutions in 1 year. The alerts appear when the Backup Exec Services Start and during a backup or catalog job.
Stop the Backup Exec Services. 2. For more information, click the following link:http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml We have tried: 1. I'm looking for a new home Wi-Fi router — any advice? I'm getting about 50 job notifications every night, half of them failed or "succeeded with exceptions".
Or do you have to use other software for physical servers ?Veeam only works with virtual servers, not physical ones. 3 Pimiento OP Saul2641 Sep 29, 2014 at fl Level 4 05-28-2010 11:21 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content We're having major issues with our Feature Pack for Microsoft SQL Server 2005 http://www.microsoft.com/downloads/details.aspx?FamilyID=50B97994-8453-4998-8226-FA42EC403D17&displaylang=en sqlncli.msi (Microsoft SQL Server Native Client) SQLServer2005_SQLCMD.msi (Microsoft SQL Server 2005 Command Line Query Utility SQLcmd) 2) Stop the Backup Exec services using Possible lost connection to database or unsuccessful access to catalog index in the database. Source: Backup Exec CatErrorHandler ServerEvent ID: 34327Error : Update to catalog index (Catalog index database) failedReason:[Microsoft][ODBC
No Yes Menu Close Search SOLUTIONS Solutions Overview Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government PRODUCTS Product Overview Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z SERVICES If the current Backup Exec version is 2010 R2 or 2010 R3, run the osql scripts up to the 13_0 version and then run the "catrebuildindex -r". 4. 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. Join our community for more solutions or to ask questions.
Join the community of 500,000 technology professionals and ask your questions. After a catalog job is performed the restore selections may show partial or no restore selections. (FIGURE A) Solution: NOTE: There are three possible solutions to resolve this issue. Backup Exec - How does this actually work?   1 2 Next ► 37 Replies Datil OP Mark McKinlay Sep 29, 2014 at 9:18 UTC I use BE Text Quote Post |Replace Attachment Add link Text to display: Where should this link go?