I would suggest not backing up PST files, if the environment is running
Exchange. Exchange is the proper store for email in that case, as PST files are
much more fragile than the Exchange store.
If the environment is so small that they are not using Exchange, then IMHO TSM
is probably not a
http://gnuwin32.sf.net - you'll find good tools there, including wc and other
core unix utils.
To find the number of files, a better incantation for your dir command is
dir /s /b | wc -l
This will give a better line/file count. You could also pipe this to an output
file, and put
Any way to integrate Wake-on-LAN to boot/shutdown systems?
| -Original Message-
| From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]
| Behalf Of
| Paul Zarnowski
| Sent: Wednesday, August 16, 2006 19:02
| To: ADSM-L@VM.MARIST.EDU
| Subject: [ADSM-L] Power saving and TSM backups
|
|
|
| -Original Message-
| From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]
| Behalf Of
| Richard Mochnaczewski
| Sent: Friday, August 18, 2006 08:07
| To: ADSM-L@VM.MARIST.EDU
| Subject: [ADSM-L] Batch script in Windows to create filelist
|
|
| Hi,
|
| I need to create a filelist of
This will mostly be a function of the [avg latency/hop in WAN] and [# of
hops in WAN] and [max throughput of slowest link in WAN] and [efforts made
to tune packet size to avoid fragmentation - that is, adjusting packet MTU
size to match WAN limitations]. For the last factor, if you're using
processed 124562
items for a total of 22,930,460,672 bytes with a completion state of FAILURE
at 13:04:18.
--End Log Snippet--
Thanks,
Kurt Buff
Lead Network Administrator
Zetron, Inc.
425.820.6363 x463
[EMAIL PROTECTED]
PO Box 97004
Redmond, WA 98073
This won't help you now, but it may help someone else before crisis hits
1) As part of the documentation of the server, use either the natvie 'net
share' command, or rmtshare.exe from the Windows Resource Kit to document
your shares. Create a batch file that creates the shares and copy it off
if they start to migrate to tape and/or 3) get notification if
space in the diskpools is such that files from the file server are likely to
migrate to tape?
The version for TSM shown at the CLI interface is Version 5, Release 1,
Level 5.0.
Thanks,
Kurt Buff
Sr. Network Administrator
Zetron, Inc
Wanda Prather said...
Well, the straightforward TSM way to keep files in a diskpool, is to
remove the NEXTSTGPOOL value from the definition of the
storage pool (so
that the files have no place to migrate to), or set the
HIGHMIG stgpool
pool property to 100%, so that migration will never
I suggest psloglist.exe - it's a free MSFT utility, from the
Sysinternals guys. The whole suite of tools is nearly mandatory for
inclusion in a Windows administration toolkit.
http://www.microsoft.com/sysinternals
Kurt
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL
All,
We're contemplating purchasing this product, which seems to be an HSM,
along with some data deduplication.
Link here: http://www.sunbeltsoftware.com/Business/Sunbelt-File-Archiver/
Does anyone on this list have experience with it, especially how it
integrates (or doesn't!) with TSM?
I'm
All,
We have a TSM server that's running out of steam, and nearing the end
of its expected reliable life. We have Version 5, Release 3, Level 4.6
installed, with various levels of clients installed on our servers.
The server has 1gb RAM, roughly 2tb of disk storage, but it's old/slow
PATA, and
, or at a
clean installation of TSM Server (at 5.5.3 for example) and migrating clients
into the new instance?
Cheers,
/David Mc
London, UK
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Kurt
Buff
Sent: 12 October 2009 18:54
Of Kurt
Buff
Sent: Monday, October 12, 2009 1:02 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Migration for Windows-based installation
I'd prefer to be able to migrate server data as much as possible,
including the diskpool, but if it it would be an incredibly difficult
maneuver (or take
feasible to 'introduce' to your new hardware?
/DMc
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Kurt
Buff
Sent: 12 October 2009 21:09
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Migration for Windows-based installation
So, what happens
on how the data was stored
(primary/copypool/backupset/db backup/other). Once the references are gone,
you should delete the storage pools and device classes that are obsolete.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Kurt Buff
Sent
.
Then you will have to redefine your library and drives.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Kurt
Buff
Sent: Monday, October 12, 2009 3:37 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Migration for Windows-based installation
All,
Thanks for your help on migration strategies. I think it's doable by
us (me, really) with only a few things to be ironed out.
However, I've also been asked to look at moving to a different
solution entirely.
Has anyone here been asked to do this? The new solution is yet to be
determined,
18 matches
Mail list logo
