| The risks of data loss |
A survey of small businesses found of those companies that lost customer data:
- 30% lost sales as a result
- 20% lost customers
- 25% said the data loss caused them severe disruptions
- 20% had no backups at all
|
| Top causes of data loss |
Survey of small businesses found the most common causes of data loss, from most to least common, were:
- Hard Disk failure
- Software bug
- Destroyed by malware
- Accident
- Fire or disaster
- Erased by hacker
- Computer stolen
- Lost password
- Malicious employee
- and Natural Disasters can destroy your valuable data: Forever in an instant.
|
It happens to thousands of businesses every day. Many are eventually forced to close.
|
 |
NAT/Firewalls Configuration
This page provides information about the ports used by Web Secure Backup, and details on what ports need to be opened to enable Web Secure Backup to work across different networks behind a NAT/Firewall. |
TCP Port 32004 |
Web Server opens this port. All Client-Server communication including backups, restore etc. (except TCP discovery) is done through this port. If a Web Secure Server is behind a NAT/Firewall then this port needs to be opened to enable Web Secure clients to backup to this server. Opening up this port is mandatory for the core functionality of backup and restore to work in Web Secure. By default the port used by Web Secure is 32004, if you have modified the 'Backup Server Port' during installation, then you have to open the corresponding port in your NAT/Firewall. |
TCP Port 32005 |
Both Web Secure Client and Server open this port. This port is used for two purposes:
-
For all communication between the PHP module (invoked by the Web Secure browser based WebConsole) and the Web Secure C++ modules. In Web Secure, all UI requests from the browser are served by PHP pages, which in turn connect to this port to get the required data. By default the port used by Web Secure is 32005, if you have modified the 'UI Communication Port' during installation, then you have to open the corresponding port in your NAT/Firewall.
-
Web Secure peers also use this port to do a more complete discovery of each other sharing details about other peers etc. This TCP discovery is always enabled in Web Secure.
This port need not be configured in the NAT/Firewall. If so, the only feature that would not work is: Switching to a Web Secure peer behind the NAT/Firewall through the WebConsole of another Web Secure peer outside the NAT/Firewall. |
TCP Port 6060 |
This port is used by the Web Secure Web Server (Apache) to serve requests from Web Secure WebConsole (User Interface). This port is configurable. When you first installed Web Secure you would have been given an option to change this port. The NAT/Firewall should also 'allow' this port if you need the ability to connect/administer a Web Secure peer behind the NAT/Firewall.. |
Multicast Ports (UDP) 6363, 6364 |
These two multicast ports are used by Web Secure Clients and Servers for discovering peers within a subnet. In most networks, multicasting will work only within a subnet. There is no need to open these ports in firewall or NAT devices as multicast packets may not be sent across networks, anyway. Multicast discovery is enabled by default in Web Secure. |
UDP Port 32006 |
This UDP port is used in discovery of Web Secure peers in a network. Web Secure does a UDP scanning on port 32006 of all possible IP Addresses in a network to detect the presence of other Web Secure peers. There is no need to open this port in the NAT/firewall as Web Secure does the UDP scanning only within its subnet. By default, UDP network scanning is disabled in Web Secure. |
Web Secure Backup Support
|
|
|
|
Technical Features
|
|
Benefits
|
|
|
