One thing that hasn't been mentioned yet is how the use of FILE or DISK impacts
server recovery. If you have to restore your database, you will have to audit
all of your DISK volumes. You can avoid auditing FILE or TAPE volumes through
the use of REUSEDELAY.
..Paul
At 01:52 PM 2/13/2015, Zol
ry 13, 2015 7:37 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] DEVCLASS=FILE - what am I missing
FILE allows deduplication; DISK doesn't.
My impression after some experimenting is that FILE wasn't meant to replace
DISK; it was solely meant to replace tape device classes. We didn'
t reclaim, but
> you can manually move the data.
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
> Nick Laflamme
> Sent: Friday, February 13, 2015 10:37 AM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: DEVCLASS=FILE - what
;normal" value so you can investigate before disaster sets in.
>
> Good luck!
>
> Wanda Prather
> TSM Consultant
> ICF International Enterprise and Cybersecurity Systems Division
>
>
>
>
>
> -Original Message-
> From: ADSM: Dist Stor Manager
Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Nick
Laflamme
Sent: Friday, February 13, 2015 10:37 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: DEVCLASS=FILE - what am I missing
FILE allows deduplication; DISK doesn't.
My impression after some experimenting is that FILE wasn'
y Systems Division
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan
Forray
Sent: Friday, February 13, 2015 12:13 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] DEVCLASS=FILE - what am I missing
Up until recently, I have always used DEVCLAS
FILE allows deduplication; DISK doesn't.
My impression after some experimenting is that FILE wasn't meant to replace
DISK; it was solely meant to replace tape device classes. We didn't need
to, so those experiments quietly ended.
On Fri, Feb 13, 2015 at 12:30 PM, Zoltan Forray wrote:
> WOW - I
WOW - I didn't realize that. Thanks for pointing that out.
Won't automatically go to nextstgpool, didn't automatically reclaim? So,
what is the advantage/benefit of DEVCLASS=FILE? Sounds like time to go
back to DEVCLASS=DISK
On Fri, Feb 13, 2015 at 1:22 PM, Paul Zarnowski wrote:
> At 12:12
Sure there were plenty of errors:
2/12/2015 10:00:23 PM ANR0522W Transaction failed for session 2639 for node
RO-CVS (Linux x86-64) - no space available in storage pool BACKUPPOOL and
all successor pools.
2/12/2015 10:04:20 PM ANR0522W Transaction failed for session 2648 for node
RDO3 (WinNT) - no
At 12:12 PM 2/13/2015, Zoltan Forray wrote:
>Well, last night became a disaster. Backups failing all over because it
>couldn't allocate any more files and also would not automatically shift to
>use the "nextpool" which is defined as a tape pool.
Alas, TSM doesn't automatically "roll over" when th
As the number of vols is damn close to Max scratch. I'd say you ran out.
No thing in actlog? Bung it up and see what happens.
On Fri, 13 Feb 2015 17:15 Zoltan Forray wrote:
> Up until recently, I have always used DEVCLASS=DISK for disk storage and
> always preformatted/allocated the disk volume
Up until recently, I have always used DEVCLASS=DISK for disk storage and
always preformatted/allocated the disk volumes into multiple chunks to all
for multi-I/O benefits.
When I recently stood-up a new server, I decided to try DEVCLASS=FILE for
disk-based storage/incoming backups.
I thought I un
12 matches
Mail list logo
