Jump to content

Scillonian

Members
  • Content count

    556
  • Joined

  • Last visited

  • Days Won

    23

Everything posted by Scillonian

  1. Scillonian

    Data deduplication query

    Block Level Incremental Backup only applies to files over 100MB in size. Additionally if the time since the last backup of the file is more than thirty days the whole file will be copied. These rules can be changed and there is a Retrospect Knowledge Base article that covers this. Unless you tell Retrospect to ignore changes to security settings on a file any change will cause the file to be copied even if the content has not changed. (This is an option on Retrospect for Windows and I assume Rectrospect for MacOS has the same.)
  2. I've had this problem too with Windows 10 clean installs. It usually comes down to some driver files and/or registry entries that get installed under Windows 7 and are carried over in the Windows 10 upgrade but are not installed when adding the device to a Windows 10 clean install. Turning off automatic detection and installation of devices in Windows 10 (after installation of the OS but before connection of the LTO drive) and then manually installing the Windows 7 drivers can sometimes work. If the SAS interface and LTO drive are using Microsoft supplied generic drivers try installing drivers from the manufacturer. The generic drivers may lack functionality that is required for Retrospect to detect them. Are you using Windows 10 version 1511 or 1607?
  3. ... and note that RDX devices have been moved to Disk from Removable Disk.
  4. Scillonian

    Emergency Restore of Win7 Boot Drive - Error 625

    The recent versions of Retrospect for Windows changed the Disaster Recovery Media to use the Windows Preinstallation Environment (WinPE). When you come to create the Disaster Recovery media you will be prompted to install the Windows ADK. The Windows ADK provides the WinPE for the Disaster Recovery media. If you choose the online install and want to save some disk space (and download bandwidth) the only part of the Windows ADK you need to install is 'Windows Preinstallation Environment (Windows PE)' and its dependency 'Deployment Tools' for Disaster Recovery media creation. (They are the only part I installed and the Disaster Recovery media appeared to work properly when I did a test restore.)
  5. Scillonian

    Emergency Restore of Win7 Boot Drive - Error 625

    You could try doing a Live Restore as follows: Make a temporary install of the same edition of Windows 7 that existed on the failed backup server. (Ensure the volume containing Windows 7 is at least the same size as the original.) If the installation media is pre-SP1 then use Windows Update to bring it to SP1. If the KB3125574 'Convenience rollup update for Windows 7 SP1 and Windows Server 2008 R2 SP1' was also installed I would recommend installing this too. (I've found this can avoid some restore problems related to Windows 7 itself as I've had mixed results restoring an SP1 system over a pre-SP1 system.) Install your current version of Retrospect. (Full application, not the Client). Add the catalog to Retrospect for the backup set to be used for the restore. (If you don't have the catalog file then a catalog rebuild will be required.) Perform the restore of the entire volume of the backup server over the temporary volume. Follow the prompts from Retrospect. The activities following the reboot to finish the restore can take a long time with periods where nothing appears to be happening. A Live Restore takes longer than a Disaster Recovery Restore but you should end up with a working system in the end.
  6. In this forum have a read of the "RetroClient Linux 11.0.0.107 Test Flight on Mint 17.3 64bit (Ubuntu 14.04)" thread which gives some information on the current Linux client.
  7. Scillonian

    How to create backup to new disk, every day?

    Why are you wanting to back them up to an external drive? Is to protect against the failure of the NAS or to have historical copies of the files and folders? If it is for historical purposes you could use the existing NAS as the destination. Regardless of what backup application you use this will always be the weak link. If you have one person tasked to this job and this job takes priority over other activities then you may stand a fighting chance. It will if the person tasked to change the drive is allowed to do their job without interference. I've seen it happen all to often where something apparently more important comes up so the task gets postponed and before long the day is gone and the drive is not changed. Unless management are well educated backup is seen as a low priority. For any backup to run reliably you need to be certain that the destination for that backup will be there. This is why I suggest the NAS as the destination as you can be fairly certain it will be there each time the backup runs. When you are using external disks can you be certain the needed one will be there? For the monetary investment in all those external drives you could source and provision another NAS for the backups if protection against failure of the production NAS is also required. A small number of external drives will still be needed for the off-site requirements but these can be under your control to ensure reliability. Regardless of what backup application you choose a NAS is the simple solution. As a destination you can be certain it is there. With RAID redundancy, depending on the RAID level used, it can tolerate the failure of at least one disk without data loss. I've been using a NAS as destination for at least ten years and it been basically set and forget
  8. Scillonian

    How to create backup to new disk, every day?

    From Bill Clark's original post this is eleven (11) drives split between two sets of five (5). (Yes, I know 2*5=10 — perhaps 11 is a spare.) Every weekday a disk will be swapped. User has to remember the week of the month and the day of the week. Bill Clark's proposal will require at least ten (10) backup sets if not more. Each one is going to need a script with appropriate schedules. I see the problems arising when after a backup the disk is not replaced with the next one. When the time arrives for the next backup it cannot run because the media is not present so by default Retrospect will wait until the media is present indefinitely. Because the Desktop and Professional versions of Retrospect only have a single execution unit nothing more can happen until the media problem is solved. At this point user intervention is required to supply the correct media to allow the backup to run or abort the backup and ensure the correct media is available for the next scheduled backup so normal service can resume. This is why I like the simplicity of your scheme as a starting point. It is tolerant, within reason, to a late media change and it is easy to identify which is the next media in the rotation.
  9. I've found that it depends how you set the member size — either initially or subsequently. If you set the size using a specific size in GB (e.g. 600GB) then the size will always be that regardless of the underlying volume size. If you set the size using a specific size in % (e.g. 20%) then the size will always be that percentage of the underlying volume. Setting the size as a percentage of the underlying volume can cause problems if you move the member to a smaller volume because the member size will then become smaller because of the underlying volume is now smaller.
  10. Go to Configure > Backup Sets. In the dialog that opens select the Backup Set you want to resize then click the Properties... button. In the dialog that opens click the Members tab. Select the Member you want to resize the click the Properties button. In the dialog that opens use either of the Use at most boxes to enter the new size for that member. Click the OK button to apply the change.
  11. I'm wondering if you've found a bug in Retrospect. I think your catalog file should be called '03-01-16' from the folder structure on the 6TB disk as listed below: /Retrospect /03-01-16 /1-03-01-16 /2-03-01-16 /3-03-01-16 /4-03-01-16 /5-03-01-16 /6-03-01-16 /7-03-01-16 /8-03-01-16 But the log extract you posted reports the catalog name as '01-16'. A catalog named '01-16' would be looking for the folder structure below: /Retrospect /03-01-16 /1-01-16 /2-01-16 /3-01-16 /4-01-16 /5-01-16 /6-01-16 /7-01-16 /8-01-16 As this folder structure does not exist on the disk then the catalog will be empty. Why Retrospect is using the wrong name I don't know. It must have allowed you to use the name '03-01-16' when the media set was created but there must be something about that name that causes the rebuild to use another name.
  12. Scillonian

    How to create backup to new disk, every day?

    But media management and schedule are linked. The schedule relies on pre-defined media management for it to execute successfully and the user's execution of the pre-defined media management governs whether the schedule works or not. Both have to be considered together. The "I'll sort that out when I need to" approach with backups can cause big problems down the line when a restore is needed. For this to have any chance to work the user in charge of changing the drive must ensure the drive is properly logically disconnected in Windows before physically disconnecting it. Failure to do so can result in the next drive to be connected becoming irrevocably corrupted because the previous drive was not properly disconnected. If you want something simple and reliable with minimal user intervention then the scheme suggested by David Hertzberg is a good starting point. Another potential pitfall of having so many schedules for one script is when one scheduled event does not complete Retrospect will wait until that scheduled event can be completed before moving onto the next event. At that point user intervention is required to get the schedule back on track. Retrospect (Professional or Desktop) on Windows has from my experience the ability to send e-mails for: Application start and exit (Retrospect is a single application on Windows so no separate engine and console.) Media requests (e.g Current media full and waiting for user response.) Backup successful Backup failures (e.g. Network communication problems during client backup.) Backup progress events (e.g. Automatic grooming of a disk backup set during backup to free more space, Windows VSS errors and warnings.) I'm not aware of any way for Retrospect [in Professional or Desktop] to send an e-mail to prompt the user for the media required for the next scheduled event. The nearest you could get would be to habituate on change the media to the next required on receipt of the backup successfully completed e-mail.
  13. If you are using Retrospect 13 a catalog rebuild behaves in a different way than before. Along with the .RDB files on the backup media there will be some .SESSION files. To speed up the rebuild Retrospect uses the .SESSION files to rebuild the catalog instead of sequentialy reading the .RDB files. If you want to force Retrospect 13 to rebuild the catalog by reading the .RDB files then the .SESSION files will need to be deleted before you start the rebuild process. (The .SESSION files will be recreated during the rebuild.)
  14. Scillonian

    How to create backup to new disk, every day?

    I only use a NAS with Retrospect for my backup sets so can't help with regards to media rotation and requests for USB drives. With your proposed scheme it can never be fully automatic because there will need to be manual intervention at the beginning and end of the month to deal with the unused disks. If you go for a schedule which uses a fixed number of weeks and ignores calendar months then the schedule will be simpler and the need to handle exceptions of part weeks will be avoided. Example: Suppose the current month starts on a Wednesday. When you come to MonthWeek3 then the Monday and Tuesday disks will still have backups from the previous month because there was no overwrite of the media in the current month.
  15. Scillonian

    How to create backup to new disk, every day?

    How will you manage the unused disks in MonthWeek1 when the month starts after Monday? Your proposed scheme only allows for twenty-eight days (four weeks) of backups per month. How do you plan to handle the eleven months of the year that have thirty and thirty-one days? Retrospect can handle some very complex schedules. However if you want this to be fully automatic the simpler you can make it the better — especially if you are relying on a user to change a disk daily (and use the right one). What is your make and model of NAS? Some allow for the installation of apps on them to facilitate the backup of data from shares to externally connected USB/eSATA/Thunderbolt drives.
  16. The Retrospect search function is powered by the Google AJAX Search API. If you are using any content blockers in you browser the search box may be missing altogether or there but not functional. If you are using Ghostery then the 'Google AJAX Search API' needs to be allowed. If you are using a script blocker (e.g NoScript on Firefox, ScriptSafe on Chrome) then scripts need to be allowed from 'forums.retrospect.com', 'googleapis.com', 'apis.google.com', 'cse.google.com' and 'google.com'.
  17. Scillonian

    Sign on with iOS app

    For access to Retrospect on a Windows system the password is the password of the user account that Retrospect is running under. If you do not use a password on the Windows user account then you will not be able to get the iOS App to connect. (Well I could never get it to connect without a password being set for the Windows user account.) If you want to use the iOS App you will need to set a password on the Windows user account that Retrospect runs under. Be aware that from my experience the iOS App can sometime take a long time to make the initial connection to the Retrospect backup server.
  18. In this specific case the problem is the interaction of the Retrospect Client, Windows and VMware virtual network interfaces. The Retrospect Client always binds to the VMware virtual interface and ignores any communication to it on the physical interface where the Retrospect server is. From my experience the type of IP address assigned has no effect. From my experience the Retrospect Client, on Windows at least, seems to have problems with binding to the correct network interface when a system has more than one active network interface.
  19. I had exactly the same problem with a system with VMware virtual network adaptors that had an active connection to the host system. This looks to be a specific Windows/VMware/Retrospect combination problem. From my experience as long as the VMware virtual network adaptors remain disabled then Retrospect will follow the DHCP allocated IP address. If you can work with the VMware virtual network adaptors host connections disabled then this is the easiest solution.
  20. Is 'Client A' network connection wired or wireless? Is it laptop/notebook or desktop? Is 'Client C' network connection wired or wireless? Is it laptop/notebook or desktop?
  21. Scillonian

    Retrospect 7.7 hangs while backing up pc

    Sorry about that. For future reference go to Start > Control Panel > Administrative Tools then double click Event Viewer. In Event Viewer's left panel open Windows Logs > Application and look for the entry for 'Chkdsk'. Note that CHKDSK events will only be recorded if it is run from the copy of Windows installed on the disk. If it was run from the Windows 7 install media (or another Windows installation) it will not be recorded.
  22. Scillonian

    What is "thorough rebuild" and how do I change it?

    "Using thorough rebuild" started appearing in backup logs with Retrospect 11 for Windows. I believe this is related to the changes made to Catalog rebuilding in Retrospect 11 for Windows and also the .session files that Retrospect 11 for Windows stores with a disk backup set's .rdb files. The .session files and the changes they relate to are covered in post ".session" files stored alongside ".rdb" files new to Retrospect v13? on the 'Retrospect 9 or higher for Macintosh' board. This is where 'Using thorough rebuild' appears in the log from Retrospect 11 for Windows backup: + Normal backup using Byre Laptop Proactive at 2016-05-13 21:31 Using thorough rebuild 2016-05-13 21:32:00: Finished scanning backup set data files To Backup Set Byre Laptop [B1603]... - 2016-05-13 21:31:59: Copying Pushka Windows 10 Pro (C:) on Pushka-LT Unable to use Instant Scan 2016-05-13 21:38:45: Found: 147,065 files, 27,588 folders, 53.6 GB 2016-05-13 21:38:48: Finished matching Backing up 0 out of 4 files using block level incremental backup, storing full backups for remaining 4. 2016-05-13 21:39:51: Copying: 799 files (2.3 GB) and 1 hard links 2016-05-13 21:42:12: Building Snapshot... 2016-05-13 21:42:16: Copying VSS writer files 2016-05-13 21:42:50: Finished copying VSS writer files 2016-05-13 21:42:56: Copying properties for 27,588 folders 2016-05-13 21:43:10: Finished copying properties for 27,588 folders and 0 files 2016-05-13 21:43:32: Copying Snapshot: 291 files (259.6 MB) 2016-05-13 21:43:45: Snapshot stored, 259.6 MB 2016-05-13 21:43:45: Execution completed successfully Completed: 799 files, 2.3 GB Performance: 965.3 MB/minute Duration: 00:11:45 (00:09:22 idle/loading/preparing) - 2016-05-13 21:43:57: Verifying Byre Laptop [B1603] 2016-05-13 21:44:51: Execution completed successfully Completed: 800 files, 2.3 GB Performance: 3367.0 MB/minute Duration: 00:00:53 (00:00:12 idle/loading/preparing)
  23. Version of Retrospect and platform running on would also be useful too.
  24. Thanks for the system information. Let us have a look at what permissions SYSTEM has on the Toshiba laptop for the following two files: Navigate to the files in Windows Explorer and right click on them and select 'Properties'. On the 'Security' tab select 'SYSTEM' under 'Group or user names:' then under 'Permissions for SYSTEM' there should be check marks under 'Allow' for all entries except 'Special Permissions' which should be blank. Below are links to two screen captures for the two files on one of my systems running Windows 10 Pro: https://onedrive.live.com/redir?resid=64C0D6294A56F2BA!2608&authkey=!AFdUpzEx_S9-pIs&v=3&ithint=photo%2cjpg https://onedrive.live.com/embed?cid=64C0D6294A56F2BA&resid=64C0D6294A56F2BA%212609&authkey=ADqcXp-KgiB89VI (Sorry they are not embedding but I have spent over an hour trying to using various browsers and options without success.)
  25. True. Just assuming no Active Directory because we're on the board for the desktop version of Retrospect. It would help if the Retrospect User Guide noted these account groups only exist on domain computers. Also hasn't told us which edition (Desktop, Single Server, Etc) of Retrospect they are using, which edition or editions (Home, Pro, Enterprise, etc) of Windows 10 they are using and whether clean installs or upgrades from earlier versions of Windows for each machine.
×