That's a way to do it, you do need to reduce max and offline reorg the
database after the conversion to get everything to run at 100% speed
without wasted database space after the conversion
I prefer to upgrade the old server to 7.1.7 and replicate the data from
tape/VTL/whatever to the new server
Node replication would be the only real way to go directly to the container
pool.
You could define the file-class pool on the same storage directories as the new
container pool, so that once you land everything and convert, you have two
pools but don't waste any storage.
__
Not to a directory container pool, only to a traditional pool.
-
Thanks,
Marc...
Marc Lanteigne
Accelerated Value Specialist for Spectrum Protect
416.478.0233 | marclantei...@ca.ibm.com
Office Hours: Monday to Friday, 7:00 to 16:00 Eastern
create server to sever comm and export import node... it should work
hth
Chavdar
On Wednesday, November 29, 2017, Marc Lanteigne
wrote:
> Hi,
>
> You might be able to use node replication to move the data from the old
> server into the new server.
>
> If you go with the import into a filepo
Hi,
You might be able to use node replication to move the data from the old
server into the new server.
If you go with the import into a filepool method, you don't need two
directory container pools, you can convert the filepool into the existing
container pool.
-
Thanks,
Marc...
Hi guys!
We are migrating our clients from a version 6 server to a new 7.1.7 server with
a directory container pool. Switching clients is easy, just updating the option
files and they will start a new backup cycle on the new TSM server. But a lot
of clients also store long term archives. I can't
