I found the problem. There was a leftover replicated node from previous testing, with the same name. Replicated nodes don't show up when doing a "q node" so I wasn't seeing it on the new server. Thanks for the fresh eyes.
From: Dury, John C. Sent: Wednesday, September 11, 2013 2:02 PM To: 'ADSM-L (ADSM-L@VM.MARIST.EDU)' Subject: Re: [ADSM-L] ANR1817W when exporting node to another server That is exactly what I am trying to do. John - What happens if you specify a specific node name that hasn't been exported - yet? On Wed, Sep 11, 2013 at 12:20 PM, Dury, John C. <JDury AT duqlight DOT com> wrote: > I have tried several combinations of the following and they all fail with > the output listed below. > > export node toserver=LINUXSERVER filespace=* filedata=all > export node toserver=LINUXSERVER filedata=all > export node toserver=LINUXSERVER filedata=all replacedefs=yes > mergefilespaces=yes > export node toserver=LINUXSERVER filedata=all replacedefs=no > mergefilespaces=no > export node toserver=LINUXSERVER filedata=all domain=standard > > > > - Didn't notice the actual EXPORT command/options you used? > > > On Wed, Sep 11, 2013 at 8:30 AM, Dury, John C. <JDury AT duqlight DOT com> > wrote: > > > We have 2 6.3.4.0 TSM servers, one AIX and one linux. We want to move all > > of the data from the AIX server to the linux server and then eventually > > retire the AIX server. I understand I can also do this with replication, > > but because the lijnux server will eventually be replicating to a second > > linux server at a remote site and until the whole process is complete, > the > > AIX server will still be doing backups, I thought exporting node data > would > > be a simpler solution. > > I have the AIX and linux servers talking to each other and was able to > > successfully export admins from the AIX server directory to the linux > > server but when I try to export a node from AIX to linux, I get the > > following messages during the process and I'm not sure why. I've tried > > every combination of replacedefs and mergefilespaces but all get the same > > errors. Here is the output from the "export node". The output below was > > sanitized but should be easily readable. > > > > Ideas anyone? > > > > > > 09/11/2013 08:03:32 ANR0984I Process 667 for EXPORT NODE started in the > > BACKGROUND at 08:03:32. (SESSION: 744051, PROCESS: > > 667) > > 09/11/2013 08:03:32 ANR0609I EXPORT NODE started as process 667. > (SESSION: > > 744051, PROCESS: 667) > > 09/11/2013 08:03:32 ANR0402I Session 744080 started for administrator > > ADMINID > > (Server) (Memory IPC). (SESSION: 744051, PROCESS: > > 667) > > 09/11/2013 08:03:32 ANR0408I Session 744081 started for server > LINUXSERVER > > (Linux/x86_64) (Tcp/Ip) for general administration. > > (SESSION: 744051, PROCESS: 667) > > 09/11/2013 08:03:32 ANR0610I EXPORT NODE started by ADMINID as process > > 667. > > (SESSION: 744051, PROCESS: 667) > > 09/11/2013 08:03:33 ANR0635I EXPORT NODE: Processing node NODENAME in > > domain > > STANDARD. (SESSION: 744051, PROCESS: 667) > > 09/11/2013 08:03:33 ANR0637I EXPORT NODE: Processing file space > > \\NODENAME\c$<file:///\\NODENAME\c$> > > for node NODENAME fsId 1 . (SESSION: 744051, > PROCESS: > > 667) > > 09/11/2013 08:03:33 ANR0637I EXPORT NODE: Processing file space > > \\NODENAME\d$<file:///\\NODENAME\d$> > > for node NODENAME fsId 2 . (SESSION: 744051, > PROCESS: > > 667) > > 09/11/2013 08:04:09 ANR8337I LTO volume TAPEVOLUME mounted in drive > > TAPEDRIVE > > (/dev/rmt4). (SESSION: 744051, PROCESS: 667) > > 09/11/2013 08:04:09 ANR0512I Process 667 opened input volume TAPEVOLUME. > > (SESSION: > > 744051, PROCESS: 667) > > 09/11/2013 08:05:37 ANR1817W EXPORT NODE: No valid nodes were identified > > for > > import on target server LINUXSERVER. (SESSION: > > 744051, > > PROCESS: 667) > > 09/11/2013 08:05:37 ANR0562I EXPORT NODE: Data transfer complete, > deleting > > temporary data. (SESSION: 744051, PROCESS: 667) > > 09/11/2013 08:05:37 ANR0405I Session 744081 ended for administrator > > LINUXSERVER > > (Linux/x86_64). (SESSION: 744051, PROCESS: 667) > > 09/11/2013 08:05:37 ANR0515I Process 667 closed volume TAPEVOLUME. > > (SESSION: > > 744051, PROCESS: 667) > > 09/11/2013 08:05:37 ANR0724E EXPORT NODE: Processing terminated > > abnormally - > > transaction failure. (SESSION: 744051, PROCESS: > 667) > > 09/11/2013 08:05:37 ANR0626I EXPORT NODE: Copied 1 node definitions. > > (SESSION: > > 744051, PROCESS: 667) > > 09/11/2013 08:05:37 ANR0627I EXPORT NODE: Copied 2 file spaces 0 archive > > files, 1 backup files, and 0 space managed files. > > (SESSION: 744051, PROCESS: 667) > > 09/11/2013 08:05:37 ANR0629I EXPORT NODE: Copied 1589 bytes of data. > > (SESSION: > > 744051, PROCESS: 667) > > 09/11/2013 08:05:37 ANR0611I EXPORT NODE started by ADMINID as process > > 667 has > > ended. (SESSION: 744051, PROCESS: 667) > > 09/11/2013 08:05:37 ANR0986I Process 667 for EXPORT NODE running in the > > BACKGROUND processed 4 items for a total of 1,589 > > bytes > > with a completion state of FAILURE at 08:05:37. > > (SESSION: > > 744051, PROCESS: 667) > > 09/11/2013 08:05:37 ANR1893E Process 667 for EXPORT NODE completed with > a > > completion state of FAILURE. (SESSION: 744051, > > PROCESS: > > 667) > > 09/11/2013 08:07:40 ANR2017I Administrator ADMINID issued command: QUERY > > ACTLOG search='process: 667' (SESSION: 744051) > > >
