We are supporting a few large sites using Aegir (>10GB), and cloning these sites has become unrealistic due to time and space used in our environment.
To resolve this we should be able to use the following steps.

  1. Build a new platform
  2. Build a minimal site
  3. Dump the source site database into the new site
  4. Create a symlink/Use stage file proxy for the files.

It seems like a logical feature to be able to exclude files on clone.

Comments

DanielVeza created an issue. See original summary.

ergonlogic’s picture

Status: Active » Postponed (maintainer needs more info)

The process you describe is basically the recommended solution to exceedingly large site files/ dirs. Aegir ought not to follow symlinks when creating backups, and so clones become a much quicker process. However, that also means that *no* backups contain the sites' files, and so some other backup mechanism (outside of Aegir) should be implemented.

So, I guess I'm unclear what feature you're requesting here. Are you saying that process doesn't work to exclude the contents of files/ from backups? If so, then this should be a bug report. Or are you suggesting automating the process?

DanielVeza’s picture

Status: Postponed (maintainer needs more info) » Active

Sorry, I just reread my message and I was rather unclear.

The process I was listing above is what I do to get around the issue that we can't currently clone without files using just aegir.

The feature I was suggesting was a "Clone without files" functionality. I'm happy enough with the workaround process I listed, but if you think it has value to create a "clone without files" functionality that would make things easier.

Thanks guys!