Rainer,
I found out, the hard way, that only the copies defined in VERE are
retrievable. The thirty extra copies that showed up in a SQL search
weren't there in the gui or the cli for the client.
At 01:55 PM 7/5/2006 +0200, you wrote:
Hi,
we have tsmserver 5.3.3.2 / Client 5.3.3.0 - on solaris
The Copy-Group looks like:
Policy Policy Mgmt Copy Versions Versions Retain
Retain
Domain Set
Name Class Group Data Data Extra Only
Name Name Name Exists Deleted Versions
Version
--------- --------- --------- --------- -------- -------- --------
-------
AAA000 ACTIVE DIRECTORY STANDARD No
Limit 5 60 60
AAA000 ACTIVE STANDARD STANDARD 5 5 60
60
AAA000 STANDARD DIRECTORY STANDARD No
Limit 5 60 60
AAA000 STANDARD STANDARD STANDARD 5 5 60
60
I have tested the 'verexist' option and can see that
(without running expiration on the server)
I can do for example 6 incremental backups on the same always changing file.
Now the query on the inactive Files only shows up 5 Versions of that file
even though there are really 6 Versions stored at the server.
I am not sure but i think in former tsm-Versions i could
query/restore all the 6 Versions from the Client.
Is that behavior now normal ?
Consequently for the retonly-Option ( here 60 days ) :
If not running any expiration on the server: Am I able to restore
an inactive / deleted file - expired more than 60 days ago ?
I always thought all files that haven'T left TSM through
the expiration could be restored at the Client - but it does seem to be so ?
Thanks in advance
for any hints
Rainer
--
------------------------------------------------------------------------
Rainer Wolf eMail: rainer.wolf AT uni-ulm DOT de
kiz - Abt. Infrastruktur Tel/Fax: ++49 731 50-22482/22471
Universitaet Ulm wwweb: http://kiz.uni-ulm.de
Fred Johanson
ITSM Administrator
University of Chicago
773-702-8464
|