RMAN OVERVIEW

 

                                                     RMAN

 

[oracle@ranesh ~]$ rman target /

Recovery Manager: Release 12.1.0.2.0 - Production on Thu Sep 17 20:00:45 2020

Copyright (c) 1982, 2014, Oracle and/or its affiliates.  All rights reserved.

connected to target database: PRIME (DBID=2122042046)

 

RMAN> show all;         

using target database control file instead of recovery catalog

RMAN configuration parameters for database with db_unique_name STAND are:

CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default

CONFIGURE BACKUP OPTIMIZATION OFF; # default

CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default

CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default

CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default

CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default

CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default

CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default

CONFIGURE MAXSETSIZE TO UNLIMITED; # default

CONFIGURE ENCRYPTION FOR DATABASE OFF; # default

CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default

CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default

CONFIGURE RMAN OUTPUT TO KEEP FOR 7 DAYS; # default

CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default

 

To perforn a full database backup use:

 

RMAN> backup database;

Starting backup at 17-SEP-20

allocated channel: ORA_DISK_1

channel ORA_DISK_1: SID=37 device type=DISK

channel ORA_DISK_1: starting full datafile backup set

channel ORA_DISK_1: specifying datafile(s) in backup set

input datafile file number=00001 name=/u01/app/oracle/oradata/stand/system01.dbf

input datafile file number=00003 name=/u01/app/oracle/oradata/stand/sysaux01.dbf

input datafile file number=00004 name=/u01/app/oracle/oradata/stand/undotbs01.dbf

input datafile file number=00006 name=/u01/app/oracle/oradata/stand/users01.dbf

channel ORA_DISK_1: starting piece 1 at 17-SEP-20

channel ORA_DISK_1: finished piece 1 at 17-SEP-20

piece handle=/u01/app/oracle/fast_recovery_area/STAND/backupset/2020_09_17/o1_mf_nnndf_TAG20200917T200915_hp6x8mmp_.bkp tag=TAG20200917T200915 comment=NONE

channel ORA_DISK_1: backup set complete, elapsed time: 00:00:56

channel ORA_DISK_1: starting full datafile backup set

channel ORA_DISK_1: specifying datafile(s) in backup set

including current control file in backup set

including current SPFILE in backup set

channel ORA_DISK_1: starting piece 1 at 17-SEP-20

channel ORA_DISK_1: finished piece 1 at 17-SEP-20

piece handle=/u01/app/oracle/fast_recovery_area/STAND/backupset/2020_09_17/o1_mf_ncsnf_TAG20200917T200915_hp6xbddz_.bkp tag=TAG20200917T200915 comment=NONE

channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01

Finished backup at 17-SEP-20

 

To backup all archive logs use:

RMAN> BACKUP ARCHIVELOG ALL;

 

Starting backup at 17-SEP-20

using channel ORA_DISK_1

channel ORA_DISK_1: starting archived log backup set

channel ORA_DISK_1: specifying archived log(s) in backup set

input archived log thread=1 sequence=77 RECID=1 STAMP=1044910854

input archived log thread=1 sequence=78 RECID=2 STAMP=1044911049

input archived log thread=1 sequence=79 RECID=3 STAMP=1044911087

input archived log thread=1 sequence=80 RECID=4 STAMP=1044911458

input archived log thread=1 sequence=81 RECID=5 STAMP=1044911462

input archived log thread=1 sequence=82 RECID=6 STAMP=1044911473

input archived log thread=1 sequence=83 RECID=9 STAMP=1044911706

input archived log thread=1 sequence=84 RECID=11 STAMP=1044913561

channel ORA_DISK_1: starting piece 1 at 17-SEP-20

channel ORA_DISK_1: finished piece 1 at 17-SEP-20

piece handle=/u01/app/oracle/fast_recovery_area/STAND/backupset/2020_09_17/o1_mf_annnn_TAG20200917T201607_hp6xoho7_.bkp tag=TAG20200917T201607 comment=NONE

channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01

channel ORA_DISK_1: starting archived log backup set

channel ORA_DISK_1: specifying archived log(s) in backup set

input archived log thread=1 sequence=1 RECID=12 STAMP=1044913749

input archived log thread=1 sequence=2 RECID=13 STAMP=1044914249

input archived log thread=1 sequence=3 RECID=14 STAMP=1044914459

input archived log thread=1 sequence=4 RECID=15 STAMP=1044914492

input archived log thread=1 sequence=5 RECID=16 STAMP=1044914513

input archived log thread=1 sequence=6 RECID=17 STAMP=1044915866

input archived log thread=1 sequence=7 RECID=18 STAMP=1044915890

input archived log thread=1 sequence=8 RECID=19 STAMP=1044916659

channel ORA_DISK_1: starting piece 1 at 17-SEP-20

channel ORA_DISK_1: finished piece 1 at 17-SEP-20

piece handle=/u01/app/oracle/fast_recovery_area/STAND/backupset/2020_09_17/o1_mf_annnn_TAG20200917T201607_hp6xok21_.bkp tag=TAG20200917T201607 comment=NONE

channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01

channel ORA_DISK_1: starting archived log backup set

channel ORA_DISK_1: specifying archived log(s) in backup set

input archived log thread=1 sequence=1 RECID=20 STAMP=1044917218

input archived log thread=1 sequence=2 RECID=23 STAMP=1044917219

input archived log thread=1 sequence=3 RECID=26 STAMP=1044917224

input archived log thread=1 sequence=4 RECID=28 STAMP=1044917226

input archived log thread=1 sequence=5 RECID=30 STAMP=1044917228

channel ORA_DISK_1: starting piece 1 at 17-SEP-20

channel ORA_DISK_1: finished piece 1 at 17-SEP-20

piece handle=/u01/app/oracle/fast_recovery_area/STAND/backupset/2020_09_17/o1_mf_annnn_TAG20200917T201607_hp6xol7l_.bkp tag=TAG20200917T201607 comment=NONE

channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01

Finished backup at 17-SEP-20

 

To backup the database and all archive log files use:

RMAN> BACKUP DATABASE PLUS ARCHIVELOG;

 

To backup the current controlfile :

RMAN> BACKUP CURRENT CONTROLFILE;

 

Starting backup at 17-SEP-20

using channel ORA_DISK_1

channel ORA_DISK_1: starting full datafile backup set

channel ORA_DISK_1: specifying datafile(s) in backup set

including current control file in backup set

channel ORA_DISK_1: starting piece 1 at 17-SEP-20

channel ORA_DISK_1: finished piece 1 at 17-SEP-20

piece handle=/u01/app/oracle/fast_recovery_area/STAND/backupset/2020_09_17/o1_mf_ncnnf_TAG20200917T202643_hp6y9dkk_.bkp tag=TAG20200917T202643 comment=NONE

channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01

Finished backup at 17-SEP-20

 

SPFILE BACKUP

 

RMAN> BACKUP SPFILE;

Starting backup at 17-SEP-20

using channel ORA_DISK_1

channel ORA_DISK_1: starting full datafile backup set

channel ORA_DISK_1: specifying datafile(s) in backup set

including current SPFILE in backup set

channel ORA_DISK_1: starting piece 1 at 17-SEP-20

channel ORA_DISK_1: finished piece 1 at 17-SEP-20

piece handle=/u01/app/oracle/fast_recovery_area/STAND/backupset/2020_09_17/o1_mf_nnsnf_TAG20200917T202821_hp6ydf9r_.bkp tag=TAG20200917T202821 comment=NONE

channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01

Finished backup at 17-SEP-20

 

Datafile backups

 

RMAN> backup datafile '/u01/app/oracle/oradata/stand/system01.dbf';

 

Starting backup at 17-SEP-20

using channel ORA_DISK_1

channel ORA_DISK_1: starting full datafile backup set

channel ORA_DISK_1: specifying datafile(s) in backup set

input datafile file number=00001 name=/u01/app/oracle/oradata/stand/system01.dbf

channel ORA_DISK_1: starting piece 1 at 17-SEP-20

channel ORA_DISK_1: finished piece 1 at 17-SEP-20

piece handle=/u01/app/oracle/fast_recovery_area/STAND/backupset/2020_09_17/o1_mf_nnndf_TAG20200917T202950_hp6yh6pv_.bkp tag=TAG20200917T202950 comment=NONE

channel ORA_DISK_1: backup set complete, elapsed time: 00:00:26

channel ORA_DISK_1: starting full datafile backup set

channel ORA_DISK_1: specifying datafile(s) in backup set

including current control file in backup set

including current SPFILE in backup set

channel ORA_DISK_1: starting piece 1 at 17-SEP-20

channel ORA_DISK_1: finished piece 1 at 17-SEP-20

piece handle=/u01/app/oracle/fast_recovery_area/STAND/backupset/2020_09_17/o1_mf_ncsnf_TAG20200917T202950_hp6yj19f_.bkp tag=TAG20200917T202950 comment=NONE

channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01

Finished backup at 17-SEP-20

 

 

 

 

 

 

 

 

 

Alternatively specify datafile no

 

RMAN> backup datafile 1;

 

The data file number can be obtained from V$DATAFILE

 

RMAN> SELECT file#, name FROM v$datafile;

     FILE#                                                                                   NAME                                                                           

--------------------------------------------------------------------------------

         1                                                              /u01/app/oracle/oradata/stand/system01.dbf

 

         3                                                                 /u01/app/oracle/oradata/stand/sysaux01.dbf

 

         4                                                                  /u01/app/oracle/oradata/stand/undotbs01.dbf

 

         6                                                                /u01/app/oracle/oradata/stand/users01.dbf

 

 

 

 

......when the RMAN backup is running, if you want to see the proress, you can query the V$RMAN_STATUS

 

output

 

RMAN> SELECT OPERATION, STATUS, MBYTES_PROCESSED, START_TIME, END_TIME from V$RMAN_STATUS;

 

OPERATION                         STATUS                  MBYTES_PROCESSED

--------------------------------- ----------------------- ----------------

START_TIM END_TIME

--------- ---------

RMAN                              RUNNING                                0

17-SEP-20 17-SEP-20

 

DUPLICATE DB FROM ACTIVE USING B  FAILED                                 0

03-JUL-20 03-JUL-20

 

RMAN                              COMPLETED WITH ERRORS                  0

03-JUL-20 03-JUL-20

 

RMAN                              COMPLETED                              0

 

Incremental Backups

 

By default backups are full (level 0). Backups can also be incremental (level 1).

Incremental backups can be:

Differential - includes all changes since the last full or incremental backup

Cumulative - includes all changes since the last full backup

Differential backups require less space. Cumulative backups are faster to restore

 

RMAN> BACKUP INCREMENTAL LEVEL 1 DATABASE;

 

Starting backup at 17-SEP-20

using target database control file instead of recovery catalog

allocated channel: ORA_DISK_1

channel ORA_DISK_1: SID=39 device type=DISK

channel ORA_DISK_1: starting incremental level 0 datafile backup set

channel ORA_DISK_1: specifying datafile(s) in backup set

input datafile file number=00001 name=/u01/app/oracle/oradata/stand/system01.dbf

input datafile file number=00003 name=/u01/app/oracle/oradata/stand/sysaux01.dbf

input datafile file number=00004 name=/u01/app/oracle/oradata/stand/undotbs01.dbf

input datafile file number=00006 name=/u01/app/oracle/oradata/stand/users01.dbf

channel ORA_DISK_1: starting piece 1 at 17-SEP-20

channel ORA_DISK_1: finished piece 1 at 17-SEP-20

piece handle=/u01/app/oracle/fast_recovery_area/STAND/backupset/2020_09_17/o1_mf_nnnd0_TAG20200917T204810_hp6zkm6v_.bkp tag=TAG20200917T204810 comment=NONE

channel ORA_DISK_1: backup set complete, elapsed time: 00:00:55

channel ORA_DISK_1: starting incremental level 1 datafile backup set

channel ORA_DISK_1: specifying datafile(s) in backup set

including current control file in backup set

including current SPFILE in backup set

channel ORA_DISK_1: starting piece 1 at 17-SEP-20

channel ORA_DISK_1: finished piece 1 at 17-SEP-20

piece handle=/u01/app/oracle/fast_recovery_area/STAND/backupset/2020_09_17/o1_mf_ncsn1_TAG20200917T204810_hp6zmcvs_.bkp tag=TAG20200917T204810 comment=NONE

channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01

Finished backup at 17-SEP-20

 

RMAN> BACKUP INCREMENTAL LEVEL 1 CUMULATIVE DATABASE;

 

Starting backup at 17-SEP-20

using channel ORA_DISK_1

channel ORA_DISK_1: starting incremental level 1 datafile backup set

channel ORA_DISK_1: specifying datafile(s) in backup set

input datafile file number=00001 name=/u01/app/oracle/oradata/stand/system01.dbf

skipping datafile 00001 because it has not changed

input datafile file number=00003 name=/u01/app/oracle/oradata/stand/sysaux01.dbf

skipping datafile 00003 because it has not changed

input datafile file number=00004 name=/u01/app/oracle/oradata/stand/undotbs01.dbf

skipping datafile 00004 because it has not changed

input datafile file number=00006 name=/u01/app/oracle/oradata/stand/users01.dbf

skipping datafile 00006 because it has not changed

channel ORA_DISK_1: backup cancelled because all files were skipped

channel ORA_DISK_1: starting incremental level 1 datafile backup set

channel ORA_DISK_1: specifying datafile(s) in backup set

including current control file in backup set

including current SPFILE in backup set

channel ORA_DISK_1: starting piece 1 at 17-SEP-20

channel ORA_DISK_1: finished piece 1 at 17-SEP-20

piece handle=/u01/app/oracle/fast_recovery_area/STAND/backupset/2020_09_17/o1_mf_ncsn1_TAG20200917T204949_hp6znpyt_.bkp tag=TAG20200917T204949 comment=NONE

channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01

Finished backup at 17-SEP-20

 

Note that in order to take a level 1 backup, a level 0 backup must already exist.

A full backup using BACKUP DATABASE is not the same as a level 0 backup. - the LV column of the LIST BACKUP output is NULL after a full backup.

 

 level 0 backup

 

RMAN> BACKUP INCREMENTAL LEVEL 0 DATABASE;

 

Starting backup at 17-SEP-20

using channel ORA_DISK_1

channel ORA_DISK_1: starting incremental level 0 datafile backup set

channel ORA_DISK_1: specifying datafile(s) in backup set

input datafile file number=00001 name=/u01/app/oracle/oradata/stand/system01.dbf

input datafile file number=00003 name=/u01/app/oracle/oradata/stand/sysaux01.dbf

input datafile file number=00004 name=/u01/app/oracle/oradata/stand/undotbs01.dbf

input datafile file number=00006 name=/u01/app/oracle/oradata/stand/users01.dbf

channel ORA_DISK_1: starting piece 1 at 17-SEP-20

channel ORA_DISK_1: finished piece 1 at 17-SEP-20

piece handle=/u01/app/oracle/fast_recovery_area/STAND/backupset/2020_09_17/o1_mf_nnnd0_TAG20200917T205106_hp6zq2vb_.bkp tag=TAG20200917T205106 comment=NONE

channel ORA_DISK_1: backup set complete, elapsed time: 00:00:55

channel ORA_DISK_1: starting incremental level 0 datafile backup set

channel ORA_DISK_1: specifying datafile(s) in backup set

including current control file in backup set

including current SPFILE in backup set

channel ORA_DISK_1: starting piece 1 at 17-SEP-20

channel ORA_DISK_1: finished piece 1 at 17-SEP-20

piece handle=/u01/app/oracle/fast_recovery_area/STAND/backupset/2020_09_17/o1_mf_ncsn0_TAG20200917T205106_hp6zrv2p_.bkp tag=TAG20200917T205106 comment=NONE

channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01

Finished backup at 17-SEP-20

 

 

 

 

Managing Tablespaces And Datafiles

 

Managing Tablespaces And Datafiles

You can create Locally Managed or Dictionary Managed Tablespaces. In prior versions of Oracle only Dictionary managed Tablespaces were available but from Oracle ver. 8i you can also create Locally Managed tablespaces.

To create a locally managed tablespace

SQL> create tablespace  Ranesh2 datafile '/u01/app/oracle/oradata/stand/ranesh2.dbf' size 50m extent management dictionary local autoallocate;

AUTOALLOCATE causes the tablespace to be system managed with a minimum extent size of 64K, You can specify that size in the SIZE clause of UNIFORM. If you omit SIZE, then the default size is 1M

To Create Dictionary Managed Tablespace

SQL> create tablespace  Ranesh2 datafile '/u01/app/oracle/oradata/stand/ranesh2.dbf' size 50m extent management dictionary;

Bigfile Tablespaces(10g)

A bigfile tablespace is a tablespace with a single, but very large (up to 4G blocks) datafile

To create a bigfile tablespace

SQL> create bigfile tablespace  Ranesh3 datafile '/u01/app/oracle/oradata/stand/ranesh3.dbf' size 50g:

 

To Extend the Size of a tablespace

Option 1

You can extend the size of a tablespace by increasing the size of an existing datafile

SQL> alter  database Ranesh2 datafile '/u01/app/oracle/oradata/stand/ranesh2.dbf' resize 100m;

Option 2

You can also extend the size of a tablespace by adding a new datafile to a tablespace

SQL> alter tablespace add datafile '/u01/app/oracle/oradata/stand/ranesh3.dbf' size 50m;

 

Option 3

SQL> alter database datafile '/u01/app/oracle/oradata/stand/ranesh3.dbf' auto extend ON next 5M maxsize 500M;

To decrease the size of a tablespace

SQL> alter  database Ranesh2 datafile '/u01/app/oracle/oradata/stand/ranesh2.dbf' resize 30m;

 

Taking tablespaces Offline or Online

To Take a Tablespace Offline

SQL>alter tablespace ranesh offline;

To again bring it back online .

SQL>alter tablespace ranesh online;

To take individual datafile offline type the following command

SQL>alter database datafile ‘/u01/app/oracle/oradata/stand/ranesh2.dbf’ offline;

Again to bring it back online give the following command

SQL> alter database datafile ‘/u01/app/oracle/oradata/stand/ranesh2.dbf’ online;

Note: You can’t take individual datafiles offline it the database is running in NOARCHIVELOG mode.  If the datafile has become corrupt or missing when the database is running in NOARCHIVELOG mode then you can only drop it by giving the following command

SQL>alter database datafile ‘‘/u01/app/oracle/oradata/stand/ranesh2.dbf’ offline for drop;

Making a tablespace read-only

Making a tablespace read-only prevents updates on all tables in the tablespace, regardless of a user's update privilege level.

To make a tablespace read only

SQL>alter tablespace ranesh read only;

Again to make it read write

sql> alter tablespace ranesh read write;

 

Renaming Tablespaces

alter tablespace users ranesh TO ranesh3;

Dropping Tablespaces

You can drop a tablespace and its contents (the segments contained in the tablespace) from the database if the tablespace and its contents are no longer required. You must have the DROP TABLESPACE system privilege to drop a tablespace.

To drop a tablespace give

SQL> drop tablespace ica;

This will drop the tablespace only if it is empty. If it is not empty and if you want to drop it

SQL>drop tablespace ica including contents;

This will drop the tablespace even if it is not empty. But the datafiles will not be deleted you have to use operating system command to delete the files.

But If  you include datafiles keyword then, the associated datafiles will also be deleted from the disk.

SQL>drop tablespace ica including contents and datafiles;

 Viewing Information about Tablespaces and Datafiles

Oracle has provided many Data dictionaries to view information about tablespaces and datafiles.  Some of them are:

To view information about Tablespaces in a database give the following query

SQL> select * from dba_tablespaces
SQL> select * from v$tablespace;

To view information about Datafiles

SQL> select * from dba_data_files;
SQL> select * from v$datafile;

To view information about Tempfiles

SQL> select * from dba_temp_files;
SQL> select * from v$tempfile;

To view information about free space in datafiles

SQL> select * from dba_free_space;

To view information about free space in tempfiles

SQL> select * from V$TEMP_SPACE_HEADER;

 

Renaming or Relocating Datafiles belonging to a Single Tablespace

1.       Take the tablespace offline

2.       Rename or Relocate the datafiles using operating system command

3.       Give the ALTER TABLESPACE with RENAME DATAFILE option to change the filenames within the Database.

4.       Bring the tablespace Online

 

 

 

 

12.2 Patching

 

From R12.2 onwards oracle has introduced online patching functionality.

Online Patching
Online patching uses the latest feature of the Oracle database 11gR2 which is called “Edition Based 
Redefinition” and also uses multiple file systems on the application side. During online patching, business application users continue using the Oracle application and simultaneously a patch or a sequence of patches can be applied to another edition of the same database and application. Another edition here means another exact copy of database and application. And once the patching is complete the users are switched over to a patched file system/database in cutover phase by just bouncing middle tier services.

File System
A R12.2.0 is installed with three file Systems.

1.FS1 – Production file system that is used by application users when system is being patched.

2.FS2 – Exact copy of production used by the patching tool. This copy is patched by the patching tool. It gets synchronized with FS1 by the patching tool before it gets updated by a patch. When patching is complete, the patching tool swaps the FS1 and FS2 file systems. FS2 file system becomes FS1 and FS1 is switched to FS2. This way, FS2 is again ready to be used for any future patching tasks.

3.FS-NE – This is a non-edition file system which stores data that is stored in a file system like data import/export files, report out and log files.

 

 

 

 

 

 

 

 

 

Phases of ADOP(online patching)

ADPATCH utility is no longer used in R12.2.0 and is being replaced by ADOP – AD Online Patching. There are five phases or life cycles of ADOP which are:

 

a) PREPARE

b) APPLY

c) FINALIZE

d) CUTOVER

e) CLEANUP

 

 

Steps:-

1.                 Download the patch and unzip on patch_top and go through the read me to check,what its going to do.

 

A) Prepare phase

      Prepare the system for patching

a.     Run environment file(optional)

Note: The adop utility sets its own environment. There is therefore no need to source the environment before running it.

     b.   adop phase=prepare

 

B) Apply Phase -

adop phase=apply patches=, workers=<number_of_worker>

After patch has been successfully applied, complete the patch cycle

 

 C) Finalize phase - Used to perform the final patching operations that can be executed while the application is still online:

 

adop phase=finalize workers= (called automatically)

 

D) Cutover phase - Used to perform the transition to the patched environment:

adop phase=cutover  workers=<number_of_worker>

 

E) Cleanup phase - Used to remove old objects that are no longer needed:

adop phase=cleanup (called automatically)

 

 

-------------------------------------------------------------------------------------------

 

Now synchronise the technology level between patch and run fc_clone.

  adop phase=fs_clone

 

 

 

Abort phase - Used only if the online patching cycle needs to be terminated before completion:

 

$ adop phase=abort

 

 

 

Important: The abort phase can only be run after the prepare phase and before completion of the cutover phase. After the cutover phase completes, it is no longer possible to abort the online patching cycle.

 

Last two commands for adop

a. adop -help

b. adop -examples

 

 

 

Patch Log Files:-

To review the relevant log files after any patching operation. The adop log files are located on the non-editioned file system (fs_ne), under:

 

$NE_BASE/EBSapps/log/adop//__//log

 

 

Phases:

1.adop phase= prepare --------copies the application code

2.adop phase =apply-------apply patches to patch environment

3.adop phase=finalize-------makes ready the system for cutover

4.adop phase=cutover--------bounce the system and does filesystem switchover fs2 to become Run environment

5.adop phase=cleanup------remove obsolete objects

6.adop phase=fs_clone-----syschronize file systems