Backup configuration with LD417

Hi,
I have an old Local Directory i'm trying to configure in ACTIVE / STANDBY using the backup command with two real servers. So i have configured the virtual address to map to one real server and then configure the 2nd real server as a backup of the first but it doesn't seem to work. I can access the real server bound to the virtual address, but when i shut down the switchport connecting to the 1st real server i don't get any connectivity to the 2nd.
virtual 89.21.18.13:0:0:tcp is
real 89.21.18.11:0:0:tcp is
real 89.21.18.10:0:0:tcp is
backup 89.21.18.11:0:0:tcp 89.21.18.10:0:0:tcp
name 89.21.18.11 server2
name 89.21.18.10 server1
bind 89.21.18.13:0:0:tcp 89.21.18.11:0:0:tcp
LB01(config)# show bind
Virtual Machine(s) Real Machines/Urls
89.21.18.13:0:0:tcp(IS)
server2:0:0:tcp(IS)
LB01(config)# show bac
Real Machine(s) Backup
server2:0:0:tcp server1:0:0:tcp
Virtual Machine(s) Backup
Litmus_LB01(config)#
If anyone can offer some guidance i'd be grateful.
Rgds
Paddy

Your mention of system context gave the clue.
Backup and restore from ASDM is only available when the firewall is running in single context mode. Reference.

Similar Messages

Cisco Prime: Restore Backup-Configuration

Hi,
how can I restore a backup-configuration with cisco prime on a cisco-router through TFTP?
Is there a way to say cisco prime: logon the router through ssh and then run comand copy tftp:... ?
Thanks for your help!
Cu, Marco

Marco,
In PI you use Templates to be pushed on devices as configurations.
For more details check the following document for Overview of device configurations from PI.
-Thanks
Vinod

LMS 3.2 with RME 4.3.1 backup configuration problem

Hi,
I am faing some problems in backing up devices in the network where it shows errors.
i am trying the to backup configuration for switches
1- WS-C2960-24PC-L with an ip 10.10.x.1 (10.10.11.1, 10.10.12.1, 10.10.14.1,,,,,,,,,,,,,) but it is giving me errors, sometimes it gives:
*** Device Details for 10.10.12.1 ***
Protocol ==> Unknown / Not Applicable
Selected Protocols with order ==> Telnet,TFTP,SSH,RCP,HTTPS
Execution Result:
Unable to get results of job execution for device. Retry the job after increasing
the job result wait time using the option:
Resource Manager Essentials -> Admin -> Config Mgmt -> Archive Mgmt ->Fetch Settings
i have tried to change the fetch setting but it keeps on changing it to default setting.
and another time this output
CM0151 PRIMARY STARTUP Config fetch failed for 10.10.14.1 Cause: TELNET:
Failed to establish TELNET connection to 10.10.14.1 - Cause: Authentication failed on device 3 times.
PRIMARY-STARTUP config Fetch Operation failed for TFTP.
Could not detect SSH protocols running on the device
Failed to fetch config using RCP.Verify RCP is enabled or not.
Action: Check if protocol is supported by device and required device package
is installed. Check device credentials. Increase timeout value, if required.
2- WS-C3560V2-24PS with an ip 10.10.x.2 (10.10.11.2 ,,,,,,) with error that i have to check the dcmaservice.log
3- WS-C2960-48PST-L with an ip 10.0.0.100 with error that i have to check the dcmaservice.log
Note: the switches 3560v2 and 2960-48PST-L are showing as unknown in the DFM although i updated the DFM with the patch
Please find the attach the dcmaservice.log , i was not able to analyz it
Please i appreciate some help.
Regards,
George

Without debugging, it's impossible to say exactly why things are failing. However, based on the errors, I would double-check the DCR credentials for these devices and make absolutely sure you can connect to them using the DCR credentials from the LMS server. You can confirm this by exporting the records for these devices from Common Services > Device and Credentials > Device Management. If SSH should be the protocol that works, also try telneting to the device from the LMS server on TCP port 22. You will get an SSH version string back. Make sure it is one of 1.5, 1.99, or 2.0.
The timeout problem could be symptomatic of another bug. Restarting ConfigMgmtServer (pdterm ConfigMgmtServer/pdexec ConfigMgmtServer) may help. The fact that the job timeout resets to the default means there is a problem with your regdaemon.xml file. If you post this file, I can fix it for you.

Backup rserver with sticky configured

Hi,
I would like to ask regarding the configuration for the backup rserver with sticky configured.
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin:0cm;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:SimSun;
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
This is not documented in the Cisco guides.
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin:0cm;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:SimSun;
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
Suppose the real server1 fails and connections are diverted to server2. Then server1 resumes service. What happens to existing connections on server2 and the new connections?
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin:0cm;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:SimSun;
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
serverfarm SFARM1
rserver SERVER1
backup-rserver SERVER2
inservice
rserver SERVER2
inservice standby

- Existing connections keep accessing server2.
- If a new client request (connection) matches a sticky entry for server2, ACE forwards this request to server2.
ACE looks up sticky entries and use server2 since standby state is handled as UP.
http://www.cisco.com/en/US/docs/interfaces_modules/services_modules/ace/vA2_3_0/configuration/slb/guide/rsfarms.html#wp1000385
- If a new client request (connection) doesn't match any sticky entry for server2, ACE forwards this request to server1.
If you want to use server1 after coming back OPERATIONAL, I recommend you use 'backup serverfarm' without sticky option as below.
http://www.cisco.com/en/US/docs/interfaces_modules/services_modules/ace/vA2_3_0/configuration/slb/guide/sticky.html#wp1137791
serverfarm SFARM1
rserver SERVER1
inservice
serverfarm SFARM2
rserver SERVER2
inservice
sticky ip-netmask 255.255.255.255 address both sticky_ip
serverfarm SFARM1 backup SFARM2
The following is a test result of standby rserver and sticky ip.
ACE20a/Admin# sh rserver
rserver              : sv1, type: HOST
state                : OPERATIONAL (verified by arp response)
                                                ----------connections-----------
       real                  weight state        current    total
   ---+---------------------+------+------------+----------+--------------------
   serverfarm: sf
       192.168.72.11:0       8      PROBE-FAILED 0          2
rserver              : sv2, type: HOST
state                : OPERATIONAL (verified by arp response)
                                                ----------connections-----------
       real                  weight state        current    total
   ---+---------------------+------+------------+----------+--------------------
   serverfarm: sf
       192.168.72.12:0       8      OPERATIONAL 0          8
ACE20a/Admin#
!___ access from client to ACE vip
ACE20a/Admin# sh sticky database
sticky group : sticky_ip
type         : IP
timeout      : 1440          timeout-activeconns : FALSE
sticky-entry          rserver-instance                 time-to-expire flags
---------------------+--------------------------------+--------------+-------+
13882423967172020068 sv2:0                            86384          -
!___ ACE learns client address and registers the entry
ACE20a/Admin#
ACE20a/Admin# sh rserver
rserver              : sv1, type: HOST
state                : OPERATIONAL (verified by arp response)
                                                ----------connections-----------
       real                  weight state        current    total
   ---+---------------------+------+------------+----------+--------------------
   serverfarm: sf
       192.168.72.11:0       8      OPERATIONAL 0          2
!___ return OPERATIONAL
rserver              : sv2, type: HOST
state                : OPERATIONAL (verified by arp response)
                                                ----------connections-----------
       real                  weight state        current    total
   ---+---------------------+------+------------+----------+--------------------
   serverfarm: sf
       192.168.72.12:0       8      STANDBY      0          9
!___ return STANDBY
ACE20a/Admin# sh sticky database
sticky group : sticky_ip
type         : IP
timeout      : 1440          timeout-activeconns : FALSE
sticky-entry          rserver-instance                 time-to-expire flags
---------------------+--------------------------------+--------------+-------+
13882423967172020068 sv2:0                            86356          -
!___ ACE keeps sticky entry to server2.
ACE20a/Admin#
!___ access from client with new syn packet
ACE20a/Admin# sh sticky database
sticky group : sticky_ip
type         : IP
timeout      : 1440          timeout-activeconns : FALSE
sticky-entry          rserver-instance                 time-to-expire flags
---------------------+--------------------------------+--------------+-------+
13882423967172020068 sv2:0                            86389          -
!___ use this sticky entry (time-to-expire flag is reset) and send packets to server2
ACE20a/Admin#
ACE20a/Admin# sh ver | i image
system image file: [LCP] disk0:c6ace-t1k9-mz.A2_3_1.bin

HT5927 Using apple configurator with supervised devises, enabling iCloud/ find my iOS device (after being supervised), backing up that supervised / find my iPhone enabled image, --issue; unable to apply back up to any iOS device (including the orign. devi

Senario:
Need to manage 500 Enterprise iPads
Requirements;
1) Trackable via Find my iOS device (we have 500 iPads and with the 100 device limit per iCloud account for Find my iOS device limit we have 5+ iCloud accounts).
2) Individually named iPads for locating and sending commands to wipe, lost mode, etc.. on map per Find my iOS device (we uniquely name them in Apple Configurator either by using the "sequensetially numbering feature", or by creating individual back ups (yes, 450) with the name specified in the image).
3) Find my iOS device feature enabled in base Prepared or Supervised image (using one of our 5+ iCloud accounts) (image can be created during prepared stage, or in supervised stage) - tried both and have the same issue - which I am getting to...
4) VPP codes for paid apps (all VPP codes purchased with generic account which is the Apple Admin account for VPP purchases). Apple Configurator is set up under a different/ unique Apple account (i.e. not VPP admin account) and not logged into iTunes for any purchases/ services).
Issue: Can not do any following senarios;
A)
1) configure master iOS 7 iPad with iCloud account with Find my iOS feature enabled in Prepare stage (added during preparing stage)
2) configure master iOS 7 iPad with iCloud account with Find my iOS feature enabled in Supervised stage (added after supervising, and then backing up that supervised and iOS Find my iOS device enabled)
B) 1) Apply master image to any Supervised iPad (under senario step A) or senario step B)), including the (Supervised or/ Prepared iPad that was used to create the maset iOS 7 image
Result = fail with Apple generic code "4" ; This is obviously due to Find my iOS device feature enabled during image capture.
According to Apple (see Apple Config. Help) the 'Activation lock' (new feature in iOS 7) will not be enabled on a supervised device when an iCloud account with "Find my iDevice" is enabled. Their "help files" seem to imply after the device is Supervised, and a person (presumably and end user) adds thier own iCloud account with Find my iOS device enabled the activation lock is not enabled and erasing/ reconfiguring with Apple Configurator will not cause reimaging probhlems such as requiring the end user's credentials to reconfigure the device using Apple Configurator (i.e. you won't need the end user's credentials).
Needed: To be able to configure Supervised iPads with iCloud account (Enterprised owned iCloud account) configured on the basse image, which has Find my iOS device enabled, and to be able to apply that base image to all Enterprise iPads without generic apple error code 4 issue.

Hi all
I am trying to replicate these steps in my environment but I am having trouble getting an iCloud backup restored to a supervised device. Can someone clarify the steps? The parts I am unsure on are:
1) Do you Prepare in Configurator with all the institution owned apps? Or do you install them after restoring the iCloud backup?
2) After entering the personal AppleID to restore the iCloud backup, the setup wizard prompts for the Institution/Configurator AppleID, there is an option to 'Skip Now'. Do you enter in the password for the institution account? or do you skip that step?
3) What exactly is on the screen in the 'mini setup assistant' after the restore when you Refresh with Configurator?
Any help would be greatly appreciated!

Backup fail with VSSwriter error

Hello,
we currently are using Symantec Backup on tape and Windows Server Backup to make two differents backups on a SBS 2008.
We are getting failed backup randomly during the week for both. Sometimes one is succeed and not the others.
We have found several post about the VSS issues and how to fix it but nothing has changed.
What we have done:
- check the VSS writer and all is in "no error" state
- check the settings of the backups
- restart the VSS services
- Configure the Shadow Copy on the drives
- reboot the server
- Tried several solutions from forums
What we can see in the event viewer
ID 12289
"Volume Shadow Copy Service error: Unexpected error VSS_E_WRITER_STATUS_NOT_AVAILABLE. An older active writer session state is being overwritten by a newer session. The most common cause is that the number of parallel backups has exceeded the maximum
supported limit. hr = 0x80042409.
Operation:
Aborting Writer
ID 7001
VssAdmin: Unable to create a shadow copy: The shadow copy provider had an error. Please see the system and application event logs for more information.
Command-line: 'C:\Windows\system32\vssadmin.exe Create Shadow /AutoRetry=15 /For=C:\'. "
ID 12341
Volume Shadow Copy Warning: VSS spent 75 seconds trying to flush and hold the volume \\?\Volume{c22d5d46-0540-11e0-9496-806e6f6e6963}\. This might cause problems when other volumes in the shadow-copy set timeout waiting for the release-writes phase,
and it can cause the shadow-copy creation to fail. Trying again when disk activity is lower may solve this problem.
Operation:
Executing Asynchronous Operation
Context:
Current State: flush-and-hold writes
Volume Name: \\?\Volume{c22d5d46-0540-11e0-9496-806e6f6e6963}\"
Some will post the link of "how to troubleshoot VSSwriter issue": we have already used it.
Does someone have a fresh idea about this issue ?
Thanks in advance

Hi Nerea,
Before going further, would you please let me confirm if temporarily disable either of the two backup, will
another backup operation run smoothly? In other words, if temporarily disable Symantec Backup, will Windows Server Backup always run successfully? Or if disable Windows Server Backup, will Symantec Backup always run successfully? Please check if Windows Server
Backup conflicts with Symantec Backup.
Based on the error message, please run
chkdsk command and check if there is any issue in the disk. Then use
Vssadmin resize shadowstorage to resizes the maximum amount of storage space that can be used for shadow copy storage. And check if this issue still persists.
In addition, would you please let me know whether re-register Volume VSS components? If this issue still persists,
please re-register and monitor the result.
From command prompt:
cd windows\system32
Net stop vss
Net stop swprv
regsvr32 ole32.dll
regsvr32 vss_ps.dll
Vssvc /Register
regsvr32 /i swprv.dll
regsvr32 /i eventcls.dll
regsvr32 es.dll
regsvr32 stdprov.dll
regsvr32 vssui.dll
regsvr32 msxml.dll
regsvr32 msxml3.dll
regsvr32 msxml4.dll
net start swprv
net start vss
By the way, did the Symantec Backup and Windows Server Backup run at the same time? Or before one backup finished,
had another backup started?
Hope this helps.
Best regards,
Justin Gu

Backup Fails with Invalid RECID Error

Hi All,
Please help me to understand Caution -section
below text is from
[http://download.oracle.com/docs/cd/B10501_01/server.920/a96566/rcmtroub.htm#447765]
Backup Fails with Invalid RECID Error: Solution 2
This solution is more difficult than solution 1:
To create the control file with SQL*Plus:
   1. Connect to the target database with SQL*Plus. For example, enter:
      % sqlplus 'SYS/oracle@trgt AS SYSDBA'
   2. Mount the database if it is not already mounted:
      SQL> ALTER DATABASE MOUNT;
   3. Back up the control file to a trace file:
      SQL> ALTER DATABASE BACKUP CONTROLFILE TO TRACE;
   4. Edit the trace file as necessary. The relevant section of the trace file looks something like the following:
      # The following commands will create a new control file and use it
      # to open the database.
      # Data used by the recovery manager will be lost. Additional logs may
      # be required for media recovery of offline data files. Use this
      # only if the current version of all online logs are available.
      STARTUP NOMOUNT
      CREATE CONTROLFILE REUSE DATABASE "TRGT" NORESETLOGS ARCHIVELOG
      -- STANDBY DATABASE CLUSTER CONSISTENT AND UNPROTECTED
          MAXLOGFILES 32
          MAXLOGMEMBERS 2
          MAXDATAFILES 32
          MAXINSTANCES 1
          MAXLOGHISTORY 226
      LOGFILE
        GROUP 1 '/oracle/oradata/trgt/redo01.log' SIZE 25M,
        GROUP 2 '/oracle/oradata/trgt/redo02.log' SIZE 25M,
        GROUP 3 '/oracle/oradata/trgt/redo03.log' SIZE 500K
      -- STANDBY LOGFILE
      DATAFILE
        '/oracle/oradata/trgt/system01.dbf',
        '/oracle/oradata/trgt/undotbs01.dbf',
        '/oracle/oradata/trgt/cwmlite01.dbf',
        '/oracle/oradata/trgt/drsys01.dbf',
        '/oracle/oradata/trgt/example01.dbf',
        '/oracle/oradata/trgt/indx01.dbf',
        '/oracle/oradata/trgt/tools01.dbf',
        '/oracle/oradata/trgt/users01.dbf'
      CHARACTER SET WE8DEC
      # Take files offline to match current control file.
      ALTER DATABASE DATAFILE '/oracle/oradata/trgt/tools01.dbf' OFFLINE;
      ALTER DATABASE DATAFILE '/oracle/oradata/trgt/users01.dbf' OFFLINE;
      # Configure RMAN configuration record 1
      VARIABLE RECNO NUMBER;
      EXECUTE :RECNO := SYS.DBMS_BACKUP_RESTORE.SETCONFIG('CHANNEL','DEVICE TYPE DISK
      DEBUG 255');
      # Recovery is required if any of the datafiles are restored backups,
      # or if the last shutdown was not normal or immediate.
      RECOVER DATABASE
      # All logs need archiving and a log switch is needed.
      ALTER SYSTEM ARCHIVE LOG ALL;
      # Database can now be opened normally.
      ALTER DATABASE OPEN;
      # Commands to add tempfiles to temporary tablespaces.
      # Online tempfiles have complete space information.
      # Other tempfiles may require adjustment.
      ALTER TABLESPACE TEMP ADD TEMPFILE '/oracle/oradata/trgt/temp01.dbf' REUSE;
      # End of tempfile additions.
   5. Shut down the database:
      SHUTDOWN IMMEDIATE
   6. Execute the script to create the control file, recover (if necessary), archive the logs, and open the database:
      STARTUP NOMOUNT
      CREATE CONTROLFILE ...;
      EXECUTE ...;
      RECOVER DATABASE
      ALTER SYSTEM ARCHIVE LOG CURRENT;
      ALTER DATABASE OPEN ...;
Caution:
      If you do not open with the RESETLOGS option,
then two copies of an archived redo log for a given log sequence number may
exist--even though these two copies have completely different contents.
For example, one log may have been created on the original host and the other on the new host.
If you accidentally confuse the logs during a media recovery,
then the database will be corrupted but Oracle and RMAN cannot detect the problem.

Please help me to understand Caution -section
Caution:
If you do not open with the RESETLOGS option,
then two copies of an archived redo log for a given log sequence number may
exist--even though these two copies have completely different contents.
For example, one log may have been created on the original host and the other on the new host.
If you accidentally confuse the logs during a media recovery,
then the database will be corrupted but Oracle and RMAN cannot detect the problem.As per my understanding it says. If you don't open database with RESETLOGS option then there may be archived logs with log sequence number which is already archived on the source host. This may happen due to difference in RECIDs. Now when the database needs media recovery for this particular log sequence, you may provide any of them. So in this case, RMAN and Oracle will not be able to differentiate the two files and can accept any of the archived log files during recovery. Since the contents of two archived logs are different, because they are generated at different times and they contains different transactions. So, internally it corrupts your database.
Rgds.

I am trying to use apple configurator with ipads. I have been successful with all our ipads but 1. It will not allow me to add apps. The error I get is that it is refreshed but with errors e

I am trying to use apple configurator with ipads. I have been successful with preparing and supervising all ipads but one. When preparing it in configurator, I receive an error that it is refreshed but with an error. Under supervise, I am not able to add apps. I have erased all content to start over but this does not work either

Are you trying to restore a backup, or just sync some apps? Do you have profiles installed on the device?
Have you plugged the ipad into iTunes, and did a fresh install? I'm assuming the device went through the prepare setup properly. You many have to unsupervise it first, then plug it into iTunes to wipe it completely.
I'd then do each step seperately. Prepare it, then install 1 app, if that works, try another app, then maybe a profile.

CSS One Arm Configuration with VIP(non-shared)/IP Interface Redundancy

With Reference to the following CCO documentation;
1). "How to Configure the CSS to Load Balance Using 1 Interface"
In this example, the Real Server's (10.10.10.2 etc) gateway are pointed to the router's gateway(10.10.10.1) and used the 'add destination service' command to NAT the RealServer's IP address back to the VIP (10.10.10.6).
2). "Understanding and Configuring VIP and Interface Redundancy on the CSS11000".
In the interface redundancy configuration, the gateway of the Real Server are configured as the CSS11000's Interface Redundancy Address (192.168.1.1), not the Router's gateway.
Can anyone help to advise on the preferred one arm configuration with VIP/IP redundancy?
(i). Is the reason for configuring the gateway of the Real Server to CSS11000's Interface Redundancy Address in 2) same as using 'add destination service' command in 1)? That is to make sure that the return path from Real Server back to Client passes through the CSS and is NAT back to the VIP.
(ii). To configure VIP(non-shared)/IP Interface redundancy(Active/Backup Mode) in a one arm configuration, my understanding is that there are 2 methods of configuration. Is it correct? Which method is preferred?
Method a)
1.Configure the Real Server's gateway to Router's Gateway
2.Configure 'add destination service' command on the CSS to NAT the RealServer's IP address back to the VIP
3.Configure VIP(non-shared) redundancy for the VIP on the CSS
4.IP Interface Redundancy on the CSS is not required as the Real Server's gateway is already pointing to the Router's gateway. (Assuming that HSRP redundancy is already running on the Router)
Method b)
1. Configure the Real Server's gateway to the CSS's IP Interface Redundancy IP Address
2. Configure IP Interface Redundancy on the CSS (as the Real Server's gateway)
3. Configure VIP(non-shared) redundancy for the VIP on the CSS

if you use method a) (server gateway is the router) you need the CSS to nat
the source ip address of the client in order to force the server to send traffic back to the CSS.
The issue then is that the server does not see the IP address of real client.
The server only see connections with source IP address = CSS ip address.
With method b) you don't have the above problem, but connection initiated by the servers are sent to the CSS that will then send it to the router.
You have a performance issue because the traffic will cross 2 times the one-armed interface.
If this is a new design, it is strongly recommended not to use one-armed setup.
Regards,
Gilles.

Backup Deletion with DB13?

Hey there,
I have planned some AllOnlineRedolog Backups to a disk. But there is only enough space for ONE Backup. So, after the Backup on the disk has been saved to a tape, it should be deleted. Not directly after the Tape-Backup but relatively before the new AllOnlineRedolog Backup.
Example:
01.01.2008 - 3:00am - AllOnline + RedoLog Backup (to Disk)
01.01.2008 - 8:00pm - Backup to Tape
08.01.2008 - 1:00am - Deletion of old Backup
08.01.2008 - 3:00am - AllOnline.... and so on.
Is this possible just with DB13? How could I realize this?
Thanks in advance!

Hi there,
If you are using the DB13 you probably are familiar with the profile file init<SID>.sap in that file you can configure the disk path if you didn't then the backups goes to the default path that is %SAP_DATA%\sapbackup. In the same file you can configure the retention period of that files and all the logs created during backup activities.
There is an activity pattern in the DB13 called Clean up logs, that pattern could be configured to delete old backup files.
We implement exactly the way you want, and in the init<SID>.sap located in %ORACLE_HOME%\database\ we set the parameters as follow:
retention period in days for archive log files saved on disk
default: 30
cleanup_disk_archive = 14
This means that offline readologs will be deleted if they are 14 days old
retention period in days for database files backed up on disk
default: 30
cleanup_disk_backup = 1
This means that all datafiles only will be available 1 day and at the next day when you run "Clean up logs" activity the previous backup will be deleted.
You can configure that for example the Clean up runs every day one our before the backup and with that you first delete the old backup and then you make a new one.
You can use the scheduler task if you want but if you use the DB13 you dont need to enter to you server every day to review the logs. We configure the scheduler task for our Portal because has no ABAP instance .
the instructions in the .bat file coul be "brconnect -u / -c force -p init<SID>.sap -f cleanup " and that is actually the pattern in DB13.
You can review the documentation of brconnect for more details.
http://help.sap.com/saphelp_sm40/helpdata/EN/50/7dd41742210144aee3fdee21c553eb/content.htm
Regards.
Gustavo Balboa

Why HTTP 404 Page not Found when trying to Backup Configuration?

Good day:
I bought this RV082 VPN Router. After configuring it, I tried to save its configuration using the System Management's Backup Utility. When I set everything up and ready to proceed, as I click on the Backup Configuration button, I get this Page Not Found error.
After several additional retries, and cold startup of my laptop, I still get this.
Then I wondered, "Why don't I try to upgrade the firmware instead?".
Guess what: I get the same page not found error.
Can anyone tell why is this? Using Windows 7 Pro 32-bit.
Thanks in advance!
Javier.
P.S. I have replied to another thread about not getting connected with Quick VPN to the RV082, which is another painful trouble I've got with it.

Hi Rybak,
Thanks for your reply.
Try to clean the Cache for TFS 2013 manually(delete the content of the folder only, not the cache folder itself):
Clean the Cache folder on Server machine. The folder path is:
C:\Program Files\Microsoft Team Foundation Server 12.0\Application Tier\Web Services\_tfs_data.
After cleaned, on Server machine, click Start and select
Run… to open the dialog box, then input iisreset.exe and click OK, wait it run completely.
If clean Cache cannot resolve this issue, please try to repair your TFS 2013 Update 4 Server, then check the result.
Additionally, you can run TFS 2013 Power Tools BPA to scan the installation of your TFS Server.
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.
Click
HERE to participate the survey.

JDBC Configuration with Multi Datasource

Hi all,
We're using Weblogic 9.2 and has configured Multi Datasource with Failover algorithm. All is working well, but our DBA has reported that some requests were randomly still going to the 2nd node although he was sure that nothing was wrong with the 1st node. Is this an expected behavior with the Failover algorithm.
Any help would be greatly appreciated.
Thanks & Regards,
Besetya

Some of the application-level work? I think you can configure an MDS to 'fail over' if the first pool is
simply at capacity and unable to deliver another connection. You can check that, and make sure the
first pool is big enough. Than, also configure the backup pool with an initial capacity of 0, so it
never even makes a connection unless the MDS fails over to it.

Backups failing with error 19: the backup disk could not be resolved, or there was a problem mounting it

Hello all,
Doubt this issue relates to a recent and ugly issue but sharing anyways (resolved thanks to a user here: LaPastenague)
Time Capsule won't backup if Modem (Motorola SB6121) attached
This was on Feb 10th resolved. Few days later I upgraded to Yosemite. Backups were working fine since.
Yesterday I happen to notice my last backup was 5 days ago. I looked in the console logs and saw:
2/25/15 3:55:06.127 PM com.apple.backupd[2777]: Attempting to mount network destination URL: afp://Paul;AUTH=SRP@Time%20Capsule._afpovertcp._tcp.local./Data
2/25/15 3:55:17.778 PM com.apple.backupd[2777]: NAConnectToServerSync failed with error: 2 (No such file or directory) for url: afp://Paul;AUTH=SRP@Time%20Capsule._afpovertcp._tcp.local./Data
2/25/15 3:55:17.792 PM com.apple.backupd[2777]: Backup failed with error 19: The backup disk could not be resolved, or there was a problem mounting it.
2/25/15 3:57:18.808 PM com.apple.prefs.backup.remoteservice[2021]: Attempt to use XPC with a MachService that has HideUntilCheckIn set. This will result in unpredictable behavior: com.apple.backupd.status.xpc
I called Apple. Their front line was clueless. He suggested resetting the TC (latest "tower" model btw") which then a backup kicked off YEAH
But the next hour it failed
Called Apple again, this time to Sr Advisor. He suggested factory reset of the TC and set up again. Also first backup worked then rest failed
Third call to Apple useless also. He was asking questions I didn't feel relevant. He also was asking me to reset the TC which I told him was done 2 hours prior. He asked me to reboot which I could NOT at that time.
I begged him to collect data to submit to engineering, which will take days to get a reply.
So I thought I would throw this out to the community....
TC Is NEW (replaced from last issue). Mac is 8 months old (iMac 27"), Os is Yosemite, TC also new (latest model)
Thanks...

Yosemite is problematic on two fronts.. Networking and Time Machine.. so the combo of doing both with a Time Capsule is like bugs on bugs.
Here is my standard list.. but your problem maybe difficult to resolve.. and my suggestion is simple.. until Apple get their act together and fix TM.. buy Carbon Copy Cloner and use that for your backup. It is solid and reliable.. even better if you use USB drive plugged into the computer and do a bootable clone.. because then you have a backup that is able to be tested for full functionality 2min after the end of the backup.
This also starts from a factory reset.. but the reason for it is to change the configuration which is much more easily handled with factory reset to begin.. the instructions are there.. because this is my standard reply.. this is not uncommon!!
Factory reset universal
Power off the TC.. ie pull the power cord or power off at the wall.. wait 10sec.. hold in the reset button.. be gentle.. power on again still holding in reset.. and keep holding it in for another 10sec. You may need some help as it is hard to both hold in reset and apply power. It will show success by rapidly blinking the front led. Release the reset.. and wait a couple of min for the TC to reset and come back with factory settings. If the front LED doesn’t blink rapidly you missed it and simply try again. The reset is fairly fragile in these.. press it so you feel it just click and no more.. I have seen people bend the lever or even break it. I use a toothpick as tool.
N.B. None of your files on the hard disk of the TC are deleted.. this simply clears out the router settings of the TC.
Setup the TC again.
ie Start from a factory reset. No files are lost on the hard disk doing this.
Then redo the setup from the computer with Yosemite.
1. Use very short names.. NOT APPLE RECOMMENDED names. No spaces and pure alphanumerics.
eg TCgen5 and TCwifi for basestation and wireless respectively.
Even better if the issue is more wireless use TC24ghz and TC5ghz with fixed channels as this also seems to help stop the nonsense. But this can be tried in the second round.
2. Use all passwords that also comply but can be a bit longer. ie 8-20 characters mixed case and numbers.. no non-alphanumerics.
3. Ensure the TC always takes the same IP address.. you will need to do this on the main router using dhcp reservation.. or a bit more complex setup using static IP in the TC. But this is important.. having IP drift all over the place when Yosemite cannot remember its own name for 5 min after a reboot makes for poor networking. If the TC is main router it will not be an issue.
4. Check your share name on the computer is not changing.. make sure it also complies with the above.. short no spaces and pure alphanumeric.. but this change will mess up your TM backup.. so be prepared to do a new full backup. Sorry.. keep this one for second round if you want to avoid a new backup.
5. Mount the TC disk in the computer manually.
In Finder, Go, Connect to server from the top menu,
Type in SMB://192.168.0.254 (or whatever the TC ip is which you have now made static. As a router by default it is 10.0.1.1 and I encourage people to stick with that unless you know what you are doing).
You can use name.. SMB://TCgen5.local where you replace TCgen5 with your TC name.. local is the default domain of the TC and doesn't change.
However names are not so easy as IP address.. nor as reliable. At least not in Yosemite they aren't. The domain can also be an issue if you are not plugged or wireless directly to the TC.
6. Make sure IPv6 is set to link-local only in the computer. For example wireless open the network preferences, wireless and advanced / TCP/IP.. and fix the IPv6. to link-local only.
There is a lot more jiggery pokery you can try but the above is a good start.. if you find it still unreliable.. don't be surprised.
You might need to do some more work on the Mac itself. eg Reset the PRAM.. has helped some people. Clean install of the OS is also helpful if you upgrade installed.
Tell us how you go.
Someone posted a solution.. See this thread.
Macbook can't find Time Capsule anymore
Start from the bottom and work up.. What I list here is good network practice changes but I have avoided Yosemites bug heaven.
This user has had success and a few others as well.
RáNdÓm GéÉzÁ
Yosemite has serious DNS bug in the networking application.. here is the lets say more arcane method of fixing it by doing a network transplant from mavericks.
http://arstechnica.com/apple/2015/01/why-dns-in-os-x-10-10-is-broken-and-what-yo u-can-do-to-fix-it/

Backup configuration missing from ASDM

Having a problem with an ASA5520 system in that Backup and Restore configuration option under the ASDM Tools menu is not displayed/available. Any ideas as to why this is? ASDM version supports it as far as I can see. Further details:
- ASDM/ASA versions of ASA5505 and ASA5520 system are:
ASDM Version 7.1(3)
ASA Version 9.1(2)
Java 1.7.0_45
- User logging in with is a Priv 15 user.
- Only when system context is selected, under the Tools menu "System Reload" is available along with File Management, Downgrade Software etc. but no Backup Configuration or Restore Configuration.
- If same ASDM client is used with ASA5505 instead of ASA5520, the Backup Configuration and Restore Configuration options display just below "Downgrade Software" and backup and restore work.
- If try to access ASDM via a different system with different version of Java etc. same problem.

Your mention of system context gave the clue.
Backup and restore from ASDM is only available when the firewall is running in single context mode. Reference.

Time Machine. Backup failed with error code: 21

Hi,
I recently upgraded to Leopard 10.5.4 mainly for the time machine backup. I'm using a DNS-323 in a RAID1 configuration as the TM backup drive. Also I have the DNS-323 connected to my Airport Extreme through the ethernet to give NAS ability to my home network.
After much hunting around the forums I got the sparsebundle created and copied to the DNS-323 share volume. See http://www.flokru.org/2008/02/29/time-machine-backups-on-network-shares-in-leopa rd/ My thanks to flokru.
However, TM is still not working. The console messages have the following:
Network mountpoint /Volume/Volume_1 not owned by backupd... remounting
Network volume mounted at /Volume/Volume11
Failed to mount disk image /Volume/Volume1_1/MacBook001b6334c307.sparebundle
Backup failed with error: 21
It would appear this error lies in the way TM is trying to mount the volume, specifically that Volume_1, the DNS-323 volume name, is not owned by TM. TM then tries to create a new volume, Volume11 and stick the sparebundle on it.
Is there a way of making TM "own" the volume, Volume_1?
Has anybody else seen this error or better yet, got a fix for it?

James,
It would appear this error lies in the way TM is trying to mount the volume, specifically that Volume_1, the DNS-323 volume name, is not owned by TM. TM then tries to create a new volume, Volume11 and stick the sparebundle on it.
Is there a way of making TM "own" the volume, Volume_1?
Actually, it is not TMs failure to mount the volume that is causing your failure to backup. I have received the same Console message using a Time Capsule. However, Time Machines' attempt to 'remount' the volume always succeeds and the backup goes through. That appears not to be your experience, but it is NOT because the volume is not being mounted. It is.
*Mount Point Conflict (TMDisk-1)*
NOTE: the following distinguishes “network drive” (the physical hard disk) from “disk image” (the sparsebundle file TM uses to backup to).
First of all, I am convinced that the second mount point that is created (in your case Volume11) is due to the fact that you already had the network drive mounted on your desktop at the time of the attempted backup. Was that the case?
When you manually mount a network drive the system creates a mount point in the /Volumes folder (Let’s call it TMDisk ). While that exists any attempt by Time Machine to mount the same disk will created a second mount point ( TMDisk-1 )
Nevertheless, as I have observed, this doesn't seem to prevent backups from taking place successfully, at least on the Time Capsule. And according to your Console logs it appears that your volume is being ‘remounted’ successfully.
*”The Backup Disk Image Could Not Be Mounted”*
The real issue is Time Machines' failure to mount the disk image (sparsebundle) contained on your network drive.
+Failed to mount disk image /Volume/Volume1_1/MacBook001b6334c307.sparebundle+
+Backup failed with error: 21+
More often than not this is due to having the Time Machine backup disk image (sparsebundle) mounted on your desktop during a backup attempt.
Eject the backup disk image (sparsebundle) by either clicking the little Eject icon to the right of the disk image in the Finders’ Sidebar, or Ctrl-Click the drive icon on the desktop and select “Eject” from the contextual menu. Now try backing up again or launching Time Machine to view previous backups.
For more information, see an article on this here:
[http://discussions.apple.com/thread.jspa?threadID=1715977]
Alternatively, a backup disk image can fail to mount if there is a problem with your computer name.
*Proper Computer Name* #
Make sure your computer has a proper name. Go to System Preferences --> Sharing. Time Machine needs to differentiate your computer from others on your network (i.e. "Bills MacBook" or "Office iMac"). If the "Computer Name" field is blank, create a name. Realize that if this step is necessary, you will likely have to start the Time Machine backup process over again and do another full initial backup.
According to THIS article [http://support.apple.com/kb/TS1760], Time Machine may experience problems if your computer name includes certain characters. Make sure the computer name only includes ASCII characters from the following set.
(0123456789abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ)
Once a change in the computer name occurs, you should stop and restart Sharing on the affected computer. Uncheck and then recheck Sharing in the Services list on the left.
Let me know if any of this helps.
Cheers!

Backup configuration with LD417

Similar Messages

Maybe you are looking for