Hi,
Maybe if you restore the vm with a new name...
Before check these values for your backup
select * from summary_extended where sub_entity=''
De :"McWilliams, Eric"
A : ADSM-L@VM.MARIST.EDU,
Date : 2015-03-23 16:39
Objet : [ADSM-L] Restore error message
Envoyé par :"ADSM: Dis
I sympathize, Kjell...
Having been into Unix (among other OSes) since 1975, I was cautiously
optimistic when Linux developed critical mass, hoping that it would
help normalize the Unix world. Unfortunately, Linux only added more
stories to the Tower of Babel, further fracturing the situation with
m
Thank you for the information :-)
Hm, I have trouble understanding *why* it has to be like this, but...
What does a person then do when this server crashes, and sees a golden
opportunity to install a new with a more uptodate operating system?
Files cannot be restored?
/kjell
Richard Sims wrote:
Mos
Most likely. That's the same kind of situation the previous customer
experienced, with different flavors of Linux. You're probably best off
restoring to a work area on the system which originated the backup, and
then transfer that data to the destination system.
Richard Sims
"Linux is only free
fromserver:
Red Hat Linux release 7.3 (Valhalla)
LABEL=/home /home ext3defaults1 2
toserver:
Red Hat Enterprise Linux ES release 3 (Taroon Update 4)
/dev/md8/home ext3defaults1 2
Does this mean "all bets are off
When posting, please include vital details: platform type(s), software
levels.
We've seen this before where the From and To platform types and or file
system types were not the same. All bets are off when you attempt
something like that.
Note that -FROMNode can be problematic if this was not in con
I have good news, my problem is fixed. After having the issues with ADSM/TSM
restores, I tried to mitigate my issues by ftp'ing the data to another machine. After
the ftp, the checksums on the files did not match. I tried rcp and again, the
checksums did not match.
So, armed with that inform
Richard,
I searched, I found one hit:
http://www-1.ibm.com/support/docview.wss?uid=swg1IC36033
But, this is for TDP for Informix.
What did you find?
-Tom
>>> [EMAIL PROTECTED] 01/15/04 05:42PM >>>
>The 103068123th code was found to be out of sequence.
Tom - That's a defect. Search
...
>The 103068123th code was found to be out of sequence.
...
Tom - That's a defect. Search the IBM database for
"code was found to be out of sequence" to see the APAR.
As you discerned, it involves compression.
Richard Sims, BU
Hi,
Did you maybe change te compression settings on this client? If so, change
them back to be able to restore these files...
> Help on a restore.
>
> I have a unix admin who sent me this message:
>
> "That's right, I'm not yet sure if I really have a problem, but on 95% of
> the files I'm rest
Check your client version, you might be attempting the restore from
a version that is down level from the version that was used to
backup the file.
-Original Message-
From: Gill, Geoffrey L. [SMTP:[EMAIL PROTECTED]]
Sent: Sunday, December 30, 2001 6:26 PM
To: [EMAIL PROTECTED]
Su
Long ago in a 3.x version there was a (client) bug that went something
like...
there were 4 bytes of control info, the last byte indicated if a file was
compresses, routines always assumed the 4 bytes would be together within an
inbound record... when the randomness of data actually split the 4 b
Sorry, but the messages manual says it did not restore the file.
Looks nasty. Are you restoring a failed server? Are you sure the client
level is high enough or the same that was used to backup?
-Original Message-
From: Gill, Geoffrey L. [mailto:[EMAIL PROTECTED]]
Sent: Sunday, December
t;
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Subject: Re: restore error
Shekkar,
That looks like the filesystems in question are already mounted, and you're
trying to restore the mount points. You'll either need to unmount t
:48:06 PM
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Subject: Re: restore error
Shekkar,
That looks like the filesystems in question are already mounted, a
Shekkar,
That looks like the filesystems in question are already mounted, and you're
trying to restore the mount points. You'll either need to unmount the
filesystems in question before the restore (then remount them before you
restore data to them) or just ignore the error. I'd just ignore it
>ANS9505E : cannot initialize DM services. Reason: No such file or directory
Don - This is a defect, described in APAR IC23349
Richard Sims, BU
17 matches
Mail list logo
