But i have one issue bothering me, it will be great if someone can help me out on this
1. I take full backup on Monday 8 pm which ends at 9.30 PM
2. Diff Backup starts at 10 PM every 2 hrs till Tuesday 7.59 PM
3. Transactional Log backup is happening every 10 min till tueday 7.59 PM
Now when i restore it in the same order i get error that Log in the set is too late to apply. I have recemmonded by team to stop log backup on the time they start full backups and take transactional log backup only after differentials are restored. Now is this a correct suggestion???
Also appendin the differential backup is a good idea or overwriting them is a better approach if Database is backedup every night and Differential occurs every 2 hrs.
Regarding backups. The first available time to do a full backup is at 11:00pm which also applies to diff. backups. How often does the trans. logs need a back up?
we have MS SQL 2005 Standard and we have setup Maint. Plans with the SQL Server Management Studio front end.
i didn't set this up, so if it's completely crazy, i'm just the messenger :)
we have two maintenance plans:
maintenance plan A (to generalize) runs its full back up, then generates its differential backups and transactional logs.
then maintenance plan B runs its full back up and generates differential backups on a second drive without transactional logs.
what appears to happen with this is MS SQL will only let us restore from the most recent differential, so if maintenance plan B's differential ran last, it renders maintenance plan A's differentials essentially useless.
the reason it was setup this way was that in theory, we wanted A to backup to one drive and B to backup to a drive that gets rotated for offsite backup.
if we're breaking diff backups, this isn't optimal. anyone have a better method for creating backups on primary backup drive and a swap out drive?
The space allocated to the Log in question is 180 GB. During this time period I was running TLog backups every 5 minutes, yet the log continued to chew through to 80 GB used, even after the process was complete and a final TLog backup had been taken. It continued to stay very large until the Full backup was complete -- or something else that I'm unaware of completed. Like every other DBA I typically take a TLog backup to shrink the log, but what appeared to be the case here was the Full completed and it released the used log space. All said, will Transaction Log backups not free up the log during Full backups?
I'm having difficulties copying a production DB to a new computer using backup files. The production computer had tempdb on the D: drive, the new computer is much smaller and only has a C: drive. I've successfully restored the Master DB backup but now the database will only start with the (-F) parameter. I know how to Alter the DB to move the tempdb, but I cann't get the DB to start while Tempdb is pointed to the D: drive
I run two different types of backups on the same database.
A monthly full and nightly diffs appending to the same full file - file 'A'
A weekly full with 10 min trans log backups appending to same file - file 'B'- during working hours.
2 strategies, 2 backup files.
These are new strats that have gone live this week - tuesday in fact. The monthly and weekly both ran fine on tuesday as did the nightly diff and all the TS backups througout the day. last night - Weds - the nightly diff failed with the following error:
"
Executed as user: <USERNAME>. Cannot perform a differential backup for database "objectstore", because a current database backup does not exist. Perform a full database backup by reissuing BACKUP DATABASE, omitting the WITH DIFFERENTIAL option. [SQLSTATE 42000] (Error 3035) BACKUP DATABASE is terminating abnormally. [SQLSTATE 42000] (Error 3013). The step failed.
"
Whilst the error is perfectly legible I dont understand what its implying - cant I add multiple Diff backups to the same full backup OR is my weekly / 10 mins on the same database (but to a diff backup file) ballsing things up for me somehow? If this is the case how come everything ran fine on tuesday night?
Any help gets beers.
THanks
Alastair Jones.
"A computer once beat me at chess - but it was no match for me at kick boxing" - Emo Phillips.
I backup a database at the begining of each month with a full and then do nightly diffs on it.
For the same database I run daily fulls and 10 minute log backups.
these two backups create / append to two different backup files.
The problem im having is that I cant restore the Differential backup set. SQL seems to restore the full just fine but alwasy throws an error when its about to start to retore the last diff. now forgive me but I clicked OK on the message and I cant find any record of the error in the logs but its something like:
"SQL cannot restore the database as the database has not been restored to the previous correct state"
is my 10 min TS log backups screwing up the DIff chain somehow?
this is really doing my head in. any help appreciated.
"A computer once beat me at chess - but it was no match for me at kick boxing" - Emo Phillips.
We lost (Couldn't find ) the full backup on a Tape we were supposed to use for restore, but seems like they lost it. All we have is a Diff backup. Wondering if that is any good at all .
WE ARE DOWNLOADING THE BACKUP FILE FROM OTHER BRANCH OFFICE AND THE FILE SIZE IS GROWING LIKE HELL SO I AM CHANGING THE BACKUP POLICY TO DOWNLOAD THE DIFFERENTIAL BACKUP FILES EVERYDAY. BUT EVEN THE FILE SIZE GROWS DAY BY DAY UNTILL WE TAKE THE FULL BACKUP THERE. SO I WANT TO TAKE A DIIFERNETIAL BACKUP AND THEN IMMIDIATELY A FULL BACKUP AT THE REMOTE SERVER END. SO MY NEXT DIFFERNTIAL BACKUP WILL HAVE THE DATA OF ONLY PREVIOUS DAY. FOR THIS I AM SCHEDULING A JOB WHICH FIRST TAKES A DIFFERENTIAL BACKUP AND THEN IMMIDIATELY FULL BACKUP EVERYDAY AT 12.00AM. BUT I HAVE A CONCERN.. WHILE TAKING THE DIFFERENTIAL BACKUP ANY TRANSACTIONS THAT ARE TO BE COMMITED WILL NOT COMMIT UNTIL THE DIFFERENTIAL BACKUP COMPLETES. BUT IMMIDIATELY I AM STARTING FULL BACKUP. IS THERE ANY CHANCE THAT A TRANSACTION GETTING COMMITTED IN BETWEEN THESE TWO STEPS. IF SO IS THERE ANY WAY .. NOT RELEASE THE DATABASE UNTILL THESE 2 BACKUPS ARE COMPLETED?? I AM RUNNING IT AS A JOB.. ANY SUGGESTION??
I have daily scheduled full backups of each database and log backups scheduled for every 2 hours. My question is should they be scheduled for overwriting or appending? I have always had them set as overwrite, but I don't know if that is correct? Any recommendations would be appreciated
Does the full and differential backups have to be in the same location or can I do a once a week full backup on one drive and everyday differential backups on a different drive?
Every Sunday morning (a different time each week) there is a full backup created for every database on the server. The backup is not a scheduled backup from any maintenance plan or SQL Agent job. The backup set is unrestorable and has a strange name in the format of 'DBNAME_00_12c95fb7_399d_41ce_9a0d_b5728b6a00ba_'
Because this backup is listed as the last full backup and will not restore, it is causing a problem with our disaster recovery plans as nothing will restore from this point forward to the next full backup.
Does anyone know how a backup record like this can get created, and/or how to find the source. The backups are listed in the backupsets table in msdb - are there other system tables that may hold some clues as to the source of these backups?
I make two full backups on Oct 1 and Oct 10. I want to restore the server to a state in Oct 5. So I just do as follows:
1.Perform a transaction log backup on the server on Oct 23. I have never backup transaction log in the past. 2. Restore the server with Oct 1 full backup with NORECOVERY option. 3.Try to restore to the point at Oct 5 12:00, with the transaction log.
But the restore fails and SQL Server said the transaction log does not contain the point. The point is too early. Why? Also my .LDF file is about 13G, but the transaction log backup is only 200MB. Why?
I am running a full backup quarterly using "with init" to overwrite the existing file if it is still on the server. Then I run a differential back weekly using "with init". Finally I run a transaction log backup nightly using "with init".
My question is should I be using "with init" for the transaction log backup or allow it to accumulate until the next differential backup?
Hi sql server experts. This is a beginners question.
Let's say, I run a full backup at 4:30 am it takes usually 35 minutes to finish.
I want to schedule a differential backup to run every hour.
Should I start this job at 5:10 after the full backup finishes? or it doesn't matter? I am confused about timing.
Let's say my full back up takes 1 hour to finish, that means that when the differential backup runs the full backup will be still running, so in case I need to restore the database, can I use this differential from 5:10 or the differential from 6:10.
Same issue with the transactional, the job runs every 30 minutes, should I started after the differential is done?
I am so confused, what happens with the backups jobs that run while other backups are running?
Is there a way to suppress or re-direct the messages that result from a tran. log dump? We're running a tran. log dump every 15 minutes in prod. and the errorlog is really cumbersome to look at.
(In another RDBMS I worked with all backup messages went to a separate error/message log.)
We have a SQL 2012 server instance that has log shipping set up to another SQL 2012 server to provide a warm standby for a forward facing application. The databases on the primary server occasionally are required to be backed up and restored to a development environment, completely different server. Is there a way to schedule full backups with log shipping enabled?
I am in plan to implement following for backup of one of our database Enable Full recovery mode
1- Create full backup nightly 2- Create transaction log backup after every 25 min
as I am taking full backup every night, I think I can remove transaction log file backups at the time of full backup, as we can apply transaction log backup over full backup.My question is regarding removal of transaction log backups.
-Should I remove all transaction log backups and then execute full backup? -Should I execute full backup and remove all transaction log backup older than 24Hrs ? -Do I have to consider SCN or related info before deleting any transaction log backup ?
I make two full backups on Oct 1 and Oct 10. I want to restore the server to a state in Oct 5. So I just do as follows:
Perform a transaction log backup on the server on Oct 23. I have never backup transaction log in the past. Restore the server with Oct 1 full backup with NORECOVERY option.Try to restore to the point at Oct 5 12:00, with the transaction log.
But the restore fails and SQL Server said the transaction log does not contain the point. The point is too early. Why? Also my .LDF file is about 13G, but the transaction log backup is only 200MB. Why?
I make two full backups on Oct 1 and Oct 10. I want to restore the server to a state in Oct 5. So I just do as follows:
1.Perform a transaction log backup on the server on Oct 23. I have never backup transaction log in the past. 2. Restore the server with Oct 1 full backup with NORECOVERY option. 3.Try to restore to the point at Oct 5 12:00, with the transaction log.
But the restore fails and SQL Server said the transaction log does not contain the point. The point is too early. Why? Also my .LDF file is about 13G, but the transaction log backup is only 200MB. Why?
I have a few Log Shipped DBs that are working great.
Currently they are set to fire off every 15 minutes 24/7.
My question is this ... I need to get FULL backups of the source DBs in order to restore them on certain Dev boxes.
If I were to execute the full backup on one of these Log Shipped DBs ... how would it affect the log shipping process?
Is there a special method to accomplish this?
As a side note, what would be some concerns/issues if in being able to create the FULL backups and not interupt log shipping, I were to create the backup using a 3rd party tool like Quest LiteSpeed?
I sure wish we were on Enterprise, then I could create a mirror and then snapshot off it to create my backups BUT ... that is not the case as we stand today.
I need to write a 'select' statement to fetch data from different tables, which are located on different servers. Can any one help in writing this 'select' statement with out moving the tables on to same server.
I am setting up Availability Groups and I want to use the secondary replica to perform the full copy_only backups to reduce the load on the primary replica.But what is the best way to check for successful full backups on Availability Group databases?
Previously I could check the system table msdb.dbo.backupset but this is not available for copy_only backups.So I wonder how people are monitoring that their full backups have been successful?
Do you just check that the SQL Agent job that runs the backup was successful?
Or do you search the SQL Server Error Log for entries like "Database backed up. Database: xxx" where database xxx is in an Availability Group?
Using Ola Hallengren's scripts I do a full backup of a database on a Sunday. Then differential backups every 6 hours and log backups every hour. I would like to keep a full week of backups based off the full backup done on Sunday. Is there a way for me to clear out the diff and log folders after the successful full backup on Sunday nights?
Hi! I need help! We have 98% transact log full. After run DUMP TRANSACTION WITH TRUNCATE ONLY it still doesn't purge the log. How can we resolve problem.
I created a procedure called 'Longtextprocedure'. The length of this procedure is 650000 characters long. When I was giving the following query - select len(routine_definition) from INFORMATION_SCHEMA.routines where ROUTINE_NAME = 'Longextprocedure'; Length is showing as '4000' characters long. It is not showing the remaining part of the procedure, it is showing upto the 4000 characters of procedure code. But when you execute the procedure(exec 'Longtextprocedure') it is showing the exact result.
My question is i want to read all the 650000 characters long procedure code{select routine_definition from INFORMATION_SCHEMA.routines where ROUTINE_NAME = 'Longextprocedure'} to a variable which is varchar(max).
When i am trying to read the whole procedure code it is taking 4000 characters of data into the variable not the whole. Is there a way to read the huge procedure code into the variable?
Code:-
CREATE PROCEDURE FAKEPROCEDURE @procName VARCHAR(50) --@procName is 'Longtextprocedure' AS BEGIN DECLARE @routineDefinition VARCHAR(MAX); DECLARE @replaceToChar VARCHAR(MAX);
[Code] ....
When i am trying to execute the line EXEC(@dupliacteRouteDef), it is showing like there is no procedure defined. This is due to '@dupliacteRouteDef' variable is having 4000 characters of data not the whole data. Is there a way to read whole procedure data into the variable irrespective of the length of the string?
I have an SSIS Package which Retreives Data using a SQL Query like below
select a.* from dbo.test a (nolock) JOIN dbo.test1 b (nolock) ON a.DetailsId = b.DetailsId JOIN dbo.test c (nolock) on c.DetailsLineId = b.DetailsLineId where convert(date,c.CpPlacedDate)>? and convert(date,c.CpPlacedDate) < convert(date,GETDATE()) and c.PartnerCode in ('akakak07')
The CpPlacedDate DataType is Datetime. After the Successfull Execution of SSIS Package the final output results in destination is lesser than source.
The Maximum of cpplaceddate in the Destination for a particular date is '2015-06-13 23:46:08.923'
The Maximum of cpplaceddate in the Source for a particular date is '2015-06-13 23:59:14.873'
