Highlighted
Absent Member.
Absent Member.
3124 views

MS SQL Server Backup - Errors with new databases

Jump to solution

Hi,

 

we always get errors with transaction log backups with Dataprotector 6.11 when new databases are created on SQL Server and there is not a full backup executed before.

In former tests Dataprotector was switching in such cases automatically to full oder differential backup. But now the backup job on the SQL Server instance is aborting for this database and is continuing with the next databases.

 

Is this a bug or an option I can configure ?

 

This is the message I get in such cases:

 

Normal] From: OB2BAR_New_0@sqlserver.test.com "(DEFAULT)"  Time: 22.08.2012 10:00:46  Starting OB2BAR Backup: sqlserver.test.com:/(DEFAULT)/New/0 "MSSQL"

[Normal] From: OB2BAR_Main@sqlserver.test.com "(DEFAULT)"  Time: 8/22/2012 10:00:46 AM  Starting backup of database New. Required backup type is transaction log (incremental).

[Normal] From: OB2BAR_Main@sqlserver.test.com "(DEFAULT)"  Time: 8/22/2012 10:00:46 AM  SQL statement:  BACKUP LOG (New) TO  VIRTUAL_DEVICE = "Data Protector_(DEFAULT)_New_10_00_16"  WITH NAME = 'Data Protector: 2012/08/22 0540', BLOCKSIZE = 4096, MAXTRANSFERSIZE = 65536;

[Warning] From: OB2BAR_Main@sqlserver.test.com "(DEFAULT)"  Time: 8/22/2012 10:01:46 AM  Error has occurred while executing a SQL statement.  Error message: '<Microsoft SQL-DMO (ODBC SQLState: 42000):1076> [Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP LOG cannot be performed because there is no current database backup. [Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP LOG is terminating abnormally.'

[Normal] From: OB2BAR_New_0@sqlserver.test.com "(DEFAULT)"  Time: 22.08.2012 10:01:48  Completed OB2BAR Backup: sqlserver.test.com:/(DEFAULT)/New/0 "MSSQL"

[Major] From: OB2BAR_New_0@sqlserver.test.com "(DEFAULT)"  Time: 22.08.2012 10:01:48  Aborting connection to RSM. Abort code -2.

 

 

Thanks and regards

_K_

Tags (1)
0 Likes
1 Solution

Accepted Solutions
Highlighted
Absent Member.. Absent Member..
Absent Member..

Hi,

 

this is working as designed. In help you can find: Trans - When you select this backup type, you must ensure that a full backup exists in the IDB (found in DP 6.20 and 7.01 help).
Meaning it will no switch automatically to full backup. So make sure you always have a full backup before starting a transactional backup for a new database.

 

 

 

Best regards

Daniel

-----------
Please assign Kudos - How to assign...

View solution in original post

2 Replies
Highlighted
Absent Member.. Absent Member..
Absent Member..

Hi,

 

this is working as designed. In help you can find: Trans - When you select this backup type, you must ensure that a full backup exists in the IDB (found in DP 6.20 and 7.01 help).
Meaning it will no switch automatically to full backup. So make sure you always have a full backup before starting a transactional backup for a new database.

 

 

 

Best regards

Daniel

-----------
Please assign Kudos - How to assign...

View solution in original post

Highlighted
Absent Member.
Absent Member.

Hi Daniel,

 

thanks for this valuable info.

 

I mixed up this behaviour with databases which are in simple mode. There this automatically switch at transaction log backups is proceeded ...

 

 

Thanks

Florian

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.