Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Sysback command line
Operating Systems AIX Sysback command line Post 302739211 by spacebar on Monday 3rd of December 2012 05:53:18 PM
Old 12-03-2012
Backup, List, Verify and Restore Command Output Screen
The output screen for the backup, list, verify, and restore options is different from
that of other SMIT-executed commands. This screen provides the following
advantages:
  • Output is not saved in the SMIT log file (smit.log). This prevents very long file lists from taking unnecessary space on the disk.
    You are still provided the option of writing the output to a log file after the command has completed.
  • There is no delay when the command has completed. The delay is normally required for SMIT processing and writing of the smit.log file.
  • Command output (stdout) and error (stderr) are displayed in separate windows.
  • This provides much cleaner output for commands that provide both standard output and standard error messages.
  • The complete command and the time the command started and ended is displayed at the top of the screen.

You should be able write the output output to a log file after the command has completed.
You can also try this by redirecting output to a specified file:
Code:
smit sb_list >list.txt 2>&1

 

10 More Discussions You Might Find Interesting

1. AIX

sysback end of tpae

We are currently using AIX sysback for our backups and I have a script that kicks off the backups daily. We just had the problem with the tape filling up and hanging the script. I want to add a test to my script to listen for the End of Tape error or tape full error. I can't find any information... (0 Replies)
Discussion started by: daveisme
0 Replies

2. AIX

Sysback Warnings

I am currently running backups using an entry in the crontab redirection the output to a file. From time to time I get a backup complete with Warnings but don't know what the warnings are and they don't appear in the file. Where can I view the warings? Is there a command to view the warnings? ... (2 Replies)
Discussion started by: daveisme
2 Replies

3. AIX

sysback hangs

I've set sysback to run in the cron daily to backup my servers to a nim servers SAN storage. Every once and a while the backup process hangs and the backup doesn't complete. When I check the processes the sysback processes are still running hours after sysback would normally end. I don't see any... (1 Reply)
Discussion started by: daveisme
1 Replies

4. AIX

sysback 6.1 backup questions

In smitty sysback I see there is are Offline Mirror backup and Snap Shot backup options and want to know how to use these backups without TSM. Or does anybody know where I can find information on setting up and preforming these type of backups and restores from the backups? (0 Replies)
Discussion started by: daveisme
0 Replies

5. Emergency UNIX and Linux Support

Missing requisite filesets when installing Sysback AIX

I am trying to install the Sysback client (TSM for System Backup and Recovery) 6.1 on an LPAR running AIX 5.3. One of the filesets is failing to install. Here's what it says in the preview: FAILURES: tivoli.tsm.client.api.32bit 5.5.1.0 # TSM Client - Application Pro... MISSING... (2 Replies)
Discussion started by: need2bageek
2 Replies

6. AIX

sysback - estimate backup size only?

Is there a flag to send to sysback on the command line so it will return the estimated backup size and exit? We're having issues with running to a second tape at a remote data center, and I want to alter the script to exit or add exclusions if the backup is over a certain size. The other... (0 Replies)
Discussion started by: tommysalami
0 Replies

7. AIX

sysback with aix over NIM

HELLO ALL i have installed aix 6.2 , and install sysback 6.1 over Nim , and cinfigure it by Nim AND sysback smitty menu with create spot and lppsource and make TSM configration for that, i take image backup(installation image) successfully but when i want to restore this image , the boot cycle... (5 Replies)
Discussion started by: nancy_ghawanmeh
5 Replies

8. Shell Programming and Scripting

sed command to replace a line at a specific line number with some other line

my requirement is, consider a file output cat output blah sdjfhjkd jsdfhjksdh sdfs 23423 sdfsdf sdf"sdfsdf"sdfsdf"""""dsf hellow there this doesnt look good et cetc etc etcetera i want to replace a line of line number 4 ("this doesnt look good") with some other line ... (3 Replies)
Discussion started by: vivek d r
3 Replies

9. Shell Programming and Scripting

sed command to replace a line in a file using line number from the output of a pipe.

Sed command to replace a line in a file using line number from the output of a pipe. Is it possible to replace a whole line piped from someother command into a file at paritcular line... here is some basic execution flow.. the line number is 412 lineNo=412 Now i have a line... (1 Reply)
Discussion started by: vivek d r
1 Replies

10. Shell Programming and Scripting

Perl command line option '-n','-p' and multiple files: can it know a file name of a printed line?

I am looking for help in processing of those options: '-n' or '-p' I understand what they do and how to use them. But, I would like to use them with more than one file (and without any shell-loop; loading the 'perl' once.) I did try it and -n works on 2 files. Question is: - is it possible to... (6 Replies)
Discussion started by: alex_5161
6 Replies

LEARN ABOUT OSF1

log

log(8)							      System Manager's Manual							    log(8)

NAME

       log - Records input and output from a program

SYNOPSIS

       /usr/sbin/log <logfile> <command>

OPERANDS

       The file in which to record the interaction being logged.  The command to execute.

DESCRIPTION

       The  log  program  runs <command> and logs the input to and output from <command> to the <logfile> file.  Input and output are logged until
       <command> exits, the log program exits, and the exit status of <command> is returned.

       The log program is used by the system  installation  procedure  and  the  it(8)	command  to  create  the  /var/adm/smlogs/install.log  and
       /var/adm/smlogs/it.log installation log files.

RESTRICTIONS

       Because	the  log  program is used in the installation standalone environment, program size was the greatest concern in its implementation.
       The log program does not search for the PATH variable to locate <command> and error messages are terse.

       The log program causes <command> to take standard input from and write standard output and standard error to  UNIX  pipes.   Some  commands
       will  not  be able to operate in this environment; therefore, it is suggested that you use the script(1) command instead.  UNIX shells will
       not issue prompts when run from log unless the shell is started with an explicit interactive switch (-i for most shells).  For example, log
       foo.tmp /sbin/sh -i

       In the previous example, foo.tmp is the name of <logfile>.

       The  log  program  intercepts  end-of-file (usually Ctrl/d).  Therefore programs which normally receive end-of-file as an exit command must
       exit by some other means.

ERRORS

       Log open error

   Explanation:
       The log program was unable to open <logfile>. Verify that the directory exists and that ownerships and permissions are set correctly.

       Exec Error

   Explanation:
       The log program was unable to execute <command>. Verify that you specified a full pathname for <command> and  that  <command>  is  an  exe-
       cutable file.

       Fork Error

   Explanation:
       The log program was unable to create one of the processes it requires to log data.

SEE ALSO

       Commands: it(8), script(1)

																	    log(8)
All times are GMT -4. The time now is 03:52 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy