Adsm 3.1.2? ouch.. that's old and not even supported anymore.. Anyways I started with 3.7 so other then that descrepency...
1. There shouldn't be a problem although you should be aware that it will increase the load on all your servers as they'll now have to also compress the files when doing backups. I've seen this become an issue on servers that already experience a significant load. 2. The only time I've seen a "no space on server" type error in regards to compression is when you have caching enabled on your disk pools. So caching + compression would cause problems. But each without the other worked great. 3. again the only problem is that all clients now will experience an increased load due to having to compress the data. For most this isn't an issue but some environments may have a client or two that under normal operations experience quite a load already. Gerald Wichmann Sr. Systems Development Engineer Zantaz, Inc. 925.598.3099 w 408.836.9062 c -----Original Message----- From: Julie Xu [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 02, 2002 8:31 PM To: [EMAIL PROTECTED] Subject: compress setup question Dear adsmer, we have setup our adsm server version 3.1.2 for all the client to compress depend no client. Compression: Client's Choice Our client do not want the choice and they want me to setup compress at server end. Before I do it, I would like to get advice about: 1. For WinNT servers, the force compress will cause problem at time of backup/restory? 2. The reason they do not like to make decision about compress is that some machine is ok to compress; some will get error as "no space on server". Can it be avoided by setup compress on server? 3. What is the petiential problem related adsm server setup force compress. Regards Julie Julie Xu Unix/Network Administrator Information Technology Directorate University of Westen Sydney, Campbelltown Campbelltown NSW 2560 Phone: 61 02 4620-3098 Mobile: 0416 179 868 Email: [EMAIL PROTECTED]
