Trying to rush this kind of procedure generally leads to much greater
downtime and lost data.

The technical name for those who take this risk without a backup is "foolish".

{o.o}

On 2011/12/20 06:22, Felip Moll wrote:
> Thank you for your answers!.
>
> Regarding to the backups I have an external backup system with bacula + tapes
> and another with NFS, so it should not be a problem. The problem is that I want
> to do all this process in a short period time to minimize the downtime.
>
> Be sure that your e-mails will be useful to me. Thank you.
>
> 2011/12/20 Nico Kadel-Garcia <[log in to unmask] <mailto:[log in to unmask]>>
>
>     On Tue, Dec 20, 2011 at 5:52 AM, Jason Bronner <[log in to unmask]
>     <mailto:[log in to unmask]>> wrote:
>      > Felip.
>      >
>      > always always always: back up the array. create the new array. move the old
>      > array to the new array. destroy the old array.
>
>     Amen. Also, in making the backup, consider using "star" if you use
>     SELinux. rsync and normal tar do not preserve SELinux attributes.
>
>     It is a good time to consider your backup policy. RAID is *not*
>     backup, and the white paper from Google at
>     http://static.googleusercontent.com/external_content/untrusted_dlcp/research.google.com/en/us/archive/disk_failures.pdf
>
>