Salta al contenuto principale

Rename destination NAS

Thread needs solution

I need to (or at least strongly want to) change the name of a NAS that is destination for ATI backups for 4 computers.  All 4 computers take "Files and folders" FTP backups to the NAS. 3 of them also take "Disks and partitions" SMB backups to the NAS.  2 of the "Disk and partitions" backups are from ATI 202 producing .tibx backups; the other is from ATI 2019 so is a .tib backup.

I don't know what to do after changing the name of the NAS.

  1. Just change the destination name in the task an hope that ATI can associate the old and new backups as parts of the same chains?  (I'm almost certain that won't work.)
  2. Delete the existing tasks and try "Add existing backup"?  I'm almost sure that function is broken in the FTP support, and I suspect the metadata in the .tibx files will make it fail.  Maybe it will work for the 1 ATI 2019 "Disk and partitions" backup?
  3. Delete the existing tasks and create new ones with new names?  That will certainly work.

Whatever I do, will an ATI recovery be able to use the old backup files?

0 Users found this helpful

Is it one of the Synology NAS or the Qnap or WD? Long time back I an IP address change for my Synology NAS and for disk and partitions backup all I had to do was to update the settings, navigate to the new destination, and all was OK - more recently I have used devise name to avoid this issue. (This was with *.tib not *.tibx backups.) I have never tried it with a ftp backup.

I would try 1, and if that does not work, try 2. Not sure what is contained in the first backup file; however that may be why you cannot as yet move such backup tasks. If it is disk ID that is the issue, then you should be OK, but if it also embeds the file location that may be fatal. I think you should still be able to recover the backup, but you may need to use the recovery media. Steve will no doubt have much more to say on this matter.

Ian

I've decided to put off this change for a while.

Patrick,

I recommend deleting the smb connections in your machines registries for the tasks then, manually run each task.  This process will invoke the credentials login due to the removal of the smb registry values.  After connection is made proceed with running the task.  This will result in the task script being updated as well as all metadata values and the internal backup database archive.

I'll give that a shot.

I've got 3 SMB backups (weekly) and 4 FTP backups (daily) living on that NAS.  I think I'll move the FTP backups to a different NAS.  Then I won't have to scramble to get all the backups changes as soon as I change the name of the NAS.  The ATI "Move" doesn't work for FTP backups, but at least AAP doesn't get in the way of messing with .tib files on a NAS.

Completely unrelated to any Acronis product, I'm going through this NAS renaming because Synology has liberal rules on host names - they don't have to conform to the DNS RFC's rules on naming hosts.  Neither the Synology devices nor Windows cared, but I also have a QNAP NAS.  QNAP strictly adheres to the DNS RFC's rules and will not talk to a device that does not follow the rules.  I wanted to set up a direct transfer between a Synology NAS and  A QNAP NAS, but I had an underscore in my Synology host names and QNAP would not accept that.  (I perhaps could have used the IP address.  I didn't try.) 

I'd stick with Domain names.  I use them and have done so for years.  For me they are much easier than IP Addresses.