Search results

You should use 802.3ad but you need also configure this on the switch. /etc/network/interfaces # 802.3adauto bond0 iface bond0 inet manual slaves eth0 eth1 bond_miimon 100 bond_mode 4

I don't think you need 32GB Ram. This can be true for some exchange servers but not true for most of linux servers. Adding more RAM is no problem you can do it also later. You need a real hardware raid controller and i would say 2 more disks to get a raid10 array.

Why not using ntp? You could also set the date/time with ntpdate NTPSERVER this also works

I think as long as i only need openVZ it is the best to save resources. If i need windows or a own kernel with special modules then i use KVM. I have about 90% openvz and 10% kvm.

On the hardware node there should be only needed services like nrpe to monitor the system and other things like that. All other things should run in a vm.

I think rebooting servers without any reason is only creating downtime. If there is no problem why do you do it? I reboot only after kernel updates. I also think that you will loose performance. Some services will have to rebuild or create their cache.

Nobody should even think about it to create a template for debian oldstable. Some guys would use it and did not know what they do. There are no more security updates for oldstable anymore. Everybody should use now squeeze. I think this is no bug this is a child-proof lock ;)

For 1:1 nat you also need one public ip per host. The only you can do is port forwarding. If you need ssl you can forget it then you need one ip per server. Ips are not expensive so buy some ips and you will not have the problem. I looked at my isp there a /29 cost 29€ for setup and no running...

Have two options: define it in the ports.conf file or in pve.conf file

You should bind the Apache to the lan ip address. Then nobody should be able to connect to the wan address.

I think yes but i didn't would use such gaming/overclocking mainboards for servers. If you try to use onboard raid controllers you will have problems because that are in most cases raidcontroller which only work by software (driver). Simple try it then you will see it.

The DL380G5 runs out of the box. You should install the hp tools. You can download them as deb packages.

First try to install failban and configure it. You should also configure a iptables firewall on proxmox host. Then you can set limits and log everything. Or you think about a real firewall like pfSense. Then you can also install snort an IDS. All this things help as long as you have only...

What does the bios show?

To avoid such problems use blkid. With this id all partitions have a unique id.