On Thu, Dec 08, 2016 at 07:24:08AM -0500, Jean-Louis Martineau wrote: > On 08/12/16 03:56 AM, Heiko Schlittermann wrote: > > Jon LaBadie <[email protected]> (Do 08 Dez 2016 06:05:17 CET): > > > I'm thinking of systems, like laptops, that are booted > > > irregularly and are unlikely to be running during the > > > normal backup time period. > > … > > > > You're looking for amdump_client, aren't you? (I never used it, but > > according to the manual it *should* be what you're looking for.) > > > > Please correct me, if I'm wrong. > > You are right. > amdump_client works by running 'amdump CONF HOST DISKNAME' on the > server,which require the server to connect to the client. >
So amdump_client is run on the client? How does it communicate that to the server? Any extra configuration needed on the server? Is the "--no-taper" option used on the server, or specified on amdump_client? Any problem if multiple clients try to do amdump_client at the same time? I'd guess this is not available for windows clients using ZWC. Is there a write-up on setting up amdump_client beyond the manpage? > In 3.4, there is an improved program: ambackup > This program works by sending the dump directly to the server, it doesn't > need to connect to the client. > This program also works if the client is behind a VPN. > > Jean-Louis >>> End of included message <<< -- Jon H. LaBadie [email protected] 11226 South Shore Rd. (703) 787-0688 (H) Reston, VA 20190 (703) 935-6720 (C)
