Search results

Mir sind die Dateien am Wochenende aufgefallen, nachdem ein Backuptask zum zweitenmal mit "unable to aquire lock" hängenblieb. Durch Recherche bin ich auf diesen Thread gestoßen: https://forum.proxmox.com/threads/tape-backup-unable-to-acquire-lock-on-tape.112564/ Dann schaute ich bei meiner...

Hallo, ich habe in o.g. Ordner viele .lck-Dateien zu diversen Medien. Welchen Zweck haben diese Dateien? Kann man sie einfach löschen oder wird damit das expiration-management betrieben? Hintergrund ist der, dass ein bestimmter Job regelmässig mit "can't aquire lock" stehenblieb und ich einen...

What's the purpose of these lockfiles? I have plenty of them, but is it wise to delete them? Are they maybe used by the expiry-mechanism?

Ein retired tape kann ich aber später noch im Desaster-Fall wieder einlesen bzw. auch so einfach wieder benutzen? Der Status ist nur Optik bzw. für den Jobscheduler?

Hallo, wir machen täglich ein Backup (5 Jobs, 5 Pools mit je einem Tape, wie anderswo im Forum auch als Lösung erklärt). Nun wollen wir am zweiten Freitag im Monat ein frisches Band einlegen und das Alte wegschließen (Archiv). Gibt es hierfür eine saubere Lösung? Ich dachte an ein Script...

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...

Hello, 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.

I see you're from .AT ... can you please contact me via PM if you're interested in such a controller? (gerne deutschsprachig!) Unfortunately, i wasn't able to contact you directly.

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...

➜ ~ sg_raw -r 1k /dev/tape/by-id/scsi-10WT124396-sg 12 00 00 00 60 00 SCSI Status: Good Received 96 bytes of data: 00 01 80 06 12 41 01 10 02 49 42 4d 20 20 20 20 20 ....A...IBM 10 55 4c 54 52 49 55 4d 2d 48 48 38 20 20 20 20 20 ULTRIUM-HH8 20 4e 39 4d 31 00 00 6a 00 00...

Same error: ➜ ~ proxmox-tape scan --drive LTO8 rewinding tape Error: read failed - scsi command failed: transport error ➜ ~ proxmox-tape scan --drive LTO7 rewinding tape Error: read failed - scsi command failed: transport error ➜ ~ Are there some other low-level logs i can provide?

Same thing on the LTO7-drive which. "2022-03-22T11:23:51+01:00: TASK ERROR: read failed - scsi command failed: transport error" Formating went fine!

➜ ~ proxmox-tape label --label-text full --drive LTO8 TASK ERROR: media read error - read failed - scsi command failed: transport error

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 │...