Incremental backup SLOW

I'm using Time Machine to back up to an external drive (a sparsebundle on a drobo) and since upgrading to Snow Leopard, I've noticed it being ungodly slow. It's backing up much of the time, which is annoying because the computer as a whole is sluggish when it's backing up. According to the logs found through the TM Buddy widget, it backs up at a rate of roughly 1MB/minute. There are no indications of errors or anything off in the logs, but this obviously isn't how it should be.

Yes, there are some reports of trouble backing-up to Drobos. Search this forum (and/or the Leopard Time Machine forum); you may find something useful there.
If your backups seem to be too large considering how much you've changed, see #D4 Time Machine - Troubleshooting *User Tip* at the top of this forum.
If the size seems reasonable, but they're slow (as yours sure seem to be), see #D2 there.

Similar Messages

RMAN: Increment backup very slow

Hi All,
We have Datawarehouse database having size around 7TB. Increment backup performance is extremely poor it is taking approx 14hrs to complete the process. We have also enabled block change tracking but failed to meet target.
Below mentioned DB info & RMAN configuration parameters:
DB: 11.1.0.6
OS: Linux 2.6.18-128.el5 x86_64
System has 16 processor when more than two process per CPU i.e. 32
CONFIGURE RETENTION POLICY TO REDUNDANCY 5;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/d01copy/control_bkp/autobackup_control_file%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 13 BACKUP TYPE TO COMPRESSED BACKUPSET;
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 'BZIP2';
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.1.0/dbs/snapcf_PRODDB.f'; # default
Thanks in advance.

Thnaks for reply.
Have you configured Compressed backups?
--> Yes. with below command.
RMAN> backup as compressed backupset incremental level 1 tag=$v_tag database;
Have you allocated channels ?
--> Yes.
allocate channel backup_disk1 type disk format '$v_bdest/%U' maxpiecesize 10G;
allocate channel backup_disk2 type disk format '$v_bdest/%U' maxpiecesize 10G;
allocate channel backup_disk3 type disk format '$v_bdest/%U' maxpiecesize 10G;
allocate channel backup_disk4 type disk format '$v_bdest/%U' maxpiecesize 10G;
allocate channel backup_disk5 type disk format '$v_bdest/%U' maxpiecesize 10G;
What is the Large pool size configured? try to increase.
--> large_pool_size=1073741824
Is backup to DISK or TAPE? mentioned in script?
--> Backup goes to DISK only.
How is DISK performance?
--> How can we calculate DISK performance on LINUX?
Regards,

Oracle incremental backup too slow

Hello All,
Oracle 9.2.0.7
Windows 2003 server
Database size around 200 GB.
Daily archive generation may be around 40. Archive log size 200 MB.
We have implemented the below backup strategy
1. weekly once full incremental level 0 backup(differential).
2. Daily incremental level 1 backup(differential).
Daily incremental backup size will be around 1 GB.
Now we are facing a problem because of the incremental backup. The incremental backup is taking more than 1 hour time to complete. So we are not able to run it in the production time.its a 24/7 production database.
Please advice how to reduce the incremental backup time ?
Is there any options like what we have in 10g Block change tracking. please advice..
TIA,

ORCLDB wrote:
Hello All,
Oracle 9.2.0.7
Windows 2003 server
Database size around 200 GB.
Daily archive generation may be around 40. Archive log size 200 MB.
We have implemented the below backup strategy
1. weekly once full incremental level 0 backup(differential).
2. Daily incremental level 1 backup(differential).
Daily incremental backup size will be around 1 GB.
Now we are facing a problem because of the incremental backup. The incremental backup is taking more than 1 hour time to complete. So we are not able to run it in the production time.its a 24/7 production database.
Please advice how to reduce the incremental backup time ?
Is there any options like what we have in 10g Block change tracking. please advice..
TIA,Please refer to documentation:
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmtunin.htm#CACJCBDB

RMAN backup slow

Hi,
I have a Production Database (10204) running on HP Unix (B.11.11).
Daily morning 6AM, a full RMAN backup runs. The db size is only around 225GB. But it takes 4.5 hours to complete.
The syntax which I use is given below.
RMAN> run {
     allocate channel ch1 type "sbt_tape";
     allocate channel ch2 type "sbt_tape";
     allocate channel ch3 type "sbt_tape";
send
'NB_ORA_CLIENT=jjcprd04-back.backup.ncsus.jnj.com,NB_ORA_POLICY=JJCPRD04-RMAN';
     backup
     format 'bk_%s_%p_%t'
     (database include current controlfile);
     sql 'alter system archive log current';
     backup
     format 'arch_%d_%s_%p_%t'
     (archivelog all delete input );
Is there a way to increase the speed of this backup? Currently the backup is way too slow as it takes 4.5 hours to copy 225GB of data!
Thanks!

I'll start by stating that backups directly to tape are generally quite slow.
I'd still recommend moving to disk backups though... and just archiving it to a tape...Hi Jony,
You can of course backup to disk. Thats a common solution. But you have to deal with space more than everything. In addition to that backing up to disk does not free you from moving/copying your data - depending on your backup strategy - to a long-term storage.
So you have two different and not conjunct backup operations: the rman backup itself and the job which backups the rman area to another media.
In recovery cases you might end up with RMAN requesting older backupsets which are not on disk anymore. This will most probably lead to recovery failures and manual intervention which is not desirable in recovery scenarios.
Another point is the control of the data flow. Backing up via a MML (i.e. "to tape") does not necessarily mean "to tape". Instead it means "to the backup software" which is responsible for managing the backup data. Common scenarios involve backing up the full backups via SAN directly to tape and backing up the archivelogs or incremental backups over LAN which will be stored by the backup software on a hard disk and later copied and/or moved on to tape. The data flow (to SAN / to disk / whereever) is solely controlled by the backup software.
The advantage here is one continuous backup and restore job. The backup software deals with "where is my saveset located" and requests automatically the needed tapes or disks in recovery scenarios. This makes recoveries far more flexible and comfortable.
Regarding the throughput i have set up a rather large OLTP database ( 12 TB currently) which is backed up with EMC Networker. Full backups are written via SAN directly to tape. The average speed with four LTO-3 drives is approx. 550 MB/s (the tape drives compress the data in hardware; the database itself is text-only and seems rather good compressable). I guess thats not too bad.
you can also compress the BACKUPSETS (this generates a little more CPU but less network IO)He said he is on HP-UX. These kind of CPUs tend to be not that fast. Using compression is an option worth testing but there is another point to test when doing compressed backups: The RESTORE TIME.
Ronny Egner
My Blog: http://blog.ronnyegner-consulting.de

Incremental Backups in Time Machine taking forever

Greetings all,
I have read the various posts about slow initial backups with Time Machine. I, on the other hand, had no such problem. However, now that my initial backup is complete I find it takes quite a long time for Time Machine to do its hourly thing. I mean a LONG time. The machine will sit for minutes at a time doing nothing, then copy a few kilobytes of a reported 239 MB backup. Then when it finally does complete - roughly 30 minutes later - it will sit for 10 or 15 minutes at the "Finishing backup" stage. At this rate Time Machine is running almost constantly - by the time the darnned thing finishes it's almost time to start again. It didn't do this on my G5 quad core with the same amount of data (about 850 GB). Does anyone have any ideas why this might be happening?
Thanks for your help.

Your Majesty!!
Sounds like your incremental backups are quite fast!
I have a mid 2011 iMac with SSD and 2TB HDD, and Time Machine incremental backups take anything up to 5 hours, sometimes longer. Trivial amounts of data are usually involved, but the log reports very large numbers of files.
One time I completed a Time Machine backup, rebooted and initiated another backup immediately with very few apps running (Console, Activity Monitor), and after several hours, the backup log said it had backed up over 800,000 files but only a very small amount of data.
I have a case open with AppleCare since July 1st. They have a whole lot of logs and other information being analyzed.
You will find others who have the same unresolved problem at - https://discussions.apple.com/thread/3144862?start=0&tstart=0

Time Machine Stuck (Incremental backup, not Initial)

Hey...me again.
I was finally successful yesterday backing up 160GB of data with Time Machine.
However, this morning, the incremental backup is taking forever. It's been stuck at "3.6MB of 6.7MB" for over 20 minutes. It would seem to me that 6.7MB should be pretty quick to backup.
I have received these messages from TM Buddy:
Starting standard backup
Backing up to: /Volumes/Time Machine/Backups.backupdb
No pre-backup thinning needed: 100.0 MB requested (including padding), 279.56 GB available
Unable to rebuild path cache for source item. Partial source path:
Copied 305079 files (49.1 MB) from volume Macintosh HD.
No pre-backup thinning needed: 100.0 MB requested (including padding), 279.31 GB available
And Console shows this:
Aug 25 10:23:53 Kieran-Roys-MacBook-Pro /System/Library/CoreServices/backupd[254]: Backup requested by user
Aug 25 10:23:53 Kieran-Roys-MacBook-Pro /System/Library/CoreServices/backupd[254]: Starting standard backup
Aug 25 10:23:53 Kieran-Roys-MacBook-Pro /System/Library/CoreServices/backupd[254]: Backing up to: /Volumes/Time Machine/Backups.backupdb
Aug 25 10:26:21 Kieran-Roys-MacBook-Pro /System/Library/CoreServices/backupd[254]: No pre-backup thinning needed: 100.0 MB requested (including padding), 279.56 GB available
Aug 25 10:27:51 Kieran-Roys-MacBook-Pro /System/Library/CoreServices/backupd[254]: Unable to rebuild path cache for source item. Partial source path:
Aug 25 10:41:06 Kieran-Roys-MacBook-Pro /System/Library/CoreServices/backupd[254]: Copied 305079 files (49.1 MB) from volume Macintosh HD.
Aug 25 10:42:21 Kieran-Roys-MacBook-Pro /System/Library/CoreServices/backupd[254]: No pre-backup thinning needed: 100.0 MB requested (including padding), 279.31 GB available
Any idea on how to resolve?
Thanks,
K

kieranroy wrote:
Hey...me again
Hi again. You seem to have really angered the god of TM, haven't you!
However, this morning, the incremental backup is taking forever. It's been stuck at "3.6MB of 6.7MB" for over 20 minutes. It would seem to me that 6.7MB should be pretty quick to backup.
Unable to rebuild path cache for source item. Partial source path:
This usually doesn't cause a real problem, as long as it's occasional.
Copied 305079 files (49.1 MB) from volume Macintosh HD.
This we see on occasion -- the crazy high file count, and very slow backup.
Aug 25 10:42:21 Kieran-Roys-MacBook-Pro /System/Library/CoreServices/backupd254: No pre-backup thinning needed: 100.0 MB requested (including padding), 279.31 GB available
Normally, TM will make a second, "catch-up" pass if changes were made during it's first pass. Usually this is very quick, but since the first one way very slow, this one may be worse.
Do you have any folders, particularly email mailboxes, with a very large number of files (thousands), that are actively being added-to or changed? There was a similar situation recently where an app named SpamSieve was putting messages into a "spam" folder, and the user never cleared it out. Clearing it out helped, but excluding it from Time Machine solved the problem.
Click here to download the TimeTracker app. It shows most of the files saved by TM for each backup (excluding some hidden/system files, etc.). I think it will only show completed backups, so you may not be able to find anything. But look at what's being backed-up to see if any of the files, even if there's only one, are in extremely large folders. If so, try excluding the folder (TM Preferences > Options).

Incremental backup Doubt!

hi,
Oracle version:10.2.0.1.0
In 10G is there any way to merge the incremental backup into a fullbackup?
I read it here
"Incremental backups are merged into the online full
image backup thereby creating a new full backup current
to the point of the merged incremental "
if yes. how ?plz explain...
TIA,

This particular syntax only applied to image copies.
Backups have always been "refreshable" with incrementals by virtue of simply doing 'recover database': if it thinks it appropriate, RMAN has always been able to take block images from a later incremental and 'slot it in' to the base backup to effectively bring it more up to date. Then, redo is applied to bring it completely up to date.
The new syntax available in 10g was designed to allow the same sort of 'refresh' capability to image copies which had previously lacked them and which could therefore previously only be brought up to date by applying redo to them. If you image copies were taken only once a week (say), and your database crashed on the 6th day, that could be a very slow recovery (lots of redo takes a long time to apply). If you can take your Sunday image copy and slot in blocks copied during a Wednesday backup, you effectively have a Wednesday image copy. So a recovery done by applying redo to it on the Friday will have much less work to do.

I am trying to restore my catalog having previously done a back up to an external hard drive and subsequently an incremental backup. I am using Photoshop Elements 11 and the only option given in the restore procedure is to open a .tly file.

I have done this but now the restore function is asking for yet another file, which i assume to be the original back up, but that is the only .tly file since the only other relevant file appears to be called catalog.buc but that is just not visible when using the restore function? How do I continue from here with this restoration of my catalog?

Martin_Had a écrit:
Thank you Andaleeb. I appear to have an old backup of a year ago, and a more recent full back up plus an incremental backup.
Regrettably I don't really understand what is going on because firstly the restore does not complete its cycle so I cannot see what that backup file contains and secondly all I have read would suggest that the .tly file is the full backup and the catalog.buc file is the incremental backup. For the present, the catalog shows the photos for 2014 which makes me think I might have backed from the old back up file.
I am minded to create another catalog and try again.
Any views on what I can do?
A backup (full or incremental) is a folder, not a file. It contains renamed pictures file copies as well a copies of the files and subfolders of the original catalog. The catalog.buc is a renamed copy of the database of your original catalog while the backup.tly. That backup.tly file contains the information to restore the renamed pictures where you decide, the original location or a new custom one. You can't do anything with the backup yourself, only the restore process can do the job if it finds the backup.tly file. In the case of an incremental backup, you have to tell the restore process where to find the incremental backup folder; it finds the backup.tly file in that folder and finds what is to restore there; then it asks you for the previous backup folder (in your case the full backup); you then browse to that full backup folder so that the restore process can find find the backup.tly there; the restore then deals with the rest of the files to restore.

Can't resume incremental backups

I fist finished moving and after a few weeks of sitting in a box I set up my Time Capsule to resume operation as my backup device and wireless router. Unfortunately, I must have made a mistake during setup because now my MacBook Pro is treating the TC as a completely new device, seeking to make a full backup of its entire hard drive rather than the first incremental backup since before the move. Is there some way of forcing my MBP to recognize the existing backups on the TC and pick up where it left off? I'd really appreciate some help because I've got some valuable old files trapped in those old backups. Thanks!

I think i have an idea of why this might be happening now but don't know how to fix this. any help would be appreciated.
so i checked this directory
/Volumes/Time Machine Backup 2/Backups.backupdb
and there were two directories. a new one called "computer" and the old folder with my backups "computer 2", so Time Machine must be looking at the "computer" folder. How can I force Time Machine to look at the other older folder? I tried removing the "computer" folder but it won't let me rename "computer 2" to "computer", even from the terminal using sudo and admin privileges. Is there a reason why I'm not allowed rename files on my own machine when I'm the admin?
thanks

ACS 5.3 Incremental BackUp Issue

We have ACS 5.3 and it turns back to "Off" by itself and doesn't perform incremental backup. I turned it "On" several times, but it keeps on turning "Off"
Version : 5.3.0.40.8 in VM Enviroment.

Hi Kumar2000,
I tried to answer anas query here, you may want to go through the same.
https://supportforums.cisco.com/discussion/12142716/acs-inceremental-backup-turns
Regards,
Jatin Katyal
*Do rate helpful posts*

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.

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.

RMAN RECOVERY FROM INCREMENTAL BACKUP

Hi,
hOW TO RECOVER FROM INCREMENTAL BACKUP ?
Any script for recovery from Full+incremental BACKUP?
Many thanks before.

Thank you,
but I can not connect from RMAN when database is shutdowned.
C:\Documents and Settings\Farid>rman catalog rman/****@reprman target sys/***@bd1
Recovery Manager: Release 10.2.0.1.0 - Production on Ven. FÚvr. 16 18:28:19 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: Úchec de l'initialisation du gestionnaire de rÚcupÚration interne
RMAN-04005: erreur de la base de donnÚes cible :
ORA-12514: TNS : le processus d'Úcoute ne conna¯t pas actuellement le service demandÚ dans le descripteur de connexion
tnsping BD1Adaptateur TNSNAMES utilisÚ pour la rÚsolution de l'alias
Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST
E = bd1.virtualparc.com)))
OK (30 msec)

Incremental Backups are Cumulative Vs Differential??

Dear all,
The followings are Weekly Full Backup and Daily Backup scripts:
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
allocate channel ch1 type disk format '/u02/db/backup/RMAN/backup_%d_%t_%s_%p_%U.bck';
backup incremental level 0 database plus archivelog delete all input;backup current controlfile;
backup spfile;
release channel ch1;
Daily Backup:
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
allocate channel ch1 type disk format '/u02/db/BACKUP/RMAN/backup_%d_%t_%s_%p_%U.bck';
backup incremental level 1 cumulative database plus archivelog delete all input;delete noprompt obsolete;
delete noprompt archivelog all backed up 2 times to disk;
backup current controlfile;
backup spfile;
release channel ch1;
I will do the full backup on Sunday and daily backup on Mon to Sat.
Scenario 1:
Incremental Backups are cumulative, I need of sunday full backup and tuesday daily backup to restore the database if crash on wednesday.
Scenario 2:
Incremental Backups are differential, then I need of sunday full backup and all incremental backups until crash.
I am wondering which scenario (1 or 2) is for my scripts that I post on above? Because I have different answer from others.
Best Regards,
Amy

Your scripts are following the scenario 1. Incremental backups are by default
differential. Since you are using the keywork CUMULATIVE, it's the 1 scenario.
What made you doubtfull? Scripts are straight forward.......

Incremental backup SLOW

Similar Messages

Maybe you are looking for