[ADSM-L] Problem with management class
2008-04-24 16:17:28
Hi everyone.
I have a number of Windows servers backing up directly to a disk
storage pool (WDISKPOOL).
I have a single 3580 LTO4 standalone drive to which I migrate the disk
pool weekly. So:
Windows Servers ---(daily incremental)---> WDISKPOOL ---(weekly
migration)---> WLTOPOOL
A few days back I added a new large server to this Windows domain, and
now my disk storage pool almost fills up daily.
So I decided to have this one server go directly to the tape storage
pool WLTOPOOL while the rest keep going to WDISKPOOL.
I created a new management class (WINTAPE_CLS) and used the include
statements in the dsm.opt of my large server to make it bind to this
new class (I left the dsm.opt on the other servers untouched).
INCLUDE F:\Data_Repository\...\* WINTAPE_CLS
Here is a display of the copy groups (WINDOWS_CLS is the default
management class):
tsm: SRVTSM>q copy windows_dom windows_pol f=d
Policy Domain Name: WINDOWS_DOM
Policy Set Name: WINDOWS_POL
Mgmt Class Name: WINDOWS_CLS
Copy Group Name: STANDARD
Copy Group Type: Backup
Versions Data Exists: 7
Versions Data Deleted: 1
Retain Extra Versions: 30
Retain Only Version: 60
Copy Mode: Modified
Copy Serialization: Shared Static
Copy Frequency: 0
Copy Destination: WDISKPOOL
Table of Contents (TOC) Destination:
Last Update by (administrator): ADMIN
Last Update Date/Time: 01/29/2008 16:53:53
Managing profile:
Changes Pending: No
Policy Domain Name: WINDOWS_DOM
Policy Set Name: WINDOWS_POL
Mgmt Class Name: WINTAPE_CLS
Copy Group Name: STANDARD
Copy Group Type: Backup
Versions Data Exists: 7
Versions Data Deleted: 1
Retain Extra Versions: 30
Retain Only Version: 60
Copy Mode: Modified
Copy Serialization: Shared Static
Copy Frequency: 0
Copy Destination: WLTOPOOL
Table of Contents (TOC) Destination:
Last Update by (administrator): ADMIN
Last Update Date/Time: 04/20/2008 16:17:45
Managing profile:
Changes Pending: No
The problem I am having now, is that now every windows server is
opening and closing the mounted tape multiple times like so:
04/21/2008 02:11:07 ANR0511I Session 2111 opened output volume WIN001L4.
(SESSION: 2111)
04/21/2008 02:11:10 ANR0514I Session 2111 closed volume WIN001L4. (SESSION:
2111)
...
04/21/2008 02:37:17 ANR0514I Session 2133 closed volume WIN001L4. (SESSION:
2133)
04/21/2008 02:37:40 ANR0511I Session 2133 opened output volume WIN001L4.
(SESSION: 2133)
...
04/21/2008 02:20:42 ANR0511I Session 2116 opened output volume WIN001L4.
(SESSION: 2116)
04/21/2008 02:21:04 ANR0514I Session 2116 closed volume WIN001L4. (SESSION:
2116)
like this for all the backup sessions multiple times.
Here is how the management classes are defined for these servers:
tsm: SRVTSM>q mgm windows_dom
Policy Policy Mgmt Default Description
Domain Set Name Class Mgmt
Name Name Class ?
--------- --------- --------- --------- ------------------------
WINDOWS_- ACTIVE WINDOWS_- Yes Management Class for
DOM CLS Windows Servers
WINDOWS_- ACTIVE WINTAPE_- No Management Class for
DOM CLS direct to tape backups
WINDOWS_- WINDOWS_- WINDOWS_- Yes Management Class for
DOM POL CLS Windows Servers
WINDOWS_- WINDOWS_- WINTAPE_- No Management Class for
DOM POL CLS direct to tape backups
Question: Why are all the Windows servers now going to tape if I just
updated this one to use the new (non-default) management class?
TSM server is 5.4.2.0 and the clients are 5.4.0.2
Thanks in advance for your help.
Cesar
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [ADSM-L] Problem with management class,
chicharras <=
|
|
|