Great. Thanks a lot.
Is there an elegant way to handle holidays? So inserting the Friday-tape at thursday f.e. will not work if we use several friday-tapes for the month - or will the Friday-tape get written to on thurday _AND_ friday with the new allocation policy?
Yes, that's exactly what i want!
Currently my pool hat "allocate always" and "retention 7 days" - which isn't what i want.
Setting it to "allocate fr. 17:00" and "retention 7 days" while running the jobs mo-fr 18:00 would result in a new set every friday evening, starting with ALL chunks of the...
I already keep snapshots of everything on 2 separate systems (one on-site, one synced to my location) - the tape backup is just the last resort and should only contain the most recent snapshot of each vm ("last only" - works as expected)
I also read trough the documentation, but some parts are...
as the topic tells: I need some help as i'm quite new to the topic of tape backups.
We have a PBS saving around 8TB of machines (last snapshot) per day.
Our media pool should have 4-5 friday/weekend-tapes (full) and 4 weektime tapes for incremential changes to keep the duration low...
I had some quite good results with just adding 2 SSDs as l2arc. That dropped GC and other tasks by some magnitudes. Only problem left is the "not so perfect" read/write-rate to the tape device (around 150mb/s, with tops up to 180mb/s and some dips)
The l2arc - in contrast to special devices -...
It seems like PBS doesn't like RAID-controllers, even when they pass-trough the drive entirely.
Maybe it relies on some exotic commands that aren't 100% emulated / passed to the drive which linux and other backup tools don't use.
The controller itself never has been a problem. It passes trough tape-devices.
Neither via mt/tar/dd-stuff directly on linux, nor via iscsi or esos talking to a windows-server-vm with veritas backup - everything was fine. So at first, it was not logical to search there. But because i got one on...
After changing the controller from an Adaptec ASR-5805 to a dumb LSI one, at least the labeling works.
Right now i've started a backup job, drive is idling:
2022-03-29T09:09:11+02:00: update media online status
2022-03-29T09:09:11+02:00: media set uuid: 548b060a-9dc0-4750-9f41-e1a115063440...
Sorry, didn't notice that.
The lto8 is factory new, the lto7 worked for veritas and linux (dd) for several years. no encryption or any extraordinary stuff.
dmesg stays silent during the error.
Is there a way to dump the communication while doing a task? Maybe that way we can get any further...
Thank you very much in advance!
The drive is a plain standard LTO8, freshly bought. Vendordiagnostics don't show any problems.
The media is nothing special,
proxmox-tape status shows some written data:
│ Name │ Value │...
i freshly connected a new LTO8-drive to my PBS. The drive gets detected. Eject, Erase, Format etc works fine.
But i'm unable to label the media.
I only get the following error:
"media read error - read failed - scsi command failed: transport error"
The tape itself is a brand new sony...
Inside the PBS-gui i am able to change the note of the complete node, not only its items.
That way, even if the folder isn't open, i am able to see which VM is contained.
I wasn't able to find a command to do this via shell, thus i'm not able to extend the script to do this.
Does anyone know how...