Runlevel for taking backups

I'm sure I've seen somewhere a recommendation to use runlevel one to take backups to ensure filesystem consistency, however that kills automation unless I handle it through inittab, which seems a bit backwards. So, how essential is having an unchanging filesystem when running rsync to backup everything and how else could I ensure a stable filesystem without runlevel switching? I thought about remounting partitions read-only, but that doesn't work if something is using them.
Last edited by Barrucadu (2010-05-31 22:12:25)

Doing file-system level backups are generally fine* without changing run-levels.
As bruce mentioned, if you want to do block-level backups using dd or dump then it becomes important.
At the end of the day, doing the backup is only half the job. You have to do test restores as well, so that will highlight if you have any issues with your backup stage.
* Exceptions to this are things like database files. The files will backup OK, but if the database is running, then you've backed them up in an "open" state which the DBMS may not like recovering from in a restore situation. Text files, music, movies, documents etc should be fine.

Similar Messages

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

What commands used for taking backup of oracle database using BR*Tools

Can somebody please help me urgently to know what are the commands used for taking backup of oracle database using BR TOOLS.Also specifythe commands in detail which can be used for taking backups of oracle database ,Online Redo log files in databse using BRBACK tool,Archiving of offline, redo log files using BRARCHIVE, and Restoring a Database using BRRESTORE tool Commands(Plese specify the commands with their Syntax used).Also specify the commands with their Syntax which are used for taking backup of oracle database(online,Offline redo log files) into Tapedrives using BRTOOLS commands.
Thanking You for helping (in advance).

Dear Ashish,
BRBACKUP / BRARCHIVE calls the operating system command to copy the files.
Simple approach to get the commands is as follows.
1. Set the BR_TRACE (as given in the SAP note 29321) and run the command for which you need to know the OS / SQL commands.
2. This will generate the log file with the trace information. This trace has the information of the commands used by the job you have run.
Hope this helps.
Regards,
Madhukar

Can legato be compatible for taking backups with RMAN

can legato software be compatible for taking backups with RMAN
oracle 10g
Message was edited by:
user531314

Rman is so feature rich and yiou can integrate your third party backup software with rman to take backups, there is nothing to worry in your case, this is very much in the reach.
hare krishna
Alok

For Taking Backup with BRTOOLS

Hello,
I want to take backup with BRTOOLS utility.
Please tell me that exact scenario of taking backup with BRTOOLS.
Thanks
Mohit

Mohit,
Check below link.
http://help.sap.com/erp2005_ehp_04/helpdata/DE/8d/991ce04c81054a96b30469835cb11d/frameset.htm
Hope it helps
Thanks
Sushil

Steps for taking bachup of oracle database

Can anyone please help me urgently to know what are the steps and commands used with BR*Tools with their SYANTAX in detail for BRBACKUP for taking backup of (datbase files,Online redolog files,control files) ,BRARCHIVE for taking backup of offline redolog filesand BRRESTORE for restoring of a datbase backups(Please give the syntax for taking backup of Oracle database in Tapedrives using BRBACK,BRARCHIVE,BRRESTORE.)
Thanking you for helping(in advance) .

help yourself
-> <a href="http://help.sap.com/saphelp_nw04/helpdata/en/50/7dd41742210144aee3fdee21c553eb/content.htm">BRTools in Detail</a>
GreetZ, AH

TCODE FOR DATABASE BACKUP

Hi All,
Please let me know the complete procedure for to take backup of all database tables in request form.
Mean What is tcode for taking backup of all database in 3 requests?
Thanks In Advance.

Hi Naveen.
I would like to suggest,
The Transaction code for backups is DB13.
Generaly, the transactions related to DB backup management start with DB letters.
I would like to suggest a few references,
[SAP HELP - Standard References for Database backup by BR Tools|http://help.sap.com/saphelp_47x200/helpdata/en/0c/cd271365debc42bef96ac7fd907787/content.htm]
[SDN - PDF - Standard Reference for Database Backup Utility|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d8fc1f3a-0d01-0010-1c84-ac8bee9f7c9b]
Hope that's usefull.
Good Luck & Regards.
Harsh Dave

Process for taking the Oracle 9.2.0.5 backup on solaris

Hi All,
Thanks for you support.
Please help me on this
Process for taking the Oracle 9.2.0.5 backup on solaris

i am new to DBA activity's. that's why i am looking
for guidence, to take the oracle 9.2.0.5 backup on
solaris.Still please be specific what's your problem is.
Is your database down you can't get it startup ,
or your database is crashed you need to recover it?
Define 'backup'
At least tell us what you did and what you didn't, if you have no clue what's going on check Oracle document,
http://download.oracle.com/docs/cd/B19306_01/server.102/b14196/toc.htm

Error while taking backup through RMAN in 10g XE

While taking backup through RMAN in XE instance , an error comes out.
The contents of oxe_backup_current file is as below :
XE Backup Log
Recovery Manager: Release 10.2.0.1.0 - Production on Wed Jul 6 15:49:51 2011
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: XE (DBID=2635631092)
RMAN>
echo set on
RMAN> shutdown immediate;
using target database control file instead of recovery catalog
database closed
database dismounted
Oracle instance shut down
RMAN> startup mount;
connected to target database (not started)
Oracle instance started
database mounted
Total System Global Area     805306368 bytes
Fixed Size                     1261444 bytes
Variable Size                209715324 bytes
Database Buffers             591396864 bytes
Redo Buffers                   2932736 bytes
RMAN> configure retention policy to redundancy 2;
old RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
new RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
new RMAN configuration parameters are successfully stored
RMAN> configure controlfile autobackup format for device type disk clear;
RMAN configuration parameters are successfully reset to default value
RMAN> configure controlfile autobackup on;
old RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP OFF;
new RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP ON;
new RMAN configuration parameters are successfully stored
RMAN> sql "create pfile=''/usr/lib/oracle/xe/app/oracle/product/10.2.0/server/dbs/spfile2init.ora'' from spfile";
*sql statement: create pfile=''/usr/lib/oracle/xe/app/oracle/product/10.2.0/server/dbs/spfile2init.ora'' from spfile*
*RMAN-00571: ===========================================================*
*RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============*
*RMAN-00571: ===========================================================*
*RMAN-03009: failure of sql command on default channel at 07/06/2011 15:50:57*
*RMAN-11003: failure during parse/execution of SQL statement: create pfile='/usr/lib/oracle/xe/app/oracle/product/10.2.0/server/dbs/spfile2init.ora' from spfile*
*ORA-27086: unable to lock file - already in use*
*Linux Error: 11: Resource temporarily unavailable*
Additional information: 8
Additional information: 16476
RMAN> backup as backupset device type disk database;
Starting backup at 06-JUL-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=102 devtype=DISK
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00003 name=/usr/lib/oracle/xe/oradata/XE/sysaux.dbf
input datafile fno=00005 name=/usr/lib/oracle/xe/oradata/XE/ftress_data_log01.dbf
input datafile fno=00006 name=/usr/lib/oracle/xe/oradata/XE/ftress_data_lrg01.dbf
input datafile fno=00001 name=/usr/lib/oracle/xe/oradata/XE/system.dbf
input datafile fno=00009 name=/usr/lib/oracle/xe/oradata/XE/ftress_indx_log01.dbf
input datafile fno=00010 name=/usr/lib/oracle/xe/oradata/XE/ftress_indx_lrg01.dbf
input datafile fno=00002 name=/usr/lib/oracle/xe/oradata/XE/undo.dbf
input datafile fno=00004 name=/usr/lib/oracle/xe/oradata/XE/users.dbf
input datafile fno=00008 name=/usr/lib/oracle/xe/oradata/XE/ftress_data_sml01.dbf
input datafile fno=00012 name=/usr/lib/oracle/xe/oradata/XE/ftress_indx_sml01.dbf
input datafile fno=00011 name=/usr/lib/oracle/xe/oradata/XE/ftress_indx_mdm01.dbf
input datafile fno=00007 name=/usr/lib/oracle/xe/oradata/XE/ftress_data_mdm01.dbf
channel ORA_DISK_1: starting piece 1 at 06-JUL-11
channel ORA_DISK_1: finished piece 1 at 06-JUL-11
piece handle=/usr/lib/oracle/xe/app/oracle/flash_recovery_area/XE/backupset/2011_07_06/o1_mf_nnndf_TAG20110706T155057_718dw649_.bkp tag=TAG20110706T155057 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:15
Finished backup at 06-JUL-11
Starting Control File and SPFILE Autobackup at 06-JUL-11
piece handle=/usr/lib/oracle/xe/app/oracle/flash_recovery_area/XE/autobackup/2011_07_06/o1_mf_s_755797849_718dwofy_.bkp comment=NONE
Finished Control File and SPFILE Autobackup at 06-JUL-11
RMAN> configure controlfile autobackup off;
old RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP ON;
new RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP OFF;
new RMAN configuration parameters are successfully stored
RMAN> alter database open;
database opened
RMAN> delete noprompt obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
using channel ORA_DISK_1
Deleting the following obsolete backups and copies:
Type                 Key    Completion Time    Filename/Handle
Backup Set           3      06-JUL-11
Backup Piece       3      06-JUL-11          /usr/lib/oracle/xe/app/oracle/flash_recovery_area/XE/backupset/2011_07_06/o1_mf_nnndf_TAG20110706T133443_7184wr4d_.bkp
Backup Set           4      06-JUL-11
Backup Piece       4      06-JUL-11          /usr/lib/oracle/xe/app/oracle/flash_recovery_area/XE/autobackup/2011_07_06/o1_mf_s_755789675_7184x7fp_.bkp
deleted backup piece
backup piece handle=/usr/lib/oracle/xe/app/oracle/flash_recovery_area/XE/backupset/2011_07_06/o1_mf_nnndf_TAG20110706T133443_7184wr4d_.bkp recid=3 stamp=755789684
deleted backup piece
backup piece handle=/usr/lib/oracle/xe/app/oracle/flash_recovery_area/XE/autobackup/2011_07_06/o1_mf_s_755789675_7184x7fp_.bkp recid=4 stamp=755789699
Deleted 2 objects
RMAN>
Recovery Manager complete.
RMAN error: See log for details.

I think it is trying to overwrite exiting file. Either give a different name or cleanup the files in preferred location.

This backup is too large for the backup volume - ridiculous Size!!!

Hi .. i own a macbook 13" aluminium, I have Snow Leopard 10.6.2 , and i change my internal hard drive to a 500Gb.
I bought 1Tb Western Digital My Book USB External Drive to use it for back ups using Time machine.. at the beginning worked great, when i changed my hard drive i restore everything in lest than 2 hours.
Then one time, it said that the hard drive where going out of space, and i said to delete the oldest backups, it erase everything and kept the last back up. Since then, it came a message
*_+This backup is too large for the backup volume. The backup requires 2.73EB but only 995 Gb are available.*+_
its ridiculous, when i go to the time machine preference, it said that the full size back up it would take 83Gb only.
I tried everything, formatting the unit, taking out the partition , and making it out again, it makes the first full back up, but then the same message...
Please anyone... i am desperate
Thanks Again
Daniel

DanielFaour wrote:
*_+This backup is too large for the backup volume. The backup requires 2.73EB but only 995 Gb are available.*+_
Hi, and welcome to the forums.
That message seems to indicate that something is corrupted on your internal HD. Do a +*Verify Disk+* on it, per #A5 in the Time Machine - Troubleshooting *User Tip,* also at the top of this forum.
If that finds errors, you'll have to use the procedure in the yellow box there to Repair them.
If that does not find errors, Restart your Mac and do a "full reset" of Time Machine, per #A4 there.
I tried everything, formatting the unit, taking out the partition , and making it out again, it makes the first full back up, but then the same message...
What partition? Are there multiple partitions on your TM drive? How large is the one for Time Machine? Check the setup per #C1 of the Troubleshooting Tip.

"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!

This backup is too large for the backup disk

I have a 1TB time capsule used to backup two MacBooks. One backup file is 817GB (MacBook 1) and the other one is 137GB (MacBook 2).
I get an error message when running the backup on MacBook 2. It says "Time Machine could not complete the backup. This backup is too large for the backup disk. The backup requires 55.64GB but only 42.98GB are available"
I always though the TimeCapsule would automatically remove older backupos to make space and you would never run into such an issue.
Please not that my MacBook 1 was stolen a while ago so I do not know how to reduce the size of the larger backup.

Karl R. wrote:
I always though the TimeCapsule would automatically remove older backupos to make space and you would never run into such an issue.
Usually that's true, but not always. One exception is, Time Machine will delete the oldest backups of the Mac it's running on, but not any other Mac's backups. That's probably what you've run up against here.
Please not that my MacBook 1 was stolen a while ago so I do not know how to reduce the size of the larger backup.
First, connect to the TC via Ethernet.
If you want to delete all the backups from MacBook 1, double-click your Time Capsule via the Finder, then you should see two +sparse bundles,+ one for each Mac. Delete the one for the old Mac. That will take a long time, even via Ethernet. If it's taking extremely long, see the blue box in #Q5 of [Using Time Machine with a Time Capsule|http://web.me.com/pondini/TimeMachine/TimeCapsule.html] (or use the link in *User Tips* at the top of this forum).
Or, you can delete individual backups of the other Mac. To see them, you'll need the +*Browse Other Time Machine Disks+* option, per #17 in [Time Machine - Frequently Asked Questions|http://web.me.com/pondini/Time_Machine/FAQ.html] (or use the link in *User Tips* at the top of the +Time Machine+ forum). To delete individual backups, see #12 in the FAQ, and don't miss the pink box there.
Message was edited by: Pondini

Step by step process for taking oracle back up on solaris

Hi
Can you please explain me step by step process for taking oracle back up on solaris.
as well as i don't know about RMAN . what is this how to install this. whenever i am typing the rman in solaris $ rman
rman not found is comming please help me in this
Message was edited by:
user640349

First of all, what's your Oracle Version?
RMAN has changed a lot since if first appeared in Oracle 8.0. Now, if you don't have any knowledge at all of recovery manager you must first take a look at the recovery manager version corresponding to your particular oracle version so you get acquainted to the concepts.
If you see the error 'rman not found ...' then it means you don't even have set the environment variables for your session, which is part of the install process. The PATH environment variable must include the $ORACLE_HOME/bin where the rman along many other oracle binaries are located.
1. Check the environment variables.
2. Specify the Oracle version
3. You can use Enterprise Manager to easy your life, but the setup procedure is subject to the oracle version you are referring to.
4. Take a look at the backup/recovery manual to get acquainted with rman concepts.
~ Madrid
http://hrivera99.blogspot.com/

How to setup a user account for brtools backup

Dear Sir,
We have SAP running on Unix (AIX) and ORACLE Database . For the backup , we take the backup using brtools . At present , I am able to take the backup from the dba user account .
DBA user account (at os level) is oradv and group name is sapsys .
For taking the routine backup using brtools , I want to create a seperate user account . For this I created a user , named bkup . For this user , I have defined primery group as sapsys .
During execution of brtools command , I am getting following error :
BR0252E Function stat() failed for '/usr/sap/DEV/SYS/exe/run/brarchive' at location BrFileStatGet-1
BR0253E errno 13: Permission denied
BR0273E Determination of file status for /usr/sap/DEV/SYS/exe/run/brarchive failed
Kindly guide us , as what parameters / authorization etc need to be changed for user account bkup , so that brtools command can work without any error .
With Thanks and Rgds
Sonia Agarwal

do lsuser oradv, check it's authorizations and give same auths to new user bkup

Co-location for daily backup

I have created a protection group for file server and taking backup of a share on tape drive.
under protection method--> I chose I want short-term protection using : tape
retention range: 1 week
frequency of backup: daily
backup mode: full and incremental
so full backup on Saturday and other days incremental backup.
I have around 700 GB data size.
I have shortages of tape. from recovery option: I saw in this month on 12thOct, on Saturday it run full backup. It took one tape [say tape 1]
on the next 6 days it run incremental backup on another tape.[say tape 2]
again on Saturday for full backup it took tape 3 [tape 3]
again to run incremental backup it is asking for free tape. and back up failed.
in this way I am wasting space on tape. data size is 700 GB, tape size is around 3 TB.
I can see there is option in 'optimize usage' where I can mention under advanced. write period and expiry tolerance.
i believe I need to modify these settings. please suggest if i want daily incremental backup and full backup on Saturday with 1 week retention and reuse the same tape or second tape instead of waiting for more tapes

Hi,
It is currently working as designed for tape library.
See the following TechNet page:
How DPM Uses Tape Libraries
http://technet.microsoft.com/en-us/library/hh757885.aspx
Short-term tape "full and incremental" option
The full backup will require a free tape for each scheduled job, and the incremental backup for all data sources will be appended to a single separate tape.
As tapes fill up, new free tapes will be allocated.
When the next full backup occurs, it will require another free tape, and subsequent incremental backups will be appended to another free tape.
So basically, you will need three sets of tapes for a 1 week retention range.
Please 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. Regards, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

Runlevel for taking backups

Similar Messages

Maybe you are looking for