> From: Long, Matt [mailto:Matt.Long AT marriott DOT com]
> Sent: Wednesday 08 November, 2000 21:49

>       Currently, I am fighting an OTM issue which is causing
> my NT client backups to fail.  Recently, we have upgraded from
> version 3.2 to version 3.4 as an eval customer.  I am concerned
> in that since we have upgraded, all of our NT client backups are
> failing with a return code 1 which indicates that
> the client was unable to backup certain registry files etc.

 status 1 isn't a real failure, a backup has been done, but some
files couldn't be backuped. on Microsoft Windows, it's usually because
of applications locking files, Microsoft Office is the most
common culprit.

 the netbackup client is "registry-aware", you shouldn't get
error when backuping the registry files, and you doesn't
need OTM for that. see page 84 of "NetBackup administration
guide", topic "Microsoft Windows registry backup" for more
details on this.

 did you check the "problems with backup" on the report app? it
will tell you what files exactly will cause this.

> Also, when I go into the admin GUI and try to "configure" the client,
> I am getting a "unable to connect to Master" error. I have stopped and
> restarted everything and am still getting these errors.

 i think you have a network connection problem, check the network
problem resolution part in the troubleshooting guide.

 fx

#include <std_disclaimer.h>

--
     fx AT veritas DOT com       | the only problem with troubleshooting
François-Xavier Peretmere | is that sometimes trouble shoots back
 http://www.veritas.com/  |               - alt.sysadmin.recovery