Welcome to SCSI
TSM: ทำไมเวลาใช้คำสั่ง Q Volume แล้ว space ที่ใช้ได้ไม่เท่ากับความจุของ Tape จริง PDF Print E-mail
Written by Wira Chinwong   
Thursday, 30 June 2011 21:18

อ้างจาก Technote ของ IBM

"query volume" shows estimated capacity value less than expected value

Technote (FAQ)


Question

For volumes in status full, "query volume" shows the estimated capacity less than what is really stored on the volume

Answer

The QUERY VOLUME command does not always display a expected volume capacity when the
volume has reached end-of volume (EOV). When a volume is in status full, the estimated
capacity always displays the real capacity of the volume, i.e. the total number of bytes being stored on the volume in general. This value of the real capacity may not match the value of the estimated capacity. The value of the real capacity could be smaller than the value of the estimated capacity..

Here is an example from a WORM LTO3 tape. This WORM LTO3 tape volume was brand new.
The LTO3 compressed mode was used for backup data. When this volume was full, the Estimated Capacity showed that the volume capacity was 91.7G in this example. However, when the volume was empty, the Estimated Capacity was 400G. So the real capacity is smaller than the previous estimated capacity.

The output from Tivoli Storage Manager server console for LTO3 WORM tape:


Volume Name Storage Device Estimated Scaled Pct Volume Access
Pool Name Class Name Capacity Capacity Util Status
Applied
----------- --------- ---------- --------- -------- ----- ------- ----------
VOL001L3 WORMPOOL WORMTAPE 91.7 G 100.0 Full Read/Write




To get the full estimated capacity, you can define a storage pool with the option
dataformat=nonblock. For more information about the dataformat parameter see the
Tivoli Storage Manager server Administrator Reference.

This issue is also related to the Tivoli Storage Manager server option TXNGroupmax.

The Tivoli Storage Manager server write a segment each time to the volume.
A segment is usually a aggregate bitfile which contains up to number of "TXNGroupmax"
files. If the size of a segment (aggregate bitfile) is smaller than the block size 256K,
there will be gap in the volume because it wrote 256K each time.
If the size of a segment greater than 256K, it will write multiple times with 256K
each time until the whole segment wrote to the volume, so, most time, the last write
for a segment will have gap because the segment size is not likely to be integral
multiple of 256K. But most time, the size of a segment is much bigger than 256K,
so the percentage of wasted space can be very small.

The gap is introduced when backup or archive from the client.
There is no way to remove the current gap unless the files get expired.

You can increase TXNGroupmax to prevent further gap.
But notice that use a too lager value of TXNGroupmax could cause performance issue.
For more information about the TXNGroupmax server option see the Tivoli Storage Manager
server Administrator Reference.
You can use the following way to calculate how you should change TXNGroupmax to.

Example:
The current TXNGroupmax is A, the capacity of volume is B,
the data can actually wrote to the volume is C.
The new TXNGroupmax can be calculated as follow: A * B / C.
For example, if the current TXNGroupmax is 256, the capacity of LTO3 tape is 400G,
the data can actually wrote to the tape is 91.7G.
You can change the TXNGroupmax to 256 * 400 / 91.7 = 1116

The root cause is if you have many very small files and we are writing many small segments
(smaller than 256K) to the volume, and that caused space gap in the volume.
Increasing TXNGroupmax can prevent this kind of gap.

Example with FILE type volume to see how it works .
After increasing the TXNGroupmax, the problem can be resolved.

First test:
Define two FILE type devclass FILEDEV and FILEDEV2 which have capacity 200M and 40M respectively.
Backup about 100000 files, each file is smaller than 1K.
The TXNGroupmax is 256. After backup stgpool, we can see the volume 00000011.BFS has
estimated capacity of 23.1M which smaller than the devclass' capacity.
23.1M is the actually data wrote to the volume.

query volume


Volume Name Storage Device Estimated Pct Volume
Pool Name Class Name Capacity Util Status
-------------------- ----------- ---------- --------- ----- --------
D:\TSM\0000000C.BFS FILEPOOL FILEDEV 200.0 M 20.3 Filling
D:\TSM\00000011.BFS COPYPOOL FILEDEV2 23.1 M 100.0 Full
D:\TSM\00000012.BFS COPYPOOL FILEDEV2 40.0 M 43.8 Filling



Second test:

Backup more files than first test, define the second devclass FILEDEV3 has capacity of 50M .
The TXNGroupmax is 440 this time. After backup stgpool, we can see the volume 0000002D.BFS
has estimated capacity of 49.6M which very close to 50M.

query volume


Volume Name Storage Device Estimated Pct Volume
Pool Name Class Name Capacity Util Status
-------------------- ----------- ---------- --------- ----- --------
D:\TSM\00000027.BFS FILEPOOL FILEDEV 200.0 M 28.9 Filling
D:\TSM\0000002C.BFS FILEPOOL FILEDEV 200.0 M 0.6 Filling
D:\TSM\0000002D.BFS COPYPOOL FILEDEV3 49.6 M 100.0 Full
D:\TSM\0000002E.BFS COPYPOOL FILEDEV3 50.0 M 19.0 Filling
 
TSM: SQL Command ที่ใช้บ่อย PDF Print E-mail
Written by Wira Chinwong   
Wednesday, 29 June 2011 21:24

ต้องการดูว่าแต่ละ Node ใช้ Volume อะไรบ้าง

q nodedata NODENAME stg=XXXX

 

หรือ

 

select volume_name from contents where node_name like '%nodename%' and FILESPACE_NAME like '%Filespacename%' and FILE_NAME like '%Filename%'

 

 

Last Updated on Thursday, 30 June 2011 21:09
 
TSM Fastback: การเก็บ log เพื่อนำมาวิเคราะห์ หรือส่งให้ทาง IBM Support PDF Print E-mail
Written by Wira Chinwong   
Friday, 24 June 2011 12:19

FastBack server log:

1. System Information Logs: You can locate this information by going to: " Start Menu\All Programs\Accessories\System Tools\ System Information" or in the directory "c:\Program Files\Common Files\Microsoft Shared\MSInfo" as misinfo32.exe. Inside the System Information Tool go to "File-> Save", and save as "System_Info.nfo".

2. Application and Server Event Logs: Go to "Start -> Settings -> Control Panel -> Administrative Tools -> Event Viewer." In the left window click on "Application". From the drop-down menu go to "Actions -> Save Log File As" and name the text file "Application Event Log.evt". Repeat this process for the System Event Log, naming the file "System Event Log.evt".

3. FastBack Logs and Files Windows 2008: "C:\ProgramData\Tivoli\TSM\FastBack\server"
This folder contains error logs and configuration files for Fastback Server. Zip all files that are in this root directory (but do not include the other sub-directories) by highlighting the files, right clicking, and then selecting "Send To->.Compressed Folder". 

FastBack client log:


1. System Information Logs: You can locate this information by going to: " Start Menu\All Programs\Accessories\System Tools\ System Information" or in the directory "c:\Program Files\Common Files\Microsoft Shared\MSInfo" as misinfo32.exe. Inside the System Information Tool go to "File-> Save", and save as "System_Info.nfo".

2. Application and Server Event Logs: Go to "Start -> Settings -> Control Panel -> Administrative Tools -> Event Viewer." In the left window click on "Application". From the drop-down menu go to "Actions -> Save Log File As" and name the text file "Application Event Log.evt". Repeat this process for the System Event Log, naming the file "System Event Log.evt".

3. FastBack Logs and Files Windows (NOT windows 2008): "C:\Documents and Settings\All Users\Application Data\Tivoli\TSM\Fastback\Client"
This folder contains error logs and configuration files for Fastback Client. Zip all files that are in this root directory (but do not include the other sub-directories) by highlighting the files, right clicking, and then selecting "Send To->.Compressed Folder". 


above steps are refer to technote :
https://www-304.ibm.com/support/docview.wss?uid=swg21314831

Last Updated on Friday, 01 July 2011 19:46
 
Oracle: การเปิด และ ปิด Archive log PDF Print E-mail
Written by Wira Chinwong   
Sunday, 26 June 2011 09:08

การเปิด archive log สามารถทำได้ดังนี้

1. ทำการกำหนดค่าของ Archive หลังจากที่มีการ Enable แล้วใน initxxx.ora หรือ ใน spfilexxx.ora

############################
# Archive Log Destinations -benr(10/15/04)
############################
log_archive_dest_1='location=/u02/oradata/cuddle/archive'
log_archive_start=TRUE

2. เปิด Database ใน Mode Mount และทำการ Enable Archive log

SQL> startup mount;
ORACLE instance started.

Total System Global Area 1073741824 bytes
Fixed Size                  1265508 bytes
Variable Size             465567900 bytes
Database Buffers          536870912 bytes
Redo Buffers               70037504 bytes
Database mounted.
SQL> select log_mode from v$database;

LOG_MODE
------------
NOARCHIVELOG

SQL> alter database archivelog;

Database altered.

SQL> alter database open;

Database altered.

 

 
TSM: Using TSM for VE to backup VMWare environment PDF Print E-mail
Written by Wira Chinwong   
Monday, 20 June 2011 22:39

Wroten by Vedran.


1) Using only TSM client for Windows V6.2.3 and TSM standard edition

  • this will only give you ability to do full image backups using vStorage API. You don't need staging area for images anymore (like in VCB) but the whole disk image is read every time from the VMFS store.
  • since server-side deduplication is now avaliable in standard edition of TSM (i.e. you don't need Extended Edition anymore), if your backup window allows it you can perform daily full image backups that don't take much server space since the parts of the image that didn't change will get deduplicated.
  • keep in mind that deduplication works only with a devclass of type FILE. For this to work you need double space for storagepools (so they can take whole image and later deduplicate it) or do on-the-fly deduplication/migration but you'll probably hog your hardware since you need to use AUTOCOPY to copystgpools and then reclaim volumes while backup is still running... or disable DEDUPREQUIRESBACKUP and risk data corruption.
  • if you can not afford to use deduplication and full image backups for frequent backups, you can do weekly (or monthly) vmware image backups and incremental-by-date client backups. For this you need to instal TSM BA clients into VMware guests.

STEPS TO SET UP:

  • simply choose a windows machine that will be your "backup proxy". Install TSM BA client into it and configure it with "VMBACKUPENGINE=FULLVM" and "VMFULLTYPE=VSTOR". The latter option enables the use of vStorage API. Also you need to tell your BA client where your vCenter host is and give it credentials to connect. All of these options are configured in the "VM backup" tab of the BA client configuration screen.
  • if you want your guests to be backed up under their own node names, you need to create a node for each guest and then grant proxy rights to your windows machine node
  • to back up machines using command line, use for example "BACKUP VM MACHINE_NAME". You can back up multiple VMs at once,
  • TIP: you can use either a vCenter or an ESX host as your VMCHOST
  • TIP: you can use pre-freeze and post-thaw scripts that will run before/after taking the snapshot for backing up. You can use this for example to quiesce a guest database/application to have a consistent snapshot. But remember that you need to run native database backups in order to prune transaction logs for your databases.
  • WARNING: your proxy machine can be a VM too but you must not have it back up itself due to the bug mentioned in the OP (it dismounts both its own hot-added image as well as the system image from which the system was booted). If you need it backed up too, use classic "backup image" or have another windows client backup your proxy.


===
2) Using TSM for Virtual Environments (somewhere listed as TDP4VMware) with TSM standard edition
- this will allow you to perform incremental image backups of your vmware machines using CBT.
- Virtual Hardware for the guest needs to be V7.0 in order for CBT to work, otherwise the full image is read every time.
- VMware tools need to be installed and running in guest OS
- TSM4VE also offers fantastic restore options... for example you can choose to attach your backup image to a live guest... it appears as an additional drive and it is available immediatly, even if most of the image is stored on a tape... requests just block until the image is restored, just like in HSM. Details here: http://publib.boulder.ibm.com/infocenter/tsminfo/v6r2/topic/com.ibm.itsm.ve.doc/t_ve_restoring.html

STEPS TO SET UP:

same as #1, plus:
- install TDP4VMware. If i recall correctly, with it you will receive TDP4VMware.lic that needs to be put in the BA client folder or you will get some sort of licencing error if you try to use incremental backups
- now you can perform backups with "backup vm -vmbackuptype=fullvm -mode=incremental
- the first time you perform

===
3) Using Tivoli Storage Manager for Virtual Environments + TSM Extended Edition
- only EE offers client-side deduplication (new feature in V6.2)
- this is as good as it gets. you can do incremental CBT-based image backups that are compressed and deduplicated on the client and then sent to the server for maximum space savings and minimum amount of network traffic / VMFS store access.
- I repeat, this is awesome :) In one real implementation we were backing up 1,5TB of SAN storage to a 1,5TB TSM server. The storage has about 700GB of data on it. File share, AD, SQL server, the usual. We were retaining 30 backup versions (a whole month, weekly fulls, daily incrementals, SQL backups) and all 30 versions (that's 4-5 full image backups and ~25 incrementals) after deduplication and compression only consumed around 500GB of TSM disk storage! Daily incremental backups took around 20 minutes to complete with minimal impact.

STEPS TO SET UP:

  • same as #1 + #2 plus:
  • your proxy node needs to have "dedup=clientorserver" and "compression=yes" set
  • everything else required for stadard deduplication applies: enable your destination storage pool for deduplication. The first pool in the hiearchy must be of type "file" and have DEDUP=YES. This is the storage pool defined in your copy group for your management class. Volumes won't be deduplicated before being backed up to a copystoragepool unless you set the server option DEDUPREQUIRESBACKUP to NO.


other things worth mentioning:

  • it appears that if your oldest full backup is older than RETEXTRA days and gets expired, this will invalidate all the incremental backups made until the next oldest full backup.

 

  • compression + deduplication only works if you got everything working right. Also, you can not send compressed data to a deduplicated pool for asynchronous server-side deduplication. Deduplication needs to occur before data compression and the only way to do it is on the client side, this is why you need EE to reap the full benefits.

 

  • TSM BA client will always try to choose the best path to the target VMFS store... if it resides on the same ESX host it will probably use hot-add to back up the image. If it is located on a remote ESX host it will use NBD. As long as your proxy can reach the ESX host via network, it will be able to back up your VM guests. In some situations I found hot-add to be slower than NBD... possibly because VM had snapshots, I don't know. You can force the client to use a specific transport mode using the "vmbackvcbtransport" parameter (and yes, it applies to vStorage API too despite its name). See here: http://publib.boulder.ibm.com/infocenter/tsminfo/v6r2/topic/com.ibm.itsm.ve.doc/r_cmd_bkupvm.html

 

 
<< Start < Prev 1 2 3 4 5 6 7 Next > End >>

Page 4 of 7

Polls

คุณใช้ Software Backup อะไรในองค์กร
 

Who's Online

We have 17 guests online