Abraham Deutsch
asked on
Join a server to the network from amazon EC2
I have a window server on amazon EC2 and want to join it to the network in the office so it can replace the server in the office and provide the all services a server provides to all workstations and other devices. Domain, DNS, DHCP, Shared folders, GOP.....
Which service from amazon would do this job fast and ez, (only need it for temporarily)
Please advice
Which service from amazon would do this job fast and ez, (only need it for temporarily)
Please advice
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You have a nice high level idea, but the devil is in the details, being able to spin up an offsite replica of an onsite server is quite a complex problem, this would usually be done bay taking an image (can be VSS snapshot) based backup to an "offline" disk offsite.
Take a look at Datto as an example.
If all of your clients used hyper-v for running their servers, then you could look at hyper-v replication over the internet using certificates for auth.
Bear in mind, that to be able to keep an offsite server replica up to date, requires bandwidth roughly equivalent to the amount of data change on the source...
Take a look at Datto as an example.
If all of your clients used hyper-v for running their servers, then you could look at hyper-v replication over the internet using certificates for auth.
Bear in mind, that to be able to keep an offsite server replica up to date, requires bandwidth roughly equivalent to the amount of data change on the source...
ASKER
I am currently looking on this product http://www.cloudberrylab.com/ but I told them that the main feature is missing bringing it in to the network. And thy claim it's something Amazon offers out of the box. Which is not the way I see it and seems you as well.
Cloudberry backup can restore to EC2 (or baremetal or hyper-v or vmware) , and the backups would continue, you could then restore again to bare metal (or hyper-v or vmare), but there is no way to "move" the EC2 instance.
In any event, you would still need the VPN to AWS as I detailed previously.
As an alternative idea, You could keep a suitably specified hyper-v/vmware host ready to have a backup restored to which you could then take onsite.
Have you calculated the AWS S3 costs of using cloudberry for one of your clients ? It may be significantly more than you expect...
In any event, you would still need the VPN to AWS as I detailed previously.
As an alternative idea, You could keep a suitably specified hyper-v/vmware host ready to have a backup restored to which you could then take onsite.
Have you calculated the AWS S3 costs of using cloudberry for one of your clients ? It may be significantly more than you expect...
ASKER
With the alternative way I will only able to offer onside backup as it would be impossible from my side to handle this much of bandwidth (once the clientele base starts growing)
Re cost amazing AWS is only 0.03 a GB and cloud Barry is a one time fee of $59 par year but the problem is when there is a need for a restore if it I'll do it to my machine the download will take a significant amount of time, and can take easy 24 hours to be back in production.
Re cost amazing AWS is only 0.03 a GB and cloud Barry is a one time fee of $59 par year but the problem is when there is a need for a restore if it I'll do it to my machine the download will take a significant amount of time, and can take easy 24 hours to be back in production.
Do remember that the $0.03 per month is for data stored on S3, so as an exampe, if you had a very small file server of say 100GB, your base cost would be only $3 per month if no files change, if you have 10Gb of changed files per day, and the smallest billing period for Amazon is one month, so your additional cost will be $0.30 * 20 working days in a month = $6, so your actual cost would be $9 per month, three times higher that just the base storage. if you had 1TB on the file server with the same percentage of file change, then your costs go from $30 per month to $90 per month, or $1080 per year.
If you compare to using windows backup with external USB disks, the pricing may start to lose some of its initial appeal.
If you compare to using windows backup with external USB disks, the pricing may start to lose some of its initial appeal.
Why don't to use Cloudberry for onsite backups? In case of disaster you can restore a server locally (in other words fast enough) and if the entire site is burned/flooded/(insert your option) you can restore it to EC2 and proceed with functioning.
Having AD/DNS/DHCP/Fileshare server on EC2 VM will require high I/O and thus expensive instance with a drive (for file sharing) big enough to store all the data but it will be EBS and thus $0.09/GB/mo.
You have to get all the numbers down in order to see the full picture.
Having AD/DNS/DHCP/Fileshare server on EC2 VM will require high I/O and thus expensive instance with a drive (for file sharing) big enough to store all the data but it will be EBS and thus $0.09/GB/mo.
You have to get all the numbers down in order to see the full picture.
ASKER
I agree but in order in case of a total onsite disaster to be able to do a restore to EC2 it needs to be first backed up to AWS [without a EC2 running and only use EC2 if needed] correct?
but again comes up the question how to join the EC2 to the network.
but if I understand you correctly a local backup should be enough for a server failure and even with a NAS drive [not sure yet on the model which sport] have the server up in running as a VM. And in case total onsite disaster to recover relocate and set up all other stuff will give enough time to download from AWS to do a local restore even with large amount of date. Correct?
PS wondering what is the point of them putting in so much effort in restore to EC2 when i don't see how to make use of it.
but again comes up the question how to join the EC2 to the network.
but if I understand you correctly a local backup should be enough for a server failure and even with a NAS drive [not sure yet on the model which sport] have the server up in running as a VM. And in case total onsite disaster to recover relocate and set up all other stuff will give enough time to download from AWS to do a local restore even with large amount of date. Correct?
PS wondering what is the point of them putting in so much effort in restore to EC2 when i don't see how to make use of it.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You wouldn't be joining the restored instance on EC2 to the domain, in a single server environment it would _be_ the domain...
Once restored, you would have to change its IP address, and have a method of providing a VPN from the remote site to access it. DHCP could be handled by the router/firewall.
Once restored, you would have to change its IP address, and have a method of providing a VPN from the remote site to access it. DHCP could be handled by the router/firewall.
As far as I understand you can't have a server in EC2 with no DHCP configured thus addressing is not an issue. Computer names may cause some issue though.
ASKER
As well in order for the workstation to access their files on the server in must be part of the network.
So assuming that in order to have the office up and running the server in EC2 will need to be joined to the network, I come back to initial question what service from Amazon is needed and is it something out of the box as cloud Barry claims so it's fair to promise a client that in case of a disaster his office will be operational in a short period of time?
So assuming that in order to have the office up and running the server in EC2 will need to be joined to the network, I come back to initial question what service from Amazon is needed and is it something out of the box as cloud Barry claims so it's fair to promise a client that in case of a disaster his office will be operational in a short period of time?
In case of workstations you can use Amazon Workspaces and just RDP to them from your desktops.
I think you can promise only what's achievable is both RTO and RPO described properly.
I think you can promise only what's achievable is both RTO and RPO described properly.
ASKER
Sorry I did not explain my self correctly.
What I was referring to is. In case the server fails its only the server all workstations in the office are in perfect condition re hardware but in order to be in production in need the server for to have access to its file on the server. in order this to happen the server need to be on the network.
PS I has set a appointment with Datto to discuss their product.
What I was referring to is. In case the server fails its only the server all workstations in the office are in perfect condition re hardware but in order to be in production in need the server for to have access to its file on the server. in order this to happen the server need to be on the network.
PS I has set a appointment with Datto to discuss their product.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
as I said in my first answer, you would need a VPN to connect the instance of the server running on AWS to the site...
+1 to ArneLovius' comment above
Too much work to set up in the event you actually needed it. And it's going to be a pressure situation, with everyone looking over your shoulder as you set it all up - VPN, your hardware firewall, DNS, DHCP, AD, etc etc
Too much work to set up in the event you actually needed it. And it's going to be a pressure situation, with everyone looking over your shoulder as you set it all up - VPN, your hardware firewall, DNS, DHCP, AD, etc etc
ASKER
although ArneLovius answered my initial question, but the "solution" to accomplish my goal was bast answered by Kaffiend and assisted solution by David Atkin.
Thank you all
Thank you all
ASKER
What I came up, do a daily backup to AWS when a disaster happens get the server from AWS running in EC2 and with the service (which in question) get the server into the network so the office is up and running.