Unsolved
79 Posts
0
283
February 25th, 2021 09:00
networker Directive for SQL clients
What file should we be skipping if we want to perform filesystem backups for a SQL database client from networker .
Database online backups are triggered by dbas from client side.
No Events found!
bingo.1
2.4K Posts
0
February 25th, 2021 09:00
Sorry, but you better know where your db directories have been installed. Just skip the appropriate paths or volumes.
barry_beckers
393 Posts
0
March 9th, 2021 03:00
when you have the NW NMM module installed, then NW would be aware of MSSQL and would skip the MSSQL files automatically (would have been a nice feature also with other database/application modules, if configurable). but then again MSSQL might be easier to get to know this about if for example SYSTEM has the permissions to find out which files are actually belonging to the mssql instance(s). But that is for a backup scheduled from NW server end.
From client end, might depend how the backup is triggered? If it logs in, into the NW server and triggers a workflow or rather only specifying a save command or using the Networker GUI on client end?
For SAP and Oracle we tend to have the DB admins create client end directives themselves, preferably in an automated fashion whenever a new filesystem is added that then the required client end directive is also created.