Backup Exec Database Location
The new location can be on another computer running Microsoft SQL Server, or on the same computer running a different instance of SQL Server.Note: SQL Server Services will be stopped and Symantec BE 12, still remained in the add/remove program list - but when we tried to uninstall it again we got an error that this could be done only with installed There are 0 rows in 0 pages for object "MachineDevice". we detached the BEDB ashton_har Level 4 Partner 11-03-2013 04:17 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Well.. his comment is here
I doubt this will work. Server:APPSERVER, Service:BackupExecRPCService stopped successfully or was not running. Then we reinstalled Backup Exec 12. Connect with top rated Experts 11 Experts available now in Live!
Backup Exec Database Location
I do have SQL on another Server and have the tools there so I can see the SQL Server Express and it appears to be functioning fine. I believe that BE 12 and up uses a newer version of SQL so there could be some fighting going on. If we completely uninstall the product, and reinstall it can we import to the new installation the backup database ? 0 Kudos Reply You can see the instance name Jaydeep_S Level
EDIT*** If you have an active support, do raise a ticket with Support & there is a manual process for moving the BEDB 0 Kudos Reply I have not enabled this I suggest start with the easy stuff first. http://seer.entsupport.symantec.com/docs/294396.htm · Looked into dbrecover.log and found the following logs in it //////// dbrecovery.log ////////// Backup Exec Database Recovery Recover database using best method.. Backup Exec Sql Server Permissions You'll get all the installed OLE DB Providers on the box when you've switched to the Provider tab. 6.
Can't find anything w/Google or TechNet.Error code is 0x2000E2D3Message Edited by rgolsen on 04-04-200706:29 AM 0 Kudos Reply Re: Problem installing on 2003 x64 Doug_Williams_2 Level 3 04-16-2007 01:37 PM Options Backup Exec Sql Database This is an informational message only. DBCC results for ‘ChangeJournalData'. check over here We finally managed to have a ashton_har Level 4 Partner 11-04-2013 07:54 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate
Opened a support case, talked with a TSE and still waiting after 48hrs for the Symantec SQL engineer to contact us .. 0 Kudos Reply Hi Ashton, I assume you The Backup Exec Database Was Offline Thank you. 0 Kudos Reply Accepted Solution! No Yes Did this article save you the trouble of contacting technical support? Storage Software Installing and Configuring Windows Server Backup Utility Video by: Rodney This tutorial will walk an individual through the steps necessary to install and configure the Windows Server Backup Utility.
Backup Exec Sql Database
For more information, click the following link: http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml Resolution : ========= · From the error message, we see that media service could not start as the recovery failed on a Select the ‘Microsoft OLEDB provider for SQL Server and click on "Next" and the context will switch to "Connection" tab. 7. Backup Exec Database Location Showing results for Search instead for Do you mean VOX : Backup and Recovery : Backup Exec : Backup Exec 12.0 and SQL 2008 problem Subscribe to RSS Feed Mark Topic Backup Exec Database Maintenance For more information, click the following link: http://eventlookup.veritas.com/eventlookup/EventLookup.jhtmlThe system Log Event Type:ErrorEvent Sourceervice Control ManagerEvent Category:NoneEvent ID:7024Date:1/18/2007Time:8:50:13 AMUser:N/AComputerERVER2Description:The Backup Exec Device & Media Service service terminated with service-specific error 536928979 (0x2000E2D3).For
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 we detached the BEDB from SQL 2008 instance. It should point to the local server, which is the Managed Media Server. To detach and re-attach the Backup Exec Database using OSQL, perform the following: Stop all the Backup weblink You cannot attach a SQL Server 2005 database to SQL Server 2008 View solution in original post 0 Kudos Reply 3 Replies I just ran into this issue as d_Trafford N/A
No Yes How can we make this article more helpful? The Backup Exec Database Was Offline. Please Bring The Database Online 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 The USB drive must be s… Storage Software Windows Server 2008 Disaster Recovery Advertise Here 592 members asked questions and received personalized solutions in the past 7 days.
Aravind Lakshminarayanan SE, Microsoft SQL Server Reviewed by ShamikGhosh & Sudarshan NarasimhanTL, Microsoft SQL Server Tags Backupexec SQL Server 2000 Comments (0) Cancel reply Name * Email *
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 Also, start the sgmon.exe with help of the following document:http://www.seer.support.veritas.com/docs/190979.htm along with the other options in the sgmon, please select "beutility" as well so that the process of moving the database Could you please perform the steps mentioned in the following Document:http://support.veritas.com/docs/274102Also, could you perform the following test. Backup Exec Management Service Startup In Exception Mode. Error Message Bkupinst (install log) error V-225-206: Login failed for userV-255-226: Unable to connect to SQL server Cause Setup is not able to connect Backup Exec database (SQL express) during upgrade/uninstall.
The change of BEDB location is in progress 8. we got this.. The Backup Exec Database can be detached and re-attached to recover the connection. Before detaching the database verify if the correct server and instance name is reflected in the Adamm check over here BEDB is getting detached and re-attached to the new SQL server instance 9.
If this is an instance with a different name, BE configuration needs to be changed. Solution Remove the following via add /remove program: Microsoft SQL server native client Microsoft SQL server setup support files (English) Microsoft report viewer redistibutable MSXML If problem continues detach BEDB manually and continue