With this plugin the destination of your dump no longer has to be a named file. It can now also be a stdin of an arbitrary command or a port on any host on your network.
Similarly, an existing dump can be LOADed from stdout of a command or from a port on any host.
Why would you want that? A number of possibilities open up:
- offload the CPU-intensive compression by running the compression utility on another machine;
- archive dumps on another host without NFS issues
- integrate with an off-site backup provider
- encrypt dumps without unencrypted data ever touching temporary storage;
- transfer databases from one server to another /directly/
- use the included “sybdump” utility (open sourced) in your own scripts, processing dumps without waiting for them to finish…
Pipe from Virtual Estates, uses the undocumented Backupserver API for the sybmultbuf to load in their libpipe.so / libpipe.dll file. The end of the pipe can be just about anything, meaning you could conceivably dump your database using their pipe plugin, compress the stream, encrypt it, transform the data stream to morse code, send it over HAM radio (as morse code) to your buddy on another continent to reverse the method, loading it into her database.