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
pki-upgrade(8)							 PKI Upgrade Tool						    pki-upgrade(8)

NAME
pki-upgrade - Tool for upgrading system-wide configuration for Certificate System. SYNOPSIS
pki-upgrade [OPTIONS] DESCRIPTION
There are two parts to upgrading Certificate System: upgrading the system configuration files used by both the client and the server pro- cesses and upgrading the server configuration files. When upgrading Certificate System, the existing system configuration files (e.g. /etc/pki/pki.conf) may need to be upgraded because the content may have changed from one version to another. The configuration upgrade is executed automatically during RPM upgrade. However, in case there is a problem, the process can also be run manually using pki-upgrade. The system upgrade process is done incrementally using upgrade scriptlets. The upgrade process and scriptlet execution is monitored in upgrade trackers. A counter shows the latest index number for the most recently executed scriptlet; when all scriptlets have run, the com- ponent tracker shows the updated version number. The scriptlets are stored in the upgrade directory: /usr/share/pki/upgrade/<version>/<index>-<name> The version is the system version to be upgraded. The index is the script execution order. The name is the scriptlet name. During upgrade, the scriptlets will back up all changes to the filesystem into the following folder: /var/log/pki/upgrade/<version>/<index> The version and index values indicate the scriptlet being executed. A copy of the files and folders that are being modified or removed will be stored in oldfiles. The names of the newly-added files and folders will be stored in newfiles. The system upgrade process is tracked using this file: /etc/pki/pki.version The file stores the current configuration version and the last successful scriptlet index. OPTIONS
General options --silent Upgrade in silent mode. --status Show upgrade status only without performing the upgrade. --revert Revert the last version. -X Show advanced options. -v, --verbose Run in verbose mode. -h, --help Show this help message. Advanced options The advanced options circumvent the normal component tracking process by changing the scriptlet order or changing the tracker information. WARNING: These options may render the system unusable. --scriptlet-version <version> Run scriptlets for a specific version only. --scriptlet-index <index> Run a specific scriptlet only. --remove-tracker Remove the tracker. --reset-tracker Reset the tracker to match the package version. --set-tracker <version> Set the tracker to a specific version. OPERATIONS
Interactive mode By default, pki-upgrade will run interactively. It will ask for a confirmation before executing each scriptlet. % pki-upgrade If there is an error, it will stop and show the error. Silent mode The upgrade process can also be done silently without user interaction: % pki-upgrade --silent If there is an error, it will stop and show the error. Checking upgrade status It is possible to check the status of a running upgrade process. % pki-upgrade --status Troubleshooting If there is an error, rerun the upgrade in verbose mode: % pki-upgrade --verbose Check the scriptlet to see which operations are being executed. Once the error is identified and corrected, the upgrade can be resumed by re-running pki-upgrade. It is possible to rerun a failed script by itself, specifying the instance and subsystem, version, and scriptlet index: % pki-upgrade --scriptlet-version 10.0.1 --scriptlet-index 1 Reverting an upgrade If necessary, the upgrade can be reverted: % pki-upgrade --revert Files and folders that were created by the scriptlet will be removed. Files and folders that were modified or removed by the scriptlet will be restored. FILES
/usr/sbin/pki-upgrade AUTHORS
Ade Lee <alee@redhat.com>, Ella Deon Lackey <dlackey@redhat.com>, and Endi Dewata <edewata@redhat.com>. pki-upgrade was written by the Dogtag project. COPYRIGHT
Copyright (c) 2013 Red Hat, Inc. This is licensed under the GNU General Public License, version 2 (GPLv2). A copy of this license is avail- able at http://www.gnu.org/licenses/old-licenses/gpl-2.0.txt. version 1.0 Jul 22, 2013 pki-upgrade(8)