Hello,
I am starting the testing for the upgrade to Dom 6. How do I test the production server? My tets box is called test, I cannot copy accross 5.0.11 as it is, and start it - or can I? [my production server is called prod].
Should I create a new instance with a new name, and create new users, then modify all databases for testing purposes? Surel;y there is an easier way?
Please advise. I am doing this on Win2000. I assume that this is general knowledge cause I have not seen any reference to this on the upgrade manuals…
Thanks…
Subject: Testing Upgrade? Best procedure? How to simulate production server?
I copied the entire lotus folder over from my production server to my test server.
Then I isolated the test server on it’s own network with a test client machine. Then I upgraded it. Ran through all my test (r5 client, r6 client, converting mail databases to openntf template 
stuff like that).
Worked like a champ. Doesn’t disturb your production environment in the least.
Remember, Notes/Domino is not Exchange - it doesn’t burrow into the registry or WINNT directories - it’s fairly portable from machine to machine.
Subject: Thanks… got it to work…
Hello,
Well, I got this to work. FYI I copied the data files to the testing server, edited the host file, adding prod 127.0.0.1 and the the administration client connected…]
This was a great help as I do not have to reconfigure any of the custom databases, ACLs etc…
Thanks for the help here…
Subject: Testing Upgrade? Best procedure? How to simulate production server?
Hi,
I would say this depends on what you want to do. :-))
A)Do you want to test R6 and its new functions ?
B)Do you want to test if your existing applications run on R6 ?
C)Do you want to configure a server and use it later as your production server ?
In general I would suggest to set up a testing server this way:
-
Create a new server (new name)in a new domain (new name as well)
-
Make a cross certification for your whole organisation in this new domain (so you can access it with your id, but ids created in test cant access your production environment)
-
copy any of your databases to the new server (no system databases)
-
do not replicate anything back to your production environment (I would recommend it)
In such an environment you can test perfectly any new features and dont have to worry about anything (A).
You can test the functionality of all your applications as well, but you have to reconfigure them because your servername has changed.You may even encounter problems with the changed server name, but I think that this is not a disadvantage because at least you find all of the applications with “hard-coded” servernames and can repair them.(B)
To point “C” I wouldnt recommend this. It is much better to set up a server for testing and then “through” it away (together with all testing data).
Hope this helps.
Bye
Hynek