Privelege for normal backup

Hi,
I need to know whether there is a specific privilege for a user to perform backup only in oracle.
He should not be able to do any other activity.please help me with this.
Regards,
Dileep.

In 11g and below, the account running the RMAN backup has to connect with the SYSDBA privilege. Normally, this is done by having RMAN backup executed by the OS's oracle account that, being a member of the OS's dba group has the privilege.
If you are using methods other than RMAN, you can setup an account that has been granted the ALTER DATABASE privilege so that it can run ALTER DATABASE BEGIN BACKUP (but it can still do many other things with the ALTER DATABASE privilege). Optionally, the SYSOPER privilege can be mapped to an OS group --- that way members of this OS group can run database backups.
12c introduces a new privilege "SYSBACKUP" that can be used specifically for RMAN backups.
Hemant K Chitale
Message was edited by: HemantKChitale
Added line on SYSOPER

Similar Messages

17 hours remaning for 1st backup of iphone 4 16gb. is that normal?

17 hours remaning for 1st backup of iphone 4 16gb. is that normal?

Not at all.
Try resetting your iPhone then try again.
Hold the Sleep/Wake button and the Home button at the same time for at least ten seconds, until the Apple logo appears.

DAG - Backup failing on 1 DB only with error - The Microsoft Exchange Replication service VSS Writer instance ID failed with error code 80070020 when preparing for a backup of database 'DB012'

Hi Board,
i´ve search across the board, technet and symantec sites but did not found a hint about my problem.
we drive a 2 node DAG (Location1-Ex1-mb1
Location2-exc1-mb1), on SP2 RU4 patchlevel with 40 Databases.
Since some time the backup of one - and only one DB - is failing with these events, logged on the Mailboxserver on which the passive DB is hosted.
Log Name:      Application
Source:        MSExchangeRepl
Date:          28.09.2012 00:37:17
Event ID:      2112
Task Category: Exchange VSS Writer
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Location1-Exc1-MB1
Description: The Microsoft Exchange Replication service VSS Writer instance 1ab7d204-609a-4aea-b0a7-70afb0db38de failed with error code 80070020 when preparing for a backup of database 'DB012'.
Followed by
Log Name:      Application
Source:        MSExchangeRepl
Date:
01.10.2012 03:33:06
Event ID:      2024
Task Category: Exchange VSS Writer
Level:         Error
Keywords:      Classic
User:
N/A
Computer:      Location1-Exc1-MB1
Description:
The Microsoft Exchange Replication service VSS Writer (Instance 42916d80-36c1-4f73-86d0-596d30226349) failed with error 80070020 when preparing for a backup.
The backup Application - Symantec Backup Exec 2010 R3 – states, this error
Snapshot provider error (0xE000FED1): A failure occurred querying the Writer status.
Check the Windows Event Viewer for details.
Writer Name: Exchange Server, Writer ID: {76FE1AC4-15F7-4BCD-987E-8E1ACB462FB7}, Last error: The VSS Writer failed, but the operation can be retried (0x800423f3), State: Stable (1).
Symatec suggests within http://www.symantec.com/business/support/index?page=content&id=TECH184095
to restart the MS Exchange Replication Service – BUT the mentioned eventID
8229 isn´t present on any of the both Mailboxservers.
The affected Database is active on Location2-Exc1-Mb1 Server and in an overall healthy state. I found during my research, that below Location2-Exc1-Mb1 Server, there are not removed shadow copies present!
This confuses me, since all Backups are normally taken from the passive copy of a Database.
So my questions to the board are:
* Does anyone is facing similar issues?
* Can someone explain why snapshots are present on the Mailboxserver hosting the Active Database, whilst the errors are logged on the passive one?
-          * Does someone know the conditions, why shadows copies remain and
aren´t removed in a proper manner?
What can cause the circumstance, that only 1 DB is facing such issues?
Any suggestion is welcome!
BR
Markus

Hi Lenora,
I´ve encreases VSS / Exchange Backup Log levels to expert, before starting
those things i´ve all tried now:
- Backup from passive DB (forced within Symantec Backup Exec)
- Backup from active DB (forced within Symantec Backup Exec)
- Backup from passive DB without GRT enabled (forced within Symantec Backup Exec)
- Backup from active DB without GRT enabled(forced within Symantec Backup Exec)
All those attempts failed.
But brought some more details - the backup against the active DB states, that there is still a backup in progress and therefore this backup is cancelled by VSS.
The Solution was, that i´ve needed to restart the Exchange Replication Service on the Mailbox Server hosting the passive DB.
Backups are working again on all DBs!
THX for your replys.
Best regards
Markus

Hi. I recently backed up using iCloud (normally backup to my computer), now I have lost a heap of contacts. Can anyone help me out with where they've gone? Thanks :)

Hi. I live in New Zealand, and have an iphone 5s. I normally backup to My Computer, as I have alot of photos and videos on my iphone, and icloud only gives 5GB free. In order to fit everything on my phone, I would most likely need the 50GB one, which costs $125 over here. The other day a friend told me I should backup to icloud. So I did. Then yesterday I noticed that she txt me, and it came up with her number, not her name. I thought there was a problem with her phone. But last night I was going through my Contacts list, and I see there is a heap of them missing. I also changed my password on my Yahoo! email account the other day, but I done that on my laptop. So when I went to my settings on my iphone, I just deleted the password and typed in the new one, the emails and everything all came up fine. So I don't think that is the problem. I have read other questions on here and on Google, where they say to go to yr Contacts, and to Groups, untick them all, and tick them again. I have done this, and still they don't come back. Mine Groups appear in the following order: ICLOUD - All iCloud; FACEBOOK - All Facebook; YAHOO! - All Yahoo!. Yahoo! is my primary email account. I have also turned the wifi off on my iphone, then turned the iphone off. Then turned them both back on, this still doesn't work. Yet when I go to my email account on my laptop, that still has all the contacts. "All Yahoo!" is ticked on my iphone, so I don't know why it isnt syncing them to my iphone. I won't be backing up to icloud again. I have now installed an app called My Contents Backup Pro that someone on here mentioned. Wish I'd known about it earlier. Hope someone can help. Thanks

Have you tried the line inputs on the back of your FirePod? If you update its firmware (not sure if you will need to or not), I seem to remember hearing that the FirePod can run without FW connection, i.e. stand alone. In this mode with the outs from your mixer into line ins 1-2 (2nd from left on the back) it should work fine. I say should because I have never tried. However, these are used for returns from an external effects unit. I assume here, and the important word is assume, that there are two so that they can be used as a stereo send or as a mono send. Worth a try! Let us know how it goes.
Best, Fred

Time Machine Error - The backup is too large for the backup disk

I have been using Lion (currently 10.7.1) on my MacBook Pro (13" - early 2011) since it was released. I haven't had any serious problems with it.
All of a sudden, I am getting an error in Time Machine. When it tries to run a backup, the error "This backup is too large for the backup disk. The backup requires 7.51 GB but only 630.1 GB are available." What gives? That's plenty of room. I have installed Logic Studio and a few plug-ins, so the 7.51 GB is probably right. The free space is correct as well. I can't understand what the problem is.
The backup disk is an external USB 2.0 drive with no other Time Machine backups on it or any other files. The folder "Backups.backupdb" is the only thing on the root of the disk.
I am reluctant to reset the Time Machine and lose all of the backups, but I will if anyone recommends it.

Hi Linc,
It is not working at the moment, as I have restored the original Lion image again; it has all my work and apps on it.
Many thanks for the info on the log, though. It tells a strange story. Here's the log from the last backup that worked to the first one that failed: --
Sep 12 17:15:55 Johns-MacBook-Pro com.apple.backupd[674]: Starting standard backup
Sep 12 17:15:55 Johns-MacBook-Pro com.apple.backupd[674]: Backing up to: /Volumes/Backup/Backups.backupdb
Sep 12 17:15:55 Johns-MacBook-Pro com.apple.backupd[674]: 100.0 MB required (including padding), 633.72 GB available
Sep 12 17:15:55 Johns-MacBook-Pro com.apple.backupd[674]: Waiting for index to be ready (100)
Sep 12 17:16:00 Johns-MacBook-Pro com.apple.backupd[674]: Copied 793 files (601 KB) from volume System.
Sep 12 17:16:00 Johns-MacBook-Pro com.apple.backupd[674]: 100.0 MB required (including padding), 633.72 GB available
Sep 12 17:16:01 Johns-MacBook-Pro com.apple.backupd[674]: Copied 89 files (93 bytes) from volume System.
Sep 12 17:16:01 Johns-MacBook-Pro mds[34]: (Error) Volume: Could not find requested backup type:2 for volume
Sep 12 17:16:01 Johns-MacBook-Pro com.apple.backupd[674]: Starting post-backup thinning
Sep 12 17:16:01 Johns-MacBook-Pro com.apple.backupd[674]: Deleted /Volumes/Backup/Backups.backupdb/John’s MacBook Pro/2011-09-11-154229 (1.1 MB)
Sep 12 17:16:01 Johns-MacBook-Pro com.apple.backupd[674]: Post-back up thinning complete: 1 expired backups removed
Sep 12 17:16:01 Johns-MacBook-Pro com.apple.backupd[674]: Backup completed successfully.
Sep 13 10:34:12 Johns-MacBook-Pro com.apple.backupd[287]: Starting standard backup
Sep 13 10:34:12 Johns-MacBook-Pro com.apple.backupd[287]: Backing up to: /Volumes/Backup/Backups.backupdb
Sep 13 10:34:52 Johns-MacBook-Pro com.apple.backupd[287]: 7.51 GB required (including padding), 630.11 GB available
Sep 13 10:34:52 Johns-MacBook-Pro com.apple.backupd[287]: No expired backups exist - deleting oldest backups to make room
Sep 13 10:34:52 Johns-MacBook-Pro mds[32]: (Error) Volume: Could not find requested backup type:2 for volume
Sep 13 10:35:03 Johns-MacBook-Pro com.apple.backupd[287]: Backup failed with error: Not enough available disk space on the target volume.
I don't understand. For starters, I think it's a little wasteful that 3.5 GB has been used to back up 601 KB. That's the difference in free space on the backup volume between the two backups. That can't be normal, surely.
The only error is that mds[32] error, and from what I've read on forums, that seems to appear on backups that work perfectly.
Too weird. It looks like I'll have to reinstall Lion and all my applications again to get Time Machine working, or find another backup solution.

"Backup is too large for the backup volume" error

I've been backing up with TM for a while now, and finally it seems as though the hard drive is full, since I'm down to 4.2GB available of 114.4GB.
Whenever TM tries to do a backup, it gives me the error "This backup is too large for the backup volume. The backup requires 10.8 GB but only 4.2GB are available. To select a larger volume, or make the backup smaller by excluding files, open System Preferences and choose Time Machine."
I understand that I have those two options, but why can't TM just erase the oldest backup and use that free space to make the new backup? I know a 120GB drive is pretty small, but if I have to just keep accumulating backups infinitely, I'm afraid I'll end up with 10 years of backups and a 890-zettabyte drive taking up my garage. I'm hoping there's a more practical solution.

John,
Please review the following article as it might explain what you are encountering.
*_“This Backup is Too Large for the Backup Volume”_*
First, much depends on the size of your Mac’s internal hard disk, the quantity of data it contains, and the size of the hard disk designated for Time Machine backups. It is recommended that any hard disk designated for Time Machine backups be +at least+ twice as large as the hard disk it is backing up from. You see, the more space it has to grow, the greater the history it can preserve.
*Disk Management*
Time Machine is designed to use the space it is given as economically as possible. When backups reach the limit of expansion, Time Machine will begin to delete old backups to make way for newer data. The less space you provide for backups the sooner older data will be discarded. [http://docs.info.apple.com/article.html?path=Mac/10.5/en/15137.html]
However, Time Machine will only delete what it considers “expired”. Within the Console Logs this process is referred to as “thinning”. It appears that many of these “expired” backups are deleted when hourly backups are consolidated into daily backups and daily backups are consolidated into weekly backups. This consolidation takes place once hourly backups reach 24 hours old and daily backups reach about 30 days old. Weekly backups will only be deleted, or ‘thinned’, once the backup drive nears full capacity.
One thing seems for sure, though; If a new incremental backup happens to be larger than what Time Machine currently considers “expired” then you will get the message “This backup is too large for the backup volume.” In other words, Time Machine believes it would have to sacrifice to much to accommodate the latest incremental backup. This is probably why Time Machine always overestimates incremental backups by 2 to 10 times the actual size of the data currently being backed up. Within the Console logs this is referred to as “padding”. This is so that backup files never actually reach the physically limits of the backup disk itself.
*Recovering Backup Space*
If you have discovered that large unwanted files have been backed up, you can use the Time Machine “time travel” interface to recovered some of that space. Do NOT, however, delete files from a Time Machine backup disk by manually mounting the disk and dragging files to the trash. You can damage or destroy your original backups by this means.
Additionally, deleting files you no longer wish to keep on your Mac does not immediately remove such files from Time Machine backups. Once data has been removed from your Macs' hard disk it will remain in backups for some time until Time Machine determines that it has "expired". That's one of its’ benefits - it retains data you may have unintentionally deleted. But eventually that data is expunged. If, however, you need to remove backed up files immediately, do this:
Launch Time Machine from the Dock icon.
Initially, you are presented with a window labeled “Today (Now)”. This window represents the state of your Mac as it exists now. +DO NOT+ delete or make changes to files while you see “Today (Now)” at the bottom of the screen. Otherwise, you will be deleting files that exist "today" - not yesterday or last week.
Click on the window just behind “Today (Now)”. This represents the last successful backup and should display the date and time of this backup at the bottom of the screen.
Now, navigate to where the unwanted file resides. If it has been some time since you deleted the file from your Mac, you may need to go farther back in time to see the unwanted file. In that case, use the time scale on the right to choose a date prior to when you actually deleted the file from your Mac.
Highlight the file and click the Actions menu (Gear icon) from the toolbar.
Select “Delete all backups of <this file>”.
*Full Backup After Restore*
If you are running out of disk space sooner than expected it may be that Time Machine is ignoring previous backups and is trying to perform another full backup of your system? This will happen if you have reinstalled the System Software (Mac OS), or replaced your computer with a new one, or hard significant repair work done on your exisitng Mac. Time Machine will perform a new full backup. This is normal. [http://support.apple.com/kb/TS1338]
You have several options if Time Machine is unable to perform the new full backup:
A. Delete the old backups, and let Time Machine begin a fresh.
B. Attach another external hard disk and begin backups there, while keeping this current hard disk. After you are satisfied with the new backup set, you can later reformat the old hard disk and use it for other storage.
C. Ctrl-Click the Time Machine Dock icon and select "Browse Other Time Machine disks...". Then select the old backup set. Navigate to files/folders you don't really need backups of and go up to the Action menu ("Gear" icon) and select "Delete all backups of this file." If you delete enough useless stuff, you may be able to free up enough space for the new backup to take place. However, this method is not assured as it may not free up enough "contiguous space" for the new backup to take place.
*Outgrown Your Backup Disk?*
On the other hand, your computers drive contents may very well have outgrown the capacity of the Time Machine backup disk. It may be time to purchase a larger capacity hard drive for Time Machine backups. Alternatively, you can begin using the Time Machine Preferences exclusion list to prevent Time Machine from backing up unneeded files/folders.
Consider as well: Do you really need ALL that data on your primary hard disk? It sounds like you might need to Archive to a different hard disk anything that's is not of immediate importance. You see, Time Machine is not designed for archiving purposes, just as a backup of your local drive(s). In the event of disaster, it can get your system back to its' current state without having to reinstall everything. But if you need LONG TERM storage, then you need another drive that is removed from your normal everyday working environment.
This KB article discusses this scenario with some suggestions including Archiving the old backups and starting fresh [http://docs.info.apple.com/article.html?path=Mac/10.5/en/15137.html]
Let us know if this clarifies things.
Cheers!

TM is very slow even for tiny backups

Hi,
I've been using Time Machine for quite some time now, a year or more. It was fine at first, no problems doing the initial backup and everything works fine.
But over time it seems to have become slower and slower. Now even when the amount of data to back up is very small (a few megabytes), the whole process takes 25 minutes or more. When the backup is larger (100mb or more), the backup often takes longer than an hour. Time Machine spends more time backing up than it does waiting in between backups.
I see nothing in the Console logs that indicates a problem. Here's what a typical small backup looks like:
14/03/09 7:47:27 AM /System/Library/CoreServices/backupd[1216] Starting standard backup
14/03/09 7:47:36 AM /System/Library/CoreServices/backupd[1216] Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
14/03/09 7:49:47 AM /System/Library/CoreServices/backupd[1216] No pre-backup thinning needed: 222.2 MB requested (including padding), 71.15 GB available
14/03/09 7:59:00 AM /System/Library/CoreServices/backupd[1216] Copied 140670 files (12.4 MB) from volume alex.
14/03/09 7:59:06 AM /System/Library/CoreServices/backupd[1216] Copied 140680 files (12.5 MB) from volume Macintosh HD.
14/03/09 8:00:23 AM /System/Library/CoreServices/backupd[1216] No pre-backup thinning needed: 237.2 MB requested (including padding), 71.14 GB available
14/03/09 8:06:21 AM /System/Library/CoreServices/backupd[1216] Copied 110501 files (13.9 MB) from volume alex.
14/03/09 8:06:32 AM /System/Library/CoreServices/backupd[1216] Copied 110609 files (14.0 MB) from volume Macintosh HD.
14/03/09 8:12:46 AM /System/Library/CoreServices/backupd[1216] Starting post-backup thinning
14/03/09 8:13:03 AM /System/Library/CoreServices/backupd[1216] Deleted backup /Volumes/Time Machine Backups/Backups.backupdb/TellyMac/2009-03-13-072250: 71.14 GB now available
14/03/09 8:13:03 AM /System/Library/CoreServices/backupd[1216] Post-back up thinning complete: 1 expired backups removed
14/03/09 8:13:03 AM /System/Library/CoreServices/backupd[1216] Backup completed successfully.
As you can see, well over 20 minutes from start to finish. The whole time it's happening, backupd thrashes the disk and uses 20-50% CPU, so it's not fun.
Surely this is not normal? I never measured it before, but I'm certain it was many times faster before.

awhs wrote:
The pre-backup and copying time is now very short, less than a minute.
Ah, that's more like it.
Post-backup thinning takes almost all of the 10 minutes. Removing the IMAP folder reduced the size of the TM data by around 10gb. So the issue here seems to be the number of files. I suspect there is something else in my old backups (which go back around 12 months) that has a large number of small files, just like the IMAP folder, and that is contributing to the 10 minute post-backup time.
Not exactly. Post-backup thinning is just TM deleting "expired" backups -- hourlies over 24 hours, dailies over a month. Once it's down to deleting only a few at a time, it should be much faster. What may be happening is, the old backups still contain thousands of the "multi-links" from the IMAP files. Once they get weeded out, each one will be deleted much faster.
A couple of things to try:
Download the TimeTracker app, from www.charlessoft.com.
It shows most of the files saved by TM for each backup (excluding some hidden/system files, etc.). This will tell you what, specifically, is being backed-up now.
Do a +Repair DIsk+ (not Permissions) on your TM drive via Disk Utility (in your Applications/Utilities folder).
Then watch both the number of backups deleted and how long it takes to delete them.

When I try to sync my iPhone I get the message: The iPhone cannot be synced. You do not have enough access priveleges for this operation.

When I try to sync my iPhone, I get the message: The iPhone cannot be synced. You do not have enough access priveleges for this operation.
The iPhone won't sync anymore. How can I fix this?

This works even for my ipod on my computer. I recently time machined myself and when i open intunes it always does all that backgroud magic and pops up saying "....You do not have enough access priveleges for this operation."
It turns out i don't need that, because i do not use sync. I do not sync. I don't use the sync. I abstain from getting my sync on...etc.
The first solution posted above works, i'll repeat it but credit goes to King_Penguin a true friend from the motherland! Just find this one file and delete it.
YOU LAZY APPLE DEVEOPERS NEED TO FIX THIS ISSUE!
"I've found this which may (or may not) help : http://www.itjungles.com/iphone-tips/fixed-iphone-sync-error-you-do-not-have-eno ugh-access-privileges-for-this-operation . There's also this thread where the person had the same problem (though on Mac not Windows) http://discussions.apple.com/thread.jspa?threadID=997075"
I'll save you the legwork, heres what you'll find at that first link, and it works. Win the game!
"When iTunes attempt to perform a photo synchronization for the first time it will try to create a folder on the computer called "iPod Photo Cache". You normally can located at:
>User>Pictures>iPhoto Library>iPod Photo Cache.
To fix this error just delete the folder."

Too large for the backup volume?

Hi everyone,
A strange problem when I went to do my daily backup this morning. I always backup:
My internal mac HD (250GB)
My external drive 1 (250GB)
My external drive 2 (500GB)
...to my 1TB external Time machine drive, normally with no problems at all. However this morning I got a message saying
"Time Machine Error. This backup is too large for the backup volume. The backup requires 61.0GB but only 8.2 are available. To select a larger volume or make the backup smaller by excluding files, open System preferences and choose Time Machine"
This doesn't make any sense to me; Time Machine should write the new files over the oldest ones so why is it saying it needs more space?
Does anyone heave any ideas?

Ultrapix wrote:
Thanks for your help; is there anything I can in the meantime?
Backup what you can to separate external drives and either get a larger TM drive or consider a different backup solution. I use TM and also use CCC, not wishing to put all my eggs in a single basket, so to speak.
A RAID TM drive of 5 GB or more would probably work, but separate backups are probably a better solution since TM is primarily designed for backing up a computer with a single large HD, but not several as you have.
CCC works quite will for me, and not includes differential, scheduled backups, as does TM, so it is very similar in that respect, but does not have the TM limitations. Of course, TM is a *pseudo-archival backup system, whilst CCC and SuperDuper! are not.
*Pseudo-archival in that TM will not delete old backups until absolutely necessary, so many old files are still on the TM drive whilst with CCC they are not.

Time Machine Error This backup is too large for the backup disk

Hi, I have a 1TB Time Capsule which backs up my Mac. I was having some issues with my mac so I decided to perform an erase and install and then use Migration Assistant to transfer everything back to my Mac.
After I reinstalled Snow Leopard and restored my Mac using Migration Assistant, Time Machine says that the backup has failed. It says " Time Machine Error This backup is too large for the backup disk. The Backup requires 663 GB but only 255 GB are available.
What do I do? Is my only option to erase my Time Capsule and have it back everything up from scratch?

Hi, thanks for the help. I erased everything off of the Time Capsule and it's backing up my Mac from scratch. It's almost finished backing up my whole mac. It's now at 641.86gb of 646.54gb but it's now backing up very slowly. It's backing up .1 every few minutes. Is this normal?
Here's the log from Time Machine Buddy:
Starting standard backup
Attempting to mount network destination using URL: afp://Stuart%[email protected]/Time%20Capsule
Mounted network destination using URL: afp://Stuart%[email protected]/Time%20Capsule
Creating disk image /Volumes/Time Capsule/StuartsMacPro.sparsebundle
QUICKCHECK ONLY; FILESYSTEM CLEAN
Disk image /Volumes/Time Capsule/StuartsMacPro.sparsebundle mounted at: /Volumes/Time Machine Backups
Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
Ownership is disabled on the backup destination volume. Enabling.
Detected system migration from: /Volumes/My Book
Backup content size: 850.0 GB excluded items size: 606.5 GB for volume Stuart's Drive
Backup content size: 425.9 GB excluded items size: 67.3 GB for volume Macintosh HD
No pre-backup thinning needed: 722.56 GB requested (including padding), 928.68 GB available
Waiting for index to be ready (101)
Copied 28.3 GB of 602.1 GB, 29340 of 1478089 items
Copied 55.0 GB of 602.1 GB, 41596 of 1478089 items
Copied 82.9 GB of 602.1 GB, 55899 of 1478089 items
Copied 110.7 GB of 602.1 GB, 63347 of 1478089 items
Copied 138.8 GB of 602.1 GB, 83831 of 1478089 items
Copied 166.8 GB of 602.1 GB, 94574 of 1478089 items
Copied 194.7 GB of 602.1 GB, 102854 of 1478089 items
Copied 222.8 GB of 602.1 GB, 114388 of 1478089 items
Copied 129159 files (242.5 GB) from volume Stuart's Drive.
Copied 248.4 GB of 602.1 GB, 130414 of 1478089 items
Copied 265.5 GB of 602.1 GB, 355699 of 1478089 items
Copied 293.6 GB of 602.1 GB, 382912 of 1478089 items
Copied 322.1 GB of 602.1 GB, 387974 of 1478089 items
Copied 349.8 GB of 602.1 GB, 399204 of 1478089 items
Copied 378.3 GB of 602.1 GB, 399358 of 1478089 items
Copied 406.9 GB of 602.1 GB, 399441 of 1478089 items
Copied 434.5 GB of 602.1 GB, 415817 of 1478089 items
Copied 461.5 GB of 602.1 GB, 471528 of 1478089 items
Copied 488.2 GB of 602.1 GB, 537277 of 1478089 items
Copied 515.1 GB of 602.1 GB, 580446 of 1478089 items
Copied 541.3 GB of 602.1 GB, 590386 of 1478089 items
Copied 566.8 GB of 602.1 GB, 602496 of 1478089 items
Copied 593.3 GB of 602.1 GB, 649575 of 1
Message was edited by: Stuart Lawrence
Message was edited by: Stuart Lawrence

Reliability of restoring from a disk image vs from a "normal" backup file

How would you rate the reliability of restoring your data from a disk image file (a sparseimage file, in this case/question) versus from a 'normal' file, e.g. one created by the Backup 3 app?
I read a few discussions here that mention corrupted disk image files...that result in a total loss of data...as opposed to other types of backup files, in which individual files, or folders, could be corruputed.
For some context: my ultimate goal is (a) to create reliable backup files, e.g. in folders in my Home Folder, stored on an external disk drive, and (b) to secure that data.
Thanks to Niel, in a prior discussion, I discovered that I could create a sparseimage file on the Lacie (encrypted).
http://discussions.apple.com/thread.jspa?threadID=763337&tstart=0
I could then select that secured file as the target / destination for the backup file/s I'm creating with the Backup 3 app. When I log out, that file is locked tight.
But is this 'elegant' solution for backing up data "reliable" when I'll need it at 3am on that dark day when...?
Many thanks.
- David
words to help others' search:
BU3; sparse image;
MBP 15" Core 2 Duo | LaCie d2 250GB ext Mac OS X (10.4.8)

I keep both images of my boot volume which is just OS and apps, and of my home directory. But I also have full regular backups as well. It is not "either or" but a matter of having backup sets that will work. And rotating those sets.
A daily backup, weekly, and monthly. That could require 3 or even 7 or more. Or partitions. But definitely more than one disk drive.
One disk drive backup set should always be safely off line when making a backup set.
Just as I have a clone of the system, an emergency boot drive, and one backup of the last OS revision.
You have to change sparseimage to dmg if you hope to use Apple Disk Utility Restore, especially if you are working from DVD and not from a hard drive.
I've used DU restore and SuperDuper and never seen or suffered a problem or corruption. But I zero drives before use.

Minimum privilege for hot backup

Hi,
Dears,
which privilege is required to take hot backup i want create user to take hotbackup with minimum privilege .now i take hotbackup with SYS user but this is danger because another department should be take hotbackup.
best regards
allahmorad

Allahmorad wrote:
Hi,
Dears,
which privilege is required to take hot backup i want create user to take hotbackup with minimum privilege .now i take hotbackup with SYS user but this is danger because another department should be take hotbackup.
best regards
allahmoradalter database,alter system, create session is enough privileges to make vast changes in your database.So there is not such priveleges.(as fortmann suggested).
I will suggest you to use the rman for hot backup.
Hope this help :)
--neeraj

Excise invoice is meant for normal exports.

Hi Gurus,
In Deemed exports : While raising ARE-3 its showing the following error message:
0000000003/2008 excise invoice is meant for normal exports.
Message no. 4F260
Please share your ideas to go ahead.
I have used same excise group but different series group and number ranges for that series group.
Regards
Sri

Maintained number ranges and in J1iin selected expots under bond.
Its working fine.
Best Regards
Sri

To build web based application for taking backup

Actually , I have prepared menu based scripts for taking backup.
Now what i want to make is WEB BASED APPLICAATION for taking backup. My idea is to build the Web Pages which will call the scripts which i have already buit . But I don't know how through Web Pages I am able to go in the server and call the scripts .
If anybody having any idea regarding this . Pls guide me I am very thankful to him/her.
Thanx
Waiting for valuable advice

Dear Sandeep Saini,
You may develop the web application is used SDK DI Server.
Please refer to SDK help and sample for more information about DI Server.
Best Regards
Jane Jing
SAP Business One Forum team

Password for encrypted backup of device

I need help to change the type of encryption for my iPhone and iPad backups in itunes. I have tried all the passwords I ve used in years and have no clue. Somewhere in Support I found an instruction that did not lead to clearing the password. It did send me to backup to iCloud and do a restoere from there. But this is not what I am trying to acheive. I already was backing up to iCloud. If I need to do a restore from a backup in iTunes on my PC I cannot do it because I cannot provide a correct passowrd for the encrypted backup.
Can anyone help me with a solution?

If the user cannot remember the password for the backup, the backup is useless. There is no way to reset or remove the password requirement.
If the user did not enable backup encryption, the backup is corrupt.
In other words, the backup is no good without the password, delete it and move on with life.

Privelege for normal backup

Similar Messages

Maybe you are looking for