Using TAR to write multiple sessions to the same tape

WojtekO · 04-22-2009, 02:50 PM

Hello there everyone

I'm trying to write multiple sessions to the same tape but am only seeing the last write.

Ex:

Code:

tar -czf /dev/st0 /dir1
tar -czf /dev/st0 /dir2
tar -czf /dev/st0 /dir3
tar -czf /dev/st0 /dir4

And when I do

Code:

tar -tzf /dev/st0

It only displays the contents of /dir4

I've googled a bit and found the following to be able to write multiple sessions:

Code:

tctl -f /dev/rmt0 rewind
tar cvf /dev/rmt0 filenametosave

tctl -f /dev/rmt0 rewind
tctl -f /dev/rmt0.1 fsf 1
tar cvf /dev/rmt0 filenametosave

tctl -f /dev/rmt0 rewind
tctl -f /dev/rmt0.1 fsf 2
tar cvf /dev/rmt0 filenametosave

Thing is, I don't have rmt0 in my /dev/, only st0 and nst0. Nor do I have a tctl executable. I use mt and mtx.

The tape box is a Dell PowerVault TL2000 that the previous system admin here setup to be accessed through another box.

Any input would be greatly appreciated.

Thank You

michaelk · 04-22-2009, 03:59 PM

/dev/st0 will automatically rewind the tape after the current task completes but /dev/nst0 does not.

WojtekO · 04-22-2009, 04:23 PM

Thank you michaelk, it seems to be working fine now with nst0 and using fsf 1 to navigate the tape before listing files.

Now, is there a way to list the size of the files on the tape?
Say I'm building a script, how could it tell how much space is left on the tape?

Code:

[root@leda Wojtek]# mt -f /dev/nst0 eod
[root@leda Wojtek]# mt -f /dev/nst0 tell
/dev/nst0: Input/output error
[root@leda Wojtek]# mt -f /dev/nst0 status
SCSI 2 tape drive:
File number=4, block number=-1, partition=0.
Tape block size 0 bytes. Density code 0x46 (no translation).
Soft error count since last status=0
General status bits on (9010000):
 EOD ONLINE IM_REP_EN

It only tells me that there's 4 files but nothing else.
Any special command I can do? Or the only way is prior to backing up, calculate the total size of a backup, save it to a file, and everytime I'm backing up, add the totals to know how much was backed up and substract that from the total capacity of 1 tape?

michaelk · 04-22-2009, 04:48 PM

AFAIK you need to manually calculate.

WojtekO · 04-22-2009, 04:59 PM

The only problem I see with this is that if I use the -z flag with tar, I'll calculate the uncompressed filesize, not exactly the size that what will be written to tape.

Anyone got any suggestions? besides not compressing the files?

choogendyk · 04-22-2009, 06:10 PM

You can't ever really be sure. If you compress before writing to tape, and have the tape's hardware compression turned off, then you have a better idea. If you rely on the tape's hardware compression, then you have less of an idea.

Typically, backup software writes to tape until it gets an end of tape error. That's how it knows that the tape is full. Then the last thing that was written has to be written again to a new tape.

WojtekO · 04-23-2009, 03:33 PM

We won't be using hardware compression, so that should help.
I'm thinking of gziping every file that will be archived, total the size into a file and then tar that to tape without the -z flag.
I think that should give me a quite accurate size.

Now, another question came to my mind.
Is there a way to rename the tape as seen in mtx status?

Code:

[root@leda Sun]# mtx status
  Storage Changer /dev/sg5:1 Drives, 24 Slots ( 1 Import/Export )
Data Transfer Element 0:Full (Storage Element 1 Loaded):VolumeTag = 000001L4
      Storage Element 1:Empty
      Storage Element 2:Full :VolumeTag=000002L4
      Storage Element 3:Full :VolumeTag=000003L4
      Storage Element 4:Full :VolumeTag=000004L4
      Storage Element 5:Full :VolumeTag=000005L4
      Storage Element 6:Full :VolumeTag=000006L4
      Storage Element 7:Full :VolumeTag=000007L4
      Storage Element 8:Full :VolumeTag=000008L4
      Storage Element 9:Full :VolumeTag=000009L4
      Storage Element 10:Full :VolumeTag=000010L4
      Storage Element 11:Empty
      Storage Element 12:Empty
      Storage Element 13:Empty
      Storage Element 14:Empty
      Storage Element 15:Empty
      Storage Element 16:Empty
      Storage Element 17:Empty
      Storage Element 18:Empty
      Storage Element 19:Empty
      Storage Element 20:Empty
      Storage Element 21:Empty
      Storage Element 22:Empty
      Storage Element 23:Empty
      Storage Element 24 IMPORT/EXPORT:Empty

Like instead of of seeing 000002L4, it would display ProjectX-Tape2

And yet another question, does an LTO4 tape really hold 800GB of data or like a hard drive it contains less because it's formatted?

Thank You

michaelk · 04-23-2009, 04:31 PM

I do not think it is possible
http://www.fermit.org.uk/~awr/quickies/sun_l9_mtx.html
http://74.125.95.132/search?q=cache:...&ct=clnk&gl=us

WojtekO · 04-23-2009, 07:44 PM

Thanks for the links Michaelk, I appreciate it.

What about the 800GB size? Is that the real usable size?

michaelk · 04-23-2009, 07:47 PM

choogendyk · 04-23-2009, 09:25 PM

If you kept a separate file that was a table of barcodes with your project names, then you could write a perl script that takes the mtx output and fills in the project names. It wouldn't take too much effort, and, once done, you'd have it for repeated use.

As far as compression goes, I would compress, whether you choose hardware compression or gzip. You could get an estimate of how compressible your data is and then make a conservative guess at how much to put on the tapes. If you have a lot of data to backup, you shouldn't have to make do with less than the tape can hold (that is, settling for 800G, when it could perhaps hold half again or twice that depending on your data).