Backup logic?

If the drives are simply spun down during inactivity, then there should be no issue with backup - they should simply spin up again when the backup starts.

This is not the same as sleep mode. The CPU is still running as normal when the drives are spun down.

On the other hand if the NAS is actually in sleep mode, or is powered up/down on schedule, then you do need to make sure it is awake/running at the right time.

StephenB,
Somehow I just knew that when I used the word 'sleep' I would get hammered. No harm, no foul. My bad.
I do not believe that I ever PUT any of NAS' to 'sleep.' They either run fully up, or, I use RAIDAR to turn them OFF.

I just really allow the NAS' to power down their hard drives after 30 minutes of inactivity. My NAS' act as storage cells; and their only activity is directly by me moving files to them or away from them. I do not run any add-ons that may/may not read/write to my NAS' auto-magically without my knowledge. I do accept that my NAS' communicate with NG. I do not know what this communication is, but I do see it from time to time in my Router logs. Fine. Phone Home. Other than that, I feel reasonably safe and secure.
I am now to the point of backing up my primary NAS [C] to perhaps , or [A]. I have a print-out from Papa Bear. I am still studying it. Yes I am slow, perhaps.

Thank you - starting a backup job will not fail because the drives an a target NAS are powered down. Otherwise I would simply use SETUP in RAIDAR to force a Reboot/File Check on the target NAS; and, just wait for it to complete.

That's what I know ATM. I will read this forum for other knowledge.

NASNoob wrote:
...Somehow I just knew that when I used the word 'sleep' I would get hammered...

Sorry, I wasn't meaning to hammer you - I just wanted to cover both scenarios to make sure you got the info you needed.

StephenB,
Thanks. That is sort of how I believed the logic worked. My NAS' run hot 24/7; even though I allow the hard drives to 'spin down.
' when not in use'. I will go forward with your counsel for now. :D
I tried the backup logic, but could not get it to work. :oops:
So, I just did a real-time copy from [C] to [A]. Done! [C] is now backed up; sort of. :D
More study for sure.

How did frontview backup fail?

StephenB,
Sorry to say, but the Frontview backup did not fail simply because I got lost/confused in the setup selections. So, I just quit Frontview and went back to my Windows Net Neighborhood. I opened a link to NASc and a link to NASa. Then I just copied the shares on 'c' to 'a'. Yes, this did take a very long time; but, I now have NASc 'backed up to NASa.
Today is the 20th and I feel better. Perhaps today I may try Frontview again to backup 'c' to 'b'.
Do you ever suppose that Netgear will ever give us a "Backup NOW!' button? :(

The backup button on the physical NAS can be programmed to run a user-specified of backup jobs. Though there's no way to "press" this remotely in Frontview.

StephenB,
Oh darn! I completely forgot about the 'backup' button on the NAS. I have never used it! OK, I am a goof! :oops:
But still I need to play Frontview to create some sort of 'backup profile' correct?
After I get past this question, I will review past instructions about initial backups, followed by kinda sorta 'incremental' (just new since last full backup of files) backup.......... :?
Sorry, I am starting to walk/talk on thin ice again.

NASNoob wrote:
....But still I need to play Frontview to create some sort of 'backup profile' correct?...

Yes - first you need to create a backup job. You can then either run it on a schedule, when you press the backup button, or both.