I am trying to implement a plan for a SQL7 database that is used by the company I work for. Having read the SQL manuals I have come to the following conclusion:
I want to do a complete backup of the database at midnight and do a transaction log backup every 30 minutes between 7am and 7pm. I am hoping this will allow me to 'undo' any user mistakes and roll back the database changes to the last transaction log backup.
The questions I have are:
1) By backing up the transaction log every 30 minutes, will this then give me the ability to 'roll back' the database to the last time the transaction log was backed up (i.e. 30 minutes max) ?
2) How do I load the transaction log back in ? (i.e roll the database changes back). A simple Restore operation (with truncate ???)
Backup : Full and Transaction log. Hardware : Clustering, RAID
I am not sure about what all need to be Scripted for having a good disaster recovery plan?? Scripting:: tables, views, defaults, rules, users, roles, permissions Backup : Triggers, Stored Procedures
Hi, Im going to set up a disaster recovery plan for SQL-servers at my company. Does anyone know where to find a template for this ? Something to help me that describes what you must write down and so on ?
Please email me besides answering at discussion board.
we are using sql server 2000 and it's on a remote system. One of the databases "Dbase1" went to Suspect mode. when we checked both the .mdf and .ldf files were missing from the Server. they were not there at all. Is there any way to recover the databse. To make it more secure what are the possibilities which we can use so that in future we should be able to restore our databse.
Can any one please share the sample disaster recovery plan. I dont know what I have to include in it and how to prepare it. Your help will be highly appreciated. Thanks in advance...
We have a client which they have production 2 node cluster environment. On it around 200 databases with single SQL instance.
Now client wants disatster plan for these 200 database. In these 200 database 3 db's are around 80 GB each databases remaing are less than 5 DB.Note: All these 200 db's are having produciton sites (i mean to say each db is having single site)
For this DR paln clinet is going to provide other DR server,they wants to setup DR between exsting produciton cluster instance to this DR server.
So in this case we have suggest SQL server AlwaysOn availability group.
Here my main question is can we keep all these databases in single AG? .If yes, guidlines to move up. if not, do we have any limitations.Also, best method to setup for this DR plan.
I am new to always on management, I would like to know if exist a best practice for configuring maintenance plan on a alwayson system (two nodes) or is just running the maintenance plan wizard on both nodes.
I currently work for a company that has had a "family business" mentality for many years. The only trouble is, it has grown into a fairly large company over the years and that mentality just doesn't cut it anymore (We have around 200 employees in 2 offices, and 25-50 remote users).
I have recently taken over the role of System Administrator, and I'm having a lot of trouble trying to get everything under wraps. There are a LOT of un-documented things happening with our database/web server, and in order to keep things safe & secure, I need to try & flesh out what those mystery settings would be. I feel that NOW is the time to get some solid documentation down, to protect my ass before some critical failure happens.
I'm wading into unknown waters here, and I'm hoping that somebody who's "been there" might have some tips to make my life a little easier.
I have an IBM Bladecenter, and a spare blade with which I can use to re-produce as close to a mirror copy of our system as possible. I have installed windows 2003 /w SQL2000 and restored a full backup of our databases and imported all database user accounts, and logins. What about Maintenance Jobs? Error Logs? Patches/Hotfixes? Service accounts? Membership roles? System databases? ODBC Sources? Services? Startup Scripts? I'm sure the list could go on & on... What are some of the crucial details I should look into?
Has anybody been in this boat before having little knowledge of what was built before you arrived, and have any insight on how to get through this without too much headache?
Pages on a full recovery model database corrupted, need to ensure data loss is minimal for restore operation am thinking about restoring the latest full backup.
We have an issue with a 3 node SQL 2012 Always on availability group. Normal operation is node 1 (primary replica) with node 2 and node 3 as secondary replicas.After some patching, SQL wasn't running on node 1 hence the AG flipped over to node 2. This went unnoticed for some time and the transaction log for one of the AG databases became full on node 2 and node 3. (I think this is because it couldn't commit the transactions on node 1 so couldn't truncate it's t-log?) The DB is using synchronous replication btw.So I started SQL on node 1 and flipped the AG back to node 1 (with a data loss warning but I accepted this).Now the issue is that on node 2 and 3, the DB in question is stuck in a "Reverting / In Recovery" State. I've tried various commands such as ALTER DATABASE SET ONLINE, RESTORE DATABASE WITH RECOVERY etc but these fail stating unable to obtain a lock on the DB.
The weird thing is that on node 1 the state of the DB is "synchronised".how to resolve this issue on node 2 and 3? I've left them overnight (in case they were rolling back transactions, the DB is fairly large) but nothing seems to have happened. remove the DB from the AG in node 2 and 3 and add it back in again, ie recreate the replication?
Last week I backed up my SQL Server by using BE 2012. I named the file "SQL Server BAK" which contained copies of my SQL Server databases. A few days ago I lost some part of my data due to accidental deletion. I backed it up, so I tried to restore the database from the .bkf file. The problem comes here, when I try to to restore my .bkf file, it becomes inaccessible.what causes this?
Running SQL version 7 on "Terminal" Server I have a database marked in Load Receovery and we are unable to get to it. We tried MS SQL document on how to but we are still unable to recover it!
hai! i have a database which crashed recently(26th sep 2007).my last backup is on 14 sep 2007.i have restored database after two days.Now i have a database (old) with data upto 14sep 2007 and from 26sep to till date.(data from 14sep to 26sep missing).I restored database on 28th with a new database name which has data upto 26th sep 2007.how to attach these two databases to a single database to have data from beginning to tilldate.
Hi, I made an UPDATE query without specifying any criteria so I had more than 1500 records have been changed and I cannot undo the UPDATE. Is there any way I can recover the data UPDATE from the Transactions Log. I did not back up the database lately so what is the appropriate solutions for this?
Is there a way to Revover a Sql Server 2000 database in the absence of the backup file(the backup file got overwritten). Does Sql Server do any automatic Transaction logging?
SQL Server 2005 Database, So I want to know about Database Backup and Pointing Recovery concepts..so can u please help me and any send me related documents...
--- Thanks, Nageswar.V New Horizons Cybersoft Ltd +919848854114 : nageswar@nhclindia.com
Hi,I'm no where close to a SQL Server expert but we're using it as a back endto another application.I lost a PC that had MS SQL Server 2000. I was able to recover the .MDF and..LDF files but nothing else. How can I restore these files to another SQLServer installation on another PC. When I tried to attach them they are notrecognized as valid files (I get the red X instead of the green CHECK).Is this a basic security function that I'm not going to get around or shouldit be possible? Do the .mdf and .ldf files contain specific info about whatPC they were created on?Are there third party apps that might be able to at least extract thetables?Thanks,WH
Is there a way to check the status of a database in recovery. Like how far along it may be. If not is there a way to stop a database in recovery and just drop it.
Our server ran out of disk space during a stored procedure process. We were able to free up some space, stopped all SQL services, restarted all SQL services and now SQL Management Studio shows the database to be in recovery. Is there a way to monitor this to ensure progress is being made and to estimate when it might complete?
What does it actually mean when the database is in recovery? My database has been in recovery overnight. What is normally going on in this situation. Should I wait or take more drastic action?
I had to change the path of .mdf and .ldf files, so I decided to:
1) Take offline the database
2) run the quey ALTER DATABASE... MODIFY to change the path
3) Bring online the database.
The last step hung up (with no errors) and left the database In Recovery.
When I tried to stop and restart sql server other databases changed their status In Recovery...
Here is a dump of Errorlog files
2007-08-26 18:13:29.28 spid24s Starting up database 'DbOrdini'. ... ... 2007-08-26 18:13:30.09 spid24s * BEGIN STACK DUMP: 2007-08-26 18:13:30.09 spid24s * 08/26/07 18:13:30 spid 24 2007-08-26 18:13:30.09 spid24s * 2007-08-26 18:13:30.09 spid24s * Location: "logmgr.cpp":5334 2007-08-26 18:13:30.09 spid24s * Expression: !(minLSN.m_fSeqNo < lfcb->lfcb_fSeqNo) 2007-08-26 18:13:30.09 spid24s * SPID: 24 2007-08-26 18:13:30.09 spid24s * Process ID: 1380 ..... ..... 2007-08-26 18:13:30.40 spid24s Error: 17066, Severity: 16, State: 1. 2007-08-26 18:13:30.40 spid24s SQL Server Assertion: File: <"logmgr.cpp">, line=5334 Failed Assertion = '!(minLSN.m_fSeqNo < lfcb->lfcb_fSeqNo)'. This error may be timing-related. If the error persists after rerunning the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted. 2007-08-26 18:13:30.40 spid24s Error: 3624, Severity: 20, State: 1. 2007-08-26 18:13:30.40 spid24s A system assertion check has failed. Check the SQL Server error log for details
Could it be dangerous trying to kill this process ? If not, what is the best way do to it ? From Sql Server Activity Monitor (spid 24) or from Task Manager ?
Hello,I am working on a web site which will use SQL 2005.I am planing my first SQL database and I am looking for advice.1. There will be two types of users: students and professors.2. Both users types will have login information. (Username, Password, AccessLevel) 3. The remaining information on students and professores is different. Student (Name, Email, Phone, ...) / Professor (Name, Email, Phone, Subjects, ...)4. Professors can publish documents. Each document has some info (Type, Title, Description, ...)My plan in this moment is to:A. Create the tables Students, Professors, Login and Documents.B. Students table would be connected to Login table. Professors table would be connected to Login table and Documents table.C. The field [Type] in documents table should include the type or should I create a table DocumentsTypes where I add codes for each type. I have seen this. What is the advantage?Can someone give me some advice?Thank you Very Much,Miguel
We are using a database maintenance plan to backup and reindex our db's. Up until the end of last month this was working perfectly - however now it has stopped deleting the old backups (even though we have checked 'Delete files over 1 day old').
Does anyone have any ideas as to why they are now being deleted - and how we can remove them automatically - has something been corruped? Would it be a case of creating a new maintenance plan?
I have a Database Maintenance Plan that back up some databases and delete old backup files that more than two day. Can any one have idea which action is first, backup or delete old files?
Overview of my database: size - 45 GB, Full Recovery Mode, Log shipping ever 15 minutes; Full Backup nightly; Optimization and integrity checks on Sunday night.
The Database takes a transactional log every 15 minutes and ships it to our failover database. Usually these are small logs and are executed in matter of seconds. On sunday night there is a problem. The optimization job (part of DB maintenance plan) runs for 3 hours and during this time the transactional log backup continues to runs and takes close to 4 hours of complete. When the tran log completes its close to a 30 GB file and this is causing problems with space and shipping. This also causes the failover server to be out of sync and at times we have to re setup log shipping.
Does anyone know if there is a way to get around this problem. Appreciate all help and comments.
I need to create sql 2005 standard maintenance plan for system and user databases and database maintenance plan should include Reorganize index task, full backup task, maintenance cleanup task(for backup files), history cleanup task.
What should be the tasks order ? please let me know....I have to complete this on 8 servers by 11/16/2007 10 AM PST
In sql 2000 database maintenance plan, any rebuild index task is there ??
I need to create sql 2005 standard maintenance plan for system and user databases and database maintenance plan should include Reorganize index task, full backup task, maintenance cleanup task(for backup files), history cleanup task.
What should be the tasks order ? please let me know....I have to complete this on 8 servers by 11/16/2007 10 AM PST
In sql 2000 database maintenance plan, any rebuild index task is there ??
We have a requirement to build SQL environment which will give us local high availability and disaster recovery to second site. We have two sites- Site A & Site B. We are planning to have two nodes at Site A and 2 nodes at Site B. All four nodes will be part of same Windows failover cluster. We will build two SQL Cluster, InstanceA will be clustered between the nodes at Site A Server and InstanceB will be clustered between the nodes at Site B, we will enable Always On Between the InstanceA and InstanceB and will be primary owner where data will be written on InstanceA and will be replicated to InstaceB. URL....Now we want we will have instanceC on the Site B and data will be writen from the application available on Site B, will be replicated to the instance on the Site A as replica.
I have in production, the database maintenance plan that runs the nightly backups. I want to restore this to a completly different server I am setting up for testing. What is the best way to restore a backup on one server (that was done using the maintenance plan) to another server? I tried just mapping a drive and then forcing a restore, however, I got some error message about an ID or something. Maybe I need to do it through query analyzer and there is an easier way to force it? thanks!
Our Database Maintenance Plan has stopped backing up the database. I can manually backup the database but the plan does not work. We tried creating a new plan but the new plan is not backing up either. Any ideas would be appreciated. Thank you for your help!
