As long as you make sure all of your primary stgpools go to the COPY/DRM-pool
there is nothing else special about it.
On 18/04, Mehdi Salehi wrote:
> Thanks David,
> Does it matter from DRM point-of-view if there are many storage pools?
Jim -
That evidence says that the warranted changes have not been made to
the client to correct the initially reported problems, which
continue. A thorough review of that client should be conducted,
starting with 'dsmc query option' and 'dsmc query inclexcl', as the
administration of that client
On Apr 19, 2010, at 6:22 AM, Richard Sims wrote:
Jim -
That evidence says that the warranted changes have not been made to
the client to correct the initially reported problems, which
continue. A thorough review of that client should be conducted,
starting with 'dsmc query option' and 'dsmc qu
Hi Grigori,
Thanks for the info. I don't see anything wrong. I think I have been able
to reproduce your symptom, though, and it would seem that this is a defect.
For a workaround, try using an explicit TCPCLIENTPORT setting, such as
1502, for one of your scheduler services. You will need to make s
Hello everybody,
I tried restoring a windows 2008 R2 server image (c: partition) and
ran into a problem. Here's what I did (according to the field guide
"TSM Recovery Techniques using Win PE Environment"):
- Created Image Backup of c: partition with VSS (ESX vSphere 4.0 VM)
- Did daily incrementa
I would use that same BartPE disk to determine if you can read the newly
restored disk after the restore. If so, I would attempt to fix the boot sector
as you mentioned below by booting a Windows Server 2008 R2 CD and running
through the various options to fix the boot sector.
Good luck.
If yo
04/19/2010 08:38:26
04/19/2010 08:38:26 Schedule Name: TEST_SCHEDULE
04/19/2010 08:38:26 Action:Incremental
04/19/2010 08:38:26 Objects:
04/19/2010 08:38:26 Options:
04/19/2010 08:38:26 Server Window Start: 08:40
I have seen something like this before. I would guess that according to the
log, that something is corrupt in '/public/proval-old' . Perhaps a bad inode,
invalid file name or just plain corrupt file. I would do some 'ls -l' in and
around that directory looking for a bad file.
TSM backups are gr
On Apr 19, 2010, at 11:45 AM, James Choate wrote:
04/19/2010 08:56:26 --- SCHEDULEREC OBJECT BEGIN TEST_SCHEDULE
04/19/2010 08:40:00 04/19/2010 08:56:27 Incremental backup of volume
'/'
04/19/2010 08:56:27 Incremental backup of volume '/boot'
04/19/2010 08:56:27 Incremental backup of volume '/pu
It seems to me that /public/proval-old is a filesystem of some sort since
there was no other virtualmountpoint messages. Maybe it's a loopback
mount or something?
Try putting this in there to exclude it:
exclude.fs /public/proval-old
If that doesn't work, provide the output of a "df"
If it doe
I'm having trouble running a snapdiff backup from a Windows 2008 TSM client.
TSM client 6.1.3.3
Windows 2008 Server Standard SP2 64 bit
I've been able to do a snapdiff backup of the same NAS volume from two other
Windows machines, I believe both running Windows 2003. I've already done the
'set
I am looking for the longest fully qualified file name on the system.
An error=6 might be indicating ENAMETOOLONG (The only errno that equals 6 in
Linux).
Repeated runs (manual) today have resulting in the exact same result.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads..
I just ran an fsck on /public/proval-old, No errors were found on that mount.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Ben
Bullock
Sent: Monday, April 19, 2010 10:25 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Linux Client failing with ANS19
Hello Andy,
Thank you very much for information. I think this is a bug too, but I couldn't
prove this. I can say similar setup was working fine for years before upgrade
to 6.2.0. I think problem was caused by second scheduler, which was using the
same port 1501 as the first one (no automatic swi
14 matches
Mail list logo
