Backup to a different san or network location and archive to tape.īut at the very least I believe the client should do the following:.T ( 1200 GB, raid 5) – for tempdb data files.D ( 1200 GB, raid 10/5) – for sql data files.C ( 156 GB, raid 1) – for system and app files.I am wanting to suggest the client reconfigure their SAN as follows: I’ve also noticed Brent Ozar’s Blitz script reveals slow writes to the E drive at times. Periodically the client experiences sluggishness, sometimes severely, for short periods with the web application. The SQL Server is more read intensive, with data bulk loaded nightly like a data warehouse and the web app used for looking up and reporting on the data. C (156 GB) – for system and apps (IIS, web app, SQL, SSIS, CA ArcServe backup app, VIPRE antivirus)Ģ. O 8 drive bays all filled with 600 GB SATA-II 7.2K drives (5.4 TB total)ġ. Storage: o Cybernetics miSAN-D8/T16 SAN iSCSI storage appliance.
0 Comments
Leave a Reply. |