Search:

Following on from my ancient posting that the Windows Client Community Edition hasn't been updated in years, it looks like even the recent major update of
the Linux client to 3.4 hasn't prompted an...

Attempting to install the Amanda 3.4 server RPM on CentOS 6 results in missing dependencies
(there were some new perl dependencies not listed below, so I yum install'ed those before
trying the...

I just installed Amanda 3.3.9 on CentOS 6 (I've been running 3.X on that platform for years) and noticed that amstatus displays MB figures to 10 decimal places, which is very ugly indeed and didn't...

Amanda does a nice job encrypting backups and most users probably configure multiple hosts to be backed up with it. However, this means that all hosts have the same encryption key and that encryption...

The RPM does make a mess of the amanda-security.conf install - it puts it in /etc/amanda rather than /etc and it sets the ownership to amandabackup rather than root. Also note that the directory...

Whilst you can get the ZIP64'ed Windows dump onto a Linux tape server using amfetchdump, the dump format is highly proprietary and actually goes against the grain of the "community edition", IMHO. I...

You do realise that reading this forum is much like watching tumbleweed blowing past? There seems to be very few responses from the actual Amanda developers and the Windows client has bit-rotted for...

If you don't do anything, the error code 318 just repeats day after day and never fixes itself. Apart from "318" having no meaning (text error messages would be nice), I've still only found that...

The Windows client has been stuck on version 3.3 (yes, bizarrely no third dot field in the version) for over 2 years now, despite fresh dates being claimed on the download pages for 3.3.1-3.3.6. For...

We've seen a steadily growing number of 5-digit named files (yes, with no file extension) in the misc directory underneath the
Zmanda Windows Client 3.3 install tree. These seem to be a multiple of...

Just a few remarks about 3.3.4, which generally seems to be working fine on my Linux systems:

* For the 4th consecutive time, the release notes fail to fully explain what fixes where made, with...

Inexplicably, the Zmanda Windows client has a different version number from the Linux equivalent. For example, as I write this, the latest Linux release is 3.3.4, whereas the latest Windows release...

I use a Linux server to backup Windows clients with Amanda 3.3.X and haven't had any problems with incrementals. The dumptype global stuff isn't listed in the original posting, so I'm assuming that's...

We've installed the Zmanda Windows Client 3.3.2 on various Windows servers and then recently started upgrading them to 3.3.3. However, when looking at the version number of the client in the list of...

I know this is a "me too" posting, but if the Amanda Windows client's output (in ZIP64) cannot be extracted by amrecover on the Linux Amanda server side (whereas Linux Amanda client dumps *can* be),...

Thanks for the fix! I'd already restarted the ZWC services with no joy, but examining the backup history, I noticed that we'd had one successful level zero and then many failures to do an incremental...

At the moment, we're using just program "DUMP" in the Amanda server dumptype config for Zmanda Windows clients (i.e. no client-side compression or encryption). There are several issues about...

It's high time Amanda devs realised that the defaults for Amanda have the serious potential to batter both Amanda clients and Amanda servers involved in the backup scheme. With Web and DB servers...

I got the same error this week and it's because I have two Amanda sets using the same autoloader. Hence, I want to Amanda to ignore the "other set's" tapes of course (i.e. I don't want any attempt to...

Although I didn't think CPU on the client was an issue, disabling client side compression on the clients and enabling on the server (which is dual quad core - we may even use pigz if that improves...

By setting inparallel=1 and the same client options (fast compression but no encryption) on Windows VM vs. Linux VM clients both using the same SAN (and the same network setup), there is a massive...

Apart from the dismal backup speed of the Amanda Windows client I'm seeing (between 2 to 20 times slower speeds than the Linux Amanda client using the same SAN - and, yes, inparallel=1 to avoid...

You put the exclusions in the Windows dumptype you're using in amanda.conf on the Amanda server (also specify the dumptype in the disklist file as the third field of course). For example, your...

It's a single SAN (OK, 2 SANs with one of them on standby as an automatic failover using drbd and heartbeat) presented as a set of volumes to the clients that ultimately use the same RAID container....

Although Amanda has an overall network bandwidth throttle config option, it's quite surprising that there isn't a per-client disk read throttle setting too. In our situation, we're using the same SAN...