June 30, 2009 at 8:53 am
How often are you doing log backups? What's the max amount of data that's allowed in the case of a disaster?
Oh, you are doing this testing on a test server? The way things read, it almost sounds like you're planning to do this on live. I hope I'm misreading.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 1, 2009 at 12:46 am
I'm doing log backups once a day; its a very small database where the information rarely changes. However it is the only system which does have a true test database and is live. The vast majority of the databases on SQL Server 2005 are development databases where the developers are not particularly bothered if they crash.
However we will be moving two very large and mission critical systems onto SQL Server 2005 in the future. This is why I'm playing around with this system's test database to find the best backup strategy where I can return to a point in time. When I go and speak to the Infrastructure manager about the tape backups, I want to have tried all possible combinations.
Madame Artois
July 8, 2009 at 4:43 am
After doing some more testing with different backup strategies, I have discovered a rather large problem which may explain my confusion.
We have TSM backup which backs up every server every night. This overwrites the SQL backup full database backup so there is no start to the restore chain. I can obtain a SQL server backup if I schedule it for the early hours of the morning after the TSM backup and can restore to that point only (using the most recent option). However the next night the TSM overwrite happens again.
The whole issue has been sent through the management.
What fun!
Madame Artois
July 10, 2009 at 12:58 am
S Hodkinson (7/8/2009)
We have TSM backup which backs up every server every night. This overwrites the SQL backup full database backup so there is no start to the restore chain. I can obtain a SQL server backup if I schedule it for the early hours of the morning after the TSM backup and can restore to that point only (using the most recent option). However the next night the TSM overwrite happens again.
cant the name of two backups be different so that they dont overwrite each other? also, can u elaborate more on TSM backups?
If you're referring to tran log chain, full backup do not break the log chain so you can still do point in time restores.
July 13, 2009 at 1:32 am
Sorry no you cannot rename the backups. TSM is a IBM product which does have a SQL element and as such overwrites everything. We have now been requested to stop backing up the transaction logs
It seems that the TSM will backup and restore everything in the future
Madame Artois
July 13, 2009 at 2:54 am
S Hodkinson (7/13/2009)
We have now been requested to stop backing up the transaction logsIt seems that the TSM will backup and restore everything in the future
Just to clarify, the TSM application will take full backup as well as tran log backups in future right?
July 13, 2009 at 3:20 am
Yes it will
Madame Artois
Viewing 7 posts - 16 through 21 (of 21 total)
You must be logged in to reply to this topic. Login to reply