Backup Exec 15 doesn't detect some of SharePoint resources
I have Windows Server 2008, Windows SharePoint Services (WSS) 3.0, and Backup Exec 15 with all updates installed. I used to have Backup Exec 2010. Since I upgraded to 15, I see that two of SharePoint databases SharedServices_DB and SharedServices_Search_DB are no longer grayed out under MSSQLSERVER while SharePoint resources SharedServices and Global Settings no longer show up under my Server Farm.
Sharepoint 2013 backup error: Unable to query the Team database meta-data.
Hello, We have a single Sharepoint 2013 server and SQL 2012server hosted on aWindows Server 2012. Thebackup job was one day toanother failing with the error: V-79-57344-794 - Error: Unable to query the Team database meta-data. I still have ticket open withSymantec Advanced teams for weeks without a solution. So I turn to you for assistance. The backup server production server isBE 2014 running on a Windows 2008 R2 server. I read issue is solved in newest version of BE sofor future testing I have done following: Installed a new BE 15 server on Window’s2012 and updated the BE agents on SQL and SP servers. Afterwards I created new jobs, but the error is still appears on most of the databases. (Some succeeded) I have verified that the backup account is farm administrator and db owener on the SQL as advised by Symantec. Also the backup from the Sharepoint 2013 Central Administration works fine. Thanks!
on restore Backupexec 2014 SP2 can't see all Sharepoint 2013 sites
Hello, We have backupExec 2014 Sp2 on windows server 2012, and 4 sharepoint 2013 WebApp. We backup the Farm with this 4 WebApp.the backup work fine When we select to restore sharepoint individual items OR Sharepoint Farm Components, we don't dave the 4th webAPp on the selection list. We already check right of the BE exec on the farm and on the server. Can you help us? regards.
Sharepoint Server Farms FS_NO_MORE Error
Hello, we recently migrated from Backup Exec 2010 to Backup Exec 2014. Ever since our migration our Sharepoint Server Farms backup has been failing daily with the error FS_NO_MORE. I have read through the forums and the only semi related post is this one: http://www.symantec.com/connect/forums/fsnomore-backing-certain-sql-databases However, I do not believe it is a path length issue. I ran a debug on Sharepoint Server Farm 9 (one of 7 Farms in the backup job) and the job failed out instantly. The debug generated just under 3800 lines of output so I snipped out what I thought was relevant. Anybody have any suggestions as to possible cause of the failures? BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\ra] - NRDS_RA_FindDrives entered BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\ra] - NRDS_RA_FindDrives completed immediately because we aren't browsing locally BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\systemstate] - AD:DeviceName "System?State" in SystemState::CreateDLEs:186 BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\systemstate] - AD:Full Device Path "System?State" in SystemState::CreateDLEs:191 BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\systemstate] - AD:ADRO Agent is authorized for System?State. BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\systemstate] - AD:Found 0 instances of Active Directory Applcation Mode in SystemState::GetADAMInstanceCount:1288 BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\adc] - ADC_FindAgents entered BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\adc] - ADC_FindAgents completed immediately because we aren't browsing locally BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\ev] - EVM_FindDrives: Function called BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\ev] - EVM_FindDrives: Function Exit BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\sql2] - SQL2_FindDrives - checking instance BKUPEXEC. BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\sql2] - IsLocalInstance called on BKUPEXEC BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\sql2] - Attempting to open registry key SOFTWARE\Wow6432Node\MICROSOFT\Microsoft SQL Server\MSSQL10_50.BKUPEXEC\Cluster BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\sql2] - failed to open registry key. status = 2, connectKey = NULL, lastError = 997 BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\sql2] - returning instance is local BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\sql2] - IsServiceClusterOk called on SERVER-NAME-34 BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\sql2] - could not get cluster name from registry. BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\sql2] - SQL2_CreateInstanceParentDLE - creating SERVER-NAME-34\Microsoft SQL Server Instances. BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\sql2] - SQL2_CreateDLE - creating SERVER-NAME-34\BKUPEXEC. BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\sql2] - SQL Version 2008 R2 BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\sql2] - GetNextAlias - FS_NO_MORE BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\sql2] - Setting 2K5 extended feature bit. BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\sql2] - Setting 2K8 extended feature bit. BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\sql2] - SQL2_FindDrives - checking instance CAIDLO. BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\sql2] - IsLocalInstance called on CAIDLO BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\sql2] - Attempting to open registry key SOFTWARE\Wow6432Node\MICROSOFT\Microsoft SQL Server\MSSQL11.CAIDLO\Cluster BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\sql2] - failed to open registry key. status = 2, connectKey = NULL, lastError = 203 BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\sql2] - returning instance is local BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\sql2] - IsServiceClusterOk called on SERVER-NAME-34 BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\sql2] - could not get cluster name from registry. BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\sql2] - SQL2_CreateDLE - creating SERVER-NAME-34\CAIDLO. BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\sql2] - SQL Version 2012 BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\sql2] - GetNextAlias - FS_NO_MORE BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\sql2] - Setting 2K5 extended feature bit. BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\sql2] - Setting 2K8 extended feature bit. BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\ese] - [FSYS:ESE07] FindDrives ... This is not an Exchange Server (0) BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidence on SERVER-NAME-34, in SERVER-NAME-59 BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidenc: key opened BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidenc: ret = 0 BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidenc: WOW key opened BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidenc: ret = 0 BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidence on SERVER-NAME-34, in SERVER-NAME-57 BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidenc: key opened BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidenc: ret = 0 BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidenc: WOW key opened BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidenc: ret = 0 BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidence on SERVER-NAME-34, in SERVER-NAME-90 BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidenc: key opened BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidenc: ret = 0 BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidenc: WOW key opened BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidenc: ret = 0 BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidence on SERVER-NAME-34, in SERVER-NAME-61 BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidenc: key opened BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidenc: ret = 0 BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidenc: WOW key opened BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidenc: ret = 0 BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidence on SERVER-NAME-34, in SERVER-NAME-88 BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidenc: key opened BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidenc: ret = 0 BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidenc: WOW key opened BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidenc: ret = 0 BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidence on SERVER-NAME-34, in SERVER-NAME-04 BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidenc: key opened BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidenc: ret = 0 BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidenc: WOW key opened BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidenc: ret = 0 BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidence on SERVER-NAME-34, in SERVER-NAME-VM74 BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidenc: key opened BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidenc: ret = 0 BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidenc: WOW key opened BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidenc: ret = 0 BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidence on SERVER-NAME-34, in SERVER-NAME-VM73 BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidenc: key opened BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidenc: ret = 0 BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidenc: WOW key opened BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidenc: ret = 0 BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidence on SERVER-NAME-34, in SERVER-NAME-44 BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidenc: key opened BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidenc: ret = 0 BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidenc: WOW key opened BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidenc: ret = 0 BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidence on SERVER-NAME-34, in CA60-TFS2008 BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidenc: key opened BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidenc: ret = 0 BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidenc: WOW key opened BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidenc: ret = 0 BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidence on SERVER-NAME-34, in SERVER-NAME-55 BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidenc: key opened BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidenc: ret = 0 BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidenc: WOW key opened BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidenc: ret = 0 BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidence on SERVER-NAME-34, in SERVER-NAME-58 BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidenc: key opened BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidenc: ret = 0 BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidenc: WOW key opened BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidenc: ret = 0 BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidence on SERVER-NAME-34, in SERVER-NAME-92 BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidenc: key opened BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidenc: ret = 0 BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidenc: WOW key opened BEREMOTE: [05/05/15 14:35:39] [7068] [fsys\spsv3] - checking for SPS evidenc: ret = 0 . . . BESERVER: [05/05/15 14:35:43] [0000] In Function MN: SendNotification added from to subject Backup Exec Alert: Job Failed (Server: "SERVER-NAME-34") (Job: "Debug Server Farm 9 Backup-Backup") messsage (Server: "CORP-ALT-34") (Job: "Debug Server Farm 9 Backup-Backup") Debug Server Farm 9 Backup-Backup -- The job failed with the following error: FS_NO_MOREbengine.exe keeps crashing once a week
Hi, i had BE 2014 SP1 running fine for some month, now i had to update to SP2 for some problems mit Tape usage. But in the last weeks, since installation of SP2 the bengine keeps crashing about every week. I have Windows 2012 R2 Update 1 Std, All Updates, English Language I have BE 2014 SP2 (14.1.1786.1093) and i just keeps crashing during normal backup jobs (Backup, Catalog, Duplicate). Today the engine crashed during a backup of a Hyper-V SQL Server (Windows 2012 R2, SQL 2012) during increment backup. Last week it crashed during a catalog job of a Hyper-V SQL Server (GRT) job. Where can i start debugging? Symantec is helpless because, the event log show´s no useful information . A process crash has been detected. Faulting application: bengine.exe 14.1.1786.1093 Faulting module: ??? ??? I had a case open, but support wasn´t able to find some hints, so they closed the case. Any help is appreciated. Thanks Jürgen PS. I will installfirst the Hotfix 227745
How to best backup SharePoint 2013 with 2008R2 SQL and VMware?
Hi, My customer´s environment is this: - One server(2012) with SharePoint 2013 server(only one server in the farm) - One server(2012) with MS SQL 2008R2(all sharepoint databases are here. this server also handles lots of other databases) All servers are virtual using VMware. The Backup Exec 2014 server(2008R2) is a physical standalone machine. I need to backup everything, preferable using VMware Agent with GRT. The plan in to run Full backups of everything once a month, and incrementals daily. One of the problem I have is that almost every Sharepoint Farm backups fail with the following errer: "Final error: 0xe0000363 - The Backup Exec SQL Agent was not used to create the last full, differential, or log backup of this database. You must use the SQL Agent to run a full backup before you can run a differential backup or transaction log backup." Ofcourse I only backup with BE, nothin else. I interpret the message above as I do a VMware GRT backup of the database server first, the following backup using Sharepoint agent complains. I would like to know what the best practises is to backup with a scenario like this? I´m getting confused and suspect that I backup both the sharepoint anvironment and the sql environment twice which is stupid. Some questions I have in my head are: Should I backup the SQL server using VMware Agent with SQL GRT? Since I want to restore individual databases other that Sharepoint. Or should I backup without GRT and do a backup using the SQL agent and select only the non-sharepoint databases? And Should I do the same for the SharePoint server or not? Or what about backup the "farm" since that seems to backup databases too? Please help me how I should set this up the best way. Regards, //Andreas..