SquashFu - An incremental backup utility

About a week ago, I deemed my now former backup solution to be old and busted. It didn't do compression, and it didn't do incrementals. Once or twice I found myself hurrying to fix something before my backup fired off at 2am (yes yes I could have stopped that).
Say herro to SquashFu. Written entirely in Bash, it uses squashfs, aufs, and rsync to create and manage incrementals while maintaining a decent level of compression on the base backup. The number of incrementals kept is user defined and can be changed freely. A minimum number of incrementals is also defined by the user. This number is referenced when the max is exceeded and SquashFu recreates the base backup, merging in enough of the oldest incrementals to bring you down to this minimum level.
Rolling back is easy. Because each backup is stored separately, you just need to specify how many you want to "peel off", and SquashFu creates a mount that represents that point in time. Simple! A query/reporting option decodes when backups were made to help decision making.
I deem it to be beta quality currently. It doesn't have all the options I'd like it to have just yet, but the major components are set in stone and will not change (i.e. 6 months from now this util will work on incrementals created today). Bug reports and minor feature requests are welcome.
PKGBUILD
GitHub page (with more detailed doc)

This looks interesting. Fairly happy with my backup system however I think I will look at this once I get my head around exactly how it works. Good documentation.

Similar Messages

  • ACS 5.3 incremental backup error

    Hi ,
    I have ACS 5.3 that recently having problems with the incremental backup.
    The error is : on demand back failed
    and the details is: SQL Anywhere backup utility connection error: insufficient system resources- failed  to allocate a SYSV semphorenull .
    I mean come on.... and I did not find this error on cisco website.
    The ADE.log file is not showing errors/details related to this. Atttached are the files showing the errors
    Have anyone faced this problem before? Ideas? Anything?
    Regards,
    George

    Hi George:
    with 5.3 I experienced many issues including the incremental backup does not work. whenever I set it to "ON" next time the scheduled backup comes It fails and set itself back to "Off'. I did not get same message you get though.
    I finally did two things:
    - upgraded to latest patch.
    - moved the log collector from the primary to the secondary.
    Now things are fine for about 1 month without issues.
    Regarding your issue, I think it could be related to resource issue as mentioned in the message.
    What is the current DB size that you have?
    Note that the message is misleading (messages I got with my ACS are the same) because they mention incremental backup in the message title and then say on-demand full backup failed!
    So, you have to specify yourself if the issue with the incremental backup or the full backup?
    HTH
    Amjad
    Rating useful replies is more useful than saying "Thank you"

  • RMAN RECOVERY FROM INCREMENTAL BACKUP

    Hi,
    hOW TO RECOVER FROM INCREMENTAL BACKUP ?
    Any script for recovery from Full+incremental BACKUP?
    Many thanks before.

    Thank you,
    but I can not connect from RMAN when database is shutdowned.
    C:\Documents and Settings\Farid>rman catalog rman/****@reprman target sys/***@bd1
    Recovery Manager: Release 10.2.0.1.0 - Production on Ven. FÚvr. 16 18:28:19 2007
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00554: Úchec de l'initialisation du gestionnaire de rÚcupÚration interne
    RMAN-04005: erreur de la base de donnÚes cible :
    ORA-12514: TNS : le processus d'Úcoute ne conna¯t pas actuellement le service demandÚ dans le descripteur de connexion
    tnsping BD1Adaptateur TNSNAMES utilisÚ pour la rÚsolution de l'alias
    Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST
    E = bd1.virtualparc.com)))
    OK (30 msec)

  • Restore using incremental backup with noarchivelog mode

    Hello experts,
    We are running SAP on Oracle databse(IN NOARCHIVELOG MODE) for which we are having full offline backup on every sunday and post which incremental backups on rest of the days. We have scenario to do restore db to the state till last friday's incremental backup.
    Please let us know the procedure for restoring till that point. If possible using brtools utility(which is SAP specific).
    Thank You
    Regards,
    Venkateshwar

    If you do not want to read the whole doc This is the snippet for you.
    Recovering a NOARCHIVELOG Database with Incremental Backups
    Restoring a database running in NOARCHIVELOG mode is similar to restoring a database in ARCHIVELOG mode. The main differences are:
    Only consistent backups can be used in restoring a database in NOARCHIVELOG mode.
    Media recovery is not possible because no archived redo logs exist.
    You can perform limited recovery of changes to a database running in NOARCHIVELOG mode by applying incremental backups. The incremental backups must be consistent, like all backups of a database run in NOARCHIVELOG mode, so you cannot make backups of the database when it is open.
    When you are recovering a NOARCHIVELOG database, specify the NOREDO option on the RECOVER command to indicate that RMAN should not attempt to apply archived redo logs. Otherwise, RMAN returns an error.
    To recover a NOARCHIVELOG database with incremental backups:
    After connecting to the target database and the recovery catalog, place the database in a mounted state:
    STARTUP FORCE MOUNT
    Restore and recover the database.
    For example, you can perform incomplete recovery with the following commands:
    RESTORE DATABASE
    FROM TAG "consistent_whole_backup";
    RECOVER DATABASE NOREDO;
    Open the database with the RESETLOGS option.
    For example, enter the following command:
    ALTER DATABASE OPEN RESETLOGS;

  • Time Machine Incremental Backups

    I have just purchased a new MacBook Pro and restored my old MacBook on the new one using my Time Machine backup. Now I want Time Machine to continue backing up using the old backup and not starting a new backup from scratch. In effect, I want Time Machine to do incremental backups. I have read about Time Machine tying the Mac address of the old MacBook to the old backup I already have and as such, my new MacBook will have to create its own backup from scratch. Is there a work around this problem? Any helpful hints are welcome.

    iMinds wrote:
    Thanks for your suggestion. Yes, I did a full system restore, by booting the new Mac from the Leopard Install disc and selecting Utilities then Restore from Backups from the Menubar. What else can I do?
    Eeeeek! You now have the old Mac's entire version of OSX on the new one. I'm surprised it booted up at all. You may not have the correct hardware drivers and other things for the new Mac.
    I'm sorry to say, you need to start over. You need to do an *Erase and Install* using the Leopard Install disc that came with the new Mac, to put the correct version of OSX back on it. Then you can Migrate (transfer) everything else from your TM backups.
    See the *Erase, Install, & Migrate* section of the Glenn Carter - Restoring Your Entire System / Time Machine *User Tip* at the top of this forum.
    Once that's done, TM's next backup will be a full one. Everything you put on the new Mac's internal HD is new *to that Mac* as well as new *to that disk,* and TM's whole role in life is to back up everything that's new or changed. You cannot prevent it.
    Also, your old backups will not appear if you use the normal +Enter Time Machine+ option on the new Mac; you'll need the Browse option as per item #17 of the Frequently Asked Questions *User Tip* at the top of this forum.
    Plus, they won't be deleted by TM as the disk fills up, and it needs room for new backups. So your best bet will probably be, once you're sure everything transferred over properly, to simply erase the TM disk via Disk Utility and let TM start fresh.

  • Time machine not doing incremental backups - instead doing full backups

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

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

  • OS X Lion v10.7 Time machine won't do incremental backups.

    Time machine under Snow Leopard used to do small incremental backups just fine. After upgrading to Lion though, every time I try to do a time machine backup, it attempts to perform a full backup (hundreds of gigabytes every time). Usually the first full backup completes fine but instead of doing subsequent small/incremental backups of the changed files, it starts over doing full backup but there isn't enough room on the backup drive for that so it fails.
    I've found other people with the same issue here: http://forums.whirlpool.net.au/archive/1745345
    And attempted several suggested fixes/tests but none of them work just as in that thread. Am I alone in this issue? Any suggestions?
    I have a 10.7.1 install on a mid 2010 15" MBP with two drives (one SSD, one HDD, no optical). As I mentioned before, time machine worked beautifullly under 10.6.x backing up to external 1TB FW 800 -> SATA bridges.
    Thanks,
    M

    I have the same problem only full backups all the time I upgraded from Snow Leopard to Lion and on Snow Leopard I had no issues with Time Machine. So what I have done:
    Formated the Time Machine Backup Disk (it's an USB-drive) - didn't help
    I deleted all the Time Machine Settings (plists) - didn't help
    Used Disk Utility to verify user rights and drive - didn't help
    Used TechTool Pro 6 to verify the drive - didn't help
    I still only get full backups. If I exclude the a catalogue/folder, the backup will be smaller, but it still takes a full backup of the items selected ...
    My system is the same as before the upgrade - no new hardware and so on. This is really strange

  • No Incremental Backups - Can Only Force Backup

    I waited until the patch was released before posting this message as I thought my issue may go away. It has not...
    Time machine suddenly stopped working about a week ago. I get no incremental backups at all. I can force a backup with no issues.
    Today I read all the help topics, I re-formated my Lacie Disk, my PC name is fine and so is the name of my Lacie drive. I still get no incremental backups. TM says that in an hour it will backup, it does not, TM then says it will backup in another hour, it does not.
    The only thing I might not have done (newbie) is formatted to GUID? I dont know what that is. In disk utility I selected erase and used the MAC OS Extended (Journald) option, I then created 2 partitions, one for TS and one for storage.
    Its starting to annoy me now. Any help would be appreciated.
    Message was edited by: ShaggyRS6

    I downoaded Bento demo. Then about 10 mins later TM backed up. I then downloaded an iTune and waited for the next schedule backup. That did not work. Strange
    Nov 16 06:53:47 localhost com.apple.launchctl.System[2]: launchctl: Dubious permissions on file (skipping): /System/Library/LaunchDaemons/com.apple.backupd-auto.plist
    Nov 16 08:20:43 localhost com.apple.launchctl.System[2]: launchctl: Dubious permissions on file (skipping): /System/Library/LaunchDaemons/com.apple.backupd-auto.plist
    Nov 16 08:59:22 host171 /System/Library/CoreServices/backupd[336]: Backup requested due to disk attach
    Nov 16 08:59:22 host171 /System/Library/CoreServices/backupd[336]: Starting standard backup
    Nov 16 08:59:24 host171 /System/Library/CoreServices/backupd[336]: Backing up to: /Volumes/Time Machine/Backups.backupdb
    Nov 16 08:59:46 host171 /System/Library/CoreServices/backupd[336]: No pre-backup thinning needed: 819.8 MB requested (including padding), 82.19 GB available
    Nov 16 09:00:54 host171 /System/Library/CoreServices/backupd[336]: Copied 5043 files (612.4 MB) from volume Macintosh HD.
    Nov 16 09:00:55 host171 /System/Library/CoreServices/backupd[336]: No pre-backup thinning needed: 153.3 MB requested (including padding), 81.57 GB available
    Nov 16 09:01:00 host171 /System/Library/CoreServices/backupd[336]: Copied 443 files (49.8 MB) from volume Macintosh HD.
    Nov 16 09:01:01 host171 /System/Library/CoreServices/backupd[336]: Starting post-backup thinning
    Nov 16 09:01:01 host171 /System/Library/CoreServices/backupd[336]: No post-back up thinning needed: no expired backups exist
    Nov 16 09:01:01 host171 /System/Library/CoreServices/backupd[336]: Backup completed successfully.

  • Incremental backups of iTunes Library?

    Every few months I copy the complete iTunes directory from my iMac to a USB based hard-drive. As the library grows, it takes longer each time. Is there a utility to copy/update only whats changed, i.e. a incremental backup?

    Bill
    I use DejaVu for just this purpose with both my iTunes, iPhoto and other files.
    Regards
    TD

  • I am trying to restore my catalog having previously done a back up to an external hard drive and subsequently an incremental backup. I am using Photoshop Elements 11 and the only option given in the restore procedure is to open a .tly file.

    I have done this but now the restore function is asking for yet another file, which i assume to be the original back up, but that is the only .tly file since the only other relevant file appears to be called catalog.buc but that is just not visible when using the restore function? How do I continue from here with this restoration of my catalog?

    Martin_Had a écrit:
    Thank you Andaleeb. I appear to have an old backup of a year ago, and a more recent full back up plus an incremental backup.
    Regrettably I don't really understand what is going on because firstly the restore does not complete its cycle so I cannot see what that backup file contains and secondly all I have read would suggest that the .tly file is the full backup and the catalog.buc file is the incremental backup. For the present, the catalog shows the photos for 2014 which makes me think I might have backed from the old back up file.
    I am minded to create another catalog and try again.
    Any views on what I can do?
    A backup (full or incremental) is a folder, not a file. It contains renamed pictures file copies as well a copies of the files and subfolders of the original catalog. The catalog.buc is a renamed copy of the database of your original catalog while the backup.tly. That backup.tly file contains the information to restore the renamed pictures where you decide, the original location or a new custom one. You can't do anything with the backup yourself, only the restore process can do the job if it finds the backup.tly file. In the case of an incremental backup, you have to tell the restore process where to find the incremental backup folder; it finds the backup.tly file in that folder and finds what is to restore there; then it asks you for the previous backup folder (in your case the full backup); you then browse to that full backup folder so that the restore process can find find the backup.tly there; the restore then deals with the rest of the files to restore.

  • Can't resume incremental backups

    I fist finished moving and after a few weeks of sitting in a box I set up my Time Capsule to resume operation as my backup device and wireless router. Unfortunately, I must have made a mistake during setup because now my MacBook Pro is treating the TC as a completely new device, seeking to make a full backup of its entire hard drive rather than the first incremental backup since before the move. Is there some way of forcing my MBP to recognize the existing backups on the TC and pick up where it left off? I'd really appreciate some help because I've got some valuable old files trapped in those old backups. Thanks!

    I think i have an idea of why this might be happening now but don't know how to fix this. any help would be appreciated.
    so i checked this directory
    /Volumes/Time Machine Backup 2/Backups.backupdb
    and there were two directories. a new one called "computer" and the old folder with my backups "computer 2", so Time Machine must be looking at the "computer" folder. How can I force Time Machine to look at the other older folder? I tried removing the "computer" folder but it won't let me rename "computer 2" to "computer", even from the terminal using sudo and admin privileges. Is there a reason why I'm not allowed rename files on my own machine when I'm the admin?
    thanks

  • ACS 5.3 Incremental BackUp Issue

    We have ACS 5.3 and it turns back to "Off" by itself and doesn't perform incremental backup. I turned it "On" several times, but it keeps on turning "Off"
    Version : 5.3.0.40.8 in VM Enviroment.

    Hi Kumar2000,
    I tried to answer anas query here, you may want to go through the same.
    https://supportforums.cisco.com/discussion/12142716/acs-inceremental-backup-turns
    Regards,
    Jatin Katyal
    *Do rate helpful posts*

  • Time Machine won't do incremental backups after I restored my computer

    I am using a macbook (2010 version) and operating Lion.  I had a problem with my Macbook where it wouldn't log on, even in safe mode, so I restored it using Timemachine.  Now that everything is back up and running well I want to keep backing up.  But Time Machine now says that there is not eneough space on the backup disk as it wants to back up the whole computer alongside the exisitng back up.  In short it will no longer do incremental backups on top of what has already been backed up.  I don't want to wipe my backup disk for fear that something might go wrong again and I may want to go back to a version earlier than the one I restored.  Is there anyway of getting round this problem?  It seems like a fairly serious problem.
    I would appreciate any help.

    ms364 wrote:
    I am using a macbook (2010 version) and operating Lion.  I had a problem with my Macbook where it wouldn't log on, even in safe mode, so I restored it using Timemachine.
    When you erased the disk, it got a new UUID (Universally Unique IDentifier), which is treated like a different drive, and Time Machine will back it up in it's entirety.
    Did you do a full system restore, starting from the Recovery HD?  If so, that should have left a "trail" so Time Machine should have automatically "associated" the restored disk with the existing backups.
    If you did it "piecemeal," though, via the "Star Wars" display, it won't (that doesn't leave the trail for TM to figure out what happened).
    You might be able to get it to do the association manually.  See #B6 in Time Machine - Troubleshooting.
    But Linc is right;  you apparently need a larger TM drive.  See #1 in Time Machine - Frequently Asked Questions.

  • ENTERPRIZE BACKUP UTILITY

    제품 : ORACLE SERVER
    작성날짜 : 1996-11-29
    1. The Problem
    과거 메인 프레임 환경에서 사용하던 고객들이 저 비용, C/S환경으로
    Migration시에는 주로 Open system과 Oracle RDBMS를 채택하고 있다.
    이런 관계로 해당 제품 시장은 고 성장을 구가하고 있기도 하다.
    이러한 고 성장을 가능케 하는 요소는 물론 H/W,S/W에서의 혁신적인
    진보이나, 메인 프레임급에 걸 맞는 대용량 DB를 관리하고 Backup하는
    데 필수적인 System management tool은 과거와 크게 달라진 바가 없다.
    tar, cpio, dd같은 UNIX backup tool들은 실제 backup media의 관리
    측면에서 별 기여 를 하지 못하고 있다. 대용량 DB를 위한 Backup script는
    source만 해도 수백line에 달하며 test와 troubleshoot에서도 많은 문제점을
    갖고 있다. 뿐만 아니라 대용량 Database(이하 VLDB)의 Restore는
    Backup보다도 훨씬 더 복잡한 문제를 갖고 있다.
    최근의 Backup file이 어느 곳에 저장 되었는지를 알기 위해 Backup
    tape을 분류하고, damaged file들을 restore 해야 하는 등의 일련의 작업이
    필요하다.
    2. The Solution
    최근에 몇몇 media management vendor들은 media management기능,
    scheduling기능, 강력한 security기능, UNIX system에서 제공하는 backup
    tool이상의 신뢰성을 갖는 강력한backup product를 공급하기 시작했다.
    이러한 product들은 system level에서의 관리를 용이하게 해주는 장점은
    있으나 이미 위에서 지적된 VLDB의 backup시 제기되는 문제점들을
    완전히 해결해 주지는 못한다.
    Oracle7 Enterprise Backup Utility(이하 EBU)는 이런 문제점을 해결하는
    solution이다. EBU는 backup/restore시 media management product와 강력한
    인터페이스를 제공하며 다른 어느것과 비교 할 수 없는 강점을 갖고
    있다.
    3. Introducing Oracle7 Enterprise Backup Utility
    EBU는 open system상에서 메인 프레임급 성능을 제공하여 한 기업
    전반에 걸쳐 전략적으로 중요한 역할을 감당하게 된다. 이 utility는 DB의
    신속한backup과 restore를 위해disk와 backup될 media device에서H/W
    parallelism을 이용한다.open system의 full capacity를 이용하기 위해
    device가 add될 때 performance가 증가된다.parallel H/W, backup
    configuration check ,error detection and cleaning ,restore시의
    database의block verification과 같은 특징들이EBU가 high reliability를 갖게
    하는 특징들이다.
    Oracle7 데이타베이스는 data files, control files, redo log files로
    구성되는데 EBU는data file, control file을 backup받고 archived redo log
    file을 받는다. (release2.0.8) Media failure의 경우 DB를 full restore/
    partial restore가 가능하며 data file도 선택적으로 최근의 last backup까지,
    어느 일정 시점 까지 만의 선택이 가능하다. 또한 recovery도 일정 시점으로
    완전recovery가 가능하다.
    4. Architecture
    EBU는 크게 두 부분으로 구성되는데 backup하려 하는 DB에 관한 모든
    current정보와history를 관리하는 catalog부분, 그리고 실행 파일 부분으로
    구성된다. 실행 파일들과 catalog는 반드시 같은 host내에 존재할 필요는
    없다. 실행 파일들은 다음으로 구성된다.
    *obackup : 모든 다른 프로세스들을 monitor하며 backup하려하는 DB,
    catalog와의 communication을 담당한다.또한 Instance Manager를
    running시킨다.
    *brio  : obackup, brdk, brtp사이 조정 역할을 수행한다.parallel I/O
    stream당 하나의 brio process가 발생한다.
    *brdk : Disk file의 read/write를 조절한다. File당 하나의 brdk를 발생시키
    므로 만일 여러 개의 file들을 하나의 single data stream으로 결합시
    키는 경우 하나의 I/O stream내에 여러 개의 brdk process를
    create한다.
    *brtp : Tape file들의 read/write를 조절한다. I/O stream당 하나의 brtp
    create.
    *brd : Instance Manager로써 backup catalog, obackup을 monitor하는
    daemon process이다. backup을 위한 cleanup과 비정상 종료된 작업을
    복구 한다.
    Backup동안 database file들은 disk process인 brdk에 의해 읽혀져 backup
    buffer area로 넘겨지고 그 후 third vendor의 media management s/w를
    경유하여 backup device에 brtp process에 의해 write된다. Restore시는
    반대의 과정이 진행된다. 위의backup buffer는 hard disk와 tape device간에
    발생하는 I/O상의 speed mismatch를 조절하는 역할을 한다.
    5. EBU의 장점(Benefits)
    Third vendor의 media management product와 함께 사용되는 EBU는
    기존의 UNIX 에서 제공하는 backup tool보다 다음과 같은 강력한 장점을
    지닌다.
    (1) 강력한 Reliability.
    *. Consistent backup procedures
    기존의 hot backup script의 경우 만일 datafile이 추가될 경우 script에
    새로 지정해 주어야 하며 VLDB의 경우 script만 해도 수백line에 달하여
    관리상 번거로운 게 사실 이였다. 그러나 EBU의 경우는 어느 datafile이
    어느directory에 위치하는지를 작업자가 알 필요가 없고 script는 짧고
    단순하여 누구든 쉽게 알아볼 수 있다.
    또한 DB 구성이 자동으로 확인되며 backup media를 자동으로 인식 및
    관리한다.
    예).full online backup script .partial online backup script
    backup online database backup online
    db_name = "PRODB" db_name = "PRODB"
    oracle_sid = "PROD" oracle_sid = "PROD"
    tablespace = "SALES"
    .full restore script
    restore database
    db_name = "PRODB"
    oracle_sid = "PROD"
    이와 같이 간단한 script에 의해 DBA는 VLDB를 쉽게 backup과 restore를
    할 수 있으며 작업에 필요한 세부정보는 backup catalog내에 있게 된다.
    *. End-to-End checksum
    Backup시 EBU는 각 backup data의 byte를 계산하고, restore시도 계산하여
    정상 수행 여부를 판단 시 checksum 값을 상호 체크 한다.
    *. Instance Manager
    Instance Manager는 backup/restore시에 진행 상황을 monitor하고 작업
    중에 에러가 발생시 복구 및 각종resource를 release시키는 기능을 담당하게
    한다.
    (2) High Performance
    다음과 같은 EBU의 특징과 고속media device의 지원 아래 VLDB의
    backup을 적은시간 내에 완전하게 수행 할 수 있게 되었다.
    *. Parallel Hardware Capability
    Backup/restore시 multiple device를 사용하여 동시에 여러 tablespace에
    대한 작업을 수행 할 수 있다. VLDB와 같이 다수의 tablespace, datafile이
    여러 disk에 분산되어 있는 경우 이와 같이 물리적으로 다수의 device를
    parallel하게 사용함으로서 performance를 극대화 시킬 수 있다.
    Backup시 동시 사용되는 device의 수와 performance는 정비례하게 나타난다.
    *. Multiplexing
    EBU는 backup device가 최고의 속도로 backup을 수행 할 수 있게 script에
    지정 할 수가 있다.이것은 backup media access속도보다 disk access
    속도가 훨씬 작은 경우에 여러 disk에 분산된 datafile들을 한device에
    multiplexing되게 지정함으로 가능하다.
    *. Null Block Compression
    EBU는 backup시 null data block을 skip시키고 restore시 재구성함으로써
    공간 을 절약하며 performance를 증가시킨다.
    *. Buffered I/O
    EBU는 disk I/O와 device I/O사이의 access speed의 mismatch를 줄이기
    위하여 모든 I/O stream을 bufferring한다. 양쪽의 I/O는 shared memory
    buffer를 거치게 함으로써 backup/restore수행 중 항시 일정 속도를 유지
    하게 한다. shared memory는 user가 parameter로 구성할 수 있으며 기본
    적으로는 parallel data stream의 개수와 buffer size에 dependent하다.
    (3) Availability
    한 기업에서 전략적으로 중요한 DB들은 대부분 24시간*7일 full로
    가동되며, 사용 중에 backup을 수행할 수 밖에 없다. Offline full backup은
    당연히 지원되며, EBU는 DB를 online상태로 full backup이 가능하며,
    또한partial backup도 가능하다. 기존의 online backup이 backup으로 인해
    performance를 저하시키는 단점이 있었으나 EBU는DB 운영에 최소의
    영향만을 미친다.
    Recovery시에도 full로 restore 시킬 수 있으며 나머지는 사용 중인
    상태에서 필요 부분만 partial restore가 가능하다. 일단 EBU가 data를
    restore시킨 후에는 기존의 Oracle7의 표준 recovery process가 적용되어
    진다.
    (4) Usability
    *. Auto-configuration
    Online backup을 수행 시 EBU는 current DB configuration과 backup catalog
    내의 가장 최근의 configuration정보를 비교하여 backup catalog정보가 더
    오래 전의 것이면 EBU는 DB의 backup직전으로 update시킨다.
    Auto-configuration은 default이며 명시적으로 지정하여 disable시킬 수 있다.
    Offline backup시는 backup script내에 backup command기술 전에 register
    라는 명령어를 기술 해야만 configuration정보를 update시킬 수 있다.
    *. Light-Out backups
    Third party의 media management s/w를 이용하여 EBU를 operator의 개입 없
    이 자동으로 수행이 가능하다. UNIX의 cron에서도 자동으로 수행되게 할 수
    있다.
    *. Raw device support
    EBU는 raw device로 잡힌 DB도 operator의 특별한 조치 없이 일반 file
    system의 backup과 똑같이 수행할 수 있게 한다.
    *. Aggregated restore
    기업의 mission-critical system에서의 backup 전략들은 흔히 partial
    backup에 의존하게 된다. 이와 같은 환경에서는 backup data내의 모든file에
    대한 current version을 검색하는 일이 중요한데 EBU는 이것을 자동으로
    수행한다. partial backup data는 restore시 media failure이전에 취해진
    가장 최근의 full backup data와 aggregated 되어져 이용된다.
    *. Point-in-Time restore
    EBU는 backup catalog내에 backup하려하는 DB에 대한 모든 configuration
    history를 갖고 있어서, 만일 하나의 tablespace가 drop된 후 다시 필요하게
    되면 비록 그 후 일정 시간이 경과되고 많은 변경이 일어났더라도 drop직전으로
    일부분만 restore하여 사용이 가능하게 할 수 있다. 이 같은 tablespace는
    다른 machine에 restore 될 수도 있어 현재의 DB작동에 아무 영향을 미치지
    않고 수행할 수가 있다.
    *. Backup catalog
    EBU에 의해 제공되는 backup catalog는 모든 backup대상 DB의 configuration
    과 history의 저장소로써 제공된다. backup catalog에 저장된 정보는 backup된
    file, tablespace 그리고 multiplexing정보, 마지막backup이나 restore의
    시간기록,backup type(full or subset),backup들이 저장 되어 있는 file set
    등을 포함하고 있다. 하나의 backup catalog는 기업 내 모든 분산된 dB들을 관리
    할 수 있다.
    *. Dry Runs
    VLDB를 backup시 겪는 문제 중 하나는 과연 script가 정상적으로 수행이 완료
    되는지를 검증하는 것이다. 특별한 방법이 없는 한 긴 시간 동안 수행시켜 끝난
    후 확인 할 수 밖에 없는데 EBU는 I/O없이 간단히 test로 수행을 시킬 수가
    있다. 이로 인해 신뢰성 있는 backup전략을 DBA가 수립 가능하게 한다.
    *. Enterprise-wide backup
    이것은 backup이 단순히 single database에 국한되지 않고 한 기업 전체에
    걸쳐서 global하게 수행 가능함을 말한다. 예로 전국적으로 다수의 site에
    database가 구축 되어진 상황에서 각database들이 two phase commit,
    snapshot 같은 분산처리 작업을 통해 다른 database들을 synchronous하게
    또는 asynchronous하게 update할 경우 기업 전체를 하나의 logical
    database로 보고 이런 logical database를 중앙에서 EBU를 통해 backup시킬
    수가 있다.EBU는 중앙의 catalog내에 모든database들에 대한 backup정보를
    간직하고 있다.
    이와 같은 중앙의 한 지점을 통하여 기업 전체 모든 database들에 대한
    backup수행 기능은 EBU의 가장 큰 장점 중 하나이며 이런 경우 N/W상에 대량의
    data가 전송되어 network의 bandwidth가 backup의 중요한 요소로 부각된다.
    6. Flexibility
    *. EBU API
    EBU는 앞에서도 소개되었듯이 단독으로 사용되는 것이 아니고 third-part
    에서 제공하는 media management product와 같이 사용된다. 이때 두 product
    사이의 interface는 backup/restore Application Programming Interface
    (API Glue)에 의해서 이루어 진다. 이것은 third part에 의해 제공되며
    EBU install시 installer에 의해 자동적으로 access된다.
    *. Media management products
    Epoch*s EpochBackup, IBM Adstar*s Distributed Storage Manager,
    Legato Systems*NetWorker, HP*s Omniback*, SprectraLogic*s
    Alexandria,StorageTek*s REEL, etc.
    *. Media device
    4mm and 8mm DATS,3480s,3490s,WORM,Writable Optical Devices and
    automated systems such as stackers and silos.
    7. Pricing
    EBU는 무상으로 공급되며 사용을 위해서는 third vendor의 media
    management product를 구입하여 설치하여야 한다.

    Sure, would you clarify which DB, which OS and which product?
    Concept in general is quite simple:
    - stop BOE (SIA on XI3, All services, finishing with CMS on XIr2, ideally putting a sleep between all servers shutdown and CMS shutdown). NET STOP on windows.
    - Backup the CMS DB (imp/exp on Oracle, mysqldump for MySQL)
    - Backup the FileStore (use robocopy in a batch for delta backup)
    - Restart BOE
    The "catches" are around Oracle doing export in US7ASCII by default under Unix, which is a destructive conversion from UTF8 (your CMS DB should be under this format as per supported platforms), so you need to make sure to set the NLS_LANG to UTF8 on Unix user doing the backup.
    Other than that, batch as shell can do all of that.
    Regarding the "general" best practices, I recommend the following doc:
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/c0020482-ca8d-2c10-9bad-d1bd332bbb28
    Note on integrated BO tools: Import Wizard as biarengine are good tools for promoting a set of data between wto BOE environment or if you need to backup a specific set, but they are definitly not recommended as backup solution. I would refrain from this solution IF the point of the backup is to be able to recover the system when it crashes.
    Does that answer the question?

  • BR0231E Problem with Legato bACKUP utility

    Hi,
    I'm try to restore my database with brrestore and I'm get the following error:
    BR0280I BRRESTORE time stamp: 2008-03-02 10.12.16
    BR0229I Calling backup utility with function 'restore'...
    BR0278I Command output of 'E:\usr\sap\DOP\SYS\exe\run\backint.exe -u DOP -f restore -i E:\oracle
    \DOP\sapbackup\.rdxjtccy.lst -t file -p E:\oracle\DOP\920\database\init.off.DOP.utl':
    BR0375E Backup utility has reported an error while restoring file M:\ORACLE\DOP\SAPDATA10\BTABI_
    7\BTABI.DATA7
    BR0280I BRRESTORE time stamp: 2008-03-02 10.16.24
    BR0279E Return code from 'E:\usr\sap\DOP\SYS\exe\run\backint.exe -u DOP -f restore -i E:\oracle\
    DOP\sapbackup\.rdxjtccy.lst -t file -p E:\oracle\DOP\920\database\init.off.DOP.utl': 2
    BR0374E 0 of 1 file restored by backup utility
    BR0280I BRRESTORE time stamp: 2008-03-02 10.16.24
    BR0231E Backup utility call failed
    I' have windows 2003 + SAP 4.7 Oracle 9.0.2
    Please help
    Edited by: Luis Minaya on Mar 2, 2008 3:55 PM

    Hello,
    Legato log files might tell you more about the root cause.
    And here's just a guess: Files permissions have to be considered as well. Did you do backup and restore as the same operating system user? If users are different, then different permissions may be a problem.

Maybe you are looking for