Changing domain assignment will affect retention parameters -- not data location. If you want the data moved, using 5.1.1.1 or later (the only level I would consider using on a 5.1 server), use the new MOVE NODEDATA command to get the old data into the new storage pool. Alternative, under 4.x is to await expiration.
Don France Technical Architect -- Tivoli Certified Consultant Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390 San Jose, Ca (408) 257-3037 mailto:[EMAIL PROTECTED] Professional Association of Contract Employees (P.A.C.E. -- www.pacepros.com) -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Argeropoulos, Bonnie Sent: Wednesday, July 24, 2002 1:39 PM To: [EMAIL PROTECTED] Subject: New Policy Domain Hello, Running aix 4.1.1 and 4.1.1 on the NT clients.... I recently created a new domain with separate disk storage space from the existing domain and moved 4 nodes to this domain. Backups seem to be running okay...but there is still occupancy for these nodes in the old domains disk space...this should definitely have migrated by now. Does anyone know why I have disk space in the old space of gen_disk....shouldn't there only be space in the new gen_disk2? Any help would be appreciated....thanks Bonnie Argeropoulos [EMAIL PROTECTED] Node Name Type Filespace Storage Number of Physical Logical Name Pool Name Files Space Space Occupied Occupied (MB) (MB) ---------------- ---- ---------- ---------- --------- --------- --------- HBO Bkup $1$DRA0: GEN_DISK 366 383.84 237.17 HBO Bkup $1$DRA0: GEN_DISK2 933 8,616.59 8,616.59 HBO Bkup $1$DRA0: GEN_OFFSI- 11,956 36,774.52 36,475.88 TE HBO Bkup $1$DRA0: GEN_TAPE 10,657 27,982.64 27,622.38
