| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 449.1 | Log and restore | COOKIE::HEISLER | Chris Heisler, ABS Engineering | Fri Apr 25 1997 11:32 | 9 |
| Jan,
Can you post an ABS SHOW RESTORE/FULL output for the restore request?
Also, can you post the log from the restore?
Thanks,
Chris
|
| 449.2 | Please check this first | COOKIE::MHUA | | Fri Apr 25 1997 16:35 | 16 |
|
One common mistake you see in restore request is that the restore
selection criteria (on or before - or what time) is not set correctly.
In your case, the file you want to restore is created 23-apr-97 22:11.
If your restore request does not specify correctly to include data
saved from this data/time, restore request will not find entries in
catalog.
For example, if your restore request says "on or before 22-apr-1997
00:00" as selection criteria, it does not find matching data to
restore.
Please make sure that this is not the case.
Masami
|
| 449.3 | requested info | UTRTSC::KNOL | isn't every bug a bit wrong | Mon Apr 28 1997 08:01 | 178 |
| here is the information you've asked for
Atlas2>abs lookup /full
"/usr/users/p11608/piepel"/object_type=unix_files_gtar/s
ince=23-apr-1997/node=jupiter/storage_class=unix_backups
Object of type UNIX_FILES_GTAR found
Object
Node name - JUPITER
Device name -
Object name - /usr/users/p11608/piepel
Object version - 0
Date archived - 26-APR-1997 22:12:04.96
Archive Expiration - 17-MAY-1997 22:00:41.06
Object type - UNIX_FILES_GTAR
Object creation -
Object revision -
Object expiration -
Owner - ATLAS2::
Saveset UID - E2DE62F2-BE80-11D0-A81A-08002B398C07
Save transaction UID - A0410F83-BD7E-11D0-A818-08002B398C07
Storage class UID - 9EFEEBFA-BD73-11D0-A818-08002B398C07
File section # - 1
Transaction status - In Progress
Transaction severity - Operation Successful
Object
Node name - JUPITER
Device name -
Object name - /usr/users/p11608/piepel
Object version - 0
Date archived - 25-APR-1997 22:12:01.38
Archive Expiration - 16-MAY-1997 22:00:42.55
Object type - UNIX_FILES_GTAR
Object creation -
Object revision -
Object expiration -
Owner - ATLAS2::
Saveset UID - BA17E1EB-BDB7-11D0-A818-08002B398C07
Save transaction UID - A0410F83-BD7E-11D0-A818-08002B398C07
Storage class UID - 9EFEEBFA-BD73-11D0-A818-08002B398C07
File section # - 1
Transaction status - In Progress
Transaction severity - Operation Successful
Object revision -
Object expiration -
Owner - ATLAS2::
Saveset UID - 16E1850C-BD64-11D0-A818-08002B398C07
Save transaction UID - B92A82BF-BD63-11D0-A818-08002B398C07
Storage class UID - 0D4D5AA1-BC93-11D0-A818-08002B398C07
File section # - 1
Transaction status - In Progress
Transaction severity - Operation Successful
Object
Node name - JUPITER
Device name -
Object name - /usr/users/p11608/piepel
Object version - 0
Date archived - 23-APR-1997 22:11:30.65
Archive Expiration - 14-MAY-1997 22:00:19.15
Object type - UNIX_FILES_GTAR
Object creation -
Object revision -
Object expiration -
Owner - ATLAS2::
Show log entry failed for the following reason:
A Transaction Log entry was not found in the catalog
********************************************************************************
********************************Executing ABS LOGIN.COM
Completed execution of ABS LOGIN.COM
"@abs_system:coordinator.com 55A1DD1C-BFB4-11D0-B577-08002B398C07"
Executing, output follows :
------------------------------------------------------
---------------------------------------------------------------
Starting New Request at 28-APR-1997 10:44:19.58
Name: UNIX_TEST_RESTORE
UID: 55A1DD1C-BFB4-11D0-B577-08002B398C07
COORDINATOR: Looking up /usr/users/p11608/piepel in catalog ABS_CATALOG
COORDINATOR: A Transaction Log entry was not found in the catalog
COORDINATOR: Facility ABS: ABS_TLE_NOT_FOUND, A Transaction Log entry
was not found in the catalog
COORDINATOR: Line = 719, File = RESD$:[SRC]COORDINATOR.C;1
COORDINATOR: Facility ABS: ABS_TLE_NOT_FOUND, A Transaction Log entry
was not found in the catalog
COORDINATOR: Line = 441, File = RESD$:[SRC]COORD_THREAD_MANAGEMENT.C;1
COORDINATOR: Facility ABS: ABS_TLE_NOT_FOUND, A Transaction Log entry
was not found in the catalog
COORDINATOR: Line = 1223, File = RESD$:[SRC]COORD_XN_MANAGEMENT.C;1
COORDINATOR: Facility ABS: ABS_TLE_NOT_FOUND, A Transaction Log entry
was not found in the catalog
COORDINATOR: Line = 1217, File =RESD$:[SRC]COORD_CATALOG_MANAGEMENT.C;1
COORDINATOR: Facility ABS: ABS_TLE_NOT_FOUND, A Transaction Log entry
was not found in the catalog
COORDINATOR: Line = 224, File = RESD$:[SRC]CATAPI_C_SHOW_TLE.C;1
COORDINATOR: Facility ABS: ABS_TLE_NOT_FOUND, A Transaction Log entry
was not found in the catalog
COORDINATOR: Line = 154, File = RESD$:[SRC]CATAPI_S_SHOW_TLE.C;1
COORDINATOR: Facility ABS: ABS_TLE_NOT_FOUND, A Transaction Log entry
was not found in the catalog
COORDINATOR: Line = 1382, File = RESD$:[SRC]ABS_CATALOG_TLE.C;1
COORDINATOR: Facility ABS: ABS_TLE_NOT_FOUND, A Transaction Log entry
was not found in the catalog
COORDINATOR: Line = 3343, File = RESD$:[SRC]ABS_CATALOG_TLE.C;1
COORDINATOR: Final status is A Transaction Log entry was not found in
the catalog
%SYSTEM-F-OPINCOMPL, operation is incomplete
ABS job terminated at 28-APR-1997 10:44:23.25
Accounting information:
Buffered I/O count: 330 Peak working set size: 12144
Direct I/O count: 331 Peak page file size: 67984
Page faults: 1860 Mounted volumes: 0
Charged CPU time: 0 00:00:00.83 Elapsed time: 0 00:00:16.71
|
| 449.4 | More information requested | COOKIE::HEISLER | Chris Heisler, ABS Engineering | Mon Apr 28 1997 11:07 | 15 |
| Jan,
I also would like to see the following information:
ABS SHOW RESTORE/FULL UNIX_TEST_RESTORE
and
ABS SHOW STORAGE/FULL UNIX_BACKUPS
Can you post that information?
Thanks,
Chris
|
| 449.5 | | UTRTSC::KNOL | isn't every bug a bit wrong | Mon Apr 28 1997 12:49 | 70 |
| Atlas2>abs SHOW RESTORE/FULL UNIX_TEST_RESTORE
Restore Request
Name - UNIX_TEST_RESTORE
Version - 3
UID - 55A1DD1C-BFB4-11D0-B577-08002B398C07
Movement Type - SELECTIVE_RESTORE
Data Object Set
Movement Criteria - OVERLAP
Commit Granularity - KEEP_PARTIAL
Include Spec - /usr/users/p11608/piepel
Exclude Spec -
Type Name - UNIX FILES GTAR
Data Movement Flags - SEPARATE_LISTING, BRIEF_LISTING
File System Options - None
Object Date Options - None
Selection Options - None
Restore Options - None
Date Identifier - NONE
Low Limit Date - 17-NOV-1858 00:00:00.00
High Limit Date - 17-NOV-1858 00:00:00.00
Output Spec - None
Owner - ATLAS2::ABS
Access Right - ATLAS2::ABS
Access Granted - READ, WRITE, SET, SHOW, DELETE, CONTROL,
EXECUTE
Class Name - UNIX_BACKUPS
Date Archived - 24-APR-1997 00:00:00.00
Match Criteria - PRECEDING_COPY
Output Spec - None
Execution Envir - UNIX_BACKUPS_ENV
Wait Flag - NO
Prologue Command - None
Epilogue Command - None
Alt Restore Info - None
|
| 449.6 | Output doesn't look right | COOKIE::HEISLER | Chris Heisler, ABS Engineering | Mon Apr 28 1997 14:35 | 13 |
|
The output from the SHOW RESTORE/FULL isn't complete. You are
missing the line that shows the nodename. Did you edit that
output before you posted it?
Please do the command again and re-enter the output.
Also, please post the output from an
ABS SHOW STORAGE/FULL UNIX_BACKUPS
Thanks again,
Chris
|
| 449.7 | jupiter was the nodename | UTURBO::KNOL | isn't every bug a bit wrong | Tue Apr 29 1997 03:08 | 41 |
| some creative click and drop had dropped a line
so the nodename was Jupiter.
the output of ABS SHOW STORAGE/FULL UNIX_BACKUPS
Storage Class
Name - UNIX_BACKUPS
Version - 52
UID - 9EFEEBFA-BD73-11D0-A818-08002B398C07
Node Name - ATLAS2
Archive File System
Primary Archive Location -
Staging Location -
Primary Archive Type - SLS/MDMS
Staging Archive Type - NOT IMPLEMENTED
Staging Retention Period - 17-NOV-1858 00:00:00.00
Owner - ATLAS2::P6632
Access Right - ATLAS2::ABS
Access Granted - READ, WRITE, SET, SHOW, DELETE, CONTROL, EXECUTE
Tape Pool - Hades_10
Volume Set Name - AAK338
Retention Criteria
Number Of Copies - 4
Retention Period - 21 00:00:00.00
Consolidation Criteria
Count - 0
Capacity - 0
Size - 0
Interval- 1 00:00:00.00
Catalog Name - ABS_CATALOG
Retain When Idle Flag - NO
Streams - 1
Media Management Info
Media Location - None
Media Type - TK87K
Device Name - None
|
| 449.8 | We're thinking | COOKIE::HEISLER | Chris Heisler, ABS Engineering | Tue Apr 29 1997 09:33 | 7 |
| Hi,
I am not sure what is causing the problem with the restore.
I'll do some more checking and see if we can give you some
suggestions.
Chris
|
| 449.9 | does any restore work? | COOKIE::LEWIS | | Tue Apr 29 1997 12:57 | 12 |
| After the upgrade to v2.1, can the customer restore any kind of file? Do
vms restores work, or nt restores, or any other unix restore? What if he
tries to restore a file that was saved after the upgrade to v2.1? does that
work?
We don't know of any specific problems with this.
Also, when the customer upgraded, did the upgrade go ok? Did the customer
execute the catalog conversion, and if so, did it work ok?
Thanks, we'll keep looking also.
Jim
|
| 449.10 | restores after upgrade are ok | UTRTSC::KNOL | isn't every bug a bit wrong | Wed Apr 30 1997 03:01 | 7 |
| The customer only needed to restore from a unix backup, don't know
if he tried a vmsbackup. He told me that he was able to restore files
made with backups after the upgrade to abs 2.1
I don't know if he did a conversion, can't ask him today it's the queens
birthday so everybody in Holland has a day off.
I'll keep you posted.
jan
|
| 449.11 | Conversion? | COOKIE::HEISLER | Chris Heisler, ABS Engineering | Wed May 07 1997 12:06 | 5 |
| Jan,
Did you find out whether the customer converted their catalogs?
Chris
|
| 449.12 | solved.....itself | UTRTSC::KNOL | isn't every bug a bit wrong | Thu May 15 1997 10:23 | 12 |
| sorry for the delay ,
Called the customer today, and he told me that his problem was over
because he didn't has any backups made with abs 2.0 left.
As always some problems disappear over time if you wait long enough.
Thanks for the assistance and time you spent trying to solve this
problem
jan
|
| 449.13 | Thanks | COOKIE::HEISLER | Chris Heisler, ABS Engineering | Thu May 15 1997 15:18 | 5 |
| Jan,
Ok, thanks for the update.
Chris
|