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
cdslinvchk(8) System Manager's Manual cdslinvchk(8)
NAME
cdslinvchk - Checks the CDSL inventory of the base operating system and layered applications.
SYNOPSIS
/usr/sbin/cdslinvchk [log_file_path]
OPTIONS
The path name to a location for the log file. By default this will be /var/adm/cdsl_check_list.
DESCRIPTION
Use the cdslinvchk script to verify the current inventory of Context Dependent Symbolic Links (CDSLs) on a running system. CDSLs are spe-
cial symbolic links that enable a system to work in a cluster. If CDSLs are accidentally removed, your system will not function correctly
in a cluster. While this is not a problem for stand-alone systems, you may not be able to add the system as a member of a working cluster
at some future time. You can run this script at any time or configure it to run at system start-up, or as a cron task.
When you invoke the script, it checks the CDSLs on the running system against CDSLs of the installed inventory in /usr/.smdb and the addi-
tional entries in /var/adm/cdsl_admin.inv, and ensures that each target file exists on the system as a properly-constituted CDSL. If the
check is successful, the following message is displayed and the script terminates: Successful CDSL inventory check
If the script finds inconsistencies in the inventory, warning messages are displayed on your terminal and logged to the default log file at
/var/adm/cdsl_check_list. You can specify an alternate location for the log fill if required. The script locates any modified, missing,
or replaced CDSLs. Note that the previous copy of the log file is renamed and retained for reference and is renamed by appending to the
filename.
Refer to the System Administration guide for information on recreating any missing or broken CDSLs. Refer to the hier(5) reference page
for an inventory of CDSLs.
MESSAGES
One or more of the following messages may be displayed and logged to the log file: Unable to create <pathname> report file -- the script
was not able to create a log file. Check the target directory and security. Expected CDSL: <cdsl_pathname> -> <pathname> CDSL Target has
been modified to: <pathname> CDSL has been replaced with <pathname> CDSL is missing Failed CDSL inventory check. See details in <log file>
FILES
Additional inventory file entries. This file will not exist on all systems. The current and previous log files for inventory errors and
messages
SEE ALSO
Commands: cron(8)
Others: hier(5)
See also the System Administration guide for details of CDSLs
cdslinvchk(8)
