ot;ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:(bcc: John Naylor/HAV/SSE)
Subject: Re: Handling spikes in storage transfer
Did that. TERSE is on and the log contains only the summary of what is
going on. No file info.
Don't have access to this system. I
OTECTED]]
> Sent: Tuesday, January 15, 2002 8:49 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Handling spikes in storage transfer
>
>
> Did that. TERSE is on and the log contains only the summary of what is
> going on. No file info.
>
> Don't have access to this system.
ot;ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
01/14/2002 03:04 PM
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject:Re: Handling spikes in storage transfer
Get the client's dsmsched.log file (best way);
or que
Sounds like they have started doing a SEL /* instead of an INCR /* and are
backing up everything. Typical user error.
-Original Message-
From: Zoltan Forray/AC/VCU [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 14, 2002 9:47 AM
To: [EMAIL PROTECTED]
Subject: Handling spikes in storage
, January 14, 2002 11:13 AM
To: [EMAIL PROTECTED]
Subject: Re: Handling spikes in storage transfer
Try this... but alter the "<1" to fit your need... maybe need <2 etc...
select * from adsm.backups where (node_name='YOUR_NODE' and
cast((current_timestamp-backup_da
e-mail: [EMAIL PROTECTED] - voice: 804-828-4807
"Denis L'Huillier" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
01/14/2002 02:33 PM
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc
Er, from contents. Oops.
-Original Message-
From: Alex Paschal
Sent: Monday, January 14, 2002 2:01 PM
To: 'ADSM: Dist Stor Manager'
Subject: RE: Handling spikes in storage transfer
Zoltan,
from a *nix box, I suggest
dsmadmc -server=serverstanza -id=id -password=password -
Freightliner, LLC
(503) 745-6850 phone/vmail
-Original Message-
From: Zoltan Forray/AC/VCU [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 14, 2002 12:04 PM
To: [EMAIL PROTECTED]
Subject: Re: Handling spikes in storage transfer
I am pretty sure it isn't a growth in the # of files.
before the first
big backup
Robin Sharpe
Berlex Labs
"Zoltan
Forray/AC/VCU
" To:[EMAIL PROTECTED]
Subject:
Re: Handl
53-8000 ofc
425-988-8478 fax
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
> Zoltan Forray/AC/VCU
> Sent: Monday, January 14, 2002 2:56 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Handling spikes in storage transfer
>
>
>
r"
To: [EMAIL PROTECTED]
cc:
Subject: Re: Handling spikes in storage transfer
Do you still have the older sessions in your actlog? Or you could look in
the summary table. Try to see if it's because of a lot more files, or
just
more data. If not
]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
01/14/2002 02:33 PM
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject:Re: Handling spikes in storage transfer
Try,
select sum(bytes) from sum
ttp://admpwb01/misc/misc/storage_forms_main.html
Zoltan
Forray/AC/VCUTo: [EMAIL PROTECTED]
Subject: Re: Handling spikes in storage
transfer
Sent by:
Do you still have the older sessions in your actlog? Or you could look in
the summary table. Try to see if it's because of a lot more files, or just
more data. If not many more files, look in the contents table for files
larger than 30GB. If none found, gradually decrease the size until you
f
ailto:[EMAIL PROTECTED]]
> Sent: Monday, January 14, 2002 11:13 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Handling spikes in storage transfer
>
>
> Try this... but alter the "<1" to fit your need... maybe need
> <2 etc...
>
> select * from adsm.backups whe
atis <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
01/14/2002 11:05 AM
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject:Re: Handling spikes in storage transfer
If you kn
[EMAIL PROTECTED]>
01/14/2002 11:05 AM
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject: Re: Handling spikes in storage transfer
If you know what node it is (sounds like you do), you can run "q occ"
daily, and
ECTED]]
Sent: Monday, January 14, 2002 10:02 AM
To: [EMAIL PROTECTED]
Subject: Re: Handling spikes in storage transfer
I already tried that. The information it gives isn't detailed enough. It
just tells me about the filespaces.
I need to know specifics, such as the names/sizes of th
If you know what node it is (sounds like you do), you can run "q occ"
daily, and see what filesystem is increasing the number of files stored and
space occupied. Once you know the filesystem, you can approach the system
owner with a more direct question. Can't help with the non-response part
(ma
<[EMAIL PROTECTED]>
01/14/2002 10:29 AM
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject:Re: Handling spikes in storage transfer
Do a "q occ " and look for what file systems are out on your
diskpool in
Do a "q occ " and look for what file systems are out on your
diskpool in great quantity.
That is, if you send all data first to a diskpool and then bleed it off to
tape (daily).
That will give you an idea of what file systems are sending the most data,
currently.
Then you may perform something lik
21 matches
Mail list logo
