Thanks, will do.
My case it targeted at scripting and using proxmox-backup-server in shell
While using ITDT, oh yes, I understand "best effort".
In pbs, works for about 90% of moving, some format / barcode. But then I guess after that it gets confused. Drive is listed, just fails.
Currently system is stock debian, just wanted to make sure there nothing else that might affect it...
Guess I am missing the secret ingredient, " scsi 2:0:0:0: TLR Disabled"
In my case, trying to get more use out of some old hardware , "scsi 2:0:0:0: Sequential-Access IBM ULTRIUM-TD4 C7QH PQ: 0 ANSI: 3"
Reading IBM drives are suppose to support TLR, not sure how far back, but this...
I sure this is not a PBS problem, but just asking my peers..
I have really high i/o delay in my pbs dashboard.
I have determined its the disk I have attached via iscsi.
Its (the iscsi stuff) low end and not the best setup, and I have accepted that.
But is it possible to make the i/o delay...
I too have noticed this, hence the search. Seem to affect both my win and linux VMs. Have to kill the VM and restart. Still searching, fingers crossed..
In one of my cases (Ubuntu server 20.04.4) its listed as;
00:02.0 VGA compatible controller: Red Hat, Inc. Virtio GPU (rev 01)
Thanks, was kind of the same logic I was thinking. Thanks for your response. Was hoping that since they are already running under 6.x my chances were better than average. But as we all know, that might not mean much !
Well I updated my personel proxmox to 7.1 with no real issues yet. But all my guests are linux
I have a 4 node system here that I manage, but I still have a few 2003 servers and one 2000.
I skimmed over a few posts , one that sticks out is lack of newer virto nic drivers on newer releases...
hate to answer this with a "I don't know"
I have my prune set every 30 mins, maybe it was there at the beginning of the backup but later was purged during the backup
Garbage collection 1x a week.
Or, I have seen failed snapshots appear, and I later cleared. Maybe these?
I have a feeling...
I get an occasional error such as the following
2021-06-02T03:14:47-04:00: backup snapshot vm/117/2021-06-01T00:00:15Z
2021-06-02T03:15:03-04:00: TASK ERROR: store 'pbspsiscsi', unable to load chunk '4ddfecd9ad1d749184e4bac5592f3506a7bfb107706778a68ed006b22fd61d18' - blob too small (0...
its dirty messy, but its what I use when I have to. Maybe others have a more elegant solution. Looking , I think it first revinds, writes weof, goes off line
Anyway I have to edit it each time for what I do since I have several libraries I have worked with.
the line for i in # # # # # #...
Ahh.. I can understand that one. Makes sense.
I have same type library with LTO6 units on baroes, was hesitant to pull it for use here till I was sure.
Like most mom and pop operations IT budget is $0, maybe I can get them to spurge on a few LTO4 tapes
Thanks for your insight and help
Gonna guess the library has the whole encryption wrapped up with its "key" for encryption and prevents the drive
I have look in various places and have not found any firmware to make this work.
I don't use any keys within pbs, but guess we still check?
root@pbs172:~/ITDT# stenc -f...
Hope I get the right info, as far as firmware, I think its the latest from the dell site that had LTO4 included with the library update firmware.
Not sure how comfortable I might feel trying to shoehorn another firmware into it, even tho it is IBM
I'll look around again, I was ok till this...
Can format ok, barcode/label fails
decode data encryption caps page failed - not external data encryption control capable
There are no encryption keys configured, let me know if I can grab any info
root@pbs172:~# proxmox-tape status --drive drive1