Hi Eric,
I don't know any other way to reduce the DB size. But this brought me a
question about your nodes migration. After you delete filespace on
those nodes on new server that are not going to be migrated, is that true
the new V3 server will start to delete/remove those nodes data from the
tape. Then, will the V2 server still be able to see those data?
Regards,
Jsack
tangeric AT hk1.ibm DOT com on 01/05/99 08:21:53 AM
Please respond to ADSM-L AT vm.marist DOT edu
To: ADSM-L AT vm.marist DOT edu
cc:
Subject: Reduce database size
Hi all,
To migrate some nodes to from a v2 server to a new v3 server, database is
backup from v2 server and restore to v3 server, and delete filespace on
those nodes on new server that are not going to be migrated.
Allocated database size in v2 server is 11092MB, and below is "q db" on the
new server after del filespace.
adsm> q db
Available Assigned Maximum Maximum Page Total Used Pct
Max.
Space Capacity Extension Reduction Size Usable Pages Util
Pct
(MB) (MB) (MB) (MB) (bytes) Pages
Util
--------- -------- --------- --------- ------- --------- --------- ----- --
---
---
13,284 11,092 2,192 2,060 4,096 2,839,552 215,244 7.6
13,284 11,092 2,192 2,060 4,096 2,839,552 215,244 7.6
7.6
'Reduce db' can only reduce db size by 2060M, is there any other way to
reduce the db size?
I have tried backup, dsmserv install log & database then restore, but
result is the same.
Regards,
Eric Tang
|