You are on page 1of 6

Database information

1.Model Rack RAM Processor Estndar 48 GB Intel CPU Velocity Quantity Tipo Cores HD Cantidad Velocidad Format Capacity Ethernet LAN+iSCSI 1000 Mbit/s HBA Console IP Conections SAN FC 2+2 QLogic QMH2462 4Gb FC 1 2 64 bits 2.66 Ghz 2 X5650 6 2 15K RPM RAID1 146 GB HP BL460c G7 CTO

Host Name Connected to SRV-C4i-ECDB01.BICENTSSP.GDF.MX SRV-C4i-ECDB01.BICENTSSP.GDF.MX SRV-C4i-ECDB02.BICENTSSP.GDF.MX SRV-C4i-ECDB02.BICENTSSP.GDF.MX

RAID Type RAID1 /0 RAID1 /0 RAID1 /0 RAID1 /0

RAID Group # 2 6 5 7

Drive Modules* 0_0_9,0_0_10,0_0_11,0_ 0_12 2_0_4,2_0_5 1_0_4,1_0_5,1_0_6,1_0_ 7 3_0_0,3_0_1

LUN # 4 5 6 7

LUN Size 307,200.0 MB 204,800.0 MB 307,200.0 MB 204,800.0 MB

SP Assigned B B A A

Storage Group SRV-C4iECHDB-01 SRV-C4iECHDB-01 SRV-C4iECHDB-02 SRV-C4iECHDB-02

2.- SQL VERSION . SQL - 10.0.1600.22 Enterprise Edition (64-bit) SQL VERSION WITNES 10.0.4000.0 Enterprise Edition (64-bit) SP2 3.- Configuration of the mirror with witness

SERVER SRV-C4i-ECDB-01 SRV-C4i-ECDB-02 SRV-C4i-WS-01

PORT 5022 5023 5024

IP ADDRESS 10.20.2.1 10.20.2.2 10.20.3.4

TYPE SERVER PRINCIPAL SECONDARY WITNESS

Login by Authentication Windows User with witness and services on server get up. BICENTSSP\CAD-C4-SQL-AGENT Service login Services BICENTSSP\CAD-C4-SQL-Engine Login Services Type Mirroring: High safely with automatic failover (synchronous) commit changes at both server principal and mirror Time of synchronize 1-2 min if there are transactions the synchronize is automatic.

4.- Initial Sizing for HD L:\300GB LOG 60% S:\200GB DATA 40%

5.- Actual politic backup

The backup now is implementing manually with Store Procedure , this store procedure was schedule for 3 days a week making a backup automatic was stored in network path on the SAN DATA SCHEDULE BACKUP FULL-BACKUP
APP CAD CAD INSTANCE NAME ECHO DB NavteqDB DATABASE Echo NavteqDB SERVER SRV-C4i-ECDB01 SRV-C4i-ECDB01 IP 10.20.2. 1 10.20.2. 1 M T W T F S S

LOG SCHEDULE BACKUP FULL-BACKUP


APP CAD Instancia ECHO DB DATABASE Echo SERVER SRV-C4iECDB-01 IP 10.20.2.1 M T W T F S S

NAVTEQ LOG IS NOT NECESSARY TO DO A BACKUP SCHEDULE BECAUSE IS NOT TRANSACTIONAL DATABASE, IS GOOD FOR DO IT ONCE EACH 15 DAYS.

6.Politic Mirrorring For be functional Miirroring is necessary : Create End_points on the 3 servers for connection Certificates from the 3 servers on the 3 servers A snapshot (backup)from the database, for the secondary database. A Logins created for be run the services (Active Directory Logins)

7.Configuring Distribution The following steps need to be done: Step 1. Configure a distribution agent for the distribution instance which will contain the distribution database. The distribution database may be located in the same instance as the publisher instance, but for reasons of flexibility it will be located in a separate distribution instance created for this specific purpose. Step 2. Create the distribution database in the distribution instance which will appear as a new database under the System Databases folder.

Configure the CAD DB (ECHO_DB C4i) instance to be a publisher using the distribution database in the distribution instance. Note that as the CAD DB is configured with mirroring for high availability, both instances (Principal and Mirror) will need to be configured as the publisher.

Replication Implement Publication The following steps need to be done: Step 1. Configure the CAD DB instances (Principal and Mirror) to be publishers on the master database, using the distribution database which is located in the distribution instance. Step 2. Specify ECHO as the database to be published on the master database in the CAD DB server instances. Step 3. Create and configure a Log Reader Agent in the CAD DB server instance on the ECHO database. Step 4. Create a publication on the ECHO database in the CAD DB server instance, Step 5. Create the publication snapshot, Step 6. Add ECHO database objects (articles) to the publication. All tables in the ECHO DB are added into the publication. An important point is worth mentioning for this step is that no DELETE transactions should be replicated as all history of data has to be retained in the HISDB. Step 7. Start the Snapshot Agent to generate the initial snapshot for this publication.

Synchronize method there need to be on value native. After the initial snapshot has been applied at the HISTORY DB, the data and schema changes in the CAD DB will be propagated to the HISTORY DB continuously. From here on, the HISTORY DB will be synchronized in near real-time with the CAD DB.

8.-

Size DB 1352.2 5 565.44 110.81 7416.0 6

Space used 836.88 7.99 92 6866.05

Free Space 515.38 557.45 18.81 550.01

Name NavteqDB NavteqDB_lo g ECHO ECHO_log

9.Do you need here the process to make an snapshot (backup)?

10.In this point we need to be very carefully because we can make usually a Purge for the database directly over because is connected with the replication make a shrink on the database is not the best practice I have now a script for purge the old data on C4.

11.-

- Check for Consistency and Corruption.execute DBCC CHECKDB and DBCC CHECKCATALOG on each database (Echo and Navteq)

- Check for table/index fragmentation DBCC SHOWCONTIG.

This is optimal performance for a physical I/O perspective as well optimising space allocation within the database. - Rebuild any fragmented indexes that are identified (DBCC DBREINDEX or DBCC INDEXDEFRAG)