Re: retro-talk #635 - 06/19/00
Luke: Here are two scenarios, I hope one of them meets your needs. Method 1 - automated 1. Back up what's there now (twice :-) to create a new snapshot. 2. Restore the old snapshot using the "Replace Corresponding files" destination setting. (This overwrites new file versions, but doesn't delete new files.) 3. Restore the new snapshot using the "Replace Corresponding files" destination setting. (This restores the new file versions that were overwritten by the previous restore.) Method 2 - manually 1. Preview the restore of the old version using the Replace Corresponding destination setting. Leave the Files Chosen window open with all files marked (checked). 2. Go to ConfigureVolumes and browse the destination. Select All and Copy. 3. Switch to the restore's Files Chosen browser. Paste. All corresponding files will be highlighted. Unmark. 4. Restore. None of the existing files will be overwritten because you're not restoring any of them. Extra credit - automate method 2 using a Saved Highlights selector. (Very scary, try it on a test case first!!! :-) I agree that neither of these is quite as friendly as an setting that says "don't overwrite older files". If neither of the above works for you, let's get in touch and hash it out, then I'll let you report to the list. Best Regards, Paul Mackinney Dantz Development Corporation 925.253.3098 [EMAIL PROTECTED] I'm in the midst of a big workstation rollout and I'm using Retrospect to move data between computers. Here's the scenario -- Users moving from a G3 running 8.6 to a G4 running 9.0.4. I back up each G3 to its own backup file on an external HD. I have a standard profile of system folder standard apps, etc, that I've pre-installed onto every G4, using Apple Software Restore and a custom .img file I created. I want to back up the G3's and restore the files onto the G4's, but I don't want to overwrite newer items with older items. (especially things like "Finder" and "System"). Is there a way I can prevent Retro overwriting corresponding items that have a newer mod date? -- top of the world, Luke Jaeger, Technology Coordinator Disney Magazine Publishing Northampton, Massachusetts [EMAIL PROTECTED] -- -- To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives:http://list.working-dogs.com/lists/retro-talk/ Problems?: [EMAIL PROTECTED]
RE: Stubbornly Invisible Client!
Hi, As one of the senior QA people here at Dantz, I've been asked to reply to this post. Hopefully I can cover most of the issues involved. First, I have to thank Gowan for that last post. I appreciate its pragmatic approach. My intention with this post is to address Gowan's questions, and to provide an overview of troubleshooting an NT/2000 system with multiple NICs. Gowan's questions: 1. Does anyone have the Retrospect CLIENT running successfully on a Win2k SERVER? YES. Absolutely. Here at Dantz we back up Windows 2000 servers via the client every night. 2. Does anyone have the Retrospect Client working on a dual-homed machine? YES. I personally have backed up a client with 2 NICs every night for over a year, using Win NT 4.0 and then Windows 2000 as soon as the first stable beta was available. 3. Are there any known cases of Retrospect Client having port conflicts with other TCP/IP services? Not with other services per se. The client issues we see are almost always to to configuration issues. Each TCP/IP host has an internal routing table. This has to be set up properly. Each network router needs to properly support multicasting and subnet broadcasting. Of course, you could force our software to conflict by setting http (or some other service) to step on our well-known port, but that's an unlikely scenario. Troubleshooting a multiple NIC system: I'm going to cover the simplest case, where your system has 2 NICs and each NIC has one address. 1. The first thing to do is install the client and restart, then open the client control panel. The status should be "Waiting for first access", or "Ready" if the client has ever been logged in. If this fails (for example, the client status might be "(network shut down)") then you need to troubleshoot basic TCP/IP network connectivity on the client. 2. The next thing to do is to try and access the client from Retrospect. If you're using Retrospect for Windows, go to ConfigureClientsAdd and use the Test button. You can enter the client name as displayed in the control panel, the WINS name, or the TCP/IP address. Possible responses are: error -530 - This means that the host wasn't there (eg, ping failed). error -541 - This means that the host is there (eg, ping succeeded) but it's not a Retrospect Client. Found client... with address, name version displayed. If your client has 2 NICS and each NIC has a single address, simply try each TCP/IP address. One should work, and the other should get an error -541. 3. Now it gets complicated. If step 2 succeeded and the client is at the right address, you're done. If step 2 succeeded and the client is at the wrong address, you should be able to edit the BindListener registry entry (see below) to set the address PROVIDED THAT a) The client is running Windows NT or 2000, and b) The address you want to set it to is a fixed (not DHCP) address. 4. If steps 2 and 3 don't resolve your problem, it's time to talk to Dantz Technical support. BindListener Instructions: You must be using NT/2000 and want to force the client to bind to a FIXED address. 1. Use the services control panel to halt the Retrospect Client service. 2. In Regedit, go to HKEY_LOCAL_MACHINE\SOFTWARE\Dantz\Client\5.0 3. Change the BindListener value from "0.0.0.0" to the desired address. 4. Start the client service, open the control panel verify the status is Ready or Waiting for first access. Hope this helps everyone, Paul Mackinney Dantz Development Corporation -- -- To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives:http://list.working-dogs.com/lists/retro-talk/ Problems?: [EMAIL PROTECTED]
Beta testing opportunity
Hi, Dantz is currently looking for beta testers for a new product. We're looking for people who enjoy trying new things, problem solving, and evaluating software. To qualify, applicants should have: - A Windows computer with 32 MB or more that can run Retrospect for Windows. - An Intel-based Linux computer with a reasonably modern Linux distribution. - A TCP/IP network connecting the above computers - An email address where we can contact you. - The ability to download beta software from our FTP site. - The willingness to complete a Non-Disclosure Agreement with Dantz. Can you guess what the product is? If you are interested in participating in this beta program, please complete the following application and email it to me (NOT the retro-talk list!) at [EMAIL PROTECTED] Sincerely, Paul Mackinney Beta Coordinator Dantz Development Corporation [EMAIL PROTECTED] *** Beta Tester Application *** Name: Company: Address: City: State: Zip: email: System info Windows system (CPU/speed/RAM): Windows OS: Linux system (CPU/speed/RAM): Linux Distribution (eg, Red Hat): Linux Kernel version: Backup device info Interface (ATAPI, SCSI, etc.): Type (tape/CD-R/removable/file): Manufacturer/Model: -- -- To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives:http://list.working-dogs.com/lists/retro-talk/ Problems?: [EMAIL PROTECTED]
RE: How can I stop an NT service before backup?
Perhaps this idea will help, its implementation requires only that you can use command-line arguments to halt and restart the server: You have a special script that just backs up the database files that can't be backed up while the server is running. You create a RetroEventhandler.bat halts the server when the special script starts, and restarts the server when the special script finishes. Meanwhile, you have another script that backs up everything except the database files, it runs at any time and doesn't shut down the server. In your case, hopefully the time required to back up a single database wouldn't require too much downtime. Dantz is using this strategy successfully in-house with an NT 4.0 Server and a MySQL database. We're not even shutting down the server, since MySQL has a convenient tool that allows a single command to dump the database to a file without halting the database service. Our RetroEventhandler.bat script simply runs the dump command before backup, the backup script has a custom selector that backs up everything (including the dump) except for the live database files. See the Retrospect 5.1 User's Guide Addendum for a complete discussion of Retrospect scripting events. Best Regards, Paul Mackinney Dantz Development Corporation From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Kraut, David Sent: Tuesday, October 31, 2000 3:02 PM To: 'retro-talk' Subject: RE: How can I stop an NT service before backup? Thanks Ben but like I mentioned, my backups sometimes start at 7:00PM and are still running the next morning when I come in! I am backing up 10+ servers to a tape library and I can't leave the service down for that long of a time -- -- To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives:http://list.working-dogs.com/lists/retro-talk/ For urgent issues, please contact Dantz technical support directly at [EMAIL PROTECTED] or 925.253.3050.
