- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: tape label identification
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
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
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
тАО12-18-2005 04:17 PM
тАО12-18-2005 04:17 PM
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-18-2005 04:47 PM
тАО12-18-2005 04:47 PM
SolutionIt can be indentified with the help of OmniBack Database information and going through the backup specification configuration.
Tape label's are Bard codes and can be decoded and understood by Robotic Arm easily. It is very difficult for us to identify the tapes with Barcode Information.
Regards,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-18-2005 04:49 PM
тАО12-18-2005 04:49 PM
Re: tape label identification
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-18-2005 05:04 PM
тАО12-18-2005 05:04 PM
Re: tape label identification
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-18-2005 05:11 PM
тАО12-18-2005 05:11 PM
Re: tape label identification
man frecover for details.
ufsdump is specific to sun as I understand, so I do not know much about it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-19-2005 12:33 AM
тАО12-19-2005 12:33 AM
Re: tape label identification
Managing a tape libtrary does require some detailed thought, especially with the backup scripts. If operators choose the tapes at random, you *will* lose data. Backup scripts should be driven by a defined set of steps to pick a tape, run the backup and then put the tape back in the correct location. Part of the inventory script should be a verificattion that the expected tape is in the correct slot. Backup (and inventory and audit) scripts should never leave a tape in a drive, whether the backup was successful or not. This is to minimize mistakes caused by writing to the wrong drive.
Bill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-19-2005 02:23 AM
тАО12-19-2005 02:23 AM
Re: tape label identification
FBACKUP/FRECOVER
Things to remember about fbackup:
* fbackup MUST rewind the tape before beginning the backup and after
completing.
* a tape created with fbackup is only recoverable with frecover.
* a file listed in the index file (from option -rvNf) is not guaranteed
to be on the tape; this simply means that fbackup intended to back the
file up when it began the backup session.
Command Description
fbackup -vf /dev/rmt/0m -i / full system backup
fbackup -vf /dev/rmt/0m -i specifically include file/directory
/etc/hosts preceded by -i
fbackup -vf /dev/rmt/0m -i specifically include multiple
/etc/hosts -i /usr files/directories preceded by -i
fbackup -vf /dev/rmt/0m -e specifically exclude file/directory
/etc/hosts preceded by -e
fbackup -vf /dev/rmt/0m -g
graph_file_name backup from a graph file
frecover -xvf /dev/rmt/0m restore entire tape to originating
directory structure
restore entire tape to originating
frecover -xovf /dev/rmt/0m directory structure and overwrite any
existing files
cd /tmp restore entire tape to /tmp
frecover -xXvf /dev/rmt/0m (originating directory structure will
not be overwritten)
frecover -vf /dev/rmt/0m -I verify backup and read the index file
/tmp/index from the tape into a file called
/tmp/index
fbackup -vf /dev/rmt/0m 2>&1 log what is backed up, along with any
|tee /tmp/backup.log errors that occur
frecover -rNv -f /dev/rmt/0m 2>
/tmp/listing list of what is really on the tape
frecover -V /tmp/volume_headers
-f /dev/rmt/0m show volume headers on the tape
Good Luck,