One addition step that I failed to note earlier. I am not sure if it was
required, but I did go back into
fedora_core4_linux_machine> nsradmin
an add an NSR client for the client name that I was recovering.
Thanks,
Jim Carlson
RTI International
3040 Cornwallis Road
MCNC-Bldg. 1, Room 318
Research Triangle Park, North Carolina 27709
jcarlson AT rti DOT org
ph 919-248-9238
fax 919-248-1455
This email and its attachments contain confidential information which is
intended solely for the use of the addressee and may contain information
that is legally privileged, confidential or exempt from disclosure and
may be subject to a Mutual Non-Disclosure Agreement between the sender
and the recipient. It is intended only for the individual(s) or entity
named above and to others who have been specifically authorized to
receive it. If you are not the intended recipient, please do not read,
copy, use or disclose the contents of this communication to other.
Please notify the sender that you have received this e-mail in error by
calling the phone number indicated or by e-mail, and delete the e-mail
(including any attachment/s) subsequently.
-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
On Behalf Of Carlson, Jim
Sent: Friday, June 23, 2006 9:33 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Re-establishing systems - archiving
I apologize for the error in sending before I had completed my steps -
Here is the e-mail again with the completions -
I want to thank all of those who responded with suggestions. I am
recovering data and for the most part it is going okay. I am sharing
this with the group should someone else need to do as I am having to do.
So often we are concerned with getting the data onto a tape, but do not
consider how someone else might have to get that data back off the tape.
In my specific case, I started with a box of tapes and thankfully, an
administer that was well organized. They maintained a log book that
identified not only the process for creating tapes, but also the
software used to create them, including a printed e-mail with the
version and license.
The only information lacking was how to recover data in an environment
outside of the network and machines of that time.
As much as I struggled to try and understand the gui, I found the
command line much better suited to use in the recovery effort.
The first thing I had to do was to get the software to recognize my tape
drive. This was done using the
fedora_core4_linux_machine> nsradmin
Running this command brought up a prompt and asked for -visual to give a
fill form type display. Moving around with arrows, I could add a NSR
Device.
I added my tape drive and saved it.
With what I needed to do, a single command did the trick. I started by
running
fedora_core4_linux_machine> scanner /dev/nst0
which gave me some additional information
scanner: scanning 8mm 5GB tape Back Up 13 July 01 on /dev/nst0
scanner: ssid 16899: host `[client name]' must be a valid host name
I then edited my /etc/host file and created an entry for [client name]
and gave it a non routable ip address.
Now all I had to do was run one command as long as the data was all from
the same client -
I created a directory that was named the label on the tape. Then for
each tape I ran
> scanner -c client_name /dev/nst0 -x uasm -rv -/=/usb/recover/tapename
I occasionally repeated
fedora_core4_linux_machine> scanner /dev/nst0
to check for additional clients.
Thanks,
Jim Carlson
RTI International
3040 Cornwallis Road
MCNC-Bldg. 1, Room 318
Research Triangle Park, North Carolina 27709
jcarlson AT rti DOT org
ph 919-248-9238
fax 919-248-1455
This email and its attachments contain confidential information which is
intended solely for the use of the addressee and may contain information
that is legally privileged, confidential or exempt from disclosure and
may be subject to a Mutual Non-Disclosure Agreement between the sender
and the recipient. It is intended only for the individual(s) or entity
named above and to others who have been specifically authorized to
receive it. If you are not the intended recipient, please do not read,
copy, use or disclose the contents of this communication to other.
Please notify the sender that you have received this e-mail in error by
calling the phone number indicated or by e-mail, and delete the e-mail
(including any attachment/s) subsequently.
-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
On Behalf Of Howard Martin
Sent: Thursday, June 15, 2006 5:22 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Re-establishing systems - archiving
On Wed, 14 Jun 2006 10:26:12 -0400, Albert Eddie Contractor AFRPA CIO/IT
<Eddie.Albert AT AFRPA.PENTAGON.AF DOT MIL> wrote:
>This is actually an excellent example for a lot of us to look at.
>
>My org is required to be able to restore files from at minimum 10 years
>but recently restored files from the 1988. You can imagine how
>technology has changed.
>
>I am thinking it would be prudent to perform data migrations to new
>technologies every 2 years or so. Just to ensure we are able to restore
>data from current technology as fast as possible.
>
>Any thoughts or experience on this subject? /ALE
>
I consider that backups can serve 2 purposes - using a recent backup to
replace lost or corrupted files/disks and to archive data. The first
generally only needs a few weeks worth of backups and it is relatively
simple to ensure that these are readable, the second requires a
different
strategy. To recover data that has been kept for more than a few months
you need to make sure that either the backups are kept compatible with
you
current backup software and hardware or the software and hardware used
in
making the archived backups should be kept available. A few years ago I
was asked to keep some data for 2 years, to the surorise of the
requestor
instead of putting a recent backup in the back of a dusty cupboard I
specified the format of the data on the tape and used our existing
DLT7000
to create 2 tapes, these were kept in different geographical locations
adn
were to be checked for readability every 6 months at which point if a
tape
was unreadable a copy of the other tape would be made to replace it and
if
the software or hardware was improved/updated then one or both tapes
(depending on the timescale of complete removal of the old
hardware/software) would be transfered using the new infrastructure.
This
resulted in rewriting the tapes when we started using LTO-1. I stated
that
this was a cheap solution and there was no way I know of to 100%
guarantee
that the data would be recoverable - more copies and testing them more
often would raise the cost of the solution.
Oh and I almost forgot the tapes were stored in temperature and humidity
controlled rooms within their plastic cases (to keep out dust) and kept
on
edge (to stop tape slippage ).
If I had to keep data for legal reasons I would make damn sure that I
would not be blamable for loss of archived data.
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu
if you have any problems
wit this list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu
if you have any problems
wit this list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu
if you have any problems
wit this list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|
