Continuation of: thread52-1094470
I hate my first thread was archived. Priorities just get in the way sometimes.... I'm finally back on this dilemma.
The story is:
Production has an Autoloader with a Single LTO-2 drive.
Test has a Single LTO-2 drive.
Production & test are on same OS - AIX 5.1.
I create my backup tapes with mkvgback.
Production can restore tapes made from production.
Test can restore tapes made from test.
I try to put Production's tape in Test's drive and do a list backup contents.
I see it list all the LV's and files, but then it errors:
sbread: Invalid status record type
Tape control error on /dev/rmt1.1
I/O error
I have tried restores through SMIT and command line, the tape is rewound, the restore does work on the original machine. I have tried many different tapes created on many different days. All fail with the same results. No files are ever restored.
My latest update: The ATAPE driver is now loaded on both machines, but the problem still exists. (It was previously only on production.) Do I need to reboot the test server maybe for the driver to take hold?
Any ideas?
Thanks in advance,
Debi
I hate my first thread was archived. Priorities just get in the way sometimes.... I'm finally back on this dilemma.
The story is:
Production has an Autoloader with a Single LTO-2 drive.
Test has a Single LTO-2 drive.
Production & test are on same OS - AIX 5.1.
I create my backup tapes with mkvgback.
Production can restore tapes made from production.
Test can restore tapes made from test.
I try to put Production's tape in Test's drive and do a list backup contents.
I see it list all the LV's and files, but then it errors:
sbread: Invalid status record type
Tape control error on /dev/rmt1.1
I/O error
I have tried restores through SMIT and command line, the tape is rewound, the restore does work on the original machine. I have tried many different tapes created on many different days. All fail with the same results. No files are ever restored.
My latest update: The ATAPE driver is now loaded on both machines, but the problem still exists. (It was previously only on production.) Do I need to reboot the test server maybe for the driver to take hold?
Any ideas?
Thanks in advance,
Debi