Networker

Re: [Networker] Migrating backup data from tool "A" to tool "B"

2006-10-06 08:01:33
Subject: Re: [Networker] Migrating backup data from tool "A" to tool "B"
From: Stan Horwitz <stan AT TEMPLE DOT EDU>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Fri, 6 Oct 2006 07:51:43 -0400
On Oct 6, 2006, at 6:15 AM, Gaddy wrote:

Ok, this is a bit off topic,
but I have been asked recently how to migrate data on tapes from
TSM to NetWorker (or NetBackup to TSM or the like).

And I haven't found an easy answer yet.

My theoretical migration scheme would be like this <very first guess>:

1.) have a very big disk (SATA array) at hand
2.) develop a new systematic order for the migrated data sets
    e.g. $clientname_$savetime
3.) create directories/volumes named according to this order
4.) restore datasets into this directory with $OldTool
5.) backup directories/volumes with $NewTool

While this could(?) be a solution for filesystems,
I expect a lot trouble for all those application data
(i.e. R/3, Oracle, Exchange, etc.), which will not
fit easily into a directory scheme like this.
And most of the restores would require the application on
the "migration client".

Sure I know I could keep the old servers/tapes/drives/licenses etc.

Maybe some else has a better idea, but if this were me, I would set aside a server that has whatever is needed (e.g., Windows SQL, Oracle, SAP, Novell, etc.) to recover any type of data that might need to be recovered. The biggest fly in the ointment is licensing for the software you might need such as Oracle.

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

<Prev in Thread] Current Thread [Next in Thread>