මචන් බෑන්ක්, ටෙලිකොමිනිකේස්න් වල සිස්ටම් ක්රෑස් වලදී සර්විස් ඉන්ට්රප්ට් නොවෙන විදියට වැඩ කරන ටෙක්නොලොජි එක මොකක්ද බන්? මේන් සිස්ටම් එක සර්වර් කීපයක රන් වෙනවද? 
Latest ads
-
Shared Hosting වාර්ෂිකව රු 2200 සිට!
- Nadun26
- Updated:
-
හොඳ, දැන්වීම්-රහිත (ad-free) ආයුර්වේද ඇප් එකක් සොයා ගැනීමට නොහැකි වූ නිසා, මමම එකක් නිර්මාණය කළා- kitchen_discussions
- Updated:
-
ZTE MF283U 4G Unlocked Router (Used)
- ayanthamaxi
- Updated:
-
ලංකාවේ හොඳම උපකාරක පන්ති සහ ගුරුවරුන් එකම තැනකින් - TopTuition.lk- dulithapathum
- Updated:
system backup
- Thread starter manjulabw
- Start date
අපේනන් DR ඒකක් තියනවාමචන් බෑන්ක්, ටෙලිකොමිනිකේස්න් වල සිස්ටම් ක්රෑස් වලදී සර්විස් ඉන්ට්රප්ට් නොවෙන විදියට වැඩ කරන ටෙක්නොලොජි එක මොකක්ද බන්? මේන් සිස්ටම් එක සර්වර් කීපයක රන් වෙනවද?
මාස 6කට පාරක් පැය 12හක් ස්විච්කරනවා මෙයින් ඒකෙන් ඔකට
Redundancy - running multiple instances of applications in multiple data centers (availability zones in cloud).
Having hot/ warm/ cold disaster recovery sites.
Having hot/ warm/ cold disaster recovery sites.
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.
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.
