Hello All,
Let me introduce myself.
I am Martijn Groenleer, owner of a small Dutch design and hosting company.
I have been using DA as an reseller for about 2,5 year i think and switched recently to a vps also with DA.
While getting more and more sites to maintain i switched also to subversion for version control. A number of sites (think 6) are every minute checked out with a cronjob. This means each minute some .svn directories and files will change (get update with last timestamp etc).
The admin interface has been scheduled to backup each and every account. As you can guess backing up files that get changed won't work. Most of the time i get the following message in the messagesystem:
Ofcourse the backup process will continue with the next account, but i also would like to automaticly try again the failed account, or exclude the .svn directories. Because all failed backups are failing because of changed .svn directories and files.
The time when the backup has been scheduled is at night, no changes are made in the subversion repositories and that way other files won't get changed.
My big question:
How can i prevent that the '.svn' files and directories are packed with tar?
Or how can i automaticly reschedule a backup for a failed account?
I can imagine that we can shoot a backup task in to the queue and make a notice of it in the general backup message.
I do hope, somebody can help me on my way to a working solution.
Kind regards,
Martijn
Let me introduce myself.
I am Martijn Groenleer, owner of a small Dutch design and hosting company.
I have been using DA as an reseller for about 2,5 year i think and switched recently to a vps also with DA.
While getting more and more sites to maintain i switched also to subversion for version control. A number of sites (think 6) are every minute checked out with a cronjob. This means each minute some .svn directories and files will change (get update with last timestamp etc).
The admin interface has been scheduled to backup each and every account. As you can guess backing up files that get changed won't work. Most of the time i get the following message in the messagesystem:
Code:
Error Compressing the backup file user.gicts.omegacms.tar.gz : /bin/tar: domains/omegacms.intern/stable/media/smiley/.svn: file changed as we read itThe time when the backup has been scheduled is at night, no changes are made in the subversion repositories and that way other files won't get changed.
My big question:
How can i prevent that the '.svn' files and directories are packed with tar?
Or how can i automaticly reschedule a backup for a failed account?
I can imagine that we can shoot a backup task in to the queue and make a notice of it in the general backup message.
I do hope, somebody can help me on my way to a working solution.
Kind regards,
Martijn
