Guide de déduplication NetBackup™

Exécution de la migration vers le nouveau serveur de niveau cloud direct MSDP

Avant de poursuivre le processus d'installation et de configuration du nouveau serveur de niveau cloud direct MSDP, il est recommandé de configurer la consignation. Si des problèmes surviennent pendant l'installation, les journaux vous aident à diagnostiquer les erreurs potentielles pendant la migration. Les éléments suivants sont recommandés :

Pour exécuter la migration, accédez à l'invite de commande sur le serveur de niveau cloud direct MSDP et exécutez :

/usr/openv/netbackup/bin/admincmd/nbdecommission -migrate_cloudcatalyst

Sélectionnez le serveur de stockage Cloud Catalyst à migrer et entrez les informations à l'invite de l'utilitaire nbdecommission.

Voici un exemple d'écran visible pendant la migration :

# /usr/openv/netbackup/bin/admincmd/nbdecommission -migrate_cloudcatalyst
MSDP storage server to use for migrated CloudCatalyst:  myserver.test.com

Generating list of configured CloudCatalyst storage servers.
This may take a few minutes for some environments, please wait.

Cloud Storage Server Cloud Bucket CloudCatalyst Server Storage Server Type
1) amazon.com         my-bucket    myserver.test.com   PureDisk_amazon_rawd

Enter line number of CloudCatalyst server to migrate: 1

MSDP KMS encryption is enabled for amazon.com.
Please confirm that CloudCatalyst was configured using 
KMSKeyGroupName amazon.com:testkey

Continue? (y/n) [n]: y

Enter new disk volume name for migrated CloudCatalyst server: newdv
Enter new disk pool name for migrated CloudCatalyst server: newdp
Enter cloud account username or access key:  AAAABBBBBCCCCCDDDDD
Enter cloud account password or 
secret access key: aaaabbbbccccddddeeeeffffggg

You want to migrate amazon.com (bucket my-bucket) to
newmsdpserver.test.com (volume newdv, pool newdp).
Is that correct? (y/n) [n]: y

To fully decommission myserver.test.com after 
CloudCatalyst migration is complete,run the 
following command on the master server:
/usr/openv/netbackup/bin/admincmd/nbdecommission 
-oldserver myserver.test.com

Administrative Pause set for machine myserver.test.com

Migrating CloudCatalyst will include moving the images to server 
newmsdpserver.test.com deleting the old disk pool, storage unit, and 
storage server, deactivating policies that reference the old storage 
unit, and restarting MSDP on server newmsdpserver.test.com.

Before proceeding further, please make sure that no jobs are running on
media server myserver.test.com or media server newmsdpserver.test.com.
This command may not be able to migrate CloudCatalyst
with active jobs on either of those servers.

To avoid potential data loss caused by conflicts between the 
old CloudCatalyst server and the migrated MSDP server, stop the 
NetBackup services on myserver.test.com if they are running.

It is recommended to make one or both of the following changes 
on myserver.test.com to prevent future data loss caused by 
inadvertently starting NetBackup services.
1) Rename /usr/openv/esfs/bin/vxesfsd to /usr/openv/esfs/bin/vxesfsd.off
2) Change "ReadOnly" to "1" in the esfs.json configuration file
See the documentation for more information about esfs.json.

It is also recommended to perform a catalog cleanup and backup prior 
to migration so that the catalog can be restored to its original 
state in the event that migration is not completed.

Continue? (y/n) [n]: y

Successfully cloned storage server: amazon.com to: 
newmsdpserver.test.com_newdv

Storage server newmsdpserver.test.com has been successfully updated

The next step is to list the objects in the cloud and migrate 
the MSDP catalog. The duration of this step depends on how much data 
was uploaded by CloudCatalyst.
It may take several hours or longer, so please be patient.

You may reduce the duration by not migrating the 
CloudCatalyst image sharing information if you are certain that 
you do not use the image sharing feature.

Do you wish to skip migrating CloudCatalyst image 
sharing information? (y/n) [n]:

Jun 24 15:37:11 List CloudCatalyst objects in cloud
Jun 24 15:37:13 List CloudCatalyst objects in cloud
Jun 24 15:37:18 List CloudCatalyst objects in cloud
Jun 24 15:37:26 MSDP catalog migrated successfully from CloudCatalyst

Disk pool newdp has been successfully created with 1 volumes

Moved CloudCatalyst images from myserver.test.com to newmsdpserver.test.com

Disk pool awsdp (PureDisk_amazon_rawd) is referenced by the following 
storage units:
    awsdp-stu

Storage unit awsdp-stu: host myserver.test.com
Deactivating policies using storage unit awsdp-stu
Storage unit awsdp-stu is referenced by policy testaws
Deactivated policy testaws
Deleting storage unit awsdp-stu on host _STU_NO_DEV_HOST_
Deleted storage unit awsdp-stu
Deleted PureDisk_amazon_rawd disk pool awsdp
Deleted PureDisk_amazon_rawd storage server amazon.com

Stopping ocsd and spoold and spad
Checking for PureDisk ContentRouter
spoold (pid  55723) is running...
Checking for PDDE Mini SPA                                 [  OK  ]
spad (pid  55283) is running...
Checking for Open Cloud Storage Daemon                     [  OK  ]
ocsd (pid 55150) is running...
Stopping PureDisk Services
ocsd is stopped

Run MSDP utility to prepare for online checking.  
This may take some time, please wait.

Starting ocsd and spoold and spad
Checking for Open Cloud Storage Daemon
ocsd is stopped
Starting Open Cloud Storage Daemon: ocsd Checking for PDDE Mini SPA
spad is stopped
spad (pid  56856) is running...                            [  OK  ]
Checking for PureDisk ContentRouter
spoold is stopped
spoold (pid  57013) is running...spoold                    [  OK  ]
Starting PureDisk Services
spoold (pid  57013) is running...

Enabling data integrity check.
Starting data integrity check.
Waiting for data integrity check to finish.
Processing the queue.
CloudCatalyst server myserver.test.com has been successfully 
migrated to newmsdpserver.test.com.
To avoid potential data loss caused by conflicts between the 
old CloudCatalyst server and the
migrated MSDP server, stop the NetBackup daemons (or services) 
on myserver.test.com if they are running.

Utilisez la sortie de la commande nbdecommission pour consulter les erreurs. D'autres journaux permettent de surveiller l'activité et de détecter les erreurs potentielles. Ils résident dans le répertoire storage_path/log/. Vous devez surveiller le journal ocsd_storage et les journaux spad et spoold pour détecter d'éventuels problèmes de commande cacontrol.

Si une erreur se produit et que vous pouvez la corriger, la migration peut être reprise à partir de ce point en utilisant l'option start_with, comme indiqué dans la sortie de la commande nbdecommission. En cas de questions concernant l'erreur, contactez le support Veritas avant de reprendre la migration.

Lors de la migration, plusieurs invites s'affichent lorsque la migration est en cours. Les options de ligne de commande permettent de fournir des réponses à ces invites, s'il y a lieu. Veritas recommande d'utiliser les invites interactives, car elles facilitent l'utilisation de la migration et sont moins sources d'erreurs que les options de ligne de commande. Si vous choisissez d'utiliser la ligne de commande, les options sont documentées dans le Guide de référence des commandes NetBackup.

Pendant le processus de migration, la plupart des invites sont explicites et le nombre et le type d'invites peuvent changer. Le nombre et le type d'invites dépendent des facteurs suivants :

La section Tableau : Invites de migration aborde des informations supplémentaires sur certaines de ces invites.

No MSDP storage server found on 
myserver.test.com.

Please create the MSDP storage server 
before running this utility.

Disk pools exist for storage server 
PureDisk myserver.test.com.

CloudCatalyst migration requires a 
new storage server with no 
configured disk pools.

Enter cloud bucket name:

Enter CloudCatalyst server hostname:

Is MSDP KMS encryption enabled 
for amazon.com?
(y/n) [n]:

Enter new disk volume name for 
migrated CloudCatalyst server:

Enter new disk pool name for 
migrated CloudCatalyst server:

Enter cloud account username or 
access key:

Enter cloud account password or 
secret access key: