ASR:\ C:\ SYSTEM DB:\ SYSTEM FILES:\ SYSTEM STATE:\ MSSQL:mytopup
I have set up Networker to back some ordinary files. It works. The Schedule is full only on Suday while the rest of the week is inc. That is not the case for MSSQL:nameoddata base, because each day I am getting full backup with inc backup immediately after 8 minutes mminfo screen output
A00009 node2.fplus.local 8/5/2009 2326 MB full MSSQL:fptopup A00009 node2.fplus.local 8/5/2009 412 B incr MSSQL:fptopup .... A00009 node2.fplus.local 8/7/2009 2365 MB full MSSQL:fptopup ... A00009 node2.fplus.local 8/7/2009 412 B incr MSSQL:fptopup ... A00009 node2.fplus.local 8/8/2009 2381 MB full MSSQL:fptopup ... A00009 node2.fplus.local 8/8/2009 412 B incr MSSQL:fptopup ... A00009 node2.fplus.local 8/9/2009 2395 MB full MSSQL:fptopup ... A00009 node2.fplus.local 8/9/2009 412 B incr MSSQL:fptopup
Am I missing something? The schedule works fine for non MSSL like work set. Why?
One problem more is that I could not recover my database (as test only for now) when I am with "Networker User" and select Recover Option (database server) I could not see database to recover. What could be the problem?
Anyway why it is important that we have TWO instances? I did set up that way to somehow separate them during monitoring, but what design requirements require two instances of the client?
Networker uses the save command by default on your client - this backups up file systems. If you use a module you have to use a different command which will speak with the application and accept a backup stream from the application's API.
This one was raised in the forum over the last couple of weeks so you may want to browse back and see how that one was resolved. If the license was assigned to a different client it will be assigned to that client until all backups to it have expired. If you no longer have any related backups then I would suggest deleting and re-adding the enabler code.
The second save set (always a small save set -about 400 to 600 bytes) is for the meta data, also known as cover save set. When you browse using the NetWorker Module for SQL, you can see the database information (date and time of backup, size, logical name, physical location, properties, etc.) thanks to this meta data saveset. This is expected behavior of NetWorker Module for SQL. The meta data saveset should always be level incremental, even if the backup is full (there was an old "data loss" issue caused when the meta data saveset was full, so this saveset level was changed to incremental in order to avoid that issue.)
For your last question, but "NetWorker User" you mean winworkr (normal "NetWorker User") or "NetWorker User for SQL Module" (nwmsql.exe)? Make sure you are using the last one.
SQL savesets (any saveset that starts with MSSQL:) have to be backed up with nsrsqlsv.exe (the NetWorker Module for SQL backup command). File System save sets (example: ALL, C:\, VSS SYSTEM BOOT:, etc), are backed up with the save.exe backup command. Only one backup command can be specified per client instance, thus you need to client instances to backup both File System and SQL databases.