Incrementally updated backup and EMC NMDA

Hello Everyone,
I'm kind of a newbie in setting up networker module for oracle, to backup database to tape. We use the oracle's suggested backup strategy to backup DB to Disk first using the incrementally updated backups with recovery set to 3 days (RECOVER COPY OF DATABASE WITH TAG ... UNTIL TIME 'SYSDATE-3') , which helps us to recover DB to any point in time using the backup files in disks vs. going to tape. After backup to disk, we backup recovery area to tape nightly. However, we do want to maintain backup Retention Policy of 1 month. Couple of questions,
1. If i set RP to recovery window of 31 days in RMAN, then backups don't obsolete at all. this forces me to set RP in networker and they don't recommend setting RP in both RMAN and networker. how is this done generally to obsolete backups from tape as well as rman (catalog in CF) with above strategy. perhaps in this case i should set RP in netwoker and set RP in RMAN to none and rely on crosscheck and delete expired commands to sync with RNAM catalog.
2. Wondering if nightly backup of recovery area to tape is going to take incremental from previous day and NOT full backup. The reason i ask is, i do not want the tape to do full backup of FRA every day cause full backup datafiles change once in 3 days based on the until time set. is there an option do set in networker to do incremental only or that's the default.
Thanks in Advance!
11gR2, 4 Node RAC, Linux, NMDA 1.1, Networker 7.6 sp1

Loic wrote:
You do a full backup of the FRA on tape ?No, I do a full backup of the database on tape. Using RMAN together with Veritas NetBackup.
I mean if you use incremental updated backup it'll not work on tape... Because the level 0 backup that will be updated with the backup of the day after will be on tape and will not be updated.The incrementally updated backup is in the FRA only, on disk (both the image copy and the following backup sets that are used for recovery of the image copy). Never gets written to tape or updated on tape.
Why don't you use then normal incremental backup ? That will have no problem with the tape backup even if level0, or level1,2 becomes reclaimable... ?I think I do :-)
Maybe:
To keep that you can put the redundancy to 2 out of 1 copy. Like this even with one copy on disk and tape it'll say keep the 2 copies.
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;I'll think about that.

Similar Messages

Differential Incremental Backup or Incrementally Updated Backup?

DB Version:11g
DB Size:450Gb
DB type: OLTP (storing retail warehouse transactions)
To implement a proper backup strategy, we are currently weighing the Pros and Cons of Differential Incremental Backup and Incrementally Updated Backup.
I understand that , for Incrementally Updated Backup , the level 0 backup must be stored in FRA. We don't want to configure FRA as of now.
Which backup strategy would you choose for a similair environment?

I don't think that 11g RMAN level 0 backup need to use FRA: can you provide us the link to Oracle doc ?
When designing your backup strategy you need to define:
RTO: recovery time objective
RPO: recovery point objective.
See http://download.oracle.com/docs/cd/B19306_01/server.102/b14210/hadesign.htm
To meet a low RTO objective, you may need to use incrementally updated backup because it should be faster to recover from incrementally updated backup compared to differential incremental backup.

Incrementally Updated Backups -- do you Backup to TAPE ?

Incrementally Updated Backups on disk provide
a. only a single image of the database
b. as of only a particular point in time (the last incremental update)
c. no protection against disk/storage failure as the backups are on the same server as the database
Your Incrementally Updated Backups should go to Tape or to another Disk Area on another server or Virtual Tape Library frequently.
You may find the need to "restore and recover the database as of 3 days ago OR as of the last critical processing date" which cannot be done if you incrementally update your backup every day.
A backup on disk doesn't protect you from disk failure.
Hemant K Chitale
http://hemantoracledba.blogspot.com

Look in the FAQ for SuperDuper at: <http://www.shirt-pocket.com/forums/showthread.php?t=3942&highlight=time+capsul e>
where you'll find a discussion of what you can do.

Concept about Incremental Updated backup

I am going through Backup portion of Oracle. However, I am not able to understand the concept about the incremental Updated backups, its advantages and disadvantages.
Can anyone here help me out to get my concept clear.
Thanks in advance .

916438 wrote:
I am going through Backup portion of Oracle. However, I am not able to understand the concept about the incremental Updated backups, its advantages and disadvantages.
Can anyone here help me out to get my concept clear.
Thanks in advance .http://docs.oracle.com/cd/E11882_01/backup.112/e10643/rcmsynta2011.htm#RCMRF111

Incremental RMAN backup and compression

Does RMAN compress the data for the incremental Level 0 and Level 1 backups. More specifically - Can I use Advanced compression if olny use incremental backups ?

you would use the comfigure command to use zlib which is does not compress as well as bzip2 which does not require the advanced compression option, but zlib does not consume as much cpu as bzip2.
now for the backup you have 2 options. you can configure backupsets to compress
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET ;
or it using table
CONFIGURE DEVICE TYPE sbt BACKUP TYPE TO COMPRESSED BACKUPSET ;
Then do you backups as backup sets
database
backup as backupset incremental level 1 tag hot_1_${DTE} DATABASE NOT BACKED UP SINCE TIME 'SYSDATE - .6';
archivelogs
backup as compressed backupset format '${INST_LOWER}_Archive_%d_%s_%p_%t' archivelog all not backed up 1 times ;

Incremental updated RMAN backup help 11gR2

Dear all,
My manager ask me to build RMAN scripts to backup the 11gr2 database in redhat Linux.
Any help how to achieve this using RMAN?
thank you

I am not asking you to write a script. I can write it by myself.
What I need to know:
1- Incremental level 0 is a must in my case or I can just use the command below and it does everything (Level 0 , level 1 and level 0 incrementally updated)
backup incremental level 1 for recover of copy tag 'ALL_BACKUP' database;
2- The TAG must be unique every week, or can be always "ALL_BACKUP" ?
3- Which retention period is adequate in my case? 8 days are ok ?
4- Should I update the CONTROL_FILE_RECORD_KEEP_TIME to more than 7 days?
thank you

Incremental Updates and PKCS7 Signatures

Hello, this is my first message in this forum and I thank you in advance for your help.
I am developing a component to countersign PDFs. I was able to place the first signature ok, but when a countersign it problems come.
The way I countersign the document (as i read in the document "Digital Signatures in the PDF Language") is:
I create an incremental update with the following information:
1* Catalog changes
2* Info object
3* Acroform changes
4* New Annotation
5* New signature.
6* xref section
7* Trailer
The new signature is computed on the whole document but the signature new itself.
After this, not only the new signature is invalid, the previous signature becomes invalid althout there is no change in the previous version. I only have to remove the incremental update to get first signature to be valid again.
Acrobat Reader shows next message:
Error during signature verification.
Unexpected byte range values defining scope of signed data.
Details: byte range of signature is invalid.
I have reviewed thouse ranges several times but i did not find any error. Can anyone help me?
I could post a (badly) countersigned file if that could help.
Thank in advance,
José

Hello again. First of all, thanks again for your help.
I don't want to abuse but I have another problem with signatures.
I have two ways two sign a PDF.
A) Load the PDF, add the signature fields, sign and save.
B) Load the PDF, add the signature as an incremental update, sign and save.
I would prefer to use always the second alternative but problems come when I use method B to countersign.
If I sign a PDF with method A and then countersign using method B, I have a correct PDF with two signatures.
http://www.igijon.com/personales/josepm/RPACTCENTROS.SIGNED.signed_B.rar
If I sign and countersign usign method B, acrobat just ignore the second signature as it was not there, although It is able to detect changes after first signature.
http://www.igijon.com/personales/josepm/RPACTCENTROS.SIGNED.signed.rar
The incremental update is done always the same way, somethink like this:
%%EOF
1 0 obj
<<
/Type /Catalog
/AcroForm 26 0 R
/PageMode /UseNone
/Pages 2 0 R
/ViewerPreferences <<
/FitWindow true
/NonFullScreenPageMode /UseNone
/PageLayout /SinglePage
>>
>>
endobj
24 0 obj
<<
/CreationDate (D:20070824132228+02'00')
/ModDate (D:20070824132233+02'00')
/Producer (Burke - Componente de Firma)
>>
endobj
8 0 obj
<<
/Type /Page
/Annots [ 25 0 R 32 0 R ]
/Contents [ 5 0 R ]
/Parent 2 0 R
/Resources 6 0 R
>>
endobj
26 0 obj
<<
/Fields [ 25 0 R 32 0 R ]
/SigFlags 3
>>
endobj
32 0 obj
<<
/Type /Annot
/Border [ 0.000000 0.000000 5.000000 ]
/F 4
/FT /Sig
/M (D:20070824132233+02'00')
/P 8 0 R
/Rect [ 407.000000 58.000000 457.000000 16.000000 ]
/Subtype /Widget
/T (ContraFirmo yo)
/V 33 0 R
>>
endobj
33 0 obj
<<
/Type /Sig
/ByteRange [ 0 230122 250124 438 ]
/ContactInfo (Sin contacto)
/Contents <308 ... 000>
/FT /Sig
/Filter /Adobe.PPKMS
/Location (ContraFirmo aquí)
/M (D:20070824132233+02'00')
/Name (ContraFirmo yo)
/Reason (ContraFirmo porque si)
/SubFilter /adbe.pkcs7.detached
>>
endobj
xref
0 2
0000000000 65535 f
0000229283 00000 n
8 1
0000229602 00000 n
24 1
0000229465 00000 n
26 1
0000229712 00000 n
32 2
0000229772 00000 n
0000229997 00000 n
trailer
<<
/Info 24 0 R
/Prev 228481
/Root 1 0 R
/Size 34
>>
startxref
250310
%%EOF
I have tried to detect the error with the Preflight function of Acrobat and with the "PDF Appraiser" with no results.
Thanks again for your help.

Reindexing and Incremental Update

Indexes can be scheduled,but I don't know they are scheduled for Reindexing or for Incremental Update.
If I want them to work as Incremental Update everyday and work as Reindexing everyweek, what do I have to do?

If you schedule, it will basically do an incremental update. As far as I know you can't schedule a reindex. Warning - doing a reindex deletes the index and starts again - so it will work your TREX very hard!
Paul

INCREMENTAL MERGE BACKUP & RECOVERY

INCREMENTAL MERGE BACKUP & RECOVERY
=====================================
1) 개요
RMAN을 이용하여 database의 Image copy를 Backup하고 그 Backup에 retention policy만큼의 Incremental Backup을 적용하여서 복구의 시간을 단축한 Backup의 방법입니다.
즉 retention policy에 설정되어있는 시간 전의 최후의 시간까지 Image Copy를 보장하는 방법이며 Disk Space는 Incremental Backup만 사용하는 방법보다는 Image Copy를 사용하는 것임으로 많이 소요됩니다.
물론 Backup & Recovery 정책에 따라서 Retention Policy를 Recovery Window나 Redundancy 2이상으로 설정할 수 있으나, Incremental Merge Backup & Recovery의 장점을 극대화 하기 위해서는 Redundancy 1 (Default)로 설정하는 것을 권해드립니다.
2) 장점
- Recovery 시에 최근 Incremental Backup의 정보들이 적용이 되어있기 때문에 최소한의 시간으로 Recovery 작업을 진행하실 수 있습니다. 물론 장점을 극대화 하시기 위해서는 Retention Policy를 redundancy 1로 설정해 주시길 권해드립니다.
- Datafile들의 Destination을 Backup된 Image Copy가 있는 곳으로 Switch 하여 Restore하는 시간을 단축하셔서 Recovery를 진행하실 수도 있으나 Recovery 후의 관리의 용이성을 위해 부득히한 경우를 재외하고는 권장하지 않습니다.
3) Syntax
- Backup
RMAN> BACKUP INCREMENTAL LEVEL 1
FOR RECOVER OF COPY
WITH TAG WEEKLY DATABASE;
위 명령어를 사용하시면 WEEKLY라는 Tag로 생성된 Copy가 없을 시에는 Image Copy를 Weekly라는 Tag로 구분하여 Backup을 받게 됩니다.
* 여기서 Copy라 함은 FOR RECOVER OF COPY라는 구문을 사용하여서 만든 Image Copy를 뜻합니다.
RMAN> RECOVER COPY OF DATABASE WITH TAG WEEKLY;
위 명령어를 사용하시면 현재 받았던 Incremental Backup을 Weekly라는 Tag를 가지고 있는 Database Copy에 적용을 하게 됩니다.
RMAN> Delete Obsolete;
위 명령어를 사용하시면 현재의 Image Copy에 적용된 Incremental Backup을 재외한 나머지 Incremental Backup들이 Delete됩니다.
-Recovery
RMAN> switch database to copy;
문제가 발생하셨을 때 위 명령어를 사용하시면 모든 datafile의 pointer들은 image backup copy를 바라보게 됨으로 Restore의 시간을 절약할 수 있습니다.
4) Retention Policy에 따른 Syntax 변화
* 기본적으로 INCREMENTAL MERGE BACKUP & RECOVERY의 장점인 Recovery 시간을 극대화 하기 위해서는 Retention Policy를 redundancy 1(Default)로 설정하시는 것을 권장해드립니다.
하지만 User가 Backup & Recovery 계획을 변경하여 retention policy를 recovery window 또는 redundancy 1 이상으로 설정해 주시면 Obsolete한 Backupset을 Delete하는 부분과 Backupset을 적용시키는 부분을 수정해 주셔야합니다.
- Recovery Window of 2
Recovery Window를 2일로 설정해 놓으시면 Backup시에는 똑같은 Syntax를 사용하실 수 있으나 Recover copy of database 명령어는 아래와 같이 바뀌어야 합니다.
RMAN> BACKUP INCREMENTAL LEVEL 1
FOR RECOVER OF COPY
WITH TAG WEEKLY DATABASE;
RMAN> RECOVER COPY OF DATABASE WITH TAG WEEKLY until time 'sysdate-2';
왜냐하면 retention policy에 마춰서 image copy도 2일전의 상태로 보관되어야하며 그에 따라서 2일동안의 Backupset들도 보관되어야하기 때문입니다. 만약 until time을 사용하지 않으시면 incremental backup들이 obsolete 상태로 안변하게 됩니다.
- Redundancy 2 이상
Redundancy 2이상으로 설정해 주시면 2개 이상의 Tag를 보관하는 효과로서 역시 예상대로 Obsolete로 안 변하는 현상이 발생됩니다.
DAY 1)
RMAN> BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG DAILY DATABASE;
-위와 같이 실행하시면 한개의 Database Copy (Tag DAILY)가 생성됩니다.
DAY 2)
RMAN> BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG DAILY DATABASE;
RMAN> BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG WEEKLY DATABASE;
-위와 같이 실행하시면 한개의 Database Copy (Tag WEEKLY)와 한개의 Backupset (Tag DAILY)가 생성됩니다.
DAY 3)
RMAN> BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG DAILY DATABASE;
RMAN> BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG WEEKLY DATABASE;
RMAN> BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG MONTHLY DATABASE;
-위와 같이 실행하시면 한개의 Database Copy (Tag MONTHLY)와 두개의 Backupset (Tag DAILY, Tag WEEKLY)가 생성됩니다.
DAY 4)
RMAN> Delete Obsolete;
- 위와 같이 실행하시면 DAILY Tag와 관련된 부분이 Delete 됩니다. (최신 2개의 Tag관련 Backup만 보관)
RMAN> Delete Obsolete redundancy 1
- 위와 같이 실행하시면 DAYLY Tag와 WEEKLY Tag 관련된 부분이 Delete 됩니다. (Redundancy 1로 설정한 것과 똑같은 효과)
Reference:
Article-ID: Note 351455.1
Title: Oracle Suggested Strategy & Backup Retention
Article-ID: Note 303861.1
Title: Incrementally Updated Backup In 10G
글 수정:
hunlee

I would always include an archivelog backup:
... with tag 'fullbackup’ database plus archivelog delete all input;
And at the end:
delete obsolete noprompt;
That delete incrmental backups already applied to the basic image copies.
Your configuration allows only limited point in time recoveries. As soon as an incremental backup is applied to the image copies, you cannot go back in time. To change this you can add a 'until time' clause, for example:
recover
copy of database
with tag 'fullbackup until time 'sysdate-11';
This creates a recovery window of 10 days, only image copies older than 10 days will be changed.
Werner

Backup and recovery questions

Hi,
I am a newbie in Oracle database 11g Release 11.2.0.1.0 and Oracle Linux and I have questions regarding backup and recovery.
I used the “Schedule Oracle-Suggested Backup” and have it run nightly to back up to local disk. In the Backup Setting, on the Retention Policy, I selected “Retain backup that are necessary for a recovery to any time within the specified number of days (point-in-time recovery) day = 7”
With the setting above, I checked the “Manage Current Backups” and I have many back sets for SPfiles, controlfiles, datafiles, and archivelogs for the last several days. However, for image copies, I have only one set and it get over write nightly. With the configuration above, is that true that I can only recover to any point in last 24 hours?
My goal is to be able to recover any “point-in-time” in the past 5 days, should I change my Retention Policy to “Retain at least the specified number of full backups for each datafile” to 5 backups (each full daily backup)? Please provide some advices. Thanks

By looking the following, it looks like by default its 24 hours but it depends upon the recovery window you choose.
Enterprise Manager makes it easy to set up an Oracle-suggested backup strategy for backups to disk that protects your data and provides efficient recoverability to any point in the a recovery window of your choosing. (In the simplest case, examined in this section, this window is 24 hours.) The Oracle-suggested strategy leverages Oracle's incremental backup and incrementally-updated backup features to provide faster backups than whole database backups, and faster recoverability than is possible through applying database changes from the archived log to your datafiles.
The Oracle-suggested backup strategy is based on creating an image copy of your database. This copy is rolled forward by means of incrementally updated backups. Oracle Enterprise Manager schedules RMAN backups jobs for you to run during the overnight hours.
For each datafile, the strategy calls for backups as follows:
At the beginning of day 1 of the strategy (the time the first scheduled job actually runs), an incremental level 0 datafile copy backup. It contains the datafile's contents at the beginning of day 1. In a restore-and-recovery scenario, the redo logs from day 1 can be used to recover to any point during day 1.
At the beginning of day 2, an incremental level 1 backup is created, containing the blocks changed during day 1. In a restore-and-recovery scenario, this incremental level 1 can be applied to quickly roll forward the level 0 backup to the beginning of day 2, and redo logs can be used to recover to any point during day 2.
At the beginning of each day n for days 3 and onwards, the level 1 backup from the beginning of day n-1 is applied to the level 0 backup. This brings the datafile copy to its state at the beginning of day n-1. Then, a new level 1 is created, containing the blocks changed during day n-1. In a restore-and-recovery scenario, this incremental level 1 can be applied to the datafile rolled forward on day n-1 to the beginning of day n, and redo logs can be used to recover the database to any point during day n.
The datafile copies used in the Oracle-suggested backup strategy are tagged with the tag ORA$OEM_LEVEL_0. The level 1 incremental backups for use in this strategy are created for use with datafile copies that are so labelled. You can safely implement other backup strategies without concern for interference from the backups for the Oracle suggested strategy.
There are also Oracle-suggested strategies that use tape backups along with disk backups, but those are beyond the scope of this chapter.

Does SAP support incremental/delta backups? if so which note describes it

I'm just about to test incremental/delta backups on udb 9.5 fp1. Now to my question:
Does SAP support incrmental/delta backups?
Is there a note, I couldnt get a hit on OSS
Are there any gotcha's? such as do I need to move read only tables to a new talbespace?
Any info on this is greatly appreciated.
Anke

Hi Anke,
You can specify whether you want to perform a full, incremental or incremental delta backup and the frequency via DB13 or the planning calender in DBACOCKPIT.
SAP Note 1269697 DB6: Backup Performance
should be of use to you and please also see our administration guide available at our main page
https://www.sdn.sap.com/irj/sdn/db6 under Administration. Specifically check the guide
"Data Recovery and High Availability Guide and Reference" mentioned in Chapter 8.3.5 Advanced Backup Techniques
There is not a specific SAP note relating to incremental/delta backups but they can be scheduled via DB13 and so, they are supported.
Regards,
Paul

Create Incremental Full Backup

Hey, I thought I created an incremental full backup with attached rman script.
But at the point of restoring the database it comes up, that I just have an incremental backup of the source database.
Whats wrong in my configuration ? I like to have a daily full backup of the database where just the changes to the full backup are backed up. But the backupfile should always be a full backup.
I am using 10gR2 Standard Edition
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
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 '/backup/app/control_%F';
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 1;
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 '/backup/app/LEVEL0_%u_%T';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/opt/oracle/product/10gR2/db_1/dbs/snapcf_db01.f'; # default
# Database RAC Logswitch
sql 'alter system archive log current';
# Fullbackup Database - Perform incremental level 0 backup
run {
BACKUP incremental level 0 format '/backup/app/%d_Level0_%T_%U' database PLUS ARCHIVELOG format '/backup/app/%d_A
rchivelog_%T_%U';
}

An Incremental Backup is a fresh backup of all the changes that have occurred in the database since the last backup.
Thus, a Level 1 Incremental Backup is a smaller backup than the preceding Level 0 Backup.
However, when you say :
I like to have a daily full backup of the database where just the changes to the full backup are backed up. But the backupfile should always be a full backup.You seem to want an Incrementally Updated Backup. That is a backup strategy where your Backup itself is updated.
I am not sure if this is available in the Standard Edition.
Here's documentation on Incrementally Updated Backups : at 4.4.3 Incrementally Updated Backups: Rolling Forward Image Copy Backups
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/bkup004.htm#sthref408
While this is the "normal" Incremental Backups : at 4.4 RMAN Incremental Backups
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/bkup004.htm#sthref383
Hemant K Chitale
http://hemantoracledba.blogspot.com

Updated to an iphone 4s from iphone 4. Did backup and sync but some apps have not been copied to the 4s although they do show up on the iphone4. How can I get my missing apps?

Updated to an iphone 4s from iphone 4. Did backup and sync but some apps have not been copied to the 4s although they do show up on the iphone4. How can I get my missing apps?

Download Past Purchases
http://support.apple.com/kb/HT2519
Log into iTunes using the account the Purchase was made with... Click on Buy... and a notice will come up saying you already have it... do you wish to download it again... Click Yes...

Not able to see ikm oracle incremental update and ikm oracle slowly changing dimensions under PHYSCIAL tab in odi 12c

not able to see ikm oracle incremental update and ikm oracle slowly changing dimensions under PHYSCIAL tab in odi 12c
But i'm able to see other IKM's please help me, how can i see them

Nope, It has not been altered.
COMPONENT NAME: LKM Oracle to Oracle (datapump)
COMPONENT VERSION: 11.1.2.3
AUTHOR: Oracle
COMPATIBILITY: ODI 11.1.2 and above
Description:
- Loading Knowledge Module
- Loads data from an Oracle Server to an Oracle Server using external tables in the datapump format.
- This module is recommended when developing interfaces between two Oracle servers when DBLINK is not an option.
- An External table definition is created on the source and target servers.
- When using this module on a journalized source table, the Journaling table is first updated to flag the records consumed and then cleaned from these records at the end of the interface.

Had a recent crash on my macbook, was previously using OS 10.6 I think. Restored from recent Time Machine backup and updated to OS 10.8.2 and now I cannot open Logic Pro 9. I get a 'No entry' Icon and a not supported on this type of Mac message. I cannot

Had a recent crash on my macbook, was previously using OS 10.6 I think. Restored from recent Time Machine backup and updated to OS 10.8.2 and now I cannot open Logic Pro 9. I get a 'No entry' Icon and a not supported on this type of Mac message. I cannot update either as anything up to 9.1.1 tells me I don't need it yet 9.1.2 tells me I need an eligable Logic Pro Version was not found in applications.
All of my files are stored in a separate hard drive with only the actual app having been on my Macbook. Should I just reinstall?

Hi
To run Mouitain Lion you need to update Logic.
For the updaters to work the Logic application must be:
a) Within the Applications folder, and not in any sub-folder
b) Named "Logic Pro" with no extra numbers or spaces
CCT

Incrementally updated backup and EMC NMDA

Similar Messages

Maybe you are looking for