Hi,
I tried putting a non-mount point in the domain line, but the client
didn't like that. Recommendations?
You can use the virtualmountpoint option on unix clients.
Place the following option in dsm.sys:
virtualmountpoint /etc
and then define /etc as a domain in dsm.opt:
domain /etc
This
Has any one run into evault as a competitor to TSM? Can anyone share their
experiences if you have worked with eVault in the past specifically as it
relates to iSeries?
Thanks
For Dave:
Try using the "virtualmountpoint".
This allows just what you want. It telss tsm to treat the specified
directory tree as if it were a real mountpoint.
Good luck.
Gary Lee
Senior System Programmer
Ball State University
phone: 765-285-1310
-Original Message-
From: ADSM: Dis
Take a look at the "virtual mountpoint" feature on the Backup Archive Client
Installation and User's Guide.
On 7/18/07, Dave Mussulman <[EMAIL PROTECTED]> wrote:
I have a few systems I'd like to add to TSM but only backup a few
directory hierarchies. These aren't always mount points (for examp
On Jul 18, 2007, at 1:06 PM, Dave Mussulman wrote:
I have a few systems I'd like to add to TSM but only backup a few
directory hierarchies. These aren't always mount points (for example,
the /etc directory under the / mount point.) Does TSM really not
have a
way for me to define "just back up
Specify the directories in the command line, e.g.:
dsmc i /dir1/ /dir2/ /etc/ -subdir=yes
etc.
You can define a separate schedule for the machine and put the directories
in the OBJECTS field of the schedule, e.g.:
def schedule standard special objects="/dir1/ /dir2/ /etc/"
options="-subdi
Our sequence:
backup
db backup
disk to copy pool
migration
cartridge primary pool to copypool (in case some did not complete
before migration)
db backup
expiration
reclamation
>>> [EMAIL PROTECTED] 07/18/2007 2:13 PM >>>
Wouldn't you want to backup primary to copy before migration? That
way
you'r
Wouldn't you want to backup primary to copy before migration? That way
you're doing that from disk. If you migrate then backup primary to
copy, you're doing the copy from tape to tape, rather than from disk to
tape. In addition, it gets your offsite copies created earlier in the
cycle, so that y
I have a few systems I'd like to add to TSM but only backup a few
directory hierarchies. These aren't always mount points (for example,
the /etc directory under the / mount point.) Does TSM really not have a
way for me to define "just back up X" without worrying about anything
else on that mount?
After a bit more thought, I believe I follow the problem through now. Our
offsite copy tape pool supports multiple primary pools and IS subject to
reclamation so presumably the full tapes in the primary (unchanging) pool will
still be read on occasion to support reclamation on the offsite copy p
Thanks for that Richard. Reclamation should not be an issue because the content
of a full tape in this pool never changes. Once full, the tapes just sit there
taking up space. I've noticed in TSMManager that I have the option to checkout
a tape to onsite storage so I may experiment with that.
I
On Jul 18, 2007, at 8:40 AM, Angus Macdonald wrote:
So can I take it my suggestion won't work?
Checking tapes out of a library will work to create empty cells in
the library, but is problematic in that it is an "out of band"
measure. TSM is enterprise software, with a rules set and regimen to
I agree with Mark on this one, with the exception that I would do the drm
processing after backing up the primary to the copypool, and then backup the db
and then run a prepare. That way the copypool volumes show up as offsite and
won't be marked as destroyed in case of a disaster.
Cory Heikel
As always, it depends . . .
Our TSM DB is on raided enterprise disk (IBM DS8100 behind a SAN Volume
control) as is our TSM LOGs. We run our logs in roll forward mode. The odds
of losing both the DB and LOG except in a DR situation is small. If we have to
restore the DB, we can roll forward us
I believe the best practise is
Backup
Migration
Backup primary to copy
Backup db
Expiration
Reclamation
Start all over again
:)
Cheers
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Timothy Hughes
Sent: Wednesday, 18 July 2007 9:14 PM
To: ADSM-L
Hi,
You plan your ITSM db backups depending on how much data you want to
loose or time want to spent rerunning ran jobs (...). And things like
re-use delays on storage pools should be also taken into account.
After having to deal with a database restore to a point before the last
reclamation run
We actually backup ours after nightly backups complete and before
migration. Is there a
specific recommended order or is it up to each individual site and it's
environment?
Helder Garcia wrote:
You should backup db after migration and before expiration.
On 7/17/07, Gregory Lynch <[EMAIL PROTEC
So can I take it my suggestion won't work?
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Richard Sims
Sent: 18 July 2007 12:58
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Checkout full, unchanging tape volumes
On Jul 18, 2007, at 7:50 AM, Angus M
You should backup db after migration and before expiration.
On 7/17/07, Gregory Lynch <[EMAIL PROTECTED]> wrote:
Hello all,
How many times a day should I be backing up the TSM DB and should it be
after migration?
Thanks
Greg
***
On Jul 18, 2007, at 7:50 AM, Angus Macdonald wrote:
I support a TSM 5.3 installation with a 3582 library, which is
running out of local capacity. One of the tape pools is used
exclusively for a large body of files which receive regular
additions but are never changed or deleted. The tapes in the
I support a TSM 5.3 installation with a 3582 library, which is running out of
local capacity. One of the tape pools is used exclusively for a large body of
files which receive regular additions but are never changed or deleted. The
tapes in the pool are all full, apart from the one that is being
21 matches
Mail list logo
