![]() Primary: SQL Server 2008 Developer Edition.Firewall preventing the endpoints from talking – test telnet to your portsīelow is the setup used if you want to follow along exactly while configuring your own lab.Restore of the tail log wasn’t done or successful – restore procedure as a whole.When setting up mirroring there are two points to troubleshoot if the mirror will not start synchronizing. Service Credentials set for security (account name).So for example with this mirroring lab we are configuring, you may want to list something like the following Not doing this often will cause you headaches trying to debug configurations when in reality the configuration problem is simply a problem with the instances colliding. Documentation can save you from false errors and testing not functioning as it should. When configuring mirroring, replication or log shipping on one local machine be sure to document your configurations for each HA or DR test. Example: You principal, mirror or witness cannot share the same port of 5022. Note: Catch number one in this lab setup when configuring mirroring in which the mirror, principal and/or witness are on the same physical machine, ensure that your endpoint ports are configured so each entry point is aware of its own path. The instances for our examples will be located on the same physical hardware. To set our mirror up we will need two instances. At the time of this writing, the cost was still only $47. ![]() ![]() Developer Edition is a great tool that is extremely inexpensive. Today we are going to get down into actually configuring a basic mirror using Developer Edition. We’ve gone over Planning your hardware for SQL Server Mirroring and Planning your SQL Server mirroring landscape. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |