Regarding an External HD Backup Strategy...

I have tried some of the suggestions for a backup strategy and need more help. I partitioned the external drive (LaCie 250 GB via Firewire 800) into three volumes: one volume large enough for a clone of my internal HD, one volume for Mac OS X and TechTool Pro, and one for data.
1. When partitioning using Apple's Disk Utility, I could only choose one "option" for all volumes: the best options included "GUID Partition Table" (If I want to use that disk to start up an Intel-based Mac) or Apple Partition Map (If I want to use that drive as a non-startup disk with any Mac). I checked the box for Mac OS 9 drivers to be installed and chose the Apple Partition Map. I did this because I used SuperDuper! to clone my HD and checked the option to make that backup bootable (which is an option in SuperDuper). Is it still bootable on a non-GUID formatted drive? Are the Mac OS 9 drivers necessary? Does it hurt to have them?
2. When I install Mac OS X and TechTool Pro on the other volume, how do I make that volume bootable? When this is done, do I have to boot from this volume to update to 10.4.9? Will the Mac OS 9 drivers hinder this volume when I try to boot from it?
3. In case I do need to reformat using the GUID Partition Table, can I still store data on a volume that I don't intend to boot from? Should I still install the Mac OS 9 drivers if I am installing Mac OS X?
4. Is there a way to safely test these bootable volumes and the backup?
Thank you for your time and advice.

1. GUID is fine, but you don't need an OS9 drivers on an Intel Mac, no harm if they are on there.
2. At start up you hold down [option] and it will list all possible Boot volumes, select the one you wish to use.
3. Yes you can store data on any format, the main impact the format has in that case is whether the volume is read/write capable from Mac OS and/or Windows.
4. Once you've made your clone of the main hard drive onto the external volume, reboot holding down [option] and try booting from it ...

Similar Messages

IPhoto file and backup strategy

I am new to iPhoto in last 9 months, but before I get in too deep, would love some advice about how I am structuring the library and about my backup strategy.
Spent many years on Windows where I would use a typical file Windows file structure. Broke my pics down into years, then events, then pics. Some pictures I would rename "Ella Bday 2006" and others are simply "jpeg-10006". When I moved to the Mac, I've started to use events "Ella Bday 2008" or else "Jan-Mar 2009". I've read that many prefer to create albums and not rely so much on the events. I am not there yet, but that's my next goal.
My questions are multiple. First, what is the best way to backup all this data so that if I crash, I can easily recreate? I backup the windows files in the same file structure as they existed on my HD, but with photos, events, albums, etc I am not sure the best way on the Mac.
I did import all the windows pics into iPhoto -- so now I have a single app for all photos dating back to 2004. I am not using Time Machine (remember I am a newbie) at the moment, and my initial plan is to back up each year to a separate DVD for off-site storage. Once this is done, I will look for a more permanent and recurring backup strategy - Time Machine I suppose - that will use an external HD.
Sorry if my post is convoluted, or if my questions are ignorant, but I was a lifetime Windows guy who is just exploring all the features/functions of Mac -- so any advice or redirection would be fantastic!
Thanks in advance

First, what is the best way to backup all this data so that if I crash, I can easily recreate?
Make a copy of the iPhoto Library in your Pictures Folder. That gets all the photos and database files which contain your organisation.
If you want to burn a copy of the Library to DVD use the Share => Burn command.
FWIW here's my back up system. I used to use DVDs but it was too tedious and a bit expensive too. Remember, if you burn, say 2005 to DVD ths year, you will be burning it again in a couple of years as DVDs to degrade over time.
My Library lives on my iMac.It’s Backed up to two external hard disks every day. These disks are permanently attached to the iMac. These back ups run automatically. One is done by Time Machine, one is a bootable back up done by SuperDuper
It’s also backed up to a portable hard disk when ever new photos are added. This hard disk lives in my car. For security, this disk is password protected. For this job I use DejaVu because it makes a simple back up that is clear and can be tested easily without doing an full restore.
I have a second off-site back up at a relative’s house across town. That’s updated every 3 or 4 months.
My Photos are backed up online. Personally I use SmugMug but there are many options including flickr. However, check the terms of your account carefully. While most sites have free uploading, you will often find that these uploads are limited in terms of the file size, or the bandwidth you can use per month. For access that allows you to upload full size pics with no restrictions you will need to pay.
Every couple of months I test the back ups to make sure they are working correctly. It’s very easy to mis-configure a back up application, and the only way to protect against that is to do a restore.
Regards
TD

Cut-to-case backup strategy

Me is on seting up a concept of backup strategy for mbp being planned to be used in our environment.
Till now no experience with mac clients at all.
We will do it stepwise. At the beginning the Mavericks on-board tool for backup Time Machine.
As soon as bit conformable with platform disk cloning will possibly be included in the process.
But only if Time Machine not sufficient for our needs.
Finally if one day it turns out it all does not suite to our needs a switch to 3rd party backup solutions will be conducted.
However this day me can see some signals saying the Time Machine will not
be suitable due to functional limitations. So for final decision bit more information is needed.
We plan to use NAS attached to router as backup destination storage.
Mass storage of nas will be formatted in NTFS. Mac client will get access to nas for
purposes of backup at regular cycle but not continuously, let's say 1 time a week - this corresponds to current
backup strategy and fulfills the needs completely.
As far mine understanding is the TM drive (backup target) removes backed up items in following situations
- as soon as the remaining storage space is below some limit the oldest increments
get removed, number of increments being removed depends on how quick the minimal free space
requirement if met.
- there is no warranty a file is backed up on TM drive as soon the drive gets connected to mac client
and the original item no more exists on the client's drive (source)
A. Is the above understanding fine? Any other situation to be added onto the list?
B. Local snapshots: Is this how the foundation of mac os trash bin are built and look?
C. Or is the mac os trash bin a function and implementation independent from TM local snapshots?
So a nas is planned to store the backup files. Additionally a usb 3.0 drive is planned to backup the backup nas.
In emergency situation where the mac os will following procedure will need to be conducted.
step 1, By other means the backup files are to be copied from ntfs formatted nas storage to
external drive - usb or thunderbolt - formatted using mac os conform file system.
step 2, external drive with TM backups prepared as above to be connected locally to mac client
step 3, recovery using Recovery HD is to be carried out.
Is the above understanding fine?

Yes, you are right.
In the meantime have had more read about TM.
As the well-known article does it claim it in the beginning indeed a complicated
and mysterious machine.
I guess for the same reason one needs more than one read runs
to have an overview.
Now I am aware, TM is proprietary and rather a closed-platform system.
Those components are not standardized. If any grade of flexibility is shown
it is so thanks to capabilities of that proprietary system.
I see some functional limitations shown by TM which immediate disqualify this
solution in our environment. We will need to take a 3rd party solution.
What a pity, the costs continue to explode.
Cloud based solution will not be acceptable due to connection rates
in my region. It is also quite regular case here to be left without broad -band connection
for more weeks after had changed the flat.
Also due to mine concerns regarding data security basically nowadays.

Long-term retention backup strategy for Oracle 10g

Hello,
I need design a Archivelog, Level 0 and Level 1 long-term retention backup strategy for Oracle 10g, It must be based in Rman with tapes.
¿Somebody could tell me what it's the best option to configure long-term retention backups in Oracle?, "CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 1825 DAYS;" It's posibble ?
Regards and thanks in advance

Hello;
RECOVERY WINDOW is an integer so yes its possible. Does it make sense?
Later My bad, this is Oracle 11 only ( the gavinsoorma link ) . Getting harder and harder to think about 10. Don't think I would use RECOVERY WINDOW.
I would let the tape backup system handle the retention of your rman backups.
Using crosscheck and delete expired commands you can keep the catalog current with the available backups on tape.
Oracle 10
Keeping a Long-Term Backup: Example
http://docs.oracle.com/cd/B19306_01/backup.102/b14191/rcmbackp.htm#i1006840
http://web.njit.edu/info/oracle/DOC/backup.102/b14191/advmaint005.htm
Oracle 11
If you want to keep 5 years worth of backups I might just use KEEP specific date using the UNTIL TIME clause :
keep until time 'sysdate+1825'More info :
RMAN KEEP FOREVER, KEEP UNTIL TIME and FORCE commands
http://gavinsoorma.com/2010/04/rman-keep-forever-keep-until-time-and-force-commands/
Best Regards
mseberg
Edited by: mseberg on Dec 4, 2012 7:20 AM

Need help with backup strategy

So my 2 TB backup drive failed this morning. I'm using a Seagate drive in an OWC external enclosure. I plugged it in and the drive didn't pop-up on the desktop, nor is it visible in Disk Utility.
I know that all drives eventually fail, but it seems like I've had more than my fair share of problems lately. This is of course making me think hard about my backup strategy. Here's what I'm doing now - I'd appreciate your thoughts on how to make it even more "bulletproof".
> TimeMachine back-up of boot drive and media drive (with photos, documents, movies, etc.)
> External clone of boot drive and media drive (on two partitions) - this is the one that failed
I suppose I could add a third external clone for redundancy, but an offsite backup would probably be even better. Not quite sure what the best option is there, though. Any ideas?

I too love automation. However, an automated backup requires the backup drive to be always connected (and maybe powered) in order to perform the backup. Also, the computer you speak of must remain on (by the sounds of it) 24/7 in order to do a nightly back up at midnight.
First of all, it probably is not the best to leave your puter on 24/7. I won't go into all the OS reasons why. But here are 2 other reasons to think about:
1) Your internal HD will always be powered, bad on drives
2) You are constantly using power to run your system. Not good for your power bill or the greater environment
As for the always connected Backup HD- I only connect, and power on my backup when I go to do a backup. This leaves it disconnected in case of virus infection. And powered down/disconnected removes some of the risk of damage from power surges/spikes (yes I use a UPS, but these can/have failed)
So to sum up: I back up everyday. What I do is after I am done working in LR for the day I shut it down, and than start it back up (ugh) so that I can back up my Library with all the work I just did (wish Adobe would do a back up upon closing!!!)
Than I close down LR AGAIN..... Than I connect my Back up HD. Via usb, once connected it automatically powers up and fires up the back up software. All I do is hit start. Since this is an incremental back up it only takes a short while. I go use the "John" grab a drink, and come back unplug the Back up HD, and turn off the system for the day.

InfoProviders backup Strategy in SAP BW

Hello;
Does any one experienced a backup issue with BW especially when you would like to perform a risky modification. Is there any backup strategy that is supported by SAP for any modifcation senario, if it is a small modification or also a big one affecting one or more infoproviders. if there is any document please share with us.
Regards
Anis

Hi,
After the modification if you want original cube structure mean you need to roll back your transports with help of basis team. About roll back you cross check with basis team
Before doing the changes first have exact informations from your client or users.
If you think like that as need original cube structure then you can on copy cube structure at prod and move to dev thru transport.
When you need same or old cube structure, from dev you can move to prod or roll back option.
Thanks

Best backup strategy

Time Machine is brilliant. It's saved me many times.
But recently, the backup drive with a year's worth of backups, died.
I therefore lost ALL my backups.
Not a major problem as I still have my current data and having re-formatted the Time Machine drive it's merrily backing it all up again. (I just hope I don't need to recover to last week's backup ... as I no longer have it.)
But until that's finished I have NO backups! Eeek!
So what is the best backup strategy, bearing in mind drives can fail, houses can burn down, etc. Should I have two or three Time Machine backup discs and keep swapping them every day so if one dies I've still got a one-day-old version?
Making DVD backups and storing them elsewhere is very time consuming and while my data is really important to me, it defeats the object if I can get on with any work on that data as I'm constantly burning to lotsof DVDs!
Your views would be appreciated!

I pretty much do a similar thing, but my offsite backup goes to a locked cabinet in my office (easier to get to weekly to bring home and update then using a bank - I honestly cannot remember when I last physically went to my bank, its been years).
TM makes a great source for restoring single files or being able to go back to an earlier version of a file. And the clones are easier for full restoration, or even for booting from temporarily if the machines boot drive dies and you just want to get in to deauthorize it before sending in for repairs or such. Always good to have a bootable clone around, for many reasons.
My external clones are on firewire 800 bus powered portable drives, again for simplicity (no power cables or bricks to go with them).
I also still burn to optical disc for specific things like filed tax returns, and other financial documents I need to keep around in the fire safe for some period of time.

Backup strategy

Hi,
short story:
Due to the structure of the library I have the "originals" and "modified" images, when edited some. When importing a library into another without copying them I have some/many thumbnails twice. How do I prevent iPhoto to use the original thumb when a modified exists?
Long story:
I'm looking for a working backup strategy for iPhoto. I'd like to collect fotos over the time and when the library reaches some GByte I'd like to copy it to two external drives in a software raid set (mirror). I know that I can merge the two libraries (one on raid, one on MacBook) with some piece of software. So far so good.
Now I'd like to have the thumbnails of the fotos on the ext. drive on my MacBook as well. I can import them to a library with the option not to copy the images but leave them where they are (on ext. drive). When I'm on the go I can access the thumbnails. When viewing them I am asked to insert the drive.
But now comes my problem: Due to the structure of the library I have the "originals" and "modified" images, when edited some. So I have some thumbnails twice. How do I prevent iPhoto to use the original thumb when a modified exists?
Thanks a lot.

What you really need to use isMedia Expression. It creates catalogs containing thumbnails of the cataloged photos and the catalog can be used without the source file being available.
You can add keywords and other identifiers to the photos while just using the catalog and then when you get back and have the source files available the new metadata can be applied to the actual file.
Expression Media appears to be available for the upgrade price of $99 if you are using iPhoto as shown here:
$99 (Full Version $199)
For qualifying owners of:
Licensed copy of an earlier version of Expression Media or any iView Multimedia product.
OR
Any licensed photographic software, including Windows Photo Gallery or iPhoto
That info is from this site: http://www.microsoft.com/expression/products/Upgrade.aspx and by clicking on the "here" link on that page. I've emailed the developers to see if I've intrepreted that page correctly.
In the meantime you can download and run the demo. You can also catalog your iPhoto library with EM and write all metadata entered in iPhoto back to the original files. Steps 1-7 of Old Toad's Tutorial #1 describe how. That page is in revision since iView is no longer available and Step #2 is slightly different with the EM demo. It should be changed by the end of the day today.
I use it in conjunction with iPhoto. EM is my primary DAM (digital asset management) application and I use iPhoto for projects like books, calendars, slideshows, etc.
TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto (iPhoto.Library for iPhoto 5 and earlier) database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
I've created an Automator workflow application (requires Tiger or later), iPhoto dB File Backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. It's compatible with iPhoto 6 and 7 libraries and Tiger and Leopard. Just put the application in the Dock and click on it whenever you want to backup the dB file. iPhoto does not have to be closed to run the application, just idle. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.
Note: There's now an Automator backup application for iPhoto 5 that will work with Tiger or Leopard.

Best practice PDW database backup strategy/plan

Hello All,
We are ready with PDW infra , appliance is almost ready. we are planning for implementation.
but before that , I have to document best practice for PDW database backup strategy/plan.
since PDW environment is pretty new . Please help me with best backup strategy/plan which can
be followed to implement in my proposed PDW solution.
your suggestions will be highly appreciated.
Regards,
Anish.S
Asandeen

Hi Anish.S,
According to your description, you want to backup SQL Server Parallel Data Warehouse (PDW) database.
Before we get to the backup and restore syntax, it’s worth noting that the Parallel Data Warehouse (PDW) appliance architecture offers an environment that greatly enhances backup times (due to dedicated storage and network interfaces, see the following post
for more information -
https://saldeloera.wordpress.com/2012/07/09/lesson-1-of-parallel-data-warehouse-basic-architecture-overview/).
For more details how to backup and restore database on PDW, please refer to the following blog:
http://www.sqlservercentral.com/blogs/useful-information-and-case-studies-covering-data-warehousing-data-modeling-and-business-intelligence/2012/10/04/parallel-data-warehouse-pdw-how-to-using-backup-and-restore-database-on-pdw/
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Backup strategy for ebs R12?

Hi,
I have a couple of questions regarding to backup strategy for ebs R12.
Let's say that we have one application server and one database server running, and we would like to have a backup periodically for both servers.
This means that we want to have the exactly same backup of configurations and other files for the application server and the database server in case of any fatal crashes in the servers.
I went through some discussion threads and it seems common way is to use RMAN for the data of database and file system copy for application and database servers. But, I would like to know what's the best way or recommended way for the backup strategy for data and server files of Oracle e-business suite.
Do you guys have any suggestion for this?
Thanks in advance.
Cheers,
SH

Hi SH;
I suggest check first our previous discussion
backup and recovery startegy for EBS
Re: Backup System
Backup Policy for EBS can
If you make search you can find many other thread which is mention same question
For your issue basicly what we do
1. For our prod db, if possible we take weekly cold backup(sunday) and take rman backup also daily(full backup, but it depends system you can prefer to take incremental)
2. For our system we take file system backup weekly(OS base)
3. For application we take backup every sunday(for some system 15 days or 30 days period). The most important point here if your system prod, and if you need to apply patch to your system you need to have valid backup and also need backup for after patching
One other important issue is we run preclone sh before take backup for apps and db tier
Regard
Helios

SMD Diagnostics Agent Backup Strategy?

Posting this question here as well as the Solution Manager forum since we're running SAP on the iSeries.
My organization has just started deploying SMD agents across our SAP landscape and we're considering how this new component (the agent) fits in our backup strategy. Should the agents even be included in our periods backups? They're small, easy to reinstall if necessary, and don't store any data, but would have to be re-registered. Any other backup consideration? We're interested in how other organizations have dealt with this question, thanks for your input!
Robert Garst
Perrigo SAP Basis Team

Hi Robert,
as you already supposed I wouldn't include SMD agents in the backup strategy since they are little and don't store data. What's important is the central Solution Manager System itself. There the data reported by SMD agents is used and stored.
Best regards,
Christoph

Production Database Advance backup Strategy

Hi,
Now I am taking the backup with Rman Scripts daily after 6 PM. But the problem is that my company can not afford any data loss. I want to implement the backup advance backup startegy. Please I am going implement the advance backup strategy. Environment is
1.EBS R12.0.4
2.Database 10g R2.
4.Plateform RHEL AS 4.0.
Please guide me step by step how can I implement this backup startegy.
Help will be highly appreciated.
Regards.
pzdba

Now I am taking the backup with Rman Scripts daily after 6 PM. But the problem is that my company can not afford any data loss. I want to implement the backup advance backup startegy. Please I am going implement the advance backup strategy. Environment is What is you current backup mode
What kind of advance strategy are you looking for
If you are in archivelog mode and have your archivelogs
If you are backing up full
if you are backing up to the disk and your mirrored that disk in case of loosing disk failure
What kind of advance backup strategy you need more ?
what you need is testing the consistency of you backups. If they are consistent if you can recover the database it means you dont have data loss option with your current strategy.
Also you need to be sure about the time of backup to cover your needs.

Performance & Backup Strategy Approach

I purchased a MBP last October. I love this machine. I also have 2 External HDs that I use for primary (working) disk for my images and a boot partition and the other External HD for a backup copy of all images from the 1st External HD. I am considering making some changes/upgrades and would like some opinions. I am not going to discuss specific products as I would like to keep the discussion to the approach and not brand.
Main Purpose/Uses are for Digital Photography. I use Photoshop CS3 and Lightroom. These are the two main applications. I also run Parallels (usually when I am not doing my digital Photography work) to run MS Office apps.
Currently this is my setup:
MacBook Pro 15 2.4 GHz, 2GB RAM (667), 160GB 7200 HD
This internal drive is used for OS and Applications
The Lightroom Catalog is also on the internal HD /Users/myname/Pictures/Lightroom
The CS3 Scratch Disk is also located on the internal drive
2 External HD 500GB ; Western Digital My Book Pro (USB, FW400 & 800) Both connected via FW800. The second daisy chained to the first
The first drive is partitioned into Two MAC OS Extended Partitions consising of a Boot Clone (150GB/80GB available) as a backup of local documents (office, email, etc) that reside on my MBP internal drive and in case I need to boot from other than the internal drive. The other partition is for Storage (315GB/154GB available). This partition is where I keep all of my images (RAW, JPG, PSD, etc). This is the critical data.
The second drive is a single partition also MAC OS Extended (465GB/304 Available). This single partition is a copy of the Storage partition from the 1st External Hard drive another copy of my images.
I use SuperDuper to 1) refresh the Boot partition from my internal drive each night, 2) copy my data partition from External HD 1 to External HD2 each night.
I am considering the following changes. My goals are 1) Better performance specifically for CS3 and Lightroom (as well as in general) and 2) more robust backup protection.
Upgrade to 4GB of RAM from 2GB
Add another drive that will become my Primary Data Drive that contains all of my images and that I work from. Takes the place of the current 1st Drive that has the 2 partitions. I am considering 1 TB ; Raid 0; eSATA via card on my MBP. I will Partition this new drive in to 2 Partitions - 1) CS3 Scratch Disk
and 2) Primary Data Storage and working disk for all of my images
The Current 1st 500GB External Drive will remain the same boot partition and data partition. But, this drive now becomes on-site backup of the Primary storage from the new drive above as well as the Boot partition. Thus I now have my primary storage on eSATA Raid 0.
The Current 2nd 500GB External Drive will be reformatted and partitioned to look just like the current 1st 500GB External Drive and will also contain a boot partition and a 2nd partition for my data. However, this drive will be refreshed every week and then taken offsite for safety and protection.
How does this sound?
Any major issues? Any gotchas?
How big should the CS3 Scratch Disk partition be?
Will I gain better performance?
Is this a better backup strategy now that I incorporate offsite refresh once per week?
Thanks so much for you input in advance. I really do appreciate it.
David

Perhaps Phos+/_ four dots can respond.

RMAN Backup Strategy Comment Needed

Hi,
Currently I'm trying to implement a backup strategy with RMAN.
Scenario: My side we're 5 days operational (Monday to Friday). I'm planning my backup as follow:
Mon – Incremental level 1 differential
Tue – Incremental level 1 differential
Wed – Incremental level 1 cumulative
Thurs – Incremental level 1 differential
Fri – Incremental level 0 (aka full database backup)
I planned Mon,Tues and Thurs as an incremental differential, while Wed as an incremental cumulative. With Wed as a cumulative backup, my thinking is that if my db is to fail on Thurs/Fri, my recovery will need to apply fewer backups but at the expense of storage.
Any comment or view about the strategy will be greatly appreciated.
Thanks and Regards
Eugene (ET)

hi,
there is Oracle suggested backup strategy
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/bkup004.htm
other
http://books.google.cz/books?id=3aEIIqRHkY8C&pg=RA1-PA326&lpg=RA1-PA326&dq=oracle+rman+backup+stratery&source=bl&ots=DrnVZ3tZPs&sig=QajKM0SXbpoa3eWZgl5kmwmSUPI&hl=cs&ei=o6xcSvSaCpKwsAbmu8yVDA&sa=X&oi=book_result&ct=result&resnum=4
Regards,
Tom

The backup strategy

What would be the backup strategy for the following database:
Documentum application. The database keeps references to the files on filesystem. Both database and filesystem with documents should be in sync.
Using only the RMAN probably not the perfect solution here; I do not know whether it is possible to backup plain filesystem from it.
So far, I end up creating snapshots of the database and documents' file-structure when the database in hot-backup mode or down. The snapshot is the feature of the NetApp filer and once created it can be backed up on a conventional way by copying files to the backup media. The creation of the snapshot is also instantaneous so the down time for the application and database is minimal. The disadvantage of such method is in complicated recovery, but I did not find anything better than this so far. Any ideas will be appreciated.
Regards
Leonid

Hi.To building backup recovery strategy depend some reasons.This strategy must prevent and safe your database against media fails(disk problem) user fails(human errors).Therefore firstly place your database in archivelog mode as:
sqlplus "/as sysdba"
shutdown immediate;
startup mount;
alter system set db_recovery_file_dest='flash_recovery_area'
/*(recommended that backups including all archivelogs placed in FRA)*/
alter database archivelog;
alter database open; Also you can take every day incremental backup using RMAN and weekend you can take full(level 0) backup
rman target /
run{
backup incremantal level 1 for recover of copy with tag 'incr_db' database ;
recover copy of database with tag 'incr_db';
}and enable flashback on for user errors.In additionally you can use dataguard,create standby database.Using this way you prevent your database against disasters. For more information see below links;
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/strategy.htm#i1005311
http://download.oracle.com/docs/cd/B14117_01/server.101/b10823/create_ps.htm

Regarding an External HD Backup Strategy...

Similar Messages

Maybe you are looking for