Servers - General

Re: Proliant ML350 G9 Server 2016 connectivity issue with QNAP NAS

 
jkn48336
Occasional Contributor

Proliant ML350 G9 Server 2016 connectivity issue with QNAP NAS

I have a Proliant ML350 G9 running Windows Server 2016 and a QNAP TS-h886 NAS.  

The backups to the NAS device keep failing because the backup software logs show that the destination is not able to be reached.  Says destination path is unreachable.   

I am able to ping the NAS device, I am able to use web browswer to access the NAS,  I am able to map to the storage folder, and the NAS has a valid IP lease and a reservation has been made.  The username and password are correct.  

I have two other servers runnng Server 2012r2 that backup to the NAS device with same software with no failures.

It seems like it might be an operating system issue.  

4 REPLIES 4
KarimBouwmans
Occasional Advisor

Re: Proliant ML350 G9 Server 2016 connectivity issue with QNAP NAS

Hi ,

What smb protocols do your nas supports?
If it's an old one like smb1 theb you have to manually activate this on the os due security risks.

Karim Bouwmans
IT Solutionadvisor
Max ICT B.V.


>Max ICT B.V • Castorstraat 17-27 • 5047RC • Tilburg • The Netherlands

jkn48336
Occasional Contributor

Re: Proliant ML350 G9 Server 2016 connectivity issue with QNAP NAS

The NAS device is set to accept security between smb1 to smb3. 

The odd thing is that the backups are working as files are being written to the NAS, but the backup software when it finishes the job returns an error of destination inaccessible.

AmRa
HPE Pro

Re: Proliant ML350 G9 Server 2016 connectivity issue with QNAP NAS

May I know backup software details?

Also please refer microsoft community form, diccused simialr issue.

https://docs.microsoft.com/en-us/answers/questions/362119/kb5001347-april-2021-update-issue-with-server-back.html

I am an HPE Employee

Accept or Kudo
jkn48336
Occasional Contributor

Re: Proliant ML350 G9 Server 2016 connectivity issue with QNAP NAS

Software is StorageCraft SPX v 7.02

Here is the log for failed job on C:\ drive:

021-07-01 08:30:00 D [7956] apscheduler.scheduler (579): Looking for jobs to run
2021-07-01 08:30:00 D [11916] apscheduler.threadpool (69): Started worker thread
2021-07-01 08:30:00 D [7956] apscheduler.scheduler (588): Next wakeup is due at 2021-07-01 09:00:46.606000 (in 1846.605000 seconds)
2021-07-01 08:30:00 I [11916] apscheduler.scheduler (509): Running job "run (trigger: JobTrigger(job_id=u'2d6f94d8a54a457dad45c247f0456c78'), next run at: 2021-07-02 08:30:00)" (scheduled at 2021-07-01 08:30:00)
2021-07-01 08:30:00 I [11916] spx_service.backup.backuprun (46): ----- backup run ----- (see job log) BackupJob(name=u'OLS Boot 2021', uuid=u'2d6f94d8a54a457dad45c247f0456c78')
2021-07-01 08:30:00 D [11916] stc_misc.xos.win32.box (106): impersonation [
2021-07-01 08:30:13 D [9720] spx_service.database.models.destination (228): NAS Direct 4 contains "\\169.254.100.106\homes\OLS Server\C_VOL-b006-i006.spi"
2021-07-01 08:31:50 D [11916] stc_misc.xos.win32.box (111): ] impersonation
2021-07-01 08:31:50 D [11916] stc_misc.xos.win32.box (106): impersonation [
2021-07-01 08:31:50 D [11916] spx_service.database.models.destination (136): destination inaccessible<{"path": "\\\\169.254.100.106\\homes\\OLS Server", "error": "[Errno 22] invalid mode ('w') or filename: u'\\\\\\\\169.254.100.106\\\\homes\\\\OLS Server\\\\.spx_dest_access_test.5793595529.tmp'"}
2021-07-01 08:31:50 D [11916] stc_misc.xos.win32.box (111): ] impersonation
2021-07-01 08:31:50 D [11916] spx_service.helper.spxscheduler (49): db session cleanup
2021-07-01 08:31:50 E [11916] apscheduler.scheduler (520): Job "run (trigger: JobTrigger(job_id=u'2d6f94d8a54a457dad45c247f0456c78'), next run at: 2021-07-02 08:30:00)" raised an exception
Traceback (most recent call last):
File "D:\bamboo-home\xml-data\build-dir\SPX-CXSPX543-JOB1\.envs\SPX-CXSPX543-JOB1\lib\site-packages\apscheduler\scheduler.py", line 512, in _run_job
File "D:\bamboo-home\xml-data\build-dir\SPX-CXSPX543-JOB1\spx_service\helper\scheduler.py", line 158, in wrapper
File "D:\bamboo-home\xml-data\build-dir\SPX-CXSPX543-JOB1\spx_service\helper\spxscheduler.py", line 214, in run
File "D:\bamboo-home\xml-data\build-dir\SPX-CXSPX543-JOB1\spx_service\backup\runservice.py", line 49, in run_backup_job
File "D:\bamboo-home\xml-data\build-dir\SPX-CXSPX543-JOB1\spx_service\backup\backuprun.py", line 116, in run
File "D:\bamboo-home\xml-data\build-dir\SPX-CXSPX543-JOB1\spx_service\backup\backuprun.py", line 184, in _scan_destination
File "D:\bamboo-home\xml-data\build-dir\SPX-CXSPX543-JOB1\spx_service\helper\imagescan.py", line 47, in scan
DestinationAccessError: error.destination.inaccessible
2021-07-01 08:31:50 I [6996] stc_misc.mailer (46): Connection Successful
2021-07-01 08:31:50 I [6996] spx_service.helper.notify (58): Email sent successfully.
2021-07-01 08:31:51 D [11916] apscheduler.threadpool (94): Exiting worker thread

 

Here is the log file for F:\drive on the same server, same software, same NAS that in the SPX software shows successful, however even in this log file shows destination unreachable. 

2021-07-01 07:35:00 D [7956] apscheduler.scheduler (579): Looking for jobs to run
2021-07-01 07:35:00 D [12396] apscheduler.threadpool (69): Started worker thread
2021-07-01 07:35:00 D [7956] apscheduler.scheduler (588): Next wakeup is due at 2021-07-01 08:00:46.606000 (in 1546.602000 seconds)
2021-07-01 07:35:00 I [12396] apscheduler.scheduler (509): Running job "run (trigger: JobTrigger(job_id=u'9ea9df959f7c4c558c89e02f22db71b6'), next run at: 2021-07-01 12:35:00)" (scheduled at 2021-07-01 07:35:00)
2021-07-01 07:35:00 I [12396] spx_service.backup.backuprun (46): ----- backup run ----- (see job log) BackupJob(name=u'OLS Data 2021', uuid=u'9ea9df959f7c4c558c89e02f22db71b6')
2021-07-01 07:35:00 D [12396] stc_misc.xos.win32.box (106): impersonation [
2021-07-01 07:35:16 D [10624] spx_service.database.models.destination (228): NAS Direct 4 contains "\\169.254.100.106\homes\OLS Server\F_VOL-b002-i010.spi"
2021-07-01 07:35:23 D [12396] stc_misc.xos.win32.box (111): ] impersonation
2021-07-01 07:35:23 D [12396] stc_misc.xos.win32.box (106): impersonation [
2021-07-01 07:35:23 D [12396] spx_service.database.models.destination (136): destination inaccessible<{"path": "\\\\169.254.100.106\\homes\\OLS Server", "error": "[Errno 22] invalid mode ('w') or filename: u'\\\\\\\\169.254.100.106\\\\homes\\\\OLS Server\\\\.spx_dest_access_test.4098546030.tmp'"}
2021-07-01 07:35:23 D [12396] stc_misc.xos.win32.box (111): ] impersonation
2021-07-01 07:35:23 D [12396] spx_service.helper.spxscheduler (49): db session cleanup
2021-07-01 07:35:23 E [12396] apscheduler.scheduler (520): Job "run (trigger: JobTrigger(job_id=u'9ea9df959f7c4c558c89e02f22db71b6'), next run at: 2021-07-01 12:35:00)" raised an exception
Traceback (most recent call last):
File "D:\bamboo-home\xml-data\build-dir\SPX-CXSPX543-JOB1\.envs\SPX-CXSPX543-JOB1\lib\site-packages\apscheduler\scheduler.py", line 512, in _run_job
File "D:\bamboo-home\xml-data\build-dir\SPX-CXSPX543-JOB1\spx_service\helper\scheduler.py", line 158, in wrapper
File "D:\bamboo-home\xml-data\build-dir\SPX-CXSPX543-JOB1\spx_service\helper\spxscheduler.py", line 214, in run
File "D:\bamboo-home\xml-data\build-dir\SPX-CXSPX543-JOB1\spx_service\backup\runservice.py", line 49, in run_backup_job
File "D:\bamboo-home\xml-data\build-dir\SPX-CXSPX543-JOB1\spx_service\backup\backuprun.py", line 116, in run
File "D:\bamboo-home\xml-data\build-dir\SPX-CXSPX543-JOB1\spx_service\backup\backuprun.py", line 184, in _scan_destination
File "D:\bamboo-home\xml-data\build-dir\SPX-CXSPX543-JOB1\spx_service\helper\imagescan.py", line 47, in scan
DestinationAccessError: error.destination.inaccessible
2021-07-01 07:35:24 D [12396] apscheduler.threadpool (94): Exiting worker thread