I have TSM server 5.5.2 and some older Netware clients. Netware 6.5 and most are TSM client 5.2.2.0. These are our Network file shares.
The current volumes are NSS (TSM server filespace type "NTW:LONG".) The team is about to migrate all Netware over to Linux, SLES 10 and the TSM filespace type will be "NSS". They have done a small one as a test and this is how it comes out. Several questions. 1. I know that disimilar filesystem types can't be backed up/restored. So, with the old Netware filespaces, I need to keep them around to restore old data to one spare Netware server and then they copy data to new system if a restore is needed after migrating. I thought I would ask though if there is anyway that this can be migrated as this is probably a popular move and maybe there is a way to do it, even if a third party something. Ha ha! I know is a dumb question, but I see Andy Raibeck's standard line about that frequently! 2. With the new Linux servers, they will also implement Novell's Dynamic Storage Technology. This will enable the infrequent accessed files to be dumped off to a "shadow" space on SATA drives. Does anybody know if this speeds up the TSM backup? In other words, does the "file scan" done when backups run also have to scan this also each day? Any experienced do's/don'ts about this from TSM point of view? Thanks, David Longo ##################################### This message is for the named person's use only. It may contain private, proprietary, or legally privileged information. No privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Health First reserves the right to monitor all e-mail communications through its networks. Any views or opinions expressed in this message are solely those of the individual sender, except (1) where the message states such views or opinions are on behalf of a particular entity; and (2) the sender is authorized by the entity to give such views or opinions. #####################################
