Allan Pritchard
affa --rise-all prodserv
just returns an error.....
it said there was no archive.0 the data appears to be in the directory prodserv/schedule.running....
Did you use the correct syntax, note there is a space between rise and --all, & two dashes before all ie
from the wiki article
affa --rise [--all] JOB [ARCHIVE]
in your case
affa --rise --all prodserv
Maybe the wrong syntax in the command prevented the archive from being accessed.
If it transpires that a certain archive is truly not available, then you could specify the last known available good archive
ie
affa --rise --all prodserv scheduled.0
Note that the use of --all is optional, read the wiki why you would (or would not) use it, it does not seem absolutely necessary to me.
http://wiki.contribs.org/AffaI would not attempt to rise using a scheduled.running archive, as that is a backup that is incomplete, & will obviously be missing some data, ie the backup was stopped part way through & is waiting to finish the next time it can. Perhaps this was due to the power supply failure issue.
Its now 2am here and in desperation we have manually moved the data from the affa backup from the /var/affa... to /home/e-smith
and /etc
Just moving the data is probably not sufficient, as you have not restored the mysql databases (from the dump file), so that would explain why webmail is not accessible (ie wrong password). It may also explain other issues. Probably you have moved the dump file back to the server (with other data) but not ran the suitable commands to restore the contents to the mysql database system.
Charlie has suggested to try & fix one cloned drive.
As you have already tried using Affa rise, I suggest you try that again, this time using the correct command syntax.
It may be your quickest solution for now.