Home » RDBMS Server » Backup & Recovery » Filesperset behaviour (Oracle 10.2.03, Solaris 10)
Filesperset behaviour [message #510568] Mon, 06 June 2011 08:23 Go to next message
valmar
Messages: 10
Registered: May 2011
Junior Member
Hello,
I have a policy running every night that has to backup some read write and partitioned datafile of production db.
Setting filesperset 20 I noticed that rman puts
one and only one datafile in each backup set.
The MAXSETSIZE parameter is set to unlimited.
Could please someone of you clarify me this behaviour ?

Thanks in advance and best regards
Valeria
Re: Filesperset behaviour [message #510569 is a reply to message #510568] Mon, 06 June 2011 08:33 Go to previous messageGo to next message
Michel Cadot
Messages: 59298
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
Post the whole command and configuration.
Do not explain, SHOW us.

Regards
Michel
Re: Filesperset behaviour [message #510571 is a reply to message #510569] Mon, 06 June 2011 08:46 Go to previous messageGo to next message
valmar
Messages: 10
Registered: May 2011
Junior Member
Hello,
sorry, here you are the rman command

RUN {
   ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE'; 
   ALLOCATE CHANNEL ch01 TYPE 'SBT_TAPE'; 
   BACKUP
   TAG ST_READWRITE_20110606 
   FILESPERSET 20 
   INCREMENTAL LEVEL=1
   # recommended format
   FORMAT 'bk_%s_%p_%t' 
   datafile 
     <list of quite 1000 datafiles>;
   CROSSCHECK BACKUPSET;
   CROSSCHECK ARCHIVELOG ALL;
   DELETE NOPROMPT EXPIRED BACKUP;
   DELETE NOPROMPT OBSOLETE;
   RELEASE CHANNEL ch00;
   RELEASE CHANNEL ch01;
}


Here you are the result printout:

allocated channel: ch00
channel ch00: sid=482 devtype=SBT_TAPE
channel ch00: VERITAS NetBackup for Oracle - Release 6.0 (2006110304)

allocated channel: ch01
channel ch01: sid=487 devtype=SBT_TAPE
channel ch01: VERITAS NetBackup for Oracle - Release 6.0 (2006110304)

Starting backup at 06-JUN-11
channel ch00: starting incremental level 1 datafile backupset
channel ch00: specifying datafile(s) in backupset
input datafile fno=00135 name=/<path_name>/datafile1.dbf
channel ch00: starting piece 1 at 06-JUN-11
channel ch01: starting incremental level 1 datafile backupset
channel ch01: specifying datafile(s) in backupset
input datafile fno=00145 name=/<path_name>/datafile2.dbf
channel ch01: starting piece 1 at 06-JUN-11
....


Waiting for your feedback
br / Valeria
Re: Filesperset behaviour [message #510572 is a reply to message #510571] Mon, 06 June 2011 10:02 Go to previous messageGo to next message
Mahesh Rajendran
Messages: 10628
Registered: March 2002
Location: oracleDocoVille
Senior Member
Account Moderator
Quoting docs.

Quote:
FILESPERSET = integer

Specifies the maximum number of input files in each backup set. If you set FILESPERSET = n, then RMAN never includes more than n files in a backup set

[Updated on: Mon, 06 June 2011 10:02]

Report message to a moderator

Re: Filesperset behaviour [message #510573 is a reply to message #510571] Mon, 06 June 2011 10:35 Go to previous messageGo to next message
Michel Cadot
Messages: 59298
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
Post "show all;"

What are the parameters given at NetBackup side?

Regards
Michel
Re: Filesperset behaviour [message #510653 is a reply to message #510573] Tue, 07 June 2011 02:31 Go to previous messageGo to next message
valmar
Messages: 10
Registered: May 2011
Junior Member
Hello,
here you are the rman show all:

RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 1 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO '%F'; # defa
ult
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 1 BACKUP TYPE TO BACKUPSET;
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS  'ENV=(NBU_SERV=xx.xx.xx.xx)';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/global/home9/dbown/product/10.2.0/Db_2/dbs/snapcf_target.f'; 
# default

About netbackup parameters, colud you please tell me the command to list them ?
Thank you for your help
BR / Valeria

[Updated on: Tue, 07 June 2011 02:47] by Moderator

Report message to a moderator

Re: Filesperset behaviour [message #510682 is a reply to message #510572] Tue, 07 June 2011 04:36 Go to previous messageGo to next message
valmar
Messages: 10
Registered: May 2011
Junior Member
So, if FILESPERSET can't assure that RMAN put more that one
datafile in a backupset witch parameter should I set to have
backupset containing more datafiles ?
Any help is appreciated
BR / Valeria
Re: Filesperset behaviour [message #510736 is a reply to message #510682] Tue, 07 June 2011 07:38 Go to previous messageGo to next message
kapardi
Messages: 19
Registered: May 2011
Location: Pune
Junior Member

hello valmar

[Edit MC: Metalink note removed, DO NOT post copyrighted document]



[Updated on: Tue, 07 June 2011 08:14] by Moderator

Report message to a moderator

Re: Filesperset behaviour [message #510740 is a reply to message #510736] Tue, 07 June 2011 07:41 Go to previous messageGo to next message
kapardi
Messages: 19
Registered: May 2011
Location: Pune
Junior Member

hello valmar

according to me i think we can alter the FILESPERSET command set it to your no of datafiles that you want so that i think this issue will be resolved

Thanks and Regards
Kapardi
Re: Filesperset behaviour [message #510919 is a reply to message #510740] Wed, 08 June 2011 06:12 Go to previous messageGo to next message
valmar
Messages: 10
Registered: May 2011
Junior Member
Hello,
I found the parameter DISKRATIO that helped with the issue I posted.
By disabling it (DISKRATIO=0) it seems that more datafile (up to FILESPERSET value)
are grouped in a single backup set.
Any comment ?
Thanks again for your help
BR / Valeria
Re: Filesperset behaviour [message #510925 is a reply to message #510919] Wed, 08 June 2011 06:28 Go to previous messageGo to next message
Michel Cadot
Messages: 59298
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
For doc:

Quote:
Directs RMAN to populate each backup set with datafiles from at least integer disks. This parameter is only enabled when you are backing up datafiles or control files, and when the operating system can give RMAN disk contention and node affinity information. To manually disable this feature, set DISKRATIO = 0.
For example, assume that datafiles are distributed across 10 disks. If the disks supply data at 10 bytes/second, and if the tape drive requires 50 bytes/second to keep streaming, then set DISKRATIO = 5 to direct RMAN to include datafiles from at least 5 disks in each backup set.

If you set FILESPERSET but not DISKRATIO, then DISKRATIO defaults to the same value as FILESPERSET. If you specify neither parameter, then DISKRATIO defaults to 4. RMAN compares the DISKRATIO value to the actual number of devices involved in the backup and uses the lowest value. For example, if DISKRATIO is 4 and the datafiles are located on three disks, then RMAN attempts to include datafiles from three disks in each backup set.

The DISKRATIO parameter is easier for datafile backups when the datafiles are striped or reside on separate disk spindles and you either:

Use a high-bandwidth tape drive that requires several datafiles to be multiplexed in order to keep the tape drive streaming

Make backups while the database is open and you need to spread the I/O load across several disk spindles to leave bandwidth for online operations .

Note: Do not spread I/O over more than the minimum number of disks required to keep the tape streaming. Otherwise, you increase restore time for a file without increasing performance.


Regards
Michel
Re: Filesperset behaviour [message #510961 is a reply to message #510919] Wed, 08 June 2011 11:37 Go to previous message
Mahesh Rajendran
Messages: 10628
Registered: March 2002
Location: oracleDocoVille
Senior Member
Account Moderator
Try backup as backupset.
You can use
backup as backupset datafile 1,2,n

or
backup as backupset tablespace this,that,thisandthat;


RMAN>  run { allocate channel ch1 type disk format '/backup10g/test/rman_%d_%t_bpiece.bak';
2>  backup as backupset datafile 1,2,3,4;
3> }

allocated channel: ch1
channel ch1: sid=74 devtype=DISK

Starting backup at 08-JUN-11
channel ch1: starting full datafile backupset
channel ch1: specifying datafile(s) in backupset
input datafile fno=00001 name=+FRA/chub/datafile/system.272.753276903
input datafile fno=00002 name=+FRA/chub/datafile/undotbs1.271.753276919
input datafile fno=00003 name=+FRA/chub/datafile/sysaux.270.753276921
input datafile fno=00004 name=+FRA/chub/datafile/users.264.753276931
channel ch1: starting piece 1 at 08-JUN-11
channel ch1: finished piece 1 at 08-JUN-11
piece handle=/backup10g/test/rman_CHUB_753280345_bpiece.bak tag=TAG20110608T123224 comment=NONE
channel ch1: backup set complete, elapsed time: 00:00:07
channel ch1: starting full datafile backupset
channel ch1: specifying datafile(s) in backupset
including current control file in backupset
including current SPFILE in backupset
channel ch1: starting piece 1 at 08-JUN-11
channel ch1: finished piece 1 at 08-JUN-11
piece handle=/backup10g/test/rman_CHUB_753280352_bpiece.bak tag=TAG20110608T123224 comment=NONE
channel ch1: backup set complete, elapsed time: 00:00:03
Finished backup at 08-JUN-11
released channel: ch1

RMAN> exit


Recovery Manager complete.
oracle@eddie#ls -lart /backup10g/test
total 551608
drwxr-xr-x  16 oracle   root        4096 Jun  8 12:01 ..
-rw-r-----   1 oracle   dba      274710528 Jun  8 12:32 rman_CHUB_753280345_bpiece.bak
drwxr-xr-x   2 oracle   dba         4096 Jun  8 12:32 .
-rw-r-----   1 oracle   dba      7143424 Jun  8 12:32 rman_CHUB_753280352_bpiece.bak




RMAN> run { allocate channel ch1 type disk format '/backup10g/test/rman_%d_%t_bpiece.bak';
2> backup as backupset tablespace system,sysaux,users;
3> }

using target database control file instead of recovery catalog
allocated channel: ch1
channel ch1: sid=75 devtype=DISK

Starting backup at 08-JUN-11
channel ch1: starting full datafile backupset
channel ch1: specifying datafile(s) in backupset
input datafile fno=00001 name=+FRA/chub/datafile/system.272.753276903
input datafile fno=00003 name=+FRA/chub/datafile/sysaux.270.753276921
input datafile fno=00004 name=+FRA/chub/datafile/users.264.753276931
channel ch1: starting piece 1 at 08-JUN-11
channel ch1: finished piece 1 at 08-JUN-11
piece handle=/backup10g/test/rman_CHUB_753280529_bpiece.bak tag=TAG20110608T123529 comment=NONE
channel ch1: backup set complete, elapsed time: 00:00:07
channel ch1: starting full datafile backupset
channel ch1: specifying datafile(s) in backupset
including current control file in backupset
including current SPFILE in backupset
channel ch1: starting piece 1 at 08-JUN-11
channel ch1: finished piece 1 at 08-JUN-11
piece handle=/backup10g/test/rman_CHUB_753280537_bpiece.bak tag=TAG20110608T123529 comment=NONE
channel ch1: backup set complete, elapsed time: 00:00:04
Finished backup at 08-JUN-11
released channel: ch1

[Updated on: Wed, 08 June 2011 11:38]

Report message to a moderator

Previous Topic: rman backup doesn't become obsolete
Next Topic: Backup
Goto Forum:
  


Current Time: Thu Oct 02 10:37:15 CDT 2014

Total time taken to generate the page: 0.08413 seconds