Results 1 to 2 of 2

Thread: Best use of backup sets

Hybrid View

  1. #1

    Default Best use of backup sets

    I'm debating the best way to use backup sets.

    I have about 20 servers that I am backing up for a total of about 20Gb. of data.

    I have 2 Tb of media (disks) to back up to.

    I have one backup server dedicated to receiving the backups and moving them to the storage media.

    I can easily create 5-6 backup sets distributing them in logical categories by products and type of servers. ex. product 1 web servers. product 1 DBs, product 2 web servers and so on.

    But I am thinking making sure the runs do not overlap and so on will mean having to keep track of things a little more.

    Would it be easier to have only one backup set?

    Are their benefits to having more than one set?
    Last edited by mikep; August 4th, 2009 at 06:00 AM.

  2. #2
    Join Date
    Oct 2005


    From your description, it appears that you are backing up to disks. Amanda writes to the media sequentially from the holding disk. If you divide the data into multiple backup sets, you can perform the backup jobs in parallel from holding disks to the storage media.
    If you divide the data into multiple DLEs, you can backup each DLE in parallel from the client to holding disk (assuming there is sufficient network bandwidth between server and

    If you have multiple backup sets, you can do restores also in parallel.


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts