Hi all
I have an EXCHANGE SERVER backing up via TDP for Exchange
I have 3 Management classes with different Retention periods i.e
EXCHANGE - 30 Days, EXCHANGE_MONTHLY - 365 DAYS and EXCHANGE_YEARLY -
2555 Days
I have 1 node and 4 schedules associated, i.e Daily Incremental, Weekly
Full,
If you truly do only have one node, you have effectively shot yourself
in the proverbial foot - every time you run the tdp to a different mgmt
class it is going to rebind EVERYTHING for that node. So whatever
monthly/yearly backups you had were rebound to the daily class and
expired.
You need to
Hi Richard
Thanks for confirming that. I presumed it was much the same as MSSQL TDP
that requires different nodes for each Management class requried.
I'll try that and see if it solves the retention problem.
Regards
Adrian
-Original Message-
From: Richard Sims [mailto:[EMAIL
Hi,
I can confirm you that it is the case, for each different retention you need a
different node, unless you will face rebinding of all data's to the last
management class used at each backup.
And it will be the same for all TDP using backup copy group.
Pierre
> -Message d'origine-
>
Adrian,
Are you sure that you are getting what you want? By assigning
several nodes to various retention levels, are you backing up each node
every day?
If your EXCHANGE_MONTHLY node only backs up once a month, all of the
changes that have happened during the month will NOT be captured and
All,
I am getting quite a errors in my act log.. any ideas?
Date/Time Message
--
11/19/07 09:15:27 ANR8216W Error sending data on socket 26. Reason
Hello Everyone,
I want to upgrade our TSM server so that we can use TDP; the version compatible
with Exchange 2007 x64 but it seems there is only a version 5.5.0. Do I have to
upgrade to TSM server 5.5.0 to get Exchange 2007 TDP? Currently we are running
5.3.3 TDP for our Exchange Server 2003
I haven't rolled to v5.5.0 - yet...
I have TSM v5.3.5 Server and on the Exchange 2007 x64 - TSM v5.4.1.3 and TDP
v.5.4.1.0.
But, it does "Legacy-Backups" only... We don't have the necessary components
for the VSS-backups.
You have to get the TDP v.5.4.1.0 from the "Passport" website...
FYI,
Hi, I'm still having problems on the backup of domino
[EMAIL PROTECTED]:/opt/tivoli/tsm/client/domino/bin/domdsmc_notes> ./domdsmc
query domino
ACD5130E Could not initialize the connection to Lotus Domino properly.
error=1543
The connection with tsm server is okay when i execute ./domdsmc que
What's the storage agent support rule in relation to the server. Is storage
agent 5.3.4.0 supported with server 5.3.6.0?
Am I the only one who has difficulty finding the software you need on the
Passport site?
I can find version 5.5.0 and 5.3.3 among several older ones...
http://www.ibm.com/products/finder/us/finders?lc=en&C2=5000787&C1=5000674&tmpl=%2Fproducts%2Ffinder%2Fus%2Fen%2Ffinders&ibm-go.y=9&ibm-go.x=20&s
Sorry for the miscommunication...
v.5.4.1 does support VSS-backups.
I meant that my facility doesn't have the necessary components.
Troy
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Daniel Lane
Sent: Monday, November 19, 2007 1:15 PM
To: ADSM-L
Hello,
Can you tell me how to update the schedule to run a backup every hour
? thanks for your help.
>From the client side:
Schedule name: 2100_somename
Description:
Schedule Style: Classic
Action: Incremental
Options: -subdir=yes
Objects:
Priority:5
Next Execution: 23 Hours and 17 Minutes
Avy,
Something like the following is what you could do to change it to run
hourly. This assumes that it can complete in less than an hour,
otherwise sometimes you will get a "missed" backup for those times that
run longer than an hour.
Update schedule standard 2100_something duration=15 durunits
I would make it DURATION=59 DURUNITS=MINUTES. That way if the previous hourly
backup ran longer, it would have an extra 59-minutes
before registered as a miss. Instead of only an extra 15-minutes.
Bill Boyer
"My problem was caused my a loose screw at the keyboard" - ??
-Original Message
Hi here are some details of my problem
With TDP de Domino in Linux.
Getting the following
mail1:/opt/tivoli/tsm/client/domino/bin # su - notes
[EMAIL PROTECTED]:/opt/tivoli/tsm/client/domino/bin> ./domdsmc query domino
IBM Tivoli Storage Manager for Mail:
Data Protection for Lotus
Thank you Bill and Larry..(o :
Avy Wong
Business Continuity Administrator
Mohegan Sun
1 Mohegan Sun Blvd
Uncasville, CT 06382
(860)862-8164
(cell) (860)961-6976
William Boyer
<[EMAIL PROTECTED]
.NET> To
The TDP for Domino is a sensitive beast. One of the reasons for this is
that it uses a wrapper script that runs in every environment that domino
can run in to determine which operating system, architecture and other
relevant information.
I suggest that you re-install TDP from scratch, and pay car
Just a watch-for. I have installed both 32-bit and 64-bit TSM server
upgrades for Windows. In both cases the upgrade went fine, but I had to
start the server at an OS prompt the first time to do a dsmserv upgradedb.
The installation script did not do this for me as it did in previous
releases.
b.t
thanks, but isn't ISC on version 6.01 ?
On Nov 20, 2007 5:46 AM, Joerg Pohlmann <[EMAIL PROTECTED]> wrote:
> Just a watch-for. I have installed both 32-bit and 64-bit TSM server
> upgrades for Windows. In both cases the upgrade went fine, but I had to
> start the server at an OS prompt the first t
Shouldn't it be:
upd sched standard 2100_something dur=59 duru=minutes period=1 peru=hours
???
On Nov 19, 2007 11:14 PM, Mcnutt, Larry E. <[EMAIL PROTECTED]> wrote:
> Avy,
>
> Something like the following is what you could do to change it to run
> hourly. This assumes that it can complete in
21 matches
Mail list logo
