D
D
Dmitry Lebedev2015-07-03 08:39:59
linux
Dmitry Lebedev, 2015-07-03 08:39:59

How to organize Backup servers?

Hello.
Tell me how to organize a competent Backup of Windows Server (2008-2012) and Centos servers. It is desirable free ^_^
There is Windows Server 2012 R2 - Hyper-V on it 3 virtual machines:

  1. Windows Server 2012R2 (DC,DNS)
  2. Windows Server 2012R2 (Symantec Endpoint Security Manager, DFS, AD FS)
  3. Ubuntu 14.10 LTS (Squid).

A couple of CentOS servers on VMWare ESXI (which is free, not from vSpehere).
Physical Windows Server 2008 (DC, DHCP, DNS)
It is necessary to organize Backup of all this economy. There are many options:
  • Veeam Backup https://www.veeam.com/ru/
  • Bacula habrahabr.ru/post/260955
  • ntbackup
  • rdiff
  • Worker-peasant backup under Windows habrahabr.ru/post/246743

As I understand it, basically all options are simply copying data and packing it into an archive.
But the question is, how quickly can I deploy the same Windows Server 2008 (DC, DHCP, DNS) in case of a crash?
Keeping DHCP, DNS, etc?
I want a generic method. For for Windows, you can use ntbackup, for Linux, the same rdiff.
Give advice comrades/colleagues.

Answer the question

In order to leave comments, you need to log in

4 answer(s)
E
Eugene, 2015-07-03
@k3NGuru

judging by your config, you have a second DC - virtual.
If you have no other services on the physical DC except AD,DHCP,DNS, then recovery after a failure can be done quite slowly, especially if you first raise the DHCP service on the virtual DC and create a copy of the area there, but do not activate it.
the server stores its copy of the directory service, DNS is integrated into AD. (meaning, of course, the general case). Judging by the description of the free Veeam product, windows machines will be backed up with the help of windows server backup. wsb and in its purest form can make bare metal backups, to restore from which it is enough to boot from the installation disk to get a restored copy of the system at the time of backup within 40-50 minutes (on my hardware).
When a physical DC fails, we activate DHCP for clients on the virtual server. With all your settings - for the duration of the restoration of the physical DC.
In general, before choosing a solution, I would first divide all data into three areas:
- Backup of servers (OS Windows Server, CentOs,
- Backup of system data and service data (AD, AD FS, etc.)
- Backup of user data.
And already further I thought how and what and what to back up.

S
Sergey Kovalev, 2015-07-03
@Sergey-S-Kovalev

| But the question is, how quickly can I deploy the same Windows Server 2008 (DC, DHCP, DNS) in case of a crash?
| Keeping DHCP, DNS, etc?
If iron suffers, then you will not be able to quickly.
Virtualize everything. Hyper-V is quite suitable, in the latest edition it is very good.
Veeam Backup & Recovery is amazing, even in the free edition.

M
Maxim Kovalenko, 2015-07-03
@maxxx_kovalenko

For backup and full recovery of virtual machines on ESXi, I can recommend ghettoVCB.sh - Free alternative for backing up VM's for ESX(i)
Works on all esxi https://communities.vmware.com/docs/DOC-8760
Read more www.vmgu .ru/articles/vmware-esx-ghetto-vcb-manual

S
shaazz, 2015-07-07
@shaazz

And why is a standard Windows backup not suitable? There don't seem to be many servers. After all, you can specify a folder in the file storage when backing up, and test the recovery scenario on a virtual machine.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question