Dear List,
for a client with large filespaces, we would like to split the backup up
into several nodes in order to balance the load. On the basis of the
TSM-client documentation we created several stanzas in the dsm.sys file
with different servername entries. In the init-script several dsmc
proces
According to:
http://www.spec.org/sfs2008/results/res2012q1/sfs2008-20120201-00205.htmlthere
are two E8400 dual-cores, so I'll guess 400 PVU's.
But it's better to contact IBM Sales for this.
Regards,
Maurice van 't Loo
http://mvantloo.nl/
2012/12/11 Hans Christian Riksheim
> Hitachi 3090
-Ethan Günther wrote: -
>for a client with large filespaces, we would like to split the backup
>up
>into several nodes in order to balance the load. On the basis of the
>TSM-client documentation we created several stanzas in the dsm.sys
>file
>with different servername entries. In the init
When create archive copy group use retver=NOLimit
On Wed, Dec 12, 2012 at 6:39 PM, Lee, Gary wrote:
> Just received a request to have a few files stored in tsm essentially forever.
>
> I am trying to figure out the best way to accomplish this with minimal
> administrative overhead.
>
> So far,
Hello, Ethan. I've not seen this. Do they run if you start them manually?
How about if you remove 6.2.4.4 and backlevel to 6.2.0.0 to match the working
box?
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Ethan
Günther
Sent: Wednesday, Dec
Just received a request to have a few files stored in tsm essentially forever.
I am trying to figure out the best way to accomplish this with minimal
administrative overhead.
So far,
1. create a management class with an archive group set for days, then
archive the files.
2. create a mana
Thanks. Forgot about that one.
Gary Lee
Senior System Programmer
Ball State University
phone: 765-285-1310
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Chavdar Cholev
Sent: Wednesday, December 12, 2012 11:49 AM
To: ADSM-L@VM.MARIST.EDU
Ron:
I understand that archive is preferable, but there is sufficient data there as
to interfere with daily backups. Therefore, I want to do it with backups so as
not to re-move data.
I have a management class "permanent-retain" with a backup copygroup defined as
follows:
Also consider exporting the data with a very descriptive note taped to it.
Andy Huebner
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Ron
Delaware
Sent: Wednesday, December 12, 2012 11:08 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] perm
Gary,
The problem you will run into is that the backup data will be mixed in
with all of the other backup data, unless you have a management class that
sends the data to a separate storage pool and tape pool. If you need to
have this data isolated, archives or a separate storage pool is the only
Gary,
You really don't want to use backup's for long term retention, that is an
archive function. But if you must, you set everything to NOLIMIT NOLIMIT
NOLIMIT NOLIMIT that way the data will hang around forever, but as I
stated, Archives are the way to go
Gary,
Since you're using backup for archiving, you can route these backups to your
disk/tape archive pools, then you'll avoid having to move the data around much
once it's been saved.
Bob.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Ron
12 matches
Mail list logo
