HBS3 target QNAP hibernates post QTS .3577 update

[emeljay42]

I have two QNAP devices, the primary is a TVS-873e running 5.2.10.3577 since August 25, and the target is a TS-569L running 4.3.4.2814. the target NAS is typically in hibernation, with a WOL command run weekly just before the scheduled HBS3 jobs from the Primary.

The Target has the power sleep scheduled set to sleep the system daily at 2:am.

The option to “postpone scheduled sleep/restart/shutdown when a replication job is in progress” has been selected.

This configuration has been running for some years without issue.

Now the Target NAS no longer recognises that replication jobs are in progress. The HBS3 app on the target system incoming jobs does not list the recent copies.

consequentially, the Sleep command causes the system to hibernate in the middle of a copy.

Any ideas please?

[NA9D]

I’m not entirely sure of the issue but have you tried re-setting up the scheduled job and connection?

[SteveKo]

We’ll check internally whether any changes were made on the firmware side that could have affected the settings. In the meantime, you may also want to try reconfiguring the settings to see if that restores things. Thanks for your question!

[emeljay42]

Thanks to you both.

I have created some now one-way syncs that mimic older jobs that used to work.

as far as I can see, one of the new jobs works, and shows up in the target NAS (VRSNAS02) as a background task and is also listed in the target HBS3 incoming jobs list - MediaTest via VRSNAS02. this is listed in the target NAS HBS3 incoming jobs list as entry #1

the second new jobs in my example is Copy Media03-01_Current_via VRSNAS02. This job copies files, however the is no recognition in the target NAS interfaces. no background task, and nothing listed in the HBS3 incoming jobs list.

Screen shots show

1 - side by side NAS consoles with second job running

2 - same displays with target nas dashboard in foreground. note the incoming 62 MB/s rate as a result of the active copy job

3 - Job has completed - success listed in source NAS HBS3 Jobs list, No records in the target NAS.

all further guidance gratefully received

Martin

[SteveKo]

First, may we ask whether the sleep issue has been resolved after reconfiguring?

Also, regarding the two jobs you mentioned — aside from the different folders, are there any other differences in their settings? We’ll try to reproduce the issue on our end. If possible, could you also provide a screenshot of your “My Job” page, or the HBS debug log? Thanks!

[emeljay42]

Hi Steve

Yes the problem persists.

To display the settings in the two jobs, I have used edit, then sequentially taken screen shots.

These are all taken from the source QNAP (VRSNAS03) and show a) jobs list b) Storage spaces with the target definition highlighted. The successful job (MediaTest via VRSNAS02) is the third entry, and the ignored job (Copy Media03-01_Current_via VRSNAS02) is the first.

Whenever I run the successful job, it shows on both the source and target NAS job lists.

When I run the ignored job, it only shows on the source NAS, despite data being transferred to the target.

Whilst taking these screenshots I noted two differences

.

a) no schedule vs Scheduled after job xxx

b) network interface - Automatic vs Default Route

by amending the Network interface to Automatic, the job runs and is recognized and reported by the target QNAP (VRSNAS03).

Is this expected behavior for the various network interface options?

[emeljay42]

PS I have screen shots from both job definitions plus the debug logs, if required

[Franklin]

You have 2 remote NAS’s on the same ip. Not sure if this is causing the problem.

[Franklin]

Maybe I didn’t frame that correctly. You have the same NAS listed as a remote NAS twice.

[NA9D]

Well, the thing that I am wondering about is you have an error repeatedly showing in your pics. What is that error? I like to get those resolved first.

[emeljay42]

John - Thanks for your response.
the errored jobs that you mention were being kept as a record of earlier tasks.

Since identifying the cause of my issue, and amending the new jobs, I have subsequently removed the old errored jobs.

[emeljay42]

Hi Franklin

the 2 NAS device that you have mentioned were in place whilst I was debugging.

Since identifying the cause of my issue, I have now removed that associated jobs and NAs definitions.

[NA9D]

So did setting up new jobs then resolve your issue?

[emeljay42]

John,

All old jobs have been deleted with new jobs created. in early testing, the new jobs also failed.

The issue has been addressed by by amending the Network interface from Default route to Automatic.

Now, each job runs and is recognized and reported by the target QNAP (VRSNAS02) which delays the power sleep schedule while a job is running.

Regards