SQL Server 2000 log transport function - setting (1)
The log transmit function automatically copies the database's transaction log file, and returns another database of the standby server (STANDBY Server). Therefore, the availability of the SQL Server database can be greatly improved. Because the standby database completely receives the power of the source database, it is a copy of the source database - the difference is only the time difference generated by the data replication and the loading process. However, when the primary server is stopped, you can change the standup server to a new primary server. If the original primary server can be used back online, you can set it to a new backup server - in fact is the role of the two servers. Among the SQL Server 2000 Enterprise or Development, Microsoft provides a log shipping function in Enterprise Manager - one of the Log Shipping. When using the previous SQL Server, you need to create a log transfer system. Set log transmission
The primary server is a formal server that actually handles the data; this server has a source database. The subside server (Secondary Server) is stored, used to copy the transaction log files for the reply source database. Monitor Server is used to monitor the primary server and the secondary server. Unlike SQL Server 7.0 (SQL Server 7.0 is the log transmitting action on the secondary server), SQL Server 2000 uses Enterprise Manager log transfer monitoring tool to monitor log data in each set of transfer. Microsoft recommends that you install this tool program on another monitoring server. You can use Enterprise Manager's database maintenance plan wizard to set the log transfer of SQL Server 2000. But before you activate the wizard, you must first make some preparations. First, please follow the steps: 1. Determine a set of servers to set logs (ie, where the log transfer process, the primary server is the secondary server). 2. Select a monitoring server. It is best to be different from the primary server or the secondary server. 3. Set the security of all servers. The Windows account you use to set the log sent must have the permissions of the SQL Server System Manager (SA) on all servers. 4. Create a sharing folder on the main / secondary server. First, the directory where the source database transaction log file is located is set to the shared directory. Then, on the secondary server, share the directory you plan to return to the transaction log file. In order to clearly identify each shared directory, please indicate the name of the server and the database within the sharing name. If the shared directory name already exists, you may need to remove or move other files from the shared directory, especially the old log backup file. Then open the permissions of these shared directories to the Windows account used by the SQL Agent on each server. 5. Decide how to establish and initialize the destination database. You can create a database of initial synchronization destination before log delivery settings, otherwise you must manually perform the reply action of the initial database. 6. Register this three servers in Enterprise Manager (ie, primary, secondary and monitoring servers). When you complete these preparation action, you can prepare the Database Maintenance Scheme wizard to set the log transfer. You can view five consecutive steps in the log transfer process, as shown in Figure 1:
Figure 1: Setting steps for SQL Server 2000 Log Transport.
The first two are optional steps. If you have not synchronized the source and destination database, step 1 will back up the source database first, and then perform the synchronization action. At step 2, the wizard copies the backup file to the secondary server and respond to the destination database. The elves will certainly perform the remaining three steps. At step 3, the wizard will create a SQL Agent work (JOB) on the primary server. This work will always back up the contents of the transaction log file to disk files periodically. The elves will also establish a database maintenance plan for transfer logs on the secondary server; this plan contains two SQL Agent work: one is to copy the transaction log file to the secondary server (step 4), the other is the transaction log The file is returned to the destination database (step 5). These steps will establish a set of log transport servers (two databases with each other). If you want an additional fault tolerance function or set a report server, you can combine the primary server with another secondary server, and set a set of log transfer matters. Preparation 1. Prepare Primary Server (The following is ZTAO-1) and Secondary Server (below INTRONTEST) 2. The database (the following is the Recovery Model) where the database (the INTRONERP) will be set to complete (FULL). 3. Add two computer SQL Server service accounts to Administrator group 4. Create a PRIMARY SERVER backup LOG data clip A. Create C: / Logfile to save the primary server database Transaction log backup B. C: / logfile Data sharing, share the permissions of the directory open to the Windows account used by the SQL Agent. 5. Create a data clip restored by Secondary Server a. Create a C: / ShippedLog folder to store the transfer of Transaction logs from Primary Server, create a C: / logfile data clip, after the role is exchanged, The database transaction log c can be stored in the new primary server. Share the C: / Logfile data clip, share the permissions of the directory open to the Windows account used by the SQL Agent. 6. In Primary Server, new SECONDARY SERVER registration information
