is it possible to change the user level backup location?

[dmacleo]

I have dedicated drive for backups and can easily set admin_backups and system_backups to write to it, I can set the reseller level backups to write to it using a symlink, so those 3 (admin,system,reseller) are ok.

I cannot see what controls the user level backup location.
I have been looking for any conf file or template but I am not having any luck.
thanks.

 

[DirectAdmin Support]

Hello,

The Reseller backups go to:
/home/reseller/user_backups

In a similar fashion, backups created by the User would go to:
/home/user/backups

where you might be able to create a link, eg:
/home/user/backups -> /other/drive/user/backups

or something like that..

DA may complain about a link.. not 100% sure, but if my memory is correct, others are already doing it this way.

John

 

[dmacleo]

was wondering about that, I would have to setup a link for every user from their home directory correct?
for resellers I just symlink to backupdrive/reseller_backups/ and then the names created by backup.
but for users I was thinking if I DIDN'T manually create links for each then each one would all go into one directory and be visible to everyone. want to not do that

 

[DirectAdmin Support]

Hello,

Yes, the user_create_post.sh would be handy to create it for Users.

By creating sub user folders, you can keep the tar.gz in their own spaces... which is actually needed, as User Level backups are not uniquely named to a User.. just a date.
The user_create_post.sh would also create the backup folders on the other drive.. make sure to chown the /other/drive/user to chown user:access, with chmod 710, to help lock it down.

John

 

[dmacleo]

Hello,

Yes, the user_create_post.sh would be handy to create it for Users.

By creating sub user folders, you can keep the tar.gz in their own spaces... which is actually needed, as User Level backups are not uniquely named to a User.. just a date.
The user_create_post.sh would also create the backup folders on the other drive.. make sure to chown the /other/drive/user to chown user:access, with chmod 710, to help lock it down.

John

ok thanks, will take a look at that in a bit.
still trying to make dabackup plugin devs (syslint) see how their flipping the skip_domains_in_backups to 1 is really screwing up user level backups. if I can get the normal da process to use the other drive for user backups like it does for system/admin/reseller I would no longer need any benefits dabackup plugin gives.

 

[dmacleo]

yeah I guess syslint sees no problem with their plugin flipping that setting then never flipping back.
which of course means a user cannot initiate a full backup.
swear they don't bother to actually read the tickets.