Re: Re: [ADSM-L] Backing out of a container storagepool

[Remco Post]

the fine manual list move nodedata with import/export as an illegal operation 
for directory containers. Really, it’s a small wonder if you’re able to restore 
your data from a directory container, it probably took a lot of debating within 
IBM to get that feature supported ;-)


> On 2 Aug 2017, at 22:34, Jonathan Dresang  wrote:
> 
> move nodedata * fromstg=ContainerPool tostg=VTL should work.
> 
> 
> Jonathan Dresang
> Madison Gas & Electric
> 608-252-7296
> 
> 
> 
> 
> From:   Remco Post 
> To: 
> Date:   08/02/2017 03:26 PM
> Subject: Re: [ADSM-L] Backing out of a container storagepool
> Sent by:"ADSM: Dist Stor Manager" 
> 
> 
> 
> export & import the node will do I guess. Other that that, your data is 
> stuck in the directory container….
> 
>> On 2 Aug 2017, at 22:02, David Ehresman  
> wrote:
>> 
>> We have some data in a container storagepool and now have the need to 
> move it back to a virtual tape pool.  Is there anything other than 
> updating the copygroup to point to the vtl and do full backups that I can 
> do to move the data out of the container pool to a primary vtl pool?
>> 
>> David
> 
> -- 
> 
> Met vriendelijke groeten/Kind Regards,
> 
> Remco Post
> r.p...@plcs.nl
> +31 6 248 21 622
> 
> 
> 

-- 

 Met vriendelijke groeten/Kind Regards,

Remco Post
r.p...@plcs.nl
+31 6 248 21 622

Re: Backing out of a container storagepool

[Remco Post]

> On 2 Aug 2017, at 22:33, Anders Räntilä  wrote:
> 
>> export & import the node will do I guess. 
> 
> No!  Export/import doesn't work with container pools.
> 

f*ck, you must be kidding! (no you’re not). So I have tons of archive data to 
move from one TSM server to another, and basically I can’t? Really IBM? Do you 
guys actually want us to implement this new technology, or what? How hard can 
it be to do things right?

> You can replicate the data to another server - to any type of pool - and then 
> replicate it back.  
> 

that might work for what we are planning. Thanks for the heads up!

> /Anders Räntilä
> 
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> RÄNKAB - Räntilä Konsult AB  
> Klippingvägen 23
> SE-196 32 Kungsängen
> Sweden
>  
> Email: and...@rantila.com
> Phone: +46 701 489 431
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> 
> 
> 

-- 

 Met vriendelijke groeten/Kind Regards,

Remco Post
r.p...@plcs.nl
+31 6 248 21 622

Re: Re: [ADSM-L] Backing out of a container storagepool

[Jonathan Dresang]

move nodedata * fromstg=ContainerPool tostg=VTL should work.


Jonathan Dresang
Madison Gas & Electric
608-252-7296




From:   Remco Post 
To: 
Date:   08/02/2017 03:26 PM
Subject: Re: [ADSM-L] Backing out of a container storagepool
Sent by:"ADSM: Dist Stor Manager" 



export & import the node will do I guess. Other that that, your data is 
stuck in the directory container….

> On 2 Aug 2017, at 22:02, David Ehresman  
wrote:
> 
> We have some data in a container storagepool and now have the need to 
move it back to a virtual tape pool.  Is there anything other than 
updating the copygroup to point to the vtl and do full backups that I can 
do to move the data out of the container pool to a primary vtl pool?
> 
> David

-- 

 Met vriendelijke groeten/Kind Regards,

Remco Post
r.p...@plcs.nl
+31 6 248 21 622

Re: Backing out of a container storagepool

[Anders Räntilä]

>export & import the node will do I guess. 

No!  Export/import doesn't work with container pools.

You can replicate the data to another server - to any type of pool - and then 
replicate it back.  

/Anders Räntilä

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
RÄNKAB - Räntilä Konsult AB  
Klippingvägen 23
SE-196 32 Kungsängen
Sweden
 
Email: and...@rantila.com
Phone: +46 701 489 431
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

Re: Backing out of a container storagepool

[Remco Post]

export & import the node will do I guess. Other that that, your data is stuck 
in the directory container….

> On 2 Aug 2017, at 22:02, David Ehresman  wrote:
> 
> We have some data in a container storagepool and now have the need to move it 
> back to a virtual tape pool.  Is there anything other than updating the 
> copygroup to point to the vtl and do full backups that I can do to move the 
> data out of the container pool to a primary vtl pool?
> 
> David

-- 

 Met vriendelijke groeten/Kind Regards,

Remco Post
r.p...@plcs.nl
+31 6 248 21 622

Backing out of a container storagepool

[David Ehresman]

We have some data in a container storagepool and now have the need to move it 
back to a virtual tape pool.  Is there anything other than updating the 
copygroup to point to the vtl and do full backups that I can do to move the 
data out of the container pool to a primary vtl pool?

David

Re: Migrate from TSM Server 5.5.7 on Windows to TSM Server 7.1.7 on Linux - the unsupported way because exportdb --> insertdb did not work

[Rick Adamson]

Hi Dennis,
I suggest if possible upgrading your old server to a minimum of version 6.3 
then retry the migration, then both databases are full DB2.
Many people had issues going from 5.x straight to version 7 and had much more 
success by first upgrading the old server.

Also, if possible I would use the "new server network method". It eliminates 
the complexities that a tape library adds to the process.
Hope this helps

-Rick Adamson
 


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
Schneck, Dennis
Sent: Wednesday, August 02, 2017 3:24 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Migrate from TSM Server 5.5.7 on Windows to TSM Server 7.1.7 
on Linux - the unsupported way because exportdb --> insertdb did not work

Hello,
how to migrate from TSM Server 5.5.x on Windows to TSM Server 7.1.7 on Linux ( 
only one tape library ) ?
because my way ( see 2nd ) is not supported


1st I tryed: ( exportdb --> insertdb )

VM1: TSM 5.5.7 on Windows and VM2: TSM 7.1.7 on Windows

VM1:
restore backup from productive System.
install UpgradeTool

VM2:
migrate on VM2 with dsmupgdx from VM1
then I had TSM 7.1.7 running.
Did a exportdb on TSM 7.1.7 on Windows

If "insertdb" on Linux TSM Server 7.1.7 got this error:

/opt/tivoli/tsm/server/bin/dsmserv insertdb manifest=/import/manifest.txt

IBM Tivoli Storage Manager for Linux/x86_64 Version 7, Release 1, Level 7.100 
...
"ANR1953E INSERTDB: Linux/x86_64 cannot be the target of a database upgrade 
from Windows."



2nd I tryed: ( local migrate )

Install TSM Server 5.5.7 on Linux ( SLES 12 SP2 ) + TSM Client 5.5.4.0 restore 
backup from productive System.
Install UpgradeTool

Upgrade to TSM 7.1.3 an run "dsmupgdx"
for migrate local Server (Network Method).
Then TSM Server 7.1.3 is running with Data from TSM Server 5.5.x Windows Then 
Update to 7.1.7.300

this works... but IBM support say by phonecall - " .. this is not supported " 
:-(



Any proposals for a supported way ?



Thanks
Dennis

Re: Migrate from TSM Server 5.5.7 on Windows to TSM Server 7.1.7 on Linux - the unsupported way because exportdb --> insertdb did not work

[Andrew Galloway]

You may also want to make use of the documents found in this link.
 
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Storage%20Manager/page/Migrating%20Tivoli%20Storage%20Manager%20Servers%20from%20one%20Operating%20System%20to%20another
 


 
 
__
Andrew Galloway
Operational Systems Continuity Analyst
SSC RCMP Technology Directorate
CIO Building C1035
R.C.M.P. Headquarters
1200 Vanier Parkway
Ottawa ON
K1A 0R2
613.998.7707
andrew.gallo...@ssc-spc.gc.ca__
>>> "Schneck, Dennis"  2017-08-02 3:24 AM >>>
Hello,
how to migrate from TSM Server 5.5.x on Windows to TSM Server 7.1.7 on Linux ( 
only one tape library ) ?
because my way ( see 2nd ) is not supported


1st I tryed: ( exportdb --> insertdb )

VM1: TSM 5.5.7 on Windows and VM2: TSM 7.1.7 on Windows

VM1:
restore backup from productive System.
install UpgradeTool

VM2:
migrate on VM2 with dsmupgdx from VM1
then I had TSM 7.1.7 running.
Did a exportdb on TSM 7.1.7 on Windows

If "insertdb" on Linux TSM Server 7.1.7 got this error:

/opt/tivoli/tsm/server/bin/dsmserv insertdb manifest=/import/manifest.txt

IBM Tivoli Storage Manager for Linux/x86_64 Version 7, Release 1, Level 7.100
...
"ANR1953E INSERTDB: Linux/x86_64 cannot be the target of a database upgrade 
from Windows."



2nd I tryed: ( local migrate )

Install TSM Server 5.5.7 on Linux ( SLES 12 SP2 ) + TSM Client 5.5.4.0
restore backup from productive System.
Install UpgradeTool

Upgrade to TSM 7.1.3 an run "dsmupgdx"
for migrate local Server (Network Method).
Then TSM Server 7.1.3 is running with Data from TSM Server 5.5.x Windows
Then Update to 7.1.7.300

this works... but IBM support say by phonecall - " .. this is not supported " 
:-(



Any proposals for a supported way ?



Thanks
Dennis

Re: Migrate from TSM Server 5.5.7 on Windows to TSM Server 7.1.7 on Linux - the unsupported way because exportdb --> insertdb did not work

[Chavdar Cholev]

Hi
I am nou sre if it is supported. But create server to server connection
between old and new server and export node by node... We did it last year
and it works, bur depend on amount of data


HTH
Chavdar
On Wednesday, 2 August 2017, Loon, Eric van (ITOPT3) - KLM <
eric-van.l...@klm.com> wrote:

> Hi Dennis!
> Can you partition your library? In that case you can connect it to both
> your old Windows server and your new Linux server and use export node
> toserver= to move your existing backups to the new TSM server.
> Kind regards,
> Eric van Loon
> Air France/KLM Storage Engineering
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU ]
> On Behalf Of Schneck, Dennis
> Sent: woensdag 2 augustus 2017 9:24
> To: ADSM-L@VM.MARIST.EDU 
> Subject: Migrate from TSM Server 5.5.7 on Windows to TSM Server 7.1.7 on
> Linux - the unsupported way because exportdb --> insertdb did not work
>
> Hello,
> how to migrate from TSM Server 5.5.x on Windows to TSM Server 7.1.7 on
> Linux ( only one tape library ) ?
> because my way ( see 2nd ) is not supported
>
>
> 1st I tryed: ( exportdb --> insertdb )
>
> VM1: TSM 5.5.7 on Windows and VM2: TSM 7.1.7 on Windows
>
> VM1:
> restore backup from productive System.
> install UpgradeTool
>
> VM2:
> migrate on VM2 with dsmupgdx from VM1
> then I had TSM 7.1.7 running.
> Did a exportdb on TSM 7.1.7 on Windows
>
> If "insertdb" on Linux TSM Server 7.1.7 got this error:
>
> /opt/tivoli/tsm/server/bin/dsmserv insertdb manifest=/import/manifest.txt
>
> IBM Tivoli Storage Manager for Linux/x86_64 Version 7, Release 1, Level
> 7.100 ...
> "ANR1953E INSERTDB: Linux/x86_64 cannot be the target of a database
> upgrade from Windows."
>
>
>
> 2nd I tryed: ( local migrate )
>
> Install TSM Server 5.5.7 on Linux ( SLES 12 SP2 ) + TSM Client 5.5.4.0
> restore backup from productive System.
> Install UpgradeTool
>
> Upgrade to TSM 7.1.3 an run "dsmupgdx"
> for migrate local Server (Network Method).
> Then TSM Server 7.1.3 is running with Data from TSM Server 5.5.x Windows
> Then Update to 7.1.7.300
>
> this works... but IBM support say by phonecall - " .. this is not
> supported " :-(
>
>
>
> Any proposals for a supported way ?
>
>
>
> Thanks
> Dennis
> 
> For information, services and offers, please visit our web site:
> http://www.klm.com. This e-mail and any attachment may contain
> confidential and privileged material intended for the addressee only. If
> you are not the addressee, you are notified that no part of the e-mail or
> any attachment may be disclosed, copied or distributed, and that any other
> action related to this e-mail or attachment is strictly prohibited, and may
> be unlawful. If you have received this e-mail by error, please notify the
> sender immediately by return e-mail, and delete this message.
>
> Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its
> employees shall not be liable for the incorrect or incomplete transmission
> of this e-mail or any attachments, nor responsible for any delay in receipt.
> Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch
> Airlines) is registered in Amstelveen, The Netherlands, with registered
> number 33014286
> 
>

Re: Migrate from TSM Server 5.5.7 on Windows to TSM Server 7.1.7 on Linux - the unsupported way because exportdb --> insertdb did not work

[Loon, Eric van (ITOPT3) - KLM]

Hi Dennis!
Can you partition your library? In that case you can connect it to both your 
old Windows server and your new Linux server and use export node 
toserver= to move your existing backups to the new TSM server.
Kind regards,
Eric van Loon
Air France/KLM Storage Engineering

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
Schneck, Dennis
Sent: woensdag 2 augustus 2017 9:24
To: ADSM-L@VM.MARIST.EDU
Subject: Migrate from TSM Server 5.5.7 on Windows to TSM Server 7.1.7 on Linux 
- the unsupported way because exportdb --> insertdb did not work

Hello,
how to migrate from TSM Server 5.5.x on Windows to TSM Server 7.1.7 on Linux ( 
only one tape library ) ?
because my way ( see 2nd ) is not supported


1st I tryed: ( exportdb --> insertdb )

VM1: TSM 5.5.7 on Windows and VM2: TSM 7.1.7 on Windows

VM1:
restore backup from productive System.
install UpgradeTool

VM2:
migrate on VM2 with dsmupgdx from VM1
then I had TSM 7.1.7 running.
Did a exportdb on TSM 7.1.7 on Windows

If "insertdb" on Linux TSM Server 7.1.7 got this error:

/opt/tivoli/tsm/server/bin/dsmserv insertdb manifest=/import/manifest.txt

IBM Tivoli Storage Manager for Linux/x86_64 Version 7, Release 1, Level 7.100 
...
"ANR1953E INSERTDB: Linux/x86_64 cannot be the target of a database upgrade 
from Windows."



2nd I tryed: ( local migrate )

Install TSM Server 5.5.7 on Linux ( SLES 12 SP2 ) + TSM Client 5.5.4.0 restore 
backup from productive System.
Install UpgradeTool

Upgrade to TSM 7.1.3 an run "dsmupgdx"
for migrate local Server (Network Method).
Then TSM Server 7.1.3 is running with Data from TSM Server 5.5.x Windows Then 
Update to 7.1.7.300

this works... but IBM support say by phonecall - " .. this is not supported " 
:-(



Any proposals for a supported way ?



Thanks
Dennis

For information, services and offers, please visit our web site: 
http://www.klm.com. This e-mail and any attachment may contain confidential and 
privileged material intended for the addressee only. If you are not the 
addressee, you are notified that no part of the e-mail or any attachment may be 
disclosed, copied or distributed, and that any other action related to this 
e-mail or attachment is strictly prohibited, and may be unlawful. If you have 
received this e-mail by error, please notify the sender immediately by return 
e-mail, and delete this message. 

Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its 
employees shall not be liable for the incorrect or incomplete transmission of 
this e-mail or any attachments, nor responsible for any delay in receipt. 
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch 
Airlines) is registered in Amstelveen, The Netherlands, with registered number 
33014286

Migrate from TSM Server 5.5.7 on Windows to TSM Server 7.1.7 on Linux - the unsupported way because exportdb --> insertdb did not work

[Schneck, Dennis]

Hello,
how to migrate from TSM Server 5.5.x on Windows to TSM Server 7.1.7 on Linux ( 
only one tape library ) ?
because my way ( see 2nd ) is not supported


1st I tryed: ( exportdb --> insertdb )

VM1: TSM 5.5.7 on Windows and VM2: TSM 7.1.7 on Windows

VM1:
restore backup from productive System.
install UpgradeTool

VM2:
migrate on VM2 with dsmupgdx from VM1
then I had TSM 7.1.7 running.
Did a exportdb on TSM 7.1.7 on Windows

If "insertdb" on Linux TSM Server 7.1.7 got this error:

/opt/tivoli/tsm/server/bin/dsmserv insertdb manifest=/import/manifest.txt

IBM Tivoli Storage Manager for Linux/x86_64 Version 7, Release 1, Level 7.100
...
"ANR1953E INSERTDB: Linux/x86_64 cannot be the target of a database upgrade 
from Windows."



2nd I tryed: ( local migrate )

Install TSM Server 5.5.7 on Linux ( SLES 12 SP2 ) + TSM Client 5.5.4.0
restore backup from productive System.
Install UpgradeTool

Upgrade to TSM 7.1.3 an run "dsmupgdx"
for migrate local Server (Network Method).
Then TSM Server 7.1.3 is running with Data from TSM Server 5.5.x Windows
Then Update to 7.1.7.300

this works... but IBM support say by phonecall - " .. this is not supported " 
:-(



Any proposals for a supported way ?



Thanks
Dennis

Re: ndmp

[Stefan Folkerts]

Same here, we have more than a few clients running NAS solutions going up
to I believe about 200TB and the backups are done via a windows server
connected to cifs shares.
file attributes might become an issue if the NAS is sharing via CIFS and
NFS but other than that it seems to work okay, it's a pity (but logical)
that you can't run journalled backups but at least you can backup 10+
shares at once, still, if you have many small files backups can take a long
time to complete and don't undersize the server that will be running the
backups either.


On Wed, Aug 2, 2017 at 12:04 AM, Skylar Thompson 
wrote:

> I agree, we use this approach as well. NDMP has scaling issues, doesn't
> play nicely with TSM incremental backups or include/exclude lists, and ties
> you into a single storage vendor for both backups and restores. That last
> point is particularly scary for anyone writing DR plans, since who knows
> what storage you'll end up with after a real disaster.
>
> On Tue, Aug 01, 2017 at 09:27:06PM +, Thomas Denier wrote:
> > You might be better off having proxy systems access the NAS contents
> using CIFS and/or NFS, and having the proxy systems use the backup/archive
> client to back up the NAS contents.
> >
> > My department supports Commvault as well as TSM (the result of a merger
> of previously separate IT organizations). The Commvault workload includes a
> NAS server on the same scale as yours. Our Commvault representative advised
> us to forget about Commvault's NDMP support and use the Commvault analog of
> the approach described in the previous paragraph.
> >
> > The subject of NAS backup coverage arose at an IBM training/marketing
> event for the Spectrum family of products. The IBM representative who
> responded was not as bluntly dismissive of NDMP as our Commvault
> representative, but he sounded decidedly unenthusiastic when he mentioned
> NDMP as a possible approach to NAS backups.
> >
> > Thomas Denier,
> > Thomas Jefferson University
> >
> > -Original Message-
> > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf
> Of Remco Post
> > Sent: Monday, July 31, 2017 16:41
> > To: ADSM-L@VM.MARIST.EDU
> > Subject: [ADSM-L] ndmp
> >
> > Hi all,
> >
> > I???m working on a large TSM implementation for a customer who also has
> HDS NAS systems, and quite some data in those systems, more than 100 TB
> that needs to be backed up. We were planning to go 100% directory container
> for the new environment, but alas IBM???s ???best of both worlds" (DISK &
> FILE) doesn???t support NDMP and I don???t like FILE with deduplication
> (too much of a hassle), so is it really true, are we really stuck with
> tape? ISn???t it about time after so many years that IBM finally gives us a
> decent solution to backup NAS systems?
> >
> > --
> >
> >  Met vriendelijke groeten/Kind Regards,
> >
> > Remco Post
> > r.p...@plcs.nl
> > +31 6 248 21 622
> > The information contained in this transmission contains privileged and
> confidential information. It is intended only for the use of the person
> named above. If you are not the intended recipient, you are hereby notified
> that any review, dissemination, distribution or duplication of this
> communication is strictly prohibited. If you are not the intended
> recipient, please contact the sender by reply email and destroy all copies
> of the original message.
> >
> > CAUTION: Intended recipients should NOT use email communication for
> emergent or urgent health care matters.
> >
>
> --
> -- Skylar Thompson (skyl...@u.washington.edu)
> -- Genome Sciences Department, System Administrator
> -- Foege Building S046, (206)-685-7354
> -- University of Washington School of Medicine
>