- A copy is stored locally
- A copy can be saved to a fileserver or NAS
- A copy can be sent to a TSM server
The product does not require TSM and looks to solve a lot of problems with large fileservers. I’ll admit, I want this as soon as it comes available. The one problem I see is who is going to buy the disk required for this?
The second piece I have seen a need for some time is HSM for Windows. Well wait no longer, it’s here! IBM has just announced HSM for Windows. As with other products it allows you to migrate files off of a server when it reaches a certain age but provides for file level granularity, as the file is now a stub linked to the actual file in TSM storage. To learn more about both products you can read up on them here.
How would it compete with Windows versioning and MS WSUS? What are the benefits of using CDP over WSUS?ReplyDelete
Nice site, another addition in my browser favorites.
I am new to TSM hence visiting the related websites, one of those is this one.
In my opinion,ReplyDelete
The benefit would be you can use this product cross platform and intergrate it into your existing TSM infastructure.
The other feature is that it's an instant backup. So technically backups would be done when work stops on the server if it ever does. It's going to be a big disk resource need, I don't see how going to tape every time a file is changed or created will would work well, but if you got the disk (I have a lot of FastT so I'm ok) it will really help with fileserver restore requests. I have had a couple requests for file restores where the file never was backed up because something happened to it before it could be backed up later that night.ReplyDelete
Agreed, it may be worth increasing my disk pool space to accommodate these activities during the day. Assuming the integration with TSM will use your management classes and allow the files to traverse your storage hierarchy.ReplyDelete