cfieldgate

I guess you could have just added a new drive to your backup set. Retrospect would then just start backing up to the new drive when the old one was full. If the old drive is fine (as in reliable and not obsolete / giving concern) there is no need to replace it with a bigger one. I have several large (>1TB) backup sets across several drives / devices. Perhaps not ideal, but I re-use old hardware where I can.

P.S. I am a Brit living in the UK. Clearly I read too many US technology posts ?

As I said in my post, an AD account isn't strictly necessary - a local account (on the PC running Retrospect) with access to the destination shares (on a Synology NAS?) works just fine. Just make sure the accounts have the same username/password - I even setup a mapped drive to be sure I had access, although I did not use the resulting drive letter within Retrospect. The share Volume I declare by running the Retrospect Client on the NAS (but even that isn't strictly necessary) - you can just set up the Backup Set with the \\NASname\Share method. The key thing is setting up the Retrospect Launcher Service to login with a user account which you define (in your case a local account on the PC) that has access to wherever you want the backups stored, and in Retrospect Preferences set Retrospect to run as the logged in user - which will be the same user as the Retrospect Launcher as it will fire up Retrospect at the appointed time set in your scripts.

I have just checked - in the Retrospect Client on the NAS both Volumes are selected and sub-volumes defined.

Yes, I am accessing the RAID 6 array (source) on the NAS via the Retrospect Client - as it is setup as a Volume. I need to check if I have set the single disk (destination) as a Volume (which would then also use the Retrospect Client) or whether it is simply accessed via SMB (v3 or v2, as v1 is disabled for security reasons). As my NAS is a DS1817+ I doubt the (4 core) CPU is being overloaded, but I guess its possible.

Nope, no Windows Server here. I am running Active Directory on my Synology NAS courtesy of Samba. Retrospect runs on a Windows 10 Pro PC, not on the NAS (obviously, as the NAS is Linux based). So i think even using a local account (which I used to do) will work for you. The reason for my using an AD account is simply to provide central management of accounts and their access privileges in my home lab.

Haggis999, Perhaps I have misunderstood your thread , but I use the Retrospect Launcher to fire up Retrospect every day to run my scripted backups regular as clockwork. I have set Retrospect Launcher service to login as an account I have set up for backups in my AD (i.e. a non-local account) which has access to my NAS shares used for backup storage, and not as the default System account. I also have Retrospect set to run as the logged in user - which when automatically launched (by the Retrospect Launcher) will be my designated AD account. I have no UAC issues and have no need for a link in the startup folder. This has worked in ever yversion since 7 that I have purchased (I have missed out several along the way).

Many thanks to you both for replying - your advice is noted and appreciated - and has given me other reliable / trusted options to try. I have a SATA removable drive bay in one PC which I can use (and a CD drive), so I wasn't planning on going USB, and I have other NAS boxes to copy the recovered files to. I will of course test my solution thoroughly before relying on it. The Linux live CD approach sounds like the best option for me. But I will also try out the Paragon driver https://www.paragon-software.com/home/linuxfs-windows/ as an academic exercise (a free 10 day trial licence is available).

Hi Scillonian, To explain - my NAS is both a destination for PC backups and a source for my photo archive backups - hence installing the client on it (although I know this is not strictly necessary). I have a dedicated PC that runs backups and Retrospect. It has a number of local disks to use for backup storage, but also my NAS. The error pops up on occasion, but not always. It didn't today but it did yesterday. No files had been added on either day. For this backup it is both the source and the destination - one volume being the source (RAID 6, 5 disks) and another volume (1 disk) as the destination. It is this 1 disk it seems to have a problem with 'finding'.

Hi, I have put a new drive in my NAS (single disk volume) and have recently been getting this message: Backup Set member "7-Backup - Archive": error -1116 (can't access network volume) However, the backup says it completes with no errors or warnings! I do get an email with this message: Script zBackup - Archive (Maggie): waiting for media I am running Retrospect 15.1.2.100. The NAS is running a Linux client 15.1.2.101.

Hi, A simple question I couldn't find a direct answer to. I have a disk formatted in BTRFS housed in a Synology box (as a single disk volume) which I use for Retrospect backups. If the Synology box fails, but the disk is fine, can I restore from the disk if I put it in a Windows 10 PC with a read-only BTRFS driver (Paragon)? Basically,, does the Retrospect Restore capability require Write access to the storage mediocre or not?

Thanks Lennart. I feared as much. It looks like I will need to find an appropriate time to fit this in.

Hi, I have recently installed a new production server (NAS) to hold my >6TB of image files. The old sever is now to be used as the primary backup server. I used rsync to copy the files across so the modified dates / attributes have been retained but the creation dates have changed. Both run Retrospect clients (Linux 64 bit). I also hold a Retrospect backup on another server (without a Retrospect client). This was backed up from the old server that is now designated a backup server. When I now backup up from the new production server Retrospect does not recognise that the vast majority of the files are the same, and proceeds to attempt to backup the entire >6TB! Is there a way around this? It will take >2 days to do a Recycle Backup. I run Retrospect v10.5.0.110 on Windows 10 Pro PC. I run Retrospect as the logged in user with the Launcher Service run under a local admin account - I could not get it to start under a Domain admin account. The backup PC starts from a BIOS timer and shuts down again on completion. PCs / Laptops are fired up using WoL in the Scripts.

OK, thanks Scillonian. I have just tried your suggestion but it didn't work for me. I also tried switching off the Windows 8 firewall but that made no difference. So I am stumped for now.

Hi, A short while ago I rebuilt my backup PC (which runs Retrospect Desktop) with Windows 8 (don't go there, please). As my backups run nightly I don't often use Retrospect for iOS but I tried it today and it no longer connects. I note that when I try to "Add a Server" with the "+" icon it asks for "Server" and "Password". Previously I recall I just put in my backup PC's IP address. So, what password should I be using?