Ms Backup Error(Bkf ) Recovery

Sometimes, the backup files get corrupt, damaged and this happens when the backup files are saved in the local hard disk and not protected by System Restore. Common causes of BKF file corruption are CRC errors, registry corruption, backup interruption, sudden
system shutdown, unrecognized media and software failure.
So, it is very compulsory to keep up the backup copies of all files and folders in order to restore them using Restore Wizard or the Automated System Recovery Wizard whenever the operating system get gone down. NTbackup.exe is a tool which is inbuilt with
the windows  it can be used to create the backup files.
When the data that get deleted, lost, corrupted or damaged due to logical or physical errors BKF file, Backup files can be used for restoring the lost items.
For doing it, this software performs repair operation to retrieve valuable BKF files created by using Veritas software for Windows NTBackup or Backup Exec. In this system, it locates all the BKF files.
In DAT file, it restores scan output to recover it later. It also supports the backup utility of Windows 2003, Xp and 2000.
So I will Recommend:- http://www.filesrecoverytool.com/bkf-recovery-tool.html

BKF Recovery tool is fastest, stable and dependable recovery tool to
recover data from corrupt BKF file in a shortest possible time.
BKF Recovery tool which will allow you to see at least the preview of data that it can recover for you almost instantly.

Similar Messages

  • I want to backup my Mac to iCloud, but receive an error message recovery partition required.  Is this an easy fix?

    I want to backup my MacBook Pro to iCloud, but receive the error message "recovery partition required".  Is this easy to fix? 
    Thanks for your time.

    Sounds like your missing the partition. I have seen this before when I friend had a bad drive and took it in. Apple store replaced the driveamd installed lion but no partition. I had to reinstall lion from a full install DVD to build the recovery partition. Looks like you need to do the same. No data will be lost if you don't re-partition with the disk util. Just run the lion install from within lion and use the default. It will build the partition for you. Then re-run the apple updates for the 10.7.2 update which embeds the find my Mac part of iCloud in the recovery partition.
    Good luck.

  • Backup error occured, Error code 3700 "hostfile_error"

    HI,
    We are trying to MaxDB database backup to tape and getting below error.
    ===================================================================================================
    ERR
    -24988,ERR_SQL: SQL error
    -104,DBM command impossible at this time
    3,Data backup failed
    Servertask Info: because Error in backup task occured
    Job 1 (Backup / Restore Medium Task) [executing] WaitingT204 Result=3700
    Error in backup task occured, Error code 3700 "hostfile_error"
    Backupmedium #1 (
    .\pipe\backup) I/O Error
    Backup error occured, Error code 3700 "hostfile_error"
    ===================================================================================================
    I went through the previous threads regarding the same error but couldn't find a solution.
    System Info is Win 2008, MaxDB version 7.7.07.14.
    Here is the complete log, please suggest what can be done.
    ===================================================================================================
    DBA Action starts:
    Timestamp: 20110831100408   Function: sda   Object: DATA
    2011-08-31 10:04:08
    Using environment variable 'TEMP' with value 'C:\Windows\TEMP' as directory for temporary files and pipes.
    Using connection to Backint for MaxDB Interface.
    2011-08-31 10:04:09
    Checking existence and configuration of Backint for MaxDB.
        Using environment variable 'BSI_ENV' with value 'G:\sapdb\data\wrk\MXP\bsi.env' as path of the configuration file of Backint
        Reading the Backint for MaxDB configuration file 'G:\sapdb\data\wrk\MXP\bsi.env'.
            Found keyword 'BACKINT' with value 'D:\sapdb\MXP\db\bin\backint.exe'.
            Found keyword 'INPUT' with value 'G:\sapdb\data\wrk\backint\sapdb.in'.
            Found keyword 'OUTPUT' with value 'G:\sapdb\data\wrk\backint\sapdb.out'.
            Found keyword 'ERROROUTPUT' with value 'G:\sapdb\data\wrk\backint\sapdb.err'.
            Found keyword 'PARAMETERFILE' with value 'G:\sapdb\data\wrk\MXP\maxdb_config.par'.
            Found keyword 'ORIGINAL_RUNDIRECTORY' with value 'G:\sapdb\MXP\sapdata'.
        Finished reading of the Backint for MaxDB configuration file.
        Using 'D:\sapdb\MXP\db\bin\backint.exe' as Backint for MaxDB program.
        Using 'G:\sapdb\data\wrk\backint\sapdb.in' as input file for Backint for MaxDB.
        Using 'G:\sapdb\data\wrk\backint\sapdb.out' as output file for Backint for MaxDB.
        Using 'G:\sapdb\data\wrk\backint\sapdb.err' as error output file for Backint for MaxDB.
        Using 'G:\sapdb\data\wrk\MXP\maxdb_config.par' as parameter file for Backint for MaxDB.
        Using '300' seconds as timeout for Backint for MaxDB in the case of success.
        Using '300' seconds as timeout for Backint for MaxDB in the case of failure.
        Using 'G:\sapdb\MXP\sapdata\dbm.knl' as backup history of a database to migrate.
        Using 'G:\sapdb\MXP\sapdata\dbm.ebf' as external backup history of a database to migrate.
        Checking availability of backups using backint's inquire function.
    Check passed successful.
    2011-08-31 10:04:09
    Checking medium.
    Check passed successfully.
    2011-08-31 10:04:09
    Preparing backup.
        Setting environment variable 'BI_CALLER' to value 'DBMSRV'.
        Setting environment variable 'BI_REQUEST' to value 'NEW'.
        Setting environment variable 'BI_BACKUP' to value 'FULL'.
        Constructed Backint for MaxDB call 'D:\sapdb\MXP\db\bin\backint.exe -u MXP -f backup -t file -p G:\sapdb\data\wrk\MXP\maxdb_
        Created temporary file 'G:\sapdb\data\wrk\backint\sapdb.out' as output for Backint for MaxDB.
        Created temporary file 'G:\sapdb\data\wrk\backint\sapdb.err' as error output for Backint for MaxDB.
        Writing '
    .\pipe\backup #PIPE' to the input file.
    Prepare passed successfully.
    2011-08-31 10:04:09
    Starting database action for
         the backup.
        Requesting 'SAVE DATA QUICK TO '
    .\pipe\backup' PIPE BLOCKSIZE 8 NO CHECKPOINT MEDIANAME 'BackupMXP'' from db-kernel.
    The database is working on the request.
    2011-08-31 10:04:09
    Waiting until database has prepared the backup.
        Asking for state of database.
        2011-08-31 10:04:09 Database is still preparing the backup.
        Waiting 1 second ...
        Done.
        Asking for state of database.
        2011-08-31 10:04:10 Database has finished preparation of the backup.
    The database has prepared the backup successfully.
    2011-08-31 10:04:10
    Starting Backint for MaxDB.
        Starting Backint for MaxDB process 'D:\sapdb\MXP\db\bin\backint.exe -u MXP -f backup -t file -p G:\sapdb\data\wrk\MXP\maxdb_
        Process was started successfully.
    Backint for MaxDB has been started successfully.
    2011-08-31 10:04:10
    Waiting for end of the backup operation.
        2011-08-31 10:04:10 The backup tool is running.
        2011-08-31 10:04:10 The database is working on the request.
        2011-08-31 10:04:15 The backup tool is running.
        2011-08-31 10:04:15 The database is working on the request.
        2011-08-31 10:04:25 The backup tool is running.
        2011-08-31 10:04:25 The database is working on the request.
        2011-08-31 10:04:40 The backup tool is running.
        2011-08-31 10:04:40 The database is working on the request.
        2011-08-31 10:05:00 The backup tool is running.
        2011-08-31 10:05:00 The database is working on the request.
        2011-08-31 10:05:13 The backup tool process has finished work with return code 2.
        2011-08-31 10:05:13 The database has finished work on the request.
        Receiving a reply from the database kernel.
        Got the following reply from db-kernel:
            SQL-Code              :-903
    The backup operation has ended.
    2011-08-31 10:05:13
    Filling reply buffer.
        Have encountered error -24920:
            The backup tool failed with 2 as sum of exit codes. The database request failed with error -903.
        Constructed the following reply:
            ERR
            -24920,ERR_BACKUPOP: backup operation was unsuccessful
            The backup tool failed with 2 as sum of exit codes. The database request failed with error -903.
    Reply buffer filled.
    2011-08-31 10:05:13
    Cleaning up.
        Copying output of Backint for MaxDB to this file.
    Begin of output of Backint for MaxDB (G:\sapdb\data\wrk\backint\sapdb.out)----
            Reading parameter file G:\sapdb\data\wrk\MXP\maxdb_config.par.
            Using staging area D:\TEMP\STAGE1 with a size of 1048576000 bytes.
            Using staging area D:\TEMP\STAGE2 with a size of 1048576000 bytes.
            Using 2 file per Backint for Oracle call.
            Using C:\Program Files\Tivoli\TSM\tdp_r3\ora64\backint.exe as Backint for Oracle.
            Using G:\sapdb\data\wrk\MXP\initMXP.utl as parameterfile of Backint for Oracle.
            Using G:\sapdb\data\wrk\MXP\BackintHistory.txt as history file.
            Using G:\sapdb\data\wrk\backint\backint1.in as input of Backint for Oracle.
            Using G:\sapdb\data\wrk\backint\backint1.out as output of Backint for Oracle.
            Using G:\sapdb\data\wrk\backint\backint1.err as error output of Backint for Oracle.
            Using a maximal delay for a Backint for Oracle call of 3600 seconds.
            Reading input file G:\sapdb\data\wrk\backint\sapdb.in.
            Backing up pipe
    .\pipe\backup.
            Found 1 entry in the input file.
            Starting the backup.
            Starting pipe2file program(s).
            Waiting for creation of temporary files.
            1 temporary file is available for backup.
            Calling Backint for Oracle at 2011-08-31 10:05:12.
            Calling 'C:\Program Files\Tivoli\TSM\tdp_r3\ora64\backint.exe -u MXP -f backup -t file -p G:\sapdb\data\wrk\MXP\initMXP.
            Backint for Oracle ended at 2011-08-31 10:05:13 with return code 2.
            Backint for Oracle output:
            Backint for Oracle output:                          Data Protection for SAP(R)
            Backint for Oracle output:
            Backint for Oracle output:              Interface between BR*Tools and Tivoli Storage Manager
            Backint for Oracle output:              - Version 6, Release 1, Modification 0.0  for Win x64 -
            Backint for Oracle output:                    Build: 358  compiled on Nov  4 2008
            Backint for Oracle output:         (c) Copyright IBM Corporation, 1996, 2008, All Rights Reserved.
            Backint for Oracle output:
            Backint for Oracle output: BKI2027I: Using TSM-API version 6.2.3.1 (compiled with 5.3.2.0).
            Backint for Oracle output: BKI2000I: Successfully connected to ProLE on port tdpr3ora64.
            Backint for Oracle output: BKI0005I: Start of program at: 08/31/11 10:05:12 .
            Backint for Oracle output: BKI1216E: There are no backup management classes available.
            Backint for Oracle output: BKI1215I: Average transmission rate was 0.000 GB/h (0.000 MB/sec).
            Backint for Oracle output: BKI1227I: Average compression factor was 1.000.
            Backint for Oracle output: BKI0020I: End of program at: 08/31/11 10:05:13 .
            Backint for Oracle output: BKI0021I: Elapsed time: 01 sec .
            Backint for Oracle output: BKI0024I: Return code is: 2.
            Backint for Oracle output:
            Backint for Oracle error output:
            Finished the backup unsuccessfully.
            #ERROR
    .\pipe\backup
    End of output of Backint for MaxDB (G:\sapdb\data\wrk\backint\sapdb.out)----
        Removed Backint for MaxDB's temporary output file 'G:\sapdb\data\wrk\backint\sapdb.out'.
        Copying error output of Backint for MaxDB to this file.
    Begin of error output of Backint for MaxDB (G:\sapdb\data\wrk\backint\sapdb.err)----
            Backint for Oracle was unsuccessful.
    End of error output of Backint for MaxDB (G:\sapdb\data\wrk\backint\sapdb.err)----
        Removed Backint for MaxDB's temporary error output file 'G:\sapdb\data\wrk\backint\sapdb.err'.
        Removed the Backint for MaxDB input file 'G:\sapdb\data\wrk\backint\sapdb.in'.
    Have finished clean up successfully.
    SAVE/RESTORE request:
    SAVE DATA CANCEL
    SAVE/RESTORE request accepted:
    OK
    SAVE/RESTORE result:
    ERR
    -24988,ERR_SQL: SQL error
    -104,DBM command impossible at this time
    3,Data backup failed
    Servertask Info: because Error in backup task occured
    Job 1 (Backup / Restore Medium Task) [executing] WaitingT204 Result=3700
    Error in backup task occured, Error code 3700 "hostfile_error"
    Backupmedium #1 (
    .\pipe\backup) I/O Error
    Backup error occured, Error code 3700 "hostfile_error"
    DBA Action ends:
    Timestamp: 20110831100513   State:    Failure
    ===================================================================================================

    Hi Markus,
    Thanks for quick response. I did checked KNLMSG file and it has XML file kind of information where as dbm.prt has some information and here it is
    =================================================================================================
    2011-08-31 10:18:30 0x00009ecc INF          1 DBMSrvCo A DBM Server client connection was established at 2011-08-31 10:18:29 (client process has process ID 24352 on computer 10.1.47.21).
    2011-08-31 10:18:30 0x00009ecc INF        283 DBMSrv   Command 'auto_extend show' is being executed.
    2011-08-31 10:18:30 0x00009ecc INF        419 DBMSrv   Command 'auto_extend' has ended with return code 0.
    2011-08-31 10:18:30 0x00009ecc INF        283 DBMSrv   Command 'auto_update_statistics show' is being executed.
    2011-08-31 10:18:31 0x00009ecc INF        419 DBMSrv   Command 'auto_update_statistics' has ended with return code 0.
    2011-08-31 10:18:41 0x00009ecc INF        283 DBMSrv   Command 'backup_save "Backup" DATA RECOVERY' is being executed.
    2011-08-31 10:18:42 0x00009ecc INF          1 DBMKnl   Sending an administrative statement to the database
                        0x00009ecc INF          8 DBMKnl   Statement:  SAVE DATA QUICK TO '
    .\pipe\backup' PIPE BLOCKSIZE 8 NO CHECKPOINT MEDIANAME 'Backup'
    2011-08-31 10:19:47 0x00009ecc ERR          3 DBMKnl   Received the result of an administrative statement from the database
                        0x00009ecc ERR          9 DBMKnl   Statement:  SAVE DATA QUICK TO '
    .\pipe\backup' PIPE BLOCKSIZE 8 NO CHECKPOINT MEDIANAME 'Backup'
                        0x00009ecc ERR         10 DBMKnl   Returncode: -903
                        0x00009ecc ERR          5 DBMKnl   Errortext:  Host file I/O error
    2011-08-31 10:19:47 0x00009ecc ERR     -24580 DBMSrv   ERR_COMMAND_FAILED: Command 'backup_save' has ended and failed with return code -24920.
                        0x00009ecc ERR     -24920 DBMSrv   ERR_BACKUPOP: backup operation was unsuccessful
                        0x00009ecc ERR     -24778 DBMSrv   The backup tool failed with 2 as sum of exit codes. The database request failed with error -903.
    2011-08-31 10:19:53 0x00009ecc INF          2 DBMSrvCo A DBM Server client connection was released (client process has process ID 24352 on computer 10.1.47.21).
    2011-08-31 10:19:53 0x00009ecc INF          1 DBMKnl   Sending an administrative statement to the database
                        0x00009ecc INF          8 DBMKnl   Statement:  SAVE DATA CANCEL
    2011-08-31 10:19:53 0x00009ecc ERR          3 DBMKnl   Received the result of an administrative statement from the database
                        0x00009ecc ERR          9 DBMKnl   Statement:  SAVE DATA CANCEL
                        0x00009ecc ERR         10 DBMKnl   Returncode: -104
                        0x00009ecc ERR          5 DBMKnl   Errortext:  DBM command impossible at this time

  • RMAN-06004:ORACLE error from recovery catalog ... ORA-00904: : invalid ...

    Good Morning All,
    One of our RMAN backups is failing with the following error message. Any suggestions would be greatly appreciated.
    ==================================================================================================
    Starting backup at 12/30/2008 22:03:47
    using channel ORA_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of backup command at 12/30/2008 22:03:47
    RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
    RMAN>
    RMAN> ##BACKUP ARCHIVELOG ALL FORMAT '%d_bkp_al_%t_Set%s_Piece%p' delete input;
    2>
    3> # DELETE ARCHIVELOG UNTIL TIME 'SYSDATE-7';
    4>
    5> # check if database can be restored
    6> # RESTORE DATABASE VALIDATE;
    7>
    8> # check if controlfile can be restored
    9> ##RESTORE CONTROLFILE to '/backups/admin/custpr/custpr_bkp_cntlfile.ctl' VALIDATE;
    10>
    11> # check if archivelogs for the past two weeks can be restored
    12> # RESTORE ARCHIVELOG FROM TIME 'SYSDATE-7' VALIDATE;
    13>
    14> # - Verify all backups on backup media are intact
    15> # CROSSCHECK BACKUP OF DATABASE;
    16>
    17> # - Display a list of files that need to be backed up based on the retention
    18> # policy. For this case study, files that don't have at least 1 backups
    19> # will be reported.
    20> REPORT NEED BACKUP;
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to recovery window of 7 days
    Report of files whose recovery needs more than 7 days of archived logs
    File Days Name
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of report command at 12/30/2008 22:03:48
    RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
    RMAN>
    RMAN> # - delete un-necessary backups. This command deletes backups based on the
    2> # retention policy.
    3> ######### commented out DELETE OBSOLETE - TSM not configured to delete on 68
    4> #########DELETE OBSOLETE;
    5>
    6> # - get complete list of existing backups
    7> LIST BACKUP;
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of list command at 12/30/2008 22:03:49
    RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
    RMAN>
    RMAN> #-end of file-
    2> **end-of-file**
    RMAN>
    Edited by: ORA_UMAIR on Dec 31, 2008 7:51 AM

    This Oracle Database is 9.2.0.6.0. Here is the complete log file. The RMAN script that I am using ran successfully many times before.
    ====================================================================================================
    Recovery Manager: Release 9.2.0.6.0 - 64bit Production
    Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
    RMAN>
    connected to recovery catalog database
    RMAN>
    connected to target database: CUSTPR (DBID=525071053)
    RMAN>
    RMAN> #########################################################################
    2> # LEVEL 0 BACKUP #
    3> #########################################################################
    4>
    5> # Configure backups to be written to disk.
    6> CONFIGURE DEFAULT DEVICE TYPE TO DISK;
    old RMAN configuration parameters:
    CONFIGURE DEFAULT DEVICE TYPE TO DISK;
    new RMAN configuration parameters:
    CONFIGURE DEFAULT DEVICE TYPE TO DISK;
    new RMAN configuration parameters are successfully stored
    starting full resync of recovery catalog
    full resync complete
    RMAN>
    RMAN> # Set the retention policy to a recovery window of 7 days. This ensures that
    2> # RMAN retains all backups needed to recover the database to any point in time
    3> # in the last 7 days. You can use the DELETE OBSOLETE command to delete
    4> # backups that are no longer required by the retention policy. To exclude a
    5> # backup from consideration by the policy, you can use KEEP option with the
    6> # BACKUP command.
    7> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
    old RMAN configuration parameters:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
    new RMAN configuration parameters:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
    new RMAN configuration parameters are successfully stored
    starting full resync of recovery catalog
    full resync complete
    RMAN>
    RMAN> # Configure RMAN to use two disk channels for backup, restore, recovery, and
    2> # maintenance operations.
    3> CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
    old RMAN configuration parameters:
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
    new RMAN configuration parameters:
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
    new RMAN configuration parameters are successfully stored
    starting full resync of recovery catalog
    full resync complete
    RMAN>
    RMAN> # Configure RMAN to write disk backups to the /backup directory.
    2> # The format specifier %t is replaced with a 4-byte timestamp, %s with the
    3> # backup set number, and %p with the backup piece number.
    4> CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
    old RMAN configuration parameters:
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
    new RMAN configuration parameters:
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
    new RMAN configuration parameters are successfully stored
    starting full resync of recovery catalog
    full resync complete
    RMAN>
    RMAN> # Configure RMAN to back up the control file after each backup.
    2> CONFIGURE CONTROLFILE AUTOBACKUP ON;
    old RMAN configuration parameters:
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    new RMAN configuration parameters:
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    new RMAN configuration parameters are successfully stored
    starting full resync of recovery catalog
    full resync complete
    RMAN>
    RMAN> # Configure RMAN to write controlfile autobackups to the /backup directory.
    2> CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
    old RMAN configuration parameters:
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
    new RMAN configuration parameters:
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
    new RMAN configuration parameters are successfully stored
    starting full resync of recovery catalog
    full resync complete
    RMAN>
    RMAN> # Enable the backup optimization feature introduced in 9i to make sure that
    2> # RMAN won't backup an archivelog or datafile if there already exists a backup
    3> # of that file. The FORCE option can be used to override optimization on a
    4> # specific BACKUP command.
    5> CONFIGURE BACKUP OPTIMIZATION ON;
    old RMAN configuration parameters:
    CONFIGURE BACKUP OPTIMIZATION ON;
    new RMAN configuration parameters:
    CONFIGURE BACKUP OPTIMIZATION ON;
    new RMAN configuration parameters are successfully stored
    starting full resync of recovery catalog
    full resync complete
    RMAN>
    RMAN> # Use the SHOW ALL command to see the current configuration settings.
    2> SHOW ALL ;
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
    CONFIGURE BACKUP OPTIMIZATION ON;
    CONFIGURE DEFAULT DEVICE TYPE TO DISK;
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '%d_bkp_cf%F';
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
    CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 1;
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' FORMAT '%d_bkp_df%t_Set%s_Piece%p';
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/orahome2/custprdb/9.2.0/dbs/snapcf_custpr.f'; # default
    RMAN>
    RMAN> # The following commands are run each day to start the backup cycle.
    2> # The steps are:
    3> # - Take an incremental level 0 backup of the database. A level 0 backup is
    4> # a complete backup of the entire file which can be used as the basis
    5> # for a subsequent incremental backup.
    6> # - Backup all archivelogs that have not already been backed up.
    7> # - Delete on-disk archivelogs older than seven days.
    8>
    9> BACKUP INCREMENTAL LEVEL 0 FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p'
    10> DATABASE maxsetsize 33G
    11> PLUS ARCHIVELOG FORMAT '/backups/admin/custpr/%d_bkp_al%t_Set%s_Piece%p'
    12> delete all input;
    Starting backup at 12/30/2008 22:01:40
    current log archived
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=11 devtype=DISK
    channel ORA_DISK_1: starting archive log backupset
    channel ORA_DISK_1: specifying archive log(s) in backup set
    input archive log thread=1 sequence=8008 recid=7910 stamp=674638862
    input archive log thread=1 sequence=8009 recid=7911 stamp=674671207
    input archive log thread=1 sequence=8010 recid=7912 stamp=674697380
    input archive log thread=1 sequence=8011 recid=7913 stamp=674780433
    input archive log thread=1 sequence=8012 recid=7914 stamp=674784211
    input archive log thread=1 sequence=8013 recid=7915 stamp=674863288
    input archive log thread=1 sequence=8014 recid=7916 stamp=674863300
    channel ORA_DISK_1: starting piece 1 at 12/30/2008 22:01:41
    channel ORA_DISK_1: finished piece 1 at 12/30/2008 22:03:47
    piece handle=/backups/admin/custpr/CUSTPR_bkp_al674863300_Set3083_Piece1 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:02:07
    channel ORA_DISK_1: deleting archive log(s)
    archive log filename=/custpr/arch/arch_custpr_8008.log recid=7910 stamp=674638862
    archive log filename=/custpr/arch/arch_custpr_8009.log recid=7911 stamp=674671207
    archive log filename=/custpr/arch/arch_custpr_8010.log recid=7912 stamp=674697380
    archive log filename=/custpr/arch/arch_custpr_8011.log recid=7913 stamp=674780433
    archive log filename=/custpr/arch/arch_custpr_8012.log recid=7914 stamp=674784211
    archive log filename=/custpr/arch/arch_custpr_8013.log recid=7915 stamp=674863288
    archive log filename=/custpr/arch/arch_custpr_8014.log recid=7916 stamp=674863300
    Finished backup at 12/30/2008 22:03:47
    Starting backup at 12/30/2008 22:03:47
    using channel ORA_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of backup command at 12/30/2008 22:03:47
    RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
    RMAN>
    RMAN> ##BACKUP ARCHIVELOG ALL FORMAT '%d_bkp_al_%t_Set%s_Piece%p' delete input;
    2>
    3> # DELETE ARCHIVELOG UNTIL TIME 'SYSDATE-7';
    4>
    5> # check if database can be restored
    6> # RESTORE DATABASE VALIDATE;
    7>
    8> # check if controlfile can be restored
    9> ##RESTORE CONTROLFILE to '/backups/admin/custpr/custpr_bkp_cntlfile.ctl' VALIDATE;
    10>
    11> # check if archivelogs for the past two weeks can be restored
    12> # RESTORE ARCHIVELOG FROM TIME 'SYSDATE-7' VALIDATE;
    13>
    14> # - Verify all backups on backup media are intact
    15> # CROSSCHECK BACKUP OF DATABASE;
    16>
    17> # - Display a list of files that need to be backed up based on the retention
    18> # policy. For this case study, files that don't have at least 1 backups
    19> # will be reported.
    20> REPORT NEED BACKUP;
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to recovery window of 7 days
    Report of files whose recovery needs more than 7 days of archived logs
    File Days Name
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of report command at 12/30/2008 22:03:48
    RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
    RMAN>
    RMAN> # - delete un-necessary backups. This command deletes backups based on the
    2> # retention policy.
    3> ######### commented out DELETE OBSOLETE - TSM not configured to delete on 68
    4> #########DELETE OBSOLETE;
    5>
    6> # - get complete list of existing backups
    7> LIST BACKUP;
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of list command at 12/30/2008 22:03:49
    RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
    RMAN>
    RMAN> #-end of file-
    2> **end-of-file**
    RMAN>
    Recovery Manager complete.

  • Restore a single tablespace from full backup erroring out

    Hi,
    I have backed up the full database using RMAN:
    $ rman catalog rman/rman@catdb target /
    RMAN> run {
    backup as compressed backupset
    format '<Full Path>/databkp/DATA_%d_%s_%p'
    database
    plus archivelog format '<Full Path>/arcbkp/ARC_%d_%s_%p';
    Backup was successful.
    Now dropped the tablespaces:
    SQL> alter tablespace rtestusr offline;
    SQL> drop tablespace RTESTUSR including contents and datafiles;
    Now trying to restore the tablespace RTESTUSR
    $ rman catalog rman/rman@catdb target /
    RMAN> restore tablespace rtestusr;
    Starting restore at 25-FEB-11
    starting full resync of recovery catalog
    full resync complete
    using channel ORA_DISK_1
    using channel ORA_DISK_2
    using channel ORA_DISK_3
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 02/25/2011 14:28:47
    RMAN-06004: ORACLE error from recovery catalog database: RMAN-20202: tablespace not found in the recovery catalog
    RMAN-06019: could not translate tablespace name "RTESTUSR"
    Also performed the Tablespace Point-in-time recovery:
    RMAN> run {
    2> set until time "to_date('2011-02-25:12:44:00','yyyy-mm-dd:hh24:mi:ss')";
    3> restore tablespace RTESTUSR;
    4> }
    executing command: SET until clause
    Starting restore at 25-FEB-11
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=46 devtype=DISK
    allocated channel: ORA_DISK_2
    channel ORA_DISK_2: sid=45 devtype=DISK
    allocated channel: ORA_DISK_3
    channel ORA_DISK_3: sid=44 devtype=DISK
    channel ORA_DISK_1: starting datafile backupset restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    restoring datafile 00006 to /dev2db/rmantst/db/oradata/rtest/rtestusr01.dbf
    channel ORA_DISK_1: reading from backup piece /dev2db/rmantst/archrtst/databkp/DATA_RTEST_76_1
    channel ORA_DISK_1: restored backup piece 1
    piece handle=/dev2db/rmantst/archrtst/databkp/DATA_RTEST_76_1 tag=TAG20110225T114341
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:02
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 02/25/2011 15:07:42
    ORA-19654: must use backup control file to switch file incarnations
    Please help.
    Thanks in advance.
    Regards,
    Bikram

    I think you misunderstand some concepts.
    1) drop tablespace RTESTUSR including contents and datafiles;
    is a valid command, it removes the named tablespace from the database. There's nothing wrong with the database (although it may be a logical (human) error). Restore/recovery is used to repair media failures. RMAN is right: 'RMAN-06019: could not translate tablespace name "RTESTUSR"', since there's no such tablespace in the actual database, the restore/recover process fails.
    2) Unfortunately you hide your database version. Up to 10gR2 tablespace point-in-time recovery cannot be used to recover dropped tablespaces, in 11gR1 and higher it's possible.
    And - TSPITR - requires a little bit more than 'set until ...'. Refer to the doumentation for your unknown database version.
    Werner

  • Backup error; datafiles is already in backup status

    Dear Experts,
    While we are starting online db backup, we are getting following errors;
    BR0280I BRBACKUP time stamp: 2009-07-13 02.16.07
    BR0319I Control file copy created: /oracle/TBP/sapbackup/cntrlTBP.dbf 34783232
    BR0328E Database file /oracle/TBP/sapdata1/system_1/system.data1 of tablespace SYSTEM is already in backup status
    BR0328E Database file /oracle/TBP/sapdata1/undo_1/undo.data1 of tablespace PSAPUNDO is already in backup status
    BR0328E Database file /oracle/TBP/sapdata1/sysaux_1/sysaux.data1 of tablespace SYSAUX is already in backup status
    BR0328E Database file /oracle/TBP/sapdata2/sr3_1/sr3.data1 of tablespace PSAPSR3 is already in backup status
    BR0328E Database file /oracle/TBP/sapdata3/sr3700_1/sr3700.data1 of tablespace PSAPSR3700 is already in backup status
    BR0328E Database file /oracle/TBP/sapdata4/sr3usr_1/sr3usr.data1 of tablespace PSAPSR3USR is already in backup status
    BR0328E Database file /oracle/TBP/sapdata4/sr3700_2/sr3700.data2 of tablespace PSAPSR3700 is already in backup status
    BR0328E Database file /oracle/TBP/sapdata1/sr3_2/sr3.data2 of tablespace PSAPSR3 is already in backup status
    BR0328E Database file /oracle/TBP/sapdata2/sr3_3/sr3.data3 of tablespace PSAPSR3 is already in backup status
    BR0328E Database file /oracle/TBP/sapdata3/sr3_4/sr3.data4 of tablespace PSAPSR3 is already in backup status
    BR0328E Database file /oracle/TBP/sapdata4/sr3_5/sr3.data5 of tablespace PSAPSR3 is already in backup status
    BR0328E Database file /oracle/TBP/sapdata1/sr3_6/sr3.data6 of tablespace PSAPSR3 is already in backup status
    BR0328E Database file /oracle/TBP/sapdata3/sr3_7/sr3.data7 of tablespace PSAPSR3 is already in backup status
    BR0328E Database file /oracle/TBP/sapdata4/sr3_8/sr3.data8 of tablespace PSAPSR3 is already in backup status
    BR0328E Database file /oracle/TBP/sapdata2/sr3700_3/sr3700.data3 of tablespace PSAPSR3700 is already in backup status
    BR0328E Database file /oracle/TBP/sapdata1/sr3_9/sr3.data9 of tablespace PSAPSR3 is already in backup status
    BR0328E Database file /oracle/TBP/sapdata2/sr3_10/sr3.data10 of tablespace PSAPSR3 is already in backup status
    BR0328E Database file /oracle/TBP/sapdata3/sr3_11/sr3.data11 of tablespace PSAPSR3 is already in backup status
    BR0328E Database file /oracle/TBP/sapdata4/sr3_12/sr3.data12 of tablespace PSAPSR3 is already in backup status
    BR0056I End of database backup: beazuchh.anf 2009-07-13 02.16.08
    BR0280I BRBACKUP time stamp: 2009-07-13 02.16.08
    I've tried to take datafiles out of backup mode with following commands ;
    SQL> select * from v$backup;
         FILE# STATUS                CHANGE# TIME
             1 ACTIVE              492340220 05-JUL-09
             2 ACTIVE              492340220 05-JUL-09
             3 ACTIVE              492340220 05-JUL-09
             4 ACTIVE              492340220 05-JUL-09
             5 ACTIVE              492340220 05-JUL-09
             6 ACTIVE              492340220 05-JUL-09
             7 ACTIVE              492340220 05-JUL-09
             8 ACTIVE              492340220 05-JUL-09
             9 ACTIVE              492340220 05-JUL-09
            10 ACTIVE              492340220 05-JUL-09
            11 ACTIVE              492340220 05-JUL-09
         FILE# STATUS                CHANGE# TIME
            12 ACTIVE              492340220 05-JUL-09
            13 ACTIVE              492340220 05-JUL-09
            14 ACTIVE              492340220 05-JUL-09
            15 ACTIVE              492340220 05-JUL-09
            16 ACTIVE              492340220 05-JUL-09
            17 ACTIVE              492340220 05-JUL-09
            18 ACTIVE              492340220 05-JUL-09
            19 ACTIVE              492340220 05-JUL-09
    19 rows selected.
    SQL> select 'alter database datafile '
      2  || file#  || ' end backup;'
      3  from v$backup where status = 'ACTIVE';
    'ALTERDATABASEDATAFILE'||FILE#||'ENDBACKUP;'                                   
    alter database datafile 1 end backup;                                          
    alter database datafile 2 end backup;                                          
    alter database datafile 3 end backup;                                          
    alter database datafile 4 end backup;                                          
    alter database datafile 5 end backup;                                          
    alter database datafile 6 end backup;                                          
    alter database datafile 7 end backup;                                          
    alter database datafile 8 end backup;                                          
    alter database datafile 9 end backup;                                          
    alter database datafile 10 end backup;                                         
    alter database datafile 11 end backup;                                         
    'ALTERDATABASEDATAFILE'||FILE#||'ENDBACKUP;'                                   
    alter database datafile 12 end backup;                                         
    alter database datafile 13 end backup;                                         
    alter database datafile 14 end backup;                                         
    alter database datafile 15 end backup;                                         
    alter database datafile 16 end backup;                                         
    alter database datafile 17 end backup;                                         
    alter database datafile 18 end backup;                                         
    alter database datafile 19 end backup;                                         
    when we execute above script we are getting following errors;
    alter database datafile 1 end backup
    ERROR at line 1:
    ORA-01235: END BACKUP failed for 1 file(s) and succeeded for 0
    ORA-01234: cannot end backup of file 1 - file is in use or recovery
    ORA-01110: data file 1: '/oracle/TBP/sapdata1/system_1/system.data1'
    alter database datafile 2 end backup
    ERROR at line 1:
    ORA-01235: END BACKUP failed for 1 file(s) and succeeded for 0
    ORA-01234: cannot end backup of file 2 - file is in use or recovery
    ORA-01110: data file 2: '/oracle/TBP/sapdata1/undo_1/undo.data1'
    alter database datafile 3 end backup
    ERROR at line 1:
    ORA-01235: END BACKUP failed for 1 file(s) and succeeded for 0
    ORA-01234: cannot end backup of file 3 - file is in use or recovery
    ORA-01110: data file 3: '/oracle/TBP/sapdata1/sysaux_1/sysaux.data1'
    alter database datafile 4 end backup
    ERROR at line 1:
    ORA-01235: END BACKUP failed for 1 file(s) and succeeded for 0
    ORA-01234: cannot end backup of file 4 - file is in use or recovery
    ORA-01110: data file 4: '/oracle/TBP/sapdata2/sr3_1/sr3.data1'
    alter database datafile 5 end backup
    ERROR at line 1:
    ORA-01235: END BACKUP failed for 1 file(s) and succeeded for 0
    ORA-01234: cannot end backup of file 5 - file is in use or recovery
    ORA-01110: data file 5: '/oracle/TBP/sapdata3/sr3700_1/sr3700.data1'
    How can we take datafile out of backup mode ?
    Regards
    Atakan

    Hi,
    You can take out tablespace from backp mode from below sql.
    SQL>ALTER TABLESPACE <tablespace name> END BACKUP;
    Check Re: backup problem
    Hope this helps
    Thanks
    Sushil

  • Oracle Secure Backup error: 'No such file or directory'

    Hi,
    could you help me to fix the following issue?
    RMAN> run {   ALLOCATE CHANNEL c1 DEVICE TYPE sbt PARMS='SBT_LIBRARY=C:\windows\
    system32\orasbt.dll' ; backup database format 'CF_%d_%T_s%sp%pt%t'; }
    using target database control file instead of recovery catalog
    allocated channel: c1
    channel c1: SID=8 device type=SBT_TAPE
    channel c1: Oracle Secure BackupStarting backup at 26-OCT-09
    channel c1: starting full datafile backup set
    channel c1: specifying datafile(s) in backup set
    input datafile file number=00001 name=C:\APP\AIME\ORADATA\ORCL\SYSTEM01.DBF
    input datafile file number=00002 name=C:\APP\AIME\ORADATA\ORCL\SYSAUX01.DBF
    input datafile file number=00003 name=C:\APP\AIME\ORADATA\ORCL\UNDOTBS01.DBF
    input datafile file number=00004 name=C:\APP\AIME\ORADATA\ORCL\USERS01.DBF
    input datafile file number=00005 name=C:\APP\AIME\PRODUCT\11.2.0\DBHOME_1\DATABA
    SE\TBS_5.F
    channel c1: starting piece 1 at 26-OCT-09
    released channel: c1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of backup command on c1 channel at 10/26/2009 00:20:54
    ORA-19506: failed to create sequential file, name="CF_ORCL_20091026_s10p1t701223
    652", parms=""
    ORA-27028: skgfqcre: sbtbackup returned error
    ORA-19511: Error received from media manager layer, error text:
    sbt__rpc_cat_query: Query for piece CF_ORCL_20091026_s10p1t701223652 failed.
    (Oracle Secure Backup error: 'No such file or directory').
    Thanks,
    jun

    You can work entirely in Xcode by using the command-line tool template in C. Xcode > File > New > Project > Command-Line Tool > Next > Language: C > Next > Create.
    If you do want to work on the command line, you may as well just use the "clang" program instead. The "gcc" tool is just a compatibility tool for existing scripts that are expecting the actual "gcc" program. Apple hasn't used the real "gcc" for years. (Read up on the GPLv3 for more information.)
    The gcc/clang arguments are the same. The "-c" flag instructs the compiler to only compile a single .c file into a .o object file. It won't create an executable. If you are only compiling a single source file, just omit the "-c" flag and the compiler will create an executable named "a.out" that you can run by typing "./a.out". You can specify "-o <executable name>" if you want to specify a name. Once you get more than a handful of source files, using the terminal starts to become a hassle. At that point, you definitely want to start using Xcode.
    I'm not sure why you would try to compile "helloworlddot1.c" and then get an error message about "filename.c". Something else is wrong.
    If you are working in the Terminal, it is easiest to use the "cd" command to move into the same directory as your source files. Then you don't have to keep typing the full path.
    It is hard to say what the "best" community is. There are many to choose from.

  • Fatal error in recovery manager

    Hi,
    I am trying to restore my DB for disaster recovery, I have taken a backup earlier in flash_recovery_area with controlfile autobackup on.
    I have successfully restored spfile and controlfiles, but when I am running restore database, rman is crashing:
    RMAN> startup force mount;
    RMAN> restore database;
    Starting restore at 17-JUL-13
    Starting implicit crosscheck backup at 17-JUL-13
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=170 device type=DISK
    Crosschecked 4 objects
    Finished implicit crosscheck backup at 17-JUL-13
    Starting implicit crosscheck copy at 17-JUL-13
    using channel ORA_DISK_1
    Finished implicit crosscheck copy at 17-JUL-13
    searching for all files in the recovery area
    cataloging files...
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00601: fatal error in recovery manager
    RMAN-03004: fatal error during execution of command
    ORA-01092: ORACLE instance terminated. Disconnection forced
    RMAN-03002: failure of restore command at 07/17/2013 23:44:08
    ORA-03113: end-of-file on communication channel
    Process ID: 10307
    Session ID: 162 Serial number: 9
    ORACLE error from target database:
    ORA-03114: not connected to ORACLE
    please help me out identifying the issue.
    thanks,

    this directory is actually empty : /scratch/oradba/db/apps_st/zDB/dat/
    It had all data files earlier, but to try disaster recovery I manually removed all of them to bring them back from backup.
    I am following all these steps: Hemant's Oracle DBA Blog: RMAN Backup and Recovery for Loss of ALL files
    but at restore database, its crashing out. 

  • Backup database required recovery

    Hello all,
    I am trying to perform hot backup and recovery, the bckup was taken and then im getting this error.
    iam using oracle 11.2.0.1.0 and on windows environment.
    SQL> alter database open read only;
    alter database open read only
    ERROR at line 1:
    ORA-16004: backup database required recovery
    ORA-01195: online backup of file 1 needs more recovery to be consistent
    ORA-01110: data file 1: 'C:\APP\USER\ORADATA\PROD3\SYSTEM01.DBF'

    SQL> startup
    ORACLE instance started.
    Total System Global Area 2555445248 bytes
    Fixed Size 2178456 bytes
    Variable Size 1577058920 bytes
    Database Buffers 956301312 bytes
    Redo Buffers 19906560 bytes
    Database mounted.
    ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
    SQL> alter database open read only;
    alter database open read only
    ERROR at line 1:
    ORA-16004: backup database required recovery
    ORA-01195: online backup of file 1 needs more recovery to be consistent
    ORA-01110: data file 1: 'C:\APP\USER\ORADATA\PROD3\SYSTEM01.DBF'
    SQL> select hxfil FILENUMBER,fhsta STATUS,fhscn SCN,fhrba_Seq SEQUENCE from x$kc
    vfh;
    FILENUMBER STATUS SCN SEQUENCE
    1 8193 20030487 15
    2 1 20030487 15
    3 1 20030487 15
    4 1 20030487 15
    5 1 20030487 15
    6 4 20032393 19
    7 4 20032393 19
    7 rows selected.

  • Backup error due to System Writer missing (enumeration of system32 printer dlls takes too long)

    Hi,
    On a Windows 2008 R2 we get a Windows Backup error while backupping System State (event id: 5, error code: '2155347997').
    We tried *ALL* solutions found on Internet regarding the same issue (and we also applied the suggested hotfix KB2807849) but without success. So we DIGGED INTO VSS to see what is happening.
    ***1) First we saw that an USB printer had a problem and this resulted in
    hundreds of entries in the following registry keys:
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\StillImage\DeviceNameStore\Canon MF6500 Series #100010]
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\StillImage\DeviceNameStore\Canon MF6500 Series #100011]
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\StillImage\DeviceNameStore\Canon MF6500 Series #100012]
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\StillImage\DeviceNameStore\{6BDD1FC6-810F-11D0-BEC7-08002BE2092F}\79590]
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\StillImage\DeviceNameStore\{6BDD1FC6-810F-11D0-BEC7-08002BE2092F}\79591]
    ***2) We completely removed ALL drivers/devices related to that printer (now the DeviceNameStore is empty and
    pnputil -e returns no driver related to the printer)
    ***3) Using process monitor we saw that during vssadmin list writers the system is searching for the DLLs related to that printer AND SEEMS CAUGHT IN AN ENDLESS LOOP: this is an excerpt of the scan:
    09:56:34,5205954    svchost.exe    324    RegSetValue    HKLM\System\CurrentControlSet\services\VSS\Diag\System Writer\IDENTIFY (Enter)    SUCCESS
    09:57:18,2310377 svchost.exe 324 QueryDirectory C:\Windows\System32\spool\drivers\color\cnz005.icc NO SUCH FILE Filter: cnz005.icc
    09:57:18,2312877 svchost.exe 324 QueryDirectory C:\Windows\System32\spool\drivers\color\cnf6500m.icc NO SUCH FILE Filter: cnf6500m.icc
    09:57:18,2314854 svchost.exe 324 QueryDirectory C:\Windows\System32\cncmfp20.ini NO SUCH FILE Filter: cncmfp20.ini
    09:57:18,2316416 svchost.exe 324 QueryDirectory C:\Windows\System32\cnclsi20.dll NO SUCH FILE Filter: cnclsi20.dll
    ... and so on
    .... THE SAME FILES ARE REPEATED HUNDREDS OF TIMES!!!! ...
    It seems that somewhere there is a catalog of system files which still contains the references to the (same) files used by the hundreds of devices that WERE present in the DeviceNameStore (see point ***1 above, but now it is empty),  and the System
    Writer continues to search/enumerate those files and fails.
    How can I fix it ? Is there a way to "reset" the System Writer and "rebuild" (???) the correct files that it should backup? (in order to complete a successfull system state backup)
    Can you help me?
    Thank you in advance.
    EDIT: some additional (useful?) information:
    * we also ran chkdsk /f C: 
    * sfc /scannow completes without errors
    * in the vssadmin list writers the "system writer" is missing (but - as said above - when we run it the associated process repeatedly search printer dll files in the System32 directory)
    * perhaps those file are contained is some filemaps catalog ?!? Is there a way to "reset" them?!?
    ***EDIT 2***:
    I found that the reference to those missing DLLs are in ***C:\Windows\inf\setupapi.ev3*** but if I move the file away the System Writer continues not being listed in vssadmin list writer (though the vssadmin command complete very fast).
    This is what is happening:
    svchost.exe    324    CloseFile    C:\Windows\inf    SUCCESS    
    svchost.exe    324    CloseFile    C:\Windows\System32\DriverStore\infpub.dat    SUCCESS    
    svchost.exe    324    CreateFile    C:\Windows\System32\DriverStore\infpub.dat    ACCESS DENIED
    svchost.exe    324    CreateFile    C:\Windows\System32\DriverStore\infstor.dat    ACCESS DENIED
    svchost.exe    324    CreateFile    C:\Windows\System32\DriverStore\infstrng.dat    ACCESS DENIED
    svchost.exe    324    CreateFile    C:\Windows\System32\DriverStore\drvindex.dat    ACCESS DENIED
    svchost.exe    324    CreateFile    C:\Windows\System32\DriverStore\INFCACHE.0    NAME NOT FOUND
    svchost.exe    324    CreateFile    C:\Windows\System32\DriverStore\INFCACHE.1    ACCESS DENIED
    svchost.exe    324    CreateFile    C:\Windows\System32\DriverStore\INFCACHE.2    NAME NOT FOUND
    svchost.exe    324    CreateFile    C:\Windows\inf    SUCCESS
    svchost.exe    324    QueryBasicInformationFile    C:\Windows\inf    SUCCESS
    svchost.exe    324    RegCloseKey    HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup    SUCCESS    
    svchost.exe    324    CreateFile    C:\Windows\inf\setupapi.ev1    SUCCESS
    svchost.exe    324    QueryStandardInformationFile    C:\Windows\inf\setupapi.ev1    SUCCESS
    svchost.exe    324    CreateFileMapping    C:\Windows\inf\setupapi.ev1
    svchost.exe    324    QueryStandardInformationFile    C:\Windows\inf\setupapi.ev1    SUCCESS
    svchost.exe    324    CreateFileMapping    C:\Windows\inf\setupapi.ev1
    svchost.exe    324    CreateFile    C:\Windows\inf\setupapi.ev2    SUCCESS
    svchost.exe    324    QueryStandardInformationFile    C:\Windows\inf\setupapi.ev2
    svchost.exe    324    CreateFileMapping    C:\Windows\inf\setupapi.ev2
    svchost.exe    324    QueryStandardInformationFile    C:\Windows\inf\setupapi.ev2    SUCCESS
    svchost.exe    324    CreateFileMapping    C:\Windows\inf\setupapi.ev2
    svchost.exe    324    CreateFile    C:\Windows\inf\setupapi.ev3    SUCCESS
    svchost.exe    324    QueryStandardInformationFile    C:\Windows\inf\setupapi.ev3
    svchost.exe    324    CreateFileMapping    C:\Windows\inf\setupapi.ev3
    svchost.exe    324    QueryStandardInformationFile    C:\Windows\inf\setupapi.ev3
    svchost.exe    324    CreateFileMapping    C:\Windows\inf\setupapi.ev3    SUCCESS
    svchost.exe    324    CreateFile    C:\Windows\System32\drivers    SUCCESS
    svchost.exe    324    QueryDirectory    C:\Windows\System32\drivers\acpi.sys    SUCCESS
    svchost.exe    324    QueryDirectory    C:\Windows\System32\drivers\rdpbus.sys    SUCCESS
    svchost.exe    324    QueryDirectory    C:\Windows\System32\drivers\i8042prt.sys    SUCCESS
    .... EVERYTHING IS OK UP TO HERE ...
    svchost.exe    324    CloseFile    C:\Windows\System32\drivers    SUCCESS
    svchost.exe    324    CreateFile    C:\Windows\System32    SUCCESS
    svchost.exe    324    QueryDirectory    C:\Windows\System32\cncc6500.dll    NO SUCH FILE    Filter: cncc6500.dll
    svchost.exe    324    QueryDirectory    C:\Windows\System32\cnci6500.dll    NO SUCH FILE    Filter: cnci6500.dll
    svchost.exe    324    QueryDirectory    C:\Windows\System32\cncc6500.dll    NO SUCH FILE    Filter: cncc6500.dll
    svchost.exe    324    QueryDirectory    C:\Windows\System32\cnci6500.dll    NO SUCH FILE    Filter: cnci6500.dll
    ... !!!!!GET CAUGHT IN AN ENDLESS LOOP!!!!!!!! (System Writer probably ends for timeout)...
    Is there a way to rebuild/modify that file C:\Windows\inf\setupapi.ev3
    Perhaps I can delete the catroot2 directory?

    Hi,
    Please check if there are number of files in Temporary ASP.NET folders under "C:\Windows\Microsoft.Net\Framework". If so, clear these files then restart the server to check the results.
    In additional, you could try the steps below to troubleshoot the issue:
    1. Give NETWORK SERVICE Read permissions on COM+ Event System.
    a. Open the registry editor and navigate to HKLM\CurrentControlSet\Services\EventSystem.
    b. Right click on the EventSystem and then select ‘Permissions’
    c. Click on ‘ADD’ button and then type in ‘NETWORK SERVICE’ and give it READ permission.
    d. Reboot the machine and then run the 'VSS admin list writers' to check if it shows up the 'system writer'.
    2. If the step 1 doesn't work then move the contents of C:\Windows\winsxs\FileMaps to an alternate location. Then run the command 'VSS admin list writers' to check if it shows up the 'system writer'.  Is so, some of those files maybe corrupted and we
    need to identify them and replace the files from a healthy machine.
    Regards,
    Mandy
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • JDeveloper 11.1.2.0.0 Version Application wizard : File Backup Error

    hi
    As shown in the scenario (sc1) screencast at http://screencast.com/t/GA7OcgYZ
    the JDeveloper 11.1.2.0.0 Version Application wizard can fail sometimes, showing a "File Backup Error" dialog, with the message
    "Failed attempting to back up imported resource
    D:\screencast\VersionAppLockedIssueApp-v0.01\VersionAppLockedIssueApp\Model.
    Check that there are no file system explorers viewing files in this location and that none of the files are open in other applications before resuming."
    This even occurs when there are no other processes (like Windows Explorer or an editor) using/locking the file.
    It should be possible to reproduce the behaviour using the example application
    at http://www.consideringred.com/files/oracle/2011/VersionAppLockedIssueApp-v0.01.zip
    which is really nothing special I think, so it might also reproduce using another application.
    First open the application and also open the file "browseEmployees.jsf" in design view.
    After that, as it seems, the Version Application wizard fails.
    Note that it might be relevant that I am using Windows 7, as I can imagine that this could behave differently when using JDeveloper on other operating systems.
    Also note, if I try to ZIP the application folder (instead of using the Version Application wizard) after opening the file "browseEmployees.jsf" in design view, I get a message like "WARNING: The process cannot access the file because it is being used by another process.
    : D:\screencast\VersionAppLockedIssueApp-v0.01\VersionAppLockedIssueApp\.data\00000000\je.lck ",
    as can be seen in the scenario (sc2) screencast at http://screencast.com/t/rFiL47Bil
    As it seems that the Version Application wizard has managed to commit the source files, one workaround could be to checkout the source in another location and continue working there.
    Other suggestions to avoid this issue, or deal with it, are welcome.
    questions:
    - (q1) Can this "File Backup Error" behaviour for the Version Application wizard be reproduced?
    - (q2) How can this "File Backup Error" behaviour for the Version Application wizard be explained?
    many thanks
    Jan Vervecken

    fyi
    Today I noticed that there is a My Oracle Support note about this:
    - note id 1353389.1 , "In JDeveloper11.1.2.0.0 the Version Application Wizard Failed with the Error: File Backup Error "
    Its "Solution" section currently says:
    "The problem is still investigated by development.
    But there is a possible workaround for Bug 12912410 by unchecking the checkbox 'Perform Checkout' in step 5 of 6 in the wizard screen. "
    regards
    Jan

  • Time machine backup error in Mavericks

    I"m getting backup errors in Mavericks when it tries to back up to the Backups.backupdb folder in my 3TB external backup drive.  This happens even when I turn Time Machine off! 
    This is the error I'm getting (taken from the console) when I manually start a time machine backup:
    10/26/13 9:56:39.268 AM com.apple.backupd[18160]: Starting manual backup
    10/26/13 9:56:40.826 AM com.apple.backupd[18160]: Backing up to /dev/disk2s2: /Volumes/Macbook Pro Backup 3TB/Backups.backupdb
    10/26/13 9:56:46.069 AM com.apple.backupd[18160]: Error: (22) setxattr for key:com.apple.backupd.HostUUID path:/Volumes/Macbook Pro Backup 3TB/Backups.backupdb/Macbook Pro 25 size:37
    10/26/13 9:56:46.070 AM com.apple.backupd[18160]: Backup failed with error 2: 2
    Has anyone seen this?  At this point, I haven't been able to back up anything after upgrading to Mavericks, and I really don't want to delete the backup folder and start over.
    I thought it might be a permissions problem, so I tried to use the disk utility to verify this.  I wasn't able to select verify or repair disk permissions.  When I tried to verify the disk, I got a 'Live file system repair is not supported' error.  I've never seen this before.
    Any thoughts on all of this?

    I fixed this by hard booting, then repairing the disk.  A restart didn't work. 

  • Restoring iTunes Backup Error

    I have 8 DVDs of a backup I did on my PC before I restored it. iTunes will backup the first DVD fine. When I put in my second DVD, I get the error "unknown error occurred (-69)". Also if I try to load the disc later, iTunes just freezes up until I eject the disc.
    Edit: Also I tried to contact Apple but they actually have no way to contact them about backup errors.
    Message was edited by: thaychris

    I have exactly the same problem - 1st DVD worked fine, 2nd worked until 255 song out of 721 and the other 4 dvds just cause itunes and my whole laptop to crash Since I'd made the original dvd backup I did an incremental back up using cds - these have worked fine. Beginning to wonder if the dvds just hold too much data for itunes to be able to copy from dvd at one time. Let me know if you find out anything new and good luck. Thanks.

  • I cant update my iphone4 to IOS6 because of a backup error, -43.

    Hmm... not quite sure what else I need to say. Just to re-state my question: I cant update my iphone4 to IOS6 because of a backup error, -43.

    Hi, and welcome to the community!
    So was this Spotify account originally created with facebook and not created with Spotify then linked to facebook? It sounds like it if you login with an email.
    Can you log in on the Spotify web player?
    Anthony

  • ITunes[260:16443]: iTunes: Backup error -30

    When I try to synchronize my iPhone I always have the save message : Unable to backup the iPhone...
    When I look at the Console, I read the following message
    iTunes[260:16443]: iTunes: Backup error -30
    Could someone help me ?

    I had the same error and just fixed it.
    I'd moved the backup files to an external drive then deleted them from the library, but even without old backups, the process failed.
    I tried many of the suggestions I found in other threads, but it still wouldn't work.
    Eventually I tried unchecking the "Encrypt iPhone Backup" My previous backups were encrypted with a password, so when I unchecked the box, I was prompted for that password, which let me remove the encryption.
    I then rechecked the box, entered in a "new" password, but I used the same one as before. The back up ran and showed progress in a pop-up window. A few minutes later, it was done.
    I've since tested it through the normal process and everything is working again.
    Hope this helps.

Maybe you are looking for