When I do backups to disk with TSM, it writes backups into the same file. I have a need to have each day's backups written into a separate file. Can this be done?
If you absolutly need it, then create a Disk Storage Pool for each day of the week and a schedule for day for every host.
When using TSM disk storage pools, it is not overwriting any data. This is where migration levels come into play. If your disk pool is set to migrate @ 90% full, then it will migrate the oldest/largest version until the low migration rate is met.
Thanks for the reply. I'm going to be terse on details, but having each client's backup for a single day in a single file allows me to perform certain desirable actions.
I'm really green on TSM, so I apologize for the newbie questions. I believe that all TSM backups go first to disk, then to a secondary area that is a user-selected medium (tape, disk, etc.). I want the backups that are sent to that seconday area (which will be on disk, in my case) to be written such that each client's backup is a separate file on each day.
Thanks for the suggestion of creating a different Disk Storage Pool for each day of the week. If I want to keep, perhaps, multiple weeks on secondary disk (with each backup in a separate file), can this idea be extended?
Also, is creating these separate Disk Storage Pools and schedules a big deal, or very easy?
TSM can be backed up to disk and/or tape first. It will all depend on how you set up your copy groups. TSM does not save the backed up data into a file, it is in a sequential disk pool/tape pool wherever you have it. It does not backup to a file as in other products. You create a storage by using the dsmfmt -data commands which formats a file into the size of your stg pool. You can however use collocation which keeps the clients file seperate from each other, but using this has performance hit.
It will not be easy to create a seperate schedule/storage pool if that is the route you take. Every host has to have a schedule for each day of the week, so if you have 10 clients that is 70 schedules. You will also have to create the storage pools that will eat your disk alive.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.