Full backup or Incremental backup????

We have Oracle 9.2.0.5
We have a Database in a Datawarehouse system.
We make full backup on saturday, it take 2 or 3 hoursâ¦ but we need to do a backup daily because we have a transactional system to modificate some data and we have a repository of the reporting tool too..
We can make a night backup but we need to do a fast backupâ¦
Our System Administrator said me itâs not convenient to do a incremental backup and He suggest a full backupâ¦ Itâs correct? Whatâs your recommendations????
Thanks!

I think full backup is fine but here you have some redundant information. If you choose incremental backup then it will be faster and save redundant information.

Similar Messages

How to restore using increment backup after full backup restore in RMAN?

Hi All,
We have a files of full backup of database after turning on the Archive log.
And after that, daily incremental backup is taken.
Now, i want to restore the the database into a new machine using both files of full and incremental backups. Can anybody give me script for restore of full backup and after that restore of incremental backup?
Thanks,
Praveen.

Praveen,
>>
In my case, i have 2 sets of backups. One is full backup and other is incremental backup. In order to keep the restored database upto date, i need to restore the full backup and then restore incremental backup. Now, i got any idea how to restore using full backup. My doubt is how to update the restored database with incremental backup also?
>>
Restore always looks for level 0 backup, not the incremental backups.
Incremental backups comes in picture during recovery.
During Recovery, Oracle looks for incremental backups, if exists, it will do the recovery with the incremental backups, if no incremental backups available, then, it will look for archived logs.
Therefore, incremental backups never used during restore, they are used only during the recovery.
Jaffar

Time Machine making full backups--not incremental

Hi,
I just installed Snow Leopard on my Mac Pro a couple of days ago, and have been using Time Machine to make backups (never used it before now). I have TimeMachineEditor installed, and have it set to make a backup daily at 3:30am. It backs up data from my 500GB main hard drive to another internal 500GB hard drive.
The first backup went without a hitch, and did a full backup as expected (everything). But the second, third, and fourth backups all were full backups as well....not incremental as they should've been. The fourth one was actually a manual backup I did to test it...I chose "Back Up Now" to see if it did full or incremental. It did a full backup.
So, after four backups, each a little over 100GB, I'm already running out of space Has anyone else run into this behaviour? Is this a consequence of TimeMachineEditor having screwed it up somehow? Even if it has, shouldn't a manual backup still do an incremental backup?
Very strange....

canadavenyc wrote:
V.K. wrote:
yes, well, if Toronto ever gets a team in any sport worth rooting for, I might stop posting on apple forums and start watching them.
lol...well, seeing as how you'll clearly be here a while then... ...perhaps I can prevail upon you to answer one last question that just occurred to me.
Let's say I have tons of TM snapshots on my backup drive, and at some point I want to delete a few to clear some space. I know TM automatically goes after the earliest ones when the drive fills up,
You should know that TM also constantly thins recent backups. It keeps hourly backups for 24 hours and then deletes all but one for every day; it keeps daily backups for 30 days and then deletes all but one for every week. it keeps all weekly backups till the TM drive gets full at which point it starts deleting the oldest ones.
but let's say I manually want to delete a few snapshots that contain, say, a massive cache file or something totally useless to keep around, which I could afford to delete and would gain me a lot more drive space.
When I go into the TM interface to do the removal, how can I figure out which snapshots to get rid of? How would you do it?
TM offers two options. you can delete an entire backup corresponding to a time point or it can delete all backups of a given file/folder. to do that enter TM and scroll back in time to some time point. select something and click on the "gears" action button in Finder toolbar. you'll see options "delete backup" (deletes the entire backup for that time point), and 'delete all backups of this item". deletes all backups of the selected item from all time points. I use the latter sometimes to get rid of backups of very large files.

Incremental and Full backups using WBADMIN and Task Scheduler in Server 2008 R2

I'd like to create an automated rotating schedule of backups using wbadmin and task scheduler, which would backup Bare Metal Recovery; System State; Drive C: and D: to a Network Share in a pattern like this:
Monday - Incremental, overwrite last Monday's
Tuesday - Incremental, overwrite last Tuesday's
Wednesday - Incremental, overwrite last Wednesday's
Thursday - Incremental, overwrite last Thursday's
Friday - Incremental overwrite last Friday's
Saturday - Full, overwrite last Saturday's
I need to use the wbadmin commands within the Task Scheduler and do not know any of the required Syntax to make sure everything goes smoothly, I do not want to do this through the CMD.

I know each backup for the previous corresponding day will be replaced, how do you figure I wont be able to do incremental backups...
Because incremental backup is based on Volume Shadow Copy (VSS) feature and due to Windows Server 2008 R2 limitations (this limitation is resolved in Windows 8) only one version of backed up data can be stored in a shared folder. So the
result is that every time you back up some data on a shared folder, you actually creating a full backup of them.
is it not supported through task scheduler?
The Task Scheduler is only a feature that does the tasks that you have defined for it. Actually it runs the
wbadmin command that runs on an operating system with the mentioned limitation.
I know you can do Incremental backups through Windows Server Backup, but my limitation using that is I cant setup multiple backups.
Yes, you are right. Windows Server Backup feature in Windows Server 2008/2008 R2 has not this functionality (although
ntbackup in Windows XP and Windows Server 2003 had this functionality). So, the only workaround to this limitation is through using Task Scheduler feature with wbadmin command. For more information see the following article:
http://blogs.technet.com/b/filecab/archive/2009/04/13/customizing-windows-server-backup-schedule.aspx
So are you saying that even though I want each backup to go to a different place on the Shared Folder that it will replace the previous backup anyways?
No and because of this I said in my previous post that with some modifications and additions you can do the scenario. For example, you back up to a shared folder with the name of Shared1 on Mondays. You also have been configured the backup feature to back
up data on another shared folder, named Shared2, on Wednesday. When you repeat the backup operation in Shared1, only the backed up data that resides on it will be affected, and the data on Shared2 remains intact.
Please feel free to let us know if you have any question or concern.
Please VOTE as HELPFUL if the post helps you and remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading
the thread.
Hi R.Alikhani
Then do you know if wbadmin supports incremental backup in Windows 8? As you said the VSS issue is fixed in Win8. However, the wbadmin has less options then in windows server. I tried a bit but it seems it only supports full backup? ps, I use a network share
- will the incremental backup works if I define a ISCCI then? My remote backup PC is also running Win8.

Autonomy Backup Client - issue with full backup but incrementals okay

We run Autonomy to back-up our Laptops across the enterprise .
I notice on one laptop here that the account within Autonomy Admin shows taht "Last known good full backup = Not applicable", but when you go into client history you can see that the incremental backups have been happening okay.
Should I be conerned? Is this backup file corrupt? If so, how please can I fix with minimal impact to the user.
Thanks

Ronnie73 wrote:
We run Autonomy to back-up our Laptops across the enterprise .
I notice on one laptop here that the account within Autonomy Admin shows taht "Last known good full backup = Not applicable", but when you go into client history you can see that the incremental backups have been happening okay.
Should I be conerned? Is this backup file corrupt? If so, how please can I fix with minimal impact to the user.
Thanks
For this unless this is a HP software product you need to contact the Software manufacture that you use for your backup for support on their software...
I am a Volunteer to help others on here-not a HP employee.
Replies aren't online 24/7 because of Time Zone differences.
Remember in this Day and Age of Computing the Internet is Knowledge at your fingertips if you choose understand it. -2015-

Time machine not doing incremental backups - instead doing full backups

hi,
Time machine does a complete full backup, and then instead of doing incremental backups, it wants to keep doing full backups.
help.

why do you think it's doing full backups?
install TimeMachineBuddy widget and see exactly what it says. also install TimeTracker and see what exactly is being backed up every time
http://www.charlessoft.com/
but first, verify both the internal and TM drive with disk utility. verify disk, not permissions. if it reports any errors repair both drives. you'll need to boot from the snow leopard DVD to repair the main startup drive.
also, see Pondini's troubleshooting tips at the top of the TM forum.
http://discussions.apple.com/thread.jspa?threadID=2057525
Message was edited by: V.K.

Time Machine wants to do a full backup. How do I point it to my previous backups so it will do an incremental backup?

I lost my wireless connection to my backup drive for a short time. Now time machine wants to do a full backup. It doesn't know that I have previous backups. How do I point it to the previous backups so that time machine continues to do incremental backups rather than doing another full backup.

I did some more reading and I found that Time Machine would find the older backups once a new backup is completed. The backup ended up being a little larger than previous backups (2.65 GB vs typical incremental backups of several MB's) but when it completed, time machine updated the last backup time/date and the oldest backup time/date properly. So I guess, I don't have a problem.

Retrospect Incremental seems to want a full backup???

Hello everyone,
I was hoping someone could shed some light on a Retrospect issue.
I have a G4 Xserve with OS X Server 10.4.3 and Retrospect 6.1.126 with a Sony AIT-3 Autoloader. I have 3 storage sets, one for a long term incremental and two to run full backups every second week and incrementally everyday.
The funny thing is that it has been working fine but one day we had a power cut and now retrospect’s catalogues seems to think that the files had never been previously backed up! It now wants to backup the whole server again. This isn't a huge problem as two of the storage sets are recyclable ever second week anyway and I just have to add more tapes to the long term incremental.
I just want to know if anyone has any ideas how this happened and if it is likely to happen again?
Nothing has changed, the path to the data is the same and the name of the drive is the same. The volume is two 250GB ADM mirrored together. The RAID is fine. Retrospect is still set to match files (so if you did change the path it would match the files and not bother to back it up again).
Any thoughts?
Many thanks,
David

Hi David
At a guess, it sounds like the storage sets have gone sideways, I have seen this before with retrospect and incremental backups.
You can either -
Rebuild the storage set from tapes (depending on how many tapes in this set)
Backup the whole RAID to tape and carry on with the current set
Start a new Incremental set and keep the old one as archive
I always setup retrospect to duplicate the storage sets to another device on the network after incremental backup, so if the set goes bad I can just grab the last one from less than 24hours ago and carry on.
Regards
Ed

RMAN Incremental Lvl 0 backup vs Full Backup

Hi all professionals,
If my RMAN backup script did not specify the incremental backup strategy, what is the default strategy it would adopt?
say for example: backup as compressed backup set database plus archive log delete input;
Will it use full backup or lvl 0 incremental backup?
There is a RMAN script (similar with the above) running as scheduled job daily and I will also use backup exec to backup the database to tape (manually scheduled to run for each time but not daily) at the same time.
Will the scheduled daily rman script backup affect the scn of the backup using backup exec so that it could not be restore the tape backup using backup exec to a testing db as usual?
(checked that backup exec also use rman script to backup but it uses incremental lvl 0)
Welcome your professional comments and sharing.
Thanks,
Calvin
Edited by: Calvin CS Ng on Aug 8, 2010 9:29 PM

backup as compressed backup set database plus archive log delete input;
Will it use full backup or lvl 0 incremental backup?
It will be a full backup.
There is a RMAN script (similar with the above) running as scheduled job daily and I will also use backup exec to backup the database to tape (manually scheduled to run for each time but not daily) at the same time.
Will the scheduled daily rman script backup affect the scn of the backup using backup exec so that it could not be restore the tape backup using backup exec to a testing db as usual?There should be no impact on restore/recovery.
Doc http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmconc1.htm#i1011483 says:
>
The only difference between a level 0 incremental backup and a full backup is that a full backup is never included in an incremental strategy.

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

Time Machine randomly performing full backups instead of incremental

I've been using a Time Capsule since October 2009 with my 13" MBP running Snow Leopard with no issues.
A few weeks ago, I noticed Time Machine decided to do a full 160GB backup, which then filled the Time Capsule and then deleted older backups. It then kept trying to do full backups every single time, resulting in the error 'Not enough space'.
I archived the backups from the Time Capsule, disabled Time Machine and completely erased the Time Capsule.
I set up Time Machine again and it's been working for about a week, but it's doing the same thing again - trying to do another large HD sized backup of 160GB or so (the amount of data my drive has).
I have noticed in the logs the following line
*17/02/2010 13:36:16 com.apple.backupd[946] Event store UUIDs don't match for volume: HD*
Which seems to appear as Time Machine starts to do it's full backup.
Any ideas? It's getting to the point that Time Machine is becoming unusable as I can't rely on it.

Cool, I'll give that a try.
Log files are here. I did rename my machine to remove spaces and punctuation but haven't backed up since then (only a few hours ago).
Should I resume this backup or erase the TC and start again? (I've also renamed the TC network and drive)
Feb 20 00:16:14 marty com.apple.backupd[8919]: Starting standard backup
Feb 20 00:16:14 marty com.apple.backupd[8919]: Attempting to mount network destination using URL: afp://[email protected]/Time%20Machine
Feb 20 00:16:22 marty com.apple.backupd[8919]: Mounted network destination using URL: afp://[email protected]/Time%20Machine
Feb 20 00:16:32 marty com.apple.backupd[8919]: Disk image /Volumes/Time Machine/Jordan’s MacBook Pro.sparsebundle mounted at: /Volumes/Time Machine Backups
Feb 20 00:16:32 marty com.apple.backupd[8919]: Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
Feb 20 00:16:38 marty com.apple.backupd[8919]: No pre-backup thinning needed: 1.13 GB requested (including padding), 264.22 GB available
Feb 20 00:16:47 marty com.apple.backupd[8919]: Copied 8 files (15 KB) from volume HD.
Feb 20 00:16:47 marty com.apple.backupd[8919]: Starting post-backup thinning
Feb 20 00:16:48 marty com.apple.backupd[8919]: Deleted backup /Volumes/Time Machine Backups/Backups.backupdb/Marty/2010-02-18-234422: 264.22 GB now available
Feb 20 00:16:48 marty com.apple.backupd[8919]: Deleted backup /Volumes/Time Machine Backups/Backups.backupdb/Marty/2010-02-18-225109: 264.22 GB now available
Feb 20 00:16:48 marty com.apple.backupd[8919]: Post-back up thinning complete: 2 expired backups removed
Feb 20 00:16:48 marty com.apple.backupd[8919]: Backup completed successfully.
Feb 20 00:16:50 marty com.apple.backupd[8919]: Ejected Time Machine disk image.
Feb 20 00:16:51 marty com.apple.backupd[8919]: Ejected Time Machine network volume.
Feb 20 00:23:42 marty com.apple.backupd[9017]: Starting standard backup
Feb 20 00:23:42 marty com.apple.backupd[9017]: Attempting to mount network destination using URL: afp://[email protected]/Time%20Machine
Feb 20 00:23:52 marty com.apple.backupd[9017]: Mounted network destination using URL: afp://[email protected]/Time%20Machine
Feb 20 00:24:11 marty com.apple.backupd[9017]: Disk image /Volumes/Time Machine/Jordan’s MacBook Pro.sparsebundle mounted at: /Volumes/Time Machine Backups
Feb 20 00:24:11 marty com.apple.backupd[9017]: Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
Feb 20 00:24:11 marty com.apple.backupd[9017]: Backup canceled.
Feb 20 00:24:14 marty com.apple.backupd[9017]: Ejected Time Machine disk image.
Feb 20 00:24:14 marty com.apple.backupd[9017]: Ejected Time Machine network volume.
Feb 20 00:25:24 marty com.apple.backupd[9017]: Starting standard backup
Feb 20 00:25:24 marty com.apple.backupd[9017]: Attempting to mount network destination using URL: afp://[email protected]/Time%20Machine
Feb 20 00:25:25 marty com.apple.backupd[9017]: Mounted network destination using URL: afp://[email protected]/Time%20Machine
Feb 20 00:25:30 marty com.apple.backupd[9017]: Disk image /Volumes/Time Machine/Jordan’s MacBook Pro.sparsebundle mounted at: /Volumes/Time Machine Backups
Feb 20 00:25:32 marty com.apple.backupd[9017]: Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
Feb 20 00:34:44 marty com.apple.backupd[9017]: No pre-backup thinning needed: 200.38 GB requested (including padding), 264.22 GB available
Feb 20 00:35:46 marty com.apple.backupd[9017]: Copied 283 files (6.5 MB) from volume HD.
Feb 20 00:35:46 marty com.apple.backupd[9017]: Backup canceled.
Feb 20 00:35:49 marty com.apple.backupd[9017]: Ejected Time Machine disk image.
Feb 20 00:35:50 marty com.apple.backupd[9017]: Ejected Time Machine network volume.

HT1175 Time Machine wants to start with a new, full backup instead of using the existing one

Hi, my Time Machine wants to start a new, full backup, instead of continuing with the existing one on the time Capsule.
Looking a the Troubleshooting guide, I've found the following piece of info, which is, as 99% of the times with the troubleshooting guides, totally useless to resolve my problem...
Message: Time Machine starts a new, full backup instead of a smaller incremental backup
There are three reasons why this may occur:
You performed a full restore.
Your Computer Name (in Sharing preferences) was changed--when this happens, Time Machine will perform a full backup on its next scheduled backup time.
If you have had a hardware repair recently, contact the Apple Authorized Service Provider or Apple Retail Store that performed your repair. In the meantime, you can still browse and recover previous backups by right-clicking or Control-clicking the Time Machine Dock icon, and choosing "Browse Other Time Machine disks" from the contextual menu.
It should be noted (hence the uselessness of the guide) that:
-I haven't performed ANY full restore
- I havent changed my computer name
- My computer has not had ANY repair, much less a hardware repair. Neither recently, nor in the 9 months I've owned it.
Which puts me back to square one, with the marginal improvement that now I have a way of browsing my old backups.
In the event I decide to start all over again, will there be a way for me to "sew" the two backup files?
Or will I always have to go the silly way around?
Anybody has any idea?
Thank you for your time (machine/capsule, your choice;-)

Hi John,
no, that doesn't have anything to do with my problem.
Just look at the image below.
Time Machine thinks that the disk I've always used to do my backups has none of them.
If I open the disk with Finder, obviously they are where they should be.
It is even possible to navigate them as per the instruction reported above, but even following Pondini's advice #s B5 and B6 (which are more applicable to my problem) didn't solve the problem.
Actually, not being a coder, I'm always scared of doing more damage than good when I have a Terminal window open.
My question is: how is it possible that Apple hasn't thought of some kind of user command to tell the idiotic Time Machine software that a hard disk backup is a hard disk backup, no matter what?
Estremely frustrating and annoying: I'm wasting HOURS in trying to find a solution to a problem that should not have arisen in the first place...
Have a nice weekend
Antonio

ACS 5.3.0.40 On-demand Full Backup failed.

Hi,
I have ACS 5.3.0.40 Primary Secondary Authenticators , of which the Scheduled backup has stopped.
When checked the :
Monitoring Configuration >
System Operations >
Data Management >
Removal and Backup
> Incremental Backup , it had changed to OFF mode. without any reason.
The same was observed earlier too.
I have made the
Incremental Backup to ON and intiated the
View Full Database Backup Now. But it wasn't successful and reported an Error:
FullBackupOnDemand-Job Incremental Backup Utility System Fri Dec 28 11:56:57 IST 2012 Incremental Backup Failed: CARS_APP_BACKUP_FAILED : -404 : Application backup error Failed
Later i did the acs stop/start "view-jobmanager" and initiated the On-demand Full Backup , but no luck, same error reported this time too.
Has any one faced similar type of error /problem reported , please let me know the solution.
Thanks & Regards.

One other thing; if this does end up being an issue with disk space it is worth considering patch 5.3.0.40.6 or later since improves database management processes
This cumulative patch includes fixes/enhancements related to disk management to avoid following issue
CSCtz24314: ACS 5.x *still* runs out of disk space
and also fix for
CSCua51804: View backup fails   even when there is space in disk
Following is taken from the readme for this patch
   The Monitoring and Reporting database can increase when as records are collected. There are two mechanisms to reduce this size and prevent it from exceeding the maximum limit.
1. Purge: In this mechanism the data will be purged based on the configured data retention period or upon reaching the upper limit of the database.
2. Compress: This mechanism frees up unused space in the database without deleting any records.
Previously the compress option could only be run manually. In ACS 5.3 Patch 6 there are enhancements so it will run daily at a predefined time, automatically when specific criteria are met. Similarly by default purge job runs every day at 4 AM. In Patch 6 new option provided to do on demand purge as well.
The new solution is to perform the Monitoring and Reporting database compress automatically.
2.       New GUI option is provided to enable the Monitoring and Reporting database compress to run on every day at 5 AM. This can be configured under GUI Monitoring And Configuration -> System Operations -> Data Management -> Removal and Backup
3.       Changed the upper and lower limit of purging of Monitoring and Reporting data. This is to make sure at lower limit itself ACS has enough space to take the backup. The maximum size allocated for monitoring and reporting database is 42% of /opt( 139 GB). The lower Limit at which ACS purges the data by taking the backup is 60% of maximum size Monitoring and Reporting database (83.42 GB). The upper limit at which ACS purges the data without taking backup is 80% of maximum size Monitoring and Reporting database (111.22 GB).
4. The acsview-database compress operation stops all services till 5.3 patch 5 , now only Monitoring and Reporting related services are stopped during this operation.
5. Provided “On demand purge” option in Monitoring and Reporting GUI. This option will not try to take any backup, it will purge the data based on window size configured.
6. Even if the “Enable ACS View Database compress” option is not enabled in GUI then also automatic view database compress will be triggered if the physical size of Monitoring and Reporting database reached to the upper limit of its size.
7. This automatic database compress takes place only when the “LogRecovery” feature is enabled, this is to make sure that the logging which happens during this operation will be recovered once this operation is completed. ACS generates alert when there is a need to do automatic database compress and also to enable this feature.
8. Before enabling “LogRecovery” feature configure the Logging Categories in such way that only mandatory data to log into Local Log Target and Remote Log Target as Log collector under System Administration > ... > Configuration > Log Configuration
This “LogRecovery” feature can recover the logs only if the logs are present under local log target.
9       This automatic database compress operation also performed only when the difference between actual and physical size of Monitoring and Reporting database size is > 50GB.
10 The new CLI “acsview” with option “show-dbsize” is provided to show the actual and physical size of the Monitoring and Reporting database. This is available in “acs-config” mode.
           acsview     show-dbsize     Show the actual and physical size of View DB and transaction log file

Time Machine repeatedly does full backups, including FileVault while logged in

So let me preface this - for months I'd hoped for a way that Time Machine could backup my FileVault encrypted account without logging out. Last night Snow Leopard spontaneously started doing this. I know many may think that I'm looking a gift horse in the mouth, but read further and hopefully someone can help me make sense of this.
Last night I attached my external 1TB USB hard drove to my 15" MBP (spring 2010 model) running OS X 10.6.7. It started doing a Time Machine backup automatically, as usual. Since I was logged into my account that uses FileVault (a massive home folder - 220GB) I expected a fast backup of things only outside my home folder. As i looked at the details, however, i quickly realized that it was backing up all 270GB of data on my hard drive - including my FileVault account while still logged in!
At first i thought i just got lucky - i'd been craving this feature for years and it just happened to me without even doing anything. Curious guy that i am, i logged out of my acct with my USB drive still attached to see what would happen. After FileVault cleared out space in my home folder, it did _another_ backup, that took about 10 minutes to complete. This seemed strange so i logged back in and started another backup manually. To my utter shock, it started doing the whole 270GB over again!
I even cleared out my TM drive, erased, reformatted, checked permissions, etc etc and did the same on my system drive, hoping that it was just a matter of broken permissions. No change.
So there's two things going on here and i'm pretty concerned about both:
1) Why is TM backing up my entire encrypted home folder while i'm still logged in??? Apple has clearly designed TM and FV to NOT work this way for data integrity reasons and the fact that it's happening has me freaked out a bit over the reliability of my backups.
2) Why is TM doing full backups after each time i login to my account? If i stay logged in, it appears to only do incremental (normal) backups but if i logout, then re-login and allow the hour to pass and let a backup start on its own, it starts the whole 270GB again.
I'm getting to the point of wiping the system and starting from scratch but since i presently live in a country with no Apple store and extremely poor internet access, that prospect horrifies me
any ideas?
many thanks,
-Tim

Thanks for the input Pondini -
I tried deleting the file as mentioned in #A4 and it still had the problem. Last weekend i finally got a brand new hard drive and reinstalled OSX 10.6.3 from scratch, then promptly applied the 10.6.7 combo update. I purposely chose to NOT import my old user from backup and instead set up everything again manually (royal pain, but the only way i could be sure that i wouldn't bring the problem with me). Today i whipped out my TimeMachine drive and set it up for backups. I crossed my fingers and it AGAIN started backing up all 250+GB of my system from within my FileVault protected account.
My wife's MBP is still running 10.6.4 and i'm beginning to wonder if his is an issue with 10.6.7 since i'm relatively certain i didn't experience this before that upgrade.
I've checked my wife's exclusions under Options and her home folder is NOT in that list, yet her TM is not attempting to backup everything until she logs out of her FV acct.
In response to Linc Davis, _yes_ it was backing up my info into a sparsebundle file, not just the raw unencrypted data, which is extremely strange.
If i DO add my home folder to the exclude list, will it still be backed up when i log out?
At this point, i'm thinking my next steps are:
1) try a different TM backup drive, even though i've wiped and checked my current drive numerous times
2) downgrade to an older version of Snow Leopard to see if 10.6.7 is the culprit
Any other ideas?

Full backup system restore from time machine

Help: I need to rebuild my system from Time Machine.
I am using iMac with 10.6.8. I plan to replace my HDD.
When trying to emulate the system restoration, I used the MAC Install DVD, which allowed accessing the Time Machine external disk.
However, TM suggested only one full backup dated 3/2011......
Can't time machine use all incremental steps between 2011 and today? 3 years......
What should I do before changing my HDD? Any way to force TM to accept a full backup NOW?
And then, will Restore rebuild my system as I see it today?
Thanks,
Moshe

The only one I've ever used is SuperDuper. It and Carbon Copy Cloner have free trail periods so you can experiment. I'm not familiar with the others.
Clone - Carbon Copy Cloner (Often recommended as it has more features than some others)
Clone – Data Backup
Clone – Deja Vu
Clone - SuperDuper
Clone - Synk
Clone Software – 6 Applications Tested

Full backup or Incremental backup????

Similar Messages

Maybe you are looking for