Welcome to SCSI
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 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
 
Exchagne: Setup Circular Loggin ใน Exchange 2010 PDF Print E-mail
Written by Wira Chinwong   
Wednesday, 15 June 2011 15:32

    Log file truncation, or deleting the transactional log files that are no longer required for a successful database restore, takes place once you do a successful backup. But if you do not perform a backup in situations where you decided to no longer use traditional point-in-time backups, how will you make sure the log files are removed so they don’t pile up? Simple: they are never removed.

    Once you enable circular logging when multiple database copies are in place, you get a new type of circular logging called continuous replication circular logging (CRCL) which behaves differently from traditional circular logging known from Exchange 2007 and before.
 CRCL is performed by the Microsoft Exchange Replication Service, not the Microsoft Exchange Information Store service. Also, CRCL requires considering log files that are required for log shipping and replay before removing them. This situation needs special logic to ensure that all database copies process the log file before it is removed, which differs from the traditional circular logging logic where the log file was deleted when it was committed to the database.


 When CRCL is enabled, log file truncation for database copies that are not lagged occurs in the following way:
- The log file is checked to determine whether it is below the checkpoint.
- The log file is inspected that all other non-lagged database copies replayed the log file into their database.
- The log file has been inspected by all database copies (including any lagged database
copies).

Log file truncation happens for lagged database copies in the following way:
- The log file is checked to determine whether it is below the checkpoint.
- The log file is older than ReplayLagTime and TruncationLagTime.
- The log file is already deleted on an active database copy and all copies agree on the
deletion.

 
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

 

 
Linux: วิธีการ Mount Windows share folder บน Linux PDF Print E-mail
Written by Wira Chinwong   
Tuesday, 14 June 2011 22:12

# mkdir /mnt/cifs
# mount -t cifs //server-name/share-name /mnt/cifs -o username=shareuser,password=sharepassword,domain=scsi
# mount -t cifs //192.168.101.100/sales /mnt/cifs -o username=shareuser,password=sharepassword,domain=scsi
หรือ
#mount.cifs //192.168.101.100/sales /mnt/cifs -o username=shareuser,password=sharepassword,domain=scsi

โดยที่

  • username=shareuser : specifies the CIFS user name.
  • password=sharepassword : specifies the CIFS password. If this option is not given then the environment variable PASSWD is used. If the password is not specified directly or indirectly via an argument to mount, mount will prompt for a password, unless the guest option is specified.
  • domain=scsi: sets the domain (workgroup) of the user
Last Updated on Sunday, 03 July 2011 02:56
 
<< Start < Prev 1 2 3 4 5 6 Next > End >>

Page 4 of 6

Polls

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