based on the error it seems to cut off the .1 from the MSSQL DB  MSSQL:EatechSettings1.1?What was exactly mentioned in the client's saveset field? Copy/pasting things into there, might indeed have entered something that isn't visible?Then again I see that the client runs nmm 9.0.1? That is pretty old and unsupported at that.Might it not be time getting into supported territory again?No idea if that very, very, very early nw9.0 version might even have had an issue dealing with MSSQL db's wit a "." (dot) in their name?If it is the only DB that is failing, an easy test would be if also another DB was introduced that also has a .1 in its name to see if that has the same issue? Should be fairly easy to test by adding a more or less empty additional DB. Even on a test system.If updating NW and NMM is out of the question, one might try renaming the DB (which might even be more cumbersome).Is it even necessary to specify the DB instead of simply using MSSQL: instead? Why do you want or need to specify the DB's even? As deleting one would cause the backup to fail, while when adding one, it would not end up in the backup?
Hi expert..! We had a SQL DB failure for the (standalone) client. when we keep the DB name in the save set manually the backup will fail for the particular database with the below error. [IMAGE]   . when we keep the DB name in the save set as default that is MSSQL that backup is getting successfully. (PFA) [IMAGE] Kindly help us to fix 
MSSQL DB failure