Home > Backup Exec > Backup Exec Database Location

Backup Exec Database Location

Contents

Thank You! Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem Backup Exec Device and Media service fails to start with the message "Database Copying database file from \\OLDSQLSERVER\C$\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\bedb.bak to \\NEWSQLSERVER\c$\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\bedb.bak. this content

As you finish projects in Quip, the work remains, easily accessible to all team members, new and old. - Increase transparency - Onboard new hires faster - Access from mobile/offline Try Ensure that the provider is installed properly" Steps to perfom UDL Test 1. It also has an MD1000 disk array. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.HKLM\Software\Symantec\Backup Exec for Windows\ADAMM\Check the Database Server Name key to verify server Source

Backup Exec Database Location

Open the BEUTILITY consoleLocation: X:\Program Files\Symantec\Backup Exec Where X:\ is the Drive on which Backup Exec is installed2. I'm using Windows Server 2003 Enterprise R2 (32-bit, not x64). No Yes Did this article save you the trouble of contacting technical support?

View solution in original post 0 Kudos Reply 9 Replies 1. CALL US: 1 (866) 837-4827 Solutions Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government Products Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z Services Education Services Business Critical Error: Copy database failed. Backup Exec Sql Server Permissions Right-click on All media servers and select the new media server3.

At some point I will try reinstalling BE 11d and SQL Express. 0 Kudos Reply Re: Problem installing on 2003 x64 Patty_McGowan Level 6 Employee ‎04-17-2007 10:52 AM Options Mark as Backup Exec Sql Database Email Address (Optional) Your feedback has been submitted successfully! But when we try to change the backup Exec Database Location via Backup Exec Utility we have an error because it failed to start the SQL service (which is running..) failed Otherwise, grab copies of the Data and Catalogs folders, and consider a reinstallation carefully.

Upon checking it failing in a "Database Recovery". The Backup Exec Database Was Offline BE2010 R3 is running on "APPSERVER", while "OLDSQLSERVER" is the old server running SQL 2005. "NEWSQLSERVER" is a virtual machine running SQL 2005 Express. BEDB no longer requires MSDE services or SQL Express.  7. It is possible that updates have been made to the original version after this document was translated and published.

Backup Exec Sql Database

We manually deleted every 'BKUPEXEC' value from the registry (one couldn't be deleted). If we upgrade to a newer version (that supports SQL2008) can we solve the issue ? 0 Kudos Reply Well.. Backup Exec Database Location Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Unable to move Backup Exec database from MSDE Backup Exec Database Maintenance the installation program asked us for the database instance, and we pointed it to the 'BACKUPEXEC' instance that we had created in the previous attempts.

Select All Tasks | Detach database (Figure 3)  Figure 3      4. news Any suggestions ? This may fail as the original instance does not exist. Go to Solution. Backup Exec Management Service Was Unable To Start

Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem How to change the Backup Exec Database (BEDB) location using BEUTILITY. This showed me the following message;� CREATE DATABASE permission denied in database 'master' �.I gave the userid that was running the BEUtility the relevant permissions in the master database on the Click OK to confirm (Figure 4)   Figure 4       To re-attach the BEDB database:  1. http://technologyprometheus.com/backup-exec/backup-exec-error-codes.html the installation program asked us for the database instance, and we pointed it to the 'BACKUPEXEC' instance that we had created in the previous attempts.

Hence the error message mentioned in subject is misleading. · Took hints from below mentioned article in Symantec website which talks about a file called ‘dbrecover.log’ located at C:\Program Files\Symantec\Backup Exec\Logs\ The Backup Exec Database Was Offline. Please Bring The Database Online Join Now For immediate help use Live now! Subscribe to our monthly newsletter for tech news and trends Membership How it Works Gigs Live Careers Plans and Pricing For Business Become an Expert Resource Center About Us Who We

Right-click on the BEDB database  3.

You pkh Moderator Trusted Advisor Certified ‎10-23-2011 10:08 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content I doubt this This will be created automatically by Backup Exec.  2. User can move the database to an existing SQL server to overcome 2 GB storage capacity limitation provided by MSDE or SQL Express engine.Caution: Backup Exec database is the most critical Backup Exec Management Service Startup In Exception Mode. Labels: Backing Up Backup and Recovery Backup Exec Configuring Database Error messages Installing SQL Troubleshooting 0 Kudos Reply 1 Solution Accepted Solutions Accepted Solution!

Hence decided to run DBCC CHECKDB(‘BEDB') and check the consistency of the database. · The results turned out to be clean and we confirmed that there is no corruption in the You'll get all the installed OLE DB Providers on the box when you've switched to the Provider tab. 6. You may also refer to the English Version of this knowledge base article for up-to-date information. check my blog Go to Solution.

No Yes How can we make this article more helpful? The manual process is simple, VJware Level 6 Employee Accredited Certified ‎01-05-2012 01:51 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Then we reinstalled Backup Exec 12. Go to Solution.

How can we check this ? 3/ We tried to attach the db, but it failed. The Database Recovery Log follows:Backup Exec Database Recovery01/17/07 11:58:05-----------------------------Initializing...BEGetComputerName = 'SERVER2'GetBeVirtualServerName = ''Using node name for media serverData for BE database:Structure size: 6504Media Server : SERVER2Node, if clust: SQL Server : http://blogs.msdn.com/b/sqlexpress/archive/2005/05/05/415084.aspx 0 Kudos Reply Have you tried to move it VJware Level 6 Employee Accredited Certified ‎01-05-2012 12:32 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Stopping SQL service on server: OLDSQLSERVER : MSSQLSERVER Copying database file from \\OLDSQLSERVER\C$\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\bedb_dat.mdf to \\NEWSQLSERVER\c$\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\bedb_dat.mdf.

Go to the services.msc applet in the Control Panel and open the previous Backup Exec database SQL server (MSDE) or SQL Express instance.For example, SERVER\BKUPEXEC  The old MSDE or SQL Express There is also a Dell PowerVault 100T DAT72 internal.This configuration was working. Showing results for  Search instead for  Do you mean  VOX : Backup and Recovery : Backup Exec : Problem installing on 2003 x64 Subscribe to RSS Feed Mark Topic as New Connect with top rated Experts 11 Experts available now in Live!

Whenever we try to install an SQL 2005 Express instance named BKUPEXEC, we get always the same eerror We can install a new SQL 2005 Express instance if we give Does anyone know why this is happening? 0 Kudos Reply Hi You can try doing this newsolutionBE Level 6 ‎10-23-2011 08:01 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Great care should be taken when making changes to a Windows registry. The server name is there with no instance name. 0 Kudos Reply Re: Problem installing on 2003 x64 rgolsen Level 2 ‎04-16-2007 02:41 PM Options Mark as New Bookmark Subscribe Subscribe

we detached the BEDB from SQL 2008 instance. Email Address (Optional) Your feedback has been submitted successfully! I cannot get the upgrade to complete at all.