Hi all, I wonder if you can help.
I need to schedule a Mac client to do a daily incrbydate backup.
On the client I have created a file called daily-incrbydate.sh with the single
line dsmc incremental -incrbydate in.
If I run this directly it works fine, but when I try to create a schedule on
On 10/6/2010 8:09 PM, Richard Sims wrote:
Don't use the GUI for major restorals - performance suffers.
Use -Virtualnodename for CLI-based cross-nodename operations, as described in
the client manual.
Richard Sims
Thanks Richard! I found the option in the Unix/Linux manual I am
assuming
On 10/6/2010 8:35 PM, David Bronder wrote:
Timothy Hughes wrote:
one of the sun servers we backup was rebuilt (the os was upgraded to
solaris 10) and the client was re-installed with a new name bolton01 to
boton0s10
F.y.I - the reason for the new name is because will eventually get rid
of
Did you follow the quoting specifications documented for the DEFine SCHedule
command, to deal with the blank characters in the string?
On Oct 7, 2010, at 8:10 AM, Timothy Hughes wrote:
On 10/6/2010 8:09 PM, Richard Sims wrote:
Don't use the GUI for major restorals - performance suffers.
Use -Virtualnodename for CLI-based cross-nodename operations, as described
in the client manual.
Richard Sims
Thanks Richard! I
Greetings Matt et al:
I thought I had resolved this 18 character limitation in TSM version 5.5.5 by
defining the 'from' clause 'Domains' as D, 'Nodes' as N, and 'Occupancy' as O
(see Revised SQL below) but the SQL statement chokes saying ANR2906E Unexpected
SQL literal token - 'D'. (or
Hi Richard
I was just using double quotes, so now use single and double.
The schedule looks as follows and still fails with ANR2579E Schedule
MACSERVERS in domain STANDARD for node CHI-XS02 failed
(return code 127).
Policy Domain Name: STANDARD
Schedule Name: MACSERVERS
On 10/7/2010 8:19 AM, Richard Sims wrote:
On Oct 7, 2010, at 8:10 AM, Timothy Hughes wrote:
On 10/6/2010 8:09 PM, Richard Sims wrote:
Don't use the GUI for major restorals - performance suffers.
Use -Virtualnodename for CLI-based cross-nodename operations, as described in
the client manual.
Hi, Farren -
Making progress...
The 127 error is complaining about the path of the command. I don't see that
you need the /Server HD at the front of the path spec: have it start with
/Applications and give that a try, first doing 'ls -l' on the revised path to
verify the file path, and assure
The virtualnodename option is for use in command line only !
If you want to use an alternate nodename, then make many servername definitions
in your dsm.sys whith each nodename
-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] De la part de
Timothy Hughes
-Virtualnodename should be used on the command line, as it is a provisional
execution option, not something that should endure in the options file.
Use this link to find information about the -virtualnodename option:
http://www.ibm.com/developerworks/wikis/display/tivolidoccentral/Tivoli
+Storage+Manager
(I recommend this be bookmarked for future reference.)
You can select the TSM version you use, then enter virtualnodename in the
search
Wonderful, that seems to be working :-) Thank you.
One final question though. Can I run this command such that I still see the
output as I would in the normal dsmsched.log?
Regards
Farren
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
How have others handled litigation issues where one is told to capture all
folders for specific servers.
You can copy them all to a read only system.
You can take a backup of them with a different node name.
You can export everything which would include active and inactive.
You cant just pull
Farren,
Try to add /some_path/log_file_name at the end of your command.
Also, make sure that there is no quiet commutator in your dsm.opt file, or
replace it with verbose.
Cheers.
Arnaud
**
Corporate IT Systems
Hello Danny,
Try something like this:
select DISTINCT occ.node_name,SUM(occ.num_files)/2,
SUM(occ.physical_mb)/2, occ.filespace_name from domains dom, nodes nod,
occupancy occ where dom.domain_name=nod.domain_name and
nod.node_name=occ.node_name and dom.domain_name='DM_PRD' GROUP BY
Wonderful, works a treat.
Thanks to all for the help.
Regards
Farren
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of PAC
Brion Arnaud
Sent: 07 October 2010 14:49
To: ADSM-L@vm.marist.edu
Subject: Re: [ADSM-L] How to run a command for a Mac
It really depends on what's been requested. If you're talking about
capturing today's copy as it is on the client now, then backing them up to
different node names (in a different policy domain, even!) will probably be
easiest for future reference. If you're talking about including historical
If the need is for all current active date you could look at the
generate backupset command.
It is stored as a single object in server storage and only needs a BA
client to restore.
~Rick
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
TSM
Have you considered creating a normal Incremental schedule and using
-opt='-incrbydate' flag?
This seems to be far less error prone?
On 7 okt 2010, at 13:56, Minns, Farren - Chichester wrote:
Hi all, I wonder if you can help.
I need to schedule a Mac client to do a daily incrbydate
I think Q LOG F=D just reports active space usage. My solution was
to monitor the usage on the directory containing the archive log files
through cron. Once the free space on the filesystem drops below a
certain threshold I'll kick off a DB backup using dsmadmc.
On 10/01/10 10:45, Vandeventer,
On 10/7/2010 8:52 AM, Richard Sims wrote:
-Virtualnodename should be used on the command line, as it is a provisional
execution option, not something that should endure in the options file.
Richard Thanks again for your assistance! The restore completed
successfully.
The manual confused me
Andy Thanks for your reply also, I got the restore to work by doing
the following
I changed the name in the dsm.opt file back to the OLD name ( bolton01)
before it was rebuilt.
Then did a dsmc so it would except it as that name and then I did the
restore. Although I realize i have to get use
Thanks Yann and David for your replies.
I have to work on this virtualnodename option to get it to work. I
believe I used the alternate nodename method in the dsm.sys file to get
it to restore.
regards
On 10/7/2010 8:51 AM, Meunier, Yann wrote:
The virtualnodename option is for use in
Have you looked at move data? You can move data from a volume to a pool. We
frequently use this to move data when we change storage systems.
Andy Huebner
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Paul_Dudley
Sent: Wednesday, October
Timothy,
The URL works. It apparently got reformatted so that the URL was broken up
onto two lines, and I suspect when you clicked on it, it just picked up the
first line. You need the rest of it as well.
Best regards,
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Product
On Oct 7, 2010, at 2:01 PM, Timothy Hughes wrote:
Richard Thanks again for your assistance! The restore completed
successfully.
The manual confused me with the information below. It say's place the
option in the dsm.opt file
Glad the restoral worked, but using the Nodename option to do it
On 10/7/2010 2:25 PM, Richard Sims wrote:
On Oct 7, 2010, at 2:01 PM, Timothy Hughes wrote:
Richard Thanks again for your assistance! The restore completed
successfully.
The manual confused me with the information below. It say's place the
option in the dsm.opt file
Glad the restoral
Andy Thanks,
Yes it did get broken up (left off the second line part of the url)
+Storage+Manager
I got it now
Best regards
Tim
On 10/7/2010 2:22 PM, Andrew Raibeck wrote:
Timothy,
The URL works. It apparently got reformatted so that the URL was broken up
onto two lines, and I suspect when
On Oct 7, 2010, at 2:45 PM, Timothy Hughes wrote:
Just as a precaution anything else I could do to to make sure the password
wasn't changed?
I usually just physically inspect the TSM.PWD file, seeing if its mtime has
changed very recently and, if so, check the internals to assure the ASCII
On 10/7/2010 2:55 PM, Richard Sims wrote:
On Oct 7, 2010, at 2:45 PM, Timothy Hughes wrote:
Just as a precaution anything else I could do to to make sure the password
wasn't changed?
I usually just physically inspect the TSM.PWD file, seeing if its mtime has
changed very recently and, if
On Oct 7, 2010, at 3:18 PM, Timothy Hughes wrote:
Richard, I checked using dsmc query session and it shows the correct
reported nodename. I also tried to inspect the TSM.PWD but could not
find it.
I checked the /etc/security/adsm directory and did not see it.
Your platform is Solaris, I
On 10/7/2010 3:25 PM, Richard Sims wrote:
On Oct 7, 2010, at 3:18 PM, Timothy Hughes wrote:
Richard, I checked using dsmc query session and it shows the correct
reported nodename. I also tried to inspect the TSM.PWD but could not
find it.
I checked the /etc/security/adsm directory and did
Matt:
Thanks. Your suggestion worked. The only difference I can see is using dom
instead of D, nod instead of N, and occ instead of O. Brilliant. Must be
something about single letters it didn't like. The winning SQL is as follows:
select DISTINCT occ.node_nameNode Name,
We were once told to hold ALL data of ALL our TSM servers. We put _all_ copy
pool tapes and DBbackups (2 for each server) in the archive, together with
the printed planfiles. Next we had to order that amount of scratch of
course... We made a very happy media supplier that year I dare not to
Hi there guys,
After much searching and figuring out how to do select statements on TSM 6.2
This is what I have come up with for backups.
You can manipulate it to suit you.
SELECT substr(char(start_time),1,19) AS
START_TIME,timestampdiff(4,char(timestamp(end_time) - (start_time))) AS
Hi there guys,
After much searching and figuring out how to do select statements on TSM 6.2
This is what I have come up with for backups.
You can manipulate it to suit you.
SELECT substr(char(start_time),1,19) AS
START_TIME,timestampdiff(4,char(timestamp(end_time) - (start_time))) AS
Probably a few months later, any how
Have you tried increasing the resources on your expire inventory command?
Secondly I'd advise against the upgrade of TSM 6.1.3 to 6.1.4. Too many bugs.
I would advise going straight to TSM6.2.1
Pretty stable so far. And the upgrade process is not that bad as
If you're going to load the 5.2 IDL (WebGUI), do so before upgrading to 5.5.5.
Once you've upgraded to 5.5.5, the 5.2 IDL load fails.
[RC]
On Oct 05, 2010, at 08:25 AM, Matthew G. Leis matthew.l...@usbank.com wrote:
I opened a case with IBM, here are the results:
We are encountering the
39 matches
Mail list logo
