Sven,
"Run as administrator" did it. Thanks. I knew I was missing something
2008 specific.
Ullrich,
Sorry, I should have put my commandlines in the original post.
I already use -k and -u flags.
Also, as shown in the OP, I was already in the instance directory.
Habit, and easier than messing wit
Windows 2008R2 x64 Datacenter
TSMS 6.3.0.0 for Windows (12:47:17 on Oct 10 2011)
My current server hangs on start, and I can't figure out why.
*wheeze* back in the day, you could run dsmserv.exe from a command prompt
on Windows, and get stdout.
So, I log in as the instance user, run cmd.exe, go
The size of storage is not enough information to size a system.
The number of sessions determines system size.
If you have four clients, 1 gig per night, you could run 8GB RAM, Core2
2GHz and be okay.
Realistically, 32GB per instance is good. db2sysc will use about 20GB per
instance if it's avai
I ran into an odd issue, and it took me a while to figure out the
cause. I'm posting this because I found very few hits about
lvmread.c, and none matched. Most gave info about memory consumption,
which is no factor here.
If you have to replace the OS on your TSM server, and you're not using
AD,
The issue is that with 75M files, it's paramount to keep the metadata
in something faster than spinning disk.
Windows 2003 32-bit uses 36-bit memory addressing. You can use 32G of
RAM. That might help, but what you WANT in cache never seems to STAY
in cache. Bulk data pushes your MFT out of cac
I find that periodically, through system updates, I have to recompile
adsmpipe anyway.
I've got the original, and several builds for Linux, binary and source at:
http://omnitech.net/images/linkto/adsmpipe/adsmpipe.7z
With friendly Regards,
Josh-Daniel S. Davis
OmniTech Industries
On Thu, Mar 3,
Last time I checked, the formal upgrade instructions say TSM 5.3 and
up are supported for migration, and that migration can be with DB
upgrade or via export.
That would imply to me that a TSM 5.3 server should be able to export
into a TSM 6.2 server; however, I wouldn't expect the inverse.
Usually
Just to be sure, can you verify you have the EE license applied?
With friendly Regards,
Josh-Daniel S. Davis
On Fri, Mar 4, 2011 at 9:32 AM, Laks, Brian wrote:
> I have 9 LTO-4 drives connected to our TSM server, only 5 of them work at any
> time after upgrading to a new fiber card.
>
> We hav
Maybe something simple like verifying TCPWIN on the receiving side is 2x
TCPBUF on th sender.
Set COMPRESS=NO to make sure you're not misreading retransmits.
Check topas during your local backup to itself.
Check nmon's disk stats during the backup to see if you've got a hot LUN.
Check the same from
I vote +1 for low dedupe ratios being due to precompressed data:
* Even MS Office files are actually ZIP files now.
* Windows keeps gigs of installers, which are mostly precompressed cabinets
* Many application data dumps are precompressed
* All practical media files are precompressed
* Many file s
Paul,
Did you find out a definitive answer on this?
Initial searching shows that the crypto cards work on AIX, and are accessible
through a standardized API that banks use. The card itself seems to be a dual
PPC405e on card with a Linux service processor and DMA based communication back
to the OS
I'm at 1h, 40m waiting on callback, but I thought I'd post this for people
searching.
I found the issue because DBB to tape would crash, but BA STG to tape did not.
Neither did BA DB T=F DEVC=FILECLASS.
I found out later that the customer loaded some tapes and checked them in, but
it didn't c
I scanned through, but maybe I missed, bug was it ever determined what's
actually going onto this 12TB LUN? Aside from our longings for kilobytes vs
terabytes, and concerns of 75M files in a filesystem, I didn't see for sure.
An example:
I have a customer with 14TB on one sys. It's something l
You cannot append export tapes.
You can export multiple nodes at once.
OPTION 1: Make a new export tape on a scratch volume
OPTION 2: DELETE VOLHIST and make a new export.
-JD
- Original Message
From: yoda woya
To: ADSM-L@VM.MARIST.EDU
Sent: Thu, April 15, 2010 9:58:26 AM
Subject: Re:
If TBMR is actually Fastback, that's interesting. Fastback is FilesX, a product
and company that IBM purchased April 21, 2008.
FilesX is a block level filesystem incremental backup product for MS Windows.
They can use VSS for 2003 OS and 2005 Exchange/SQL. For older Exchange/SQL it
will initi
Nothing specific to Linux or Redhat.
General things:
If your TSM server is *NIX, you can increase your TCPWINdowsize to 262144 on
the server and use a TCPBUFfersize of 131072.
Older Windows will have problems with anything over 63.
Enabling jumbo frames also helps with CPU load from network trans
You could attach the TSM server to the clustered filesystem and allow it to
perform the backup from its own client. This might get you better bandwidth if
it's done properly.
MEMORYEFFICIENT YES will scan one directory at a time per producer
thread. This keeps from eating up all system memory,
For now, the best you could hope for would be an image mode snapshot backup
going into a deduplicated storage pool.
Alternatively, if your application has a TSM connect agent (such as TDP for
Databases), then you could use that to get the application data incrementally
rather than pulling the
In other environments, I've used MOVE DRM REMOVE=untileefull with
scsi/fibre attached 3584 and it works fine.
In this environment, we have a library manager and 4 library clients.
The 3584 has 20x 3592-E05 drives and 64 virtual I/O slots.
MOVE DRM REMOVE=BULK works fine from the library clients
I've seen a few hits where the only fix was to
DELETE VOLHIST TYPE=REMOTE FORCE=YES
but where it was never identified HOW the volumes got stuck.
I found one way at my customer site.
MOVE DRM notifies the library manager that the volume is TYPE=REMOTE.
The LOCATION is filled with the serv
Things I've run into today which took a little bit of tinkering because
searching didn't come up with anything...
##
During DSMSERV RESTORE DB, while using a manual library, if your DEFINE
PATH for the drive is incorrect, TSM will report an error about the
LIBRARY's path rather than
, TSM Manager, Bocada, and TSM Operational Reporting all can generate
reports for you. Operational Reporting would probably require that you
generate your own queries in order to get useful reports. I'm not sure if
Admin Center has any useful or configurable queries yet.
-Josh Davis
On
about compressing
files.
-Josh
On Mon, 9 Apr 2007, Josh Davis wrote:
Date: Mon, 9 Apr 2007 16:31:38 -0500
From: Josh Davis <[EMAIL PROTECTED]>
Reply-To: "ADSM: Dist Stor Manager"
To: ADSM-L@VM.MARIST.EDU
Subject: HSM for Windows: FileAttributesFilter
Has anyone tried setting the Fi
Experience, no.
Support, maybe. TSM supports 3592 drive encryption. It's important to
make sure you have some way, external to TSM, to store the keys so you can
get at the tapes in a recovery scenario.
AES encryption from the API should work fine, though I'm not sure you have
a way of initially
' registry entries. Thwhen
I went to remove, both showed up, so I was able to delete the bad one,
then reimport the good one, then delete the good one.
There are some legacy registry entries that can't be removed with regedit
and these seem to be the ones in the way.
-Josh Davis
On Fri, 1
se to not migrate since there are known issues.
-Josh Davis
Notes about recall:
Right click, properties
If it's on a directory, it's ok.
If it's on a migrated file, it forces a recall
Notes about DSMFILEINFO:
dsmfileinfo doesn't seem to accept wildcards
dsmfileinfo strips the backslash off of the end of quoted portions of
the filename
S
One correction - recall on properties happens for executable file types.
Still need info on backup before migrate seeming to require HSM to use the
same node name as the baclient.
I'm at HSM 5.4.0.3 and TSMC 5.4.0.2
On Mon, 9 Apr 2007, Josh Davis wrote:
Date: Mon, 9 Apr 2007 15:56:43
Chip,
I have seen many options here, but the first, most simple thing to do is
to make sure that TSM actually knows anything at all about your missing
tapes.
First, find out how many tapes you are supposed to have, total, based on
what has been purchased, minus what has been destroyed.
Second, f
Kelly,
I didn't see a reply for you on this.
I'm sure there is an HSM API, and I don't think it's documented outside of
IBM. Evidence of that is in the HSM for Windows which doesn't use the
Space Management API at all.
The type of information you are looking for is very much server-internal.
Th
The API used on the filesystem side really shouldn't have any effect on
the backend implementation.
The reason it's different is because Tivoli/IBM purchased the product from
a separate company.
As such, HSM for Windows is not derived from HSM for AIX.
The Redbook doesn't clarify all of the in
UNDOCUMENTED OPTIONS FOR EXPIRE INVENTORY:
There are two undocumented/unsupported options for EXPIRE INV;
BEGINNODEID and ENDNODEID.
These accept the decimal node number of a node and can be used to
expire a specific node's filespaces, or a specific range.
WHY WOULD YOU EVER WANT TO USE THESE?
Just in case no one noticed, TSM v4.1 goes end of service at the end of
June. If you find that you don't have time to get upgraded by then,
you may want to sign up for extended support:
https://www.tivoli.com/secure/Tivoli_Electronic_Support/prodextension.nsf/SupExt?OpenForm
-Josh
I whipped this up because I run into so many people who want to figure
it out on their own, but really are just lost in the slew of new
concepts. Here is a basic list of things to do when setting up your tsm
server the first time. Suggestions and corrections are welcome.
-Josh
---
---
TSM Policy Settings
---
POLICY DOMAIN - This is a container for policy and scheduling info
*BACKRETention* is a fallback value for any files which
have been backed up under the specified policy domain,
but for
35 matches
Mail list logo
