Search our blog Search Blog Post Category Filter Blog Post Category Filter Recent Blog Posts So posting this as I couldn’t find any reference to this particular environment related SFB backup service error issue elsewhere. Run health check for DR site, the result looks all correct. Run health check again “get-csbackupservicestatus -poolfqdn primarypoolname”, the overallexportstatus: FinaState, the overallimportstatus:NormalState. After that, restarted the backup services, everything started working again. Reconfigured the DFS farm, all the SFB FE servers across both sites resolved the filestore name against the primary site DFS host. ![]() This breaks the configuration sync and caused backup service failed. A couple of weeks ago, the IT team made some changes on the DFS farm, at the end, SFB FE servers at primary site resolved the filestore name against the Primary site DFS host, however, the SFB FE servers at DR site resolved the filestore name against the DR site DFS host, which is a totally different host. I spoke with customer IT team and they advised that originally both primary filestore and DR filestore were located on one DFS host. This meant the filestore of primary site and DR site can’t talk with each other, so that’s the root cause of the backup service having error status. I did further ping test and verified that filestore host name was resolved differently at primary site and DR site. When I moved to the DR servers and tried to browse to primary site backup folder via the same directory, interesting thing happened, obviously, the filestore with the same directory path name on the DR servers was totally different from the filestore I browsed on the Primary servers. I tried to browse to the DR folder at the primary site. I started to do basic troubleshooting again from the primary site, I browse to the backup folder on the primary site servers recheck the folder permissions and everything looked good. I was sure that something changed from the environment background. But when I run “get-csbackupservicestatus -poolfqdn poolname” on both pools, I get the same error results as previous. I run “Invoke-csbackupservicesync -poolfqdn primarypoolname” also “Invoke-csbackupservicesync -poolfqdn backuppoolname” Everything looked just fine. After a few seconds, the new backup folder structures were recreated again. After this, I restarted all the stopped services above. Deleted the folder structure within the backup service folders. I tried to stop SFB Backup Service, File Transfer Agent Service, Master Replicator Agent Service on the FE servers across both primary pool and DR pool. Then I did a bit of googling: people say to solve the backup service problem by recreating the backup folder. This made sense because the backup services were running all good prior to certain time point. So this issue was not related with folder permission settings. ![]() I Checked the filestore folder permissions settings, it looked all correct, everyone is given access to the folder with read
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |