AS Prior IT in association with the Ritchot Chamber of Commerce is pleased to present the Cyber Senior Project to the community.
The introductions will be made during the Refresh & Rejuvenate Expo Jan 30 @ 9:00 am – 10:00 am at the TransCanada Center in Ile des Chênes, Manitoba
The Ritchot Chamber of Commerce will have a boot setup where École Gabrielle Roy students will be able to show how they can help seniors in their discovery of the new technologies.
CapoDiGrande will be serving coffee for this event
Source: Home | Cyber Seniors
A Very Happy New Year to you too..! May 2014 be the best it can be!
When you talk about Domino, think of a house.. Each one have the same basic components (Kitchen, Living Room etc) but each are laid out, sized, decorated differently. No one house will fit everyone’s need.
For that reason, no simple answer can be given on how the final Domino architecture will look like until all the questions are studies and answered..
-How many servers?
-Where are those servers?
-Where are the users?
-Are those users mobile?
-Those users require fast connection or not ?
-Can those users use iNotes?
-What is the backup design ?
-What is the recovery plan?
-What is the company SLA on eMail?
-Do users connect with iPhone, iPad, etc…?
-What are the local infrastructures?
-Are those servers fast?
-How many power users ?
and so much more questions….
DAOS will greatly reduce the space needed on your servers. It will also greatly reduce the backup times! So enabling it on all servers is a very good thing.
Below, I give you a scenario as it comes out on first draft….. Please note that ANY of what you will find below could change based on the answers of questions asked. Therefore, this document is NOT complete and is written only to help you understand/design your infrastructure.
First, some statements….
-ALL server should have DAOS and all mailfile should be DAOS’ified.
-NLO should NEVER be replicated/copied to another server. Let each Domino server do their own work.
-Your servers should be in a cluster and users should be assigned a HOME server that is closest to them.
-Compression should be enabled between servers
-You should make use of Local Replica where ever you can (Laptop and workstations users (Make sure they work with the local replica and replicate in the background)). Your users will really appreciate opening that 15 MB PDF in a few seconds…! 🙂 And YOU will appreciate the fact users are not using bandwidth and server resources to open the same attachment over and over…
-You should make use of iNotes where you can (This will help having to update client on everyone’s machine (Yes, the new iNotes client is VERY nice! I have users who never saw the difference)
-Users should have a failover replica on a second server. This can be decided by PingTime, location etc…. I would not have replicas on all the servers.
-You can disable the NLO Encryption but another set of question comes with this decision.
-If you are using SAN disk, Transaction logs should be on different spindles.. Not only in different logical partitions…..This is very important for performance.
Second, an example to help you.
Remember that this is written on the fly and is ONLY an example to help you. .
Server 1 Europe (ServerEurope1) Based in Paris
Server 2 North America (ServerNA2) Based in New York
Server 3 Asia (ServerAsia3). Based in Singapore
Those servers should be in a cluster. This cluster will be High Availability.
Users will have their HOME server based on their closest locations
Tokyo users will be in Singapore
Toronto users will be in New York
London users will be in Paris
What I would do is give them a Failover replica on the second closest server.
Users could have a Failover replica on the other 2 servers but I am not sure this is required… But it is up to you to decide. (Think about backup also)
Example, An Australian user who ‘s HOME server is the ServerAsia3, would have their replicated (fail over copy) on the ServerEurope1.
Just remember that once you define where users will go, this will become YOUR logic. Make sure you have it down on paper to explain future administrators so they keep using it. Without it, things could get confusing VERY fast.
On ALL 3 servers, I would create a folder structure as follow
Your server structure would look something like this…
ServerEurope1/EuropeMail (all Europe Users would have this server as their HOME server and their files would be in the EuropeMail server)
ServerEurope1/AsiaMail (Asia users with this server as a failover would have a replica of their mail in that folder.)
ServerErope1/NorthAMail (North American users with this server as a failover would have a replica of their mail in that folder.)
The other 2 servers would be set the same way.. (showing only ServerAsia3 as example)
ALL servers would have TransacLog enabled.
ALL 3 servers would be DAOS enabled for ALL mailfile no matter which folder they reside in
ALL users mail file would be DAOSed on ALL server where it resides (Local AND replicated files)
You could backup the mailfiles locally.You could backup only the Active mail files.(But backup is a complete new discussion…..)
ServerAsia3/AsiaMail (Backup only the mail files in the AsiaMail folder and backup the whole NLO folder)
ServerEurope1/EuropeMail (Backup only the mail files in the EuropeMail folder and backup the whole NLO folder)
ServerNorthAMail/NorthAMail (Backup only the mail files in the NorthAMail folder and backup the whole NLO folder)
Perhaps you want to have ALL the mailfiles replicated to a 4th server called Europe2 and then backup this one ONLY…. Backup ALL the mail files and ALL the NLO… BUT then again, this is decided after discussion with other groups.
Bottom line, Ideas about the final architecture are virtually endless. Domino can be tweaked to run faster and more efficiently depending on YOUR environment and specific needs.. NO one size fits all…
Remember that what ever decision you take will involve other department. You need to keep them close to you. They need to understand what you want to do so they can help the best they can. The more they know, the better YOUR side will work with THEIR side…….
I would be happy to contract with you locally or remotely on that project.
Hope this helps.
Last night was New Year’s Eve. My son went to a house party while my daughter went to a bar.
While she was just coming out of being sick with coughing, she just went to have fun and no drink and drove home.
My son on the other hand drank. They are still on driving probationary permit and the tolerance is 0.
We thought our kids responsibility and it pays off now..
Both on Christmas and New Year’s eve, he called us to go pick him up.
Yes, it was about 2am but that is the price to pay to have great kids as ours..
We do not regret one minute of it and we will always be there for them. No matter where, no matter what time and no matter why…..
I am wondering what versions of Lotus Notes/Domino are in use at your site and if there are plans to upgrade.
As we all know, there is a definite dissatisfaction of the Domino environment in many places but what we have seen is that Domino is not at the most current version.
I have worked with a a company where Notes was laid on the cutting board.
The problems we found were multiple but simply said,
– The servers were at version 6.0 when 7.x was Gold release
– The servers were in a cluster but permissions prevented them to talk to each other
– One of the division was working with Notes 4.5 (this is not a typo!)- The administrators were so overwhelmed by the daily problems that improving the system was not an option
We were able to work together with the administrators (Domino, Network, Hardware, Servers, Linux etc) and build a solid environment which maintained a 99.9% uptime for over 4 years now.
All the new features such as DAOS, IDVault, Cloud access to email were implemented along with full mobility. This increased the user satisfaction to the point where Domino has been put back on it’s legs and is no longer scheduled for the knife.
So the question is… What version and features are you using?