Skip to main content

Acronis SFTP issue - cannot rename file

Thread needs solution

Acronis seems to have an issue with SFTP as storage - it shows that the file x cannot be renamed.

Access works (the temp file is also generated on the SFTP server) - a test with SFTP client also works. Access method is via User + passwd.

XML File content looks OK.

 

Generating SFTP logfile according to https://kb.acronis.com/content/44576 does not work. (no logs generated)

Version:

Acronis Backup 12.5 Build: 11010

SFTP Server: Windows 10 with OpenSSH feature enabled.

 

Error code: 207
Module: 161
LineInfo: 0x0B320396ADFE3C18
Fields: {"IsReturnCode":"1","$module":"disk_bundle_vs_11010"}
Message: Erstellen eines Archivs im Speicherort 'sftp://192.168.1.110/E:/Backup/StorageNode/' ist fehlgeschlagen.
------------------------
Error code: 26
Module: 161
LineInfo: 0xA0F87A51D6F9CECC
Fields: {"$module":"disk_bundle_vs_11010"}
Message: Speichern der Archiv-Metainfo fehlgeschlagen. Sie entweder keinen Schreibzugriff auf den Ordner oder er ist im Augenblick nicht verfügbar.
------------------------
Error code: 8
Module: 523
LineInfo: 0x93DDF24CF210E756
Fields: {"$module":"disk_bundle_vs_11010"}
Message: Umbenennen der Datei '.tmp.71BF8181-F2DF-4DD4-AE5E-ED6003CB0E9A.Buero.research.ok-edv.de-C0A2B808-BC4E-4652-8666-0FBE10B52C50-9FEE844B-F1FA-46E1-8173-C125824422A2A.xml' nach 'Buero.research.ok-edv.de-C0A2B808-BC4E-4652-8666-0FBE10B52C50-9FEE844B-F1FA-46E1-8173-C125824422A2A.xml' fehlgeschlagen.

0 Users found this helpful

today the sftp log was there it shows

->  PSize 143 SSH_FXP_OPEN File /E:/Backup/StorageNode/Buero.research.ok-edv.de-C0A2B808-BC4E-4652-8666-0FBE10B52C50-9FEE844B-F1FA-46E1-8173-C125824422A2A.xml
<-  PSize 29 SSH_FXP_STATUS  Err 2 No such file
->  PSize 189 SSH_FXP_OPEN File /E:/Backup/StorageNode/.tmp.71BF8181-F2DF-4DD4-AE5E-ED6003CB0E9A.Buero.research.ok-edv.de-C0A2B808-BC4E-4652-8666-0FBE10B52C50-9FEE844B-F1FA-46E1-8173-C125824422A2A.xml
<-  PSize 13 SSH_FXP_HANDLE Handle 0000
->  PSize 29 SSH_FXP_WRITE Handle 0000 Offset  Size 3
...
<-  PSize 24 SSH_FXP_STATUS  Err 0 Success

<-  PSize 24 SSH_FXP_STATUS  Err 0 Success
->  PSize 135 SSH_FXP_LSTAT File /E:/Backup/StorageNode/Buero.research.ok-edv.de-C0A2B808-BC4E-4652-8666-0FBE10B52C50-9FEE844B-F1FA-46E1-8173-C125824422A2A.xml Flags ---
<-  PSize 29 SSH_FXP_STATUS  Err 2 No such file
->  PSize 307 SSH_FXP_RENAME f1 /E:/Backup/StorageNode/.tmp.71BF8181-F2DF-4DD4-AE5E-ED6003CB0E9A.Buero.research.ok-edv.de-C0A2B808-BC4E-4652-8666-0FBE10B52C50-9FEE844B-F1FA-46E1-8173-C125824422A2A.xml
<-  PSize 24 SSH_FXP_STATUS  Err 4 Failure

but the file is present on server and you can see above that the file was opened and writable via Acronis.

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 0
Comments: 2016

Hello Endurance,

please check whether the user account you run this backup plan from has modify rights.

If you experience issues with generating SFTP logs, please collect Acronis System Information from the machine where this problem occurs and share it with Acronis Support Team.

Hi Maria, don't get the point regarding user account running the backup plan from. For the SFTP connection a completely different user is used (also asked to enter the credential while creating the location for the backup plan).

E.g. Acronis Managementserver and Machine executing are in a windows domain. The SFTP server is outside not management via the domain so using a local user on the SFTP server. As described the creation of the temp file works (including adding content to it). The rename fails via Acronis (tested it sucessfully via ssh commandline). 

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 0
Comments: 2016

Hello,

For the SFTP connection a completely different user is used (also asked to enter the credential while creating the location for the backup plan).

Please check whether this user has enough rights to modify files in the backup location