Audit & System Log Retention Policy
Hello Everyone,
I am trying to collect informatiion from various sources to see what the standard industry practice is to maintain the Audit & Systems Logs? This information will be crucial for us determine how many days worth of logs we should keep and what we can delete. Any information will be highly appreicated.
Thanks!
RK
#THIS DOES NOT WORK
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '\\medabdb2\rmandisk\%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 1; # 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 SNAPSHOT CONTROLFILE NAME TO 'C:\ORACLE\ORA92\DATABASE\SNCFABANO.ORA'; # default
#THIS WORKS
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 'D:\RmanDisk\%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 1; # 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 SNAPSHOT CONTROLFILE NAME TO 'D:\ORACLE\ORA92\DATABASE\SNCFORCL.ORA';# default
System that works has redundancy to 1; nothing changes even if I set the redundancy to 1 for the system that does not work...
Bye.
Message was edited by:
Stefano IT
Similar Messages
-
Recovery window retention policy deletes archive logs before a backup?
Hi All,
Oracle 11G on Windows 2008 R2
This afternoon, I changed my RMAN retention policy from 'RETENTION POLICY REDUNDANCY 3' to RETENTION POLICY RECOVERY WINDOW OF 3 DAYS'
However, i checked tonight and after my daily backup ran, all the archive logs prior to the backup had been deleted! Thus meaning i dont think i can restore to any point in time, prior to my daily backup. All the .arc logs were there after the backup. So i tried another test and kicked off the daily backup again. During the backup process, the archive logs got deleted again! Now i don't have any archive logs..
Is this proper behaviour of RETENTION POLICY RECOVERY WINDOW?? I thought it would keep all the files needed for me to restore to any point in time for the previous 3 days. When i used REDUNDANCY, with my daily backups, it kept 3 days worth of backups+ archive logs so i could restore point-in-time to any point. How can i use RECOVERY WINDOW so that i can actually restore to any point-in-time for the 3 days??
I wanted to change to RECOVERY WINDOW since i read that by using REDUNDANCY it only keeps X copies of a backup (so if i ran the backup 3 times in a day, i would only have those 3).
Thanks in advance.Hi All,
Here is the SHOW ALL output:
RMAN> show all;
RMAN configuration parameters for database with db_unique_name MMSPRD7 are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 3 DAYS;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
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 LOA
D TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'D:\ORACLE\DATABASE\ORA11G\DATABASE\SNCFM
MSPRD7.ORA'; # default
Here is the RMAN script:
Recovery Manager: Release 11.2.0.3.0 - Production on Mon Jan 20 23:03:12 2014
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to target database: XXX (DBID=)
RMAN> CROSSCHECK ARCHIVELOG ALL;
2> CROSSCHECK BACKUPSET;
3> CROSSCHECK BACKUP;
4> CROSSCHECK COPY;
5> DELETE NOPROMPT EXPIRED ARCHIVELOG ALL;
6> DELETE NOPROMPT EXPIRED BACKUPSET;
7> DELETE NOPROMPT OBSOLETE;
8> BACKUP CURRENT CONTROLFILE;
9> BACKUP AS COMPRESSED BACKUPSET DATABASE PLUS ARCHIVELOG DELETE INPUT;
Also, not sure if you needed the whole RMAN output, but here is the deletion part:
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 3 days
using channel ORA_DISK_1
Deleting the following obsolete backups and copies:
Type Key Completion Time Filename/Handle
Backup Set 1392 15-JAN-14
Backup Piece 1392 15-JAN-14 F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_15\O1_MF_NNNDF_TAG20140115T190054_9FG89R8N_.BKP
Backup Set 1393 15-JAN-14
Backup Piece 1393 15-JAN-14 F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_15\O1_MF_ANNNN_TAG20140115T192204_9FG9KDHX_.BKP
Backup Set 1397 16-JAN-14
Backup Piece 1397 16-JAN-14 F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_16\O1_MF_ANNNN_TAG20140116T190027_9FJWNW6L_.BKP
Backup Set 1400 17-JAN-14
Backup Piece 1400 17-JAN-14 F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_17\O1_MF_ANNNN_TAG20140117T190138_9FMK349M_.BKP
deleted backup piece
backup piece handle=F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_15\O1_MF_NNNDF_TAG20140115T190054_9FG89R8N_.BKP RECID=1392 STAMP=836938856
deleted backup piece
backup piece handle=F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_15\O1_MF_ANNNN_TAG20140115T192204_9FG9KDHX_.BKP RECID=1393 STAMP=836940124
deleted backup piece
backup piece handle=F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_16\O1_MF_ANNNN_TAG20140116T190027_9FJWNW6L_.BKP RECID=1397 STAMP=837025228
deleted backup piece
backup piece handle=F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_17\O1_MF_ANNNN_TAG20140117T190138_9FMK349M_.BKP RECID=1400 STAMP=837111700
Deleted 4 objects -
SCEP Client Activity Logs Files - Retention Policy?
In SCEP 2012....
1. Where are client activity log files stored?
2. What is the default retention policy?
I remember with FCS, I think the historical data was stored for 14 months (by default). Is that the same for SCEP?
Andrew MarcosLogs are in c:\program data\Microsoft\Microsoft Antimalware\Support.
Not sure on retention as I am working in non-persistent VDI's that get their logs reset after a log off!
Cheers
Paul | sccmentor.wordpress.com -
Mailbox Retention Policy - Tracking - Logging
we have a mbx retention policy which deleted items older than 6 months in sent items and it allows the users to receover from the recover deleted items.
This one users sent items disappered today completely except for 2 emails. Then she receovered the items from recover deleted items. Is there a way I can find when was the mbx retetnion policy fired agianst this user? Even if it was fired
its shoudl be gradual.
thanks uyou can look in event viewer on mailbox server, App logs - filter by event ID
event ID 10027 Managed Folder Assistant - statistics of MRM expiration at end of this work cycle
you will not see specific usernames there, but you can isolate this user by just applying policy on her mailbox and run MRM on demand with PS
start-managedfolderassistant -identity clientname
also you can temporarily put retention hold and run mrm to see items tagged and their status.. like expires date on top of messages
thanks -
Auditing / Logging of policy updates/publishing?
Is there such a thing? Is any publishing of the policy logged anywhere?
We've had a couple of issues in last few weeks where one of our admins has pushed the wrong policy out to groups of people overwriting their proper policy and causing no end of headache's.
Is there any sort of auditing in place showing who changed policy, or what changes were made, or who pushed out what policy, when, and who to?This is what I got:
The Management Console will show the last user that edited a particular policy (on the main screen with the list of policies). Details of what changed would have to be done through manual SQL queries.
If this is not enough (which I suspect), please enter an enhancement request in order for PM to priorize this feature accordingly for future release.
>>>
From: Daniel Spinatto<[email protected]>
To:novell.support.zenworks.endpoint-security-management
Date: 12/15/2010 3:31 pm
Subject: Re: Auditing / Logging of policy updates/publishing?
Hey Andy,
Good question. There's nothing with 4.1 that I know of.
Let me ask anyway and I'll get back to you.
>>>
From: andystewartSL<[email protected]>
To:novell.support.zenworks.endpoint-security-management
Date: 12/10/2010 6:36 am
Subject: Auditing / Logging of policy updates/publishing?
Is there such a thing? Is any publishing of the policy logged anywhere?
We've had a couple of issues in last few weeks where one of our admins
has pushed the wrong policy out to groups of people overwriting their
proper policy and causing no end of headache's.
Is there any sort of auditing in place showing who changed policy, or
what changes were made, or who pushed out what policy, when, and who to?
Andy Stewart - Somewhere In Scotland
zcm 10.2.2, 4 servers in esx vm environment, 2000 users so far...
(i'd still rather be snowboarding)
andystewartSL's Profile: http://forums.novell.com/member.php?userid=1054
View this thread: http://forums.novell.com/showthread.php?t=427867 -
Archive Log Backups Retention Policy
How can I define Retention Policy for archive log backups?
The question asked and answer you have marked as "Correct answer" is misleading.
For archived log deletion policy, look below.
Configuring the RMAN Environment
For the actual question posted "How can I define Retention Policy for archive log backups?", look below link.
http://docs.oracle.com/cd/E11882_01/backup.112/e10642/rcmconfb.htm#i1019318
Also, did you start the thread to clear your doubt or test the other forum users?
Thank you!! -
Tracking oracle database activities in security/system logs of windows server
Can database activity like create or drop tables and packages be tracked in the security/system logs of windows 2003 server for the oracle database 10.2.0.4?
Can purging of oracle log, n case the file has become big or even tempered be tracked in the security/system logs of windows 2003 server for the oracle database 10.2.0.4?
dhomyaHi Dhomya,
I am not familiar with Oracle database, though you may try to enable file system auditing:
Audit object access
https://technet.microsoft.com/en-us/library/cc776774(v=ws.10).aspx
Apply or modify auditing policy settings for an object using Group Policy
https://technet.microsoft.com/en-us/library/cc757864(v=ws.10).aspx
Best Regards,
Amy
Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] -
Control_file_record_keep_time vs retention policy
Its not thread nor question just read from documents and tried to imply the fact of documents and i think its written correct what i tried to do proof it practically ,neither i am trying to be smart just share with you guys is my observation correct or not.i am using FRA area for backup.
<quote>
Relation between RMAN retention period and control_file_record_keep_time
RMAN backup keeps the backup metadata information in the reusable section of the controlfile.Its depends on the parameter CONTROL_FILE_RECORD_KEEP_TIME. CONTROL_FILE_RECORD_KEEP_TIME specifies the minimum number of days before a reusable record in the control file can be reused.
In the event a new record needs to be added to a reusable section and there is not enough space then it will delete the oldest record, which are aged enough.
Backup retention policy is the rule to set regarding which backups must be retained (whether on disk or other backup media) to meet the recovery and other requirements.
If the CONTROL_FILE_RECORD_KEEP_TIME is less than the retention policy then it may overwrite reusable records prior to obsoleting them in the RMAN metadata. Therfor it is recommended that the CONTROL_FILE_RECORD_KEEP_TIME should set to a higher value than the retention policy.
Formula
CONTROL_FILE_RECORD_KEEP_TIME = retention period + level 0 backup interval + 1
For e.g.
e.q. level 0 backup once a week with retention policy of a recovery windows of 14 days then in this
case the CONTROL_FILE_RECORD_KEEP_TIME should be 14+7+1=22
<quote>
RMAN> show retention policy
2> ;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
SQL> show parameter control_file_record_keep_time
NAME TYPE VALUE
control_file_record_keep_time integer 7
SQL>
SQL> alter system set control_file_record_keep_time=1
2 /
System altered.
SQL> show parameter control_file_record_keep_time
NAME TYPE VALUE
control_file_record_keep_time integer 1
RMAN> configure retention policy to redundancy 3
2> ;
new RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO REDUNDANCY 3;
new RMAN configuration parameters are successfully stored
RMAN> show retention policy
2> ;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 3;
RMAN> backup database
2> ;
Starting backup at 20-NOV-07
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=126 devtype=DISK
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSTEM01.DBF
input datafile fno=00003 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSAUX01.DBF
input datafile fno=00002 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\UNDOTBS01.DBF
input datafile fno=00004 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\USERS01.DBF
channel ORA_DISK_1: starting piece 1 at 20-NOV-07
channel ORA_DISK_1: finished piece 1 at 20-NOV-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\BACKUPSET\2007_11_20\O1_MF_NN
NDF_TAG20071120T185951_3N5T2RTX_.BKP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:01:17
Finished backup at 20-NOV-07
Starting Control File and SPFILE Autobackup at 20-NOV-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\AUTOBACKUP\2007_11_20\O1_MF_S
_639169270_3N5T598C_.BKP comment=NONE
Finished Control File and SPFILE Autobackup at 20-NOV-07
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 3
no obsolete backups found
RMAN> backup database
2> ;
Starting backup at 20-NOV-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=00001 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSTEM01.DBF
input datafile fno=00003 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSAUX01.DBF
input datafile fno=00002 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\UNDOTBS01.DBF
input datafile fno=00004 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\USERS01.DBF
channel ORA_DISK_1: starting piece 1 at 20-NOV-07
channel ORA_DISK_1: finished piece 1 at 20-NOV-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\BACKUPSET\2007_11_20\O1_MF_NN
NDF_TAG20071120T190313_3N5T94SG_.BKP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:01:22
Finished backup at 20-NOV-07
Starting Control File and SPFILE Autobackup at 20-NOV-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\AUTOBACKUP\2007_11_20\O1_MF_S
_639169477_3N5TCPVW_.BKP comment=NONE
Finished Control File and SPFILE Autobackup at 20-NOV-07
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 3
no obsolete backups found
RMAN> backup database
2> ;
Starting backup at 20-NOV-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=00001 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSTEM01.DBF
input datafile fno=00003 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSAUX01.DBF
input datafile fno=00002 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\UNDOTBS01.DBF
input datafile fno=00004 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\USERS01.DBF
channel ORA_DISK_1: starting piece 1 at 20-NOV-07
channel ORA_DISK_1: finished piece 1 at 20-NOV-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\BACKUPSET\2007_11_20\O1_MF_NN
NDF_TAG20071120T190500_3N5TDGC9_.BKP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:55
Finished backup at 20-NOV-07
Starting Control File and SPFILE Autobackup at 20-NOV-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\AUTOBACKUP\2007_11_20\O1_MF_S
_639169556_3N5TG65X_.BKP comment=NONE
Finished Control File and SPFILE Autobackup at 20-NOV-07
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 3
Report of obsolete backups and copies
Type Key Completion Time Filename/Handle
Archive Log 30 19-NOV-07 C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_19\O1_MF_1_1_3N35QQX7_.ARC
Archive Log 31 19-NOV-07 C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_19\O1_MF_1_2_3N39LR86_.ARC
Archive Log 32 20-NOV-07 C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_20\O1_MF_1_3_3N4RZBXV_.ARC
Archive Log 33 20-NOV-07 C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_20\O1_MF_1_4_3N4W8SLF_.ARC
Archive Log 34 20-NOV-07 C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_20\O1_MF_1_5_3N4Y1CN7_.ARC
Archive Log 35 20-NOV-07 C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_20\O1_MF_1_6_3N4Z6LGF_.ARC
Archive Log 36 20-NOV-07 C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_20\O1_MF_1_7_3N53S4XK_.ARC
Archive Log 37 20-NOV-07 C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_20\O1_MF_1_8_3N57XHYB_.ARC
Archive Log 38 20-NOV-07 C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_20\O1_MF_1_9_3N5C52D8_.ARC
Archive Log 39 20-NOV-07 C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_20\O1_MF_1_10_3N5C83YB_.ARC
Archive Log 40 20-NOV-07 C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_20\O1_MF_1_11_3N5K9J2Z_.ARC
Archive Log 41 20-NOV-07 C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_20\O1_MF_1_12_3N5MMXHO_.ARC
Archive Log 42 20-NOV-07 C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_20\O1_MF_1_13_3N5N566W_.ARC
Archive Log 43 20-NOV-07 C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_20\O1_MF_1_14_3N5RVB4G_.ARC
RMAN>
Now i just delete alls backup and increase the control_file_record_keep_time 7 which will be more then retention policy redundancy 3
RMAN> list backup
2> ;
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
6 Full 512M DISK 00:01:10 20-NOV-07
BP Key: 6 Status: AVAILABLE Compressed: NO Tag: TAG20071120T185951
Piece Name: C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\BACKUPSET\2007_11_20\O
1_MF_NNNDF_TAG20071120T185951_3N5T2RTX_.BKP
List of Datafiles in backup set 6
File LV Type Ckp SCN Ckp Time Name
1 Full 478504 20-NOV-07 C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSTEM01
.DBF
2 Full 478504 20-NOV-07 C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\UNDOTBS0
1.DBF
3 Full 478504 20-NOV-07 C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSAUX01
.DBF
4 Full 478504 20-NOV-07 C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\USERS01.
DBF
BS Key Type LV Size Device Type Elapsed Time Completion Time
7 Full 2M DISK 00:00:04 20-NOV-07
BP Key: 7 Status: AVAILABLE Compressed: NO Tag: TAG20071120T190110
Piece Name: C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\AUTOBACKUP\2007_11_20\
O1_MF_S_639169270_3N5T598C_.BKP
Controlfile Included: Ckp SCN: 478975 Ckp time: 20-NOV-07
SPFILE Included: Modification time: 20-NOV-07
BS Key Type LV Size Device Type Elapsed Time Completion Time
8 Full 513M DISK 00:01:15 20-NOV-07
BP Key: 8 Status: AVAILABLE Compressed: NO Tag: TAG20071120T190313
Piece Name: C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\BACKUPSET\2007_11_20\O
1_MF_NNNDF_TAG20071120T190313_3N5T94SG_.BKP
List of Datafiles in backup set 8
File LV Type Ckp SCN Ckp Time Name
1 Full 480265 20-NOV-07 C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSTEM01
.DBF
2 Full 480265 20-NOV-07 C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\UNDOTBS0
1.DBF
3 Full 480265 20-NOV-07 C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSAUX01
.DBF
4 Full 480265 20-NOV-07 C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\USERS01.
DBF
BS Key Type LV Size Device Type Elapsed Time Completion Time
9 Full 2M DISK 00:00:02 20-NOV-07
BP Key: 9 Status: AVAILABLE Compressed: NO Tag: TAG20071120T190437
Piece Name: C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\AUTOBACKUP\2007_11_20\
O1_MF_S_639169477_3N5TCPVW_.BKP
Controlfile Included: Ckp SCN: 480346 Ckp time: 20-NOV-07
SPFILE Included: Modification time: 20-NOV-07
BS Key Type LV Size Device Type Elapsed Time Completion Time
10 Full 513M DISK 00:00:52 20-NOV-07
BP Key: 10 Status: AVAILABLE Compressed: NO Tag: TAG20071120T190500
Piece Name: C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\BACKUPSET\2007_11_20\O
1_MF_NNNDF_TAG20071120T190500_3N5TDGC9_.BKP
List of Datafiles in backup set 10
File LV Type Ckp SCN Ckp Time Name
1 Full 480415 20-NOV-07 C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSTEM01
.DBF
2 Full 480415 20-NOV-07 C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\UNDOTBS0
1.DBF
3 Full 480415 20-NOV-07 C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSAUX01
.DBF
4 Full 480415 20-NOV-07 C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\USERS01.
DBF
BS Key Type LV Size Device Type Elapsed Time Completion Time
11 Full 2M DISK 00:00:02 20-NOV-07
BP Key: 11 Status: AVAILABLE Compressed: NO Tag: TAG20071120T190556
Piece Name: C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\AUTOBACKUP\2007_11_20\
O1_MF_S_639169556_3N5TG65X_.BKP
Controlfile Included: Ckp SCN: 480449 Ckp time: 20-NOV-07
SPFILE Included: Modification time: 20-NOV-07
RMAN> delete backup
2> ;
using channel ORA_DISK_1
List of Backup Pieces
BP Key BS Key Pc# Cp# Status Device Type Piece Name
6 6 1 1 AVAILABLE DISK C:\ORACLE\FLASH_RECOVERY_AREA\OR
C\ORC\BACKUPSET\2007_11_20\O1_MF_NNNDF_TAG20071120T185951_3N5T2RTX_.BKP
7 7 1 1 AVAILABLE DISK C:\ORACLE\FLASH_RECOVERY_AREA\OR
C\ORC\AUTOBACKUP\2007_11_20\O1_MF_S_639169270_3N5T598C_.BKP
8 8 1 1 AVAILABLE DISK C:\ORACLE\FLASH_RECOVERY_AREA\OR
C\ORC\BACKUPSET\2007_11_20\O1_MF_NNNDF_TAG20071120T190313_3N5T94SG_.BKP
9 9 1 1 AVAILABLE DISK C:\ORACLE\FLASH_RECOVERY_AREA\OR
C\ORC\AUTOBACKUP\2007_11_20\O1_MF_S_639169477_3N5TCPVW_.BKP
10 10 1 1 AVAILABLE DISK C:\ORACLE\FLASH_RECOVERY_AREA\OR
C\ORC\BACKUPSET\2007_11_20\O1_MF_NNNDF_TAG20071120T190500_3N5TDGC9_.BKP
11 11 1 1 AVAILABLE DISK C:\ORACLE\FLASH_RECOVERY_AREA\OR
C\ORC\AUTOBACKUP\2007_11_20\O1_MF_S_639169556_3N5TG65X_.BKP
Do you really want to delete the above objects (enter YES or NO)? yes
deleted backup piece
backup piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\BACKUPSET\2007_11_20\O
1_MF_NNNDF_TAG20071120T185951_3N5T2RTX_.BKP recid=6 stamp=639169192
deleted backup piece
backup piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\AUTOBACKUP\2007_11_20\
O1_MF_S_639169270_3N5T598C_.BKP recid=7 stamp=639169273
deleted backup piece
backup piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\BACKUPSET\2007_11_20\O
1_MF_NNNDF_TAG20071120T190313_3N5T94SG_.BKP recid=8 stamp=639169396
deleted backup piece
backup piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\AUTOBACKUP\2007_11_20\
O1_MF_S_639169477_3N5TCPVW_.BKP recid=9 stamp=639169478
deleted backup piece
backup piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\BACKUPSET\2007_11_20\O
1_MF_NNNDF_TAG20071120T190500_3N5TDGC9_.BKP recid=10 stamp=639169502
deleted backup piece
backup piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\AUTOBACKUP\2007_11_20\
O1_MF_S_639169556_3N5TG65X_.BKP recid=11 stamp=639169558
Deleted 6 objects
RMAN> delete archivelog all
2> ;
released channel: ORA_DISK_1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=126 devtype=DISK
specification does not match any archive log in the recovery catalog
RMAN> list backup
2> ;
RMAN> show retention policy
2> ;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 3;
SQL> show parameter control_file_record_keep_time
NAME TYPE VALUE
control_file_record_keep_time integer 1
SQL> alter system set control_file_record_keep_time=7
2 /
System altered.
SQL> show parameter control_file_record_keep_time
NAME TYPE VALUE
control_file_record_keep_time integer 7
SQL>
RMAN> backup database
2> ;
Starting backup at 20-NOV-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=00001 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSTEM01.DBF
input datafile fno=00003 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSAUX01.DBF
input datafile fno=00002 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\UNDOTBS01.DBF
input datafile fno=00004 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\USERS01.DBF
channel ORA_DISK_1: starting piece 1 at 20-NOV-07
channel ORA_DISK_1: finished piece 1 at 20-NOV-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\BACKUPSET\2007_11_20\O1_MF_NN
NDF_TAG20071120T191412_3N5TXRSG_.BKP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:01:15
Finished backup at 20-NOV-07
Starting Control File and SPFILE Autobackup at 20-NOV-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\AUTOBACKUP\2007_11_20\O1_MF_S
_639170131_3N5V03YT_.BKP comment=NONE
Finished Control File and SPFILE Autobackup at 20-NOV-07
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 3
no obsolete backups found
RMAN> backup database
2> ;
Starting backup at 20-NOV-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=00001 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSTEM01.DBF
input datafile fno=00003 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSAUX01.DBF
input datafile fno=00002 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\UNDOTBS01.DBF
input datafile fno=00004 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\USERS01.DBF
channel ORA_DISK_1: starting piece 1 at 20-NOV-07
channel ORA_DISK_1: finished piece 1 at 20-NOV-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\BACKUPSET\2007_11_20\O1_MF_NN
NDF_TAG20071120T191655_3N5V2S20_.BKP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:45
Finished backup at 20-NOV-07
Starting Control File and SPFILE Autobackup at 20-NOV-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\AUTOBACKUP\2007_11_20\O1_MF_S
_639170261_3N5V462Z_.BKP comment=NONE
Finished Control File and SPFILE Autobackup at 20-NOV-07
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 3
no obsolete backups found
RMAN> backup database
2> ;
Starting backup at 20-NOV-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=00001 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSTEM01.DBF
input datafile fno=00003 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSAUX01.DBF
input datafile fno=00002 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\UNDOTBS01.DBF
input datafile fno=00004 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\USERS01.DBF
channel ORA_DISK_1: starting piece 1 at 20-NOV-07
channel ORA_DISK_1: finished piece 1 at 20-NOV-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\BACKUPSET\2007_11_20\O1_MF_NN
NDF_TAG20071120T191836_3N5V5X20_.BKP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:45
Finished backup at 20-NOV-07
Starting Control File and SPFILE Autobackup at 20-NOV-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\AUTOBACKUP\2007_11_20\O1_MF_S
_639170362_3N5V7C1K_.BKP comment=NONE
Finished Control File and SPFILE Autobackup at 20-NOV-07
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 3
no obsolete backups foundnothing obsolete it means control_file_record_keep_time will not affect backups unless it will be less then or equal
to retention policy.
Note : Please agree or disagree with me may be i would be wrong
KhurramSorry for alls readers after a long practical observation at my own database server i came across that my observation was wrong and absurd in this first post, the above observation is not due to control_file_record_keep_time ,its due to something obvious which i am going to share you guys here.
RMAN> show retention policy
2> ;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
no obsolete backups found
RMAN> list backup
2> ;
RMAN>AS documentation says
"Besides affecting datafile and control file backups, the retention policy affects archived logs and archived log backups.
First, RMAN decides which datafile and control file backups are obsolete. Then, RMAN considers as obsolete all archived
log backups that are older than the oldest datafile or control file backup that must be retained."
Now i connect to SQL and create two big table for filling the redo log file and then get it archived.Please
consider it here that i am getting archived before any taking backup i.e backup database in order to make
archive older then the oldest datafile.
SQL> show parameter control_file_record_keep_time
NAME TYPE VALUE
control_file_record_keep_time integer 7
SQL> create table a1 as select * from all_objects
2 /
Table created.
SQL> create table a2 as select * from all_objects
2 /
Table created.
C:\>dir C:\oracle\product\10.1.0\flash_recovery_area\ORCL\ARCHIVELOG\2008_03_17
Volume in drive C is khurram
Volume Serial Number is F49D-FF2B
Directory of C:\oracle\product\10.1.0\flash_recovery_area\ORCL\ARCHIVELOG\2008_03_17
03/17/2008 03:44 PM <DIR> .
03/17/2008 03:44 PM <DIR> ..
03/17/2008 03:44 PM 9,750,528 O1_MF_1_15_3XWLVK6T_.ARC
1 File(s) 9,750,528 bytes
2 Dir(s) 62,714,875,904 bytes free
Now i take backup
RMAN> backup database
2> ;
Starting backup at 17-MAR-08
using channel ORA_DISK_1
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
no obsolete backups found
RMAN> backup database
2> ;
Starting backup at 17-MAR-08
using channel ORA_DISK_1
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
Report of obsolete backups and copies
Type Key Completion Time Filename/Handle
Archive Log 402 17-MAR-08 C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
COVERY_AREA\ORCL\ARCHIVELOG\2008_03_17\O1_MF_1_15_3XWLVK6T_.ARCYou can see the obsolete archived files which is the older then the oldest file which has been obsolete.It also
does'nt make sense to keep the archived log files which is older then the oldest file cause it will no longer
be useful for recovery process.
now back to pavillion
RMAN> delete obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
using channel ORA_DISK_1
Deleting the following obsolete backups and copies:
Type Key Completion Time Filename/Handle
Archive Log 402 17-MAR-08 C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
COVERY_AREA\ORCL\ARCHIVELOG\2008_03_17\O1_MF_1_15_3XWLVK6T_.ARC
Do you really want to delete the above objects (enter YES or NO)? yes
deleted archive log
archive log filename=C:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ORCL\ARCHIVELO
G\2008_03_17\O1_MF_1_15_3XWLVK6T_.ARC recid=402 stamp=649611842
Deleted 1 objects
RMAN> delete backup
2> ;
using channel ORA_DISK_1
RMAN> list backup
2> ;
C:\>dir C:\oracle\product\10.1.0\flash_recovery_area\ORCL\ARCHIVELOG\2008_03_17
Volume in drive C is khurram
Volume Serial Number is F49D-FF2B
Directory of C:\oracle\product\10.1.0\flash_recovery_area\ORCL\ARCHIVELOG\2008_
03_17
03/17/2008 03:59 PM <DIR> .
03/17/2008 03:59 PM <DIR> ..
0 File(s) 0 bytes
2 Dir(s) 62,724,440,064 bytes freenow this time what i did i created the archived log files after first backup in order to not to make it older
then the oldest datafile backup.
RMAN> backup database
2> ;
Starting backup at 17-MAR-08
using channel ORA_DISK_1
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
no obsolete backups foundnow i come to at SQL and make redo log file filled by creating 2 big tables in order to get it archived
SQL> create table a3 as select * from all_objects
2 /
Table created.
SQL> create table a4 as select * from all_objects
2 /
Table created.
C:\>dir C:\oracle\product\10.1.0\flash_recovery_area\ORCL\ARCHIVELOG\2008_03_17
Volume in drive C is khurram
Volume Serial Number is F49D-FF2B
Directory of C:\oracle\product\10.1.0\flash_recovery_area\ORCL\ARCHIVELOG\2008_
03_17
03/17/2008 04:09 PM <DIR> .
03/17/2008 04:09 PM <DIR> ..
03/17/2008 04:09 PM 9,751,552 O1_MF_1_16_3XWNCGRS_.ARC
1 File(s) 9,751,552 bytes
2 Dir(s) 62,563,205,120 bytes free
RMAN> backup database
2> ;
Starting backup at 17-MAR-08
using channel ORA_DISK_1
channel ORA_DISK_1: starting compressed full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
no obsolete backups foundYou can see no archived logs get obsolete yet cause the archivelog O1_MF_1_16_3XWNCGRS_.ARC
is not older then oldest datafile backup.
But this archivelog file will get obsolete if its beyond the retention policy,lest see how ,just take one more
backup ,as i have already taken two time backup and the moment i go to take third backup it will cross ours
retetnion policy from the period of 2.
RMAN> backup database
2> ;
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
Report of obsolete backups and copies
Type Key Completion Time Filename/Handle
Backup Set 240 17-MAR-08
Backup Piece 231 17-MAR-08 C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
COVERY_AREA\ORCL\BACKUPSET\2008_03_17\O1_MF_NNNDF_TAG20080317T160604_3XWN4WTB_.B
KP
Backup Set 241 17-MAR-08
Backup Piece 232 17-MAR-08 C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
COVERY_AREA\ORCL\BACKUPSET\2008_03_17\O1_MF_NCSNF_TAG20080317T160604_3XWN6Z95_.B
KP
Archive Log 403 17-MAR-08 C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
COVERY_AREA\ORCL\ARCHIVELOG\2008_03_17\O1_MF_1_16_3XWNCGRS_.ARCKhurram -
Question about Archive Log Deletion policy
I've a problem to understand the Archive Log Deletion policy, and I I'd like to this problem explain with the following example.
Messages of the database are in German, but I guess you'll understand them.
SQL> startup
ORACLE-Instance hochgefahren.
Total System Global Area 5344731136 bytes
Fixed Size 2129240 bytes
Variable Size 2684355240 bytes
Database Buffers 2617245696 bytes
Redo Buffers 41000960 bytes
Datenbank mounted.
Datenbank geöffnet.
SQL> archive log list
Datenbank-Log-Modus Archive-Modus
Automatische Archivierung Aktiviert
Archivierungsziel E:\oracle\thetis_iv\arch
Älteste Online-Log-Sequenz 17917
Nächste zu archivierende Log-Sequenz 17919
Aktuelle Log-Sequenz 17919
SQL> alter system switch logfile;
System wurde geändert.I created a brand new archive log.
SQL> exit
Verbindung zu Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options beendet
D:\OracleDB\product\11.1.0\db_1\BIN>dir E:\oracle\thetis_iv\arch
Datenträger in Laufwerk E: ist Volume
Volumeseriennummer: 3EBD-77E5
Verzeichnis von E:\oracle\thetis_iv\arch
06.04.2011 15:04 <DIR> .
06.04.2011 15:04 <DIR> ..
06.04.2011 15:04 17.137.152 ARC17919_0721667907.001
1 Datei(en), 17.137.152 Bytes
2 Verzeichnis(se), 41.073.258.496 Bytes freiand this is the only archive log in the directory. Now I start rman:
D:\OracleDB\product\11.1.0\db_1\BIN>rman target / catalog rmanrepo@rmanrepo
Recovery Manager: Release 11.1.0.7.0 - Production on Mi Apr 6 15:05:35 2011
Copyright (c) 1982, 2007, Oracle. All rights reserved.
Mit Ziel-Datenbank verbunden: ENTWIV (DBID=21045568)
Kennwort für Recovery-Katalog-Datenbank:
Verbindung mit Datenbank des Recovery-Katalogs
RMAN> show all;
RMAN-Konfigurationsparameter für Datenbank mit db_unique_name ENTWIV sind:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 1 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
CONFIGURE CONTROLFILE AUTOBACKUP OFF;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'E:\oracle\thetis_iv\backup\CF_%F_ENTWIV.ORA';
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO '%F'; # default
CONFIGURE DEVICE TYPE SBT_TAPE PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
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=(TPDO_OPTFILE=D:\Services\Tivoli\TSM\AgentOBA64\tpdo.opt)';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BZIP2'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 2 TIMES TO 'SBT_TAPE';
CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'D:\ORACLEDB\PRODUCT\11.1.0\DB_1\DATABASE\SNCFENTWIV.ORA'; # defaultThe archive log deletion policy says the the logfiles have to be backed up for two times before they get deleted.
Now I backup all archive logs, that havn't been backed up for at least two times.
RMAN> run { backup archivelog all not backed up 2 times
2> format '%d_AR_%Y%M%D_%s_%t'
3> tag 'ARCHIVE LOGS'
4> DELETE ALL INPUT;
5> }
Starten backup um 06.04.2011 15:08:01
Aktuelles Log archiviert
Zugewiesener Kanal: ORA_SBT_TAPE_1
Kanal ORA_SBT_TAPE_1: SID=253 Device-Typ=SBT_TAPE
Kanal ORA_SBT_TAPE_1: Data Protection for Oracle: version 5.5.1.0
Kanal ORA_SBT_TAPE_1: Backup Set für Archive Log wird begonnen
Kanal ORA_SBT_TAPE_1: Archive Logs in Backup Set werden angegeben
Eingabe-Archive-Log-Thread=1 Sequence=17919 RECID=147 STAMP=747759899
Eingabe-Archive-Log-Thread=1 Sequence=17920 RECID=148 STAMP=747760081
Kanal ORA_SBT_TAPE_1: Piece 1 wird auf 06.04.2011 15:08:02 begonnen
Kanal ORA_SBT_TAPE_1: Piece 1 auf 06.04.2011 15:08:09 beendet
Piece Handle=ENTWIV_AR_20110406_23_747760082 Tag=ARCHIVE LOGS Kommentar=API Version 2.0,MMS Version 5.5.1.0
Kanal ORA_SBT_TAPE_1: Backup Set vollstõndig, abgelaufene Zeit: 00:00:08
Kanal ORA_SBT_TAPE_1: Archive Logs werden gel÷scht
Archive Log-Dateiname=E:\ORACLE\THETIS_IV\ARCH\ARC17919_0721667907.001 RECID=147 STAMP=747759899
Archive Log-Dateiname=E:\ORACLE\THETIS_IV\ARCH\ARC17920_0721667907.001 RECID=148 STAMP=747760081
Beendet backup um 06.04.2011 15:08:10
RMAN> exit
Recovery Manager abgeschlossen.
D:\OracleDB\product\11.1.0\db_1\BIN> dir E:\oracle\thetis_iv\arch
Datenträger in Laufwerk E: ist Volume
Volumeseriennummer: 3EBD-77E5
Verzeichnis von E:\oracle\thetis_iv\arch
06.04.2011 15:08 <DIR> .
06.04.2011 15:08 <DIR> ..
0 Datei(en), 0 Bytes
2 Verzeichnis(se), 41.090.396.160 Bytes freirman deleted all archive logs, even I they are on tape only once by now.
Thats not what I expected. Where is my mistake?Hi,
I do new tests it's very strange.
BACKUP ARCHIVELOG command is not obeying the policy of archivelog.
You can open a SR on MOS. (to check bugs)
I reproduce the same test and the result was the same, it seems that this is a bug.
CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 2 TIMES TO DISK;
RMAN> backup archivelog all not backed up 2 times delete all input;
Starting backup at 06-APR-11
current log archived
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=15 RECID=16 STAMP=747753711
input archived log thread=2 sequence=20 RECID=17 STAMP=747753714
input archived log thread=1 sequence=16 RECID=19 STAMP=747753729
input archived log thread=2 sequence=21 RECID=18 STAMP=747753729
channel ORA_DISK_1: starting piece 1 at 06-APR-11
channel ORA_DISK_1: finished piece 1 at 06-APR-11
piece handle=+DATA/orcl/backupset/2011_04_06/annnf0_tag20110406t132210_0.304.747753731 tag=TAG20110406T132210 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
channel ORA_DISK_1: deleting archived log(s)
archived log file name=+DATA/orcl/archivelog/2011_04_06/thread_1_seq_15.293.747753711 RECID=16 STAMP=747753711
archived log file name=+DATA/orcl/archivelog/2011_04_06/thread_2_seq_20.295.747753715 RECID=17 STAMP=747753714
archived log file name=+DATA/orcl/archivelog/2011_04_06/thread_1_seq_16.294.747753729 RECID=19 STAMP=747753729
archived log file name=+DATA/orcl/archivelog/2011_04_06/thread_2_seq_21.298.747753729 RECID=18 STAMP=747753729
Finished backup at 06-APR-11
RMAN> list archivelog all;
specification does not match any archived log in the repositoryOracle Docs Says:
The BACKUP ARCHIVELOG ... DELETE INPUT command deletes archived log files after they are backed up.
This command eliminates the separate step of manually deleting archived redo logs.
With DELETE INPUT, RMAN deletes only the specific copy of the archived log chosen for the backup set.
With DELETE ALL INPUT, RMAN deletes each backed-up archived redo log file from all log archiving destinations.
As explained in "Configuring an Archived Redo Log Deletion Policy",
the BACKUP ... DELETE INPUT and DELETE ARCHIVELOG commands obey the archived redo log deletion policy
for logs in all archiving locations. For example, if you specify that logs should only be deleted when backed
up at least twice to tape, then BACKUP ... DELETE honors this policy.http://download.oracle.com/docs/cd/E11882_01/backup.112/e10642/rcmbckba.htm#BRADV89524
But in ours case it's not honors this policy.
Only with the FORCE command should this happen. But it is not our case.
Oracle Docs:
If FORCE is not specified on the deletion commands,
then these deletion commands obey the archived log deletion policy.
If FORCE is specified, then the deletion commands ignore the archived log deletion policy.http://download.oracle.com/docs/cd/E11882_01/backup.112/e10643/rcmsynta010.htm#RCMRF113
Alternatively you can do the following:
Set the commands separately.
Check this:
RMAN> run {
2> backup archivelog all not backed up 2 times ;
3> delete archivelog all backed up 2 times to disk;
4> }
Starting backup at 06-APR-11
current log archived
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=2 sequence=22 RECID=21 STAMP=747755128
input archived log thread=1 sequence=17 RECID=20 STAMP=747755127
channel ORA_DISK_1: starting piece 1 at 06-APR-11
channel ORA_DISK_1: finished piece 1 at 06-APR-11
piece handle=+DATA/orcl/backupset/2011_04_06/annnf0_tag20110406t134528_0.295.747755129 tag=TAG20110406T134528 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 06-APR-11
released channel: ORA_DISK_1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=78 instance=orcl1 device type=DISK
RMAN-08138: WARNING: archived log not deleted - must create more backups
archived log file name=+DATA/orcl/archivelog/2011_04_06/thread_1_seq_17.298.747755127 thread=1 sequence=17
RMAN-08138: WARNING: archived log not deleted - must create more backups
archived log file name=+DATA/orcl/archivelog/2011_04_06/thread_2_seq_22.294.747755129 thread=2 sequence=22
RMAN>Edited by: Levi Pereira on Apr 6, 2011 1:35 PM -
SharePoint Retention Policy workflow does not start
Hi,
Using Nintex workflows I have created a workflow and attached it to a content type and tested that it runs manually ok. I want it to run according to a retention policy, and so I created a policy based on one of the content type's date fields to start
my workflow automatically. When I manually run the timer jobs I see the following error in ULS logs and the workflow does not start. Interestingly if I amend the policy to do something simple like move the item to the recycle bin, that works fine.
Can anyone suggest what is wrong and where I can go from here to find the issue?
Thanks
Error running the expiration action on item <document url> . Error: System.InvalidOperationException:
The workflow with id=<workflow id > is no longer available.
at Microsoft.Office.RecordsManagement.PolicyFeatures.WorkflowExpirationAction.RunExpirationWithPostActions(SPListItem
item, XmlNode parametersData, DateTime expireDate)
at Microsoft.Office.RecordsManagement.PolicyFeatures.BaseExpirationAction.Microsoft.Office.RecordsManagement.PolicyFeatures.IExpirationActionWithPostActions.OnExpirationWithPostActions(SPListItem
item, XmlNode parametersData, DateTime expireDate)
at Microsoft.Office.RecordsManagement.PolicyFeatures.ExpirationTask.ExpirationActionData.RunExpirationAction(SPListItem
item, DateTime expireDate)
at Microsoft.Office.RecordsManagement.PolicyFeatures.ExpirationTask.<>c__DisplayClass19.<ProcessExpiredItems>b__17(SPListItem
item)
at Microsoft.Office.Server.Utilities.MonitoredScopeWrapper.RunWithMonitoredScope(Action code)
at Microsoft.Office.Server.Utilities.ContentIterator.ProcessItem(SPListItem item, Boolean fIncludeFolderItems,
MonitoredScopeWrapper monitoredScopeWrapper, ItemProcessor itemProcessor, ItemProcessorErrorCallout errorCallout)Hi,
Based on your description, my understanding is that the Retention Policy cannot start the Nintex workflow.
To narrow the issue scope, I recommend to check the things below:
Create a SharePoint 2010 Reusable workflow for the same content type or 2013 list workflow and modify the Retention Policy to start this workflow, and then check how it works.
Create Retention Policy with the Nintex workflow in another list and then compare the results.
Thanks,
Victoria
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Victoria Xia
TechNet Community Support -
CONFIGURE RETENTION POLICY TO REDUNDANCY 0
Our database is 11g R2, below is our RMAN script
Presently our retention policy is 1, so 1 backup is retained along with the current backup.
I Just want to have 1 backup, i.e RMAN should take the backup and delete the old bacup.
Will it work if i change the retention policy to 0 ?
RUN
ALLOCATE CHANNEL ch1 DEVICE TYPE DISK;
ALLOCATE CHANNEL ch2 DEVICE TYPE DISK;
ALLOCATE CHANNEL ch3 DEVICE TYPE DISK;
DELETE NOPROMPT OBSOLETE;
BACKUP DATABASE INCLUDE CURRENT CONTROLFILE format 'G:\Oracle\flash_recovery_area\BACKUPSET\tmp\rman_backup\df_%d_%s_%p_%T';
SQL "ALTER SYSTEM ARCHIVE LOG CURRENT";
BACKUP ARCHIVELOG ALL DELETE INPUT format 'G:\Oracle\flash_recovery_area\BACKUPSET\tmp\rman_backup\df_%d_%s_%p_%T';
RMAN> show all
2> ;
using target database control file instead of recovery catalog
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
CONFIGURE BACKUP OPTIMIZATION OFF; # defaultEdited by: user10243788 on Apr 24, 2012 1:14 AMuser10243788 wrote:
Our database is 11g R2, below is our RMAN script
Presently our retention policy is 1, so 1 backup is retained along with the current backup.
I Just want to have 1 backup, i.e RMAN should take the backup and delete the old bacup.
Will it work if i change the retention policy to 0 ?You cannot set the retention policy to redundancy 0 because redundancy count must be greater than zero.
>
RUN
ALLOCATE CHANNEL ch1 DEVICE TYPE DISK;
ALLOCATE CHANNEL ch2 DEVICE TYPE DISK;
ALLOCATE CHANNEL ch3 DEVICE TYPE DISK;
DELETE NOPROMPT OBSOLETE;
BACKUP DATABASE INCLUDE CURRENT CONTROLFILE format 'G:\Oracle\flash_recovery_area\BACKUPSET\tmp\rman_backup\df_%d_%s_%p_%T';
SQL "ALTER SYSTEM ARCHIVE LOG CURRENT";
BACKUP ARCHIVELOG ALL DELETE INPUT format 'G:\Oracle\flash_recovery_area\BACKUPSET\tmp\rman_backup\df_%d_%s_%p_%T';
}Just switch the order of operation:
use
BACKUP DATABASE INCLUDE CURRENT CONTROLFILE format 'G:\Oracle\flash_recovery_area\BACKUPSET\tmp\rman_backup\df_%d_%s_%p_%T';
DELETE NOPROMPT OBSOLETE;
instead of
DELETE NOPROMPT OBSOLETE;
BACKUP DATABASE INCLUDE CURRENT CONTROLFILE format 'G:\Oracle\flash_recovery_area\BACKUPSET\tmp\rman_backup\df_%d_%s_%p_%T';
You can also exclude the operation SQL "ALTER SYSTEM ARCHIVE LOG CURRENT" because BACKUP ARCHIVELOG ALL implicitly switch logfile before archiving. -
Retention policy and deletion of archived files
hello, I 'am a novice DBA having a backup question.
Our retention policy is set to 14 days; weekly we have full database backup; daily we have an incremental backup.
See scripts below.
The drive "\\is003s012\rhea\rman" where the backup files reside has files older than 2 months.
I expected these files to be deleted already by rman.
I can't find the cause why these files are not removed.
The database backup jobs are running fine ; logs file do not contain any errors and once and a while you see that rman removes obsolete files.
list expired / report obsolete do not return any files.
thanks for the assistance
chris
================= full db
c$rman_script="backup incremental level 0 cumulative device type disk tag '%TAG' database;
backup device type disk tag '%TAG' archivelog all not backed up delete all input;
allocate channel for maintenance type disk;
delete noprompt obsolete device type disk;
release channel;
&br_save_agent_env();
&br_prebackup($l_db_connect_string, $l_is_cold_backup, $l_use_rcvcat, $l_db_10_or_higher, $l_backup_strategy, "TRUE");
my $result = &br_backup();
exit($result);
================ incr db
$rman_script="backup incremental level 1 cumulative device type disk tag '%TAG' database;
recover copy of database;
backup device type disk tag '%TAG' archivelog all not backed up delete all input;
allocate channel for maintenance type disk;
delete noprompt obsolete device type disk;
release channel;
&br_save_agent_env();
&br_prebackup($l_db_connect_string, $l_is_cold_backup, $l_use_rcvcat, $l_db_10_or_higher, $l_backup_strategy, "TRUE");
my $result = &br_backup();
exit($result);
================== rman setting
RMAN> show all;
RMAN configuration parameters for database with db_unique_name RHEA are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 14 DAYS;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '\\is003s012\rhea\rman\%F';
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 CHANNEL DEVICE TYPE DISK FORMAT '\\is003s012\rhea\rman\%U';
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 ARCHIVELOG DELETION POLICY TO BACKED UP 1 TIMES TO 'SBT_TAPE';
CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'D:\ORACLE\PRODUCT\11.2.0\DBHOME_1\DATABASE\SNCFRHEA.ORA'; # defaultChris,
Thanks for the info; my current setting for this parameter:
SQL> show parameter CONTROL_FILE_RECORD_KEEP_TIME;
NAME TYPE VALUE
control_file_record_keep_time integer 7
I found another thread that elaborated on this: Re: CONTROL_FILE_RECORD_KEEP_TIME vs Retention Policy in RMAN
a) RMAN Retention Policy set to recovery window of 30 days means backups and archivelogs that you need to do a Point in Time Recovery to before 30 days do not get obsolete.
b) CONTROLFILE_RECORD_KEEP_TIME=7 will keep (potentially, if space pressure in the controlfile) the records of these files for only 7 days
Effect: Your old backups and archivelogs (+7 days) are no longer known by the system and will not get deleted (automatically or by delete obsolete) and your recovery area/backup location/archive destination will get filled up with old files.
Therefore set b) > a)
Based on this I changed the parameter:
alter system set CONTROL_FILE_RECORD_KEEP_TIME=35 scope=both;
Even tho the 'stale' backupsets are still invisible (still getting 'no obsolete backups found' when doing REPORT OBSOLETE), I guess that's because it will take a while (23 days?) for the CONTROL_FILE_RECORD_KEEP to catch up to the RMAN Retention Policy of 30 days)....
Barry -
RMAN Backups with retention policy to redundancy 1 doesn't work fine.
Hi experts,
I have a Oracle database with the following system backups:
Monday: ArchiveLog Backup
Tuesday: Full Backup
Wednesday: ArchiveLog Backup
Thursday: ArchiveLog Backup
Friday : Full Backup
Saturday: ArchiveLog Backup
Sunday: ArchiveLog Backup
ArchiveLog Backup = backup tag 'ARCHIVELOG_BACKUP' device type disk archivelog all not backed up delete all input;
Full Backup = backup tag 'FULL_BACKUP' device type disk database skip readonly plus archivelog tag 'FULL_BACKUP_ARCHIVELOGS';
crosscheck backup;
crosscheck copy;
delete noprompt obsolete;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 8;
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 ARCHIVELOG DELETION POLICY TO NONE; # default
What this system has done until last two weeks? For example:
Tuesday : Full Backup
Wednesday: ArchiveLog Backup
Thursday: ArchiveLog Backup
Friday : Full Backup - > After that, Full backup from Tuesday and ArchiveLog backups from Wed, and Thurs, are deleted. (Thanks to Retention policy) .
What this system do now?
Tuesday : Full Backup
Wednesday: ArchiveLog Backup
Thursday: ArchiveLog Backup
Friday : Full Backup - > After that, Full backup from Tuesday are deleted but not ArchiveLog backups from Wed, and Thurs.
When I execute a crosscheck on RMAN return that all are AVAILABLE.
My question is: What is right? The system backups before or after?
Thanks for your help!You are confused about the purpose of crosscheck.
There are two concepts for which you must grasp the distinction.
- Expired
- Obsolete
Expired
When an archive log is written, or rman makes a backup, a record of that archivelog or backupset is written to the repository in the control file.
Crosscheck simply checks the existence of the archivelogs or backupsets that are recorded in the repository. If something went missing (say, if you used an OS command to delete archivelogs), the record of the missing file is marked as 'expired'. If you follow the crosscheck command with a 'delete expired' command, the repository records that have been marked 'expired' are deleted from the repository, so rman has no more memory of those files. Note that 'expired' has nothing to do with retention policy. Also note that if you do not actually issue the 'delete expired' command, the expired records will remain in the repository.
Obsolete
The retention policy deals with when a backupset is obsolete, meaning it is no longer needed to protect the retention period. Backupset are not marked as obsolete. They are evaluated for obsolescence at the time of a command that needs it -- "report obsolete" or "delete obsolete", or when FRA maintenance requires an implied 'delete obsolete'. -
Total lock-ups with fan running - translate system.log file please!?
Hi, all. My late 2005 2.3 gig dual G5 has been experiencing random lock ups for as long as I can remember. My system is up to date and I have tested each pair of the 5 gigs of ram that I have and the system freezes with each pair. It can happen at any time, when I am doing absolutely nothing, for example, overnight. I am at my wits end!
Here's the system log file for the latest freezes. Can anyone tell me what's going on here??? I really need to get to the root of this problem. Thanks so so much in advance.
Apr 12 17:32:52 Marc-Weinbergs-Computer kernel[0]: AFP_VFS afpfs_Reconnect: connect on /Volumes/Macintosh HD failed 89.
Apr 12 17:32:52 Marc-Weinbergs-Computer kernel[0]: AFP_VFS afpfs_unmount: /Volumes/Macintosh HD, flags 524288, pid 62
Apr 12 17:44:46 Marc-Weinbergs-Computer /Library/Application Support/FLEXnet Publisher/Service/11.03.005/FNPLicensingService: Started\n
Apr 12 17:44:46 Marc-Weinbergs-Computer /Library/Application Support/FLEXnet Publisher/Service/11.03.005/FNPLicensingService: This service performs licensing functions on behalf of FLEXnet enabled products.\n
Apr 12 18:01:06 Marc-Weinbergs-Computer KernelEventAgent[62]: tid 00000000 received unknown event (256)
Apr 12 18:01:49 Marc-Weinbergs-Computer KernelEventAgent[62]: tid 00000000 received unknown event (256)
Apr 12 18:08:29 Marc-Weinbergs-Computer diskarbitrationd[69]: SDCopy [1056]:36091 not responding.
Apr 12 18:16:18 Marc-Weinbergs-Computer KernelEventAgent[62]: tid 00000000 received unknown event (256)
Apr 12 18:16:53 Marc-Weinbergs-Computer KernelEventAgent[62]: tid 00000000 received unknown event (256)
Apr 12 19:24:12 Marc-Weinbergs-Computer ntpd[191]: time reset -0.650307 s
Apr 13 01:05:45 Marc-Weinbergs-Computer ntpd[191]: time reset -0.496917 s
Apr 13 03:15:03 Marc-Weinbergs-Computer cp: error processing extended attributes: Operation not permitted
Apr 13 07:15:03 Marc-Weinbergs-Computer postfix/postqueue[1778]: warning: Mail system is down -- accessing queue directly
Apr 13 03:15:03 Marc-Weinbergs-Computer cp: error processing extended attributes: Operation not permitted
Apr 13 15:53:53 Marc-Weinbergs-Computer KernelEventAgent[62]: tid 00000000 received unknown event (256)
Apr 13 15:53:54 Marc-Weinbergs-Computer KernelEventAgent[62]: tid 00000000 received unknown event (256)
Apr 13 22:15:48 localhost kernel[0]: standard timeslicing quantum is 10000 us
Apr 13 22:15:47 localhost mDNSResponder-108.6 (Jul 19 2007 11: 33:32)[63]: starting
Apr 13 22:15:48 localhost kernel[0]: vmpagebootstrap: 506550 free pages
Apr 13 22:15:47 localhost memberd[70]: memberd starting up
Apr 13 22:15:49 localhost kernel[0]: migtable_maxdispl = 70
Apr 13 22:15:49 localhost kernel[0]: Added extension "com.firmtek.driver.FTATASil3132E" from archive.
Apr 13 22:15:49 localhost kernel[0]: Added extension "com.firmtek.driver.Sil3112DeviceNub" from archive.
Apr 13 22:15:49 localhost kernel[0]: Copyright (c) 1982, 1986, 1989, 1991, 1993
Apr 13 22:15:49 localhost kernel[0]: The Regents of the University of California. All rights reserved.
Apr 13 22:15:49 localhost kernel[0]: using 5242 buffer headers and 4096 cluster IO buffer headers
Apr 13 22:15:49 localhost kernel[0]: AppleKauaiATA shasta-ata features enabled
Apr 13 22:15:49 localhost kernel[0]: DART enabled
Apr 13 22:15:47 localhost DirectoryService[75]: Launched version 2.1 (v353.6)
Apr 13 22:15:49 localhost kernel[0]: FireWire (OHCI) Apple ID 52 built-in now active, GUID 001451ff fe1b4c7e; max speed s800.
Apr 13 22:15:49 localhost kernel[0]: USBF: 20.590 OHCI driver: OHCIRootHubPortPower bit not sticking (1). Retrying.
Apr 13 22:15:49 localhost kernel[0]: USBF: 20.590 OHCI driver: OHCIRootHubPortPower bit not sticking (1). Retrying.
Apr 13 22:15:49 localhost kernel[0]: USBF: 20.590 OHCI driver: OHCIRootHubPortPower bit not sticking (1). Retrying.
Apr 13 22:15:49 localhost kernel[0]: USBF: 20.590 OHCI driver: OHCIRootHubPortPower bit not sticking (1). Retrying.
Apr 13 22:15:49 localhost kernel[0]: USBF: 20.590 OHCI driver: OHCIRootHubPortPower bit not sticking (1). Retrying.
Apr 13 22:15:49 localhost kernel[0]: USBF: 20.590 OHCI driver: OHCIRootHubPortPower bit not sticking (1). Retrying.
Apr 13 22:15:49 localhost kernel[0]: USBF: 20.590 OHCI driver: OHCIRootHubPortPower bit not sticking (1). Retrying.
Apr 13 22:15:49 localhost kernel[0]: USBF: 20.590 OHCI driver: OHCIRootHubPortPower bit not sticking (1). Retrying.
Apr 13 22:15:49 localhost kernel[0]: USBF: 20.590 OHCI driver: OHCIRootHubPortPower bit not sticking (1). Retrying.
Apr 13 22:15:48 localhost lookupd[71]: lookupd (version 369.5) starting - Sun Apr 13 22:15:48 2008
Apr 13 22:15:49 localhost kernel[0]: USBF: 20.590 OHCI driver: OHCIRootHubPortPower bit not sticking (1). Retrying.
Apr 13 22:15:49 localhost kernel[0]: Extension "com.microsoft.driver.MicrosoftKeyboardUSB" has no kernel dependency.
Apr 13 22:15:49 localhost kernel[0]: AppleSMUparent::clientNotifyData nobody registed for 0x40
Apr 13 22:15:49 localhost kernel[0]: Security auditing service present
Apr 13 22:15:49 localhost kernel[0]: BSM auditing present
Apr 13 22:15:49 localhost kernel[0]: disabled
Apr 13 22:15:49 localhost kernel[0]: rooting via boot-uuid from /chosen: 82827EDF-0263-3B93-BEED-4B114E820B85
Apr 13 22:15:49 localhost kernel[0]: Waiting on <dict ID="0"><key>IOProviderClass</key><string ID="1">IOResources</string><key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict>
Apr 13 22:15:49 localhost kernel[0]: Got boot device = IOService:/MacRISC4PE/ht@0,f2000000/AppleMacRiscHT/pci@9/IOPCI2PCIBridge/k2-sat a-root@C/AppleK2SATARoot/k2-sata@0/AppleK2SATA/ATADeviceNub@0/IOATABlockStorageD river/IOATABlockStorageDevice/IOBlockStorageDriver/ST3320620AS Media/IOApplePartitionScheme/AppleHFS_Untitled1@10
Apr 13 22:15:49 localhost kernel[0]: BSD root: disk0s10, major 14, minor 12
Apr 13 22:15:49 localhost kernel[0]: jnl: replay_journal: from: 8451584 to: 11420160 (joffset 0x952000)
Apr 13 22:15:50 localhost kernel[0]: AppleSMU -- shutdown cause = 3
Apr 13 22:15:50 localhost kernel[0]: AppleSMU::PMU vers = 0x000d00a0, SPU vers = 0x67, SDB vers = 0x01,
Apr 13 22:15:50 localhost kernel[0]: HFS: Removed 8 orphaned unlinked files
Apr 13 22:15:50 localhost kernel[0]: Jettisoning kernel linker.
Apr 13 22:15:50 localhost kernel[0]: Resetting IOCatalogue.
Apr 13 22:15:50 localhost kernel[0]: Matching service count = 1
Apr 13 22:15:50 localhost kernel[0]: Matching service count = 1
Apr 13 22:15:50 localhost kernel[0]: Matching service count = 1
Apr 13 22:15:50 localhost kernel[0]: Matching service count = 1
Apr 13 22:15:50 localhost kernel[0]: Matching service count = 1
Apr 13 22:15:50 localhost kernel[0]: Matching service count = 3
Apr 13 22:15:50 localhost kernel[0]: NVDANV40HAL loaded and registered.
Apr 13 22:15:50 localhost kernel[0]: PowerMac112ThermalProfile::start 1
Apr 13 22:15:50 localhost kernel[0]: PowerMac112ThermalProfile::end 1
Apr 13 22:15:50 localhost kernel[0]: SMUNeo2PlatformPlugin::initThermalProfile - entry
Apr 13 22:15:50 localhost kernel[0]: SMUNeo2PlatformPlugin::initThermalProfile - calling adjust
Apr 13 22:15:50 localhost kernel[0]: PowerMac112ThermalProfile::adjustThermalProfile start
Apr 13 22:15:50 localhost kernel[0]: IPv6 packet filtering initialized, default to accept, logging disabled
Apr 13 22:15:50 localhost kernel[0]: BCM5701Enet: Ethernet address 00:14:51:61:ee:78
Apr 13 22:15:50 localhost kernel[0]: BCM5701Enet: Ethernet address 00:14:51:61:ee:79
Apr 13 22:15:51 localhost lookupd[86]: lookupd (version 369.5) starting - Sun Apr 13 22:15:51 2008
Apr 13 22:15:51 localhost kernel[0]: jnl: replay_journal: from: 21611008 to: 7857152 (joffset 0x952000)
Apr 13 22:15:51 localhost kernel[0]: jnl: replay_journal: from: 673280 to: 24382976 (joffset 0x952000)
Apr 13 22:15:51 localhost kernel[0]: jnl: replay_journal: from: 3890176 to: 6294016 (joffset 0x7d01000)
Apr 13 22:15:51 localhost diskarbitrationd[69]: disk0s10 hfs 82827EDF-0263-3B93-BEED-4B114E820B85 NewestSeagate /
Apr 13 22:15:52 localhost kernel[0]: NVDA,Display-A: vram [90020000:10000000]
Apr 13 22:15:52 localhost mDNSResponder: Adding browse domain local.
Apr 13 22:15:53 localhost kernel[0]: hfs mount: enabling extended security on Maxtor
Apr 13 22:15:53 localhost diskarbitrationd[69]: disk1s3 hfs 0DBE2113-B1F5-388F-BF70-2E366A095330 Maxtor /Volumes/Maxtor
Apr 13 22:15:54 localhost kernel[0]: NVDA,Display-B: vram [94000000:08000000]
Apr 13 22:15:54 Marc-Weinbergs-Computer configd[67]: setting hostname to "Marc-Weinbergs-Computer.local"
Apr 13 22:15:54 Marc-Weinbergs-Computer /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow: Login Window Application Started
Apr 13 22:15:56 Marc-Weinbergs-Computer diskarbitrationd[69]: disk2s3 hfs 971CABB3-C211-38FC-8E91-6B4F8EA5FA20 B08-09-07 /Volumes/B08-09-07
Apr 13 22:15:56 Marc-Weinbergs-Computer loginwindow[110]: Login Window Started Security Agent
Apr 13 22:15:57 Marc-Weinbergs-Computer kernel[0]: AppleBCM5701Ethernet - en1 link active, 1000-Mbit, full duplex, symmetric flow control enabled
Apr 13 22:15:57 Marc-Weinbergs-Computer configd[67]: AppleTalk startup
Apr 13 22:15:57 Marc-Weinbergs-Computer TabletDriver[119]: #### GetFrontProcess failed to get front process (-600)
Apr 13 22:15:59 Marc-Weinbergs-Computer configd[67]: posting notification com.apple.system.config.network_change
Apr 13 22:16:00 Marc-Weinbergs-Computer configd[67]: posting notification com.apple.system.config.network_change
Apr 13 22:16:00 Marc-Weinbergs-Computer configd[67]: executing /System/Library/SystemConfiguration/Kicker.bundle/Contents/Resources/enable-net work
Apr 13 22:16:00 Marc-Weinbergs-Computer configd[67]: posting notification com.apple.system.config.network_change
Apr 13 22:16:01 Marc-Weinbergs-Computer lookupd[123]: lookupd (version 369.5) starting - Sun Apr 13 22:16:01 2008
Apr 13 22:16:01 Marc-Weinbergs-Computer kernel[0]: HFS: Removed 2 orphaned unlinked files
Apr 13 22:16:01 Marc-Weinbergs-Computer diskarbitrationd[69]: disk3s3 hfs CDA8BCC5-0CE4-33E8-A910-4B0952DBC230 FullBU-09-07 /Volumes/FullBU-09-07
Apr 13 22:16:04 Marc-Weinbergs-Computer configd[67]: target=enable-network: disabled
Apr 13 22:16:05 Marc-Weinbergs-Computer configd[67]: AppleTalk startup complete
Apr 13 22:16:09 Marc-Weinbergs-Computer TabletDriver[237]: #### GetFrontProcess failed to get front process (-600)
Apr 13 22:16:09 Marc-Weinbergs-Computer launchd[241]: com.wacom.wacomtablet: exited with exit code: 253
Apr 13 22:16:09 Marc-Weinbergs-Computer launchd[241]: com.wacom.wacomtablet: 9 more failures without living at least 60 seconds will cause job removal
Apr 13 22:16:29 Marc-Weinbergs-Computer /Applications/DiskWarrior.app/Contents/MacOS/DiskWarriorDaemon: [Sun Apr 13 22:16:28 EDT 2008] : ATA device 'ST3320620AS', serial number '6QF0L6LR', reports it is functioning at a temperature of 95.0F (35C) degrees.
Apr 13 22:16:29 Marc-Weinbergs-Computer /Applications/DiskWarrior.app/Contents/MacOS/DiskWarriorDaemon: [Sun Apr 13 22:16:28 EDT 2008] : Spare blocks for ATA device 'ST3320620AS', serial number '6QF0L6LR', appear to still be available. (Total Available: 36) (Use Attempts: 0)
Apr 13 22:16:29 Marc-Weinbergs-Computer /Applications/DiskWarrior.app/Contents/MacOS/DiskWarriorDaemon: [Sun Apr 13 22:16:29 EDT 2008] : ATA device 'ST3320620AS', serial number '6QF0LGS4', reports it is functioning at a temperature of 100.4F (38C) degrees.
Apr 13 22:16:29 Marc-Weinbergs-Computer /Applications/DiskWarrior.app/Contents/MacOS/DiskWarriorDaemon: [Sun Apr 13 22:16:29 EDT 2008] : Spare blocks for ATA device 'ST3320620AS', serial number '6QF0LGS4', appear to still be available. (Total Available: 36) (Use Attempts: 0)
Apr 13 22:16:29 Marc-Weinbergs-Computer /Applications/DiskWarrior.app/Contents/MacOS/DiskWarriorDaemon: [Sun Apr 13 22:16:29 EDT 2008] : ATA device 'ST3320620AS', serial number '9RV000FC', reports it is functioning at a temperature of 95.0F (35C) degrees.
Apr 13 22:16:29 Marc-Weinbergs-Computer /Applications/DiskWarrior.app/Contents/MacOS/DiskWarriorDaemon: [Sun Apr 13 22:16:29 EDT 2008] : Spare blocks for ATA device 'ST3320620AS', serial number '9RV000FC', appear to still be available. (Total Available: 36) (Use Attempts: 0)
Apr 13 22:16:29 Marc-Weinbergs-Computer /Applications/DiskWarrior.app/Contents/MacOS/DiskWarriorDaemon: [Sun Apr 13 22:16:29 EDT 2008] : ATA device 'Maxtor 6B300S0', serial number 'B6211G0H', reports it is functioning at a temperature of 89.6F (32C) degrees.
Apr 13 22:16:29 Marc-Weinbergs-Computer /Applications/DiskWarrior.app/Contents/MacOS/DiskWarriorDaemon: [Sun Apr 13 22:16:29 EDT 2008] : Spare blocks for ATA device 'Maxtor 6B300S0', serial number 'B6211G0H', appear to still be available. (Total Available: 63) (Use Attempts: 0)
Apr 13 22:16:54 Marc-Weinbergs-Computer /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder: _TIFFVSetField: tiff data provider: Invalid tag "Copyright" (not supported by codec).\n
Apr 13 22:16:54 Marc-Weinbergs-Computer /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder: _TIFFVSetField: tiff data provider: Invalid tag "Copyright" (not supported by codec).\n
etc.Hi-
The machine seems to be having trouble with loading certain drivers, but, as this isn't a crash log, and doesn't show the "hang-up" or freeze, it's hard to tell.
Noted possibilities are:
-Microsoft keyboard (possible USB power problem)
-firmtek driver (from archive) questionable due to the "archive" annotation
-Wacom tablet driver, causing system problems
Running in Safe mode without freezes would help to determine if one of these drivers is the problem.
Other possibilities are outdated drivers, or simply a need to reinstall the OS.
If unnecessary, removing the driver(s) would be a good idea.
External USB and Firewire devices are all suspect, should all be disconnected, revert to Apple keyboard, and test system performance. Adding one device at a time, and testing each will be necessary to clear each device.
I have experienced system trouble when a Wacom tablet was not connected, but the driver was left installed.
Disabling the driver from Startup items may be necessary to test without the Wacom tablet connected. -
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."
Maybe you are looking for
-
I am not getting my email verification for my icloud when I click icloud on my phone the screen is locked or something wont let me choose anything. its saying check my emil for verification but nothing is coming to my email
-
Apple's multicam workaround is bogus?
On Pogue's blog, Apple supposedly gave this as a workaround for multicam editing: Apple intends to restore this feature in an update, calling it "a top priority." Until it does, here's a stopgap facsimile of multicam editing: If you drag two clips in
-
Jdeveloper 11g web service - java.lang.NoClassDefFoundError
Hi, I've just installed JDeveloper 11 preview 3. I'd like to perform this http://www.oracle.com/technology/obe/obe11jdev/11/ws/ws.html tutorial, but when I test web service, I get java.lang.NoClassDefFoundError. Attached is the complete server log. D
-
Mass Cancellation of Confirmation
Hi Experts, Is there any transaction Code to do the Mass cancellation of the PM Orders Confirmations. Regards, Kavvya
-
Faulty/D.O.A. 60gb ipod photo? Please help
Re-posting my question/problem here as I posted in the "connecting to Windows" forum my mistake... Today I received my replacement iPod from Apple after my first one broke after just one month. Following the instructions that came with my replacement