Setting the retention Policy to recovery window.
We are using Netbackup as a our third party tool for corporate backups and have used brbackup with backint on Windows for many years with great success.We would like to incorporate RMAN incremental backups for our backup strategy. Currently our retention policies through netbackup are:
Backup Retention
Daily Online 2 weeks.
Weekly Online 4 weeks.
Monthly Online 12 months.
Redologs 4 weeks.
We would like to continue to retain the monthly backup. Other than setting the retention policy window to 365, how could we do this???? We would like to avoid growing a huge control file.
Regards
Scott
Hello Scott,
> We would like to avoid growing a huge control file.
Ok nice approach, but the (RMAN) data in the control file is reused after the value of the init parameter CONTROL_FILE_RECORD_KEEP_TIME. (has nothing todo with the retention policy)
http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/initparams029.htm#CHDDBCDB
> Other than setting the retention policy window to 365, how could we do this????
You can use the KEEP clause with the command BACKUP or CHANGE.
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta035.htm#i97063
Regards
Stefan
Similar Messages
-
Not set configure retention policy to recovery window of 7 days
HI all,
if parameter "" configure retention policy to recovery window of 7 days "" is not set
then i am taking weekly and inreamental cumulative backup any effect of backup
i think in this case delete obsolete is not working.
currently parameter set is CONFIGURE RETENTION POLICY TO REDUNDANCY 1;HI all,
if parameter "" configure retention policy to recovery window of 7 days "" is not set
then i am taking weekly and inreamental cumulative backup any effect of backup
i think in this case delete obsolete is not working.
currently parameter set is CONFIGURE RETENTION POLICY TO REDUNDANCY 1; -
Rman Retention policy to recovery window
Hi,
I have few basic doubts in RMAN backup policy
1 . Is that possible to set Retention policy to recovery window in minutes??
2 . If i set Backup Retention Policy to recovery window to 3 days and i am performing RMAN differential incremental backup for 4 days. Will my backups become obsolete after 3 days even though they are needed for recovery or they won't become obsolete since they are needed for recovery ???
Regards,
0071) Syntax is .... TO RECOVERY WINDOW OF integer DAYS ... no other time statement.
2) Backups become obsolete when no longer needed to fulfil a retention policy. In a (theoretical) scenario, you perform a level 0 backup and then only incremental backups, the starting level 0 backup must be kept for ever (even if it WOULD be possible to define a recovery window in minutes).
Werner -
Backup with retention policy to recovery window of N days
Hello,
I've issued command to create database incremental backup with configuration:
run
configure retention policy to recovery window of 14 days;
backup incremental level 1 cumulative
tag daily_incr_14_days
database
plus archivelog delete all input;
All parameters are set to their default values and database backups goes to FRA. I've got recovery catalog connected and all RC_ views at my disposal.
1) Is there any way to find out, what recovery window was used for backup from any command in rman or query from RC_ views or local database views (information from control file)?
2) If I use other recovery window setting with configure command what would rman crosscheck or report commands do?
BR
Patrycjusz.TenakaKhan wrote:
Mahir,
thanks for answer - this means that recovery window should be used mainly for maintenance purposes (crosscheck, delete obsolete, report need backup etc.) and it's not related to actual retention period with backup pieces like 'keep until' clause for backup ... database command (this information are saved with backup as I could check in rc_backup_set view from recovery catalog)?
Yes it is.
Maintaining RMAN Backups and Repository Records
keepOption
backup retention policy
A user-defined policy for determining how long backups and archived logs must be retained for media recovery. You can define a retention policy in terms of backup redundancy or a recovery window.
RMAN retains the data file backups required to satisfy the current retention policy, and any archived redo logs required for complete recovery of those data file backups.
recovery window
A recovery window is one type of RMAN backup retention policy, in which the DBA specifies a period of time and RMAN ensures retention of backups and archived redo logs required for point-in-time recovery to any time during the recovery window.
The interval always ends with the current time and extends back in time for the number of days specified by the user. For example, if the retention policy is set for a recovery window of seven days, and the current time is 11:00 AM on Tuesday,
RMAN retains the backups required to allow point-in-time recovery back to 11:00 AM on the previous Tuesday.
Regards
Mahir M. Quluzade -
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 0 DAYS;
Hi Guys
Can you please put some light on the 0 days. what is the meaning on 0 days and how does this work.
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 0 DAYS; If I take full backup every night how many backup will it contain and how will it obsolete the backup.
RMan 9i R2
Soalris 5.9
I understand the concept if recover window is 1 or more days but confuse with 0 days.
Thank you in advance.RECOVERY WINDOW OF 0 DAYS is effective like REDUNDANCY 1.
RMAN> configure retention policy to recovery window of 0 days;
old RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
new RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 0 DAYS;
new RMAN configuration parameters are successfully stored
RMAN> backup datafile 4;
Starting backup at 09-SEP-07
using target database controlfile instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=15 devtype=DISK
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00004 name=E:\ORACLE\ORADATA\WIN9I\DRSYS01.DBF
channel ORA_DISK_1: starting piece 1 at 09-SEP-07
channel ORA_DISK_1: finished piece 1 at 09-SEP-07
piece handle=E:\ORACLE\ORA92\DATABASE\0BIRHB2F_1_1 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
Finished backup at 09-SEP-07
RMAN> report obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 0 days
no obsolete backups found
RMAN> backup datafile 4;
Starting backup at 09-SEP-07
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00004 name=E:\ORACLE\ORADATA\WIN9I\DRSYS01.DBF
channel ORA_DISK_1: starting piece 1 at 09-SEP-07
channel ORA_DISK_1: finished piece 1 at 09-SEP-07
piece handle=E:\ORACLE\ORA92\DATABASE\0CIRHB4Q_1_1 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
Finished backup at 09-SEP-07
RMAN> report obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 0 days
Report of obsolete backups and copies
Type Key Completion Time Filename/Handle
Backup Set 10 09-SEP-07
Backup Piece 10 09-SEP-07 E:\ORACLE\ORA92\DATABASE\0BIRHB2F_1_1
RMAN> delete backup;
using channel ORA_DISK_1
List of Backup Pieces
BP Key BS Key Pc# Cp# Status Device Type Piece Name
10 10 1 1 AVAILABLE DISK E:\ORACLE\ORA92\DATABASE\0BIRHB2F_1_1
11 11 1 1 AVAILABLE DISK E:\ORACLE\ORA92\DATABASE\0CIRHB4Q_1_1
Do you really want to delete the above objects (enter YES or NO)? yes
deleted backup piece
backup piece handle=E:\ORACLE\ORA92\DATABASE\0BIRHB2F_1_1 recid=10 stamp=632859727
deleted backup piece
backup piece handle=E:\ORACLE\ORA92\DATABASE\0CIRHB4Q_1_1 recid=11 stamp=632859802
Deleted 2 objects
RMAN> configure retention policy to redundancy 1;
old RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 0 DAYS;
new RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
new RMAN configuration parameters are successfully stored
RMAN> backup datafile 4;
Starting backup at 09-SEP-07
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00004 name=E:\ORACLE\ORADATA\WIN9I\DRSYS01.DBF
channel ORA_DISK_1: starting piece 1 at 09-SEP-07
channel ORA_DISK_1: finished piece 1 at 09-SEP-07
piece handle=E:\ORACLE\ORA92\DATABASE\0DIRHB90_1_1 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
Finished backup at 09-SEP-07
RMAN> report obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
no obsolete backups found
RMAN> backup datafile 4;
Starting backup at 09-SEP-07
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00004 name=E:\ORACLE\ORADATA\WIN9I\DRSYS01.DBF
channel ORA_DISK_1: starting piece 1 at 09-SEP-07
channel ORA_DISK_1: finished piece 1 at 09-SEP-07
piece handle=E:\ORACLE\ORA92\DATABASE\0EIRHB9H_1_1 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
Finished backup at 09-SEP-07
RMAN> report obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
Report of obsolete backups and copies
Type Key Completion Time Filename/Handle
Backup Set 12 09-SEP-07
Backup Piece 12 09-SEP-07 E:\ORACLE\ORA92\DATABASE\0DIRHB90_1_1
RMAN> -
Retention policy to recovery window of 31 days means
HI all,
according to our company policy we need to restore database from last 7year.
backup happen on SBT TAPE.. we freez that tape for next 7 year.
my doubt is we are taking backup using recovery catalog...daily basis we are taking backup using recovery catalog...but i have one doubt while configuring we have configure retention policy of recovery window 31 days..
i m very much confused about this policy ..if we use this policy then can we able to recover database before 7 year or not..
becacuse we are not firing any delete obsulate backup command on recovery catalog.
we are only deleting archivelog by using delete nopromt archive log sysdate-3..
so please suggest does it possible if renrtion policy to recovery window 31 days...i can able to restore this database before 31 days.
Thanks,Hi there user12009184
If you do not delete old backups through your rman script, then old backups will have to be deleted through your tape backup software. Unless you have endlessly large tapes ;-)
So, yes you could theoretically restore from backups older than your retention window of 31 days.
You should ensure that your control_file_record_keep_time is set to a value of 31 or larger (set it to your retention window period plus 1). Otherwise your control files will now know about your older backups.
If you want to restore a very old backup, than you will need to restore a spfile and a control file first, then restore, then recover your database.
You really, really need to test this. So that you know exactly how to do it and you have it documented.
hope this helped,
Andrew -
Basic question on setting Redundancy as the Retention policy
DB version:11g
I am planning to implement Differential Incremental Backup for my database. My strategy is
Sunday --> Level 0 backup
Monday --> Level 1 backup
Tuesday--> Level 1 backup
Wednesday--> Level 1 backup
Thursday--> Level 1 backup
Friday--> Level 1 backup
Saturday--> Level 1 backup
Again, the new weekly backup cycle starts
Sunday --> Level 0 backup
Monday --> Level 1 backup
.Retention Policy set to Recovery Window
==========================
I understand What Recovery window retention policy means.If i configure
'CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;' This means only those backups which are older than 7 days will be reported as obsolete when the 'delete obsolete' command is executed.
Retention Policy set to Redundancy
=============================
But i am a bit confused about Retention Policy set to Redundancy:
Does
CONFIGURE RETENTION POLICY TO REDUNDANCY 3;mean that you maintain 3 copies of backups on different disk locations ? How does this fit in with my above mentioned incremental backup strategy?Thank you Centinul.
If REDUNDANY simply means maintain N number of copies of datafiles then what does
BACKUP DEVICE TYPE DISK COPIES 3 DATAFILE 7 FORMAT '/u02/orabkp/%U','/u01/oradata/%U';command do?Are they both the same? -
Control_file_record_time -retention policy to recover window
Hi:
If i have control_file_record_time=7 and retention policy to recover window=3 can i still go back and recover upto the last 5th day provided the backups are available.If i have run delete obsolete at the end of 5th day it will delete obsolete backups from the disk but i have the copies stored on some othere disks ...how does rman deal with obsolete but control file still having backup information.
Are they related in anyway or just the obsolete command is for DBA convinence to delete the obsolete backups and does not play a factor during recovery
Thanks,
GaneshHi there user12009184
If you do not delete old backups through your rman script, then old backups will have to be deleted through your tape backup software. Unless you have endlessly large tapes ;-)
So, yes you could theoretically restore from backups older than your retention window of 31 days.
You should ensure that your control_file_record_keep_time is set to a value of 31 or larger (set it to your retention window period plus 1). Otherwise your control files will now know about your older backups.
If you want to restore a very old backup, than you will need to restore a spfile and a control file first, then restore, then recover your database.
You really, really need to test this. So that you know exactly how to do it and you have it documented.
hope this helped,
Andrew -
How do I set the delivery policy for a queue in iMQ 2.0?
The list on page 67 of the 2.0 administration guide appears to be
incomplete. Specifically, I'm interested in knowing how to set
the default delivery policy for a Queue through the jmqobjmgr command.
I need the valid attribute name to pass in to jmqobjmgr.The "queueDeliveryPolicy" is an attribute of a queue
created in the broker - not in the administered object
destination so that is why you are not seeing that
attribute on the list on page 67.
By default, the broker by will use the "single" queue delivery
policy unless you choose to change the values of the property
"jmq.queue.defaultdeliveryPolicy" to SINGLE, ROUND-ROBIN, or
FAILOVER. If you would like to do this, see the Chapter 4
in the admin guide on "Starting and Configuring the Broker".
It may be easier to set the delivery policy for just one queue.
To do this, you can use the following command:
jmqcmd create dst -n myQueue -t q -o "queueDeliveryPolicy=f"
where valid values to queueDeliveryPolicy is f, s, r.
You can do a 'jmqcmd -H' to get more info on queue attributes or
see Chapter 6 in the admin guide on "Creating and Destroying Destinations". -
How to set the title of an urxvt window?
Hello,
I have read the manpage and FAQ on the urxvt website, but my problem persists:
When I try to set the title of an urxvt window, for example:
$ urxvt -title test
then the new window shows for a second the title "test" and then switches to "username@hostname:~".
Yes, I have
case $TERM in
xterm*|*rxvt*|Eterm|eterm|rxvt-unicode|urxvt)
PROMPT_COMMAND='echo -ne "\033]0;${USER}@${HOSTNAME%%.*}:${PWD/$HOME/~}\007"'
screen)
PROMPT_COMMAND='echo -ne "\033_${USER}@${HOSTNAME%%.*}:${PWD/$HOME/~}\033\\"'
esac
in my .bashrc.
But I think, the explicit command line option "-title" should break the .bashrc, right?
The default setting by .bashrc is intentional, but in this specific case I would like to set the window title by hand.
How can I do that?
Last edited by indianahorst (2011-06-22 11:01:34)I would recommend that you not use the PROMPT_COMMAND to set your bash prompt at all. Use the PS1 environment variable. By using PROMPT_COMMAND, you are invoking a subshell each time you hit return; which is most likely unnecessary.
In fact, you are probably already setting PS1 in your .bashrc; and that is what is changing your window title. You can set PS1 to a different value, and then it will not reset your window title with each command.
Just set PS1 in your .bashrc to:
PS1="[\u@\h \W]\$ "
You can see a more complete list of the available \u, \H, etc. options here.
If you do wish to reset the urxvt window title by setting PS1, do the following:
PS1="[\u@\h \W]\$ "
PS1="\[\e]2;\u \W\a\]$PS1"
Edit: As I look at this a little closer, I see that your PROMPT_COMMAND is indeed setting your window title. You could change it to the following:
PROMPT_COMMAND='echo -ne "${USER}@${HOSTNAME%%.*}:${PWD/$HOME/~}"'
But I would still not use PROMPT_COMMAND and just set PS1 instead.
Last edited by rockin turtle (2011-06-23 03:53:57) -
Can i use the retention policy without using the Flash Recovery area?
Yes ,lets see here
RMAN>list backup summary
C:\>dir *.bus
Volume in drive C is khurram
Volume Serial Number is F49D-FF2B
Directory of C:\
File Not Found
C:\>dir *.arc
Volume in drive C is khurram
Volume Serial Number is F49D-FF2B
Directory of C:\
File Not Found
RMAN> crosscheck backup
2> ;
using channel ORA_DISK_1
RMAN> list backup summary
2> ;
RMAN> show retention policy
2> ;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
RMAN> run {
2> allocate channel ch0 type disk;
3> backup as compressed backupset database format
4> 'c:\rman_%s_%d_%T.bus'
5> plus archivelog format 'c:\arch_%s_%d_%T.arc';
6> release channel ch0;
7> allocate channel ch1 device type disk format 'c:\arch_%s_%d_%T.arc';
8> release channel ch1;
9> delete force noprompt obsolete;
10> allocate channel ch2 device type disk format 'c:\rman_%s_%d_%T.bus';
11> release channel ch2;
12> delete force noprompt obsolete;
13> }
released channel: ORA_DISK_1
allocated channel: ch0
channel ch0: sid=146 devtype=DISK
Starting backup at 15-APR-08
current log archived
channel ch0: starting compressed archive log backupset
channel ch0: specifying archive log(s) in backup set
input archive log thread=1 sequence=24 recid=79 stamp=652108461
input archive log thread=1 sequence=25 recid=80 stamp=652112650
channel ch0: starting piece 1 at 15-APR-08
channel ch0: finished piece 1 at 15-APR-08
piece handle=C:\ARCH_130_ORCL1_20080415.ARC comment=NONE
channel ch0: backup set complete, elapsed time: 00:00:05
Finished backup at 15-APR-08
Starting backup at 15-APR-08
channel ch0: starting compressed full datafile backupset
channel ch0: specifying datafile(s) in backupset
input datafile fno=00001 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL1\SYSTEM01.DB
F
input datafile fno=00003 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL1\SYSAUX01.DB
F
input datafile fno=00004 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL1\USERS01.DBF
input datafile fno=00002 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL1\UNDOTBS01.D
BF
channel ch0: starting piece 1 at 15-APR-08
channel ch0: finished piece 1 at 15-APR-08
piece handle=C:\RMAN_131_ORCL1_20080415.BUS comment=NONE
channel ch0: backup set complete, elapsed time: 00:00:45
Finished backup at 15-APR-08
Starting backup at 15-APR-08
current log archived
channel ch0: starting compressed archive log backupset
channel ch0: specifying archive log(s) in backup set
input archive log thread=1 sequence=26 recid=81 stamp=652112703
channel ch0: starting piece 1 at 15-APR-08
channel ch0: finished piece 1 at 15-APR-08
piece handle=C:\ARCH_132_ORCL1_20080415.ARC comment=NONE
channel ch0: backup set complete, elapsed time: 00:00:02
Finished backup at 15-APR-08
Starting Control File and SPFILE Autobackup at 15-APR-08
piece handle=C:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ORCL1\AUTOBACKUP\2008_
04_15\O1_MF_S_652112718_408X3ZVJ_.BKP comment=NONE
Finished Control File and SPFILE Autobackup at 15-APR-08
released channel: ch0
allocated channel: ch1
channel ch1: sid=146 devtype=DISK
released channel: ch1
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=146 devtype=DISK
Deleting the following obsolete backups and copies:
Type Key Completion Time Filename/Handle
Backup Set 128 15-APR-08
Backup Piece 128 15-APR-08 C:\ARCH_130_ORCL1_20080415.ARC
Archive Log 79 15-APR-08 C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
COVERY_AREA\ORCL1\ARCHIVELOG\2008_04_15\O1_MF_1_24_408RYXDF_.ARC
Archive Log 80 15-APR-08 C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
COVERY_AREA\ORCL1\ARCHIVELOG\2008_04_15\O1_MF_1_25_408X1SCR_.ARC
deleted backup piece
backup piece handle=C:\ARCH_130_ORCL1_20080415.ARC recid=128 stamp=652112652
deleted archive log
archive log filename=C:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ORCL1\ARCHIVEL
OG\2008_04_15\O1_MF_1_24_408RYXDF_.ARC recid=79 stamp=652108461
deleted archive log
archive log filename=C:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ORCL1\ARCHIVEL
OG\2008_04_15\O1_MF_1_25_408X1SCR_.ARC recid=80 stamp=652112650
Deleted 3 objects
released channel: ORA_DISK_1
allocated channel: ch2
channel ch2: sid=146 devtype=DISK
released channel: ch2
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=146 devtype=DISK
no obsolete backups found
RMAN>
C:\>dir *.bus
Volume in drive C is khurram
Volume Serial Number is F49D-FF2B
Directory of C:\
04/15/2008 02:24 PM 96,813,056 RMAN_131_ORCL1_20080415.BUS
1 File(s) 96,813,056 bytes
0 Dir(s) 61,960,724,480 bytes free
C:\>dir *.arc
Volume in drive C is khurram
Volume Serial Number is F49D-FF2B
Directory of C:\
04/15/2008 02:25 PM 56,832 ARCH_132_ORCL1_20080415.ARC
1 File(s) 56,832 bytes
0 Dir(s) 61,960,724,480 bytes free
C:\>
RMAN> run {
2> allocate channel ch0 type disk;
3> backup as compressed backupset database format
4> 'c:\rman_%s_%d_%T.bus'
5> plus archivelog format 'c:\arch_%s_%d_%T.arc';
6> release channel ch0;
7> }
released channel: ORA_DISK_1
allocated channel: ch0
channel ch0: sid=146 devtype=DISK
Starting backup at 15-APR-08
current log archived
channel ch0: starting compressed archive log backupset
channel ch0: specifying archive log(s) in backup set
input archive log thread=1 sequence=26 recid=81 stamp=652112703
input archive log thread=1 sequence=27 recid=82 stamp=652112873
channel ch0: starting piece 1 at 15-APR-08
channel ch0: finished piece 1 at 15-APR-08
piece handle=C:\ARCH_134_ORCL1_20080415.ARC comment=NONE
channel ch0: backup set complete, elapsed time: 00:00:02
Finished backup at 15-APR-08
Starting backup at 15-APR-08
channel ch0: starting compressed full datafile backupset
channel ch0: specifying datafile(s) in backupset
input datafile fno=00001 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL1\SYSTEM01.DB
F
input datafile fno=00003 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL1\SYSAUX01.DB
F
input datafile fno=00004 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL1\USERS01.DBF
input datafile fno=00002 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL1\UNDOTBS01.D
BF
channel ch0: starting piece 1 at 15-APR-08
channel ch0: finished piece 1 at 15-APR-08
piece handle=C:\RMAN_135_ORCL1_20080415.BUS comment=NONE
channel ch0: backup set complete, elapsed time: 00:00:45
Finished backup at 15-APR-08
Starting backup at 15-APR-08
current log archived
channel ch0: starting compressed archive log backupset
channel ch0: specifying archive log(s) in backup set
input archive log thread=1 sequence=28 recid=83 stamp=652112925
channel ch0: starting piece 1 at 15-APR-08
channel ch0: finished piece 1 at 15-APR-08
piece handle=C:\ARCH_136_ORCL1_20080415.ARC comment=NONE
channel ch0: backup set complete, elapsed time: 00:00:02
Finished backup at 15-APR-08
Starting Control File and SPFILE Autobackup at 15-APR-08
piece handle=C:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ORCL1\AUTOBACKUP\2008_
04_15\O1_MF_S_652112928_408XBKCZ_.BKP comment=NONE
Finished Control File and SPFILE Autobackup at 15-APR-08
released channel: ch0
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
Report of obsolete backups and copies
Type Key Completion Time Filename/Handle
Backup Set 129 15-APR-08
Backup Piece 129 15-APR-08 C:\RMAN_131_ORCL1_20080415.BUS
Backup Set 130 15-APR-08
Backup Piece 130 15-APR-08 C:\ARCH_132_ORCL1_20080415.ARC
Backup Set 131 15-APR-08
Backup Piece 131 15-APR-08 C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
COVERY_AREA\ORCL1\AUTOBACKUP\2008_04_15\O1_MF_S_652112718_408X3ZVJ_.BKP
Backup Set 132 15-APR-08
Backup Piece 132 15-APR-08 C:\ARCH_134_ORCL1_20080415.ARC
Archive Log 81 15-APR-08 C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
COVERY_AREA\ORCL1\ARCHIVELOG\2008_04_15\O1_MF_1_26_408X3HRP_.ARC
Archive Log 82 15-APR-08 C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
COVERY_AREA\ORCL1\ARCHIVELOG\2008_04_15\O1_MF_1_27_408X8RXN_.ARC
RMAN>Note: i have archivelog which is at FRA ,it also apply there and as well yours own defined backupsets path.
Yours comments are wellcome.
http://oraware.blogspot.com/2008/04/can-i-use-retention-policy-without.htmlKhurramHmmm, I can't see where the confusion originates. The table near the bottom of www.apple.com/timecapsule/specs.html has one row labelled "For backup using Time Machine" and another row labelled "For AirPort Disk with a USB hard drive".
The requirement for backup via Time Machine is OS 10.5.1 or better. Time Machine is not supported in pre-Leopard (OS 10.5) nor in Windows.
The requirement for using Time Capsule as a remote disk is identified as "Mac with Mac OS X v10.4.8 or later" or "PC with Windows XP (SP2) or Windows Vista; Bonjour for Windows (included on Time Capsule CD)".
Doesn't that pretty much spell out that Time Capsule works as a network drive without the need for Time Machine?
Also Joe (the OP) never indicated any desire to use it with Windows so I'm not sure why all the discussion about Windows compatibility. ??
Also the quote posted by Henry seems pretty clear:
"Time Capsule with Time Machine in Leopard is the ideal backup solution. But that doesn’t mean Tiger, Windows XP, and Windows Vista users can’t enjoy the benefits of Time Capsule, too. Because it mounts as a wireless hard drive, Tiger and Windows users simply access Time Capsule directly from the wireless network for exchanging and storing files quickly and easily." -
Hi All,
I've inherited and Exchange 2010 SP3 UR4 environment that has UM but no Retention Policy has been set. As a result, I have MP3s filling up disk space. Adding to that is that I'm a N00b when it comes to Exchange. I've more or less created
User and Room Mailboxes, etc.
This Retention Policy should address it:
New-RetentionPolicyTag "Voice Mail 60 Day Retention" -Type All -MessageClass voicemail -Comment "Untagged messages removed after 60 days." -RetentionEnabled $true -AgeLimitForRetention
60 -RetentionAction DeleteAndAllowRecovery
Thing is, just like any "set" cmdlet, I prefer to first query like everyone else with a "get" cmdlet.
Do you know if there's a way to query this first?
Thank you very much for your time,
Mr MisterYou mean you want to see if it actually works as expected? In that case I would create the policy and then apply only to one mailbox and see how that goes.
http://technet.microsoft.com/en-us/library/dd298052(v=exchg.141).aspx
Apply a Retention Policy to Mailboxes
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied. -
How can i set the session of a new window?
I am placing in session an object from an action class like this request.getSession().setAttribute("currentBean",orderInfoModel.getDetails()); and i use it into a jsp page to print some informations. The page name is called orders.jsp where i use the object: <jsp:useBean id = "currentBean" scope="session" type="miru.orderInfo.OrderInfoBean"/> on that page i have a button and when i click it it opens me a new window(not a new tab) <input type="button" value="Edit" onclick="openWindow('http://localhost:8080/miru/scrisoareTransport.jsp','ScrisoareDeTransport',1150,600)">
the jsp for the new window(scrisoareTransport.jsp) looks like this :
<%@ include file="taglibs.jsp" %>
<%@ page import="database.navigator.Navigator"%>
<jsp:useBean id = "currentBean" scope="session" type="miru.orderInfo.OrderInfoBean"/>
<html>
</html>
Because IE is starting a new session on new window i need to pass the session and probably the currentBean object from the parent page to the childpage and set the child page session with the one coming from the parent page
Advices?
10xwell, the Gaussian window and the Gaussian Monopulse vis are good starting points, I would start with the window vi, but with a shorter length and add zeros before and after to get the full window with the peak at the desired position.
If
Greetings from Germany
Henrik
LV since v3.1
“ground” is a convenient fantasy
'˙˙˙˙uıɐƃɐ lɐıp puɐ °06 ǝuoɥd ɹnoʎ uɹnʇ ǝsɐǝld 'ʎɹɐuıƃɐɯı sı pǝlɐıp ǝʌɐɥ noʎ ɹǝqɯnu ǝɥʇ' -
How to set the WebDynpro application title (IE windows title)?
Hello all,
I would like to set the WebDynpro application title according to the current transaction ID. This title is the IE windows title that is shown on the upper left-corner of the IE browser.
Rule: [Object Instance Information] u2013 [Application Title] u2013 [Browser Title]
For example: Trans. <No.> - <My App> - Windows Internet Explorer
I would like to set <No.> dynamically on run-time according to my current transaction number.
I have this piece of code that gets a reference to the application info:
data: lr_app_info TYPE REF TO if_wdr_rr_application.
lr_app_info ?= wdr_task=>application->application_info.
And there is lr_app_info->get_description() method to have the description of the application, but there is no set method.
The application description can be hardcoded in:
tx. SE80, opening the WebDynpro component, then accessing its WebDynpro application. In the properties tab, there is a description field. I need to append transaction ID to it.
Do you know any way to implement this? This issue is for WebDynpro ABAP.
Best regards and thanks in advance,
Fouad.Hello Satra,
Thanks for your reply. I already had a look into that thread, but my question is not related to the windows title of the WebDynpro component.
My question is related to the title of the Internet Explorer that we all see on the top left-corner. For WebDynpro , this is the WebDynpro application title. How can we change it?
I hope my question is clear now, and I wish someone can help me soon.
With kind regards,
Fouad. -
How to set the dimension of main page windows for std dot matrix printer
Hi All,
I have to print a form in a pre- printed form which is coming from the standard dot matrix printer( 80 column).
In the Sap script how i will define the dimensions of main page window .
The printer is in US . How i can sets the page dimensions .
reward point will be provided.
RegardsChange SEQUENCE = "213" to SEQUENCE = "218" in the Task ID Field component. That will solve the issue.
--Shiv
Maybe you are looking for
-
IPad cannot be found after trying to update to 7.1.1
While updating my iPad to 7.1.1 through my computer, it crashed and now it says I need to restore, but it won't let me. I cant even touch the iPad, it shows the plug into iTunes icons. itunes is recognizing the device to some extent because when I pl
-
RDP Users seeing display issues with SharePoint Online Template
I originally posted this in the SharePoint Online forums, but they referred me to the RDP forums as it appears to be an issue with RDP, not SharePoint Online: Original Post I've been able to verify this only happens in RDP when opening a Word Templat
-
Printing in only last line item printing in main window
Hi All, My requiremnet is to print same data in two blocks for F110 payment cheque Iam using 2 main windows to print same data if block exceeds it will go to next page iam calling the windows as shown below CALL FUNCTION 'WRITE_FORM' EXPORTING
-
Dvt:map, JSR-168 portlets, and WebCenter Spaces
Please click here [http://fusion.appshosting.com:8788/coxcustomportlets/faces/callcenterportlet.jspx] When I attempt to view this portlet in WebCenter Spaces, the map will not render. The rest of the portlet renders fine. The connections.xml file is
-
Error in GP CO(comp interface controller code) implementation
Hi Frndz.. I have 3 quires on GP n itz configurations those 1)Am developing an GP callable Object , am following this doc https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e0957cb6-5103-2a10-6d9d-a0a4d68c8bf1 In the Interface compon