be safe?
As for question 2 i was trying to think out of the box for an easy way to
replicate the Db across sites... You are probably right though the restore
would be a nightmare...
thanks
On Thu, Sep 1, 2011 at 2:38 PM, Xav Paice wrote:
> - "Andrew Meadows" wrote:
> >
All,
We recently started installing fresh tsm 6.2.1 instances in house. I was
wondering if someone could help me with the following questions/issues.
Question 1)
We have a 500 GB Database allocated. I have that split up into 4 filesystems
with 127 GB each. Currently Only the first filesystem is
All,
Correct me if I am wrong but I think you need to be root to apply updates.
On Aug 19, 2011 1:18 PM, "Yanick Quirion"
wrote:
> Dear all,
>
> Today I'm trying to upgrade our TSM 6.1 to 6.2 on a Redhat Linux 5 server.
>
> I logon using my username, which doesn't have root access.
>
> When I start the
dedup).
>
> Changing from file to vtl device type will make you lost client side dedup
> capabilities.
> --Message d'origine--
> De: Andrew Meadows
> Expéditeur : ADSM: Dist Stor Manager
> À: ADSM-L@VM.MARIST.EDU
> Répondre à: ADSM: Dist Stor Manager
> Objet:
>
> I have a question about client side dedup I was hoping I could get some
>> help with.
>>
>>
>>
>>
>>
>> Environment:
>>
>>
>>
>> Server TSM 6.1.3
>>
>> Client TSM 6.2.3
>>
>>
>> We are using client side dedup to decrease the amount of data being sent
>> over the network. The problem is we rec
Super magnet or Sledge hammer Thats about the only way. You could
write junk data to them but it takes at least 8 passes to really clean
them. If you have encryption on then you have nothing to worry about.
Herrmann, Boris wrote:
Hi all,
I've another question. We've got two new 3584 Libr
We saw a similar issue on LTO1's even with the latest firmware. We have
since upgraded to LTO3 drives and have not seen the issue since. Even
when reading the "trouble" LTO1's.
On Mon, 2007-04-09 at 13:18 -0400, Kauffman, Tom wrote:
> Is there any particular firmware I should be running in my IBM
You wouldnt be able to set up a copypool for the offsite copy it would
have to be another onsite pool. You could always try using the devcl
type of file and going that route.
I would also look at doing the dbbackups as devcl=file. That is what we
are looking at doing to reduce the waste of gigs of