10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi Everyone,
we are running rsync with --backup mode, Are there any rsync options to remove backup folders on successful deployment?
Thanks in adv. (0 Replies)
Discussion started by: MVEERA
0 Replies
2. UNIX for Dummies Questions & Answers
Hi guys,
I'm new to Linux and dont know much about scripts..there's an backup script that will backup the database from a location to another location between servers..it will run automatically by adding it to crontab...it was created by another person and I tried to understand it somewhat..
... (1 Reply)
Discussion started by: koolhart
1 Replies
3. Shell Programming and Scripting
Hi,
I made a following script for Data Backup on Tape Device, but script is not working fine. Please review the script.
DAT=`date +%d_%m_%Y`
BDIR="/home/userid/$DAT"
TD="/dev/st0"
LOGS="/scripts/$DAT"
clear
echo | tee $LOGS
if mt -f $TD status | grep 41010000 > /dev/null
then... (3 Replies)
Discussion started by: telnor
3 Replies
4. Shell Programming and Scripting
hi,
Please tell me, how to restore backup to normal location in shell scripting while deployment script is getting an error.
Thanks (2 Replies)
Discussion started by: bcb
2 Replies
5. AIX
Hello all....
I am trying to backup a client from the NIM master. While doing so, I get this error:
backup: 0511-089
can not open /tmp/6282.mnt0/<hostname>_mksysb_<date>
0042-001 m_mkbosi: processing error encountered on client
0042-001 m_mkbosi: processing error encountered on master... (0 Replies)
Discussion started by: solaix14
0 Replies
6. AIX
Hi I am receiving the following backup error when using backup -0uf /dev/rmt0.1 for the file system
backup: Backing up /dev/rfslv00 (/u04) to /dev/rmt0.1.
backup: 0511-251 The file system is still mounted; data may not be consistent.
Use the umount command to unmount the filesystem;... (1 Reply)
Discussion started by: jimthompson
1 Replies
7. Solaris
Hello buddy,
I used usfbackup command but error after full backup Solaris 5.5.1
/dev/c0t3d0s0 /
/dev/c0t3d0s6 /usr
I get error when restart after complete full backup
Can't load the root file system
Type 'go' to resume
***FULL MY STORY***
... (1 Reply)
Discussion started by: posky
1 Replies
8. HP-UX
Hy everyone and happy new year!
I would like to know how can i verify that some of my backup tapes, created with vdump, are ok?
Some of them were created before i came to the company that i'm workin for now, so i would like to test them before i actually use them. Unfortunately, i don't have... (0 Replies)
Discussion started by: veccinho
0 Replies
9. UNIX for Dummies Questions & Answers
After perfomring a remote backup from HP-UX to a SUN, it prompt the following error.
Can you please advise what does this error means?
How to retify this error?
"dd: unexpected short write, wrote 0 bytes, expected 10240
205802517+126 records in
10290129+0 records out"
The command used is ... (1 Reply)
Discussion started by: gelbvonn
1 Replies
10. UNIX for Dummies Questions & Answers
Hello everyone,
I like to start off by saying thank-you all. You guys have saved my butt alot of time. Well I have a problem in which I can't find in the search.
I'm trying to do a tar backup to a DDS3 tape as root:
tar -cvf /dev/rmt/0 /home/larry
the error
tar:... (8 Replies)
Discussion started by: larry
8 Replies
newinv(1) General Commands Manual newinv(1)
NAME
newinv - Updates distribution kit master inventory
SYNOPSIS
/usr/bin/newinv mi-file input-path...
OPERANDS
The pathname of the master inventory file to be processed. If no master inventory file exists, you must create an empty one before using
the newinv command. The name of the product hierarchy to be scanned for files belonging in the inventory. All files and directories found
below the input-path are processed as belonging in the inventory.
DESCRIPTION
The newinv command interactively maintains the master inventory files used for producing distribution kits in setld format. The program
updates the master inventory for a product when changes are made to the hierarchy of files that are to be packaged in the subsets which
constitute the product.
The product hierarchy is scanned to produce a list of component path names relative to input-path. The list of pathnames is processed
against the mi-file to produce a list of files that have been removed from the product hierarchy and a list of files that have been added.
The user is then given an opportunity to intervene and direct the inventory maintenance by editing these lists. The user is placed in the
editor with each list available for editing. The editor used is the one specified by the EDITOR environment variable. If EDITOR is not
set, vi is used. When editing the list of files that have been removed from the product, the user is expected to verify that the removals
were intentional and confirm the intent by removing the associated records from the file. When editing the list of added files, the user
is expected to provide options and subset information for each new file, transforming the elements of the list into master inventory
records.
To produce a new copy of the master inventory file, both of these lists are merged with the records for the files which existed in the pre-
vious version and are still included.
RESTRICTIONS
The default text editor, if not specified in $EDITOR, is /usr/ucb/vi.
Files in the product hierarchy cannot be excluded from the master inventory. Files can be blocked from being kitted in the final distribu-
tion kit by setting the subset field of the master inventory record to a minus sign (-).
ERRORS
The mi-file specified on the command line cannot be found. The input-path directory specified on the command line does not exist.
EXAMPLES
To update the hypothetical master inventory file OAT100.mi from the hierarchy beginning at /var/kits/input, type:
newinv OAT100.mi /var/kits/input
FILES
Backup copy of master inventory The list of files missing from the product The list of files new to the product Intermediate join file List
of all files in the product
SEE ALSO
invcutter(1), kits(1), vi(1), setld(8) stl_mi(4) environ(5) Guide to Preparing Product Kits
newinv(1)
