Search results

  1. M

    strange things on vzdump

    Has solutions for 2.6.32-19-pve?
  2. M

    Add network interface

    How add vmnet bridge to network interface like 802.1q (eth0.123) via web-interface without reboot server?
  3. M

    Help for Storage Model strategy

    How to store the CTs and VMs on the node's hdd which is a hypervisor for them? Only in migration to move data to the hard disk target node.
  4. M

    Help for Storage Model strategy

    I would not have external storage. No money... But I have some servers (nodes) with their HDD. I would like to use theirs own HDD and only for theirs own CT and VM. Only in migration at neighboring node transfer data at same node's hdd.
  5. M

    Help for Storage Model strategy

    In this case CT of second and third nodes will be placed at hdd of first node. It's not right. Note I don't want use NFS strongly.
  6. M

    Help for Storage Model strategy

    Do you offer to do so? For example three nodes with their local storage (hdd), NFS mount in /etc/fstab, in Proxmox's WEB-interface storages added as Direcotry: Node #1: /var/lib/vz01 - local fs /var/lib/vz02 - nfs to node2:/var/lib/vz02 /var/lib/vz03 - nfs to node3:/var/lib/vz03 Node #2...
  7. M

    Help for Storage Model strategy

    I don't want to use DRDB because this is not perfect work in primary/primary mode. Also when I add more nodes DRDB can not work with them. I wanted to create partitions at each node and share their via iSCSI, then use these target at their owners for CT and VM (after being added the targets to...
  8. M

    Help for Storage Model strategy

    Now I have two servers (nodes) in cluster and have not network storage. Each node has its own local storage for its own CT and VM. I want to use migration and backup to neighboring nodes. What strategy for data storage should I choose? Also I want to easily add new nodes later.