Urgent--dial backup with a PPPOE configuration

Hi all. I have a pppoe for my DSL connection. I cannot get the dial backup to work while the dsl is working.

Hi,
I think there are few problems:
1. the backup interface command should be applied under the dialer interface
2. the dialer interface will never go down unless you shut it
Let' try to configure dialer watch (http://www.cisco.com/en/US/docs/ios/12_0/dial/configuration/guide/dcdbakdw.html) or may be enhanced object tracking (http://www.cisco.com/en/US/products/sw/iosswrel/ps5413/products_feature_guide09186a00801d862d.html).
Hope it helps, rate if does
Krisztian

Similar Messages

Need help on dial backup with ISP

I've been googling around a couple hours and can't find a simple configuration for dial backup to an Internet Service Provider.
So far, what I've been able to find is direct dialing to routers and dial backup using ISDN.
All I need is for a router to dial. The ISP uses PAP/CHAP authentication and dynamically assigns IP addresses to dialup accounts.
I have an 1841 router with a T1 line on S0/0/0. I want it to fail over to the modem on the AUX port and use that as the new default gateway for all traffic.
Any help is appreciated.

I think you can use Dial on Demand Routing (DDR) as described here:
http://www.cisco.com/en/US/tech/tk801/tk133/tsd_technology_support_protocol_home.html
and this particular guide as well:
http://docwiki.cisco.com/wiki/Internetwork_Design_Guide_--_Designing_DDR_Internetworks#Dial_Backup_for_Leased_Lines
Basically your dial connection will not be active until certain traffic will pass through.
Now, to pass traffic only when primary is down, you can define a static floating route as explained above, which is a route with a higher admin distance than the default one, so if the normal route is up, nothing will pass to the dialer, if it's down, the route to the dialer will be used.
To detect that primary route is down, either use dynamic routing or route tracking as suggested.
I hope that helps.
Regards,
bastien.

1750 dial backup with WIC-1ENET

Does anyone have dial backup working with a DSL or CAble link on the WIC-1ENET card as the wan link?
My dial backup doesn't automatically come up when using the WIC-1ENET card. It does work correctly when I use a serial connection as the WAN link such as the WIC-1T card.
Cisco stated something about the E0 interface not sensing the change which caused the dial backup not to come up without pulling the ethernet cable out of E0.
Any help would be greatly appreciated.
Thanks

Hi
Hope this helps...
You need to run object tracking feature to enable automatic fallback.
http://www.cisco.com/en/US/partner/docs/ios/12_3/12_3x/12_3xe/feature/guide/dbackupx.html
regds

ISDN dial-in with Cisco 1721 and WIC-1B-S/T

Hi there,
we use a Cisco 1721 with a WIC-1B-S/T interface for ISDN backup purposes. I configured the Cisco 1721 and connected the BRI-WIC to a ISDN channel. When I try to test the ISDN connection, I always get the error that the line protocol is down. The WIC is connected to the ISDN correctly. I do not understand why the line protocol is always down. Could anybody help? The chosen encapsulation is PPP, the ISDN Switch Type is basic-1tr6 (I think thats the right one for Germany). The IOS version is 12.4 (1c).
Regards, J. Schroeder

Hi there,
the BRI interface is connected to a telephone system and not directly to a NTBA. The hostname matches the username, is this right? When I try to dial out, I get this messages:
*Mar 9 16:28:11.804: ISDN BR0 **ERROR**: host_disconnect_ack: Unfound B-channel on Disconnect_Ack call id 0x8003
*Mar 9 16:28:33.792: ISDN BR0 **ERROR**: CCBRI_Go: NO CCB Src->HOST call id 0x8003, event 0x5 ces 1
*Mar 9 16:29:47.324: ISDN BR0 **ERROR**: host_disconnect_ack: Unfound B-channel on Disconnect_Ack call id 0x8004
*Mar 9 16:30:09.312: ISDN BR0 **ERROR**: CCBRI_Go: NO CCB Src->HOST call id 0x8004, event 0x5 ces 1
*Mar 9 16:30:12.952: ISDN BR0 **ERROR**: host_disconnect_ack: Unfound B-channel on Disconnect_Ack call id 0x8005
*Mar 9 16:30:34.940: ISDN BR0 **ERROR**: CCBRI_Go: NO CCB Src->HOST call id 0x8005, event 0x5 ces 1

Dial-backup - business hours limit

Hi everybody,
I´m working in a lab that includes dial-backup for a VSAT link (satellite link). This part of the lab is working excelent, dial-backup goes up when the VSAT connection is lost, and goes down when the VSAT link is recovered.
So, all is ok but... I need to grant dial-backup access only in business hours (ex: 9 am to 5 pm) and deny these the rest of the day.
I worked with time range + access list + dial-list but it didn´t work for me. I was following the steps of this link: http://www.cisco.com/en/US/tech/tk801/tk133/technologies_configuration_example09186a0080094089.shtml.
Is there other way to do this or other idea?
Regards.

Todd,
Sorry for the delay but i was on vacation. At below you´ll find the configuration, specifically highlighted in red the configuration regarding to block dial-in connections. This configuration intends to permit the dial-in connections only on business hours. I know that just is blocking IP traffic but I did not find a way to block PPP or other protocol in a low level.
Could you help me?
Thanks in advance.
Current configuration : 18107 bytes
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
hostname central
boot-start-marker
boot-end-marker
logging message-counter syslog
no logging buffered
no logging console
enable password CVMSLoA
aaa new-model
aaa authentication ppp default local
aaa authorization exec dafault local
aaa session-id common
memory-size iomem 30
dot11 syslog
ip source-route
ip cef
ip domain name test_dbkp
no ipv6 cef
multilink bundle-name authenticated
PURPOSELY REMOVED
username alumine password 0 alumine
username senillosa password 0 senillosa
interface Loopback0
ip address 192.168.2.1 255.255.255.255
interface FastEthernet0/0
description to TELCO1
ip address 10.1.176.1 255.255.255.248
ip nbar protocol-discovery
ip nat outside
ip virtual-reassembly
duplex auto
speed auto
analysis-module monitoring
service-policy output CUSTOMER_QoS
interface FastEthernet0/1
description to TELCO2
ip address 10.1.176.9 255.255.255.248
duplex auto
speed auto
analysis-module monitoring
interface FastEthernet0/1/0
interface FastEthernet0/1/1
interface FastEthernet0/1/2
interface FastEthernet0/1/3
interface Integrated-Service-Engine1/0
ip unnumbered Vlan1
ip nbar protocol-discovery
service-module ip address 10.1.48.253 255.255.255.0
!Application: running
service-module ip default-gateway 10.1.48.1
no keepalive
interface Vlan1
ip address 10.1.48.1 255.255.255.0
ip flow ingress
ip flow egress
ip nat inside
ip virtual-reassembly
no autostate
interface Async1
no ip address
encapsulation slip
async mode interactive
no peer default ip address
interface Async0/0/0
ip unnumbered Loopback0
encapsulation ppp
async dynamic address
async mode interactive
no peer default ip address
dialer-group 2
ppp authentication chap
routing dynamic
interface Async0/0/1
ip unnumbered Loopback0
encapsulation ppp
async dynamic address
async mode interactive
no peer default ip address
dialer-group 2
ppp authentication chap
routing dynamic
interface Async0/0/2
ip unnumbered Loopback0
encapsulation ppp
async dynamic address
async mode interactive
no peer default ip address
dialer-group 2
ppp authentication chap
routing dynamic
interface Async0/0/3
ip unnumbered Loopback0
encapsulation ppp
async dynamic address
async mode interactive
no peer default ip address
dialer-group 2
ppp authentication chap
routing dynamic
interface Async0/0/4
ip unnumbered Loopback0
encapsulation ppp
async dynamic address
async mode interactive
no peer default ip address
dialer-group 2
ppp authentication chap
routing dynamic
interface Async0/0/5
ip unnumbered Loopback0
encapsulation ppp
async dynamic address
async mode interactive
no peer default ip address
dialer-group 2
ppp authentication chap
routing dynamic
interface Async0/0/6
ip unnumbered Loopback0
encapsulation ppp
async dynamic address
async mode interactive
no peer default ip address
dialer-group 2
ppp authentication chap
routing dynamic
interface Async0/0/7
ip unnumbered Loopback0
encapsulation ppp
async dynamic address
async mode dedicated
no peer default ip address
dialer-group 2
ppp authentication chap
routing dynamic
router bgp 1
no synchronization
bgp log-neighbor-changes
network 10.1.48.0 mask 255.255.255.0
network 10.222.48.0 mask 255.255.255.0
network 192.168.2.1 mask 255.255.255.255
neighbor 10.1.176.25 remote-as 4
neighbor 10.1.176.25 ebgp-multihop 255
neighbor 10.1.176.33 remote-as 5
neighbor 10.1.176.33 ebgp-multihop 255
neighbor 10.1.176.41 remote-as 6
neighbor 10.1.176.41 ebgp-multihop 255
neighbor 10.1.176.49 remote-as 7
neighbor 10.1.176.49 ebgp-multihop 255
neighbor 10.1.176.57 remote-as 8
neighbor 10.1.176.57 ebgp-multihop 255
neighbor 10.1.176.65 remote-as 9
neighbor 10.1.176.65 ebgp-multihop 255
neighbor 10.1.176.73 remote-as 110
neighbor 10.1.176.73 ebgp-multihop 255
neighbor 10.1.176.81 remote-as 11
neighbor 10.1.176.81 ebgp-multihop 255
neighbor 10.1.176.89 remote-as 12
neighbor 10.1.176.89 ebgp-multihop 255
neighbor 10.1.176.97 remote-as 13
neighbor 10.1.176.97 ebgp-multihop 255
neighbor 10.1.176.105 remote-as 14
neighbor 10.1.176.105 ebgp-multihop 255
neighbor 10.1.176.113 remote-as 15
neighbor 10.1.176.113 ebgp-multihop 15
neighbor 10.1.176.121 remote-as 16
neighbor 10.1.176.121 ebgp-multihop 255
neighbor 10.1.176.129 remote-as 17
neighbor 10.1.176.129 ebgp-multihop 255
neighbor 10.1.176.137 remote-as 18
neighbor 10.1.176.137 ebgp-multihop 255
neighbor 10.1.176.145 remote-as 19
neighbor 10.1.176.145 ebgp-multihop 255
neighbor 10.1.176.153 remote-as 20
neighbor 10.1.176.153 ebgp-multihop 255
neighbor 10.1.176.161 remote-as 21
neighbor 10.1.176.161 ebgp-multihop 255
neighbor 10.1.176.169 remote-as 22
neighbor 10.1.176.169 ebgp-multihop 255
neighbor 10.1.176.177 remote-as 24
neighbor 10.1.176.177 ebgp-multihop 255
neighbor 10.1.176.185 remote-as 25
neighbor 10.1.176.185 ebgp-multihop 255
neighbor 10.1.176.193 remote-as 220
neighbor 10.1.176.193 ebgp-multihop 255
ip forward-protocol nd
ip route 0.0.0.0 0.0.0.0 10.1.176.6
ip route 10.1.48.253 255.255.255.255 Integrated-Service-Engine1/0
ip route 10.1.176.0 255.255.255.0 10.1.176.2
ip route 10.1.176.24 255.255.255.248 10.1.176.10
ip route 10.1.176.40 255.255.255.248 10.1.176.10
ip route 10.1.176.64 255.255.255.248 10.1.176.10
ip route 10.1.176.72 255.255.255.248 10.1.176.10
ip route 10.1.176.88 255.255.255.248 10.1.48.16
ip route 10.1.176.152 255.255.255.248 10.1.176.10
ip route 10.1.176.200 255.255.255.248 10.1.48.16
ip route 10.1.176.208 255.255.255.240 10.1.48.16
ip route 10.1.176.248 255.255.255.248 10.1.176.10
ip route 10.2.48.0 255.255.255.0 10.1.176.2
ip route 10.3.48.0 255.255.255.0 10.1.176.2
PURPOSELY REMOVED
access-list 1 permit 192.168.150.199
access-list 1 permit 10.1.176.2
access-list 1 permit 10.1.176.6
access-list 1 permit 10.1.48.0 0.0.0.255
access-list 1 permit 10.222.48.0 0.0.0.255
access-list 101 permit ip any any time-range BUSINESS-HOURS
access-list 101 deny ip any any
dialer-list 2 protocol ip list 101
snmp-server community RTPE-T-2 RO
snmp-server community RTPE-R-2 RO
snmp-server community RTPE-W-2 RO
snmp-server location CCTE
snmp-server contact AREA C+T
snmp-server host 10.1.48.19 RTPE-T-2
snmp-server host 10.1.48.219 RTPE-T-2
control-plane
voice-port 0/2/0
voice-port 0/2/1
voice-port 0/2/2
voice-port 0/2/3
dial-peer voice 1 pots
preference 1
destination-pattern *1
port 0/2/0
dial-peer voice 2 pots
preference 2
destination-pattern *1
port 0/2/1
dial-peer voice 3 pots
preference 3
destination-pattern *1
port 0/2/2
dial-peer voice 4 pots
preference 4
destination-pattern *1
port 0/2/3
dial-peer voice 5 pots
preference 1
destination-pattern [5-7]...
port 0/2/0
forward-digits all
dial-peer voice 6 pots
preference 2
destination-pattern [5-7]...
port 0/2/1
forward-digits all
dial-peer voice 7 pots
preference 3
destination-pattern [5-7]...
port 0/2/2
forward-digits all
dial-peer voice 8 pots
preference 4
destination-pattern [5-7]...
port 0/2/3
forward-digits all
dial-peer voice 9 voip
destination-pattern 199
session protocol sipv2
session target ipv4:10.255.48.227
no vad
dial-peer voice 10 voip
destination-pattern 101
session protocol sipv2
session target ipv4:10.3.48.3
no vad
dial-peer voice 11 voip
destination-pattern 102
session protocol sipv2
session target ipv4:10.3.48.35
no vad
dial-peer voice 12 voip
destination-pattern 103
session protocol sipv2
session target ipv4:10.3.48.67
no vad
dial-peer voice 13 voip
destination-pattern 121
session protocol sipv2
session target ipv4:10.2.48.3
no vad
dial-peer voice 14 voip
destination-pattern 122
session protocol sipv2
session target ipv4:10.4.48.3
no vad
dial-peer voice 15 voip
destination-pattern 123
session protocol sipv2
session target ipv4:10.18.48.3
no vad
dial-peer voice 16 voip
destination-pattern 131
session protocol sipv2
session target ipv4:10.12.48.3
no vad
dial-peer voice 17 voip
destination-pattern 132
session protocol sipv2
session target ipv4:10.220.48.3
no vad
PURPOUSLY REMOVED
line con 0
line aux 0
stopbits 1
line 0/0/0 0/0/7
modem InOut
autoselect ppp
stopbits 1
speed 57600
flowcontrol hardware
line 66
no activation-character
no exec
transport preferred none
transport input all
transport output lat pad telnet rlogin lapb-ta mop udptn v120 ssh
line vty 0 4
access-class 1 in
privilege level 15
transport input telnet ssh
line vty 5 15
access-class 1 in
privilege level 15
scheduler allocate 20000 1000
time-range BUSINESS-HOURS
periodic daily 09:00 to 17:00
end

DMVPN Dial Backup

Hi,
I need to configure a DMVPN with Dial Backup, my intention is when to fall interface ADSL, my router 837 make a call to local ISP by Console port and close the DMVPN in this interface, that is possible???..Somebody has some configuration as example? Thanks.

I've been reviewing that document over and over, but it only appears to work properly with static IPs, and I will need to use DHCP. There was another document talking about RSR with DHCP, but I still couldn't get it to work properly. Here's why...
My default route is the hubs tunnel address. Then I have a /32 route for the public-facing IP of the hub, via DHCP.
The above-mentioned document doesn't function this way, because they assume that your default route is placed by DHCP. Additionally, I can't seem to find a way to work without my default route pointing the the hub tunnel address.

Options: dial backup not using ISDN

This is my first post here. I hope I'm in the right place. I need to provide dial backup to one of our locations but it is too far to run an ISDN circuit to them. Mgt. says too expensive and wants a dial backup solution across a POTS line. The site was just upgraded to VOIP. We only need to allow data traffic.
We have a 2821 router running 12.4(3) version IOS. Not sure what the best option is here. Maybe another alternate way other than a modem and a POTS line. I am just looking for ideas if anyone has them. Thanks

Hello,
since cost is a concern, you could just use the AUX port (provided the device at the remote location has one) to configure a dial backup solution. This would still involve using a POTS line, but that is probably the cheapest way to get any sort of backup accomplished. Below is a configuration example. Regarding the voice traffic that should not traverse the backup connection, you would need to deny that traffic to trigger the backup, as well as to get across. In order to accomplish this, you would need to configure an access list that denies VoIP traffic, for Cisco, this would typically look like this:
access-list 101 deny tcp any any eq 1720
access-list 101 deny udp any any range 16384 32767
access-list permit ip any any
This access list then would need to be applied to the async interface (based on the configuration example given), as well as to the dialer list that triggers the backup:
interface Async65
ip access-group 101 out
dialer-list 1 protocol ip list 101
Configuring AUX-to-AUX Port Async Backup with Dialer Watch
http://www.cisco.com/en/US/tech/tk801/tk36/technologies_configuration_example09186a0080093d2b.shtml
HTH,
GP

Dial-backup in 1841 and 2801

Please, does anyone know if the AUX ports in 1841 and 2801 support dial-backup, for example, using PPP ?
Thanks,
Cleber

Hello,
TMBK they do. Check this document for configuration details:
Configuring AUX-to-AUX Port Async Backup with Dialer Watch
http://www.cisco.com/en/US/tech/tk801/tk36/technologies_configuration_example09186a0080093d2b.shtml
HTH,
GNT

Required to take backup with out TSM in PROD server.

Dear all,
I required to take backup with out using TSM .
we have got error in TSM . so that i am getting error .
Prod server backup is working automated through TSM .
now i need to take Online backup with out using TSM like DEV and QA (Manual backup) .
For DEV and QA server backup is manual . i am simply moved the tape to tape library and fired the online backup as well same QA also .
Now my query is reqiured to take backup with out the help of TSM in PROD server . Is it possible ?
2 profiles are configured for Online backup and offline backup .
pls check the below profiles .
initSIDdaily.sap -
> Online backup .
initSIDweekly.sap -
> Offline backup
is there any parameter i need to change ?
Kindly advise

Dear all ,
I have initialised the Tape IRPB01 , after i have try to tkae backup , i got below error .
BR0051I BRBACKUP 7.00 (48)
BR0055I Start of database backup: bedqreyq.ant 2010-07-12 13.19.44
BR0484I BRBACKUP log file: /oracle/IRP/sapbackup/bedqreyq.ant
BR0477I Oracle pfile /oracle/IRP/102_64/dbs/initIRP.ora created from spfile /ora
cle/IRP/102_64/dbs/spfileIRP.ora
BR0280I BRBACKUP time stamp: 2010-07-12 13.19.45
BR0319I Control file copy created: /oracle/IRP/sapbackup/cntrlIRP.dbf 15122432
BR0280I BRBACKUP time stamp: 2010-07-12 13.19.46
BR0057I Backup of database: IRP
BR0058I BRBACKUP action ID: bedqreyq
BR0059I BRBACKUP function ID: ant
BR0110I Backup mode: ALL
BR0077I Database file for backup: /oracle/IRP/sapbackup/cntrlIRP.dbf
BR0061I 42 files found for backup, total size 158434.742 MB
BR0143I Backup type: online
BR0112I Files will not be compressed
BR0130I Backup device type: tape
BR0102I Following backup device will be used: /dev/rmt0.1
BR0103I Following backup volume will be used: IRPB01
BR0280I BRBACKUP time stamp: 2010-07-12 13.19.46
BR0256I Enter 'c[ont]' to continue, 's[top]' to cancel BRBACKUP:
c
BR0280I BRBACKUP time stamp: 2010-07-12 13.19.52
BR0257I Your reply: 'c'
BR0259I Program execution will be continued...
BR0208I Volume with name IRPB01 required in device /dev/rmt0.1
BR0210I Please mount BRBACKUP volume, if you have not already done so
BR0280I BRBACKUP time stamp: 2010-07-12 13.19.52
BR0256I Enter 'c[ont]' to continue, 's[top]' to cancel BRBACKUP:
c
BR0280I BRBACKUP time stamp: 2010-07-12 13.19.55
BR0257I Your reply: 'c'
BR0259I Program execution will be continued...
BR0280I BRBACKUP time stamp: 2010-07-12 13.19.55
BR0226I Rewinding tape volume in device /dev/rmt0 ...
BR0351I Restoring /oracle/IRP/sapbackup/.tape.hdr0
BR0355I from /dev/rmt0.1 ...
BR0241I Checking label on volume in device /dev/rmt0.1
BR0280I BRBACKUP time stamp: 2010-07-12 13.19.55
BR0226I Rewinding tape volume in device /dev/rmt0 ...
BR0202I Saving /oracle/IRP/sapbackup/.tape.hdr0
BR0203I to /dev/rmt0.1 ...
BR0209I Volume in device /dev/rmt0.1 has name IRPB01
BR0202I Saving init_ora
BR0203I to /dev/rmt0.1 ...
BR0202I Saving /oracle/IRP/102_64/dbs/initIRPdaily.sap
BR0203I to /dev/rmt0.1 ...
BR0280I BRBACKUP time stamp: 2010-07-12 13.19.59
BR0198I Profiles saved successfully
BR0280I BRBACKUP time stamp: 2010-07-12 13.20.00
BR0315I 'Alter tablespace PSAPSR3 begin backup' successful
BR0202I Saving /oracle/IRP/sapdata1/sr3_1/sr3.data1
BR0203I to /dev/rmt0.1 ...
BR0278E Command output of 'LANG=C dd obs=64k bs=64k if=/oracle/IRP/sapdata1/sr3_
1/sr3.data1 of=/dev/rmt0.1':
dd: /oracle/IRP/sapdata1/sr3_1/sr3.data1: Invalid argument
BR0280I BRBACKUP time stamp: 2010-07-12 13.20.00
BR0279E Return code from 'LANG=C dd obs=64k bs=64k if=/oracle/IRP/sapdata1/sr3_1
/sr3.data1 of=/dev/rmt0.1': 2
BR0222E Copying /oracle/IRP/sapdata1/sr3_1/sr3.data1 to/from /dev/rmt0.1 failed
due to previous errors
BR0280I BRBACKUP time stamp: 2010-07-12 13.20.02
BR0317I 'Alter tablespace PSAPSR3 end backup' successful
BR0056I End of database backup: bedqreyq.ant 2010-07-12 13.20.00
BR0280I BRBACKUP time stamp: 2010-07-12 13.20.02
BR0054I BRBACKUP terminated with errors
BR0292I Execution of BRBACKUP finished with return code 5
BR0668I Warnings or errors occurred - you can continue to ignore them or go back
to repeat the last action
BR0280I BRTOOLS time stamp: 2010-07-12 13.20.02
BR0670I Enter 'c[ont]' to continue, 'b[ack]' to go back, 's[top]' to abort:
Kindly Advise

How can I create a new TC backup with ethernet, so I don't have to wait two days for a new wireless backup?

How can I create a new TC backup with ethernet, so I don't have to wait two days for a new wireless backup?
Several times in the last year, I've gotten a message that Time Machine needs to completely redo my backup. Using the wireless connection, this takes almost two days. Is there a way to do the backup with ethernet and then switch back to wireless? Thanks.

May I know what is needed to make sure the MacBook is able to see Time Capsule on ethernet?
Connect an Ethernet cable from one of the LAN <-> ports on the 2Wire gateway to the WAN port (circle of dots icon) on the Time Capsule.
If AirPort Utility cannot "see" the Time Capsule now, you will need to perform a "hard reset" by holding in the reset button for 7-8 seconds or so and then reconfigure the Time Capsule. You can use the same Time Capsule name and password, etc. as before.
Configure the Time Capsule to "Create a wireless network" and select the Bridge Mode option when it appears during the setup using AirPort Utility.
Once the Time Capsule is configured, restart the entire network again. Power down everything, start the 2Wire first and then start each other device after that one at a time about a minute apart.
Now you can connect your Mac directly to one of the LAN <-> ports on the Time Capsule for the backup using another Ethernet cable. In general, about 20-25 GB per hour will transfer.
The Time Capsule will broadcast a much faster wireless network than the 2Wire can provide, so you might want to leave the setup "as is" for awhile after the first backup is complete. If you decide to use the Time Capsule as your main wireless access point, you would want to turn the wireless off on the 2Wire since two wireless networks in close proximity can create interference problems.
Or, if you want to use the wireless on the 2Wire, you could turn off the wireless on the Time Capsule. Then backups will occur over the 2Wire wireless, or over Ethernet.
I don't really recommend the "Join a wireless network" setting on the Time Capsule for most users, but you could go back to that setup as well if you want after the first backup is complete.

Windows Server 2003 R2 Backup with Hyper-V in DPM

Hello,
I am trying to backup multiple Windows Server 2003 R2 VMs on Hyper-V (Windows Server 2012 R2) with DPM.
When I try to this I get the following errors:
On the Hyper-V Host:
Source: VSS ID:8229
A VSS writer has rejected an event with error 0x800423f4, The writer experienced a non-transient error. If the backup process is retried,
the error is likely to reoccur.
. Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer.
Operation:
   PrepareForSnapshot Event
Context:
   Execution Context: Writer
   Writer Class Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
   Writer Name: Microsoft Hyper-V VSS Writer
   Writer Instance ID: {0b5be050-91e2-41a6-9207-414f1291f975}
   Command Line: C:\Windows\system32\vmms.exe
   Process ID: 5312
Source: Hyper-V-VMMS ID: 18014
Checkpoint operation for 'VMName' was cancelled. (Virtual machine ID D605FC49-D379-4C60-A730-485C8E9279DC)
Source: Hyper-V-VMMS ID: 18012
Checkpoint operation for 'VMName' failed. (Virtual machine ID D605FC49-D379-4C60-A730-485C8E9279DC)
Source: Hyper-V-VMMS ID: 10150
Could not create backup checkpoint for virtual machine 'VMName': Element not found. (0x80070490). (Virtual machine ID D605FC49-D379-4C60-A730-485C8E9279DC)
Source: Hyper-V-Worker ID: 3280
'VMName' could not initiate a checkpoint operation: Element not found. (0x80070490). (Virtual machine ID D605FC49-D379-4C60-A730-485C8E9279DC)
Source: Hyper-V-VMMS ID: 16010
The operation failed.
The Output of vssadmin list writers on the Hyper-V Host looks like this:
Writer name: 'Microsoft Hyper-V VSS Writer'
   Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
   Writer Instance Id: {0b5be050-91e2-41a6-9207-414f1291f975}
   State: [8] Failed
   Last error: Non-retryable error
In the Windows Server 2003 R2 VM there are no errors in the eventlog.
Only the information, that VSS is started and stopped after a while.
When I do a Backup with ntbackup of in the VM everything runs fine.
When I create a checkpoint with Hyper-V everything runs fine, too.
The integration services are up to date and get-vmintegrationservice -vmname VMName shows everything is enabled and OK.
On the Hyper-V host there are 13 VMs. 3 of them are running Windows Server 2003 R2 and 2 of them are showing this error. It seems to be no general problem with Windows Server 2003 R2 then.
I tried the backup on a different Hyper-V host with no success.
How can I narrow down the cause of this error?
Thanks.
greets,
torsten

Thank you to everyone in this thread!
After digging through VSS and Hyper-V dead-ends, the solution above worked for me in a W2012 R2 environment.
I only had this problem trying to back up W2012 R2 Hyper-V VMs stored on a CSV, hosted on a W2012 R2 Host Cluster, backing up from a Host node. I could back up from within the guests fine. Both Windows Server Backup and DPM 2012 R2
gave VSS errors on the cluster hosts.
In fact Windows Server Backup complains with 80780189 it won't back up an application with files on a CSV, which is a common cluster configuration. This is an example of another caveat in a minefield of MS caveats buried in fine print which often negates
configurations touted by MS Marketing, things which sound great on a sell sheet, but in practice are impractical or just not production-ready because of these restrictions.
Disabled Backup in Integration Services, performed an offline back up from DPM 2012 R2 (which did briefly affect serving the workloads on the VM), which succeeded, and then re-enabled Backup in Integration Services. DPM then continued to
sync successfully after that for a day. However, this problem returned after a period of heavy DPM backup activity. So I redistributed backups through various Protection Groups to spread the DPM load over a longer period and this seems to
have solved this problem.
In general I had lots of problems installing, configuring, and now operating DPM, so the experience has not been smooth, but most of the problems have now been solved. I find you have to "baby" this product and not push it too hard,
otherwise things start breaking.
Thanks again everyone!
DPM Error ID 30111 0x800423F4
DPM-EM Event ID 3106

Backup with retention policy to recovery window of N days

Hello,
I've issued command to create database incremental backup with configuration:
run
configure retention policy to recovery window of 14 days;
backup incremental level 1 cumulative
tag daily_incr_14_days
database
plus archivelog delete all input;
All parameters are set to their default values and database backups goes to FRA. I've got recovery catalog connected and all RC_ views at my disposal.
1) Is there any way to find out, what recovery window was used for backup from any command in rman or query from RC_ views or local database views (information from control file)?
2) If I use other recovery window setting with configure command what would rman crosscheck or report commands do?
BR
Patrycjusz.

TenakaKhan wrote:
Mahir,
thanks for answer - this means that recovery window should be used mainly for maintenance purposes (crosscheck, delete obsolete, report need backup etc.) and it's not related to actual retention period with backup pieces like 'keep until' clause for backup ... database command (this information are saved with backup as I could check in rc_backup_set view from recovery catalog)?
Yes it is.
Maintaining RMAN Backups and Repository&nbsp;Records
keepOption
backup retention policy
A user-defined policy for determining how long backups and archived logs must be retained for media recovery. You can define a retention policy in terms of backup redundancy or a recovery window.
RMAN retains the data file backups required to satisfy the current retention policy, and any archived redo logs required for complete recovery of those data file backups.
recovery window
A recovery window is one type of RMAN backup retention policy, in which the DBA specifies a period of time and RMAN ensures retention of backups and archived redo logs required for point-in-time recovery to any time during the recovery window.
The interval always ends with the current time and extends back in time for the number of days specified by the user. For example, if the retention policy is set for a recovery window of seven days, and the current time is 11:00 AM on Tuesday,
RMAN retains the backups required to allow point-in-time recovery back to 11:00 AM on the previous Tuesday.
Regards
Mahir M. Quluzade

Db_file parameter change in oracle 8i with physical standby configured

i have oracle 8i (8.1.7) with physical standby configured.
i need to change the db_file parameter value. kindly check the below steps are correct? Thanks.
1. alter database backup controlfile to trace;
2. edit the init.ora file as db_file=<new value> (after backing up the existing pfile)
3. edit the create control file statement in udump -- max datafile (and also remove the first line startup nomount)
4. shutdown immediate;
5. startup pfile ='file name';
6. in sqlplus run the create control file statement;
7. alter database backup controfl file for standby;
8. move the standby control file to standby db server
9. shutdown immediate in standby
10. copy the pfile and edit the new values
11. startup mount pfile='new pfile' (in standby)
12. recover control file <location> from rman
13. start the recovering of standby.
Thanks,
Raman.

Just change the db_files value to some higher value in the init.ora file and restart the database. With this you can create more datafiles no need to create control file.

RMAN backup with smallest backup size

Oralce 11g2 on Redhat 5. The diskspace is our tightest resource, and we want to an incremental backup with level0 on Sunday and level 1 every week days and Saturday. I am to use the comamnds to do the job--Sunday
backup incremental level 0 tag 'level_0' database plus archivelog;
--Other days
backup incremental level 1 database plus archivelog delete all input;I do not think this is the best practice nor produce smallest backup files.
What are you comments and opinions. Thanks

Pavan, Thank you for reply. Here are the info requested
what is size of DB ??
~250GB, including UNDO and TEMP. It is a dev database and not very big. But we have total 800GB disk space. After setting some housekeeoing folders, and allow some space for data growth, it leaves 180GB for flash_recovery_area.
what would be max size of archive logs generated per day ??
Variable from less than 1 GB to 12 GB
Are you taking backups to tape or Disk ??
Disk. In the 180GB flash_recovery_area, Current backup size is 152GB. If a backup fails to delete obsolete files, the next backup will fill the flash_recovery_area.
Provide the Rman configuration information ??
RMAN> show all;
RMAN configuration parameters for database with db_unique_name TDEV2 are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.2.0/dbhome_1/dbs/snapcf_tdev2.f'; # default

RMAN Backups with retention policy to redundancy 1 doesn't work fine.

Hi experts,
I have a Oracle database with the following system backups:
Monday:       ArchiveLog Backup
Tuesday:      Full Backup
Wednesday: ArchiveLog Backup
Thursday:     ArchiveLog Backup
Friday :         Full Backup
Saturday:      ArchiveLog Backup
Sunday:       ArchiveLog Backup
ArchiveLog Backup = backup tag 'ARCHIVELOG_BACKUP' device type disk archivelog all not backed up delete all input;
Full Backup = backup tag 'FULL_BACKUP' device type disk database skip readonly plus archivelog tag 'FULL_BACKUP_ARCHIVELOGS';
                     crosscheck backup;
                     crosscheck copy;
                     delete noprompt obsolete;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 8;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
What this system has done until last two weeks? For example:
Tuesday :     Full Backup
Wednesday: ArchiveLog Backup
Thursday:     ArchiveLog Backup
Friday :         Full Backup - > After that, Full backup from Tuesday and ArchiveLog backups from Wed, and Thurs, are deleted. (Thanks to Retention policy) .
What this system do now?
Tuesday :     Full Backup
Wednesday: ArchiveLog Backup
Thursday:     ArchiveLog Backup
Friday :         Full Backup - > After that, Full backup from Tuesday are deleted but not ArchiveLog backups from Wed, and Thurs.
When I execute a crosscheck on RMAN return that all are AVAILABLE.
My question is: What is right? The system backups before or after?
Thanks for your help!

You are confused about the purpose of crosscheck.
There are two concepts for which you must grasp the distinction.
- Expired
- Obsolete
Expired
When an archive log is written, or rman makes a backup, a record of that archivelog or backupset is written to the repository in the control file.
Crosscheck simply checks the existence of the archivelogs or backupsets that are recorded in the repository. If something went missing (say, if you used an OS command to delete archivelogs), the record of the missing file is marked as 'expired'. If you follow the crosscheck command with a 'delete expired' command, the repository records that have been marked 'expired' are deleted from the repository, so rman has no more memory of those files. Note that 'expired' has nothing to do with retention policy. Also note that if you do not actually issue the 'delete expired' command, the expired records will remain in the repository.
Obsolete
The retention policy deals with when a backupset is obsolete, meaning it is no longer needed to protect the retention period. Backupset are not marked as obsolete. They are evaluated for obsolescence at the time of a command that needs it -- "report obsolete" or "delete obsolete", or when FRA maintenance requires an implied 'delete obsolete'.

Urgent--dial backup with a PPPOE configuration

Similar Messages

Maybe you are looking for