Unavailable NAS Blocking other Backups
Hello Forum,
I hope you kind souls can assist me :)
I have a Laptop which is sometimes at home, often not. At home I have a NAS, and Acronis set up to do full backups to it. This is all very well.
But I also have recently purchased a 2 TB internal drive that I wish to Backup my O/S (from 256Gb SSD) to even when not at home. But for this (separate) backup Acronis always says that the NAS is not available and backups are cancelled, depsite this backup having an accessible (internal) location. The only way I can see to change this is to remove the NAS backup from the list. But I don't want to do this, as I still want it to backup to NAS when it can and the NAS is available.
- When I try to run the Internal Backup it fails and there is a big red dot in the middle, which, when clicked says "The last backup has failed. The backup cannot be started. Ensure that folder <NAS network location> is accessible." But the destination for this backup is local hard drive!
- Similarly if I try to go to the "Options" button in the Backup (for which both source and destination are local disks) it waits a while then asks me to log into my NAS network location. As I cannot do this my only option is "Cancel". When I click this it offers me a knowledge base article about connectivity issues and then brings me back to the main window.
Can someone tell me where I am going wrong? Do I really have to always have access to a network backup location to even backup from internal drive to internal drive??
Many thanks
Chris
Tom is correct in suggesting that something is amiss. Please provide more information.
The problem may be associated with the absence of a connection to the NAS; you probably need a pre-command that tests for the presence of the NAS. Not something I am an expert on. There is a discussion somewhere on the Forum. Steve Smith will know where to direct you.
Ian
Chris, please see the attached PDF document (written a couple of years back now, but should still be relevant here). This demonstrates how to use the Windows PING command to test for the presence of your network server and decide whether to continue the backup task or abort it. The only downside to this method is if you are on another network which has a device using the exact same IP address as your home network server. In such a case, you could ping your network server by name instead of by IP address, where it is very unlikely there would be another device with that name on the network..
Thanks all for your helpful responses.
@Tom - this is exactly what I would like - for it to be a separate task and for them not to be linked/dependant. I just can't see any way to do this. Can you help at all? I don't mind that the NAS backup will fail sometimes, just the the File Based backup can run independently.
I think my biggest issue right now though is that almost anything I try to do on any of the backup related config screens prompts me to log into the NAS (which is currently offline). For example if I choose "Options" on the File Based backup, or "Move..." or "Validate" from the context menu of the File System based backup (NOT the NAS backup), it asks me to log in to the NAS and when I can't it takes me back out again, so I can't even get to any of the screens I would need to to change anything or to try Steve's suggestion.
Seems like for now I will have to wait until the NAS is available to do anything, or delete the NAS backup completely and add it again later. But I am concerned that this will not "remember" what has previously been backed up.
It does seem like the lack of ability to even enter setup screens without the NAS being available is a bit buggy though. Surely it should let me enter the options screen of the File System based backup without needing the NAS to be on line? Even for the NAS based backup I can't see how Steves suggestion helps to solve this issue about lack of access to the options screens.
All - just to add to this. I think I have solved my issue.
I don't know how or why (maybe because of the way the backup was named very similarly to the NAS backup?) but the file based backup I had setup somehow was corrupted and thought it was linked to the NAS - I created a new one, gave it a completely different name but otherwise set up the same with local source and local target and this one works just fine. Somewhere in the background ACRONIS was thinking that the File based backup I had created was pointed to the same location as the NAS backup. No idea why!
Very strange. Anyway, problem solved as the new backup can run independently, as I would expect, and I removed the problematic one from the list (it still tried to log on to the NAS to do this but let me eventually :)
Many thanks all for your help