IDS/IPS config Backup through IDM

Hi,
Can we take config backup through IDM, as I regularly upgrade OS & signautures and need to take backup of our config. But in IDM I could not find any option. AS I solely want to use IDM for all purposes.
Currenlty I need to do ssh,take backup and then upgrade thru IDM.

Thanks for your reply! I should then request Cisco developers to give such usefule facility as then we can solely use IDM for all purposes. Its painful to log thru ssh take backup and then upgrade using IDM. or use only ss to do everything then what for IDM is?
Reg.
YT

Similar Messages

  • How do I backup an IPS config (ASA-SSM-10)

    Hi,
    How do I backup an IPS config (ASA-SSM-10)?
    Thanks

    There is a copy command in the IPS CLI that can be used to copy the current configuration to a backup configuration on the sensor itself.
    Or to copy the current configuration to an FTP or SCP server.
    The copy command can then be used to copy a configuration from backup or from an FTP or SCP server back to the running configuration of the sensor.
    http://www.cisco.com/en/US/docs/security/ips/6.2/command/reference/crCmds.html#wp458440

  • WLC 4400 and IDS/IPS

    One of my clients is keen to know the IDS/IPS capabilities with WLC 4400. Any hints? Also can anyone explain IDS sensor to me? Thank you.

    There are a number of IDS capabilities that are highlighted regarding the WLC. Unfortunately, you will find that the product continues to suffer from ongoing false positives and a severe lack of documentation (and support) for the IDS.
    For example, if you utilize containment against a rogue AP (which is used to prevent users from attaching to the rogue), the system detects its own containment messages as a denial of service attack. The system is not intelligent enough to know that it is the source of these messages and ignore them.
    Initially, Cisco flagged these false positive as "cosmetic" and claimed that to fix them required a "feature request that must be run through the Cisco sales team" which we did in the spring of 07. Cisco has be VERY slow in coming around on getting these fixed (it has been well over a year since these have been documented and they are still not resolved in the current version of 4.2).
    The Wireless IDS system is also famous for other false alarms which Cisco TAC has linked to alarming on normal behavior when a client goes out of range and a string of deauthentication messages is sent to make sure that the conversation has ended. The WLC 4.2 continues to flag these as false-positive denial-of-service attacks even though the IDS parameters could be adjusted (from the factory) to account for the known 64 repeated deauths that are sent.
    The IDS file is capable of "tuning" but the parameters are very lightly documented. In fact, the IDS parameter file itself had the least sparse version of documentation and it is a text file only 200-lines long.
    In terms of determining if a rogue AP is on-wire. This functionality does not work reliably (not just if there is no path on the wired network to the controller which is understandable) but even if the rogue AP is on the same subnet as the controller. It just plain does not work.
    If you are attempting to determine if there are clients on the rogue AP, this mechanism works with limited success since the AP has to catch the client attaching during its brief scan interval. This results in misleading information.
    There are other false alarms that appear to be related to a specific chipset (using the OUI / first octet of the MAC address). However, there has been very little movement on Cisco's part in getting resolution to getting these anomalies addressed. The basic attitude has been "if we didn't see it in our lab in San Jose when we wrote the code, there's nothing we can do". Since the IDS lacks any ability to "phone home" (sending the alarms it is seeing to the development team) they end up having to develop in a relatively limited environment.
    For more information, please reference the following:
    Wireless LAN Controller IDS Signature Parameters
    http://www.cisco.com/en/US/tech/tk722/tk809/technologies_tech_note09186a008063e5d0.shtml
    I would send you the link to some of the bugs, such as CSCsj06015, CSCsh35010, CSCsk60655, etc. but the Cisco bug tool ( http://tools.cisco.com/Support/BugToolKit/ )is currently not working (no doubt the system is getting overworked). Maybe the site will be up when you read this.
    In the interest of fairness, there have been efforts over the past year by Cisco to address these false alarms and a number of them appear to finally be resolved.
    Bottom line: In my opinion, the wireless IDS is still not ready for prime time. To quote my customer, "I just can't trust it". Unless you set your customer's expectations fairly low, you will both end up disappointed.
    That said, the product itself still has many compelling reasons to implement it including ease of installation and management. If you are willing to wade through the various bugs in the IDS and WCS it still is the best game in town.
    - John

  • IDS/IPS 4250, two sensors, connection status Paused

    Hi,
    I have VMS 2.3 and SecMon 2.2 and two IDSs in there. I have noticed that the connection status for the sensors have changed from "Connected TLS" to "Paused". I have gone through database truncation process and all file sizes are good butstill having issues.
    I deleted the sensors from the SecMon and added only one sensor, the connection status changed back to connected but it was set to paused in one hour time after adding the one sensor.
    I can login to the sensor, i can ping the VMS server from the IDS command prompt and the IDS from the VMS DOS prompt. I have done everything possible to change this condition but none has so far worked.
    any thoughts???
    Thx,
    Masood

    Connection states for RDEP devices are written into a table in the database by the receiver collector object. This means that if the receiver thread hangs or is not currently running, whatever state was last written to the table will be displayed.
    "Paused" means that the collector for this device is waiting for the system to clear a large backload of data that is waiting to be inserted into the database. This can occur if the rate of flow of events temporarily overwhelms the receiver and usually indicates that the database has grown too large (more than 2 million IDS or Syslog events) or the system is very busy (servicing event viewer, generating reports, pruning, etc.). It usually takes several minutes (fifteen or more) for the system to recover to the point where it can begin collecting events again.
    What sounds like happened here was that the sensors were offline, or at least were not getting events from the MC for a period. Then when you reconnected it the events began to be processed by the receiver process which in turn caused the 'paused' state. As I mentioned above, once it catches up with event processing you should be ok. Of course you'll want to ensure that you regularly prune your IDSMC/SecMon database to prevent this from happening again.
    You may also want to look at see how much you're logging. You may still need to tune your signatures down as well and you should not have every signature enabled.
    You should also look to upgrade your IDS/IPS software (you didn't mention what version you're on) to the latest service pack (4.1.5 for 4.x and 5.0.5 for 5.0.x)
    Thanks,
    Jeff

  • HA for Cisco IDS/IPS 42xx appliances

    Can anyone refer me to documentation on the Cisco site that talks about high-availability options and configuration examples for Cisco IDS/IPS 42xx appliances? Thank you in advance.

    I am also interested in understanding the high availability options.
    I found the following in the IPS V5 datasheet:
    Auto and manual sensor bypass configuration-High availability can be achieved through numerous mechanisms for Cisco IPS sensors. Resiliency and redundancy can be delivered through unique network collaboration, for example, hot Standby Router Protocol (HSRP) configuration and Cisco EtherChannel® load balancing on Cisco Catalyst switches to divert traffic to a secondary IPS device upon the failure of a primary device.
    I would like to have more info about how to divert traffic to a secondary IPS device; info about HSRP and EtherChannel load balancing as it relates to IPS. Is this HA option only available in bypass mode? Thanks.

  • MaxDB backup through Backint on Oracle for TSM

    Hello Gurus:
    We are using TSM backint interface for Oracle database. We are in the process of implementing SCM. We would like to schedule MaxDB backup through backint interface for Oracle.
    I checked some forums and configured but backint is not recognizing MaxDB parameter file. Please see below parameter file and error logs.
    *BSI File:*
    BACKINT D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe
    INPUT D:\sapdb\data\wrk\backint\sapdb.in
    OUTPUT D:\sapdb\data\wrk\backint\sapdb.out
    ERROROUTPUT D:\sapdb\data\wrk\backint\sapdb.err
    PARAMETERFILE D:\sapdb\data\wrk\LCD\maxdb_config.par
    ORIGINAL_RUNDIRECTORY L:\sapdb\LCD\sapdata
    *Parameter File - MaxDB_config*
    STAGING AREA:     D:\TEMP\STAGE1 1024000 KB
    FILES PER BACKINT CALL:     2
    BACKINT:     D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe
    PARAMETERFILE OF BACKINT:     D:\oracle\SCD\102\database\initSCD.utl
    HISTORY FILE:     D:\sapdb\data\wrk\BackintHistory
    INPUTFILE OF BACKINT:     D:\sapdb\data\wrk\backint\backint.in
    OUTPUTFILE OF BACKINT:     D:\sapdb\data\wrk\backint\backint.out
    ERRORFILE OF BACKINT:     D:\sapdb\data\wrk\backint\backint.err
    MAXIMAL DELAY OF BACKINT CALL:     30
    Error Logs:
    2010-03-30 17:38:35
    Using environment variable 'TEMP' with value 'C:\Windows\TEMP' as directory for temporary files and pipes.
    Using connection to Backint for MaxDB Interface.
    2010-03-30 17:38:35
    Checking existence and configuration of Backint for MaxDB.
        Using environment variable 'BSI_ENV' with value 'D:\sapdb\data\wrk\LCD\bsi.env' as path of the configuration file of Backint for MaxDB.
        Reading the Backint for MaxDB configuration file 'D:\sapdb\data\wrk\LCD\bsi.env'.
            Found keyword 'BACKINT' with value 'D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe'.
            Found keyword 'INPUT' with value 'D:\sapdb\data\wrk\backint\sapdb.in'.
            Found keyword 'OUTPUT' with value 'D:\sapdb\data\wrk\backint\sapdb.out'.
            Found keyword 'ERROROUTPUT' with value 'D:\sapdb\data\wrk\backint\sapdb.err'.
            Found keyword 'PARAMETERFILE' with value 'D:\sapdb\data\wrk\LCD\maxdb_config.par'.
            Found keyword 'ORIGINAL_RUNDIRECTORY' with value 'L:\sapdb\LCD\sapdata'.
        Finished reading of the Backint for MaxDB configuration file.
        Using 'D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe' as Backint for MaxDB program.
        Using 'D:\sapdb\data\wrk\backint\sapdb.in' as input file for Backint for MaxDB.
        Using 'D:\sapdb\data\wrk\backint\sapdb.out' as output file for Backint for MaxDB.
        Using 'D:\sapdb\data\wrk\backint\sapdb.err' as error output file for Backint for MaxDB.
        Using 'D:\sapdb\data\wrk\LCD\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 'L:\sapdb\LCD\sapdata\dbm.knl' as backup history of a database to migrate.
        Using 'L:\sapdb\LCD\sapdata\dbm.ebf' as external backup history of a database to migrate.
        Checking availability of backups using backint's inquire function.
    Check passed successful.
    2010-03-30 17:38:35
    Checking medium.
    Check passed successfully.
    2010-03-30 17:38:35
    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:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe -u LCD -f backup -t file -p D:\sapdb\data\wrk\LCD\maxdb_config.par -i D:\sapdb\data\wrk\backint\sapdb.in -c'.
        Created temporary file 'D:\sapdb\data\wrk\backint\sapdb.out' as output for Backint for MaxDB.
        Created temporary file 'D:\sapdb\data\wrk\backint\sapdb.err' as error output for Backint for MaxDB.
        Writing '
    .\pipe\BACKscd #PIPE' to the input file.
    Prepare passed successfully.
    2010-03-30 17:38:35
    Starting database action for the backup.
        Requesting 'SAVE DATA QUICK TO '
    .\pipe\BACKscd' PIPE BLOCKSIZE 8 NO CHECKPOINT MEDIANAME 'Back123'' from db-kernel.
    The database is working on the request.
    2010-03-30 17:38:35
    Waiting until database has prepared the backup.
        Asking for state of database.
        2010-03-30 17:38:35 Database is still preparing the backup.
        Waiting 1 second ... Done.
        Asking for state of database.
        2010-03-30 17:38:36 Database has finished preparation of the backup.
    The database has prepared the backup successfully.
    2010-03-30 17:38:36
    Starting Backint for MaxDB.
        Starting Backint for MaxDB process 'D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe -u LCD -f backup -t file -p D:\sapdb\data\wrk\LCD\maxdb_config.par -i D:\sapdb\data\wrk\backint\sapdb.in -c >>D:\sapdb\data\wrk\backint\sapdb.out 2>>D:\sapdb\data\wrk\backint\sapdb.err'.
        Process was started successfully.
    Backint for MaxDB has been started successfully.
    2010-03-30 17:38:36
    Waiting for end of the backup operation.
        2010-03-30 17:38:36 The backup tool process has finished work with return code 2.
        2010-03-30 17:38:36 The backup tool is not running.
        2010-03-30 17:38:36 The database is working on the request.
        2010-03-30 17:38:36 The database is working on the request.
        2010-03-30 17:38:41 The database is working on the request.
        2010-03-30 17:38:51 The database is working on the request.
        2010-03-30 17:39:06 The database is working on the request.
        2010-03-30 17:39:26 The database is working on the request.
        2010-03-30 17:39:37 Canceling Utility-task after a timeout of 60 seconds elapsed ... OK.
        2010-03-30 17:39:38 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.
    2010-03-30 17:39:38
    Filling reply buffer.
        Have encountered error -24920:
            The backup tool failed with 2 as sum of exit codes. The database request was canceled and ended 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 was canceled and ended with error -903.
    Reply buffer filled.
    2010-03-30 17:39:38
    Cleaning up.
        Copying output of Backint for MaxDB to this file.
        **-- Begin of output of Backint for MaxDB (D:\sapdb\data\wrk\backint\sapdb.out)--**
                                     **Data Protection for SAP(R)**
                         **Interface between BRTools and Tivoli Storage Manager***
                         **- Version 6, Release 1, Modification 0.0  for Win x64 -**
                               **Build: 358  compiled on Nov  4 2008**
                    **(c) Copyright IBM Corporation, 1996, 2008, All Rights Reserved.**
            **BKI8310E: The keyword MAXIMAL is not allowed.**
            **BKI1001E: syntax error in file 'D:\sapdb\data\wrk\LCD\maxdb_config.par'. Exiting program.**
            **BKI0020I: End of program at: 03/30/10 17:38:36 .**
            **BKI0021I: Elapsed time: 00 sec .**
            **BKI0024I: Return code is: 2.**       
    End of output of Backint for MaxDB (D:\sapdb\data\wrk\backint\sapdb.out)----
        Removed Backint for MaxDB's temporary output file 'D:\sapdb\data\wrk\backint\sapdb.out'.
        Copying error output of Backint for MaxDB to this file.
    Begin of error output of Backint for MaxDB (D:\sapdb\data\wrk\backint\sapdb.err)----
    End of error output of Backint for MaxDB (D:\sapdb\data\wrk\backint\sapdb.err)----
        Removed Backint for MaxDB's temporary error output file 'D:\sapdb\data\wrk\backint\sapdb.err'.
        Removed the Backint for MaxDB input file 'D:\sapdb\data\wrk\backint\sapdb.in'.
    Have finished clean up successfully.
    Any help will be appreciated.
    Thanks,
    Miral.

    > We are using TSM backint interface for Oracle database. We are in the process of implementing SCM. We would like to schedule MaxDB backup through backint interface for Oracle.
    > *BSI File:*
    >
    > BACKINT D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe
    > *Parameter File - MaxDB_config*
    > STAGING AREA:     D:\TEMP\STAGE1 1024000 KB
    > FILES PER BACKINT CALL:     2
    > BACKINT:     D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe
    >
    >     Using 'D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe' as Backint for MaxDB program.
    > 2010-03-30 17:39:38
    > Cleaning up.
    >     Copying output of Backint for MaxDB to this file.
    >                                  **Data Protection for SAP(R)**
    >                      **Interface between BRTools and Tivoli Storage Manager***
    >                      **- Version 6, Release 1, Modification 0.0  for Win x64 -**
    >         **BKI8310E: The keyword MAXIMAL is not allowed.**
    >         **BKI1001E: syntax error in file 'D:\sapdb\data\wrk\LCD\maxdb_config.par'. Exiting program.**
    >         **BKI0020I: End of program at: 03/30/10 17:38:36 .**
    >         **BKI0021I: Elapsed time: 00 sec .**
    >         **BKI0024I: Return code is: 2.**       
    >
    >     -
    End of output of Backint for MaxDB (D:\sapdb\data\wrk\backint\sapdb.out)----
    >     Removed Backint for MaxDB's temporary output file 'D:\sapdb\data\wrk\backint\sapdb.out'.
    >     Copying error output of Backint for MaxDB to this file.
    >     -
    Begin of error output of Backint for MaxDB (D:\sapdb\data\wrk\backint\sapdb.err)----
    @Markus: thanks for the hint with the quote-formatting option!
    Concerning the issue:
    Sorry, but you misunderstood the way how the general BACKINT for Oracle interface is used with MaxDB.
    See, MaxDB comes with a own BACKINT executable.
    This is a enhanced BACKINT tools that allows pipes as data input channels - which is not supported by the Backint for Oracle.
    The MaxDB Backint serves as a adapter program between the MaxDB Kernel and the backint for Oracle program.
    So instead of
    BACKINT:     D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe
    you should point it to the MaxDB provided adapater program.
    I propose to revisit the documentation on that topic [Connecting to a Backint for Oracle Interface |http://maxdb.sap.com/doc/7_7/45/746a5712e14022e10000000a1553f6/content.htm].
    best regards,
    Lars

  • Error while taking backup  through RMAN in 10g XE

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

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

  • Error while Backup through DB13

    Hi Experts.
    This is the first time when we are taking backup through DB13.
    I have inserted the Tape in the Tape drive and run the Online Full Backup. But an error was thrown as mentioned Below.
    Please also suggest me what are the changes which needs to be done on OS Level for the successful backup through DB13.
    Part of Error Message
    BR0280I BRBACKUP time stamp: 2010-09-09 18.01.59
    BR0057I Backup of database: JMD
    BR0058I BRBACKUP action ID: beebweva
    BR0059I BRBACKUP function ID: ant
    BR0110I Backup mode: ALL
    BR0077I Database file for backup: /oracle/JMD/sapbackup/cntrlJMD.dbf
    BR0061I 55 files found for backup, total size 109113.406 MB
    BR0143I Backup type: online
    BR0111I Files will be compressed
    BR0130I Backup device type: tape
    BR0102I Following backup device will be used: /dev/rmt/0mn
    BR0103I Following backup volume will be used: JMDB01
    BR0134I Unattended mode with 'force' active - no operator confirmation allowed
    BR0208I Volume with name JMDB01 required in device /dev/rmt/0mn
    BR0280I BRBACKUP time stamp: 2010-09-09 18.01.59
    BR0226I Rewinding tape volume in device /dev/rmt/0m ...
    BR0351I Restoring /oracle/JMD/sapbackup/.tape.hdr0
    BR0355I from /dev/rmt/0mn ...
    BR0278E Command output of 'LANG=C cd /oracle/JMD/sapbackup && /usr/sap/JMD/SYS/exe/run/brtools -f detach LANG=C cpio -iuvB .tape.hdr0 < /dev/rmt/0mn':          -
    error
    Can't open /dev/tty to prompt for more media.
    BR0280I BRBACKUP time stamp: 2010-09-09 18.01.59
    BR0279E Return code from 'LANG=C cd /oracle/JMD/sapbackup && /usr/sap/JMD/SYS/exe/run/brtools -f detach LANG=C cpio -iuvB .tape.hdr0 < /dev/rmt/0mn': 2
    BR0359E Restore of /oracle/JMD/sapbackup/.tape.hdr0 from /dev/rmt/0mn failed due to previous errors
    BR0218E Checking label on volume in device /dev/rmt/0mn failed         -
    error
    BR0236I Perhaps volume initialization with option '-i force' required
    BR0056I End of database backup: beebweva.ant 2010-09-09 18.01.59
    BR0280I BRBACKUP time stamp: 2010-09-09 18.01.59
    BR0054I BRBACKUP terminated with errors
    Kindly Suggest.

    Hi Anil,
    Thanks for your help. I did as you Said and it also proceeded a Bit Far...
    Now I Get A different set of Error. Please Give your Valuable Suggestions.
    BR0280I BRBACKUP time stamp: 2010-09-10 15.04.09
    BR0057I Backup of database: JMD
    BR0058I BRBACKUP action ID: beecamwa
    BR0059I BRBACKUP function ID: ant
    BR0110I Backup mode: ALL
    BR0077I Database file for backup: /oracle/JMD/sapbackup/cntrlJMD.dbf
    BR0061I 55 files found for backup, total size 109113.406 MB
    BR0143I Backup type: online
    BR0111I Files will be compressed
    BR0130I Backup device type: tape
    BR0102I Following backup device will be used: /dev/rmt/0mn
    BR0103I Following backup volume will be used: JMDB01
    BR0134I Unattended mode with 'force' active - no operator confirmation allowed
    BR0208I Volume with name JMDB01 required in device /dev/rmt/0mn
    BR0280I BRBACKUP time stamp: 2010-09-10 15.04.09
    BR0226I Rewinding tape volume in device /dev/rmt/0m ...
    BR0351I Restoring /oracle/JMD/sapbackup/.tape.hdr0
    BR0355I from /dev/rmt/0mn ...
    BR0241I Checking label on volume in device /dev/rmt/0mn
    BR0280I BRBACKUP time stamp: 2010-09-10 15.04.10
    BR0226I Rewinding tape volume in device /dev/rmt/0m ...
    BR0202I Saving /oracle/JMD/sapbackup/.tape.hdr0
    BR0203I to /dev/rmt/0mn ...
    BR0209I Volume in device /dev/rmt/0mn has name JMDB01
    BR0202I Saving init_ora
    BR0203I to /dev/rmt/0mn ...
    BR0202I Saving /oracle/JMD/102_64/dbs/initJMD.sap
    BR0203I to /dev/rmt/0mn ...
    BR0280I BRBACKUP time stamp: 2010-09-10 15.04.36
    BR0198I Profiles saved successfully
    BR0280I BRBACKUP time stamp: 2010-09-10 15.04.38
    BR0315I 'Alter tablespace PSAPSR3 begin backup' successful
    BR0201I Compressing /oracle/JMD/sapdata1/sr3_1/sr3.data1
    BR0203I to /sapinstcd/sr3.data1.Z ...                          -
    error
    BR0278E Command output of 'LANG=C compress -c /oracle/JMD/sapdata1/sr3_1/sr3.data1 > /sapinstcd/sr3.data1.Z':
    sh: /sapinstcd/sr3.data1.Z: Cannot create the specified file.
    BR0280I BRBACKUP time stamp: 2010-09-10 15.04.38
    BR0279E Return code from 'LANG=C compress -c /oracle/JMD/sapdata1/sr3_1/sr3.data1 > /sapinstcd/sr3.data1.Z': 1
    BR0224E Compressing /oracle/JMD/sapdata1/sr3_1/sr3.data1 to /sapinstcd/sr3.data1.Z failed due to previous errors -
    error
    BR0280I BRBACKUP time stamp: 2010-09-10 15.04.42
    BR0317I 'Alter tablespace PSAPSR3 end backup' successful
    BR0056I End of database backup: beecamwa.ant 2010-09-10 15.04.38
    BR0280I BRBACKUP time stamp: 2010-09-10 15.04.42
    BR0054I BRBACKUP terminated with errors
    Thanks Again.  Waiting for your Reply.

  • 10g Physical Standby to be used for Backup through RMAN

    Dear All,
    I have 10g Database Primary and Standby Server which is operating in Maximum Performance Mode. I want to use Standby Database for performing Weekly Full and Daily Incremental Backups through RMAN. Kindly inform me is it possible, if yes how should I configure it. I will also be using Compression and Encryption while performing backups.
    Best Regards,
    Asif

    Yes, that is possible.
    Because the standby databases are in mount mode, they can be accessed through the SYS account .
    I use the following RMAN script for the same purpose. Please note that we have configure the flashback area, so we are not letting RMAN delete the archive files:
    run {
    sql 'alter system archive log current';
    sql 'alter system archive log current';
    allocate channel ch1 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
    backup
    incremental level 0
    tag full_bk_db_webshop
    format 'df_%d_t%t_s%s_p%p'
    (database include current controlfile);
    backup archivelog all;
    This script is for a FULL backup ( level 0 ). You could also use the "backup full" command
    You can easily change the level of the Backup for incremental purposes.
    Starting RMAN - if configured correctly - is the same as with an open database
    export ORACLE_SID=<STDBYSID>
    rman target / rcvcat <rman/rman>@<catalogsid>
    the user for, and the catalogsid are merely examples
    Edited by: fjfranken on Mar 24, 2009 4:07 AM

  • Unable to reset password of user through IDM UI (IDM 7.1)

    Hello,
    We are unable to reset password of users in SAP Backend System through IDM UI.
    The moment we enter new password and submit, we are getting below dump.
    Any idea???
    java.lang.NullPointerException
    at com.sap.idm.wd.wf.task.TaskCompView.onActionSave(TaskCompView.java:172)
    at com.sap.idm.wd.wf.task.wdp.InternalTaskCompView.wdInvokeEventHandler(InternalTaskCompView.java:223)
    at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
    at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
    at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
    at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:333)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    Thanks
    Aditi

    Hello Aditi,
    In AS Java 7.1 and higher you go to short link /nwa and navigate
    to Configuration -> Infrastructure -> Java System Properties – Switch to
    application tab in second section (Details about <InstanceName>) ->
    search for tc~idm~jmx~app.
    For 7.0 you have to do that in Visual Admin but I would need to read docu to know where it is too.
    But you can find that all in UI installation guide http://service.sap.com/~sapidb/011000358700001233082010E
    Regards
    Norman

  • ISE Config Backup Failure - Data filesystem full above threshold

    Hi,
    Both the config and operational backups were working until earlier last month. Now the config backup is failing with the following error. No configuration or repository settings were changed.
    ISE 1.2.0.899 Patch 8 - Clustered with persona Node 1 = PAN, SMN, PSN .... Node 2 = SAN, PMN, PSN
    CLI history says the same:
    The local repository (disk:/) is looking good. The "/" filesystem is taking 77% space.
    Although it may not be relevant. Data Purging is set to 30 days in the GUI and Operations -> Reports -> Data Purging Audit indicates its running daily with success i.e. threshold_space = 80GB, used_space = 3GB.
    Is there a way to clean "/" filesystem ? It is filling up by roughly 1% every 5 days ? Note: the same on Node 2 is only 24% full.
    Any ideas on how to get the config backup issue resolved ?
    P.S. If images don't appear inline, please see the attachment
    Thanks,
    Rick.

    922963 wrote:
    Hi JK,
    Thanks for response. Yes, I am worried that it may not be enough. How about if I increase memory to 32GB, ie. I have two servers, both with 32GB? Will it be sufficient in case of one physical server fail for 8GB data?
    What is the point in having the 3rd physical box if two boxes have enough memory/capacity? You know, we need to pay licence according to no of CPU.
    thanks,
    HenryHi Henry,
    actually the recommended minimum number of physical boxes is 4 so that the witness protocol participants can all be on separate machines.
    But a minimum of 3 is highly recommended for a number of reasons related to partitioning:
    1. If you have only 2, then you are much more vulnerable to split brain scenarios (should for some reason the two servers not be able to communicate with each other, it is harder to decide which half should be the winner). In short how do you decide which box is unable to communicate with the rest of the cluster if there are only 2 boxes?
    2. You can't ensure a balanced and also machine safe partition distribution if you have a mismatching number of nodes on only 2 boxes. It would either be balanced or machine safe, but you can't get both at the same time. And you will either have mismatching number of nodes at startup or have mismatching number of nodes after one node failure.
    Best regards,
    Robert

  • SQL Injection detection with IDS/IPS on cisco ASA?

    Hi
    Is it possible to detect or prevent SQL injection attacks using Cisco IDS/ IPS on ASA or with regular expressions?
    Is there any signature available in IDS/IPS for this? And how effective it is in terms of generating correct alarms?
    Thanks in advance

    Deepak,
    We have several signatures that detect generic SQL injection attacks in the 5930-x family of signatures.

  • Reinstalling OSX: Will Time Machine read previous backup through interface?

    Or will I only see backup through Finder?

    Provided you are simply reinstalling Leopard on the same hardware and nothing else is changing (particularly your computer name in the sharing preference pane), Time Machine should be unaffected.

  • Backup through RMAN

    Hi guys.
    I am new in oracle database.my database is in no archive mode
    i want to take backup through RMAN .
    rman target sys/oracle
    backup database;
    but fail to backup. please see error
    ORA -19602: cannot backup or copy active file in noarchivelog mode

    Enable archiving in 10g
    1. shutdown immediate;
    2. edit init.ora set log_archive_start=TRUE /*Set this if your database is 9i. If 10g DB then ignore this step*/
    3. startup mount;
    4. alter database archivelog;
    5. alter database flashback on; /*Not required to enable archiving. Just extra info to enable flashback logs*/
    6. alter database open;
    7. archive log list;
    Now take backup
    run
    allocate channel ch1 type disk format '%D_%d_%t_%T_%s.bak';
    backup database plus archivelog;
    report obsolete;
    delete noprompt obsolete;
    crosscheck backupset;
    crosscheck archivelog all;
    resync catalog;
    Sami Malik
    [email protected]

  • Backup through brtools

    Hi,
      Iam unable to login the system.my ora arch directory is full,i know how to take backup through db13.
    iam unaware of how to take the back up through brtools.how to solve this problem.os is aix and db is oracle. guide me for same to solve problem.
    Thanku

    Hi Harshit,
    Do the following to take archive log backup:-
    On WIndows:-
    Step 1:- Login with SIDadm
    Step 2:- Open CMD prompt and use brtools command
    Step 3:- It will open Brtools screen
    Step 4:- Select option 4 backup and database copy
    Step 5:- Next select 2 Archivelog backup
    Step 6:- Then continue , continue and continue it will start archivelog backup.
    On Unix:-
    Step 1:- login with Ora<SID> user
    Step 2:- Brtools
    Step 3:- It will open Brtools screen
    Step 4:- Select option 4 backup and database copy
    Step 5:- Next select 2 Archivelog backup
    Step 6:- Then continue , continue and continue it will start archivelog backup.
    OR
    you can use the following command
    brarchive -c -sd -u
    Best luck
    Atil

Maybe you are looking for