I'd also recommend creating several namespaces e.g. I'm certainly not one for an "all eggs in one basket approach" whereby all roles are installed on one Server, regardless of how they are backed up. In practice working with other business', this approach has worked well for us and if I ever have to do restorations it makes the process a lot easier when it comes to expanding storage. The first question is which version of Server 2012 R2 are you running? Even if it's Standard I'd recommend having a separate Virtual Server to host DFS/File and Storage Services and to use a Virtual Disk for storage, stored on the physical drive rather than putting the drive Offline in Disk Management and assigning it to the VM. I believe a cluster has to be setup before any of the VM's are configured. Host-02 is a Dell PowerEdge T610 and has 8 x 500GB HDD (if memory serves me right, it is 2 x 500GB in Raid 1 for OS and 6 x 500GB in Raid 6 - I inherited the server 3 years ago when I took over from previous tech) I decided Veeam was a complication I didn't need.Host-01 will be a Dell PowerEdge T430 with 8 x 1TB HDDs (2 x 1TB in Raid 1 for OS, 5 x 1TB in Raid 5 for Data, 1 global hot spare) I'm using built in windows server backups and, at the moment, rsync to replicate backups. I assume the servers have DAS and therefore you can't create a Cluster? If you've got enough storage on the new server you might want to investigate allowing replication of the VMs on the older server to the new server to provide a bit more insurance against the old server failing. Have you considering remote working? if so you might want to bring up another server for RDS or DirectAccess or VPN. Your secondary DC should have DNS on it too, and DHCP failover.ĭo you have Impero or similar? You might want to create a server for that.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |