Recovery :: Server Local High Availability Using Failover Cluster And Disaster Recovery Using AlwaysOn

Aug 17, 2015

We have a requirement to build SQL environment which will give us local high availability and disaster recovery to second site. We have two sites- Site A & Site B. We are planning to have two nodes at Site A and 2 nodes at Site B. All four nodes will be part of same Windows failover cluster. We will build two SQL Cluster, InstanceA will be clustered between the nodes at Site A Server and InstanceB will be clustered between the nodes at Site B, we will enable Always On Between the InstanceA and InstanceB and will be primary owner where data will be written on InstanceA and will be replicated to InstaceB. URL....Now we want we will have instanceC on the Site B and data will be writen from the application available on Site B, will be replicated to the instance on the Site A as replica.

View 6 Replies


ADVERTISEMENT

Recovery :: Cannot Create Listener For High Availability Group Of AlwaysOn On Cluster Environment

May 27, 2015

I have getting issues when i am creating listener for always On . Error shown as below

Can not bring  the Windows server fail over cluster (WSFC) resources online. (Error Code 5942). The WSFC service may not be running or may not be accessible in its currents states, or the WSFC resources may not be in a state that could accept the request.

For information about this error code see "system error code" in windows development documentation 

The attempt to create network name and IP address for the listener is failed. The WSFC service may not be running or may not be accessible in its currents states or the value provide for the network name and IP address may be incorrect. Check the state of the WSFC cluster and validate network name and IP address with network administrator. (Microsoft SQL Server error 41066) ...

View 2 Replies View Related

Recovery :: AlwaysOn Failover Cluster And Active Sessions Failover Scenario

Oct 29, 2015

1. In alwaysON fail over cluster, Once fail over to secondary replica, what will happen to connected session in primary node? can the session fail over to secondary seamlessly or need to re-login. what happen committed transactions which has not write to disk.

2. Assume I have always on cluster with three nodes, if primary fails, how second node make write/ read mode.

3. After fail over done to 2nd secondary node what mode in production(readonly or read write).

4. How to rollback to production primary ,will change data in secondary will get updated in primary.

View 3 Replies View Related

Recovery :: Failover Cluster With Mirroring With AlwaysOn?

Jun 30, 2015

we have to build high availability SQL 2012 cluster for VDI and we have two options. One option is to build a server cluster with combination of failover and mirroring and other option is to build failover cluster with AlwaysOn.We are not sure which option to chose. We have contacted Microsoft support to provide us some documents and instructions for failovermirroring combination but they have send us instructions for AlwaysOn option.

What would be best way to build high availability cluster for VDI? Also, since first option is very complicated.

View 5 Replies View Related

Recovery :: Error Adding Replica To AlwaysOn Failover Cluster?

May 22, 2015

I'm getting an error adding Replica to SQL AlwaysOn failover cluster in the new availability group wizard.  When I enter the name of the target node (secondary replica) server and press connect, I get the following:   

A network-related or instance-specific error occurred while establishing a connection to SQL Server. 

The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 2) The system cannot fine the file specified

The SQL Browser service is up and running on the target.  I am using an Azure VM for my SQL instance.  This cluster spans geographies from our on-premise site to Azure via a VPN.  This is a multi-subnet cluster. I'm attempting to create a new AG from the primary replica node and the target is a node on Azure called SSASNodeAz03. 

[URL]

Full error:

Connect to Server
Cannot connect to ssasnodeaz03

Additional information: A network-related or instance-specific error occurred while establishing a connection to SQL Server. 

The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 2) The system cannot fine the file specified

View 8 Replies View Related

Using 32 Bit Sql Server For Disaster Recovery Of 64 Bit Prod Cluster

Feb 16, 2007



does anyone know of any potential issues of using a 32 bit sql server 2005 instance used for disaster recovery of a 64 bit sql 2005 cluster ?

thanks

View 2 Replies View Related

Recovery :: Replicate Server Database To AlwaysON Availability Groups

Dec 1, 2015

I have configured replication between Always ON Availability Groups  (Listener) (PUBLISHER), remote distributor to XYZ SUBSCRIBER...with above link ...

Now, I want to know how to replicate Data from XYZ SERVER a PUBLISHER to Always ON Availability Groups  (Listener) (SUBSCRIBER)? Distributor Database being on XYZEX:

XYZ SQL SERVER as PUBLISHER, and DISTRIBUTOR 
to 
Always ON Availability Groups  (Listener) SUBSCRIBER...

View 3 Replies View Related

Failover, Cluster, High Availability

May 18, 2004

Hello,
Does any one know, any software out there that can provide a solid failover / cluster / high availability solution for SQL Server 2000 Databases.
I have tried Incepto but it requires an extra column in every single table that involves in Replication and its not gonna work

So Please advise.

Thanks,
imransi.

View 2 Replies View Related

Recovery :: AlwaysOn Availability Groups Server Logins Fails When Switching Between Nodes

Jul 9, 2015

I am setting up a 3 node cluster as part of an availability group.Initially I tested failover between nodes using SQL Management Studio and everything failed over successfully when I stopped a node, and I was still able to write queries. I started to test with an application which connects using an SQL user and whenever I would switch nodes, I would get login failed. I believe the cause of this issue is because the server logins SID's which are tied to the database are different than the server logins on the other nodes which resulted in login failed.how can I ensure that the server logins SID's are the same between nodes? Is there a way of copying this over or how is this supposed to be done? I read a little about contained databases where I could just set the login on the database itself vs. creating a server login but I would rather not go down that route. 

View 4 Replies View Related

Recovery :: Where To Place Witness Server For Mirroring Using High-safety And Auto-failover

Apr 9, 2015

We have 2 data centers, site 1 and site 2.  Site 1 is generally our primary, and site 2 is our Disaster Recovery (DR) site.  I want to setup a SQL instance to have extremely high availability.  Therefore I was looking at using DB mirroring, with synchronous data writing, high-safety and auto-failover.  This requires the usage of a witness server.My problem with this setup, is that if the witness and principal are both at site 1, if site 1 goes away (power failure, asteroid impact, lol, anything else that would be a *true* DR scenario), then there is no failover to the mirror server at site 2.   However, if you put the witness at site 2, anytime the WAN link between site 1 and site 2 has an issue, the DB will auto-failover to site 2.  Is the reason for the recommendation of the witness being at the primary site because the thinking is that WAN link failure is likely more common than a *true* DR scenario that takes out all of site 1?

View 3 Replies View Related

Disaster Recovery Of SQL 7.0 Cluster

Mar 5, 2001

Hi All
This is a Pearler !!. SQL 7 and NT 4

Site A and B are 30 miles apart

"Site A" SQL 7.0 Cluster with Drives on Shared Storage.
"Site B" SQL Server Cluster with Drives on Shared Storage
Both Configured as Active/Active (8+ databases <100GB total)

How can I get the DB's (all) from Site A and allow a DIFFERNET cluster to control them.

Basically, I want to move all DB's from "Site A" and bring them into "Site B" with all relevant data ..ie master DB etc . I have a time window of 90 Mins and I cannot lose one single piece of data.........( I need to lie down now)
Help would be apprecitated)

View 1 Replies View Related

Recovery :: Set Up AlwaysOn Availability Groups?

Sep 16, 2015

Can we set up always on availability groups in  server 2012 standard edition.

View 3 Replies View Related

Recovery :: Add Second Node In AlwaysOn Availability Group

Aug 13, 2015

How do I add my second (secondary) node in my AlwaysOn Availability Group, after adding my head node, and the secondary node is a virtual machine. See based on the attached file if it is the correct way?

View 2 Replies View Related

Recovery :: How To Test AlwaysOn Availability After Configuring Them

Jul 3, 2015

How to test always on availablity after configuring them.I have configured always on group with 1 active and 1 passive with readonly.I want to test from application.what are cases which we can have for testing.

View 5 Replies View Related

Recovery :: AlwaysOn Availability And TRUSTWORTHY Property

Sep 18, 2015

We have a SQLServer 2012 Always-On Availability (AAG) Primary and Secondary Node installation/environments. On the Primary node, we have some databases that have the TRUSTWORTHY option enabled (Set to ON). But when the databases are synched/added to the AAG the databases loose the TRUSTWORTHY property and are reset to OFF on the Secondary Node.Because of this,When the instance fails over to the Secondary Node the applications that were working don’t work anymore.

View 5 Replies View Related

Recovery :: 2012 R2 High Availability Database Not Replicating?

May 19, 2015

Discovered that a geo-spatial AlwaysOn HA database (1 of 4) was not synchronizing as at a point in time earlier in the day.  Suspend Data Movement appears to be working perpetually without finishing.  The SQL Server services is in a Pending Changes state after an attempt to restart it from SQL Configuration Manager.  The Cluster Dashboard says it is in a Not Synchronizing state, with only the one database in question having a yellow triangle, all 3 others show green.  

The warning for the cluster is:At least one availability database on this availability replica has an unhealthy data synchronization state. If this is an asynchronous-commit availability replica, all availability databases should be in the SYNCHRONIZING state. If this is a synchronous-commit availability replica, all availability databases should be in the SYNCHRONIZED state.  There is no abnormal data movement from the primary to the seconday.The warnings for the unhealthy database are:

The data synchronization state of this availability database is unhealthy. On an asynchronous-commit availability replica, every availability database should be in the SYNCHRONIZING state. On a synchronous-commit replica, every availability database should be in the SYNCHRONIZED state.Either a database administrator or the system has suspended data synchronization on this availability database.So how to get this database back to synchronizing state?

View 2 Replies View Related

Recovery :: AlwaysOn Availability Groups - Download Hotfixes

Oct 19, 2015

I'm doing a certification process using AlwaysOn, and was using the link below, and on the lower 90 hotfix, and instead of downloading one by one, and then upgrade one by one updates, is there any way to make it more faster or practical, or unfortunately have to do this one by one, so the download as the update? This rollup contains the latest version of the Windows system files that are updated after the release of SP1. URL...

View 2 Replies View Related

Recovery :: Setup AlwaysOn Availability Group Between 2 Separate Clusters

Sep 22, 2015

I have an active passive cluster on my primary Data center in NY and have a DR Active / passive SQL Cluster in TX. These are two separate clusters in the same domain using the same SQL server credentials.Both clusters host an active / passive SQL instance. Lets call it SQLNY(Primary) and SQLTX (DR). I want to enable always On Availability group within the two SQL Instances SQLNY and SQLTX. The listener will be SQLAG which will be used by the Application to connect to the SQL instance. Is there a practical way to implement this? This will not only give me instant fail over within the NY (Primary) but also give me the flexibility to fail over to TX. I am using SQL 2014 Enterprise Edition on both clusters.

View 6 Replies View Related

Recovery :: SharePoint Database Run Out Space In AlwaysOn Availability Group

Jul 11, 2014

I have a situation where I have two servers in SQL Server 2012 R2 AlwaysOn Availability Group. One is primary and the other one being secondary.  I am only running SharePoint Database on it.I have run out of space on the primary server and about to run out of space at the secondary server.  I have tried shrinking database transaction log files, but it returns an error that it cannot be shrunk as the database is in the AlwaysOn Availability Group.

Questions:
1.  Several forums suggest that databases need to taken out of AlwaysOn Availability Group in order for the shrinking to work properply?
2.  Would it have any impact on the database if it is taken out of availability group and then added back?

View 6 Replies View Related

Recovery :: Is AlwaysOn Availability Group Support SCCM / SCOM And DPM

Apr 29, 2015

Is AlwaysOn Availability Group support SCCM , SCOM and DPM ??what is the best Solution for this products to be highly available ??

View 3 Replies View Related

Recovery :: Failover Cluster Setup

May 8, 2015

I am using SQL 2012 SE with clustering on Windows server 2008 R2. Now I want migrate it to windows server 2012 with minimal down time. So I want to evict the passive node and add a new node with windows server 2012 and install sql server 2012 SE on the new passive node and perform a failover(make the node with 2012 OS as active) and then evict the new passive node and add another node with windows 2012 and then do the same thing?

View 12 Replies View Related

Recovery :: Multiple Instances For AlwaysOn For A Cluster

Jun 19, 2015

My environment has a 4 node cluster , 2 in primary and 2 in sec dc. Storage is sperate for both.

Need to setup always on for 4 Instances there on the 2 nodes of the primary dc. Is there any restriction in setting up always on for multiple instances for a cluster.

View 3 Replies View Related

Recovery :: AlwaysOn Cluster Did Not Fail Over Successfully

Aug 14, 2015

I have had a serious issue with a production AlwaysOn cluster whereby the service did not successfully transition to the secondary node and I cannot find the root cause of the issue.

Some details: It is a 2 node cluster (same datacenter) with a shared disk quorum, Windows Server 2012, both are virtual machines running on VMWare vSphere  5.5. SQL Server version is 2012 Enterprise SP2 CU6

The failover occurred because of a network incident (a spanning tree recalculation caused a connection timeout between both nodes). Initial entries in the SQL Log look normal for this event, for example:

05/08/2015 11:18:06: A connection timeout has occurred on a previously established connection to availability replica 'FIN-IE-PA078' with id [6910F4A9-87E7-4836-BA79-0F41BE90266D].  Either a networking or a firewall issue exists or the availability replica has transitioned to the resolving role.
05/08/2015 11:18:06: AlwaysOn Availability Groups connection with secondary database terminated for primary database 'UserManagement' on the availability replica with Replica ID: {6910f4a9-87e7-4836-ba79-0f41be90266d}. This is an informational message only. No user action is required.

[code]....

My interpretation of this is that the cluster failover attempts failed, because the network condition still persisted. The network interruption lasted approximately 2 minutes, and I would have expected the cluster to come back online at this point, after the restart delay period as suggested in the last entry in the error log. However this did not happen.

View 10 Replies View Related

Recovery :: Error When Setting Up Failover Cluster

Aug 26, 2015

I'm getting the following error when I go to create a cluster in the Failover Cluster Manager in Windows Server 2008.

"The address 10.10.10.111 is not valid for its associated network"

I'm following the instruction in the book for the 70-462 exam.  There was a step that had me create a DNS A record for the address sql-cluster.contoso.com.  The IP address was mapped to 10.10.10.111.  I'm not sure if this is the culprit but its the only time I used that IP address in the setup.

Below are 2 screenshots.  The first screenshot is the error.  The second screenshot is my DNS console.

View 7 Replies View Related

Recovery :: Setup FILESTREAM On Failover Cluster

Apr 22, 2015

I saw following point on Technet article about RBS.The local FILESTREAM provider is supported only when it is used on local hard disk drives or an attached Internet Small Computer System Interface (iSCSI) device. You cannot use the local RBS FILESTREAM provider on remote storage devices such as network attached storage (NAS).It looks like that we cannot use FILESTREAM on Failover Cluster because to setup Failover Cluster we need to have NAS. But then the NAS is made available locally for Failover Cluster so FILESTREAM should work right?Found another article which talks about setting up FILESTREAM on Failover Cluster. URL...

View 2 Replies View Related

Recovery :: Add Client Software To Failover Cluster?

Jul 17, 2015

The main objective is to have a third party program operate on a failover cluster.  The OS is Windows Server 2012 Datacenter loaded on 2 nodes. A virtual node exists along with supporting disks. This client software uses a SQL Server database.  SQL Server 2012 Enterprise is installed and operating in a failover environment.  However the client software is not failing over. If the connection to node A is lost, SQL Server fails over to node B.  But the client application does not. 

What needs to occur in order to associate the client software with the failover cluster?  This software has 6 services total installed. Some are referred to as servers - looks like to communicate between remote client computers and the database. What is the process to associate the client software with the failover?

View 6 Replies View Related

Recovery :: AlwaysOn Cluster Down Due To ClusDB Corrupt / Missing

Sep 5, 2012

I have a 3-nodes AlwaysOn cluster (Windows Server 2008 R2 SP1 + SQL Server 2012 RTM), Node Majority quorum, the quorum vote for each node is 1. 

Today the AlwaysOn AG was suddenly down due to the cluster service on node 1 stopped and can't be started.

The error in eventlog is - 

The cluster database could not be loaded. The file may be missing or corrupt. Automatic repair might be attempted.
The Cluster Service service terminated unexpectedly.  It has done this 2 time(s).  The following corrective action will be taken in 120000 milliseconds: Restart the service.

The failover cluster database could not be unloaded. If restarting the cluster service does not fix the problem, please restart the machine.

The Cluster Service service terminated with service-specific error The system cannot find the file specified..

The error log in cluster log is - 

0000156c.000008f8::2012/09/05-08:09:36.057 INFO  [DM] Key RegistryMachineCluster.restored does not appear to be loaded (status STATUS_OBJECT_NAME_NOT_FOUND(c0000034))
0000156c.000008f8::2012/09/05-08:09:36.057 WARN  [DM] Node 1: Failed to unload restored hive from the registry with error STATUS_INVALID_PARAMETER(c000000d)
0000156c.000008f8::2012/09/05-08:09:36.057 INFO  [DM] Node 1: loading local hive
0000156c.000008f8::2012/09/05-08:09:36.057 ERR   [DM] Node 1: failed to unload cluster hive, error 2.

Now the cluster service can't be started on node 1, error code 2. Looks like the clusdb in C:windowscluster is missing or corrupted. How to restore the clusdb file? And how to prevent this happen again?

All nodes were well patched, AlwaysOn and cluster related hotfixes were all installed. [URL] .... doesn't wok.

View 4 Replies View Related

Recovery :: Availability Group Quorum - Majority Of Nodes Down But Cluster Still Up?

Sep 9, 2015

I'm just starting to work with AlwaysOn Availability and WSFC.

I have in my environment (in Azure) a DC, WSFC and to SQL instances, so I have 3 nodes in my Failover Cluster:

WSFC 
SQL1
SQL2

If I simulate failure by shutting down one of the SQL boxes my Availability group seamlessly fails over to the other SQL instance - which is great.

However, I'm starting to look into the workings of the Quorum, my envt has the default settings and when I shutdown both of my SQL servers I expected the Cluster itself to go offline as 2 out of the 3 votes will be negative, but the Cluster is still up - Screenshot below when SQL1 and SQL2 are  shutdown:

Going through the Wizard (but not changing anything) it shows following config:

View 6 Replies View Related

Recovery :: Service Pack Installation In Failover Cluster?

May 9, 2015

I want to install service pack 3 to my SQL Server 2012 Enterprise running on windows server 2008 R2 Enterprise fail over cluster, I read about the SP installation in technet, its mentioned that the passive node should be patched first and to do this the passive node should be removed from the cluster, I need to know whether I should completely remove the node from windows cluster or remove the node by using SQL Server installer and install the service pack and then add it back to the cluster, Can I do this by pausing the node in cluster and perform the service pack installation ?

View 3 Replies View Related

Recovery :: Windows 2008 R2 AlwaysOn Cluster - Migrate DR Node

Oct 8, 2015

I have a Windows 2008 R2 Always on Cluster with 3 nodes (two in the primary site and one in the DR site).

Primary Site:
     -Primary Site Server1
     -Primary Site Server2

DR Site 1 (to be decommed):
     -DR Site Server1

Our company is planning on decommissioning the DR site.  But before we do this, we want to add a 4th site to the cluster.  Migrate the data...and then decommission the original DR Site.

Is it possible to have this configuration:

Primary Site:
     -Primary Site Server1
     -Primary Site Server2

DR Site 1 (to be decommed):
     -DR Site Server1

DR Site 2 (NEW DR Site):
     -DR Site Server1

IF this is possible, do I simply add the new DR site to the existing cluster (same steps as adding the first DR node to the cluster when the cluster was originally configured?  or are there special steps?

View 2 Replies View Related

Recovery :: AlwaysOn Cluster Reboot Due To File Share Witness Unavailability

Apr 23, 2015

Came across this scenario in AlwaysOn Availability Group (two node), file share witness times out and RHS terminate and cause the cluster node to reboot. File share witness is for continuous failover and if the resource is unavailable my expectation was that it should go offline and should not impact Server or Sql Server. But its rebooting the cluster node to rectify the issue.

Configuration
Windows Server 2012 R2 (VMs)
Sql Server 2012 SP2
Errors

A component on the server did not respond in a timely fashion. This caused the cluster resource 'File Share Witness' (resource type 'File Share Witness', DLL 'clusres2.dll') to exceed its time-out threshold. As part of cluster health detection, recovery actions will be taken. The cluster will try to automatically recover by terminating and restarting the Resource Hosting Subsystem (RHS) process that is running this resource. Verify that the underlying infrastructure (such as storage, networking, or services) that are associated with the resource are functioning correctly.

The cluster Resource Hosting Subsystem (RHS) process was terminated and will be restarted. This is typically associated with cluster health detection and recovery of a resource. Refer to the System event log to determine which resource and resource DLL is causing the issue.

View 3 Replies View Related

Recovery :: How To Do A Full Disaster Recovery

Sep 10, 2015

If you are doing a disaster recovery of an entire SQL 2005 cluster, can you just install SQL server and restore the system database to get the configuration?

View 4 Replies View Related

Recovery :: Cluster Failover - Failed To Bring Secondary Node Online?

Oct 19, 2010

Server : Windows server 2008
DB Server : SQL Server 2008 (SP1)
 
Here are the series of events which happened.

1.) Event ID: 1135
Cluster node 'XYZ' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.

2.) Event ID: 1049
Cluster IP address resource 'SQL IP Address 1 (XYZ)' cannot be brought online because a duplicate IP address '10.9.8.113' was detected on the network.  Please ensure all IP addresses are unique.

3.) Event ID: 1069
Cluster resource 'SQL IP Address 1 (XYZ)' in clustered service or application 'SQL Server (MSSQLSERVER)' failed.

4.) Event ID: 1049
Cluster IP address resource 'Cluster IP Address' cannot be brought online because a duplicate IP address '10.9.8.112' was detected on the network.  Please ensure all IP addresses are unique.

5.) Event ID: 1069
Cluster resource 'Cluster IP Address' in clustered service or application 'Cluster Group' failed.

6.) Event ID: 1066
Cluster disk resource 'Cluster Disk 25' indicates corruption for volume '?Volume{88552e6f-aea2-11df-9790-0026b92fffa7}'. Chkdsk is being run to repair problems. The disk will be unavailable until Chkdsk completes. Chkdsk output will be logged to file 'C:WindowsClusterReportsChkDsk_ResCluster Disk 25_Disk16Part1.log'. Chkdsk may also write information to the Application Event Log.

7.) Event ID : 1066
Cluster disk resource 'Cluster Disk 26' indicates corruption for volume '?Volume{88552e05-aea2-11df-9790-0026b92fffa7}'. Chkdsk is being run to repair problems. The disk will be unavailable until Chkdsk completes. Chkdsk
output will be logged to file 'C:WindowsClusterReportsChkDsk_ResCluster Disk 26_Disk4Part1.log'. Chkdsk may also write information to the Application Event Log.

8.) Event ID: 1049
  (Same message as point 2)

9.) Event ID: 1069
     (Same message as point 3)

10.) Event ID : 1049
(same message as point 4)

11.) Event ID :1069 
(same message as point 5)

12.) Event ID :1205
The Cluster service failed to bring clustered service or application 'Cluster Group' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.

13.) Event ID: 1069
Cluster resource 'Cluster Disk 17' in clustered service or application 'SQL Server (MSSQLSERVER)' failed.

14.) Event D : 1049
(same message as point 2)

15.) Event ID: 1069
Cluster resource 'SQL IP Address 1 (XYZ)' in clustered service or application 'SQL Server (MSSQLSERVER)' failed.

16.) Event ID : 1205
 The Cluster service failed to bring clustered service or application 'SQL Server (MSSQLSERVER)' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.
 
first of all,I went through all the logs, and could not find the reason for fail-over initialization. There should be some thing logged why the failover happened? secondly after failover the service was not coming online due to duplicate IP address detection.

Later when we try  to manually bring the service online from cluster management it comes online successfully. I don't understand how would duplicate IP address get resolved when we start manually.

Lastly we see few errors related to physical disk resource between failover retries, is this could be the correlated to failover error ?

View 4 Replies View Related







Copyrights 2005-15 www.BigResource.com, All rights reserved