Morning all
I'm trying to add a filesystem back in to the a Solaris client backup.
The filesystem is called /u03
I assumed ...
include /u03/.../*
... would work but it doesn't.
What am I doing wrong ?
Farren
-
I think it is " include.fs /u03 "
Met vriendelijke groet,
Theo Brettschneider
+31 (0)6 29 02 13 53
-Oorspronkelijk bericht-
Van: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] Namens Minns, Farren
- Chichester
Verzonden: donderdag 22 december 2011 9:42
Aan: ADSM-L@VM.MARIST.EDU
How are you currently excluding it? Perhaps you have a "domain" line in
your dsm.opt file.
If so remove from there, and don't forget to restart the scheduled.
Steven
On Dec 22, 2011 8:47 AM, "Minns, Farren - Chichester"
wrote:
> Morning all
>
>
>
> I'm trying to add a filesystem back in to the
Good morning.
I was hoping someone can help me with the following:-
TSM Server version 6.1.4.1
Host AIX, version 5.3 TL12
Clients back their data up initially to my EXODISKPOOL, this is then
migrated to my primary storage pool EXOSATAPOOL. When this migration is
happening I am seeing messages in
Steve, does this command also list your empty volumes:
q v stg=exosatapool stat=emp acc=reado,unav
--
jim.o...@yale.edu
On 12/22/2011 4:23 AM, Copper, Steve wrote:
...
My question is: Why is this migration process creating scratch volumes
in my filesystems when I have 666 (not made up,cu
No - I get no volumes returned.
tsm: TSM>q v stg=exosatapool stat=emp acc=reado,unav
ANR2034E QUERY VOLUME: No match found using this criteria.
ANS8001I Return code 11.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
James R Owen
Sent: 22 Dece
TSM backs up local file systems by default. If 'dsmc q inclexcl' doesn't show
that file system as being excluded, then it should be the case that you have
Domain statements (dsmc q opt) which constrain what file systems are backed up,
in which case you should simply add that file system to the D
Try:
include /u03/*
include /u03/.../*
Making sure that this will be matched first (reading from the bottom up)
before any other matching exclude statements.
Also make sure you don't have any matching "exclude.fs" or "exclude.dir"
statements anywhere (i.e. exclude.fs /u03)
-Lloyd
On 12/22/2
Check and see what MAXSCRATCH is set to on xosatapool. If you
predefined the volumes, it should probably be "0".
Also, I've seen it do this if you remove a volume from the filesystem,
then allocate new ones, but don't remove the old volume definition from
within TSM (del vol ). For some rea
Thanks Richard (and all),
It's an odd server in that I was asked to exclude everything and then just
start adding bits in (as it's remote, large, and the transfer rate is
terrible!).
Anyway you were correct, it was a simple domain statement issue.
All sorted now
Thanks to all and a Merry Xma
MAXSCRATCH is set to 999 but I was thinking along the lines of setting
it to "0" as I don't want it to ever create scratch volumes (the
filesystems only have a couple hundred MB free anyway, if that).
I think I have found the answer (prompted by Dale Jolliff). A lot of
these volumes have recently
Does anyone know how to take this select command which produces only one month
of data and allow it to go back say 1 year if possible. I have tried to figure
it out but nothing works
select date(start_time) as "Start Date",time(start_time) as "Start
Time",date(end_time) as "End Date",time(end_t
Does anyone know how to take this select command which produces only one month
of data and allow it to go back say 1 year if possible. I have tried to figure
it out but nothing works
select date(start_time) as "Start Date",time(start_time) as "Start
Time",date(end_time) as "End Date",time(end_t
I don't' think it's your select that is the problem.
enter: q status
Look for the line "activity summary retention period"
If it is set to 30 days, that's how long the summary records are kept.
If you want the records to go back longer, change it with SET SUMMARYRETENTION
nnn
Where nnn is the n
James,
set summaryretention xx
Merry Christmas
Bob.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Lepre,
James
Sent: Thursday, December 22, 2011 10:05 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Select Statement
Does anyone know how
Perfect Thank you
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Prather, Wanda
Sent: Thursday, December 22, 2011 11:10 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] [adsm] Re: Storage pool using scratch volumes instead of
empty volumes
Hi James,
Are you at least sure that your summary table has been set to keep records
older than one month ?
Check the entry "Activity Summary Retention Period" in the output of "q stat"
to verify ...
Cheers.
Arnaud
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.M
Carefully consider extending the retention on the Summary table, as the amount
of data can be large, taxing your database. What I prefer to do is keep a
smallish Summary table, given that the need to query old data is rare, where I
keep 30 days of Activity Log data in the database and older day
18 matches
Mail list logo
