Steps to move a Backup Exec 2010 R3 Deduplication Storage folder to a new server.
|Article:TECH162083|||||Created: 2011-06-11|||||Updated: 2012-04-03|||||Article URL http://www.symantec.com/docs/TECH162083|
Need to move a Backup Exec 2010 R3 Deduplication Storage folder to a new server because
In preparation for the moving the Deduplication Storage Folder to a new server, the following information will need to be confirmed.
- Source and Target Media Servers has Backup Exec 2010 R3 installed and licensed for the Deduplication Storage Option.
- Source and Target Media Servers are at the same hotfix level.
- Target Media Server meets RAM and CPU resource requirements to support the Storage Volume.
- The Deduplication Storage Folder database folder exists on the same volume as the data folder.
- Target Media Server has the same logon account and password used for the Deduplication Storage Folder as the Source Media Server.
Note: In Backup Exec 2010 R3, the logon account used for the Deduplication Storage Folder cannot be defined as the System Logon Account.
For more information regarding the System Logon Account change, see www.symantec.com/docs/TECH164679.
1. Open Microsoft iscsi initiator.
2. Select dedupe disk lun.
3. Click on disconnect.
4. Configure iscsi target software to allow new server to access lun.
5. Open Microsoft iscsi initiator.
6. Refresh the targets.
7. Select the old dedupe lun.
8. Add the connection to the list of favorite resources.
9. Click on volume and devices in the initiator.
10. Click on auto configure.
11. Change drive letter to match the old server if desired with disk management.
12. Open backup exec.
13. Click on devices.
14. Right click on the server.
15. Create new dedupe folder.
16. Point to the iscsi lun from the old server.
17. Use the same user the was used on the old server for the log on account.
18. Click ok.
Gathering information may take hours while the permissions are updated check process monitor, and confirm the icals is using processor and disk I/O.
Article URL http://www.symantec.com/docs/TECH162083