Sponsored Content
Operating Systems HP-UX Bad performance but Low CPU loading? Post 302411162 by GreenShery on Wednesday 7th of April 2010 09:12:42 PM
Old 04-07-2010
I checked some backup job, they're set at other time. Such as 1:00,23:00...
 

10 More Discussions You Might Find Interesting

1. Programming

CPU Loading

How can I measure CPU loading (like performance monitor in Windows OS). I use Solaris but I would like to write portable code. Besides, I have to write programm to load CPU with known percent. How can I use CPU in 30% for example. Thanks for any ideas. (6 Replies)
Discussion started by: serge
6 Replies

2. UNIX for Dummies Questions & Answers

comparing Huge Files - Performance is very bad

Hi All, Can you please help me in resolving the following problem? My requirement is like this: 1) I have two files YESTERDAY_FILE and TODAY_FILE. Each one is having nearly two million data. 2) I need to check each record of TODAY_FILE in YESTERDAY_FILE. If exists we can skip that by... (5 Replies)
Discussion started by: madhukalyan
5 Replies

3. AIX

Bad performance when log in with putty

Hello guys! I'm n00b in AIX and I'm sticked in a problem. (my English is poor enough, but I hope you can understand me :P). So.. I'm trying to connect to an AIX machine with putty, and .. 'using username xxx' appears after 2 sec (OK), but 'xxx@ip's password' appears after 1:15 min. After... (6 Replies)
Discussion started by: combat2k
6 Replies

4. Solaris

Low average cpu utilization.

Hi to all, i have an app on solaris 5.8 writed in C++ (3.2.1) that use multi threading. Hardware has 8 cpu. When i run my app i note that the average of cpu go at least at 40%, and the performance are not so higher.. There is a cpu limitation on solaris, that dedicate only a part of cpu... (3 Replies)
Discussion started by: Moodie
3 Replies

5. Solaris

Sun T1000 application low performance

Hello All. I have Sun T1000 server with Solaris 10. On T1000 installed EMC smarts, application for monitoring network devices via SNMP + SNMP. So, Smarts has own DB (contains object - devices and relationships), file takes 30 mb, now, all queries to DB works very slow, so Smarts works too slow,... (5 Replies)
Discussion started by: hemulll
5 Replies

6. Solaris

By loading I have received the following issue: BAD PBR SIGN.

Hi folks. By disk cloning on Solaris x86, I used a command dd. I pulled out the source and inserted the new disk. By loading I have received the following issue: BAD PBR SIGN. :( (5 Replies)
Discussion started by: wolfgang
5 Replies

7. Solaris

Performance (iops) becomes bad, what is the reason?

I have written a virtual HBA driver named "xmp_vhba". A scsi disk is attached on it. as shown below: xmp_vhba, instance #0 disk, instance #11 But the performance became very bad when we read/write the scsi disk using the vdbench(a read/write io tool). What is the reason? ... (7 Replies)
Discussion started by: ForgetChen
7 Replies

8. AIX

High Runqueue (R) LOW CPU LOW I/O Low Network Low memory usage

Hello All I have a system running AIX 61 shared uncapped partition (with 11 physical processors, 24 Virtual 72GB of Memory) . The output from NMON, vmstat show a high run queue (60+) for continous periods of time intervals, but NO paging, relatively low I/o (6000) , CPU % is 40, Low network.... (9 Replies)
Discussion started by: IL-Malti
9 Replies

9. UNIX for Dummies Questions & Answers

CPU with long hours in top, is this bad?

Hi, We have a Solaris server that has about 43 Oracle databases on it and we also have the Oracle Enterprise Manager - emagent that is used to monitor these databases When running top, the emagent is showing as one of the top process. Excerpts from running top shows something as below: ... (3 Replies)
Discussion started by: newbie_01
3 Replies

10. AIX

AIX lpar bad disk I/O performance - 4k per IO limitation ?

Hi Guys, I have fresh new installed VIO 2.2.3.70 on a p710, 3 physical SAS disks, rootvg on hdisk0 and 3 VIO clients through vscsi, AIX7.1tl4 AIX6.1tl9 RHEL6.5ppc, each lpar has its rootvg installed on a LV on datavg (hdisk2) mapped to vhost0,1,2 There is no vg on hdisk1, I use it for my... (1 Reply)
Discussion started by: frenchy59
1 Replies
BACKUP_JOBS(8)						       AFS Command Reference						    BACKUP_JOBS(8)

NAME
       backup_jobs - Lists pending and running operations in interactive mode

SYNOPSIS
       jobs [-help]

       j [-h]

DESCRIPTION
       The backup jobs command lists the job ID number and status of each backup operation running or pending in the current interactive session.

       This command can be issued in interactive mode only. If the issuer of the backup interactive command included the -localauth flag, the
       -cell argument, or both, those settings apply to this command also.

       To terminate operations that appear in the output, issue the backup kill command and identify the operation to cancel with the job ID
       number from this command's output.

       To check the status of a Tape Coordinator, rather than of a certain operation, use the backup status command.

OPTIONS
       -help
	   Prints the online help for this command. All other valid options are ignored.

OUTPUT
       The output always includes the expiration date and time of the tokens that the backup command interpreter is using during the current
       interactive session, in the following format:

	  <date>   <time>: TOKEN EXPIRATION

       If the execution date and time specified for a scheduled dump operation is later than <date time>, then its individual line (as described
       in the following paragraphs) appears below this line to indicate that the current tokens will not be available to it.

       If the issuer of the backup command included the -localauth flag when entering interactive mode, the line instead reads as follows:

	  :  TOKEN NEVER EXPIRES

       The entry for a scheduled dump operation has the following format:

	  Job <job_ID>:  <timestamp>:  dump  <volume_set>  <dump_level>

       where

       <job_ID>
	   Is a job identification number assigned by the Backup System.

       <timestamp>
	   Indicates the date and time the dump operation is to begin, in the format month/date/year hours:minutes (in 24-hour format)

       <volume_set>
	   Indicates the volume set to dump.

       <dump_level>
	   Indicates the dump level at which to perform the dump operation.

       The line for a pending or running operation of any other type has the following format:

	  Job <job_ID>:  <operation>  <status>

       where

       <job_ID>
	   Is a job identification number assigned by the Backup System.

       <operation>
	   Identifies the operation the Tape Coordinator is performing, which is initiated by the indicated command:

	   Dump (dump name)
	       Initiated by the backup dump command. The dump name has the following format:

		   <volume_set_name>.<dump_level_name>

	   Restore
	       Initiated by the backup diskrestore, backup volrestore, or backup volsetrestore command.

	   Labeltape (tape_label)
	       Initiated by the backup labeltapen command. The tape_label is the name specified by the backup labeltape command's -name or -pname
	       argument.

	   Scantape
	       Initiated by the backup scantape command.

	   SaveDb
	       Initiated by the backup savedb command.

	   RestoreDb
	       Initiated by the backup restoredb command.

       <status>
	   Indicates the job's current status in one of the following messages. If no message appears, the job is either still pending or has
	   finished.

	   number Kbytes, volume volume_name
	       For a running dump operation, indicates the number of kilobytes copied to tape or a backup data file so far, and the volume
	       currently being dumped.

	   number Kbytes, restore.volume
	       For a running restore operation, indicates the number of kilobytes copied into AFS from a tape or a backup data file so far.

	   [abort requested]
	       The backup kill command was issued, but the termination signal has yet to reach the Tape Coordinator.

	   [abort sent]
	       The operation is canceled by the backup kill command.  Once the Backup System removes an operation from the queue or stops it from
	       running, it no longer appears at all in the output from the command.

	   [butc contact lost]
	       The backup command interpreter cannot reach the Tape Coordinator. The message can mean either that the Tape Coordinator handling
	       the operation was terminated or failed while the operation was running, or that the connection to the Tape Coordinator timed out.

	   [done]
	       The Tape Coordinator has finished the operation.

	   [drive wait]
	       The operation is waiting for the specified tape drive to become free.

	   [operator wait]
	       The Tape Coordinator is waiting for the backup operator to insert a tape in the drive.

EXAMPLES
       The following example shows that two restore operations and one dump operation are running (presumably on different Tape Coordinators) and
       that the backup command interpreter's tokens expire on 22 April 1999 at 10:45 am:

	  backup> jobs
	  Job 1: Restore, 1306 Kbytes, restore.volume
	  Job 2: Dump (user.sunday1), 34 Kbytes, volume user.pat.backup
	  Job 3: Restore, 2498 Kbytes, restore.volume
		 04/22/1999 10:45: TOKEN EXPIRATION

PRIVILEGE REQUIRED
       None. However, queuing any operation requires privilege, and it is possible to issue this command only within the interactive session in
       which the jobs are queued.

SEE ALSO
       backup(8), backup_interactive(8), backup_kill(8), backup_quit(8)

COPYRIGHT
       IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved.

       This documentation is covered by the IBM Public License Version 1.0.  It was converted from HTML to POD by software written by Chas
       Williams and Russ Allbery, based on work by Alf Wachsmann and Elizabeth Cassell.

OpenAFS 							    2012-03-26							    BACKUP_JOBS(8)
All times are GMT -4. The time now is 07:08 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy