PSE 11 incremental backup problems

Since upgrading to PSE 11, I have been unable to complete an incremental backup . Whenever incremental is selected, it does a full backup which is quite time consuming. The main photos are on an external 1tb drive and I backup to a 2 tb external drive. Any thoughts?

Hi,
That last statement of your worries me a little. If it is doing an incremental backup but actually copying everything then if you ever had to do a restore it will ask for the original full backup.
When you are starting off the incremental back, it should ask you for the new folder to backup to and for the folder containing the previous backup. Is it allowing you to enter both?
As a test, if you complete a backup and, before doing any changes to your catalog, start a new incremental backup to a new, empty folder, it should complete very quickly. Once a backup is started, I often open the folder that I'm backing up to in Windows explorer. I can then watch the progress by watching the item count going up.
Brian

Similar Messages

Catalog backup problems with PSE 11

Hi,
I'm having terrible problems trying to backup my catalog to an external hard drive.
My PC is running Windows 7 with 8 GB of internal memory. My external hard drive is formatted to FAT 32 and has 130GB of spare capacity. My catalog is 45GB.
I have previously backed up the the catalog without any problems but can't remember if I did this before I upgraded to PSE 11.
I initially tried doing a full backup but got an error part way through writing the 'breeze' data. Having read that the breeze data was only used for face recognition, I deleted the remaining breeze data files and tried again.
I then encountered a problem when writing some of my early .jpg files. I couldn't see any obvious problem with these but tried removing them and runnning the back up again.
This time it got a bit further but hung up on some .mpg files.
I removed all video files and tried again.
This time it got up to over 60% complete but it then hung up on some early files which had a 'description' 2002 rather than a straight date name to the file. I thought that there might be a problem with file names including ' 's ', so removed these and tried again.
I then tried running Catalog 'optimize' and 'repair' (I didn't tick 'the re-index visual similarity data').
I eventually got up to over 65% complete but couldn't get the backup to go past my 2007 files no matter what files I removed.
I then tried doing an incremental backup using a Catalog file that I had created in 2011. This backup failed with 'an error encountered while writing.....WaldoData\waldo.cache'
I now don't know what to try! Any suggestions would be greatly appreciated.
FYI, looking at the backup Catalog files that I have previously created, it appears that only the first contains all the images from whole catalog with an equal number of .xml files.
Two others which I created (which I can't remember were full or incremental backups) only have some of the images. I'm sure that this can't be right.
I presume that for an intial backup the .xml files should run from B0000001 to Bnnnnnnn; the .jpg/.mpg/ etc from Bnnnnnnn+1 to B 2(nnnnnnn) and that when one runs an incremental back up the new .xml files are added from B2(nnnnnnn)+1 to B2(nnnnnnnn)+(mmmm) and the image files continuing for a further (mmmm). Is this correct?
Otherwise what should one be seeing?
Regards
Mike

Thank you for your information about my problem with PSE 11. I have since tried the programme on 2 different computers and it works fine. Seems like the problem is with my computer although my old PSE 10 works okay. I'd appreciate any ideas about what could be wrong with my computer to cause my photos to break up into various segments which don't join together particularly when I move them into 'before and after horizontal' or '......vertical' and even when zooming them. ( HP Pavilion Elite) Vista Ultimate.
Regards,
Stervogel.

PSE 12.1 not seeing prior backup for incremental backup

I had the trial version of PSE 12 in place and did a prior backup less than a month ago. It is 309 GB.
I started having problems with the backup with the trial version so I purchased the license, downloaded the program again to reinstall, and did the update to 12.1.
Now, when I try to do an incremental backup, it does not see the prior backup file. I go to the exact spot where it is located. I can see the file when i use "my computer" to navigate to it.
The back up is going to an external drive. There is 1.2 TB free of the 3TB total on the external drive.
I have Windows 7 SP1, 32 bit.
Thank you in advance for your help!

Go to your username>library>preferences and delete:
com.adobe.PhotoshopElements.plist
Adobe Photoshop Elements 12 paths
Adobe Photoshop Elemetns 12 settings
and any lockfiles with the same names. That library is hidden in 10.7 and up. To see it, click the Go menu in the finder and hold down the Option key and it will appear below the little house for your user account. While you're in there go to the saved application states folder and delete any for PSE.

Can't make an incremental backup in PSE 10 Organizer

I don't understand why I can't make an incremental backup in PSE 10 Organizer. I made my first full backup to my external drive a week ago. Today I tried to make an incremental backup. After selecting Incremental Backup from the file menu, a new screen appears asking for the Backup Path, and so I entered (by selecting) the full path name on my external drive where I made my original backup. But, next, it wants to know the name of the "Previous Backup file." I have absolutely no idea what the program wants at this point. What particular file does it want me to enter as the "previous backup file"?? There are hundreds of files in my backup directory. The backup directly does have a file called "Backup.tly" which I entered, hoping that this is the file it wants, but then I get this error message: "I:\Pictures\Adobe\Backup.tly does not contain a backup set for the current catalog. Please locate the last backup you made for this catalog." What am I missing here?
Many thanks for your help,
Jeff

Hi Jeff
Once you have a full back up you can make incremental back ups but you need to follow a set routine. It’s not very intuitive.
Start by creating a new folder or label a new CD/DVD Disk - it’s best to use dates e.g. “PSE10 incr backup 2012-0104”
Press Ctrl+B and check Incremental, then click Next
Highlight your drive containing the last backup and click the bottom Browse button (previous back up file) then navigate to the TLY file and click open.
Click the Browse button above and navigate to your new folder “PSE10 incr backup 2012-0104”
Click Done.
If your full backup originally contained 500 images, the incremental backup will only contain changes since the last backup e.g. files B000501.jpg, B000502.jpg etc
If you ever have to do a complete restore you start with the TLY file from the latest incremental backup. The program automatically recognizes the number of incremental steps and you will be prompted to insert a disc or navigate to the appropriate drive.
Incremental backup’s are obviously much quicker to write to disk but I recommend that you periodically perform another full backup and delete any earlier backups.

Problem while appling incremental backup on standby 10.2.0.4

Hi,
While recovering incremental backup on standby database, we are facing problem.
Even though we have cataloged the backup we want to recover, when we issue "RMAN> recover database noredo;" recovery fails as rman tries to recover from the backup which are not avaliable on disk.
RMAN> recover database noredo;
Starting recover at 20-OCT-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=531 devtype=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: sid=530 devtype=DISK
allocated channel: ORA_DISK_3
channel ORA_DISK_3: sid=529 devtype=DISK
allocated channel: ORA_DISK_4
channel ORA_DISK_4: sid=528 devtype=DISK
channel ORA_DISK_1: starting incremental datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
destination for restore of datafile 00012: /u02/oradata/p1sipmdm/data/p1sipmdm_cmx_temp2.dbf
destination for restore of datafile 00013: /u05/oradata/p1sipmdm/index/p1sipmdm_cmx_indx3.dbf
destination for restore of datafile 00027: /u05/oradata/p1sipmdm/data/p1sipmdm_cmx_temp4.dbf
destination for restore of datafile 00042: /u01/oradata/p1sipmdm/index/p1sipmdm_cmx_indx9.dbf
destination for restore of datafile 00046: /u03/oradata/p1sipmdm/data/p1sipmdm_cmx_data19.dbf
destination for restore of datafile 00068: /u06/oradata/p1sipmdm/index/gnw_death_ors_x04.dbf
destination for restore of datafile 00076: /u07/oradata/p1sipmdm/data/p1sipmdm_cmx_data24.dbf
channel ORA_DISK_1: reading from backup piece /backup/rman_backup/p1sipmdm/qimouvjj_1_1
channel ORA_DISK_2: starting incremental datafile backupset restore
channel ORA_DISK_2: specifying datafile(s) to restore from backup set
destination for restore of datafile 00010: /u06/oradata/p1sipmdm/index/p1sipmdm_cmx_indx2.dbf
destination for restore of datafile 00022: /u07/oradata/p1sipmdm/data/p1sipmdm_cmx_data7.dbf
destination for restore of datafile 00025: /u03/oradata/p1sipmdm/data/p1sipmdm_cmx_temp3.dbf
destination for restore of datafile 00030: /u09/oradata/p1sipmdm/data/p1sipmdm_cmx_data10.dbf
destination for restore of datafile 00069: /u02/oradata/p1sipmdm/index/gnw_death_ors_x05.dbf
destination for restore of datafile 00083: /u08/oradata/p1sipmdm/data/system09.dbf
destination for restore of datafile 00086: /u08/oradata/p1sipmdm/data/gnw_producer01.dbf
channel ORA_DISK_2: reading from backup piece /backup/rman_backup/p1sipmdm/qmmov08s_1_1
channel ORA_DISK_3: starting incremental datafile backupset restore
channel ORA_DISK_3: specifying datafile(s) to restore from backup set
destination for restore of datafile 00006: /u02/oradata/p1sipmdm/data/p1sipmdm_cmx_data2.dbf
destination for restore of datafile 00009: /u05/oradata/p1sipmdm/index/p1sipmdm_cmx_indx1.dbf
destination for restore of datafile 00032: /u09/oradata/p1sipmdm/index/p1sipmdm_cmx_indx6.dbf
destination for restore of datafile 00067: /u03/oradata/p1sipmdm/index/gnw_death_ors_x03.dbf
destination for restore of datafile 00080: /u08/oradata/p1sipmdm/data/p1sipmdm_cmx_data27.dbf
channel ORA_DISK_3: reading from backup piece /backup/rman_backup/p1sipmdm/qkmov07b_1_1
channel ORA_DISK_4: starting incremental datafile backupset restore
channel ORA_DISK_4: specifying datafile(s) to restore from backup set
destination for restore of datafile 00020: /u07/oradata/p1sipmdm/data/p1sipmdm_mdm_data3.dbf
destination for restore of datafile 00072: /u01/oradata/p1sipmdm/data/docgen_data01.dbf
channel ORA_DISK_4: reading from backup piece /backup/rman_backup/p1sipmdm/qnmov0ev_1_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 10/20/2011 22:54:39
ORA-19870: error reading backup piece /backup/rman_backup/p1sipmdm/qimouvjj_1_1
ORA-19505: failed to identify file "/backup/rman_backup/p1sipmdm/qimouvjj_1_1"
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Actual files are located at /u07/oradata/p1sipmdm_bkp/ location .. when we issue list backup summary rman shows these backups that we want to use..
RMAN> list backups;
BS Key Type LV Size Device Type Elapsed Time Completion Time
11210 Incr 4.88G DISK 00:00:00 20-OCT-11
BP Key: 12907 Status: AVAILABLE Compressed: YES Tag: TAG20111020T101659
Piece Name: /u07/oradata/p1sipmdm_bkp/pmsipmdp_1empinlp_1_1
List of Datafiles in backup set 11210
File LV Type Ckp SCN Ckp Time Name
4 Incr 8428228181070 20-OCT-11 /u01/oradata/p1sipmdm/data/users01.dbf
7 Incr 8428228181070 20-OCT-11 /u03/oradata/p1sipmdm/data/p1sipmdm_cmx_data3.dbf
16 Incr 8428228181070 20-OCT-11 /u01/oradata/p1sipmdm/data/p1sipmdm_cmx_data6.dbf
18 Incr 8428228181070 20-OCT-11 /u06/oradata/p1sipmdm/data/p1sipmdm_mdm_data1.dbf
29 Incr 8428228181070 20-OCT-11 /u05/oradata/p1sipmdm/data/undotbs03.dbf
41 Incr 8428228181070 20-OCT-11 /u02/oradata/p1sipmdm/data/p1sipmdm_cmx_data15.dbf
79 Incr 8428228181070 20-OCT-11 /u06/oradata/p1sipmdm/data/p1sipmdm_cmx_data26.dbf
BS Key Type LV Size Device Type Elapsed Time Completion Time
11211 Incr 80.00K DISK 00:00:00 20-OCT-11
BP Key: 12908 Status: AVAILABLE Compressed: YES Tag: TAG20111020T101659
Piece Name: /u07/oradata/p1sipmdm_bkp/pmsipmdp_1impioai_1_1
SPFILE Included: Modification time: 20-OCT-11
please advice.
Regards,
Abhay.....

Hi,
Backups are cataloged and they are persent on te server but on another location.
BS Key Type LV Size Device Type Elapsed Time Completion Time
11210 Incr 4.88G DISK 00:00:00 20-OCT-11
BP Key: 12907 Status: AVAILABLE Compressed: YES Tag: TAG20111020T101659
Piece Name: /u07/oradata/p1sipmdm_bkp/pmsipmdp_1empinlp_1_1
List of Datafiles in backup set 11210
File LV Type Ckp SCN Ckp Time Name
4 Incr 8428228181070 20-OCT-11 /u01/oradata/p1sipmdm/data/users01.dbf
7 Incr 8428228181070 20-OCT-11 /u03/oradata/p1sipmdm/data/p1sipmdm_cmx_data3.dbf
16 Incr 8428228181070 20-OCT-11 /u01/oradata/p1sipmdm/data/p1sipmdm_cmx_data6.dbf
18 Incr 8428228181070 20-OCT-11 /u06/oradata/p1sipmdm/data/p1sipmdm_mdm_data1.dbf
29 Incr 8428228181070 20-OCT-11 /u05/oradata/p1sipmdm/data/undotbs03.dbf
41 Incr 8428228181070 20-OCT-11 /u02/oradata/p1sipmdm/data/p1sipmdm_cmx_data15.dbf
79 Incr 8428228181070 20-OCT-11 /u06/oradata/p1sipmdm/data/p1sipmdm_cmx_data26.dbf
BS Key Type LV Size Device Type Elapsed Time Completion Time
11211 Incr 80.00K DISK 00:00:00 20-OCT-11
BP Key: 12908 Status: AVAILABLE Compressed: YES Tag: TAG20111020T101659
Piece Name: /u07/oradata/p1sipmdm_bkp/pmsipmdp_1impioai_1_1
SPFILE Included: Modification time: 20-OCT-11

Incremental Backups Interface Problem???

Maybe it's just me, but doing a simple task like backing up (full / incremental) should be very simple, and I'm having a problem. I should be able to select a backup location (a preference), do a Full backup, then do an Incremental...as many as I want...and at some time I may want to do a Full backup again. But it seems it's much more complex than that...
Here's what I'm doing (obviously wrong):
I've done a Full backup on Drive D in some directory, say 'My Backup'. Fine, I think I have a Full backup.
Now later, I want to do an incremental, and I'm prompted to select a destination Drive (it's D), and then "chose browse to load your previous backup file."
OK, I browse to my D | My Backup directory (that's the previous and ONLY backup location), but I'm warned that a backup file already exists, and do I want to overwrite it. Huh???
An Incremental doesn't overwrite a Full Backup. What am I supposed to Browse to?
And what does "Load previous backup file to determine size" have anything to do with a simple need to create an incremental backup file?
Help hasn't helped. I'm missing something.
I'd really appreciate if anyone can tell me what I'm doing wrong. I obviously don't want to overwrite a Full backup with an Incremental.

See excellent answer in Technical side of the forum
Michael Sobieski, "Problem with Full - Incremental Backup in 5.0" #1, 19 Oct 2006 8:21 am

Apply problem after sync with incremental backup

Hello all,
I have primary as rac with 4 nodes and one physical (all have asm)
I made incremental backup to re-sync my primary with physical standby and when i tried to start DG process the shiping is working but apply not workin : check please :
THREAD#,Last Standby Seq Received
1,29598
2,22308
3,27230
4,21868
THREAD#,Last Standby Seq Applied
1,28634
2,21227
3,25780
4,21104
when i run apply command i see in alert log file this :
Media Recovery Waiting for thread 4 sequence 1
Fetching gap sequence in thread 4, gap sequence 1-100
Tue Apr 07 12:06:49 2015
FAL[client]: Failed to request gap sequence
GAP - thread 4 sequence 1-100
DBID 1722434320 branch 849356882
FAL[client]: All defined FAL servers have been attempted.
Check that the CONTROL_FILE_RECORD_KEEP_TIME initialization
parameter is defined to a value that's sufficiently large
enough to maintain adequate log switch information to resolve
archivelog gaps.
the system searching for gab started with seq 1 in node 4 !!!!
how can i deal with that please ??

Thanks Stefan , kindly find below the output for both primary and standby :
1- select NAME,RESETLOGS_CHANGE#, CHECKPOINT_CHANGE#,CONTROLFILE_CHANGE#,CURRENT_SCN,RECOVERY_TARGET_INCARNATION# from v$database
Primary :
ORACLE,925702,3231069178,3231935937,3231937322,2
Standby :
ORACLE,925702,3096376393,3096507373,3096507372,2
2- list incarnation
Primary :
List of Database Incarnations
DB Key Inc Key DB Name DB ID            STATUS Reset SCN Reset Time
1       1       ORACLE   1722434320       PARENT 1          24-AUG-13
2       2       ORACLE   1722434320       CURRENT 925702     04-JUN-14
Standby:
List of Database Incarnations
DB Key Inc Key DB Name DB ID            STATUS Reset SCN Reset Time
1       1       ORACLE   1722434320       PARENT 1          24-AUG-13
2       2       ORACLE   1722434320       CURRENT 925702     04-JUN-14
3- select FILE#,RESETLOGS_CHANGE#,RESETLOGS_TIME, CHECKPOINT_CHANGE#,CHECKPOINT_TIME from v$datafile_header;
FILE# RESETLOGS_CHANGE# RESETLOGS CHECKPOINT_CHANGE# CHECKPOIN
         1            925702 04-JUN-14         3231779881 08-APR-15
         2            925702 04-JUN-14         3231779881 08-APR-15
         3            925702 04-JUN-14         3231779881 08-APR-15
         4            925702 04-JUN-14         3231779881 08-APR-15
         5            925702 04-JUN-14         3231779881 08-APR-15
         6            925702 04-JUN-14         3231779881 08-APR-15
         7            925702 04-JUN-14         3231779881 08-APR-15
         8            925702 04-JUN-14         3231779881 08-APR-15
         9            925702 04-JUN-14         3231779881 08-APR-15
        10            925702 04-JUN-14         3231779881 08-APR-15
        11            925702 04-JUN-14         3231779881 08-APR-15
     FILE# RESETLOGS_CHANGE# RESETLOGS CHECKPOINT_CHANGE# CHECKPOIN
        12            925702 04-JUN-14         3231779881 08-APR-15
        13            925702 04-JUN-14         3231779881 08-APR-15
        14            925702 04-JUN-14         3231779881 08-APR-15
        15            925702 04-JUN-14         3231779881 08-APR-15
        16            925702 04-JUN-14         3231779881 08-APR-15
        17            925702 04-JUN-14         3231779881 08-APR-15
        18            925702 04-JUN-14         3231779881 08-APR-15
        19            925702 04-JUN-14         3231779881 08-APR-15
        20            925702 04-JUN-14         3231779881 08-APR-15
        21            925702 04-JUN-14         3231779881 08-APR-15
        22            925702 04-JUN-14         3231779881 08-APR-15
     FILE# RESETLOGS_CHANGE# RESETLOGS CHECKPOINT_CHANGE# CHECKPOIN
        23            925702 04-JUN-14         3231779881 08-APR-15
        24            925702 04-JUN-14         3231779881 08-APR-15
        25            925702 04-JUN-14         3231779881 08-APR-15
        26            925702 04-JUN-14         3231779881 08-APR-15
        27            925702 04-JUN-14         3231779881 08-APR-15
        28            925702 04-JUN-14         3231779881 08-APR-15
        29            925702 04-JUN-14         3231779881 08-APR-15
29 rows selected.
Standby:
FILE# RESETLOGS_CHANGE# RESETLOGS CHECKPOINT_CHANGE# CHECKPOIN
         1            925702 04-JUN-14         3065328471 25-MAR-15
         2            925702 04-JUN-14         3065328464 25-MAR-15
         3            925702 04-JUN-14         3065328464 25-MAR-15
         4            925702 04-JUN-14         3065328461 25-MAR-15
         5            925702 04-JUN-14         3065328471 25-MAR-15
         6            925702 04-JUN-14         3065328471 25-MAR-15
         7            925702 04-JUN-14         3065328461 25-MAR-15
         8            925702 04-JUN-14         3065328471 25-MAR-15
         9            925702 04-JUN-14            1016743 04-JUN-14
        10            925702 04-JUN-14            1020278 04-JUN-14
        11            925702 04-JUN-14            1020681 04-JUN-14
     FILE# RESETLOGS_CHANGE# RESETLOGS CHECKPOINT_CHANGE# CHECKPOIN
        12            925702 04-JUN-14            1021083 04-JUN-14
        13            925702 04-JUN-14            1021086 04-JUN-14
        14            925702 04-JUN-14            1021877 04-JUN-14
        15            925702 04-JUN-14            1021880 04-JUN-14
        16            925702 04-JUN-14            1021883 04-JUN-14
        17            925702 04-JUN-14            1021886 04-JUN-14
        18            925702 04-JUN-14            1031089 04-JUN-14
        19            925702 04-JUN-14            1031555 04-JUN-14
        20            925702 04-JUN-14            1032064 04-JUN-14
        21            925702 04-JUN-14            1032525 04-JUN-14
        22            925702 04-JUN-14            1032922 04-JUN-14
     FILE# RESETLOGS_CHANGE# RESETLOGS CHECKPOINT_CHANGE# CHECKPOIN
        23            925702 04-JUN-14            1033338 04-JUN-14
        24            925702 04-JUN-14            1033731 04-JUN-14
        25            925702 04-JUN-14            1034126 04-JUN-14
        26            925702 04-JUN-14           90283375 09-JUL-14
        27            925702 04-JUN-14           90291448 09-JUL-14
        28            925702 04-JUN-14         3065328471 25-MAR-15
        29            925702 04-JUN-14         3065328461 25-MAR-15
29 rows selected.
4- select name,CHECKPOINT_CHANGE#,CHECKPOINT_TIME, UNRECOVERABLE_CHANGE# ,UNRECOVERABLE_TIME from v$datafile
Prmairy :
NAME
CHECKPOINT_CHANGE#
CHECKPOINT_TIME
UNRECOVERABLE_CHANGE#
UNRECOVERABLE_TIME
+ASM_ORADATA/oracle/datafile/system.274.849356797
3232100160
04/08/2015 10:07:12
0
+ASM_ORADATA/oracle/datafile/sysaux.260.849356797
3232100160
04/08/2015 10:07:12
0
+ASM_ORADATA/oracle/datafile/undotbs1.263.849356799
3232100160
04/08/2015 10:07:12
0
+ASM_ORADATA/oracle/datafile/users.269.849356799
3232100160
04/08/2015 10:07:12
404,796,458
08/25/2014 22:36:50
+ASM_ORADATA/oracle/datafile/example.272.849356895
3232100160
04/08/2015 10:07:12
0
+ASM_ORADATA/oracle/datafile/undotbs2.262.849357043
3232100160
04/08/2015 10:07:12
0
+ASM_ORADATA/oracle/datafile/undotbs3.261.849357043
3232100160
04/08/2015 10:07:12
0
+ASM_ORADATA/oracle/datafile/undotbs4.267.849357045
3232100160
04/08/2015 10:07:12
0
+ASM_ORADATA/oracle/datafile/asd01.dbf
3232100160
04/08/2015 10:07:12
0
+ASM_ORADATA/oracle/datafile/dev01.dbf
3232100160
04/08/2015 10:07:12
0
+ASM_ORADATA/oracle/datafile/feed01.dbf
3232100160
04/08/2015 10:07:12
404,790,786
08/25/2014 22:36:42
+ASM_ORADATA/oracle/datafile/indx01.dbf
3232100160
04/08/2015 10:07:12
0
+ASM_ORADATA/oracle/datafile/indx02.dbf
3232100160
04/08/2015 10:07:12
0
+ASM_ORADATA/oracle/datafile/website01.dbf
3232100160
04/08/2015 10:07:12
0
+ASM_ORADATA/oracle/datafile/website02.dbf
3232100160
04/08/2015 10:07:12
0
+ASM_ORADATA/oracle/datafile/website03.dbf
3232100160
04/08/2015 10:07:12
0
+ASM_ORADATA/oracle/datafile/website04.dbf
3232100160
04/08/2015 10:07:12
0
+ASM_ORADATA/oracle/datafile/users01.dbf
3232100160
04/08/2015 10:07:12
404,796,505
08/25/2014 22:36:50
+ASM_ORADATA/oracle/datafile/users02.dbf
3232100160
04/08/2015 10:07:12
404,796,502
08/25/2014 22:36:50
+ASM_ORADATA/oracle/datafile/users03.dbf
3232100160
04/08/2015 10:07:12
404,796,499
08/25/2014 22:36:50
+ASM_ORADATA/oracle/datafile/users04.dbf
3232100160
04/08/2015 10:07:12
404,796,496
08/25/2014 22:36:50
+ASM_ORADATA/oracle/datafile/users05.dbf
3232100160
04/08/2015 10:07:12
404,796,493
08/25/2014 22:36:50
+ASM_ORADATA/oracle/datafile/users06.dbf
3232100160
04/08/2015 10:07:12
404,796,490
08/25/2014 22:36:50
+ASM_ORADATA/oracle/datafile/users07.dbf
3232100160
04/08/2015 10:07:12
404,796,487
08/25/2014 22:36:50
+ASM_ORADATA/oracle/datafile/users08.dbf
3232100160
04/08/2015 10:07:12
404,796,505
08/25/2014 22:36:50
+ASM_ORADATA/oracle/datafile/feed02.dbf
3232100160
04/08/2015 10:07:12
134,340,010
07/16/2014 22:06:21
+ASM_ORADATA/oracle/datafile/indx03.dbf
3232100160
04/08/2015 10:07:12
0
+ASM_ORADATA/oracle/datafile/system_2_01
3232100160
04/08/2015 10:07:12
0
+ASM_ORADATA/catalog01
3232100160
04/08/2015 10:07:12
0
Standby :
NAME
CHECKPOINT_CHANGE#
CHECKPOINT_TIME
UNRECOVERABLE_CHANGE#
UNRECOVERABLE_TIME
+DATA/oracledrs/datafile/system.3248.875795981
3096432813
03/30/2015 07:55:21
0
+DATA/oracledrs/datafile/sysaux.3244.875796111
3096432814
03/30/2015 07:55:21
0
+DATA/oracledrs/datafile/undotbs1.3249.875796547
3096432814
03/30/2015 07:55:21
0
+DATA/oracledrs/datafile/users.3255.875796621
3096432811
03/30/2015 07:55:20
404,796,458
08/25/2014 22:36:50
+DATA/oracledrs/datafile/example.3258.875796817
3096432814
03/30/2015 07:55:21
0
+DATA/oracledrs/datafile/undotbs2.3256.875796823
3096432813
03/30/2015 07:55:21
0
+DATA/oracledrs/datafile/undotbs3.3253.875796869
3096432811
03/30/2015 07:55:20
0
+DATA/oracledrs/datafile/undotbs4.3247.875797223
3096432813
03/30/2015 07:55:21
0
+DATA/oracledrs/datafile/asd01.dbf
3096432813
03/30/2015 07:55:21
0
+DATA/oracledrs/datafile/dev01.dbf
3096432814
03/30/2015 07:55:21
0
+DATA/oracledrs/datafile/feed01.dbf
3096432813
03/30/2015 07:55:21
404,790,786
08/25/2014 22:36:42
+DATA/oracledrs/datafile/indx01.dbf
3096432803
03/30/2015 07:55:20
0
+DATA/oracledrs/datafile/indx02.dbf
3096432803
03/30/2015 07:55:20
0
+DATA/oracledrs/datafile/website01.dbf
3096432813
03/30/2015 07:55:21
0
+DATA/oracledrs/datafile/website02.dbf
3096432811
03/30/2015 07:55:20
0
+DATA/oracledrs/datafile/website03.dbf
3096432811
03/30/2015 07:55:20
0
+DATA/oracledrs/datafile/website04.dbf
3096432811
03/30/2015 07:55:20
0
+DATA/oracledrs/datafile/users01.dbf
3096432811
03/30/2015 07:55:20
404,796,505
08/25/2014 22:36:50
+DATA/oracledrs/datafile/users02.dbf
3096432803
03/30/2015 07:55:20
404,796,502
08/25/2014 22:36:50
+DATA/oracledrs/datafile/users03.dbf
3096432803
03/30/2015 07:55:20
404,796,499
08/25/2014 22:36:50
+DATA/oracledrs/datafile/users04.dbf
3096432814
03/30/2015 07:55:21
404,796,496
08/25/2014 22:36:50
+DATA/oracledrs/datafile/users05.dbf
3096432813
03/30/2015 07:55:21
404,796,493
08/25/2014 22:36:50
+DATA/oracledrs/datafile/users06.dbf
3096432803
03/30/2015 07:55:20
404,796,490
08/25/2014 22:36:50
+DATA/oracledrs/datafile/users07.dbf
3096432811
03/30/2015 07:55:20
404,796,487
08/25/2014 22:36:50
+DATA/oracledrs/datafile/users08.dbf
3096432814
03/30/2015 07:55:21
404,796,505
08/25/2014 22:36:50
+DATA/oracledrs/datafile/feed02.dbf
3096432813
03/30/2015 07:55:21
134,340,010
07/16/2014 22:06:21
+DATA/oracledrs/datafile/indx03.dbf
3096432814
03/30/2015 07:55:21
0
+DATA/oracledrs/datafile/system_2_01
3096432814
03/30/2015 07:55:21
0
+DATA/oracledrs/datafile/catalog.288.873258217
3096432811
03/30/2015 07:55:20
0
Thanks in advance,

Up graded from elements 9 to 11 tried to run incremental backup and keep getting error

I keep getting error c:\ program data\adobe\elements organize\catalogs\my catalog\catalog pse 11 db. any help on this issue would be great.

That's not one of Apple's better messages, unfortunately.
Most likely, there's a problem with a particular file, but they don't bother to tell you that.
See #C3 in Time Machine - Troubleshooting.
Also note that, on Leopard, the restored drive will be treated like a new one, and Time Machine will do a full backup of it. You cannot prevent that. But if you meant 10.6.8 (Snow Leopard), it probably will figure out what's happened and do only an "incremental" backup of the changes.

ACS 5.3 incremental backup error

Hi ,
I have ACS 5.3 that recently having problems with the incremental backup.
The error is : on demand back failed
and the details is: SQL Anywhere backup utility connection error: insufficient system resources- failed to allocate a SYSV semphorenull .
I mean come on.... and I did not find this error on cisco website.
The ADE.log file is not showing errors/details related to this. Atttached are the files showing the errors
Have anyone faced this problem before? Ideas? Anything?
Regards,
George

Hi George:
with 5.3 I experienced many issues including the incremental backup does not work. whenever I set it to "ON" next time the scheduled backup comes It fails and set itself back to "Off'. I did not get same message you get though.
I finally did two things:
- upgraded to latest patch.
- moved the log collector from the primary to the secondary.
Now things are fine for about 1 month without issues.
Regarding your issue, I think it could be related to resource issue as mentioned in the message.
What is the current DB size that you have?
Note that the message is misleading (messages I got with my ACS are the same) because they mention incremental backup in the message title and then say on-demand full backup failed!
So, you have to specify yourself if the issue with the incremental backup or the full backup?
HTH
Amjad
Rating useful replies is more useful than saying "Thank you"

Time Machine won't do incremental backups after I restored my computer

I am using a macbook (2010 version) and operating Lion. I had a problem with my Macbook where it wouldn't log on, even in safe mode, so I restored it using Timemachine. Now that everything is back up and running well I want to keep backing up. But Time Machine now says that there is not eneough space on the backup disk as it wants to back up the whole computer alongside the exisitng back up. In short it will no longer do incremental backups on top of what has already been backed up. I don't want to wipe my backup disk for fear that something might go wrong again and I may want to go back to a version earlier than the one I restored. Is there anyway of getting round this problem? It seems like a fairly serious problem.
I would appreciate any help.

ms364 wrote:
I am using a macbook (2010 version) and operating Lion. I had a problem with my Macbook where it wouldn't log on, even in safe mode, so I restored it using Timemachine.
When you erased the disk, it got a new UUID (Universally Unique IDentifier), which is treated like a different drive, and Time Machine will back it up in it's entirety.
Did you do a full system restore, starting from the Recovery HD? If so, that should have left a "trail" so Time Machine should have automatically "associated" the restored disk with the existing backups.
If you did it "piecemeal," though, via the "Star Wars" display, it won't (that doesn't leave the trail for TM to figure out what happened).
You might be able to get it to do the association manually. See #B6 in Time Machine - Troubleshooting.
But Linc is right; you apparently need a larger TM drive. See #1 in Time Machine - Frequently Asked Questions.

Incremental Backup possible with iPhoto '08?

Hi - I've always run a couple backup schemes for my iMac, and with iPhoto '08 it has become a lot more time intensive as the backup programs are now always replacing the entire iPhoto library in an incremental backup as opposed to incremental backup within the iPhoto folder (which was the case in iPhoto '06). Doesn't seem to be a problem for TimeMachine. But is a major issue for other programs I use (including Mozy, which has to upload 40GB everytime I add a photo to iPhoto, which is crazy!!; as well as syncing the library to an external drive and my MacBook).
Anyone have any ideas on how to solve this?
Thanks!!

Synk Standard does look inside the iPhoto Library package and backs up only those files that are new or have been changed. Most of my libraries can be incrementally backed up in less than 1 minute. My 29,000 file library takes 2.5 minutes, only 16 seconds if I've not rebooted since the last backup and using it's ZeroScan feature.
TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
I've created an Automator workflow application (requires Tiger), iPhoto dB File Backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. It's compatible with iPhoto 08 libraries and Leopard. iPhoto does not have to be closed to run the application, just idle. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.

Quesion about the Basic concept of RMAN incremental backup

I have a problem in understanding the basic concept of two types RMAN Incremental backup ie. Differential and Cumulative. I just don't understand how cumulative incremental backup consumes more space than Differential backup.
Have a look at the scenario in which Differential backup is used.
1. On Sunday midnight, a LEVEL0 backup is taken.
2. On Monday midnight all the blocks that was changed since Sunday midnight are stored in the backup media (tape or disk)
3. On Tuesday midnight all the blocks that was changed since monday midnight are stored in the backup media.
4. On Wednesday midnight, all the blocks that was changed since tuesday midnight are stored in the backup media.
At this point, in the backup media, you have all the changed blocks from sunday midnight to wednesday midnight eventhough it was stored in a daily basis. If you had taken a cumulative backup at wednesday midnight the backup media would have contained the same changed blocks from sunday midnight(LEVEL0) to wednesday midnight, but all at one go instead of daily basis. I don't understand how cumulative backup consumes more space when the backup media contains the same amount of changed blocks as it were in the case of the Differential backup.

Considering the Scenario you given:
Sunday : Level 0 backup.
Monday : You have taken an incremental backup then there will not be any difference in size of backup set for differential or cumulative as the changes from last Level0 backup are considered.
Tuesday : A cumulative backup (n-1) will have changed blocks since Sunday's Level0 backup but a differential backup(n) will only have changed blocks since Monday. So definitely there will be more space consumed by cumulative backups compared to differentials.
Hope it helps ...
Bhupinder

PSE 7 Backup Discrepancy

I'm running PSE 7 on Vista. Because my internal drive was full I moved all of my pictures to a clean external drive. The size of the folder is 300 GB. I then did a full backup to a second clean external drive but the size of that folder is only 218 GB. I then did an incremental backup but the size of the folder didn't really change. Does anyone have any thoughts or suggestions?

I have seen a couple of reports that files moved in PSE 6 and 7 left files disconnected.   Some more troubleshooting questions:
1.      When you did the move, did you use PSE’s File > Move or did you drag-and-drop folders in Display > Folder Location view?   The latter will move any other files that are in folders even if they’re not in the catalog, which could explain the difference between 300 and 218 GB.
2.      If you did File > Move, did you see any error messages? PSE 6 File > Move has a serious bug that will permanently delete a file if the destination folder has a file of the same name as that being moved. This situation is very likely to arise if you’re moving many files in many folders.   When a file gets permanently deleted, it will show up in the catalog as missing.
3.      Try File > Reconnect > All Missing again to verify no more files are missing.
4.      Count the total number of files in PSE backup folder on the backup drive.
5.      Count the number of files in your catalog, a little harder than it sounds, due to stacks, version sets, and other issues. Make sure all media types are checked in View > Media Types, and make sure Hidden Files > Show All Files is checked. Do Find > By Filename, and enter a nonsense string, e.g. “s;lkdaaeioqjfkekrjasdif”. Then click Options (to the right of Show All) and read out the number after Options > Show Results That Do Not Match – that’s the total number of files in your catalog.
If the numbers of files from steps 4 and 5 aren’t close, then that suggests there are files on the external drive that aren’t cataloged.

Incremental backup time query?

Database size = 270GB
Time taken for full level 0 backup = 50 minutes (Day 1)
Time taken for cumulative level 1 backup = 70 minutes (Day 2)
Time taken for differental level 1 backup = 55 minutes (Day 3)
My question is how come the incremental backup is taking more time than the full backup time?
Please advice.
Sami Malik
[email protected]

Sami Malik wrote:
Yes incremental backup is taken on the same time when there is heavy load on the system. For sure is this the reason? No, not for sure. We haven't seen enough info to say for sure, but given what we have been shown, it is a reasonable first guess. To know for sure, you need to do some actual performance analysis during both full and incremental backups and compare the two. STATSPACK is always a good place to start.
I will try the incremental backup at night when there is nobody connected.
Even though online backups can be taken anytime, it's always a good idea to schedule them during low-usage times.
But one more question when in case if there is a 24/7 system, then its no use of taking incremental backup right?Why would you think that? If your system is 24/7, that's even more reason to be taking incrementals. If you do have to perform a recovery, having incrementals will shorten your recovery time, vs. haveing to apply all archived redo back to the last full backup.
Also, you should be taking regular full backups as well. Most people take a full backup weekly, and an incremental on the other 6 days of the week.
As an additional thought .... while it is a curiosity that that your incremental took longer than the full and much could be learned by chasing it down, you always have to ask "is this a problem that needs to be solved?" If you schedule all backups (full and incremental) during low-use times, and the users do not notice any impact, do you really care if the incremental took longer than the full? On the other hand, it may not be a problem that "needs" to be solved, but running it down may reveal other problems that are impacting or have real potential to impact the business, and should be solved.

Incremental Backup using "imsbackup"

Dear every body,
I have a trouble and need the help from you, please help me in this case if you can, thanks.
I want to backup incrementally my mailboxes with "imsbackup" command. I have tested following below example but not succeeded:
1. I send/receive email between 2 users in my domain at 08:00AM.
2. I performed FULL backup the whole message store using imsbackup
3. At 09:00AM I send/receive another email between 2 users in my domain
4. I performed INCREMENTAL backup the whole message store using "imsbackup -d 20091217:083000....." but my backup file including the messages that I sent before 08:30AM
I have done this several times and get the same result.
Please kindly help me in this case, how can I use imsbackup to incrementally backup my mailboxes.
Any help and advices from you is appreciated.
Thanks all of you so much.
huynq

Hi Shane,
Thanks so much for your response.
The version of Messaging Server I am using is:
{color:#ff0000}bash-3.00# ./imsimta version
Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 9 2008){color}
For your question:
Does this problem occur if you incrementally back up a single mailbox e.g.
./imsbackup -d 20091217:083000 ... user/<uid>/
My Answer is:
I have not performed above step yet because I want to backup mailboxes of all users.
For your question:
Is the time/timezone set correctly on the server?
My answer is:
Yes, of courses. I already set time/timezone correctly. I also checked the time stamp of newly created email in message store in server, their date are correct.
For your question:
Are you in daylight savings time i.e. you shift the imsbackup incremental time back-forward an hour and get the correct result?
My answer is:
I already tried many times but got the same result. For example, At{color:#ff0000} 9AM Dec 16th 2009{color} I sent an email. At{color:#ff0000} 9AM one day later (Dec 17th 2009){color} I sent another email. I performed incremental backup using{color:#ff0000} "./imsbackup -d 20091216:120000 -f- / > /email_backup/incremental.120000".{color}
The backup file I got contained the email I sent at 9AM Dec 16th.
Any advice on this ?
Anyway, thanks so much for your help. I am awaiting your response.
huynq.

PSE 11 incremental backup problems

Similar Messages

Maybe you are looking for