Use v $ session_longops to monitor RMAN backup progress

The database backed up this time is a large header with 10 TB data files. However, the management only allows backup using four channels, which directly kills the backup speed. Run the glance command to view the cp

The database backed up this time is a large header with 10 TB data files. However, the management only allows backup using four channels, which directly kills the backup speed. Run the glance command to view the cp

The database backed up this time is a large header with 10 TB data files. However, the management only allows backup using four channels, which directly kills the backup speed. You can run the glance command to check the cpu. the disk and memory are not under high pressure, even if eight or 16 channels are enabled. This host is a dual-node RAC. Each host has 32 CPUs and is backed up when the business is low on weekends.

The limitations of these four channels are like how long it will take for a Ferrari to run on the highway with a gear mounted...

1. Check the status of the target database before backing up.

Look at dba_segments. The total size of the actual data block is 5 TB.
SQL> select sum (bytes)/1024/1024/1024 GB from dba_segments;

GB
----------
5287.02454

Look at dba_data_files. The total data file size is about 10 TB.
SQL> select sum (bytes)/1024/1024/1024 GB from dba_data_files;

GB
----------
9402.70592

The temporary backup path is/orabak, and the disk space is 9 TB.
Bdf
/Dev/vx/dsk/bakdg/bakvol
9961472000 634128 9883018840 0%/orabak

2. This is a common compressed database full backup script, including control files, parameter files, and archive log files. The most prominent part is the four channels, which make people feel bad.
Vi backup. cmd

Rman target/< Run {
Allocate channel c1 device type disk maxpiecesize = 20G;
Allocate channel c2 device type disk maxpiecesize = 20G;
Allocate channel c3 device type disk maxpiecesize = 20G;
Allocate channel c4 device type disk maxpiecesize = 20G;
Backup tag 'sh _ db_full 'as compressed backupset format'/orabak/sh_db_full _ % U' database
Include current controlfile;
SQL 'alter system archive log current ';
Backup tag 'sh _ arch 'as compressed backupset archivelog all format'/orabak/sh_arch _ % U ';
Release channel c1;
Release channel c2;
Release channel c3;
Release channel c4;
}
EOF

3. Grant backup scripts to Oracle users.
Chmod 755 backup. cmd

4. Run the backup script in the background.
Nohup backup. cmd &

5. Use the nohup. out log to monitor rman backup output

Backup time:, December 12
Tail-f nohup. out

6. Run the glance command to check the system status during backup. It is found that the CPU usage is only 23%, the disk pressure is only 15%, and the cpu occupied by the four channels is about 100%. In fact, we can have a lot of resources but cannot use them.

Glance 11.13.007 16:47:43 jccmsdb1 ia64 Current Avg High
Certificate ------------------------------------------------------------------------------------------------------------------------------------
CPU Util ssn nu uw w | 23% 23% 33%
Disk Util F | 15% 11% 30%
Mem Util s su uf f | 70% 70% 70%
Networkil u ur r | 54% 54% 54%
Certificate ------------------------------------------------------------------------------------------------------------------------------------
Process list Users = 9
User CPU % Thrd Disk Memory Block
Process Name PID Name (2400% max) Cnt IO rate rss vss On
Certificate ------------------------------------------------------------------------------------------------------------------------------------
Oraclesgpmdb 12326 oracle 100 1 51.9 92.0 mb 104 mb PRI
Oraclesgpmdb 12280 oracle 100 1 54.2 92.0 mb 104 mb PRI
Oraclesgpmdb 12281 oracle 99.6 1 54.4 92.0 mb 104 mb PRI
Oraclesgpmdb 12304 oracle 99.4 1 57.6 92.0 mb 104 mb PRI
Ora_m000_sgp 28333 oracle 15.6 1 0.0 131 mb 163 mb PRI
Perl 18601 root 9.1 1 0.0 712kb 724kb died
Ora_dia0_sgp 6943 oracle 7.6 1 0.0 134 mb 136 mb SLEEP
Java 9109 root 7.4 41 0.7 305 mb 759 mb SLEEP
Df 18605 root 6.2 1 0.0 84kb 160kb died
Glance 19308 quest 6.0 1 0.0 20.1 mb 23.9 mb STRMS
Ocssd. bin 16787 grid 5.1 19 2.8 138 mb 138 mb SLEEP
Vxfsd 342 root 4.5 217 117.3 79.1 mb 89.0 mb memory m

7. Check the rman backup progress in the v $ session_longops view. This part is also the focus of this blog article.

SQL>/