MS SQL Server errors

Here you can write your Problems with Backups.

Moderator: sepma

Post Reply
booktrunk
Posts: 4
Joined: February 6th, 2014, 5:09 pm
Spam Stop: No
SEP sesam: Software

MS SQL Server errors

Post by booktrunk » June 20th, 2017, 12:43 pm

Latest version of sesam. Running on a linux server.

Windows 2008 Server
Microsoft MSSQL Server 2008 Std Edition
Latest sesam client installed.

When I do a full MSSQL Backup i am getting errors like this, not for all of the databases but for some of them.

2017-06-20 09:35:44: sbc-3103: Info: DB Module: [ATTENTION: Database [**/ReportServerTempDB] in warning status: SimpleRecoveryModel !]
2017-06-20 09:35:44: sbc-3103: Info: DB Module: [Warning state for database [**/ReportServerTempDB]]
2017-06-20 09:35:44: sbc-2076: Warning: Item [**/ReportServerTempDB] is not logged. Recovering may fail.
2017-06-20 09:35:44: sbc-3103: Info: DB Module: [ATTENTION: Database [**/TRIAL1Datamart] in warning status: SimpleRecoveryModel !]
2017-06-20 09:35:44: sbc-3103: Info: DB Module: [Warning state for database [**/TRIAL1Datamart]]
2017-06-20 09:35:44: sbc-2076: Warning: Item [**/TRIAL1Datamart] is not logged. Recovering may fail.

I am not an expert in SQL Server, but i've opened the management studio and right clicked on these databases gone into properties, and files, and each of them shows that it has a log file.

So now I'm a bit stuck as to what this error means?

mcgyver
Posts: 20
Joined: February 14th, 2012, 2:39 pm
Spam Stop: No
SEP sesam: Software

Re: MS SQL Server errors

Post by mcgyver » June 23rd, 2017, 5:45 pm

while i'm trying to keep at least a mile distance to relational DBs:
AFAIK, a DB in "simple recovery" mode MUST be backed up in "COPY" mode, attemps with "FULL" should fail by nature.
If you're using "FULL" for let's say an entire SQL server you should get the message for all DBs in simple rec mode (while consequently backups of DBs with more sophisticated recmodes should proceed). If you're running such an offset i'd assume you should urgently split the jobs to a COPY model for the simple ones and a FULL/INC model for the rest. Don't forget the INC ones if you want log truncation to happen.

If someone with SQL knowledge knows better, please jump in...

Post Reply