This blog post is to share the experience seen with issues around moving the Skype for Business fileshare from one windows server to another.
Its worth noting that this was a real life issue seen on a clients site so elements of the image are blackout to hide the clients identity.
Below is the details and scenario seen
I followed this set Microsoft procedure to move the actual file share:
- Create the new file share and configure the correct permissions;
- Stop all Skype for Business services across all FE’s in the Enterprise pool;
- Configure topology to include new file store and associate with the Enterprise pool before publishing changes;
- Run bootstrapper on all FE’s;
- Copy data from old file share to new one using robocopy;
- robocopy \\OldServerFQDN\OldShare \\NewServerFQDN\NewShare /S /R:10 /W:10 /XF Meeting.Active /MT;
- Start the Skype for Business Enterprise pool using Start-CsPool commandlet;
After following each of the steps about, all services started successfully however after a basic health check it appeared that there was an issue with the backup service (pool pairing), see below:
So go figure….?
My next steps was to de-configure the pool pairing and re-configure it, however the error same occurred.
I then proceeded to reboot each Frontend in turn, same error occurred after rebooting all Frontend’s.
Everything looked good at this point in terms of File Store association with the Enterprise pool. The old file share was not referenced anywhere.
THE FINAL PART OF THE FIX
The fix was to move the WebServices* directory on the old file share into a temp directory, very bizarre as the old share was not referenced anywhere in Topology/PowerShell.
After moving this directory and restarting the backup service again, all the errors cleared and the backup service returned to normal state.