1. Replication of the website through litespeed. Imagine for a company who has a backup-machine with litespeed running as hot-standby or just as backup. This company has to keep both machines up-to-date, maybe this can be handled by litespeed through replication. It is maybe far fetched, but it is a nice idea if you make modifications to files (webpages, css, php and so on) on the master webserver and this webserver will update the replication servers (backup , hotstandby ones) Or initiated by litespeed, through the admin interface, you can even use default unix commands!? 2. Load-balancing. You can have load-balancing implemented if you have replication. the backup/replication server can be a just read (of course) server. Maybe you can even configure in the admin interface how the load is balanced, say 80% to 20%, or whatever you like to have it! This can depend on how powerfull the other machine is.