It is currently Fri Mar 29, 2024 12:35 am


Move Automatic Backups to Another Disk

Hauptwerk software technical support only. Please make sure you have read the manual, tutorials and FAQ pages before requesting support.
  • Author
  • Message
Offline

WmHurt

Member

  • Posts: 65
  • Joined: Mon Dec 13, 2004 1:00 pm
  • Location: Seattle, Washington, USA

Move Automatic Backups to Another Disk

PostWed Apr 11, 2018 10:36 am

How can I configure HW to do automatic backups to a disc drive other than the user home account?
Offline
User avatar

chr.schmitz

Member

  • Posts: 374
  • Joined: Sun Aug 25, 2013 11:49 pm

Re: Move Automatic Backups to Another Disk

PostWed Apr 11, 2018 10:49 am

Unfortunately this is currently not possible. I already filed a feature request some time ago.

Chris
Offline
User avatar

IainStinson

Member

  • Posts: 1391
  • Joined: Tue Dec 29, 2009 6:08 pm
  • Location: NW England, UK

Re: Move Automatic Backups to Another Disk

PostWed Apr 11, 2018 1:41 pm

You can move the location where HW writes its automatic backups by using symbolic links, though this is probably not supported by MDA.

Move the folder where HW writes its automatic backups to a new drive for example; create a symbolic link (mklink in Windows (in a command window running as admin)) with the same name as this folder making the folder you moved (best to fully specify its new location location) as the link target.
{For example
cd c:\users\<userid>
copy Hauptwerk d:\Hauptwerk
delete Hauptwerk
mklink /D Hauptwerk d:\Hauptwerk
}
Only do this if you are comfortable with using symbolic links.

A similar pattern should work on MacOS.

Iain
Offline

WmHurt

Member

  • Posts: 65
  • Joined: Mon Dec 13, 2004 1:00 pm
  • Location: Seattle, Washington, USA

Re: Move Automatic Backups to Another Disk

PostWed Apr 11, 2018 2:18 pm

On Mac OS -- tried using an alias and restarting the machine, but always got:

Could not create the folder '/Users/xxxxx/Hauptwerk'. Please make sure that you are logged onto the computer with an operating system account with sufficient privileges (such as an administrator account) or try rebooting.

Message code (for diagnostic purposes): 0057

HW ignored the Hauptwerk (aliias) folder in the home directory, despite using an administrator account with full access priviledges. Restoring the original (not alias) Hauptwerk folder left everything working but with the alternate backup data back in the home directory. The sharing and permissions for the alias had been set the same as for the original Hauptwerk/AutomaticBackups/ Somehow HW identifies the alias and will not accept it.
Offline
User avatar

IainStinson

Member

  • Posts: 1391
  • Joined: Tue Dec 29, 2009 6:08 pm
  • Location: NW England, UK

Re: Move Automatic Backups to Another Disk

PostWed Apr 11, 2018 2:44 pm

I believe that symbolic links in MacOS (use the ln -s command in a terminal window) are not the same as using an alias. Symbolic links are a part of the core Unix system used by MacOS and alias are something added on top. Although programs can determine if a file/directory is a symbolic link most don't and HW doesn't seem to on Windows.

Iain
Offline

WmHurt

Member

  • Posts: 65
  • Joined: Mon Dec 13, 2004 1:00 pm
  • Location: Seattle, Washington, USA

Re: Move Automatic Backups to Another Disk

PostWed Apr 11, 2018 3:20 pm

Your are right -- using the terminal and a symbolic link worked.

The new Hauptwerk/AutomaticBackups directory was on /Volumes/HDD1; the following created a link in the home desktop directory; it worked so then copied and renamed it into the home directory and HW started without problems.:

ln -s /Volumes/HDD1/Hauptwerk /Users/xxxxx/Desktop/HauptwerkSYM

(Renamed it to Hauptwerk in the home directory without the SYM after proving it worked and deleted the original Hauptwerk folder from the home directory).

Interesting that the Finder shows this as an alias, but HW handles it OK.
Offline
User avatar

chr.schmitz

Member

  • Posts: 374
  • Joined: Sun Aug 25, 2013 11:49 pm

Re: Move Automatic Backups to Another Disk

PostWed Apr 11, 2018 3:44 pm

This is a smart workaround! This solves a long-standing issue for me :D

Chris

Return to Technical support

Who is online

Users browsing this forum: No registered users and 16 guests