Why is this posted?
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Yuvaraja Shivarama
Sent: Monday, December 12, 2011 12:51 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Anna Hazare Coming to Freedom Park on 17th Dec 2011(Sat)-
To Save Lokayuk
Hi All
TSM Server 5.5.2.0 on Solaris
Linux Client 5.5.0.0 - Real Application Cluster v6
I have the following issue. When the backup runs as a scheduled service it only
checks/backs up the /boot filesystem.
I put the following in dsm.sys and that certainly allows me to run manual
backups
-Farren Minns wrote: -
>TSM Server 5.5.2.0 on Solaris
>
>Linux Client 5.5.0.0 - Real Application Cluster v6
>
>I have the following issue. When the backup runs as a scheduled
>service it only checks/backs up the /boot filesystem.
>
>I put the following in dsm.sys and that certainly allows
OK, thanks for the advice.
Regards
Farren
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@vm.marist.edu] On Behalf Of Thomas
Denier
Sent: 12 December 2011 16:49
To: ADSM-L@vm.marist.edu
Subject: Re: [ADSM-L] Problems backing up Linux client - missed filesystem
-F
Have you checked your dsmsched.log on the client for errors? Have you checked
your tsm server actlog for the same time period for informative messages?
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Minns,
Farren - Chichester
Sent: Monday, De
Hi
Yes, and not actually seeing errors.
The backup runs fine, but only check the /boot filesystem.
Regards
Farren
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Ehresman,David E.
Sent: 12 December 2011 17:07
To: ADSM-L@VM.MARIST.EDU
Su
That's fine, but it will fail even though you point the host entry to the DR
box. This is CIFS and the \\hostname\backup has to match the one of the DDR
you're pointing to. By default on the DDR the hostname is the CIFS NBT name
used. You can change the CIFS NBT name to something different (CIFS SE
If your scheduler is not running under CAD, any changes made to dsm.sys and
dsm.opt will not be known to that scheduler process until it is restarted.
You should also review the output of 'dsmc q opt' and 'dsmc q inclexcl' for
containing what you actually want, as "compiled" specifications. An
