Recent content by BitRausch

Ok. Never mind. It is the first choice since the array is the only installed device.

Hi @all, maybe this is an easy question. Today I started to upgrade my PVE 3 Server using the Update menue. During the update I am asked where grub should be installed. The choices are: "dev/sda... Array 10", "/dev/sda1 ... /boot" and "/dev/md-0 ... pveroot". Which one is the right choice here...

duhh.... OK I figured it out. I had to create a Storage for images since I only had Storage for backups... Once Storage for images was created I could select that storage in the Move disk Screen. best regards

Hello, this is maybe a stupid question but the Wiki says: I do use NFS Storage but when I hit Move Disk (I try to move a Disk from local to NFS Storage) I can only select local. Maybe I do not understand the move part ? Or does it only work for Cluster ? My pveversion: pve-manager: 3.0-23...

Are you sure about this ? In Version 3 when you do a backup in Snapshot mode and the VM is stopped the VM is put into a pre-start mode. That is the VM starts but does not boot. I think it also allocates the memory...

ok symmcom. I am out of ideas. I am not an expert on this subject. Here some things I would try/check: - remove the storage and create a new storage (just in pve. Not deleting the backup) - check network parameters including hosts, jumbo frames (if set), dns server entry... - check cpu load...

I just took a look at some documentation. Did you see this: http://pve.proxmox.com/wiki/Performance_Tweaks I am not sure if there is an updated version somewhere. Just to see if it was not a one time event can you repeat your backup 2 or 3 times and compare results. I use cache=none for RAW...

I don't think the port matters. Do you have compression and/or dedup on on your ZFS machine ? Your pool maybe above 85% full ? Maybe you can test with a regular directory (smb) on your ZFS as a backup location. See if you still get the bad performance...

I am on a Gigabit network too. I use a HP MicroServer N40L with 4 WD Red 2 TB in one RaidZ vdev. I use a second NIC in my HP as a dedicated "Backup Line". This is how mount looks like for NFS: 192.168.178.8:/RaidZ/bigone/manu on /mnt/pve/NFS-Manu type nfs...

I was looking at one of my customer side. They are using nfs in combination with OmniOS+Napp-It: storage.cfg looks like this: nfs: NFS-Manu path /mnt/pve/NFS-Manu server 192.168.178.8 export /RaidZ/bigone/manu options vers=3 content backup nodes...

maybe this can help ? before upgrading to v3 I was using "pigz" for compression. During the upgrade pigz was replaced by gzip again. Now I switched to lzo for compression which is much better and faster. Even so I am using the raw format for my Windows VM's I use "sdelete" to zero out empty...

I don't think that just looking at the performance difference is enough to make a decision. You have to look at the "big picture" and the overall solution. Meaning you need also to consider things like: - followup costs (Backup solution etc.) - management of the system (browser based or client...

ok. I just removed the file. Now HD Space Root is only 1.3 GB in size. Thank you all for your help !