Forum Discussion

Upgrayedd's avatar
Upgrayedd
Level 2
10 years ago

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_MORE

1 Reply

  • Did you enable debugging simultaneously on the BE server and the Sharepoint servers ? If yes, then pls attach / PM the complete debug logs from both servers.

    Were the remote agents updated as well ?

    Does recreating the backup job help ?