IT_Architect
Verified User
- Joined
- Feb 27, 2006
- Messages
- 1,114
I backup VMs up every night to an NFS volume exported by a Microsoft Server. It works great. I have set up rights for DA's admin user, and it has full rights. I do not have the space to backup locally, which is what I have done with other transfer backups that has worked so well. I can log into the FreeBSD DA server with PuTTY as the admin user, and navigate to the NFS directory and do anything I want to, including making folders, files, deleting, and renaming anything I want to.
When I use Admin Backup/Transfer, and select Local and the path to NFS share /mnt/nas-1/backups/ServerTransfer/, it creates the admin subdirectory, does its thing, then deletes the subdirectory, leaves a file at named admin.root.admin.tar.gz at /mnt/nas-1/backups/ServerTransfer/, and deletes the admin subdirectory. The entry in Messages shows admin backed up fine.
However, for all of the other users, all of whom are under that admin reseller, I get a messages like these:
What is odd, is it DOES create the subdirectory /mnt/nas-1/backups/ServerTransfer/theuser/backup/ and write the files in those directories, and I can see them build. However, when it finishes, it deletes the user named subdirectory, and moves to the next user. All that remains after it goes through all of the users is the one created in the beginning from the admin backup, /mnt/nas-1/backups/ServerTransfer/user.admin.theuser.tar.gz, and it is the same size as after the admin backup.
When I use Admin Backup/Transfer, and select Local and the path to NFS share /mnt/nas-1/backups/ServerTransfer/, it creates the admin subdirectory, does its thing, then deletes the subdirectory, leaves a file at named admin.root.admin.tar.gz at /mnt/nas-1/backups/ServerTransfer/, and deletes the admin subdirectory. The entry in Messages shows admin backed up fine.
Code:
User admin has been backed up. <12:07:25>
However, for all of the other users, all of whom are under that admin reseller, I get a messages like these:
Code:
Unable to write /mnt/nas-1/backups/ServerTransfer/theuser/backup/theuserd.org/email/quota : Unable to get Lock on file:
open error for /mnt/nas-1/backups/ServerTransfer/theuser/backup/theuserd.org/email/quota.lock: No such file or directory
/mnt/nas-1/backups/ServerTransfer/theuser/backup/theuserd.org/email: No such file or directory
Error reading /mnt/nas-1/backups/ServerTransfer/theuser/backup/theuserd.org/domain.conf to insert local_domain & private_html_is_link: Unable to open /mnt/nas-1/backups/ServerTransfer/theuser/backup/theuserd.org/domain.conf for reading.
Error writing /mnt/nas-1/backups/ServerTransfer/theuser/backup/apache_owned_files.list : Unable to open file for writing
Error Compressing the backup file /mnt/nas-1/backups/ServerTransfer/theuser/backup/home.tar.gz : tar: Failed to open '/mnt/nas-1/backups/ServerTransfer/theuser/backup/home.tar.gz': Permission denied
Error renaming /mnt/nas-1/backups/ServerTransfer/theuser/user.admin.theuser.tar.gz to /mnt/nas-1/backups/ServerTransfer/user.admin.theuser.tar.gz : Unable to move /mnt/nas-1/backups/ServerTransfer/theuser/user.admin.theuser.tar.gz to /mnt/nas-1/backups/ServerTransfer/user.admin.theuser.tar.gz:
A directory component in oldpath or newpath does not exist or is a dangling symbolic link.
What is odd, is it DOES create the subdirectory /mnt/nas-1/backups/ServerTransfer/theuser/backup/ and write the files in those directories, and I can see them build. However, when it finishes, it deletes the user named subdirectory, and moves to the next user. All that remains after it goes through all of the users is the one created in the beginning from the admin backup, /mnt/nas-1/backups/ServerTransfer/user.admin.theuser.tar.gz, and it is the same size as after the admin backup.
Last edited: