Re: Netware 6 TSM 5.2 Client
Jim, first of all thanks for the reply. One question though, these will be shared cluster volumes so what does the /cluster=off do in the entry below? regards, Rowan O'Donoghue Technical Services Manager Unitech Systems Bracken Business Park Bracken Road Sandyford Industrial Estate Dublin 18. Tel: + 353 - 1 - 2942300 Fax: + 353 - 1 - 2942319 www.unitech-ie.com Jim Kirkman [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 25/09/2003 19:47 Please respond to [EMAIL PROTECTED] To [EMAIL PROTECTED] cc Subject Re: Netware 6 TSM 5.2 Client Here you go. A search on nss volumes on search.adsm.org will turn this up rather quickly. Novell's TID 10065605 and patch NW6SMS1A.EXE are needed. In particular, you need the following entry in the smsrun.bas file: nlmArray = Array(SMDR, TSA600 /cluster=off, TSAPROXY)in order for TSM to recognize the clustered volumes. Rowan O'Donoghue wrote: Hi all! I have a customer who has just implemented Netware 6.0 and the TSM 5.2 client. Everything seems to be ok apart from the fact that there are SAN volumes which are assigned to the Netware 6 server (filespace called DATA01:) which are not recognised by the TSM client. the SYS: volume is being picked up no problem. Even if I try and perform an INC DATA01:\ it comes back telling me that the filespace is invalid. Anyone have the same problem? All the Netware 5 servers with the TSM 5.1 client are ok - then again, I dont have any SAN attached volumes on these servers. regards, Rowan O'Donoghue Technical Services Manager Unitech Systems Bracken Business Park Bracken Road Sandyford Industrial Estate Dublin 18. Tel: + 353 - 1 - 2942300 Fax: + 353 - 1 - 2942319 www.unitech-ie.com -- Jim Kirkman AIS - Systems UNC-Chapel Hill 966-5884
Re: Netware 6 TSM 5.2 Client
Rowan, The cluster off switch tells the TSAs that your backup software is not cluster-aware. That is, it isn't cluster-aware in terms of using NetWare's TSA calls to back up the cluster. Without the /cluster=off switch, querying the server via the TSA will return only the SYS volume and any other local volumes. With that switch present, all volumes, including cluster volumes will be returned. TSM has it's own cluster parameter for the dsm.opt file (clusternode yes) that adds cluster support for TSM. While this isn't the native Novell method, it works fine. It names the TSM filespaces something like ClusterName/Volume instead of ServerName/Volume. Matt Zufelt Southern Utah University [EMAIL PROTECTED] 9/26/2003 2:26:44 AM Jim, first of all thanks for the reply. One question though, these will be shared cluster volumes so what does the /cluster=off do in the entry below? regards, Rowan O'Donoghue Technical Services Manager Unitech Systems Bracken Business Park Bracken Road Sandyford Industrial Estate Dublin 18. Tel: + 353 - 1 - 2942300 Fax: + 353 - 1 - 2942319 www.unitech-ie.com
Netware 6 TSM 5.2 Client
Hi all! I have a customer who has just implemented Netware 6.0 and the TSM 5.2 client. Everything seems to be ok apart from the fact that there are SAN volumes which are assigned to the Netware 6 server (filespace called DATA01:) which are not recognised by the TSM client. the SYS: volume is being picked up no problem. Even if I try and perform an INC DATA01:\ it comes back telling me that the filespace is invalid. Anyone have the same problem? All the Netware 5 servers with the TSM 5.1 client are ok - then again, I dont have any SAN attached volumes on these servers. regards, Rowan O'Donoghue Technical Services Manager Unitech Systems Bracken Business Park Bracken Road Sandyford Industrial Estate Dublin 18. Tel: + 353 - 1 - 2942300 Fax: + 353 - 1 - 2942319 www.unitech-ie.com
Re: Netware 6 TSM 5.2 Client
Here you go. A search on nss volumes on search.adsm.org will turn this up rather quickly. Novell's TID 10065605 and patch NW6SMS1A.EXE are needed. In particular, you need the following entry in the smsrun.bas file: nlmArray = Array(SMDR, TSA600 /cluster=off, TSAPROXY)in order for TSM to recognize the clustered volumes. Rowan O'Donoghue wrote: Hi all! I have a customer who has just implemented Netware 6.0 and the TSM 5.2 client. Everything seems to be ok apart from the fact that there are SAN volumes which are assigned to the Netware 6 server (filespace called DATA01:) which are not recognised by the TSM client. the SYS: volume is being picked up no problem. Even if I try and perform an INC DATA01:\ it comes back telling me that the filespace is invalid. Anyone have the same problem? All the Netware 5 servers with the TSM 5.1 client are ok - then again, I dont have any SAN attached volumes on these servers. regards, Rowan O'Donoghue Technical Services Manager Unitech Systems Bracken Business Park Bracken Road Sandyford Industrial Estate Dublin 18. Tel: + 353 - 1 - 2942300 Fax: + 353 - 1 - 2942319 www.unitech-ie.com -- Jim Kirkman AIS - Systems UNC-Chapel Hill 966-5884
