Re: ADSM v3 on Wy2k...
Thanks for the info But how the ADSM v3 (both client/server) handle the AD(Active Directory) of Win2K environment. Is it supported? If not, how we can handle that? and how do i backup the WinY2k registries? thanks in advance, -Original Message- From: Wayne T. Smith [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 09, 2002 7:21 PM To: [EMAIL PROTECTED] Subject: Re: ADSM v3 on Wy2k... Zosimo Noriega [EMAIL PROTECTED] wrote, in part.. I know that ADSM V3.1 is not compliance on Windows 2000 but i tried to use this to backup and restore files of Windows 2000 server. I haven't encounter problems, except some open files that we manage to handle it and system objects that we manage to dump into a physical files. Can you please specify clearly what are the problems, incompatibilities, or possible damage on the system when we use this for Windows 2000. If non-support from the vendor, lack of system object and unicode support, as well as lack of newer server features such as backupsets, subfile differencing and journaling are not issues of importance for you, I have seen no problem (using client v3.1.0.8 or 4.2.1.18) on a V3.1 server. I do however wish for a summary table and a serviceable server. If you mean V3.1 client, then I'd be less positive (that was positive?). The V4.2.1.18 client scheduler seems more reliable (the V3.1 scheduler was prone to permanent sleep when the network blipped or backup server was restarted) and many find the restore functions easier to use than with the older client. (We're not a big Windows client user, but have a few servers and a few dozen workstations, mostly NT and 2000). Hope this helps, wayne Wayne T. Smith [EMAIL PROTECTED] ADSM Technical Coordinator - UNET University of Maine System
ADSM v3 on Wy2k...
I know that ADSM V3.1 is not compliance on Windows 2000 but i tried to use this to backup and restore files of Windows 2000 server. I haven't encounter problems, except some open files that we manage to handle it and system objects that we manage to dump into a physical files. Can you please specify clearly what are the problems, incompatibilities, or possible damage on the system when we use this for Windows 2000. thanks in advance. Zosi Noriega
Re: ADSM v3 on Wy2k...
Zosimo Noriega [EMAIL PROTECTED] wrote, in part.. I know that ADSM V3.1 is not compliance on Windows 2000 but i tried to use this to backup and restore files of Windows 2000 server. I haven't encounter problems, except some open files that we manage to handle it and system objects that we manage to dump into a physical files. Can you please specify clearly what are the problems, incompatibilities, or possible damage on the system when we use this for Windows 2000. If non-support from the vendor, lack of system object and unicode support, as well as lack of newer server features such as backupsets, subfile differencing and journaling are not issues of importance for you, I have seen no problem (using client v3.1.0.8 or 4.2.1.18) on a V3.1 server. I do however wish for a summary table and a serviceable server. If you mean V3.1 client, then I'd be less positive (that was positive?). The V4.2.1.18 client scheduler seems more reliable (the V3.1 scheduler was prone to permanent sleep when the network blipped or backup server was restarted) and many find the restore functions easier to use than with the older client. (We're not a big Windows client user, but have a few servers and a few dozen workstations, mostly NT and 2000). Hope this helps, wayne Wayne T. Smith [EMAIL PROTECTED] ADSM Technical Coordinator - UNET University of Maine System
