Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Sarat
Constraint Violating Yak Guru
265 Posts |
 Posted - 2003-10-23 : 18:57:45
|
| Hello, Since space was real big issue for quite some time, management answered our prayers and now we are implementing SAN for our servers.As a DBA, all I am concentrating on is space for the databases I maintain and quick n easy recovery procedures.1. I would like to know if you have any DOs and Don't DOs or anything I can ask for before it is too late.Also my server admin is talking about just making n keeping database snapshots instead of logshipping and multiple (i keep 2 days bck files on the disk) backup files. He also mentioned we could keep our test databases (we have 4 test dbs on pur tst server) on different blocks/partitions to improve I/O.2.Is this good enough?3.Does anything change wrt security?Also before we move our data to the SAN, I am planning to take backups of all system and application databases. 4.Is there anything else I need to backup?Thanks,Sarat.**To be intoxicated is to feel sophisticated, but not be able to say it.** |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-10-23 : 19:06:42
|
| Well, I think it is a good idea to keep a couple of full backups on disk in case you need them. If you've ever had to restore a file from tape, you'd understand how painful it can be.Keeping the test databases on different arrays would help only if you have separate disk controllers for them. I asked our server admin if we could improve ours by doing it this way, but he explained that the SAN that we purchased is so fast that adding disk controllers would only make a very very small improvement. BTW, we're running Compaq's EVA solution, which I hear is pretty expensive.Nothing changes with security.Yes perform database backups of all the databases that you are moving to the SAN. Here is what we did:Backup all databasesStop MSSQLSERVER serviceCopy all MDFs and LDFs to SAN drive (you can do this with the service stopped)Remove the drive that you've been using for the data filesRename the SAN drive to this drive letterStart MSSQLSERVER serviceYou don't need the backups for this method, but you have them just in case anything goes wrong.You could also use the detach/attach method if you aren't going to remove the data drive in the server.You're now back up and running. We've actually done this several times now and it works great.Tara |
 |
|
|
|
|
|
|
|
Implementing new SAN