Was the directory restored to the DR machine?

That would ensure the directories of both the original and target systems 
are the same - including user and account local attributes.

Hopefully, you did NOT use BULDACCT to re-create the directory.

I believe restoring a directory from a store tape is always superior to the 
use of buldacct when performing a system "clone".


-----------------------------------------------------------------------
-
Gilles Schipper
GSA Inc.
HP System Administration Specialists
300 John Street, Box 87651   Thornhill, ON Canada L3T 7R4
Voice: 905.889.3000	Fax: 905.889.3001  
email:  [log in to unmask]  web: http://www.gsainc.com
-----------------------------------------------------------------------
-


---------- Original Message -----------
From: Raymond Familar <[log in to unmask]>
To: [log in to unmask]
Sent: Tue, 6 Dec 2005 10:13:11 -0500
Subject: [HP3000-L] MPE local attribute on userid

> Hello.
> I recently performed a failover test for an applicaiton that tracks some
> userid information.  The local attribute (LOC ATTR) is tracked, so 
> when a user logs in on the DR system, if their LOC ATTR does not 
> match, then they cannot log in.  I do not recall this being much of 
> an issue in past DR tests, so I assume they matched during the last 
> test (6-12 months ago). Under what circumstances would a userid LOC 
> ATTR be changed.  We use Vesoft Sec/3000 in our environment.
> 
> Thanks.
> Ray
> 
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
------- End of Original Message -------

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *