Description: How to certify Amazon Web Services Simple Storage Service (AWS/S3) Compatible Cloud providers for ARCserve products.

There are various Private/Public cloud providers that are compatible with AWS/S3.

If you would like to see your Cloud software to be supported by ARCserve products, for the initial certification you can contact the Product Management team.

For subsequent updates to your Cloud software, you will need to self-certify them by following the instructions below. You will need to run these tests and send the results to Product Management team

Configuring Cloud based connections with CA ARCserve Backup

Configuring an cloud provider involves creation of Cloud Connections first and then creating devices using the connections. Cloud connections and devices can be configured from Backup Manager destination tab or from Archive Manager destination tab or from device manager.

1. Open CA ARCserve Manager and follow the following steps shown in the image

2. Select Destination tab of the Backup Manager or Destination tab of Archiving Manager or Device Manager and follow the steps mentioned in the image to add new Cloud Connection.

3. After successful creation of cloud connection , follow the steps listed in the image to create cloud based devices

Test Cases to be performed

Case 1: Device Configuration1. Go to Device Manager2. Create new cloud connection by choosing “Manager Cloud Connections” from bottom right

pane.3. After succesful creation of cloud connection, a pop-up should come for creation of new

Cloud device4. Click Yes and create new cloud device

Result: Cloud device should be created successfullyNote:

1. Create Cloud device from backup manager and Archive manager2. In step 3, choose No and create cloud device by choosing “Manage Cloud-based devices”

option from bottom right pane.3. Create cloud connections with http and https if cloud vendor supports both and create

devices on both the connections

Case 2: Format Cloud device1. Format newly created Cloud device2. Run few backups on to the Cloud Device3. Format cloud device4. Submit Backup/Archive job to Formatted device in step 2Result: Data Migration jobs should be successful to the cloud device

Case 3: Erase Cloud device1. Run few backups on to the Cloud Device2. Erase cloud device3. Submit Backup/Archive job to erased device in step 2Result: Data Migration jobs should be successful to the cloud device

Case 4: Backup to FSD as staging device and migration to cloud1. Create a File system device and a cloud based device in the backup destination tab2. Click on BackupStart tab and select “Normal backup” and “Enable Staging” from that window.3. Click on BackupSource tab and select the source to be backedup.4. Click on BackupStaging tab and select the FSD created in the 1st step as a staging location.5. Click on Backuppolicies window and make all fields zero , to run the migration job

immediately.6. Click on BackupDestination tab and select the cloud device as a final destination. 7. Select Cloud Policy in backup destination tab and change the purge policy to 1 day (default is 3

years)8. Click on OptionsEncryption/Compression and select Encrypt data and Compress data at agent,

specify encryption password.

9. Submit backup job.

Result:1. Backup should be successful and no errors/warnings in activity logs.2. Wait for completion of a day, check the cloud location to see the session is purged (do not

change date/time on the machine as it will not change date/time on cloud. So need to wait for a day to check the result)

Case 5: Restore by session for files/folders from Cloud device 1. Open Restore Source window and select restore from session from the drop down menu at

the top.2. Select the session backed up in case 4 from the cloud device and open Restore Destination

tab , uncheck “Restore to original location” and select alternate location.3. Submit Restore job.4. After restore , Compare the version of the restored files with the original file.

Result: Restore and compare should be successful and no errors/warnings in activity logs.

Case 6: Backup to Dedupe device as staging device and migration to cloud1. Create a Dedupe device and a cloud based device in the backup destination tab2. Click on BackupStart tab and select “Deduplication backup” and “Enable Staging” from that

window.3. Click on BackupSource tab and select the source to be backedup.4. Click on BackupStaging tab and select the Dedupe device created in the 1st step as a staging

location.5. Click on Backuppolicies window and make all fields zero , to run the migration job

immediately.6. Click on BackupDestination tab and select the cloud device as a final destination.7. Submit backup job.

Result: Backup should be successful and no errors/warnings in activity logs.

Case 7: Restore by Backup Media 1. Open RestoreSource window and select “Restore by Backup Media” from the drop down

menu at the top.2. Select the appropriate cloud device with session backed up in case 63. Submit Restore job4. After restore , Compare the version of the restored files with the original file.

Result: Restore and compare should be successful and no errors/warnings in activity logs.

Case 8: Archive to cloud with FSD as staging device and migrate to cloud1. Create a File system device and a cloud based device in the Archive destination tab2. Click on ArchiveStart tab and select “Cloud Archive” and “Enable Staging” from that window.3. Click on ArchiveSource tab and select the source to be backedup.

4. Click on Archive Staging tab and select the FSD created in the 1st step as a staging location.5. Click on Archive policies window and create a policy for the files that needed to be archived .6. Click on Archive Destination tab and select the cloud device as a final destination.7. Click on OptionsEncryption/Compression and select Encrypt data and Compress data at agent,

specify encryption password.8. Submit Archive job.9. After Archive job check whether the backedup file is deleted from source or not.10. Connect to cloud using cloud berry or any other cloud connecting tool and check files are

available in destination.Result: Archive should be successful and no errors/warnings in activity logs.

Case 9: Restore by Backup Media from Archived session1. Open RestoreSource window and select “Restore by Backup Media” from the drop down

menu at the top.2. Select the appropriate cloud device with session backed up in case 83. Submit Restore job4. After restore , Compare the version of the restored files with the original file

Result: Restore and compare should be successful and no errors/warnings in activity logs.

Case 10: Archive to cloud with Dedup device as staging device and migrate to cloud1. Create a Dedup device and a cloud based device in the Archive destination tab2. Click on ArchiveStart tab and select “Cloud Archive” and “Enable Staging” from that window.3. Click on ArchiveSource tab and select the source to be backedup.4. Click on Archive Staging tab and select the Dedupe created in the 1st step as a staging

location.5. Click on Archive policies window and make all fields zero , to run the migration job

immediately.6. Click on Archive Destination tab and select the cloud device as a final destination.7. Submit Archive job.8. Connect to cloud using cloud berry or any other cloud connecting tool and check files are

available in destination.Result: Archive should be successful and no errors/warnings in activity logs.

Case 11: Restore by session for files/folders from archived session1. Open Restore Source window and select restore from session from the drop down menu at

the top.2. Select the session backed up in case 10 from the cloud device and open Restore Destination

tab , uncheck “Restore to original location” and select alternate location.3. Submit Restore job.4. After restore , Compare the version of the restored files with the original file.

Result: Restore and compare should be successful and no errors/warnings in activity logs.

Case 12: Purge Data from Cloud Storage from restore manager console.1. Make sure to run few backups to cloud device2. Go to restore manager, select from the Source tab -> the Restore by Session method. 3. Select the cloud sessions you want to delete from the Sessions directory tree. 4. Right-click the sessions and click Delete selected sessions.

Result: The sessions are removed immediately from the cloud storage.Case 13: Purge Data from Cloud Storage from device manager

1. Go to Device Manager console,2. Click “Browse Cloud Folder” from the toolbar3. Select a folder and right-click to delete.4. A pop-up comes that files/folders can not be deleted because it is being used by active cloud

device on server5. Go to “Manage Cloud-based devices” from toolbar and remove the cloud device6. Repeat steps 2 and 3

Result: selected folder is removed from the cloud storage.With Proxy:Run all the above cases by configuring Proxy.

Troubleshooting:

1. More information and/or errors can be seen in Amazon Logs which can be found under “$ARCSERVE_HOME\CCI\Plugin\Amazon\Log”

2. Collect below logs and share with CA Support team if further help is requried from CA Support team

a. $ARCSERVE_HOME\CCI\Plugin\Amazon\Logb. $ARCSERVE_HOME\CCI\Logc. $ARCSERVE_HOME\Logs

Configuring Cloud based connections with ARCserve D2D

Refer below screen shots on how to configure any AWS/S3 Compatible Cloud as destination with ARCserve D2D.

Configuration:

1. Go to Settings

2. Go to File Copy Settings -> Source

3. Destination can be configured with Amazon S3 with Region US_Standard(Refer below figure for details on configuration)

4. Go to File Copy Settings -> Destination

5. Scroll down in this tab, to choose other options as required. Screen-shot below

6. Go to File Copy Settings -> Schedule

Test Cases:

Policy Type: File Copy

Pre-requisites:1. Create a dataset with multiple files with various file extensions like mpeg1, mp4 and pptx2. Add mpeg1, mp4 and pptx for file copy Source and configure Cloud destination with File Versions as 3 and schedule as 1 thru File Copy Settings tab in Settings

Case 1: (Versions)1. Run the backup and completes successfully 2. Let file copy job run after each backup (as we put schedule as 1)Result: 1. Make sure files are not deleted 2. Go to Restore -> Browse File Copies3. Check the proper destination for "Restore From". If correct cloud location is not shown change to correct location using Change button4. Check all the copied files are shown properly with correct version for every file in brackets (Shows 1 as we have first version)

Case 2: (Versions)

1. Modify one file and then run another backup. 2. Let file copy job run after backup (as we put schedule as 1)Result: 1. Make sure files are not deleted 2. Go to Restore -> Browse File Copies3. Check the proper destination for "Restore From". If correct cloud location is not shown change to correct location using Change button4. Check the modified file is showing proper version (Shows 2 as we have second version)

Case 3: (Versions)1. Modify the same file used in Case 2 again and run another backup2. Let file copy job run after backup (as we put schedule as 1)Result: 1. Make sure files are not deleted 2. Go to Restore -> Browse File Copies3. Check the proper destination for "Restore From". If correct cloud location is not shown change to correct location using Change button4. Check the modified file is showing proper version (Shows 3 as we have third version)

Case 4: (Negative Test for Versions)1. Modify the same file used in Case 2 and 3 again and run another backup2. Let file copy job run after backup (as we put schedule as 1)Result: 1. Make sure files are not deleted 2. Go to Restore -> Browse File Copies3. Check the proper destination for "Restore From". If correct cloud location is not shown change to correct location using Change button4. Deletes the old version of the file as we have specified 3 and ran 4th job on the same file. Check the modified file is showing proper version (Shows 3 as version exceeds the one specified in settings)

Case 5: (Negative test)1. Do not modify any file and run the backup job2. Let file copy job run after backup (as we put schedule as 1)Result:1. None of the files are copied to the cloud as there are no changes to the files.

Pre-requisites:1. Create a dataset with multiple files with various file extensions like mpeg1, mp4 and pptx2. Add mpeg1, mp4 and pptx for file copy Source and configure Cloud destination with File Versions as 15 and schedule as 5 thru File Copy Settings tab in Settings (Default Settings)

Case 6: (Default)1. Run the backup and completes successfully 2. Let file copy job run after 5 backups (as schedule is 5)Result: 1. Make sure files are not deleted 2. Go to Restore -> Browse File Copies3. Check the proper destination for "Restore From". If correct cloud location is not shown change to correct location using Change button4. Check all the copied files are shown properly with correct version for every file in brackets (Shows 1 as we have first version)

Pre-requisites:1. Create a dataset with multiple files with various file extensions like mpeg1, mp4 and pptx2. Add mpeg1, mp4 and pptx for file copy Source and configure Cloud destination with File Versions as 15 and schedule as 5 thru File Copy Settings tab in Settings (Default Settings)

Case 7:1. Run the backup and completes successfully 2. Let file copy job run after 5 backups (as schedule is 5)3. Let backup and file copy job run as per schedules in settingsResult: 1. Make sure files are not deleted 2. Go to Restore -> Browse File Copies3. Check the proper destination for "Restore From". If correct cloud location is not shown change to correct location using Change button4. Check all the copied files are shown properly with correct version for every file in brackets.5. Make sure you get all 15 versions

File Copy Delete Source:Run all the above 7 cases by configuring "File Copy Delete Source" as policy type while adding source in File Copy Source and the result is to check "files are getting deleted from source" and verify stub file gets created in place of deleted file from source

Case 8: (Retention Time)1. Configure Retention Time as 1 day in File Copy Settings -> Destination2. Let backup\File Copy jobs run as per the policy set in settings3. Wait for a dayResult:1. Cloud Destination will have data that are copied after file copy job

2. After a day, the data will be deleted from Cloud destination

With Proxy:Run cases 1, 4 and 7 by configuring Proxy also

Troubleshooting:

3. More information and/or errors can be seen in Amazon Logs which can be found under “$D2D_HOME\Bin\CCI\Plugin\Amazon\Log”

4. Collect below logs and share with CA Support team if further help is requried from CA Support team

a. $D2D_HOME\Bin\CCI\Plugin\Amazon\Logb. $D2D_HOME\Bin\CCI\Logc. $D2D_HOME\Logs