Skip to main content

How to implement backup and restore in an enterprise

As a follow up to the best practice design for networks, here is an addition for backup and restores. The diagram above shows how to do backup and restores in an enterprise. The traffic does not flow through firewalls or across a live production interface. The backup and restores are done on separate NICs installed in the servers.
  • Use is made of Cisco switch protected ports.
  • The backup and restore VLANs are non-routed.
  • Assign a supernet, e.g. 172.18.x.x /16 and subnet it down to /23 per VLAN. Bin (or nul route) these addresses on all firewalls and network choke points and core routers.


Popular posts from this blog

easywall - Web interface for easy use of the IPTables firewall on Linux systems written in Python3.

Firewalls are becoming increasingly important in today’s world. Hackers and automated scripts are constantly trying to invade your system and use it for Bitcoin mining, botnets or other things. To prevent these attacks, you can use a firewall on your system. IPTables is the strongest firewall in Linux because it can filter packets in the kernel before they reach the application. Using IPTables is not very easy for Linux beginners. We have created easywall - the simple IPTables web interface . The focus of the software is on easy installation and use. Access this neat software over on github: easywall

No Scrubs: The Architecture That Made Unmetered Mitigation Possible

When building a DDoS mitigation service it’s incredibly tempting to think that the solution is scrubbing centers or scrubbing servers. I, too, thought that was a good idea in the beginning, but experience has shown that there are serious pitfalls to this approach. Read the post of at Cloudflare's blog: N o Scrubs: The Architecture That Made Unmetered Mitigation Possible

Should You Buy A UniFi Dream Machine, USG, USG Pro, or Dream Machine Pro?