Op 16 jan. 2014, om 11:25 heeft Karel Bos <tsm....@gmail.com> het volgende geschreven:
> Hi, > > Just got word back from ibm support. Its WaD and if I feel it should change > feel free to file RfE. as if it's completely unthinkable that the design is flawed. A defect in the design is still a defect. (just my humble opinion) > > In the meantime make sure sta client data is in the libraries sta has paths > to. > > Kind regards, > Karel > Op 14 jan. 2014 22:53 schreef "Karel Bos" <tsm....@gmail.com>: > >> Hi, >> >> Yes, data paths are set to any. >> >> Kind regards, >> Karel >> Op 14 jan. 2014 15:35 schreef "Huebner, Andy" <andy.hueb...@novartis.com>: >> >>> Is the node data read and write paths set to ANY in the node >>> configuration on the TSM server? >>> >>> Data Write Path: ANY >>> Data Read Path: ANY >>> >>> Andy Huebner >>> >>> -----Original Message----- >>> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of >>> Karel Bos >>> Sent: Tuesday, January 14, 2014 1:20 AM >>> To: ADSM-L@VM.MARIST.EDU >>> Subject: [ADSM-L] Lanfree restore fails when STA has no path to lib >>> containing data >>> >>> Hi, >>> >>> We have a tsm 6.2 server with 3 libs. Lib A hold copypool, B hold data >>> migrated from disk pool and C hold lanfree backup data. >>> >>> Customer reports rman restore fails. Looking at the error log it reports >>> "data currently not available on server". Looking at the client config it >>> had beem configured to write to dp instead of lib C. >>> >>> We set enable lanfree to no and sure enough restore started running over >>> lan. >>> >>> In the past we had to place our copy pool vols to offsite to prevent >>> sta's from failing restore from copy vols due to not having paths to that >>> library. Same seems to go for prim data. >>> >>> Why isnt the client/sta failing back to lan restore (same with path >>> failures) if the only possible path available is lan? >>> >> -- Met vriendelijke groeten/Kind Regards, Remco Post r.p...@plcs.nl +31 6 248 21 622
