Jump to content

ridgedale

Members
  • Content count

    12
  • Joined

  • Last visited

Community Reputation

0 Neutral

About ridgedale

  • Rank
    Occasional Forum Poster

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi Don, David and abb668b8-e67d-45d2-8fe4-b2a87dc2831e, Thanks you for all your feedback. It is very much appreciated. Firstly to clarify/correct my reference to the speed of the backup: 580Mb/s should have been 580MB/s as David correctly surmised. The version of Retrospect being used is the Desktop Backup 9.02 version. To expand on the reason behind the decision to opt for two 8-week cycles of recycle and incremental backup scripts, some years ago I was responsible remotely for a Windows network that also a similar NAS as a file server. In that instance a PC was dedicated to handling the backups (it did nothing else). The backups had been configured as an initial full backup followed by years' worth of recycled backups. One day the customer informed me that the NAS had failed catastrophically overnight. I can't remember the exact details (Restropsect 6 Professional (Windows) and NAS RAID 5 configuration, if I recall correctly) but ultimately multiple drives in the NAS had failed rendering it dead. The only option available was the daily backups that had been running for years. A new set of drives were ordered and installed, and the RAID reconfigured without any problems. Then came the task of restoring the data. This is where everything became a massive problem. It took over week to restore the user data to the newly configured NAS server from the Retorspect backups. The restore process was glacial and it was evident that Retrospect was checking and comparing every historical incremental backup to find the data to be restored! Following that experience I decided to change to all implemented Retrospect backup configurations so that they run on 8-week overlapping cycles (effectively a 16-week cycle to two separate backup drives) to reduce the retore overhead in the event of catastrophic server failure and still provide the option to recover files going back 4 weeks at a minimum, in essence as follows: Backup1_Week1_Recycle (Sunday) - to Backup1 External Drive Backup1_Week1_Incremental (Monday-Saturday) - to Backup1 External Drive Backup2_Week2_Incremental (Sunday-Saturday) - to Backup2 External Drive Backup1_Week3_Incremental (Sunday-Saturday) - to Backup1 External Drive Backup2_Week4_Incremental (Sunday-Saturday) - to Backup2 External Drive Backup1_Week5_Incremental (Sunday-Saturday) - to Backup1 External Drive Backup2_Week6_Incremental (Sunday-Saturday) - to Backup2 External Drive Backup1_Week7_Incremental (Sunday-Saturday) - to Backup1 External Drive Backup2_Week8_Incremental (Sunday-Saturday) - to Backup2 External Drive Backup1_Week9_Incremental (Sunday-Saturday) - to Backup1 External Drive Backup2_Week10_Recycle (Sunday) - to Backup2 External Drive Backup2_Week10_Incremental (Monday-Saturday) - to Backup2 External Drive Backup1_Week11_Incremental (Sunday-Saturday) - to Backup1 External Drive Backup2_Week12_Incremental (Sunday-Saturday) - to Backup2 External Drive Backup1_Week13_Incremental (Sunday-Saturday) - to Backup1 External Drive Backup2_Week14_Incremental (Sunday-Saturday) - to Backup2 External Drive Backup1_Week15_Incremental (Sunday-Saturday) - to Backup1 External Drive Backup2_Week16_Incremental (Sunday-Saturday) - to Backup2 External Drive I tried some time ago purchasing and testing file transfers using an eSATA adapter connected to a NAS but found that the integrity of the fiel transfers were being compromised. I just felt I couldn't trust the eSATA technology at that time to transfer large volumes of data. The mac Mini unfortunately does not incorporate a Thunderbolt port otherwise that the deicision would have been to use extrnal Thunderbolt enabled drives for the backup storage. It would appear from all the feedback provided that the primary key to Retrospect performance is the specification of the computer dedicated to the backup task with processor speed and RAM high on the list of requirements. In that case the solution would be to either upgrade or replace the macMini as well as upgrade Retrospect. It might be helpful if I provide some log stats to give you all a better handle on the situation as I not convinced the backup of the clients is an issue. I'll do that overnight after the next backup has completed. Thanks again for all your input.
  2. Hi, Currently using Retrospect 9 (MacMini running Mavericks) to backup 10Tb Raid6 NAS (will be doubling if not trebling storage capacity in near future) and 5x clients using 2 separate backup cycles (8-week recycle + daily incrementals) to 2 separate external firewire 800 drives on a weekly rotation. NAS and clients connected with 1Gb ethernet. Recycle backups start at 6:00pm on a Sunday and are not finished when the company users come in on Monday morning. Are there any improvements in the hardware/network configuration that can improve the performance without breaking the bank? An incremental backup of some 70-80Gb of data has taken upwards of 5 hours to complete earlier this morning at a rate of just 580Mb/s. Are there any settings within Retrospect that can improve the performance? Any advice on how to achieve optimum network D2D backup performance would be greatly appreciated. tia
  3. ridgedale

    Unable to Restore Any Data

    Hi CallMeDave, Thank you for your reply. As you will see from twickland's help I have been able to resolve the issue and restore the files. To answer your questions: I was trying to restore via: Restore > Restore selected files and folders Restore > Search for files in selected media sets Yes, I configured the Media Set to store the catalogue file at the root level of the disk media. I thought that if the catalgue files were stored elsewhere links would exist to that effect in the /Library/Application Support/Retrospect/Catalogs directory. Clearly, this is not the case. Point teaken regarding the path decription. I clearly misunderstood the manual. I read it that the Retrospect Console was the application installed on a remote computer to remotely manage and control backups. The catalogue files are located at the root level of the disk media. As I explained in my previous reply to twickland, Retrospect cannot access the directory /Volumes for some reason. I have no idea why. The answer to that question from twickland helped me to access the catalogue files to restore the data. Thanks again for taking the time to reply.
  4. ridgedale

    Unable to Restore Any Data

    Hi twickland, Thanks for your helpful feedback again. I now know why Retrospect cannot see the catalogue files - albeit I'm not quite sure understand why. When I go to Media Sets and click on the Location button, I scroll down to /Volumes but there is nothing listed under that directory. Note: The computer is setup with an Administrator account and a User account. All the backups are run from within the User account. If I open Terminal in the User account type: ls /Volumes I get a full list of the connected servers and external backup drive, as expected. If I check the permissions on /Volumes they are as follows: drwxrwxrwt@. I've no idea why Retrospect can't access the disk unless it has to do with the disks having been configured for Retrospect backup use, which may preclude it from accessing the disks other than from within backup scripts. I take your point about the catalogue files being stored on the backup media. I wanted to make sure they were automatically copied to the media as a backup off the computer. The solution was simply to move the catalogue files to the /Library/Application Support/Retrospect/Catalogs directory and use Media Sets > Locate to access them. I hope this also updates the backup scripts. I'll build a shell script to backup the catalogue files after the backups are completed so that a backup is on the disk media as well. Thank you for all your assistance. Much appreciated.
  5. ridgedale

    Unable to Restore Any Data

    Hi twickland, Many thanks for your reply. I tried rebooting the Mac Mini but that made no difference. I've also tried manually stopping and restarting the Retrospect engine - same result. I'm not using the Retrospect Console, btw. The folder <Mac HD>/Library/Application Support/Retrospect/Catalogs was and is empty. I tried creating a symlink to the catalogue file stored on the top level of the installation media and rebooted the Mac Mini. That didn't work either. When I check the Past Backups the list is still empty. When I check the Media Sets they are both listed and locked (- to stop tampering!) If I then click on the Backups button associated with the media that list is empty too! Question: Is there a way to manually select a catalogue file (- e.g. restored from an archive or backup) and use it to run the restore? Thanks again
  6. I'm trying to retrieve some files from earlier backups which I can see from the logs have been successful, but when I reach the screen requesting Restore file from which backup? the list is completely empty. When I set up the scripts I set the catalogue files to also be saved to the removable drives outside the backup data store directories. The catalogue files are present and are being updated but it appears they are not being picked up by the Retrospect program for the purposes of restoring any data. System Information: Retrospect 9.0.2 running on Mac Mini (OSX 10.7.4, 2.3GHz Intel Core i5, 8Gb RAM) The scripted backups are targetted at two separate removable firewire hard drives which are swapped each week (wk1bkup and wk2bkp) in accordance with the scripts. Any advice on how I can successfully recovery the files needed would be greatly appreciated.
  7. ridgedale

    Error -1019 Not Enough Resources

    I am wondering if anyone else has come across this issue. A customer's RAID server completely failed recently where all the data was backed up to a 500Gb Firewire external drive attached to an XP Pro SP3 workstation (2Gb RAM). I have rebuilt the server in a RAID6 configuration and retrieved all the data successfully. The data retrieval process (Retrospect Pro 6.5.343) took nearly a week however owing to the continuous incremental backups that had been run since setup 4 years ago. Since the reinstatement of the server I upgraded Retrospect to version 6.5.382 on the backup workstation and repartitioned the attached external Firewire drive into two equal partitions in order to setup two separate 4-week backup cycles each starting with a recycle backup followed by twice daily incremental backups. The objective being to avoid such a lengthy recovery process should the server completely fail again. The scheduled initial recycle backup ran without a glitch, however the incremental backups are failing and the following notifications are received: followed after 20 minutes by: When I go to log onto the computer the computer is found to be locked. I then log into the admin account and am presented with the following error message: It appears that the program is unable to access the second partition of the external drive to complete the backup which I do not understand as the drive is always accessible when logged on and has always been accessible albeit as a non-partitioned volume in the past. The subsequent error shows the computer can no longer access the server volumes to be backed up by the next scheduled script. The only thing that can be done at this point is to restart the computer otherwise the machine completely locks up and requires a forced reboot/shutdown. Once the computer is rebooted the failed script will run without a hitch when launched manually. A total of 8 server volumes incrementally backed up in 18 minutes this morning. Any assistance with this would be greatly appreciated.
  8. Thanks for your feedback, twickland. I've switched over to file backup and hopefully this should work fine now. Regards Dene
  9. I've just come across an issue on a server running Leopard 10.5.6 and Retrospect Backup 6.1.230. The scripts have been processing the backups automatically with little or no problems until today. I've checked the backup status today only to find that the current script is requesting new backup media despite there being 1.21Tb of free disk space available on the 2Tb target drive! Is there a limit to size of the Retrospect Data file on any particular volume? (Currently the Retrospect Data file on the target volume is 624.57Gb in size. Any assistance would be greatly appreciated. Thanks in advance Dene
  10. ridgedale

    Error 109

    I'm beginning to wonder if this is an issue relating to the temperature in the server room! Since the end of last week the temperature rocketed and the errors started occurring. When I checked the log this morning - after a relatively cool night and early morning - there was no repeat of the error! I'm going to monitor this and see what happens. Thanks for your assistance - much appreciated.
  11. ridgedale

    Error 109

    I got the following information from the device status window under Configure>Devices in Retrospect: ID Vendor Product Version Driver SCSI-A:0:0 SONY LIB-81 0106 Sony Library (5.02) SCSI-A:1:0 SONY SDX-500C 0204 Sony AIT-2 DC (5.05) Further fuller information: The server is running MacOSX 10.3.9. NOTES = The AIT Lib-81 is attached directly to the Apple G5 server which is backing up the whole local RAID-1 volume. The SCSI card is an ATTO ExpressPCIPro UL3S (Single Channel Ultra3) SCSI card. The driver for the ATTO SCSI card is v.3.20. The version of Retrospect in use is (Mac) 6.0.204. The version of the Retrospect Driver Update is (Mac) 6.3.102 The Sony tape library firmware is version 0106 The Sony tape drive firmware is version 0204 I have already spent a considerable amount of time liaising with Sony and ATTO support to get the backup performance optimised which involved making sure all the associated drivers and firmware were up-to-date - which they now are unless any new releases have occurred. There have been no changes in hardware or software other than the driver and firmware updates which were completed by the end of last month. This problem appears to be intermittent - the last couple of weeks it hasn't been a problem. But it has occurred before! All the backups are scripted backups based on a weekly recycle backup over the weekend followed by incremental backups on each Tuesday/Wednesday/Thursday/Friday early morning. Given the amount of data involved I'm loath to get involved in new backups run manually - can I do this with a subset of the data as a test? Thanks for your assistance.
  12. I have Retrospect v.6.0.204 with Driver Update v.6.3.102 running on a G5 tower server running MacOS 10.3.9 Server and am getting the following error: Error 109 (unexpected filemark or FTP end of file). This is occurring both during both the start-of-week recycle backups and also the incremental backups Could somebody please explain what this error means and how I can avoid/prevent it from happening in future? Thanks for your assistance.
×