- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: make_tape_recovery and fbackup questions
Operating System - HP-UX
1748117
Members
3670
Online
108758
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
Discussions
Discussions
Forums
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
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
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-19-2010 12:18 PM
тАО03-19-2010 12:18 PM
All,
In a system with only one vg(I know, it's not best practice), is there any difference between
make_tape_recovery -A and
make_tape_recovery -x inc_entire=vg00
and with fbackup, is there any reason to specify individual filesystems as opposed to specifying just the root filesystem? Some past threads indicated some folks made a graph file with all the mount points, I'm wondering if there was a reason to do it that way?
For example if I want to back up everything mounted under /, is there any advantage to using
fbackup -i /etc -i /opt -i /var, and so forth as opposed to -i /?
Doesn't -i / automatically include everything mounted under /? If I want everything under / is there any reason to specify the mounts individually? Thanks,
Brian
In a system with only one vg(I know, it's not best practice), is there any difference between
make_tape_recovery -A and
make_tape_recovery -x inc_entire=vg00
and with fbackup, is there any reason to specify individual filesystems as opposed to specifying just the root filesystem? Some past threads indicated some folks made a graph file with all the mount points, I'm wondering if there was a reason to do it that way?
For example if I want to back up everything mounted under /, is there any advantage to using
fbackup -i /etc -i /opt -i /var, and so forth as opposed to -i /?
Doesn't -i / automatically include everything mounted under /? If I want everything under / is there any reason to specify the mounts individually? Thanks,
Brian
Brian Bartley
Campus Card Services
Indiana University
Campus Card Services
Indiana University
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-19-2010 12:36 PM
тАО03-19-2010 12:36 PM
Solution
Hi Brian:
The make_tape_recovery option '-A' determines which disk(s) and/or volume group(s) contain essential files and then copies those files. Given that vg00 holds only operating system filesystems and no application logical volumes, I prefer to use '-x inc_entire=vg00'.
As for 'fbackup', I'd use a graph file to specify what you want to supplement your Ignite tape recovery. That is, if you do an Ignite periodically and at least whenever key configuration changes are made and/or whenever patches are applied; then you can use 'fbackup' to collect very volatile configuration files like '/etc/passwd' or '/etc/shadow', etc.
I wouldn't bother to do a 'fbackup' of filesystems that are otherwise covered by your Ignite recovery tape. After all, if you have to rebuild or clone your server, the Ignite tape is what's going to be needed.
Regards!
...JRF...
The make_tape_recovery option '-A' determines which disk(s) and/or volume group(s) contain essential files and then copies those files. Given that vg00 holds only operating system filesystems and no application logical volumes, I prefer to use '-x inc_entire=vg00'.
As for 'fbackup', I'd use a graph file to specify what you want to supplement your Ignite tape recovery. That is, if you do an Ignite periodically and at least whenever key configuration changes are made and/or whenever patches are applied; then you can use 'fbackup' to collect very volatile configuration files like '/etc/passwd' or '/etc/shadow', etc.
I wouldn't bother to do a 'fbackup' of filesystems that are otherwise covered by your Ignite recovery tape. After all, if you have to rebuild or clone your server, the Ignite tape is what's going to be needed.
Regards!
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-22-2010 06:02 AM
тАО03-22-2010 06:02 AM
Re: make_tape_recovery and fbackup questions
Thanks for all replies, I'm going to start using -x inc_entire=vg00 instead of -A.
Brian
Brian
Brian Bartley
Campus Card Services
Indiana University
Campus Card Services
Indiana University
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP