Welcome to SCSI
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

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

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 // /mnt/cifs -o username=shareuser,password=sharepassword,domain=scsi
#mount.cifs // /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
TSM: ERROR: ANS1996W The volume points enumeration on „C:\“ volume failed PDF Print E-mail
Written by Wira Chinwong   
Saturday, 04 June 2011 15:56

หลังจากใช้ TSM Fastback mount เป็น Virtual Folder ขึ้นมา แล้วใช้ TSM Client สำรองข้อมูลใน path นี้ ปรากฏว่ามี error นี้เกิดขึ้นในตอนแรก

ERROR: ANS1996W The volume points enumeration on „C:\“ volume failed

ถ้าเป็น Windows2003 SP2 ให้ลง Patch นี้ตามไป แล้วจะทำให้ไม่มี error เกิดขึ้นอีก


Last Updated on Saturday, 04 June 2011 15:57
VMware: VCB with windows 7 or windows 2008 PDF Print E-mail
Written by Wira Chinwong   
Tuesday, 14 June 2011 21:22
When you install either Windows 7 or Windows Server 2008 R2 onto a un-partitioned hard drive it will create a 100Mb partition that does not have a drive letter. This 100Mb partition is mainly there in case you are going to use the Bitlocker feature however Windows also puts its boot loader on this partition meaning you cant just delete it.
I found that after creating a 2008 R2 server on VMWare I was unable to  back up the server using VCB because of this partition, I believe VMWare expects the operation system to be the first partition. Once the partition was removed VCB worked as normal
I was getting messages such as the below when tring to mount the server using VCB.
[2010-06-10 17:12:05.872 'vcbMounter' 7600 error] Error: Cannot query guest OS information. The mount directory path is invalid.
[2010-06-10 17:12:05.872 'vcbMounter' 7600 error] An error occurred, cleaning up...
You may also want to remove this partition to have a single clean partition to make imaging a client machine easier.
If you can it is  best to stop Windows creating the partition during the install, however if you have already installed Windows and need to remove the System reserved partition for whatever reason the below steps shoukd do the trick.
I have done this several times and have not had any issues but I would say;
1) Open a command prompt with administrator privileges (right click => run as administrator)
bcdboot c:\windows /s c:
You should get a message similar to:
Boot files successfully created.
2) Open the Disk Management GUI (you could use diskpart for scripts), locate the  C:\ partition right-click and select “Mark Partition as Active”, select yes to the “do you want to continue message”
3) Reboot to confirm that everything is ok.
4) In Disk Management you can now delete the 100Mb System Reserved partition by right clicking on it and selecting “Delete volume”
5) To re-claim the 100Mb you can use a partitioning tool such as partition magic or gparted
TSM: วิธีการเลือกความสำคัญของ Volume ในกรณีที่ต้องการ Restore PDF Print E-mail
Written by Wira Chinwong   
Sunday, 22 May 2011 07:59



Is there a priority for volume selection between device types or between primary and copypools?



The following sequence/priority is used for volume selection by a restore:
1. Active-data pool (FILE)
2. DISK (random)
3. FILE (primary or copypool).
4. Active-data pool sequential onsite.
5. Sequential onsite-volume (primary or copy) priority considers:

a. mounted (idle)
b. automated
c. manual

6. Sequential offsite-volume (primary, copy or ADP)

Example 1:
If the primary pool is sequential tape and the copypool is of type FILE. The restore process will use the copypool volumes as they are higher in priority on the list.

Example 2: If both the primary pool and copypool are of the same device type such as File or Sequential Tape there is no priority of stgpool and the TSM server will optimize the restore and can use any available volume from either pool. Starting at TSM 5.4.2, due to APAR IC54239, TSM creates a tie breaker for sequential pools (non-active data pools) and will select the primary pool volume.

Last Updated on Sunday, 22 May 2011 07:59
<< Start < Prev 1 2 3 4 5 6 7 Next > End >>

Page 5 of 7


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