April 13, 2011 at 1:47 am
You need Windows Server Enterprise Edition to build a cluster, it can't be done with SBS.
-- Gianluca Sartori
April 13, 2011 at 2:57 am
Hi Gianluca Sartori,
But the Premium Edition of SBS includes the features of Microsoft SQL Server 2000. Then why it does not support SQL Clustering.
April 13, 2011 at 3:02 am
santosh Sai (4/13/2011)
Hi Gianluca Sartori,But the Premium Edition of SBS includes the features of Microsoft SQL Server 2000. Then why it does not support SQL Clustering.
In order to set up a SQL Server Cluster, you need a Windows Cluster, which can be built only upon an Enterprise Edition of Windows.
I'm sorry.
-- Gianluca Sartori
April 13, 2011 at 9:03 am
Thanks..
Is there any other way where I can take a SQL real time backup or installing SQL Clustering. I want to take a simultaneous backup of the SQL Live data, so that If my server ll down, I can restore the entire data.
April 13, 2011 at 9:10 am
I'm afraid you will have to set up a different thing.
Mirroring could be one. It depends on what you want to achieve, the downtime you can afford, the windows AND SQL Server editions you have.
Can you expand a bit more?
-- Gianluca Sartori
April 13, 2011 at 10:32 am
How can I setup a backup Server or SQL realtime backup, where If my main server will down atleast in 2nd server should back it up. And users shouldn't suffer
April 13, 2011 at 1:42 pm
Realtime backup is going to require some work. And money.
There isn't a good way to do this in SQL 2000. you can do log shipping, where you restore your log backup on antoehr machine, but this isn't real time. It can be close, every minute or two, but it's not going to be real time.
You can set up replication, but there's a lot of admin work here and you likely need a second SQL license.
I would suggest that you either do a lot of reading on the SQL 2000 HA options (and DR) or engage a consultant.
April 13, 2011 at 9:57 pm
Thanks.
But normally I am taking backup of Sql data through NT Backup in every half an hour. NT Backup supports any Microsoft product to take backup.
April 14, 2011 at 6:09 am
santosh Sai (4/13/2011)
Thanks.But normally I am taking backup of Sql data through NT Backup in every half an hour. NT Backup supports any Microsoft product to take backup.
I'm not an expert with NtBackup, but I suspect it would not take database backups, but only data files backups.
It's a very different thing. Did you ever try to restore any of those backups?
-- Gianluca Sartori
April 14, 2011 at 8:38 am
NTBackup should work, though you need to test. If you haven't restored to another machine, you are potentially not doing your due diligence. If you cannot restore those backups when an issue occurs, you might as well not have wasted the time doing them. Test.
There are issues, such as this one: http://support.microsoft.com/kb/903643, so be careful. Test regularly.
Also, you still need to run SQL backups, or make sure that you are running regular DBCCs on the existing database to look for corruption. Hardware fails. Detect this early.
It sounds as though you have not had a lot of experience in this area. I would really recommend you get a consultant for a few hours here and there to help you learn how to protect your system better in case of an issue.
April 14, 2011 at 9:04 am
I agree with Steve - if this is a production system you REALLY REALLY need to engage a qualified consultant. Given the questions you are asking and the lack of knowledge you have (nothing personal there, just an observation) you have absolutely no hope of developing and implementing a High Availability and/or Disaster Recovery plan for your company. I know of companies that no longer exist because they THOUGHT they could do those things by themselves and they found out they were wrong.
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
April 17, 2011 at 10:50 pm
Dear Steve and Kevin,
Thanks for the Suggestion. But I have tested the NT Backups and also we had a experience where the Server was totally virus affected and I have restored the OS and SQL with the Data and was working very smooth. Yes it took time to Format and reinstall the OS and to restore the backup.
But the Main problem is that am unable to recover/restore half an hour data because of my scheduled backup is running in every half an hour basis.
That's why I want to have a simultaneous backup data and also if possible Backup Mirroring Server. But for the same I need to invest a lot. I need to Upgrade my OS to Windows 2003 Enterprise edition. And also for the Backup Server.
Thanks & Regards
A.Santosh Kumar Sai.
Asst. Manger - Systems
Chrome Hotel
A Unit of Chocolate Hotels Pvt. Ltd.
April 17, 2011 at 10:55 pm
Dear Steve,
Also we are using SQL Backup to take the backup 2 times in a day. But I need a help and also some solution where I can have a Backup Database Server.
Yes regarding SQL I have not much knowledge. Because am looking after the IT Infrastructure here.
Thanks & Regards
Santosh
April 19, 2011 at 8:45 am
It's not clear what you mean with your backup schedule. You need to specifically state when you have an NT backup running and when you have a SQL backup running and what kind. Then we can help.
A cluster doesn't necessarily help you, especially if you have disk issues. The disk is shared. Mirroring is not an option with SQL 2000.
The best thing, from what I know, is for you to run log backups every minute or two. It won't prevent zero data loss, but it will minimize things. Most companies can cope with a few minutes of loss.
The big thing is to get the backups on another system by copying them immediately.
April 26, 2011 at 5:04 am
Hi Santosh,
The environment you have (W2003 SBS & SQL 2000 Std) is intended for a small business on a limited budget. Having chosen this option, there are limitations on the availability and data loss that can be achieved.
SBS is designed for fairly low availability. If a server fails you have to restore backups on to another server, and this means it will take a number of hours before you are running again if you have a spare server available, or a few days if one has to be purchased. Likewise for data loss, any data you enter into the system after the final working backup will be totally lost when you do a restore.
This level of availability and data loss was typically not thought to be a problem for small businesses even 5 years ago, but today almost all businesses want to be online all the time, and customers are not very forgiving if data loss occurrs.
I think you should look at your availability and data loss objectives from a business viewpoint. What amount of downtime can your business cope with before things turn to chaos. What amount of data loss can your business cope with before you no longer remember what changes were made since the last backup.
You should also consider that W2003 and SQL 2000 are no longer supported by Microsoft, and there is a declining pool of people who know how to put this type of system together. The fact you are running software of this age possibly means your hardware is a similar age, and therefore nearing the end of its working life. Any solution you decide to implement should aim to use currently supported software and new hardware, and the cost of this needs to be factored in to your plans.
It may be that moving from an in-house to a hosted solution would be a good way forward, but this depends on the reliability and speed of internet connections where you operate.
You should also look at how you can mitigate the impact of the gap between what your current solution can provide and what your business currently needs. Look at the data you would miss the most. I see you are in the Hotel business, so parhaps this critical data includes:
* Room booking grid
* Current outstanding customer billing
* Room cleaning schedule
* Restaurant schedule
If any of these items are critical, look at alternative ways of providing them. If your existing system provides this information in standard reports, get them run automatically every (say) 15 minutes to disk files and have the output automatically copied to some of your other computers. In this way if your server crashes then you still have immediate access to your business critical data.
If your current system cannot do this, it should be possible to fairly easily write queries to populate an excel spreadsheet with this data, and get the spreadsheets copied to some desktop machines.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
Viewing 15 posts - 1 through 15 (of 17 total)
You must be logged in to reply to this topic. Login to reply