Move mail server off-site. Need another DC?
A client would like to move away from in-house host physical email server, which runs MDaemon.
MDaemon is a simple mail server - not complicated like Exchange.
They'd like to move to DRFortress (DRF) datacenter. There, we'll setup the mail server in a vm.
DRF does provide firewall services.
They currently have a separate dc in-house.
Question: Will or should they also setup another dc at DRF?
MDaemon is a simple mail server - not complicated like Exchange.
They'd like to move to DRFortress (DRF) datacenter. There, we'll setup the mail server in a vm.
DRF does provide firewall services.
They currently have a separate dc in-house.
Question: Will or should they also setup another dc at DRF?
ASKER
Hi arnold...
Everything is self contained on the server. It is currently a member server.
We're considering moving the whole server.
Everything is self contained on the server. It is currently a member server.
We're considering moving the whole server.
It being a member server is one thing. Is the mail handling setup using webmin, or a similar tool where the data about email addresses, aliases, mailing lists, and mailboxes etc are contained within the server or does the server use the AD to authenticate users to grant them access to their emails as well as the means by which email addresses are translated to the mailbox to which a message should be delivered is part of the data in the AD.
You might not need to have/add a DC to the remote location if your mail server can be configured using openldap as a replica, the issue is that you have to maintain a link between the remote server/s and the DC in-house.
Presumably the reason to place this mail server outside your LAN is security, ?
Moving the server off site while having it link back, reduces the control you have........
There are tools as mentioned like webmin, etc. that might/could be used with a script on your inhouse side that will continually update the remote mail server with email address changes/password changes etc..........
You might not need to have/add a DC to the remote location if your mail server can be configured using openldap as a replica, the issue is that you have to maintain a link between the remote server/s and the DC in-house.
Presumably the reason to place this mail server outside your LAN is security, ?
Moving the server off site while having it link back, reduces the control you have........
There are tools as mentioned like webmin, etc. that might/could be used with a script on your inhouse side that will continually update the remote mail server with email address changes/password changes etc..........
ASKER
I just got word... They'd like to move their file server in similar fashion, at a later date... within the year.
I think it's better to setup the dc now and get that squared away. Eventually, all/most of the servers will be at DRF.
Thoughts?
I think it's better to setup the dc now and get that squared away. Eventually, all/most of the servers will be at DRF.
Thoughts?
Are they going into a CLOUD like environment?
With all that is mentioned, they seem to be going to the everything is hosted at a Datacenter and they will be using an TS/RDS to access resources there.
I would suggest you get a clear understanding on what their intentions are first rather than move a piece at a time while making adjustments to implement the changes.
you could have A DC-DC link with local workstations are thin clients that remote to server/s in the data center to perform their work.
Backup consideration/recovery for loss of connection at the office/branch,etc.
With all that is mentioned, they seem to be going to the everything is hosted at a Datacenter and they will be using an TS/RDS to access resources there.
I would suggest you get a clear understanding on what their intentions are first rather than move a piece at a time while making adjustments to implement the changes.
you could have A DC-DC link with local workstations are thin clients that remote to server/s in the data center to perform their work.
Backup consideration/recovery for loss of connection at the office/branch,etc.
ASKER
They'd like to have some kind of minimal downtime in place. It doesn't have to be zero (or close to) downtime.
Currently, everything is physical.
Server 1: DC, file server, tape and disk-to-disk backup.
Type of work: Access files on Server 1 from Dell workstations with SSD drives and 64 GB RAM. Most files are AutoCAD files, several MB each, on average. Some, 10+ MB. Balance are excel, word, jpg, pdf.
Server 2: E-mail
Server 3: A license server for various programs.
IDK how fast routine file access of several MB AutoCAD .dwg files, from 20+ users is, compared to a LAN. So, not sure going full cloud would work.
I just found out they signed a contract with DRF, for 2 server VMs. This being the case, can you recommend a good strategy to follow?
Currently, everything is physical.
Server 1: DC, file server, tape and disk-to-disk backup.
Type of work: Access files on Server 1 from Dell workstations with SSD drives and 64 GB RAM. Most files are AutoCAD files, several MB each, on average. Some, 10+ MB. Balance are excel, word, jpg, pdf.
Server 2: E-mail
Server 3: A license server for various programs.
IDK how fast routine file access of several MB AutoCAD .dwg files, from 20+ users is, compared to a LAN. So, not sure going full cloud would work.
I just found out they signed a contract with DRF, for 2 server VMs. This being the case, can you recommend a good strategy to follow?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
IS the entire email server being placed at a new location, or are they thinking of subscribing to a service where the email will be prescreen/fitlrered before delivery to the internal/in-house?