Reconnect to DDBoost share on DataDomain?

Hi,
Had a fatal disk failure in my lab environment, and all VM's expect vDP (5.5) appliance where lost (actually ran vDP on NFS-share on DataDomain).
So, the only VM I can boot is the vDP appliance.
But, it seems to have lost it's connection to DataDomain, and I cannot find a way to manually add a spesific DDBoost share to the config. Adding DataDomain to the vDP just creates a new share.
The lost VM's are not a big deal THIS TIME, but of course down the road in a real life scenario it would be handy to know how to "remap" on worst case a "fresh" vDP appliance to an existing DDBoost share on the DataDomain array.
Anyone with more Avamar skills that know the command lines for doing this, since there's no way to do this via the GUI.
Thanks!
br
Oivind

Open the Accounts pane of System Preferences, and set it as a login item for your account.
(20642)

Similar Messages

Unable to reconnect to network share after closing finder window

hi there
I have not been a mac user for long - i have a macbook pro - and generally i am getting along fine.
however, I have a NAS box which I has a number of files on it on my home network.
I am able to connect to it using finder by doing cmd+k and selecting it from the list (which I set up at some point). and 'selecting the volume i want to mount' I am then able to browse the share happily and all is well.
However, once I have done what I was doing and then closed my finder window. if i open another finder window, the share does not appear anywhere and I have to reconnect, sadly at this point, after doing the initial cmd+ K and selecting the network share, the particular volume i mounted before is greyed out and I cannot in fact re-mount it at all.
I imagine this is because somewhere, finder still has the network volume mounted, and if I could only find it I could browse it as before.
so i am left with having to reboot, as I simply dont know how to find the mounted volume.
it may be that it is in fact not still mounted, in which case I am stumped.
if anyone could offer some explanation and solution to this, i would be most grateful.
many thanks
nat
ps. having fired up the terminal, it seems that the volume in question is in fact in the /Volumes folder, but I cant seem to find that in the finder.
pps. saying the above - actually as I installed XtraFinder I can navigate up until I have the root level and it is indeed there

I had the same problem. While logged in as root, I can't use an alias or Cmd+K to connect to a server, but it works fine as any other user. I tried the link above and after reading the mount_afp man page, it describes two steps needed to mount a server. Here's what I had to put in Terminal to mount a share called Installers:
The root account does not seem to be getting past the first step when using Cmd+K or an alias to a network share, although this worked in previous versions of OSX.
This problem was not fixed in 10.7.1

Snow Leopard Not Correctly Reconnecting to SMB Shares after Network Interruption

Occasionally, my wireless connection will drop for a fraction of a second. When it comes back up (almost immediately), everything works as normal on my MacBook (Snow Leopard) except for the connections to the shares I have on my Windows 7 box. It shows the root folders and items as it should, but the folders are empty (and even labelled "no items"). Ejecting and attempting to reconnect doesn't work at all (Finder simply hangs). And to make things stranger, the drive I have shared from my Linux box (via SMB also) does actually reconnect properly. This also happens if, for some reason, I need to reboot my Windows box. The only solution I've found is to reboot the Mac. Which, as you might imagine, is a pain if you're in the middle of something. Any clues as to how to address this?
Thanks,
Sam

Renew your lease. Also try resetting the IP's. And unplud the router for a bit and restart it.

Reconnecting to Windows share after sleep

Mac newb here. I managed to get a smb share automount script to work. That connects on startup just fine. The problem is, when the laptop goes into sleep mode, it doesn't reconnect when it comes back from sleep automatically and it causes me problems with iTunes, WS word etc. Stuff starts to be saved locally instead of on the network drive. Any help would be greatly appreciated =)
TIA

You might want to repost this question in the Mac OS X Tiger forums. You will more than likely get better help for this question there as it is not MacBook specific.

NFS shares fail to reconnect after server is rebooted

Hi everyone,
I currently have a File Sharing/Media Box/Torrent/Newgroup box in my basement/theater room. It is basically running as my server for the house. Consequently I have a bunch of NFS shares on it. Previously I was running Ubuntu on a similar box and didn't have this issue. What is happening is that if I reboot the server for whatever reason, the clients do not reconnect to the shares once the server box has rebooted. When I was running Ubuntu, after reboot the shares would just automagically be reconnected.
Both boxes are running Arch Linux if it matters.
Here is the /etc/exports file on the server:
# /etc/exports: the access control list for filesystems which may be exported
# to NFS clients. See exports(5).
/media/video/dlvideo/ 192.168.X.X/24(rw,async,no_subtree_check,no_root_squash)
/media/video/DVD/ 192.168.X.X/24(rw,async,no_subtree_check,no_root_squash)
/media/video/HDVID/ 192.168.X.X/24(rw,async,no_subtree_check,no_root_squash)
/media/stuff/AudioBooks/ 192.168.X.X/24(rw,async,no_subtree_check,no_root_squash)
/media/stuff/Downloads/ 192.168.X.X/24(rw,async,no_subtree_check,no_root_squash)
/media/stuff/Music/ 192.168.X.X/24(rw,async,no_subtree_check,no_root_squash)
/media/mythtv/ 192.168.X.X/24(rw,async,no_subtree_check,no_root_squash)
And here is how I mount them on the client:
192.168.X.X:/media/video/dlvideo /media/video/dlvideo nfs rsize=8192,wsize=8192,timeo=14,intr 0 0
192.168.X.X:/media/video/DVD /media/video/DVD nfs rsize=8192,wsize=8192,timeo=14,intr 0 0
192.168.X.X:/media/video/HDVID /media/video/HDVID nfs rsize=8192,wsize=8192,timeo=14,intr 0 0
192.168.X.X:/media/stuff/Downloads /media/stuff/downloads nfs rsize=8192,wsize=8192,timeo=14,intr 0 0
192.168.X.X:/media/stuff/Music /media/stuff/music nfs rsize=8192,wsize=8192,timeo=14,intr 0 0
192.168.X.X:/media/stuff/AudioBooks /media/stuff/audiobooks nfs rsize=8192,wsize=8192,timeo=14,intr 0 0
192.168.X.X:/media/mythtv /media/mythtv nfs rsize=8192,wsize=8192,timeo=14,intr 0 0
Anyone have any ideas?
Thanks,
Kevin

Hi there,
Have you tried running the SBS specific wizards on your system, namely the Fix my Network wizard and the import trusted certificate tool?
FMNW: http://technet.microsoft.com/en-us/library/cc546095.aspx
Import Trusted Certificate:
http://technet.microsoft.com/en-us/library/cc546059.aspx
I'd start with FMNW, and then try a reboot to test if you're still having issues. If yes, then I'd try importing your certificate with the SBS tool, test again.
After that, you might look at the SBS Best Practices Analyzer results for your server to see if it picks up on a misconfiguration or condition that might be behind this issue.
www.sbsbpa.com
Hope that helps,
-Jason
Jason Miller B.Comm (Hons), MCSA, MCITP, Microsoft MVP

Unable to reconnect afp share - "sosend failed for request" error

I use rsync to synchronize an Xserve G5 (2 x2 Ghz - Mac OS X 10.3.9) from a Windows 2000 Server.
I use a script to reconnect a network share hosted by the w2k server. today system.log indicates the following lines :
Jan 11 11:53:19 XserveStudio kernel: AFP_VFS afpfs UserCommand: sosend failed for request 32
Jan 11 11:53:19 XserveStudio kernel: AFP_VFS afpfs_Reconnect started /Volumes/Studio
Jan 11 11:53:19 XserveStudio kernel: AFP_VFS afpfs_Reconnect: Wrong version 4 or no more attempts 0
I am unable to remount the share with the Finder but I can mount another share of the same server
Any idea ?
Xserve G5 2 x 2Ghz Mac OS X (10.3.9)

i had a similar problem the other day at a client's office. the solution seemed to be to remove a faulty switch between the workstation and the server.
connecting the cat5 directly to an available wall jack allowed the user to reconnect right away. before that, she was unable to reconnect after getting disconnected, and the Finder would hang, rendering the Mac useless.
how does your script connect to the server? do you explicitly use afp://... or some other syntax?

MacBook Pro Retina hangs while opening mounted share or USB drive

I have a Macbook Pro Retina that I just updated to 10.8.2 over the past weekend. Now, when I try to open a mounted SMB share or USB drive, the system hangs completely! I had the system set to auto-reconnect my network shares, so when this started happening the system would hang right after login. I was able to get in with Safe Boot and disable the auto-connect, so at least I can work now, but not being able to use a flash drive is really getting on my nerves. Any ideas?

I just ran a few tests to confirm my suspicion that this is a sleep problem for me and found that my rMBP will restart as soon as it has entered the sleep cycle. Set it to auto sleep after 10 minutes and it will restart at 10 minutes, set it to sleep at 3 minutes and it will restart at 3 minutes. Command it to sleep and it will restart.
So for me at least there is a workaround and that is to set sleep to "never". The display still sleeps but my mac keeps running. So that's not a solution but it is a workaround, and if I want it to shutdown and not restart I either hold the powerbutton or take off the power cable and choose shut down from the dropdown menu (it won't restart on battery power, it'll just shut down).
I hope that helps someone else! And I hope it helps the engineers to diagnose and actually solve the very long running problem for us all..

SMB Netinfo reconnect on wakeup

Hello. I've successfully configured two SMB mounts to my NT server using Netinfo manager. The problem is when my iBook goes to sleep or i disconnect my network it hangs the finder for a minute then asks me to disconnect the two shares. Is there a way to A. prevent this and B. auto reconnect when those shares become available again with out having to restart the machine.

Same problem here. Bluetooth pairing with Apple Mighty Mouse and Keyboard was very erratic in 10.5.x. Especially after waking Macbook Pro from sleep.
Upgraded to SL 10.6.1 and everything was working fine. Then just recently my mice and keyboards (home and office) will not pair.
Sometimes Bluetooth status in the menubar shows the devices as connected, but with no response. If not connected, selecting "Connect" registers positive, but again, without an actual pairing with the device.
In Mouse Prefs, selecting "Setup Bluetooth Mouse..." returns "No mouse found" and continuous "Searching...", even though I'm using the bluetooth mouse!
Turning Bluetooth off then on re-pairs the devices. But problems repeat after next wake from sleep...

Finder is UNSTABLE - especially when SMB shares disconnect

Hello Everyone,
Yosemite is the bane of my existence - it is SO unstable especially Finder.
The main problem I have is that if a SMB disconnect (i.e. I reboot the Windows machine) there is a greater than 50% chance that Finder will hang. Finder seems to be trying to reconnect to the share - unfortunately this causes OSX to bog down significantly and act very strange. I can't even terminate Finder!
Anyone else having this issue? It seems Finder has a lot of trouble handling disconnect scenarios.
Thanks.

Please read this whole message before doing anything.
This procedure is a test, not a solution. Don’t be disappointed when you find that nothing has changed after you complete it.
Step 1
The purpose of this step is to determine whether the problem is localized to your user account.
Enable guest logins* and log in as Guest. Don't use the Safari-only “Guest User” login created by “Find My Mac.”
While logged in as Guest, you won’t have access to any of your documents or settings. Applications will behave as if you were running them for the first time. Don’t be alarmed by this behavior; it’s normal. If you need any passwords or other personal data in order to complete the test, memorize, print, or write them down before you begin.
Test while logged in as Guest. Same problem?
After testing, log out of the guest account and, in your own account, disable it if you wish. Any files you created in the guest account will be deleted automatically when you log out of it.
*Note: If you’ve activated “Find My Mac” or FileVault, then you can’t enable the Guest account. The “Guest User” login created by “Find My Mac” is not the same. Create a new account in which to test, and delete it, including its home folder, after testing.
Step 2
The purpose of this step is to determine whether the problem is caused by third-party system modifications that load automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.
Please take this step regardless of the results of Step 1.
Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode and log in to the account with the problem. You must hold down the shift key twice: once when you turn on the computer, and again when you log in.
Note: If FileVault is enabled in OS X 10.9 or earlier, or if a firmware password is set, or if the startup volume is a software RAID, you can’t do this. Ask for further instructions.
Safe mode is much slower to start up and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal startup may also be somewhat slow.
The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
Test while in safe mode. Same problem?
After testing, restart as usual (not in safe mode) and verify that you still have the problem. Post the results of Steps 1 and 2.

Losing Windows 7 Shares, and my hair.

I have been through this countless times. I have Snow Leopard 10.6.6 on a MBP and windows 7 on a desktop. I have multiple shares on the windows machine that I access from my mac. All of a sudden, when transferring a file over smb, the transfer quits because the data "cannot be read or written" and I am unable to access the shares. When I try to reconnect to the shares I get an error saying
"Connection Failed. There was an error connecting to the server "10.0.10.5". Check the server name or IP address, and then try again. If you are unable to resolve the problem contact your system administrator (Thats Me)."
This problem persists until I restart both the mac and the pc. I use account protected sharing, not guest sharing on the pc but I have tried both with the same result. I have adjusted the 'Network Security: LAN Manager Authentication Level' in windows.
Every 12 months or so I do a clean install on my systems and the problem dissappears. After a period of time that could be 1 day or 10 months the problem returns. I have seen this issue since 10.5 and Vista and it keeps crawling back. Any feedback would be great, but I have probably already tried it.

OK, I solved it. I found an answer at http://alan.lamielle.net/2009/09/03/windows-7-nonpaged-pool-srv-error-2017 that details a registry change that makes windows 7 act more like a server.
Set the following registry key to ’1′:
HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\LargeSystemCache
and set the following registry key to ’3′:
HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\Size

AFP loses it's share points after approximately a day

After approximately a day or so of having the AFP share points accessible (internal harddrives - NOT NAS) when attempting to reconnect to the share points they are no longer available. All I see is the users home folder (if admin account) or the administartors drop box.
Anyone else experience this? I am at a loss.

What version of iPhoto? Is OS X 10.6.8 as you state correct for your OS? How are you seeing the "file size"? what happens if you export one of these photos to the desktop - Exporting From iPhoto
LN

Auto-Mounting Network Shares/Disk Images

Hi,
I'd like to share how I solved my problem with auto-mounting a network disk image/folder share to be used as a custom library/location for Aperture 3.xx. I can now either reference the master photos from the network or have it copy to this disk image volume on the network, although it might be better to have it copy to the disk image volume, so one can move it around as a file later. I researched hard over these forums and internet resources and discovered what I thought was the best way to accomplish this. Initially, I found right away that Aperture doesn't allow you to create a library over your network drive or a home server such as mine, unless it is partitioned/formatted to Mac OS. This wasn't acceptable for me as I also run Windows 7 PCs that need to utilize the network folder shares, as well.
I don't understand why I don't have this problem using iPhoto 2011, and do with Aperture 3.0, which is a far more expensive application. Anyhow, I read a little about NFS, but didn't know how to implement this or if it required the Mac Server and/or a non-built in application, it probably isn't compatible with windows. So, I found that by creating a .DMG disk image file, as a partitioned/formatted Mac OS file in Disk Utility, and saving it to the network folder of my choosing, did the trick.
Steps I used to accomplish this:
-Go to Disk Utility and create "New Image"
-Select format w/ MacOSX Extended(journaled) and choose "single partition/GUID" type (or whatever you want)
-Enter a custom size of your disk image (ex in 1GB or 1TB). Click "Create"
* I created this locally 1st and then I copied it over the network, to the network folder/subfolder on my HP Mediasmart Home Server EX495. I found that creating it over the network took too long and would crash Disk Utility.
-After it's copied to your desired location over the network folder, open Automator.
-choose "Application" workflow, double-click to add "Get Specified servers". Enter location of your server (ex smb://hpserver/)
-Then add "Connect to Servers",
-Then add "Get specified Finder Items". Click Add, and locate your disk image file over the network. (this will automatically add the location path. For ex. smb:/hpserver/photos/aperture_library.dmg)
-Then add "Mount Disk Image".
-Then test workflow by clicking on "Run" button on top right of window. If your
Finder->Preferences->General settings on your Mac is set to show "Connected Servers" on your desktop, your disk image will appear on you desktop.
-Finally, save this Application workflow as an application by clicking File menu->Save As. Save this to your documents folder area.
-To have your Mac auto-mount your disk image automatically when you login:
->go to System Preferences->Accounts->your "Admin account name"->Login Items
->click "+" sign and navigate to the Documents folder, to where the Automator application you saved
->click Add. Once done, it will appear on the Login Items area. You can choose to hide it, if you want by clicking the checkbox.
-Now Restart your Mac, and now your disk image should auto-mount.
Hope this helps, as it helped me solve the issue. Too bad one must have to program this and it is not native on MacOSX.

Too many steps. Do this:
1. Go to Disk Utility and create a disk image with the following properties:
Format: Mac OS Extended (Journaled)
Partitions: Hard Disk
Image Format: Sparse bundle disk image
2. Copy the image you just created to the share on the network where it should reside.
3. Open System Preferences, and click on the Accounts icon
4. Select *your account* and click on the Login Items tab
5. Drag the icon for the disk image from the network share into the Login Items list
If a login item is something on a network share, it will reconnect to the share it's located on automatically first.
If a login item is a disk image, the disk image will be opened and mounted.
It's important that the image is a journaled one because if it isn't, being disconnected from it while writing would be potentially disastrous.
It's important that the image is a sparsebundle for two reasons: sparsebundles only take up as much space as they need (e.g., a 1Tb sparsebundle with 100M of data takes up about 100M of space), and they also break the disk down into smaller files. If the underlying filesystem on your network share is FAT32, then no file can go over 4Gb. If you use a sparsebundle, of course, there's no practical limit to how large the disk image can get. Also, it can speed up certain types of backup procedures.
I suggest using partition type "Hard Disk" instead of "1 partition GUID" because, as a disk image, there's no sense in having a partition table or making it bootable (because you can't boot from the image).

Network shares get unmounted after wake up

Hi all,
I have all my music in a network shared drive (AFP share), and in Lion, once mounted from Finder, it would stay like that even if the iMac went to sleep.
With Mountain Lion, it seems that when the Mac goes to sleep, all mounted shares get unmounted when the system wakes up, which is very unconvenient with Apple TV.
Is there any way to return to the old behaviour? Is this a bug? Or a new feature?
Thanks
Christian

Strange thing is that the network share is not actually unmounted. Listing the volumes in terminal (ls /Volumes) shows my 'Media' SMB share (displayed as 'Media-1', don't know why, and that is probably a part of the problem) and I can browse it or whatever. iTunes also works fine. The share simply disappears from the desktop after a longer period of time.
Once I reconnect to my share through the Finder, ls /Volumes shows both the 'Media' and the 'Media-1' share, which is actually one and the same SMB share listed under two different entries.
Also, when the share disappears from the desktop, all the paths of the files in iTunes change to 'Media-1', but upon reconnecting the share and relaunching iTunes, everything gets back to normal and the paths lead correctly to the 'Media' share.
Weird.

Network Shares Disappear on Wake From Sleep

I recently got a Mac mini to replace an aging Mac Pro. I copied all my data over and everything is running great, and much faster overall. But I'm having one strange bug. When I put my Mac mini to sleep, it wakes up and all of my network shares are gone. I have 4 shares I keep connected all the time, and many more I use occasionally. All of these servers are Macs. I never had an issue like this on the Mac Pro, in all it's years of service. Including the time it was running 10.8. But now, the mini dumps shares - I think every time it goes to sleep, if not, almost every time. It's a real hassle having to reconnect to each share every time you wake up. Plus it's no fun having open documents dissapear either. My network settings are pretty simple, my primary connection is gigabit ethernet. It's first in the "service order" list. I also have airport enabled but not connected. I leave it on so my computer can have location serivces. This is all exactly the same as the setup in the old Mac Pro.
Any ideas?

If you must put your computer to sleep, you could use an applescript to re-mount your network shares when you wake it up.
tell application "Finder"
mount volume "afp://servername.local/sharename" as user name aUsername with password aPassword
end tell

File locking with OSX Server & Microsoft Word

We have a small office LAN based on a Airport Extreme bases station. Periodically Microsoft Word reports a break in connection to the shared folder where we store documents to get disconnected. When that happens and the user reconnects to the share, the user gets the file read-only message for the Word document that was open at the time.
I have found that in order to clear the read-only flag, I have to restart the server and open the Word file on the server with the ID of the user who was editing the file on the remote computer. Only that seems to clear the file locking that causes the file to be read-only.
I cannot figure out a less drastic way to release the lock file. I don't see any hidden temp files in the same folder as the document that is locked for editing found by ls -a or in the root direction of the shared folder in the .TemporaryItems/folders.<UID> that seems to be holding the lock.
I have run chflags nouchg <Word file> from Terminal, but that seems to have no effect either. I also used xattr to see if there were any locks held that way, but I don't see anything that way either.
File sharing to Macs only, which are configured just to use AFP through OSX Server.
Does anyone understand how the file locks of Word documents can be released directly with out restarting the server?
I should add that the underlying problems seems to be WiFi related. The behavior is that the WiFi connection seems to break long enough that the shared volumes disconnects. Outlook also causes a break. This behavior seems to have started with 10.9 and the purchase of new Retina Display MacBook Pros. I turned off AppNap on the Office applications but that is not clearly helpful. I also have been told the problem seems more likely to occur when Word is open in the background and another program like Outlook is in the foreground.
Any suggestions appreciated.

Apple write an operating system and also produce file sharing software as part of that to be used as a file server. Apple provide documentation for third-party software developers on how they should write software to work with Apple's software and also give those developers early access to new versions so those third-party developers can test and if needed make adjustments and issue updates to cope with any Apple changes.
Some third-party developers are good at dealing with this, some are bad, and some totally ignore what Apple does and give the impression they don't care if their product works properly or not. I think we can all judge where Microsoft sits.
It appears Microsoft have never paid any attention in particular to how Apple expect file-locking to be handled when accessing files on a Mac server. There have been problems for years and years and years with Office. Two other problems I have seen which seem different to yours but probably related are -
With Office documents it is supposed to be possible for more than one person to edit the same file at the same time, consider it a miracle if this actually works
With Office in particular Word, there is an auto-save function, unfortunately the way this seems to be implemented it seems that Word creates a new temporary file each time it auto-saves the document and keeps all the previous temporary files open still, this eventually means potentially over a hundred temporary files are open - just for one Word document and you can then hit a limit on the total number of files you are allowed to have open at the same time. At this point further auto-saves fail, and you also encounter great difficulty doing a real full save of the document.
I do not hold Apple completely blameless over this issue, it is likely their file-locking implementations change too often, and have inadequate documentation, however even considering this a company the size of Microsoft with the amount of sales (and profit) they derive from Office for the Mac has no excuses at all for failing to put the effort in to resolve any such clearly critical problems.
We could go on and on about other areas where Microsoft don't play by the (software) rules. Even in Windows Office does not obey the standard print dialog rules Microsoft specified themselves!
Unfortunately not only is Office for Mac upgraded infrequently, but even when new paid for upgrades are released Microsoft have a history of still not fixing bugs. It goes without saying that a mere free update is even less likely to actually fix a bug, typically such free updates only address security issues. The next version of Office is going to be Office for Mac 2014 see http://www.macworld.com/article/2106643/microsoft-will-release-a-new-version-of- office-for-mac-this-year.html
One area I confidently predict Microsoft not to resolve in Office for Mac 2014 is that fact that Word for Mac still does not support right-to-left languages like Hebrew and Arabic. This is despite the fact that OS X itself has supported this for years and years, and despite the fact other Mac programs support this including the free TextEdit and Pages - both of which can read Word files. Some people may remember that at one point the Israeli Government temporarily banned all Microsoft software over this issue. See http://apple-beta.slashdot.org/story/03/10/15/2215249/israeli-government-suspend s-microsoft-contracts This issue goes back over TEN years!!
I note that Microsoft has now taken their OfficeForMac blog offline, probably due to the weight of criticisms. I would not say it is due to out-right anti-Microsoft hate, that war ended long ago. We just want products that work. I myself do use Microsoft products, even at home - where they are the best solution, so I use Microsoft Media Center for example. Sadly this is now being neglected by Microsoft.

Reconnect to DDBoost share on DataDomain?

Similar Messages

Maybe you are looking for