How to migrate file shares to destination server
To migrate file shares select the “File Shares” tab, then check “Migrate file shares to destination servers”.
Secure Copy recreates on the target server, the file shares that are on the source server. Shares whose folders are not specified in the source paths are not copied. In other words, as Secure Copy runs the copy process, it checks each source path and its subfolders to see if they are shared. If so, and if this option is specified, Secure Copy recreates the share on the target computer and creates the appropriate share permissions as dictated by those of the source.
The sub options are used if the share name already exists or if the share needs to be created on a Windows 2000/XP/2003/Vista/7, Windows Server 2008, or Windows 2008 R2 cluster.
If the share name already exists…
Skip It (Ignore)
If a share already exists on the target, Secure Copy does not create the share on the target.
Overwrite (Remove old share, create new one)
If a share already exists on the target, Secure Copy unshares the share on the target, and then writes over it with the source share.
Add the prefix Add the suffix
In cases where there may be multiple shares of the same name and you want to recreate the shares using the new folders from the source, but manually renaming the shares when prompted may be unfeasible, such as in the case of a scheduled job, you can have Secure Copy add a prefix or a suffix to the new share name. This gives a uniform naming convention to the new shares and prevents unnecessary user intervention.
Cluster Group Name
Applicable only to Windows 2003. If you are copying data to a cluster group, type the name of the cluster group. Secure Copy migrates the shares to the specified cluster group.
If the shares are not created on the target, from a command line run fsmgmt.msc, select shares, and check to see if there are any shares that already exist with the same name. The job log should show the shares being identified. Click Logs and Reports, expand the name of the job, select the most recent run date, select the Logs Viewer tab and look for Messages similar to 'Attempting to obtain share 502/1005 information'. If there are no log entries with similar messages, try creating a new job (not copying the settings from an existing one) and run the job again.
© ALL RIGHTS RESERVED. Feedback 이용 약관 개인정보 보호정책 Cookie Preference Center