[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference decwet::networker

Title:	NetWorker
Notice:	kits - 12-14, problem reporting - 41.*, basics 1-100
Moderator:	DECWET::RANDALL.com::lenox

Created:	Thu Oct 10 1996
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	750
Total number of notes:	3361

516.0. "Changing server to client, how to do old restores?" by SANITY::LEMONS (And we thank you for your support.) Fri Mar 21 1997 12:12

    Currently, we have ~9 Digital UNIX / TZ8n7 / NetWorker systesm backing
    up our UNIX data.  Next week, all of the clients of these 9 backup
    servers will be migrated to our Digital UNIX / TL822 server.  Of
    course, these 9 systems will also become clients of the Digital UNIX /
    TL822 server.  So we will first remove the NetWorker software currently
    installed, and re-install it as a client.
    
    But what happens if we want to do a restore from a tape created on one
    of these 9 servers before their migration to the DU / TL822 server? 
    Should we leave the media and / or file index around on these systems.? 
    Will we be able to do a restore on a system that is, now, a NetWorker
    client?
    
    Confused.
    tl

T.R Title User Personal
Name Date Lines

516.1 you choose DECWET::EVANS NSR Engineering Fri Mar 21 1997 13:33 21

T.R	Title	User	Personal Name	Date	Lines
516.1	you choose	DECWET::EVANS	NSR Engineering	`Fri Mar 21 1997 13:33`	21
	choice #1 all info assumed to reside on New Server: when a recover is needed, take media from old server, scanner it into new server, and recover it. choice #2 old info resides on old servers, with new saves on new server. When recover needed involving data from old server, issue recover to that server. Leaving old servers as fully functional "servers" also means they are clients too (to other servers). So, in essence, setup new server, make it back up old servers, and stop all backups on old servers, but leave them alone otherwise. When contents of old server tapes are "expired", remove the volume (physically too). choice #3 mass migration. scanner in all old media to new server, and then start saving data. remove old server s/w from all old servers, installing client binaries only. misc: in general, as long as the system nodename/OS does not change, it matters little if the data is "here" or "there"... go to nodename desired, issue recover using server desired, and wait for files to come back.

choice #1
   all info assumed to reside on New Server: when a recover is needed, take
   media from old server, scanner it into new server, and recover it.

choice #2
   old info resides on old servers, with new saves on new server. When recover
   needed involving data from old server, issue recover to that server.
   Leaving old servers as fully functional "servers" also means they are
   clients too (to other servers). So, in essence, setup new server, make it
   back up old servers, and stop all backups on old servers, but leave them
   alone otherwise. When contents of old server tapes are "expired", remove
   the volume (physically too).

choice #3
   mass migration. scanner in all old media to new server, and then start
   saving data. remove old server s/w from all old servers, installing 
   client binaries only.

misc: in general, as long as the system nodename/OS does not change, it matters
 little if the data is "here" or "there"... go to nodename desired, issue
 recover using server desired, and wait for files to come back.