SQL 2012 :: Full Backup And Remove Old Log Backups
Aug 4, 2015
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 ?
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?
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 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?
We have just implemented a SQL 2012 always on environment. We have a primary and secondary server. I am confused about how to set up the backup plans. The application team was happy to tell me that in sql 2012 always on we can offload the backups to the secondary, thus reducing overhead on the primary server.
However, the secondary only supports copy only full backups. I am unsure how these would be useful in a disaster event? I could not apply any trx log backups on a copy only backup. This means I need to run my full backups on the primary server?
Can we backup our cluster databases directly to tape using native backups (without using any third party tool) ? It's SQL Server 2012 two node Active/Passive cluster. One of the DB will be huge in size, hence checking if we can directly backup from the cluster instance to a tape.
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?
We need to setup an AO availability Group for a database for which a full backup exists but the DB is in simple recovery mode now. If i change the recovery mode to full and try to configure AG will this full backup will be used or do i need to create a new full backup.
I am attempting to create a Test db from a full backup of the production db. With 2012, I cannot do it the the way i had done it in previous versions (and now i understand why because of Logical names).
The Test db runs in the same instance as Prod db.
I attempted to run this but come up with errors. This is what i executed:
RESTORE DATABASE TEST FROM DISK = 'E:<path>FULL.BAK' WITH REPLACE, RECOVERY, MOVE 'PROD' TO 'E:<path>TEST.MDF';
The errors are all cannot execute due to PROD is in use.
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?
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.
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.)
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.
Data got deleted on Friday evening, need to have database restored to FRiday afternoon and also some data has been entered on Monday, which needs to be there.
We take a full backup in the early morning and hourly transaction log back during the working hours for one database in the production server. The application team made certain changes to the design of the said database in their development server. The backup from the development server was restored to the production server during working hours. After the restoration should we take a full backup before next transactional logbackup? Would the transactional log backup with out a full backup after the restoration of a database be valid?
I have a database that is just over 1.5GB and the Full backup that is 13GB not sure how this is since we have compression on for full backups and my other full backups are much smaller than there respective databases...Now my full backup is taken every Sunday night and the differentials are taken every 6 hours after the full backup. Now I have been thrown into this DBA role with little to no experience just what I have picked up and read. So my understanding of backups are limited but what I think I understand is that we take a full backup and the differential only captures what changes in the database so my question is why is my database 1.5GB but my differential is 15.4GB? I have others database that are on the same instance and don't seem to have this problem. I also just noticed that we do not rebuild the index before a full backup like we do on other instances...
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?
heywhen i try to search an "noise word" it drop me an ERRORwhat i have done : - stop full text service- remove the words i want ,from noise.enu , noise.eng , noise.dat (@@language = u.s...) the files is in system32 and in program files...config .- start full text service-rebuild and after that re populate the catalog and it still drop me an ERROR !!! how can i resolve this prob ??? tnx tnx .
I recently moved a database from one server to another. One thing I didn't catch is that I had a Full Text Catalog on the old server.
Well, on the new server, the catalog is still pointing to a disk location that doesn't exist on the new server. I tried to remove the catalog but get an error: "Error 21776: The name 'Claims Catalog' was not found in the FullTextCatalogs collection....."
So, I go to the table and attempt to remove Full Text Indexing but get the same error with: "Error 20565: Database is not full-text enabled yet"
I tried to remove the indexing key from the table and get: "Invalid cursor state"
I even tried to fake a mapped drive with the path it was looking for and it still doesn't work.
Any suggestions other than dropping the table? (it has about 40,000 records).
I have a backup that runs every evening. I set the backup to expire in 7 days time and have it appended to an existing backup set.
When I look at the contents of the backup set I can still see backups which have expired and show the expired date in the past.
e.g. It is 23/11/2007 today and I view my backup set and can still see backups showing an expiry date of 22/11/2007.
I need to remove the expired backups from the set as I do not want the backup set file growing too large in size and therefore a pain to transfer off of the server to another location.
I tried to find somewhere I can remove expired backups from within Microsoft SQL Server Management Studio Express but am unable to locate anywhere to do this. I know you can view the contents of a backup set by selecting the database > Tasks > Backup and then Clicking 'Contents' button.
If my backup starts at 8PM and take 1 hour to complete, will the changes made to the database during that hour be captured in the full backup?
Stated another way, will my backup be a snapshot of: a) 8PM when the backup started b) 8PM with some of the changes made between the hour c) 9PM when the backup finished?
Anybody know the exact way SQL Server handles that logic?
I am using the Simple recovery model and I'm taking a weekly full backup each Monday morning with differentials taken every 4 hours during the day.
On Wednesday afternoon, a programmer ran a process that corrupted the db and I had to restore to the most recent differential. It was 5pm in the afternoon and a differential backup had just occured at 4pm. No problem, I figured.
I restored the full backup from Monday morning and tried to restore the most recent differential backup. The differential restore failed. Since I had used T-SQL for the initial attempt, I tried using Enterprise Manager to try again.
When viewing the backup history, I see my initial full backup taken on Monday plus all the differentials. BUT, on closer inspection, I noticed another full backup in the backup history that was taken early Tuesday morning. I can't figure out where this Tuesday morning full backup came from. It wasn't taken by me (or scheduled by me) and I'm the only one with access to the server. My full backups are usually named something like HCMPRP_20070718_FULL.bak. This erroneous full backup was named something like HCMPRP_03a_361adk2k_dd53.bak. It seemed like it was a system generated name. Not something I would choose. To top it off, I could not find this backup file anywhere on the server and when I tried to restore using this full backup, it failed.
Does anyone have any clues as to where this full backup might come from? Does SQL Server trigger a full backup on its own if some threshold is reached?
I ended up having to restore using the differential taken just before this erroneous full backup and lost a day of transactions.
