Thanks all for your help. much appreciated.
+--
|This was sent by [EMAIL PROTECTED] via Backup Central.
|Forward SPAM to [EMAIL PROTECTED]
+--
> A lot of people opt for the transparent encryption scheme where the
> key is held in the TSM database and it seems that IBM is moving in
> that direction with this feature being the only option in 5.5 for
> the BA-client.
The client supports three settings for ENCRYPTKEY: SAVE, PROMPT, and
GENER
I think it's a matter of considering the Schedmode and the time
window to assure that the schedule transition does not involve in any
discongruencies.
Richard Sims
Try running the following from an OS command prompt:
vssadmin list writers
How long does that take to run?
Next, start dsmc and let it sit. Does it *eventually* start? Let it sit
for a long time if needed how long does it take to start up?
Regards,
Andy
Andy Raibeck
IBM Software Group
I've never done this before and I don't think I've seen it discussed so
I'll throw this out there. I was wondering if there are any
ramifications when switching nodes to a new backup schedule. Meaning is
there a chance that the nodes will be missed? I ask this because I have
seen nodes added to a s
A lot of people opt for the transparent encryption scheme where the key is held
in the TSM database and it seems that IBM is moving in that direction with this
feature being the only option in 5.5 for the BA-client. It seems that I am the
only one who wants it the other way around.
As I see it
Check to see if you have anything in the dsierror.log. Also look in your Event
Viewer for errors. There may be a problem in your dsm.opt file.
Johnny
>>> "Large, Matthew : Barclays Wealth" <[EMAIL PROTECTED]> 3/10/2008 9:03 AM >>>
Hi ADSMers,
I've not seen this kind of problem before - I ha
In the past we had 2 times a similar problem:
first time (tsm server on mvs) the ip sequence number did a wrap around and was
not properly handled by mvs. (So large restores always stopped at different
positions)
sencond time (tsm server on nt) we realized that our network backbone did
corrupt o
Hi ADSMers,
I've not seen this kind of problem before - I have a Win32 client (5.4.1.0)
which can ping it's Solaris10 TSM server (5.4.1.2), but fails to connect.
Starting dsmc from the command line brings me no prompt, TSM appears to
deliver nothing to the screen, or the dsmerror.log.
So I ran a
Steven,
The technique that Howard described is what many customers do for
Data Protection for Exchange as well.
For example, you would have multiple node names with different policy
settings:
EXCSRV33 - for regular daily backups (with management class to keep
for 90 days)
EXCSRV33_MONTHL
We've been trying to restore a 38 GB file to a Win2003 SP1 server; the restore
comes to a near halt at 31.8 GB.
At the TSM server side (5.5.0.0) we see 'sendw', and if we leave everything
alone the restore continues at an incredibly slow pace (20 MB in 8 hours).
On the client side - CPU utiliza
.
This is not difficult.
1. Make sure that new data can be written to LTO3, via migration,
reclamation, DB Backup, etc. This must work, first.
2. Mark all the LTO2 tapes readonly.
3. Remove all LTO2 scratch tapes, and remove new ones as they are freed.
You might need these library slots to accom
I'm not sure if this is "Best" practice, but its what we do with our SQL
Servers and I imagine it would work with exchange..
We have three node names in three domains.
Exchange-exch (daily backups kept for 7 or 30 days for quick restores,
do a [first] Sunday full, then diffs the rest of the week [
Hi All,
the dutch TSM usergroup will meet on 3rd Aplril in Hendrik Ido Ambacht
(PLCS). For more info please visit http://www.tsmgg.nl/
--
Remco Post, PLCS
That second line should of course have read:
"I can restore server SERVER1 to server SERVER2"
Apologies
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Gill, Geoffrey L.
Sent: 08 March 2008 03:09
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] sql ser
Geoff
Not sure if you have had any success with this - i only read you post
this morning.
I've been through this procedure several times - this is what i have
done:
RESTORE TO ANOTHER SERVER - example SERVER1 to SERVER2
I can restore server MYSQL to server SERVER2.
Logon to SERVER2 server.
Opt
16 matches
Mail list logo