Thursday, December 29, 2011
OneKey Recovery 7.0 error code 0xEB1b068A
My gf just purchased a new laptop, and I am helping her to set it up. When I attempt to create the Recovery DVD, I receive the error 0xEB1b068A after burning the 2nd DVD. Search Lenovo site and find the answer.
Monday, December 5, 2011
Install language support in CentOS 5
I have trouble reading Chinese in my CentOS 5 VM. I search google and find this link http://www.cyberciti.biz/faq/linux-install-language-support/
I ran the command
yum install "@Chinese Support"
Now, I have no trouble reading Chinese with Firefox.
I ran the command
yum install "@Chinese Support"
Now, I have no trouble reading Chinese with Firefox.
Sunday, December 4, 2011
NetWorker cloning for DataDomain boost device
DataDomain boost is supported in NetWorker 7.6.1 or above. With clone from boost to boost devices, it is no longer a one to one ratio. You can have more than one read session from the same boost NetWorker readonly device. Also, multiple clone jobs can write to the same boost device at the same time. Of course, it is not recommended to allow more than 4 sessions at the same time per boost device.
At the same time, it only sends the delta to the clone destination (given the destination is boost device). This shorten the time for cloning after backup.
If the read or write media are not boost device, it should fall back to the one to one ratio (legacy way).
However, be very careful if your storage node is a very busy storage node, for example, SQL cluster. Because dedup happens on the storage node (storage side dedup), this can cause heavy CPU usage. So, best option is to config your SQL cluster as dedicated storage node with AFTD.
At the same time, it only sends the delta to the clone destination (given the destination is boost device). This shorten the time for cloning after backup.
If the read or write media are not boost device, it should fall back to the one to one ratio (legacy way).
However, be very careful if your storage node is a very busy storage node, for example, SQL cluster. Because dedup happens on the storage node (storage side dedup), this can cause heavy CPU usage. So, best option is to config your SQL cluster as dedicated storage node with AFTD.
Subscribe to:
Posts (Atom)