Jump to content

IrenaS

Members
  • Posts

    968
  • Joined

  • Last visited

Everything posted by IrenaS

  1. Even easier: let Retrospect do it for you! While you have the volume mounted, go the Retrospect's Configure Volumes screen. Highlight the server, and from the volumes menu at the top of the screen, select "Configure" and enter your user name and password. Retrospect will automatically mount the server volume when required for backup and unmount it at the finish. Irena Solomon Dantz Tech Support
  2. As it says in your forum Welcome message, this is not an official means of contacting Dantz support, and if you have an urgent issue, you should contact us by phone. That said, the moderators of the forum are Dantz employees, and do post here (in this thread, in fact!) Irena Solomon Dantz Tech Support
  3. How are they formatted? If you get properties on the destination drives, how much space is available? Is this the first backup or is it an incremental? Note that you can get an error 102 if there isn't enough room on the destination drive, or if the file size is approaching the maximum file size allowed on the drive. FAT drives limit files to 2 GB, FAT 32 drives limit files to 4 GB. NTFS drives have a file size limit of 1 terabyte. If your backup set approaches this limit, you can see this error. Irena Solomon Dantz Tech Support
  4. To check that you can boot from a CD, first just try it - put the CD in the tray and restart your computer. If you restart and get a message telling you that you are in Retrospect disaster recovery, you know the CD can boot your computer. At this point, just quit the disaster recovery and restart your computer normally. If this doesn't work, try booting from a Windows CD or other bootable CD. Irena Solomon Dantz Tech Support
  5. It sounds like you've scheduled a New Media backup in your script. This type of backup (instead of a Normal incremental backup or a Recycle backup) creates a NEW catalog file, appending three numbers to the end of the name (beginning with 001 and increasing with each set) and asks for a new tape. It basically creates a second whole set, in the event you'd want to take one backup set off site, or introduce a brand new set of tapes. If you'd prefer not to have a New Media backup in your script, edit the schedule from Automate: Scripts. Click the schedule button in your script summary window and any change any schedule that is currently a New Media backup to be another type of backup. Irena Solomon Dantz Tech Support
  6. The verify phase of a backup doesn't just look at the files on the CD, but it goes in and makes checks against the original files on your hard drive. A fragmented hard drive or other problems affecting access to that data might cause slow verifies. If you have software compression on, this can also slow down your verification. Device, communication and media problems can affect verification speeds as well. Irena Solomon Dantz Tech Support
  7. You can enable it, but Retrospect must be left open to be able to start a scipt at its scheduled time. Retrospect cannot launch to run a script, but it can run a script at its set time if the program is open. Irena Solomon Dantz Tech Support
  8. No, as long as the tape you leave in the drive is erased. Unattended mode (which is how Retrospect runs when it auto-launches and runs a script) means that Retrospect will automatically seek out a blank or erased tape and use it. It will only ask for confirmation if you are running in Interactive mode (such as doing an Immediate backup). Irena Solomon Dantz Tech Support
  9. Go to Configure: Backup Sets, double-click your backup set and go to the members tab. There, select the 5th CD and mark it as missing. Next time you do a backup, Retrospect will try and copy and files that were on that 5th CD again, and once it has your backup will pick up where it left off. Irena Solomon Dantz Tech Support
  10. What tape is it asking for? If it is asking for the second tape in a set (this will be 2-[your backup set name]), then it is unable to use the last tape for some reason. There are a few possibilities. The tape may have filled up, or the tape could have gotten a hardware error and Retrospect deemed the tape no longer useable. Open your Operations Log and look for any errors. From the main Retrospect directory, click Configure: Devices - does the tape show up properly? Is the name correctly reported? Check that the tape that you have in the drive exactly matches the name of the tape that Retrospect is asking for. Is there any discrepancy at all? Irena Solomon Dantz Tech Support
  11. Retrospect doesn't transfer the snapshots to the local machine, so limited disk space on the computer running the application is unlikely to cause an error -519. If the computer that you are backing up is running low on disk space, there's a possibility that the disk is highly fragmented. Disk fragmentation slows access to data and can cause a -519, but it's not the first factor I'd be likely to suspect. Have you gone through some of the other troubleshooting in the -519 Tech Note? Irena Solomon Dantz Tech Support
  12. Backup Server backs up to whatever backup set it thinks a volume needs to be backed up to most - that is, the set to which it was backed up to least recently. If all sets are available, it will operate by this logic alone. It was operating by the same logic before when backing up to tape, but you effectively were able to control this by putting in only a single tape. Backup Server might have been saying "I'd prefer to back this volume up to Backup Set A, but it's not available so I'll just use this tape in the drive that belongs to Backup Set B." Since all your backup sets are available, Backup Server will back up to each as it sees most appropriate. There's not way to control this in Retrospect without using a regular backup script. If you're familiar with AppleScript, you could experiment with a script that mounted or unmounted certain volumes at certain times. A regular backup script (not backup server) will also allow you to designate EXACTLY which backup set your data goes to, but of course you lose all the flexibility that likely led you to a Backup Server script in the first place. Irena Solomon Dantz Tech Support
  13. It will! Better hard drive backup is coming in future Retrospect releases, for all the reasons you cited! Irena Solomon Dantz Tech Support
  14. You can either create a script from scratch, or you can just create an EasyScript and modify it. I've included instructions here on how to start with an EasyScript and then customize it to back up to your hard disk. 1. Make an EasyScript backup that suits your needs and pick any other medium for your backup, letting Retrospect create these other backup sets. Save your EasyScript. 2. From the Retrospect directory, click Configure: Backup Sets. Click Create New and make two new File Backup sets, named whatever you like. Make sure you're saving them in the right location (if you have an external drive, be certain that the file is being saved to the external drive and not the local one). Once these have been created, click Cancel to exit the backup set configuration window. 3. You should be back in the main directory. Now, click Automate: Scripts and select the EasyScript you created. Click the Destinations button and you'll see the two sets Retrospect automatically created. 4. Click Add, and you can use the command or control key to select the two file backup sets that you made. Click OK, then click OK again. 5. You should now be back in your script summary window, with four sets in the destination section. Click Schedule to change the sets that you're backing up to. 6. Decide which set will replace which. For each schedule, double-click it to modify, and change the set that it's going to at the bottom of the screen. Once you've done this for all the schedulers, click OK, return to the script summary window, and save your script. 7. If you like, you can now return to the Configure: Backup Sets window and "forget" the two old backup sets that Retrospect created. It's a good idea to click Preview from the Automate tab, just to be sure that the executions are scheduled as you expect. If not, make any changes by editing the script. Hope this helps! Irena Solomon Dantz Technical Support
  15. There are two errors here, and they aren't actually related. 1. The -1020 error. This is a result of GoBack being active, sice the operating system keeps that file open. Disabling GoBack will prevent this problem. 2. The second error, -100 (device rejected command), is returned from your drive and may indicate a problem with your media, your drive, or the communication to that drive. Try running a verification from Tools -> Verify (at the Retrospect main directory). Do you get the same error? If so, try some device troubleshooting. It could just be a bad CD, it could be that your drive doesn't like the brand of CD, or it could be a hardware problem. Search the Knowledgebase for error 100 for detailed troubleshooting steps that apply to your configuration: http://www.dantz.com/index.php3?SCREEN=knowledgebase Irena Solomon Dantz Tech Support
  16. 1. Reformat the drive as NTFS. 2. Break up your backup between several File Backup sets that can remain within the FAT32 limit of 4 GB. 3. Use the Duplicate feature in Retrospect, which is not constrained by these limits. 4. Wait for an update to Retrospect that fixes this. As I said, this is certainly being addressed by our development team. Irena Solomon Dantz Tech Support
  17. The hardware database does not reflect OS X support because device testing under OS X has not been completed yet. When the 5.0 product ships, the database will be updated accordingly. Best Regards, Irena Solomon Dantz Tech Support
  18. Hello, The "Disk Busy" message means that there is something else preventing Retrospect from accessing your backup destination during your backup. To prevent this error, ensure the following step have been taken: 1. If your backup set is a Removable set, ensure that you have stored the catalog file on your local hard drive, not on the removable disk itself. 2. If it is a removable disk, turn File Sharing off so that the Mac OS will allow Retrospect to erase the disk. 3. If you are using a file backup set (if your are backing up to a Firewire hard drive, for instance) try choosing only your local hard drive as your source instead of "Local Desktop Container." If Retrospect is trying to back data up to *and* from a disk at the same time, it will report an error. Best Regards, Irena Solomon Dantz Tech Support
  19. I'm sorry that you've been so frustrated with Retrospect. Hard drive backup for very large volumes will be improved a future release of Retrospect, and the limits of the partition format will be addressed. It would probably be possible for Retrospect to check the format of the drive and issue a warning, but we'd prefer to just take a different approach to file backup sets that aren't constrained by the limit in the first place. Your User's Guide probably doesn't list this limit, but it certainly will be added. In the mean time, we have documented it in the Knowledgebase and in documents that discuss hard drive backup. Best Regards, Irena Solomon Dantz Tech Support
  20. How is the drive that you've saved the backup set to formatted? File backup sets can be limited in size by the format of the drive they are saved to: FAT: 2 GB FAT 32: 4 GB NTFS: 1 TB With compression, it's possible that your backup set was approaching the 4 GB limit. If not, how large has the file backup set grown? Is there other data on that drive? Best Regards, Irena Solomon Dantz Tech Support
  21. [Also posted under "XP and 5.6"] What kind of a hang was it? Were you able to stop the backup? Quit Retrospect normally? Did you have to force quit? Did you have to restart the whole system? Is the device that you are backing up to one that we have fully qualified? See the Device Compatibility guide to be sure that your device is supported: http://www.dantz.com/index.php3?SCREEN=compatibility_list What kind of device are you backing up to? Try a test backup to a file backup set stored on the local hard drive. If this completes without errors or hangs, it points to a problem with your backup media, device, or device communication. For detailed troubleshooting, see the correct device troubleshooting document in the Knowledgebase for your device and interface: http://dbs.dantz.com/faq/ If the hang persists even to a file backup set, this points to a problem with the data or source that you are backing up. Try running disk utilities on the drive. Try running a backup while no other processes are running on the computer to check for a conflict. Note that virus software and crash protection software can sometimes conflict with Retrospect, so try disabling these. If you are still having problems, gather as much information as you can and contact Tech Support for one-on-one assistance. Best Regards, Irena Solomon Dantz Tech Support
  22. 5.6 is fully compatible with Windows XP, so with a bit of troubleshooting you should be able to identify the problem and fix it. What kind of a hang was it? Were you able to stop the backup? Quit Retrospect normally? Did you have to force quit? Did you have to restart the whole system? Have you seen this hang more than once? If it happened once but has not reproduced, it may have been an intermittent problem with your backup media, device or computer. If the problem is reproducible, continue troubleshooting. Is the device that you are backing up to one that we have fully qualified? See the Device Compatibility guide to be sure that your device is supported: http://www.dantz.com/index.php3?SCREEN=compatibility_list What kind of device are you backing up to? Try a test backup to a file backup set stored on the local hard drive. If this completes without errors or hangs, it points to a problem with your backup media, device, or device communication. For detailed troubleshooting, see the correct device troubleshooting document in the Knowledgebase for your device and interface: http://dbs.dantz.com/faq/ If the hang persists even to a file backup set, this points to a problem with the data or source that you are backing up. Try running disk utilities on the drive. Try running a backup while no other processes are running on the computer to check for a conflict. Note that virus software and crash protection software can sometimes conflict with Retrospect, so try disabling these. If you are still having problems, gather as much information as you can and contact Tech Support for one-on-one assistance. Best Regards, Irena Solomon Dantz Tech Support
  23. Windows clients may be backed up when the user is logged out under all supported systems, including 98, 2000 and NT. Mac OS 9 clients running in multi-user mode must be logged in to be backed up. Best Regards, Irena Solomon Dantz Tech Support
  24. For full OS 9.x compatibility, upgrade to Retrospect 5.0. Irena Solomon Dantz Tech Support
  25. Each time a Retrospect Driver Update is released (about once a month), the hardware database will be updated as well. We make every effort to test and qualify new drives as quickly as possible while still ensuring complete reliability. As the testing process can be lengthy, though, there will always be a bit of a lag time before a drive that's available to the public can be qualified for use with Retrospect. Recent focus on OS X support has also meant slightly longer qualification times. This particular drive is in the testing process; please check back periodically for further information. Best Regards, Irena Solomon Dantz Tech Support
×
×
  • Create New...