SQL Server 2014 Log Shipping Deployment (2): Log shipping system requirements and experimental architecture

13.2 Deployment of log shipping

13.2.1 system requirements for deployment log shipping

The deployment of SQL Server 2014 log shipping requires a hardware infrastructure that outlines these system requirements.

Internet

Log shipping does not necessarily require a Windows domain environment, but the Windows domain environment facilitates the configuration and management of log shipping, which improves security in a relatively non-domain environment.

The SQL Server servers that participate in log shipping must be connected to each other in the network, the primary server can back up the transaction log to a shared folder, the secondary server may copy the transaction log backups to a local folder, and the monitoring server can connect to the primary and secondary servers.

Server and Storage

The primary server and the secondary server should have the same performance capacity as the primary server to ensure that when failover occurs, the secondary server will be able to deliver the same level of performance after the primary server has been worked on, and at cost, some company secondary servers will be much smaller than the primary server performance capacity. Regardless of setting up a secondary server, you need to understand the specific needs of the business and configure the secondary server appropriately.

Log shipping technology does not require an infrastructure like a Windows failover cluster that does not require shared disks; Conversely, in a log shipping deployment scenario, in order to avoid the risk of storage becoming a single point of failure, the primary and secondary servers should avoid sharing the same disk system. In addition, transaction log backups should be kept as far as possible in a fault-tolerant design of the disk system, maximizing the protection of transaction log backups from loss due to disk system failure.

Tips: (1) The server participating in log shipping should have the same size-sensitive setting; (2) The SQL Server service and SQL Server Agent account must have read and write access to the backup folder.

13.2.2 the experimental architecture for deploying log shipping

The domain environment is localdomain.local, all the servers used in the experiment are joined to the domain, although deploying log shipping does not necessarily require a domain environment, it is recommended to use a domain environment to deploy log shipping in a production environment, which is not only easy to deploy and manage, but also greatly improved in terms of security compared to non-domain environments.

(1) Domain control server name AD,IP address 192.168.1.20;

(2) Primary server name Sqlsvr1,ip address 192.168.1.241;

(3) Secondary server name Sqlsvr2,ip address 192.168.1.242;

(4) Monitor server name Sqlsvr3,ip address 192.168.1.243

650) this.width=650; "title=" image "style=" border-top:0px;border-right:0px;background-image:none;border-bottom:0 px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; "border=" 0 "alt=" image "src=" http:// S3.51cto.com/wyfs02/m02/57/fa/wkiol1slouqbk57uaadnzcj2h3m742.jpg "height=" 575 "/>

This article is from the "Margin with Wish" blog, please be sure to keep this source http://281816327.blog.51cto.com/907015/1598311

SQL Server 2014 Log Shipping Deployment (2): Log shipping system requirements and experimental architecture