Thank you very much for your response, Stefan. You mean, according to this updates, Amanda can store backup data not in a single tape but in categorized tapes(storage) as user wants, right?
I will test about these features to verify the behavior. Thanks again. 2017-01-05 1:36 GMT+09:00 Stefan G. Weichinger <[email protected]>: > Am 2016-12-13 um 08:51 schrieb Chaerin Kim: > >> Hello. >> >> I have used Amanda 3.3.9 for backup. >> But I heard Amanda 3.4.1 supports Rest API, so I tried this version. >> >> When I tested this version, I found a tapelist file format was changed. >> There are additional features, such as pool, storage, etc. >> I searched about these features, but there is little data and I couldn't >> find example about this. >> I want to know why this features are added, and what is the concept. >> > > I share your wish for learning about these new terms and concepts. > The man page for amanda.conf mentions them but doesn't really explain them > or provide examples. > > So we can (a) ask Jean-Louis ;-) or (b) try and error a bit. > > *warning* : just guessing below > > For (b) I start with "amadmin config myconf" and find a block "DEFINE > STORAGE myconf". As the manpage tells there is a default storage defined at > least (implicitly). And you can define additional storages to make amanda > store its dumps to. > > As far as I understand a key parameter might be "dump-selection": by > setting that we can configure behavior like: > > put DLEs a,b,c to storage "one" > put full dumps to storage "two" > put incrementals of DLEs d,e,f to storage "three" > etc > > right? > > Additional you have the vaulting pool(s) definition for amvault. > > Interesting features for bigger installations ... looking forward to some > tests. > > Stefan > >
