On Windows, the real details of the client configuration is comprised of:
1) The information in dsm.opt
2) The information stored in the services config and returned by 'dsmcutil
list' and 'dsmcutil query /name:"service name"'.
3) Other registry stuff.
4) Unknown magic windows security stuff.
5)
A link farm? Maybe www.butterflysoftware.net?
[RC]
st...@stevenharris.info
Sent by: ADSM-L@VM.MARIST.EDU
11/16/2011 11:57 PM
Please respond to
ADSM-L@VM.MARIST.EDU
To
ADSM-L@VM.MARIST.EDU
cc
Subject
Re: [ADSM-L] Migrating from AIX to Linux (again)
You have to move off TSM 5 sooner or
Occasionally on a friday we'd get a request to skip some backups over the
weekend. If you set the start date for the schedule to Monday's date, you
accomplish no backups running over the weekend, and you don't have to
remember to do anything on Monday to get the schedule working again.
If you w
With many of the bundled installers, you can use something like 7-Zip to
list the contents of the bundle.
If 7-Zip lists some fo the contents, but returns an error, you can
generally trust that something is wrong with the downloaded file.
Thanks,
[RC]
george.huebsch...@gmail.com
Sent by:
I find that "incrbydate" is often a win in making the first pass across a
filesystem with a large count of files to be backed up.
Doing a "dirsonly" pass is sometimes a win as well.
Thanks,
[RC]
jorgea...@hotmail.com
Sent by: ADSM-L@VM.MARIST.EDU
02/02/2012 06:37 AM
Please respond to
ADSM-
There was code around for a while, that compiled on Solaris, and could
understand NetApp's (essentialy) ufsdump format. With this you could read
an NDMP backup.
Skip foward a few years: Avamar's NDMP accelerator (a Linux box running
custom code) can take in an NDMP stream from a Celerra and ou
Has anyone seen any documentation from Tivoli, stating that a file
integrity check (or CRC check) is performed during the reclamation
process?
(In an LTO-4 pool in this case, on TSM 5.5 on AIX.)
Thanks,
[RC]
If you are not the intended addressee, please inform us immediately that you
have r
If you haven't already done so, I advise you setup a script to mount the
share and run the backup.
If this script is 100% successful, then you can look at whether the
service is gaining access to the share with the permissions you expect.
I've seen situations where the static mount doesn't have
The last time I saw one of these warnings, the file mentioned was being
included via VSS in the system state backup, but there was a problem with
the path or file name in the key entry in the registry.
(I don't remember if there was an extra space, or an extra backslash in
there.)
If you use r
There was an embarassingly bad TCP window size scaling bug in RHEL 5.4. It
wasn't acknowledged in any way by RedHat, until late in 5.5, and wasn't
fixed until 5.6.
I faced long and continued skepticism from the network people, and the
Linux admins, that such a bug could exist in a RHEL release,
10 matches
Mail list logo