5 To database backup strategy

Hi
We have a large database on AIX with database's 10g and filesystems on DS4800. This DB we'll never be stop. What could be the bests strategies for the backup implementation ?
Regards
Den

Depending on your environment, you may be able to consider Split Mirror Backups with RMAN.

Similar Messages

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

Database backup strategy(MS sql server 2005, Winodws 2003, SAP ECC 6.00)

Hello gurus,
    I am confused, about the backup system i should go for(backup device, abckup software)?? Fllowing is my SAP Landscape.
1) IDES
2) Solution manager
3) Development
4) BIW
no of users 25 max
modules implemented
MM
HR
FICO
BIW
<b>    I want to implemente before go live, backup system in my company.</b>
We have received backup schedule from our implementation partner. Our backup system is as follows.
Backup device is HP Surestore Autoloader.
Cartridge capacity is 100/200GB
Backup software is Veritas (version 8.6)
Note: Through this we take backup of our legacy system and it takes around 3 1/2 hour to 4 hours to take backup of 60 GB of our legacy data.
     Right now the problem is our backup software version is old and i even believe, the hardware we have is not sufficient to take daily database backup and fortnightly, SAP system backup.
    The only solution to the problem i can see is
1) to go for another backup device exclusively for SAP system
2) Even go for SQL Agent software used to take backup of SAP system thorugh Veritas.
3) Even upgrade my Veritas version.
<b>   Its a request to GURUS</b>
1) Is the solution, i am thinking to this issue is correct.?? If no then please advice me
2) Please tell me the best backup system in your opinion for my above mentioned system.
Thanks Gurus
Rahul

Hello,
A indication of the size of each database would be helpful.
However, its NOT a good idea to take only one on line backup a week. What if you have a tape error and cant recover a TL? You have no chance for recovery. This is not best practice. Can the business except a 4,5 or even 6 days loss of data - id guess not.
This is what id do if you don't want to purchase a new device, I would take an online backups from SQL to disk every night - this would be a separate disk! From the disk you can the pick up the backup to take at a time to suit that wont impact the existing backup. Plus you always have two copies of the backup. One on disk, one on tape.
My normal transaction log strategy is similar, again backup to disk, every hour on a production system. Then after midnight move the existing 24 logs into an archive folder. This folder would also be picked up by the existing device at a suitable time before being moved to a 'saved' folder and deleted the next day. Again you always have multiple copies of the data. two on disk, two on tape.

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.

Need Advice on Backup strategy

Hi,
Database version:10.2.0.
Database Size:60GB.
Daily Updation Approximately :2GB.
I need some advice on my backup strategy.
My backup startegy:
Monthly Once, Date: 1 Full backup (Incremental level 0).
Daily Incremental level 2 backup from Date: 2 to 6.
Weekly Once Incremental leve 1 backup on Date:7.
Daily Incremental level 2 backup from Date:8 to 13.
Weekly Incremental level 1 backup on Date:14.
Daily Incremental level 2 backup from Date:15 to 21.
Weekly Incremental level 1 backup on Date:22.
Daily Incremental level 2 backup from Date:23 to 28.
Weekly Incremental level 1 backup on Date:29.
My system requirments are i have only 70GB disk to store the backups, i can store only the full backup in it.So what i am doing is, Am storing the full backup in my disk and am transfering the Incrmental level 1(weekly Once backup) to the Tape and deleting the Daily level 2 backups, after taking that weekly backup.
Is my strategy correct or should i do anything different plz give me some advice.
TIA,

This backup strategy doesn't look bad. However the 70G of free space will be a pain in the neck. I suggest you to increase storage. Have you considered archivelog too? This average 2G daily transaction rate will increase storage requirements, sooner or later, so backup storage requirements.
~ Madrid

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.

Backup strategy in FRA

Hi Experts,
BANNER
Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - 64bit Production
PL/SQL Release 11.1.0.6.0 - Production
CORE 11.1.0.6.0 Production
TNS for HPUX: Version 11.1.0.6.0 - Production
NLSRTL Version 11.1.0.6.0 - ProductionI would like to ask some advice to place my backup in FRA.
I read in a book that it is adviced not to put the archivelog backup in the FRA since if something happen with the disk that store FRA, everything will be gone. However the concept of FRA is a centralized backup logically.
so based on your experiences, what is the best way to utilize FRA for backup strategy?
is it safe to put everything in FRA or we should still split the backup for archivelog to different location?
thanks

The idea is that you should never have a single copy of your backup anyways, be it of whatever file type. Its true that the FRA gone would lead to the non-availability of the backups but then , you should had pushed your backups from it to the tape drive eventually to safeguard them. So there wont' be an harm in putting the backup in the FRA as long as you multiplex the backup and keep it on some another location as well.
HTH
Aman....

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

Any new backup strategy with Oracle VM 3.1 ?

Now, since Oracle VM 3.1 was released, could we be updated with backup strategy.
Backing up OCFS2 repositories allow us protect OVF files right?, but what happen with apps runing on VMs, these data is also backed up? what about open files, databases, etc.
I will appreciate any comment.
Thanks in advance.

try running this on each server:
/usr/bin/rescan-scsi-bus.sh

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

Questions on Oracle EBS backup strategy

Hi all,
Currently I am planning the backup strategy for the EBS. May I know apart from backup the database using RMAN, is there anything (e.g. log files) that I need to backup such that I can fully restore the system?
Thanks a lot in advance.
Alex

I see that this is your first post, and you have not searched on this forum or on google about n-number of responses to your question that various people have already asked.
You didn't mentioned the applicaiton version you are using.
Anyways, you need to take the complete backup of the application tier directories i.e., appl_top, common_top, inst_top, etc.

Defining a backup strategy

Hello all,
I have to help someone to implement a backup strategy on a database.
Before defining the backup strategy I'm doing a document with some questions that the clients needs to answer, so I can recommend the most adequate backup strategy.
I will leave here the questions that I think are useful to ask. Please help me out with this by correcting or adding or discussing questions:
Questions to the client:
- What type of database do you have (data warehouse, transactional,...)?
- Whats the size of the database and what is the expected growth per month/ year ?
- How much information is inserted/updated into the database per day/month?
- What type of backups do you need? daily? weekly? ...
- What MTTR (mean time to recover/repair) do you need for the database?
- How will the backups be done? to the hard drive? to tape? ....
- Do you have a backup agent? If so, witch one do you have? Does the agent has its own scripts or do we need to create them ourself.
- Does the database works 24x7, or can it have any downtime for backup?
I really apreciate you help.

A good start point is the reading of Best Practices for Oracle Database 10g Backup and Recovery which discuss against three important questions :
• How quickly should recovery complete for a datafile, tablespace, and database?
• What is the tolerance for data loss?
• How far back should backups be kept to satisfy the data retention policy?
Nicolas.

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

Full vs. Whole database backup

Hallo!I am studying for my Oracle 10g Administration OCA exam.I am trying to understand the difference between Full and Whole databse backup.
From my notes the definition is as follows
A whole database backup includes all data files and at least one control file. (Remember that all control files within a database are identical.).
Full backups make a copy of each data block that contains data and which is within the files being backed up.
In pratical terms,is there really a difference between these 2 back-ups.
Can a DBA state that he/she is doing a whole database backup as opposed to full backups or vice-versa?
Please clarify the difference between these 2 back-ups.
Thanks.

hi
Normally whole database is backup strategy for which object to be backup .whole,tablespace,datafiles,archivelog is choises.
when you choise whole database backup then next screen ask you backup type you choise full backup or incremental backup.
backup as backup database or backup as copy database is only disk backup type
pls also check above link
http://www.oracle.com/technology/obe/2day_dba/backup/backup.htm
hope this helps
zekeriya

5 To database backup strategy

Similar Messages

Maybe you are looking for