I am trying to backup (scheduled) the database into a mapped network drive in windows environment.
Always get this error during validation.
Appreciate any help.
That's because it won't work. And even if it did (and it has worked on and off through the FMS versions): you don't want to do it.
Because it substitutes network i/o for disk i/o and that makes it fragile and slow. You don't want to make FMS wait for the backup to finish, nor do you want the risk of the backup failing because of some network hiccup.
The best practice is to let FMS make the backup locally and then copy, move or sync it to a remote location.
And for that remote location: don't use a mapped drive. Mapped drives are user-space functionality, FMS is a background service so it should never run with a user logged in to do the mapping. Use the network location's UNC format: \\serverName\shareName\ instead.
Use the OS or third party backup software to move your local FMS backups to a mapped drive.
For fellow Mac users, I've been using Chronosync for this for a few years now and it's been fantastic. I have a Daily backup that runs and backups to a local drive, as well as an additional Offsite backup that runs daily, but where I have the backups to keep set to 0. Then, Chronosync comes along and syncs that backup to our backup array in our remote office (fiber link) 30 minutes away. I've found this to be the best way of keeping our 300GB container files backed up. Having the backups to keep set to 0 means the name of the folder never changes and Chronosync only backs up the altered container folders/files.
Retrieving data ...