I am getting this weird problem with my backup job.
I have more than 1000 DB's on my SQL server stack. There is a weekly and daily backup jobs set to take the backup. Weekly jobs runs on every sunday and does the full backup and then the daily job does the differential backup.
Now I realized that the last Full backup of some of the databases is not updated.
I checked the job history and the job was successful without any error. When I check in the backup folder, the timing of the backup seems a bit doubtful e.g
26/10/2014 23:34 2,759,240,192 DB1 2014-10-26 23.19.59 Full.bak
26/10/2014 23:36 319,891,968 DB2 2014-10-26 23.34.46 Full.bak
26/10/2014 23:36 160,771,072 DB3 2014-10-26 23.36.17 Full.bak
26/10/2014 23:48 3,505,426,944 DB4 2014-10-26 23.36.59 Full.bak
27/10/2014 00:03 4,322,182,144 DB5 2014-10-26 23.48.12 Full.bak
***27/10/2014 00:25 7,266,648,576 DB6 2014-10-27 00.04.13 Full.bak
27/10/2014 03:31 67,190,649,344 DB7 2014-10-27 00.25.51 Full.bak***
27/10/2014 03:32 270,017,024 DB8 2014-10-27 03.31.19 Full.bak
There are some replication job runs at around 2 O'clock. I thought that may be the problem and I changed the time for my differential backup job a bit early so that it finishes before the replication job starts.
But the result is same . Job is successful. but most of the backups did not get updated and this time the last backup was taken at 19:36 and after that no backup at all.
Its really critical,Can someone please help me with what can be the reason for this ?
Your help is much appreciated.
I am using SQL server 2012
Thanks
Related
I have daily backups set up for all databases. The servers tend to get full of backups after a while and I have to go through and periodically clean it up. I would like to retain the daily backups for 30 days, then retain one backup weekly for 6 months, and then retain one backup monthly for 12 months. How do i set this up in SQL or outside of SQL? The retention needs will also vary between databases. Thanks in advance.
Create Three agent job FULLBACK_DAILY, FULLBACK_WEEKLY, FULLBACK_MONTHLY
Step 1 Take fullbackup for DB
Step 2 Cleanup old backup using powershell.
Scheduled them daily, weekly and monthly
Question: The retention needs will also vary between databases.
You can do this in the fullbackup step.
Good luck
I have 5 SSIS jobs running in sql server job agent and some of them are pulling transactional data into our database over the interval of 4 hours frequently. The problem is log file of our database is growing rapidly which means in a day, it eats up 160GB of disk space. Since our requirement dont need In-point recovery, so I set the recovery model to SIMPLE, eventhough I set it to SIMPLE, the log data consumes more than 160GB in a day. Because of disk full, the scheduled jobs getting failed often.Temporarily I am doing DETACH approach to cleanup the log.
FYI: All the SSIS packages in the job is using Transaction on some tasks. for eg. Sequence Cointainer
I want a permanent solution to keep log file in a particular memory limit and as I said earlier I dont want my log data for future In-Point recovery, so no need to take log backup at all.
And one more problem is that in our database,the transactional table has 10 million records in it and some master tables have over 1000 records on them but our mdf file size is about 50 GB now.I dont believe that this 10 million records should make it to 50GB memory consumption.Whats the problem here?
Help me on these issues. Thanks in advance.
I have this script to backup my sql server 2000 database:
BACKUP DATABASE [CRM] TO DISK = N'd:\CRM_BACKUP\crm.bak'
WITH NOINIT, NOUNLOAD, NAME = N'GUY_CRM_BACKUP', NOSKIP, STATS = 10, NOFORMAT
I want the backup to be for several days.
I thought about giving the name of the backup the day of the month
e.g. crm01.bak, crm02.bak.... crm30 or crm31.bak.
How can I do that please?
TIA
Guy
You can set RETAINDAYS to the number of days you wish to keep that backup. Since you are using NOSKIP (and NOFORMAT), SQL Server will not overwrite that backup until it has expired. At that point, you could also institute a naming standard like you are mentioning, or set a maintenance plan to erase backups older than a certain age.
we have a huge (17 gig) MSDE backup file that have discovered has been appending nightly for the last 4 years.
We had a database failure last night and now we need to restore the database.
We tried a standard restore but it restored the database info all the way back to 2008. Which isnt an accurate reflection of the state of the database as it was last backed up.
How do we restore back to just the last backup (or even a date/time) and not all the way back to 2008?
cheers
Buzz
openthe log file, findout the date of the backup you want then use the script
RESTORE DATABASE [restoretest] FROM DISK = N'C:\folder\backfile.bak' WITH FILE = 1494
GO
hurray a working answer.
Buzz
We run SQL Server 2005 and have a database that's about 100 GB (the MDF is 100GB and the LDF is 34 GB).
Our maintenance plan takes a full database back up every night. It's set up to
This backup size is usually around 95-100 GB but it all of a sudden grew to 120 GB, then 124 GB then 130 GB then back to 100 GB over 4 consecutive days.
Does anyone know what could cause this? I don't believe we added and then removed that much data in such a short period of time.
If your backup is larger than the MDF, this means you have a lot of log activity recorded too. SQL Server notes data changes that happen during a full backup and does a "mini" log backup to capture this.
I'd say that you need to change Index maintenance and backup timings