Version compatibility: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
(moved discussion to the discussion page, added info about amrecover compatibility) |
||
| Line 1: | Line 1: | ||
= Compatibility = | |||
Amanda has used several on-the-wire protocols to communicate between the server and backup clients, and not all of them have been compatible. | Amanda has used several on-the-wire protocols to communicate between the server and backup clients, and not all of them have been compatible. | ||
Versions of Amanda prior to about 2.3 used a different protocol which is not compatible. 2.3 is very old so this is not of general interest. | * Versions of Amanda prior to about 2.3 used a different protocol which is not compatible. 2.3 is very old so this is not of general interest. | ||
The Amanda 2.4 series all use the same protocol. This protocol has support for extensibility. Generally upgrading clients or servers along the 2.4 branch does not cause difficulty. | * The Amanda 2.4 series all use the same protocol. This protocol has support for extensibility. Generally upgrading clients or servers along the 2.4 branch does not cause difficulty. | ||
Amanda 2.5 uses the same protocol as 2.4. One can use a 2.5 server with 2.4 clients and a 2.4 server with 2.5 clients. | * Amanda 2.5 uses the same protocol as 2.4, except for amrecover. One can use a 2.5 server with 2.4 clients and a 2.4 server with 2.5 clients, so long as one uses <tt>oldamrecover</tt> on 2.5 clients when communicating with a 2.5 server. | ||
To restore a dump created with the tapesplit_size option using amrecover, | To restore a dump created with the tapesplit_size option using amrecover, you need a 2.5 server + 2.5 client. (Extracting that backup using only shell, mt and dd is also possible.) | ||
you need a 2.5 server + 2.5 client. (Extracting that backup using | |||
only shell, mt and dd is also possible.) | |||
= Upgrading = | |||
The recommended course for upgrades is to upgrade the server to 2.5 first, and test backups and restores before upgrading clients. Both upgrades should be seamless, although you may wish to adjust your server configuration to account for new features like [[How To:Split Dumps Across Tapes|tape spanning]]. | |||
Revision as of 21:02, 4 January 2008
Compatibility
Amanda has used several on-the-wire protocols to communicate between the server and backup clients, and not all of them have been compatible.
- Versions of Amanda prior to about 2.3 used a different protocol which is not compatible. 2.3 is very old so this is not of general interest.
- The Amanda 2.4 series all use the same protocol. This protocol has support for extensibility. Generally upgrading clients or servers along the 2.4 branch does not cause difficulty.
- Amanda 2.5 uses the same protocol as 2.4, except for amrecover. One can use a 2.5 server with 2.4 clients and a 2.4 server with 2.5 clients, so long as one uses oldamrecover on 2.5 clients when communicating with a 2.5 server.
To restore a dump created with the tapesplit_size option using amrecover, you need a 2.5 server + 2.5 client. (Extracting that backup using only shell, mt and dd is also possible.)
Upgrading
The recommended course for upgrades is to upgrade the server to 2.5 first, and test backups and restores before upgrading clients. Both upgrades should be seamless, although you may wish to adjust your server configuration to account for new features like tape spanning.