dsmserv format .... activelogsize=2048
On 3 dec 2010, at 06:21, James R Owen wrote:
> Are you running a simple TSMv6 Library Manager (LM) service?
>
> I am trying to configure a minimal TSMv6.2 LM service and wondering,
> what are minimal workable TSMv6.2 DB, Log, and Archlog allocations?
>
> We're running an active TSMv5.5 LM service under AIX6.1 for some years now
> using <1GB each for DB and Log space! [See further below, if interested]
>
> I thought these allocations were reasonably generous for TSMv6.2 migration:
> DB01 = 2GB
> DB02 = 2GB
> Log = 4GB [Active Log]
> Archlog = 8GB [Archive Log]
> but apparently Active Log space is insufficient; DSMSERV LOADFORMAT fails w/
>
> ANR0370E rdbicbck.c(772) During the format operation, the server cannot create
> files in one or more directories that you specified for ACTIVELOGDIR. Ensure
> that the file system where the directory is located has sufficient space.
>
> TSMv6.2: Planning to install server: Capacity planning: Active log space:
> http://publib.boulder.ibm.com/infocenter/tsminfo/v6r2/topic/com.ibm.itsm.srv.install.doc/c_srv_inst_active_log_space.html
> says:
> ...
> The default size of the active log is 16,384 MB (16 GB). Under normal server
> operations, you are likely to need an active log that is larger than the
> default. The maximum size of the active log is 131,072 MB (128 GB). The
> minimum size of the active log
> is 2048 MB (2 GB).
> ...
>
> But, that 2GB minimum size seems to be unworkable w/ TSMv6.2:
>
> TSMv6.2: ANR Messages: Help for ANR0370E:
> http://publib.boulder.ibm.com/infocenter/tsminfo/v6r2/topic/com.ibm.itsm.msgs.server.doc/msgs_server336.html
> says:
> ...
> * Check that space is available to the directories that you specified for
> ACTIVELOGDIR,ARCHIVELOGDIR, and ARCHFAILOVERLOGDIR. Ensure that the amount of
> space meets requirements. For example, the directory for ACTIVELOGDIR must
> have at least 8 GB space available.
> ...
>
> Increasing Active Log allocation >8GB, the error goes away,
> so the ANR0370E message advice is apparently correct!
>
> So...
>
> How would you configure DB, Log, ArchLog space for this TSMv6.2 LM service?
>
>
> Here's what our TSMv5.5.5 LM Service looks like:
>
> [Our LM TSM shares 3 tape libraries w/ 16*LTO2 + 60*LTO3 + 16*LTO5 drives
> w/ seven active Library Client TSM Backup/Recovery services,
> and also runs a gaggle of weeknightly differential NDMP backups and
> weekend DR+full NDMP backups for Oracle DBs and VMware guests on NetApps.]
>
> tsm: MGR>q db
> Session established with server MGR: AIX-RS/6000
> Server Version 5, Release 5, Level 5.0
> Server date/time: 12/02/2010 21:42:31 Last access: 12/02/2010 14:52:13
>
>
> 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
> --------- -------- --------- --------- ------- --------- --------- ----- -----
> 1,020 1,020 0 288 4,096 261,120 186,853 71.6 71.6
>
> tsm: MGR>q log
>
> 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
> --------- -------- --------- --------- ------- --------- --------- ----- -----
> 1,016 764 252 544 4,096 195,072 55,255 28.3 69.7
>
> tsm: MGR>q stg
>
> Storage Device Estimated Pct Pct High Low Next Stora-
> Pool Name Class Name Capacity Util Migr Mig Mig ge Pool
> Pct Pct
> ----------- ---------- ---------- ----- ----- ---- --- -----------
> ARCHIVEPOOL DISK 0.0 M 0.0 0.0 90 70
> BACKUPL3N LTO3N 64,810 G 34.8
> BACKUPL3NDR LTO3NDR 31,804 G 9.3
> BACKUPL3NDX LTO3NDR 155,767 G 73.3
> BACKUPPOOL DISK 0.0 M 0.0 0.0 90 70
> SPACEMGPOOL DISK 0.0 M 0.0 0.0 90 70
>
> tsm: MGR>
>
> Thanks for any advice you care to share.
> --
> Jim.Owen AT Yale DOT Edu (w#203.432.6693, c#203.494.9201, h#203.387.3030)
|
