Hi TSMers,
today a software house come and showed us some nice software: one to virtualize physical libraries and show them as a CIFS/NFS share and another one to migrate files (HSM). The HSM software has a centralized management interface that make it more "user friendly" than TSM HSM.
I asked the person about backups :) and he said that the software just set the "Offline bit" of migrated files:
does someone know how TSM BA client handles this kind of "offline bit set" files? Will this really reduce backup time as he stated? I don't think so...
I know that HSM and BA client work "together" to avoid sending the same file twice to TSM server, but I think that in a mixed environment a TSM backup could recall all migrated files..
Would like to hear from you :)
today a software house come and showed us some nice software: one to virtualize physical libraries and show them as a CIFS/NFS share and another one to migrate files (HSM). The HSM software has a centralized management interface that make it more "user friendly" than TSM HSM.
I asked the person about backups :) and he said that the software just set the "Offline bit" of migrated files:
does someone know how TSM BA client handles this kind of "offline bit set" files? Will this really reduce backup time as he stated? I don't think so...
I know that HSM and BA client work "together" to avoid sending the same file twice to TSM server, but I think that in a mixed environment a TSM backup could recall all migrated files..
Would like to hear from you :)