February 28, 2007 at 11:05 am
I'm looking for ways to simplify our disaster recovery process and am curious how everyone handles recreating local users and local groups? For past tests I've manually added any local users, local groups and local group members. The problem with this approach is how to keep track of changes made in production and make sure these changes are well documented so they can be recreated at the DR site. Is there a way to backup this information or must it be keyed in manually?
Thanks, Dave
March 5, 2007 at 3:12 am
Dave
It depends on how you are doing your DR. If you are restoring all databases, including master, at the DR site, then you don't need to do anything to recreate logins and users. Otherwise, one way of doing it is to run a job every night on your production server that generates a script to recreate all logins and users. Then, on your DR site, recreate the logins, drop the existing users from your restored production database and use the script to recreate them.
John
March 5, 2007 at 11:22 am
By local users and groups I am referring to the OS-level users and groups that are local to the physical server. Sorry for the confusion.
Thanks, Dave
March 6, 2007 at 2:10 am
Dave
The same principle applies - schedule a regular job that scripts out the users and groups regularly. I don't know exactly how you'd do that, but the NET USER and NET LOCALGROUP commands should be a good place to start.
John
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply