Search results

Anyone yet embrace/test tape backup yet? I have a Scalar i500 with a lto4 drive I'm going to give it a shot with But did not see any postings here yet, or maybe I missed them..

I have been using petasan for mine, with iscsi conx

Just thought I would update While the software seems to work, I have have had a few problems not related to PBS. Glusterfs seems rather slow, got timeouts and such. I just could be my gluster configuration , its not my everyday way of life and was just set up to dump rather large backup files...

I have a repurposed 8 node ScaleStorage appliance rebuilt with glusterFS. Have has it in use for over a year and used for small backup jobs from bareos. Was considering using it with PBS since it appears to be more efficient method on disk space. So, before I disturb my current...

+1, but have to be honest, my servers were running v.0.9.x and PBS was on 1.0-1. But I have started to see more often. So, I just updated libproxmox-backup-qemu0 on each server to match (without a full update to other proxmox components I understand it might be best to get the whole thing...

Just wondering best way to recover from a datastore running out of space I tried to purge the failed jobs, but was never able to recover any space, which then always gave me an error that the datastore was full Prune and GC did not seem to help, and since I just testing things out I just ended...

Time is a killer, only so many hours in a day. Gosh forbid us to impact users

Ah, yes, guess thats why I have more than 2 !? PBS, Bareos, and just plain tar/zip scripted stuff. What works is what works

Yea, been there. I was able to just test an iscsi target, seems ok so far.

Did that help any?

Is this by chance during a backup? Because I was lazy there are one or 2 vm that I did not install virtio and found that they did not survive backups.

I think I read your statement correctly, On the proxmox node, using broadcom nics, tg3 driver. Each vm uses virtio , but each vm itself resides on an iscsi/lvm proxmox share. Sorry did not mean to hyjack the thread, but I have known about the issues surrounding the tg3 driver and always...

I have a home lab that has been really stable for the past couple of years. And its running broadcom nics with the tg3 driver. I always considered myself lucky it never gave me much grief unlike the the cluster I have at work that constantly was an issue and put in Intel nics. Nice and stable...

This was brought up in another post on here somewhere that the bios settings were not working, they are saved in /tmp I think. Messed with it for a day or so, guess you could copy the bios file to a known location and modify the conf for the VM to load it. Having not done this, I'm not sure...

my hp units had broadcom nics that gave me all kinds of grief for about 8 months before I finally caved in and replaced them. was looking for that driver. with that said, all I can think of is firmware/bios updates. I might be mistaken, only have a few years of linux under my belt, but unless...

not seeing what I was looking for.

what does the output of lsmod give you?

having not used zfs in my prox environment, I can only guess these are shares on the *network* I can recall twice just ssh into a proxmox node to have it crash.. the tg3 drivers are just crap with any load in a cluster environment (that's just my opinion)

Well at least it caused me to learn more about OVS, Poked around trying different changes but still was unable to get results. Hope this new kernel does the trick ;) --------------- We're good it seems on the new kernel, but mir is making me read !!

Guess I'm missing it too. Checking wiki, need to work on this one a bit