On Apr 13, 2010, at 2:41 AM, M KIRAN KUMAR wrote:
> But when I try to perform incremental on the default management class,
> server is trying to mount from both the storage pools from default and
> non-default management class.
When posting a problem like this, include some information on what ki
It is not a matter of access. Node can access all management classes in domain
by default and it does not matter how many classes you have. Next is only
important:
1) it should be default management class in domain for backups without include
statements (default);
2) all other management class
I configured two management classes in one domain .node can access both
management classes .
Regards,
Kiran.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Grigori Solonovitch
Sent: Tuesday, April 13, 2010 12:58 PM
To: ADSM-L@VM.MARIST.EDU
Subj
This is default option, if node is in domain, where you have default management
class.
So just remove all additional includes (keep only default includes coming after
client installation).
Grigori G. Solonovitch
Senior Technical Architect
Information Technology Ahli United Bank Kuwait
Thanks for the solution.
But I want to backup to the storage pool which is assigned to default
management class.
What's the option.
Regards,
Kiran.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Grigori Solonovitch
Sent: Tuesday, April 13, 20
You can try to add in dsm.opt at the beginning (important!) of include/exclude
list:
INCLUDE "*:\...\*" NOT_DEFAULT_CLASS
INCLUDE.SYSTEMSTATE ALL NOT_DEFAULT_CLASS
This will fix your problem for sure.
Grigori G. Solonovitch
Senior Technical Architect
Information Technology Ahli United Bank Kuw
> I performed selective backup in non default management class. It was
> successful. Two different storage pools for backup for both management
> classes.
> But when I try to perform incremental on the default management class, server
> is trying to mount from both the storage pools from defaul
Fred, can you tell by looking at the dsmsched.log when this crash might be
happening? We've had a couple of PMRs reporting this type of error on
Windows boxes when backing up systemstate data. Please look at APAR IC66607
to see if this might apply here. Fix is scheduled for 6.1.4, but an interim
fi
Hi,
we had the problem backing up unc-shares. It turned out that the virus scan
was not able to scan the directories an thus TSM was not able to back them
up. TSM has no problem with directories with more than 256 characters (I´m
not sure where the limit is). Our tests were at TSM 5.1.6.0 Windows
First the version of "RoboCopy" that is part of the Windows 2003 resource kit
now supports paths longer that 256 characters.
Second, TSM does support the backup and restoration of files in paths longer
that 256 characters.
What errors are you getting?
Kyle
"Rees, Chris (Corp)" <[EMAIL PROTECT
We usually have the user shorten the path. If that isn't possible,
you can create a share point deeper into the directory structure
and back it from there.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Rees, Chris (Corp)
Sent: Thursday, May 19, 20
11 matches
Mail list logo
