Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Consultations on Deployment DLO 7.5

Created: 06 Jan 2014 | 1 comment
JavierTI_'s picture
hi friends,
a question on DLO v7
how much is the percent of compression of data?
more information of "Integrated high speed data deduplication".
in a WAN enviroment, that steps should I take?
 
Thanks.
Operating Systems:

Comments 1 CommentJump to latest comment

inn_kam's picture

1.Compression answer from DLO 7.5 admin guide page no 109 

Example If you are retaining three revisions of each file

and have 10 MB of data to back up, approximately
30 MB of disk space are required if file sizes
remain consistent between revisions.
Although compression can improve the space utilization, it varies significantly with
file type and other factors. Typical compression ratios are approximately 2:1, so in
the previous example, the maximum disk space usage might be reduced to
approximately 15 MB.
 
2.Global Source-side Deduplication
DLO 7.5 now supports deduped backups.
The following are the methods of deduplication supported:
■ Intelligent deduplication of files
      ■ Dedupe the entire file for the very first time; that is, the very first backup
revision of the file will be deduped.
        ■ If the file changes, then the backup modality automatically switches to
“delta mode” from “dedupe mode” for that file, that is, delta will be applied
from second revision of the backup file on a particular computer.
 
■ Content aware deduplication of PST
 
Global single instancing (SIS) of the attachments is achieved using content
aware deduplication of PST.
This feature helps in improving the network usage and optimizes the storage
requirements.
 
 
About Dedupe Storage Locations
The Dedupe Storage Location is a Common Internet File System (CIFS) network
share location where data is stored as part of deduplication process. A logical group
of Dedupe Storage Locations across which deduplication is performed is called a
Dedupe Storage Pool.
Dedupe Storage Locations hold shared data that is common across and is shared by
all or a subset of users in the system. So the users pointing to Dedupe Storage
Locations (through Storage Location Mapping) in the same Dedupe Storage Pool
need to have read/write access to all the Dedupe Storage Locations in the Storage
Pool.
For security reasons, read/write access to the Dedupe Storage Locations is not
granted to all the users even though they need to read and write data from the
Dedupe Storage Locations. Instead, while creating the Dedupe Storage Location, the
administrator configures a new user account called “Dedupe Storage Location
Access Credential”, which will be used by the Desktop Agent to access the Dedupe
Storage Location.
Hence it is recommended that the administrator specifically creates a low privilege
domain user account as “Dedupe Storage Location Access Credential” for accessing
the Dedupe Storage Location, and for security reasons.
In addition, the administrator should ensure that the password for this user account
does not expire frequently. If the password expires, then the administrator should
reset the password for the domain user.
All types of CIFS network shares supported by DLO Storage Location are supported
by Dedupe Storage Locations also.
The following are some important facts about Dedupe Storage Locations:
■ The Dedupe Storage Location name has to be unique across groups.
■ The same network share should not be assigned to more than one Dedupe
Storage Location.
■ All network shares assigned to Dedupe Storage Locations in a Dedupe Storage
Pool should have the same “Dedupe Storage Location Access Credential”.
■ Only the administrator and users with “Dedupe Storage Location Access
Credential” account should have access to the network share location used as a
Dedupe Storage Location.
■ The “Dedupe Storage Location Access Credential” account should not have
administrator rights.
■ The Dedupe Storage Location path should not be the same as the NUDF folder
path.
■ After the Dedupe Storage Location is associated with a DLO Storage Location,
and a deduped backup is performed, in case the Dedupe Storage Location should
be moved, then make sure to use the -MigrateSL command.
■ The Dedupe Storage Location user should have the “Allow log on locally” policy
set in the domain controller group policy object. To set this policy, do the
following:
■ After logging on locally with domain admin account, run gpmc.msc (Group
Policy Management).
■ Double-click the Domain name.
■ Expand <Group Policy Objects> and right-click <Default domain
controllers policy>.
■ Click Edit.
■ Expand <Computer Configurations> <Policies> <Windows Settings>
<Security Settings> <Local Policies> <User Rights Assignment>.
■ Right-click <Allow log on locally> and click Properties. Change as required.
■ Run gpupdate and wait for the confirmation: "user policy update has
completed succesfully" (default gpupdate without switches should only
apply the changes).