Hi all,
I want to implement BMR for Win2K. I backup C:\ drive ( system dirve) with
image type.
Howerver, TSM help wrote : "If you created an image of the system drive, you
cannot restore the image to the same location because the client cannot have an
exclusive lock of the system drive."
Theref
Hi Joni,
The timestamp format is:
'-mm-dd hh:mm:ss.nn'
where:
= year
mm = month
dd = day
hh = hours
mm = minutes
ss = seconds (optional)
nn = fraction of a second (optional)
When referring to a timestamp, put it in single quotes and use the above
format, i.
Mike,
Seeing Leigh's post made me remember our IIS\Win2K restores from a few years
back. I'm 99.9% sure that we ran into problems with dll's as well before we
got out doc corrected ensureing to uncheck IIS during the install. With
Windows 2003 IIS isn't checked by default so you don' thave to
Thanks everyone for your replies. Every single one of them was useful,
and now I'll be drawing up my proposed solutions.
I appreciate it!
Jim Etchison
Program Manager
Siemens Business Services
818-970-3824 (cell)
714-674-8546 (office)
-Original Message-
From: ADSM: Dist Stor Manager [m
Hello Everyone!
I have this script that I run once/day, but we are moving servers and
I would like to run this every 15 min. and have a starting point of
Friday, 8/19 at noon. How would I change the start_date and
start_time parameters so that it would look at my specific
Mike
I'm not 100% sure, but I believe that your problem lies with your
vanilla install. You appear to have installed W2K with SP3 to make the
install mirror your live system, but I think the mistake you have made
is to also install IIS. You should not install IIS as this means that it
is running d
I've seen similar results on a particular Win2K machine I was trying to
restore, Win2KPro SP4, no Exchange involved, just 1 drive. TSM 5.2.3.0
client.
Don't remember which dlls I was having a problem with - I think they
were Office related.
Fortunately I was just testing on that machine, and didn't
Instead of virtual volumes, I suggest using library sharing.
(Your node-server will have to have enough disk to have its own DB anyway.)
Virtual volumes have to reclaim by sending data over the network, twice.
Sharing the library is much faster, simpler & easier to manage than virtual
volumes.
I've done part of this. One instance controls the drives
and, more important, the scratch pool. Since there are no
clients, there's no disk storage and the DB and Log fit in
the default space that comes with the installation so the
reboot time is quite quick whenever maintenance is needed.
A
Don't forget to use enough disk space on the master, becaurse you have to
share the 5 drives with all tsm-servers.
On the tsm master, the tsm server is 1 client, so you can't use collocation
per node, but only per tsm server.
All the data goes twice over a network; from clientnode to tsm server to
Maybe a little more info... How many clients, how much nightly backup data,
what's the mix of Windows / Unix clients retention information, DB backups,
e-mail servers etc.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Bernd
Wiedmann
Sent: Mond
hi everyone,
we are planning to do some enterprise configuration.
Now, what I have in mind is something like this:
1 TSM-Master-Server, which acts as configuration manager,
central event-logger, and administration-server. 5 drives
in a storagetek library.
maybe hot standby.
n instances o
12 matches
Mail list logo
