Helpcenter +918010117117 //cdn1.storehippo.com/s/573db3149f0d58741f0cc63b/ms.settings/5256837ccc4abf1d39000001/57614ef64256dc6851749879-480x480.png" support@storehippo.com https://www.facebook.com/StoreHippohttps://twitter.com/StoreHippohttps://www.linkedin.com/company/hippoinnovations/https://plus.google.com/+Storehippo/posts
B4,309-10 Spaze iTech Park, Sector 49, Sohna Road, 122001 Gurgaon India
call to replace anchor tags contains '/admin' in href

Business continuity (BC) and disaster recovery (DR)

For Disaster Recovery (DR) and Business Continuity (BC), StoreHippo takes several measures to make sure systems recover from any unforeseen disaster and are up and running within minutes. Following are a few of them:

Database Recovery 

We are using MongoDB Atlas to store the databases. The databases are in a multi-node setup with high availability and recover automatically in case any single node fails. The data from databases are continuously backed up and point in time backups are available to restore the databases in case of any disaster. The data is encrypted at rest at the disk level to avoid any unauthorized database access

DDoS

StoreHippo web servers have throttling in place at IP level and Virtual server level to counter any DDoS attacks. StoreHippo follows a Single Page Architecture where data is rendered in the client’s browser. That provides inherent protection against DDoS as any such attack gets only the cached data and does not put a huge burden on the servers. StoreHippo aggressively uses global CDN to offload most of the site data which absorbs and mitigates any impact of DDoS.

Application Recovery

Within the primary cloud region, StoreHippo uses a redundant set of application servers behind a load balancer. The load balancer setup recovers automatically in case of single-node failures. In case of any emergency where the entire region is down, StoreHippo keeps Disk Images ready to start the Virtual machine in a different region.

2022-03-11T14:22:28.013Z