Loopback0 vs. "Backup interface GigabitEthernetx/x" for redundance

Hi,
I am a voice engineer. To configure MGCP gateways I have used the Cisco standard method of creating a loopback interface specially when there are redundant switch connections, e.g. GigabitEthernet0/0 and GigabitEthernet0/0. Can anybody please explain if I use "backup interface" method, would it work same way. The backup interface method also has a backup delay, not sure what is default, but secondary interface won't be active until the delay elapses. If I configure "no backup delay" would there still be an event for MGCP? Can somebody please share their experience?

If your primary interface fails, is there an event for MGCP? What happens to active calls?
Update: I just found that the default delay is 0 seconds (that means "no backup delay" is not required to be explicitly added, so I assume the MGCP gateway should not experience any impact at all. If you done this testing in your environment, please confirm.
And thanks a lot for quick reply!

Similar Messages

Backup interface on fiber ring

We recently installed a 100Meg MPLS fiber ring into our office, and we were given redundant connections (north loop and south loop).
The North loop is the primary interface, and will be used unless the fiber is cut.
I need to configure our router to automatically switch to the south loop in the event that the north loop goes down.
Here is the config I have so far, I just want to make sure I'm not missing anything.
interface GigabitEthernet0/0/0
description 100MB MPLS North Loop
backup delay 30 never
backup interface GigabitEthernet0/0/1
ip address X.X.X.X 255.255.255.252
media-type sfp
negotiation auto
interface GigabitEthernet0/0/1
description 100MB MPLS backup South Loop
ip address X.X.X.X 255.255.255.252
media-type sfp
negotiation auto
Am I correct in thinking that, should the North loop on Gi0/0/0 go down, it will automatically switch to Gi0/0/1 after 30 seconds of down time?
If so, how do I go about switching back to the north loop when it comes back online?

Hi,
I have see this feature configure on few ISP. For this feature to work, interface needs to go down then only RP can send UP event to standby link and make it up.
You can also go through below discussion on backup interface
https://supportforums.cisco.com/discussion/10921951/how-set-backup-delay-serial-interface-ethernet-interface
regarding backup delay , i am not sure why you want to put delay of 30 sec before standby interface becomes active and then deactivating delay is infinite, means it will always remain active even when primary interface comes up.
CCO document on backup delay
http://www.cisco.com/c/en/us/td/docs/ios/dial/command/reference/dia-cr-book/dia_a1.html#wp1011975
backup delay
To define how much time should elapse before a secondary line status changes after a primary line status has changed, use the backup delaycommand in interface configuration mode. To return to the default so that as soon as the primary fails, the secondary is immediately brought up without delay, use the no form of this command.
backup delay {enable-delay-period | never} {disable-delay-period | never}
no backup delay {enable-delay-period | never} {disable-delay-period | never}
Syntax Description
enable-delay-period
Number of seconds that elapse after the primary line goes down before the Cisco IOS software activates the secondary line.
disable-delay-period
Number of seconds that elapse after the primary line comes up before the Cisco IOS software deactivates the secondary line.
never
Secondary line is never activated or deactivated.
--Pls rate helpful posts--
Regards,
Akash

Cisco ASA 5510 Backup Interface configuration

Hi Experts,
I am a newbie with Cisco Firewalls, pls help.
We have a BSNL Leased Line of 2MBPS with few Static IP's of Which 2 IP's are configured in Firewall 1 For the Outside Interface and one for publishing the DMZ server. Most of the times due to some reasons or the other the BSNL line is going down. so now I need to configure one another TATA Broadband 1MBPS Dialup Line as a Backup for the BSNL Line so as to provide a uninterupted Internet to our users.
Pls guide me the Steps
Thank in Advance.
Anish N

Hi Anish,
Check the below mentioned link for configuration.
http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_configuration_example09186a00806e880b.shtml

Error: "This backup is too large for the backup volume."

Well TM is acting up. I get an error that reads:
"This backup is too large for the backup volume."
Both the internal boot disk and the external baclup drive are 1TB. The internal one has a two partitions, the OSX one that is 900GBs and a 32GB NTFS one for Boot Camp.
The external drive is a single OSX Extended part. that is 932GBs.
Both the Time Machine disk, and the Boot Camp disk are excluded from the backup along with a "Crap" folder for temporary large files as well as the EyeTV temp folder.
Time Machine says it needs 938GBs to backup only the OSX disk, which has 806GBs in use with the rest free. WTFFF? The TM pane says that "only" 782GBs are going to be backed up. Where did the 938GBs figure come from?
This happened after moving a large folder (128GB in total) from the root of the OSX disk over to my Home Folder.
I have reformated the Time Machine drive and have no backups at all of my data and it refuses to backup!!
Why would it need 938GBs of space to backup if the disk has "only" 806 GBs in use??? Is there anyway to reset Time Machine completely???
Some screenshots:
http://www.xcapepr.com/images/tm2.png
http://www.xcapepr.com/images/tm1.png
http://www.xcapepr.com/images/tm4.png

xcapepr wrote:
Time Machine says it needs 938GBs to backup only the OSX disk, which has 806GBs in use with the rest free. WTFFF? The TM pane says that "only" 782GBs are going to be backed up. Where did the 938GBs figure come from?
Why would it need 938GBs of space to backup if the disk has "only" 806 GBs in use??? Is there anyway to reset Time Machine completely???
TM makes an initial "estimate" of how much space it needs, "including padding", that is often quite high. Why that is, and Just exactly what it means by "padding" are rather mysterious. But it does also need work space on any drive, including your TM drive.
But beyond that, your TM disk really is too small for what you're backing-up. The general "rule of thumb" is it should be 2-3 times the size of what it's backing-up, but it really depends on how you use your Mac. If you frequently update lots of large files, even 3 times may not be enough. If you're a light user, you might get by with 1.5 times. But that's about the lower limit.
Note that although it does skip a few system caches, work files, etc., by default it backs up everything else, and does not do any compression.
All this is because TM is designed to manage it's backups and space for you. Once it's initial, full backup is done, it will by default then back-up any changes hourly. It only keeps those hourly backups for 24 hours, but converts the first of the day to a "daily" backup, which it keeps for a month. After a month, it converts one per week into a "weekly" backup that it will keep for as long as it has room
What you're up against is, room for those 30 dailies and up to 24 hourlies.
You might be able to get it to work, sort of, temporarily, by excluding something large, like your home folder, until that first full backup completes, then remove the exclusion for the next run. But pretty soon, it will begin to fail again, and you'll have to delete backups manually (from the TM interface, not via the Finder).
Longer term, you need a bigger disk; or exclude some large items (back-them up to a portable external or even DVD/RWs first); or a different strategy.
You might want to investigate CarbonCopyCloner, SuperDuper!, and other apps that can be used to make bootable "clones". Their advantage, beyond needing less room, is when your HD fails, you can immediately boot and run from the clone, rather than waiting to restore from TM to your repaired or replaced HD.
Their disadvantages are, you don't have the previous versions of changed or deleted files, and because of the way they work, their "incremental" backups of changed items take much longer and far more CPU.
Many of us use both a "clone" (I use CCC) and TM. On my small (roughly 30 gb) system, the difference is dramatic: I rarely notice TM's hourly backups -- they usually run under 30 seconds; CCC takes at least 15 minutes and most of my CPU.

"Backup is too large for the backup volume" error

I've been backing up with TM for a while now, and finally it seems as though the hard drive is full, since I'm down to 4.2GB available of 114.4GB.
Whenever TM tries to do a backup, it gives me the error "This backup is too large for the backup volume. The backup requires 10.8 GB but only 4.2GB are available. To select a larger volume, or make the backup smaller by excluding files, open System Preferences and choose Time Machine."
I understand that I have those two options, but why can't TM just erase the oldest backup and use that free space to make the new backup? I know a 120GB drive is pretty small, but if I have to just keep accumulating backups infinitely, I'm afraid I'll end up with 10 years of backups and a 890-zettabyte drive taking up my garage. I'm hoping there's a more practical solution.

John,
Please review the following article as it might explain what you are encountering.
*_“This Backup is Too Large for the Backup Volume”_*
First, much depends on the size of your Mac’s internal hard disk, the quantity of data it contains, and the size of the hard disk designated for Time Machine backups. It is recommended that any hard disk designated for Time Machine backups be +at least+ twice as large as the hard disk it is backing up from. You see, the more space it has to grow, the greater the history it can preserve.
*Disk Management*
Time Machine is designed to use the space it is given as economically as possible. When backups reach the limit of expansion, Time Machine will begin to delete old backups to make way for newer data. The less space you provide for backups the sooner older data will be discarded. [http://docs.info.apple.com/article.html?path=Mac/10.5/en/15137.html]
However, Time Machine will only delete what it considers “expired”. Within the Console Logs this process is referred to as “thinning”. It appears that many of these “expired” backups are deleted when hourly backups are consolidated into daily backups and daily backups are consolidated into weekly backups. This consolidation takes place once hourly backups reach 24 hours old and daily backups reach about 30 days old. Weekly backups will only be deleted, or ‘thinned’, once the backup drive nears full capacity.
One thing seems for sure, though; If a new incremental backup happens to be larger than what Time Machine currently considers “expired” then you will get the message “This backup is too large for the backup volume.” In other words, Time Machine believes it would have to sacrifice to much to accommodate the latest incremental backup. This is probably why Time Machine always overestimates incremental backups by 2 to 10 times the actual size of the data currently being backed up. Within the Console logs this is referred to as “padding”. This is so that backup files never actually reach the physically limits of the backup disk itself.
*Recovering Backup Space*
If you have discovered that large unwanted files have been backed up, you can use the Time Machine “time travel” interface to recovered some of that space. Do NOT, however, delete files from a Time Machine backup disk by manually mounting the disk and dragging files to the trash. You can damage or destroy your original backups by this means.
Additionally, deleting files you no longer wish to keep on your Mac does not immediately remove such files from Time Machine backups. Once data has been removed from your Macs' hard disk it will remain in backups for some time until Time Machine determines that it has "expired". That's one of its’ benefits - it retains data you may have unintentionally deleted. But eventually that data is expunged. If, however, you need to remove backed up files immediately, do this:
Launch Time Machine from the Dock icon.
Initially, you are presented with a window labeled “Today (Now)”. This window represents the state of your Mac as it exists now. +DO NOT+ delete or make changes to files while you see “Today (Now)” at the bottom of the screen. Otherwise, you will be deleting files that exist "today" - not yesterday or last week.
Click on the window just behind “Today (Now)”. This represents the last successful backup and should display the date and time of this backup at the bottom of the screen.
Now, navigate to where the unwanted file resides. If it has been some time since you deleted the file from your Mac, you may need to go farther back in time to see the unwanted file. In that case, use the time scale on the right to choose a date prior to when you actually deleted the file from your Mac.
Highlight the file and click the Actions menu (Gear icon) from the toolbar.
Select “Delete all backups of <this file>”.
*Full Backup After Restore*
If you are running out of disk space sooner than expected it may be that Time Machine is ignoring previous backups and is trying to perform another full backup of your system? This will happen if you have reinstalled the System Software (Mac OS), or replaced your computer with a new one, or hard significant repair work done on your exisitng Mac. Time Machine will perform a new full backup. This is normal. [http://support.apple.com/kb/TS1338]
You have several options if Time Machine is unable to perform the new full backup:
A. Delete the old backups, and let Time Machine begin a fresh.
B. Attach another external hard disk and begin backups there, while keeping this current hard disk. After you are satisfied with the new backup set, you can later reformat the old hard disk and use it for other storage.
C. Ctrl-Click the Time Machine Dock icon and select "Browse Other Time Machine disks...". Then select the old backup set. Navigate to files/folders you don't really need backups of and go up to the Action menu ("Gear" icon) and select "Delete all backups of this file." If you delete enough useless stuff, you may be able to free up enough space for the new backup to take place. However, this method is not assured as it may not free up enough "contiguous space" for the new backup to take place.
*Outgrown Your Backup Disk?*
On the other hand, your computers drive contents may very well have outgrown the capacity of the Time Machine backup disk. It may be time to purchase a larger capacity hard drive for Time Machine backups. Alternatively, you can begin using the Time Machine Preferences exclusion list to prevent Time Machine from backing up unneeded files/folders.
Consider as well: Do you really need ALL that data on your primary hard disk? It sounds like you might need to Archive to a different hard disk anything that's is not of immediate importance. You see, Time Machine is not designed for archiving purposes, just as a backup of your local drive(s). In the event of disaster, it can get your system back to its' current state without having to reinstall everything. But if you need LONG TERM storage, then you need another drive that is removed from your normal everyday working environment.
This KB article discusses this scenario with some suggestions including Archiving the old backups and starting fresh [http://docs.info.apple.com/article.html?path=Mac/10.5/en/15137.html]
Let us know if this clarifies things.
Cheers!

Packup - a simple backup/restore/migration script for Pacman

I have seen numerous posts on the forums asking for an easy way to backup and restore installed software for purposes of backup, migration or simply for convenience. Packup attempts to fill this void. Simply put, Packup is an ncurses wrapper for Pacman which provides a simple backup/restore/migration system for Arch. Don't believe me? Try it for yourself!

Mimi wrote:
Ghost1227 wrote:by default it should be $8 not $9... I'd love to know why yours responds differently.
┌─[~]
└─╼ ls -Bl packup-*
-rw-r--r-- 1 julia users 2633 2. Jan 18:22 packup-complete-20090102-1821
┌─[~]
└─╼ ls -Bl packup-* | egrep -v '^d' | awk '{ print $8 }'
18:22
Maybe the problem is a different date format (de_DE.utf8).
┌─[~]
└─╼ ls -Bl --time-style=iso packup-* | egrep -v '^d' | awk '{ print $8 }'
packup-complete-20090102-1821
Good point - added --time-style to the script, should fix that problem...
Mimi wrote:
If i select "Run Yaourt" the program exits, i don't know, maybe the exit status of the if condition (if [ $? = 0 ]) overrides the selection?
┌─[~]
└─╼ if [ $? = 1 ]; then echo abcdef; elif [ $? = 1 ]; then echo fedcba; fi
fedcba
Or is it just me?
I think you miscopied something there...
if [ $? = 1 ]; ... elif [ $? = 1 ]; ...
it's kinda redundant... shouldn't one of those be =0? or =3? i'm not even sure which function you're referencing.

How to check backup interface

I want to rsh to all my machines,
1. check if the backup interface is up if it is not bring it up. The problem is backup interface is named differently on every machines ie. eth1, bge1 etc.
2. check if the back up netmask and IP is setup properly if not set it up
How can I achieve this using a script?
Thanks ever so much for your help.

I am not able to do that. Do you have any suggestions on how i can achieve the above? Thanks

CSS11501 - Unable to Telnet to VRRP backup interface IP

Hi,
I have 2 units of Cisco CSS11501 which configured running on VRRP active/standby on 2 different VLAN (Circuit). When unit 1 is master unit, I am able to telnet to its circuit IP address, but unable to telnet to any circuit IP of backup unit.
Active unit configuration:
!************************** CIRCUIT **************************
circuit VLAN145
ip address 172.19.145.182 255.255.255.0
    ip virtual-router 1 priority 101
    ip redundant-vip 1 172.19.145.184
    ip redundant-interface 1 172.19.145.183
circuit VLAN550
ip address 192.168.50.18 255.255.255.0
    ip virtual-router 2 priority 101
    ip redundant-vip 2 192.168.50.20
    ip redundant-interface 2 192.168.50.19
!*************************** OWNER ***************************
owner ***
content ***
    vip address 172.19.145.184
    port 80
    protocol tcp
    add service ***
    active
!*************************** GROUP ***************************
group ***
vip address 192.168.50.20
active
Backup unit configuration:
!************************** CIRCUIT **************************
circuit VLAN145
ip address 172.19.145.183 255.255.255.0
    ip virtual-router 1 priority 90
    ip redundant-interface 1 172.19.145.182
    ip redundant-vip 1 172.19.145.184
circuit VLAN550
ip address 192.168.50.19 255.255.255.0
    ip virtual-router 2 priority 90
    ip redundant-vip 2 192.168.50.20
    ip redundant-interface 2 192.168.50.18
!*************************** OWNER ***************************
owner ***
content ***
    vip address 172.19.145.184
    port 80
    protocol tcp
    add service ***
    active
!*************************** GROUP ***************************
group ***
vip address 192.168.50.20
active
Please help!!
Regards,
Danny Lim

Hi Marko,
That means I could not to configure redundant-interface as I have redundant-vip configured already?
Actually the topology is:
VLAN550 is connecting to server farm
VLAN145 is where user sitting
my current config :
circuit VLAN145
ip address 172.19.145.182 255.255.255.0
    ip virtual-router 1 priority 101
    ip redundant-vip 1 172.19.145.184
    ip redundant-interface 1 172.19.145.183
    ip critical-service 1 PING_DEFAULT_GATEWAY
circuit VLAN550
ip address 192.168.50.18 255.255.255.0
    ip virtual-router 2 priority 101
    ip redundant-vip 2 192.168.50.20
    ip redundant-interface 2 192.168.50.19
    ip critical-service 2 PING_DEFAULT_GATEWAY
!*************************** OWNER ***************************
owner HLRLDAP
content VIP_LDAP_16611
    vip address 172.19.145.184
    port 16611
    protocol tcp
    add service KPG-HV30-3
    add service KPG-HV30-6
    active
!*************************** GROUP ***************************
group Redundant_Server
vip address 192.168.50.20
active
So, I should have change my config like this:
CSS1
circuit VLAN145
ip address 172.19.145.182 255.255.255.0
    ip virtual-router 1 priority 101
    ip redundant-vip 1 172.19.145.184
    ip redundant-interface 1 172.19.145.181
    ip critical-service 1 PING_DEFAULT_GATEWAY
circuit VLAN550
ip address 192.168.50.18 255.255.255.0
    ip virtual-router 2 priority 101
    ip redundant-interface 2 192.168.50.20
    ip critical-service 2 PING_DEFAULT_GATEWAY
CSS2
!************************** CIRCUIT **************************
circuit VLAN145
ip address 172.19.145.183 255.255.255.0
    ip virtual-router 1 priority 90
    ip redundant-interface 1 172.19.145.181
    ip redundant-vip 1 172.19.145.184
    ip critical-service 1 PING_DEFAULT_GATEWAY
circuit VLAN550
ip address 192.168.50.19 255.255.255.0
    ip virtual-router 2 priority 90
    ip redundant-interface 2 192.168.50.20
    ip critical-service 2 PING_DEFAULT_GATEWAY

Cisco BackUp Interface Operation Failing

OK Experts,
I have made this issue very simple for you guys to help me out.
I have two routers R22 and R23. I have configured the back up interface on R22 to be interface fas 0/1. Everything appears to be working fine. I issue the command show backup and I get the following on R22
r22#show backup
Primary Interface   Secondary Interface   Status
FastEthernet0/0     FastEthernet0/1       normal operation
r22#
Also I get the following:
FastEthernet0/1            10.10.13.2      YES manual standby mode          down
However, when I shutdown interface fast 0/0 to test the back up interface fast 0/1 I get the following:
r22#show backup
Primary Interface   Secondary Interface   Status
FastEthernet0/0     FastEthernet0/1       disabled
r22#
FastEthernet0/1            10.10.13.2      YES manual standby mode/disabled down
So it doesn't work.
Attached are the configs.
I was wondering if someone could help me figure out why this won't work.
Cheers

Hello Carlton,
there are some notes about your tests:
a) the configuration of the primary interface includes two logical interfaces main interface and a vlan based subinterfaces both fail when you disable fas0/0, the secondary interface has only IP configuration at main interface level
from your log files:
interface FastEthernet0/0
backup interface FastEthernet0/1
ip address 10.10.14.2 255.255.255.0
duplex auto
speed auto
interface FastEthernet0/0.1
encapsulation dot1Q 12
ip address 10.10.12.2 255.255.255.0
You should remove the subinterface fas0/0.1 as a minimum to make interface configurations compatible,
b) the specific type of interface you would like to use for backup is LAN based Fastethernet.
The backup command had been introduced for providing a backup interface for serial interface and the secondary interface may be a serial interface or ISDN based ( in this case a DDR call is triggered over ISDN).
The dial backup command reference says that support for gigabit interfaces in C7600 has been later introduced.
see
http://www.cisco.com/en/US/docs/ios/dial/command/reference/dia_a1.html#wp1012054
The use of backup command may be supported or not for fastethernet interface on your routers.
If it is not supported, you can easily implement an alternate solution, because you are running OSPF in area 0 in all router interfaces
router ospf 1
log-adjacency-changes
>>network 0.0.0.0 255.255.255.255 area 0
So all you need to do is to increase OSPF cost on fas0/1 to create a backup path
on R22, R23:
conf t
interface fas0/1
ip ospf cost 50
Hope to help
Giuseppe

Flex backup interface

hey I have cisco 2960 switch I want to ask about flex backup interface configuration on it my ask is that the STP would remove from whole switch or in the interface only !!

Setup your router interface cards such that the interface w/"physical-layer async" comes before the interface it will be used to back up. It will then get initialized before the "backup interface" command.
Implementing dial-on-demand routing (DDR) backup on a router that uses
Network Address Translation (NAT) involves more configuration than is
neccessary for regular DDR backup. This is because the router must translate packets to and from the "inside" network using different "outside" addresses depending on whether the primary or backup link is active." ... "Make sure that your Internet Service Provider (ISP) can provide you with two different IP addresses or subnets. Use one IP address or subnet for the DSL connection and the other for the backup ISDN connection. IP addresses on the two dialer interfaces need to be explicitly assigned and cannot be negotiated during PPP negotiation. This means that the ip address negotiated command is not permitted under the dialer interfaces.
For troubleshooting the 1706 router click this link.
http://www.cisco.com/en/US/products/hw/routers/ps221/prod_tech_notes_list.html

Challenge: Spanning Tree Control Between 2 links from Switch DELL M6220 to 2 links towards 2 switches CISCO 3750 connected with an stack (behavior like one switch for redundancy)

Hello,
I have an Spanning tree problem when i conect 2 links from Switch DELL M6220 (there are blades to virtual machines too) to 2 links towards 2 switches CISCO 3750 connected with an stack (behavior like one switch for redundancy, with one IP of management)
In dell virtual machine is Spanning tree rapid stp, and in 3750 is Spanning tree mode pvst, cisco says that this is not important, only is longer time to create the tree.
I dont know but do you like this solutions i want to try on sunday?:
Could Spanning tree needs to work to send one native vlan to negociate the bdpus? switchport trunk native vlan 250
Is it better to put spanning-tree guard root in both 3750 in the ports to mitigate DELL to be root in Spanning Tree?
Is it better to put spanning- tree port-priority in the ports of Swicht Dell?
¿could you help me to control the root? ¿Do you think its better another solution? thanks!
CONFIG WITH PROBLEM
======================
3750: (the 2 ports are of 2 switches 3750s conected with a stack cable, in a show run you can see this)
interface GigabitEthernet2/0/28
description VIRTUAL SNMP2
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 4,13,88,250
switchport mode trunk
switchport nonegotiate
logging event trunk-status
shutdown
interface GigabitEthernet1/0/43
description VIRTUAL SNMP1
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 4,13,88,250
switchport mode trunk
switchport nonegotiate
shutdown
DELL M6220: (its only one swith)
interface Gi3/0/19
switchport mode trunk
switchport trunk allowed vlan 4,13,88,250
exit
interface Gi4/0/19
switchport mode trunk
switchport trunk allowed vlan 4,13,88,250
exit

F.Y.I for catylyst heroes - here is the equivalent config for SG-300 - Vlan1 is required on the allowed list on the catylyst side (3xxx/4xxx/6xxx)
In this example:
VLANS - Voice on 188, data on 57, management on 56.
conf t
hostname XXX-VOICE-SWXX
no passwords complexity enable
username xxxx priv 15 password XXXXX
enable password xxxxxx
ip ssh server
ip telnet server
crypto key generate rsa
macro auto disabled
voice vlan state auto-enabled !(otherwise one switch controls your voice vlan….)
vlan 56,57,188
voice vlan id 188
int vlan 56
ip address 10.230.56.12 255.255.255.0
int vlan1
no ip add dhcp
ip default-gateway 10.230.56.1
interface range GE1 - 2
switchport mode trunk
channel-group 1 mode auto
int range fa1 - 24
switchport mode trunk
switchport trunk allowed vlan add 188
switchport trunk native vlan 57
qos advanced
qos advanced ports-trusted
exit
int Po1
switchport trunk allowed vlan add 56,57,188
switchport trunk native vlan 1
do sh interfaces switchport po1
!CATYLYST SIDE
!Must Explicitly allow VLan1, this is not normal for catalysts - or spanning tree will not work ! Even though it’s the native vlan on both sides.
interface Port-channel1
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1,56,57,189
switchport mode trunk

I have a 500 GB hard drive and a 1TB Time Capsule running on a MacBook Pro. It was all working well until the MacBook went in for a repair a week or so ago. Since then, TC will not perform a backup; instead, it says the backup is too large for the disk

Since having my MacBook Pro repaired (for a video problem) Time Capsule returns the following message: "This backup is too large for the backup disk. The backup requires 428.08 GB but only 192.14 GB are available."
I notice that there is also a new sparse bundle.
Since TC has my ONLY backup (going back about 4 years) I am reluctant to wipe it and start over fresh as I am afraid of losing files.
Is there a way of dealing with this?
I am using Snow Leopard 10.6.8

The repair shop likely replaced a major circuit board on your MacBook Pro, so Time Machine thinks that you have a "new" computer and it wants to make a new complete backup of your Mac.
You are going to have to make a decision to either add another new Time Capsule....or USB drive to your existing Time Capsule....and in effect start over with a new backup of your Mac and then move forward again.
For "most" users, I think this is probably the best plan because you preserve all your old backups in case you need them at some point, and you start over again with a new Time Capsule so you have plenty of room for years of new backups.
Or, as you have mentioned, you have the option of erasing the Time Capsule drive and starting all over again. The upside is that you start over and have plenty of room for new backups. The downside is that you lose years of backups.
Another option....trying to manually delete old backups individually....is tricky business....and very time consuming. To get an idea of what is involved here, study this FAQ by Pondini, our resident Time Capsule and Time Machine expert on the Community Support area. In particular, study the pink box.
http://web.me.com/pondini/Time_Machine/12.html
Once you look through this, I think you may agree that this type of surgery is not for the faint of heart. I would suggest that you consider this only if one of the other options just cannot work for you.

Item Open Interface giving error for Org Assignment

We ran the MTL_SYSTEMS_ITEMS_INTERFACE & loaded all the items at master level.
We are having issues in setting at Org level. Cant figure out what the issue as only few records gets assigned & then garbage sets in for remaining records. An SR has been raised & the tech support representative was saying that UOM's are different at master & org levels. Never heard of this issue earlier. I have worked with UOM's different at Master/Org levels.
The UOM's are different at Master & Org Level and in some cases the UOM are different for different Orgs. Attribute Control for Primary/Sec UOM is at Org level. The UOM's belong to the same UOM Class. There are standard conversions defined for all these UOMs.
Any pointers for quick resolution ?

Pl do not post duplicates - Item Open Interface giving error for Org Assignment

How do I create a backup DVD OS disk for my new mac mini ?

how do I create a backup DVD OS disk for my new mac mini ?
in case of failure HD etc
no disks came with it

No disk-version of Lion, but a Lion Thumb Drive http://store.apple.com/us/product/MD256
For the downloaded OSX Lion form the Mac App Store you can use this http://www.macupdate.com/app/mac/39701/lion-diskmaker to make yourself a disk.
And have a read here http://www.afp548.com/article.php?story=getting-lion-installers on how-to get/make a machine-specific OSX Lion installer disk.
Stefan

HT4859 How can I restore a previous backup in iCloud storage for my iPad?

How can I restore a previous backup in iCloud storage for my iPad?

Restoring an iCloud backup requires you to first erase your iPad. If you have any newer data that you want to save you'll need to do that first. Then go to Settings>General>Reset, tap Erase All Content and Settings, go through the setup screens on the iPad and when given the option, choose Restore from iPad backup.

Loopback0 vs. "Backup interface GigabitEthernetx/x" for redundance

Similar Messages

Maybe you are looking for