Thankfully I’ve never had to rely on my Mac backup, but it runs to an EMC Iomega NAS drive that I have in my house, (which also has all my media on it).
Backup Failed
The backup on “target-name” is already in use.
If I expand ‘details’;
Time Machine couldn’t complete the backup to “target-name”.
The backup disk image “/Volumes/Volume-Name/Mac-Name.sparsebundle” is already in use.
Solution
Now rebooting the NAS drive cures the problem, but (as stated) it’s got all my media on it which is then inaccessible for 10-15 minutes (not good if I’m watching a film, or TV series).
What you need to do is open System Preferences (click the ‘apple’ logo and select System Preferences) > Spotlight > Privacy > Add > Add in the backup volume.
Reboot your mac, (or dismount and remount the backup volume) > problem resolved. For example, below I’ve got a folder called ‘Movies’ mounted and it’s on the same device, If I remove that with the following command, my backup will start almost straight away.
[box]sudo umount -f Movies[/box]
Related Articles, References, Credits, or External Links
My colleague was setting up a DMZ server for one of our clients, it was a virtual server that was presented to the DMZ of a Cisco ASA 5510. Every time he gave it a static IP address it popped up an IP address conflict (no matter what the IP address was).
Windows has detected an IP address conflict
Another computer on this network has the same IP address as this computer. Contact your network administrator for help resolving this issue. More details are available in the Windows event log.
He asked me to set up DHCP for the DMZ to see if that would cure the problem, which I did. However that also refused to work either.
Windows IP Configuration
An error occurred while renewing interface Local Area Connection : The DHCP client has obtained an IP address that is already in use on the network. The local interface will be disabled until the DHCP client can obtain a new address.
An error occurred while releasing interface. Loopback Pseudo-Interface 1 : The system cannot find the file specified.
Solution
Turns out this is a known problem, and is pretty easy to rectify.
Option 1 (On the ASA)
1. Connect to the ASA via command line, log in and then go to enable mode
[box]
Password:******
Type help or '?' for a list of available commands.
PetesASA> enable
Password: ********
[/box]
2. Enter configure terminal mode then disable proxy ARP on the interface that’s presented to the problem network, (in this case the interface is called DMZ).
PetesASA# >write mem
Building configuration...
Cryptochecksum: 79745c0a 509726e5 b2c66028 021fdc7d
7424 bytes copied in 1.710 secs (7424 bytes/sec)
[OK]
PetesASA#
[/box] Note: You can also disable proxy arp in the nat tranlation, with the no-proxy-arp like so; [box] PetesASA(config)# nat (inside,DMZ) source static Inside-LAN Inside-LAN destination static Inside-LAN Inside-LAN no-proxy-arp [/box]
Option 2 (On the affected machine)
Note: This is is for Windows based clients. 1. Start > Run > regedit {Enter}. 2. Navigate to;
