Search
Search titles only
By:
Search titles only
By:
Log in
Register
Search
Search titles only
By:
Search titles only
By:
Menu
Install the app
Install
Forums
New posts
All threads
Latest threads
New posts
Trending threads
Trending
Search forums
What's new
New posts
New ads
New profile posts
Latest activity
Free Ads
Latest reviews
Search ads
Members
Current visitors
New profile posts
Search profile posts
Contact us
Latest ads
Ad icon
V2ray VPN for Tunneling
hu KANNA
Updated:
Oct 22, 2026
FREE SEO Check & Google Maps Check for Sri Lankan Businesses | Web Design, Website Price Rs 14,900 |
LankaSolve
Updated:
Oct 20, 2026
ඕනම රටකට සෙට් වෙන CV එකක්
ErMurazor
Updated:
Oct 17, 2026
Hambantota
7 Acres Beachfront Land For Sell DownSouth , PerPerch Price 420 000
1024 Digital
Updated:
Oct 14, 2026
Baseus PI LITE INDOOR CAMERA
ErMurazor
Updated:
Oct 12, 2026
Electronics
Vehicles
Property
Search
Reply to thread
Forums
General
ElaKiri Talk!
system backup
Get the App
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Message
<blockquote data-quote="Nisala88" data-source="post: 26188573" data-attributes="member: 8045"><p>you have a primary site with production servers.</p><p></p><p>You have a near-site environment configured with servers just as the primary site close to the primary site. There may be more than one near-site.</p><p></p><p>You have a disaster recovery site (dr site) configured with servers just as the primary site mostly on a remote data centre away from the primary site.</p><p></p><p>Production servers replicate their data to the near-site and dr site on a real-time/daily/monthly/quarterly basis.</p><p></p><p>If something happens to the production site, the connection switches to the near-site (this happens automatically or manually based on the configuration)</p><p></p><p>If something happens to both the primary site and the near-site, the connection has to be switched to the dr site. most of the time dr site is not configured to automatically linked - this may be based on the architecture and the requirement.</p><p></p><p>This is the most basic explanation for doing this. there are things like load balancing with multiple servers, fault tolerance techniques are using based on the architecture.</p></blockquote><p></p>
[QUOTE="Nisala88, post: 26188573, member: 8045"] you have a primary site with production servers. You have a near-site environment configured with servers just as the primary site close to the primary site. There may be more than one near-site. You have a disaster recovery site (dr site) configured with servers just as the primary site mostly on a remote data centre away from the primary site. Production servers replicate their data to the near-site and dr site on a real-time/daily/monthly/quarterly basis. If something happens to the production site, the connection switches to the near-site (this happens automatically or manually based on the configuration) If something happens to both the primary site and the near-site, the connection has to be switched to the dr site. most of the time dr site is not configured to automatically linked - this may be based on the architecture and the requirement. This is the most basic explanation for doing this. there are things like load balancing with multiple servers, fault tolerance techniques are using based on the architecture. [/QUOTE]
Insert quotes…
Verification
Hathara warak wissa keeyada? (Hathara wadi karanna 20)
Post reply
Top
Bottom