Sponsored Content
Full Discussion: IGNITE / Make recovery
Operating Systems HP-UX IGNITE / Make recovery Post 302157812 by mr_manny on Saturday 12th of January 2008 05:22:40 PM
Old 01-12-2008
we still use make_tape_recovery on half of our servers...the other half create an ignite image on an ignite server via make_net_recovery.

If upgrading your ignite is not an option, it might be better to simply replace your dds drive.

Drives are pretty affordable these days, with usually a zero impact to server during installation.

good luck,
manny
 

9 More Discussions You Might Find Interesting

1. HP-UX

Creating A Make Recovery Tape

A customer called me and stated that when they created a make recovery tape for their hp-ux 9000/770, it wiped out three of their volume groups from the lvmtab, fstab, /dev directory(all associated files). I didn't believe them until I conducted a tech assist. I restored their system by recreating... (3 Replies)
Discussion started by: spawarrior
3 Replies

2. Shell Programming and Scripting

make recovery tape for solaris

Hello All I am need of amke recover tape for solaris.Could anybody tell me how do i create a make recovery tape for solaris.I am on sun-solaris 2.8 regards Hrishy (2 Replies)
Discussion started by: xiamin
2 Replies

3. UNIX for Advanced & Expert Users

without an ignite server ??

system: HP-UX 10.20 with HFS mounted. How can I convert the HFS to VxFS without an ignite server ? Is this possible ? thanks simon2000 (4 Replies)
Discussion started by: simon2000
4 Replies

4. AIX

make a recovery CD/DVD - system has no writable devices

Hi, Has anyone please got some advise as to how I can make a CD/DVD on an AIX 5.3 system so that it can be fully recoverd just by inserting the backed up system. The system that I need to recover has no writable devices, not even a tape drive (it wasn't specified by me btw). I am trying to... (0 Replies)
Discussion started by: stevek007
0 Replies

5. HP-UX

Need Ignite for HP-UX 10.20

Hello All, I need to bring down our old 9000 series d350, but my supervisor wants an ignite backup created. I cannot find ignite in the usual places (/opt/ignite) nor can I find it in swlist. As far as I can tell the cd's are long gone. Is there anywhere else I could look for ignite being... (6 Replies)
Discussion started by: stay0ut
6 Replies

6. HP-UX

Ignite and HP-UX 09.XX

I am looking to make bootable tape backups of four machines running HP-UX 09.02, 09.05 and 09.07. I successfully located Ignite 10.20 and installed it and made a backup on the one machine running HP-UX 10.20. I am having trouble locating information about Ignite for HP-UX 9. Does it exist? Is... (3 Replies)
Discussion started by: whack_job
3 Replies

7. HP-UX

Ignite - make_net_recovery

I've read the Ignite User/Admin Guide but I'm having trouble figuring out if I can do a make_net_recovery if the ignite server and client server are on completely different networks? If this can be done is there any special configuration? If I initiate the command from the server it looks like it... (3 Replies)
Discussion started by: gonzotonka
3 Replies

8. HP-UX

Ignite

Hi Does anybody know how to get hold of a very old (A.3.7.n) copy of the ignite software depot for HP-UX 10.20? (7 Replies)
Discussion started by: gregsih
7 Replies

9. HP-UX

Ignite recovery issue.

On one of the Hpvm server when I try to do the ignite recovery it aborts after recovering only 30 % of the archive. I do not have any other archive backup besides this. Even after restoring the 30 archive I could see that I am able to login to that server althoug ssh and other functionalities... (9 Replies)
Discussion started by: kpatel786
9 Replies
iofind(1M)																iofind(1M)

NAME
iofind - find and convert ASCII files containing the legacy representation of device (special file name or hardware path) SYNOPSIS
file] directory] filelist] file] directory] filelist] DESCRIPTION
The command helps users with the migration to the agile naming model (see intro(7)). First, identifies ASCII files on the system that con- tain patterns representing legacy mass storage device special file names or hardware paths. Then replaces the matching patterns with their mapping in the agile naming model inside the ASCII files. NOTE: may take several minutes to execute depending on the number of files to be searched (see the options). If there are many files, the search will take a long time. An alternative is to redirect the output to a file and run in background mode (for example, The increasing size of this output file indicates that is making progress. While executing, the command creates the following files in the and directories. Files under the directory: o contains the list of valid legacy device special file patterns to search for. o contains the list of valid legacy hardware path patterns to search for. o contains a colon separated list of all legacy device special files mapped to their corresponding persistent device special files. The first field is the persistent device special file name and the second field is the legacy name. o contains a colon separated list of all legacy hardware paths mapped to their corresponding lun and lunpath hardware paths in the agile naming model. The first and second fields are the lun and lunpath hardware paths, respectively, in the agile naming model. The third field is the legacy path. o contains a list of files which match at least one of the device special file search patterns in o contains a list of files which match at least one of the hardware path search patterns in o contains the list of files to be searched. o contains the command output summary, which is also displayed on the console during execution. File under the directory: o contains a list of directories to be excluded from the search. The purpose of this file is to speed up the search by not searching directories indicated in this file. Running the iofind command will create this file if it does not already exist. If a user provides the option, this file is not used to exclude directories. A user can edit this file to add or delete any directories from the search. Delete all the entries in the file if you do not want iofind to skip any directories. By default, the following directories are repre- sented in this file: /var/adm/msgbuf/ /var/adm/iofind/ /var/adm/syslog/ /var/adm/crash/ /var/adm/userdb/ /var/opt/ignite/ /usr/share/lib/ /usr/share/man/ /var/spool/ /etc/opt/resmon/ /opt/ignite/boot/ /opt/hpsmh/ /opt/openssl/ /opt/ssh/ /opt/wbem/ /opt/atok/ /opt/X11/ /opt/java/ /opt/gnome /opt/java /opt/mozilla /opt/wrkio /opt/msscaf/ /opt/aCC/ /opt/sfmdb/ /usr/lib/ /usr/bin/ /usr/dt/ /usr/include/ /var/evm/ /var/stm/ /stand/ /tmp/ Files under the directory: o These are backup copies of the original files, if any, before they get modified by the -R option. They are stored including their parent directory. For instance, the file /usr/mydata will be saved under Files under the directory: o When option is used along with the original files are not actually modified, but a preview of the modified files, including their parent directory, is made available under this preview directory. If a user does not use the option to specify a file or files to search, the iofind command will search through directories, except those indicated in the file, and it will skip files with the following file extensions: .ttf .gif .jpg .jar .html .img .xml .mof .so.1 .so .sdl .png .css .tar .gz .zip .1m .pl The option can be used to specify a list of patterns to be searched in ASCII files on the system. The patterns to be searched must be entered in the input file, file, one per line. This input file must contain legacy device special files, legacy hardware paths, or a mix of both. Device special file names must be fully qualified. For example, the full path must be used instead of If is invoked with the option, and no input file is specified using the option, builds a list of legacy device special file patterns from the data returned by the command. If is invoked with the option, and no input file is specified using the option, builds a list of legacy hardware path patterns by calling the command. The and options can be used together to search both types of patterns. If is invoked with the option, it replaces the matching patterns with their mapping in all ASCII files identified, unless the (preview) option is specified. Before modifying the files, saves a copy of the original ASCII files in the directory. also asks for confirmation before each change, unless the (force) option is used. Options recognizes the following options: Specify the directory which contains the files to be searched. If the option is not specified, then the current directory is used. All directories under the specified directory are searched recursively. Turn off interactive mode (also known as the force option). This option must be used with the option. The user is not prompted to confirm the replacement of a pattern before the pattern is replaced. Specify a list of patterns in the input file to search for. The format of the input file is one device special file or hardware path, per line. When an input file is provided using the option, the user must also specify the or option. Search ASCII files on the system for legacy hardware path patterns. See "NOTE" in about displaying output to a file. If the option is not specified, first calls to generate a list of hardware path patterns to be searched for. Otherwise, if the option is specified, searches the ASCII files for the hardware path patterns defined in the file. Patterns are saved in the file. Either the or option must be specified. Also, both options can be specified together. Print the command usage. When is invoked with no command line options, or with the option, it prints a usage message. Provide a list of files under the specified directory, for which to search for legacy device special files and hardware paths. The user may list as many files as needed on the com- mand line when using the option. Each file must be separated by a comma. Search ASCII files on the system for legacy device special file patterns. See "NOTE" in about displaying output to a file. If the option is not specified, first calls to generate a list of device special file patterns to be searched for. Otherwise, if the option is specified, searches the ASCII files for the devices special file patterns defined in the file. Patterns are saved in the file. Either the or option must be specified. Also, both options can be specified together. Preview, but do not replace, the selected patterns. This option is only supported in combination with the option. When both the and options are specified, does not do the actual replacement of matching patterns (see the option), but the replacement information will be created under this directory: Replace matching patterns with their mapping in the agile naming model. If the option is used with the option, a preview of changes will be provided in the directory. If the option is used without the option, asks the user for a confirmation before executing each replacement in the file. If used with the option, the replacement is executed without asking the user for confirmation. You must be superuser to execute the option. You do not have to be superuser to execute the other options. All files modified by this command are first backed up in the directory. RETURN VALUE
Exit values are: Successful completion. An error condition occurred. EXAMPLES
Generate a list of searchable hardware paths on the system. Generate a list of searchable hardware paths on the system. Redirect the output to a file and run as a background task. Find all patterns matching the legacy hardware paths, 0/1/1/0.0.0 and 1/2/0/0.3.0, in the file. This file contains the strings, 0/1/1/0.0.0 and 1/2/0/0.3.0, one string per line. Search all files under the current directory for matching hardware path patterns found in and preview the replacement of any matching pat- terns without doing the actual replacement in the files. Search all files under the current directory for matching device special file patterns found in and replace all matching patterns with their mapping in the agile naming model. The format of the input file is one full path device special file, such as /dev/dsk/c1t3d0, per line. Do not prompt the user for confirmation before each replacement. Scan through all files under and its subdirectories to find all patterns matching the legacy hardware paths, 0/1/1/0.0.0 and 1/2/0/0.3.0, in the file. This file contains the strings, 0/1/1/0.0.0 and 1/2/0/0.3.0, one string per line. WARNINGS
The replace functionality needs appropriate permissions to make changes to the files to be modified. SEE ALSO
ioscan(1M), intro(7). iofind(1M)
All times are GMT -4. The time now is 05:54 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy