pereubu
2 Iron

MSSQL problems - recover

Jump to solution
This is my work set:

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?
Tags (1)
0 Kudos
1 Solution

Accepted Solutions
DavidHampson
4 Tellurium

Re: MSSQL problems - recover

Jump to solution
To recover your database you need to use Networker User for MS SQL GUI from the client
0 Kudos
8 Replies
benzino1
3 Argentium

Re: MSSQL problems - recover

Jump to solution
What version of MSSQL module do you use? What is your backup command for backing up MSSQL?
Highlighted
DavidHampson
4 Tellurium

Re: MSSQL problems - recover

Jump to solution
Are these in the same client instance? You need to have a second instance of the client set up in Networker where you define the saveset MSSQL: and where you set the backup command to nsrsqlsv.exe
DavidHampson
4 Tellurium

Re: MSSQL problems - recover

Jump to solution
To recover your database you need to use Networker User for MS SQL GUI from the client
0 Kudos
pereubu
2 Iron

Re: MSSQL problems - recover

Jump to solution
1. instance: client mysqlclient ¿ comment: non sql backup

¿ASR:\
C:\
SYSTEM DB:\
SYSTEM FILES:\
SYSTEM STATE:\¿

2. instance: client mysqlclient ¿ comment: sql backup

MSSQL:fptopup

Everything else is the same: schedule etc.

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?


C:\Program Files\Legato\nsr\bin>nsrsqlsv.exe -s server15-1rd.fplus.local -l incr
-b "Bekap servera full" MSSQL:sptopup
43708:(pid 4720):Start time: Fri Aug 14 10:17:34 2009
43621:(pid 4720):Computer Name: mycomp1 User Name: roxette
37785:(pid 4720):Last backup of database 'sptopup' was not created using NMSQL M
odule.
Promoting the backup level to full. NSR_BACKUP_LEVEL: full;
NSR_DATA_VOLUME_POOL: Bekap servera full;
NSR_LOG_VOLUME_POOL: Bekap servera full;
NSR_SAVESET_NAME: "MSSQL:sptopup";
NSR_SERVER: server15-1rd.fplus.local;
37994:(pid 4720):Backing up fptopup...
4690:(pid 4720):BACKUP database [FpTopup] TO virtual_device='Legato#3b284a9f-238
5-4425-a0d4-227db95ebf3b' WITH name=N'LegatoNWMSQL'
53085:(pid 4720):Backing up of spTopup succeeded.
nsrsqlsv: MSSQL:fptopup level=full, 2471 MB 00:02:52 1 file(s)
43709:(pid 4720):Stop time: Fri Aug 14 10:20:28 2009


C:\Program Files\Legato\nsr\bin>

On networker user for sql we have database on help EMC Networker Module for Microsoft (R) SQl Server version 5.2.1.239 ?

Now the problem is maybe the license??? I had different database server, which I do not use anymore,. Now I have problem with transfering license from one server to another a new one.

On networker Adminstrator ¿ Configuration ¿ Reistration there is networker Module for Microsoft SQL Server/9 as Authorised no expiration date.

I believe that problem is with licensing?
0 Kudos
DavidHampson
4 Tellurium

Re: MSSQL problems - recover

Jump to solution
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.
0 Kudos
DavidHampson
4 Tellurium

Re: MSSQL problems - recover

Jump to solution
I believe that problem is with licensing?

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.
0 Kudos
nsoto
1 Copper

Re: MSSQL problems - recover

Jump to solution
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.
0 Kudos
nsoto
1 Copper

Re: MSSQL problems - recover

Jump to solution
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.
0 Kudos