O
O
other_letter2015-08-19 14:27:01
System administration
other_letter, 2015-08-19 14:27:01

How to be more productive?

There is a server. DL380 if important.
It has 2012 on it. The main goal was once file storage and backup storage.
But life is life - they put Hyper-V on it and now the second DC hangs out there. There is also 2012.
Important - the main machine is not in the domain and should not be in it.
What I don't like - when something cunning and heavy is backed up (so some features with a partial backup of SQL databases, for example) - the disk subsystem clogs up sourly. From here tupnyak and on virtualka. Unprincipled, but ... ugly .
What do you advise?
Comes to mind:
1. Give one of the network cards (there are 4 of them on a piece of iron) for the needs of a specific virtual machine. The network is generally not heavily loaded.
2. And what to do with disks? now there is a simple set of disks, so in general, you can try to give one of them to be eaten by a virtual machine. Will it have an effect?

Answer the question

In order to leave comments, you need to log in

2 answer(s)
A
Artem @Jump, 2015-08-19
Tag

First, virtualization is very slow disk operations.
Give disks directly to virtual machines if you don't want to give up virtualization.
Secondly, figure out why the actual brakes, i.e. how much data at what speed goes to the backup?
You can set a fast disk as a cache or make a zero raid to receive a backup, and only then, slowly copy it to slow storage screws.

D
DastiX, 2015-08-19
@DastiX

share resources at the material level - two.

A very strange phrase. Explain.
Yes, and reliability will decrease relatively.
This is generally a pearl. Read what RAID is for.
My advice:
Make RAID, two disk groups, one for the system, the other for virtual machines. And everything will be fine)

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question