Development Server restoration notes and experiences

In August 20, I went online on the second day of isolution. I wanted to fully develop the web server, but I was given the whole server. Record On the afternoon of June 23, August 20, I took a 1 TB hard disk and added it to the development network server in the data center. Since then, this server will no longer be available. This server runs many services such as ad, exchange, DNS, SVN, VSS, sqlserver, artifactory, memcached, and file sharing on the Development Network, the stopping of the service directly causes the developers to be unable to develop and access the website, and strike one after another. Under pressure, I had to immediately install sqlserver and DNS on a machine so that the development and network could continue temporarily. Since ad has never been backed up, I can only hope that the server operating system can be restored. After several days of attempts, the machine is still on a blue screen at startup, which has been verified by experts, it should be because the hard disk is broken. Fortunately, the data in the hard disk can also be copied. Test to reduce the burden on the service and prevent similar situations, I decided to divide the server into three, the service steps are as follows: 1. AD, DNS; 2. SVN, VSS, file sharing, artifactory, and memached; 3. sqlserver, MySQL, and exchange; on June 16, August 23, the database server was independently and successfully run SQL2000, sql2005, and MySQL respectively, however, SQL2000 runs on port 1444, causing a little trouble during connection. On April 9, August 25, the source code server succeeded independently, SVN and VSS recovered to normal, and on April 9, August 26, the domain and DNS were re-installed, and manually create an account (fortunately, there are only more than 10 people), and then install an auxiliary domain control for automatic backup; at this point, the development server is basically restored, we plan to install a Linux oralcle Database Server later. Experience 1. The ad domain and the Exchange Service are stored on different servers. Otherwise, shutdown may fail. You need to manually close the exchange service to shut down normally. 2. Try to separate the services as much as possible, do not put the eggs in a basket, otherwise the loss will be very large; 3, the core service to back up in time, especially the domain backup (For details, refer to: http://blog.zol.com.cn/1756/article_1755966.html ); 4. Using One Nic to configure multiple IP addresses and Apache proxy can achieve seamless migration between servers. 5. re-install the ad domain and create an account, make sure that the domain name is the same as the old domain name. Check the "Change Password Upon first Logon" option on the account to avoid domain machine duplication and system user changes (during the first logon, use the new password. you can log on to the new account after about one minute );