ANY MATERIALS FOR A FRESHER TO CRACK THE CERTIFICATION EXAM
Hi, i am fresher going to da certification on Netbackup tool. please give me any suggestions as : 1) which certification will help me a lot to work on Netbackup all kinds of services. 2) materials which can be helpful for cracking the exam other than the guides provided by the website. 3) what should i do to be more competent enough to handle all the situations in the environment while dealing with this tool. Regards, vinay saiSolved1.4KViews0likes2CommentsBackup 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.1.3KViews0likes8CommentsSharepoint 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!467Views0likes1Commentslow sharepoint backup
Hello I have an issue with a Sharepoint GRT backup with NBU 7.6.1.2. The architecture is the following : - Sharepoint 2010, 2 Front web servers, 2 application servers, 1 Clustered SQL Server - all servers are virtual machines - Service account used for legacy Network, legacy client and client services is domain admin + local admin and has the required 4 rights in local security policy - DNS is OK (hosts has been also updated with short and long names - just in case) - non-GRT backup is runing fine - GRT backup is starting well, but after "some time" is slowing down ... - I have enabled verbose loging on SQL server and the following messages appear in bpkar log file : 21:54:06.290 [1708.7048] <2> vnet_sortaddrs: [vnet_addrinfo.c:3852] sorted addrs: 1 0x1 21:54:06.290 [1708.7048] <2> vnet_get_pref_netconnection: [vnet_addrinfo.c:4750] using interface ANY 21:54:06.290 [1708.7048] <2> vnet_sortaddrs: [vnet_addrinfo.c:3852] sorted addrs: 1 0x1 21:54:06.290 [1708.7048] <2> vnet_get_pref_netconnection: [vnet_addrinfo.c:4750] using interface ANY 21:54:06.290 [1708.7048] <8> vnet_cached_getaddrinfo_and_update: [vnet_addrinfo.c:1544] in failed cache ERR=10109 NAME=SVBLL-WI05Q SVC=bpspsserver 21:54:06.290 [1708.7048] <8> vnet_cached_getaddrinfo: [vnet_addrinfo.c:1267] vnet_cached_getaddrinfo_and_update() failed 6 0x6 21:54:06.290 [1708.7048] <8> init_remote_connect_recs: [vnet_connect.c:949] vnet_cached_getaddrinfo() failed, status=6, OS ret=10109, host=SVBLL-WI05Q, service=bpspsserver 21:54:06.290 [1708.7048] <2> vnet_sortaddrs: [vnet_addrinfo.c:3852] sorted addrs: 0 0x0 21:54:06.290 [1708.7048] <8> init_connect_recs: [vnet_connect.c:868] init_remote_connect_recs() failed 6 0x6 21:54:06.290 [1708.7048] <2> init_connect_recs: [vnet_connect.c:880] Ignoring some failures. Success count 2 0x2 21:54:06.290 [1708.7048] <2> async_connect: [vnet_connect.c:1499] connect in progress 1 0x1 21:54:06.304 [1708.7048] <2> vnet_pbxConnect: pbxConnectEx Succeeded 21:54:15.974 [1708.7048] <8> vnet_vnetd_service_socket: [vnet_vnetd.c:1995] VN_REQUEST_SERVICE_SOCKET 6 0x6 21:54:15.974 [1708.7048] <8> vnet_vnetd_service_socket: [vnet_vnetd.c:2009] service bpspsserver 21:54:16.484 [1708.7048] <2> do_pbx_service: [vnet_connect.c:2159] via PBX/via VNETD bpspsserver CONNECT FROM 10.225.64.101.64646 TO 10.225.64.106.1556 fd = 1280 21:54:16.485 [1708.7048] <2> async_connect: [vnet_connect.c:1691] connect async CONNECT FROM 10.225.64.101.64646 TO 10.225.64.106.1556 fd = 1280 21:54:16.485 [1708.7048] <2> connect_to_service: connect succeeded STATUS (0) SUCCESS FROM 0.0.0.0 TO SVBLL-WI05Q 10.225.64.106 bpspsserver VIA pbx 21:54:16.485 [1708-7048] vnetdSendRequest Sending message 0xf331 21:54:16.485 [1708-7048] vnetdProcessMessage received a reply successfully for message 0xf331 21:54:20.175 [1708.7072] <2> vnet_sortaddrs: [vnet_addrinfo.c:3852] sorted addrs: 1 0x1 21:54:20.175 [1708.7072] <2> vnet_get_pref_netconnection: [vnet_addrinfo.c:4750] using interface ANY 21:54:20.175 [1708.7072] <2> vnet_sortaddrs: [vnet_addrinfo.c:3852] sorted addrs: 1 0x1 21:54:20.175 [1708.7072] <2> vnet_get_pref_netconnection: [vnet_addrinfo.c:4750] using interface ANY 21:54:20.176 [1708.7072] <8> vnet_cached_getaddrinfo_and_update: [vnet_addrinfo.c:1544] in failed cache ERR=10109 NAME=SVBLL-WI05Q SVC=bpspsserver 21:54:20.176 [1708.7072] <8> vnet_cached_getaddrinfo: [vnet_addrinfo.c:1267] vnet_cached_getaddrinfo_and_update() failed 6 0x6 21:54:20.176 [1708.7072] <8> init_remote_connect_recs: [vnet_connect.c:949] vnet_cached_getaddrinfo() failed, status=6, OS ret=10109, host=SVBLL-WI05Q, service=bpspsserver 21:54:20.176 [1708.7072] <2> vnet_sortaddrs: [vnet_addrinfo.c:3852] sorted addrs: 0 0x0 21:54:20.176 [1708.7072] <8> init_connect_recs: [vnet_connect.c:868] init_remote_connect_recs() failed 6 0x6 21:54:20.176 [1708.7072] <2> init_connect_recs: [vnet_connect.c:880] Ignoring some failures. Success count 2 0x2 21:54:20.176 [1708.7072] <2> async_connect: [vnet_connect.c:1499] connect in progress 1 0x1 21:54:20.190 [1708.7072] <2> vnet_pbxConnect: pbxConnectEx Succeeded 21:54:24.119 [1708.7072] <8> vnet_vnetd_service_socket: [vnet_vnetd.c:1995] VN_REQUEST_SERVICE_SOCKET 6 0x6 21:54:24.119 [1708.7072] <8> vnet_vnetd_service_socket: [vnet_vnetd.c:2009] service bpspsserver 21:54:24.725 [1708.7072] <2> do_pbx_service: [vnet_connect.c:2159] via PBX/via VNETD bpspsserver CONNECT FROM 10.225.64.101.64653 TO 10.225.64.106.1556 fd = 1280 21:54:24.725 [1708.7072] <2> async_connect: [vnet_connect.c:1691] connect async CONNECT FROM 10.225.64.101.64653 TO 10.225.64.106.1556 fd = 1280 21:54:24.725 [1708.7072] <2> connect_to_service: connect succeeded STATUS (0) SUCCESS FROM 0.0.0.0 TO SVBLL-WI05Q 10.225.64.106 bpspsserver VIA pbx 21:54:24.726 [1708-7072] vnetdSendRequest Sending message 0xf331 21:54:24.726 [1708-7072] vnetdProcessMessage received a reply successfully for message 0xf331 I am worried (but maybe i am wrong) byvnet_cached_getaddrinfo_and_update: [vnet_addrinfo.c:1544] in failed cache ERR=10109 NAME=SVBLL-WI05Q SVBLL-W05Q is the front web server used as client in the NBU policy. Thanks in advance for any clue/help Best regards2KViews1like11CommentsSharePoint Restore shows only Root Site Collection
Hello, we're using NetBackup in the current version 7.6.1.2 to backup a SharePoint 2013 SP1 single server environment running on VMware. After struggling somewhile around to get the backup working - in the end we were experiencing the problem that the SharePoint Farm key did not get created automatically - god knows why. (Solved with -http://www.symantec.com/docs/TECH203759). Now the backup finishes without any error. Now we have the problem that in the GRT restore selection only the root site collection is showing up. Anywaywe have more then 20 sitecollections, all in the same Content Database,which are not showing up. All site collections are created as hostnamed site collection. Could someone point me in the right direction what could be the reason for our problem? Thanks in advance. MatthiasSolved765Views0likes1CommentRestore of SharePoint 2013 Workflows
Hi, will BE 2015 restore workflows at a granular/individual level? That is to say, if I need to restore a workflow, can I select it individually for restore, or would I need to restore an entire site? Also, if I use BE to do a SharePoint farm restore, will it restore all workflow engine components? Thank you, ChadSolved1.6KViews1like4Commentson 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.522Views0likes3CommentsSharepoint 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_MORE616Views0likes1Comment