HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Error create make_tape_recovery
Operating System - HP-UX
1827245
Members
2094
Online
109716
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-21-2005 07:21 AM
03-21-2005 07:21 AM
Error create make_tape_recovery
All
I am with the following errors below
Someone help-me
root@/:>/opt/ignite/bin/make_tape_recovery -A -a /dev/rmt/0mn
* Creating local directories for configuration files and archive.
======= 03/21/05 10:35:16 SAT Started /opt/ignite/bin/make_tape_recovery.
(Mon Mar 21 10:35:16 SAT 2005)
@(#) Ignite-UX Revision B.4.4.29
@(#) net_recovery (opt) $Revision: 10.611 $
* Testing pax for needed patch
* Passed pax tests.
* Checking Versions of Ignite-UX filesets
* Creating System Configuration.
* /opt/ignite/bin/save_config -f
/var/opt/ignite/recovery/2005-03-21,10:35/system_cfg vg00
NOTE: File: /var/opt/ignite/recovery/2005-03-21,10:35/system_cfg is not
world-readable, this may cause clients to fail to read it during an
installation.
* Backing Up Volume Group /dev/vg00
* /usr/sbin/vgcfgbackup /dev/vg00
Volume Group configuration for /dev/vg00 has been saved in /etc/lvmconf/vg00.conf
* Creating Map Files for Volume Group /dev/vg00
* /usr/sbin/vgexport -p -m /etc/lvmconf/vg00.mapfile /dev/vg00
vgexport: Volume group "/dev/vg00" is still active.
* Backing Up Volume Group /dev/vg01
* /usr/sbin/vgcfgbackup /dev/vg01
Volume Group configuration for /dev/vg01 has been saved in /etc/lvmconf/vg01.conf
* Creating Map Files for Volume Group /dev/vg01
* /usr/sbin/vgexport -p -m /etc/lvmconf/vg01.mapfile /dev/vg01
vgexport: Volume group "/dev/vg01" is still active.
* Backing Up Volume Group /dev/vg02
* /usr/sbin/vgcfgbackup /dev/vg02
Volume Group configuration for /dev/vg02 has been saved in /etc/lvmconf/vg02.conf
* Creating Map Files for Volume Group /dev/vg02
* /usr/sbin/vgexport -p -m /etc/lvmconf/vg02.mapfile /dev/vg02
vgexport: Volume group "/dev/vg02" is still active.
* Backing Up Volume Group /dev/vg03
* /usr/sbin/vgcfgbackup /dev/vg03
Volume Group configuration for /dev/vg03 has been saved in /etc/lvmconf/vg03.conf
* Creating Map Files for Volume Group /dev/vg03
* /usr/sbin/vgexport -p -m /etc/lvmconf/vg03.mapfile /dev/vg03
vgexport: Volume group "/dev/vg03" is still active.
* Backing Up Volume Group /dev/vg04
* /usr/sbin/vgcfgbackup /dev/vg04
Volume Group configuration for /dev/vg04 has been saved in /etc/lvmconf/vg04.conf
* Creating Map Files for Volume Group /dev/vg04
* /usr/sbin/vgexport -p -m /etc/lvmconf/vg04.mapfile /dev/vg04
vgexport: Volume group "/dev/vg04" is still active.
* Creating Control Configuration.
NOTE: File: /var/opt/ignite/recovery/2005-03-21,10:35/control_cfg is not
world-readable, this may cause clients to fail to read it during an
installation.
* Creating Archive File List
* Creating Archive Configuration
* /opt/ignite/bin/make_arch_config -c
/var/opt/ignite/recovery/2005-03-21,10:35/archive_cfg -g
/var/opt/ignite/recovery/2005-03-21,10:35/flist -n 2005-03-21,10:35 -r
64 -d Recovery\ Archive -t -i 1 -m t
NOTE: File: /var/opt/ignite/recovery/2005-03-21,10:35/archive_cfg is not
world-readable, this may cause clients to fail to read it during an
installation.
* Saving the information about archive to
/var/opt/ignite/recovery/previews
* Creating The Tape Archive
NOTE: File: /var/opt/ignite/recovery/2005-03-21,10:35/system_cfg is not
world-readable, this may cause clients to fail to read it during an
installation.
NOTE: File: /var/opt/ignite/recovery/2005-03-21,10:35/control_cfg is not
world-readable, this may cause clients to fail to read it during an
installation.
NOTE: File: /var/opt/ignite/recovery/2005-03-21,10:35/archive_cfg is not
world-readable, this may cause clients to fail to read it during an
installation.
msgcnt 12 vxfs: mesg 001: vx_nospace - /dev/root file system full (1 block extent)
lifcp: file truncated, no space on the LIF volume
make_medialif: error - lifcp SYSCMDS failed, probable insufficient size for /var/tmp/uxinstlf.recovery
ERROR: System Error, /opt/ignite/bin/make_medialif failed creating boot LIF
file.
ERROR: Failed to generate LIF on tape .
---------------------------------------------
bdf /
root@/:>bdf /
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 524288 450643 73645 86% /
I am with the following errors below
Someone help-me
root@/:>/opt/ignite/bin/make_tape_recovery -A -a /dev/rmt/0mn
* Creating local directories for configuration files and archive.
======= 03/21/05 10:35:16 SAT Started /opt/ignite/bin/make_tape_recovery.
(Mon Mar 21 10:35:16 SAT 2005)
@(#) Ignite-UX Revision B.4.4.29
@(#) net_recovery (opt) $Revision: 10.611 $
* Testing pax for needed patch
* Passed pax tests.
* Checking Versions of Ignite-UX filesets
* Creating System Configuration.
* /opt/ignite/bin/save_config -f
/var/opt/ignite/recovery/2005-03-21,10:35/system_cfg vg00
NOTE: File: /var/opt/ignite/recovery/2005-03-21,10:35/system_cfg is not
world-readable, this may cause clients to fail to read it during an
installation.
* Backing Up Volume Group /dev/vg00
* /usr/sbin/vgcfgbackup /dev/vg00
Volume Group configuration for /dev/vg00 has been saved in /etc/lvmconf/vg00.conf
* Creating Map Files for Volume Group /dev/vg00
* /usr/sbin/vgexport -p -m /etc/lvmconf/vg00.mapfile /dev/vg00
vgexport: Volume group "/dev/vg00" is still active.
* Backing Up Volume Group /dev/vg01
* /usr/sbin/vgcfgbackup /dev/vg01
Volume Group configuration for /dev/vg01 has been saved in /etc/lvmconf/vg01.conf
* Creating Map Files for Volume Group /dev/vg01
* /usr/sbin/vgexport -p -m /etc/lvmconf/vg01.mapfile /dev/vg01
vgexport: Volume group "/dev/vg01" is still active.
* Backing Up Volume Group /dev/vg02
* /usr/sbin/vgcfgbackup /dev/vg02
Volume Group configuration for /dev/vg02 has been saved in /etc/lvmconf/vg02.conf
* Creating Map Files for Volume Group /dev/vg02
* /usr/sbin/vgexport -p -m /etc/lvmconf/vg02.mapfile /dev/vg02
vgexport: Volume group "/dev/vg02" is still active.
* Backing Up Volume Group /dev/vg03
* /usr/sbin/vgcfgbackup /dev/vg03
Volume Group configuration for /dev/vg03 has been saved in /etc/lvmconf/vg03.conf
* Creating Map Files for Volume Group /dev/vg03
* /usr/sbin/vgexport -p -m /etc/lvmconf/vg03.mapfile /dev/vg03
vgexport: Volume group "/dev/vg03" is still active.
* Backing Up Volume Group /dev/vg04
* /usr/sbin/vgcfgbackup /dev/vg04
Volume Group configuration for /dev/vg04 has been saved in /etc/lvmconf/vg04.conf
* Creating Map Files for Volume Group /dev/vg04
* /usr/sbin/vgexport -p -m /etc/lvmconf/vg04.mapfile /dev/vg04
vgexport: Volume group "/dev/vg04" is still active.
* Creating Control Configuration.
NOTE: File: /var/opt/ignite/recovery/2005-03-21,10:35/control_cfg is not
world-readable, this may cause clients to fail to read it during an
installation.
* Creating Archive File List
* Creating Archive Configuration
* /opt/ignite/bin/make_arch_config -c
/var/opt/ignite/recovery/2005-03-21,10:35/archive_cfg -g
/var/opt/ignite/recovery/2005-03-21,10:35/flist -n 2005-03-21,10:35 -r
64 -d Recovery\ Archive -t -i 1 -m t
NOTE: File: /var/opt/ignite/recovery/2005-03-21,10:35/archive_cfg is not
world-readable, this may cause clients to fail to read it during an
installation.
* Saving the information about archive to
/var/opt/ignite/recovery/previews
* Creating The Tape Archive
NOTE: File: /var/opt/ignite/recovery/2005-03-21,10:35/system_cfg is not
world-readable, this may cause clients to fail to read it during an
installation.
NOTE: File: /var/opt/ignite/recovery/2005-03-21,10:35/control_cfg is not
world-readable, this may cause clients to fail to read it during an
installation.
NOTE: File: /var/opt/ignite/recovery/2005-03-21,10:35/archive_cfg is not
world-readable, this may cause clients to fail to read it during an
installation.
msgcnt 12 vxfs: mesg 001: vx_nospace - /dev/root file system full (1 block extent)
lifcp: file truncated, no space on the LIF volume
make_medialif: error - lifcp SYSCMDS failed, probable insufficient size for /var/tmp/uxinstlf.recovery
ERROR: System Error, /opt/ignite/bin/make_medialif failed creating boot LIF
file.
ERROR: Failed to generate LIF on tape .
---------------------------------------------
bdf /
root@/:>bdf /
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 524288 450643 73645 86% /
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-21-2005 09:07 AM
03-21-2005 09:07 AM
Re: Error create make_tape_recovery
Your make_tape_recovery command trying to backing up all the volume groups from your server and this is filling up your root file system. Instead run make_tape only for vg00 by adding -x inc_entire = vg00
Although you can include other VG in make_tape_recovery but it is advisable to include only VG00 and rest VG's you can backup by other regular methods.
The command should be like this.
/opt/ignite/bin/make_tape_recovery -a {Tape Device} -I -m tar -v -x inc_entire=vg00
-USA..
Although you can include other VG in make_tape_recovery but it is advisable to include only VG00 and rest VG's you can backup by other regular methods.
The command should be like this.
/opt/ignite/bin/make_tape_recovery -a {Tape Device} -I -m tar -v -x inc_entire=vg00
-USA..
Good Luck..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-21-2005 05:02 PM
03-21-2005 05:02 PM
Re: Error create make_tape_recovery
Hi,
As evident in the post, you don't have sufficient space to proceed with the make_tape_recovery. I would recommend to include this option (-x inc_entire=vg00) when executing make_tape_recovery.
Regards,
Isralyn
As evident in the post, you don't have sufficient space to proceed with the make_tape_recovery. I would recommend to include this option (-x inc_entire=vg00) when executing make_tape_recovery.
Regards,
Isralyn
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-21-2005 08:59 PM
03-21-2005 08:59 PM
Re: Error create make_tape_recovery
Daniel,
Do you have the latest Ignite and pax patch installed.
Can you also check if patch PHSS_27406(hp-ux 11.11)/PHSS_27407 (hp-ux 11.00)
is installed on your server.
PHSS_27406:
JAGae31512:
The make_tape_recovery, make_recovery, and make_medialif commands may fail with the messages "no space on the LIF volume" and "lifcp SYSCMDS failed, probable insufficient size for /var/tmp/uxinstlf.recovery".
Good Luck
Darrel
Do you have the latest Ignite and pax patch installed.
Can you also check if patch PHSS_27406(hp-ux 11.11)/PHSS_27407 (hp-ux 11.00)
is installed on your server.
PHSS_27406:
JAGae31512:
The make_tape_recovery, make_recovery, and make_medialif commands may fail with the messages "no space on the LIF volume" and "lifcp SYSCMDS failed, probable insufficient size for /var/tmp/uxinstlf.recovery".
Good Luck
Darrel
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP