Realize necessity of full backup with MS SQL integration when starting incremental session

Idea ID 1658053

Realize necessity of full backup with MS SQL integration when starting incremental session

DP integration for MS SQL should realize that a full backup is necessary in advance when triggered to run a differential or incremental backup and no full backup was done before. Currently the session ends with an error.

Example: New database, new backup specification, first job started by schedule, schedule triggers incremental backup, no full backup in history available to refer to. DP session does not switch to full backup like file system backup does.

Advance: Correct backup from the beginning, manual intervention not necessary, restore possible from the beginning.

2 Comments
Micro Focus Contributor
Micro Focus Contributor
Status changed to: Waiting for Votes
 
Trusted Contributor.
Trusted Contributor.

Yes, this is needed.  We have frequent MS SQL backup fails, just becuase the DBA has had to trncate the transaction log file.  It would be nice just to have a warning, or maybe minor error then switch to a full backup for that particular DB.  Maybe have this tunable via global configuration setting.

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.