On 5/20/07, Richard Sims [EMAIL PROTECTED] wrote:
On May 20, 2007, at 3:01 AM, Michael Green wrote:
For some reason that is beyond my understanding I cannot delete a db
backup volume of type DBS from the volume history:
...
Ostensibly because it is the sole and last DBSnapshot. See IBM
Hi Pierre,
Sorry I was not very clear the first time.
Since many people are familiar with the TSM Backup/Archive client,
I was trying to relate the policy management of an Exchange backup
with how the TSM Backup/Archive client handles file-level
policy management. With the TSM Backup/Archive,
On May 21, 2007, at 6:29 AM, Michael Green wrote:
Richard, you are right, however in this specific case I'm not trying
to remove the last and only DBS that is left.
There are 2 (two) database snapshots, one from 05/06/2007 and the
other one from 20/06/2007. I expect that running 'del volh
On 5/21/07, Richard Sims [EMAIL PROTECTED] wrote:
Michael -
I think you mean 05/20/2007 in the above.
yes!
There are two other factors at play as well...
First, the volume location information says offsite. That suggests
the use of TSM DRM, and in that case, DELete VOLHistory should not
Hi Del,
Yes it help me.
Sorry but I'm not english naturaly speaking so I need plain explanation...
And your's are perfectly clear.
I already know the rebinding of incremental data's when changing the management
class.
But, with some naiveté I thaught that the management binding by TSM was
I want to run this idea by the experts, to make sure I am not spinning my
wheels or really far off base.
I currently have an AIX TSM server as the sole library manager for this
3494. I need to migrate everything off to a new Linux servers.
I want to move the library management function to this
Hi,
We have recently upgraded our Tivoli Netware Clients to version 5.3.2 to match
our backend version. We run a 4 node cluster and it has become apparent that
since the update when failing resources across nodes the Tivoli client does not
unload automatically and now waits for user input
In your dsm.opt file you need this line:
NWEXITNLMPrompt NO
--Matt
On 5/21/2007 at 7:52 AM, William Kyndt [EMAIL PROTECTED] wrote:
Hi,
We have recently upgraded our Tivoli Netware Clients to version 5.3.2 to
match our backend version. We run a 4 node cluster and it has become
In this case, the iSCSI devices are being used as Raw devices, not
filesystems, so filesystem bottlenecks would not be the issue.
Thanks for the brainstorming though.
Ben
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Richard Sims
Sent: Sunday,
I need to setup an Exchange 2003 cluster with TDP Exchange. The cluster has
8 active nodes 2 inactive nodes.
The part I am having a problem is do I set them all up with the same TSM
node name or use different node names for each server?
Thanks,
Hi Bruce,
I recommend having a different TSM NODENAME for each
virtual Exchange server. I assume that your 2 inactive nodes
could run any of the 8 other virtual Exchange servers.
In that case, you need to configure those 2 inactive nodes
to be able to work with any of the 8 virtual servers.
If
Our TSM server is on AIX. The question I have is: Do I need to run a mksysb
daily (rotating on a seven-day schedule) to keep the DRM plan (including
scripts to explode) offsite going forward? How are some of you guys/gals
getting your DRM plan offsite so that you can use it upon restore your OS
I've always emailed the prepare file to myself. The things that change
daily are the DB Backup/Snapshot volume, and the macro's to mark the
storage pool volumes unavailable/offline/readonly. From the email I can
get the DB Backup volume, and for the storage pool volume access changes, I
run an
Hi.
We perform an IBM AIX sysback every third month. Each working day, we
have a script that creates the DB snapshoot, un-loads the off-site
tapes. We then create a tmp directory, which uses IBM AIX sysback to
place the TSM DR plan and the required DR files for recovering TSM
system,
Nick Cassimatis...
Is your E-Mail system at a third location??
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Nicholas Cassimatis
Sent: Monday, May 21, 2007 12:22 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Fw: DRM Plan use in DR Test
I've
Over the years the method has been different. These days I have a script
that does a full backup of the TSM database, then the one below to
capture relevent config files on the TSM Server. These are rcped to
another server in a remote location.
Our DR is to restore the databse to a instance on
Yes, it's very geographically separated from where my TSM Servers are, but
then being in a big company does that. However, since I have a local
mailfile, I always have the latest Prepare file. By sending it to multiple
people in multiple locations, I get a good disbursement of the plan file.
Both
Can someone answer his question about the INCLUDES section of the dsn.opt?
Thanks,
---
Bruce Kamp
Senior Server Analyst
Memorial Healthcare System
E-Mail: [EMAIL PROTECTED]
Phone: (954) 276-4097
Fax: (954) 276-5381
I see some incorrect statements below.
You will need a different DSM.OPT file for each of your
Exchange virtual servers. You do not put all
six NODENAMEs in a single DSM.OPT file.
The INCLUDEs for each server will be in the
DSM.OPT file set up for that specific virtual server.
You would then
19 matches
Mail list logo