Re: Moving databases to other Storage
Posted in 2008
Topics: General Discussion
That's probably the way I'd do it. I don't see why it wouldn't work. As long as you have the device links set up correctly and pointing to valid raw devices. ----- Original Message ----- Subject: Moving databases to other Storage Date: Thu, May 1, 2008 18:59 From: "Josep" <petrybr@gmail.com> Hello, > > We need more space for our databases, they're reaching 99% of our > capacity. > > So we contracted a new Storage. > > I've to move my DBs from the actual Storage to the new Storage. > > How can i do this safely?? > > I think to make a full backup and restore it on the new Storage, but > im not sure if this is going to work. > > Someone has any suggestion?!? > > Thanks, and sorry my poor english > _______________________________________________ > Informix-list mailing list > Informix-list@iiug.org > http://www.iiug.org/mailman/listinfo/informix-list > >
> ----- Original Message -----
> Subject: Moving databases to other Storage
> Date: Thu, May 1, 2008 18:59
> From: "Josep" <petrybr@gmail.com>
> Hello,
>>
>> We need more space for our databases, they're reaching 99% of our
>> capacity.
>>
>> So we contracted a new Storage.
>>
>> I've to move my DBs from the actual Storage to the new Storage.
>>
>> How can i do this safely??
>>
>> I think to make a full backup and restore it on the new Storage, but
>> im not sure if this is going to work.
>>
>> Someone has any suggestion?!?
>>
>> Thanks, and sorry my poor english
>>"Floyd Wellershaus" <floyd@fwellers.com> wrote in message
>>news:mailman.1026.1209683965.20610.informix-list@iiug.org...
> That's probably the way I'd do it.
> I don't see why it wouldn't work. As long as you have the device links set
> up correctly and pointing to valid raw devices.
Perhaps a more elegent way, involving minimal downtime, is to use Informix
mirroring. This relies upon you already using links. So you can:
1. Use onspaces to create mirror chunks on the new storage for each of the
exitsing primary chunks.
2. Stop the database.
3. Reverse all the links so that the primary chunk links point to the new
storage and the mirror chunks point to the old
4. Bring the database server back on line and drop the mirror chunks.