This post is more than 5 years old
86 Posts
0
1350
MSSQL problems - recover
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?
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?
DavidHampson
1.1K Posts
0
August 13th, 2009 05:00
benzino1
244 Posts
1
August 13th, 2009 04:00
DavidHampson
1.1K Posts
1
August 13th, 2009 05:00
pereubu
86 Posts
0
August 14th, 2009 02:00
¿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?
DavidHampson
1.1K Posts
0
August 14th, 2009 03:00
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.
DavidHampson
1.1K Posts
0
August 14th, 2009 03:00
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.
nsoto
16 Posts
0
August 14th, 2009 13:00
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.
nsoto
16 Posts
0
August 14th, 2009 13:00