DLO Mac client causes system stability issues
We have investigated deploying the DLO Mac client to our iMac/MacBook Pro population, and have run into some severe issues. I'm wondering how unique our experience might be, or if there's a solution that we should try in order to make DLO usable on the Mac platform. The primary issue we've encountered is that the system is unstable if (and only if) the DLO client is running, including in the background. After the client has been open for about 5 minutes, the hardware needs to turn on the fan because DLO is occupying as much processor time for as many cores as are available. As other apps give up processor time to DLO, this causes them to become nonresponsive, and prevents normal use of the computer. During this time, nearly any action within the DLO GUI causes the app to hang/spin, requiring a force-quit. If the GUI if avoided, this app instability only lasts about an hour - at that point, nearly without fail, a kernel panic occurs. This forces a restart, and at next login the process begins anew. We are extremely hopeful that there is a solution to our woes - be that a fix to the client configuration, or an update to the app itself which does not include these show-stopping bugs. Has anyone else given the Mac client a try?673Views0likes3CommentsMigrate server hosting DLO console
Greetings Brain-Trust, I need some of your expert advice on what I believe to be a relative simple project, although my boss thinks the world may come to an end. Let me give you a little background to get you started. Here's the sitch, our Fortune 100 company is splitting into two Fortune 200 companies. The new spinoff wants to take their data with them and untangle it from the original company domain. Yes, it's a huge project with over 4,000 servers to migrate. So right now, there is a Trust setup between domains to allow us to complete the migration(s). In a couple of years though, they will cut the cable and the new domain will have zero access to anything in the old domain and vice versa and they will be geographically separated. I have the DLO Console (DLO Admin Server) running on server DLO1.OldDomain.com and I need to migrate that server to NewDomain.com using MS's AD Migration Tool. The storage location (Network Data User Folders) are on a NAS device, NAS1.OldDomain.com. It appears that DLO is just doing a DNS lookup on the server name which is no problem as that won't change, although the FQDN certainly will. For the time being, the storage location also won't change. Users will have (temporary) access to their network storage location, no matter which domain they belong to. Re-doing all the ACLs on the NAS is not for the faint of heart, but will eventually have to be done. So my question is: what is the best strategy for carrying out this migration? What are the pitfalls? Do things need to be done in a specific order? Here's my plan so far: 1, Migrate the DLO Admin Server. If DLO is doing a lookup on the short DNS name it will find it in NewDomain.com. 2. Ensure that a user can logon (from either domain) and connect to his Network Data folder on OldDomain.com 3. Users won't be migrated as they don't want to drag all the SID history along with them. So we have a script that will run through OldDomain and create corresponding objects in NewDomain. Another script will read through the NAS and provide User.NewDomain.com with the same permissions as User.OldDomain.com Seems pretty straightforward to me. I welcome all comments and suggestions. At this point I'm just trying to get my boss to let me move forward with migrating the DLO Admin Server. How would you do things? Thanks, Greg548Views0likes1CommentHow to migrate the Symantec DLO 7.5 SP1 to a new server with different IP and Host Name.
Hi, Actually i have migrated the Symantec DLO 7.5 SP1 to a new server with different IP and Host Name, by restoring the DLO.mdf and DLO.ldf data files but after migration, the clients are not able to communicate with the new server. And after troubleshooting I found the DBServer name on clients in the registry was remain same(Old Server Host Name). If we change the DBServer Name then the Backup runs on Windows XP, but On Windows 7 machine its not working thereafter client get disabled after changing the DBServer Name in registry. So Please help me to get out of it. Is there any other way to migrate the SDLO 7.5 SP1. Thanks, Ashish Agrawal ACPL Systems Pvt. Ltd.1.5KViews2likes7CommentsTo reinstall the DLO 7.0 on the same server after formating
I have a DLO 7.0 Server on Windows Server 2008 Standard 64 bit. I want to format the server and reinstall DLO 7.0 with all agents and old settings. So what are the right steps to reinstall DLO 7.0 to get back all client, settings and storage. or which files to be backed up for disaster recovery.505Views0likes1CommentDLO updates or upgrades : news and download page
Hello, Is there an article or a page on connect that sum-up all the news and download links for DLO ? We have a page for NBU which is quite convenient, but I wasn't able to find something for DLO. (in fact I've just found this page) http://www.symantec.com/business/support/index?page=landing&key=61042 Are we supposed to receive an email when an update has been published ? Thanks for your help,908Views1like3CommentsDLO 6.1 MP7 compatable with Server 2012?
I can't seem to find anything specific about DLO 6.1 being supported with Server 2012 - the only documentation i can find predates server 2012 so that's not much help. Also need to put Backup Exec on the server, (but not for use with the DLO) i saw a few posts from late last year about this, are you any further forward yet?Solved449Views0likes1CommentWhen will SYMANTEC DLO supports Lotus Notes 8.5?
Recently I deployed Symantec DLO 7 in a customer. Customer's colaboration platform runs on Lotus Domino 8.5 & Lotus Notes 8.5.1. I saw that Symantec DLO 7.0 doesn't support Lotus Notes 8.5 and later versions. In fact, I have serious problems trying to protect Lotus Notes files. I'd like to know when Symantec DLO will support Lotus Notes 8.5. and later. Regards, GoltrekSolved1.1KViews1like3Comments