filespace no longer backed up because mount or drive is gone

ADSM-L

[Top] [All Lists]

filespace no longer backed up because mount or drive is gone

2003-01-24 14:18:19

Subject:	filespace no longer backed up because mount or drive is gone
From:	"Gill, Geoffrey L." <GEOFFREY.L.GILL AT SAIC DOT COM>
To:	ADSM-L AT VM.MARIST DOT EDU
Date:	Fri, 24 Jan 2003 11:17:27 -0800

Can anyone tell me what the affect is if a filespace no longer exists? Lets
say either a drive D on a Windows server or /cost1 is no longer on a unix
client. The filespace is no longer on the new client with the same name so
it hasn't been touched in say 180 days. What is really there? Does the
management class settings have any affect on it?

Geoff Gill
TSM Administrator
NT Systems Support Engineer
SAIC
E-Mail:    <mailto:gillg AT saic DOT com> gillg AT saic DOT com
Phone:  (858) 826-4062
Pager:   (877) 905-7154

[More with this subject...]

<Prev in Thread]	Current Thread	[Next in Thread>
filespace no longer backed up because mount or drive is gone, Gill, Geoffrey L. <= Re: filespace no longer backed up because mount or drive is gone, Ford, Phillip Re: filespace no longer backed up because mount or drive is gone, Andrew Raibeck Re: filespace no longer backed up because mount or drive is gone, Adams, Matt (US - Hermitage)

Previous by Date:	upgrade tivoli from 4.2 to 5.1.5 on AIX, Roger Ward
Next by Date:	Re: Quickie: can BACKUP STGPOOL be preempted by a client restore?, TSM Mailing List
Previous by Thread:	upgrade tivoli from 4.2 to 5.1.5 on AIX, Roger Ward
Next by Thread:	Re: filespace no longer backed up because mount or drive is gone, Ford, Phillip
Indexes:	[Date] [Thread] [Top] [All Lists]