of your data and then archive it? This
will keep the TSM DB size very small as for one archive you will have just
one entry in TSM database. Of course partial retrieval is not possible in
this case.
On Sat, Aug 25, 2012 at 8:48 AM, amit jain amit12.j...@gmail.com wrote:
Hi,
We
Hi,
We are planning to change our archive strategy. Planning to do one time
full backup and then create two backup sets, latter delete the backups.
With this strategy we can have single tsm instance to cover most of our
archive needs, as this will not fill up the TSM DB size. Also we can have
performance. These is also bottleneck
from the TSM client side. Seeing IO wait from the client side.
Thanks
Amit
On Sat, Mar 10, 2012 at 9:08 PM, amit jain amit12.j...@gmail.com wrote:
Hi,
I have to backup large data ~ 300TB and have small DISK POOL SIZE 500GB. I
have 3 filespaces, backing up
Hi,
I have to backup large data ~ 300TB and have small DISK POOL SIZE 500GB. I
have 3 filespaces, backing up on single node. I am triggering multiple
dsmc, dividing the filespace on directories. I have 15 E06 Tape drives
and can allocate 5 drives for this backup.
If I run multiple dsmc
