Troubleshooting guide

1-28
Cisco Wide Area Application Services Configuration Guide
OL-26579-01
Chapter 1 Planning Your WAAS Network
Data Migration Process
In smaller WAAS deployments where all WAEs can be configured with the same settings, you may only
need to create one general device group. This practice allows you to configure settings for the group,
then apply those settings consistently across all your WAEs.
Note The AllWAASGroup and AllWAASExpressGroup are default device groups that automatically contain
all WAAS and WAAS Express devices. In these or any other device groups, you should configure only
the settings that you want to be consistent across all the devices in the group. Settings that apply to a
single device should be configured on that device only and not on the device group.
By default, WAAS Central Manager allows you to assign a device to multiple device groups. Before you
create a device group, make sure you understand the unique properties that you want the group to
contain.
WAAS Central Manager allows you to create locations that you can associate with a WAAS device. You
assign a device to a location when you first activate the device. The main purpose of assigning a WAAS
device to a location is to help you identify a WAAS device by the physical region in which it resides.
Locations are different from device groups because devices do not inherit settings from locations.
You assign a device to a location when you activate the device as described in the Cisco Wide Area
Application Services Quick Configuration Guide. For more information about logically grouping your
WA E s , s e e Chapter 1, “Using Device Groups and Device Locations.”
Data Migration Process
If you have an existing network, there are some steps to take before setting up your WAAS network. The
first step in the data migration process is to back up the data at the branch offices and restore it to the
data center.
After you back up data to the data center, you preload the cache (called preposition) with the files for
which you want to provide the fastest access. Set up the files from your branch office file server to the
WAEs that are also located in the same branch office. You can then remove the file servers from the
branch offices and point to the data center file server.
The final step in the data migration process is to set the CIFS policies.
When doing the data migration process, note the following restrictions:
• Prepositioning only works in a CIFS environment with the CIFS accelerator (it is not supported by
the SMB accelerator).
• The topology for the file server at the data center must be identical to the topology that existed on
the branch file server.
• Resource credentials (such as ACLs) are not automatically migrated. Two options are available:
– You can use backup or restore software to restore an initial backup of the tree to the target server.
This practice allows both the creation of ACLs as well as the creation of the initial file set that
Rsync can take as an input for diff calculations. The replication inherits existing ACLs in that
tree.
– The other option is to perform a first run of Robocopy (including data and permissions), and
then continue with sync iterations using Rsync.
After replicating, use one of Microsoft’s tools for copying only ACLs (no data) onto the replicated
tree. You can use Robocopy.exe for copying directory tree or file ACLs and Permcopy.exe to copy
share permissions.