Networker upgrade


 
Thread Tools Search this Thread
Top Forums UNIX for Dummies Questions & Answers Networker upgrade
# 1  
Old 02-13-2012
Networker upgrade

Hi Guys,

we are currently upgrading our networker to a newer version on newere hardware.

We are currently running networker 6.1.2 adn are upgrading to Networker 7.6sp2.
I was wondering if there was a way to migrate our indexes (so that from the old version(on E450) to the new version of networker (V240).

can anyone help?
 
Login or Register to Ask a Question

Previous Thread | Next Thread

7 More Discussions You Might Find Interesting

1. Solaris

Legato Networker

Hi , I have a lot of Tape device with backups from solaris sparc servers. This tape are in Legato Networker Format and now I need access and search an old backup. I know that Legato needed a Server , but this server is wrong , this down long time ago. I have a Legato Networker Server/Client... (10 Replies)
Discussion started by: z0rtiz
10 Replies

2. AIX

Networker : LUS Passthrough driver

Hi. AIX 7.1, Networker 7.6.3. My system detect all drives, but a jbconfig sent me this message : "You must install the LUS SCSI passthrough driver" I have Atape driver 12.3.9 on my AIX. Tks (0 Replies)
Discussion started by: stephnane
0 Replies

3. UNIX for Dummies Questions & Answers

Legato networker 7.6

Hi ALl I have recently installed networker 7.6 on my solaris 10 host(V240). My bosses requirement was that the GUI was still availible (nwadmin). However on 7.6 there is no GUI and nwadmin does not exist. I have copied nwadmin over from the previous version of legato i had installed (6.2), and... (5 Replies)
Discussion started by: brian112
5 Replies

4. UNIX and Linux Applications

Sun EBS Networker 7.3

I am having an issue with Sun EBS Networker 7.3, (64 bit) (Sun Hardware, Solaris 9) where it expects an Oracle DB (11.5.10 with 10g Database (10.2.0.2)) size of 4294967295 bytes. The DB's get backed up anyway, but it's only happening to certain DB's. The warning messages occur at random intervals... (4 Replies)
Discussion started by: djembeplayer
4 Replies

5. UNIX for Dummies Questions & Answers

networker

hi all, I have just installed networker 7.3 on my HPUX machine, licenced and ready to go, however, when I try to load/inventory/label a type using the autochanger I am getting the following error: Cannot find attribute 'operation instance' for resource 'NSR jukebox'. When I check to see what... (1 Reply)
Discussion started by: macgre_r
1 Replies

6. HP-UX

Legato networker on hp-ux

Hello, Firstable I am new on hp-ux (well long time ago) I am more aix admin.... Legato networker is the tool backup use on the hp-ux. I don't know this tool and would like to know where to find some docs or training. My first question will be : when a system (hp-ux B.11.0) is backuped on a... (8 Replies)
Discussion started by: touny
8 Replies

7. UNIX for Advanced & Expert Users

Legato Networker

Has anyone ever used Networker to backups a SunSolaris 5.4 system. I have all the my other OS on the network being backup except for the 5.4 systems. It's has to do with a daemon. So help me out this doesn't make any since> (3 Replies)
Discussion started by: aojmoj
3 Replies
Login or Register to Ask a Question
GROUPD(8)							      cluster								 GROUPD(8)

NAME
groupd - compatibility daemon for fenced, dlm_controld and gfs_controld SYNOPSIS
groupd [OPTIONS] DESCRIPTION
The groupd daemon and libgroup library are used by the fenced, dlm_controld and gfs_controld daemons when they are operating in clus- ter2-compatible mode to perform a rolling cluster upgrade from cluster2 to cluster3. See cman(5) for more information on the upgrading configuration option needed to perform a rolling upgrade. When the upgrading option is enabled, cman adds the following to the online configuration: <group groupd_compat="1"/> This setting causes the cman init script to start the groupd daemon, and causes the groupd, fenced, dlm_controld and gfs_controld daemons to operate in the old cluster2 mode so they will be compatible with cluster2 nodes in the cluster that have not yet been upgraded. The upgrading setting, including the groupd_compat setting, cannot be changed in a running cluster. The entire cluster must be taken off- line to change these because the new cluster3 default modes are not compatible with the old cluster2 modes. The upgrading/compat settings cause the new cluster3 daemons to run the old cluster2 code and protocols. OPTIONS
Command line options override a corresponding setting in cluster.conf. -D Enable debugging to stderr and don't fork. -L Enable debugging to log file. -g num groupd compatibility mode, 0 off, 1 on. Default 0. -h Print a help message describing available options, then exit. -V Print program version information, then exit. SEE ALSO
cman(5), fenced(8), dlm_controld(8), gfs_controld(8) cluster 2009-01-19 GROUPD(8)