Unsolved
This post is more than 5 years old
11 Posts
0
4670
January 17th, 2011 10:00
SQL incemental backup promoted to full, sometimes
Hello!
I have an SQL server scheduled to do full backup every day at 1h am, and incremental backups every two hours. force incremental is set.
Incremental backup is promoted to full several times per day, others are incremental.
Does anyone know hoe to avoid this promotion to full, what could cause it since no administrator is changing SQL settings (at least not on purpose)?
Thank you in advance!
0 events found
No Events found!


DavidHampson-rY
294 Posts
0
January 17th, 2011 11:00
If there are no full backups an incremental backup will run at level full - you cannot run an incremental backup unless you already have a full backup.
milena1
11 Posts
0
January 17th, 2011 12:00
The first backup (at 1am) is full.
Rest should be incremental, but some of them are full, some are incremental.
guenterH1
117 Posts
0
January 18th, 2011 00:00
Could it be the case that any third party backup (including Windows backup utility) is conflicting with NetWorker backup?
Please check backup log at the NetWorker client, this should tell you.
David_Hampson_90e289
2 Intern
•
243 Posts
0
January 18th, 2011 01:00
Do you have a completed successful full backup when the incremental begins?
milena1
11 Posts
0
January 20th, 2011 05:00
yes, I have full backups completed at 01:00 and 07:00, others are incremental, every 2 hours.
in Group log (sso file) I just have:
Database %s backup level forced to full
I have scheduled jobs doing shrink, for logs every 4 hours (at 0, 4, 12,16), for database files once (at 0:30)
Thank you in advance!
Regards!
David_Hampson_90e289
2 Intern
•
243 Posts
0
January 20th, 2011 06:00
In the admin guide it gives the following scenarios where an incremental backup will be promoted to a full backup:
milena1
11 Posts
0
January 20th, 2011 07:00
this is exactly why I have addressed to the community:
1. Full backup exists
2. Database is in full recovery mode, incremental backups are done before and after full backups
3. Database is not in emergency mode, during working hours users are using it
Let me rephrase the question:
1. Is it possible that for some reason Networker is not avere of full backup? Could shrink (or soe other maintenance task) cause Networker to think that there is no full backup, or that last backup was done by some other software? Is it possible that EMC Replication Manager cause this kind of confusion?
2. Is it possible that at one moment MSSQL is supporting TL backup, and at the other doesn't, without user / dbadmin interverntion during woking hours?
3. I don't suspect "emergency mode", but should I?
I have two database systems acting this way: two full backups each day, each server at different time.
Other databases have one full backup and 11 incremental, as they are configured to.
rovinabi
55 Posts
0
January 20th, 2011 09:00
Can you go into the SQL manager and check if there are any backups run using the SQL native backup tool? This kind of behaviour is seen mostly when a thrid party tool is used to backup the SQl in between a Full nad incremental backups taken using NetWorker.
HTH,
Rovin D'Souza.
Luis_Rogerio
116 Posts
0
January 21st, 2011 05:00
Hi Milena,
Check if any database is configured recovery model to SIMPLE, if yes change to FULL and try again.
Regards,
Luis Rogerio
milena1
11 Posts
0
January 21st, 2011 06:00
Database is in Full Recovery Mode, as I said, incremental backups are performed sometimes.
We have noticed that if we change the start time for EMC Replication Manager, time for incremental backup promoted to full is changed too.
I suppose that's the answer!