I'm wondering can you help me please? I have inherited an ASP.NET 3.5 application talking to a Sql Server 2005 database. Both application and database are on the same box. I do not believe the database is backed up regularly.
The application is not hugh and the writes to the database amount to about 10MB per day. Application stack is light enough with just a front-end that talks to the database. No web service for example.
Here are my questions:
Q1: Should I seperate the database from the application? If yes, what type of box/server should I deploy the Sql Server onto?
Q2: Should I make regular backups of the database? If yes, how do I do that? (pointers would be great)
Q3: Should I investigate failover and redundency of the application server? ie if the application server falls over I would like another server to kick in immediately? What is the easiest way to implement this? Any good experiences you would like ot share
or articles you know of?
Thanks in advance for any comments you would like to share.
J.
Q1: Should I seperate the database from the application? If yes, what type of box/server should I deploy the Sql Server onto?
It doesn't matter whether you can keep both database & application in same server if you have enough disk memory space .
But make sure that other servers have rights to retrieve/connect the main server for just-in-case.
jellyman
Should I make regular backups of the database? If yes, how do I do that? (pointers would be great)
For this case, I suggest you to take schedule automatic database backup process in sqlserver
Click here to know about How to schedule a database backup operation by using SQL Server Management Studio in SQL Server 2005
Click here to know more about Scheduling Backups
in SQL Server 2005 Express in step by step process
jellyman
Should I investigate failover and redundency of the application server? ie if the application server falls over I would like another server to kick in immediately? What is the easiest way to implement this? Any good experiences you would like ot share or articles
you know of?
Click here to know more about ASP.NET State Server Failover
Scheme
Concerning Q1 - concerning "if you have enough disk memory space" - I heard the 70% fill rule mentioned before, that is you should never allow the server disk-space exceed more than 70%. Would you agree with that or do you have another rule of thumb...
Concerning "But make sure that other servers have rights to retrieve/connect the main server for just-in-case" what exactly do you mean? Can you elaborate please?
Thanks for th e other links to the articles you pointed out. I will investigate.
Concerning "But make sure that other servers have rights to retrieve/connect the main server for just-in-case" what exactly do you mean? Can you elaborate please?
None
0 Points
13 Posts
Deployment/backups/failover issues with existing system -- help needed
Apr 07, 2015 08:33 AM|jellyman|LINK
Hi,
I'm wondering can you help me please? I have inherited an ASP.NET 3.5 application talking to a Sql Server 2005 database. Both application and database are on the same box. I do not believe the database is backed up regularly.
The application is not hugh and the writes to the database amount to about 10MB per day. Application stack is light enough with just a front-end that talks to the database. No web service for example.
Here are my questions:
Q1: Should I seperate the database from the application? If yes, what type of box/server should I deploy the Sql Server onto?
Q2: Should I make regular backups of the database? If yes, how do I do that? (pointers would be great)
Q3: Should I investigate failover and redundency of the application server? ie if the application server falls over I would like another server to kick in immediately? What is the easiest way to implement this? Any good experiences you would like ot share or articles you know of?
Thanks in advance for any comments you would like to share.
J.
Deployment
Star
8544 Points
1376 Posts
Re: Deployment/backups/failover issues with existing system -- help needed
Apr 08, 2015 01:25 AM|Edwin Guru Singh|LINK
It doesn't matter whether you can keep both database & application in same server if you have enough disk memory space .
But make sure that other servers have rights to retrieve/connect the main server for just-in-case.
For this case, I suggest you to take schedule automatic database backup process in sqlserver
Click here to know about How to schedule a database backup operation by using SQL Server Management Studio in SQL Server 2005
Click here to know more about Scheduling Backups in SQL Server 2005 Express in step by step process
Click here to know more about ASP.NET State Server Failover Scheme
--
with regards,
Edwin
Deployment
Edwin
None
0 Points
13 Posts
Re: Deployment/backups/failover issues with existing system -- help needed
Apr 08, 2015 11:42 AM|jellyman|LINK
Thanks for the reply Edwin.
Concerning Q1 - concerning "if you have enough disk memory space" - I heard the 70% fill rule mentioned before, that is you should never allow the server disk-space exceed more than 70%. Would you agree with that or do you have another rule of thumb...
Concerning "But make sure that other servers have rights to retrieve/connect the main server for just-in-case" what exactly do you mean? Can you elaborate please?
Thanks for th e other links to the articles you pointed out. I will investigate.
J.
Deployment
Star
8544 Points
1376 Posts
Re: Deployment/backups/failover issues with existing system -- help needed
Apr 08, 2015 10:11 PM|Edwin Guru Singh|LINK
This is what I mean -refer the similar following link :
http://stackoverflow.com/questions/23560638/separating-database-services-and-iis-to-different-servers
--
with regards,
Edwin
Deployment
Edwin