- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Ignite insists on backing up additional volume gro...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
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
Community
Resources
Forums
Blogs
- 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
08-02-2011 12:30 PM
08-02-2011 12:30 PM
Hi,
I have a server that ignite insists needs both vg00 and an additonal volume group backed up during make_net_recovery. The other volume group formerly had a swap file on it, but I've removed it from /etc/fstab and deleted the logical volume. swapinfo and lvlnboot have no pointers to the other volume group.
Here's the command we are using
# make_net_recovery -A -s <server> -n 2 -x inc_entire=vg00
swapinfo:
# swapinfo -tsm
Primary swap (for next boot) :
Primary swap for next boot was not set using swapctl()
Mb Mb Mb PCT START/ Mb
TYPE AVAIL USED FREE USED LIMIT RESERVE PRI NAME
dev 4096 0 4095 0% 0 - 1 /dev/vg00/lvol2
dev 9952 1722 8228 17% 0 - 0 /dev/vg00/lvswap
reserve - 9269 -9269
memory 6812 2922 3890 43%
total 20860 13913 6944 67% - 0 -
And for good luck lvlnboot:
# lvlnboot -v
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c0t0d0s2 -- Boot Disk
Boot: lvol1 on: /dev/dsk/c0t0d0s2
Root: lvol3 on: /dev/dsk/c0t0d0s2
Swap: lvol2 on: /dev/dsk/c0t0d0s2
Dump: lvol2 on: /dev/dsk/c0t0d0s2, 0
I need to replace the system disk and the easiest way for me to do it is the ignite backup/recovery (I've done it multiple times on other servers). I'm leery of doing it when the ignite recovery wants to blow away my data disk as well. Not to mention all the space being taken up on the ignite server...
Does anyone have any idea why it still wants to back up the additional volume group and how I can make it stop?
Thanks,
David Knickmeyer
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-02-2011 12:49 PM
08-02-2011 12:49 PM
Re: Ignite insists on backing up additional volume group.
What does that other VG contain? There are some things that Ignite will automatically include because they are needed for the system.
What is the name of the other VG?
Can you please post a 'bdf' so we can see what mountpoints that VG has?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-02-2011 01:12 PM
08-02-2011 01:12 PM
Re: Ignite insists on backing up additional volume group.
To add to this -- The file /opt/ignite/recover/mnr_essentials contains a list of items that will ALWAYS be included in a make_tape_recovery or make_net_recovery backup. If any of these are NOT in VG00, then I am almost certain that the VG that does contain them will be included automatically.
So if your non-VG00 volume group contains anything listed in the mnr_essentials file, that that is the reason it is being included automatically.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-02-2011 04:48 PM
08-02-2011 04:48 PM
Re: Ignite insists on backing up additional volume group.
post the recovery log of the make_net_recovery command. on the ignite server to be found in /var/opt/ignite/archives/clients/<>/recovery.log (something like this). I think it will give a list of all lvols that it has backed up .
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-03-2011 11:54 AM
08-03-2011 11:54 AM
Re: Ignite insists on backing up additional volume group.
The 'other' volume group is vgsap. Here's the bdf if you want to slog through it:
(root@saptrn)# bdf
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 581632 334248 245504 58% /
/dev/vg00/lvol1 311296 191496 118968 62% /stand
/dev/vg00/lvol8 4710400 3822176 882528 81% /var
/dev/vg00/lvol7 6348800 3120656 3203016 49% /usr
/dev/vgborrowed/lvusrsapput
14680064 7384355 6839738 52% /usr/sap/put
/dev/vgsap/lvusrsaptrn
2097152 164103 1812286 8% /usr/sap/TRN
/dev/vg00/lvol4 1049600 205768 838088 20% /tmp
/dev/vgsap/lvmnttrn
4194304 2019131 2039977 50% /sapmnt/TRN
/dev/vg00/lvsapdatatrns
524288 17555 475066 4% /sapdatatrns
/dev/vgsap/lvoracle
524288 357748 156347 70% /oracle
/dev/vgsap/lvstage 7176192 1877043 4974639 27% /oracle/stage
/dev/vgsap/lvdbhome
2097152 79577 1894503 4% /oracle/TRN
/dev/vgsap/lvsapreorg
4194304 18203 3915165 0% /oracle/TRN/sapreorg
/dev/vgsap/lvsapdata9
10485760 9614368 864656 92% /oracle/TRN/sapdata9
/dev/vgsap/lvsapdata8
6291456 5669344 617320 90% /oracle/TRN/sapdata8
/dev/vgsap/lvsapdata7
5242880 5084616 157096 97% /oracle/TRN/sapdata7
/dev/vgsap/lvsapdata6
4194304 4117312 76464 98% /oracle/TRN/sapdata6
/dev/vgsap/lvsapdata5
4194304 4175656 18568 100% /oracle/TRN/sapdata5
/dev/vgsap/lvsapdata4
4194304 3909336 282816 93% /oracle/TRN/sapdata4
/dev/vgsap/lvsapdata3
4194304 3323728 863848 79% /oracle/TRN/sapdata3
/dev/vgsap/lvsapdata2
4194304 4050832 142424 97% /oracle/TRN/sapdata2
/dev/vg00/lvsapdata12
10485760 5403656 5042408 52% /oracle/TRN/sapdata12
/dev/vgborrowed2/lvsapdata11
51191808 51001608 188720 100% /oracle/TRN/sapdata11
/dev/vgborrowed/lvsapdata10
11526144 11417656 107648 99% /oracle/TRN/sapdata10
/dev/vgsap/lvsapdata1
4194304 4034816 158312 96% /oracle/TRN/sapdata1
/dev/vgsap/lvsaparch
8388608 693537 7214256 9% /oracle/TRN/saparch
/dev/vgsap/lvoriglogb
327680 206675 113512 65% /oracle/TRN/origlogB
/dev/vgsap/lvorigloga
327680 226555 94874 70% /oracle/TRN/origlogA
/dev/vgsap/lvmirrlogb
327680 206675 113512 65% /oracle/TRN/mirrlogB
/dev/vgsap/lvmirrloga
327680 206675 113512 65% /oracle/TRN/mirrlogA
/dev/vgsap/lv102_64
13828096 3818720 9383986 29% /oracle/TRN/102_64
/dev/vg00/lvol6 6504448 5434816 1062712 84% /opt
/dev/vg00/lvol5 24576 9424 15088 38% /home
/dev/vg00/lvhold 2097152 17595 1949592 1% /hold
sapdev.ssmhc.com:/usr/sap/trans
33554432 26552104 6575288 80% /usr/sap/trans
sapbpr.ssmhc.com:/orasource
31457280 15280768 15166688 50% /orasource
sapbpr.ssmhc.com:/sapsource
41943040 36591808 5021512 88% /sapsource
No swapfiles or anything like that.
The mnt_essentials does not have any filesystems that are on vgsap.
I didn't see anything in the recovery log about logical volumes being backed up. I tried to attach it, but the forum won't let me for some reason. The 'Post' button just keeps me in edit mode.
Thanks again for any help.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-04-2011 01:45 AM
08-04-2011 01:45 AM
Re: Ignite insists on backing up additional volume group.
> I tried to attach it, but the forum won't let me for some reason. The 'Post' button just keeps me in edit mode.
It wants a .suffix, .txt should work.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-04-2011 06:57 AM
08-04-2011 06:57 AM
Re: Ignite insists on backing up additional volume group.
Okay, the recovery.log file as recovery.txt
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-04-2011 07:07 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-04-2011 11:52 AM
08-04-2011 11:52 AM
Re: Ignite insists on backing up additional volume group.
Well, that seems to work!
Kinda strange since I use the exact same script on all of our SAP servers (and mean exact; it's on an NFS share).
Oh, well. Thanks and on to the next steps...
Dave
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-05-2011 06:10 AM
08-05-2011 06:10 AM
Re: Ignite insists on backing up additional volume group.
Ignite, I believe, builds a list of the files it intends to back up. Perhaps an examination of that list would reveal why it thought it had to include those disks/vg's.
"man make_net_recovery
.
.
.
-A Based on the files that are specified for inclusion, this option determines which disk(s) and/or volume groups(s) contain those specified files . . . . . .
.
.
.
"
Pete