diff --git a/app.py b/app.py index 9f2c97c..0af0f25 100644 --- a/app.py +++ b/app.py @@ -28,195 +28,6 @@ def compile_status_codes_if_needed(): import pdfplumber import re - PHRASE_TRANSLATIONS = { - "cannot connect on socket": "Não foi possível conectar ao socket", - "client connection refused": "Conexão com o cliente recusada", - "unable to allocate new media for backup, storage unit has none available": "Não foi possível alocar nova mídia para o backup; a unidade de armazenamento não tem nenhuma disponível", - "none of the requested files were backed up": "Nenhum dos arquivos solicitados foi salvo (backup falhou)", - "client/server handshaking failed": "Falha no handshake (aperto de mão) entre cliente e servidor", - "snapshot error encountered": "Erro de snapshot encontrado", - "disk is full": "O disco está cheio", - "file open failed": "Falha ao abrir o arquivo", - "file read failed": "Falha ao ler o arquivo", - "file write failed": "Falha ao gravar o arquivo", - "file close failed": "Falha ao fechar o arquivo", - "user backup failed": "Falha no backup solicitado pelo usuário", - "unimplemented feature": "Recurso não implementado", - "invalid command parameter": "Parâmetro de comando inválido", - "invalid command usage": "Uso de comando inválido", - "request timed out": "Tempo limite da requisição esgotado", - "system call failed": "Falha na chamada de sistema", - "permission denied": "Permissão negada", - "write open failed": "Falha ao abrir para gravação", - "read open failed": "Falha ao abrir para leitura", - "no storage units available": "Nenhuma unidade de armazenamento disponível", - "cannot connect to server": "Não foi possível conectar ao servidor", - "connection timed out": "Tempo limite de conexão esgotado", - "host is unreachable": "Host/Servidor de destino inacessível", - "network is unreachable": "Rede inacessível", - "bad file descriptor": "Descritor de arquivo inválido", - "no space left on device": "Sem espaço livre no dispositivo", - "broken pipe": "Pipe quebrado (conexão interrompida)", - "connection reset by peer": "Conexão redefinida pelo host de destino", - "address already in use": "Endereço já em uso", - "host is down": "O host de destino está desligado ou inacessível", - "too many open files": "Muitos arquivos abertos no sistema", - "file too large": "Arquivo muito grande", - "disk quota exceeded": "Cota de disco excedida", - "stale nfs file handle": "Manipulador de arquivo NFS obsoleto", - "directory not empty": "O diretório não está vazio", - "too many users": "Muitos usuários conectados", - "process limit reached": "Limite de processos atingido", - "operation canceled": "Operação cancelada", - "operation now in progress": "Operação em progresso", - "already in progress": "Já em progresso", - "bad message": "Mensagem inválida", - "identifier removed": "Identificador removido", - "no data available": "Nenhum dado disponível", - "device not configured": "Dispositivo não configurado", - "media not present": "Mídia não inserida", - "write protected": "Mídia protegida contra gravação", - "hardware error": "Erro de hardware", - "driver error": "Erro de driver de dispositivo", - "configuration error": "Erro de configuração", - "license key expired": "Chave de licença expirada", - "invalid license key": "Chave de licença inválida", - "no matching devices found": "Nenhum dispositivo correspondente encontrado", - "device busy": "Dispositivo ocupado", - "drive needs cleaning": "A unidade de fita precisa de limpeza", - "tape alert detected": "Alerta de fita detectado", - "robotic failure": "Falha na robótica (biblioteca de fitas)", - "robotic communication failed": "Falha na comunicação com a robótica", - "robotic device offline": "Dispositivo robótico offline", - "volume not found": "Volume não encontrado", - "volume in use": "Volume em uso", - "volume is read-only": "Volume configurado como somente leitura", - "cannot mount volume": "Não foi possível montar o volume", - "cannot unmount volume": "Não foi possível desmontar o volume", - "drive offline": "Unidade de drive offline", - "drive in use": "Unidade de drive em uso", - "drive not ready": "Unidade de drive não pronta", - "mount failed": "Falha na montagem", - "unmount failed": "Falha na desmontagem", - "positioning failed": "Falha no posicionamento da fita", - "rewind failed": "Falha ao rebobinar", - "unload failed": "Falha ao descarregar a fita", - "format failed": "Falha na formatação", - "database open failed": "Falha ao abrir banco de dados", - "database read failed": "Falha ao ler banco de dados", - "database write failed": "Falha ao gravar banco de dados", - "database close failed": "Falha ao fechar banco de dados", - "active backup already running": "Backup ativo já em execução para este cliente/política", - "the requested operation was successfully completed": "A operação solicitada foi concluída com sucesso", - "the requested operation was partially successful": "A operação solicitada foi parcialmente bem-sucedida", - "valid archive image produced, but no files deleted due to non-fatal problems": "Imagem de arquivo válida produzida, mas nenhum arquivo foi excluído devido a problemas não fatais", - "archive file removal failed": "Falha na remoção do arquivo de arquivamento", - "restore failed completely": "A restauração falhou completamente", - "the archive failed to backup the requested files": "O arquivamento falhou ao salvar os arquivos solicitados", - "unable to determine the status of rbak": "Incapaz de determinar o status do rbak", - "anecessary extension package is not installed or not configured properly": "Um pacote de extensão necessário não está instalado ou configurado corretamente", - "allocation failed": "Falha de alocação de memória", - "system call failed": "Falha na chamada de sistema", - "valid archive image produced but no files deleted due to nonfatal problems": "Imagem de arquivo válida produzida, mas nenhum arquivo foi excluído devido a problemas não fatais", - "can't connect to client": "Não foi possível conectar ao cliente", - "none of the requested connections were successful": "Nenhuma das conexões solicitadas foi bem-sucedida" - } - - SENTENCE_TRANSLATIONS = { - "verify that bpcompatd, vnetd, and private branch exchange (pbx) are running.": "Verifique se os serviços bpcompatd, vnetd e Private Branch Exchange (PBX) estão em execução.", - "verify that the required extension product is installed and configured.": "Verifique se o produto de extensão requerido está instalado e configurado.", - "free up memory by terminating any unneeded processes that consume memory.": "Libere memória física encerrando quaisquer processos desnecessários em execução.", - "check the alllogentries and problems reports to determine the system call that failed.": "Verifique os relatórios de 'All Log Entries' (Todos os Logs) e 'Problems' (Problemas) para determinar qual chamada de sistema falhou.", - "if you want the path for the disk storage unit to reside in the root filesystem:": "Se você deseja que o caminho da unidade de armazenamento de disco resida no sistema de arquivos raiz:", - "check the netbackup problems report for clues on where and why the problem occurred.": "Consulte o relatório de Problemas do NetBackup para obter pistas sobre onde e por que o problema ocorreu.", - "check the netbackup problems report to determine the storage unit that is out of media.": "Verifique o relatório de Problemas do NetBackup para determinar qual unidade de armazenamento está sem mídia.", - "perform the following, as appropriate:": "Execute os seguintes passos conforme apropriado:", - "do the following, as appropriate:": "Execute os seguintes passos conforme apropriado:", - "ensure that the appropriate plug-in is configured in the web ui with the appropriate credentials.": "Certifique-se de que o plug-in correto está configurado no painel Web com as credenciais apropriadas.", - "try to ping the client from the server.": "Tente realizar um teste de ping bidirecional entre o servidor e o cliente.", - "resolve network communication problems.": "Resolva os problemas de comunicação de rede e liberação de portas.", - "no action is needed, unless a database was backed up": "Nenhuma ação é necessária, a menos que um banco de dados tenha sido copiado.", - "a file or a directory path is more than 1023 characters long.": "O caminho de um arquivo ou diretório possui mais de 1023 caracteres.", - "verify that you have permission to delete the files and that": "Verifique se você possui permissões de exclusão de arquivos aplicadas e que o atributo de somente leitura não está ativo.", - "verify that you have read access to the files.": "Verifique se o usuário executor possui permissões de acesso de leitura aos arquivos.", - "check for a new core file to see if rbak quit abnormally.": "Verifique por novos arquivos de dump (core dump) para analisar se o processo rbak terminou de forma anormal.", - "free up space on the disks where netbackup catalogs reside": "Libere espaço livre nos volumes de disco onde residem os catálogos do NetBackup e tente a operação novamente." - } - - WORD_TRANSLATIONS = { - "cannot": "não é possível", "unable": "não foi possível", "failed": "falhou", "failure": "falha", - "connection": "conexão", "connect": "conectar", "refused": "recusada", "error": "erro", "client": "cliente", - "server": "servidor", "socket": "socket", "disk": "disco", "full": "cheio", "file": "arquivo", - "open": "abrir", "read": "ler", "write": "gravar", "close": "fechar", "media": "mídia", - "storage": "armazenamento", "unit": "unidade", "available": "disponível", "none": "nenhum", - "requested": "solicitado", "files": "arquivos", "backed": "salvo", "handshaking": "handshake", - "snapshot": "snapshot", "encountered": "encontrado", "invalid": "inválido", "parameter": "parâmetro", - "command": "comando", "usage": "uso", "timeout": "tempo limite esgotado", "database": "banco de dados", - "volume": "volume", "pool": "pool", "job": "job", "running": "executando", "restore": "restauração", - "delete": "excluir", "removal": "remoção", "user": "usuário", "permission": "permissão", - "denied": "negada", "directory": "diretório", "path": "caminho", "unimplemented": "não implementado", - "feature": "recurso", "empty": "vazio", "exceeded": "excedido", "limit": "limite", "device": "dispositivo", - "busy": "ocupado", "offline": "offline", "online": "online", "network": "rede", "timed": "esgotado", - "out": "fora", "verify": "verifique", "check": "verifique", "ensure": "garanta", "please": "por favor", - "resolving": "resolvendo", "problems": "problemas", "action": "ação", "recommended": "recomendada", - "the": "o", "and": "e", "or": "ou", "for": "para", "with": "com", "by": "por", "of": "de", - "is": "está", "are": "estão", "was": "foi", "were": "foram", "that": "que", "not": "não", "no": "não", - "an": "um", "a": "um", "following": "seguinte", "information": "informação", "applies": "aplica-se", - "only": "apenas", "using": "usando", "contact": "contate", "your": "seu", "increase": "aumentar", - "limit": "limite", "see": "veja", "quit": "sair", "abnormally": "anormalmente", "required": "requerido", - "product": "produto", "installed": "instalado", "configured": "configurado", "free": "liberar", - "memory": "memória", "terminating": "encerrando", "any": "qualquer", "unneeded": "desnecessário", - "processes": "processos", "all": "todos", "entries": "entradas", "reports": "relatórios", - "determine": "determinar", "want": "desejar", "reside": "residir", "root": "raiz", "filesystem": "sistema de arquivos", - "report": "relatório", "clues": "pistas", "where": "onde", "why": "por que", "problem": "problema", - "occurred": "ocorreu", "perform": "executar", "as": "como" - } - - def translate_sentence(text): - if not text: - return "" - clean_txt = text.strip() - lower_txt = clean_txt.lower().replace(" ", " ") - lookup_txt = lower_txt.rstrip(".") - - if lookup_txt in PHRASE_TRANSLATIONS: - res = PHRASE_TRANSLATIONS[lookup_txt] - if lower_txt.endswith("."): - res += "." - return res - if lookup_txt in SENTENCE_TRANSLATIONS: - res = SENTENCE_TRANSLATIONS[lookup_txt] - if lower_txt.endswith("."): - res += "." - return res - - bullet_match = re.match(r'^([■•\-\*]\s*)(.*)', clean_txt) - if bullet_match: - bullet_symbol = bullet_match.group(1) - sub_text = bullet_match.group(2) - return bullet_symbol + translate_sentence(sub_text) - - words = clean_txt.split() - translated_words = [] - for w in words: - w_clean = re.sub(r'[^a-zA-Z\']', '', w).lower() - if w_clean in WORD_TRANSLATIONS: - trans = WORD_TRANSLATIONS[w_clean] - w_trans = w.lower().replace(w_clean, trans) - if w[0].isupper(): - w_trans = w_trans.capitalize() - translated_words.append(w_trans) - else: - translated_words.append(w) - return " ".join(translated_words) - - def translate_text(multiline_text): - if not multiline_text: - return "" - lines = multiline_text.splitlines() - translated_lines = [translate_sentence(line) for line in lines] - return "\n".join(translated_lines) - def clean_spacing(text): if not text: return "" @@ -224,10 +35,10 @@ def compile_status_codes_if_needed(): def get_first_action(action_text): if not action_text: - return "Nenhuma ação recomendada específica encontrada no manual." + return "No specific recommended action found in the manual." lines = [line.strip() for line in action_text.splitlines() if line.strip()] if not lines: - return "Nenhuma ação recomendada específica encontrada no manual." + return "No specific recommended action found in the manual." bullets = ['■', '-', '*', '•'] first_bullet = None for line in lines: @@ -298,21 +109,20 @@ def compile_status_codes_if_needed(): lines = [line.strip() for line in action_full.splitlines() if line.strip()] action_clean = "\n".join(lines) - desc_pt = translate_sentence(desc) - action_clean_pt = translate_text(action_clean) - first_action_eng = get_first_action(action_clean) - first_action_pt = translate_sentence(first_action_eng) + desc_eng = desc + action_clean_eng = action_clean + first_action_eng = get_first_action(action_clean_eng) - if desc_pt and desc_pt[0].islower(): - desc_pt = desc_pt[0].upper() + desc_pt[1:] - if first_action_pt and first_action_pt[0].islower(): - first_action_pt = first_action_pt[0].upper() + first_action_pt[1:] + if desc_eng and desc_eng[0].islower(): + desc_eng = desc_eng[0].upper() + desc_eng[1:] + if first_action_eng and first_action_eng[0].islower(): + first_action_eng = first_action_eng[0].upper() + first_action_eng[1:] parsed[code_num] = { "code": code_num, - "desc": desc_pt, - "first_action": first_action_pt, - "full_action": action_clean_pt + "desc": desc_eng, + "first_action": first_action_eng, + "full_action": action_clean_eng } with open(STATUS_CODES_FILE, "w", encoding="utf-8") as f: diff --git a/nbu_status_codes.json b/nbu_status_codes.json index b855272..a3a41eb 100644 --- a/nbu_status_codes.json +++ b/nbu_status_codes.json @@ -1,3505 +1,3505 @@ { "0": { "code": 0, - "desc": "A operação solicitada foi concluída com sucesso.", - "first_action": "Nenhuma ação é necessária, a menos que um banco de dados tenha sido copiado.", - "full_action": "Nenhuma ação é necessária, a menos que um banco de dados tenha sido copiado.\nthrough um banco de dados extension produto (para example, NetBackup para Oracle ou\nNetBackup para SQL Servidor). In those instances, code 0 means o backup script\n(que started o backup) ran without erro. However, you must verifique other status\ncomo explained in o related NetBackup manual to veja if o banco de dados foi\nsuccessfully salvo up." + "desc": "The requested operation was successfully completed.", + "first_action": "No action is needed, unless a database was backed up", + "full_action": "No action is needed, unless a database was backed up\nthrough a database extension product (for example, NetBackup for Oracle or\nNetBackup for SQL Server). In those instances, code 0 means the backup script\n(that started the backup) ran without error. However, you must check other status\nas explained in the related NetBackup manual to see if the database was\nsuccessfully backed up." }, "1": { "code": 1, - "desc": "A operação solicitada foi parcialmente bem-sucedida.", - "first_action": "Um arquivo ou um diretório caminho está more than 1023 characters long.", - "full_action": "Review o Todos Log Entradas relatório e also o progress\nlog (if there está one).\nO seguinte estão some de o problemas que can appear under status code 1:\n■ Um arquivo ou um diretório caminho está more than 1023 characters long.\nPara NetBackup Snapshot Cliente, o maximum caminho name length está 1000\ncharacters para snapshot backups, não 1023. When o snapshot está created, um\nnew mount point está added to o beginning de o arquivo caminho. If o new mount\npoint plus o original arquivo caminho exceeds 1023 characters, o backup fails com\nstatus code 1. O progress log includes o entry\nERR-Skipping long dir caminho.\n■ You não é possível abrir um arquivo.\nO arquivo may have been locked para some reason.\n■ O seguinte informação aplica-se apenas to UNIX systems:\nNetBackup não é possível get o link name de um arquivo.\n■ O seguinte informação aplica-se apenas to UNIX systems:\nNetBackup não é possível process um sparse arquivo.\n■ Um ler erro que foi encontrado in um arquivo.\n■ Arquivo está de um unknown type, ou may be hidden.\n■ O seguinte informação aplica-se apenas to UNIX systems:\nO lstat system call fails on um arquivo que está eligible to be salvo up. This erro\nmay be um permissão problema.\n■ O seguinte informação aplica-se apenas to UNIX systems:\nUm arquivo não é possível be locked que has mandatory locking enabled.\n■ Um synthetic backup job may terminate com um status code 1 under o seguinte\nconditions:\n■ Não images foram found to synthesize (status code = 607).\n■ TIR informação has been pruned from component images (status code =\n136).\n■ Image format está unsupported (status code = 79).\nO synthetic backup job logs o actual status code in o NetBackup erro\nlog. Refer to o documentation para o corresponding NetBackup erro code\npara o corrective ação to take.\n■ Um BMR job may terminate com status code 1 in o seguinte situation:\nYou save o BMR configuration e it returns um erro even though o child\njobs completed successfully. Para informação, examine o Detailed Status tab\nde o Job Details dialog box, ou o nbjm unified log (originator ID 117).\n■ Um policy que contains multiple backup scripts starts um scheduled backup de um\nUNIX banco de dados extension cliente. If it fails com um status code 1, some de o\nbackup scripts returned um falha status.\n■ OnclientsusingWindowsOpenFileBackups(WOFB)tobackupopenoractive\narquivos, o seguinte may occur:\nVolume snapshots foram não enabled successfully para o backup.\nO seguinte logging messages should appear in o bpbkar32 logs if volume\nsnapshots foram não successfully enabled.\nIfmultistreamedbackupjobsareenabled,logmessagessimilartothefollowing\nappear que indicate volume snapshots foram não enabled para o multistreamed\nbackup job:\n11:05:44.601 AM: [1536.724] <4> tar_backup::V_AddToFI_XBSAObj:\nINF - Volume snapshots não enabled para: D:\\Directory1\nIfmultistreamedbackupswerenotenabled,logmessagessimilartothefollowing\nappear,whichindicatevolumesnapshotswerenotenabledforthenon-streamed\nbackup job:\n1:59:41.229 PM: [2076.2088] <4>\nV_Snapshot::V_Snapshot_CreateSnapshot: INF -\n===============================\n1:59:41.229 PM: [2076.2088] <4>\nV_Snapshot::V_Snapshot_CreateSnapshot: INF - Attempting to\ncreate snapshots para D:\\Directory1\n1:59:41.229 PM: [2076.2088] <4>\nV_Snapshot::V_Snapshot_CreateSnapshot: INF - CREATE request:\nC:\\Program Files\\VERITAS\\NetBackup\\bin\\bpfis create -fim VSP\n\"D:\\ Diretório1\"\n1:59:41.799 PM: [2076.2088] <4>\nV_Snapshot::V_Snapshot_ParseBpfisOutput: INF - Snapshot\ncreation, FIS_ID: 1058813981\n1:59:41.799 PM: [2076.2088] <4>\nV_Snapshot::V_Snapshot_ParseBpfisOutput: INF - Snapshot creation\nEXIT STATUS 11: system call falhou\n1:59:41.799 PM: [2076.2088] <4>\nV_Snapshot::V_Snapshot_CreateSnapshot: INF - Snapshot creation\nfoi não successful\n1:59:41.799 PM: [2076.2088] <4>\nV_Snapshot::V_Snapshot_CreateSnapshot: INF -\n===============================\nIn this case, examine o bpfis logs para erro messages regarding snapshot\ncreation failures. More details estão disponível on o bpfis logs.\nVeja o NetBackup Snapshot Cliente Administrator’s Guide.\nIn o bpfis logs, o seguinte messages may appear when snapshot creation\nfails para Windows Abrir Arquivo Backup:\nFirst message:\n04:01:14.168 [376.2364] <32> onlfi_fi_split: VfMS erro 11; veja\nseguinte messages:\n04:01:14.168 [376.2364] <32> onlfi_fi_split: Fatal method erro\nfoi reported\n04:01:14.168 [376.2364] <32> onlfi_fi_split: vfm_freeze_commit:\nmethod: VSP, type: FIM, function: VSP_make\n04:01:14.168 [376.2364] <32> onlfi_fi_split: VfMS method erro\n3; veja seguinte message:\n04:01:14.168 [376.2364] <32> onlfi_fi_split: snapshot services:\nsnapshot creation falhou: inválido argument(s).\nCause: VSP foi não enabled because o VSP snapshot para o backup did\nnão meet o specified minimum time in o Ocupado Arquivo Wait VSP setting.\nEither aumentar o Ocupado Arquivo Tempo limite esgotado VSP setting (recomendada setting: 300\nseconds ou more) ou submit o backup job when o volume has less activity.\nSecond message:\n04:17:55.571 [1636.3224] <2> onlfi_vfms_logf: snapshot services:\n(null): There foi um unexpected erro while preparing o VSP\nsnapshot transaction. Dumping o parâmetro array to provide\nmore informação: Erro 112 from VSP_Prepare\nCause: VSP foi não enabled para o backup because o cliente para o VSP\nSnapshot Cache arquivos does não have enough liberar disco space.\nLiberar up disco space on o volumes being salvo up.\nThird message:\nIf Microsoft Volume Shadow Copy Service (VSS) está used como o Windows Abrir\nFileBackupsnapshotproviderandsnapshotcreationfails,refertothefollowing:\nEvent Viewer’s Application e System Logs para erro informação.\n■ Um snapshot erro may have ocorreu. Also, you may have some clients que use\no Windows Abrir Arquivo Backup option to back up abrir ou active arquivos. In this\ncase, um log message in o bpbkar32 debug log appears, which indicates que\num snapshot erro ocorreu.\nO seguinte está um example de um snapshot erro:\n8:51:14.569 AM: [1924.2304] <2> tar_base::V_vTarMsgW: ERR -\nSnapshot Erro while reading test.file\nVeja o recomendada actions under status code 156.\n■ O backup de Microsoft Exchange Servidor included multiple databases, but não\ntodos de o databases foram salvo up successfully. Review o job details para\nstatementsaboutthedatabasesthatwerenotbackedup.Inafulloradifferential\nbackup, o transaction logs estão truncated para qualquer databases que estão salvo\nup successfully. O transaction logs can be restored from o backup image\neven if backups de other databases fail. Warning: Qualquer banco de dados para which o\nbackup has falhou está unprotected por this backup.\n■ Um granular-enabled backup de Microsoft Exchange Servidor successfully salvo\nupthedatabases,butthesecondGRTphasetocapturemailbox-levelinformation\nfalhou. Review o job details para o cause de o falha. In um cheio ou um differential\nbackup, transaction logs estão truncated para o databases que estão salvo up\nsuccessfully, regardless de whether o GRT phase succeeds. Qualquer banco de dados\nque está salvo up successfully can be restored from o backup image even if\no GRT phase fails.\n■ DuringVMwarebackup,thevirtualmachinecannotbeunlockedtoallowstorage\nmigration.\nO virtual machine can be restored from this backup. However, you may desejar\nto correct this problema before o next backup.\n■ During VMware backup, o virtual machine snapshot não é possível be deleted ou o\nvirtual machine's disks não é possível be consolidated.\nO virtual machine can be restored from this backup. However, you may desejar\nto correct this problema before o next backup.\n■ During VMware restauração, o virtual machine não é possível be imported into vCloud. In\ntheActivityMonitor,theDetailedStatustabofthejobdetailsincludesmessages\nfrom vCloud Director que indicate o reason para o erro.\nO restored virtual machine está present on o destination vCenter. However,\nyou must manually import it into vCloud.\nUm NetApp NDMP accelerator backup may terminate com um status code 1 com o\nseguinte clock discrepancy warnings para o volumes:\n■ Clock discrepancy detected between NDMP filer e NetBackup\nMídia Servidor.\n■ If this está não expected, por favor executar um backup com Accelerator\nforced rescan enabled.\n■ In order to stop seeing these messages, por favor address\nclock discrepancy.\nOne de o seguinte situations can cause o clock discrepancy issue:\n■ If o NetApp filer e NetBackup NDMP backup host have um time difference\nde more than one hour, um clock discrepancy warning está displayed. This warning\nestá displayed para todos de o volumes.\nVerifique o time difference para o affected volumes e update como requerido. Ou\nuse um mídia servidor que está in o same time zone como o filer.\nNote: Um NTP servidor está o recomendada method to garanta o correct time.\n■ If qualquer SnapMirror (Data Protection) volume has um lag time de more than one\nhour, o warnings appear para que volume.\nUse o seguinte comando to determinar if o volume está um Data Protection\nvolume e if o lag time está greater than one hour:\n■ Para NetApp Clustered Data ONTAP (cDOT):\nsnapmirror show -fields lag-time\n■ Para NetApp 7-mode:\nsnapmirror status\nIf Data Protection volumes estão found on o filer, either:\n■ Browse to e select o volumes para backup in o Backup Selections para\no NetBackup policy.\n■ Use o VOLUME_EXCLUDE_LIST com o ALL_FILESYSTEMS directive\nto exclude o mirror volumes.\nWhen um VMware agentless restauração está performed, o restauração can cause one de o\nseguinte issues:\n■ Falhou to detach o vmdk %s ou o SCSI controller to which %s vmdk está\nattached from o destination VM %s during cleanup.\nManually detach o vmdk ou o controller.\n■ Deletion de temporary VM %s falhou com erro %d.\nManually excluir o specified VM.\n■ Falhou to clean o staging location %s on destination VM %s.\nManually excluir o staging location.\n■ Falhou to attach o temporary vmdk %s to o destination VM %s com erro\n%d.\nMakesurethatthetargetVMhasatleastoneParavirtualcontrollerwithavailable\nLUNs.\n■ Falhou to upload o process rename arquivo to o destination VM %s com erro\n%d.\nMakesurethereissufficientspaceavailableintargetVM.ReviewthebpVMutil\nlog arquivo on o target VM para additional informação on this issue.\n■ Falhou to restauração o selected arquivos e folders.\nReview o tar log to troubleshoot this issue.\n■ FailedtoidentifythenewlyattacheddeviceondestinationVM%s.Onepossible\ncause está que o destination VM usuário credentials have insufficient permissions.\nIt está recomendada destination VM usuário credentials have raiz ou administrative\nprivileges.\nNetBackup did não find one ou more SQL Servidor databases que foram specified in\no intelligent group in o SQL Servidor policy. Um message like o seguinte está\nincluded in o erro log.\n08:31:05.561 [5736.15584] <2> debuglog: <16> bphdb do_script: ERR -\nexit status: 5465 Could não find banco de dados objects during backup.\n08:31:05.561 [5736.15584] <2> debuglog: <16> bphdb do_script: INF -\nPartial success status so switch status from <5465> to <1>\nExecutar one de o seguinte actions to resolve o issue:\n■ Review o intelligent group in o policy e adjust o query. If não ação está\ntaken, qualquer databases que NetBackup can’t find during um future backup estão\nskipped e o Banco de dados state para these databases está changed to \"Deleted\".\n■ Ifyouwantcontinuedaccesstothedatabase,youcanuseNetBackuptorecover\nit." + "desc": "The requested operation was partially successful.", + "first_action": "A file or a directory path is more than 1023 characters long.", + "full_action": "Review the All Log Entries report and also the progress\nlog (if there is one).\nThe following are some of the problems that can appear under status code 1:\n■ A file or a directory path is more than 1023 characters long.\nFor NetBackup Snapshot Client, the maximum path name length is 1000\ncharacters for snapshot backups, not 1023. When the snapshot is created, a\nnew mount point is added to the beginning of the file path. If the new mount\npoint plus the original file path exceeds 1023 characters, the backup fails with\nstatus code 1. The progress log includes the entry\nERR-Skipping long dir path.\n■ You cannot open a file.\nThe file may have been locked for some reason.\n■ The following information applies only to UNIX systems:\nNetBackup cannot get the link name of a file.\n■ The following information applies only to UNIX systems:\nNetBackup cannot process a sparse file.\n■ A read error that was encountered in a file.\n■ File is of an unknown type, or may be hidden.\n■ The following information applies only to UNIX systems:\nThe lstat system call fails on a file that is eligible to be backed up. This error\nmay be a permission problem.\n■ The following information applies only to UNIX systems:\nA file cannot be locked that has mandatory locking enabled.\n■ A synthetic backup job may terminate with a status code 1 under the following\nconditions:\n■ No images were found to synthesize (status code = 607).\n■ TIR information has been pruned from component images (status code =\n136).\n■ Image format is unsupported (status code = 79).\nThe synthetic backup job logs the actual status code in the NetBackup error\nlog. Refer to the documentation for the corresponding NetBackup error code\nfor the corrective action to take.\n■ A BMR job may terminate with status code 1 in the following situation:\nYou save the BMR configuration and it returns an error even though the child\njobs completed successfully. For information, examine the Detailed Status tab\nof the Job Details dialog box, or the nbjm unified log (originator ID 117).\n■ A policy that contains multiple backup scripts starts a scheduled backup of a\nUNIX database extension client. If it fails with a status code 1, some of the\nbackup scripts returned a failure status.\n■ OnclientsusingWindowsOpenFileBackups(WOFB)tobackupopenoractive\nfiles, the following may occur:\nVolume snapshots were not enabled successfully for the backup.\nThe following logging messages should appear in the bpbkar32 logs if volume\nsnapshots were not successfully enabled.\nIfmultistreamedbackupjobsareenabled,logmessagessimilartothefollowing\nappear that indicate volume snapshots were not enabled for the multistreamed\nbackup job:\n11:05:44.601 AM: [1536.724] <4> tar_backup::V_AddToFI_XBSAObj:\nINF - Volume snapshots not enabled for: D:\\Directory1\nIfmultistreamedbackupswerenotenabled,logmessagessimilartothefollowing\nappear,whichindicatevolumesnapshotswerenotenabledforthenon-streamed\nbackup job:\n1:59:41.229 PM: [2076.2088] <4>\nV_Snapshot::V_Snapshot_CreateSnapshot: INF -\n===============================\n1:59:41.229 PM: [2076.2088] <4>\nV_Snapshot::V_Snapshot_CreateSnapshot: INF - Attempting to\ncreate snapshots for D:\\Directory1\n1:59:41.229 PM: [2076.2088] <4>\nV_Snapshot::V_Snapshot_CreateSnapshot: INF - CREATE request:\nC:\\Program Files\\VERITAS\\NetBackup\\bin\\bpfis create -fim VSP\n\"D:\\ Directory1\"\n1:59:41.799 PM: [2076.2088] <4>\nV_Snapshot::V_Snapshot_ParseBpfisOutput: INF - Snapshot\ncreation, FIS_ID: 1058813981\n1:59:41.799 PM: [2076.2088] <4>\nV_Snapshot::V_Snapshot_ParseBpfisOutput: INF - Snapshot creation\nEXIT STATUS 11: system call failed\n1:59:41.799 PM: [2076.2088] <4>\nV_Snapshot::V_Snapshot_CreateSnapshot: INF - Snapshot creation\nwas not successful\n1:59:41.799 PM: [2076.2088] <4>\nV_Snapshot::V_Snapshot_CreateSnapshot: INF -\n===============================\nIn this case, examine the bpfis logs for error messages regarding snapshot\ncreation failures. More details are available on the bpfis logs.\nSee the NetBackup Snapshot Client Administrator’s Guide.\nIn the bpfis logs, the following messages may appear when snapshot creation\nfails for Windows Open File Backup:\nFirst message:\n04:01:14.168 [376.2364] <32> onlfi_fi_split: VfMS error 11; see\nfollowing messages:\n04:01:14.168 [376.2364] <32> onlfi_fi_split: Fatal method error\nwas reported\n04:01:14.168 [376.2364] <32> onlfi_fi_split: vfm_freeze_commit:\nmethod: VSP, type: FIM, function: VSP_make\n04:01:14.168 [376.2364] <32> onlfi_fi_split: VfMS method error\n3; see following message:\n04:01:14.168 [376.2364] <32> onlfi_fi_split: snapshot services:\nsnapshot creation failed: invalid argument(s).\nCause: VSP was not enabled because the VSP snapshot for the backup did\nnot meet the specified minimum time in the Busy File Wait VSP setting.\nEither increase the Busy File Timeout VSP setting (recommended setting: 300\nseconds or more) or submit the backup job when the volume has less activity.\nSecond message:\n04:17:55.571 [1636.3224] <2> onlfi_vfms_logf: snapshot services:\n(null): There was an unexpected error while preparing the VSP\nsnapshot transaction. Dumping the parameter array to provide\nmore information: Error 112 from VSP_Prepare\nCause: VSP was not enabled for the backup because the client for the VSP\nSnapshot Cache files does not have enough free disk space.\nFree up disk space on the volumes being backed up.\nThird message:\nIf Microsoft Volume Shadow Copy Service (VSS) is used as the Windows Open\nFileBackupsnapshotproviderandsnapshotcreationfails,refertothefollowing:\nEvent Viewer’s Application and System Logs for error information.\n■ A snapshot error may have occurred. Also, you may have some clients that use\nthe Windows Open File Backup option to back up open or active files. In this\ncase, a log message in the bpbkar32 debug log appears, which indicates that\na snapshot error occurred.\nThe following is an example of a snapshot error:\n8:51:14.569 AM: [1924.2304] <2> tar_base::V_vTarMsgW: ERR -\nSnapshot Error while reading test.file\nSee the recommended actions under status code 156.\n■ The backup of Microsoft Exchange Server included multiple databases, but not\nall of the databases were backed up successfully. Review the job details for\nstatementsaboutthedatabasesthatwerenotbackedup.Inafulloradifferential\nbackup, the transaction logs are truncated for any databases that are backed\nup successfully. The transaction logs can be restored from the backup image\neven if backups of other databases fail. Warning: Any database for which the\nbackup has failed is unprotected by this backup.\n■ A granular-enabled backup of Microsoft Exchange Server successfully backed\nupthedatabases,butthesecondGRTphasetocapturemailbox-levelinformation\nfailed. Review the job details for the cause of the failure. In a full or a differential\nbackup, transaction logs are truncated for the databases that are backed up\nsuccessfully, regardless of whether the GRT phase succeeds. Any database\nthat is backed up successfully can be restored from the backup image even if\nthe GRT phase fails.\n■ DuringVMwarebackup,thevirtualmachinecannotbeunlockedtoallowstorage\nmigration.\nThe virtual machine can be restored from this backup. However, you may want\nto correct this problem before the next backup.\n■ During VMware backup, the virtual machine snapshot cannot be deleted or the\nvirtual machine's disks cannot be consolidated.\nThe virtual machine can be restored from this backup. However, you may want\nto correct this problem before the next backup.\n■ During VMware restore, the virtual machine cannot be imported into vCloud. In\ntheActivityMonitor,theDetailedStatustabofthejobdetailsincludesmessages\nfrom vCloud Director that indicate the reason for the error.\nThe restored virtual machine is present on the destination vCenter. However,\nyou must manually import it into vCloud.\nA NetApp NDMP accelerator backup may terminate with a status code 1 with the\nfollowing clock discrepancy warnings for the volumes:\n■ Clock discrepancy detected between NDMP filer and NetBackup\nMedia Server.\n■ If this is not expected, please perform a backup with Accelerator\nforced rescan enabled.\n■ In order to stop seeing these messages, please address\nclock discrepancy.\nOne of the following situations can cause the clock discrepancy issue:\n■ If the NetApp filer and NetBackup NDMP backup host have a time difference\nof more than one hour, a clock discrepancy warning is displayed. This warning\nis displayed for all of the volumes.\nCheck the time difference for the affected volumes and update as required. Or\nuse a media server that is in the same time zone as the filer.\nNote: An NTP server is the recommended method to ensure the correct time.\n■ If any SnapMirror (Data Protection) volume has a lag time of more than one\nhour, the warnings appear for that volume.\nUse the following command to determine if the volume is a Data Protection\nvolume and if the lag time is greater than one hour:\n■ For NetApp Clustered Data ONTAP (cDOT):\nsnapmirror show -fields lag-time\n■ For NetApp 7-mode:\nsnapmirror status\nIf Data Protection volumes are found on the filer, either:\n■ Browse to and select the volumes for backup in the Backup Selections for\nthe NetBackup policy.\n■ Use the VOLUME_EXCLUDE_LIST with the ALL_FILESYSTEMS directive\nto exclude the mirror volumes.\nWhen a VMware agentless restore is performed, the restore can cause one of the\nfollowing issues:\n■ Failed to detach the vmdk %s or the SCSI controller to which %s vmdk is\nattached from the destination VM %s during cleanup.\nManually detach the vmdk or the controller.\n■ Deletion of temporary VM %s failed with error %d.\nManually delete the specified VM.\n■ Failed to clean the staging location %s on destination VM %s.\nManually delete the staging location.\n■ Failed to attach the temporary vmdk %s to the destination VM %s with error\n%d.\nMakesurethatthetargetVMhasatleastoneParavirtualcontrollerwithavailable\nLUNs.\n■ Failed to upload the process rename file to the destination VM %s with error\n%d.\nMakesurethereissufficientspaceavailableintargetVM.ReviewthebpVMutil\nlog file on the target VM for additional information on this issue.\n■ Failed to restore the selected files and folders.\nReview the tar log to troubleshoot this issue.\n■ FailedtoidentifythenewlyattacheddeviceondestinationVM%s.Onepossible\ncause is that the destination VM user credentials have insufficient permissions.\nIt is recommended destination VM user credentials have root or administrative\nprivileges.\nNetBackup did not find one or more SQL Server databases that were specified in\nthe intelligent group in the SQL Server policy. A message like the following is\nincluded in the error log.\n08:31:05.561 [5736.15584] <2> debuglog: <16> bphdb do_script: ERR -\nexit status: 5465 Could not find database objects during backup.\n08:31:05.561 [5736.15584] <2> debuglog: <16> bphdb do_script: INF -\nPartial success status so switch status from <5465> to <1>\nPerform one of the following actions to resolve the issue:\n■ Review the intelligent group in the policy and adjust the query. If no action is\ntaken, any databases that NetBackup can’t find during a future backup are\nskipped and the Database state for these databases is changed to \"Deleted\".\n■ Ifyouwantcontinuedaccesstothedatabase,youcanuseNetBackuptorecover\nit." }, "2": { "code": 2, - "desc": "Nenhum dos arquivos solicitados foi salvo (backup falhou)", - "first_action": "O seguinte informação aplica-se apenas to Lotus Notes:", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ O seguinte informação aplica-se apenas to Lotus Notes:\nThiserroroccurswhenarchivestyleloggingisnotenabledfortheLotusDomino\nservidor on UNIX. It also occurs when another backup de o transaction logs está\nin progress.\n■ Veja o troubleshooting topic de o appropriate guide para um description de\ntroubleshooting tools:\n■ NetBackup para Microsoft SQL Servidor Administrator’s Guide\n■ NetBackup para Lotus Notes Administrator’s Guide\n■ NetBackup para Enterprise Vault Agent Administrator’s Guide" + "desc": "None of the requested files were backed up", + "first_action": "The following information applies only to Lotus Notes:", + "full_action": "Do the following, as appropriate:\n■ The following information applies only to Lotus Notes:\nThiserroroccurswhenarchivestyleloggingisnotenabledfortheLotusDomino\nserver on UNIX. It also occurs when another backup of the transaction logs is\nin progress.\n■ See the troubleshooting topic of the appropriate guide for a description of\ntroubleshooting tools:\n■ NetBackup for Microsoft SQL Server Administrator’s Guide\n■ NetBackup for Lotus Notes Administrator’s Guide\n■ NetBackup for Enterprise Vault Agent Administrator’s Guide" }, "3": { "code": 3, - "desc": "Imagem de arquivo válida produzida, mas nenhum arquivo foi excluído devido a problemas não fatais", - "first_action": "Examine o progress log ou status de o archive on o", - "full_action": "Examine o progress log ou status de o archive on o\ncliente to determinar if you need to retry o archive after you correct o problema. If\no problema está não serious e o arquivos foram salvo up, you can manually excluir\no arquivos. To verifique o arquivos que foram salvo up, use o NetBackup client-user\ninterface in restauração mode e browse o arquivos in o archive.\nUm possible cause para arquivos não being deleted está que you do não have o necessary\npermissions. NetBackup não é possível excluir arquivos unless you estão o usuário que owns o\narquivos, um superuser on UNIX, ou um administrator on Windows." + "desc": "Valid archive image produced, but no files deleted due to non-fatal problems", + "first_action": "Examine the progress log or status of the archive on the", + "full_action": "Examine the progress log or status of the archive on the\nclient to determine if you need to retry the archive after you correct the problem. If\nthe problem is not serious and the files were backed up, you can manually delete\nthe files. To verify the files that were backed up, use the NetBackup client-user\ninterface in restore mode and browse the files in the archive.\nA possible cause for files not being deleted is that you do not have the necessary\npermissions. NetBackup cannot delete files unless you are the user that owns the\nfiles, a superuser on UNIX, or an administrator on Windows." }, "4": { "code": 4, - "desc": "Falha na remoção do arquivo de arquivamento", + "desc": "Archive file removal failed", "first_action": "Verifythatyouhavepermissiontodeletethefilesandthat", - "full_action": "Verifythatyouhavepermissiontodeletethefilesandthat\no read-only flag está não set para o arquivos. On UNIX clients, verifique que you have gravar\npermissiontothedirectoriesthatcontainthefiles.Sincethebackupwassuccessful,\nyou can excluir o arquivos que foram salvo up. (If you do não have o necessary\npermissions, have o system administrator excluir o arquivos.)" + "full_action": "Verifythatyouhavepermissiontodeletethefilesandthat\nthe read-only flag is not set for the files. On UNIX clients, verify that you have write\npermissiontothedirectoriesthatcontainthefiles.Sincethebackupwassuccessful,\nyou can delete the files that were backed up. (If you do not have the necessary\npermissions, have the system administrator delete the files.)" }, "5": { "code": 5, - "desc": "A restauração falhou completamente.", - "first_action": "If usando Azure, contate seu cloud provider to aumentar o threshold limite.", - "full_action": "To correct this issue, try o seguinte solutions como\nappropriate:\n■ If usando Azure, contate seu cloud provider to aumentar o threshold limite.\n■ If you try to restauração um replicated copy de EC2, create um new key-pair in o\ndestination region. O new key-pair must be consistent com o key-pair in o\nsource region.\n■ Sourcesnapshotmustberetainedonthecloudprovideruntiltheimageexpiration\nduration está selected in o protection plan.\nWhen um VMware agentless restauração está performed, o restauração can cause one de o\nseguinte issues:\n■ Falhou to upload recovery tool on destination VM %s com erro %d.\nMake sure there está sufficient space ou permissions disponível at o staging\nlocation.\n■ Falhou to extract o recovery tool on o destination VM.\nConfirmthereissufficientspaceavailableatthestaginglocation%sinthetarget\nVM.\nWhen um granular restauração fails, executar o seguinte:\n■ Para lvm e ldm disks granular restauração, upgrade o Snapshot Manager to\nversion 10.0.\n■ Garanta que restauração destination caminho está accessible com sufficient privileges e\ndisco space.\n■ O arquivo wise restauração erro e warning relatório está disponível on source host\n(Windows ou Linux) como follows:\n■ Windows host caminho:\nC:\\ProgramData\\Veritas\\CloudPoint\\restore\\/\n■ Linux host caminho: /root/veritas//\nThese locations provide o details de o disco wise restored arquivo status.\nPara example:\nD#.log -> Existing log arquivo which shows higher level falha\nD#-Error.log ->This arquivo está generated apenas when um erro\n(at least one) está displayed during o copy process.\nThis arquivo logs o Actual Exception / OS exception.\nD#-Warning.log -> This arquivo está generated apenas when um warning message\n(at least one) está displayed during o restauração task." + "desc": "Restore failed completely.", + "first_action": "If using Azure, contact your cloud provider to increase the threshold limit.", + "full_action": "To correct this issue, try the following solutions as\nappropriate:\n■ If using Azure, contact your cloud provider to increase the threshold limit.\n■ If you try to restore a replicated copy of EC2, create a new key-pair in the\ndestination region. The new key-pair must be consistent with the key-pair in the\nsource region.\n■ Sourcesnapshotmustberetainedonthecloudprovideruntiltheimageexpiration\nduration is selected in the protection plan.\nWhen a VMware agentless restore is performed, the restore can cause one of the\nfollowing issues:\n■ Failed to upload recovery tool on destination VM %s with error %d.\nMake sure there is sufficient space or permissions available at the staging\nlocation.\n■ Failed to extract the recovery tool on the destination VM.\nConfirmthereissufficientspaceavailableatthestaginglocation%sinthetarget\nVM.\nWhen a granular restore fails, perform the following:\n■ For lvm and ldm disks granular restore, upgrade the Snapshot Manager to\nversion 10.0.\n■ Ensure that restore destination path is accessible with sufficient privileges and\ndisk space.\n■ The file wise restore error and warning report is available on source host\n(Windows or Linux) as follows:\n■ Windows host path:\nC:\\ProgramData\\Veritas\\CloudPoint\\restore\\/\n■ Linux host path: /root/veritas//\nThese locations provide the details of the disk wise restored file status.\nFor example:\nD#.log -> Existing log file which shows higher level failure\nD#-Error.log ->This file is generated only when an error\n(at least one) is displayed during the copy process.\nThis file logs the Actual Exception / OS exception.\nD#-Warning.log -> This file is generated only when a warning message\n(at least one) is displayed during the restore task." }, "6": { "code": 6, - "desc": "Falha no backup solicitado pelo usuário", - "first_action": "Garanta que o appropriate plug-in está configurado in o web UI com o", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Garanta que o appropriate plug-in está configurado in o web UI com o\nappropriate credentials. If o credentials estão changed, garanta que they estão\nupdated from o web UI.\n■ Detach o disco from o target instance.\nTable 1-1 RestorefailedduetoSSLcertificateissuesorconnectivityissues\nbetween Snapshot Manager e Azure ou Azure Stack\nMessage Recomendada ação\nNão foi possível to retrieve o certificate CRL. If you CopythelatestCRLintotheECA_CRL_PATH\nhaveconfiguredtheECA_CRL_PATH,ensure caminho ou garanta o CRL distribution point\nque valid CRLs estão present at o location. URL, from o respective host certificate, está\nCheckiftheCRLURLisaccessiblefromthe accessible from o Snapshot Manager.\nSnapshot Manager.\nTheAzureorAzureStackservers’certificate Contactyoursecurityadministratortoensure\nestá revoked. Garanta que o certificates estão que o servidor presents um valid certificate.\nnão revoked por certificate authority.\n■ If o certificate foi revoked in erro,\nreissue um certificate para o host.\n■ Ifthecertificatewasrevokedasintended,\num attempted security breach may have\nocorreu.\nTable 1-1 RestorefailedduetoSSLcertificateissuesorconnectivityissues\nbetween Snapshot Manager e Azure ou Azure Stack\n(continued)\nMessage Recomendada ação\nThecertificaterevocationlist(CRL)isexpired. Garanta que o latest CRL’s estão uploaded at\nGaranta que o ECA_CRL_PATH está updated o ECA_CRL_PATH caminho.\ncom o latest CRL.\nYou can update o NetBackup CRL cache\nmanuallybyusingthefollowingcommandon\nSnapshot Manager:\ndocker exec -i flexsnap-certauth bash -c\n'/usr/openv/pdde/pdopensource\n/nbcertcmdtool/nbcertcmdtool -atLibPath\n/usr/openv/pdde/pdopensource/nbcertcmdtool\n-updateCRLCache'\nThecertificaterevocationlist(CRL)isnotyet Review seu Snapshot Manager's system\nvalid. time ou provide um valid CRL.\nO date de last update de o certificate ChecktheCRLusingtheopensslcommand\nrevocation list (CRL) está não in um valid format. ou contate seu Security Administrator.\nO date de next update de o certificate ChecktheCRLusingtheopensslcommand\nrevocation list (CRL) está não in um valid format. ou contate seu Security Administrator.\nO Azure ou Azure Stack servidor certificate Reviewthecertificateandensurethevalidity\nisexpired.Ensurethattheserverhasavalid de it por checking o certificate to make sure\ncertificate. que o end date está valid.\nVerifique if o Snapshot Manager's clock está in\nsync com o specified servidor. Correct o\ntime on o host, if necessary, e rerun o\noperation. If o problema continues, save todos\nde o erro log informação e contate\nCohesity Technical Support.\nO Azure ou Azure stack servers certificate Verifique if o Snapshot Manager’s clock está in\nestá não yet valid. sync com o specified servidor. Correct o\ntime on o host, if necessary, e rerun o\noperation. If o problema continues, save todos\nde o erro log informação e contate\nCohesity Technical Support.\nTable 1-1 RestorefailedduetoSSLcertificateissuesorconnectivityissues\nbetween Snapshot Manager e Azure ou Azure Stack\n(continued)\nMessage Recomendada ação\nUnabletofindthepublicrootandintermediate Garanta que o certificate arquivo está configurado\ncertificates de o Azure Stack servidor. correctly at o ECA_TRUST_STORE_PATH\nlocated in o bp.conf arquivo on o Snapshot\nManager.\nRerun o operation. If o problema persists,\nsave todos de o erro log informação e\ncontate Cohesity Technical Support.\nFalhou to load o Certificate Revocation List Garanta que o valid CRL arquivo está configurado\n(CRL)fromCRLcache.Ensurethatthevalid ontheSnapshotManagerforAzureorAzure\nCRL arquivo está configurado on o Snapshot Stack por o ECA_CRL_PATH.\nManager para Azure ou Azure Stack por\nECA_CRL_PATH.\nFailedtoconnecttotheAzureorAzureStack Garanta rede connectivity between o\nserver.Ensurenetworkconnectivitybetween Snapshot Manager e o Azure ou Azure\nSnapshot Manager e o Azure ou Azure Stack servidor.\nStack servidor.\nNão é possível use o specified SSL cipher para Contate Cohesity Technical Support.\nAzure ou Azure Stack servidor.\nOperation falhou com cURL erro: Rerun o operation. If o problema persists,\nsave todos de o erro log informação e\ncontate Cohesity Technical Support." + "desc": "User backup failed", + "first_action": "Ensure that the appropriate plug-in is configured in the web UI with the", + "full_action": "Do the following, as appropriate:\n■ Ensure that the appropriate plug-in is configured in the web UI with the\nappropriate credentials. If the credentials are changed, ensure that they are\nupdated from the web UI.\n■ Detach the disk from the target instance.\nTable 1-1 RestorefailedduetoSSLcertificateissuesorconnectivityissues\nbetween Snapshot Manager and Azure or Azure Stack\nMessage Recommended action\nUnable to retrieve the certificate CRL. If you CopythelatestCRLintotheECA_CRL_PATH\nhaveconfiguredtheECA_CRL_PATH,ensure path or ensure the CRL distribution point\nthat valid CRLs are present at the location. URL, from the respective host certificate, is\nCheckiftheCRLURLisaccessiblefromthe accessible from the Snapshot Manager.\nSnapshot Manager.\nTheAzureorAzureStackservers’certificate Contactyoursecurityadministratortoensure\nis revoked. Ensure that the certificates are that the server presents a valid certificate.\nnot revoked by certificate authority.\n■ If the certificate was revoked in error,\nreissue a certificate for the host.\n■ Ifthecertificatewasrevokedasintended,\nan attempted security breach may have\noccurred.\nTable 1-1 RestorefailedduetoSSLcertificateissuesorconnectivityissues\nbetween Snapshot Manager and Azure or Azure Stack\n(continued)\nMessage Recommended action\nThecertificaterevocationlist(CRL)isexpired. Ensure that the latest CRL’s are uploaded at\nEnsure that the ECA_CRL_PATH is updated the ECA_CRL_PATH path.\nwith the latest CRL.\nYou can update the NetBackup CRL cache\nmanuallybyusingthefollowingcommandon\nSnapshot Manager:\ndocker exec -i flexsnap-certauth bash -c\n'/usr/openv/pdde/pdopensource\n/nbcertcmdtool/nbcertcmdtool -atLibPath\n/usr/openv/pdde/pdopensource/nbcertcmdtool\n-updateCRLCache'\nThecertificaterevocationlist(CRL)isnotyet Review your Snapshot Manager's system\nvalid. time or provide a valid CRL.\nThe date of last update of the certificate ChecktheCRLusingtheopensslcommand\nrevocation list (CRL) is not in a valid format. or contact your Security Administrator.\nThe date of next update of the certificate ChecktheCRLusingtheopensslcommand\nrevocation list (CRL) is not in a valid format. or contact your Security Administrator.\nThe Azure or Azure Stack server certificate Reviewthecertificateandensurethevalidity\nisexpired.Ensurethattheserverhasavalid of it by checking the certificate to make sure\ncertificate. that the end date is valid.\nCheck if the Snapshot Manager's clock is in\nsync with the specified server. Correct the\ntime on the host, if necessary, and rerun the\noperation. If the problem continues, save all\nof the error log information and contact\nCohesity Technical Support.\nThe Azure or Azure stack servers certificate Check if the Snapshot Manager’s clock is in\nis not yet valid. sync with the specified server. Correct the\ntime on the host, if necessary, and rerun the\noperation. If the problem continues, save all\nof the error log information and contact\nCohesity Technical Support.\nTable 1-1 RestorefailedduetoSSLcertificateissuesorconnectivityissues\nbetween Snapshot Manager and Azure or Azure Stack\n(continued)\nMessage Recommended action\nUnabletofindthepublicrootandintermediate Ensure that the certificate file is configured\ncertificates of the Azure Stack server. correctly at the ECA_TRUST_STORE_PATH\nlocated in the bp.conf file on the Snapshot\nManager.\nRerun the operation. If the problem persists,\nsave all of the error log information and\ncontact Cohesity Technical Support.\nFailed to load the Certificate Revocation List Ensure that the valid CRL file is configured\n(CRL)fromCRLcache.Ensurethatthevalid ontheSnapshotManagerforAzureorAzure\nCRL file is configured on the Snapshot Stack by the ECA_CRL_PATH.\nManager for Azure or Azure Stack by\nECA_CRL_PATH.\nFailedtoconnecttotheAzureorAzureStack Ensure network connectivity between the\nserver.Ensurenetworkconnectivitybetween Snapshot Manager and the Azure or Azure\nSnapshot Manager and the Azure or Azure Stack server.\nStack server.\nCannot use the specified SSL cipher for Contact Cohesity Technical Support.\nAzure or Azure Stack server.\nOperation failed with cURL error: Rerun the operation. If the problem persists,\nsave all of the error log information and\ncontact Cohesity Technical Support." }, "7": { "code": 7, - "desc": "O archive falhou to back up o solicitado arquivos", - "first_action": "Verifique que you have ler access to o arquivos. Verifique o", - "full_action": "Verifique que you have ler access to o arquivos. Verifique o\nprogress log ou o status on o cliente para messages on por que o archive falhou.\nCorrect problemas e retry o archive.\nOn Windows clients, verifique que o account used to start o NetBackup services\nhas ler access to o arquivos." + "desc": "The archive failed to back up the requested files", + "first_action": "Verify that you have read access to the files. Check the", + "full_action": "Verify that you have read access to the files. Check the\nprogress log or the status on the client for messages on why the archive failed.\nCorrect problems and retry the archive.\nOn Windows clients, verify that the account used to start the NetBackup services\nhas read access to the files." }, "8": { "code": 8, - "desc": "Incapaz de determinar o status do rbak", - "first_action": "Verifique para um new core arquivo to veja if rbak sair anormalmente.", - "full_action": "Verifique para um new core arquivo to veja if rbak sair anormalmente.\nVerifique o ps output to veja if rbak está hung. If so, cancel it e try again. Verifique o\nprogress log para qualquer unusual messages from rbak." + "desc": "Unable to determine the status of rbak", + "first_action": "Check for a new core file to see if rbak quit abnormally.", + "full_action": "Check for a new core file to see if rbak quit abnormally.\nCheck the ps output to see if rbak is hung. If so, cancel it and try again. Check the\nprogress log for any unusual messages from rbak." }, "9": { "code": 9, "desc": "Anecessaryextensionpackageisnotinstalledornotconfiguredproperly", - "first_action": "Verifique que o requerido extension produto está instalado e", - "full_action": "Verifique que o requerido extension produto está instalado e\nconfigurado." + "first_action": "Verify that the required extension product is installed and", + "full_action": "Verify that the required extension product is installed and\nconfigured." }, "10": { "code": 10, - "desc": "Falha de alocação de memória", + "desc": "Allocation failed", "first_action": "Freeupmemorybyterminatinganyunneededprocesses", - "full_action": "Freeupmemorybyterminatinganyunneededprocesses\nque consume memória. Add more swap space ou physical memória." + "full_action": "Freeupmemorybyterminatinganyunneededprocesses\nthat consume memory. Add more swap space or physical memory." }, "11": { "code": 11, - "desc": "System call falhou NetBackup status codes 101 NetBackup status codes", - "first_action": "Verifique o Todos Log Entradas e Problemas relatórios to determinar o system call", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Verifique o Todos Log Entradas e Problemas relatórios to determinar o system call\nque falhou e other informação about o erro.\n■ nbjm e nbproxy return status code 11 when um exception está processed, such\ncomo when nbproxy obtains policy ou configuration informação. Examine o nbjm\nunified log (originator ID 117) ou o nbproxy legacy log para more detail on o\ncause de o erro.\n■ Um frequent cause está que o server’s arquivo system está cheio. Para example, you may\nveja um message similar to o seguinte in o Problemas relatório ou bpdbm debug\nlog:\n06/27/95 01:04:00 romb romb db_FLISTsend falhou: system call\nfalhou (11)\n06/27/95 01:04:01 romb romb mídia manager terminated por parent\nprocess\n06/27/95 01:05:15 romb romb backup de cliente romb que exited com\nstatus 11 (system call falhou)\nOn UNIX systems, run um df comando on o /usr/openv/netbackup/db\ndiretório.\nIf o df comando does não reveal o problema, verifique o bpdbm debug logs\nou do um grep para o message\nFalha na chamada de sistema\nIn relevant arquivos under o diretório /usr/openv/netbackup/db/error/\nOnWindowssystems,verifythatthediskpartitionwhereNetBackupisinstalled\nhas enough room.\n■ Verifique que o system está não executando fora de virtual memória. If virtual memória está\no problema, turn off unused applications ou aumentar o amount de virtual\nmemória.\nToincreasevirtualmemoryonWindows,dothefollowingintheorderpresented:\n■ Display o Control Panel.\n■ Double-click System.\n■ On o Performance tab, set Virtual Memória to um higher value.\n■ O seguinte informação aplica-se apenas to UNIX clients:\nVerifique para um semaphore problema. This erro may occur because o system\ndoes não have enough allocated semaphores. It está most commonly seen on\nSolaris servers when um RDBMS está also executando.\nO symptoms de o problema vary. In some cases, erro messages in o\nNetBackuplogindicateabackupfailureduetoanerrorinsemaphoreoperation.\nAnother symptom está o inability de o NetBackup dispositivo manager daemon,\nltid, to acquire um needed semaphore.\nSystem requirements vary; thus, não definite recommendations can be made.\nOne customer executando NetBackup e ORACLE on um Solaris servidor made o\nseguinte changes to o /etc/system arquivo e then restarted o system (boot\n-r). O changes foram adequate.\nset semsys:seminfo_semmni=300\nset semsys:seminfo_semmns=300\nset semsys:seminfo_semmsl=300\nset semsys:seminfo_semmnu=600\nSet these attributes to um value great enough to provide resources to todos\napplications on seu system.\n■ Examine other debug logs ou o progress log ou status on o cliente. Examine\no nbjm unified log (originator ID 117) para more detail on o cause de o erro.\nIn case de NetApp armazenamento, garanta que o seguinte configurations estão done in\nNetApp system manager:\n■ Enable Make snapshot (.snapshot) diretório visible option.\n■ Disable Automatically excluir older Snapshot copies." + "desc": "System call failed NetBackup status codes 101 NetBackup status codes", + "first_action": "Check the All Log Entries and Problems reports to determine the system call", + "full_action": "Do the following, as appropriate:\n■ Check the All Log Entries and Problems reports to determine the system call\nthat failed and other information about the error.\n■ nbjm and nbproxy return status code 11 when an exception is processed, such\nas when nbproxy obtains policy or configuration information. Examine the nbjm\nunified log (originator ID 117) or the nbproxy legacy log for more detail on the\ncause of the error.\n■ A frequent cause is that the server’s file system is full. For example, you may\nsee a message similar to the following in the Problems report or bpdbm debug\nlog:\n06/27/95 01:04:00 romb romb db_FLISTsend failed: system call\nfailed (11)\n06/27/95 01:04:01 romb romb media manager terminated by parent\nprocess\n06/27/95 01:05:15 romb romb backup of client romb that exited with\nstatus 11 (system call failed)\nOn UNIX systems, run a df command on the /usr/openv/netbackup/db\ndirectory.\nIf the df command does not reveal the problem, check the bpdbm debug logs\nor do a grep for the message\nsystem call failed\nIn relevant files under the directory /usr/openv/netbackup/db/error/\nOnWindowssystems,verifythatthediskpartitionwhereNetBackupisinstalled\nhas enough room.\n■ Verify that the system is not running out of virtual memory. If virtual memory is\nthe problem, turn off unused applications or increase the amount of virtual\nmemory.\nToincreasevirtualmemoryonWindows,dothefollowingintheorderpresented:\n■ Display the Control Panel.\n■ Double-click System.\n■ On the Performance tab, set Virtual Memory to a higher value.\n■ The following information applies only to UNIX clients:\nCheck for a semaphore problem. This error may occur because the system\ndoes not have enough allocated semaphores. It is most commonly seen on\nSolaris servers when an RDBMS is also running.\nThe symptoms of the problem vary. In some cases, error messages in the\nNetBackuplogindicateabackupfailureduetoanerrorinsemaphoreoperation.\nAnother symptom is the inability of the NetBackup device manager daemon,\nltid, to acquire a needed semaphore.\nSystem requirements vary; thus, no definite recommendations can be made.\nOne customer running NetBackup and ORACLE on a Solaris server made the\nfollowing changes to the /etc/system file and then restarted the system (boot\n-r). The changes were adequate.\nset semsys:seminfo_semmni=300\nset semsys:seminfo_semmns=300\nset semsys:seminfo_semmsl=300\nset semsys:seminfo_semmnu=600\nSet these attributes to a value great enough to provide resources to all\napplications on your system.\n■ Examine other debug logs or the progress log or status on the client. Examine\nthe nbjm unified log (originator ID 117) for more detail on the cause of the error.\nIn case of NetApp storage, ensure that the following configurations are done in\nNetApp system manager:\n■ Enable Make snapshot (.snapshot) directory visible option.\n■ Disable Automatically delete older Snapshot copies." }, "12": { "code": 12, - "desc": "Falha ao abrir o arquivo", - "first_action": "If you desejar o caminho para o disco armazenamento unidade to residir in o raiz arquivo system:", - "full_action": "Do o seguinte como appropriate:\n■ If you desejar o caminho para o disco armazenamento unidade to residir in o raiz arquivo system:\nAbrir o Change Armazenamento Unidade dialog box in o NetBackup Administration\nConsole e select o verifique box: This diretório can exist on o raiz arquivo\nsystem ou system disco.\n■ If o specified caminho para o disco armazenamento unidade está não in o raiz arquivo system ou\nsystem dispositivo, verifique que o caminho está in um mounted arquivo system.\n■ If o specified caminho para o disco armazenamento unidade está in o raiz arquivo system ou system\ndispositivo but does não need to be there, use o Change Armazenamento Unidade dialog box\nto specify um different (non-root) caminho in um mounted arquivo system.\n■ Verifique o NetBackup Problemas relatório. Try to determinar o arquivo e por que o\nerro ocorreu. Um possible cause está um permissão problema com o arquivo. Para\ndetailedtroubleshootinginformation,createadebuglogdirectoryfortheprocess\nque returned this status code. Then, retry o operation e verifique o resulting\ndebug log.\n■ Para NetBackup Lotus Notes, point-in-time restauração jobs may fail com um status 12.\nThese jobs estão initiated from o master servidor por usando either o NetBackup\nAdministration Console ou o Backup, Archive, e Restauração interface. Their\nfalha está reported in o NetBackup tar log arquivo. (para Windows, this arquivo está located\nin o install_path\\NetBackup\\logs\\tar folder. Para UNIX, it está located in o\n/usr/openv/netbackup/logs/tar folder.) If o install caminho de o NetBackup\nmaster servidor está different from o install caminho de o NetBackup cliente, o\nautomatic restauração de Lotus transaction log extents during recovery de o Lotus\nbanco de dados fail. Note que o Activity Monitor shows um status 0 (successful). O\ntarlogontheclient,however,showssuccessfortherestorebutafailure(status\n12) para o Lotus banco de dados recovery.\nExecutar o restauração job from o Backup, Archive, e Restauração interface on o\nNetBackup cliente.\n■ Para NetBackup Snapshot Cliente, status code 12 may appear in o\n/usr/openv/netbackup/logs/bptm ou bpdm log com o seguinte:\ntpc_read_config falhou: não é possível abrir arquivo\n/usr/openv/volmgr/database/3pc.conf\nThis status code may indicate que o policy está configurado com either o\nNetBackup mídia servidor ou o Third-party Copy Dispositivo como o off-host backup\nmethod, but o 3pc.conf arquivo does não exist ou está in o wrong location.\nInstructions estão disponível on how to create o 3pc.conf arquivo.\nVeja o NetBackup Snapshot Cliente Administrator’s Guide.\n■ Para um FlashBackup policy, if o CACHE= entry follows o source data entry,\no backup fails com status code 12. Messages such como o seguinte appear in\no /usr/openv/netbackup/logs/bpbkar logs on o cliente:\n09:55:33.941 [6092] <16> bpfsmap: ERR - open_snapdisk: NetBackup\nsnapshot enable falhou erro 3\n09:55:33.942 [6092] <32> bpfsmap: FTL - bpfsmap: can't abrir\nsnapshot disco /dev/rdsk/c4t1d0s3 errno 0\n09:55:33.950 [6092] <16> bpbkar Exit: ERR - bpbkar FATAL exit\nstatus = 12: arquivo abrir falhou\n09:55:33.956 [6092] <4> bpbkar Exit: INF - EXIT STATUS 12: arquivo\nabrir falhou\n09:55:33.957 [6092] <2> bpbkar Exit: INF - Fechar de stdout\ncomplete\nChangetheorderofthebackupselectionslistsothattheCACHEentryprecedes\no source data entry. (o source data entry specifies o raw partition que\ncontains o arquivo system to be salvo up.)" + "desc": "File open failed", + "first_action": "If you want the path for the disk storage unit to reside in the root file system:", + "full_action": "Do the following as appropriate:\n■ If you want the path for the disk storage unit to reside in the root file system:\nOpen the Change Storage Unit dialog box in the NetBackup Administration\nConsole and select the check box: This directory can exist on the root file\nsystem or system disk.\n■ If the specified path for the disk storage unit is not in the root file system or\nsystem device, verify that the path is in a mounted file system.\n■ If the specified path for the disk storage unit is in the root file system or system\ndevice but does not need to be there, use the Change Storage Unit dialog box\nto specify a different (non-root) path in a mounted file system.\n■ Check the NetBackup Problems report. Try to determine the file and why the\nerror occurred. A possible cause is a permission problem with the file. For\ndetailedtroubleshootinginformation,createadebuglogdirectoryfortheprocess\nthat returned this status code. Then, retry the operation and check the resulting\ndebug log.\n■ For NetBackup Lotus Notes, point-in-time restore jobs may fail with a status 12.\nThese jobs are initiated from the master server by using either the NetBackup\nAdministration Console or the Backup, Archive, and Restore interface. Their\nfailure is reported in the NetBackup tar log file. (For Windows, this file is located\nin the install_path\\NetBackup\\logs\\tar folder. For UNIX, it is located in the\n/usr/openv/netbackup/logs/tar folder.) If the install path of the NetBackup\nmaster server is different from the install path of the NetBackup client, the\nautomatic restore of Lotus transaction log extents during recovery of the Lotus\ndatabase fail. Note that the Activity Monitor shows a status 0 (successful). The\ntarlogontheclient,however,showssuccessfortherestorebutafailure(status\n12) for the Lotus database recovery.\nPerform the restore job from the Backup, Archive, and Restore interface on the\nNetBackup client.\n■ For NetBackup Snapshot Client, status code 12 may appear in the\n/usr/openv/netbackup/logs/bptm or bpdm log with the following:\ntpc_read_config failed: cannot open file\n/usr/openv/volmgr/database/3pc.conf\nThis status code may indicate that the policy is configured with either the\nNetBackup media server or the Third-party Copy Device as the off-host backup\nmethod, but the 3pc.conf file does not exist or is in the wrong location.\nInstructions are available on how to create the 3pc.conf file.\nSee the NetBackup Snapshot Client Administrator’s Guide.\n■ For a FlashBackup policy, if the CACHE= entry follows the source data entry,\nthe backup fails with status code 12. Messages such as the following appear in\nthe /usr/openv/netbackup/logs/bpbkar logs on the client:\n09:55:33.941 [6092] <16> bpfsmap: ERR - open_snapdisk: NetBackup\nsnapshot enable failed error 3\n09:55:33.942 [6092] <32> bpfsmap: FTL - bpfsmap: can't open\nsnapshot disk /dev/rdsk/c4t1d0s3 errno 0\n09:55:33.950 [6092] <16> bpbkar Exit: ERR - bpbkar FATAL exit\nstatus = 12: file open failed\n09:55:33.956 [6092] <4> bpbkar Exit: INF - EXIT STATUS 12: file\nopen failed\n09:55:33.957 [6092] <2> bpbkar Exit: INF - Close of stdout\ncomplete\nChangetheorderofthebackupselectionslistsothattheCACHEentryprecedes\nthe source data entry. (The source data entry specifies the raw partition that\ncontains the file system to be backed up.)" }, "13": { "code": 13, - "desc": "Falha ao ler o arquivo", - "first_action": "Verifique o NetBackup Problemas relatório para pistas on onde e por que o problema", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Verifique o NetBackup Problemas relatório para pistas on onde e por que o problema\nocorreu.\n■ Verifique que rede communication works properly.\nVeja \"resolvendo rede communication problemas\" in o NetBackup\nTroubleshooting Guide.\n■ Para um FlashBackup cliente, verifique o /var/adm/messages log para errors like o\nseguinte:\nMar 24 01:35:58 bison unix: WARNING: sn_alloccache: cache\n/dev/rdsk/c0t2d0s3 cheio - todos snaps usando this cache estão now\nunusable\nThis erro indicates que o cache partition está não large enough. If possible,\naumentar o size de o cache partition. Ou, if multiple backups use o same\ncache, reduce o number de concurrent backups. To reduce o number,\nreschedule some de them ou reschedule o entire backup to um time when o\narquivo system está less active.\n■ Para detailed troubleshooting informação, create um debug log diretório para o\nprocess que returned this status code. Then retry o operation e verifique o\nresulting debug log.\n■ Garanta que o latest service packs para todos products e components (SQL\nServidor, Exchange, Notes, etc.) have been instalado.\n■ Garanta que todos o rede hardware (NICs, hubs, switches, routers, etc.)\nthroughout o environment estão set to cheio duplex, não half duplex.\n■ Verifique o seguinte items regarding o NICs in seu system:\n■ Upgrade to o latest NIC drivers throughout o system.\n■ Garanta que todos NICs estão set to cheio duplex, não half duplex.\nVeja Troubleshooting rede interface card performance in o NetBackup\nTroubleshooting Guide.\n■ Aumentar o tempo limite esgotado settings on o NIC.\n■ If NIC teaming está implemented, deactivate para testing purposes.\n■ Replace o NIC itself on o affected cliente ou servidor.\n■ Para NetBackup Snapshot Cliente, status code 13 may appear in o\n/usr/openv/netbackup/logs/bpbkar log.\nO log can indicate o seguinte:\n■ ThefilestobackupresideonanIDEdriveasopposedtoSCSI.Theoff-host\nbackup method foi set to either NetBackup mídia servidor ou Third-Party\nCopy Dispositivo. If you use off-host backup, o disco que contains o cliente\narquivos must be um SCSI ou Fibre Channel dispositivo.\nIf o disco está um IDE drive, you may veja o seguinte in o /usr/openv/\nnetbackup/logs/bpfis log:\nget_disk_info: FTL - /var/tmp/caa026fEU disk_inquiry falhou.\nErrno = 25: Inappropriate ioctl para dispositivo\nThefollowinglistingmayappearinthe/usr/openv/netbackup/logs/bpbkar\nlog:\nbpbkar: INF - Processing /var\nbpbkar: ERR - get_disk_info() falhou, status 13\nbpbkar: ERR - tpc_get_disk_info() falhou: err 13\nbpbkar: ERR - bpbkar FATAL exit status = 13: arquivo ler falhou\nbpbkar: INF - EXIT STATUS 13: arquivo ler falhou\n■ Thefilestobackupexistonafilesystemthatisnotmounted.Thefilesystem\nque está specified como o snapshot source must be mounted. If o snapshot\nsource está não mounted but o mount point está present, NetBackup may try to\ntake um snapshot de o diretório preceding o diretório que foi specified\ncomo o snapshot source.\n■ Para o NetBackup mídia servidor method, you may need to aumentar o\ncliente ler tempo limite esgotado value. In some environments, NetBackup may require\nmore ler time than o default value allows. If o cliente ler tempo limite esgotado está\ninsufficient, o backup may fail e que causes this erro.\nTo aumentar o cliente ler tempo limite esgotado para todos clients, in o NetBackup\nAdministration Console, go to Host Properties > Master Servers >\ndouble-click o master servidor, then go to Properties > Timeouts. Then,\naumentar o cliente ler tempo limite esgotado.\n■ On Windows, refresh o Backup, Archive, e Restauração cliente console e\nretry o restauração. This ação refreshes o arquivo list que está displayed in o cliente\nconsole e passes o correct informação about o selected arquivos.\n■ To prevent timeouts in o VMware VDDK que cause simultaneous hotadd\nbackups from o same VMware backup host to fail, do one de o seguinte:\n■ Reduce o number de hotadd backups que run simultaneously.\n■ Aumentar o client-read tempo limite esgotado on o mídia servidor como appropriate (15\nminutes ou more):\nIn o NetBackup Administration Console, click NetBackup Management\n> Host Properties > Double-click on mídia servidor > Timeouts > Cliente\nler tempo limite esgotado." + "desc": "File read failed", + "first_action": "Check the NetBackup Problems report for clues on where and why the problem", + "full_action": "Do the following, as appropriate:\n■ Check the NetBackup Problems report for clues on where and why the problem\noccurred.\n■ Check that network communication works properly.\nSee \"Resolving network communication problems\" in the NetBackup\nTroubleshooting Guide.\n■ For a FlashBackup client, check the /var/adm/messages log for errors like the\nfollowing:\nMar 24 01:35:58 bison unix: WARNING: sn_alloccache: cache\n/dev/rdsk/c0t2d0s3 full - all snaps using this cache are now\nunusable\nThis error indicates that the cache partition is not large enough. If possible,\nincrease the size of the cache partition. Or, if multiple backups use the same\ncache, reduce the number of concurrent backups. To reduce the number,\nreschedule some of them or reschedule the entire backup to a time when the\nfile system is less active.\n■ For detailed troubleshooting information, create a debug log directory for the\nprocess that returned this status code. Then retry the operation and check the\nresulting debug log.\n■ Ensure that the latest service packs for all products and components (SQL\nServer, Exchange, Notes, etc.) have been installed.\n■ Ensure that all the network hardware (NICs, hubs, switches, routers, etc.)\nthroughout the environment are set to full duplex, not half duplex.\n■ Check the following items regarding the NICs in your system:\n■ Upgrade to the latest NIC drivers throughout the system.\n■ Ensure that all NICs are set to full duplex, not half duplex.\nSee Troubleshooting network interface card performance in the NetBackup\nTroubleshooting Guide.\n■ Increase the timeout settings on the NIC.\n■ If NIC teaming is implemented, deactivate for testing purposes.\n■ Replace the NIC itself on the affected client or server.\n■ For NetBackup Snapshot Client, status code 13 may appear in the\n/usr/openv/netbackup/logs/bpbkar log.\nThe log can indicate the following:\n■ ThefilestobackupresideonanIDEdriveasopposedtoSCSI.Theoff-host\nbackup method was set to either NetBackup media server or Third-Party\nCopy Device. If you use off-host backup, the disk that contains the client\nfiles must be a SCSI or Fibre Channel device.\nIf the disk is an IDE drive, you may see the following in the /usr/openv/\nnetbackup/logs/bpfis log:\nget_disk_info: FTL - /var/tmp/caa026fEU disk_inquiry failed.\nErrno = 25: Inappropriate ioctl for device\nThefollowinglistingmayappearinthe/usr/openv/netbackup/logs/bpbkar\nlog:\nbpbkar: INF - Processing /var\nbpbkar: ERR - get_disk_info() failed, status 13\nbpbkar: ERR - tpc_get_disk_info() failed: err 13\nbpbkar: ERR - bpbkar FATAL exit status = 13: file read failed\nbpbkar: INF - EXIT STATUS 13: file read failed\n■ Thefilestobackupexistonafilesystemthatisnotmounted.Thefilesystem\nthat is specified as the snapshot source must be mounted. If the snapshot\nsource is not mounted but the mount point is present, NetBackup may try to\ntake a snapshot of the directory preceding the directory that was specified\nas the snapshot source.\n■ For the NetBackup media server method, you may need to increase the\nclient read timeout value. In some environments, NetBackup may require\nmore read time than the default value allows. If the client read timeout is\ninsufficient, the backup may fail and that causes this error.\nTo increase the client read timeout for all clients, in the NetBackup\nAdministration Console, go to Host Properties > Master Servers >\ndouble-click the master server, then go to Properties > Timeouts. Then,\nincrease the client read timeout.\n■ On Windows, refresh the Backup, Archive, and Restore client console and\nretry the restore. This action refreshes the file list that is displayed in the client\nconsole and passes the correct information about the selected files.\n■ To prevent timeouts in the VMware VDDK that cause simultaneous hotadd\nbackups from the same VMware backup host to fail, do one of the following:\n■ Reduce the number of hotadd backups that run simultaneously.\n■ Increase the client-read timeout on the media server as appropriate (15\nminutes or more):\nIn the NetBackup Administration Console, click NetBackup Management\n> Host Properties > Double-click on media server > Timeouts > Client\nread timeout." }, "14": { "code": 14, - "desc": "Falha ao gravar o arquivo", - "first_action": "Verifique o NetBackup Problemas relatório para pistas on onde e por que o problema", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Verifique o NetBackup Problemas relatório para pistas on onde e por que o problema\nocorreu.\n■ Para detailed troubleshooting informação, create um debug log diretório para o\nprocess que returned this status code. Then retry o operation e verifique o\nresulting debug log.\n■ Make sure que o routers, bridges, e other rede devices estão todos at \"cheio\"\nduplex.\nVeja Troubleshooting rede interface card performance in o NetBackup\nTroubleshooting Guide.\n■ Use um \"sniffer\" program to determinar o number de packets being rejected ou\nre-requested.\n■ On Windows systems, o cliente bpbkar log may contain um 10054 Conexão\nReset Erro (usually indicates um hardware erro). Somewhere between o\nNetBackup cliente e servidor, o conexão foi reset. When NetBackup\nreceives this erro, it não é possível continue o backup. This erro has been attributed\nto o seguinte:\n■ Um hiccup in o rede.\n■ Um bad rede interface card on um NetBackup cliente.\n■ Um bad rede interface card on o NetBackup servidor.\n■ Faulty routers.\n■ Qualquer other applications que interfere com NetBackup connections.\n■ O erro occurs while you use o NetBackup Java interface: O application\nservidor (bpjava processos) para o NetBackup Java interface probably ran fora\nde disco space in o arquivo system containing\n/usr/openv/netbackup/logs/user_ops.Theapplicationserverwritestemporary\narquivos into directories in o /user_ops diretório. Try clearing up disco space in\no arquivo system." + "desc": "File write failed", + "first_action": "Check the NetBackup Problems report for clues on where and why the problem", + "full_action": "Do the following, as appropriate:\n■ Check the NetBackup Problems report for clues on where and why the problem\noccurred.\n■ For detailed troubleshooting information, create a debug log directory for the\nprocess that returned this status code. Then retry the operation and check the\nresulting debug log.\n■ Make sure that the routers, bridges, and other network devices are all at \"full\"\nduplex.\nSee Troubleshooting network interface card performance in the NetBackup\nTroubleshooting Guide.\n■ Use a \"sniffer\" program to determine the number of packets being rejected or\nre-requested.\n■ On Windows systems, the client bpbkar log may contain a 10054 Connection\nReset Error (usually indicates a hardware error). Somewhere between the\nNetBackup client and server, the connection was reset. When NetBackup\nreceives this error, it cannot continue the backup. This error has been attributed\nto the following:\n■ A hiccup in the network.\n■ A bad network interface card on a NetBackup client.\n■ A bad network interface card on the NetBackup server.\n■ Faulty routers.\n■ Any other applications that interfere with NetBackup connections.\n■ The error occurs while you use the NetBackup Java interface: The application\nserver (bpjava processes) for the NetBackup Java interface probably ran out\nof disk space in the file system containing\n/usr/openv/netbackup/logs/user_ops.Theapplicationserverwritestemporary\nfiles into directories in the /user_ops directory. Try clearing up disk space in\nthe file system." }, "15": { "code": 15, - "desc": "Falha ao fechar o arquivo", + "desc": "File close failed", "first_action": "ChecktheNetBackupProblemsreportforcluesonwhere", - "full_action": "ChecktheNetBackupProblemsreportforcluesonwhere\ne por que o problema ocorreu. Para detailed troubleshooting informação, create um\ndebug log diretório para o process que returned this status code. Then retry o\noperation e verifique o resulting debug log." + "full_action": "ChecktheNetBackupProblemsreportforcluesonwhere\nand why the problem occurred. For detailed troubleshooting information, create a\ndebug log directory for the process that returned this status code. Then retry the\noperation and check the resulting debug log." }, "16": { "code": 16, - "desc": "Não implementado recurso NetBackup status codes 109 NetBackup status codes", - "first_action": "Save todos de o erro informação e contate Cohesity", - "full_action": "Save todos de o erro informação e contate Cohesity\nTechnical Support." + "desc": "Unimplemented feature NetBackup status codes 109 NetBackup status codes", + "first_action": "Save all of the error information and contact Cohesity", + "full_action": "Save all of the error information and contact Cohesity\nTechnical Support." }, "17": { "code": 17, - "desc": "Pipe abrir falhou", - "first_action": "Save todos de o erro informação e contate Cohesity", - "full_action": "Save todos de o erro informação e contate Cohesity\nTechnical Support." + "desc": "Pipe open failed", + "first_action": "Save all of the error information and contact Cohesity", + "full_action": "Save all of the error information and contact Cohesity\nTechnical Support." }, "18": { "code": 18, - "desc": "Pipe fechar falhou", - "first_action": "Verifique o NetBackup Problemas relatório para pistas on por que", - "full_action": "Verifique o NetBackup Problemas relatório para pistas on por que\no falha ocorreu. Para detailed troubleshooting informação, create um debug log\ndiretório para o process que returned this status code. Then retry o operation\ne verifique o resulting debug log." + "desc": "Pipe close failed", + "first_action": "Check the NetBackup Problems report for clues on why", + "full_action": "Check the NetBackup Problems report for clues on why\nthe failure occurred. For detailed troubleshooting information, create a debug log\ndirectory for the process that returned this status code. Then retry the operation\nand check the resulting debug log." }, "19": { "code": 19, - "desc": "Getservbyname falhou", - "first_action": "Verifique o NetBackup Problemas relatório para pistas on por que o falha ocorreu.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Verifique o NetBackup Problemas relatório para pistas on por que o falha ocorreu.\n■ On um UNIX ou Linux system, verifique que /etc/services e NIS services map\n(if applicable) have entradas para o NetBackup services: bpcd, bpdbm, e bprd.\n■ On um Windows system, verifique que o\n%SystemRoot%\\system32\\drivers\\etc\\servicesfileshowsthecorrectentries\npara o NetBackup Internet processos: bpcd, bpdbm, e bprd.\nGaranta que o seguinte numbers match o settings in o services arquivo: O\nNetBackup Cliente Service Port number e NetBackup Request Service Port\nnumber on o Rede tab in o NetBackup Cliente Properties dialog box.\nTo display this dialog box, start o Backup, Archive, e Restauração interface e\nclick NetBackup Cliente Properties on o Arquivo menu. O values on o\nNetworktabarewrittentotheservicesfilewhentheNetBackupClientservice\nstarts.\nSee\"Verifyinghostnameandserviceentries\"intheNetBackupTroubleshooting\nGuide.\n■ Verifique o level de rede activity. Um overloaded rede can cause this erro.\n■ If these actions do não reveal o problema, create um debug log diretório para o\nprocess que returned this status code. Then retry o operation e verifique o\nresulting debug log." + "desc": "Getservbyname failed", + "first_action": "Check the NetBackup Problems report for clues on why the failure occurred.", + "full_action": "Do the following, as appropriate:\n■ Check the NetBackup Problems report for clues on why the failure occurred.\n■ On a UNIX or Linux system, check that /etc/services and NIS services map\n(if applicable) have entries for the NetBackup services: bpcd, bpdbm, and bprd.\n■ On a Windows system, verify that the\n%SystemRoot%\\system32\\drivers\\etc\\servicesfileshowsthecorrectentries\nfor the NetBackup Internet processes: bpcd, bpdbm, and bprd.\nEnsure that the following numbers match the settings in the services file: The\nNetBackup Client Service Port number and NetBackup Request Service Port\nnumber on the Network tab in the NetBackup Client Properties dialog box.\nTo display this dialog box, start the Backup, Archive, and Restore interface and\nclick NetBackup Client Properties on the File menu. The values on the\nNetworktabarewrittentotheservicesfilewhentheNetBackupClientservice\nstarts.\nSee\"Verifyinghostnameandserviceentries\"intheNetBackupTroubleshooting\nGuide.\n■ Check the level of network activity. An overloaded network can cause this error.\n■ If these actions do not reveal the problem, create a debug log directory for the\nprocess that returned this status code. Then retry the operation and check the\nresulting debug log." }, "20": { "code": 20, - "desc": "Parâmetro de comando inválido", - "first_action": "Review o NetBackup Problemas relatório para pistas.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Review o NetBackup Problemas relatório para pistas.\n■ If o erro occurs when you run um comando on o comando line, verifique que\no parameters estão valid.\n■ This status code may occur if nbjm passes parameters but does não have um\nrequerido parâmetro. Review o nbjm unified logs (originator ID 117) para o list\nde parameters que foram passed.\n■ O seguinte informação pertains to NetBackup Snapshot Cliente.\n■ If o seguinte appears in o /usr/openv/netbackup/logs/bptm log como\nenabled on um third-party copy backup, multiplexing foi enabled on um\nthird-party copy backup:\nbptm: não é possível executar Third-Party-Copy para multiplexed backups\nsend_brm_msg: Erro 20\nbptm: EXITING com status 20\nO Third-party Copy Dispositivo off-host backup method está incompatible com\nmultiplexing (o writing de two ou more concurrent backup jobs to o same\narmazenamento dispositivo). You must disable multiplexing para qualquer third-party copy\nbackups. If multiplexing está enabled, o backup fails.\n■ O mídia servidor may não have o correct 3pc.conf arquivo entry para o cliente\ndisco que está needed para o backup.\nO seguinte appears in o /usr/openv/netbackup/logs/bpbkar log:\n14:45:00.983 [15773] <4> bpmap_mm_get_devid: GET_DEVICE_INDEX 1\nEMC:SYMMETRIX:601092014000\n14:45:00.986 [15773] <4> bpbkar child_send_keepalives: keepalive\nchild started, pid = 15822\n14:47:02.029 [15773] <4> bpmap_mm_get_devid: keepalive child:\n15822 killed\n14:47:02.030 [15773] <4> bpmap_mm_get_devid: DEVICE_INDEX -1\n14:47:02.031 [15773] <16> bpmap_send_extend: ERR - can't obtain\ndispositivo id string EMC:SYMMETRIX:601092014000\n14:47:33.167 [15773] <16> bpbkar Exit: ERR - bpbkar FATAL exit\nstatus = 227: não entity foi found\n14:47:33.167 [15773] <4> bpbkar Exit: INF - EXIT STATUS 227: não\nentity foi found\n14:47:33.168 [15773] <2> bpbkar Exit: INF - Fechar de stdout\ncomplete\nThis shows que um particular dispositivo não é possível be found in o 3pc.conf arquivo on\nthemediaserver(14:47:02.031 [15773] <16> bpmap_send_extend: ERR\n- can't obtain dispositivo id string EMC:SYMMETRIX:601092014000).\nO problema está one de o seguinte:\n■ The3pc.conffileonthemediaserverisoutdated.Recreatethe3pc.conf\narquivo.\n■ O mídia servidor está não on o same Fibre Channel rede como o\nthird-partycopydeviceandclientdisk.Asaresult,the3pc.conffiledoes\nnão have um correct entry para o cliente disco. Run o bptpcinfo comando\ncom o -x client_name option; this option adds o cliente disco to o\n3pc.conf arquivo. Para each disco que está added to o arquivo por means de\nbptpcinfo -x client_name, you may need to add o device’s World\nWide Name (WWN=).\nVeja o NetBackup Snapshot Cliente Configuration online document.\nVeja Snapshot Cliente Assistance in o NetBackup Snapshot Cliente\nAdministrator’s Guide.\n■ O HP VxFS snapshot mechanism requires um dedicated cache partition para\neach snapshot. Um verifique está made in o mount table to make sure que o\ncache partition está não already in use. If o cache partition está already in use,\nstatus code 20 occurs.\nReviewthe/usr/openv/netbackup/logs/bpbkarlogforamessagesimilar\nto o seguinte:\nbpfsmap: FTL - bpfsmap: snapshot cache already in use,\n/dev/arrayvg/vol4c\nbpbkar Exit: ERR - bpbkar FATAL exit status = 20: inválido\ncomando parâmetro\nbpbkar Exit: INF - EXIT STATUS 20: inválido comando parâmetro\nIf o snapshot cache partition está already in use, do one de o seguinte: Set\nup seu policy schedules to run at different times ou use different cache\npartitions para each backup.\nIf o Allow multiple data streams option está enabled, each stream must\nhave its own dedicated cache partition.\n■ Compare o NetBackup version level on o servidor to o version level on o\nclients por doing o seguinte:\n■ On UNIX ou Linux NetBackup servers e clients, review o\n/usr/openv/netbackup/bin/version arquivo.\n■ On Windows NetBackup servers, review o\ninstall_path\\NetBackup\\version.txt arquivo ou o About NetBackup item\non o Help menu.\n■ On Microsoft Windows clients, review o About NetBackup item on o\nHelp menu.\n■ If um Java interface displays o erro, tell them how to enable o debug print\nmanager in o Java startup arquivo. Retry e compare o parameters que\nforam logged on o Java log com o parameters listed in o commands\nuso statement.\n■ FortheBackupMediaServeroptionforVMwarebackups,thestorageunitthat\nestá specified in o policy must be unique to seu mídia servers. If o armazenamento\nunitisalsoavailableonanothermediaserver,thesnapshotjobcannotsucceed.\n■ If you protect NAS arrays usando VSO FIM snapshot method, executar off-host\nbackup usando um alternate cliente.\n■ ForBigDatapolicies,themediaserverandthebackuphostsmustusethesame\nNetBackup version.\n■ If these actions do não reveal o problema, create um debug log diretório para o\nprocessthatreturnedthisstatuscode(iftheprocessuseslegacylogging).Then\nretry o operation e review o resulting log." + "desc": "Invalid command parameter", + "first_action": "Review the NetBackup Problems report for clues.", + "full_action": "Do the following, as appropriate:\n■ Review the NetBackup Problems report for clues.\n■ If the error occurs when you run a command on the command line, verify that\nthe parameters are valid.\n■ This status code may occur if nbjm passes parameters but does not have a\nrequired parameter. Review the nbjm unified logs (originator ID 117) for the list\nof parameters that were passed.\n■ The following information pertains to NetBackup Snapshot Client.\n■ If the following appears in the /usr/openv/netbackup/logs/bptm log as\nenabled on a third-party copy backup, multiplexing was enabled on a\nthird-party copy backup:\nbptm: cannot perform Third-Party-Copy for multiplexed backups\nsend_brm_msg: ERROR 20\nbptm: EXITING with status 20\nThe Third-party Copy Device off-host backup method is incompatible with\nmultiplexing (the writing of two or more concurrent backup jobs to the same\nstorage device). You must disable multiplexing for any third-party copy\nbackups. If multiplexing is enabled, the backup fails.\n■ The media server may not have the correct 3pc.conf file entry for the client\ndisk that is needed for the backup.\nThe following appears in the /usr/openv/netbackup/logs/bpbkar log:\n14:45:00.983 [15773] <4> bpmap_mm_get_devid: GET_DEVICE_INDEX 1\nEMC:SYMMETRIX:601092014000\n14:45:00.986 [15773] <4> bpbkar child_send_keepalives: keepalive\nchild started, pid = 15822\n14:47:02.029 [15773] <4> bpmap_mm_get_devid: keepalive child:\n15822 killed\n14:47:02.030 [15773] <4> bpmap_mm_get_devid: DEVICE_INDEX -1\n14:47:02.031 [15773] <16> bpmap_send_extend: ERR - can't obtain\ndevice id string EMC:SYMMETRIX:601092014000\n14:47:33.167 [15773] <16> bpbkar Exit: ERR - bpbkar FATAL exit\nstatus = 227: no entity was found\n14:47:33.167 [15773] <4> bpbkar Exit: INF - EXIT STATUS 227: no\nentity was found\n14:47:33.168 [15773] <2> bpbkar Exit: INF - Close of stdout\ncomplete\nThis shows that a particular device cannot be found in the 3pc.conf file on\nthemediaserver(14:47:02.031 [15773] <16> bpmap_send_extend: ERR\n- can't obtain device id string EMC:SYMMETRIX:601092014000).\nThe problem is one of the following:\n■ The3pc.conffileonthemediaserverisoutdated.Recreatethe3pc.conf\nfile.\n■ The media server is not on the same Fibre Channel network as the\nthird-partycopydeviceandclientdisk.Asaresult,the3pc.conffiledoes\nnot have a correct entry for the client disk. Run the bptpcinfo command\nwith the -x client_name option; this option adds the client disk to the\n3pc.conf file. For each disk that is added to the file by means of\nbptpcinfo -x client_name, you may need to add the device’s World\nWide Name (WWN=).\nSee the NetBackup Snapshot Client Configuration online document.\nSee Snapshot Client Assistance in the NetBackup Snapshot Client\nAdministrator’s Guide.\n■ The HP VxFS snapshot mechanism requires a dedicated cache partition for\neach snapshot. A check is made in the mount table to make sure that the\ncache partition is not already in use. If the cache partition is already in use,\nstatus code 20 occurs.\nReviewthe/usr/openv/netbackup/logs/bpbkarlogforamessagesimilar\nto the following:\nbpfsmap: FTL - bpfsmap: snapshot cache already in use,\n/dev/arrayvg/vol4c\nbpbkar Exit: ERR - bpbkar FATAL exit status = 20: invalid\ncommand parameter\nbpbkar Exit: INF - EXIT STATUS 20: invalid command parameter\nIf the snapshot cache partition is already in use, do one of the following: Set\nup your policy schedules to run at different times or use different cache\npartitions for each backup.\nIf the Allow multiple data streams option is enabled, each stream must\nhave its own dedicated cache partition.\n■ Compare the NetBackup version level on the server to the version level on the\nclients by doing the following:\n■ On UNIX or Linux NetBackup servers and clients, review the\n/usr/openv/netbackup/bin/version file.\n■ On Windows NetBackup servers, review the\ninstall_path\\NetBackup\\version.txt file or the About NetBackup item\non the Help menu.\n■ On Microsoft Windows clients, review the About NetBackup item on the\nHelp menu.\n■ If a Java interface displays the error, tell them how to enable the debug print\nmanager in the Java startup file. Retry and compare the parameters that\nwere logged on the Java log with the parameters listed in the commands\nusage statement.\n■ FortheBackupMediaServeroptionforVMwarebackups,thestorageunitthat\nis specified in the policy must be unique to your media servers. If the storage\nunitisalsoavailableonanothermediaserver,thesnapshotjobcannotsucceed.\n■ If you protect NAS arrays using VSO FIM snapshot method, perform off-host\nbackup using an alternate client.\n■ ForBigDatapolicies,themediaserverandthebackuphostsmustusethesame\nNetBackup version.\n■ If these actions do not reveal the problem, create a debug log directory for the\nprocessthatreturnedthisstatuscode(iftheprocessuseslegacylogging).Then\nretry the operation and review the resulting log." }, "21": { "code": 21, - "desc": "Socket abrir falhou", - "first_action": "Verifique o NetBackup Problemas relatório para pistas on onde e por que o falha", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Verifique o NetBackup Problemas relatório para pistas on onde e por que o falha\nocorreu. If you não é possível determinar o cause from o Problemas relatório, create\ndebug log directories para o processos que returned this status code. Then,\nretry o operation e verifique o resulting debug logs.\n■ O seguinte informação aplica-se apenas to Sun Solaris:\nVerifique que todos operating system patches estão instalado.\nVeja o Operating Notes section de o NetBackup Release Notes.\n■ O seguinte informação aplica-se apenas to Windows systems:\nVerifique que o recomendada service packs estão instalado.\n■ TheNetBackupmediaservermaynothavetheServicesforNetworkFileSystem\n(NFS) instalado. Como um result, o mídia servidor não é possível contate o Portmapper\nservice. O attempt to manually start o NFS services fails because o\nRede Arquivo System está não instalado.\nInstall o Services para Rede Arquivo System on o mídia servidor." + "desc": "Socket open failed", + "first_action": "Check the NetBackup Problems report for clues on where and why the failure", + "full_action": "Do the following, as appropriate:\n■ Check the NetBackup Problems report for clues on where and why the failure\noccurred. If you cannot determine the cause from the Problems report, create\ndebug log directories for the processes that returned this status code. Then,\nretry the operation and check the resulting debug logs.\n■ The following information applies only to Sun Solaris:\nVerify that all operating system patches are installed.\nSee the Operating Notes section of the NetBackup Release Notes.\n■ The following information applies only to Windows systems:\nVerify that the recommended service packs are installed.\n■ TheNetBackupmediaservermaynothavetheServicesforNetworkFileSystem\n(NFS) installed. As a result, the media server cannot contact the Portmapper\nservice. The attempt to manually start the NFS services fails because the\nNetwork File System is not installed.\nInstall the Services for Network File System on the media server." }, "22": { "code": 22, - "desc": "Socket fechar falhou", - "first_action": "Verifique o NetBackup Problemas relatório para pistas on onde e por que o falha", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Verifique o NetBackup Problemas relatório para pistas on onde e por que o falha\nocorreu. If you não é possível determinar o cause from o Problemas relatório, create\ndebug log directories para o processos que could have returned this status\ncode. Then, retry o operation e verifique o resulting debug logs.\n■ O seguinte informação aplica-se apenas to Sun Solaris:\nVerifique que todos operating system patches estão instalado.\nVeja o Operating Notes section de o NetBackup Release Notes.\n■ O seguinte informação aplica-se apenas to Windows systems:\nVerifique que o recomendada service packs estão instalado." + "desc": "Socket close failed", + "first_action": "Check the NetBackup Problems report for clues on where and why the failure", + "full_action": "Do the following, as appropriate:\n■ Check the NetBackup Problems report for clues on where and why the failure\noccurred. If you cannot determine the cause from the Problems report, create\ndebug log directories for the processes that could have returned this status\ncode. Then, retry the operation and check the resulting debug logs.\n■ The following information applies only to Sun Solaris:\nVerify that all operating system patches are installed.\nSee the Operating Notes section of the NetBackup Release Notes.\n■ The following information applies only to Windows systems:\nVerify that the recommended service packs are installed." }, "23": { "code": 23, - "desc": "Socket ler falhou", - "first_action": "Verifique o NetBackup Problemas relatório para pistas on onde e por que o falha", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Verifique o NetBackup Problemas relatório para pistas on onde e por que o falha\nocorreu. If you não é possível determinar o cause from o Problemas relatório, create\ndebug log directories para o processos que could have returned this status\ncode. Then, retry o operation e verifique o resulting debug logs.\n■ Corrupt binaries estão one possible cause para this erro.\nLoad um fresh bptm from o install mídia to try to resolve o problema.\n■ O seguinte informação aplica-se apenas to Sun Solaris:\nVerifique que todos operating system patches estão instalado.\nVeja o Operating Notes section de o NetBackup Release Notes.\n■ O seguinte informação aplica-se apenas to Windows systems:\nVerifique que o recomendada service packs estão instalado.\n■ O NetBackup mídia servidor está um 8.0 ou earlier version e you have disabled\ninsecure communication in NetBackup. If you desejar to continue com o host\nconexão, do one de o seguinte:\n■ In o NetBackup Administration Console on o master servidor host,\nselect Security Management > Global Security > Enable insecure\ncommunication com o NetBackup 8.0 e earlier hosts option.\n■ Specifythenbseccmd -setsecurityconfig -insecurecommunication on\ncomando." + "desc": "Socket read failed", + "first_action": "Check the NetBackup Problems report for clues on where and why the failure", + "full_action": "Do the following, as appropriate:\n■ Check the NetBackup Problems report for clues on where and why the failure\noccurred. If you cannot determine the cause from the Problems report, create\ndebug log directories for the processes that could have returned this status\ncode. Then, retry the operation and check the resulting debug logs.\n■ Corrupt binaries are one possible cause for this error.\nLoad a fresh bptm from the install media to try to resolve the problem.\n■ The following information applies only to Sun Solaris:\nVerify that all operating system patches are installed.\nSee the Operating Notes section of the NetBackup Release Notes.\n■ The following information applies only to Windows systems:\nVerify that the recommended service packs are installed.\n■ The NetBackup media server is an 8.0 or earlier version and you have disabled\ninsecure communication in NetBackup. If you want to continue with the host\nconnection, do one of the following:\n■ In the NetBackup Administration Console on the master server host,\nselect Security Management > Global Security > Enable insecure\ncommunication with the NetBackup 8.0 and earlier hosts option.\n■ Specifythenbseccmd -setsecurityconfig -insecurecommunication on\ncommand." }, "24": { "code": 24, - "desc": "Socket gravar falhou", - "first_action": "Verifique o NetBackup Problemas relatório para pistas on onde e por que o falha", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Verifique o NetBackup Problemas relatório para pistas on onde e por que o falha\nocorreu. If you não é possível determinar o cause from o Problemas relatório, create\ndebug log directories para o processos que could have returned this status\ncode. Then retry o operation e verifique o resulting debug logs.\n■ Um possible cause está um high rede load. Para example, this problema occurs com\nNão é possível gravar to STDOUT when um Windows system que monitors rede load\ndetects um high load. It then sends um ICMP packet to other systems to inform\nthem que o route they use está disconnected. O log messages foram similar\nto o seguinte:\n01/31/22 14:05:23 ruble crabtree.null.com from cliente\ncrabtree.null.com: ERR - Não é possível gravar to STDOUT. Err não= 242: Não\nroute to host\n01/31/22 14:05:48 ruble crabtree.null.com successfully wrote\nbackup id crabtree.null.com_1643637900, copy 1, fragment 1,\n440864 Kbytes at 628.538 Kbytes/sec\n01/31/22 14:05:51 netbackup crabtree.null.com Cliente\ncrabtree.null.com POLICY Remote3SysFullW SCHED Sirius EXIT\nSTATUS 24 (socket gravar falhou)\n■ O seguinte informação aplica-se apenas to Sun Solaris:\nVerifique que todos operating system patches estão instalado.\nVeja o Operating Notes section de o NetBackup Release Notes.\n■ O seguinte informação aplica-se apenas to Windows systems:\nVerifique que o recomendada service packs estão instalado." + "desc": "Socket write failed", + "first_action": "Check the NetBackup Problems report for clues on where and why the failure", + "full_action": "Do the following, as appropriate:\n■ Check the NetBackup Problems report for clues on where and why the failure\noccurred. If you cannot determine the cause from the Problems report, create\ndebug log directories for the processes that could have returned this status\ncode. Then retry the operation and check the resulting debug logs.\n■ A possible cause is a high network load. For example, this problem occurs with\nCannot write to STDOUT when a Windows system that monitors network load\ndetects a high load. It then sends an ICMP packet to other systems to inform\nthem that the route they use is disconnected. The log messages were similar\nto the following:\n01/31/22 14:05:23 ruble crabtree.null.com from client\ncrabtree.null.com: ERR - Cannot write to STDOUT. Err no= 242: No\nroute to host\n01/31/22 14:05:48 ruble crabtree.null.com successfully wrote\nbackup id crabtree.null.com_1643637900, copy 1, fragment 1,\n440864 Kbytes at 628.538 Kbytes/sec\n01/31/22 14:05:51 netbackup crabtree.null.com CLIENT\ncrabtree.null.com POLICY Remote3SysFullW SCHED Sirius EXIT\nSTATUS 24 (socket write failed)\n■ The following information applies only to Sun Solaris:\nVerify that all operating system patches are installed.\nSee the Operating Notes section of the NetBackup Release Notes.\n■ The following information applies only to Windows systems:\nVerify that the recommended service packs are installed." }, "25": { "code": 25, - "desc": "Não foi possível conectar ao socket", + "desc": "Cannot connect on socket", "first_action": "Verifythatbpcompatd,vnetd,andPrivateBranchExchange(PBX)arerunning.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Verifythatbpcompatd,vnetd,andPrivateBranchExchange(PBX)arerunning.\nInformação on how to start PBX está disponível.\nVeja \"resolvendo PBX problemas\" in o NetBackup Troubleshooting Guide.\n■ If necessary, stop e restart NetBackup.\n■ On UNIX systems, enter o seguinte:\n/usr/openv/netbackup/bin/bp.kill_all\n/usr/openv/netbackup/bin/bp.start_all\n■ On Windows systems, enter o seguinte:\ninstall_path\\NetBackup\\bin\\bpdown\ninstall_path\\NetBackup\\bin\\bpup\n■ O seguinte informação aplica-se apenas to um UNIX ou Linux NetBackup master\nservidor:\nVerifique que o bprd e o bpdbm processos estão executando. If these processos\nestão não executando, start them. On um Windows master servidor, verifique que o\nNetBackup Request Manager e o NetBackup Banco de dados Manager services\nestão executando. If these services estão não executando, start them.\nIf these processos ou services estão executando, examine o Todos Log Entradas relatório\npara o time de o falha to determinar onde o falha ocorreu.\nDo one de o seguinte:\n■ Ifyoucannotviewthereportoryougetacannot conectar on socketerror,\nverifique again que o NetBackup Banco de dados Manager service ou daemon está\nexecutando. Then, create um debug log diretório para bpdbm, retry o operation,\ne verifique o resulting debug log.\n■ If you view o relatório e do não find um problem-related entry, create o\ndebug log directories para o related processos que foram executando when o\nerro first appeared. (This process frequently está bpbrm.) Then, retry o\noperation e verifique o resulting debug logs.\n■ Verifique que o servidor list specifies o correct master servidor.\n■ O seguinte informação aplica-se apenas to Windows systems:\nO master servidor está designated in o Servidor to use para backups e\nrestoresdrop-downintheSpecifyNetBackupMachinesandPolicyType\ndialogbox.Todisplaythisdialogbox,starttheBackup,Archive,andRestore\ninterface e click Specify NetBackup Machines e Policy Type on o\nArquivo menu.\n■ O seguinte informação aplica-se apenas to UNIX e Linux systems:\nO master servidor está o first Servidor entry in o bp.conf arquivo.\n■ Verifique o Cohesity Technical Support website to garanta que todos\nrecomendada NetBackup patches estão instalado.\n■ If falha occurs when you run um user-directed backup from um cliente, make\nsure que um user-directed backup schedule exists at o master servidor.\n■ Com NetBackup banco de dados extensions:\nMakesurethattheapplicabledatabaseproducthasthecorrectpermissions\nallowing NetBackup to gravar to o progress log on o cliente.\n■ O seguinte informação aplica-se apenas to UNIX systems:\nIf bpdbm has sair when o shutdown script runs on um mídia servidor, carefully\nler o K77netbackup script. It contains details on how to prevent this\nproblema. O script está in /usr/openv/netbackup/bin/goodies.\nIf you change o servidor list on um UNIX ou Linux master servidor, do o seguinte\npara o changes to take effect: Stop e then restart o NetBackup Request\nDaemon (bprd) e NetBackup Banco de dados Manager Daemon (bpdbm). On\nWindows, stop e restart o NetBackup Request Manager e NetBackup\nBanco de dados Manager services.\n■ Verifique o services arquivo.\n■ O seguinte informação aplica-se apenas to UNIX systems:\nVerifique que o /etc/services arquivo (e NIS services if NIS está used) has\nentradas para o NetBackup services: bpcd, bpdbm, e bprd.\nOnWindows,verifythatthe%SystemRoot%\\system32\\drivers\\etc\\services\narquivo has o correct entradas para bpcd, bpdbm, e bprd.\nAlso, verifique que o seguinte numbers match o settings in o services arquivo:\nO NetBackup Cliente Service Port e o NetBackup Request Service\nPort on o Rede tab in o NetBackup Cliente Properties dialog box. To\ndisplay this dialog box, start o Backup, Archive, e Restauração interface e\nclick NetBackup Cliente Properties on o Arquivo menu. O values on o\nNetworktabarewrittentotheservicesfilewhentheNetBackupClientservice\nstarts.\nVeja Verifying host names e service entradas in NetBackup in o NetBackup\nTroubleshooting Guide.\n■ On Sun Solaris, verifique que todos operating system patches estão instalado\nVeja o Operating Notes section de o NetBackup Release Notes.\n■ On Windows, verifique que o recomendada service packs estão instalado.\n■ When o base NetBackup license key expires, daemons (such como bprd e\nbpdbm) terminate on o NetBackup servidor. If these daemons estão não executando,\nyou estão likely to encounter status code 25 errors in o Administration console.\nInstall um valid base NetBackup license key, restart o daemons, e restart o\nconsole.\n■ Para NetBackup Snapshot Cliente, o seguinte aplica-se: When many devices estão\nconfigurado on um mídia servidor, it may take um long time para o bptpcinfo\ncomando to generate o arquivo 3pc. When o backup está run para o first time, o\nbackup may fail com status 25. Make sure que o\n/usr/openv/volmgr/database/3pc.conffileexists.Ifitdoes,rerunthebackup.\nIf o backup fails again, run o bptpcinfo manually to generate o arquivo 3pc,\nthen try o backup again.\n■ In o Auto Image Replication (A.I.R.) scenario, o erro can occur if insecure\ncommunication está disabled in NetBackup after o trust relationship between\no 8.1 e 8.0 master servers está established. If you desejar to continue com o\nhost conexão, do one de o seguinte:\n■ In o NetBackup Administration Console on o master servidor host,\nselect o Security Management > Global Security > Secure\nCommunication>EnableinsecurecommunicationwithNetBackup8.0\ne earlier hosts option.\n■ Specifythenbseccmd -setsecurityconfig -insecurecommunication on\ncomando.\n■ Para RHV:\n■ Garanta que o RHV credentials estão correct e o virtualization servidor está\naccessible.\n■ Para VMware:\n■ When o VIRTUALIZATION_HOSTS_SECURE_CONNECT_ENABLED option está\nenabled, you must verifique o placement de o certificates e CRLs. Verifique\nwhethertheVMwarevirtualizationservers'(vCenter,ESX,ESXi)certificates\ne CRLs estão added to o respective ECA configurado trust store e o\nCRL caminho.\n■ Garanta que o certificates e o CRL arquivos estão in o correct format e\no trust store arquivo e o CRL arquivos estão não corrupted.\n■ Apenas o PEM certificate format para file-based trust store & Windows trust\nstore estão supported para virtualization servers. P7b ou DER format arquivo based\ntruststoreisnotsupported.Whenthisfeatureisenabled,thecertificateECA\nstore should either be Windows certificate store ou arquivo based PEM format\nstore.\n■ Para Nutanix AHV:\n■ Garanta que o CA certificate está added to o NetBackup trust store. Refer\nto o Nutanix AHV Administrator’s Guide para more details." + "full_action": "Do the following, as appropriate:\n■ Verifythatbpcompatd,vnetd,andPrivateBranchExchange(PBX)arerunning.\nInformation on how to start PBX is available.\nSee \"Resolving PBX problems\" in the NetBackup Troubleshooting Guide.\n■ If necessary, stop and restart NetBackup.\n■ On UNIX systems, enter the following:\n/usr/openv/netbackup/bin/bp.kill_all\n/usr/openv/netbackup/bin/bp.start_all\n■ On Windows systems, enter the following:\ninstall_path\\NetBackup\\bin\\bpdown\ninstall_path\\NetBackup\\bin\\bpup\n■ The following information applies only to a UNIX or Linux NetBackup master\nserver:\nVerify that the bprd and the bpdbm processes are running. If these processes\nare not running, start them. On a Windows master server, verify that the\nNetBackup Request Manager and the NetBackup Database Manager services\nare running. If these services are not running, start them.\nIf these processes or services are running, examine the All Log Entries report\nfor the time of the failure to determine where the failure occurred.\nDo one of the following:\n■ Ifyoucannotviewthereportoryougetacannot connect on socketerror,\nverify again that the NetBackup Database Manager service or daemon is\nrunning. Then, create a debug log directory for bpdbm, retry the operation,\nand check the resulting debug log.\n■ If you view the report and do not find a problem-related entry, create the\ndebug log directories for the related processes that were running when the\nerror first appeared. (This process frequently is bpbrm.) Then, retry the\noperation and check the resulting debug logs.\n■ Verify that the server list specifies the correct master server.\n■ The following information applies only to Windows systems:\nThe master server is designated in the Server to use for backups and\nrestoresdrop-downintheSpecifyNetBackupMachinesandPolicyType\ndialogbox.Todisplaythisdialogbox,starttheBackup,Archive,andRestore\ninterface and click Specify NetBackup Machines and Policy Type on the\nFile menu.\n■ The following information applies only to UNIX and Linux systems:\nThe master server is the first SERVER entry in the bp.conf file.\n■ Check the Cohesity Technical Support website to ensure that all\nrecommended NetBackup patches are installed.\n■ If failure occurs when you run a user-directed backup from a client, make\nsure that a user-directed backup schedule exists at the master server.\n■ With NetBackup database extensions:\nMakesurethattheapplicabledatabaseproducthasthecorrectpermissions\nallowing NetBackup to write to the progress log on the client.\n■ The following information applies only to UNIX systems:\nIf bpdbm has quit when the shutdown script runs on a media server, carefully\nread the K77netbackup script. It contains details on how to prevent this\nproblem. The script is in /usr/openv/netbackup/bin/goodies.\nIf you change the server list on a UNIX or Linux master server, do the following\nfor the changes to take effect: Stop and then restart the NetBackup Request\nDaemon (bprd) and NetBackup Database Manager Daemon (bpdbm). On\nWindows, stop and restart the NetBackup Request Manager and NetBackup\nDatabase Manager services.\n■ Check the services file.\n■ The following information applies only to UNIX systems:\nVerify that the /etc/services file (and NIS services if NIS is used) has\nentries for the NetBackup services: bpcd, bpdbm, and bprd.\nOnWindows,verifythatthe%SystemRoot%\\system32\\drivers\\etc\\services\nfile has the correct entries for bpcd, bpdbm, and bprd.\nAlso, verify that the following numbers match the settings in the services file:\nThe NetBackup Client Service Port and the NetBackup Request Service\nPort on the Network tab in the NetBackup Client Properties dialog box. To\ndisplay this dialog box, start the Backup, Archive, and Restore interface and\nclick NetBackup Client Properties on the File menu. The values on the\nNetworktabarewrittentotheservicesfilewhentheNetBackupClientservice\nstarts.\nSee Verifying host names and service entries in NetBackup in the NetBackup\nTroubleshooting Guide.\n■ On Sun Solaris, verify that all operating system patches are installed\nSee the Operating Notes section of the NetBackup Release Notes.\n■ On Windows, verify that the recommended service packs are installed.\n■ When the base NetBackup license key expires, daemons (such as bprd and\nbpdbm) terminate on the NetBackup server. If these daemons are not running,\nyou are likely to encounter status code 25 errors in the Administration console.\nInstall a valid base NetBackup license key, restart the daemons, and restart the\nconsole.\n■ For NetBackup Snapshot Client, the following applies: When many devices are\nconfigured on a media server, it may take a long time for the bptpcinfo\ncommand to generate the file 3pc. When the backup is run for the first time, the\nbackup may fail with status 25. Make sure that the\n/usr/openv/volmgr/database/3pc.conffileexists.Ifitdoes,rerunthebackup.\nIf the backup fails again, run the bptpcinfo manually to generate the file 3pc,\nthen try the backup again.\n■ In the Auto Image Replication (A.I.R.) scenario, the error can occur if insecure\ncommunication is disabled in NetBackup after the trust relationship between\nthe 8.1 and 8.0 master servers is established. If you want to continue with the\nhost connection, do one of the following:\n■ In the NetBackup Administration Console on the master server host,\nselect the Security Management > Global Security > Secure\nCommunication>EnableinsecurecommunicationwithNetBackup8.0\nand earlier hosts option.\n■ Specifythenbseccmd -setsecurityconfig -insecurecommunication on\ncommand.\n■ For RHV:\n■ Ensure that the RHV credentials are correct and the virtualization server is\naccessible.\n■ For VMware:\n■ When the VIRTUALIZATION_HOSTS_SECURE_CONNECT_ENABLED option is\nenabled, you must verify the placement of the certificates and CRLs. Verify\nwhethertheVMwarevirtualizationservers'(vCenter,ESX,ESXi)certificates\nand CRLs are added to the respective ECA configured trust store and the\nCRL path.\n■ Ensure that the certificates and the CRL files are in the correct format and\nthe trust store file and the CRL files are not corrupted.\n■ Only the PEM certificate format for file-based trust store & Windows trust\nstore are supported for virtualization servers. P7b or DER format file based\ntruststoreisnotsupported.Whenthisfeatureisenabled,thecertificateECA\nstore should either be Windows certificate store or file based PEM format\nstore.\n■ For Nutanix AHV:\n■ Ensure that the CA certificate is added to the NetBackup trust store. Refer\nto the Nutanix AHV Administrator’s Guide for more details." }, "26": { "code": 26, - "desc": "Falha no handshake (aperto de mão) entre cliente e servidor", - "first_action": "Verifique o PKI artifacts por executando these commands:", - "full_action": "Determinar which activity encontrado o handshake\nfalha por examining o Todos Log Entradas relatório para o appropriate time period.\nDeterminar o cliente e servidor que had o handshake falha.\nFordetailedtroubleshootinginformation,createadebuglogdirectoryfortheprocess\nque returned this status code. Then retry o operation e review o resulting\ndebug log.\nIftheerrorhasoccurredduringthecertificateenrollmentprocess,verifythefollowing:\n■ Verifique o PKI artifacts por executando these commands:\n■ nbcertcmd -listAllCertificates [-jks] - Run on o master servidor to\ndisplay o web servidor certificate informação from Java keystore.\n■ nbcertcmd -listCACertDetails -ECA - Run on o host to list o details\nde o CA certificates que estão stored its trust store.\n■ Garanta que o issuers de o cliente e servidor certificates estão disponível in each\nother’s trust stores." + "desc": "Client/server handshaking failed", + "first_action": "Verify the PKI artifacts by running these commands:", + "full_action": "Determine which activity encountered the handshake\nfailure by examining the All Log Entries report for the appropriate time period.\nDetermine the client and server that had the handshake failure.\nFordetailedtroubleshootinginformation,createadebuglogdirectoryfortheprocess\nthat returned this status code. Then retry the operation and review the resulting\ndebug log.\nIftheerrorhasoccurredduringthecertificateenrollmentprocess,verifythefollowing:\n■ Verify the PKI artifacts by running these commands:\n■ nbcertcmd -listAllCertificates [-jks] - Run on the master server to\ndisplay the web server certificate information from Java keystore.\n■ nbcertcmd -listCACertDetails -ECA - Run on the host to list the details\nof the CA certificates that are stored its trust store.\n■ Ensure that the issuers of the client and server certificates are available in each\nother’s trust stores." }, "27": { "code": 27, - "desc": "Child process killed por signal", - "first_action": "Verifique o NetBackup Todos Log Entradas relatório para pistas on", - "full_action": "Verifique o NetBackup Todos Log Entradas relatório para pistas on\nwhereandwhythefailureoccurred.Fordetailedtroubleshootinginformation,create\num debug log diretório para o process que you think may have returned this status\ncode. Then, retry o operation e verifique o resulting debug log." + "desc": "Child process killed by signal", + "first_action": "Check the NetBackup All Log Entries report for clues on", + "full_action": "Check the NetBackup All Log Entries report for clues on\nwhereandwhythefailureoccurred.Fordetailedtroubleshootinginformation,create\na debug log directory for the process that you think may have returned this status\ncode. Then, retry the operation and check the resulting debug log." }, "28": { "code": 28, - "desc": "Falhou trying to fork um process", - "first_action": "Verifique o NetBackup Todos Log Entradas relatório para pistas on", - "full_action": "Verifique o NetBackup Todos Log Entradas relatório para pistas on\nwhereandwhythefailureoccurred.Fordetailedtroubleshootinginformation,create\ndebug log directories para o processos que think may have returned this status\ncode. Then, retry o operation e verifique o resulting debug logs." + "desc": "Failed trying to fork a process", + "first_action": "Check the NetBackup All Log Entries report for clues on", + "full_action": "Check the NetBackup All Log Entries report for clues on\nwhereandwhythefailureoccurred.Fordetailedtroubleshootinginformation,create\ndebug log directories for the processes that think may have returned this status\ncode. Then, retry the operation and check the resulting debug logs." }, "29": { "code": 29, - "desc": "Falhou trying to exec um comando", - "first_action": "Verifique o NetBackup Todos Log Entradas relatório para pistas on onde e por que o", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Verifique o NetBackup Todos Log Entradas relatório para pistas on onde e por que o\nfalha ocorreu.\n■ Verifique o permissions on o comando to be run.\n■ Para detailed troubleshooting informação, create um debug log diretório para o\nprocess que returned this status code. Then retry o operation e verifique o\nresulting debug log." + "desc": "Failed trying to exec a command", + "first_action": "Check the NetBackup All Log Entries report for clues on where and why the", + "full_action": "Do the following, as appropriate:\n■ Check the NetBackup All Log Entries report for clues on where and why the\nfailure occurred.\n■ Check the permissions on the command to be run.\n■ For detailed troubleshooting information, create a debug log directory for the\nprocess that returned this status code. Then retry the operation and check the\nresulting debug log." }, "30": { "code": 30, - "desc": "Não é possível get password informação", - "first_action": "Verifique o NetBackup Todos Log Entradas relatório para pistas on", - "full_action": "Verifique o NetBackup Todos Log Entradas relatório para pistas on\nwhereandwhythefailureoccurred.Fordetailedtroubleshootinginformation,create\nadebuglogfortheprocessthatyouthinkmayhavereturnedthisstatuscode.Then,\nretry o operation e verifique o resulting debug log." + "desc": "Cannot get password information", + "first_action": "Check the NetBackup All Log Entries report for clues on", + "full_action": "Check the NetBackup All Log Entries report for clues on\nwhereandwhythefailureoccurred.Fordetailedtroubleshootinginformation,create\nadebuglogfortheprocessthatyouthinkmayhavereturnedthisstatuscode.Then,\nretry the operation and check the resulting debug log." }, "31": { "code": 31, - "desc": "Could não set usuário ID para process", - "first_action": "Verifique o NetBackup Todos Log Entradas relatório para pistas on", - "full_action": "Verifique o NetBackup Todos Log Entradas relatório para pistas on\nwhereandwhythefailureoccurred.Fordetailedtroubleshootinginformation,create\num debug log diretório para o process que you think may have returned this status\ncode. Then, retry o operation e verifique o resulting debug log." + "desc": "Could not set user ID for process", + "first_action": "Check the NetBackup All Log Entries report for clues on", + "full_action": "Check the NetBackup All Log Entries report for clues on\nwhereandwhythefailureoccurred.Fordetailedtroubleshootinginformation,create\na debug log directory for the process that you think may have returned this status\ncode. Then, retry the operation and check the resulting debug log." }, "32": { "code": 32, - "desc": "Could não set group ID para process", - "first_action": "Verifique o NetBackup Todos Log Entradas relatório para pistas on", - "full_action": "Verifique o NetBackup Todos Log Entradas relatório para pistas on\nwhereandwhythefailureoccurred.Fordetailedtroubleshootinginformation,create\num debug log diretório para o process que you think may have returned this status\ncode. Then, retry o operation e verifique o resulting debug log." + "desc": "Could not set group ID for process", + "first_action": "Check the NetBackup All Log Entries report for clues on", + "full_action": "Check the NetBackup All Log Entries report for clues on\nwhereandwhythefailureoccurred.Fordetailedtroubleshootinginformation,create\na debug log directory for the process that you think may have returned this status\ncode. Then, retry the operation and check the resulting debug log." }, "33": { "code": 33, - "desc": "Falhou while trying to send mail", - "first_action": "Verifique o NetBackup Todos Log Entradas relatório para pistas on", - "full_action": "Verifique o NetBackup Todos Log Entradas relatório para pistas on\nwhereandwhythefailureoccurred.Fordetailedtroubleshootinginformation,create\num debug log diretório para o process que you think may have returned this status\ncode. Then, retry o operation e verifique o resulting debug log." + "desc": "Failed while trying to send mail", + "first_action": "Check the NetBackup All Log Entries report for clues on", + "full_action": "Check the NetBackup All Log Entries report for clues on\nwhereandwhythefailureoccurred.Fordetailedtroubleshootinginformation,create\na debug log directory for the process that you think may have returned this status\ncode. Then, retry the operation and check the resulting debug log." }, "34": { "code": 34, - "desc": "Falhou waiting para child process", - "first_action": "Verifique o NetBackup Todos Log Entradas relatório para pistas on", - "full_action": "Verifique o NetBackup Todos Log Entradas relatório para pistas on\nwhereandwhythefailureoccurred.Fordetailedtroubleshootinginformation,create\nadebuglogfortheprocessthatyouthinkmayhavereturnedthisstatuscode.Then,\nretry o operation e verifique o resulting debug log." + "desc": "Failed waiting for child process", + "first_action": "Check the NetBackup All Log Entries report for clues on", + "full_action": "Check the NetBackup All Log Entries report for clues on\nwhereandwhythefailureoccurred.Fordetailedtroubleshootinginformation,create\nadebuglogfortheprocessthatyouthinkmayhavereturnedthisstatuscode.Then,\nretry the operation and check the resulting debug log." }, "35": { "code": 35, - "desc": "Não é possível make requerido diretório", - "first_action": "Verifique o NetBackup Todos Log Entradas relatório to determinar which diretório foi", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Verifique o NetBackup Todos Log Entradas relatório to determinar which diretório foi\nnotcreatedandwhyitwasnotcreated.Inparticular,checkforafulldiskpartition.\n■ Verifique o permissions on o parent diretório. Verifique que NetBackup services\narestartedwithaLogonasaccountthathaspermissiontocreatethedirectory.\n■ Para detailed troubleshooting informação, create um debug log diretório para o\nprocess que returned this status code. Then retry o operation e verifique o\nresulting debug log." + "desc": "Cannot make required directory", + "first_action": "Check the NetBackup All Log Entries report to determine which directory was", + "full_action": "Do the following, as appropriate:\n■ Check the NetBackup All Log Entries report to determine which directory was\nnotcreatedandwhyitwasnotcreated.Inparticular,checkforafulldiskpartition.\n■ Check the permissions on the parent directory. Verify that NetBackup services\narestartedwithaLogonasaccountthathaspermissiontocreatethedirectory.\n■ For detailed troubleshooting information, create a debug log directory for the\nprocess that returned this status code. Then retry the operation and check the\nresulting debug log." }, "36": { "code": 36, - "desc": "Falhou trying to allocate memória", + "desc": "Failed trying to allocate memory", "first_action": "Freeupmemorybyterminatinganyunneededprocesses", - "full_action": "Freeupmemorybyterminatinganyunneededprocesses\nque consume um lot de memória. Add more swap space ou physical memória." + "full_action": "Freeupmemorybyterminatinganyunneededprocesses\nthat consume a lot of memory. Add more swap space or physical memory." }, "37": { "code": 37, - "desc": "Operation solicitado por um inválido servidor", - "first_action": "O operating system onde o arquivos foram salvo up does não match o", - "full_action": "ExaminetheNetBackupAllLogEntriesreportforthetime\nde this erro to determinar which system tried to conectar to o master servidor.\nIf o servidor está um valid mídia servidor, verifique que o armazenamento unidade para o mídia servidor\nisdefined.Also,verifythattheserverorWindowsNetBackupRemoteAdministration\nConsole has um servidor list entry on o master servidor.\nIf necessary, update o servidor list.\nOn um UNIX ou Linux master servidor, add um Servidor = media_server_name to o\nbp.conf arquivo. media_server_name está o host name de o mídia servidor. On um\nWindows master servidor, add o mídia servidor to o list on o Servers tab in o\nMaster Servidor Properties dialog box.\nVeja \"usando o Host Properties window to access configuration settings\" in o\nNetBackup Troubleshooting Guide.\nIf um servidor ou NetBackup Remote Administration Console has more than one host\nname (Example: multiple rede interfaces), verifique que o master servidor has um\nservidor list entry para each de them.\nIf you change o servidor list on um UNIX ou Linux master servidor, do o seguinte para\no changes to take effect: Stop e then restart o NetBackup Request Daemon\n(bprd) e NetBackup Banco de dados Manager Daemon (bpdbm). On Windows, stop\ne restart o NetBackup Request Manager e NetBackup Banco de dados Manager\nservices.\nWhen um VMware agentless restauração está performed, o restauração can cause one de o\nseguinte issues:\n■ O operating system onde o arquivos foram salvo up does não match o\noperating system onde NetBackup attempted to restauração o arquivos.\nSelect um virtual machine para o restauração que has o same operating system como\no backup virtual machine. Confirm que o operating system type que está\nspecifiedintargetVMpropertiesmatchestotheoperatingsystemthatisinstalled\nin o target VM." + "desc": "Operation requested by an invalid server", + "first_action": "The operating system where the files were backed up does not match the", + "full_action": "ExaminetheNetBackupAllLogEntriesreportforthetime\nof this error to determine which system tried to connect to the master server.\nIf the server is a valid media server, verify that the storage unit for the media server\nisdefined.Also,verifythattheserverorWindowsNetBackupRemoteAdministration\nConsole has a server list entry on the master server.\nIf necessary, update the server list.\nOn a UNIX or Linux master server, add a SERVER = media_server_name to the\nbp.conf file. media_server_name is the host name of the media server. On a\nWindows master server, add the media server to the list on the Servers tab in the\nMaster Server Properties dialog box.\nSee \"Using the Host Properties window to access configuration settings\" in the\nNetBackup Troubleshooting Guide.\nIf a server or NetBackup Remote Administration Console has more than one host\nname (Example: multiple network interfaces), verify that the master server has a\nserver list entry for each of them.\nIf you change the server list on a UNIX or Linux master server, do the following for\nthe changes to take effect: Stop and then restart the NetBackup Request Daemon\n(bprd) and NetBackup Database Manager Daemon (bpdbm). On Windows, stop\nand restart the NetBackup Request Manager and NetBackup Database Manager\nservices.\nWhen a VMware agentless restore is performed, the restore can cause one of the\nfollowing issues:\n■ The operating system where the files were backed up does not match the\noperating system where NetBackup attempted to restore the files.\nSelect a virtual machine for the restore that has the same operating system as\nthe backup virtual machine. Confirm that the operating system type that is\nspecifiedintargetVMpropertiesmatchestotheoperatingsystemthatisinstalled\nin the target VM." }, "38": { "code": 38, - "desc": "Could não get group informação", - "first_action": "Verifique o NetBackup Problemas relatório para pistas on por que", - "full_action": "Verifique o NetBackup Problemas relatório para pistas on por que\no erro ocorreu. Para detailed troubleshooting informação, create um debug log\ndiretório para o process que returned this status code. Then retry o operation\ne verifique o resulting debug log." + "desc": "Could not get group information", + "first_action": "Check the NetBackup Problems report for clues on why", + "full_action": "Check the NetBackup Problems report for clues on why\nthe error occurred. For detailed troubleshooting information, create a debug log\ndirectory for the process that returned this status code. Then retry the operation\nand check the resulting debug log." }, "39": { "code": 39, - "desc": "Cliente name mismatch", - "first_action": "Change one de o seguinte so o two match: o", - "full_action": "Change one de o seguinte so o two match: o\nNetBackup cliente name setting on o cliente (veja o applicable NetBackup users\nguide) ou o one in o policy configuration on o servidor." + "desc": "Client name mismatch", + "first_action": "Change one of the following so the two match: the", + "full_action": "Change one of the following so the two match: the\nNetBackup client name setting on the client (see the applicable NetBackup users\nguide) or the one in the policy configuration on the server." }, "40": { "code": 40, - "desc": "Rede conexão broken", - "first_action": "Try pinging o cliente from o servidor. If pinging está não possible, verifique para loose", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Try pinging o cliente from o servidor. If pinging está não possible, verifique para loose\nconnections ou other rede problemas.\n■ Verifique que o servidor list settings estão correct on both o cliente e o servidor.\nIf o backup involves um mídia servidor, verifique que these entradas estão correct on\nboth o master e o mídia servidor. Para example, if um mídia servidor does não\nhave um servidor list entry para o master, it does não accept connections from o\nmaster.\n■ On Windows, o master servidor está designated on o Servers tab in o\nMaster Servidor Properties dialog box.\nVeja \"usando o Host Properties window to access configuration settings\" in\no NetBackup Troubleshooting Guide.\n■ On UNIX e Linux systems, o master servidor está o first Servidor entry in\no bp.conf arquivo.\nIf you change o servidor list on um UNIX ou Linux master servidor, do o seguinte\npara o changes to take effect: Stop e then restart o NetBackup Request\nDaemon (bprd) e NetBackup Banco de dados Manager Daemon (bpdbm). On\nWindows, stop e restart o NetBackup Request Manager e NetBackup\nBanco de dados Manager services.\n■ Status code 40 can also be due to denial de um mount request por o operator.\n■ Thisstatuscodemayoccurifnbjmwasunabletoconnecttobpbrmortobpmount.\nExamine o nbjm unified log (originator ID 117) ou o bpbrm ou o bpmount\nlegacy logs para more detail on o cause de o erro." + "desc": "Network connection broken", + "first_action": "Try pinging the client from the server. If pinging is not possible, check for loose", + "full_action": "Do the following, as appropriate:\n■ Try pinging the client from the server. If pinging is not possible, check for loose\nconnections or other network problems.\n■ Verify that the server list settings are correct on both the client and the server.\nIf the backup involves a media server, verify that these entries are correct on\nboth the master and the media server. For example, if a media server does not\nhave a server list entry for the master, it does not accept connections from the\nmaster.\n■ On Windows, the master server is designated on the Servers tab in the\nMaster Server Properties dialog box.\nSee \"Using the Host Properties window to access configuration settings\" in\nthe NetBackup Troubleshooting Guide.\n■ On UNIX and Linux systems, the master server is the first SERVER entry in\nthe bp.conf file.\nIf you change the server list on a UNIX or Linux master server, do the following\nfor the changes to take effect: Stop and then restart the NetBackup Request\nDaemon (bprd) and NetBackup Database Manager Daemon (bpdbm). On\nWindows, stop and restart the NetBackup Request Manager and NetBackup\nDatabase Manager services.\n■ Status code 40 can also be due to denial of a mount request by the operator.\n■ Thisstatuscodemayoccurifnbjmwasunabletoconnecttobpbrmortobpmount.\nExamine the nbjm unified log (originator ID 117) or the bpbrm or the bpmount\nlegacy logs for more detail on the cause of the error." }, "41": { "code": 41, - "desc": "Rede conexão esgotado fora NetBackup status codes 127 NetBackup status codes", - "first_action": "If you backup to many arquivos, use Host Properties on o NetBackup servidor to", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ If you backup to many arquivos, use Host Properties on o NetBackup servidor to\nchangeClientreadtimeouttoamuchhighervalue(forexample:4000).These\nsettings estão on o Universal Settings tab in o Master Servidor Properties\ndialog box. O default para this time fora está 300 seconds.\nAlso, set o Arquivo browse timeouton o Timeouts tab to um value greater than\n4000.\nThen retry o operation. O names de o arquivos estão logged on o debug log\narquivo in o /usr/openv/netbackup/logs/bpbkar diretório before bpbkar\nprocessos them. O last arquivo in o log está o arquivo que causes problemas.\n■ On UNIX, Linux, ou Windows clients, verifique para o seguinte problemas com o\nbpbkar cliente process.\nOn Windows clients:The bpbkar cliente process está não hung. Due to o arquivos e\ndirectoriesitscans,ithasnotrepliedtotheserverwithintheClientreadtimeout\nperiod. This erro occurs during incremental backups when directories have\nthousands de unmodified arquivos.\nPara this case, use Host Properties on o NetBackup servidor to change Cliente\nreadtimeout.ThissettingisontheUniversalSettingstabintheMasterServer\nProperties dialog box. O default para this time fora está 300 seconds.\nVeja \"usando o Host Properties window to access configuration settings\" in o\nNetBackup Troubleshooting Guide.\nYou can also monitor CPU utilization to determinar if this condition exists.\nO seguinte informação aplica-se apenas to UNIX ou Linux clients:\n■ Thebpbkarclientprocessishungonafilethathasamandatorylockingset.\nPara this case, add o seguinte to o client’s bp.conf arquivo:\nVERBOSE\nComo raiz on o cliente, run o seguinte:\ntouch /usr/openv/netbackup/bpbkar_path_tr\n/usr/openv/netbackup/logs/bpbkar\nThen retry o operation. O names de o arquivos estão logged on o debug\nlogfileinthe/usr/openv/netbackup/logs/bpbkardirectorybeforebpbkar\nprocessos them. O last arquivo in o log está o arquivo que causes problemas.\nNote: Also, use these procedures para other unknown bpbkar hangs.\nIf o problema está due to mandatory arquivo locking, have NetBackup skip o\nlocked arquivos. Set LOCKED_FILE_ACTION to SKIP in o\n/usr/openv/netbackup/bp.conf arquivo on o cliente.\n■ O bpbkar cliente process está não hung. Due to o arquivos e directories it\nscans, it has não replied to o servidor within CLIENT_READ_TIMEOUT ou\nCLIENT_CONNECT_TIMEOUT. This erro occurs during backups when\ndirectorieshavethousandsofunmodifiedfilesorduringrestoresofthesparse\narquivos que have thousands de holes. Para this case, try to add ou modify o\nCLIENT_READ_TIMEOUT value in o server’s\n/usr/openv/netbackup/bp.conf arquivo. O default para\nCLIENT_READ_TIMEOUT está 300 seconds if it está não specified.\nUse seu system’s ps comando e monitor CPU utilization to help decide\nwhich de these conditions exist.\nWhen you finish o investigation de o problema, excluir o\n/usr/openv/netbackup/logs/bpbkardirectory,sincethelogfilescanbecome\nquite large e estão não deleted automatically. Also excluir\n/usr/openv/netbackup/bpbkar_path_tr so you do não generate larger log\narquivos than needed o next time you create diretório\n/usr/openv/netbackup/logs/bpbkar.\n■ On Windows systems, try o seguinte:\n■ Disable o seguinte arquivo:\ninstall_path\\VERITAS\\NetBackup\\bin\\tracker.exe\n■ Repair hard drive fragmentation. Try um application que está called Diskeeper\nLite, which está part de o Windows Resource Kit.\n■ Make sure que enough space está disponível in \\temp.\n■ If o servidor não é possível conectar to o cliente, create bpcd ou bpbkar (UNIX, Linux,\ne Windows apenas) debug log directories on o cliente. Then retry o operation\ne verifique o resulting logs. If these logs do não provide um clue, create um bpbrm\ndebuglogontheserver.Thenretrytheoperationandchecktheresultingdebug\nlog.\nIf o bpbrm log has entradas similar to o seguinte, o problema está in o routing\nconfiguration on o servidor:\nbpbrm hookup_timeout: esgotado fora waiting during o cliente hookup\nbpbrm Exit: cliente backup EXIT STATUS 41: rede conexão\nesgotado fora\nVerifique que o cliente IP address está correct in o name service que está used. On\nUNIX clients, if both o NIS e o DNS arquivos estão used, verifique que they match.\nVeja \"resolvendo rede communication problemas\" in o NetBackup\nTroubleshooting Guide.\n■ If you use um AIX token ring adapter e o routed daemon está executando, o\ntime fora occurs because o token ring adapter creates dynamic routes. It then\ncauses o routed daemon to crash.\n■ Para um FlashBackup cliente, this erro occurs if o arquivo system being salvo up está\nverylargeandhasaverylargenumberoffiles.Itcanalsooccurifalargenumber\nde concurrent data streams estão active at o same time. To correct it, add\nCLIENT_READ_TIMEOUTtothe/usr/openv/netbackup/bp.conffileandset\nit to aumentar o time-out interval.\n■ Verifique o Cohesity Technical Support website to garanta que todos recomendada\nNetBackup patches estão instalado.\n■ Add o CLIENT_READ_TIMEOUT values to o master servidor, mídia servidor,\nandclientwhenaNetBackupdatabaseextensionproductisinstalled.Thevalues\nshould todos be o same para each servidor. O value set está dependent on o size\nofthedatabasebeingbackedup.MoreinformationonCLIENT_READ_TIMEOUT\nestá disponível.\nVeja o NetBackup Administrator’s Guide, Volume II.\n■ Make sure que enhanced authentication está configurado correctly. Para example,\nthefollowingmayresultinstatuscode41:HostAisconfiguredtouseenhanced\nauthentication com host B, but host B está não configurado to use enhanced\nauthentication com host Um. In this case, connections from host B to host Um estão\nlikely to fail com status code 41. Connections from host Um to B estão likely to fail\ncom authentication errors (status code 160).\n■ If o Amazon S3 compliant cloud está não able to process o high number de\nrequests, executar one de o seguinte:\n■ Configure o bandwidth throttling to reduce o number de requests. Veja\n\"NetBackup cloud armazenamento servidor conexão properties\" in o NetBackup\nCloud Administrator's Guide.\n■ Reduce o number de read/write buffers. Veja \"NetBackup cloud armazenamento\nserverbandwidththrottlingproperties\"intheNetBackupCloudAdministrator's\nGuide.\n■ Ask seu cloud vendor to aumentar o parallel requests limite.\n■ IfconnectionbetweenthemasterserverandaNATclientfailed,dothefollowing:\n■ Garanta que o subscriber service on o cliente está up e executando.\n■ If o problema persists, restart o cliente services e garanta que o\nsubscriber service está connected com o NetBackup Messaging Broker (ou\nnbmqbroker) service." + "desc": "Network connection timed out NetBackup status codes 127 NetBackup status codes", + "first_action": "If you backup to many files, use Host Properties on the NetBackup server to", + "full_action": "Do the following, as appropriate:\n■ If you backup to many files, use Host Properties on the NetBackup server to\nchangeClientreadtimeouttoamuchhighervalue(forexample:4000).These\nsettings are on the Universal Settings tab in the Master Server Properties\ndialog box. The default for this time out is 300 seconds.\nAlso, set the File browse timeouton the Timeouts tab to a value greater than\n4000.\nThen retry the operation. The names of the files are logged on the debug log\nfile in the /usr/openv/netbackup/logs/bpbkar directory before bpbkar\nprocesses them. The last file in the log is the file that causes problems.\n■ On UNIX, Linux, or Windows clients, check for the following problems with the\nbpbkar client process.\nOn Windows clients:The bpbkar client process is not hung. Due to the files and\ndirectoriesitscans,ithasnotrepliedtotheserverwithintheClientreadtimeout\nperiod. This error occurs during incremental backups when directories have\nthousands of unmodified files.\nFor this case, use Host Properties on the NetBackup server to change Client\nreadtimeout.ThissettingisontheUniversalSettingstabintheMasterServer\nProperties dialog box. The default for this time out is 300 seconds.\nSee \"Using the Host Properties window to access configuration settings\" in the\nNetBackup Troubleshooting Guide.\nYou can also monitor CPU utilization to determine if this condition exists.\nThe following information applies only to UNIX or Linux clients:\n■ Thebpbkarclientprocessishungonafilethathasamandatorylockingset.\nFor this case, add the following to the client’s bp.conf file:\nVERBOSE\nAs root on the client, run the following:\ntouch /usr/openv/netbackup/bpbkar_path_tr\n/usr/openv/netbackup/logs/bpbkar\nThen retry the operation. The names of the files are logged on the debug\nlogfileinthe/usr/openv/netbackup/logs/bpbkardirectorybeforebpbkar\nprocesses them. The last file in the log is the file that causes problems.\nNote: Also, use these procedures for other unknown bpbkar hangs.\nIf the problem is due to mandatory file locking, have NetBackup skip the\nlocked files. Set LOCKED_FILE_ACTION to SKIP in the\n/usr/openv/netbackup/bp.conf file on the client.\n■ The bpbkar client process is not hung. Due to the files and directories it\nscans, it has not replied to the server within CLIENT_READ_TIMEOUT or\nCLIENT_CONNECT_TIMEOUT. This error occurs during backups when\ndirectorieshavethousandsofunmodifiedfilesorduringrestoresofthesparse\nfiles that have thousands of holes. For this case, try to add or modify the\nCLIENT_READ_TIMEOUT value in the server’s\n/usr/openv/netbackup/bp.conf file. The default for\nCLIENT_READ_TIMEOUT is 300 seconds if it is not specified.\nUse your system’s ps command and monitor CPU utilization to help decide\nwhich of these conditions exist.\nWhen you finish the investigation of the problem, delete the\n/usr/openv/netbackup/logs/bpbkardirectory,sincethelogfilescanbecome\nquite large and are not deleted automatically. Also delete\n/usr/openv/netbackup/bpbkar_path_tr so you do not generate larger log\nfiles than needed the next time you create directory\n/usr/openv/netbackup/logs/bpbkar.\n■ On Windows systems, try the following:\n■ Disable the following file:\ninstall_path\\VERITAS\\NetBackup\\bin\\tracker.exe\n■ Repair hard drive fragmentation. Try an application that is called Diskeeper\nLite, which is part of the Windows Resource Kit.\n■ Make sure that enough space is available in \\temp.\n■ If the server cannot connect to the client, create bpcd or bpbkar (UNIX, Linux,\nand Windows only) debug log directories on the client. Then retry the operation\nand check the resulting logs. If these logs do not provide a clue, create a bpbrm\ndebuglogontheserver.Thenretrytheoperationandchecktheresultingdebug\nlog.\nIf the bpbrm log has entries similar to the following, the problem is in the routing\nconfiguration on the server:\nbpbrm hookup_timeout: timed out waiting during the client hookup\nbpbrm Exit: client backup EXIT STATUS 41: network connection\ntimed out\nVerify that the client IP address is correct in the name service that is used. On\nUNIX clients, if both the NIS and the DNS files are used, verify that they match.\nSee \"Resolving network communication problems\" in the NetBackup\nTroubleshooting Guide.\n■ If you use an AIX token ring adapter and the routed daemon is running, the\ntime out occurs because the token ring adapter creates dynamic routes. It then\ncauses the routed daemon to crash.\n■ For a FlashBackup client, this error occurs if the file system being backed up is\nverylargeandhasaverylargenumberoffiles.Itcanalsooccurifalargenumber\nof concurrent data streams are active at the same time. To correct it, add\nCLIENT_READ_TIMEOUTtothe/usr/openv/netbackup/bp.conffileandset\nit to increase the time-out interval.\n■ Check the Cohesity Technical Support website to ensure that all recommended\nNetBackup patches are installed.\n■ Add the CLIENT_READ_TIMEOUT values to the master server, media server,\nandclientwhenaNetBackupdatabaseextensionproductisinstalled.Thevalues\nshould all be the same for each server. The value set is dependent on the size\nofthedatabasebeingbackedup.MoreinformationonCLIENT_READ_TIMEOUT\nis available.\nSee the NetBackup Administrator’s Guide, Volume II.\n■ Make sure that enhanced authentication is configured correctly. For example,\nthefollowingmayresultinstatuscode41:HostAisconfiguredtouseenhanced\nauthentication with host B, but host B is not configured to use enhanced\nauthentication with host A. In this case, connections from host B to host A are\nlikely to fail with status code 41. Connections from host A to B are likely to fail\nwith authentication errors (status code 160).\n■ If the Amazon S3 compliant cloud is not able to process the high number of\nrequests, perform one of the following:\n■ Configure the bandwidth throttling to reduce the number of requests. See\n\"NetBackup cloud storage server connection properties\" in the NetBackup\nCloud Administrator's Guide.\n■ Reduce the number of read/write buffers. See \"NetBackup cloud storage\nserverbandwidththrottlingproperties\"intheNetBackupCloudAdministrator's\nGuide.\n■ Ask your cloud vendor to increase the parallel requests limit.\n■ IfconnectionbetweenthemasterserverandaNATclientfailed,dothefollowing:\n■ Ensure that the subscriber service on the client is up and running.\n■ If the problem persists, restart the client services and ensure that the\nsubscriber service is connected with the NetBackup Messaging Broker (or\nnbmqbroker) service." }, "42": { "code": 42, - "desc": "Rede ler falhou", - "first_action": "Verifique que both o cliente e o servidor estão operational.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Verifique que both o cliente e o servidor estão operational.\n■ Resolve qualquer rede communication problemas.\nVeja \"resolvendo rede communication problemas\" in o NetBackup\nTroubleshooting Guide.\n■ Verifique o Problemas relatório para pistas." + "desc": "Network read failed", + "first_action": "Verify that both the client and the server are operational.", + "full_action": "Do the following, as appropriate:\n■ Verify that both the client and the server are operational.\n■ Resolve any network communication problems.\nSee \"Resolving network communication problems\" in the NetBackup\nTroubleshooting Guide.\n■ Check the Problems report for clues." }, "43": { "code": 43, "desc": "Unexpected message received", "first_action": "Verifythatthecorrectversionofsoftwareisrunningontheclientandtheserver.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Verifythatthecorrectversionofsoftwareisrunningontheclientandtheserver.\n■ To enable detailed debug logging, do o seguinte:\n■ On o servidor, create um bpbrm debug log diretório.\n■ On clients, create um bpcd debug log diretório.\n■ Aumentar o amount de debug informação to include in o logs.\nVeja \"About logs\" in o NetBackup Logging Reference Guide.\n■ Retry o operation e examine o logs.\nIf you use bpstart_notify scripts on UNIX, Linux, ou Windows clients, verifique\nque messages estão não written to stdout ou stderr." + "full_action": "Do the following, as appropriate:\n■ Verifythatthecorrectversionofsoftwareisrunningontheclientandtheserver.\n■ To enable detailed debug logging, do the following:\n■ On the server, create a bpbrm debug log directory.\n■ On clients, create a bpcd debug log directory.\n■ Increase the amount of debug information to include in the logs.\nSee \"About logs\" in the NetBackup Logging Reference Guide.\n■ Retry the operation and examine the logs.\nIf you use bpstart_notify scripts on UNIX, Linux, or Windows clients, verify\nthat messages are not written to stdout or stderr." }, "44": { "code": 44, - "desc": "Rede gravar falhou", - "first_action": "Verifique o Problemas relatório para informação about o erro.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Verifique o Problemas relatório para informação about o erro.\n■ Verifique que o cliente e servers estão operational e connected to o rede.\n■ Create um debug log diretório para o process que reported o problema e o\noperation. Examine o resulting debug log arquivo para detailed troubleshooting\ninformação.\nVeja \"resolvendo rede communication problemas\" in o NetBackup\nTroubleshooting Guide." + "desc": "Network write failed", + "first_action": "Check the Problems report for information about the error.", + "full_action": "Do the following, as appropriate:\n■ Check the Problems report for information about the error.\n■ Verify that the client and servers are operational and connected to the network.\n■ Create a debug log directory for the process that reported the problem and the\noperation. Examine the resulting debug log file for detailed troubleshooting\ninformation.\nSee \"Resolving network communication problems\" in the NetBackup\nTroubleshooting Guide." }, "45": { "code": 45, - "desc": "Request attempted on um non-reserved port", - "first_action": "On UNIX NetBackup servers e clients, verifique o", - "full_action": "Verifique que o latest software está instalado on o cliente e\nservidor.\n■ On UNIX NetBackup servers e clients, verifique o\n/usr/openv/netbackup/bin/version arquivo.\n■ On Windows NetBackup servers, verifique o\ninstall_path\\netbackup\\version.txt arquivo ou o About NetBackup item on\no Help menu.\n■ On Microsoft Windows clients, verifique o About NetBackup item on o Help\nmenu." + "desc": "Request attempted on a non-reserved port", + "first_action": "On UNIX NetBackup servers and clients, check the", + "full_action": "Verify that the latest software is installed on the client and\nserver.\n■ On UNIX NetBackup servers and clients, check the\n/usr/openv/netbackup/bin/version file.\n■ On Windows NetBackup servers, check the\ninstall_path\\netbackup\\version.txt file or the About NetBackup item on\nthe Help menu.\n■ On Microsoft Windows clients, check the About NetBackup item on the Help\nmenu." }, "46": { "code": 46, - "desc": "Servidor não allowed access", - "first_action": "If o servidor está um valid servidor but está não listed on o cliente, add its name to o", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ If o servidor está um valid servidor but está não listed on o cliente, add its name to o\nclient’s servidor list:\n■ On Windows clients in o Specify NetBackup Machines e Policy Type\ndialogbox,dothefollowing:AddtheserverintheServertouseforbackups\ne restores drop-down list. To display this dialog box, start o Backup,\nArchive, e Restauração interface on o cliente. Then click Specify NetBackup\nMachines e Policy Type on o Arquivo menu.\n■ On UNIX e Linux clients, add um Servidor entry in o bp.conf arquivo.\nIf you continue to have problemas, more informação está disponível:\nVeja \"resolvendo rede communication problemas\" in o NetBackup\nTroubleshooting Guide.\nVeja \"Verifying host names e services entradas\" in o NetBackup\nTroubleshooting Guide.\n■ To make non-encrypted backups de o cliente, set CRYPT_OPTION on o cliente\nto allowed ou negada.\nRefer to o NetBackup Security e Encryption Guide.\n■ If o NetBackup encryption evaluation license has expired on o servidor e\nyouwanttocontinueencryptingbackupsoftheclient,dothefollowing:Purchase\num permanent encryption license key e add it to o servidor. After you add o\npermanent encryption license key, verifique o attributes de o backup policy to\nmake sure que encryption está selected.\nTo verifique o validity de um evaluation license key, do o seguinte:\nOn Windows, go to o Help menu on o NetBackup Administration window\non o NetBackup servidor e select License Keys. If o evaluation key está não\nlisted in o NetBackup License Keys window, o key has expired. Use this\nwindow to add o new permanent encryption key.\nOn UNIX, use o seguinte comando on o servidor:\n/usr/openv/netbackup/bin/admincmd/get_license_key\nSelect option f to list o active license keys e features. If o evaluation key\nestá não listed, o key has expired. Use this comando to add o new permanent\nencryption key.\n■ Be sure que todos name resolution services (primary, load-balancing, e\nsecondary) estão properly configurado para consistent forward e reverse name\nresolution de NetBackup hosts.\nMore informação está disponível in o seguinte technical article:\nhttps://www.veritas.com/support/en_US/article.100029136\n■ If o erro occurs during external certificate enrollment, do o seguinte:\n■ Add o servidor name from onde you desejar to enroll o external certificate\npara um remote host in its Servidor configuration option." + "desc": "Server not allowed access", + "first_action": "If the server is a valid server but is not listed on the client, add its name to the", + "full_action": "Do the following, as appropriate:\n■ If the server is a valid server but is not listed on the client, add its name to the\nclient’s server list:\n■ On Windows clients in the Specify NetBackup Machines and Policy Type\ndialogbox,dothefollowing:AddtheserverintheServertouseforbackups\nand restores drop-down list. To display this dialog box, start the Backup,\nArchive, and Restore interface on the client. Then click Specify NetBackup\nMachines and Policy Type on the File menu.\n■ On UNIX and Linux clients, add a SERVER entry in the bp.conf file.\nIf you continue to have problems, more information is available:\nSee \"Resolving network communication problems\" in the NetBackup\nTroubleshooting Guide.\nSee \"Verifying host names and services entries\" in the NetBackup\nTroubleshooting Guide.\n■ To make non-encrypted backups of the client, set CRYPT_OPTION on the client\nto allowed or denied.\nRefer to the NetBackup Security and Encryption Guide.\n■ If the NetBackup encryption evaluation license has expired on the server and\nyouwanttocontinueencryptingbackupsoftheclient,dothefollowing:Purchase\na permanent encryption license key and add it to the server. After you add the\npermanent encryption license key, check the attributes of the backup policy to\nmake sure that encryption is selected.\nTo check the validity of an evaluation license key, do the following:\nOn Windows, go to the Help menu on the NetBackup Administration window\non the NetBackup server and select License Keys. If the evaluation key is not\nlisted in the NetBackup License Keys window, the key has expired. Use this\nwindow to add the new permanent encryption key.\nOn UNIX, use the following command on the server:\n/usr/openv/netbackup/bin/admincmd/get_license_key\nSelect option f to list the active license keys and features. If the evaluation key\nis not listed, the key has expired. Use this command to add the new permanent\nencryption key.\n■ Be sure that all name resolution services (primary, load-balancing, and\nsecondary) are properly configured for consistent forward and reverse name\nresolution of NetBackup hosts.\nMore information is available in the following technical article:\nhttps://www.veritas.com/support/en_US/article.100029136\n■ If the error occurs during external certificate enrollment, do the following:\n■ Add the server name from where you want to enroll the external certificate\nfor a remote host in its SERVER configuration option." }, "47": { "code": 47, - "desc": "Host/Servidor de destino inacessível", - "first_action": "Verifique que o name service (ou services) used por o cliente estão configurado to", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Verifique que o name service (ou services) used por o cliente estão configurado to\nresolve o host names de o NetBackup servidor correctly.\n■ Verifique que o name service (ou services) used por o servidor estão configurado to\nresolve o host name de o NetBackup cliente correctly.\n■ Try to ping o cliente from o servidor e o servidor from o cliente.\n■ If you continue to have problemas, do o seguinte:\nVeja \"resolvendo rede communication problemas\" in o NetBackup\nTroubleshooting Guide." + "desc": "Host is unreachable", + "first_action": "Verify that the name service (or services) used by the client are configured to", + "full_action": "Do the following, as appropriate:\n■ Verify that the name service (or services) used by the client are configured to\nresolve the host names of the NetBackup server correctly.\n■ Verify that the name service (or services) used by the server are configured to\nresolve the host name of the NetBackup client correctly.\n■ Try to ping the client from the server and the server from the client.\n■ If you continue to have problems, do the following:\nSee \"Resolving network communication problems\" in the NetBackup\nTroubleshooting Guide." }, "48": { "code": 48, - "desc": "Cliente host name could não be found", - "first_action": "O NetBackup policy configuration on o master servidor.", - "full_action": "Verifique que o cliente name está correct in o seguinte:\n■ O NetBackup policy configuration on o master servidor.\n■ O General tab in o seguinte dialog boxes: NetBackup Cliente Properties\ne Specify NetBackup Machines e Policy Type (on Microsoft Windows\nnon-target clients). To display these dialog boxes, start o Backup, Archive,\nandRestoreinterfaceontheclient.FortheGeneraltab,clickNetBackupClient\nProperties on o Arquivo menu; click Specify NetBackup Machines e Policy\nType on o Arquivo menu.\n■ O bp.conf arquivo on UNIX e Linux clients.\n■ On clients e servers, verifique que o name service está set up to resolve o\nNetBackup cliente names correctly.\nOn UNIX clients, verifique que o client’s host name está in o /etc/hosts arquivo ou\no YP hosts arquivo ou NIS maps.\n■ O cliente name reflects um host onde o NetBackup cliente está instalado.\nNetBackupdoesnotcollectlogsfromanyagentlesshostswheretheNetBackup\ncliente está não instalado. Para agentless hosts, o erro log displays o seguinte\nmessage: Falhou to collect logs (EC: 48 - Cliente hostname could\nnão be found)." + "desc": "Client host name could not be found", + "first_action": "The NetBackup policy configuration on the master server.", + "full_action": "Verify that the client name is correct in the following:\n■ The NetBackup policy configuration on the master server.\n■ The General tab in the following dialog boxes: NetBackup Client Properties\nand Specify NetBackup Machines and Policy Type (on Microsoft Windows\nnon-target clients). To display these dialog boxes, start the Backup, Archive,\nandRestoreinterfaceontheclient.FortheGeneraltab,clickNetBackupClient\nProperties on the File menu; click Specify NetBackup Machines and Policy\nType on the File menu.\n■ The bp.conf file on UNIX and Linux clients.\n■ On clients and servers, verify that the name service is set up to resolve the\nNetBackup client names correctly.\nOn UNIX clients, verify that the client’s host name is in the /etc/hosts file or\nthe YP hosts file or NIS maps.\n■ The client name reflects a host where the NetBackup client is installed.\nNetBackupdoesnotcollectlogsfromanyagentlesshostswheretheNetBackup\nclient is not installed. For agentless hosts, the error log displays the following\nmessage: Failed to collect logs (EC: 48 - Client hostname could\nnot be found)." }, "49": { "code": 49, - "desc": "Cliente did não start", - "first_action": "Make sure que software está instalado on o cliente e it está o correct version. If", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Make sure que software está instalado on o cliente e it está o correct version. If\nnecessary, reinstall o cliente software.\n■ Verifique para cheio arquivo systems on o cliente.\n■ Enable detailed debug logging on o cliente por doing one de o seguinte:\n■ Create bpcd e bpbkar (UNIX, Linux, e Windows apenas) debug log\ndirectories.\n■ On um UNIX ou Linux cliente, add o VERBOSE option to o\n/usr/openv/netbackup/bp.conf arquivo.\n■ On Windows clients, aumentar o debug ou log level.\nVeja \"Changing o logging level on Windows clients\" in o NetBackup\nLogging Reference Guide.\nRetry o operation e examine o resulting logs.\n■ On UNIX ou Linux systems, use o UNIX sum comando to verifique para corrupt\nbinaries." + "desc": "Client did not start", + "first_action": "Make sure that software is installed on the client and it is the correct version. If", + "full_action": "Do the following, as appropriate:\n■ Make sure that software is installed on the client and it is the correct version. If\nnecessary, reinstall the client software.\n■ Check for full file systems on the client.\n■ Enable detailed debug logging on the client by doing one of the following:\n■ Create bpcd and bpbkar (UNIX, Linux, and Windows only) debug log\ndirectories.\n■ On a UNIX or Linux client, add the VERBOSE option to the\n/usr/openv/netbackup/bp.conf file.\n■ On Windows clients, increase the debug or log level.\nSee \"Changing the logging level on Windows clients\" in the NetBackup\nLogging Reference Guide.\nRetry the operation and examine the resulting logs.\n■ On UNIX or Linux systems, use the UNIX sum command to check for corrupt\nbinaries." }, "50": { "code": 50, - "desc": "Cliente process aborted", + "desc": "Client process aborted", "first_action": "Enable detailed debug logging.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Enable detailed debug logging.\n■ Create um bpbkar debug log diretório (UNIX, Linux, e Windows clients\napenas).\n■ Create um bpcd debug log diretório.\n■ On UNIX clients, add o VERBOSE option to o\n/usr/openv/netbackup/bp.conf arquivo.\n■ On PC clients, aumentar o debug ou o log level.\nVeja \"Changing o logging level on Windows clients\" in o NetBackup\nLogging Reference Guide.\nRetry o operation e examine o resulting logs.\n■ Thiserrormayoccurifnbjmterminatedwhileabackupjobwasrunning.Examine\no unified logging arquivos on o NetBackup servidor para nbjm (117) para more detail\non o erro. Todos unified logging está written to /usr/openv/logs (UNIX) ou\ninstall_path\\NetBackup\\logs (Windows).\n■ On UNIX clients, verifique para core arquivos in o / diretório.\n■ On UNIX clients, verifique o system log (/usr/adm/messages on Solaris) para\nsystem problemas.\n■ This problema can sometimes be due to um corrupt binary.\nOn UNIX clients, use o UNIX sum comando to verifique o bpcd, bpbkar, e\ntar binaries, which estão located in /usr/openv/netbackup/bin on o cliente.\nReinstall them if they estão não o same como in o cliente diretório under\n/usr/openv/netbackup/client on o servidor.\nOn um Windows cliente, verifique o bpinetd.exe, bpcd.exe, bpbkar32.exe, e\ntar32.exe arquivos, which estão located in o install_path\\NetBackup\\bin folder\non o cliente.\nReinstall o cliente if these arquivos estão como follows:\n■ Não o same size como on other Windows clients.\n■ Não at o same release level.\n■ Do não have o same NetBackup patches como other Windows clients.\n■ ReviewthefollowingwhenNetBackupisdeployedonaKubernetesdeployment:\n■ Verifique o number de pending pods. Post que to garanta que o issue\nocorreu due to o node pool level max pods setting, e verifique if o\nworkflow runner ou data mover pods estão in pending state. Excluir o node\npool e recreate o node pool com appropriate number to max pods usando\no seguinte formula:\n■ MAX pods per node = (RAM size * 2) + number de kube-system pods[10]\n+ Não de nodes + 2\n■ Verifique o number de pending pods. Post que to garanta que there estão sufficient\nnumberoffreeIPsareavailable.Theadministratorneedstoensurethatsufficient\nnumber de IPs estão disponível." + "full_action": "Do the following, as appropriate:\n■ Enable detailed debug logging.\n■ Create a bpbkar debug log directory (UNIX, Linux, and Windows clients\nonly).\n■ Create a bpcd debug log directory.\n■ On UNIX clients, add the VERBOSE option to the\n/usr/openv/netbackup/bp.conf file.\n■ On PC clients, increase the debug or the log level.\nSee \"Changing the logging level on Windows clients\" in the NetBackup\nLogging Reference Guide.\nRetry the operation and examine the resulting logs.\n■ Thiserrormayoccurifnbjmterminatedwhileabackupjobwasrunning.Examine\nthe unified logging files on the NetBackup server for nbjm (117) for more detail\non the error. All unified logging is written to /usr/openv/logs (UNIX) or\ninstall_path\\NetBackup\\logs (Windows).\n■ On UNIX clients, check for core files in the / directory.\n■ On UNIX clients, check the system log (/usr/adm/messages on Solaris) for\nsystem problems.\n■ This problem can sometimes be due to a corrupt binary.\nOn UNIX clients, use the UNIX sum command to check the bpcd, bpbkar, and\ntar binaries, which are located in /usr/openv/netbackup/bin on the client.\nReinstall them if they are not the same as in the client directory under\n/usr/openv/netbackup/client on the server.\nOn a Windows client, check the bpinetd.exe, bpcd.exe, bpbkar32.exe, and\ntar32.exe files, which are located in the install_path\\NetBackup\\bin folder\non the client.\nReinstall the client if these files are as follows:\n■ Not the same size as on other Windows clients.\n■ Not at the same release level.\n■ Do not have the same NetBackup patches as other Windows clients.\n■ ReviewthefollowingwhenNetBackupisdeployedonaKubernetesdeployment:\n■ Check the number of pending pods. Post that to ensure that the issue\noccurred due to the node pool level max pods setting, and check if the\nworkflow runner or data mover pods are in pending state. Delete the node\npool and recreate the node pool with appropriate number to max pods using\nthe following formula:\n■ MAX pods per node = (RAM size * 2) + number of kube-system pods[10]\n+ No of nodes + 2\n■ Check the number of pending pods. Post that to ensure that there are sufficient\nnumberoffreeIPsareavailable.Theadministratorneedstoensurethatsufficient\nnumber of IPs are available." }, "51": { "code": 51, - "desc": "Esgotado fora waiting para banco de dados informação", - "first_action": "Verifique que o NetBackup Banco de dados Manager, bpdbm, está executando.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Verifique que o NetBackup Banco de dados Manager, bpdbm, está executando.\n■ Verifique que o arquivo system que contains o NetBackup catalogs has enough\nspace.\n■ Create bpbrm e bpdbm debug log directories on o servidor e retry o\noperation.\n■ Look in o debug log arquivos to find more informação on o problema." + "desc": "Timed out waiting for database information", + "first_action": "Verify that the NetBackup Database Manager, bpdbm, is running.", + "full_action": "Do the following, as appropriate:\n■ Verify that the NetBackup Database Manager, bpdbm, is running.\n■ Verify that the file system that contains the NetBackup catalogs has enough\nspace.\n■ Create bpbrm and bpdbm debug log directories on the server and retry the\noperation.\n■ Look in the debug log files to find more information on the problem." }, "52": { "code": 52, - "desc": "Esgotado fora waiting para mídia manager to mount volume", - "first_action": "Verifique que o solicitado volume está disponível e um appropriate drive está ready", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Verifique que o solicitado volume está disponível e um appropriate drive está ready\ne in o UP state.\n■ If this erro occurs during um ler operation (restauração, duplicate, verifique), o drives\ncould be ocupado. Aumentar o tempo limite esgotado para o mídia mount que o NetBackup\nglobal attribute specifies, to allow more time to mount e position o mídia.\n■ Verifique que o tape está não um cleaning tape que está configurado como um regular volume.\n■ WhenanAutomatedCartridgeSystemcontrolstherobot,verifythattheACSLS\nsystem está up.\n■ If it está um initial installation, um procedure está disponível.\nSee\"Troubleshootingconfigurationproblems\"intheNetBackupTroubleshooting\nGuide.\n■ On Windows, verifique o Event Viewer Application log para o erro messages\nque indicate por que o tape mount did não complete. On UNIX, verifique o system\nlog." + "desc": "Timed out waiting for media manager to mount volume", + "first_action": "Verify that the requested volume is available and an appropriate drive is ready", + "full_action": "Do the following, as appropriate:\n■ Verify that the requested volume is available and an appropriate drive is ready\nand in the UP state.\n■ If this error occurs during a read operation (restore, duplicate, verify), the drives\ncould be busy. Increase the timeout for the media mount that the NetBackup\nglobal attribute specifies, to allow more time to mount and position the media.\n■ Verify that the tape is not a cleaning tape that is configured as a regular volume.\n■ WhenanAutomatedCartridgeSystemcontrolstherobot,verifythattheACSLS\nsystem is up.\n■ If it is an initial installation, a procedure is available.\nSee\"Troubleshootingconfigurationproblems\"intheNetBackupTroubleshooting\nGuide.\n■ On Windows, check the Event Viewer Application log for the error messages\nthat indicate why the tape mount did not complete. On UNIX, check the system\nlog." }, "53": { "code": 53, - "desc": "Backup restauração manager falhou to ler o arquivo list", - "first_action": "Create bpbrm debug log directories on o servidor.", - "full_action": "Verifique que o servidor software foi instalado correctly on\ntodos NetBackup servers. If que está não o problema, do o seguinte:\n■ Create bpbrm debug log directories on o servidor.\n■ On um UNIX ou Linux NetBackup servidor, add o VERBOSE option to o bp.conf\narquivo. On um Windows NetBackup servidor, set o Global logging level option on\no Logging tab in o Master Servidor Properties dialog box.\nTo display this dialog box, refer to o seguinte topic:\nVeja \"usando o Host Properties window to access configuration settings\" in o\nNetBackup Troubleshooting Guide.\nIncreasetheunifiedlogginglevelsbyusingthevxlogcfgcommandasexplained\nin o seguinte procedure:\nVeja \"About unified logging\" in o NetBackup Logging Reference Guide.\n■ Retry o operation e verifique o resulting debug logs para detailed\ntroubleshooting informação." + "desc": "Backup restore manager failed to read the file list", + "first_action": "Create bpbrm debug log directories on the server.", + "full_action": "Verify that the server software was installed correctly on\nall NetBackup servers. If that is not the problem, do the following:\n■ Create bpbrm debug log directories on the server.\n■ On a UNIX or Linux NetBackup server, add the VERBOSE option to the bp.conf\nfile. On a Windows NetBackup server, set the Global logging level option on\nthe Logging tab in the Master Server Properties dialog box.\nTo display this dialog box, refer to the following topic:\nSee \"Using the Host Properties window to access configuration settings\" in the\nNetBackup Troubleshooting Guide.\nIncreasetheunifiedlogginglevelsbyusingthevxlogcfgcommandasexplained\nin the following procedure:\nSee \"About unified logging\" in the NetBackup Logging Reference Guide.\n■ Retry the operation and check the resulting debug logs for detailed\ntroubleshooting information." }, "54": { "code": 54, - "desc": "Esgotado fora connecting to cliente", - "first_action": "Executar o seguinte procedure:", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Executar o seguinte procedure:\nVeja \"resolvendo rede communication problemas\" in o NetBackup\nTroubleshooting Guide.\nVeja \"resolvendo rede communication problemas\" in o NetBackup\nTroubleshooting Guide.\n■ OnUNIXclients,verifythatthe/usr/openv/netbackup/bin/bpcdbinaryexists\ne que it está o correct size.\n■ Verifique o /etc/inetd.conf arquivo to make sure o bpcd caminho está correct in o\nseguinte entry:\nbpcd stream tcp nowait raiz /usr/openv/netbackup/bin/bpcd bpcd\n■ On o systems que include o seguinte, make sure que o cliente name está in\no master’s /etc/hosts arquivo: NetBackup master, mídia, e clients (com\nNetBackup banco de dados extension products instalado on one ou more clients).\n■ Completely uninstall o third-party software package on o cliente que causes\no falha. Ou, contate o software manufacturer to investigate if other\nconfiguration options ou workarounds estão possible." + "desc": "Timed out connecting to client", + "first_action": "Perform the following procedure:", + "full_action": "Do the following, as appropriate:\n■ Perform the following procedure:\nSee \"Resolving network communication problems\" in the NetBackup\nTroubleshooting Guide.\nSee \"Resolving network communication problems\" in the NetBackup\nTroubleshooting Guide.\n■ OnUNIXclients,verifythatthe/usr/openv/netbackup/bin/bpcdbinaryexists\nand that it is the correct size.\n■ Check the /etc/inetd.conf file to make sure the bpcd path is correct in the\nfollowing entry:\nbpcd stream tcp nowait root /usr/openv/netbackup/bin/bpcd bpcd\n■ On the systems that include the following, make sure that the client name is in\nthe master’s /etc/hosts file: NetBackup master, media, and clients (with\nNetBackup database extension products installed on one or more clients).\n■ Completely uninstall the third-party software package on the client that causes\nthe failure. Or, contact the software manufacturer to investigate if other\nconfiguration options or workarounds are possible." }, "55": { "code": 55, - "desc": "Permissão negada por cliente during rcmd", - "first_action": "Add o servidor name to o /.rhosts arquivo on o UNIX ou", - "full_action": "Add o servidor name to o /.rhosts arquivo on o UNIX ou\nLinux cliente." + "desc": "Permission denied by client during rcmd", + "first_action": "Add the server name to the /.rhosts file on the UNIX or", + "full_action": "Add the server name to the /.rhosts file on the UNIX or\nLinux client." }, "56": { "code": 56, - "desc": "Client’s rede está unreachable", + "desc": "Client’s network is unreachable", "first_action": "Trytopingtheclientfromtheserver.ChecktheIPaddress", - "full_action": "Trytopingtheclientfromtheserver.ChecktheIPaddress\npara o cliente. If you still have problemas, talk to seu rede administrator." + "full_action": "Trytopingtheclientfromtheserver.ChecktheIPaddress\nfor the client. If you still have problems, talk to your network administrator." }, "57": { "code": 57, - "desc": "Conexão com o cliente recusada", - "first_action": "Para Windows NetBackup servers:", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Para Windows NetBackup servers:\n■ Make sure o NetBackup cliente software está instalado.\n■ Verifique que o bpcd e bprd port numbers in o\n%SystemRoot%\\system32\\drivers\\etc\\servicesfileontheservermatches\no setting on o cliente.\n■ Verifique que o NetBackup Cliente Service Port number e NetBackup\nRequestServicePortnumberontheNetworktabintheNetBackupClient\nProperties dialog match o bpcd e bprd settings in o services arquivo. To\ndisplay this dialog, start o Backup, Archive, e Restauração interface on o\nservidor e click NetBackup Cliente Properties on o Arquivo menu.\nO values on o Rede tab estão written to o services arquivo when o\nNetBackup Cliente service starts.\n■ Verifique que o NetBackup cliente service está executando.\n■ Use o seguinte comando to veja if o master servidor returns correct\ninformação para o cliente:\ninstall_path\\VERITAS\\NetBackup\\bin\\bpclntcmd -pn\n■ On UNIX servers, do o seguinte:\n■ Make sure o NetBackup cliente software está instalado.\n■ Verifique que o bpcd port number on o servidor (either NIS services map ou\nin /etc/services) matches o number in o client’s services arquivo.\n■ Additional help está disponível.\nVeja \"resolvendo rede communication problemas\" in o NetBackup\nTroubleshooting Guide." + "desc": "Client connection refused", + "first_action": "For Windows NetBackup servers:", + "full_action": "Do the following, as appropriate:\n■ For Windows NetBackup servers:\n■ Make sure the NetBackup client software is installed.\n■ Verify that the bpcd and bprd port numbers in the\n%SystemRoot%\\system32\\drivers\\etc\\servicesfileontheservermatches\nthe setting on the client.\n■ Verify that the NetBackup Client Service Port number and NetBackup\nRequestServicePortnumberontheNetworktabintheNetBackupClient\nProperties dialog match the bpcd and bprd settings in the services file. To\ndisplay this dialog, start the Backup, Archive, and Restore interface on the\nserver and click NetBackup Client Properties on the File menu.\nThe values on the Network tab are written to the services file when the\nNetBackup Client service starts.\n■ Verify that the NetBackup client service is running.\n■ Use the following command to see if the master server returns correct\ninformation for the client:\ninstall_path\\VERITAS\\NetBackup\\bin\\bpclntcmd -pn\n■ On UNIX servers, do the following:\n■ Make sure the NetBackup client software is installed.\n■ Verify that the bpcd port number on the server (either NIS services map or\nin /etc/services) matches the number in the client’s services file.\n■ Additional help is available.\nSee \"Resolving network communication problems\" in the NetBackup\nTroubleshooting Guide." }, "58": { "code": 58, - "desc": "Can’t conectar to cliente", - "first_action": "Resolve rede communication problemas.", - "full_action": "Resolve rede communication problemas.\nSee\"Resolvingnetworkcommunicationproblems\"intheNetBackupTroubleshooting\nGuide.\nWhen usando Hadoop ou HBase, verifique que o application servidor port number está\nupdated correctly when usando o tpconfig comando." + "desc": "Can’t connect to client", + "first_action": "Resolve network communication problems.", + "full_action": "Resolve network communication problems.\nSee\"Resolvingnetworkcommunicationproblems\"intheNetBackupTroubleshooting\nGuide.\nWhen using Hadoop or HBase, verify that the application server port number is\nupdated correctly when using the tpconfig command." }, "59": { "code": 59, - "desc": "Access to o cliente foi não allowed", - "first_action": "If o servidor está um valid servidor, verifique que it está in o servidor list on o cliente. If", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ If o servidor está um valid servidor, verifique que it está in o servidor list on o cliente. If\nnecessary add it como follows:\n■ On Windows clients: Add o servidor on o Servidor to use para backups e\nrestoresdrop-downintheSpecifyNetBackupMachinesandPolicyType\ndialogbox.Todisplaythisdialogbox,starttheBackup,Archive,andRestore\ninterfaceontheclient.ThenclickSpecifyNetBackupMachinesandPolicy\nType on o Arquivo menu.\n■ On UNIX clients: Add um Servidor entry in o bp.conf arquivo.\nIf you change o servidor list on um UNIX ou Linux master servidor, do o seguinte\npara o changes to take effect: Stop e then restart o NetBackup Request\nDaemon (bprd) e NetBackup Banco de dados Manager Daemon (bpdbm). On\nWindows, stop e restart o NetBackup Request Manager e NetBackup\nBanco de dados Manager services.\n■ On Windows clients, enable bpinetd debug logging como follows:\n■ Create um bpinetd debug log diretório on o cliente.\n■ Aumentar o debug ou log level.\nVeja \"Changing o logging level on Windows clients\" in o NetBackup\nLogging Reference Guide.\n■ Retry o backup e examine o resulting logs to determinar o cause de\no falha.\n■ On todos clients, enable bpcd debug logging como follows:\n■ Create um bpcd debug log diretório on o cliente.\n■ On um UNIX ou Linux cliente, add o VERBOSE option to o\n/usr/openv/netbackup/bp.conf arquivo.\n■ On PC clients, aumentar o debug ou log level como explained in o debug log\ntopics in Chapter 3.\n■ Retry o backup e examine o resulting logs to determinar o cause de\no falha.\n■ Verifique o bpcd debug log to determinar o server’s peer name e what\ncomparisons estão made.\nO bpcd process compares NetBackup servidor list entradas to o peer name de\no servidor que tries o conexão. It rejects o conexão if o names estão\ndifferent. If necessary, change o servidor list entry on o cliente to match o\npeer name.\n■ On Windows clients, verifique o seguinte:\n■ Verifique que NetBackup para Windows software foi instalado under um Windows\nadministrator account.\nIf NetBackup está under another type de account, reinstall it under um\nadministrator account. O installation completes successfully under um\nnon-administrator account except para o seguinte: O NetBackup Cliente\nservice está não added to Windows e o NetBackup servidor não é possível access\no cliente.\n■ Verifique que o Windows TCP/IP service specifies o domain servidor que\nresolves names para o subnet que contains o NetBackup servers.\nUNIX, Linux, e Windows clients estão frequently não on o same subnet\ne use different domain servers. When this condition exists, NetBackup\nserversandWindowsclientsmaybeabletopingoneanother,buttheserver\nstill não é possível access o Windows cliente.\n■ O preceding items may não resolve this problema.\nVeja \"resolvendo rede communication problemas\" in o NetBackup\nTroubleshooting Guide.\n■ If NetBackup use multiple rede interfaces com mídia servers, make sure\nthattheinterfacenamesappearintheclient’s/usr/openv/netbackup/bp.conf\narquivo.\n■ Para o Enterprise Vault Agent: Veja o Troubleshooting section de o\nNetBackup para Enterprise Vault Agent Administrator’s Guide.\n■ Be sure que todos name resolution services (primary, load-balancing, e\nsecondary) estão properly configurado para consistent forward e reverse name\nresolution de NetBackup hosts.\nMore informação está disponível in o seguinte technical article:\nhttps://www.veritas.com/support/en_US/article.100029136" + "desc": "Access to the client was not allowed", + "first_action": "If the server is a valid server, verify that it is in the server list on the client. If", + "full_action": "Do the following, as appropriate:\n■ If the server is a valid server, verify that it is in the server list on the client. If\nnecessary add it as follows:\n■ On Windows clients: Add the server on the Server to use for backups and\nrestoresdrop-downintheSpecifyNetBackupMachinesandPolicyType\ndialogbox.Todisplaythisdialogbox,starttheBackup,Archive,andRestore\ninterfaceontheclient.ThenclickSpecifyNetBackupMachinesandPolicy\nType on the File menu.\n■ On UNIX clients: Add a SERVER entry in the bp.conf file.\nIf you change the server list on a UNIX or Linux master server, do the following\nfor the changes to take effect: Stop and then restart the NetBackup Request\nDaemon (bprd) and NetBackup Database Manager Daemon (bpdbm). On\nWindows, stop and restart the NetBackup Request Manager and NetBackup\nDatabase Manager services.\n■ On Windows clients, enable bpinetd debug logging as follows:\n■ Create a bpinetd debug log directory on the client.\n■ Increase the debug or log level.\nSee \"Changing the logging level on Windows clients\" in the NetBackup\nLogging Reference Guide.\n■ Retry the backup and examine the resulting logs to determine the cause of\nthe failure.\n■ On all clients, enable bpcd debug logging as follows:\n■ Create a bpcd debug log directory on the client.\n■ On a UNIX or Linux client, add the VERBOSE option to the\n/usr/openv/netbackup/bp.conf file.\n■ On PC clients, increase the debug or log level as explained in the debug log\ntopics in Chapter 3.\n■ Retry the backup and examine the resulting logs to determine the cause of\nthe failure.\n■ Check the bpcd debug log to determine the server’s peer name and what\ncomparisons are made.\nThe bpcd process compares NetBackup server list entries to the peer name of\nthe server that tries the connection. It rejects the connection if the names are\ndifferent. If necessary, change the server list entry on the client to match the\npeer name.\n■ On Windows clients, check the following:\n■ Verify that NetBackup for Windows software was installed under a Windows\nadministrator account.\nIf NetBackup is under another type of account, reinstall it under an\nadministrator account. The installation completes successfully under a\nnon-administrator account except for the following: The NetBackup Client\nservice is not added to Windows and the NetBackup server cannot access\nthe client.\n■ Verify that the Windows TCP/IP service specifies the domain server that\nresolves names for the subnet that contains the NetBackup servers.\nUNIX, Linux, and Windows clients are frequently not on the same subnet\nand use different domain servers. When this condition exists, NetBackup\nserversandWindowsclientsmaybeabletopingoneanother,buttheserver\nstill cannot access the Windows client.\n■ The preceding items may not resolve this problem.\nSee \"Resolving network communication problems\" in the NetBackup\nTroubleshooting Guide.\n■ If NetBackup use multiple network interfaces with media servers, make sure\nthattheinterfacenamesappearintheclient’s/usr/openv/netbackup/bp.conf\nfile.\n■ For the Enterprise Vault Agent: See the Troubleshooting section of the\nNetBackup for Enterprise Vault Agent Administrator’s Guide.\n■ Be sure that all name resolution services (primary, load-balancing, and\nsecondary) are properly configured for consistent forward and reverse name\nresolution of NetBackup hosts.\nMore information is available in the following technical article:\nhttps://www.veritas.com/support/en_US/article.100029136" }, "60": { "code": 60, - "desc": "Cliente não é possível ler o mount table NetBackup status codes 144 NetBackup status codes", - "first_action": "Run um df to veja if o system can ler o mount table.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Run um df to veja if o system can ler o mount table.\n■ On um SCO system, code 60 can occur because o mount-point caminho name\nexceeds 31 characters (o maximum number on um SCOsystem). O bpbkar\ndebug log on o cliente shows um message similar to o seguinte:\nbpbkar build_nfs_list: FTL - não é possível statfs net Errno: 42406\nTo eliminate these errors para future backups, create um mount point com um shorter\nname e symbolically link o long name to o short name.\n■ Para detailed troubleshooting informação, create um bpbkar debug log diretório.\nThen retry o operation e verifique o resulting log." + "desc": "Client cannot read the mount table NetBackup status codes 144 NetBackup status codes", + "first_action": "Run a df to see if the system can read the mount table.", + "full_action": "Do the following, as appropriate:\n■ Run a df to see if the system can read the mount table.\n■ On an SCO system, code 60 can occur because the mount-point path name\nexceeds 31 characters (the maximum number on an SCOsystem). The bpbkar\ndebug log on the client shows a message similar to the following:\nbpbkar build_nfs_list: FTL - cannot statfs net Errno: 42406\nTo eliminate these errors for future backups, create a mount point with a shorter\nname and symbolically link the long name to the short name.\n■ For detailed troubleshooting information, create a bpbkar debug log directory.\nThen retry the operation and check the resulting log." }, "61": { "code": 61, - "desc": "O vnetd proxy encontrado um erro", - "first_action": "Verbose ou debug output from o comando.", - "full_action": "Examineoneofthefollowingfora76xxcodethatprecedes\no status code 61, e then look up o explanation para que 76xx code:\n■ Verbose ou debug output from o comando.\n■ O Detailed Status de o Job Details in o NetBackup Administration\nConsole.\n■ O log arquivo para o comando ou process que reported o status 61.\nPara more informação, review this technical article:\nhttps://www.veritas.com/support/en_US/article.100039945" + "desc": "The vnetd proxy encountered an error", + "first_action": "Verbose or debug output from the command.", + "full_action": "Examineoneofthefollowingfora76xxcodethatprecedes\nthe status code 61, and then look up the explanation for that 76xx code:\n■ Verbose or debug output from the command.\n■ The Detailed Status of the Job Details in the NetBackup Administration\nConsole.\n■ The log file for the command or process that reported the status 61.\nFor more information, review this technical article:\nhttps://www.veritas.com/support/en_US/article.100039945" }, "63": { "code": 63, - "desc": "Process foi killed por um signal", + "desc": "Process was killed by a signal", "first_action": "Theusualcauseforthiserroristhatsomeoneintentionally", - "full_action": "Theusualcauseforthiserroristhatsomeoneintentionally\nterminated um backup." + "full_action": "Theusualcauseforthiserroristhatsomeoneintentionally\nterminated a backup." }, "64": { "code": 64, - "desc": "Esgotado fora waiting para o cliente backup to start", - "first_action": "On todos clients, enable bpcd debug logging como follows:", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ On todos clients, enable bpcd debug logging como follows:\n■ Create um bpcd debug log diretório on o cliente.\n■ On um UNIX ou Linux cliente, add o VERBOSE option to o\n/usr/openv/netbackup/bp.conf arquivo.\n■ On PC clients, aumentar o debug ou log level.\nVeja \"Changing o logging level on Windows clients\" in o NetBackup\nLogging Reference Guide.\n■ On um UNIX, Linux, ou Windows cliente, create o bpbkar debug log diretório on\no cliente.\n■ On Windows clients, verifique que o NetBackup Cliente service está executando.\n■ On um UNIX ou Linux cliente, use o ps comando to verifique para um cliente process\nque uses too much CPU time.\n■ Retry o backup e examine o debug logs para pistas on o cause de o\nfalha." + "desc": "Timed out waiting for the client backup to start", + "first_action": "On all clients, enable bpcd debug logging as follows:", + "full_action": "Do the following, as appropriate:\n■ On all clients, enable bpcd debug logging as follows:\n■ Create a bpcd debug log directory on the client.\n■ On a UNIX or Linux client, add the VERBOSE option to the\n/usr/openv/netbackup/bp.conf file.\n■ On PC clients, increase the debug or log level.\nSee \"Changing the logging level on Windows clients\" in the NetBackup\nLogging Reference Guide.\n■ On a UNIX, Linux, or Windows client, create the bpbkar debug log directory on\nthe client.\n■ On Windows clients, verify that the NetBackup Client service is running.\n■ On a UNIX or Linux client, use the ps command to check for a client process\nthat uses too much CPU time.\n■ Retry the backup and examine the debug logs for clues on the cause of the\nfailure." }, "65": { "code": 65, "desc": "Clienttimedoutwaitingforthecontinuemessagefromthemediamanager", - "first_action": "Create um bptm debug log diretório on o servidor.", - "full_action": "Verifique que o solicitado volume está disponível e o\nrequerido dispositivo está in um UP state.\n■ Create um bptm debug log diretório on o servidor.\n■ On um UNIX ou Linux NetBackup servidor, add o VERBOSE option to o bp.conf\narquivo. On um Windows NetBackup servidor, set o Verbose logging level option\non o Logging tab in o Master Servidor Properties dialog box.\nVeja \"usando o Host Properties window to access configuration settings\" in o\nNetBackup Troubleshooting Guide.\n■ Retry o operation e verifique o bptm debug log arquivo para informação on o\ndrive, robot, e tape que causes o tempo limite esgotado.\n■ On um Windows NetBackup servidor (master ou mídia): verifique o Event Viewer\nApplication log para o erro messages que indicate por que o tape mount did não\ncomplete." + "first_action": "Create a bptm debug log directory on the server.", + "full_action": "Verify that the requested volume is available and the\nrequired device is in an UP state.\n■ Create a bptm debug log directory on the server.\n■ On a UNIX or Linux NetBackup server, add the VERBOSE option to the bp.conf\nfile. On a Windows NetBackup server, set the Verbose logging level option\non the Logging tab in the Master Server Properties dialog box.\nSee \"Using the Host Properties window to access configuration settings\" in the\nNetBackup Troubleshooting Guide.\n■ Retry the operation and check the bptm debug log file for information on the\ndrive, robot, and tape that causes the timeout.\n■ On a Windows NetBackup server (master or media): check the Event Viewer\nApplication log for the error messages that indicate why the tape mount did not\ncomplete." }, "66": { "code": 66, - "desc": "Cliente backup falhou to receive o CONTINUE BACKUP message", - "first_action": "Verifique que o servidor did não crash.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Verifique que o servidor did não crash.\n■ On UNIX, Linux, e Windows clients, enable bpbkar debug logging.\n■ Create um bpbkar debug log diretório.\n■ On um UNIX ou Linux cliente, add o VERBOSE option to o bp.conf arquivo. On um\nWindowsclient,setVerboseontheTroubleShootingtabintheNetBackup\nCliente Properties dialog box. To display this dialog box, start o Backup,\nArchive, e Restauração interface on o cliente. Then select NetBackup Cliente\nProperties from o Arquivo menu.\n■ On other PC clients, create um debug log diretório para bpcd.\nAumentar o amount de informação que appears in o logs.\nSee\"Changingthelogginglevel on Windowsclients\"in theNetBackupLogging\nReference Guide.\n■ Use o vxlogcfg comando como described in o seguinte topic:\nVeja \"About unified logging\" in o NetBackup Logging Reference Guide.\n■ Retry o operation e verifique o resulting debug logs." + "desc": "Client backup failed to receive the CONTINUE BACKUP message", + "first_action": "Verify that the server did not crash.", + "full_action": "Do the following, as appropriate:\n■ Verify that the server did not crash.\n■ On UNIX, Linux, and Windows clients, enable bpbkar debug logging.\n■ Create a bpbkar debug log directory.\n■ On a UNIX or Linux client, add the VERBOSE option to the bp.conf file. On a\nWindowsclient,setVerboseontheTroubleShootingtabintheNetBackup\nClient Properties dialog box. To display this dialog box, start the Backup,\nArchive, and Restore interface on the client. Then select NetBackup Client\nProperties from the File menu.\n■ On other PC clients, create a debug log directory for bpcd.\nIncrease the amount of information that appears in the logs.\nSee\"Changingthelogginglevel on Windowsclients\"in theNetBackupLogging\nReference Guide.\n■ Use the vxlogcfg command as described in the following topic:\nSee \"About unified logging\" in the NetBackup Logging Reference Guide.\n■ Retry the operation and check the resulting debug logs." }, "67": { "code": 67, - "desc": "Cliente backup falhou to ler o arquivo list", - "first_action": "Verifique que o servidor did não crash.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Verifique que o servidor did não crash.\n■ Set up debug logging.\n■ On o servidor, create um bpbrm debug log diretório.\n■ On UNIX, Linux, e Windows clients, create um bpbkar debug log diretório.\n■ On other PC clients, create um debug log diretório para bpcd.\nAumentar o amount de informação que appears in o logs.\nSee\"Changingthelogginglevel on Windowsclients\"in theNetBackupLogging\nReference Guide.\n■ Retry o operation e verifique o resulting debug logs." + "desc": "Client backup failed to read the file list", + "first_action": "Verify that the server did not crash.", + "full_action": "Do the following, as appropriate:\n■ Verify that the server did not crash.\n■ Set up debug logging.\n■ On the server, create a bpbrm debug log directory.\n■ On UNIX, Linux, and Windows clients, create a bpbkar debug log directory.\n■ On other PC clients, create a debug log directory for bpcd.\nIncrease the amount of information that appears in the logs.\nSee\"Changingthelogginglevel on Windowsclients\"in theNetBackupLogging\nReference Guide.\n■ Retry the operation and check the resulting debug logs." }, "68": { "code": 68, - "desc": "Cliente esgotado fora waiting para o arquivo list", - "first_action": "Verifique que o servidor did não crash.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Verifique que o servidor did não crash.\n■ Set up debug logging.\n■ On o servidor, create um bpbrm debug log diretório.\n■ On UNIX, Linux, e Windows clients, create um bpbkar debug log diretório.\n■ On other PC clients, create um debug log diretório para bpcd.\nAumentar o amount de informação que appears in o logs.\nSee\"Changingthelogginglevel on Windowsclients\"in theNetBackupLogging\nReference Guide.\n■ Retry o operation e verifique o resulting debug logs." + "desc": "Client timed out waiting for the file list", + "first_action": "Verify that the server did not crash.", + "full_action": "Do the following, as appropriate:\n■ Verify that the server did not crash.\n■ Set up debug logging.\n■ On the server, create a bpbrm debug log directory.\n■ On UNIX, Linux, and Windows clients, create a bpbkar debug log directory.\n■ On other PC clients, create a debug log directory for bpcd.\nIncrease the amount of information that appears in the logs.\nSee\"Changingthelogginglevel on Windowsclients\"in theNetBackupLogging\nReference Guide.\n■ Retry the operation and check the resulting debug logs." }, "69": { "code": 69, - "desc": "Inválido filelist specification", - "first_action": "VMware Intelligent Policy: Verifique para duplication de o VM_name de o VMs in", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ VMware Intelligent Policy: Verifique para duplication de o VM_name de o VMs in\no policy.\n■ Policy arquivo list problema: Verifique o policy arquivo list. If wildcards estão used, verifique que\no bracket characters ([ e ]) in o list match. If o arquivo list contains UNC\n(UniversalNamingConvention)names,ensurethattheyareproperlyformatted.\nThis erro can occur if nbjm está executando e um SharePoint job rediscovery returns\num 0 ou 1 e o policy arquivo list está vazio. Examine o nbjm unified log (originator\nID 117) para more detail on o cause de o erro.\n■ Enterprise Vault Agent: Para more informação, por favor veja o Troubleshooting\nsection de o NetBackup para Enterprise Vault Agent Administrator's Guide.\n■ NetBackup Snapshot Cliente: Remove o ALL_LOCAL_DRIVES entry from o arquivo\nlist.\n■ Para more informação on o supported operating systems para backup hosts,\nrefer to o NetBackup Web UI RHV Administrator's Guide.\n■ Para o errors que estão related to Hypervisor policy e Nutanix AHV, refer to\no Nutanix AHV Administrator’s Guide." + "desc": "Invalid filelist specification", + "first_action": "VMware Intelligent Policy: Check for duplication of the VM_name of the VMs in", + "full_action": "Do the following, as appropriate:\n■ VMware Intelligent Policy: Check for duplication of the VM_name of the VMs in\nthe policy.\n■ Policy file list problem: Check the policy file list. If wildcards are used, verify that\nthe bracket characters ([ and ]) in the list match. If the file list contains UNC\n(UniversalNamingConvention)names,ensurethattheyareproperlyformatted.\nThis error can occur if nbjm is running and a SharePoint job rediscovery returns\na 0 or 1 and the policy file list is empty. Examine the nbjm unified log (originator\nID 117) for more detail on the cause of the error.\n■ Enterprise Vault Agent: For more information, please see the Troubleshooting\nsection of the NetBackup for Enterprise Vault Agent Administrator's Guide.\n■ NetBackup Snapshot Client: Remove the ALL_LOCAL_DRIVES entry from the file\nlist.\n■ For more information on the supported operating systems for backup hosts,\nrefer to the NetBackup Web UI RHV Administrator's Guide.\n■ For the errors that are related to Hypervisor policy and Nutanix AHV, refer to\nthe Nutanix AHV Administrator’s Guide." }, "70": { "code": 70, - "desc": "Um entry in o filelist expanded to too many characters NetBackup status codes 149 NetBackup status codes", - "first_action": "Change o wildcards in o arquivo list to specify fewer arquivos.", - "full_action": "Change o wildcards in o arquivo list to specify fewer arquivos." + "desc": "An entry in the filelist expanded to too many characters NetBackup status codes 149 NetBackup status codes", + "first_action": "Change the wildcards in the file list to specify fewer files.", + "full_action": "Change the wildcards in the file list to specify fewer files." }, "71": { "code": 71, - "desc": "Nenhum de o arquivos in o arquivo list exist", - "first_action": "Verifique que o correct arquivo list está specified para this cliente.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Verifique que o correct arquivo list está specified para this cliente.\n■ On Windows clients, verifique que o account used to start o NetBackup Cliente\nservice has ler access to o arquivos.\nIf you back up um rede drive ou um UNC (Universal Naming Convention) caminho,\ndo o seguinte: Use o Services application in o Windows Control Panel to\nverifythattheNetBackupClientservicedoesnotstartunderthesystemaccount.\nO System Account não é possível access rede drives.\nTo back up rede drives ou UNC paths: Change o NetBackup Cliente service\nstartup to log in como um usuário que has permissão to access rede drives.\n■ Verifique o Todos Log Entradas relatório para pistas.\n■ To set up debug logging, do one de o seguinte:\n■ On UNIX, Linux, e Windows clients, create um debug log diretório para\nbpbkar.\n■ On other PC clients, create um debug log diretório para bpcd.\n■ Aumentar o amount de informação que appears in o logs.\nSee\"Changingthelogginglevel on Windowsclients\"in theNetBackupLogging\nReference Guide.\n■ Retry o operation e verifique o resulting debug logs.\n■ Para um NDMP policy type, verifique que o credentials de o NDMP hosts have\nbeen added. If não, add them." + "desc": "None of the files in the file list exist", + "first_action": "Verify that the correct file list is specified for this client.", + "full_action": "Do the following, as appropriate:\n■ Verify that the correct file list is specified for this client.\n■ On Windows clients, verify that the account used to start the NetBackup Client\nservice has read access to the files.\nIf you back up a network drive or a UNC (Universal Naming Convention) path,\ndo the following: Use the Services application in the Windows Control Panel to\nverifythattheNetBackupClientservicedoesnotstartunderthesystemaccount.\nThe System Account cannot access network drives.\nTo back up network drives or UNC paths: Change the NetBackup Client service\nstartup to log in as a user that has permission to access network drives.\n■ Check the All Log Entries report for clues.\n■ To set up debug logging, do one of the following:\n■ On UNIX, Linux, and Windows clients, create a debug log directory for\nbpbkar.\n■ On other PC clients, create a debug log directory for bpcd.\n■ Increase the amount of information that appears in the logs.\nSee\"Changingthelogginglevel on Windowsclients\"in theNetBackupLogging\nReference Guide.\n■ Retry the operation and check the resulting debug logs.\n■ For an NDMP policy type, verify that the credentials of the NDMP hosts have\nbeen added. If not, add them." }, "72": { "code": 72, - "desc": "O cliente type está incorrect in o configuration banco de dados", + "desc": "The client type is incorrect in the configuration database", "first_action": "Verifythatthepolicytypeattributeforthepolicyiscorrect.", "full_action": "Verifythatthepolicytypeattributeforthepolicyiscorrect." }, "73": { "code": 73, - "desc": "Bpstart_notify falhou", - "first_action": "Verifique o bpstart_notify script on o cliente to veja if", - "full_action": "Verifique o bpstart_notify script on o cliente to veja if\nit performs como expected." + "desc": "Bpstart_notify failed", + "first_action": "Check the bpstart_notify script on the client to see if", + "full_action": "Check the bpstart_notify script on the client to see if\nit performs as expected." }, "74": { "code": 74, - "desc": "Cliente esgotado fora waiting para bpstart_notify to complete", - "first_action": "Try to speed up o bpstart_notify script ou set o", - "full_action": "Try to speed up o bpstart_notify script ou set o\nBPSTART_TIMEOUT on o servidor to um value que está larger than o default. Set\nBPSTART_TIMEOUT in o bp.conf arquivo on um UNIX ou Linux NetBackup servidor.\nOn um Windows NetBackup servidor, use Host Properties to set Backup Start Notify\nTempo limite esgotado.\nVeja \"usando o Host Properties window to access configuration settings\" in o\nNetBackup Troubleshooting Guide." + "desc": "Client timed out waiting for bpstart_notify to complete", + "first_action": "Try to speed up the bpstart_notify script or set the", + "full_action": "Try to speed up the bpstart_notify script or set the\nBPSTART_TIMEOUT on the server to a value that is larger than the default. Set\nBPSTART_TIMEOUT in the bp.conf file on a UNIX or Linux NetBackup server.\nOn a Windows NetBackup server, use Host Properties to set Backup Start Notify\nTimeout.\nSee \"Using the Host Properties window to access configuration settings\" in the\nNetBackup Troubleshooting Guide." }, "75": { "code": 75, - "desc": "Cliente esgotado fora waiting para bpend_notify to complete", - "first_action": "Try to speed up o bpend_notify script ou set", - "full_action": "Try to speed up o bpend_notify script ou set\nBPEND_TIMEOUT on o servidor to um value que está larger than o default. Set\nBPEND_TIMEOUT in o bp.conf arquivo on um UNIX ou Linux NetBackup servidor. On\num Windows NetBackup servidor, use Host Properties to set Backup End Notify\nTempo limite esgotado." + "desc": "Client timed out waiting for bpend_notify to complete", + "first_action": "Try to speed up the bpend_notify script or set", + "full_action": "Try to speed up the bpend_notify script or set\nBPEND_TIMEOUT on the server to a value that is larger than the default. Set\nBPEND_TIMEOUT in the bp.conf file on a UNIX or Linux NetBackup server. On\na Windows NetBackup server, use Host Properties to set Backup End Notify\nTimeout." }, "76": { "code": 76, - "desc": "Cliente esgotado fora reading arquivo", - "first_action": "Make sure que o process que está to produce o data on", - "full_action": "Make sure que o process que está to produce o data on\no named FIFO está started correctly. Add um entry to o\n/usr/openv/netbackup/bp.conffileontheservertosetCLIENT_READ_TIMEOUT\nto um larger value than o default." + "desc": "Client timed out reading file", + "first_action": "Make sure that the process that is to produce the data on", + "full_action": "Make sure that the process that is to produce the data on\nthe named FIFO is started correctly. Add an entry to the\n/usr/openv/netbackup/bp.conffileontheservertosetCLIENT_READ_TIMEOUT\nto a larger value than the default." }, "77": { "code": 77, - "desc": "Execution de o specified system comando returned um nonzero status", - "first_action": "Verifique que o comando está specified correctly.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Verifique que o comando está specified correctly.\n■ Para NetBackup Snapshot Cliente apenas, do o seguinte:\nO policy arquivo list may contain o arquivos que do não residir within um arquivo system\nque foi designated como o snapshot source. To apply um snapshot method to\no backup de individual arquivos, o snapshot source must be um arquivo system. (It\nnão é possível be um raw partition ou Volume Manager volume.) O arquivos in o policy\narquivo list must residir within que arquivo system.\n■ Run o comando manually to veja if o wanted result está produced.\n■ Para detailed troubleshooting informação, set up debug logging como follows:\n■ On UNIX, Linux, e Windows clients, create um debug log diretório para\nbpbkar.\n■ On other PC clients, create um debug log diretório para bpcd.\n■ Aumentar o amount de informação que appears in o logs.\nVeja \"Changing o logging level on Windows clients\" in o NetBackup\nLogging Reference Guide.\n■ Retry o operation e verifique o resulting debug log." + "desc": "Execution of the specified system command returned a nonzero status", + "first_action": "Verify that the command is specified correctly.", + "full_action": "Do the following, as appropriate:\n■ Verify that the command is specified correctly.\n■ For NetBackup Snapshot Client only, do the following:\nThe policy file list may contain the files that do not reside within a file system\nthat was designated as the snapshot source. To apply a snapshot method to\nthe backup of individual files, the snapshot source must be a file system. (It\ncannot be a raw partition or Volume Manager volume.) The files in the policy\nfile list must reside within that file system.\n■ Run the command manually to see if the wanted result is produced.\n■ For detailed troubleshooting information, set up debug logging as follows:\n■ On UNIX, Linux, and Windows clients, create a debug log directory for\nbpbkar.\n■ On other PC clients, create a debug log directory for bpcd.\n■ Increase the amount of information that appears in the logs.\nSee \"Changing the logging level on Windows clients\" in the NetBackup\nLogging Reference Guide.\n■ Retry the operation and check the resulting debug log." }, "78": { "code": 78, - "desc": "Afs/dfs comando falhou", - "first_action": "Verifique o NetBackup Problemas Relatório para additional informação on por que o", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Verifique o NetBackup Problemas Relatório para additional informação on por que o\ncomando falhou.\n■ O bpbkar debug log shows o comando que foi run. Create um debug log\ndiretório para bpbkar. Retry o operation e retry o resulting debug log.\n■ Try executando o vos comando manually to duplicate o problema." + "desc": "Afs/dfs command failed", + "first_action": "Check the NetBackup Problems Report for additional information on why the", + "full_action": "Do the following, as appropriate:\n■ Check the NetBackup Problems Report for additional information on why the\ncommand failed.\n■ The bpbkar debug log shows the command that was run. Create a debug log\ndirectory for bpbkar. Retry the operation and retry the resulting debug log.\n■ Try running the vos command manually to duplicate the problem." }, "79": { "code": 79, - "desc": "Unsupported image format para o solicitado banco de dados query", - "first_action": "Garanta que nenhum de o images foram encrypted.", - "full_action": "Garanta que nenhum de o images foram encrypted." + "desc": "Unsupported image format for the requested database query", + "first_action": "Ensure that none of the images were encrypted.", + "full_action": "Ensure that none of the images were encrypted." }, "80": { "code": 80, - "desc": "Mídia Manager dispositivo daemon (ltid) está não active", + "desc": "Media Manager device daemon (ltid) is not active", "first_action": "OnWindows,usetheActivityMonitorortheServicesapplicationintheWindows", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ OnWindows,usetheActivityMonitorortheServicesapplicationintheWindows\nControl Panel to veja if o NetBackup Dispositivo Manager service está executando. If it\nestá não executando, start it. To enable verbose logging, place VERBOSE on um line por\nitself in o install_path\\Volmgr\\vm.conf arquivo before you start o service.\n■ On UNIX, use vmps to veja if ltid está executando e if necessary start ltid in\nverbose mode com o seguinte comando:\n/usr/openv/volmgr/bin/ltid -v\nOu, add um VERBOSE entry to o /usr/openv/volmgr/vm.conf arquivo. Create o\nvm.conf arquivo if necessary.\n■ On UNIX, verifique o system logs to verifique que ltid starts.\nNote: On UNIX systems, ltid, e on Windows systems, o NetBackup Dispositivo\nManager service, está used apenas if devices estão attached to o system." + "full_action": "Do the following, as appropriate:\n■ OnWindows,usetheActivityMonitorortheServicesapplicationintheWindows\nControl Panel to see if the NetBackup Device Manager service is running. If it\nis not running, start it. To enable verbose logging, place VERBOSE on a line by\nitself in the install_path\\Volmgr\\vm.conf file before you start the service.\n■ On UNIX, use vmps to see if ltid is running and if necessary start ltid in\nverbose mode with the following command:\n/usr/openv/volmgr/bin/ltid -v\nOr, add a VERBOSE entry to the /usr/openv/volmgr/vm.conf file. Create the\nvm.conf file if necessary.\n■ On UNIX, check the system logs to verify that ltid starts.\nNote: On UNIX systems, ltid, and on Windows systems, the NetBackup Device\nManager service, is used only if devices are attached to the system." }, "81": { "code": 81, - "desc": "Mídia Manager volume daemon (vmd) está não active", - "first_action": "On UNIX, verifique que o Mídia Manager dispositivo daemon (ltid) e o", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ On UNIX, verifique que o Mídia Manager dispositivo daemon (ltid) e o\nNetBackup Volume Manager (vmd) estão executando. Start them if necessary.\n■ On Windows, verifique que both o NetBackup Dispositivo Manager service e o\nNetBackup Volume Manager service estão executando. Start them if necessary.\nNote: ltid ou o NetBackup Dispositivo Manager service está used apenas if devices estão\nattached to o system." + "desc": "Media Manager volume daemon (vmd) is not active", + "first_action": "On UNIX, verify that the Media Manager device daemon (ltid) and the", + "full_action": "Do the following, as appropriate:\n■ On UNIX, verify that the Media Manager device daemon (ltid) and the\nNetBackup Volume Manager (vmd) are running. Start them if necessary.\n■ On Windows, verify that both the NetBackup Device Manager service and the\nNetBackup Volume Manager service are running. Start them if necessary.\nNote: ltid or the NetBackup Device Manager service is used only if devices are\nattached to the system." }, "82": { "code": 82, - "desc": "Mídia manager killed por signal", - "first_action": "This erro should não occur in normal operation. If you", - "full_action": "This erro should não occur in normal operation. If you\ndesejar to terminate um active backup, use o NetBackup Activity Monitor.\nWhen you back up um DomainOS cliente, this erro occurs after o servidor has não\nreceived anything on o socket para at least 300 seconds. It causes um cliente ler\ntempo limite esgotado e breaks o conexão. O bpbkar debug log has um entry similar to\no seguinte:\n13:22:49 [1347] <16> bpbkar: ERR - Extra output - - ECONNRESET\nConexão reset por peer (UNIX/errno status)\nTo resolve o problema, aumentar o CLIENT_READ_TIMEOUT value. In this\ninstance, set o value to 900." + "desc": "Media manager killed by signal", + "first_action": "This error should not occur in normal operation. If you", + "full_action": "This error should not occur in normal operation. If you\nwant to terminate an active backup, use the NetBackup Activity Monitor.\nWhen you back up a DomainOS client, this error occurs after the server has not\nreceived anything on the socket for at least 300 seconds. It causes a client read\ntimeout and breaks the connection. The bpbkar debug log has an entry similar to\nthe following:\n13:22:49 [1347] <16> bpbkar: ERR - Extra output - - ECONNRESET\nConnection reset by peer (UNIX/errno status)\nTo resolve the problem, increase the CLIENT_READ_TIMEOUT value. In this\ninstance, set the value to 900." }, "83": { "code": 83, - "desc": "Mídia abrir erro", - "first_action": "NetBackup Problemas relatório", - "full_action": "Para additional informação, verifique o seguinte:\n■ NetBackup Problemas relatório\n■ Event Viewer Application log (Windows)\n■ System log (UNIX)\n■ Typically, this status code indicates um drive configuration problema que allows\nmorethanoneprocessatatimetoopenthedevice.OnUNIX,theproblemmay\nbe due one ou more de o seguinte:\n■ Two (ou more) devices foram configurado que estão o same physical dispositivo\n(para different densities perhaps). Verifique que nenhum de o /dev arquivos que foram\nused para these devices have o same major ou minor numbers.\n■ Links exist in o arquivo system que allows users access to o drives.\n■ O configuration para o drives foi modified (in o administrator interface\norvm.conf)andtheMediaManagerdevicedaemon,ltid,wasnotrestarted.\nVerifique o configuration e then start ltid.\nOn Windows, o problema may be que o Mídia e Dispositivo Management\ndispositivo configuration foi modified but o NetBackup Dispositivo Manager service\nfoi não restarted. Verifique o configuration e restart o NetBackup Dispositivo\nManager service.\n■ On Windows, make sure que o tapes estão não gravar protected.\n■ Para detailed troubleshooting informação:\n■ Create um debug log diretório para bpdm (if o dispositivo está disco) ou bptm (if o\ndispositivo está tape).\n■ On UNIX, restartltid in o verbose mode por executando o seguinte:\n/usr/openv/volmgr/bin/ltid -v\nOu, add um VERBOSE entry to o /usr/openv/volmgr/vm.conf arquivo. Create\no vm.conf arquivo if necessary.\n■ On Windows, to enable verbose logging, add VERBOSE on um line por itself in\no install_path\\Volmgr\\vm.conf arquivo. Then, stop e restart o\nNetBackup Dispositivo Manager service.\n■ Retry o operation e verifique o resulting debug log arquivos.\n■ On Windows systems, look at o\ninstall_path\\VERITAS\\NetBackup\\db\\media\\errors log para um drive que\nfrequently produces errors.\nOn UNIX systems, look at o /usr/openv/netbackup/db/media/errors\nlog(whichisalsoincludedinthe/usr/openv/netbackup/bin/support/nbsu\nscript output) para um drive que frequently produces errors." + "desc": "Media open error", + "first_action": "NetBackup Problems report", + "full_action": "For additional information, check the following:\n■ NetBackup Problems report\n■ Event Viewer Application log (Windows)\n■ System log (UNIX)\n■ Typically, this status code indicates a drive configuration problem that allows\nmorethanoneprocessatatimetoopenthedevice.OnUNIX,theproblemmay\nbe due one or more of the following:\n■ Two (or more) devices were configured that are the same physical device\n(for different densities perhaps). Verify that none of the /dev files that were\nused for these devices have the same major or minor numbers.\n■ Links exist in the file system that allows users access to the drives.\n■ The configuration for the drives was modified (in the administrator interface\norvm.conf)andtheMediaManagerdevicedaemon,ltid,wasnotrestarted.\nVerify the configuration and then start ltid.\nOn Windows, the problem may be that the Media and Device Management\ndevice configuration was modified but the NetBackup Device Manager service\nwas not restarted. Verify the configuration and restart the NetBackup Device\nManager service.\n■ On Windows, make sure that the tapes are not write protected.\n■ For detailed troubleshooting information:\n■ Create a debug log directory for bpdm (if the device is disk) or bptm (if the\ndevice is tape).\n■ On UNIX, restartltid in the verbose mode by running the following:\n/usr/openv/volmgr/bin/ltid -v\nOr, add a VERBOSE entry to the /usr/openv/volmgr/vm.conf file. Create\nthe vm.conf file if necessary.\n■ On Windows, to enable verbose logging, add VERBOSE on a line by itself in\nthe install_path\\Volmgr\\vm.conf file. Then, stop and restart the\nNetBackup Device Manager service.\n■ Retry the operation and check the resulting debug log files.\n■ On Windows systems, look at the\ninstall_path\\VERITAS\\NetBackup\\db\\media\\errors log for a drive that\nfrequently produces errors.\nOn UNIX systems, look at the /usr/openv/netbackup/db/media/errors\nlog(whichisalsoincludedinthe/usr/openv/netbackup/bin/support/nbsu\nscript output) for a drive that frequently produces errors." }, "84": { "code": 84, - "desc": "Mídia gravar erro", - "first_action": "Para NetBackup Snapshot Cliente apenas:", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Para NetBackup Snapshot Cliente apenas:\nIf o seguinte message appears in o /usr/openv/netbackup/bptm log, e\no values para key, asc, e ascq estão todos zero (0x0) como shown in this example\nmessage:\ntape erro ocorreu on extended copy comando, key = 0x0, asc =\n0x0, ascq = 0x\nNetBackup Snapshot Cliente probably does não support seu host-bus adapter\nanditsdriver.Thehost-busadaptersthataresupportedinthereleasearelisted\nin o NetBackup Release Notes.\n■ Para additional informação, verifique o seguinte:\n■ NetBackup Problemas relatório to determinar o dispositivo ou mídia que caused\no erro\n■ System e erro logs para o system (UNIX)\n■ Event Viewer Application e System logs (Windows)\n■ If NetBackup writes backups to um disco arquivo, verifique o seguinte: O fragment\nsize que está configurado para o disco armazenamento unidade está não greater than o maximum\narquivo size que o operating system specifies.\n■ On Windows, make sure que o tapes estão não gravar protected.\n■ If bpbackupdb foi used to back up o NetBackup catalog to um disco caminho on um\nUNIX ou Linux system, o image you try to gravar may be greater than o\nmaximum arquivo size que está specified por que operating system. Tape arquivos do não\nhave this limite. You may have to back up o catalog to tape.\n■ If o mídia está tape, verifique para o seguinte:\n■ Um defective ou um dirty drive. Clean it ou have it repaired (refer to o tpclean\ncomando para robotic drives).\n■ O wrong mídia type. Verifique que o mídia matches o drive type you\nuse.\n■ Defective mídia. If it está defective, use o bpmedia comando to set o\nvolume to o FROZEN state so it está não used para future backups.\n■ Incorrect drive configuration. Verifique o Mídia e Dispositivo Management e\nsystem configuration para o drive.\nPara example, on UNIX o drive may be configurado para fixed mode when it\nmust be variable mode.\nVeja o NetBackup Dispositivo Configuration Guide para more informação.\nThis configuration often results in o mídia being frozen com o message\ntoo many data blocks written, verifique tape e drive block size\nconfiguration\nVeja \"Frozen mídia troubleshooting considerations\" in o NetBackup\nTroubleshooting Guide.\n■ If you receive this erro message when um GLACIER ou LIFECYCLE backup job\nfails,theerrorisrelatedtotheAmazonlifecyclepolicyandoccursinthefollowing\nsituations:\n■ O Amazon lifecycle policy que NetBackup uses não é possível be applied. O\nAmazon GLACIER ou LIFECYCLE armazenamento class está não supported para o\nregion to which o bucket belongs. Recreate o disco pool com o bucket\nin o supported region.\n■ Um different Amazon lifecycle policy other than what NetBackup uses already\nexists. Remove o policy que está não used por NetBackup e rerun o job.\n■ TheerroroccurredwhilecreatingtheAmazonlifecyclepolicythatNetBackup\nuses to back up data to Amazon. Verifique o bptm logs para more details." + "desc": "Media write error", + "first_action": "For NetBackup Snapshot Client only:", + "full_action": "Do the following, as appropriate:\n■ For NetBackup Snapshot Client only:\nIf the following message appears in the /usr/openv/netbackup/bptm log, and\nthe values for key, asc, and ascq are all zero (0x0) as shown in this example\nmessage:\ntape error occurred on extended copy command, key = 0x0, asc =\n0x0, ascq = 0x\nNetBackup Snapshot Client probably does not support your host-bus adapter\nanditsdriver.Thehost-busadaptersthataresupportedinthereleasearelisted\nin the NetBackup Release Notes.\n■ For additional information, check the following:\n■ NetBackup Problems report to determine the device or media that caused\nthe error\n■ System and error logs for the system (UNIX)\n■ Event Viewer Application and System logs (Windows)\n■ If NetBackup writes backups to a disk file, verify the following: The fragment\nsize that is configured for the disk storage unit is not greater than the maximum\nfile size that the operating system specifies.\n■ On Windows, make sure that the tapes are not write protected.\n■ If bpbackupdb was used to back up the NetBackup catalog to a disk path on a\nUNIX or Linux system, the image you try to write may be greater than the\nmaximum file size that is specified by that operating system. Tape files do not\nhave this limit. You may have to back up the catalog to tape.\n■ If the media is tape, check for the following:\n■ A defective or a dirty drive. Clean it or have it repaired (refer to the tpclean\ncommand for robotic drives).\n■ The wrong media type. Verify that the media matches the drive type you\nuse.\n■ Defective media. If it is defective, use the bpmedia command to set the\nvolume to the FROZEN state so it is not used for future backups.\n■ Incorrect drive configuration. Verify the Media and Device Management and\nsystem configuration for the drive.\nFor example, on UNIX the drive may be configured for fixed mode when it\nmust be variable mode.\nSee the NetBackup Device Configuration Guide for more information.\nThis configuration often results in the media being frozen with the message\ntoo many data blocks written, check tape and drive block size\nconfiguration\nSee \"Frozen media troubleshooting considerations\" in the NetBackup\nTroubleshooting Guide.\n■ If you receive this error message when a GLACIER or LIFECYCLE backup job\nfails,theerrorisrelatedtotheAmazonlifecyclepolicyandoccursinthefollowing\nsituations:\n■ The Amazon lifecycle policy that NetBackup uses cannot be applied. The\nAmazon GLACIER or LIFECYCLE storage class is not supported for the\nregion to which the bucket belongs. Recreate the disk pool with the bucket\nin the supported region.\n■ A different Amazon lifecycle policy other than what NetBackup uses already\nexists. Remove the policy that is not used by NetBackup and rerun the job.\n■ TheerroroccurredwhilecreatingtheAmazonlifecyclepolicythatNetBackup\nuses to back up data to Amazon. Check the bptm logs for more details." }, "85": { "code": 85, - "desc": "Mídia ler erro", - "first_action": "NetBackup Problemas relatório to determinar o dispositivo ou mídia que caused o", - "full_action": "Para additional informação, verifique o seguinte:\n■ NetBackup Problemas relatório to determinar o dispositivo ou mídia que caused o\nerro\n■ System e erro logs para o system (UNIX)\n■ Event Viewer Application e System logs (Windows)\n■ Verifique para o seguinte:\n■ Um defective ou um dirty drive. Clean it ou have it repaired (veja o tpclean\ncomando para cleaning).\n■ Incorrect drive configuration. Verifique o Mídia e Dispositivo Management e\nsystem configuration para o drive.\nPara example, on UNIX, o drive may be configurado para fixed mode when it\nmust be variable mode. More informação está disponível.\nVeja o NetBackup Dispositivo Configuration Guide.\n■ Defective mídia. In this case, you may não be able to recover todos o data\non o mídia. Use o bpmedia comando to set o volume to o FROZEN\nstate so it está não used para future backups.\nVeja \"Frozen mídia troubleshooting considerations\" in o NetBackup\nTroubleshooting Guide.\n■ O wrong mídia type. Verifique que o mídia matches o drive type you\nuse." + "desc": "Media read error", + "first_action": "NetBackup Problems report to determine the device or media that caused the", + "full_action": "For additional information, check the following:\n■ NetBackup Problems report to determine the device or media that caused the\nerror\n■ System and error logs for the system (UNIX)\n■ Event Viewer Application and System logs (Windows)\n■ Check for the following:\n■ A defective or a dirty drive. Clean it or have it repaired (see the tpclean\ncommand for cleaning).\n■ Incorrect drive configuration. Verify the Media and Device Management and\nsystem configuration for the drive.\nFor example, on UNIX, the drive may be configured for fixed mode when it\nmust be variable mode. More information is available.\nSee the NetBackup Device Configuration Guide.\n■ Defective media. In this case, you may not be able to recover all the data\non the media. Use the bpmedia command to set the volume to the FROZEN\nstate so it is not used for future backups.\nSee \"Frozen media troubleshooting considerations\" in the NetBackup\nTroubleshooting Guide.\n■ The wrong media type. Verify that the media matches the drive type you\nuse." }, "86": { "code": 86, - "desc": "Mídia position erro", - "first_action": "NetBackup Problemas relatório to determinar o dispositivo ou mídia que caused o", - "full_action": "Para additional informação, verifique o seguinte:\n■ NetBackup Problemas relatório to determinar o dispositivo ou mídia que caused o\nerro\n■ System e erro logs para o system (UNIX)\n■ Event Viewer Application e System logs (Windows)\n■ Verifique para o seguinte:\n■ Um defective ou um dirty drive. Clean it ou have it repaired (veja o tpclean\ncomando para cleaning).\n■ Incorrect drive configuration. Verifique o Mídia e Dispositivo Management e\nsystem configuration para o drive.\nPara example, on UNIX, o drive may be configurado para fixed mode when it\nmust be variable mode.\nVeja o NetBackup Dispositivo Configuration Guide para more informação.\n■ Defective mídia. In this case, some data may be lost. Use o bpmedia\ncomando to set o volume to o FROZEN state so it está não used para future\nbackups.\nVeja \"Frozen mídia troubleshooting considerations\" in o NetBackup\nTroubleshooting Guide.\n■ O wrong mídia type. Verifique que o mídia matches o drive type you\nuse." + "desc": "Media position error", + "first_action": "NetBackup Problems report to determine the device or media that caused the", + "full_action": "For additional information, check the following:\n■ NetBackup Problems report to determine the device or media that caused the\nerror\n■ System and error logs for the system (UNIX)\n■ Event Viewer Application and System logs (Windows)\n■ Check for the following:\n■ A defective or a dirty drive. Clean it or have it repaired (see the tpclean\ncommand for cleaning).\n■ Incorrect drive configuration. Verify the Media and Device Management and\nsystem configuration for the drive.\nFor example, on UNIX, the drive may be configured for fixed mode when it\nmust be variable mode.\nSee the NetBackup Device Configuration Guide for more information.\n■ Defective media. In this case, some data may be lost. Use the bpmedia\ncommand to set the volume to the FROZEN state so it is not used for future\nbackups.\nSee \"Frozen media troubleshooting considerations\" in the NetBackup\nTroubleshooting Guide.\n■ The wrong media type. Verify that the media matches the drive type you\nuse." }, "87": { "code": 87, - "desc": "Mídia fechar erro NetBackup status codes 159 NetBackup status codes", - "first_action": "NetBackup Problemas relatório to determinar o dispositivo ou mídia que caused o", - "full_action": "Para additional informação, verifique o seguinte:\n■ NetBackup Problemas relatório to determinar o dispositivo ou mídia que caused o\nerro\n■ System e erro logs para o system (UNIX)\n■ Event Viewer Application e System logs (Windows)\n■ Verifique para o seguinte:\n■ Um defective ou um dirty drive. Clean it ou have it repaired (veja o tpclean\ncomando para cleaning).\n■ Defective mídia. In this case, some data may be lost. Use o bpmedia\ncomando to set o volume to o FROZEN state so it está não used para future\nbackups.\nVeja \"Frozen mídia troubleshooting considerations\" in o NetBackup\nTroubleshooting Guide.\nWhen Amazon AWS está used como cloud armazenamento:\n■ Verifique que you have SSL enabled para communication." + "desc": "Media close error NetBackup status codes 159 NetBackup status codes", + "first_action": "NetBackup Problems report to determine the device or media that caused the", + "full_action": "For additional information, check the following:\n■ NetBackup Problems report to determine the device or media that caused the\nerror\n■ System and error logs for the system (UNIX)\n■ Event Viewer Application and System logs (Windows)\n■ Check for the following:\n■ A defective or a dirty drive. Clean it or have it repaired (see the tpclean\ncommand for cleaning).\n■ Defective media. In this case, some data may be lost. Use the bpmedia\ncommand to set the volume to the FROZEN state so it is not used for future\nbackups.\nSee \"Frozen media troubleshooting considerations\" in the NetBackup\nTroubleshooting Guide.\nWhen Amazon AWS is used as cloud storage:\n■ Verify that you have SSL enabled for communication." }, "88": { "code": 88, - "desc": "OpenStorage WORM lock erro.", - "first_action": "Look at o OpenStorage armazenamento servidor e garanta que", - "full_action": "Look at o OpenStorage armazenamento servidor e garanta que\nconfiguration de o armazenamento dispositivo está consistent com NetBackup. Review o bptm\ne o bpdm logs para more detailed messages e OST erro codes para more\ninformação about these failures." + "desc": "OpenStorage WORM lock error.", + "first_action": "Look at the OpenStorage storage server and ensure that", + "full_action": "Look at the OpenStorage storage server and ensure that\nconfiguration of the storage device is consistent with NetBackup. Review the bptm\nand the bpdm logs for more detailed messages and OST error codes for more\ninformation about these failures." }, "89": { "code": 89, - "desc": "Problemas encontrado during setup de shared memória NetBackup status codes 160 NetBackup status codes", + "desc": "Problems encountered during setup of shared memory NetBackup status codes 160 NetBackup status codes", "first_action": "ForSolaris9,thedefaultshminfo_shmmaxvalueis8megabytes.Youcanplace", - "full_action": "Checkforasharedmemoryproblem.Thiserrorcanoccur\nif o system não é possível allocate enough shared memória. It usually occurs com\nmultiplexing, which increases o amount de shared memória que está requerido para o\noperation. Um entry similar to o seguinte may be seen in um NetBackup log ou\nrelatório:\nsystem não é possível allocate enough shared memória\nIf you veja this type de message, refer to seu platform vendor documentation para\ninstructions on how to aumentar shared memória on seu system.\nPara older levels de Solaris, you may need to change one ou more default System V\nSharedMemorysettingstopreventjobsfailingwiththememoryallocationmessage,\ncomo follows:\n■ ForSolaris9,thedefaultshminfo_shmmaxvalueis8megabytes.Youcanplace\no seguinte line in seu /etc/system arquivo to aumentar this setting. Um value de 32\nmegabytes has been used in this example. Seu system may require um greater\nvalue under some circumstances such como um high value para o NetBackup\nmultiplexingparameter.AccordingtoSunMicrosystemsdocumentation,setting\nthisparametertoitsmaximumpossiblevaluehasnosideeffects.(Thisparameter\nestá não applicable to Solaris 10).\nset shmsys:shminfo_shmmax=33554432\n■ Para Solaris 9, o default shminfo_shmmni value está 100. You can place o\nfollowingline in seu /etc/system arquivo to aumentar this setting.The defaultvalue\nestá usually sufficient para NetBackup. In some circumstances, such como installing um\nNetBackup mídia servidor on um large banco de dados servidor, this setting may need to\nbe increased. Um value de 220 has been used in this example. (This parâmetro\nestá não applicable to Solaris 10).\nset shmsys:shminfo_shmmni=220\nNote: If you modify qualquer de these values in o /etc/system arquivo, you must restart\no system com boot -r para o new settings to take effect.\nRefertoyourvendordocumentationfordetailedinstructionsonhowtomodifythese\nvalues. Note que these shminfo parameters estão não applicable to Solaris 10." + "full_action": "Checkforasharedmemoryproblem.Thiserrorcanoccur\nif the system cannot allocate enough shared memory. It usually occurs with\nmultiplexing, which increases the amount of shared memory that is required for the\noperation. An entry similar to the following may be seen in a NetBackup log or\nreport:\nsystem cannot allocate enough shared memory\nIf you see this type of message, refer to your platform vendor documentation for\ninstructions on how to increase shared memory on your system.\nFor older levels of Solaris, you may need to change one or more default System V\nSharedMemorysettingstopreventjobsfailingwiththememoryallocationmessage,\nas follows:\n■ ForSolaris9,thedefaultshminfo_shmmaxvalueis8megabytes.Youcanplace\nthe following line in your /etc/system file to increase this setting. A value of 32\nmegabytes has been used in this example. Your system may require a greater\nvalue under some circumstances such as a high value for the NetBackup\nmultiplexingparameter.AccordingtoSunMicrosystemsdocumentation,setting\nthisparametertoitsmaximumpossiblevaluehasnosideeffects.(Thisparameter\nis not applicable to Solaris 10).\nset shmsys:shminfo_shmmax=33554432\n■ For Solaris 9, the default shminfo_shmmni value is 100. You can place the\nfollowingline in your /etc/system file to increase this setting.The defaultvalue\nis usually sufficient for NetBackup. In some circumstances, such as installing a\nNetBackup media server on a large database server, this setting may need to\nbe increased. A value of 220 has been used in this example. (This parameter\nis not applicable to Solaris 10).\nset shmsys:shminfo_shmmni=220\nNote: If you modify any of these values in the /etc/system file, you must restart\nthe system with boot -r for the new settings to take effect.\nRefertoyourvendordocumentationfordetailedinstructionsonhowtomodifythese\nvalues. Note that these shminfo parameters are not applicable to Solaris 10." }, "90": { "code": 90, - "desc": "Mídia manager received não data para backup image", - "first_action": "Verifique o Todos Log Entradas relatório.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Verifique o Todos Log Entradas relatório.\n■ Para detailed debug informação, create bpdm ou bptm debug log directories on\no servidor. If o cliente está Windows, also create um bpbkar debug log diretório\non o cliente. Retry o operation e verifique o resulting debug logs.\n■ Para additional informação, verifique o seguinte:\n■ NetBackup Problemas relatório to determinar o dispositivo ou mídia que caused\no erro\n■ System e erro logs para o system (UNIX)\n■ Event Viewer Application log (Windows)\n■ Verifique o Mídia e Dispositivo Management e system configuration para o\ndrive.\nPara example, on UNIX, o drive may não be set para variable mode in um case\nonde NetBackup requires que mode.\nVerifique o NetBackup Dispositivo Configuration Guide para drive configuration\ninformação.\n■ Verifique que o Mídia e Dispositivo Management configuration para o backup\ndispositivo matches what está specified para o armazenamento unidade in o NetBackup policy.\n■ Verifique que you use o correct mídia in o drive.\n■ Para detailed debug informação, create um bpdm ou bptm debug log diretório\n(whichever aplica-se) on o servidor. If o cliente está Windows, also create um bpbkar\ndebug log diretório on o cliente. Retry o operation e verifique o resulting\ndebug logs.\n■ If o erro ocorreu during duplication ou um Vault session que uses um Alternate\nLer Servidor to executar duplication, verifique que o Alternate Ler Servidor has\naccess to o source mídia." + "desc": "Media manager received no data for backup image", + "first_action": "Check the All Log Entries report.", + "full_action": "Do the following, as appropriate:\n■ Check the All Log Entries report.\n■ For detailed debug information, create bpdm or bptm debug log directories on\nthe server. If the client is Windows, also create a bpbkar debug log directory\non the client. Retry the operation and check the resulting debug logs.\n■ For additional information, check the following:\n■ NetBackup Problems report to determine the device or media that caused\nthe error\n■ System and error logs for the system (UNIX)\n■ Event Viewer Application log (Windows)\n■ Verify the Media and Device Management and system configuration for the\ndrive.\nFor example, on UNIX, the drive may not be set for variable mode in a case\nwhere NetBackup requires that mode.\nCheck the NetBackup Device Configuration Guide for drive configuration\ninformation.\n■ Verify that the Media and Device Management configuration for the backup\ndevice matches what is specified for the storage unit in the NetBackup policy.\n■ Verify that you use the correct media in the drive.\n■ For detailed debug information, create a bpdm or bptm debug log directory\n(whichever applies) on the server. If the client is Windows, also create a bpbkar\ndebug log directory on the client. Retry the operation and check the resulting\ndebug logs.\n■ If the error occurred during duplication or a Vault session that uses an Alternate\nRead Server to perform duplication, verify that the Alternate Read Server has\naccess to the source media." }, "91": { "code": 91, - "desc": "Fatal NB mídia banco de dados erro", - "first_action": "Verifique o Todos Log Entradas relatório para more informação.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Verifique o Todos Log Entradas relatório para more informação.\n■ Verifique o NetBackup Mídia Lists relatório to veja if o catalog está intact. If o\ncatalogisnotintact,youmaywanttoreloaditfromthelatestNetBackupcatalog\nbackup volume.\n■ Verifique que o disco partition on which o catalog resides has enough space.\n■ If these actions do não explain o problema, verifique o NetBackup Problemas\nrelatório.\n■ Para detailed troubleshooting informação, create um bptm debug log diretório on\no servidor e retry o operation. Verifique o resulting debug log arquivo.\n■ Contactcustomersupportandsendappropriateproblemanddebuglogsections." + "desc": "Fatal NB media database error", + "first_action": "Check the All Log Entries report for more information.", + "full_action": "Do the following, as appropriate:\n■ Check the All Log Entries report for more information.\n■ Check the NetBackup Media Lists report to see if the catalog is intact. If the\ncatalogisnotintact,youmaywanttoreloaditfromthelatestNetBackupcatalog\nbackup volume.\n■ Verify that the disk partition on which the catalog resides has enough space.\n■ If these actions do not explain the problem, check the NetBackup Problems\nreport.\n■ For detailed troubleshooting information, create a bptm debug log directory on\nthe server and retry the operation. Check the resulting debug log file.\n■ Contactcustomersupportandsendappropriateproblemanddebuglogsections." }, "92": { "code": 92, - "desc": "Mídia manager detected image que foi não in tar format", - "first_action": "Executar um bpverify de o affected image to determinar if it está written correctly.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Executar um bpverify de o affected image to determinar if it está written correctly.\n■ ChecktheNetBackupProblemsreportforadditionalinformationabouttheerror.\n■ Verifique o Mídia e Dispositivo Management e system configuration para o\ndrive.\nForexample,ifyoudonotconfigurethedriveforvariable-modeblocksizewrites\nonsomeUNIXsystems,thebackupimagesthatwritetothemediaproducethis\nerro when you attempt to restauração o image.\nO seguinte sequence de events occurs:\n■ Backup succeeds.\n■ Verifique succeeds.\n■ Restauração fails.\nO bptm debug log shows um erro similar to o seguinte:\n00:58:54 [2304] <16> write_data: gravar de 32768 bytes indicated\napenas 29696 bytes foram written, errno = 0\nIn this case, configure o drive para variable-mode block sizes e suspend o\nmídia que writes on que dispositivo.\nVeja o NetBackup Dispositivo Configuration Guide.\nO images que foram written to those mídia may be restorable (platform\ndependent),butsinglefilerestoresarealmostguaranteedtofail.Youcanexpire\nthese mídia e regenerate o backups. Ou you can attempt to duplicate o\nimages on these mídia to another dispositivo e then expire o original copy.\n■ Thiserrorhasoccurredonre-labeledandvalue-added8-mmtapedriveswhere\no drive’s micro code incorrectly processos um forward space record SCSI\ncomando.\n■ If o problema está não one de those discussed, create um debug log diretório para\neither bpdm ou bptm e retry o operation. Verifique o resulting debug log arquivo." + "desc": "Media manager detected image that was not in tar format", + "first_action": "Perform a bpverify of the affected image to determine if it is written correctly.", + "full_action": "Do the following, as appropriate:\n■ Perform a bpverify of the affected image to determine if it is written correctly.\n■ ChecktheNetBackupProblemsreportforadditionalinformationabouttheerror.\n■ Verify the Media and Device Management and system configuration for the\ndrive.\nForexample,ifyoudonotconfigurethedriveforvariable-modeblocksizewrites\nonsomeUNIXsystems,thebackupimagesthatwritetothemediaproducethis\nerror when you attempt to restore the image.\nThe following sequence of events occurs:\n■ Backup succeeds.\n■ Verify succeeds.\n■ Restore fails.\nThe bptm debug log shows an error similar to the following:\n00:58:54 [2304] <16> write_data: write of 32768 bytes indicated\nonly 29696 bytes were written, errno = 0\nIn this case, configure the drive for variable-mode block sizes and suspend the\nmedia that writes on that device.\nSee the NetBackup Device Configuration Guide.\nThe images that were written to those media may be restorable (platform\ndependent),butsinglefilerestoresarealmostguaranteedtofail.Youcanexpire\nthese media and regenerate the backups. Or you can attempt to duplicate the\nimages on these media to another device and then expire the original copy.\n■ Thiserrorhasoccurredonre-labeledandvalue-added8-mmtapedriveswhere\nthe drive’s micro code incorrectly processes a forward space record SCSI\ncommand.\n■ If the problem is not one of those discussed, create a debug log directory for\neither bpdm or bptm and retry the operation. Check the resulting debug log file." }, "93": { "code": 93, - "desc": "Mídia manager found wrong tape in drive", + "desc": "Media manager found wrong tape in drive", "first_action": "Ifthevolumeisinarobotandtherobotsupportsbarcodes,performaCompare", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Ifthevolumeisinarobotandtherobotsupportsbarcodes,performaCompare\nContents com Volume Configuration robot inventory (on Windows) ou\nCompare robot contents com volume configuration robot inventory (UNIX).\nO resulting relatório shows o mídia ID que foi found e validates its slot\nnumberwithwhatisinthevolumeconfiguration.Then,eitherchangethephysical\nlocation in o robot ou change o volume configuration to show o correct\nslot.\n■ If o volume foi mounted on um nonrobotic drive, verifique que o correct volume\nfoi mounted e assigned." + "full_action": "Do the following, as appropriate:\n■ Ifthevolumeisinarobotandtherobotsupportsbarcodes,performaCompare\nContents with Volume Configuration robot inventory (on Windows) or\nCompare robot contents with volume configuration robot inventory (UNIX).\nThe resulting report shows the media ID that was found and validates its slot\nnumberwithwhatisinthevolumeconfiguration.Then,eitherchangethephysical\nlocation in the robot or change the volume configuration to show the correct\nslot.\n■ If the volume was mounted on a nonrobotic drive, verify that the correct volume\nwas mounted and assigned." }, "94": { "code": 94, - "desc": "Não é possível position to correct image", - "first_action": "Try o restauração on another drive if possible.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Try o restauração on another drive if possible.\n■ Para additional informação, verifique o seguinte:\n■ NetBackup Problemas relatório to determinar o dispositivo ou volume que caused\no erro\n■ System e erro logs para o system (UNIX)\n■ Event Viewer Application e System logs (Windows)\n■ Para detailed troubleshooting informação, create um debug log diretório para bptm\ne retry o operation. Verifique o resulting debug log arquivos." + "desc": "Cannot position to correct image", + "first_action": "Try the restore on another drive if possible.", + "full_action": "Do the following, as appropriate:\n■ Try the restore on another drive if possible.\n■ For additional information, check the following:\n■ NetBackup Problems report to determine the device or volume that caused\nthe error\n■ System and error logs for the system (UNIX)\n■ Event Viewer Application and System logs (Windows)\n■ For detailed troubleshooting information, create a debug log directory for bptm\nand retry the operation. Check the resulting debug log files." }, "95": { "code": 95, - "desc": "Mídia ID está não assigned to this host in o EMM banco de dados", - "first_action": "Run um NetBackup Mídia List relatório to determinar o valid", - "full_action": "Run um NetBackup Mídia List relatório to determinar o valid\nmídia IDs e their assigned hosts. Then, retry o comando com um valid mídia\nID e assigned host." + "desc": "Media ID is not assigned to this host in the EMM database", + "first_action": "Run a NetBackup Media List report to determine the valid", + "full_action": "Run a NetBackup Media List report to determine the valid\nmedia IDs and their assigned hosts. Then, retry the command with a valid media\nID and assigned host." }, "96": { "code": 96, "desc": "Unabletoallocatenewmediaforbackup,storageunithasnoneavailable", - "first_action": "If o armazenamento unidade está um robot com vazio slots, add more volumes (remember to", - "full_action": "Verifique o NetBackup Problemas relatório to determinar o\narmazenamento unidade que está fora de mídia.\n■ If o armazenamento unidade está um robot com vazio slots, add more volumes (remember to\nspecify o correct volume pool).\n■ If there estão não vazio slots, move some mídia to nonrobotic e then add\nnew volumes.\n■ If you have difficulty keeping track de seu disponível volumes, try o\navailable_media script:\nOn UNIX, this script está in:\n/usr/openv/netbackup/bin/goodies/available_media\nOn Windows, o script está in:\ninstall_path\\NetBackup\\bin\\goodies\\available_media.cm\nd\nThis script lists todos volumes in o volume configuration, e augments que\nlist com informação on o volumes currently assigned to NetBackup.\n■ Set up um scratch volume pool como um reserve de unassigned tapes. If NetBackup\nneeds um new tape e nenhum estão disponível in o current volume pool, it does\no seguinte: Moves um tape from o scratch pool into o volume pool que o\nbackup uses.\n■ If o armazenamento unidade e volume pool appear to have mídia, verifique o seguinte:\n■ Volume está não FROZEN ou SUSPENDED.\nVerifique para this condition por usando o NetBackup Mídia List relatório. If o\nvolume está frozen ou suspended, use o bpmedia comando to unfreeze ou\nunsuspend it (if que está wanted).\nVeja \"Frozen mídia troubleshooting considerations\" in o NetBackup\nTroubleshooting Guide.\n■ Volume has não expired ou excedido its maximum number de mounts.\n■ O EMM banco de dados host name para o dispositivo está correct.\nIf you change o EMM banco de dados host name, stop e restart o seguinte:\nO Mídia Manager dispositivo daemon, ltid, (if o servidor está UNIX ou Linux)\nou o NetBackup Dispositivo Manager service (if o servidor está um Windows\nsystem).\n■ O correct host está specified para o armazenamento unidade in o NetBackup\nconfiguration.\nO host conexão should be o servidor (master ou mídia) com drives\nconnected to it.\n■ O Mídia e Dispositivo Management volume configuration has mídia in o\ncorrect volume pool. Unassigned ou active mídia está disponível at o requerido\nretention level.\nUse o NetBackup Mídia List relatório to show o retention levels, volume\npools, e status (active e so on) para todos volumes. Use o NetBackup\nMídia Summary relatório to verifique para active volumes at o correct retention\nlevels.\n■ O NetBackup bptm process está rejected when it requests mídia from o vmd\nprocess (UNIX) ou o NetBackup Volume Manager service (Windows). O\ncause de this problema está que o process ou service não é possível determinar o name\nde o host que makes o request.\nThis erro can be due to um incorrect rede configuration que involves o\nseguinte:\n■ Multiple rede interfaces\n■ /etc/resolv.conf on those UNIX ou Linux systems que use it\n■ Executando DNS com reverse addressing não configurado\n■ Create bptm e vmd debug log directories e retry o operation.\n■ Examine o bptm debug log to verifique que bptm connects to o correct system.\nIf um erro está logged, examine o vmd log.\nOn UNIX, o vmd log está:\n/usr/openv/volmgr/debug/daemon/log.xxxxxx\nOn Windows, o vmd log está:\ninstall_path\\Volmgr\\debug\\daemon\\xxxxxx.log\n■ If this armazenamento unidade está new e this attempt to use it está o first, stop e restart\nNetBackup on o master servidor.\nNote: O mds unified logging arquivos (OID 143) usually show o NetBackup\nmídia selection process.\nMoretroubleshootinginformationinawizardformatisavailableforthisstatuscode." + "first_action": "If the storage unit is a robot with empty slots, add more volumes (remember to", + "full_action": "Check the NetBackup Problems report to determine the\nstorage unit that is out of media.\n■ If the storage unit is a robot with empty slots, add more volumes (remember to\nspecify the correct volume pool).\n■ If there are no empty slots, move some media to nonrobotic and then add\nnew volumes.\n■ If you have difficulty keeping track of your available volumes, try the\navailable_media script:\nOn UNIX, this script is in:\n/usr/openv/netbackup/bin/goodies/available_media\nOn Windows, the script is in:\ninstall_path\\NetBackup\\bin\\goodies\\available_media.cm\nd\nThis script lists all volumes in the volume configuration, and augments that\nlist with information on the volumes currently assigned to NetBackup.\n■ Set up a scratch volume pool as a reserve of unassigned tapes. If NetBackup\nneeds a new tape and none are available in the current volume pool, it does\nthe following: Moves a tape from the scratch pool into the volume pool that the\nbackup uses.\n■ If the storage unit and volume pool appear to have media, verify the following:\n■ Volume is not FROZEN or SUSPENDED.\nCheck for this condition by using the NetBackup Media List report. If the\nvolume is frozen or suspended, use the bpmedia command to unfreeze or\nunsuspend it (if that is wanted).\nSee \"Frozen media troubleshooting considerations\" in the NetBackup\nTroubleshooting Guide.\n■ Volume has not expired or exceeded its maximum number of mounts.\n■ The EMM database host name for the device is correct.\nIf you change the EMM database host name, stop and restart the following:\nThe Media Manager device daemon, ltid, (if the server is UNIX or Linux)\nor the NetBackup Device Manager service (if the server is a Windows\nsystem).\n■ The correct host is specified for the storage unit in the NetBackup\nconfiguration.\nThe host connection should be the server (master or media) with drives\nconnected to it.\n■ The Media and Device Management volume configuration has media in the\ncorrect volume pool. Unassigned or active media is available at the required\nretention level.\nUse the NetBackup Media List report to show the retention levels, volume\npools, and status (active and so on) for all volumes. Use the NetBackup\nMedia Summary report to check for active volumes at the correct retention\nlevels.\n■ The NetBackup bptm process is rejected when it requests media from the vmd\nprocess (UNIX) or the NetBackup Volume Manager service (Windows). The\ncause of this problem is that the process or service cannot determine the name\nof the host that makes the request.\nThis error can be due to an incorrect network configuration that involves the\nfollowing:\n■ Multiple network interfaces\n■ /etc/resolv.conf on those UNIX or Linux systems that use it\n■ Running DNS with reverse addressing not configured\n■ Create bptm and vmd debug log directories and retry the operation.\n■ Examine the bptm debug log to verify that bptm connects to the correct system.\nIf an error is logged, examine the vmd log.\nOn UNIX, the vmd log is:\n/usr/openv/volmgr/debug/daemon/log.xxxxxx\nOn Windows, the vmd log is:\ninstall_path\\Volmgr\\debug\\daemon\\xxxxxx.log\n■ If this storage unit is new and this attempt to use it is the first, stop and restart\nNetBackup on the master server.\nNote: The mds unified logging files (OID 143) usually show the NetBackup\nmedia selection process.\nMoretroubleshootinginformationinawizardformatisavailableforthisstatuscode." }, "97": { "code": 97, - "desc": "Solicitado mídia ID está in use, não é possível process request", - "first_action": "Retry o comando when o volume está não in use. Use", - "full_action": "Retry o comando when o volume está não in use. Use\no Dispositivo Monitor to determinar if o volume está in use." + "desc": "Requested media ID is in use, cannot process request", + "first_action": "Retry the command when the volume is not in use. Use", + "full_action": "Retry the command when the volume is not in use. Use\nthe Device Monitor to determine if the volume is in use." }, "98": { "code": 98, - "desc": "Erro requesting mídia (tpreq)", - "first_action": "Verifique o NetBackup Problemas relatório to determinar o reason para o falha.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Verifique o NetBackup Problemas relatório to determinar o reason para o falha.\nO most common cause está que o NetBackup Dispositivo Manager service (on\nWindows)ortheMediaManagerdevicedaemon(ltid)(onUNIX)isnotrunning.\nStart it if necessary.\n■ If you duplicate backups ou use Vault to duplicate backups, this erro could\nindicate o seguinte: O Alternate Ler Servidor does não have access to o\ntape onde o original backup resides." + "desc": "Error requesting media (tpreq)", + "first_action": "Check the NetBackup Problems report to determine the reason for the failure.", + "full_action": "Do the following, as appropriate:\n■ Check the NetBackup Problems report to determine the reason for the failure.\nThe most common cause is that the NetBackup Device Manager service (on\nWindows)ortheMediaManagerdevicedaemon(ltid)(onUNIX)isnotrunning.\nStart it if necessary.\n■ If you duplicate backups or use Vault to duplicate backups, this error could\nindicate the following: The Alternate Read Server does not have access to the\ntape where the original backup resides." }, "99": { "code": 99, - "desc": "NDMP backup falha NetBackup status codes 168 NetBackup status codes", - "first_action": "Verifique o NetBackup Todos Log Entradas relatório para more informação.", - "full_action": "Do o seguinte:\n■ Verifique o NetBackup Todos Log Entradas relatório para more informação.\n■ Try o seguinte commands from another master servidor ou mídia servidor:\n# tpautoconf -verifique ndmp_filer\n# tpautoconf -probe ndmp_host\nOn o filer, verifique que o NDMP service está executando. O verification process\ndepends on o filer.\nPara NetApp, run ndmpd status to verifique que o NDMP daemon está executando. If\nnão, execute ndmpd on e re-run ndmpd status to verifique.\n■ Change o NDMP wildcard to specify caminho names apenas. You não é possível use um\nwildcardcharacterthatalsomatchesafilename.Forexample,anNDMPbackup\nselection está /vol/vol_archive_01/autoit*. This specification matches caminho\nname /vol/vol_archive_01/autoit_01/, bit it also matches arquivo\nname/vol/vol_archive_01/autoit-v1-setup.exe." + "desc": "NDMP backup failure NetBackup status codes 168 NetBackup status codes", + "first_action": "Check the NetBackup All Log Entries report for more information.", + "full_action": "Do the following:\n■ Check the NetBackup All Log Entries report for more information.\n■ Try the following commands from another master server or media server:\n# tpautoconf -verify ndmp_filer\n# tpautoconf -probe ndmp_host\nOn the filer, verify that the NDMP service is running. The verification process\ndepends on the filer.\nFor NetApp, run ndmpd status to verify that the NDMP daemon is running. If\nnot, execute ndmpd on and re-run ndmpd status to verify.\n■ Change the NDMP wildcard to specify path names only. You cannot use a\nwildcardcharacterthatalsomatchesafilename.Forexample,anNDMPbackup\nselection is /vol/vol_archive_01/autoit*. This specification matches path\nname /vol/vol_archive_01/autoit_01/, bit it also matches file\nname/vol/vol_archive_01/autoit-v1-setup.exe." }, "100": { "code": 100, - "desc": "System erro ocorreu while processing usuário comando", - "first_action": "Enable debug logging para bparchive, bpbackup, bplist, ou bprestore (como", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Enable debug logging para bparchive, bpbackup, bplist, ou bprestore (como\nappropriate) por creating debug log directories para them.\nOn UNIX, if um nonroot usuário has problemas, verifique que o diretório que foi\ncreated has mode 666. Look para e correct qualquer reported errors.\n■ Retry o operation e verifique o resulting logs.\nIf o logs do não reveal o problema, use o command-line version de o\ncomando e correct qualquer problemas que estão reported on stderr." + "desc": "System error occurred while processing user command", + "first_action": "Enable debug logging for bparchive, bpbackup, bplist, or bprestore (as", + "full_action": "Do the following, as appropriate:\n■ Enable debug logging for bparchive, bpbackup, bplist, or bprestore (as\nappropriate) by creating debug log directories for them.\nOn UNIX, if a nonroot user has problems, verify that the directory that was\ncreated has mode 666. Look for and correct any reported errors.\n■ Retry the operation and check the resulting logs.\nIf the logs do not reveal the problem, use the command-line version of the\ncommand and correct any problems that are reported on stderr." }, "101": { "code": 101, - "desc": "Falhou opening mail pipe", + "desc": "Failed opening mail pipe", "first_action": "Makesurethatmailisconfiguredontheclient.Fordetailed", - "full_action": "Makesurethatmailisconfiguredontheclient.Fordetailed\ntroubleshooting informação, create um bpcd debug log diretório e retry o\noperation. Verifique o resulting bpcd debug log." + "full_action": "Makesurethatmailisconfiguredontheclient.Fordetailed\ntroubleshooting information, create a bpcd debug log directory and retry the\noperation. Check the resulting bpcd debug log." }, "102": { "code": 102, - "desc": "Falhou closing mail pipe", + "desc": "Failed closing mail pipe", "first_action": "Makesurethatmailisconfiguredontheclient.Fordetailed", - "full_action": "Makesurethatmailisconfiguredontheclient.Fordetailed\ntroubleshooting informação, create um bpcd debug log diretório e retry o\noperation. Verifique o resulting bpcd debug log." + "full_action": "Makesurethatmailisconfiguredontheclient.Fordetailed\ntroubleshooting information, create a bpcd debug log directory and retry the\noperation. Check the resulting bpcd debug log." }, "103": { "code": 103, - "desc": "Erro ocorreu during initialization, verifique configuration arquivo", - "first_action": "Create o 3pc.conf arquivo manually before executando o first", - "full_action": "Create o 3pc.conf arquivo manually before executando o first\nmultistreamdatamoverbackup.Usethefollowingcommandtocreatethe3pc.conf\narquivo:\n# bptpcinfo -um\nO 3pc.conf arquivo está created at /usr/openv/volmgr/database/3pc.conf.\nMore informação está disponível on o 3pc.conf arquivo e how to create it.\nVeja Configuring NetBackup para off-host data mover backups in o NetBackup\nSnapshot Cliente Configuration Guide." + "desc": "Error occurred during initialization, check configuration file", + "first_action": "Create the 3pc.conf file manually before running the first", + "full_action": "Create the 3pc.conf file manually before running the first\nmultistreamdatamoverbackup.Usethefollowingcommandtocreatethe3pc.conf\nfile:\n# bptpcinfo -a\nThe 3pc.conf file is created at /usr/openv/volmgr/database/3pc.conf.\nMore information is available on the 3pc.conf file and how to create it.\nSee Configuring NetBackup for off-host data mover backups in the NetBackup\nSnapshot Client Configuration Guide." }, "104": { "code": 104, - "desc": "Inválido arquivo pathname", - "first_action": "Nenhum", - "full_action": "Nenhum" + "desc": "Invalid file pathname", + "first_action": "None", + "full_action": "None" }, "105": { "code": 105, - "desc": "Arquivo pathname exceeds o maximum length allowed", - "first_action": "Shorten o current working diretório caminho length.", - "full_action": "Shorten o current working diretório caminho length." + "desc": "File pathname exceeds the maximum length allowed", + "first_action": "Shorten the current working directory path length.", + "full_action": "Shorten the current working directory path length." }, "106": { "code": 106, - "desc": "Inválido arquivo pathname found, não é possível process request", - "first_action": "Verifique que o cheio caminho names estão used e que they do não exceed o", - "full_action": "Do one ou more de o seguinte:\n■ Verifique que o cheio caminho names estão used e que they do não exceed o\nmaximumpathlengthforthesystem.(OnUNIX,theystartwithaslashcharacter\n[ / ].)\n■ Verifique que o arquivos exist e que o permissions allow NetBackup to access\nthem.\n■ Some NDMP servers do não support directory-level expansion. Some NDMP\nfiler vendors do não have o APIs que estão used to support wildcard characters\nlower than o volume level. Para example, /fs1/dir* está não um supported backup\nselection specification on EMC filers." + "desc": "Invalid file pathname found, cannot process request", + "first_action": "Verify that the full path names are used and that they do not exceed the", + "full_action": "Do one or more of the following:\n■ Verify that the full path names are used and that they do not exceed the\nmaximumpathlengthforthesystem.(OnUNIX,theystartwithaslashcharacter\n[ / ].)\n■ Verify that the files exist and that the permissions allow NetBackup to access\nthem.\n■ Some NDMP servers do not support directory-level expansion. Some NDMP\nfiler vendors do not have the APIs that are used to support wildcard characters\nlower than the volume level. For example, /fs1/dir* is not a supported backup\nselection specification on EMC filers." }, "108": { "code": 108, - "desc": "Ação succeeded but auditing falhou", - "first_action": "Garanta que o nbaudit daemon (NetBackup Audit Manager) está executando.", - "full_action": "Do o seguinte:\n■ Garanta que o nbaudit daemon (NetBackup Audit Manager) está executando.\n■ Examine o logs responsible para o primary ação e o nbaudit logs para\nmore details on o cause de o erro. Para example, verifique o bpdbm logs para\npolicy creation." + "desc": "Action succeeded but auditing failed", + "first_action": "Ensure that the nbaudit daemon (NetBackup Audit Manager) is running.", + "full_action": "Do the following:\n■ Ensure that the nbaudit daemon (NetBackup Audit Manager) is running.\n■ Examine the logs responsible for the primary action and the nbaudit logs for\nmore details on the cause of the error. For example, check the bpdbm logs for\npolicy creation." }, "109": { "code": 109, - "desc": "Inválido date specified", + "desc": "Invalid date specified", "first_action": "Iftheerroroccurredonacommandline,examinethestandarderroroutputfrom", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Iftheerroroccurredonacommandline,examinethestandarderroroutputfrom\no comando para um explanatory message.\n■ Refertotheformatforthedateoptionsintheusagestatementforthecommand.\nLook up o locale de o master servidor. Compare o date format de que locale\ncom o date format on o uso statement para o comando.\n■ Verifique o NetBackup Problemas relatório para pistas.\n■ If o erro appears in um Java interface, enable o debug print manager in o\nJava startup arquivo. Retry e compare o parameters que estão logged in o Java\nlog com o parameters listed in o command’s uso statement.\n■ If these actions do não reveal o problema, create um debug log diretório para o\nprocess que returned this status code. Then retry o operation e verifique o\nresulting debug log.\n■ If o erro appears in o web UI while performing um Microsoft SQL Servidor\nrestauração, review o date provided. O date must be in ISO 8601 format." + "full_action": "Do the following, as appropriate:\n■ Iftheerroroccurredonacommandline,examinethestandarderroroutputfrom\nthe command for an explanatory message.\n■ Refertotheformatforthedateoptionsintheusagestatementforthecommand.\nLook up the locale of the master server. Compare the date format of that locale\nwith the date format on the usage statement for the command.\n■ Check the NetBackup Problems report for clues.\n■ If the error appears in a Java interface, enable the debug print manager in the\nJava startup file. Retry and compare the parameters that are logged in the Java\nlog with the parameters listed in the command’s usage statement.\n■ If these actions do not reveal the problem, create a debug log directory for the\nprocess that returned this status code. Then retry the operation and check the\nresulting debug log.\n■ If the error appears in the web UI while performing a Microsoft SQL Server\nrestore, review the date provided. The date must be in ISO 8601 format." }, "110": { "code": 110, - "desc": "Não é possível find o NetBackup configuration informação", - "first_action": "On Windows, reinstall NetBackup software on o cliente.", - "full_action": "On Windows, reinstall NetBackup software on o cliente.\nOn UNIX, create um /usr/openv/netbackup/bp.conf arquivo com at least o seguinte\nlines:\nServidor = server_name\nCLIENT_NAME = client_name" + "desc": "Cannot find the NetBackup configuration information", + "first_action": "On Windows, reinstall NetBackup software on the client.", + "full_action": "On Windows, reinstall NetBackup software on the client.\nOn UNIX, create a /usr/openv/netbackup/bp.conf file with at least the following\nlines:\nSERVER = server_name\nCLIENT_NAME = client_name" }, "111": { "code": 111, - "desc": "Não entry foi found in o servidor list", - "first_action": "On um UNIX cliente, add o seguinte line to o top de o", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ On um UNIX cliente, add o seguinte line to o top de o\n/usr/openv/netbackup/bp.conf arquivo:\nServidor = server_name\n■ On um Microsoft Windows cliente, add o servidor name on o Servidor to use para\nbackups e restores drop-down in o Specify NetBackup Machines e\nPolicy Type dialog box. To display this dialog box, start o Backup, Archive,\ne Restauração interface on o cliente. Then click Specify NetBackup Machines\ne Policy Type on o Arquivo menu." + "desc": "No entry was found in the server list", + "first_action": "On a UNIX client, add the following line to the top of the", + "full_action": "Do the following, as appropriate:\n■ On a UNIX client, add the following line to the top of the\n/usr/openv/netbackup/bp.conf file:\nSERVER = server_name\n■ On a Microsoft Windows client, add the server name on the Server to use for\nbackups and restores drop-down in the Specify NetBackup Machines and\nPolicy Type dialog box. To display this dialog box, start the Backup, Archive,\nand Restore interface on the client. Then click Specify NetBackup Machines\nand Policy Type on the File menu." }, "112": { "code": 112, - "desc": "Undefined erro ou there estão não arquivos specified in o policy backup selection.", - "first_action": "Specify at least one arquivo to be restored.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Specify at least one arquivo to be restored.\n■ This status code may occur if nbjm está executando e um stream discovery fails to\nfind todos stream arquivos. Examine o nbjm unified log (originator ID 117) para more\ndetails on o cause de o erro.\n■ Garanta que o correct backup selections estão specified in o policy e they\nestão in o correct format.\nO supported backup selection estão:\n■ Para subscription: /Subscription IDif Subscription ID está\n1950a258-227b-4e31-a9cf-717495945fc2thenspecifythebackupselection\ncomo - / 1950a258-227b-4e31-a9cf-717495945fc2\n■ Forresourcegroup:/Subscription ID/Resource Groupif Subscription\nID está 1950a258-227b-4e31-a9cf-717495945fc2 e Resource Group\nname está TestRG, specify o backup selection como - /\n1950a258-227b-4e31-a9cf-717495945fc2/TestRG\n■ Para VM Name: /Subscription ID/Resoutrce Group/VM Nameif\nSubscription ID está 1950a258-227b-4e31-a9cf-717495945fc2,Resource\nGroup name está TestRG, e o VM name está MyVM, specify o backup\nselection como - / 1950a258-227b-4e31-a9cf-717495945fc2/TestRG/MyVM\nWhen performing um backup ou restauração de um Cassandra banco de dados, executar o\nseguinte como appropriate:\n■ Verifique que o seguinte setting está commented fora from o sudoers list on\nCassandra nodes:\n#Defaults:!requiretty" + "desc": "Undefined error or there are no files specified in the policy backup selection.", + "first_action": "Specify at least one file to be restored.", + "full_action": "Do the following, as appropriate:\n■ Specify at least one file to be restored.\n■ This status code may occur if nbjm is running and a stream discovery fails to\nfind all stream files. Examine the nbjm unified log (originator ID 117) for more\ndetails on the cause of the error.\n■ Ensure that the correct backup selections are specified in the policy and they\nare in the correct format.\nThe supported backup selection are:\n■ For subscription: /Subscription IDif Subscription ID is\n1950a258-227b-4e31-a9cf-717495945fc2thenspecifythebackupselection\nas - / 1950a258-227b-4e31-a9cf-717495945fc2\n■ Forresourcegroup:/Subscription ID/Resource Groupif Subscription\nID is 1950a258-227b-4e31-a9cf-717495945fc2 and Resource Group\nname is TestRG, specify the backup selection as - /\n1950a258-227b-4e31-a9cf-717495945fc2/TestRG\n■ For VM Name: /Subscription ID/Resoutrce Group/VM Nameif\nSubscription ID is 1950a258-227b-4e31-a9cf-717495945fc2,Resource\nGroup name is TestRG, and the VM name is MyVM, specify the backup\nselection as - / 1950a258-227b-4e31-a9cf-717495945fc2/TestRG/MyVM\nWhen performing a backup or restore of a Cassandra database, perform the\nfollowing as appropriate:\n■ Verify that the following setting is commented out from the sudoers list on\nCassandra nodes:\n#Defaults:!requiretty" }, "114": { "code": 114, - "desc": "Não implementado erro code", + "desc": "Unimplemented error code", "first_action": "Examinethenbjmunifiedlog(originatorID117)fordetailed", - "full_action": "Examinethenbjmunifiedlog(originatorID117)fordetailed\ninformação on o cause de o erro." + "full_action": "Examinethenbjmunifiedlog(originatorID117)fordetailed\ninformation on the cause of the error." }, "116": { "code": 116, - "desc": "VxSS authentication falhou", + "desc": "VxSS authentication failed", "first_action": "EnsurethattheVeritasProductAuthenticationServiceisinstalledandconfigured.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ EnsurethattheVeritasProductAuthenticationServiceisinstalledandconfigured.\nForcompleteinstallationinstructions,seetheNetBackupSecurityandEncryption\nGuide.\n■ Verifique que both parties have um valid certificate. Examine o expiry date que está\nlisted from um bpnbat -WhoAmI. Para example:\nbpnbat -WhoAmI\nName: JDOG\nDomain: MYCOMPANY\nIssued por: /CN=broker/OU=root@machine1.mycompany.com/O=vx\nExpiry Date: Sep 19 12:51:55 2009 GMT\nAuthentication method: Microsoft Windows\nOperation completed successfully.\nShows um expiry date de September 19th, 2009. After 12:51:55 GMT this\ncredential está não longer valid e um new credential está requerido.\n■ If you run from o NetBackup Administration Console, fechar e reopen o\nconsole. O console automatically obtains um credential para o currently logged\nin identity, if possible. Por default, these certificates estão valid para 24 hours. O\nseguinte está um example de how to extend o credential beyond 24 hours to 30\ndays (2592000 seconds):\nWindows: \\veritas\\netbackup\\sec\\at\\bin\\vssat\nsetexpiryintervals -p -t -e 2592000\nUNIX: usr/openv/netbackup/sec/at/bin/vssat setexpiryintervals -p\n -t -e 2592000\n■ Garanta que o certificates para both sides use o same broker ou estão children\nde o same raiz broker e que trusts estão established between them.\nVeja o NetBackup Security e Encryption Guide para more informação on\nbroker hierarchies e how to establish trust relationships between brokers.\n■ Garanta que connectivity between o physical systems in question está possible.\nIf general sockets não é possível conectar between o computers (such como ping e\ntelnet), issues within o rede unrelated to NetBackup can cause this\nproblema.\n■ Garanta que o system has sufficient swap space e o seguinte directories\nestão não cheio:\n■ /home/username\n■ /usr/openv/netbackup/logs\n■ /tmp" + "full_action": "Do the following, as appropriate:\n■ EnsurethattheVeritasProductAuthenticationServiceisinstalledandconfigured.\nForcompleteinstallationinstructions,seetheNetBackupSecurityandEncryption\nGuide.\n■ Check that both parties have a valid certificate. Examine the expiry date that is\nlisted from a bpnbat -WhoAmI. For example:\nbpnbat -WhoAmI\nName: JDOG\nDomain: MYCOMPANY\nIssued by: /CN=broker/OU=root@machine1.mycompany.com/O=vx\nExpiry Date: Sep 19 12:51:55 2009 GMT\nAuthentication method: Microsoft Windows\nOperation completed successfully.\nShows an expiry date of September 19th, 2009. After 12:51:55 GMT this\ncredential is no longer valid and a new credential is required.\n■ If you run from the NetBackup Administration Console, close and reopen the\nconsole. The console automatically obtains a credential for the currently logged\nin identity, if possible. By default, these certificates are valid for 24 hours. The\nfollowing is an example of how to extend the credential beyond 24 hours to 30\ndays (2592000 seconds):\nWindows: \\veritas\\netbackup\\sec\\at\\bin\\vssat\nsetexpiryintervals -p -t -e 2592000\nUNIX: usr/openv/netbackup/sec/at/bin/vssat setexpiryintervals -p\n -t -e 2592000\n■ Ensure that the certificates for both sides use the same broker or are children\nof the same root broker and that trusts are established between them.\nSee the NetBackup Security and Encryption Guide for more information on\nbroker hierarchies and how to establish trust relationships between brokers.\n■ Ensure that connectivity between the physical systems in question is possible.\nIf general sockets cannot connect between the computers (such as ping and\ntelnet), issues within the network unrelated to NetBackup can cause this\nproblem.\n■ Ensure that the system has sufficient swap space and the following directories\nare not full:\n■ /home/username\n■ /usr/openv/netbackup/logs\n■ /tmp" }, "117": { "code": 117, - "desc": "VxSS access negada Recomendada Ação: Do o seguinte, como appropriate: ■ If you use o default groups, make certain que o usuário attempts to executar um operationappropriateforthatgroup.Forexample,amemberofNBU_Operators está não foi possível to modify policy informação, which está um permissão reserved para administrator roles. ■ Garanta que o system has sufficient swap space e o seguinte directories estão não cheio: ■ /home/username ■ /usr/openv/netbackup/logs NetBackup status codes 176 NetBackup status codes ■ /tmp ■ If you use seu own defined groups e permissions, first determinar o object com which o operation está associated. Then, add o permissions relative to o ação. Para example, um usuário está requerido to up e down drives but currently does não have permissão to do so. Verifique que o usuário belongs to o correct authorization group. If necessary, verifique que o group has Up e Down permissions on o Drive object within o Group Permissão tab. If necessary, aumentar o verbosity level de NetBackup to locate what object e what permissions estão requerido para o failing request. O pertinent lines in o debug logs look similar to o seguinte: 17:19:27.653 [904.872] <2> GetAzinfo: Peer Cred Info. Name: JMIZZLE Domain: MYCOMPANY Expiry: Sep 24 21:45:32 2003 GMT Issued por: /CN=broker/OU=root@machine1.mycompany.com/O=vx AuthType: 1 17:19:37.077 [904.872] <2> VssAzAuthorize: vss_az.cpp.5082: Function: VssAzAuthorize. Object NBU_RES_Drives 17:19:37.077 [904.872] <2> VssAzAuthorize: vss_az.cpp.5083: Function: VssAzAuthorize. Permissions Up 17:19:40.171 [904.872] <2> VssAzAuthorize: vss_az.cpp.5166: Function: VssAzAuthorize. 20 Permissão negada. Inthisexample,theuserJMIZZLEattemptstoperformanoperationthatrequires o Up permissão on o Drives object. To diagnose o problema, examine o groups to which o usuário belongs to garanta que o appropriate group includes o Up permissão. (Up está um member de o Operate permissão set para Drives.) ■ If you have performed disaster recovery e estão now executando catalog recovery usando o Remote Administration Console, you need to restart o master servidor services. After o restart, if you do não log fora from o Remote AdministrationConsoleandtrytoaccesstheSecurityManagementtab,you receive this erro message e must log on again. Click here to view technical notes e other informação on o Cohesity Technical Support website about this status code.", - "first_action": "If you use o default groups, make certain que o usuário attempts to executar um", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ If you use o default groups, make certain que o usuário attempts to executar um\noperationappropriateforthatgroup.Forexample,amemberofNBU_Operators\nestá não foi possível to modify policy informação, which está um permissão reserved para\nadministrator roles.\n■ Garanta que o system has sufficient swap space e o seguinte directories\nestão não cheio:\n■ /home/username\n■ /usr/openv/netbackup/logs\n■ /tmp\n■ If you use seu own defined groups e permissions, first determinar o object\ncom which o operation está associated. Then, add o permissions relative to\no ação. Para example, um usuário está requerido to up e down drives but currently\ndoes não have permissão to do so. Verifique que o usuário belongs to o correct\nauthorization group.\nIf necessary, verifique que o group has Up e Down permissions on o Drive\nobject within o Group Permissão tab. If necessary, aumentar o verbosity\nlevel de NetBackup to locate what object e what permissions estão requerido para\no failing request. O pertinent lines in o debug logs look similar to o\nseguinte:\n17:19:27.653 [904.872] <2> GetAzinfo: Peer Cred Info.\nName: JMIZZLE\nDomain: MYCOMPANY\nExpiry: Sep 24 21:45:32 2003 GMT\nIssued por: /CN=broker/OU=root@machine1.mycompany.com/O=vx\nAuthType: 1\n17:19:37.077 [904.872] <2> VssAzAuthorize: vss_az.cpp.5082:\nFunction: VssAzAuthorize. Object\nNBU_RES_Drives\n17:19:37.077 [904.872] <2> VssAzAuthorize: vss_az.cpp.5083:\nFunction: VssAzAuthorize. Permissions Up\n17:19:40.171 [904.872] <2> VssAzAuthorize: vss_az.cpp.5166:\nFunction: VssAzAuthorize. 20 Permissão negada.\nInthisexample,theuserJMIZZLEattemptstoperformanoperationthatrequires\no Up permissão on o Drives object. To diagnose o problema, examine o\ngroups to which o usuário belongs to garanta que o appropriate group includes\no Up permissão. (Up está um member de o Operate permissão set para Drives.)\n■ If you have performed disaster recovery e estão now executando catalog recovery\nusando o Remote Administration Console, you need to restart o master\nservidor services. After o restart, if you do não log fora from o Remote\nAdministrationConsoleandtrytoaccesstheSecurityManagementtab,you\nreceive this erro message e must log on again." + "desc": "VxSS access denied Recommended Action: Do the following, as appropriate: ■ If you use the default groups, make certain that the user attempts to perform an operationappropriateforthatgroup.Forexample,amemberofNBU_Operators is unable to modify policy information, which is a permission reserved for administrator roles. ■ Ensure that the system has sufficient swap space and the following directories are not full: ■ /home/username ■ /usr/openv/netbackup/logs NetBackup status codes 176 NetBackup status codes ■ /tmp ■ If you use your own defined groups and permissions, first determine the object with which the operation is associated. Then, add the permissions relative to the action. For example, a user is required to up and down drives but currently does not have permission to do so. Verify that the user belongs to the correct authorization group. If necessary, verify that the group has Up and Down permissions on the Drive object within the Group Permission tab. If necessary, increase the verbosity level of NetBackup to locate what object and what permissions are required for the failing request. The pertinent lines in the debug logs look similar to the following: 17:19:27.653 [904.872] <2> GetAzinfo: Peer Cred Info. Name: JMIZZLE Domain: MYCOMPANY Expiry: Sep 24 21:45:32 2003 GMT Issued by: /CN=broker/OU=root@machine1.mycompany.com/O=vx AuthType: 1 17:19:37.077 [904.872] <2> VssAzAuthorize: vss_az.cpp.5082: Function: VssAzAuthorize. Object NBU_RES_Drives 17:19:37.077 [904.872] <2> VssAzAuthorize: vss_az.cpp.5083: Function: VssAzAuthorize. Permissions Up 17:19:40.171 [904.872] <2> VssAzAuthorize: vss_az.cpp.5166: Function: VssAzAuthorize. 20 Permission denied. Inthisexample,theuserJMIZZLEattemptstoperformanoperationthatrequires the Up permission on the Drives object. To diagnose the problem, examine the groups to which the user belongs to ensure that the appropriate group includes the Up permission. (Up is a member of the Operate permission set for Drives.) ■ If you have performed disaster recovery and are now running catalog recovery using the Remote Administration Console, you need to restart the master server services. After the restart, if you do not log out from the Remote AdministrationConsoleandtrytoaccesstheSecurityManagementtab,you receive this error message and must log on again. Click here to view technical notes and other information on the Cohesity Technical Support website about this status code.", + "first_action": "If you use the default groups, make certain that the user attempts to perform an", + "full_action": "Do the following, as appropriate:\n■ If you use the default groups, make certain that the user attempts to perform an\noperationappropriateforthatgroup.Forexample,amemberofNBU_Operators\nis unable to modify policy information, which is a permission reserved for\nadministrator roles.\n■ Ensure that the system has sufficient swap space and the following directories\nare not full:\n■ /home/username\n■ /usr/openv/netbackup/logs\n■ /tmp\n■ If you use your own defined groups and permissions, first determine the object\nwith which the operation is associated. Then, add the permissions relative to\nthe action. For example, a user is required to up and down drives but currently\ndoes not have permission to do so. Verify that the user belongs to the correct\nauthorization group.\nIf necessary, verify that the group has Up and Down permissions on the Drive\nobject within the Group Permission tab. If necessary, increase the verbosity\nlevel of NetBackup to locate what object and what permissions are required for\nthe failing request. The pertinent lines in the debug logs look similar to the\nfollowing:\n17:19:27.653 [904.872] <2> GetAzinfo: Peer Cred Info.\nName: JMIZZLE\nDomain: MYCOMPANY\nExpiry: Sep 24 21:45:32 2003 GMT\nIssued by: /CN=broker/OU=root@machine1.mycompany.com/O=vx\nAuthType: 1\n17:19:37.077 [904.872] <2> VssAzAuthorize: vss_az.cpp.5082:\nFunction: VssAzAuthorize. Object\nNBU_RES_Drives\n17:19:37.077 [904.872] <2> VssAzAuthorize: vss_az.cpp.5083:\nFunction: VssAzAuthorize. Permissions Up\n17:19:40.171 [904.872] <2> VssAzAuthorize: vss_az.cpp.5166:\nFunction: VssAzAuthorize. 20 Permission denied.\nInthisexample,theuserJMIZZLEattemptstoperformanoperationthatrequires\nthe Up permission on the Drives object. To diagnose the problem, examine the\ngroups to which the user belongs to ensure that the appropriate group includes\nthe Up permission. (Up is a member of the Operate permission set for Drives.)\n■ If you have performed disaster recovery and are now running catalog recovery\nusing the Remote Administration Console, you need to restart the master\nserver services. After the restart, if you do not log out from the Remote\nAdministrationConsoleandtrytoaccesstheSecurityManagementtab,you\nreceive this error message and must log on again." }, "118": { "code": 118, - "desc": "VxSS authorization falhou NetBackup status codes 177 NetBackup status codes", - "first_action": "Garanta que o Cohesity Produto Authorization Service ou daemon está executando.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Garanta que o Cohesity Produto Authorization Service ou daemon está executando.\nVeja o NetBackup Security e Encryption Guide para more informação on\nauthentication e authorization daemons.\n■ Garanta que you estão in communication com o correct master servidor. Within\no bp.conf arquivos on o local servidor, verifique que o entry\nAUTHORIZATION_SERVICESspecifiestheproperhostname(fullyqualified)ofthe\nauthorization service. Para example, AUTHORIZATION_SERVICE =\nmachine2.mycompany.com 0 specifies que o servidor contacts machine2 to\nexecutar authorization checks. Also garanta que this entry matches que de o\nmaster servidor.\n■ Garanta que o system has sufficient swap space e o seguinte directories\nestão não cheio:\n■ /home/userName\n■ /usr/openv/netbackup/logs\n■ /tmp\n■ Garanta que o servidor que contacts o master has um valid certificate. O\ncomputer certificate can be examined como follows:\nPara UNIX:\n# bpnbat -WhoAmI -cf\n/usr/openv/var/vxss/credentials/machine3.mycompany.com\nPara Windows:\nBpnbat WhoAmI -cf \"c:\\Program\nFiles\\VERITAS\\NetBackup\\var\\vxss\\credentials\\machine3.my\ncompany.com\"\nBoth de which would return:\nName: machine3.mycompany.com\nDomain: NBU_Machines@machine2.mycompany.com\nIssued por: /CN=broker/OU=root@machine2.mycompany.com/O=vx\nExpiry Date: Sep 2 19:25:29 2004 GMT\nAuthentication method: Veritas Private Security\nOperation completed successfully.\nIf o expiry date foi excedido, use bpnbat -LoginMachine to obtain um new\ncredential para o computer.\nSeetheNetBackupCommandsReferenceGuideformoreinformationonbpnbat.\nTheserverthatattemptsthecheckisnotauthorizedtoexaminetheauthorization\nbanco de dados. Garanta que bpnbaz -ShowAuthorizers re-tuned o computer's\nidentity.Ensurethatthecomputerhasacomputercredentialunderthedirectory\ncomo follows:\nProgram Files\\VERITAS\\var\\vxss\\credentials (Windows)\n/usr/openv/var/vxss/credentials (UNIX)\nThis credential should have o cheio name de o computer como in o seguinte\nexample: machine1.company.com.\n■ Checkthatthemaximumnumberofopensocketstotheauthorizationdatabase\nfoi não exhausted. Use netstat to determinar o number de sockets que estão\nopened to port 4032 on o authorization servidor e que refer to o seguinte\nconfigurations:\nWindows:\nHKLM\\SOFTWARE\\VERITAS\\Security\\Authorization\\Communication\\ClientMaxConnections\nUNIX: /etc/vx/vss/VRTSaz.conf entryClientMaxConnections\nIf o maximum number de abrir connections foi reached, you may need to\nincreasethenumberofmaximumopenconnections.Anincreaseinthenumber\nofopenconnectionsincreasesthememoryfootprintoftheauthorizationservice\nordaemon.Notethatextremeincreasesinthemaximumnumberofconnections\ncan cause performance degradation." + "desc": "VxSS authorization failed NetBackup status codes 177 NetBackup status codes", + "first_action": "Ensure that the Cohesity Product Authorization Service or daemon is running.", + "full_action": "Do the following, as appropriate:\n■ Ensure that the Cohesity Product Authorization Service or daemon is running.\nSee the NetBackup Security and Encryption Guide for more information on\nauthentication and authorization daemons.\n■ Ensure that you are in communication with the correct master server. Within\nthe bp.conf files on the local server, verify that the entry\nAUTHORIZATION_SERVICESspecifiestheproperhostname(fullyqualified)ofthe\nauthorization service. For example, AUTHORIZATION_SERVICE =\nmachine2.mycompany.com 0 specifies that the server contacts machine2 to\nperform authorization checks. Also ensure that this entry matches that of the\nmaster server.\n■ Ensure that the system has sufficient swap space and the following directories\nare not full:\n■ /home/userName\n■ /usr/openv/netbackup/logs\n■ /tmp\n■ Ensure that the server that contacts the master has a valid certificate. The\ncomputer certificate can be examined as follows:\nFor UNIX:\n# bpnbat -WhoAmI -cf\n/usr/openv/var/vxss/credentials/machine3.mycompany.com\nFor Windows:\nBpnbat WhoAmI -cf \"c:\\Program\nFiles\\VERITAS\\NetBackup\\var\\vxss\\credentials\\machine3.my\ncompany.com\"\nBoth of which would return:\nName: machine3.mycompany.com\nDomain: NBU_Machines@machine2.mycompany.com\nIssued by: /CN=broker/OU=root@machine2.mycompany.com/O=vx\nExpiry Date: Sep 2 19:25:29 2004 GMT\nAuthentication method: Veritas Private Security\nOperation completed successfully.\nIf the expiry date was exceeded, use bpnbat -LoginMachine to obtain a new\ncredential for the computer.\nSeetheNetBackupCommandsReferenceGuideformoreinformationonbpnbat.\nTheserverthatattemptsthecheckisnotauthorizedtoexaminetheauthorization\ndatabase. Ensure that bpnbaz -ShowAuthorizers re-tuned the computer's\nidentity.Ensurethatthecomputerhasacomputercredentialunderthedirectory\nas follows:\nProgram Files\\VERITAS\\var\\vxss\\credentials (Windows)\n/usr/openv/var/vxss/credentials (UNIX)\nThis credential should have the full name of the computer as in the following\nexample: machine1.company.com.\n■ Checkthatthemaximumnumberofopensocketstotheauthorizationdatabase\nwas not exhausted. Use netstat to determine the number of sockets that are\nopened to port 4032 on the authorization server and that refer to the following\nconfigurations:\nWindows:\nHKLM\\SOFTWARE\\VERITAS\\Security\\Authorization\\Communication\\ClientMaxConnections\nUNIX: /etc/vx/vss/VRTSaz.conf entryClientMaxConnections\nIf the maximum number of open connections was reached, you may need to\nincreasethenumberofmaximumopenconnections.Anincreaseinthenumber\nofopenconnectionsincreasesthememoryfootprintoftheauthorizationservice\nordaemon.Notethatextremeincreasesinthemaximumnumberofconnections\ncan cause performance degradation." }, "120": { "code": 120, - "desc": "Não é possível find configuration banco de dados record para solicitado NB banco de dados backup", + "desc": "Cannot find configuration database record for requested NB database backup", "first_action": "ChecktheNetBackupProblemsreportforadditionalinformationabouttheerror.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ ChecktheNetBackupProblemsreportforadditionalinformationabouttheerror.\n■ Para detailed troubleshooting informação, create admin e bpdbm debug log\ndirectories e retry o operation. Verifique o resulting debug logs.\n■ Contate customer support e send o appropriate problema e debug log\nsections que detail o erro." + "full_action": "Do the following, as appropriate:\n■ ChecktheNetBackupProblemsreportforadditionalinformationabouttheerror.\n■ For detailed troubleshooting information, create admin and bpdbm debug log\ndirectories and retry the operation. Check the resulting debug logs.\n■ Contact customer support and send the appropriate problem and debug log\nsections that detail the error." }, "121": { "code": 121, - "desc": "Não mídia está defined para o solicitado NB banco de dados backup", - "first_action": "Add o mídia IDs to o catalog backup configuration.", - "full_action": "Add o mídia IDs to o catalog backup configuration.\nVerifique que o mídia IDs estão in o NetBackup volume pool." + "desc": "No media is defined for the requested NB database backup", + "first_action": "Add the media IDs to the catalog backup configuration.", + "full_action": "Add the media IDs to the catalog backup configuration.\nVerify that the media IDs are in the NetBackup volume pool." }, "122": { "code": 122, - "desc": "Specified dispositivo caminho does não exist", - "first_action": "Retry o comando por usando um valid dispositivo arquivo name.", - "full_action": "Retry o comando por usando um valid dispositivo arquivo name." + "desc": "Specified device path does not exist", + "first_action": "Retry the command by using a valid device file name.", + "full_action": "Retry the command by using a valid device file name." }, "123": { "code": 123, - "desc": "Specified disco caminho está não um diretório", - "first_action": "Specify um different disco caminho para o catalog backup ou", - "full_action": "Specify um different disco caminho para o catalog backup ou\nexcluir o arquivo que already exists." + "desc": "Specified disk path is not a directory", + "first_action": "Specify a different disk path for the catalog backup or", + "full_action": "Specify a different disk path for the catalog backup or\ndelete the file that already exists." }, "124": { "code": 124, - "desc": "NB banco de dados backup falhou, um caminho foi não found ou está inaccessible", + "desc": "NB database backup failed, a path was not found or is inaccessible", "first_action": "ChecktheNetBackupProblemsreportforadditionalinformationabouttheerror.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ ChecktheNetBackupProblemsreportforadditionalinformationabouttheerror.\nO seguinte estão some possible causes:\n■ O caminho does não exist.\n■ On um UNIX system, one de o paths contains um symbolic link.\n■ After you determinar which caminho não é possível be accessed, correct o caminho names in\no catalog backup configuration." + "full_action": "Do the following, as appropriate:\n■ ChecktheNetBackupProblemsreportforadditionalinformationabouttheerror.\nThe following are some possible causes:\n■ The path does not exist.\n■ On a UNIX system, one of the paths contains a symbolic link.\n■ After you determine which path cannot be accessed, correct the path names in\nthe catalog backup configuration." }, "125": { "code": 125, - "desc": "Um NetBackup catalog backup está in progress", - "first_action": "Retry o operation after o catalog backup completes.", - "full_action": "Retry o operation after o catalog backup completes." + "desc": "A NetBackup catalog backup is in progress", + "first_action": "Retry the operation after the catalog backup completes.", + "full_action": "Retry the operation after the catalog backup completes." }, "126": { "code": 126, - "desc": "NB banco de dados backup header está too large, too many paths specified", - "first_action": "Excluir some de o paths from o catalog backup", - "full_action": "Excluir some de o paths from o catalog backup\nconfiguration." + "desc": "NB database backup header is too large, too many paths specified", + "first_action": "Delete some of the paths from the catalog backup", + "full_action": "Delete some of the paths from the catalog backup\nconfiguration." }, "127": { "code": 127, - "desc": "Specified mídia ou caminho does não contain um valid NB banco de dados backup header", - "first_action": "Validate que o correct mídia ID está used.", - "full_action": "Validate que o correct mídia ID está used." + "desc": "Specified media or path does not contain a valid NB database backup header", + "first_action": "Validate that the correct media ID is used.", + "full_action": "Validate that the correct media ID is used." }, "128": { "code": 128, "desc": "NBdatabaserecoveryfailed,aprocesshasencounteredanexceptional condition", "first_action": "Fixtheproblemthatwasreportedintheerrormessageinthebprecoveroutput.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Fixtheproblemthatwasreportedintheerrormessageinthebprecoveroutput.\n■ Identify which NetBackup services to shut down before um NetBackup banco de dados\nrecovery attempt:\nSee\"AboutrecoveringtheNetBackupcatalog\"intheNetBackupTroubleshooting\nGuide.\nO NetBackup services should be shut down except para o NetBackup Cliente\nService, which must be executando para o banco de dados recovery to succeed.\n■ ChecktheNetBackupProblemsreportforadditionalinformationabouttheerror.\nO seguinte estão some possible causes:\n■ Um disco may be cheio.\n■ O NetBackup catalog tape may be corrupt." + "full_action": "Do the following, as appropriate:\n■ Fixtheproblemthatwasreportedintheerrormessageinthebprecoveroutput.\n■ Identify which NetBackup services to shut down before a NetBackup database\nrecovery attempt:\nSee\"AboutrecoveringtheNetBackupcatalog\"intheNetBackupTroubleshooting\nGuide.\nThe NetBackup services should be shut down except for the NetBackup Client\nService, which must be running for the database recovery to succeed.\n■ ChecktheNetBackupProblemsreportforadditionalinformationabouttheerror.\nThe following are some possible causes:\n■ A disk may be full.\n■ The NetBackup catalog tape may be corrupt." }, "129": { "code": 129, - "desc": "Disco armazenamento unidade está cheio", - "first_action": "Either liberar sufficient space ou add more space to o arquivo system para this armazenamento", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Either liberar sufficient space ou add more space to o arquivo system para this armazenamento\nunidade.\n■ Lower o high capacity mark para this disco armazenamento unidade. Configure o policies\nto access it through um armazenamento unidade group que provides alternative armazenamento to\nuse when this armazenamento unidade fills up. Ideally, if um image exceeds o arquivo system’s\nhighcapacitymark,italsocompletessuccessfully.Thisimageleavesthestorage\nunidade in um cheio state (over o high capacity mark). O armazenamento unidade then está não\nassigned to other jobs until its capacity falls under its high capacity mark.\n■ If o Staging attribute está set on o disco armazenamento unidade que did não have enough\ncapacity, it may be não foi possível to create liberar space. It não é possível create space because\no backups que estão staged to o disco estão não relocated (eligible to be deleted\nfromthestagingstorageunit).Ensurethatstaging’srelocation(duplication)jobs\nsuccessfully copy enough images to provide sufficient liberar space para new\nbackups." + "desc": "Disk storage unit is full", + "first_action": "Either free sufficient space or add more space to the file system for this storage", + "full_action": "Do the following, as appropriate:\n■ Either free sufficient space or add more space to the file system for this storage\nunit.\n■ Lower the high capacity mark for this disk storage unit. Configure the policies\nto access it through a storage unit group that provides alternative storage to\nuse when this storage unit fills up. Ideally, if an image exceeds the file system’s\nhighcapacitymark,italsocompletessuccessfully.Thisimageleavesthestorage\nunit in a full state (over the high capacity mark). The storage unit then is not\nassigned to other jobs until its capacity falls under its high capacity mark.\n■ If the Staging attribute is set on the disk storage unit that did not have enough\ncapacity, it may be unable to create free space. It cannot create space because\nthe backups that are staged to the disk are not relocated (eligible to be deleted\nfromthestagingstorageunit).Ensurethatstaging’srelocation(duplication)jobs\nsuccessfully copy enough images to provide sufficient free space for new\nbackups." }, "130": { "code": 130, - "desc": "System erro ocorreu", + "desc": "System error occurred", "first_action": "ChecktheNetBackupProblemsreportforadditionalinformationabouttheerror.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ ChecktheNetBackupProblemsreportforadditionalinformationabouttheerror.\n■ Verifique o system log para reported problemas.\n■ Para detailed troubleshooting informação, create bpdbm, bptm, e bprd debug\nlog directories on o master servidor. Aumentar o unified logging level por usando\no vxlogcfg comando.\nVeja \"About unified logging\" in o NetBackup Logging Reference Guide.\n■ Retry o operation e verifique o resulting debug logs.\nIf o policy validation fails, it está due to one de seguinte reasons:\n■ Um certificate mismatch está present on o cliente. Remove o Snapshot Manager\nCA certificate from o seguinte location e validate o policy again:\ninstall_location/var/global/cloudpoint/certificates\n■ O Snapshot Manager está não accessible.\n■ If o NetBackup APIs produce this erro, examine o unified logs para\nnbwebservice on o master servidor. Para details on o web services logs, veja\no section on o NetBackup Web Services logging within o NetBackup\nLogging Reference Guide.\nWhen um VMware agentless restauração está performed, o restauração can cause one de o\nseguinte issues:\n■ Falhou to stage recovery tool on caminho %s in destination VM %s com erro code\n%d.\nMake sure que o staging location caminho que está used exists e o provided\ntarget VM credentials have raiz ou admin privileges.\n■ Falhou to get o staging location para destination VM %s com erro %d.\nMake sure que there está TMP ou TEMP environment caminho disponível in o target\nVM ou provided target VM credentials has raiz ou admin privileges.\n■ FailedtoretrievetheguestVM%soperatingsystem(OS)detailswitherrorcode\n%d.\nMake sure que latest VMware Tools estão instalado e executando in o target VM." + "full_action": "Do the following, as appropriate:\n■ ChecktheNetBackupProblemsreportforadditionalinformationabouttheerror.\n■ Check the system log for reported problems.\n■ For detailed troubleshooting information, create bpdbm, bptm, and bprd debug\nlog directories on the master server. Increase the unified logging level by using\nthe vxlogcfg command.\nSee \"About unified logging\" in the NetBackup Logging Reference Guide.\n■ Retry the operation and check the resulting debug logs.\nIf the policy validation fails, it is due to one of following reasons:\n■ A certificate mismatch is present on the client. Remove the Snapshot Manager\nCA certificate from the following location and validate the policy again:\ninstall_location/var/global/cloudpoint/certificates\n■ The Snapshot Manager is not accessible.\n■ If the NetBackup APIs produce this error, examine the unified logs for\nnbwebservice on the master server. For details on the web services logs, see\nthe section on the NetBackup Web Services logging within the NetBackup\nLogging Reference Guide.\nWhen a VMware agentless restore is performed, the restore can cause one of the\nfollowing issues:\n■ Failed to stage recovery tool on path %s in destination VM %s with error code\n%d.\nMake sure that the staging location path that is used exists and the provided\ntarget VM credentials have root or admin privileges.\n■ Failed to get the staging location for destination VM %s with error %d.\nMake sure that there is TMP or TEMP environment path available in the target\nVM or provided target VM credentials has root or admin privileges.\n■ FailedtoretrievetheguestVM%soperatingsystem(OS)detailswitherrorcode\n%d.\nMake sure that latest VMware Tools are installed and running in the target VM." }, "131": { "code": 131, - "desc": "Cliente está não validated to use o servidor", - "first_action": "Examine o NetBackup Problemas relatório.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Examine o NetBackup Problemas relatório.\n■ Createadebuglogdirectoryforbprdandretrytheoperation.Checktheresulting\ndebug log to determinar o conexão e o cliente names.\nDepending on o request type (restauração, backup, e so on), you may need ou\ndesejar to do o seguinte:\n■ Change o client’s configurado name.\n■ Modify o routing tables on o cliente.\n■ On o master servidor, set up um altnames diretório e arquivo para this cliente.\nVeja o NetBackup Administrator’s Guide, Volume I.\nOu\n■ On um UNIX master servidor, create um soft link in o NetBackup image catalog.\n■ SeeVerifyinghostnamesandservicesentriesintheNetBackupTroubleshooting\nGuide." + "desc": "Client is not validated to use the server", + "first_action": "Examine the NetBackup Problems report.", + "full_action": "Do the following, as appropriate:\n■ Examine the NetBackup Problems report.\n■ Createadebuglogdirectoryforbprdandretrytheoperation.Checktheresulting\ndebug log to determine the connection and the client names.\nDepending on the request type (restore, backup, and so on), you may need or\nwant to do the following:\n■ Change the client’s configured name.\n■ Modify the routing tables on the client.\n■ On the master server, set up an altnames directory and file for this client.\nSee the NetBackup Administrator’s Guide, Volume I.\nOr\n■ On a UNIX master server, create a soft link in the NetBackup image catalog.\n■ SeeVerifyinghostnamesandservicesentriesintheNetBackupTroubleshooting\nGuide." }, "132": { "code": 132, - "desc": "Usuário está não validated to use o servidor from this cliente", - "first_action": "Nenhum", - "full_action": "Nenhum" + "desc": "User is not validated to use the server from this client", + "first_action": "None", + "full_action": "None" }, "133": { "code": 133, - "desc": "Inválido request", - "first_action": "If you suspect que o software versions estão o problema, verifique que todos", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ If you suspect que o software versions estão o problema, verifique que todos\nNetBackup software está at o same version level.\n■ On UNIX NetBackup servers e clients, verifique o\n/usr/openv/netbackup/bin/version arquivo.\n■ On Windows NetBackup servers, verifique o\ninstall_path\\NetBackup\\version.txtfileortheAboutNetBackupitem\non o Help menu.\n■ On Microsoft Windows clients, verifique o About NetBackup item on o\nHelp menu.\n■ If o servidor denies list e restauração requests, do one de o seguinte:\n■ Go to o NetBackup Administration Console. In o left pane, expand\nNetBackupManagement>HostProperties>MasterServers.Intheright\npane, double-click o master servidor you desejar to modify. In o properties\ndialog box, in o left pane, select Cliente Attributesto access o Allow\ncliente browse e Allow cliente restauração options.\n■ Remove o DISALLOW_CLIENT_LIST_RESTORE e\nDISALLOW_CLIENT_RESTORE options from o bp.conf arquivo on um UNIX\nNetBackup servidor ou from o registry on um Windows NetBackup servidor.\nThen,stopandrestarttheNetBackupRequestDaemon(UNIX)orNetBackup\nRequest Manager service (Windows).\n■ Para detailed troubleshooting informação, create bpdbm, bprd, e admin debug\nlog directories. Retry o operation e verifique o resulting debug logs." + "desc": "Invalid request", + "first_action": "If you suspect that the software versions are the problem, verify that all", + "full_action": "Do the following, as appropriate:\n■ If you suspect that the software versions are the problem, verify that all\nNetBackup software is at the same version level.\n■ On UNIX NetBackup servers and clients, check the\n/usr/openv/netbackup/bin/version file.\n■ On Windows NetBackup servers, check the\ninstall_path\\NetBackup\\version.txtfileortheAboutNetBackupitem\non the Help menu.\n■ On Microsoft Windows clients, check the About NetBackup item on the\nHelp menu.\n■ If the server denies list and restore requests, do one of the following:\n■ Go to the NetBackup Administration Console. In the left pane, expand\nNetBackupManagement>HostProperties>MasterServers.Intheright\npane, double-click the master server you want to modify. In the properties\ndialog box, in the left pane, select Client Attributesto access the Allow\nclient browse and Allow client restore options.\n■ Remove the DISALLOW_CLIENT_LIST_RESTORE and\nDISALLOW_CLIENT_RESTORE options from the bp.conf file on a UNIX\nNetBackup server or from the registry on a Windows NetBackup server.\nThen,stopandrestarttheNetBackupRequestDaemon(UNIX)orNetBackup\nRequest Manager service (Windows).\n■ For detailed troubleshooting information, create bpdbm, bprd, and admin debug\nlog directories. Retry the operation and check the resulting debug logs." }, "134": { "code": 134, - "desc": "Não foi possível to process request because o servidor resources estão ocupado", - "first_action": "Nenhum", - "full_action": "Nenhum\nO 134 code está um informational message apenas e está não considered um erro. It\ncan occur para um number de reasons in normal operation. O 134 status code can\noccur more frequently in um SSO environment. Não ação está necessary.\nAstatus134isnotloggedintheerrorlogs.A134statuscausesanewtrytoappear\nin o Activity Monitor. It does não aumentar o retry count que está associated com\no allowed number de retries." + "desc": "Unable to process request because the server resources are busy", + "first_action": "None", + "full_action": "None\nThe 134 code is an informational message only and is not considered an error. It\ncan occur for a number of reasons in normal operation. The 134 status code can\noccur more frequently in an SSO environment. No action is necessary.\nAstatus134isnotloggedintheerrorlogs.A134statuscausesanewtrytoappear\nin the Activity Monitor. It does not increase the retry count that is associated with\nthe allowed number of retries." }, "135": { "code": 135, - "desc": "Cliente está não validated to executar o solicitado operation", - "first_action": "Retry o operation como um raiz usuário (on UNIX) ou como um", - "full_action": "Retry o operation como um raiz usuário (on UNIX) ou como um\nadministrator (on Windows) on o master servidor. Also veja status code 131." + "desc": "Client is not validated to perform the requested operation", + "first_action": "Retry the operation as a root user (on UNIX) or as an", + "full_action": "Retry the operation as a root user (on UNIX) or as an\nadministrator (on Windows) on the master server. Also see status code 131." }, "136": { "code": 136, - "desc": "Tir info foi pruned from o image arquivo", - "first_action": "Reimport o TIR informação into o catalog de each", - "full_action": "Reimport o TIR informação into o catalog de each\ncomponent image (from which o TIR informação foi pruned). Then rerun o\nsynthetic backup job. O TIR informação can be imported into o image catalog\nbyinitiatingatrueimagerestoreofanyfilefromthatcomponentimage.Therestore\nprocess also restores o TIR informação in o image catalog." + "desc": "Tir info was pruned from the image file", + "first_action": "Reimport the TIR information into the catalog of each", + "full_action": "Reimport the TIR information into the catalog of each\ncomponent image (from which the TIR information was pruned). Then rerun the\nsynthetic backup job. The TIR information can be imported into the image catalog\nbyinitiatingatrueimagerestoreofanyfilefromthatcomponentimage.Therestore\nprocess also restores the TIR information in the image catalog." }, "140": { "code": 140, - "desc": "Usuário ID foi não superuser", - "first_action": "If appropriate, give o usuário ou o process administrator", - "full_action": "If appropriate, give o usuário ou o process administrator\nprivileges (on Windows) ou raiz privileges (on UNIX) e retry o operation." + "desc": "User ID was not superuser", + "first_action": "If appropriate, give the user or the process administrator", + "full_action": "If appropriate, give the user or the process administrator\nprivileges (on Windows) or root privileges (on UNIX) and retry the operation." }, "141": { "code": 141, - "desc": "Arquivo caminho specified está não absolute", - "first_action": "Correct o arquivo specification e retry o comando.", - "full_action": "Correct o arquivo specification e retry o comando." + "desc": "File path specified is not absolute", + "first_action": "Correct the file specification and retry the command.", + "full_action": "Correct the file specification and retry the command." }, "142": { "code": 142, - "desc": "Arquivo does não exist", + "desc": "File does not exist", "first_action": "InstalltheVxFSdynamiclibrariesontheNetBackupclient", - "full_action": "InstalltheVxFSdynamiclibrariesontheNetBackupclient\ne try o backup again." + "full_action": "InstalltheVxFSdynamiclibrariesontheNetBackupclient\nand try the backup again." }, "143": { "code": 143, - "desc": "Inválido comando protocol", + "desc": "Invalid command protocol", "first_action": "ExaminetheNetBackuperrorlogstodeterminethesystem", - "full_action": "ExaminetheNetBackuperrorlogstodeterminethesystem\nthatwasthesourceofthedata.Onthatsystem,determinetheprocessthatinitiated\no request. If it foi um NetBackup process, verifique que o process ou comando está\ncompatible com o version de software on o servidor." + "full_action": "ExaminetheNetBackuperrorlogstodeterminethesystem\nthatwasthesourceofthedata.Onthatsystem,determinetheprocessthatinitiated\nthe request. If it was a NetBackup process, verify that the process or command is\ncompatible with the version of software on the server." }, "144": { "code": 144, - "desc": "Uso de comando inválido", - "first_action": "Either correct o comando ou verifique que todos NetBackup", - "full_action": "Either correct o comando ou verifique que todos NetBackup\nbinaries estão at o same version level." + "desc": "Invalid command usage", + "first_action": "Either correct the command or verify that all NetBackup", + "full_action": "Either correct the command or verify that all NetBackup\nbinaries are at the same version level." }, "145": { "code": 145, - "desc": "Daemon está already executando", + "desc": "Daemon is already running", "first_action": "Terminatethecurrentcopyoftheprocessandthenrestart", - "full_action": "Terminatethecurrentcopyoftheprocessandthenrestart\no process." + "full_action": "Terminatethecurrentcopyoftheprocessandthenrestart\nthe process." }, "146": { "code": 146, - "desc": "Não é possível get um bound socket", - "first_action": "Examine o NetBackup Problemas e Todos Log Entradas relatórios.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Examine o NetBackup Problemas e Todos Log Entradas relatórios.\n■ Create bprd e bpdbm debug log directories e retry o operation. Verifique\ntheresultinglogstoseethesystemerrormessagethatresultedfromtheattempt.\nIf another process has o port, use other system commands to determinar o\nprocess.Basedonthisresearch,eitherchangetheportnumberinyourservices\narquivo ou map ou terminate o process que acquired o port.\nOn UNIX, another possible cause para this erro está o use de o kill comando\nto terminate bprd ou bpdbm. To stop bpdbm, use o\n/usr/openv/netbackup/bin/bpdbm -terminate comando. Use de o kill\ncomando to stop these processos can leave them não foi possível to bind to their\nassigned ports o next time they estão started.\nTo identify um bprd ou um bpdbm problema, look para lines similar to o seguinte in\no debug log para o respective process:\n<16> getsockbound: bind() falhou, Address already in use (114)\n<32> listen_loop: não é possível get bound socket. errno = 114\n<4> terminate: termination begun...error code = 146\nSimilar entradas can appear in o relatórios.\n■ If o problema persists longer than 10 minutes, it may be necessary to restart\no servidor." + "desc": "Cannot get a bound socket", + "first_action": "Examine the NetBackup Problems and All Log Entries reports.", + "full_action": "Do the following, as appropriate:\n■ Examine the NetBackup Problems and All Log Entries reports.\n■ Create bprd and bpdbm debug log directories and retry the operation. Check\ntheresultinglogstoseethesystemerrormessagethatresultedfromtheattempt.\nIf another process has the port, use other system commands to determine the\nprocess.Basedonthisresearch,eitherchangetheportnumberinyourservices\nfile or map or terminate the process that acquired the port.\nOn UNIX, another possible cause for this error is the use of the kill command\nto terminate bprd or bpdbm. To stop bpdbm, use the\n/usr/openv/netbackup/bin/bpdbm -terminate command. Use of the kill\ncommand to stop these processes can leave them unable to bind to their\nassigned ports the next time they are started.\nTo identify a bprd or a bpdbm problem, look for lines similar to the following in\nthe debug log for the respective process:\n<16> getsockbound: bind() failed, Address already in use (114)\n<32> listen_loop: cannot get bound socket. errno = 114\n<4> terminate: termination begun...error code = 146\nSimilar entries can appear in the reports.\n■ If the problem persists longer than 10 minutes, it may be necessary to restart\nthe server." }, "147": { "code": 147, - "desc": "Requerido ou specified copy foi não found", - "first_action": "Correct o request to specify um copy number que does", - "full_action": "Correct o request to specify um copy number que does\nexist." + "desc": "Required or specified copy was not found", + "first_action": "Correct the request to specify a copy number that does", + "full_action": "Correct the request to specify a copy number that does\nexist." }, "148": { "code": 148, - "desc": "Daemon fork falhou", - "first_action": "Restart o service at um later time e investigate o system problemas que limite", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Restart o service at um later time e investigate o system problemas que limite\no number de processos.\n■ On Windows systems, verifique o Event Viewer Application e System logs." + "desc": "Daemon fork failed", + "first_action": "Restart the service at a later time and investigate the system problems that limit", + "full_action": "Do the following, as appropriate:\n■ Restart the service at a later time and investigate the system problems that limit\nthe number of processes.\n■ On Windows systems, check the Event Viewer Application and System logs." }, "149": { "code": 149, - "desc": "Master servidor request falhou", - "first_action": "Nenhum", - "full_action": "Nenhum" + "desc": "Master server request failed", + "first_action": "None", + "full_action": "None" }, "150": { "code": 150, - "desc": "Termination solicitado por administrator", - "first_action": "Nenhum", - "full_action": "Nenhum" + "desc": "Termination requested by administrator", + "first_action": "None", + "full_action": "None" }, "152": { "code": 152, - "desc": "Requerido value não set", - "first_action": "Verifique que todos software está at o same version level.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Verifique que todos software está at o same version level.\n■ Para detailed troubleshooting informação, create bpdbm e admin debug log\ndirectories e retry o operation. Verifique o resulting debug logs." + "desc": "Required value not set", + "first_action": "Verify that all software is at the same version level.", + "full_action": "Do the following, as appropriate:\n■ Verify that all software is at the same version level.\n■ For detailed troubleshooting information, create bpdbm and admin debug log\ndirectories and retry the operation. Check the resulting debug logs." }, "153": { "code": 153, - "desc": "Servidor está não o master servidor", - "first_action": "Nenhum", - "full_action": "Nenhum" + "desc": "Server is not the master server", + "first_action": "None", + "full_action": "None" }, "154": { "code": 154, - "desc": "Armazenamento unidade characteristics mismatched to request", - "first_action": "Para um NetBackup Snapshot Cliente, o policy armazenamento unidade foi set to", - "full_action": "Verifique que o characteristics de o selected armazenamento unidade\nestão appropriate para o attempted backup.\n■ Para um NetBackup Snapshot Cliente, o policy armazenamento unidade foi set to\nAny_available e o off-host backup method foi set to Third-Party Copy\nDeviceorNetBackupMediaServer.DonotchooseAny_available.Aparticular\narmazenamento unidade must be specified when Third-Party Copy Dispositivo ou NetBackup\nMídia Servidor está specified como o off-host backup method.\n■ Para um NDMP policy type, verifique o seguinte:\n■ You have defined um armazenamento unidade de type NDMP.\n■ O NDMP host value matches o host name de o cliente. Para example, if\no NDMP policy specifies toaster como o cliente, o configuration para o\narmazenamento unidade must specify toaster como o NDMP host.\n■ O mídia servidor para o armazenamento unidade está executando o correct version de\nNetBackup.\n■ Para um policy type other than NDMP, verifique que o policy specifies um mídia\nmanager ou disco type armazenamento unidade." + "desc": "Storage unit characteristics mismatched to request", + "first_action": "For a NetBackup Snapshot Client, the policy storage unit was set to", + "full_action": "Verify that the characteristics of the selected storage unit\nare appropriate for the attempted backup.\n■ For a NetBackup Snapshot Client, the policy storage unit was set to\nAny_available and the off-host backup method was set to Third-Party Copy\nDeviceorNetBackupMediaServer.DonotchooseAny_available.Aparticular\nstorage unit must be specified when Third-Party Copy Device or NetBackup\nMedia Server is specified as the off-host backup method.\n■ For an NDMP policy type, verify the following:\n■ You have defined a storage unit of type NDMP.\n■ The NDMP host value matches the host name of the client. For example, if\nthe NDMP policy specifies toaster as the client, the configuration for the\nstorage unit must specify toaster as the NDMP host.\n■ The media server for the storage unit is running the correct version of\nNetBackup.\n■ For a policy type other than NDMP, verify that the policy specifies a media\nmanager or disk type storage unit." }, "155": { "code": 155, - "desc": "O disco está cheio", - "first_action": "Liberar up space on o disks onde NetBackup catalogs", - "full_action": "Liberar up space on o disks onde NetBackup catalogs\nresidir ou onde o track log folder resides e retry o operation." + "desc": "Disk is full", + "first_action": "Free up space on the disks where NetBackup catalogs", + "full_action": "Free up space on the disks where NetBackup catalogs\nreside or where the track log folder resides and retry the operation." }, "156": { "code": 156, - "desc": "Erro de snapshot encontrado", - "first_action": "Garanta que o appropriate plug-in está configurado in o web UI com o", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Garanta que o appropriate plug-in está configurado in o web UI com o\nappropriate credentials. If o credentials estão changed, garanta que they estão\nupdated from o web UI.\n■ Garanta que o snapshot limite de o cloud provider está sufficient.\n■ Verifique o ncfnbcs logs.\n■ Select um different armazenamento option para Oracle Copilot backup com instant access.\nFormoreinformation,reviewtheOracleCopilotwithinstantaccessanduniversal\nshare chapter in o NetBackup para Oracle Administrator’s Guide.\n■ Thesnapshotissuccessfulwhentheassetisdiscoveredinnextdiscoverycycle.\nOu, o usuário can manually initiate um discovery when um new asset está added.\n■ Restart o shadow copy service.\n■ Right click on o C drive e then select Configure Shadow Copies….\n■ Select C drive e click Settings.\n■ Click schedule e then OK.\n■ Select another drive e repeat o steps. If there estão não other drives then\nclick OK.\n■ Refer to Configuring VSS to store shadow copies on o originating drive in\no NetBackup Snapshot Manager Install e Upgrade Guide.\n■ Unsubscribe o protection plan from o asset.\n■ To discover o asset, start um manual discovery ou it would be discovered in o\nnext autodiscovery.\n■ If o Snapshot fails com o erro asset hierarchy está incomplete, refer to\no seguinte technical article:\n■ CloudPoint snapshot está failing com \"o host level snapshot de não é possível be\nperformed como asset hierarchy está incomplete\" due to ebsnvme-id returning\n/dev/sda when it should just return sda para o boot disco.\n■ Veja “" + "desc": "Snapshot error encountered", + "first_action": "Ensure that the appropriate plug-in is configured in the web UI with the", + "full_action": "Perform the following, as appropriate:\n■ Ensure that the appropriate plug-in is configured in the web UI with the\nappropriate credentials. If the credentials are changed, ensure that they are\nupdated from the web UI.\n■ Ensure that the snapshot limit of the cloud provider is sufficient.\n■ Check the ncfnbcs logs.\n■ Select a different storage option for Oracle Copilot backup with instant access.\nFormoreinformation,reviewtheOracleCopilotwithinstantaccessanduniversal\nshare chapter in the NetBackup for Oracle Administrator’s Guide.\n■ Thesnapshotissuccessfulwhentheassetisdiscoveredinnextdiscoverycycle.\nOr, the user can manually initiate a discovery when a new asset is added.\n■ Restart the shadow copy service.\n■ Right click on the C drive and then select Configure Shadow Copies….\n■ Select C drive and click Settings.\n■ Click schedule and then OK.\n■ Select another drive and repeat the steps. If there are no other drives then\nclick OK.\n■ Refer to Configuring VSS to store shadow copies on the originating drive in\nthe NetBackup Snapshot Manager Install and Upgrade Guide.\n■ Unsubscribe the protection plan from the asset.\n■ To discover the asset, start a manual discovery or it would be discovered in the\nnext autodiscovery.\n■ If the Snapshot fails with the error asset hierarchy is incomplete, refer to\nthe following technical article:\n■ CloudPoint snapshot is failing with \"The host level snapshot of cannot be\nperformed as asset hierarchy is incomplete\" due to ebsnvme-id returning\n/dev/sda when it should just return sda for the boot disk.\n■ See “" }, "157": { "code": 157, - "desc": "Suspend solicitado por administrator", - "first_action": "O administrator can resume o job from o last", - "full_action": "O administrator can resume o job from o last\ncheckpoint from o Activity Monitor." + "desc": "Suspend requested by administrator", + "first_action": "The administrator can resume the job from the last", + "full_action": "The administrator can resume the job from the last\ncheckpoint from the Activity Monitor." }, "158": { "code": 158, - "desc": "Falhou accessing daemon lock arquivo", - "first_action": "Examine o NetBackup erro log to determinar por que o system call falhou. Then", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Examine o NetBackup erro log to determinar por que o system call falhou. Then\ncorrect o problema. It may be um permissão problema.\n■ If o erro log does não show o erro, create um debug log diretório para bprd\nou bpdbm (depending on which process encontrado o erro). Aumentar o\nunified logging level if nbpem, nbjm, ou nbrb encontrado o erro. Use o\nvxlogcfg comando como explained in o seguinte topic:\nVeja \"About unified logging\" in o NetBackup Logging Reference Guide.\nRetry o operation e verifique o resulting debug log." + "desc": "Failed accessing daemon lock file", + "first_action": "Examine the NetBackup error log to determine why the system call failed. Then", + "full_action": "Do the following, as appropriate:\n■ Examine the NetBackup error log to determine why the system call failed. Then\ncorrect the problem. It may be a permission problem.\n■ If the error log does not show the error, create a debug log directory for bprd\nor bpdbm (depending on which process encountered the error). Increase the\nunified logging level if nbpem, nbjm, or nbrb encountered the error. Use the\nvxlogcfg command as explained in the following topic:\nSee \"About unified logging\" in the NetBackup Logging Reference Guide.\nRetry the operation and check the resulting debug log." }, "159": { "code": 159, - "desc": "Licensed use has been excedido", - "first_action": "To determinar o cause de o erro, examine o", - "full_action": "To determinar o cause de o erro, examine o\nNetBackupAllLogEntriesreportforthecommandthatwasrun.SeealsotheActivity\nMonitor details para informative messages.\nIf o job fails on um SAN mídia servidor armazenamento unidade, garanta que apenas o local cliente\nestá specified in o policy. If remote clients estão specified in o policy, do one de o\nseguinte: remove them e place them in um policy que specifies um different armazenamento\nunidade ou change o armazenamento unidade para que policy.\nIf you desejar to back up remote clients por usando o SAN mídia servidor, you can\npurchase um regular NetBackup mídia servidor license." + "desc": "Licensed use has been exceeded", + "first_action": "To determine the cause of the error, examine the", + "full_action": "To determine the cause of the error, examine the\nNetBackupAllLogEntriesreportforthecommandthatwasrun.SeealsotheActivity\nMonitor details for informative messages.\nIf the job fails on a SAN media server storage unit, ensure that only the local client\nis specified in the policy. If remote clients are specified in the policy, do one of the\nfollowing: remove them and place them in a policy that specifies a different storage\nunit or change the storage unit for that policy.\nIf you want to back up remote clients by using the SAN media server, you can\npurchase a regular NetBackup media server license." }, "160": { "code": 160, - "desc": "Authentication falhou", - "first_action": "Add back o names que foram removed e retry o operation.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Add back o names que foram removed e retry o operation.\n■ Create o seguinte debug log directories para o processos que estão involved\nin authentication between NetBackup systems:\n■ Servidor: bprd, bpdbm, e bpcd.\n■ Cliente: bpbackup, bprestore, e bpbkar.\nRetry o operation e review o debug logs.\nO seguinte actions relate to Snapshot Manager:\n■ Garanta que o Snapshot Manager credentials estão correct.\n■ Verifique que o credentials que foram entered while registering estão valid.\n■ If o credentials e o Snapshot Manager port number estão updated, garanta\nque they estão updated in NetBackup.\n■ Garanta que o Snapshot Manager credentials estão correct.\n■ VerifythatthecredentialsthatwereenteredwhileregisteringSnapshotManager\nestão valid.\n■ Verifythatthecredentialsthatwereenteredwhileconfiguringastorageprovider\nestão valid.\n■ If o credentials e o Snapshot Manager port number estão updated, garanta\nque they estão updated in NetBackup." + "desc": "Authentication failed", + "first_action": "Add back the names that were removed and retry the operation.", + "full_action": "Do the following, as appropriate:\n■ Add back the names that were removed and retry the operation.\n■ Create the following debug log directories for the processes that are involved\nin authentication between NetBackup systems:\n■ Server: bprd, bpdbm, and bpcd.\n■ Client: bpbackup, bprestore, and bpbkar.\nRetry the operation and review the debug logs.\nThe following actions relate to Snapshot Manager:\n■ Ensure that the Snapshot Manager credentials are correct.\n■ Verify that the credentials that were entered while registering are valid.\n■ If the credentials and the Snapshot Manager port number are updated, ensure\nthat they are updated in NetBackup.\n■ Ensure that the Snapshot Manager credentials are correct.\n■ VerifythatthecredentialsthatwereenteredwhileregisteringSnapshotManager\nare valid.\n■ Verifythatthecredentialsthatwereenteredwhileconfiguringastorageprovider\nare valid.\n■ If the credentials and the Snapshot Manager port number are updated, ensure\nthat they are updated in NetBackup." }, "161": { "code": 161, "desc": "Evaluation software has expired.", - "first_action": "Obtain um licensed copy de NetBackup. Para informação on", - "full_action": "Obtain um licensed copy de NetBackup. Para informação on\nlicensing, contate seu NetBackup sales ou partner representative." + "first_action": "Obtain a licensed copy of NetBackup. For information on", + "full_action": "Obtain a licensed copy of NetBackup. For information on\nlicensing, contact your NetBackup sales or partner representative." }, "162": { "code": 162, - "desc": "Incorrect servidor platform para license NetBackup status codes 197 NetBackup status codes", - "first_action": "Garanta que you use um license key que está intended para o", - "full_action": "Garanta que you use um license key que está intended para o\nplatform on which you plan to install." + "desc": "Incorrect server platform for license NetBackup status codes 197 NetBackup status codes", + "first_action": "Ensure that you use a license key that is intended for the", + "full_action": "Ensure that you use a license key that is intended for the\nplatform on which you plan to install." }, "163": { "code": 163, - "desc": "Mídia block size changed prior resume", - "first_action": "Verifique o Activity Monitor job details para o job ID de o", - "full_action": "Verifique o Activity Monitor job details para o job ID de o\nrestarted job." + "desc": "Media block size changed prior resume", + "first_action": "Check the Activity Monitor job details for the job ID of the", + "full_action": "Check the Activity Monitor job details for the job ID of the\nrestarted job." }, "164": { "code": 164, - "desc": "Não foi possível to mount mídia because it está in um DOWN, ou otherwise não disponível", - "first_action": "If volume está in um DOWN drive, remove it e place it in its designated slot. Then,", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ If volume está in um DOWN drive, remove it e place it in its designated slot. Then,\nretry o restauração.\n■ If o volume está in o wrong slot, use um robot inventory option to reconcile o\ncontents de o robot com o volume configuration." + "desc": "Unable to mount media because it is in a DOWN, or otherwise not available", + "first_action": "If volume is in a DOWN drive, remove it and place it in its designated slot. Then,", + "full_action": "Do the following, as appropriate:\n■ If volume is in a DOWN drive, remove it and place it in its designated slot. Then,\nretry the restore.\n■ If the volume is in the wrong slot, use a robot inventory option to reconcile the\ncontents of the robot with the volume configuration." }, "165": { "code": 165, - "desc": "NB image banco de dados contains não image fragments para solicitado backup id/copy number NetBackup status codes 198 NetBackup status codes", - "first_action": "Verifique o NetBackup Problemas relatório para additional", - "full_action": "Verifique o NetBackup Problemas relatório para additional\ninformationabouttheerror.Fordetailedtroubleshootinginformation,createadebug\nlog diretório para either bpdm ou bptm (whichever aplica-se) e retry o operation.\nVerifique o resulting debug log." + "desc": "NB image database contains no image fragments for requested backup id/copy number NetBackup status codes 198 NetBackup status codes", + "first_action": "Check the NetBackup Problems report for additional", + "full_action": "Check the NetBackup Problems report for additional\ninformationabouttheerror.Fordetailedtroubleshootinginformation,createadebug\nlog directory for either bpdm or bptm (whichever applies) and retry the operation.\nCheck the resulting debug log." }, "166": { "code": 166, - "desc": "Backups estão não allowed to span mídia", - "first_action": "Nenhum", - "full_action": "Nenhum" + "desc": "Backups are not allowed to span media", + "first_action": "None", + "full_action": "None" }, "167": { "code": 167, - "desc": "Não é possível find solicitado volume pool in EMM banco de dados", - "first_action": "Verifique o Mídia e Dispositivo Management volume", - "full_action": "Verifique o Mídia e Dispositivo Management volume\nconfiguration. Verifique o NetBackup Problemas relatório para more informação about\ntheerror.Fordetailedtroubleshootinginformation,createabptmdebuglogdirectory\ne retry o operation. Verifique o resulting debug log." + "desc": "Cannot find requested volume pool in EMM database", + "first_action": "Verify the Media and Device Management volume", + "full_action": "Verify the Media and Device Management volume\nconfiguration. Check the NetBackup Problems report for more information about\ntheerror.Fordetailedtroubleshootinginformation,createabptmdebuglogdirectory\nand retry the operation. Check the resulting debug log." }, "168": { "code": 168, - "desc": "Não é possível overwrite mídia, data on it está protected NetBackup status codes 199 NetBackup status codes", - "first_action": "Replace o volume com um new one ou set o NetBackup", - "full_action": "Replace o volume com um new one ou set o NetBackup\nALLOW_MEDIA_OVERWRITE option to o appropriate value." + "desc": "Cannot overwrite media, data on it is protected NetBackup status codes 199 NetBackup status codes", + "first_action": "Replace the volume with a new one or set the NetBackup", + "full_action": "Replace the volume with a new one or set the NetBackup\nALLOW_MEDIA_OVERWRITE option to the appropriate value." }, "169": { "code": 169, - "desc": "Mídia ID está either expired ou will exceed maximum mounts", - "first_action": "If o volume foi suspended, wait until it expires e", - "full_action": "If o volume foi suspended, wait until it expires e\nthen replace it. Para NetBackup catalog backups, replace o mídia." + "desc": "Media ID is either expired or will exceed maximum mounts", + "first_action": "If the volume was suspended, wait until it expires and", + "full_action": "If the volume was suspended, wait until it expires and\nthen replace it. For NetBackup catalog backups, replace the media." }, "170": { "code": 170, - "desc": "Third party copy backup falha", - "first_action": "If um non third-party copy dispositivo está listed in 3pc.conf arquivo, correct it ou remove", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ If um non third-party copy dispositivo está listed in 3pc.conf arquivo, correct it ou remove\no non third-party copy dispositivo entry.\n■ If um incorrect LUN está specified in o 3pc.conf arquivo ou o dispositivo does não exist,\ncorrect o 3pc.conf arquivo como appropriate.\n■ If um appropriate mover.conf arquivo (com ou without arquivo name extension) não é possível\nbe found, o /usr/openv/netbackup/logs/bptm log may show o seguinte:\n09:51:04 [22281] <2> setup_mover_tpc: não\nmover.conf.vertex_std_tpc ou mover.conf arquivo exists, não é possível\nexecutar TPC backup\n09:51:04 [22281] <16> bptm: não foi possível to find ou communicate com\nThird-Party-Copy mover para policy vertex_std_tpc\nMakesurethatanappropriatemover.conf fileexistsin/usr/openv/netbackup\non o mídia servidor. This arquivo can be qualquer de o seguinte:\n■ mover.conf.policy_name arquivo, onde policy_name exactly matches o\nname de o policy.\n■ mover.conf.storage_unit_name,wherestorage_unit_nameexactlymatches\no name de o armazenamento in o Backup Policy Management Policy\nattributes dialog box.\n■ mover.conf arquivo (não extension) para o configurations que have apenas one\nthird-party copy dispositivo.\nNote que NetBackup looks para um appropriate mover.conf arquivo in o order.\n■ If o SCSI pass-through caminho de o third-party copy dispositivo, como entered in o\nmover.conf arquivo, does não exist, o bptm log may show o seguinte:\n09:50:12 [22159] <16> setup_mover_tpc: abrir de passthru caminho\n/dev/sg/cXtXlX falhou, Não such arquivo ou diretório\n09:50:12 [22159] <16> bptm: não foi possível to find ou communicate com\nThird-Party-Copy mover para policy vertex_std_tpc\nCorrecttheSCSIpass-throughpathofthethird-partycopydevicethatisentered\nin o mover.conf arquivo.\n■ If o third-party copy dispositivo returned um erro, you may veja either de o\nseguinte messages in /usr/openv/netbackup/logs/bptm log:\nnão é possível process extended copy erro due to truncated sense data,\nmay be HBA problema\ndisco erro ocorreu on extended copy comando, key = 0x0, asc =\n0x0, ascq = 0x0\n(onde key, asc, e ascq estão todos zero)\nSeu host-bus adapter (HBA) e its driver may need to be updated, ou\nNetBackup Snapshot Cliente may não support them. O supported host-bus\nadapters estão listed.\nVeja o NetBackup Release Notes." + "desc": "Third party copy backup failure", + "first_action": "If a non third-party copy device is listed in 3pc.conf file, correct it or remove", + "full_action": "Do the following, as appropriate:\n■ If a non third-party copy device is listed in 3pc.conf file, correct it or remove\nthe non third-party copy device entry.\n■ If an incorrect LUN is specified in the 3pc.conf file or the device does not exist,\ncorrect the 3pc.conf file as appropriate.\n■ If an appropriate mover.conf file (with or without file name extension) cannot\nbe found, the /usr/openv/netbackup/logs/bptm log may show the following:\n09:51:04 [22281] <2> setup_mover_tpc: no\nmover.conf.vertex_std_tpc or mover.conf file exists, cannot\nperform TPC backup\n09:51:04 [22281] <16> bptm: unable to find or communicate with\nThird-Party-Copy mover for policy vertex_std_tpc\nMakesurethatanappropriatemover.conf fileexistsin/usr/openv/netbackup\non the media server. This file can be any of the following:\n■ mover.conf.policy_name file, where policy_name exactly matches the\nname of the policy.\n■ mover.conf.storage_unit_name,wherestorage_unit_nameexactlymatches\nthe name of the storage in the Backup Policy Management Policy\nattributes dialog box.\n■ mover.conf file (no extension) for the configurations that have only one\nthird-party copy device.\nNote that NetBackup looks for an appropriate mover.conf file in the order.\n■ If the SCSI pass-through path of the third-party copy device, as entered in the\nmover.conf file, does not exist, the bptm log may show the following:\n09:50:12 [22159] <16> setup_mover_tpc: open of passthru path\n/dev/sg/cXtXlX failed, No such file or directory\n09:50:12 [22159] <16> bptm: unable to find or communicate with\nThird-Party-Copy mover for policy vertex_std_tpc\nCorrecttheSCSIpass-throughpathofthethird-partycopydevicethatisentered\nin the mover.conf file.\n■ If the third-party copy device returned an error, you may see either of the\nfollowing messages in /usr/openv/netbackup/logs/bptm log:\ncannot process extended copy error due to truncated sense data,\nmay be HBA problem\ndisk error occurred on extended copy command, key = 0x0, asc =\n0x0, ascq = 0x0\n(where key, asc, and ascq are all zero)\nYour host-bus adapter (HBA) and its driver may need to be updated, or\nNetBackup Snapshot Client may not support them. The supported host-bus\nadapters are listed.\nSee the NetBackup Release Notes." }, "171": { "code": 171, - "desc": "Mídia ID must be 6 ou less characters", - "first_action": "Retry o comando com um valid mídia ID.", - "full_action": "Retry o comando com um valid mídia ID." + "desc": "Media ID must be 6 or less characters", + "first_action": "Retry the command with a valid media ID.", + "full_action": "Retry the command with a valid media ID." }, "172": { "code": 172, "desc": "Cannotreadmediaheader,maynotbeNetBackupmediaoriscorrupted", - "first_action": "If o volume está in um robot que supports bar codes, verifique o robot contents por", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ If o volume está in um robot que supports bar codes, verifique o robot contents por\nusando um robot inventory option.\n■ If o volume foi mounted on um nonrobotic drive, verifique que o correct volume\nfoi mounted e assigned.\n■ Verifique o NetBackup Problemas relatório. If it shows um fatal ler erro, try o\noperation again com another drive, if possible.\n■ If seu configuration has multiple servers ou HBAs com access to seu tape\nservices, make sure que o SCSI Reserve ou Release está onfigured correctly.\n(Most likely, o tape services configuration está um SSO configuration.)\nPara more informação on o armazenamento servidor, por favor veja o NetBackup\nAdministrator's Guide, Volume II." + "first_action": "If the volume is in a robot that supports bar codes, verify the robot contents by", + "full_action": "Do the following, as appropriate:\n■ If the volume is in a robot that supports bar codes, verify the robot contents by\nusing a robot inventory option.\n■ If the volume was mounted on a nonrobotic drive, verify that the correct volume\nwas mounted and assigned.\n■ Check the NetBackup Problems report. If it shows a fatal read error, try the\noperation again with another drive, if possible.\n■ If your configuration has multiple servers or HBAs with access to your tape\nservices, make sure that the SCSI Reserve or Release is onfigured correctly.\n(Most likely, the tape services configuration is an SSO configuration.)\nFor more information on the storage server, please see the NetBackup\nAdministrator's Guide, Volume II." }, "173": { "code": 173, - "desc": "Não é possível ler backup header, mídia may be corrupted", - "first_action": "Verifique o NetBackup Problemas relatório para pistas como to what caused o erro.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Verifique o NetBackup Problemas relatório para pistas como to what caused o erro.\n■ Try o restauração on another drive if possible.\n■ Para detailed troubleshooting informação, create um debug log diretório para bptm\ne retry o operation. Verifique o resulting debug log." + "desc": "Cannot read backup header, media may be corrupted", + "first_action": "Check the NetBackup Problems report for clues as to what caused the error.", + "full_action": "Do the following, as appropriate:\n■ Check the NetBackup Problems report for clues as to what caused the error.\n■ Try the restore on another drive if possible.\n■ For detailed troubleshooting information, create a debug log directory for bptm\nand retry the operation. Check the resulting debug log." }, "174": { "code": 174, - "desc": "Mídia manager - system erro ocorreu", - "first_action": "Verifique o NetBackup Problemas relatório to veja if it shows o cause de o", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Verifique o NetBackup Problemas relatório to veja if it shows o cause de o\nproblema. If you veja um Problemas relatório message similar to o seguinte, save\ntodos logs e contate Cohesity Technical Support:\nattempted to gravar 32767 bytes, não um multiple de 512\n■ On UNIX, if this erro occurs during um restauração, o tape drive may be incorrectly\nconfigurado. It may be configurado to gravar in fixed-length mode when it should\ngravar in variable length mode.\nVerifique seu drive’s configuration por comparing it to what está recomendada in o\nNetBackup Dispositivo Configuration Guide.\nIfyourconfigurationincorrectlyspecifiesfixed-lengthmode,changeittovariable\nlengthmodeandsuspendthemediathatwerewrittenonthatdevice.Theimages\nque foram written to those mídia may be restorable (platform dependent), but\nsingle arquivo restores estão likely to fail.\n■ If o problema occurs com um particular cliente apenas, verifique que o cliente binaries\nestão correct, especially para bpcd.\n■ If you can ler ou gravar qualquer other images on this mídia, verifique o seguinte\nrelatórios para pistas:\n■ Images on Mídia relatório\n■ Mídia Contents relatório\n■ Verifique o seguinte:\n■ O mídia, por usando o NetBackup image verifique option.\n■ Que you used o correct mídia type para o dispositivo.\n■ Verifique o system ou o console log para errors (on UNIX) ou o Event Viewer\nApplication log (on Windows).\n■ Para detailed debug informação, create um debug log diretório para either bptm ou\nbpdm (whichever aplica-se) e retry o operation. Verifique o resulting debug\nlog.\nOn UNIX, if o bptm debug log shows um erro similar to o seguinte, o tape\ndriveisconfiguredtowriteinfixed-lengthmoderatherthanvariablelengthmode.\n00:58:54 [2304] <16> write_data: gravar de 32768 bytes indicated\napenas 29696 bytes foram written, errno = 0\nO image being written encontrado o end-of-media.\n■ If o backup foi configurado para um OpenStorage disco armazenamento unidade, o\nOpenStorage vendor's plug-in may não be instalado on todos mídia servers in o\narmazenamento unit's mídia servidor list. Either install o vendor plug-in on todos de o\nmídia servers ou remove from o list o servers que do não have o plug-in\ninstalado.\n■ On UNIX, if this erro occurs during um restauração, refresh o Backup, Archive,\ne Restauração cliente console e retry o restauração. This ação refreshes o arquivo\nlist displayed in o cliente console e passes o correct informação about o\nselected arquivos." + "desc": "Media manager - system error occurred", + "first_action": "Check the NetBackup Problems report to see if it shows the cause of the", + "full_action": "Do the following, as appropriate:\n■ Check the NetBackup Problems report to see if it shows the cause of the\nproblem. If you see a Problems report message similar to the following, save\nall logs and contact Cohesity Technical Support:\nattempted to write 32767 bytes, not a multiple of 512\n■ On UNIX, if this error occurs during a restore, the tape drive may be incorrectly\nconfigured. It may be configured to write in fixed-length mode when it should\nwrite in variable length mode.\nVerify your drive’s configuration by comparing it to what is recommended in the\nNetBackup Device Configuration Guide.\nIfyourconfigurationincorrectlyspecifiesfixed-lengthmode,changeittovariable\nlengthmodeandsuspendthemediathatwerewrittenonthatdevice.Theimages\nthat were written to those media may be restorable (platform dependent), but\nsingle file restores are likely to fail.\n■ If the problem occurs with a particular client only, verify that the client binaries\nare correct, especially for bpcd.\n■ If you can read or write any other images on this media, check the following\nreports for clues:\n■ Images on Media report\n■ Media Contents report\n■ Verify the following:\n■ The media, by using the NetBackup image verify option.\n■ That you used the correct media type for the device.\n■ Check the system or the console log for errors (on UNIX) or the Event Viewer\nApplication log (on Windows).\n■ For detailed debug information, create a debug log directory for either bptm or\nbpdm (whichever applies) and retry the operation. Check the resulting debug\nlog.\nOn UNIX, if the bptm debug log shows an error similar to the following, the tape\ndriveisconfiguredtowriteinfixed-lengthmoderatherthanvariablelengthmode.\n00:58:54 [2304] <16> write_data: write of 32768 bytes indicated\nonly 29696 bytes were written, errno = 0\nThe image being written encountered the end-of-media.\n■ If the backup was configured for an OpenStorage disk storage unit, the\nOpenStorage vendor's plug-in may not be installed on all media servers in the\nstorage unit's media server list. Either install the vendor plug-in on all of the\nmedia servers or remove from the list the servers that do not have the plug-in\ninstalled.\n■ On UNIX, if this error occurs during a restore, refresh the Backup, Archive,\nand Restore client console and retry the restore. This action refreshes the file\nlist displayed in the client console and passes the correct information about the\nselected files." }, "175": { "code": 175, - "desc": "Não todos solicitado arquivos foram restored", - "first_action": "Verifique o NetBackup Problemas relatório e o status lot ou o progress log on", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Verifique o NetBackup Problemas relatório e o status lot ou o progress log on\no cliente para additional informação about o erro.\n■ Para detailed troubleshooting informação, create um debug log diretório para either\nbptm ou bpdm (whichever aplica-se) e retry o operation. Verifique o resulting\ndebug log." + "desc": "Not all requested files were restored", + "first_action": "Check the NetBackup Problems report and the status lot or the progress log on", + "full_action": "Do the following, as appropriate:\n■ Check the NetBackup Problems report and the status lot or the progress log on\nthe client for additional information about the error.\n■ For detailed troubleshooting information, create a debug log directory for either\nbptm or bpdm (whichever applies) and retry the operation. Check the resulting\ndebug log." }, "176": { "code": 176, - "desc": "Não é possível executar specified mídia import operation", - "first_action": "If o mídia ID está already active, duplicate todos images on o original mídia ID", - "full_action": "Verifique o NetBackup Problemas relatório to find o exact\ncause de o falha e try o seguinte:\n■ If o mídia ID está already active, duplicate todos images on o original mídia ID\ntoanothervolume.Then,manuallyexpiretheoriginalmediaandredotheimport.\n■ If o mídia ID está não present in o volume configuration, add it.\n■ If you received um fatal bptm erro, verifique que o seguinte estão active: o\nNetBackupVolumeManager(vmd)onUNIXortheNetBackupVolumeManager\non Windows.\n■ If o entire image está não present, executar import phase 1 on o mídia IDs que\nhave o remainder de o image.\n■ If o barcode e mídia ID estão um mismatch, use um barcode label que matches\ntherecordedmediaID.TapescanthenbemountedinadrivewithAVRDrunning\nso que o recorded mídia ID está displayed. Then, um barcode com que label\nneeds to be placed on o tape." + "desc": "Cannot perform specified media import operation", + "first_action": "If the media ID is already active, duplicate all images on the original media ID", + "full_action": "Check the NetBackup Problems report to find the exact\ncause of the failure and try the following:\n■ If the media ID is already active, duplicate all images on the original media ID\ntoanothervolume.Then,manuallyexpiretheoriginalmediaandredotheimport.\n■ If the media ID is not present in the volume configuration, add it.\n■ If you received a fatal bptm error, verify that the following are active: the\nNetBackupVolumeManager(vmd)onUNIXortheNetBackupVolumeManager\non Windows.\n■ If the entire image is not present, perform import phase 1 on the media IDs that\nhave the remainder of the image.\n■ If the barcode and media ID are a mismatch, use a barcode label that matches\ntherecordedmediaID.TapescanthenbemountedinadrivewithAVRDrunning\nso that the recorded media ID is displayed. Then, a barcode with that label\nneeds to be placed on the tape." }, "177": { "code": 177, - "desc": "Could não deassign mídia due to Mídia Manager erro", - "first_action": "Verifique o NetBackup Problemas relatório para o cause de o problema.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Verifique o NetBackup Problemas relatório para o cause de o problema.\n■ Verifique que o NetBackup Volume Manager (vmd) está active on UNIX ou o\nNetBackup Volume Manager service está active on Windows.\n■ Para detailed troubleshooting informação, create um debug log diretório para bptm\ne retry o operation. Verifique o resulting debug log." + "desc": "Could not deassign media due to Media Manager error", + "first_action": "Check the NetBackup Problems report for the cause of the problem.", + "full_action": "Do the following, as appropriate:\n■ Check the NetBackup Problems report for the cause of the problem.\n■ Verify that the NetBackup Volume Manager (vmd) is active on UNIX or the\nNetBackup Volume Manager service is active on Windows.\n■ For detailed troubleshooting information, create a debug log directory for bptm\nand retry the operation. Check the resulting debug log." }, "178": { "code": 178, - "desc": "Mídia ID está não in NetBackup volume pool", - "first_action": "Verifique o Mídia e Dispositivo Management volume", - "full_action": "Verifique o Mídia e Dispositivo Management volume\nconfiguration to verifique que o mídia IDs estão present e in o NetBackup volume\npool." + "desc": "Media ID is not in NetBackup volume pool", + "first_action": "Check the Media and Device Management volume", + "full_action": "Check the Media and Device Management volume\nconfiguration to verify that the media IDs are present and in the NetBackup volume\npool." }, "179": { "code": 179, - "desc": "Density está incorrect para o mídia ID", + "desc": "Density is incorrect for the media ID", "first_action": "CheckthevolumeconfigurationandtheNetBackupcatalog", - "full_action": "CheckthevolumeconfigurationandtheNetBackupcatalog\nbackup configuration e correct qualquer problemas found." + "full_action": "CheckthevolumeconfigurationandtheNetBackupcatalog\nbackup configuration and correct any problems found." }, "180": { "code": 180, - "desc": "Tar foi successful", - "first_action": "Nenhum", - "full_action": "Nenhum" + "desc": "Tar was successful", + "first_action": "None", + "full_action": "None" }, "181": { "code": 181, - "desc": "Tar received um inválido argument", - "first_action": "On um UNIX cliente:", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ On um UNIX cliente:\n■ Garanta que o nbtar comando in /usr/openv/netbackup/bin está o one\nprovided por NetBackup. If you estão in doubt, reinstall it.\n■ Verifique /usr/openv/netbackup/bin/version on o cliente to verifique que o\nclientisrunningthecorrectlevelsoftware.Ifthesoftwareisnotatthecorrect\nlevel,updatethesoftwareperthedirectionsintheNetBackupReleaseNotes.\n■ On um Windows cliente, create um tar debug log diretório, retry o operation, e\nverifique o log." + "desc": "Tar received an invalid argument", + "first_action": "On a UNIX client:", + "full_action": "Do the following, as appropriate:\n■ On a UNIX client:\n■ Ensure that the nbtar command in /usr/openv/netbackup/bin is the one\nprovided by NetBackup. If you are in doubt, reinstall it.\n■ Check /usr/openv/netbackup/bin/version on the client to verify that the\nclientisrunningthecorrectlevelsoftware.Ifthesoftwareisnotatthecorrect\nlevel,updatethesoftwareperthedirectionsintheNetBackupReleaseNotes.\n■ On a Windows client, create a tar debug log directory, retry the operation, and\ncheck the log." }, "182": { "code": 182, - "desc": "Tar received um inválido arquivo name", - "first_action": "Create um bpcd debug log diretório on o cliente .", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Create um bpcd debug log diretório on o cliente .\n■ On um Windows cliente, create um tar debug log diretório.\n■ Aumentar o logging level on o cliente:\n■ On um UNIX cliente, add o VERBOSE option to o\n/usr/openv/netbackup/bp.conf arquivo.\n■ On PC clients, aumentar o debug ou log level.\nVeja \"Changing o logging level on Windows clients\" in o NetBackup\nLogging Reference Guide.\n■ Rerun o operation, verifique o resulting debug logs para o parameters que\nforam passed to tar e contate Cohesity Technical Support." + "desc": "Tar received an invalid file name", + "first_action": "Create a bpcd debug log directory on the client .", + "full_action": "Do the following, as appropriate:\n■ Create a bpcd debug log directory on the client .\n■ On a Windows client, create a tar debug log directory.\n■ Increase the logging level on the client:\n■ On a UNIX client, add the VERBOSE option to the\n/usr/openv/netbackup/bp.conf file.\n■ On PC clients, increase the debug or log level.\nSee \"Changing the logging level on Windows clients\" in the NetBackup\nLogging Reference Guide.\n■ Rerun the operation, check the resulting debug logs for the parameters that\nwere passed to tar and contact Cohesity Technical Support." }, "183": { "code": 183, - "desc": "Tar received um inválido archive", + "desc": "Tar received an invalid archive", "first_action": "IftheproblemiswithaUNIXclient,createa/usr/openv/netbackup/logs/tar", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ IftheproblemiswithaUNIXclient,createa/usr/openv/netbackup/logs/tar\ndebug log diretório on o cliente e rerun o operation.\n■ Checkthetardebuglogfileforanyerrormessagesthatexplaintheproblem.\n■ Restart o cliente to veja if it clears o problema.\n■ When you finish com seu investigation de o problema, excluir o\n/usr/openv/netbackup/logs/ tar diretório on o cliente.\n■ If o problema está com um Microsoft Windows cliente, do o seguinte in o order\npresented:\n■ Create um bpcd debug log diretório on o cliente.\n■ On um Windows cliente, create um tar debug log diretório.\n■ Aumentar o debug ou log level.\nVeja \"Changing o logging level on Windows clients\" in o NetBackup\nLogging Reference Guide.\n■ Rerun o operation e verifique o resulting debug logs.\n■ Restart o cliente to veja if it clears o problema." + "full_action": "Do the following, as appropriate:\n■ IftheproblemiswithaUNIXclient,createa/usr/openv/netbackup/logs/tar\ndebug log directory on the client and rerun the operation.\n■ Checkthetardebuglogfileforanyerrormessagesthatexplaintheproblem.\n■ Restart the client to see if it clears the problem.\n■ When you finish with your investigation of the problem, delete the\n/usr/openv/netbackup/logs/ tar directory on the client.\n■ If the problem is with a Microsoft Windows client, do the following in the order\npresented:\n■ Create a bpcd debug log directory on the client.\n■ On a Windows client, create a tar debug log directory.\n■ Increase the debug or log level.\nSee \"Changing the logging level on Windows clients\" in the NetBackup\nLogging Reference Guide.\n■ Rerun the operation and check the resulting debug logs.\n■ Restart the client to see if it clears the problem." }, "184": { "code": 184, - "desc": "Tar had um unexpected erro", + "desc": "Tar had an unexpected error", "first_action": "IftheproblemiswithaUNIXclient,createa/usr/openv/netbackup/logs/tar", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ IftheproblemiswithaUNIXclient,createa/usr/openv/netbackup/logs/tar\ndebug log diretório on o cliente e rerun o operation.\n■ Checkthetardebuglogfileforanyerrormessagesthatexplaintheproblem.\n■ Restart o cliente to veja if it clears o problema.\n■ When you finish seu investigation de o problema, excluir o\n/usr/openv/netbackup/logs/tar diretório on o cliente.\n■ If o problema está com um Microsoft Windows cliente:\n■ Create um bpcd debug log diretório on o cliente .\n■ Aumentar o debug ou log level.\nVeja \"Changing o logging level on Windows clients\" in o NetBackup\nLogging Reference Guide.\n■ On um Windows cliente, create um tar debug log diretório.\n■ Retry o operation e verifique o resulting debug logs.\n■ Restart o cliente to veja if it clears o problema." + "full_action": "Do the following, as appropriate:\n■ IftheproblemiswithaUNIXclient,createa/usr/openv/netbackup/logs/tar\ndebug log directory on the client and rerun the operation.\n■ Checkthetardebuglogfileforanyerrormessagesthatexplaintheproblem.\n■ Restart the client to see if it clears the problem.\n■ When you finish your investigation of the problem, delete the\n/usr/openv/netbackup/logs/tar directory on the client.\n■ If the problem is with a Microsoft Windows client:\n■ Create a bpcd debug log directory on the client .\n■ Increase the debug or log level.\nSee \"Changing the logging level on Windows clients\" in the NetBackup\nLogging Reference Guide.\n■ On a Windows client, create a tar debug log directory.\n■ Retry the operation and check the resulting debug logs.\n■ Restart the client to see if it clears the problem." }, "185": { "code": 185, - "desc": "Tar did não find todos o arquivos to be restored", - "first_action": "If o problema está com um UNIX cliente:", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ If o problema está com um UNIX cliente:\n■ Enable bpcd debug logging por creating o\n/usr/openv/netbackup/logs/bpcd diretório on o cliente.\n■ Reruntheoperation,checktheresultingbpcdlogfilefortheparametersthat\nforam passed to nbtar, e contate Cohesity Technical Support.\n■ If o problema está com um Microsoft Windows cliente:\n■ Create um bpcd debug log diretório on o cliente.\n■ Aumentar o debug ou log level.\nVeja \"Changing o logging level on Windows clients\" in o NetBackup\nLogging Reference Guide.\n■ On um Windows cliente, create um tar debug log diretório.\n■ Retry o operation.\n■ Verifique o resulting debug logs para o parameters que foram passed to tar\ne contate Cohesity Technical Support." + "desc": "Tar did not find all the files to be restored", + "first_action": "If the problem is with a UNIX client:", + "full_action": "Do the following, as appropriate:\n■ If the problem is with a UNIX client:\n■ Enable bpcd debug logging by creating the\n/usr/openv/netbackup/logs/bpcd directory on the client.\n■ Reruntheoperation,checktheresultingbpcdlogfilefortheparametersthat\nwere passed to nbtar, and contact Cohesity Technical Support.\n■ If the problem is with a Microsoft Windows client:\n■ Create a bpcd debug log directory on the client.\n■ Increase the debug or log level.\nSee \"Changing the logging level on Windows clients\" in the NetBackup\nLogging Reference Guide.\n■ On a Windows client, create a tar debug log directory.\n■ Retry the operation.\n■ Check the resulting debug logs for the parameters that were passed to tar\nand contact Cohesity Technical Support." }, "186": { "code": 186, - "desc": "Tar received não data", - "first_action": "Retry o operation e verifique o status ou o progress log on o cliente para", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Retry o operation e verifique o status ou o progress log on o cliente para\nqualquer erro messages que reveal o problema.\n■ Verifique que o tape está disponível e readable.\n■ Verifique que o drive está in um UP state. Use o Dispositivo Monitor.\n■ Para detailed troubleshooting informação:\n■ Create um bptm debug log on o servidor.\n■ On um Windows cliente, create um tar debug log.\n■ Retry o operation e verifique o resulting debug logs." + "desc": "Tar received no data", + "first_action": "Retry the operation and check the status or the progress log on the client for", + "full_action": "Do the following, as appropriate:\n■ Retry the operation and check the status or the progress log on the client for\nany error messages that reveal the problem.\n■ Verify that the tape is available and readable.\n■ Verify that the drive is in an UP state. Use the Device Monitor.\n■ For detailed troubleshooting information:\n■ Create a bptm debug log on the server.\n■ On a Windows client, create a tar debug log.\n■ Retry the operation and check the resulting debug logs." }, "189": { "code": 189, - "desc": "O servidor está não allowed to gravar to o client’s arquivo systems", - "first_action": "On um UNIX cliente, excluir DISALLOW_SERVER_FILE_WRITES from o", - "full_action": "Performthefollowingtoperformrestoresorinstallsoftware\nfrom o servidor:\n■ On um UNIX cliente, excluir DISALLOW_SERVER_FILE_WRITES from o\n/usr/openv/netbackup/bp.conf arquivo.\n■ On um Microsoft Windows cliente, select Allow server-directed restores on o\nGeneral tab in o NetBackup Cliente Properties dialog box. To display this\ndialog box, start o Backup, Archive, e Restauração interface on o cliente e\nselect NetBackup Cliente Properties from o Arquivo menu." + "desc": "The server is not allowed to write to the client’s file systems", + "first_action": "On a UNIX client, delete DISALLOW_SERVER_FILE_WRITES from the", + "full_action": "Performthefollowingtoperformrestoresorinstallsoftware\nfrom the server:\n■ On a UNIX client, delete DISALLOW_SERVER_FILE_WRITES from the\n/usr/openv/netbackup/bp.conf file.\n■ On a Microsoft Windows client, select Allow server-directed restores on the\nGeneral tab in the NetBackup Client Properties dialog box. To display this\ndialog box, start the Backup, Archive, and Restore interface on the client and\nselect NetBackup Client Properties from the File menu." }, "190": { "code": 190, - "desc": "Found não images ou mídia matching o selection criteria", - "first_action": "Change o search criteria e retry.", - "full_action": "Change o search criteria e retry." + "desc": "Found no images or media matching the selection criteria", + "first_action": "Change the search criteria and retry.", + "full_action": "Change the search criteria and retry." }, "191": { "code": 191, - "desc": "Não images foram successfully processed", - "first_action": "Verifique o NetBackup Problemas relatório para o cause de o erro. To obtain", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Verifique o NetBackup Problemas relatório para o cause de o erro. To obtain\ndetailed troubleshooting informação, create um admin debug log diretório e\nretry o operation. Verifique o resulting debug log.\n■ If o backup ou duplicate job falhou para um policy configurado com um retention level\ngreater than 25, you can either upgrade o mídia servidor to NetBackup 8.0 ou\nlater ou set o retention level between 0 e 25. Note que o retention period\nforlevel25isalwayssettoexpireimmediatelyandthisvaluecannotbechanged.\n■ Iftheerrorwasencounteredduringduplicationofbackups,checktheduplication\nprogress log to help determinar o raiz cause de o problema.\n■ Um Auto Image Replication job may cause this erro. If o armazenamento lifecycle\npolicy names ou data classifications do não match o originating domain e\no target domain, o import job fails. Falhou imports appear in o Problemas\nrelatório when it está run on o target master servidor. O image está expired e\ndeleted during catalog cleanup. Note que o originating domain does não track\nfalhou imports.\nMore informação está disponível about troubleshooting this problema:\nPara more informação on troubleshooting this problema, por favor veja o About\nTroubleshootingAutoImageReplicationtopicoftheNetBackupTroubleshooting\nGuide.\n■ Um automatic import job may cause this erro. This job está um import job que\nshows um armazenamento lifecycle policy name.\nMore informação está disponível about troubleshooting this problema:\nPara more informação on troubleshooting this problema, por favor veja o About\nTroubleshootingAutoImageReplicationtopicoftheNetBackupTroubleshooting\nGuide.\n■ If um Vault job encontrado o erro responsible para o duplication, verifique o\nduplicate.log arquivos in seu sidxxx directories to determinar o raiz cause:\nUNIX:\n/usr/openv/netbackup/vault/sessions/vault_name/sidxxx\nWindows:\ninstall_path\\NetBackup\\vault\\sessions\\vault_name\\sidxxx\n(onde xxx está o session ID)\n■ Reduce o maximum fragment size on o armazenamento unidade que writes to this arquivo\nsystem. This value está typically less than 20 GB. But you may need to adjust o\nmaximum fragment size como necessary until o STS_EFILESYSTEM errors não\nlonger occur. O value está based on how much data que o armazenamento unidade writes\nto o image.\nTo change this value, in o NetBackup Administration Console, in o left\npane, expand NetBackup Management > Armazenamento. Then in o right pane,\ndouble-click o armazenamento unidade para this arquivo system. In o Change Armazenamento Unidade\ndialog box, change o value de o Maximum Fragment Size to 20480 MB (20\nGB) por checking o Reduce fragment size to checkbox e entering o new\nvalue.\n■ Aumentar o Allocation Unidade Size por reconfiguring o arquivo system. This usually\nrequires que you format o arquivo system, so this ação may não be um feasible para\num existing arquivo system. Consider this when you create um new arquivo system para\nBasicDisk images ou AdvancedDisk images. Because setting this value está\ndifferent on each OS arquivo system, refer to o appropriate OS ou arquivo system\ndocumentation para instructions.\n■ Garanta que o Logical Armazenamento Unidade (LSU) name ou o Domain Volume name\nhas less than 50 ASCII characters, including um hyphen (-) e um underscore\n(_), e que o name does não have um blank space." + "desc": "No images were successfully processed", + "first_action": "Check the NetBackup Problems report for the cause of the error. To obtain", + "full_action": "Do the following, as appropriate:\n■ Check the NetBackup Problems report for the cause of the error. To obtain\ndetailed troubleshooting information, create an admin debug log directory and\nretry the operation. Check the resulting debug log.\n■ If the backup or duplicate job failed for a policy configured with a retention level\ngreater than 25, you can either upgrade the media server to NetBackup 8.0 or\nlater or set the retention level between 0 and 25. Note that the retention period\nforlevel25isalwayssettoexpireimmediatelyandthisvaluecannotbechanged.\n■ Iftheerrorwasencounteredduringduplicationofbackups,checktheduplication\nprogress log to help determine the root cause of the problem.\n■ An Auto Image Replication job may cause this error. If the storage lifecycle\npolicy names or data classifications do not match the originating domain and\nthe target domain, the import job fails. Failed imports appear in the Problems\nreport when it is run on the target master server. The image is expired and\ndeleted during catalog cleanup. Note that the originating domain does not track\nfailed imports.\nMore information is available about troubleshooting this problem:\nFor more information on troubleshooting this problem, please see the About\nTroubleshootingAutoImageReplicationtopicoftheNetBackupTroubleshooting\nGuide.\n■ An automatic import job may cause this error. This job is an import job that\nshows a storage lifecycle policy name.\nMore information is available about troubleshooting this problem:\nFor more information on troubleshooting this problem, please see the About\nTroubleshootingAutoImageReplicationtopicoftheNetBackupTroubleshooting\nGuide.\n■ If a Vault job encountered the error responsible for the duplication, check the\nduplicate.log files in your sidxxx directories to determine the root cause:\nUNIX:\n/usr/openv/netbackup/vault/sessions/vault_name/sidxxx\nWindows:\ninstall_path\\NetBackup\\vault\\sessions\\vault_name\\sidxxx\n(where xxx is the session ID)\n■ Reduce the maximum fragment size on the storage unit that writes to this file\nsystem. This value is typically less than 20 GB. But you may need to adjust the\nmaximum fragment size as necessary until the STS_EFILESYSTEM errors no\nlonger occur. The value is based on how much data that the storage unit writes\nto the image.\nTo change this value, in the NetBackup Administration Console, in the left\npane, expand NetBackup Management > Storage. Then in the right pane,\ndouble-click the storage unit for this file system. In the Change Storage Unit\ndialog box, change the value of the Maximum Fragment Size to 20480 MB (20\nGB) by checking the Reduce fragment size to checkbox and entering the new\nvalue.\n■ Increase the Allocation Unit Size by reconfiguring the file system. This usually\nrequires that you format the file system, so this action may not be a feasible for\nan existing file system. Consider this when you create a new file system for\nBasicDisk images or AdvancedDisk images. Because setting this value is\ndifferent on each OS file system, refer to the appropriate OS or file system\ndocumentation for instructions.\n■ Ensure that the Logical Storage Unit (LSU) name or the Domain Volume name\nhas less than 50 ASCII characters, including a hyphen (-) and an underscore\n(_), and that the name does not have a blank space." }, "192": { "code": 192, - "desc": "VxSS authentication está requerido but não disponível", - "first_action": "Make sure que both systems estão configurado to use", - "full_action": "Make sure que both systems estão configurado to use\nNetBackup Access Control VxSS authentication com each other. Ou, make sure\nque both systems estão não configurado to use VxSS com each other. O first thing\ntocheckistheUseVxSSHostpropertiesvalueoneachsystem.Ifoneisconfigured\npara Requerido, o other must be configurado para Requerido ou AUTOMATIC. If\none está configurado para PROHIBITED,the other must be configurado para PROHIBITED\nou AUTOMATIC.\nVeja o NetBackup Administrator’s Guide, Volume I, para o seguinte informação:\nhow to set o Access Control-related host properties, e how to configure um\nsystem to use Access Control." + "desc": "VxSS authentication is required but not available", + "first_action": "Make sure that both systems are configured to use", + "full_action": "Make sure that both systems are configured to use\nNetBackup Access Control VxSS authentication with each other. Or, make sure\nthat both systems are not configured to use VxSS with each other. The first thing\ntocheckistheUseVxSSHostpropertiesvalueoneachsystem.Ifoneisconfigured\nfor REQUIRED, the other must be configured for REQUIRED or AUTOMATIC. If\none is configured for PROHIBITED,the other must be configured for PROHIBITED\nor AUTOMATIC.\nSee the NetBackup Administrator’s Guide, Volume I, for the following information:\nhow to set the Access Control-related host properties, and how to configure a\nsystem to use Access Control." }, "193": { "code": 193, - "desc": "VxSS authentication está solicitado but não allowed", - "first_action": "Make sure que both systems estão configurado to use", - "full_action": "Make sure que both systems estão configurado to use\nNetBackup Access Control VxSS authentication com each other. Ou, make sure\nque both systems estão não configurado to use VxSS com each other. O first thing\ntocheckistheUseVxSSHostpropertiesvalueoneachsystem.Ifoneisconfigured\npara Requerido, o other must be configurado para Requerido ou AUTOMATIC. If\none está configurado para PROHIBITED,the other must be configurado para PROHIBITED\nou AUTOMATIC.\nVeja o NetBackup Administrator’s Guide, Volume I, para o seguinte informação:\nhow to set o Access Control-related host properties how to configure um system\nto use Access Control." + "desc": "VxSS authentication is requested but not allowed", + "first_action": "Make sure that both systems are configured to use", + "full_action": "Make sure that both systems are configured to use\nNetBackup Access Control VxSS authentication with each other. Or, make sure\nthat both systems are not configured to use VxSS with each other. The first thing\ntocheckistheUseVxSSHostpropertiesvalueoneachsystem.Ifoneisconfigured\nfor REQUIRED, the other must be configured for REQUIRED or AUTOMATIC. If\none is configured for PROHIBITED,the other must be configured for PROHIBITED\nor AUTOMATIC.\nSee the NetBackup Administrator’s Guide, Volume I, for the following information:\nhow to set the Access Control-related host properties how to configure a system\nto use Access Control." }, "194": { "code": 194, - "desc": "O maximum number de jobs per cliente está set to 0", - "first_action": "To enable backups e archives, change o Maximum", - "full_action": "To enable backups e archives, change o Maximum\njobs per cliente value to o wanted nonzero setting. This attribute está on o Global\nNetBackup Attributes tab in o Master Servidor Properties dialog box.\nVeja \"usando o Host Properties window to access configuration settings\" in o\nNetBackup Troubleshooting Guide." + "desc": "The maximum number of jobs per client is set to 0", + "first_action": "To enable backups and archives, change the Maximum", + "full_action": "To enable backups and archives, change the Maximum\njobs per client value to the wanted nonzero setting. This attribute is on the Global\nNetBackup Attributes tab in the Master Server Properties dialog box.\nSee \"Using the Host Properties window to access configuration settings\" in the\nNetBackup Troubleshooting Guide." }, "195": { "code": 195, - "desc": "Cliente backup foi não attempted", - "first_action": "Retry o backup either immediately com um manual backup ou allow o normal", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Retry o backup either immediately com um manual backup ou allow o normal\nscheduler retries.\n■ Para additional informação, verifique o Todos Log Entradas relatório. Para detailed\ntroubleshooting informação, aumentar o logging level para o diagnostic e\ndebug logs para nbpem, nbjm, e nbrb.\nUse o vxlogcfg comando como explained in o seguinte topic:\nVeja \"About unified logging\" in o NetBackup Logging Reference Guide.\nAfter o next backup try, verifique o logs." + "desc": "Client backup was not attempted", + "first_action": "Retry the backup either immediately with a manual backup or allow the normal", + "full_action": "Do the following, as appropriate:\n■ Retry the backup either immediately with a manual backup or allow the normal\nscheduler retries.\n■ For additional information, check the All Log Entries report. For detailed\ntroubleshooting information, increase the logging level for the diagnostic and\ndebug logs for nbpem, nbjm, and nbrb.\nUse the vxlogcfg command as explained in the following topic:\nSee \"About unified logging\" in the NetBackup Logging Reference Guide.\nAfter the next backup try, check the logs." }, "196": { "code": 196, - "desc": "Cliente backup foi não attempted because backup window closed", - "first_action": "If possible, change o schedule to extend o backup window para this", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ If possible, change o schedule to extend o backup window para this\ncombination de policy e schedule so it does não occur again.\n■ If o backup must be run, use o Manual Backup comando on o Policy\nmenu in o Backup Policy Management window to executar o backup.\nManual backups ignore o backup window." + "desc": "Client backup was not attempted because backup window closed", + "first_action": "If possible, change the schedule to extend the backup window for this", + "full_action": "Do the following, as appropriate:\n■ If possible, change the schedule to extend the backup window for this\ncombination of policy and schedule so it does not occur again.\n■ If the backup must be run, use the Manual Backup command on the Policy\nmenu in the Backup Policy Management window to perform the backup.\nManual backups ignore the backup window." }, "197": { "code": 197, - "desc": "O specified schedule does não exist in o specified policy", - "first_action": "Verifique o cliente progress log (if disponível) to determinar o policy e schedule", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Verifique o cliente progress log (if disponível) to determinar o policy e schedule\nque foram specified.\n■ Verifique o configuration on o master servidor to determinar if o schedule está\nvalid para o policy. If o schedule está não valid, either add o schedule to o\npolicy configuration ou specify um valid schedule on o cliente." + "desc": "The specified schedule does not exist in the specified policy", + "first_action": "Check the client progress log (if available) to determine the policy and schedule", + "full_action": "Do the following, as appropriate:\n■ Check the client progress log (if available) to determine the policy and schedule\nthat were specified.\n■ Check the configuration on the master server to determine if the schedule is\nvalid for the policy. If the schedule is not valid, either add the schedule to the\npolicy configuration or specify a valid schedule on the client." }, "198": { "code": 198, - "desc": "Não active policies contain schedules de o solicitado type para this cliente NetBackup status codes 215 NetBackup status codes", - "first_action": "If o cliente está in such um policy, verifique o general policy attributes to verifique que", - "full_action": "Determinar if o cliente está in qualquer policy que has um schedule\nde o appropriate type (either usuário backup ou archive).\n■ If o cliente está in such um policy, verifique o general policy attributes to verifique que\no policy está set to active.\n■ If o cliente está não in such um policy, do either de o seguinte:\n■ Add um schedule de o appropriate type to um existing policy que has this\ncliente.\n■ Create um new policy que has this cliente e um schedule de o appropriate\ntype." + "desc": "No active policies contain schedules of the requested type for this client NetBackup status codes 215 NetBackup status codes", + "first_action": "If the client is in such a policy, check the general policy attributes to verify that", + "full_action": "Determine if the client is in any policy that has a schedule\nof the appropriate type (either user backup or archive).\n■ If the client is in such a policy, check the general policy attributes to verify that\nthe policy is set to active.\n■ If the client is not in such a policy, do either of the following:\n■ Add a schedule of the appropriate type to an existing policy that has this\nclient.\n■ Create a new policy that has this client and a schedule of the appropriate\ntype." }, "199": { "code": 199, - "desc": "Operation não allowed during this time period", - "first_action": "If possible, retry o operation when o backup window está abrir.", - "full_action": "Determinar o policies to which this cliente belongs que\nalso have um schedule de o appropriate type (either usuário backup ou archive).\n■ If possible, retry o operation when o backup window está abrir.\n■ If o backup window está não abrir during appropriate time periods, adjust um\nbackup window para um schedule in one de o policies." + "desc": "Operation not allowed during this time period", + "first_action": "If possible, retry the operation when the backup window is open.", + "full_action": "Determine the policies to which this client belongs that\nalso have a schedule of the appropriate type (either user backup or archive).\n■ If possible, retry the operation when the backup window is open.\n■ If the backup window is not open during appropriate time periods, adjust a\nbackup window for a schedule in one of the policies." }, "200": { "code": 200, - "desc": "O scheduler found que não backups estão due. Ou, o target hosts do não need to be upgraded.", - "first_action": "Examine o NetBackup Todos Log Entradas relatório para qualquer messages in addition to", - "full_action": "Usually, this message can be considered informational\ne does não indicate um problema. However, if you suspect um problema, do o\nseguinte:\n■ Examine o NetBackup Todos Log Entradas relatório para qualquer messages in addition to\no one que indicates o scheduler found nothing to do.\n■ Examine o policy configuration para todos policies ou o specific policy in question\nto determinar if qualquer de o reasons in o Explanation section apply.\n■ Toobtaindetailedtroubleshootinginformation,increasetheunifiedlogginglevel\npara o diagnostic e debug logs.\nUse o vxlogcfg comando como explained in o seguinte procedure:\nVeja \"About unified logging\" in o NetBackup Logging Reference Guide.\nRetry o operation e verifique o resulting logs.\n■ Para SQL Servidor policies que use intelligent groups, garanta que o credentials\nestão valid para o SQL Servidor instances ou databases que estão included in o\npolicy.\nRefertotheNetBackupforMicrosoftSQLServerAdministrator’sGuideformore\ndetails on this erro." + "desc": "The scheduler found that no backups are due. Or, the target hosts do not need to be upgraded.", + "first_action": "Examine the NetBackup All Log Entries report for any messages in addition to", + "full_action": "Usually, this message can be considered informational\nand does not indicate a problem. However, if you suspect a problem, do the\nfollowing:\n■ Examine the NetBackup All Log Entries report for any messages in addition to\nthe one that indicates the scheduler found nothing to do.\n■ Examine the policy configuration for all policies or the specific policy in question\nto determine if any of the reasons in the Explanation section apply.\n■ Toobtaindetailedtroubleshootinginformation,increasetheunifiedlogginglevel\nfor the diagnostic and debug logs.\nUse the vxlogcfg command as explained in the following procedure:\nSee \"About unified logging\" in the NetBackup Logging Reference Guide.\nRetry the operation and check the resulting logs.\n■ For SQL Server policies that use intelligent groups, ensure that the credentials\nare valid for the SQL Server instances or databases that are included in the\npolicy.\nRefertotheNetBackupforMicrosoftSQLServerAdministrator’sGuideformore\ndetails on this error." }, "201": { "code": 201, - "desc": "Handshake falhou com servidor backup restauração manager", + "desc": "Handshaking failed with server backup restore manager", "first_action": "Determinetheactivitythatencounteredthehandshakefailurebyexaminingthe", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Determinetheactivitythatencounteredthehandshakefailurebyexaminingthe\nNetBackup Todos Log Entradas relatório para o appropriate time period. If there estão\nmídia servers, determinar if:\n■ O handshake falha foi encontrado between o master e um mídia\nservidor.\nou\n■ Apenas o master servidor foi involved.\n■ Ifnecessary,createthefollowingdebuglogdirectoriesandincreasethelogging\nlevel:\n■ bpcd on o NetBackup mídia host (can be either o master ou um mídia\nservidor).\n■ Iftheerrorwasencounteredduringabackupoperation,increasethelogging\nlevel para o diagnostic e debug logs para nbpem, nbjm, e nbrb.\nUse o vxlogcfg comando como explained in o seguinte procedure:\nVeja \"About unified logging\" in o NetBackup Logging Reference Guide.\n■ If o erro foi encontrado during um restauração operation, bprd on o master\nservidor.\n■ If o erro foi encontrado during um mídia list operation, admin in o\nNetBackup logs/admin diretório on o master servidor.\n■ Status code 201 may occur if nbjm fails after it connects to bpbrm ou bpmount\nbut before o policy arquivo list está sent. Examine o nbjm unified log (originator ID\n117) ou o bpbrm ou o bpmount legacy logs para more detail on o cause de\no erro.\n■ Retry o operation e examine o resulting debug logs para informação on\npor que o erro ocorreu." + "full_action": "Do the following, as appropriate:\n■ Determinetheactivitythatencounteredthehandshakefailurebyexaminingthe\nNetBackup All Log Entries report for the appropriate time period. If there are\nmedia servers, determine if:\n■ The handshake failure was encountered between the master and a media\nserver.\nor\n■ Only the master server was involved.\n■ Ifnecessary,createthefollowingdebuglogdirectoriesandincreasethelogging\nlevel:\n■ bpcd on the NetBackup media host (can be either the master or a media\nserver).\n■ Iftheerrorwasencounteredduringabackupoperation,increasethelogging\nlevel for the diagnostic and debug logs for nbpem, nbjm, and nbrb.\nUse the vxlogcfg command as explained in the following procedure:\nSee \"About unified logging\" in the NetBackup Logging Reference Guide.\n■ If the error was encountered during a restore operation, bprd on the master\nserver.\n■ If the error was encountered during a media list operation, admin in the\nNetBackup logs/admin directory on the master server.\n■ Status code 201 may occur if nbjm fails after it connects to bpbrm or bpmount\nbut before the policy file list is sent. Examine the nbjm unified log (originator ID\n117) or the bpbrm or the bpmount legacy logs for more detail on the cause of\nthe error.\n■ Retry the operation and examine the resulting debug logs for information on\nwhy the error occurred." }, "202": { "code": 202, - "desc": "Esgotado fora connecting to servidor backup restauração manager", - "first_action": "Verifique que o schedule specifies o correct armazenamento unidade.", - "full_action": "Determinar which activity encontrado o conexão\ntempo limite esgotado falha por examining o Todos Log Entradas relatório para o appropriate time\nperiod. If there estão mídia servers, determinar if o tempo limite esgotado ocorreu between o\nmaster e um mídia servidor ou if apenas o master foi involved.\n■ Verifique que o schedule specifies o correct armazenamento unidade.\n■ Run o ping comando from one host to another por usando o seguinte\ncombinations:\n■ From o master servidor, ping o master e todos mídia servers por usando o\nhost names que estão found in o armazenamento unidade configuration.\n■ From each de o mídia servers, ping o master servidor por usando o host\nname que está specified in o NetBackup servidor list. On um UNIX ou Linux\nserver,themasteristhefirstSERVERentryinthebp.conffile.OnaWindows\nservidor, o master está designated on o Servers tab in o Master Servidor\nProperties dialog box.\nVeja \"usando o Host Properties window to access configuration settings\" in\no NetBackup Troubleshooting Guide.\n■ Verifique que o master servidor can communicate com bpcd on o host que has\no armazenamento unidade.\n■ Executar o seguinte procedures:\nVeja \"Testing o mídia servidor e clients\" in o NetBackup Troubleshooting\nGuide.\nVeja \"resolvendo rede communication problemas\" in o NetBackup\nTroubleshooting Guide.\n■ If necessary, create debug log directories para o seguinte processos e retry\no operation. Then, verifique o resulting debug logs on o master servidor:\n■ If o erro ocorreu during um backup operation, aumentar o logging level\npara o diagnostic e debug logs para nbpem, nbjm, e nbrb.\nUse o vxlogcfg comando como explained in o seguinte procedure:\nVeja \"About unified logging\" in o NetBackup Logging Reference Guide.\nAlso, verifique o bpcd legacy debug logs.\n■ If o erro occurs during um restauração operation, verifique o bprd debug logs." + "desc": "Timed out connecting to server backup restore manager", + "first_action": "Verify that the schedule specifies the correct storage unit.", + "full_action": "Determine which activity encountered the connection\ntimeout failure by examining the All Log Entries report for the appropriate time\nperiod. If there are media servers, determine if the timeout occurred between the\nmaster and a media server or if only the master was involved.\n■ Verify that the schedule specifies the correct storage unit.\n■ Run the ping command from one host to another by using the following\ncombinations:\n■ From the master server, ping the master and all media servers by using the\nhost names that are found in the storage unit configuration.\n■ From each of the media servers, ping the master server by using the host\nname that is specified in the NetBackup server list. On a UNIX or Linux\nserver,themasteristhefirstSERVERentryinthebp.conffile.OnaWindows\nserver, the master is designated on the Servers tab in the Master Server\nProperties dialog box.\nSee \"Using the Host Properties window to access configuration settings\" in\nthe NetBackup Troubleshooting Guide.\n■ Verify that the master server can communicate with bpcd on the host that has\nthe storage unit.\n■ Perform the following procedures:\nSee \"Testing the media server and clients\" in the NetBackup Troubleshooting\nGuide.\nSee \"Resolving network communication problems\" in the NetBackup\nTroubleshooting Guide.\n■ If necessary, create debug log directories for the following processes and retry\nthe operation. Then, check the resulting debug logs on the master server:\n■ If the error occurred during a backup operation, increase the logging level\nfor the diagnostic and debug logs for nbpem, nbjm, and nbrb.\nUse the vxlogcfg command as explained in the following procedure:\nSee \"About unified logging\" in the NetBackup Logging Reference Guide.\nAlso, check the bpcd legacy debug logs.\n■ If the error occurs during a restore operation, check the bprd debug logs." }, "203": { "code": 203, - "desc": "Servidor backup restauração manager’s rede está unreachable NetBackup status codes 219 NetBackup status codes", + "desc": "Server backup restore manager’s network is unreachable NetBackup status codes 219 NetBackup status codes", "first_action": "Fromthemasterserver,pingthemasterandallmediaserversbyusingthehost", - "full_action": "Determinar which activity encontrado this falha por\nexamining o Todos Log Entradas relatório para o appropriate time frame. If there está more\nthan one NetBackup servidor (one ou more mídia servers), determinar o seguinte:\nifthefailurewasbetweenthemasterandamediaserverorifonlythemasterserver\nfoi involved. Run o ping comando from one host to another por usando o\nseguinte combinations:\n■ Fromthemasterserver,pingthemasterandallmediaserversbyusingthehost\nnames in o armazenamento unidade configuration.\n■ From each de o mídia servers, ping o master servidor host por usando o host\nname que está specified in o NetBackup servidor list. On um UNIX ou Linux servidor,\no master está o first Servidor entry in o bp.conf arquivo. On um Windows servidor,\no master está designated on o Servers tab in o Master Servidor Properties\ndialog.\nVeja \"usando o Host Properties window to access configuration settings\" in o\nNetBackup Troubleshooting Guide.\n■ Executar o seguinte procedures:\nVeja \"Testing o mídia servidor e clients\" in o NetBackup Troubleshooting\nGuide.\nVeja \"resolvendo rede communication problemas\" in o NetBackup\nTroubleshooting Guide.\n■ Ifnecessary,createdebuglogdirectoriesforbprdandretrytheoperation.Then,\nchecktheresultingdebuglogsonthemasterserver.Iftheerroroccurredduring\num restauração, verifique o bprd debug logs." + "full_action": "Determine which activity encountered this failure by\nexamining the All Log Entries report for the appropriate time frame. If there is more\nthan one NetBackup server (one or more media servers), determine the following:\nifthefailurewasbetweenthemasterandamediaserverorifonlythemasterserver\nwas involved. Run the ping command from one host to another by using the\nfollowing combinations:\n■ Fromthemasterserver,pingthemasterandallmediaserversbyusingthehost\nnames in the storage unit configuration.\n■ From each of the media servers, ping the master server host by using the host\nname that is specified in the NetBackup server list. On a UNIX or Linux server,\nthe master is the first SERVER entry in the bp.conf file. On a Windows server,\nthe master is designated on the Servers tab in the Master Server Properties\ndialog.\nSee \"Using the Host Properties window to access configuration settings\" in the\nNetBackup Troubleshooting Guide.\n■ Perform the following procedures:\nSee \"Testing the media server and clients\" in the NetBackup Troubleshooting\nGuide.\nSee \"Resolving network communication problems\" in the NetBackup\nTroubleshooting Guide.\n■ Ifnecessary,createdebuglogdirectoriesforbprdandretrytheoperation.Then,\nchecktheresultingdebuglogsonthemasterserver.Iftheerroroccurredduring\na restore, check the bprd debug logs." }, "204": { "code": 204, - "desc": "Conexão recusada por servidor backup restauração manager", + "desc": "Connection refused by server backup restore manager", "first_action": "Fromthemasterserver,pingthemasterandallmediaserversbyusingthehost", - "full_action": "Runthepingcommandfromonehosttoanotherbyusing\no seguinte combinations:\n■ Fromthemasterserver,pingthemasterandallmediaserversbyusingthehost\nnames in o armazenamento unidade configuration.\n■ From each de o mídia servers, ping o master servidor por usando o name que\nfoi specified in o NetBackup servidor list. On um UNIX ou Linux servidor, this\nmaster está o first Servidor entry in o bp.conf arquivo. On um Windows servidor, o\nmasterisdesignatedontheServerstabintheMasterServerPropertiesdialog\nbox. O seguinte topic shows how to access this dialog box:\nVeja \"usando o Host Properties window to access configuration settings\" in o\nNetBackup Troubleshooting Guide.\n■ On UNIX e Linux servers, verifique que o bpcd entradas in /etc/services ou\nNIS on todos o servers estão identical. Verifique que o mídia host listens on o\ncorrectportforconnectionstobpcd.Toverify,runoneofthefollowingcommands\n(depending on platform e operating system):\nnetstat -um | grep bpcd\nnetstat -um | grep 13782 (ou o value que foi specified during o install)\nrpcinfo -p | grep 13782 (ou o value que foi specified during o install)\nOn UNIX e Linux servers, it may be necessary to change o service number\npara o seguinte: bpcd in /etc/services e o NIS services map e send\nSIGHUP signals to o inetd processos on o clients.\n/bin/ps -ef | grep inetd\nkill -HUP the_inetd_pid\nou\n/bin/ps -aux | grep inetd\nkill -HUP the_inetd_pid\nNote: On um Hewlett-Packard UNIX platform, use inetd -c to send um SIGHUP to\ninetd.\n■ On Windows servers, do o seguinte:\n■ Verifique que o bpcd entradas estão correct in o seguinte:\n%SystemRoot%\\system32\\drivers\\etc\\services\n■ Verifique que o seguinte numbers match o settings in o services arquivo:\nNetBackupClientServicePortnumberandNetBackupRequestService\nPortnumberontheNetworktabintheNetBackupClientPropertiesdialog\nbox. To display this dialog box, start o Backup, Archive, e Restauração\ninterface e select NetBackup Cliente Properties on o Arquivo menu.\nO values on o Rede tab estão written to o services arquivo when o\nNetBackup Cliente service starts.\n■ Stop e restart o NetBackup services.\n■ Executar o seguinte procedures:\nVeja \"Testing o mídia servidor e clients\" in o NetBackup Troubleshooting\nGuide.\nVeja \"resolvendo rede communication problemas\" in o NetBackup\nTroubleshooting Guide.\n■ Ifnecessary,createdebuglogdirectoriesforbprdandretrytheoperation.Then,\nverifique o resulting debug logs on o master servidor:\n■ If o erro ocorreu during um backup operation, verifique o nbpem, nbjm, e\nnbrb logs por usando o vxlogview comando.\n■ If o erro ocorreu during um restauração operation, verifique o bprd debug logs." + "full_action": "Runthepingcommandfromonehosttoanotherbyusing\nthe following combinations:\n■ Fromthemasterserver,pingthemasterandallmediaserversbyusingthehost\nnames in the storage unit configuration.\n■ From each of the media servers, ping the master server by using the name that\nwas specified in the NetBackup server list. On a UNIX or Linux server, this\nmaster is the first SERVER entry in the bp.conf file. On a Windows server, the\nmasterisdesignatedontheServerstabintheMasterServerPropertiesdialog\nbox. The following topic shows how to access this dialog box:\nSee \"Using the Host Properties window to access configuration settings\" in the\nNetBackup Troubleshooting Guide.\n■ On UNIX and Linux servers, verify that the bpcd entries in /etc/services or\nNIS on all the servers are identical. Verify that the media host listens on the\ncorrectportforconnectionstobpcd.Toverify,runoneofthefollowingcommands\n(depending on platform and operating system):\nnetstat -a | grep bpcd\nnetstat -a | grep 13782 (or the value that was specified during the install)\nrpcinfo -p | grep 13782 (or the value that was specified during the install)\nOn UNIX and Linux servers, it may be necessary to change the service number\nfor the following: bpcd in /etc/services and the NIS services map and send\nSIGHUP signals to the inetd processes on the clients.\n/bin/ps -ef | grep inetd\nkill -HUP the_inetd_pid\nor\n/bin/ps -aux | grep inetd\nkill -HUP the_inetd_pid\nNote: On a Hewlett-Packard UNIX platform, use inetd -c to send a SIGHUP to\ninetd.\n■ On Windows servers, do the following:\n■ Verify that the bpcd entries are correct in the following:\n%SystemRoot%\\system32\\drivers\\etc\\services\n■ Verify that the following numbers match the settings in the services file:\nNetBackupClientServicePortnumberandNetBackupRequestService\nPortnumberontheNetworktabintheNetBackupClientPropertiesdialog\nbox. To display this dialog box, start the Backup, Archive, and Restore\ninterface and select NetBackup Client Properties on the File menu.\nThe values on the Network tab are written to the services file when the\nNetBackup Client service starts.\n■ Stop and restart the NetBackup services.\n■ Perform the following procedures:\nSee \"Testing the media server and clients\" in the NetBackup Troubleshooting\nGuide.\nSee \"Resolving network communication problems\" in the NetBackup\nTroubleshooting Guide.\n■ Ifnecessary,createdebuglogdirectoriesforbprdandretrytheoperation.Then,\ncheck the resulting debug logs on the master server:\n■ If the error occurred during a backup operation, check the nbpem, nbjm, and\nnbrb logs by using the vxlogview command.\n■ If the error occurred during a restore operation, check the bprd debug logs." }, "205": { "code": 205, - "desc": "Não é possível conectar to servidor backup restauração manager", + "desc": "Cannot connect to server backup restore manager", "first_action": "Fromthemasterserver,pingthemasterandallmediaserversbyusingthehost", - "full_action": "Runthepingcommandfromonehosttoanotherbyusing\no seguinte combinations:\n■ Fromthemasterserver,pingthemasterandallmediaserversbyusingthehost\nnames in o armazenamento unidade configuration.\n■ From each de o mídia servers, ping o master servidor por usando o name que\nestá specified in o NetBackup servidor list. On um UNIX ou Linux servidor, this master\nestá o first Servidor entry in o bp.conf arquivo. On um Windows servidor, o master\nestá designated on o Servers tab in o Master Servidor Properties dialog box.\nVeja \"usando o Host Properties window to access configuration settings\" in o\nNetBackup Troubleshooting Guide.\n■ On um UNIX ou Linux servidor, verifique que o bpcd entry in /etc/services ou NIS\non todos o servers estão identical. Verifique que o mídia host listens on o correct\nport para connections to bpcd. To verifique, run one de o seguinte commands\n(depending on platform e operating system):\nnetstat -um | grep bpcd\nnetstat -um | grep 13782 (ou o value que está specified during o install)\nrpcinfo -p | grep 13782 (ou o value que está specified during o install)\n■ On Windows servers, do o seguinte:\n■ Verifique que o bpcd entradas estão correct in o services arquivo:\n%SystemRoot%\\system32\\drivers\\etc\\services\n■ Verifique que o seguinte numbers match o settings in o services arquivo:\nNetBackupClientServicePortnumberandNetBackupRequestService\nPortnumberontheNetworktabintheNetBackupClientPropertiesdialog\nbox. To display this dialog box, start o Backup, Archive, e Restauração\ninterface e select NetBackup Cliente Properties on o Arquivo menu.\nO values on o Rede tab estão written to o services arquivo when o\nNetBackup Cliente service starts.\n■ Stop e restart o NetBackup services.\n■ Executar o seguinte procedures:\nVeja \"Testing o mídia servidor e clients\" in o NetBackup Troubleshooting\nGuide.\nVeja \"resolvendo rede communication problemas\" in o NetBackup\nTroubleshooting Guide.\n■ Create um bpcd debug log diretório on o servidor que has o armazenamento unidade e\nretry o operation. Then, verifique para additional informação in o debug log." + "full_action": "Runthepingcommandfromonehosttoanotherbyusing\nthe following combinations:\n■ Fromthemasterserver,pingthemasterandallmediaserversbyusingthehost\nnames in the storage unit configuration.\n■ From each of the media servers, ping the master server by using the name that\nis specified in the NetBackup server list. On a UNIX or Linux server, this master\nis the first SERVER entry in the bp.conf file. On a Windows server, the master\nis designated on the Servers tab in the Master Server Properties dialog box.\nSee \"Using the Host Properties window to access configuration settings\" in the\nNetBackup Troubleshooting Guide.\n■ On a UNIX or Linux server, verify that the bpcd entry in /etc/services or NIS\non all the servers are identical. Verify that the media host listens on the correct\nport for connections to bpcd. To verify, run one of the following commands\n(depending on platform and operating system):\nnetstat -a | grep bpcd\nnetstat -a | grep 13782 (or the value that is specified during the install)\nrpcinfo -p | grep 13782 (or the value that is specified during the install)\n■ On Windows servers, do the following:\n■ Verify that the bpcd entries are correct in the services file:\n%SystemRoot%\\system32\\drivers\\etc\\services\n■ Verify that the following numbers match the settings in the services file:\nNetBackupClientServicePortnumberandNetBackupRequestService\nPortnumberontheNetworktabintheNetBackupClientPropertiesdialog\nbox. To display this dialog box, start the Backup, Archive, and Restore\ninterface and select NetBackup Client Properties on the File menu.\nThe values on the Network tab are written to the services file when the\nNetBackup Client service starts.\n■ Stop and restart the NetBackup services.\n■ Perform the following procedures:\nSee \"Testing the media server and clients\" in the NetBackup Troubleshooting\nGuide.\nSee \"Resolving network communication problems\" in the NetBackup\nTroubleshooting Guide.\n■ Create a bpcd debug log directory on the server that has the storage unit and\nretry the operation. Then, check for additional information in the debug log." }, "206": { "code": 206, - "desc": "Access to servidor backup restauração manager negada", - "first_action": "Verifique que o master servidor appears como um servidor in its own servidor list como well", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Verifique que o master servidor appears como um servidor in its own servidor list como well\ncomo being listed on todos mídia servers.\nIf you change o master servidor list, stop e restart o NetBackup Banco de dados\nManager (bpdbm) e NetBackup Request Daemon (bprd) to garanta que todos\nappropriate NetBackup processos use o new servidor entry.\n■ Ifnecessary,createdebuglogdirectoriesforbprdandretrytheoperation.Then,\nverifique o resulting debug logs on o master servidor:\n■ If o erro ocorreu during um backup operation, verifique o nbpem, nbjm, e\nnbrb logs por usando o vxlogview comando.\n■ If o erro ocorreu during um restauração operation, verifique o bprd debug logs." + "desc": "Access to server backup restore manager denied", + "first_action": "Verify that the master server appears as a server in its own server list as well", + "full_action": "Do the following, as appropriate:\n■ Verify that the master server appears as a server in its own server list as well\nas being listed on all media servers.\nIf you change the master server list, stop and restart the NetBackup Database\nManager (bpdbm) and NetBackup Request Daemon (bprd) to ensure that all\nappropriate NetBackup processes use the new server entry.\n■ Ifnecessary,createdebuglogdirectoriesforbprdandretrytheoperation.Then,\ncheck the resulting debug logs on the master server:\n■ If the error occurred during a backup operation, check the nbpem, nbjm, and\nnbrb logs by using the vxlogview command.\n■ If the error occurred during a restore operation, check the bprd debug logs." }, "207": { "code": 207, - "desc": "Erro obtaining date de last backup para cliente", - "first_action": "Verifique que o NetBackup Banco de dados Manager, bpdbm, está executando.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Verifique que o NetBackup Banco de dados Manager, bpdbm, está executando.\n■ ExaminetheAllLogEntriesreportfortheappropriatetimeframetogathermore\ninformação about o falha.\n■ Para detailed troubleshooting informação, create um bpdbm log diretório on o\nmaster servidor. Aumentar o logging level para o diagnostic e debug logs para\nnbpem.\nUse o vxlogcfg comando como explained in o seguinte topic:\nVeja \"About unified logging\" in o NetBackup Logging Reference Guide.\nRetry o operation, then verifique o resulting logs." + "desc": "Error obtaining date of last backup for client", + "first_action": "Verify that the NetBackup Database Manager, bpdbm, is running.", + "full_action": "Do the following, as appropriate:\n■ Verify that the NetBackup Database Manager, bpdbm, is running.\n■ ExaminetheAllLogEntriesreportfortheappropriatetimeframetogathermore\ninformation about the failure.\n■ For detailed troubleshooting information, create a bpdbm log directory on the\nmaster server. Increase the logging level for the diagnostic and debug logs for\nnbpem.\nUse the vxlogcfg command as explained in the following topic:\nSee \"About unified logging\" in the NetBackup Logging Reference Guide.\nRetry the operation, then check the resulting logs." }, "209": { "code": 209, - "desc": "Erro creating ou getting message queue", - "first_action": "Create debug log directories on o master servidor e", - "full_action": "Create debug log directories on o master servidor e\nretry o operation. Then, determinar o type de system falha por examining o\nlogs. Start com o bprd debug log.\nOn UNIX e Linux servers, also gather o output de o ipcs -um comando to\nveja what system resources estão currently in use." + "desc": "Error creating or getting message queue", + "first_action": "Create debug log directories on the master server and", + "full_action": "Create debug log directories on the master server and\nretry the operation. Then, determine the type of system failure by examining the\nlogs. Start with the bprd debug log.\nOn UNIX and Linux servers, also gather the output of the ipcs -a command to\nsee what system resources are currently in use." }, "210": { "code": 210, - "desc": "Erro receiving informação on message queue", - "first_action": "Create debug log directories on o master servidor e", - "full_action": "Create debug log directories on o master servidor e\nretry o operation. Then, determinar o type de system falha por examining o\nlogs. Start com o bprd debug log.\nOn UNIX e Linux servers, also gather o output de o ipcs -um comando to\nveja what system resources estão currently in use." + "desc": "Error receiving information on message queue", + "first_action": "Create debug log directories on the master server and", + "full_action": "Create debug log directories on the master server and\nretry the operation. Then, determine the type of system failure by examining the\nlogs. Start with the bprd debug log.\nOn UNIX and Linux servers, also gather the output of the ipcs -a command to\nsee what system resources are currently in use." }, "212": { "code": 212, - "desc": "Erro sending informação on message queue", - "first_action": "Create debug log directories on o master servidor e", - "full_action": "Create debug log directories on o master servidor e\nretry o operation. Then, determinar o type de system falha por examining o\nlogs. Start com o bprd debug log.\nOn UNIX e Linux servers, also, gather o output de o ipcs -um comando to\nveja what system resources estão currently in use." + "desc": "Error sending information on message queue", + "first_action": "Create debug log directories on the master server and", + "full_action": "Create debug log directories on the master server and\nretry the operation. Then, determine the type of system failure by examining the\nlogs. Start with the bprd debug log.\nOn UNIX and Linux servers, also, gather the output of the ipcs -a command to\nsee what system resources are currently in use." }, "213": { "code": 213, - "desc": "Não armazenamento units disponível para use", - "first_action": "Examine o Backup Status e Todos Log Entradas relatório para o appropriate time", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Examine o Backup Status e Todos Log Entradas relatório para o appropriate time\nperiod to determinar o policy ou schedule que received o erro.\n■ Verifique que o mídia servidor has não been deactivated para o armazenamento unidade ou\nunits que estão unavailable.\n■ Verifique que o armazenamento unit’s drives estão não down.\n■ Verifique o seguinte attribute settings para todos armazenamento units:\n■ Para disco armazenamento units, o Maximum concurrent jobs está não set to 0\n■ Para Mídia Manager armazenamento units, o Maximum concurrent gravar drives\nestá não set to 0\n■ Verifique que o robot number e host name in o armazenamento unidade configuration\nmatches o Mídia e Dispositivo Management dispositivo configuration.\n■ Determinar if todos armazenamento units estão set to On demand apenas para um combined policy\ne schedule que does não require um specific armazenamento unidade. In this case, either\nspecify um armazenamento unidade para o policy e o schedule combination ou turn off On\ndemand apenas para um armazenamento unidade.\n■ IfthestorageunitisonaUNIXorLinuxNetBackupmediaserver,itmayindicate\num problema com bpcd. Verifique /etc/inetd.conf on o mídia servidor to verifique\nque o bpcd entry está correct.\nIf o armazenamento unidade está on um Windows NetBackup mídia servidor, verifique que o\nNetBackupClientservicewasstartedontheWindowsNetBackupmediaserver.\n■ Para detailed troubleshooting informação, aumentar o logging levels de nbrb\ne mds on o master servidor.\nUse o vxlogcfg comando como explained in o seguinte topic:\nVeja \"About unified logging\" in o NetBackup Logging Reference Guide.\nRetry o operation e verifique o resulting debug logs." + "desc": "No storage units available for use", + "first_action": "Examine the Backup Status and All Log Entries report for the appropriate time", + "full_action": "Do the following, as appropriate:\n■ Examine the Backup Status and All Log Entries report for the appropriate time\nperiod to determine the policy or schedule that received the error.\n■ Verify that the media server has not been deactivated for the storage unit or\nunits that are unavailable.\n■ Verify that the storage unit’s drives are not down.\n■ Verify the following attribute settings for all storage units:\n■ For disk storage units, the Maximum concurrent jobs is not set to 0\n■ For Media Manager storage units, the Maximum concurrent write drives\nis not set to 0\n■ Verify that the robot number and host name in the storage unit configuration\nmatches the Media and Device Management device configuration.\n■ Determine if all storage units are set to On demand only for a combined policy\nand schedule that does not require a specific storage unit. In this case, either\nspecify a storage unit for the policy and the schedule combination or turn off On\ndemand only for a storage unit.\n■ IfthestorageunitisonaUNIXorLinuxNetBackupmediaserver,itmayindicate\na problem with bpcd. Check /etc/inetd.conf on the media server to verify\nthat the bpcd entry is correct.\nIf the storage unit is on a Windows NetBackup media server, verify that the\nNetBackupClientservicewasstartedontheWindowsNetBackupmediaserver.\n■ For detailed troubleshooting information, increase the logging levels of nbrb\nand mds on the master server.\nUse the vxlogcfg command as explained in the following topic:\nSee \"About unified logging\" in the NetBackup Logging Reference Guide.\nRetry the operation and check the resulting debug logs." }, "215": { "code": 215, - "desc": "Falhou reading global config banco de dados informação", + "desc": "Failed reading global config database information", "first_action": "OnaUNIXorLinuxmasterserver,verifythattheNetBackupDatabaseManager", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ OnaUNIXorLinuxmasterserver,verifythattheNetBackupDatabaseManager\n(bpdbm) process está executando. On um Windows master servidor, verifique que o\nNetBackup Banco de dados Manager service está executando.\n■ Try to view o global configuration settings por usando o NetBackup\nadministrationinterface(onUNIXandLinuxsystems),orbyusingHostProperties\n(on Windows systems).\n■ Fordetailedtroubleshootinginformation,createdebuglogdirectoriesfornbproxy\ne bpdbm on o master servidor e retry o operation. Verifique o resulting\ndebug logs para these processos. Also verifique o nbpem logs por usando o\nvxlogview comando." + "full_action": "Do the following, as appropriate:\n■ OnaUNIXorLinuxmasterserver,verifythattheNetBackupDatabaseManager\n(bpdbm) process is running. On a Windows master server, verify that the\nNetBackup Database Manager service is running.\n■ Try to view the global configuration settings by using the NetBackup\nadministrationinterface(onUNIXandLinuxsystems),orbyusingHostProperties\n(on Windows systems).\n■ Fordetailedtroubleshootinginformation,createdebuglogdirectoriesfornbproxy\nand bpdbm on the master server and retry the operation. Check the resulting\ndebug logs for these processes. Also check the nbpem logs by using the\nvxlogview command." }, "216": { "code": 216, - "desc": "Falhou reading retention banco de dados informação", + "desc": "Failed reading retention database information", "first_action": "OnaUNIXorLinuxmasterserver,verifythattheNetBackupDatabaseManager", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ OnaUNIXorLinuxmasterserver,verifythattheNetBackupDatabaseManager\n(bpdbm) process está executando. On um Windows master servidor, verifique que o\nNetBackup Banco de dados Manager service está executando.\n■ Para detailed troubleshooting informação, create um debug log diretório para bpdbm\non o master servidor.\nAumentar o logging level para nbpem por usando o vxlogcfg comando como\ndescribed in o seguinte topic:\nVeja \"About unified logging\" in o NetBackup Logging Reference Guide.\nRetry o operation e verifique o resulting logs." + "full_action": "Do the following, as appropriate:\n■ OnaUNIXorLinuxmasterserver,verifythattheNetBackupDatabaseManager\n(bpdbm) process is running. On a Windows master server, verify that the\nNetBackup Database Manager service is running.\n■ For detailed troubleshooting information, create a debug log directory for bpdbm\non the master server.\nIncrease the logging level for nbpem by using the vxlogcfg command as\ndescribed in the following topic:\nSee \"About unified logging\" in the NetBackup Logging Reference Guide.\nRetry the operation and check the resulting logs." }, "217": { "code": 217, - "desc": "Falhou reading armazenamento unidade banco de dados informação", + "desc": "Failed reading storage unit database information", "first_action": "OnaUNIXorLinuxserver,verifythattheNetBackupDatabaseManager(bpdbm)", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ OnaUNIXorLinuxserver,verifythattheNetBackupDatabaseManager(bpdbm)\nprocess está executando. On um Windows servidor, verifique que o NetBackup Banco de dados\nManager service está executando.\n■ TrytoviewthestorageunitconfigurationbyusingtheNetBackupadministration\ninterface.\n■ Para detailed troubleshooting informação, create debug logs para nbproxy e\nbpdbm on o master servidor e retry o operation. Verifique o resulting debug\nlogs. Also verifique o nbpem logs por usando o vxlogview comando.\nGaranta que o correct master servidor está specified para o conexão." + "full_action": "Do the following, as appropriate:\n■ OnaUNIXorLinuxserver,verifythattheNetBackupDatabaseManager(bpdbm)\nprocess is running. On a Windows server, verify that the NetBackup Database\nManager service is running.\n■ TrytoviewthestorageunitconfigurationbyusingtheNetBackupadministration\ninterface.\n■ For detailed troubleshooting information, create debug logs for nbproxy and\nbpdbm on the master server and retry the operation. Check the resulting debug\nlogs. Also check the nbpem logs by using the vxlogview command.\nEnsure that the correct master server is specified for the connection." }, "218": { "code": 218, - "desc": "Falhou reading policy banco de dados informação", + "desc": "Failed reading policy database information", "first_action": "OnaUNIXorLinuxserver,verifythattheNetBackupDatabaseManager(bpdbm)", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ OnaUNIXorLinuxserver,verifythattheNetBackupDatabaseManager(bpdbm)\nprocess está executando. On um Windows servidor, verifique que o NetBackup Banco de dados\nManager service está executando.\n■ Try to view o policy configuration por usando o NetBackup administration\ninterface.\n■ Fordetailedtroubleshootinginformation,createdebuglogdirectoriesfornbproxy\ne bpdbm on o master servidor e retry o operation. Verifique o resulting\ndebug logs. Also verifique o nbpem logs por usando o vxlogview comando.\nGaranta que o correct master servidor está specified para o conexão." + "full_action": "Do the following, as appropriate:\n■ OnaUNIXorLinuxserver,verifythattheNetBackupDatabaseManager(bpdbm)\nprocess is running. On a Windows server, verify that the NetBackup Database\nManager service is running.\n■ Try to view the policy configuration by using the NetBackup administration\ninterface.\n■ Fordetailedtroubleshootinginformation,createdebuglogdirectoriesfornbproxy\nand bpdbm on the master server and retry the operation. Check the resulting\ndebug logs. Also check the nbpem logs by using the vxlogview command.\nEnsure that the correct master server is specified for the connection." }, "219": { "code": 219, - "desc": "O requerido armazenamento unidade está unavailable", - "first_action": "Verifique que o schedule specifies o correct armazenamento unidade e o armazenamento unidade", - "full_action": "Look in o Job Details window para o falhou job.\n■ Verifique que o schedule specifies o correct armazenamento unidade e o armazenamento unidade\nexists.\n■ Verifythatthefollowingdevicesarerunning:theMediaManagerdevicedaemon\n(ltid) (UNIX ou Linux servidor) ou o NetBackup Dispositivo Manager service\n(Windows servidor). Use bpps on UNIX e Linux e o Activity Monitor on\nWindows ou o Services application in o Windows Control Panel.\n■ Verifique o seguinte attribute settings:\n■ Para um disco armazenamento unidade, Maximum concurrent jobs está não set to 0.\n■ ForaMediaManagerstorageunit,theMaximumconcurrentdrivesattribute\nestá não set to 0.\n■ If o armazenamento unidade está um tape, verifique que at least one de o drives está in o UP\nstate. Use o Dispositivo Monitor.\n■ Verifique que o robot number e host in o armazenamento unidade configuration match\nwhat está specified in o Mídia e Dispositivo Management dispositivo configuration.\n■ Verifique que o master servidor can communicate com o bpcd process on o\nservidor que has o armazenamento unidade.\n■ Verifique que bpcd listens on o port para connections.\nOn um UNIX ou Linux servidor onde o armazenamento unidade está connected, if you run\nnetstat -um | grep bpcd,itshouldreturnsomethingsimilartothefollowing:\n*.bpcd *.* 0 0 0 0 LISTEN\nOn um Windows NetBackup servidor onde o armazenamento unidade está connected, run\nnetstat -um to print several lines de output. If bpcd listens, one de those lines\nestá similar to o seguinte:\nTCP myhost:bpcd 0.0.0.0:0 LISTENING\n■ Verifique o nbrb e o mds logs por usando o vxlogview comando.\n■ If o cause de o problema está não obvious, executar some de o steps in o\nseguinte procedure:\nVeja Resolvendo Rede Communication Problemas in o NetBackup\nTroubleshooting Guide." + "desc": "The required storage unit is unavailable", + "first_action": "Verify that the schedule specifies the correct storage unit and the storage unit", + "full_action": "Look in the Job Details window for the failed job.\n■ Verify that the schedule specifies the correct storage unit and the storage unit\nexists.\n■ Verifythatthefollowingdevicesarerunning:theMediaManagerdevicedaemon\n(ltid) (UNIX or Linux server) or the NetBackup Device Manager service\n(Windows server). Use bpps on UNIX and Linux and the Activity Monitor on\nWindows or the Services application in the Windows Control Panel.\n■ Verify the following attribute settings:\n■ For a disk storage unit, Maximum concurrent jobs is not set to 0.\n■ ForaMediaManagerstorageunit,theMaximumconcurrentdrivesattribute\nis not set to 0.\n■ If the storage unit is a tape, verify that at least one of the drives is in the UP\nstate. Use the Device Monitor.\n■ Verify that the robot number and host in the storage unit configuration match\nwhat is specified in the Media and Device Management device configuration.\n■ Verify that the master server can communicate with the bpcd process on the\nserver that has the storage unit.\n■ Verify that bpcd listens on the port for connections.\nOn a UNIX or Linux server where the storage unit is connected, if you run\nnetstat -a | grep bpcd,itshouldreturnsomethingsimilartothefollowing:\n*.bpcd *.* 0 0 0 0 LISTEN\nOn a Windows NetBackup server where the storage unit is connected, run\nnetstat -a to print several lines of output. If bpcd listens, one of those lines\nis similar to the following:\nTCP myhost:bpcd 0.0.0.0:0 LISTENING\n■ Check the nbrb and the mds logs by using the vxlogview command.\n■ If the cause of the problem is not obvious, perform some of the steps in the\nfollowing procedure:\nSee Resolving Network Communication Problems in the NetBackup\nTroubleshooting Guide." }, "220": { "code": 220, - "desc": "Banco de dados system erro", - "first_action": "Create um debug log diretório para bpdbm. Aumentar o", - "full_action": "Create um debug log diretório para bpdbm. Aumentar o\nlogging level para o diagnostic e debug logs para nbemm.\nUse o vxlogcfg comando como explained in o seguinte topic:\nVeja \"About unified logging\" in o NetBackup Logging Reference Guide.\nRetry o operation e verifique o resulting logs para informação." + "desc": "Database system error", + "first_action": "Create a debug log directory for bpdbm. Increase the", + "full_action": "Create a debug log directory for bpdbm. Increase the\nlogging level for the diagnostic and debug logs for nbemm.\nUse the vxlogcfg command as explained in the following topic:\nSee \"About unified logging\" in the NetBackup Logging Reference Guide.\nRetry the operation and check the resulting logs for information." }, "221": { "code": 221, "desc": "Continue", - "first_action": "Determinar o cause de o status code que follows this", - "full_action": "Determinar o cause de o status code que follows this\none." + "first_action": "Determine the cause of the status code that follows this", + "full_action": "Determine the cause of the status code that follows this\none." }, "222": { "code": 222, "desc": "Done", - "first_action": "Determinar o cause de o status code que follows this", - "full_action": "Determinar o cause de o status code que follows this\none." + "first_action": "Determine the cause of the status code that follows this", + "full_action": "Determine the cause of the status code that follows this\none." }, "223": { "code": 223, - "desc": "Um inválido entry foi encontrado", - "first_action": "Verifique que todos NetBackup software está at o same version", - "full_action": "Verifique que todos NetBackup software está at o same version\nlevel e o comando parameters estão specified correctly. If neither de these está o\nproblem,obtaindetailedtroubleshootinginformationbycreatingabpdbmdebuglog\ndiretório. Then retry o operation. Verifique o resulting debug log." + "desc": "An invalid entry was encountered", + "first_action": "Verify that all NetBackup software is at the same version", + "full_action": "Verify that all NetBackup software is at the same version\nlevel and the command parameters are specified correctly. If neither of these is the\nproblem,obtaindetailedtroubleshootinginformationbycreatingabpdbmdebuglog\ndirectory. Then retry the operation. Check the resulting debug log." }, "224": { "code": 224, - "desc": "There foi um conflicting specification", - "first_action": "Verifique que todos NetBackup software está at o same version", - "full_action": "Verifique que todos NetBackup software está at o same version\nlevel. If que está não o problema, obtain detailed troubleshooting informação por\ncreating bpdbm e admin debug log directories. Then retry o operation. Verifique\no resulting debug logs." + "desc": "There was a conflicting specification", + "first_action": "Verify that all NetBackup software is at the same version", + "full_action": "Verify that all NetBackup software is at the same version\nlevel. If that is not the problem, obtain detailed troubleshooting information by\ncreating bpdbm and admin debug log directories. Then retry the operation. Check\nthe resulting debug logs." }, "225": { "code": 225, - "desc": "Text excedido allowed length NetBackup status codes 231 NetBackup status codes", - "first_action": "Verifique que todos NetBackup software está at o same version", - "full_action": "Verifique que todos NetBackup software está at o same version\nlevel. If que está não o problema, create debug log directories para bpdbm e admin.\nThen, retry o operation e examine o resulting debug logs." + "desc": "Text exceeded allowed length NetBackup status codes 231 NetBackup status codes", + "first_action": "Verify that all NetBackup software is at the same version", + "full_action": "Verify that all NetBackup software is at the same version\nlevel. If that is not the problem, create debug log directories for bpdbm and admin.\nThen, retry the operation and examine the resulting debug logs." }, "226": { "code": 226, - "desc": "O entity already exists", - "first_action": "Correct seu request e re-execute o comando.", - "full_action": "Correct seu request e re-execute o comando." + "desc": "The entity already exists", + "first_action": "Correct your request and re-execute the command.", + "full_action": "Correct your request and re-execute the command." }, "227": { "code": 227, - "desc": "Não entity foi found", - "first_action": "Garanta que o appropriate plug-in está configurado from o web UI.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Garanta que o appropriate plug-in está configurado from o web UI.\n■ Garanta que o discovery de o asset está complete e o appropriate asset está\nvisible in o web UI." + "desc": "No entity was found", + "first_action": "Ensure that the appropriate plug-in is configured from the web UI.", + "full_action": "Do the following, as appropriate:\n■ Ensure that the appropriate plug-in is configured from the web UI.\n■ Ensure that the discovery of the asset is complete and the appropriate asset is\nvisible in the web UI." }, "228": { "code": 228, - "desc": "Não foi possível to process request", + "desc": "Unable to process request", "first_action": "Ifthisstatusinvolvesamediaserver,verifythatitsserverlistspecifiesthecorrect", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Ifthisstatusinvolvesamediaserver,verifythatitsserverlistspecifiesthecorrect\nmaster servidor. On um UNIX ou Linux servidor, o master servidor está o first Servidor\nentry in o bp.conf arquivo. On um Windows servidor, o master está designated on o\nServers tab in o Master Servidor Properties dialog box.\nVeja \"usando o Host Properties window to access configuration settings\" in o\nNetBackup Troubleshooting Guide.\n■ Para detailed troubleshooting informação, create um bpdbm debug log diretório\ne retry o operation. Then, verifique o resulting debug log." + "full_action": "Do the following, as appropriate:\n■ Ifthisstatusinvolvesamediaserver,verifythatitsserverlistspecifiesthecorrect\nmaster server. On a UNIX or Linux server, the master server is the first SERVER\nentry in the bp.conf file. On a Windows server, the master is designated on the\nServers tab in the Master Server Properties dialog box.\nSee \"Using the Host Properties window to access configuration settings\" in the\nNetBackup Troubleshooting Guide.\n■ For detailed troubleshooting information, create a bpdbm debug log directory\nand retry the operation. Then, check the resulting debug log." }, "229": { "code": 229, - "desc": "Events fora de sequence - image inconsistency", - "first_action": "Obtain detailed troubleshooting informação por creating um", - "full_action": "Obtain detailed troubleshooting informação por creating um\ndebug log diretório para bpdbm. Then, retry o operation, save o resulting debug\nlog, e contate Cohesity Technical Support." + "desc": "Events out of sequence - image inconsistency", + "first_action": "Obtain detailed troubleshooting information by creating a", + "full_action": "Obtain detailed troubleshooting information by creating a\ndebug log directory for bpdbm. Then, retry the operation, save the resulting debug\nlog, and contact Cohesity Technical Support." }, "230": { "code": 230, - "desc": "O specified policy does não exist in o configuration banco de dados", + "desc": "The specified policy does not exist in the configuration database", "first_action": "Correctyourparametersoroptionsandretrytheoperation.", "full_action": "Correctyourparametersoroptionsandretrytheoperation." }, "231": { "code": 231, "desc": "Schedule windows overlap", - "first_action": "Correct o schedule to eliminate o overlapping backup", - "full_action": "Correct o schedule to eliminate o overlapping backup\nwindows." + "first_action": "Correct the schedule to eliminate the overlapping backup", + "full_action": "Correct the schedule to eliminate the overlapping backup\nwindows." }, "232": { "code": 232, - "desc": "Um protocol erro has ocorreu", - "first_action": "Create um debug log diretório para bpdbm. Then, retry o", - "full_action": "Create um debug log diretório para bpdbm. Then, retry o\noperation, save o debug log, e contate Cohesity Technical Support." + "desc": "A protocol error has occurred", + "first_action": "Create a debug log directory for bpdbm. Then, retry the", + "full_action": "Create a debug log directory for bpdbm. Then, retry the\noperation, save the debug log, and contact Cohesity Technical Support." }, "233": { "code": 233, - "desc": "Premature eof encontrado", - "first_action": "During um restauração, this status code means que tar (on o", - "full_action": "During um restauração, this status code means que tar (on o\ncliente) received um stream de data que foi não what it expected. If o restauração está um\nnew configuration, verifique que o tape drive está configurado para variable mode.\nVeja o NetBackup Dispositivo Configuration Guide.\nIf o communication falha está não due to um interrupt on um cliente system, save todos\nerro informação e contate Cohesity Technical Support." + "desc": "Premature eof encountered", + "first_action": "During a restore, this status code means that tar (on the", + "full_action": "During a restore, this status code means that tar (on the\nclient) received a stream of data that was not what it expected. If the restore is a\nnew configuration, verify that the tape drive is configured for variable mode.\nSee the NetBackup Device Configuration Guide.\nIf the communication failure is not due to an interrupt on a client system, save all\nerror information and contact Cohesity Technical Support." }, "234": { "code": 234, "desc": "Communication interrupted", - "first_action": "Save todos de o erro informação e contate Cohesity", - "full_action": "Save todos de o erro informação e contate Cohesity\nTechnical Support." + "first_action": "Save all of the error information and contact Cohesity", + "full_action": "Save all of the error information and contact Cohesity\nTechnical Support." }, "235": { "code": 235, "desc": "Inadequate buffer space", - "first_action": "Verifique que todos NetBackup software está at o same version level. Update earlier", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Verifique que todos NetBackup software está at o same version level. Update earlier\nversions de NetBackup software.\n■ On UNIX e Linux, NetBackup servers e clients, verifique o\n/usr/openv/netbackup/bin/version arquivo.\n■ On Windows NetBackup servers, verifique o\ninstall_path\\NetBackup\\version.txtfileortheAboutNetBackupitem\non o Help menu.\n■ On Microsoft Windows clients, verifique o About NetBackup item on o\nHelp menu.\n■ Iftheproblempersists,saveallerrorinformationandcontactCohesityTechnical\nSupport." + "first_action": "Verify that all NetBackup software is at the same version level. Update earlier", + "full_action": "Do the following, as appropriate:\n■ Verify that all NetBackup software is at the same version level. Update earlier\nversions of NetBackup software.\n■ On UNIX and Linux, NetBackup servers and clients, check the\n/usr/openv/netbackup/bin/version file.\n■ On Windows NetBackup servers, check the\ninstall_path\\NetBackup\\version.txtfileortheAboutNetBackupitem\non the Help menu.\n■ On Microsoft Windows clients, check the About NetBackup item on the\nHelp menu.\n■ Iftheproblempersists,saveallerrorinformationandcontactCohesityTechnical\nSupport." }, "236": { "code": 236, - "desc": "O specified cliente does não exist in um active policy within o configuration banco de dados", - "first_action": "Activate o requerido policy, correct o cliente name, ou", - "full_action": "Activate o requerido policy, correct o cliente name, ou\nadd o cliente to um policy que meets seu needs. After you make o correction,\nretry o operation." + "desc": "The specified client does not exist in an active policy within the configuration database", + "first_action": "Activate the required policy, correct the client name, or", + "full_action": "Activate the required policy, correct the client name, or\nadd the client to a policy that meets your needs. After you make the correction,\nretry the operation." }, "237": { "code": 237, - "desc": "O specified schedule does não exist in um active policy in o configuration banco de dados NetBackup status codes 235 NetBackup status codes", - "first_action": "Activate o requerido policy, correct o schedule name,", - "full_action": "Activate o requerido policy, correct o schedule name,\nou create um schedule in um policy que meets seu needs. After you make o\ncorrection, retry o operation." + "desc": "The specified schedule does not exist in an active policy in the configuration database NetBackup status codes 235 NetBackup status codes", + "first_action": "Activate the required policy, correct the schedule name,", + "full_action": "Activate the required policy, correct the schedule name,\nor create a schedule in a policy that meets your needs. After you make the\ncorrection, retry the operation." }, "238": { "code": 238, - "desc": "O banco de dados contains conflicting ou erroneous entradas", - "first_action": "Obtain detailed troubleshooting informação para bpdbm (on", - "full_action": "Obtain detailed troubleshooting informação para bpdbm (on\nUNIX e Linux) ou o NetBackup Banco de dados Manager service (on Windows) por\ncreating um debug log diretório para it. Then, retry o operation, save o resulting\ndebug log, e contate Cohesity Technical Support." + "desc": "The database contains conflicting or erroneous entries", + "first_action": "Obtain detailed troubleshooting information for bpdbm (on", + "full_action": "Obtain detailed troubleshooting information for bpdbm (on\nUNIX and Linux) or the NetBackup Database Manager service (on Windows) by\ncreating a debug log directory for it. Then, retry the operation, save the resulting\ndebug log, and contact Cohesity Technical Support." }, "239": { "code": 239, - "desc": "O specified cliente does não exist in o specified policy", - "first_action": "Correct o cliente name specification, specify um different", - "full_action": "Correct o cliente name specification, specify um different\npolicy, ou add o requerido cliente name to o policy. After you make o correction,\nretry o operation." + "desc": "The specified client does not exist in the specified policy", + "first_action": "Correct the client name specification, specify a different", + "full_action": "Correct the client name specification, specify a different\npolicy, or add the required client name to the policy. After you make the correction,\nretry the operation." }, "240": { "code": 240, - "desc": "Não schedules de o correct type exist in this policy", - "first_action": "Specify um different policy ou create um schedule de o", - "full_action": "Specify um different policy ou create um schedule de o\nneeded type in o policy. After you make o correction, retry o operation." + "desc": "No schedules of the correct type exist in this policy", + "first_action": "Specify a different policy or create a schedule of the", + "full_action": "Specify a different policy or create a schedule of the\nneeded type in the policy. After you make the correction, retry the operation." }, "241": { "code": 241, - "desc": "O specified schedule está o wrong type para this request", - "first_action": "Specify apenas cheio ou incremental schedules para manual", - "full_action": "Specify apenas cheio ou incremental schedules para manual\nbackups. If one does não exist in o policy, create one." + "desc": "The specified schedule is the wrong type for this request", + "first_action": "Specify only full or incremental schedules for manual", + "full_action": "Specify only full or incremental schedules for manual\nbackups. If one does not exist in the policy, create one." }, "242": { "code": 242, - "desc": "Operation would cause um illegal duplication", + "desc": "Operation would cause an illegal duplication", "first_action": "Checktheerrorreportstodeterminethespecificduplication", - "full_action": "Checktheerrorreportstodeterminethespecificduplication\nque would occur. Correct o settings para o operation e retry it." + "full_action": "Checktheerrorreportstodeterminethespecificduplication\nthat would occur. Correct the settings for the operation and retry it." }, "243": { "code": 243, - "desc": "O cliente está não in o configuration", - "first_action": "Either correct o cliente name ou add o cliente to o", - "full_action": "Either correct o cliente name ou add o cliente to o\nwanted policy." + "desc": "The client is not in the configuration", + "first_action": "Either correct the client name or add the client to the", + "full_action": "Either correct the client name or add the client to the\nwanted policy." }, "245": { "code": 245, - "desc": "O specified policy está não de o correct cliente type", + "desc": "The specified policy is not of the correct client type", "first_action": "Retrytheoperationbyspecifyingapolicythatisthecorrect", - "full_action": "Retrytheoperationbyspecifyingapolicythatisthecorrect\ntype para o cliente. If such um policy does não exist, create one." + "full_action": "Retrytheoperationbyspecifyingapolicythatisthecorrect\ntype for the client. If such a policy does not exist, create one." }, "246": { "code": 246, - "desc": "Não active policies in o configuration banco de dados estão de o correct cliente type", + "desc": "No active policies in the configuration database are of the correct client type", "first_action": "Createoractivateanappropriatepolicysotheuserbackup", "full_action": "Createoractivateanappropriatepolicysotheuserbackup\nrequest can be satisfied." }, "247": { "code": 247, - "desc": "O specified policy está não active", - "first_action": "Activate o policy e retry o operation.", - "full_action": "Activate o policy e retry o operation." + "desc": "The specified policy is not active", + "first_action": "Activate the policy and retry the operation.", + "full_action": "Activate the policy and retry the operation." }, "248": { "code": 248, - "desc": "There estão não active policies in o configuration banco de dados", - "first_action": "Activate o appropriate policy e retry o operation.", - "full_action": "Activate o appropriate policy e retry o operation." + "desc": "There are no active policies in the configuration database", + "first_action": "Activate the appropriate policy and retry the operation.", + "full_action": "Activate the appropriate policy and retry the operation." }, "249": { "code": 249, - "desc": "O arquivo list está incomplete", - "first_action": "On o servidor, bptm, bpbrm, e bpdbm.", - "full_action": "First,obtainadditionalinformationbycreatingdebuglogs.\nThen try to recreate o erro. O debug logs to create estão como follows:\n■ On o servidor, bptm, bpbrm, e bpdbm.\n■ On UNIX, Linux, e Windows clients, bpbkar.\n■ On other clients, bpcd." + "desc": "The file list is incomplete", + "first_action": "On the server, bptm, bpbrm, and bpdbm.", + "full_action": "First,obtainadditionalinformationbycreatingdebuglogs.\nThen try to recreate the error. The debug logs to create are as follows:\n■ On the server, bptm, bpbrm, and bpdbm.\n■ On UNIX, Linux, and Windows clients, bpbkar.\n■ On other clients, bpcd." }, "250": { "code": 250, - "desc": "O image foi não created com TIR informação", - "first_action": "Obtain detailed troubleshooting informação por creating", - "full_action": "Obtain detailed troubleshooting informação por creating\ndebug logs para bptm ou bpdbm on o servidor. Then, retry o operation e verifique\no resulting debug logs." + "desc": "The image was not created with TIR information", + "first_action": "Obtain detailed troubleshooting information by creating", + "full_action": "Obtain detailed troubleshooting information by creating\ndebug logs for bptm or bpdbm on the server. Then, retry the operation and check\nthe resulting debug logs." }, "251": { "code": 251, - "desc": "O tir informação está zero length", - "first_action": "Verifique o policy arquivo list e o exclude e include lists", - "full_action": "Verifique o policy arquivo list e o exclude e include lists\non o cliente to verifique que o cliente has eligible arquivos para backup. Para example, this\nstatus code can appear if o exclude list on o cliente excludes todos arquivos.\nToobtaindetailedtroubleshootinginformation,createdebuglogsforbptmorbpdbm\non o servidor. Then, retry o operation e verifique o resulting debug logs." + "desc": "The tir information is zero length", + "first_action": "Check the policy file list and the exclude and include lists", + "full_action": "Check the policy file list and the exclude and include lists\non the client to verify that the client has eligible files for backup. For example, this\nstatus code can appear if the exclude list on the client excludes all files.\nToobtaindetailedtroubleshootinginformation,createdebuglogsforbptmorbpdbm\non the server. Then, retry the operation and check the resulting debug logs." }, "252": { "code": 252, - "desc": "Um extended erro status has been encontrado, verifique detailed status", - "first_action": "To determinar o actual erro, examine o job details", - "full_action": "To determinar o actual erro, examine o job details\ndisplay." + "desc": "An extended error status has been encountered, check detailed status", + "first_action": "To determine the actual error, examine the job details", + "full_action": "To determine the actual error, examine the job details\ndisplay." }, "253": { "code": 253, - "desc": "O catalog image .f arquivo has been archived", - "first_action": "Refer to o catalog archiving help informação to restauração", - "full_action": "Refer to o catalog archiving help informação to restauração\no archived catalog image .f arquivos." + "desc": "The catalog image .f file has been archived", + "first_action": "Refer to the catalog archiving help information to restore", + "full_action": "Refer to the catalog archiving help information to restore\nthe archived catalog image .f files." }, "254": { "code": 254, - "desc": "Servidor name não found in o NetBackup configuration", - "first_action": "Save todos de o erro informação e contate Cohesity", - "full_action": "Save todos de o erro informação e contate Cohesity\nTechnical Support." + "desc": "Server name not found in the NetBackup configuration", + "first_action": "Save all of the error information and contact Cohesity", + "full_action": "Save all of the error information and contact Cohesity\nTechnical Support." }, "256": { "code": 256, - "desc": "Logic erro encontrado", - "first_action": "Contate customer support e send o appropriate logs.", - "full_action": "Contate customer support e send o appropriate logs." + "desc": "Logic error encountered", + "first_action": "Contact customer support and send the appropriate logs.", + "full_action": "Contact customer support and send the appropriate logs." }, "257": { "code": 257, - "desc": "Falhou to get job data", - "first_action": "Contate customer support e send o appropriate logs.", - "full_action": "Contate customer support e send o appropriate logs." + "desc": "Failed to get job data", + "first_action": "Contact customer support and send the appropriate logs.", + "full_action": "Contact customer support and send the appropriate logs." }, "258": { "code": 258, - "desc": "Vault duplication foi aborted por administrator request", - "first_action": "Garanta que o abort request foi intentional.", - "full_action": "Garanta que o abort request foi intentional." + "desc": "Vault duplication was aborted by administrator request", + "first_action": "Ensure that the abort request was intentional.", + "full_action": "Ensure that the abort request was intentional." }, "259": { "code": 259, - "desc": "Vault configuration arquivo não found", - "first_action": "Contate customer support e send o appropriate logs.", - "full_action": "Contate customer support e send o appropriate logs." + "desc": "Vault configuration file not found", + "first_action": "Contact customer support and send the appropriate logs.", + "full_action": "Contact customer support and send the appropriate logs." }, "260": { "code": 260, - "desc": "Falhou to send signal", - "first_action": "Contate customer support e send o appropriate logs.", - "full_action": "Contate customer support e send o appropriate logs." + "desc": "Failed to send signal", + "first_action": "Contact customer support and send the appropriate logs.", + "full_action": "Contact customer support and send the appropriate logs." }, "261": { "code": 261, - "desc": "Vault internal erro 261", - "first_action": "Contate customer support e send o appropriate logs.", - "full_action": "Contate customer support e send o appropriate logs." + "desc": "Vault internal error 261", + "first_action": "Contact customer support and send the appropriate logs.", + "full_action": "Contact customer support and send the appropriate logs." }, "262": { "code": 262, - "desc": "Vault internal erro 262", - "first_action": "Contate customer support e send o appropriate logs.", - "full_action": "Contate customer support e send o appropriate logs." + "desc": "Vault internal error 262", + "first_action": "Contact customer support and send the appropriate logs.", + "full_action": "Contact customer support and send the appropriate logs." }, "263": { "code": 263, - "desc": "Session ID assignment falhou", + "desc": "Session ID assignment failed", "first_action": "VerifythatthesessionIDthatisstoredinthesession.last", - "full_action": "VerifythatthesessionIDthatisstoredinthesession.last\narquivo está valid.\nUNIX e Linux:\n/usr/openv/netbackup/vault/sessions/vault_name/session.last\nWindows:\ninstall_path\\NetBackup\\vault\\sessions\\vault_name\\session.last\nMake sure que o arquivo system está não cheio e que não one has inadvertently edited\no session.last arquivo. To correct o problema, store o highest session ID que\nfoi assigned to um session para this Vault in o session.last arquivo. If o problema\npersists, contate customer support e send o appropriate logs." + "full_action": "VerifythatthesessionIDthatisstoredinthesession.last\nfile is valid.\nUNIX and Linux:\n/usr/openv/netbackup/vault/sessions/vault_name/session.last\nWindows:\ninstall_path\\NetBackup\\vault\\sessions\\vault_name\\session.last\nMake sure that the file system is not full and that no one has inadvertently edited\nthe session.last file. To correct the problem, store the highest session ID that\nwas assigned to a session for this Vault in the session.last file. If the problem\npersists, contact customer support and send the appropriate logs." }, "265": { "code": 265, - "desc": "Session ID arquivo está vazio ou corrupt", - "first_action": "Garanta que o session ID que está stored in o", - "full_action": "Garanta que o session ID que está stored in o\nsession.last arquivo está não corrupt. Make sure que o arquivo system está não cheio e que\nnão one has inadvertently edited o arquivo. To correct o problema, store o highest\nsession ID que foi assigned to um session para this Vault in o session.last arquivo.\nIf o problema persists, contate customer support e send o appropriate logs." + "desc": "Session ID file is empty or corrupt", + "first_action": "Ensure that the session ID that is stored in the", + "full_action": "Ensure that the session ID that is stored in the\nsession.last file is not corrupt. Make sure that the file system is not full and that\nno one has inadvertently edited the file. To correct the problem, store the highest\nsession ID that was assigned to a session for this Vault in the session.last file.\nIf the problem persists, contact customer support and send the appropriate logs." }, "266": { "code": 266, - "desc": "Não é possível find robot, vault, ou profile in o vault configuration", + "desc": "Cannot find robot, vault, or profile in the vault configuration", "first_action": "Rerunthecommandwiththecorrectprofile_nameortriplet", "full_action": "Rerunthecommandwiththecorrectprofile_nameortriplet\nrobot_name/vault_name/profile_name." }, "267": { "code": 267, - "desc": "Não é possível find o local host name", + "desc": "Cannot find the local host name", "first_action": "Issuea hostnamecommandattheOScommandprompt.", - "full_action": "Issuea hostnamecommandattheOScommandprompt.\nSeethehostname(orgethostbyname)manpageforanexplanationoftheconditions\nque would cause it to fail.\nVeja o OS System Administrator’s Guide para more informação." + "full_action": "Issuea hostnamecommandattheOScommandprompt.\nSeethehostname(orgethostbyname)manpageforanexplanationoftheconditions\nthat would cause it to fail.\nSee the OS System Administrator’s Guide for more information." }, "268": { "code": 268, - "desc": "O vault session diretório está either missing ou inaccessible", - "first_action": "Make sure que you estão executando on o master servidor", - "full_action": "Make sure que you estão executando on o master servidor\nonde Vault está instalado e configurado. Also garanta que não one accidentally\nremoved o sessions diretório ou changed permissão on o diretório caminho so it\nestá inaccessible to o Vault job." + "desc": "The vault session directory is either missing or inaccessible", + "first_action": "Make sure that you are running on the master server", + "full_action": "Make sure that you are running on the master server\nwhere Vault is installed and configured. Also ensure that no one accidentally\nremoved the sessions directory or changed permission on the directory path so it\nis inaccessible to the Vault job." }, "269": { "code": 269, - "desc": "Não vault session ID foi found", + "desc": "No vault session ID was found", "first_action": "EitherspecifyadifferentprofilefortheVaultjobsthatwere", - "full_action": "EitherspecifyadifferentprofilefortheVaultjobsthatwere\nrun ou exit vltopmenu e run um Vault job para o specific profile. Then rerun\nvltopmenu e select o profile." + "full_action": "EitherspecifyadifferentprofilefortheVaultjobsthatwere\nrun or exit vltopmenu and run a Vault job for the specific profile. Then rerun\nvltopmenu and select the profile." }, "270": { "code": 270, - "desc": "Não foi possível to obtain process id, getpid falhou", - "first_action": "Look at o system log para qualquer unusual system problemas.", - "full_action": "Look at o system log para qualquer unusual system problemas.\nWait um while e then try executando o process again when system resources estão\nfreed up." + "desc": "Unable to obtain process id, getpid failed", + "first_action": "Look at the system log for any unusual system problems.", + "full_action": "Look at the system log for any unusual system problems.\nWait a while and then try running the process again when system resources are\nfreed up." }, "271": { "code": 271, "desc": "Vault XML version mismatch", - "first_action": "Enable logging, start nbvault, e then examine o", - "full_action": "Enable logging, start nbvault, e then examine o\nnbvault logs to determinar o cause de o falha. If o upgrade process fails\nagain, contate seu customer support representative.\nO seguinte estão o locations de o nbvault logs:\nUNIX e Linux: /usr/openv/netbackup/logs/nbvault/\nWindows: install_path\\NetBackup\\logs\\nbvault" + "first_action": "Enable logging, start nbvault, and then examine the", + "full_action": "Enable logging, start nbvault, and then examine the\nnbvault logs to determine the cause of the failure. If the upgrade process fails\nagain, contact your customer support representative.\nThe following are the locations of the nbvault logs:\nUNIX and Linux: /usr/openv/netbackup/logs/nbvault/\nWindows: install_path\\NetBackup\\logs\\nbvault" }, "272": { "code": 272, - "desc": "Execution de um vault notify script falhou", + "desc": "Execution of a vault notify script failed", "first_action": "Ensurethatthenotifyscriptisexecutableandrunswithout", - "full_action": "Ensurethatthenotifyscriptisexecutableandrunswithout\nerrors. You must debug o script por executando it manually to eliminate coding errors." + "full_action": "Ensurethatthenotifyscriptisexecutableandrunswithout\nerrors. You must debug the script by running it manually to eliminate coding errors." }, "273": { "code": 273, - "desc": "Inválido job id", - "first_action": "Specify o job ID de o active Vault job que está currently", - "full_action": "Specify o job ID de o active Vault job que está currently\nat o duplication step ou operation." + "desc": "Invalid job id", + "first_action": "Specify the job ID of the active Vault job that is currently", + "full_action": "Specify the job ID of the active Vault job that is currently\nat the duplication step or operation." }, "274": { "code": 274, - "desc": "Não profile foi specified", - "first_action": "Contate customer support e send o appropriate logs.", - "full_action": "Contate customer support e send o appropriate logs." + "desc": "No profile was specified", + "first_action": "Contact customer support and send the appropriate logs.", + "full_action": "Contact customer support and send the appropriate logs." }, "275": { "code": 275, - "desc": "Um session está already executando para this vault", - "first_action": "Start o Vault session after o previous session has", - "full_action": "Start o Vault session after o previous session has\ncompleted." + "desc": "A session is already running for this vault", + "first_action": "Start the Vault session after the previous session has", + "full_action": "Start the Vault session after the previous session has\ncompleted." }, "276": { "code": 276, - "desc": "Inválido session ID", - "first_action": "Contate customer support e send o appropriate logs.", - "full_action": "Contate customer support e send o appropriate logs." + "desc": "Invalid session ID", + "first_action": "Contact customer support and send the appropriate logs.", + "full_action": "Contact customer support and send the appropriate logs." }, "277": { "code": 277, - "desc": "Não foi possível to print relatórios", - "first_action": "Contate customer support e send o appropriate logs.", - "full_action": "Contate customer support e send o appropriate logs." + "desc": "Unable to print reports", + "first_action": "Contact customer support and send the appropriate logs.", + "full_action": "Contact customer support and send the appropriate logs." }, "278": { "code": 278, - "desc": "Não foi possível to collect pre eject informação from o API", - "first_action": "Garanta que todos Mídia e Dispositivo Management daemons", - "full_action": "Garanta que todos Mídia e Dispositivo Management daemons\nestão executando ou o robot está live e up." + "desc": "Unable to collect pre eject information from the API", + "first_action": "Ensure that all Media and Device Management daemons", + "full_action": "Ensure that all Media and Device Management daemons\nare running or the robot is live and up." }, "279": { "code": 279, - "desc": "Eject process está complete", - "first_action": "Nenhum", - "full_action": "Nenhum" + "desc": "Eject process is complete", + "first_action": "None", + "full_action": "None" }, "280": { "code": 280, - "desc": "There estão não volumes to eject", + "desc": "There are no volumes to eject", "first_action": "Ensurethatthemediatobeejectedarenotremovedfrom", - "full_action": "Ensurethatthemediatobeejectedarenotremovedfrom\no library manually." + "full_action": "Ensurethatthemediatobeejectedarenotremovedfrom\nthe library manually." }, "281": { "code": 281, - "desc": "Vault core erro", - "first_action": "Contate customer support e send o appropriate logs.", - "full_action": "Contate customer support e send o appropriate logs." + "desc": "Vault core error", + "first_action": "Contact customer support and send the appropriate logs.", + "full_action": "Contact customer support and send the appropriate logs." }, "282": { "code": 282, - "desc": "Não é possível conectar to nbvault servidor", - "first_action": "To determinar o reason para falha, examine o logs para", - "full_action": "To determinar o reason para falha, examine o logs para\no service ou services que estão down e o operating system logs (EventLog on\nWindows).Restarttheserviceorservicesthataredownafterresolvingtheproblem.\nO seguinte estão o locations de o nbvault logs:\nUNIX e Linux: /usr/openv/netbackup/logs/nbvault/\nWindows: install_path\\NetBackup\\logs\\nbvault" + "desc": "Cannot connect to nbvault server", + "first_action": "To determine the reason for failure, examine the logs for", + "full_action": "To determine the reason for failure, examine the logs for\nthe service or services that are down and the operating system logs (EventLog on\nWindows).Restarttheserviceorservicesthataredownafterresolvingtheproblem.\nThe following are the locations of the nbvault logs:\nUNIX and Linux: /usr/openv/netbackup/logs/nbvault/\nWindows: install_path\\NetBackup\\logs\\nbvault" }, "283": { "code": 283, - "desc": "Error(s) ocorreu during vault relatório generation", - "first_action": "Verifique logs para details de o falha.", - "full_action": "Verifique logs para details de o falha." + "desc": "Error(s) occurred during vault report generation", + "first_action": "Check logs for details of the failure.", + "full_action": "Check logs for details of the failure." }, "284": { "code": 284, - "desc": "Error(s) ocorreu during vault relatório distribution", - "first_action": "Verifique logs para details de o falha.", - "full_action": "Verifique logs para details de o falha." + "desc": "Error(s) occurred during vault report distribution", + "first_action": "Check logs for details of the failure.", + "full_action": "Check logs for details of the failure." }, "285": { "code": 285, - "desc": "Não foi possível to locate vault diretório", - "first_action": "O Vault diretório está created when o Vault package", - "full_action": "O Vault diretório está created when o Vault package\nestá instalado on o master servidor. Garanta que o Vault job ou comando está started\ncomo raiz on o master servidor. Garanta que o Vault diretório foi não removed\ninadvertently ou made inaccessible to o raiz usuário." + "desc": "Unable to locate vault directory", + "first_action": "The Vault directory is created when the Vault package", + "full_action": "The Vault directory is created when the Vault package\nis installed on the master server. Ensure that the Vault job or command is started\nas root on the master server. Ensure that the Vault directory was not removed\ninadvertently or made inaccessible to the root user." }, "286": { "code": 286, - "desc": "Vault internal erro", - "first_action": "Contate customer support e send o appropriate logs.", - "full_action": "Contate customer support e send o appropriate logs." + "desc": "Vault internal error", + "first_action": "Contact customer support and send the appropriate logs.", + "full_action": "Contact customer support and send the appropriate logs." }, "287": { "code": 287, - "desc": "Vault eject falhou", - "first_action": "Garanta que o Mídia e Dispositivo Management services", - "full_action": "Garanta que o Mídia e Dispositivo Management services\nestão executando, o robot está up, e vazio slots estão disponível in o mídia access port\n(MAP)." + "desc": "Vault eject failed", + "first_action": "Ensure that the Media and Device Management services", + "full_action": "Ensure that the Media and Device Management services\nare running, the robot is up, and empty slots are available in the media access port\n(MAP)." }, "288": { "code": 288, "desc": "Vault eject partially succeeded", - "first_action": "Garanta que o mídia estão não loaded in um drive e in", - "full_action": "Garanta que o mídia estão não loaded in um drive e in\nuse por other processos. Garanta que vazio slots estão disponível in o mídia access\nport (MAP)." + "first_action": "Ensure that the media are not loaded in a drive and in", + "full_action": "Ensure that the media are not loaded in a drive and in\nuse by other processes. Ensure that empty slots are available in the media access\nport (MAP)." }, "289": { "code": 289, - "desc": "Não é possível consolidate relatórios de sessions from container e slot-based vaults", - "first_action": "Change o relatório consolidation so que apenas relatórios para", - "full_action": "Change o relatório consolidation so que apenas relatórios para\none type de vault operation estão consolidated, either slots ou containers." + "desc": "Cannot consolidate reports of sessions from container and slot-based vaults", + "first_action": "Change the report consolidation so that only reports for", + "full_action": "Change the report consolidation so that only reports for\none type of vault operation are consolidated, either slots or containers." }, "290": { "code": 290, - "desc": "One ou more errors detected during eject processing", - "first_action": "Manually remove qualquer mídia que estão in o off-site Vault volume group but estão", - "full_action": "Para detailed informação, review o Vault debug log in\no seguinte diretório:\nUNIX e Linux: /usr/openv/netbackup/logs/vault\nWindows: install_path\\NetBackup\\logs\\vault\nAlso review o summary.log in each de o sidxxx directories que had problemas:\nUNIX e Linux: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx\nWindows: install_path\\NetBackup\\vault\\sessions\\vault_name\\sidxxx\n(onde xxx está o session ID)\nAfter o problema está identified e corrected, o mídia que foram não ejected may\nneed to be ejected manually por means de vlteject ou vltopmenu.\nThis erro often indicates que o mídia foram left in o off-site Vault volume group\nbut physically residir in o robot ou o robotic MAP.\nTo solve this problema, do one de o seguinte:\n■ Manually remove qualquer mídia que estão in o off-site Vault volume group but estão\nstill in o robotic library.\n■ Inventorytheroboticlibrary.Aninventoryputsanymediathatwereintheoff-site\nVault volume group back into o robotic volume group. Then rerun o Vault\nsessions que falhou." + "desc": "One or more errors detected during eject processing", + "first_action": "Manually remove any media that are in the off-site Vault volume group but are", + "full_action": "For detailed information, review the Vault debug log in\nthe following directory:\nUNIX and Linux: /usr/openv/netbackup/logs/vault\nWindows: install_path\\NetBackup\\logs\\vault\nAlso review the summary.log in each of the sidxxx directories that had problems:\nUNIX and Linux: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx\nWindows: install_path\\NetBackup\\vault\\sessions\\vault_name\\sidxxx\n(where xxx is the session ID)\nAfter the problem is identified and corrected, the media that were not ejected may\nneed to be ejected manually by means of vlteject or vltopmenu.\nThis error often indicates that the media were left in the off-site Vault volume group\nbut physically reside in the robot or the robotic MAP.\nTo solve this problem, do one of the following:\n■ Manually remove any media that are in the off-site Vault volume group but are\nstill in the robotic library.\n■ Inventorytheroboticlibrary.Aninventoryputsanymediathatwereintheoff-site\nVault volume group back into the robotic volume group. Then rerun the Vault\nsessions that failed." }, "291": { "code": 291, - "desc": "Number de mídia has excedido capacity de MAP; must executar manual eject usando vltopmenu ou vlteject", + "desc": "Number of media has exceeded capacity of MAP; must perform manual eject using vltopmenu or vlteject", "first_action": "Usevltopmenutomanuallyejectthemediafortheselected", - "full_action": "Usevltopmenutomanuallyejectthemediafortheselected\nprofile e session ID. O vltopmenu option lets you eject o selected mídia, um\nMAP-full (ou less) at um time." + "full_action": "Usevltopmenutomanuallyejectthemediafortheselected\nprofile and session ID. The vltopmenu option lets you eject the selected media, a\nMAP-full (or less) at a time." }, "292": { "code": 292, - "desc": "Eject process falhou to start", - "first_action": "Para detailed informação about o problema, review o", - "full_action": "Para detailed informação about o problema, review o\nVault debug log in o seguinte diretório:\nUNIX e Linux: /usr/openv/netbackup/logs/vault\nWindows: install_path\\NetBackup\\logs\\vault\nAlso review o summary.log in each de o sidxxx directories que had problemas:\nUNIX e Linux: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx\nWindows:install_path\\NetBackup\\vault\\sessions\\vault_name\\sidxxx\n(onde xxx está o session ID)\nUse o robtest utility to garanta que you can communicate com o Vault robotic\nlibrary. After o problema está resolved, rerun o Vault session, vlteject comando,\nou vltopmenu comando." + "desc": "Eject process failed to start", + "first_action": "For detailed information about the problem, review the", + "full_action": "For detailed information about the problem, review the\nVault debug log in the following directory:\nUNIX and Linux: /usr/openv/netbackup/logs/vault\nWindows: install_path\\NetBackup\\logs\\vault\nAlso review the summary.log in each of the sidxxx directories that had problems:\nUNIX and Linux: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx\nWindows:install_path\\NetBackup\\vault\\sessions\\vault_name\\sidxxx\n(where xxx is the session ID)\nUse the robtest utility to ensure that you can communicate with the Vault robotic\nlibrary. After the problem is resolved, rerun the Vault session, vlteject command,\nor vltopmenu command." }, "293": { "code": 293, "desc": "Eject process has been aborted", - "first_action": "Manually remove qualquer mídia que estão in o off-site Vault volume group but estão", - "full_action": "Para detailed informação about por que o process foi\ncanceled, review o Vault debug log in o seguinte diretório:\nUNIX e Linux: /usr/openv/netbackup/logs/vault\nWindows: install_path\\NetBackup\\logs\\vault\nAlso review o summary.log in each de o sidxxx directories que had problemas:\nUNIX e Linux:\n/usr/openv/netbackup/vault/sessions/vault_name/sidxxx\nWindows:\ninstall_path\\NetBackup\\vault\\sessions\\vault_name\\sidxxx\n(onde xxx está o session ID)\nThis erro often indicates que o mídia foram left in o off-site Vault volume group\nbut physically residir in o robot ou o robotic MAP.\nTo solve this problema, do one de o seguinte:\n■ Manually remove qualquer mídia que estão in o off-site Vault volume group but estão\nstill in o robotic library.\n■ Inventorytheroboticlibrary.Aninventoryputsanymediathatwereintheoff-site\nVault volume group back into o robotic volume group. Then, rerun o Vault\nsessions que falhou." + "first_action": "Manually remove any media that are in the off-site Vault volume group but are", + "full_action": "For detailed information about why the process was\ncanceled, review the Vault debug log in the following directory:\nUNIX and Linux: /usr/openv/netbackup/logs/vault\nWindows: install_path\\NetBackup\\logs\\vault\nAlso review the summary.log in each of the sidxxx directories that had problems:\nUNIX and Linux:\n/usr/openv/netbackup/vault/sessions/vault_name/sidxxx\nWindows:\ninstall_path\\NetBackup\\vault\\sessions\\vault_name\\sidxxx\n(where xxx is the session ID)\nThis error often indicates that the media were left in the off-site Vault volume group\nbut physically reside in the robot or the robotic MAP.\nTo solve this problem, do one of the following:\n■ Manually remove any media that are in the off-site Vault volume group but are\nstill in the robotic library.\n■ Inventorytheroboticlibrary.Aninventoryputsanymediathatwereintheoff-site\nVault volume group back into the robotic volume group. Then, rerun the Vault\nsessions that failed." }, "294": { "code": 294, - "desc": "Vault catalog backup falhou", - "first_action": "Review o Vault debug log in o seguinte diretório para", - "full_action": "Review o Vault debug log in o seguinte diretório para\ndetailed informação about por que o process falhou:\nUNIX e Linux: /usr/openv/netbackup/logs/vault\nWindows: install_path\\NetBackup\\logs\\vault\nTo find o actual problema que caused o catalog backup (bpbackupdb) to fail,\nreview o summary.log in each de o sidxxx directories que had problemas:\nUNIX e Linux: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx\nWindows: install_path\\NetBackup\\vault\\sessions\\vault_name\\sidxxx\n(onde xxx está o session ID)\nCorrect o problema e rerun o Vault job." + "desc": "Vault catalog backup failed", + "first_action": "Review the Vault debug log in the following directory for", + "full_action": "Review the Vault debug log in the following directory for\ndetailed information about why the process failed:\nUNIX and Linux: /usr/openv/netbackup/logs/vault\nWindows: install_path\\NetBackup\\logs\\vault\nTo find the actual problem that caused the catalog backup (bpbackupdb) to fail,\nreview the summary.log in each of the sidxxx directories that had problems:\nUNIX and Linux: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx\nWindows: install_path\\NetBackup\\vault\\sessions\\vault_name\\sidxxx\n(where xxx is the session ID)\nCorrect the problem and rerun the Vault job." }, "295": { "code": 295, - "desc": "Eject process could não obtain informação about o robot", + "desc": "Eject process could not obtain information about the robot", "first_action": "Fordetailedinformationaboutwhytheprocessfails,review", - "full_action": "Fordetailedinformationaboutwhytheprocessfails,review\no Vault debug log in o seguinte diretório:\nUNIX e Linux: /usr/openv/netbackup/logs/vault\nWindows: install_path\\NetBackup\\logs\\vault\nAlso review o summary.log in each de o sidxxx directories que had problemas:\nUNIX e Linux: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx\nWindows: install_path\\NetBackup\\vault\\sessions\\vault_name\\sidxxx\n(onde xxx está o session ID)\nCorrect o erro e rerun o Vault session, vlteject comando, ou vltopmenu\neject comando." + "full_action": "Fordetailedinformationaboutwhytheprocessfails,review\nthe Vault debug log in the following directory:\nUNIX and Linux: /usr/openv/netbackup/logs/vault\nWindows: install_path\\NetBackup\\logs\\vault\nAlso review the summary.log in each of the sidxxx directories that had problems:\nUNIX and Linux: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx\nWindows: install_path\\NetBackup\\vault\\sessions\\vault_name\\sidxxx\n(where xxx is the session ID)\nCorrect the error and rerun the Vault session, vlteject command, or vltopmenu\neject command." }, "296": { "code": 296, "desc": "Process called but nothing to do", - "first_action": "This erro está um informative one e does não require qualquer", - "full_action": "This erro está um informative one e does não require qualquer\nação." + "first_action": "This error is an informative one and does not require any", + "full_action": "This error is an informative one and does not require any\naction." }, "297": { "code": 297, - "desc": "Todos volumes estão não disponível to eject", - "first_action": "Remove ou correct o defective mídia ID from o", - "full_action": "Remove ou correct o defective mídia ID from o\nvlt_ejectlist_notify script e rerun o Vault session. If o bad mídia ID está\nin o MAP ou um drive ou in transit, something está misconfigured." + "desc": "All volumes are not available to eject", + "first_action": "Remove or correct the defective media ID from the", + "full_action": "Remove or correct the defective media ID from the\nvlt_ejectlist_notify script and rerun the Vault session. If the bad media ID is\nin the MAP or a drive or in transit, something is misconfigured." }, "298": { "code": 298, - "desc": "O library está não ready to eject volumes", - "first_action": "Wait until o robotic library can support o eject ação", - "full_action": "Wait until o robotic library can support o eject ação\ne rerun o Vault session, vlteject comando, ou vltopmenu comando." + "desc": "The library is not ready to eject volumes", + "first_action": "Wait until the robotic library can support the eject action", + "full_action": "Wait until the robotic library can support the eject action\nand rerun the Vault session, vlteject command, or vltopmenu command." }, "299": { "code": 299, - "desc": "There está não disponível MAP para ejecting", - "first_action": "Wait until o robotic library’s MAP está disponível para use", - "full_action": "Wait until o robotic library’s MAP está disponível para use\ne rerun o Vault session, vlteject comando, ou vltopmenu comando." + "desc": "There is no available MAP for ejecting", + "first_action": "Wait until the robotic library’s MAP is available for use", + "full_action": "Wait until the robotic library’s MAP is available for use\nand rerun the Vault session, vlteject command, or vltopmenu command." }, "300": { "code": 300, - "desc": "Vmchange eject verifique não responding", - "first_action": "Review o Vault debug log in o seguinte diretório para detailed informação", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Review o Vault debug log in o seguinte diretório para detailed informação\nabout por que o process falhou:\nUNIX: /usr/openv/netbackup/logs/vault\nWindows: install_path\\NetBackup\\logs\\vault\n■ Alsoreviewthesummary.logineachofthesidxxxdirectoriesthathadproblems:\nUNIX:/usr/openv/netbackup/vault/sessions/vault_name/sidxxx\nWindows:install_path\\NetBackup\\vault\\sessions\\vault_name\\sidxxx\n(onde xxx está o session ID)\nThis erro often indicates que o mídia foram left in o off-site Vault volume\ngroupbutphysicallyresideintherobotortheroboticMAP.Tosolvethisproblem,\ndo one de o seguinte:\n■ Manually remove qualquer mídia que estão in o off-site Vault volume group but estão\nstill in o robot.\n■ Inventory o robot. Um inventory puts qualquer mídia que foram in o off-site Vault\nvolumegroupbackintotheroboticvolumegroup.Then,reruntheVaultsessions\nque falhou." + "desc": "Vmchange eject verify not responding", + "first_action": "Review the Vault debug log in the following directory for detailed information", + "full_action": "Do the following, as appropriate:\n■ Review the Vault debug log in the following directory for detailed information\nabout why the process failed:\nUNIX: /usr/openv/netbackup/logs/vault\nWindows: install_path\\NetBackup\\logs\\vault\n■ Alsoreviewthesummary.logineachofthesidxxxdirectoriesthathadproblems:\nUNIX:/usr/openv/netbackup/vault/sessions/vault_name/sidxxx\nWindows:install_path\\NetBackup\\vault\\sessions\\vault_name\\sidxxx\n(where xxx is the session ID)\nThis error often indicates that the media were left in the off-site Vault volume\ngroupbutphysicallyresideintherobotortheroboticMAP.Tosolvethisproblem,\ndo one of the following:\n■ Manually remove any media that are in the off-site Vault volume group but are\nstill in the robot.\n■ Inventory the robot. An inventory puts any media that were in the off-site Vault\nvolumegroupbackintotheroboticvolumegroup.Then,reruntheVaultsessions\nthat failed." }, "301": { "code": 301, - "desc": "Vmchange api_eject comando falhou", - "first_action": "Review o Vault debug log in o seguinte diretório para", - "full_action": "Review o Vault debug log in o seguinte diretório para\ndetailed informação about por que o process falhou:\nUNIX: /usr/openv/netbackup/logs/vault\nWindows: install_path\\NetBackup\\logs\\vault\nAlso review o summary.log in each de o sidxxx directories que had problemas:\nUNIX: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx\nWindows: install_path\\NetBackup\\vault\\sessions\\vault_name\\sidxxx\n(onde xxx está o session ID)\nWhen o problema está resolved, rerun o Vault session, vlteject comando, ou\nvltopmenu comando." + "desc": "Vmchange api_eject command failed", + "first_action": "Review the Vault debug log in the following directory for", + "full_action": "Review the Vault debug log in the following directory for\ndetailed information about why the process failed:\nUNIX: /usr/openv/netbackup/logs/vault\nWindows: install_path\\NetBackup\\logs\\vault\nAlso review the summary.log in each of the sidxxx directories that had problems:\nUNIX: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx\nWindows: install_path\\NetBackup\\vault\\sessions\\vault_name\\sidxxx\n(where xxx is the session ID)\nWhen the problem is resolved, rerun the Vault session, vlteject command, or\nvltopmenu command." }, "302": { "code": 302, "desc": "Errorencounteredtryingbackupofcatalog(multipletapecatalogbackup)", - "first_action": "Para o actual erro que caused o falha, review o", - "full_action": "Para o actual erro que caused o falha, review o\nVault debug log in o seguinte diretório:\nUNIX: /usr/openv/netbackup/logs/vault\nWindows: install_path\\NetBackup\\logs\\vault\nReview o summary.log in each de o sidxxx directories que had problemas:\nUNIX: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx\nWindows: install_path\\NetBackup\\vault\\sessions\\vault_name\\sidxxx\n(onde xxx está o session ID)\nIn addition, review o admin debug log in o seguinte diretório:\nUNIX: /usr/openv/netbackup/logs/admin\nWindows: install_path\\NetBackup\\logs\\admin\nCorrect o erro e rerun o Vault session." + "first_action": "For the actual error that caused the failure, review the", + "full_action": "For the actual error that caused the failure, review the\nVault debug log in the following directory:\nUNIX: /usr/openv/netbackup/logs/vault\nWindows: install_path\\NetBackup\\logs\\vault\nReview the summary.log in each of the sidxxx directories that had problems:\nUNIX: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx\nWindows: install_path\\NetBackup\\vault\\sessions\\vault_name\\sidxxx\n(where xxx is the session ID)\nIn addition, review the admin debug log in the following directory:\nUNIX: /usr/openv/netbackup/logs/admin\nWindows: install_path\\NetBackup\\logs\\admin\nCorrect the error and rerun the Vault session." }, "303": { "code": 303, - "desc": "Erro encontrado executing Mídia Manager comando", - "first_action": "Para o actual erro que caused o comando to fail,", - "full_action": "Para o actual erro que caused o comando to fail,\nreview o Vault debug log in o seguinte diretório:\nUNIX: /usr/openv/netbackup/logs/vault\nWindows: install_path\\NetBackup\\logs\\vault\nAlso review o summary.log in each de o sidxxx directories que had problemas:\nUNIX: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx\nWindows: install_path\\NetBackup\\vault\\sessions\\vault_name\\sidxxx\n(onde xxx está o session ID)\nTry executando o comando (com o same arguments como in o log arquivo) to veja o\nactualerror.EnsurethattheMediaandDeviceManagementdaemonsarerunning.\nAlso garanta que o robot está functional e you can communicate com it (para\nexample, inventory o robot through o GUI)." + "desc": "Error encountered executing Media Manager command", + "first_action": "For the actual error that caused the command to fail,", + "full_action": "For the actual error that caused the command to fail,\nreview the Vault debug log in the following directory:\nUNIX: /usr/openv/netbackup/logs/vault\nWindows: install_path\\NetBackup\\logs\\vault\nAlso review the summary.log in each of the sidxxx directories that had problems:\nUNIX: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx\nWindows: install_path\\NetBackup\\vault\\sessions\\vault_name\\sidxxx\n(where xxx is the session ID)\nTry running the command (with the same arguments as in the log file) to see the\nactualerror.EnsurethattheMediaandDeviceManagementdaemonsarerunning.\nAlso ensure that the robot is functional and you can communicate with it (for\nexample, inventory the robot through the GUI)." }, "304": { "code": 304, - "desc": "Specified profile não found", - "first_action": "Rerun o Vault comando com um profile name que está", - "full_action": "Rerun o Vault comando com um profile name que está\ndefined in o Vault configuration." + "desc": "Specified profile not found", + "first_action": "Rerun the Vault command with a profile name that is", + "full_action": "Rerun the Vault command with a profile name that is\ndefined in the Vault configuration." }, "305": { "code": 305, "desc": "Multiple profiles exist", - "first_action": "Rerun o Vault comando com o triplet", - "full_action": "Rerun o Vault comando com o triplet\nrobot_name/vault_name/profile_name. O triplet uniquely identifies o profile in\nseu Vault configuration." + "first_action": "Rerun the Vault command with the triplet", + "full_action": "Rerun the Vault command with the triplet\nrobot_name/vault_name/profile_name. The triplet uniquely identifies the profile in\nyour Vault configuration." }, "306": { "code": 306, "desc": "Vault duplication partially succeeded", - "first_action": "Verifique o Vault logs in o vault diretório e o", - "full_action": "Verifique o Vault logs in o vault diretório e o\nbpduplicate logs in o admin diretório para o cause de o falha. These log\ndirectories estão located at /usr/openv/netbackup/logs on UNIX e\ninstalled-dir\\NetBackup\\logs\\ on Windows." + "first_action": "Check the Vault logs in the vault directory and the", + "full_action": "Check the Vault logs in the vault directory and the\nbpduplicate logs in the admin directory for the cause of the failure. These log\ndirectories are located at /usr/openv/netbackup/logs on UNIX and\ninstalled-dir\\NetBackup\\logs\\ on Windows." }, "307": { "code": 307, - "desc": "Eject process has already been run para o solicitado Vault session", - "first_action": "Rerun vlteject para another session ID para which mídia", - "full_action": "Rerun vlteject para another session ID para which mídia\nhas não been ejected." + "desc": "Eject process has already been run for the requested Vault session", + "first_action": "Rerun vlteject for another session ID for which media", + "full_action": "Rerun vlteject for another session ID for which media\nhas not been ejected." }, "308": { "code": 308, - "desc": "Não images duplicated", - "first_action": "Para more informação, review o Vault debug log in o", - "full_action": "Para more informação, review o Vault debug log in o\nseguinte diretório:\nUNIX: /usr/openv/netbackup/logs/vault\nWindows: install_path\\NetBackup\\logs\\vault\nAlso review o summary.log in each de o sidxxx directories que had problemas:\nUNIX: /usr/openv/netbackup/vault/sessions/sidxxx\nWindows: install_path\\NetBackup\\vault\\sessions\\vault_name\\sidxxx\n(onde vault_name está o name de o vault, e xxx está o session ID)\nLook para o log entry que gives o total number de images processed. Um common\ncause de falha está um lack de resources, such como não more mídia disponível in o\nspecified pools para duplication. Correct o problema e rerun o Vault job. Note\nque o NetBackup scheduler retries um Vault job que terminates com this erro.\nReview o admin debug log para duplicate entradas e o bptm debug log." + "desc": "No images duplicated", + "first_action": "For more information, review the Vault debug log in the", + "full_action": "For more information, review the Vault debug log in the\nfollowing directory:\nUNIX: /usr/openv/netbackup/logs/vault\nWindows: install_path\\NetBackup\\logs\\vault\nAlso review the summary.log in each of the sidxxx directories that had problems:\nUNIX: /usr/openv/netbackup/vault/sessions/sidxxx\nWindows: install_path\\NetBackup\\vault\\sessions\\vault_name\\sidxxx\n(where vault_name is the name of the vault, and xxx is the session ID)\nLook for the log entry that gives the total number of images processed. A common\ncause of failure is a lack of resources, such as no more media available in the\nspecified pools for duplication. Correct the problem and rerun the Vault job. Note\nthat the NetBackup scheduler retries a Vault job that terminates with this error.\nReview the admin debug log for duplicate entries and the bptm debug log." }, "309": { "code": 309, - "desc": "Relatório solicitado without eject being run", - "first_action": "Rerun vlteject ou vltopmenu to eject o mídia para o session before you", - "full_action": "Executar one de these actions:\n■ Rerun vlteject ou vltopmenu to eject o mídia para o session before you\ngenerate o relatórios.\n■ Reconfigure o profile to allow o eject step to be performed when o next\nVault session para this profile runs.\n■ Disable o relatório generation in o profile para o relatórios que require mídia to\nbe ejected." + "desc": "Report requested without eject being run", + "first_action": "Rerun vlteject or vltopmenu to eject the media for the session before you", + "full_action": "Perform one of these actions:\n■ Rerun vlteject or vltopmenu to eject the media for the session before you\ngenerate the reports.\n■ Reconfigure the profile to allow the eject step to be performed when the next\nVault session for this profile runs.\n■ Disable the report generation in the profile for the reports that require media to\nbe ejected." }, "310": { "code": 310, - "desc": "Updating de Mídia Manager banco de dados falhou", - "first_action": "To find o raiz cause de o erro, review o Vault debug", - "full_action": "To find o raiz cause de o erro, review o Vault debug\nlogs in o seguinte diretório:\nUNIX: /usr/openv/netbackup/logs/vault\nWindows: install_path\\NetBackup\\logs\\vault\nTo fix o issue may involve making configuration changes." + "desc": "Updating of Media Manager database failed", + "first_action": "To find the root cause of the error, review the Vault debug", + "full_action": "To find the root cause of the error, review the Vault debug\nlogs in the following directory:\nUNIX: /usr/openv/netbackup/logs/vault\nWindows: install_path\\NetBackup\\logs\\vault\nTo fix the issue may involve making configuration changes." }, "311": { "code": 311, - "desc": "Iron Mountain Relatório está already created para this session", - "first_action": "Nenhum. This relatório não é possível be generated again.", - "full_action": "Nenhum. This relatório não é possível be generated again." + "desc": "Iron Mountain Report is already created for this session", + "first_action": "None. This report cannot be generated again.", + "full_action": "None. This report cannot be generated again." }, "312": { "code": 312, - "desc": "Inválido container banco de dados entry", + "desc": "Invalid container database entry", "first_action": "Togetthelinenumberofaninvalidrecordinthecontainer", - "full_action": "Togetthelinenumberofaninvalidrecordinthecontainer\nbanco de dados, ler o log arquivo under o diretório netbackup/logs/vault. Be aware\nque um Vault log may não exist unless o diretório netbackup/logs/vault existed\nbefore o erro ocorreu. Abrir o container banco de dados arquivo cntrDB e correct que\ninválido entry. Note que this erro occurs every time Vault reads this entry in cntrDB\nuntil either this inválido entry está deleted ou it está corrected." + "full_action": "Togetthelinenumberofaninvalidrecordinthecontainer\ndatabase, read the log file under the directory netbackup/logs/vault. Be aware\nthat a Vault log may not exist unless the directory netbackup/logs/vault existed\nbefore the error occurred. Open the container database file cntrDB and correct that\ninvalid entry. Note that this error occurs every time Vault reads this entry in cntrDB\nuntil either this invalid entry is deleted or it is corrected." }, "313": { "code": 313, - "desc": "Container does não exist in container banco de dados", + "desc": "Container does not exist in container database", "first_action": "Verifythatyouputsomemediaintothiscontainerbyusing", - "full_action": "Verifythatyouputsomemediaintothiscontainerbyusing\no vltcontainers comando. Verifique que you did não excluir it por usando o\nvltcontainers -excluir comando." + "full_action": "Verifythatyouputsomemediaintothiscontainerbyusing\nthe vltcontainers command. Verify that you did not delete it by using the\nvltcontainers -delete command." }, "314": { "code": 314, - "desc": "Container banco de dados truncate operation falhou", + "desc": "Container database truncate operation failed", "first_action": "Seethelogfileunderthedirectorynetbackup/logs/vault", - "full_action": "Seethelogfileunderthedirectorynetbackup/logs/vault\npara more details. Be aware que um log arquivo está não created unless o\nnetbackup/logs/vault diretório has already been created." + "full_action": "Seethelogfileunderthedirectorynetbackup/logs/vault\nfor more details. Be aware that a log file is not created unless the\nnetbackup/logs/vault directory has already been created." }, "315": { "code": 315, - "desc": "Falhou appending to container banco de dados", - "first_action": "Ler o relevant log arquivo under o diretório", - "full_action": "Ler o relevant log arquivo under o diretório\ninstall_path/netbackup/logs/vault para more details. Be aware que if this\ndiretório does não already exist, um log arquivo está não created." + "desc": "Failed appending to container database", + "first_action": "Read the relevant log file under the directory", + "full_action": "Read the relevant log file under the directory\ninstall_path/netbackup/logs/vault for more details. Be aware that if this\ndirectory does not already exist, a log file is not created." }, "316": { "code": 316, - "desc": "Container_id está não unique in container banco de dados", - "first_action": "Verifique que you have specified o correct container ID.", - "full_action": "Verifique que you have specified o correct container ID." + "desc": "Container_id is not unique in container database", + "first_action": "Verify that you have specified the correct container ID.", + "full_action": "Verify that you have specified the correct container ID." }, "317": { "code": 317, - "desc": "Container banco de dados fechar operation falhou", - "first_action": "Ler o relevant log arquivo under o diretório", - "full_action": "Ler o relevant log arquivo under o diretório\nnetbackup/logs/vault para more details. Be aware que if this diretório does não\nalready exist, um log arquivo está não created." + "desc": "Container database close operation failed", + "first_action": "Read the relevant log file under the directory", + "full_action": "Read the relevant log file under the directory\nnetbackup/logs/vault for more details. Be aware that if this directory does not\nalready exist, a log file is not created." }, "318": { "code": 318, - "desc": "Container banco de dados lock operation falhou", - "first_action": "Ler o relevant log arquivo under o diretório", - "full_action": "Ler o relevant log arquivo under o diretório\nnetbackup/logs/vault para more details. Be aware que if this diretório does não\nalready exist, um log arquivo não created.\nIf some other Vault operation uses o container banco de dados e locks it, wait until\nque operation completes e o container banco de dados está unlocked." + "desc": "Container database lock operation failed", + "first_action": "Read the relevant log file under the directory", + "full_action": "Read the relevant log file under the directory\nnetbackup/logs/vault for more details. Be aware that if this directory does not\nalready exist, a log file not created.\nIf some other Vault operation uses the container database and locks it, wait until\nthat operation completes and the container database is unlocked." }, "319": { "code": 319, - "desc": "Container banco de dados abrir operation falhou", - "first_action": "Ler o relevant log arquivo under o diretório", - "full_action": "Ler o relevant log arquivo under o diretório\nnetbackup/logs/vault para more details. Be aware que if this diretório does não\nalready exist, um log arquivo está não created." + "desc": "Container database open operation failed", + "first_action": "Read the relevant log file under the directory", + "full_action": "Read the relevant log file under the directory\nnetbackup/logs/vault for more details. Be aware that if this directory does not\nalready exist, a log file is not created." }, "320": { "code": 320, - "desc": "O specified container está não vazio", - "first_action": "Inject todos de o mídia que it contains into um robot.", - "full_action": "Verifique que you have specified o correct container ID.\nIf you still desejar to excluir this container from o container banco de dados, first vazio it\npor doing either de o seguinte:\n■ Inject todos de o mídia que it contains into um robot.\n■ Clear o Vault container ID fields para these mídia from o EMM banco de dados por\nusando vmchange -vlt cid com um value de -.\nTry to excluir o container again." + "desc": "The specified container is not empty", + "first_action": "Inject all of the media that it contains into a robot.", + "full_action": "Verify that you have specified the correct container ID.\nIf you still want to delete this container from the container database, first empty it\nby doing either of the following:\n■ Inject all of the media that it contains into a robot.\n■ Clear the Vault container ID fields for these media from the EMM database by\nusing vmchange -vlt cid with a value of -.\nTry to delete the container again." }, "321": { "code": 321, - "desc": "Container não é possível hold qualquer mídia from o specified robot", - "first_action": "Verifique que you specified o correct container ID e", - "full_action": "Verifique que you specified o correct container ID e\nmídia IDs. Ler o relevant log arquivo under o diretório\ninstall_path/netbackup/logs/vault para more details. Be aware que if this\ndiretório does não already exist, um log arquivo está não created." + "desc": "Container cannot hold any media from the specified robot", + "first_action": "Verify that you specified the correct container ID and", + "full_action": "Verify that you specified the correct container ID and\nmedia IDs. Read the relevant log file under the directory\ninstall_path/netbackup/logs/vault for more details. Be aware that if this\ndirectory does not already exist, a log file is not created." }, "322": { "code": 322, - "desc": "Não é possível find vault in vault configuration arquivo", - "first_action": "Verifique que you specified o correct Vault name. Ler", - "full_action": "Verifique que you specified o correct Vault name. Ler\no relevant log arquivo under o diretório netbackup/logs/vault para more details.\nBe aware que if this diretório does não already exist, um log arquivo está não created." + "desc": "Cannot find vault in vault configuration file", + "first_action": "Verify that you specified the correct Vault name. Read", + "full_action": "Verify that you specified the correct Vault name. Read\nthe relevant log file under the directory netbackup/logs/vault for more details.\nBe aware that if this directory does not already exist, a log file is not created." }, "323": { "code": 323, - "desc": "Não é possível find robot in vault configuration arquivo NetBackup status codes 264 NetBackup status codes", - "first_action": "Verifique que you specified o correct robot number. Ler", - "full_action": "Verifique que you specified o correct robot number. Ler\no relevant log arquivo under o diretório netbackup/logs/vault para more details.\nBe aware que if this diretório does não already exist, um log arquivo está não created." + "desc": "Cannot find robot in vault configuration file NetBackup status codes 264 NetBackup status codes", + "first_action": "Verify that you specified the correct robot number. Read", + "full_action": "Verify that you specified the correct robot number. Read\nthe relevant log file under the directory netbackup/logs/vault for more details.\nBe aware that if this directory does not already exist, a log file is not created." }, "324": { "code": 324, - "desc": "Inválido data found in retention map arquivo para duplication", - "first_action": "Verifique o entradas in o retention_mappings arquivo.", - "full_action": "Verifique o entradas in o retention_mappings arquivo." + "desc": "Invalid data found in retention map file for duplication", + "first_action": "Check the entries in the retention_mappings file.", + "full_action": "Check the entries in the retention_mappings file." }, "325": { "code": 325, - "desc": "Não foi possível to find policy/schedule para image usando retention mapping", - "first_action": "Verifique whether ou não o backup policy ou o schedule", - "full_action": "Verifique whether ou não o backup policy ou o schedule\nque created o image still exists. If either one ou both do não exist, o image está\nnão duplicated through o Vault profile." + "desc": "Unable to find policy/schedule for image using retention mapping", + "first_action": "Verify whether or not the backup policy or the schedule", + "full_action": "Verify whether or not the backup policy or the schedule\nthat created the image still exists. If either one or both do not exist, the image is\nnot duplicated through the Vault profile." }, "326": { "code": 326, - "desc": "Specified arquivo contains não valid entry", + "desc": "Specified file contains no valid entry", "first_action": "Verifythateachentryin thespecifiedfiledoesnotexceed", - "full_action": "Verifythateachentryin thespecifiedfiledoesnotexceed\no string size limite: six characters para mídia IDs e 16 characters para o numeric\nequivalent de barcodes. Correct o inválido entradas in o specified arquivo e try o\nsame operation again. Ler o relevant log arquivo under o diretório\ninstall_path/netbackup/logs/vault para more details. Be aware que if this\ndiretório does não already exist, um log arquivo está não created." + "full_action": "Verifythateachentryin thespecifiedfiledoesnotexceed\nthe string size limit: six characters for media IDs and 16 characters for the numeric\nequivalent of barcodes. Correct the invalid entries in the specified file and try the\nsame operation again. Read the relevant log file under the directory\ninstall_path/netbackup/logs/vault for more details. Be aware that if this\ndirectory does not already exist, a log file is not created." }, "327": { "code": 327, - "desc": "Não mídia ejected para o specified vault session", - "first_action": "Verifique que you have specified o correct combination de", - "full_action": "Verifique que you have specified o correct combination de\nVault name e session ID. Verifique que o specified Vault session has ejected at\nleast one piece de mídia. Ler o relevant log arquivo under o diretório\nnetbackup/logs/vault para more details. Be aware que if this diretório does não\nalready exist, um log arquivo está não created." + "desc": "No media ejected for the specified vault session", + "first_action": "Verify that you have specified the correct combination of", + "full_action": "Verify that you have specified the correct combination of\nVault name and session ID. Verify that the specified Vault session has ejected at\nleast one piece of media. Read the relevant log file under the directory\nnetbackup/logs/vault for more details. Be aware that if this directory does not\nalready exist, a log file is not created." }, "328": { "code": 328, - "desc": "Inválido container ID", - "first_action": "Verifique que o container ID does não contain qualquer space", - "full_action": "Verifique que o container ID does não contain qualquer space\ncharacters, e que o string size está um maximum de 29 characters long." + "desc": "Invalid container ID", + "first_action": "Verify that the container ID does not contain any space", + "full_action": "Verify that the container ID does not contain any space\ncharacters, and that the string size is a maximum of 29 characters long." }, "329": { "code": 329, - "desc": "Inválido recall status", - "first_action": "Verifique que o recall status está either 1 ou 0.", - "full_action": "Verifique que o recall status está either 1 ou 0." + "desc": "Invalid recall status", + "first_action": "Verify that the recall status is either 1 or 0.", + "full_action": "Verify that the recall status is either 1 or 0." }, "330": { "code": 330, - "desc": "Inválido banco de dados host", + "desc": "Invalid database host", "first_action": "VerifythattheEMMdatabasehostnamedoesnotcontain", "full_action": "VerifythattheEMMdatabasehostnamedoesnotcontain\nanyspacecharacters,andthatthestringsizeisamaximumof256characterslong." }, "331": { "code": 331, - "desc": "Inválido container description", - "first_action": "Verifique que o string size de o container description está um", - "full_action": "Verifique que o string size de o container description está um\nmaximum de 25 characters long." + "desc": "Invalid container description", + "first_action": "Verify that the string size of the container description is a", + "full_action": "Verify that the string size of the container description is a\nmaximum of 25 characters long." }, "332": { "code": 332, - "desc": "Erro getting informação from EMM banco de dados", + "desc": "Error getting information from EMM database", "first_action": "OnUNIX,verifythattheNetBackupVolumeManagerdaemon(vmd)isrunning.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ OnUNIX,verifythattheNetBackupVolumeManagerdaemon(vmd)isrunning.\nOn Windows, verifique que o NetBackup Volume Manager service está executando.\n■ Veja o process-specific erro log diretório para more details.\nUNIX: /usr/openv/netbackup/logs/process_name\nWindows: install_path\\NetBackup\\logs\\process_name\nPara example, if you get this erro while executando um Vault comando (such como\nvltcontainers ou vltopmenu), look at o seguinte logs to learn por que:\n/usr/openv/netbackup/logs/vault\nNote: O log arquivo não é possível be created unless o appropriate log diretório (para\nexample, /usr/openv/netbackup/logs/vault) está already created." + "full_action": "Do the following, as appropriate:\n■ OnUNIX,verifythattheNetBackupVolumeManagerdaemon(vmd)isrunning.\nOn Windows, verify that the NetBackup Volume Manager service is running.\n■ See the process-specific error log directory for more details.\nUNIX: /usr/openv/netbackup/logs/process_name\nWindows: install_path\\NetBackup\\logs\\process_name\nFor example, if you get this error while running a Vault command (such as\nvltcontainers or vltopmenu), look at the following logs to learn why:\n/usr/openv/netbackup/logs/vault\nNote: The log file cannot be created unless the appropriate log directory (for\nexample, /usr/openv/netbackup/logs/vault) is already created." }, "333": { "code": 333, - "desc": "Erro getting informação from mídia manager comando line", - "first_action": "Contate customer support e send o appropriate logs.", - "full_action": "Contate customer support e send o appropriate logs." + "desc": "Error getting information from media manager command line", + "first_action": "Contact customer support and send the appropriate logs.", + "full_action": "Contact customer support and send the appropriate logs." }, "334": { "code": 334, - "desc": "Não foi possível to receive response from robot; robot não ready.", - "first_action": "Garanta que todos Mídia e Dispositivo Management daemons", - "full_action": "Garanta que todos Mídia e Dispositivo Management daemons\nestão executando ou o robot está live e up." + "desc": "Unable to receive response from robot; robot not ready.", + "first_action": "Ensure that all Media and Device Management daemons", + "full_action": "Ensure that all Media and Device Management daemons\nare running or the robot is live and up." }, "335": { "code": 335, - "desc": "Falha ocorreu while suspending mídia para eject", - "first_action": "Contate customer support e send o appropriate logs.", - "full_action": "Contate customer support e send o appropriate logs." + "desc": "Failure occurred while suspending media for eject", + "first_action": "Contact customer support and send the appropriate logs.", + "full_action": "Contact customer support and send the appropriate logs." }, "336": { "code": 336, - "desc": "Falha ocorreu while updating session informação", - "first_action": "Contate customer support e send o appropriate logs.", - "full_action": "Contate customer support e send o appropriate logs." + "desc": "Failure occurred while updating session information", + "first_action": "Contact customer support and send the appropriate logs.", + "full_action": "Contact customer support and send the appropriate logs." }, "337": { "code": 337, - "desc": "Falha ocorreu while updating o eject.mstr arquivo", - "first_action": "Contate customer support e send o appropriate logs.", - "full_action": "Contate customer support e send o appropriate logs." + "desc": "Failure occurred while updating the eject.mstr file", + "first_action": "Contact customer support and send the appropriate logs.", + "full_action": "Contact customer support and send the appropriate logs." }, "338": { "code": 338, - "desc": "Vault eject esgotado fora", - "first_action": "Remove o mídia from o MAP if it está already cheio.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Remove o mídia from o MAP if it está already cheio.\n■ Make sure que o MAP está closed properly." + "desc": "Vault eject timed out", + "first_action": "Remove the media from the MAP if it is already full.", + "full_action": "Do the following, as appropriate:\n■ Remove the media from the MAP if it is already full.\n■ Make sure that the MAP is closed properly." }, "339": { "code": 339, - "desc": "Vault configuration arquivo format erro", - "first_action": "Contate customer support e send o appropriate logs.", - "full_action": "Contate customer support e send o appropriate logs." + "desc": "Vault configuration file format error", + "first_action": "Contact customer support and send the appropriate logs.", + "full_action": "Contact customer support and send the appropriate logs." }, "340": { "code": 340, - "desc": "Vault configuration tag não found", - "first_action": "If o Vault's operation está affected, contate customer", - "full_action": "If o Vault's operation está affected, contate customer\nsupport e send o appropriate logs." + "desc": "Vault configuration tag not found", + "first_action": "If the Vault's operation is affected, contact customer", + "full_action": "If the Vault's operation is affected, contact customer\nsupport and send the appropriate logs." }, "341": { "code": 341, - "desc": "Vault configuration serialization falhou", - "first_action": "Contate customer support e send o appropriate logs.", - "full_action": "Contate customer support e send o appropriate logs." + "desc": "Vault configuration serialization failed", + "first_action": "Contact customer support and send the appropriate logs.", + "full_action": "Contact customer support and send the appropriate logs." }, "342": { "code": 342, - "desc": "Não é possível modify - stale view", - "first_action": "Verifique o latest attributes de o robot ou vault ou profile.", - "full_action": "Verifique o latest attributes de o robot ou vault ou profile.\nTo verifique, refresh o view in o NetBackup Administration Console ou retrieve\no attributes in o Vault Administration menu usuário interface again. Then retry\no operation." + "desc": "Cannot modify - stale view", + "first_action": "Check the latest attributes of the robot or vault or profile.", + "full_action": "Check the latest attributes of the robot or vault or profile.\nTo check, refresh the view in the NetBackup Administration Console or retrieve\nthe attributes in the Vault Administration menu user interface again. Then retry\nthe operation." }, "343": { "code": 343, "desc": "Robot already exists", - "first_action": "Refresh o view in o NetBackup Administration", - "full_action": "Refresh o view in o NetBackup Administration\nConsoleor retrievetheattributesin theVaultAdministrationmenu usuário interface\nagain to veja o robot." + "first_action": "Refresh the view in the NetBackup Administration", + "full_action": "Refresh the view in the NetBackup Administration\nConsoleor retrievetheattributesin theVaultAdministrationmenu user interface\nagain to see the robot." }, "344": { "code": 344, "desc": "Vault already exists", - "first_action": "Choose um different name para o vault.", - "full_action": "Choose um different name para o vault." + "first_action": "Choose a different name for the vault.", + "full_action": "Choose a different name for the vault." }, "345": { "code": 345, "desc": "Profile already exists", - "first_action": "Choose um different name para o profile.", - "full_action": "Choose um different name para o profile." + "first_action": "Choose a different name for the profile.", + "full_action": "Choose a different name for the profile." }, "346": { "code": 346, "desc": "Duplicate MAP", - "first_action": "Contate customer support e send o appropriate logs.", - "full_action": "Contate customer support e send o appropriate logs." + "first_action": "Contact customer support and send the appropriate logs.", + "full_action": "Contact customer support and send the appropriate logs." }, "347": { "code": 347, - "desc": "Vault configuration cache não initialized", - "first_action": "Contate customer support e send o appropriate logs.", - "full_action": "Contate customer support e send o appropriate logs." + "desc": "Vault configuration cache not initialized", + "first_action": "Contact customer support and send the appropriate logs.", + "full_action": "Contact customer support and send the appropriate logs." }, "348": { "code": 348, - "desc": "Specified relatório does não exist", - "first_action": "Contate customer support e send o appropriate logs.", - "full_action": "Contate customer support e send o appropriate logs." + "desc": "Specified report does not exist", + "first_action": "Contact customer support and send the appropriate logs.", + "full_action": "Contact customer support and send the appropriate logs." }, "349": { "code": 349, "desc": "Incorrect catalog backup policy", - "first_action": "Verifique que you specified um catalog backup policy para o", - "full_action": "Verifique que you specified um catalog backup policy para o\ncatalog backup in o Vault profile e que o policy está de type NBU-Catalog." + "first_action": "Verify that you specified a catalog backup policy for the", + "full_action": "Verify that you specified a catalog backup policy for the\ncatalog backup in the Vault profile and that the policy is of type NBU-Catalog." }, "350": { "code": 350, "desc": "Incorrect vault catalog backup schedule", "first_action": "VerifythatyouspecifiedaVaultCatalogBackupschedule", - "full_action": "VerifythatyouspecifiedaVaultCatalogBackupschedule\npara o catalog backup in o Vault profile. Also verifique que o schedule está de type\nVault Catalog Backup." + "full_action": "VerifythatyouspecifiedaVaultCatalogBackupschedule\nfor the catalog backup in the Vault profile. Also verify that the schedule is of type\nVault Catalog Backup." }, "351": { "code": 351, - "desc": "Todos configurado vault steps falhou", + "desc": "All configured vault steps failed", "first_action": "Forduplicationandcatalogbackupsteps,usetheActivity", - "full_action": "Forduplicationandcatalogbackupsteps,usetheActivity\nMonitor to verifique o status de o respective jobs que Vault started. Para Eject step\nstatus, verifique o Detailed Status tab de o Job Details dialog box para o Vault\njob." + "full_action": "Forduplicationandcatalogbackupsteps,usetheActivity\nMonitor to check the status of the respective jobs that Vault started. For Eject step\nstatus, check the Detailed Status tab of the Job Details dialog box for the Vault\njob." }, "400": { "code": 400, - "desc": "Servidor Group Type está Inválido", - "first_action": "Select um valid servidor group type: MediaSharing, ou AltServerRestore.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Select um valid servidor group type: MediaSharing, ou AltServerRestore.\n■ Para detailed troubleshooting informação, create o admin debug log diretório\ne retry o operation. Verifique o resulting debug logs. Additional debug\ninformação can be found in o logs para nbemm (originator ID 111) which uses\nunified logging." + "desc": "Server Group Type is Invalid", + "first_action": "Select a valid server group type: MediaSharing, or AltServerRestore.", + "full_action": "Do the following, as appropriate:\n■ Select a valid server group type: MediaSharing, or AltServerRestore.\n■ For detailed troubleshooting information, create the admin debug log directory\nand retry the operation. Check the resulting debug logs. Additional debug\ninformation can be found in the logs for nbemm (originator ID 111) which uses\nunified logging." }, "401": { "code": 401, - "desc": "Servidor Group Already Exists", - "first_action": "Verifique que o specified servidor group name está não in use.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Verifique que o specified servidor group name está não in use.\n■ Create o servidor group por specifying um name que está não currently in use.\n■ Para detailed troubleshooting informação, create o admin debug log diretório\ne retry o operation. Verifique o resulting debug logs. Additional debug\ninformação can be found in o log para nbemm (originator ID 111), which uses\nunified logging." + "desc": "Server Group Already Exists", + "first_action": "Verify that the specified server group name is not in use.", + "full_action": "Do the following, as appropriate:\n■ Verify that the specified server group name is not in use.\n■ Create the server group by specifying a name that is not currently in use.\n■ For detailed troubleshooting information, create the admin debug log directory\nand retry the operation. Check the resulting debug logs. Additional debug\ninformation can be found in the log for nbemm (originator ID 111), which uses\nunified logging." }, "402": { "code": 402, - "desc": "Servidor Group Already Exists com um different type", - "first_action": "Verifique que o specified servidor group name está não in use.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Verifique que o specified servidor group name está não in use.\n■ Try to create o servidor group por specifying um name que está não currently in use.\n■ Para detailed troubleshooting informação, create o admin debug log diretório\ne retry o operation. Verifique o resulting debug logs. Additional debug\ninformação can be found in o log para nbemm (originator ID 111), which uses\nunified logging." + "desc": "Server Group Already Exists with a different type", + "first_action": "Verify that the specified server group name is not in use.", + "full_action": "Do the following, as appropriate:\n■ Verify that the specified server group name is not in use.\n■ Try to create the server group by specifying a name that is not currently in use.\n■ For detailed troubleshooting information, create the admin debug log directory\nand retry the operation. Check the resulting debug logs. Additional debug\ninformation can be found in the log for nbemm (originator ID 111), which uses\nunified logging." }, "403": { "code": 403, - "desc": "Servidor Group Active State está não valid", - "first_action": "Valid servidor group states estão: ACTIVE e INACTIVE", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Valid servidor group states estão: ACTIVE e INACTIVE\n■ Para detailed troubleshooting informação, create o admin debug log diretório\ne retry o operation. Verifique o resulting debug logs. Additional debug\ninformação can be found in o log para nbemm (originator ID 111), which uses\nunified logging." + "desc": "Server Group Active State is not valid", + "first_action": "Valid server group states are: ACTIVE and INACTIVE", + "full_action": "Do the following, as appropriate:\n■ Valid server group states are: ACTIVE and INACTIVE\n■ For detailed troubleshooting information, create the admin debug log directory\nand retry the operation. Check the resulting debug logs. Additional debug\ninformation can be found in the log for nbemm (originator ID 111), which uses\nunified logging." }, "404": { "code": 404, - "desc": "Servidor Group does não exist", - "first_action": "Verifique que o specified mídia está correct.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Verifique que o specified mídia está correct.\n■ Verifique o mídia ownership.\n■ Verifique que o servidor group exists.\n■ Verifique que o servidor onde o operation está performed está um member de o\nowning servidor group. If não, try o operation from um servidor que está um member de\no servidor group.\n■ Para detailed troubleshooting informação, create o admin debug log diretório\ne retry o operation. Verifique o resulting debug logs. Additional debug\ninformação can be found in o log para nbemm (originator IDs 111 e 143),\nwhich uses unified logging." + "desc": "Server Group does not exist", + "first_action": "Verify that the specified media is correct.", + "full_action": "Do the following, as appropriate:\n■ Verify that the specified media is correct.\n■ Verify the media ownership.\n■ Verify that the server group exists.\n■ Verify that the server where the operation is performed is a member of the\nowning server group. If not, try the operation from a server that is a member of\nthe server group.\n■ For detailed troubleshooting information, create the admin debug log directory\nand retry the operation. Check the resulting debug logs. Additional debug\ninformation can be found in the log for nbemm (originator IDs 111 and 143),\nwhich uses unified logging." }, "405": { "code": 405, - "desc": "Member’s servidor type não compatible com Servidor Group", - "first_action": "O Mídia Sharing servidor group can contain o seguinte types de servers:", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ O Mídia Sharing servidor group can contain o seguinte types de servers:\nMaster, Mídia, NDMP, e cluster.\n■ Para detailed troubleshooting informação, create o admin debug log diretório\ne retry o operation. Verifique o resulting debug logs. Additional debug\ninformação can be found in o log para nbemm (originator IDs 111 e 143),\nwhich uses unified logging." + "desc": "Member’s server type not compatible with Server Group", + "first_action": "The Media Sharing server group can contain the following types of servers:", + "full_action": "Do the following, as appropriate:\n■ The Media Sharing server group can contain the following types of servers:\nMaster, Media, NDMP, and cluster.\n■ For detailed troubleshooting information, create the admin debug log directory\nand retry the operation. Check the resulting debug logs. Additional debug\ninformation can be found in the log for nbemm (originator IDs 111 and 143),\nwhich uses unified logging." }, "406": { "code": 406, - "desc": "O computer specified está não um member de o servidor group specified", - "first_action": "Verifique que o specified mídia está correct.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Verifique que o specified mídia está correct.\n■ Verifique o mídia ownership.\n■ Verifique que o servidor onde o operation está performed está um member de o\nowning servidor group. If não, try o operation from um servidor que está um member de\no servidor group.\n■ Para detailed troubleshooting informação, create o admin debug log diretório\ne retry o operation. Verifique o resulting debug logs. Additional debug\ninformação can be found in o log para nbemm (originator IDs 111 e 143),\nwhich use unified logging." + "desc": "The computer specified is not a member of the server group specified", + "first_action": "Verify that the specified media is correct.", + "full_action": "Do the following, as appropriate:\n■ Verify that the specified media is correct.\n■ Verify the media ownership.\n■ Verify that the server where the operation is performed is a member of the\nowning server group. If not, try the operation from a server that is a member of\nthe server group.\n■ For detailed troubleshooting information, create the admin debug log directory\nand retry the operation. Check the resulting debug logs. Additional debug\ninformation can be found in the log for nbemm (originator IDs 111 and 143),\nwhich use unified logging." }, "407": { "code": 407, - "desc": "Member’s NetBackup version não compatible com Servidor Group", + "desc": "Member’s NetBackup version not compatible with Server Group", "first_action": "EnsurethateachmemberserverhasavalidNetBackupversionforthespecified", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ EnsurethateachmemberserverhasavalidNetBackupversionforthespecified\nservidor group type.\n■ Para detailed troubleshooting informação, create o admin debug log diretório\ne retry o operation. Verifique o resulting debug logs. Additional debug\ninformationcanbefoundinthelogfornbemm(originatorIDs111and143),which\nuses unified logging." + "full_action": "Do the following, as appropriate:\n■ EnsurethateachmemberserverhasavalidNetBackupversionforthespecified\nserver group type.\n■ For detailed troubleshooting information, create the admin debug log directory\nand retry the operation. Check the resulting debug logs. Additional debug\ninformationcanbefoundinthelogfornbemm(originatorIDs111and143),which\nuses unified logging." }, "408": { "code": 408, - "desc": "Servidor Group está in use", - "first_action": "Garanta que o servidor group está não o owner de qualquer mídia por executando", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Garanta que o servidor group está não o owner de qualquer mídia por executando\nbpmedialist -owner group_name from o master servidor.\n■ Para detailed troubleshooting informação, create o admin debug log diretório\ne retry o operation. Verifique o resulting debug logs. Additional debug\ninformação can be found in o log para nbemm (originator IDs 111 e 143),\nwhich uses unified logging." + "desc": "Server Group is in use", + "first_action": "Ensure that the server group is not the owner of any media by running", + "full_action": "Do the following, as appropriate:\n■ Ensure that the server group is not the owner of any media by running\nbpmedialist -owner group_name from the master server.\n■ For detailed troubleshooting information, create the admin debug log directory\nand retry the operation. Check the resulting debug logs. Additional debug\ninformation can be found in the log for nbemm (originator IDs 111 and 143),\nwhich uses unified logging." }, "409": { "code": 409, - "desc": "Member already exists in servidor group", - "first_action": "Garanta que o servidor group member que you add does não already exist in o", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Garanta que o servidor group member que you add does não already exist in o\ngroup.\n■" + "desc": "Member already exists in server group", + "first_action": "Ensure that the server group member that you add does not already exist in the", + "full_action": "Do the following, as appropriate:\n■ Ensure that the server group member that you add does not already exist in the\ngroup.\n■" }, "410": { "code": 410, - "desc": "Um backup host pool com this name already exists.", - "first_action": "Use um unique name para o backup host pool.", - "full_action": "Use um unique name para o backup host pool." + "desc": "A backup host pool with this name already exists.", + "first_action": "Use a unique name for the backup host pool.", + "full_action": "Use a unique name for the backup host pool." }, "411": { "code": 411, - "desc": "O backup host pool group state está não active.", - "first_action": "While creating um backup host pool, provide -grpstate", - "full_action": "While creating um backup host pool, provide -grpstate\nACTIVE como o parâmetro value." + "desc": "The backup host pool group state is not active.", + "first_action": "While creating a backup host pool, provide -grpstate", + "full_action": "While creating a backup host pool, provide -grpstate\nACTIVE as the parameter value." }, "412": { "code": 412, - "desc": "O backup host pool does não exist.", + "desc": "The backup host pool does not exist.", "first_action": "Usethenbsvrgrp -listcommandtocheckifthebackup", "full_action": "Usethenbsvrgrp -listcommandtocheckifthebackup\nhost pool exists." }, "413": { "code": 413, - "desc": "O host entry in o backup host pool already exists.", - "first_action": "O specified host está already um part de o backup host", - "full_action": "O specified host está already um part de o backup host\npool. Não usuário ação está requerido." + "desc": "The host entry in the backup host pool already exists.", + "first_action": "The specified host is already a part of the backup host", + "full_action": "The specified host is already a part of the backup host\npool. No user action is required." }, "501": { "code": 501, - "desc": "You estão não authorized to use this application.", - "first_action": "Verifique o auth.conf arquivo on o host que está specified in", - "full_action": "Verifique o auth.conf arquivo on o host que está specified in\no NetBackup Java login dialog box para o proper authorization. If o auth.conf\narquivo does não exist, it must be created com o proper entry para this usuário name. More\ndetails on o auth.conf arquivo estão disponível.\nVeja NetBackup Administrator’s Guide, Volume I." + "desc": "You are not authorized to use this application.", + "first_action": "Check the auth.conf file on the host that is specified in", + "full_action": "Check the auth.conf file on the host that is specified in\nthe NetBackup Java login dialog box for the proper authorization. If the auth.conf\nfile does not exist, it must be created with the proper entry for this user name. More\ndetails on the auth.conf file are available.\nSee NetBackup Administrator’s Guide, Volume I." }, "502": { "code": 502, - "desc": "Noauthorizationentryexistsintheauth.conffileforusernameusername. Nenhum de o NetBackup Java applications estão disponível to you.", - "first_action": "Verifique o auth.conf arquivo on o computer (host name)", - "full_action": "Verifique o auth.conf arquivo on o computer (host name)\nspecified in o NetBackup Java logon dialog box para o proper authorization. If\nthefiledoesnotexist,createitwiththeproperentryforthisusername.Moredetails\non o auth.conf arquivo estão disponível.\nVeja NetBackup Administrator’s Guide, Volume I." + "desc": "Noauthorizationentryexistsintheauth.conffileforusernameusername. None of the NetBackup Java applications are available to you.", + "first_action": "Check the auth.conf file on the computer (host name)", + "full_action": "Check the auth.conf file on the computer (host name)\nspecified in the NetBackup Java logon dialog box for the proper authorization. If\nthefiledoesnotexist,createitwiththeproperentryforthisusername.Moredetails\non the auth.conf file are available.\nSee NetBackup Administrator’s Guide, Volume I." }, "503": { "code": 503, - "desc": "Inválido usuário name.", - "first_action": "Para UNIX hosts: o usuário name must be um valid usuário name in o passwd arquivo on", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Para UNIX hosts: o usuário name must be um valid usuário name in o passwd arquivo on\no host que está specified in o logon dialog box.\n■ Para Windows hosts: refer to o LogonUser function in o section titled\nClient/Server Access Control Functions de o Windows Platform Software\nDeveloper’s Kit to determinar o requerido privileges." + "desc": "Invalid user name.", + "first_action": "For UNIX hosts: the user name must be a valid user name in the passwd file on", + "full_action": "Do the following, as appropriate:\n■ For UNIX hosts: the user name must be a valid user name in the passwd file on\nthe host that is specified in the logon dialog box.\n■ For Windows hosts: refer to the LogonUser function in the section titled\nClient/Server Access Control Functions of the Windows Platform Software\nDeveloper’s Kit to determine the required privileges." }, "504": { "code": 504, "desc": "Incorrect password.", - "first_action": "Enter o correct password.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Enter o correct password.\n■ On Windows hosts: O exact erro can be found in o bpjava-msvc log arquivo.\nFormoredetails,refertotheLogonUserfunctioninthesectionClient/ServerAccess\nControl Functions de o Windows Platform Software Developer’s Kit." + "first_action": "Enter the correct password.", + "full_action": "Do the following, as appropriate:\n■ Enter the correct password.\n■ On Windows hosts: The exact error can be found in the bpjava-msvc log file.\nFormoredetails,refertotheLogonUserfunctioninthesectionClient/ServerAccess\nControl Functions of the Windows Platform Software Developer’s Kit." }, "505": { "code": 505, - "desc": "Não é possível conectar to o NetBackup Java authentication service on host on o configurado port - (port_number). Verifique o log arquivo para more details.", - "first_action": "On UNIX, compare o bpjava-msvc entry in o /etc/services arquivo com o", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ On UNIX, compare o bpjava-msvc entry in o /etc/services arquivo com o\nBPJAVA_PORT entry in o /usr/openv/java/nbj.conf arquivo\nOn Windows, compare o bpjava-msvc entry in o\n%systemroot%\\system32\\drivers\\etc\\services arquivo com o\ninstall_path\\java\\setconf.bat arquivo (Windows). O entradas must match.\n■ Garanta que não other application uses o port que está configurado para o\nNetBackup Java interface." + "desc": "Cannot connect to the NetBackup Java authentication service on host on the configured port - (port_number). Check the log file for more details.", + "first_action": "On UNIX, compare the bpjava-msvc entry in the /etc/services file with the", + "full_action": "Do the following, as appropriate:\n■ On UNIX, compare the bpjava-msvc entry in the /etc/services file with the\nBPJAVA_PORT entry in the /usr/openv/java/nbj.conf file\nOn Windows, compare the bpjava-msvc entry in the\n%systemroot%\\system32\\drivers\\etc\\services file with the\ninstall_path\\java\\setconf.bat file (Windows). The entries must match.\n■ Ensure that no other application uses the port that is configured for the\nNetBackup Java interface." }, "506": { "code": 506, - "desc": "Não é possível conectar to o NetBackup Java usuário service on host on port port_number. If successfully logged in before, retry seu last operation. Verifique o log arquivo para more details.", - "first_action": "Restart o NetBackup Java interface e log in again.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Restart o NetBackup Java interface e log in again.\n■ If o problema persists, enable detailed debug logging.\n■ Restart o NetBackup Java interface e examine o logs." + "desc": "Cannot connect to the NetBackup Java user service on host on port port_number. If successfully logged in before, retry your last operation. Check the log file for more details.", + "first_action": "Restart the NetBackup Java interface and log in again.", + "full_action": "Do the following, as appropriate:\n■ Restart the NetBackup Java interface and log in again.\n■ If the problem persists, enable detailed debug logging.\n■ Restart the NetBackup Java interface and examine the logs." }, "507": { "code": 507, - "desc": "SocketconnectiontotheNetBackupJavauserservicehasbeenbroken. Retry seu last operation. Verifique o log arquivo para more details.", - "first_action": "Retry o last operation.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Retry o last operation.\n■ If o problema persists, restart o NetBackup Java interface e try again.\n■ Iftheproblemstillpersists,setthedebugloggingformediamanagertoahigher\nlevel.\n■ Restart o NetBackup Java interface e examine o logs.\nNote: You may have rede ou system problemas unrelated to NetBackup." + "desc": "SocketconnectiontotheNetBackupJavauserservicehasbeenbroken. Retry your last operation. Check the log file for more details.", + "first_action": "Retry the last operation.", + "full_action": "Do the following, as appropriate:\n■ Retry the last operation.\n■ If the problem persists, restart the NetBackup Java interface and try again.\n■ Iftheproblemstillpersists,setthedebugloggingformediamanagertoahigher\nlevel.\n■ Restart the NetBackup Java interface and examine the logs.\nNote: You may have network or system problems unrelated to NetBackup." }, "508": { "code": 508, - "desc": "Não é possível gravar arquivo.", + "desc": "Cannot write file.", "first_action": "Retrievethespecificdetailsfromtheuserservicelogfiles.", - "full_action": "Retrievethespecificdetailsfromtheuserservicelogfiles.\nSet o debug logging para mídia manager to um higher level." + "full_action": "Retrievethespecificdetailsfromtheuserservicelogfiles.\nSet the debug logging for media manager to a higher level." }, "509": { "code": 509, - "desc": "Não é possível execute program.", - "first_action": "If o problema persists, restart o NetBackup Java interface e try again.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ If o problema persists, restart o NetBackup Java interface e try again.\n■ If o problema still persists, enable detailed debug logging como explained in o\nseguinte topic:\nVeja \"Setting debug logging to um higher level\" in o NetBackup Logging\nReference Guide.\n■ Restart o NetBackup Java interface e examine o logs.\nO erro está probably o result de um system resource issue. When detailed debug\nlogging está enabled, you can retrieve o details from o bpjava-msvc,\nbpjava-susvc, ou bpjava-usvc log arquivos." + "desc": "Cannot execute program.", + "first_action": "If the problem persists, restart the NetBackup Java interface and try again.", + "full_action": "Do the following, as appropriate:\n■ If the problem persists, restart the NetBackup Java interface and try again.\n■ If the problem still persists, enable detailed debug logging as explained in the\nfollowing topic:\nSee \"Setting debug logging to a higher level\" in the NetBackup Logging\nReference Guide.\n■ Restart the NetBackup Java interface and examine the logs.\nThe error is probably the result of a system resource issue. When detailed debug\nlogging is enabled, you can retrieve the details from the bpjava-msvc,\nbpjava-susvc, or bpjava-usvc log files." }, "510": { "code": 510, - "desc": "Arquivo already exists: file_name", + "desc": "File already exists: file_name", "first_action": "Removethefile,whichcanbeidentifiedintheuserservice", - "full_action": "Removethefile,whichcanbeidentifiedintheuserservice\nlog arquivos.\nVeja \"Troubleshooting erro messages in o NetBackup Administration Console\"\nin o NetBackup Logging Reference Guide." + "full_action": "Removethefile,whichcanbeidentifiedintheuserservice\nlog files.\nSee \"Troubleshooting error messages in the NetBackup Administration Console\"\nin the NetBackup Logging Reference Guide." }, "511": { "code": 511, - "desc": "NetBackup Java application servidor interface erro.", - "first_action": "If o problema persists, restart o NetBackup Java interface e try again.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ If o problema persists, restart o NetBackup Java interface e try again.\n■ If o problema still persists, enable detailed debug logging como explained in o\nseguinte topic:\nVeja \"Setting Mídia Manager debug logging to um higher level\" in o NetBackup\nLogging Reference Guide.\n■ Restart o NetBackup Java interface e examine o logs.\nO erro está probably o result de um system resource issue. When detailed debug\nlogging está enabled, o details can be retrieved from o bpjava-msvc,\nbpjava-susvc, ou bpjava-usvc log arquivos." + "desc": "NetBackup Java application server interface error.", + "first_action": "If the problem persists, restart the NetBackup Java interface and try again.", + "full_action": "Do the following, as appropriate:\n■ If the problem persists, restart the NetBackup Java interface and try again.\n■ If the problem still persists, enable detailed debug logging as explained in the\nfollowing topic:\nSee \"Setting Media Manager debug logging to a higher level\" in the NetBackup\nLogging Reference Guide.\n■ Restart the NetBackup Java interface and examine the logs.\nThe error is probably the result of a system resource issue. When detailed debug\nlogging is enabled, the details can be retrieved from the bpjava-msvc,\nbpjava-susvc, or bpjava-usvc log files." }, "512": { "code": 512, - "desc": "Internal erro - um bad status packet foi returned por NetBackup Java application servidor que did não contain um exit status code.", - "first_action": "If o problema persists, restart o NetBackup Java interface e try again.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ If o problema persists, restart o NetBackup Java interface e try again.\n■ If o problema still persists, enable detailed debug logging como explained in o\nseguinte topic:\nVeja \"Setting Mídia Manager debug logging to um higher level\" in o NetBackup\nLogging Reference Guide.\n■ Restart o NetBackup Java interface e examine o logs.\nO erro está probably o result de um system resource issue. When detailed debug\nlogging está enabled, o details can be retrieved from o bpjava-msvc,\nbpjava-susvc, ou bpjava-usvc log arquivos." + "desc": "Internal error - a bad status packet was returned by NetBackup Java application server that did not contain an exit status code.", + "first_action": "If the problem persists, restart the NetBackup Java interface and try again.", + "full_action": "Do the following, as appropriate:\n■ If the problem persists, restart the NetBackup Java interface and try again.\n■ If the problem still persists, enable detailed debug logging as explained in the\nfollowing topic:\nSee \"Setting Media Manager debug logging to a higher level\" in the NetBackup\nLogging Reference Guide.\n■ Restart the NetBackup Java interface and examine the logs.\nThe error is probably the result of a system resource issue. When detailed debug\nlogging is enabled, the details can be retrieved from the bpjava-msvc,\nbpjava-susvc, or bpjava-usvc log files." }, "513": { "code": 513, - "desc": "Bpjava-msvc: o cliente está não compatible com this servidor version (server_version).", - "first_action": "Log in to um different NetBackup remote host.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Log in to um different NetBackup remote host.\n■ Upgrade o NetBackup software on either de o seguinte: o computer que\nestá specified in o logon dialog box ou o local host onde you started o\nNetBackup Java interface." + "desc": "Bpjava-msvc: the client is not compatible with this server version (server_version).", + "first_action": "Log in to a different NetBackup remote host.", + "full_action": "Do the following, as appropriate:\n■ Log in to a different NetBackup remote host.\n■ Upgrade the NetBackup software on either of the following: the computer that\nis specified in the logon dialog box or the local host where you started the\nNetBackup Java interface." }, "514": { "code": 514, - "desc": "NetBackup Java: bpjava-msvc está não compatible com this application version (application_version). You may try logon to um different NetBackup host ou exittheapplication.TheremoteNetBackuphosthastobeconfiguredwiththesame version de NetBackup como o host you started o application on.", - "first_action": "Log in to um different NetBackup remote host.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Log in to um different NetBackup remote host.\n■ Upgrade o NetBackup software on either de o seguinte: o specified\ncomputer in o logon dialog box ou o local host onde you started o\nNetBackup Java interface." + "desc": "NetBackup Java: bpjava-msvc is not compatible with this application version (application_version). You may try logon to a different NetBackup host or exittheapplication.TheremoteNetBackuphosthastobeconfiguredwiththesame version of NetBackup as the host you started the application on.", + "first_action": "Log in to a different NetBackup remote host.", + "full_action": "Do the following, as appropriate:\n■ Log in to a different NetBackup remote host.\n■ Upgrade the NetBackup software on either of the following: the specified\ncomputer in the logon dialog box or the local host where you started the\nNetBackup Java interface." }, "516": { "code": 516, "desc": "Couldnotrecognizeorinitializetherequestedlocale-(locale_NetBackup Java_was_started_in).", - "first_action": "On o specified host in o NetBackup Java logon dialog", - "full_action": "On o specified host in o NetBackup Java logon dialog\nbox, verifique o configuration arquivo to garanta que um mapping está disponível para o\nindicated locale.\nPara informação on locale configuration e mapping, refer to o NetBackup\nAdministrator's Guide, Volume II.\nIf there está um mapping, try to set o mapped locale on o host que foi specified in\no NetBackupJava logon dialog box. This system may não be configuredproperly." + "first_action": "On the specified host in the NetBackup Java logon dialog", + "full_action": "On the specified host in the NetBackup Java logon dialog\nbox, check the configuration file to ensure that a mapping is available for the\nindicated locale.\nFor information on locale configuration and mapping, refer to the NetBackup\nAdministrator's Guide, Volume II.\nIf there is a mapping, try to set the mapped locale on the host that was specified in\nthe NetBackupJava logon dialog box. This system may not be configuredproperly." }, "517": { "code": 517, - "desc": "Não é possível conectar to o NetBackup Java usuário service por VNETD on host on port configured_port_number. If successfully logged on beforehand, retry seu last operation. Verifique o log arquivo para more details.", - "first_action": "On UNIX: Compare o VNETD entry in o /etc/services arquivo com o", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ On UNIX: Compare o VNETD entry in o /etc/services arquivo com o\nVNETD_PORT entry in /usr/openv/java/nbj.conf\nOn Windows: Compare o VNETD entry com o VNETD_PORT entry in o\ninstall_path\\java\\setconf.bat arquivo.\nThese entradas must match.\n■ Garanta que não other application uses o port que está configurado para VNETD." + "desc": "Cannot connect to the NetBackup Java user service by VNETD on host on port configured_port_number. If successfully logged on beforehand, retry your last operation. Check the log file for more details.", + "first_action": "On UNIX: Compare the VNETD entry in the /etc/services file with the", + "full_action": "Do the following, as appropriate:\n■ On UNIX: Compare the VNETD entry in the /etc/services file with the\nVNETD_PORT entry in /usr/openv/java/nbj.conf\nOn Windows: Compare the VNETD entry with the VNETD_PORT entry in the\ninstall_path\\java\\setconf.bat file.\nThese entries must match.\n■ Ensure that no other application uses the port that is configured for VNETD." }, "518": { "code": 518, - "desc": "Não ports disponível in range (port_number) through (port_number) per o NBJAVA_CLIENT_PORT_WINDOW configuration option. NetBackup status codes 286 NetBackup status codes", - "first_action": "Restart o NetBackup Java interface e try again.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Restart o NetBackup Java interface e try again.\n■ If o problema persists, aumentar o range de ports por changing o\nNBJAVA_CLIENT_PORT_WINDOWoptioninthe/usr/openv/java/nbj.conf\narquivo (UNIX) ou o install_path\\java\\setconf.bat arquivo (Windows)." + "desc": "No ports available in range (port_number) through (port_number) per the NBJAVA_CLIENT_PORT_WINDOW configuration option. NetBackup status codes 286 NetBackup status codes", + "first_action": "Restart the NetBackup Java interface and try again.", + "full_action": "Do the following, as appropriate:\n■ Restart the NetBackup Java interface and try again.\n■ If the problem persists, increase the range of ports by changing the\nNBJAVA_CLIENT_PORT_WINDOWoptioninthe/usr/openv/java/nbj.conf\nfile (UNIX) or the install_path\\java\\setconf.bat file (Windows)." }, "519": { "code": 519, - "desc": "Inválido NBJAVA_CLIENT_PORT_WINDOW configuration option value: (option_value).", - "first_action": "Correct o value in arquivo /usr/openv/java/nbj.conf", - "full_action": "Correct o value in arquivo /usr/openv/java/nbj.conf\n(UNIX) ou install_path\\java\\setconf.bat arquivo (Windows)." + "desc": "Invalid NBJAVA_CLIENT_PORT_WINDOW configuration option value: (option_value).", + "first_action": "Correct the value in file /usr/openv/java/nbj.conf", + "full_action": "Correct the value in file /usr/openv/java/nbj.conf\n(UNIX) or install_path\\java\\setconf.bat file (Windows)." }, "520": { "code": 520, - "desc": "Inválido value para NetBackup Java configuration option (option_name): (option_value).", - "first_action": "Correct o value in arquivo /usr/openv/java/nbj.conf", - "full_action": "Correct o value in arquivo /usr/openv/java/nbj.conf\n(UNIX) ou install_path\\java\\setconf.bat arquivo (Windows)." + "desc": "Invalid value for NetBackup Java configuration option (option_name): (option_value).", + "first_action": "Correct the value in file /usr/openv/java/nbj.conf", + "full_action": "Correct the value in file /usr/openv/java/nbj.conf\n(UNIX) or install_path\\java\\setconf.bat file (Windows)." }, "521": { "code": 521, - "desc": "NetBackup Java Configuration arquivo (file_name) does não exist.", - "first_action": "Make sure que o configuration arquivo o NetBackup Java", - "full_action": "Make sure que o configuration arquivo o NetBackup Java\ninterface exists e está properly formatted." + "desc": "NetBackup Java Configuration file (file_name) does not exist.", + "first_action": "Make sure that the configuration file the NetBackup Java", + "full_action": "Make sure that the configuration file the NetBackup Java\ninterface exists and is properly formatted." }, "522": { "code": 522, - "desc": "NetBackup Java Configuration arquivo (file_name) está não readable due to o seguinte erro: (message).", - "first_action": "Correct o arquivo como specified in o message.", - "full_action": "Correct o arquivo como specified in o message." + "desc": "NetBackup Java Configuration file (file_name) is not readable due to the following error: (message).", + "first_action": "Correct the file as specified in the message.", + "full_action": "Correct the file as specified in the message." }, "523": { "code": 523, - "desc": "NetBackup Java application servidor protocol erro.", - "first_action": "If o problema persists, restart o NetBackup Java interface e try again.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ If o problema persists, restart o NetBackup Java interface e try again.\n■ If o problema still persists, enable detailed debug logging como explained in o\nseguinte topic:\nVeja \"Setting Mídia Manager debug logging to um higher level\" in o NetBackup\nLogging Reference Guide.\n■ Restart o NetBackup Java interface e examine o logs.\nNote: O erro está probably o result de um system resource issue. When detailed\ndebug logging ID está enabled, o details can be retrieved from o bpjava-msvc,\nbpjava-susvc, ou bpjava-usvc log arquivos." + "desc": "NetBackup Java application server protocol error.", + "first_action": "If the problem persists, restart the NetBackup Java interface and try again.", + "full_action": "Do the following, as appropriate:\n■ If the problem persists, restart the NetBackup Java interface and try again.\n■ If the problem still persists, enable detailed debug logging as explained in the\nfollowing topic:\nSee \"Setting Media Manager debug logging to a higher level\" in the NetBackup\nLogging Reference Guide.\n■ Restart the NetBackup Java interface and examine the logs.\nNote: The error is probably the result of a system resource issue. When detailed\ndebug logging ID is enabled, the details can be retrieved from the bpjava-msvc,\nbpjava-susvc, or bpjava-usvc log files." }, "525": { "code": 525, - "desc": "CannotconnecttotheNetBackupJavaauthenticationservicebyVNETD on (host) on port (vnetd_configured_port_number). Verifique o log arquivo para more details.", - "first_action": "On UNIX: Compare o VNETD entry in o /etc/services arquivo com o", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ On UNIX: Compare o VNETD entry in o /etc/services arquivo com o\nVNETD_PORT entry in /usr/openv/java/nbj.conf\nOn Windows: Compare o VNETD entry com o VNETD_PORT entry in o\ninstall_path\\java\\setconf.bat arquivo.\nThese entradas must match.\n■ Garanta que não other application uses o port que está configurado para VNETD." + "desc": "CannotconnecttotheNetBackupJavaauthenticationservicebyVNETD on (host) on port (vnetd_configured_port_number). Check the log file for more details.", + "first_action": "On UNIX: Compare the VNETD entry in the /etc/services file with the", + "full_action": "Do the following, as appropriate:\n■ On UNIX: Compare the VNETD entry in the /etc/services file with the\nVNETD_PORT entry in /usr/openv/java/nbj.conf\nOn Windows: Compare the VNETD entry with the VNETD_PORT entry in the\ninstall_path\\java\\setconf.bat file.\nThese entries must match.\n■ Ensure that no other application uses the port that is configured for VNETD." }, "526": { "code": 526, - "desc": "Bpjava authentication service conexão falhou", - "first_action": "If o target servidor está executando um inválido version de NetBackup, o Java GUI", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ If o target servidor está executando um inválido version de NetBackup, o Java GUI\nattempts um further conexão por o VNETD port 13724. Não ação está requerido.\n■ Verifique que o PBX service ou daemon has been started on o servidor e que\nNetBackup services estão executando.\n■ Verifique iftheJava GUIproperties(java/nbj.conf) have been setup toconnect\nto um PBX port other than 1556." + "desc": "Bpjava authentication service connection failed", + "first_action": "If the target server is running an invalid version of NetBackup, the Java GUI", + "full_action": "Do the following, as appropriate:\n■ If the target server is running an invalid version of NetBackup, the Java GUI\nattempts a further connection by the VNETD port 13724. No action is required.\n■ Check that the PBX service or daemon has been started on the server and that\nNetBackup services are running.\n■ Check iftheJava GUIproperties(java/nbj.conf) have been setup toconnect\nto a PBX port other than 1556." }, "527": { "code": 527, - "desc": "Bpjava usuário service conexão if conexão to pbx on port 1556 fails", - "first_action": "Verifique que o PBX service ou daemon has been started on o servidor e que", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Verifique que o PBX service ou daemon has been started on o servidor e que\nNetBackup services estão executando.\n■ If o target servidor está executando um inválido version de NetBackup, o Java GUI\nattempts um further conexão por o VNETD port 13724. Não ação está requerido.\n■ CheckiftheJavaGUIproperties(java/nbj.conf)havebeenmodifiedtoattempt\num PBX port other than 1556." + "desc": "Bpjava user service connection if connection to pbx on port 1556 fails", + "first_action": "Check that the PBX service or daemon has been started on the server and that", + "full_action": "Do the following, as appropriate:\n■ Check that the PBX service or daemon has been started on the server and that\nNetBackup services are running.\n■ If the target server is running an invalid version of NetBackup, the Java GUI\nattempts a further connection by the VNETD port 13724. No action is required.\n■ CheckiftheJavaGUIproperties(java/nbj.conf)havebeenmodifiedtoattempt\na PBX port other than 1556." }, "537": { "code": 537, - "desc": "ConnectiontotheNetBackupdatabasewasnotsuccessful.Ensurethat o banco de dados service está executando.", - "first_action": "Start o NetBackup banco de dados service.", - "full_action": "Start o NetBackup banco de dados service." + "desc": "ConnectiontotheNetBackupdatabasewasnotsuccessful.Ensurethat the database service is running.", + "first_action": "Start the NetBackup database service.", + "full_action": "Start the NetBackup database service." }, "538": { "code": 538, - "desc": "Não foi possível to login", - "first_action": "Synchronize o time on both hosts ou decrease o", - "full_action": "Synchronize o time on both hosts ou decrease o\ndifference in time to less than 24 hours." + "desc": "Unable to login", + "first_action": "Synchronize the time on both hosts or decrease the", + "full_action": "Synchronize the time on both hosts or decrease the\ndifference in time to less than 24 hours." }, "552": { "code": 552, - "desc": "O Certificate Revocation List (CRL) could não be downloaded e, therefore,thecertificaterevocationstatuscouldnotbeverified.Formoreinformation, veja o NetBackup logs.", - "first_action": "Para more informação, veja o bpjava logs.", - "full_action": "Para more informação, veja o bpjava logs." + "desc": "The Certificate Revocation List (CRL) could not be downloaded and, therefore,thecertificaterevocationstatuscouldnotbeverified.Formoreinformation, see the NetBackup logs.", + "first_action": "For more information, see the bpjava logs.", + "full_action": "For more information, see the bpjava logs." }, "555": { "code": 555, - "desc": "Não foi possível to logon.", - "first_action": "Use another authentication mechanism. Para example,", - "full_action": "Use another authentication mechanism. Para example,\nauthenticate com either um usuário name e password ou com o Windows Active\nDiretório logon credentials." + "desc": "Unable to logon.", + "first_action": "Use another authentication mechanism. For example,", + "full_action": "Use another authentication mechanism. For example,\nauthenticate with either a user name and password or with the Windows Active\nDirectory logon credentials." }, "600": { "code": 600, - "desc": "Um exception condition ocorreu", + "desc": "An exception condition occurred", "first_action": "Contactcustomersupportandsendtheappropriatedebug", - "full_action": "Contactcustomersupportandsendtheappropriatedebug\nlogs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "full_action": "Contactcustomersupportandsendtheappropriatedebug\nlogs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "601": { "code": 601, - "desc": "Não foi possível to abrir listen socket", + "desc": "Unable to open listen socket", "first_action": "ChecktheOSerrorthatwasreportedintheerrormessage,", - "full_action": "ChecktheOSerrorthatwasreportedintheerrormessage,\nwhich bpsynth logged in o NetBackup erro log. This erro helps to diagnose o\nproblem.EnsurethatthebpsynthbinarymatchestheinstalledNetBackupversion.\nRetry o synthetic backup job. If o problema persists, contate customer support\ne provide o appropriate logs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "full_action": "ChecktheOSerrorthatwasreportedintheerrormessage,\nwhich bpsynth logged in the NetBackup error log. This error helps to diagnose the\nproblem.EnsurethatthebpsynthbinarymatchestheinstalledNetBackupversion.\nRetry the synthetic backup job. If the problem persists, contact customer support\nand provide the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "602": { "code": 602, - "desc": "Não é possível set non-blocking mode on o listen socket", + "desc": "Cannot set non-blocking mode on the listen socket", "first_action": "ChecktheOSerrorthatwasreportedintheerrormessage,", - "full_action": "ChecktheOSerrorthatwasreportedintheerrormessage,\nwhich foi logged in o NetBackup erro log. O erro helps to diagnose o\nproblem.EnsurethatthebpsynthbinarymatchestheinstalledNetBackupversion.\nIf o condition persists, contate customer support e send o appropriate logs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "full_action": "ChecktheOSerrorthatwasreportedintheerrormessage,\nwhich was logged in the NetBackup error log. The error helps to diagnose the\nproblem.EnsurethatthebpsynthbinarymatchestheinstalledNetBackupversion.\nIf the condition persists, contact customer support and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "603": { "code": 603, - "desc": "Não é possível register handler para accepting new connections", - "first_action": "Garanta que o bpsynth binary matches o instalado", - "full_action": "Garanta que o bpsynth binary matches o instalado\nNetBackup version. Retry o synthetic backup job. If o problema persists, contate\ncustomer support e send o appropriate logs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "desc": "Cannot register handler for accepting new connections", + "first_action": "Ensure that the bpsynth binary matches the installed", + "full_action": "Ensure that the bpsynth binary matches the installed\nNetBackup version. Retry the synthetic backup job. If the problem persists, contact\ncustomer support and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "604": { "code": 604, - "desc": "Não target armazenamento unidade specified para o new job", - "first_action": "Retry o synthetic backup job. If o problema persists,", - "full_action": "Retry o synthetic backup job. If o problema persists,\ncontate customer support e provide appropriate logs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "desc": "No target storage unit specified for the new job", + "first_action": "Retry the synthetic backup job. If the problem persists,", + "full_action": "Retry the synthetic backup job. If the problem persists,\ncontact customer support and provide appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "605": { "code": 605, - "desc": "Received erro notification para o job", - "first_action": "Submit um problema relatório along com o appropriate logs.", - "full_action": "Submit um problema relatório along com o appropriate logs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "desc": "Received error notification for the job", + "first_action": "Submit a problem report along with the appropriate logs.", + "full_action": "Submit a problem report along with the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "606": { "code": 606, - "desc": "Não robot on which o mídia can be ler", - "first_action": "Contate customer support e provide o appropriate", - "full_action": "Contate customer support e provide o appropriate\nlogs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "desc": "No robot on which the media can be read", + "first_action": "Contact customer support and provide the appropriate", + "full_action": "Contact customer support and provide the appropriate\nlogs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "607": { "code": 607, - "desc": "Não images foram found to synthesize", - "first_action": "Garanta que um synthetic cheio backup has one cheio image", - "full_action": "Garanta que um synthetic cheio backup has one cheio image\n(real ou synthetic) e one ou more subsequent incremental images (differential ou\ncumulative) to synthesize. Para um cumulative synthetic backup, there must be two\nou more incremental (differential ou cumulative) images to synthesize. Adjust seu\nschedulessotheappropriatebackupjobscompletesuccessfullybeforethesynthetic\njob está run. O scheduler does não retry um synthetic backup job que fails com this\nerro code." + "desc": "No images were found to synthesize", + "first_action": "Ensure that a synthetic full backup has one full image", + "full_action": "Ensure that a synthetic full backup has one full image\n(real or synthetic) and one or more subsequent incremental images (differential or\ncumulative) to synthesize. For a cumulative synthetic backup, there must be two\nor more incremental (differential or cumulative) images to synthesize. Adjust your\nschedulessotheappropriatebackupjobscompletesuccessfullybeforethesynthetic\njob is run. The scheduler does not retry a synthetic backup job that fails with this\nerror code." }, "608": { "code": 608, - "desc": "Armazenamento unidade query falhou", + "desc": "Storage unit query failed", "first_action": "Verifythatthebpdbmprocessisrunningandthatnoerrors", - "full_action": "Verifythatthebpdbmprocessisrunningandthatnoerrors\nforam logged to o NetBackup erro log. Restart o bpdbm process (on UNIX), ou\no NetBackup Banco de dados Manager Service (on Windows) e retry o synthetic\nbackup job. If o problema persists, contate customer support e send o\nappropriate logs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "full_action": "Verifythatthebpdbmprocessisrunningandthatnoerrors\nwere logged to the NetBackup error log. Restart the bpdbm process (on UNIX), or\nthe NetBackup Database Manager Service (on Windows) and retry the synthetic\nbackup job. If the problem persists, contact customer support and send the\nappropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "609": { "code": 609, - "desc": "Reader falhou", + "desc": "Reader failed", "first_action": "SeetheNetBackuperrorlogfortheerrorsthatthebpsynth", - "full_action": "SeetheNetBackuperrorlogfortheerrorsthatthebpsynth\nandbptmorbpdmreaderlogged.Theerrormessageshouldcontaintheactualerror\nque o bptm ou o bpdm reader relatórios.\nVeja o NetBackup Troubleshooting Guide para informação on o erro que o\nbptm ou o bpdm reader relatórios. O mídia may não be present ou está defective ou\no drive que foi used para reading o mídia está defective. If o problema persists,\ncontate customer support e send o appropriate logs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "full_action": "SeetheNetBackuperrorlogfortheerrorsthatthebpsynth\nandbptmorbpdmreaderlogged.Theerrormessageshouldcontaintheactualerror\nthat the bptm or the bpdm reader reports.\nSee the NetBackup Troubleshooting Guide for information on the error that the\nbptm or the bpdm reader reports. The media may not be present or is defective or\nthe drive that was used for reading the media is defective. If the problem persists,\ncontact customer support and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "610": { "code": 610, - "desc": "Endpoint terminated com um erro", - "first_action": "Review o errors in o NetBackup erro log que o", - "full_action": "Review o errors in o NetBackup erro log que o\nseguinte processos logged: bpsynth e bptm ou bpdm. Refer to o debug logs\npara these processos para more informação. O conexão may have broken due to\nthefollowing:anerrorconditionthatthebptmorthebpdmprocessdetectsornetwork\nproblemsbetweenthemasterandthemediaserver.Checkthenetworkconnectivity\nbetweenthemasterandthemediaserver.Retrythejobandiftheproblempersists,\ncontate customer support, e send o appropriate logs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "desc": "Endpoint terminated with an error", + "first_action": "Review the errors in the NetBackup error log that the", + "full_action": "Review the errors in the NetBackup error log that the\nfollowing processes logged: bpsynth and bptm or bpdm. Refer to the debug logs\nfor these processes for more information. The connection may have broken due to\nthefollowing:anerrorconditionthatthebptmorthebpdmprocessdetectsornetwork\nproblemsbetweenthemasterandthemediaserver.Checkthenetworkconnectivity\nbetweenthemasterandthemediaserver.Retrythejobandiftheproblempersists,\ncontact customer support, and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "611": { "code": 611, - "desc": "Não conexão to reader", + "desc": "No connection to reader", "first_action": "Thiserrorshouldnotoccur.Submitaproblemreportalong", - "full_action": "Thiserrorshouldnotoccur.Submitaproblemreportalong\ncom o appropriate logs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "full_action": "Thiserrorshouldnotoccur.Submitaproblemreportalong\nwith the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "612": { "code": 612, - "desc": "Não é possível send extents to bpsynth", - "first_action": "Submit um problema relatório along com o appropriate logs.", - "full_action": "Submit um problema relatório along com o appropriate logs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "desc": "Cannot send extents to bpsynth", + "first_action": "Submit a problem report along with the appropriate logs.", + "full_action": "Submit a problem report along with the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "613": { "code": 613, - "desc": "Não é possível conectar to ler mídia servidor", + "desc": "Cannot connect to read media server", "first_action": "Ensurethatnetworkconnectivityexistsbetweenthemaster", - "full_action": "Ensurethatnetworkconnectivityexistsbetweenthemaster\nservidor e o specified mídia servidor. Examine o NetBackup erro log para qualquer\nerro messages que bpsynth logged. Para more informação, refer to o debug logs\npara bpsynth on o master servidor e bpcd e bptm ou bpdm on o mídia servidor.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "full_action": "Ensurethatnetworkconnectivityexistsbetweenthemaster\nserver and the specified media server. Examine the NetBackup error log for any\nerror messages that bpsynth logged. For more information, refer to the debug logs\nfor bpsynth on the master server and bpcd and bptm or bpdm on the media server.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "614": { "code": 614, - "desc": "Não é possível start reader on o mídia servidor", - "first_action": "Examine o NetBackup erro log para qualquer errors que bpsynth logged. Para more", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Examine o NetBackup erro log para qualquer errors que bpsynth logged. Para more\ninformação, refer to o seguinte debug logs: para bpsynth on o master servidor\ne para bpcd e bptm ou bpdm on o mídia servidor. Garanta que o bptm ou o\nbpdm binaries on o mídia servidor estão executable e estão não corrupt. Try\nexecutando bptm ou bpdm commands locally on o mídia servidor to garanta que o\nbinary está executable e não corrupt. Para instance, you can run o seguinte\ncomando\n/bp/bin/bptm -count -rn 0 -rt 8\nwhererobotnumberis0andtherobottypeis8.Therobottypethatcorresponds\nto o robot number can be taken from o comando line que está logged in o\ndebug log para bptm. This comando displays o counts para o up, shared, e\nassigned drives in o robot.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "desc": "Cannot start reader on the media server", + "first_action": "Examine the NetBackup error log for any errors that bpsynth logged. For more", + "full_action": "Do the following, as appropriate:\n■ Examine the NetBackup error log for any errors that bpsynth logged. For more\ninformation, refer to the following debug logs: for bpsynth on the master server\nand for bpcd and bptm or bpdm on the media server. Ensure that the bptm or the\nbpdm binaries on the media server are executable and are not corrupt. Try\nrunning bptm or bpdm commands locally on the media server to ensure that the\nbinary is executable and not corrupt. For instance, you can run the following\ncommand\n/bp/bin/bptm -count -rn 0 -rt 8\nwhererobotnumberis0andtherobottypeis8.Therobottypethatcorresponds\nto the robot number can be taken from the command line that is logged in the\ndebug log for bptm. This command displays the counts for the up, shared, and\nassigned drives in the robot.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "615": { "code": 615, - "desc": "Internal erro 615", - "first_action": "Submit um problema relatório along com o appropriate logs.", - "full_action": "Submit um problema relatório along com o appropriate logs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "desc": "Internal error 615", + "first_action": "Submit a problem report along with the appropriate logs.", + "full_action": "Submit a problem report along with the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "616": { "code": 616, - "desc": "Internal erro 616", - "first_action": "Submit um problema relatório along com o appropriate logs.", - "full_action": "Submit um problema relatório along com o appropriate logs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "desc": "Internal error 616", + "first_action": "Submit a problem report along with the appropriate logs.", + "full_action": "Submit a problem report along with the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "617": { "code": 617, - "desc": "Não drives disponível to start o reader process", - "first_action": "Garanta que sufficient drives estão disponível before you", - "full_action": "Garanta que sufficient drives estão disponível before you\nrestart o job." + "desc": "No drives available to start the reader process", + "first_action": "Ensure that sufficient drives are available before you", + "full_action": "Ensure that sufficient drives are available before you\nrestart the job." }, "618": { "code": 618, - "desc": "Internal erro 618", - "first_action": "Contate customer support e send o appropriate logs.", - "full_action": "Contate customer support e send o appropriate logs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "desc": "Internal error 618", + "first_action": "Contact customer support and send the appropriate logs.", + "full_action": "Contact customer support and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "619": { "code": 619, - "desc": "Internal erro 619 NetBackup status codes 298 NetBackup status codes", - "first_action": "Contate customer support e send o appropriate logs.", - "full_action": "Contate customer support e send o appropriate logs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "desc": "Internal error 619 NetBackup status codes 298 NetBackup status codes", + "first_action": "Contact customer support and send the appropriate logs.", + "full_action": "Contact customer support and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "620": { "code": 620, - "desc": "Internal erro 620", - "first_action": "Contate customer support e send o appropriate logs.", - "full_action": "Contate customer support e send o appropriate logs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "desc": "Internal error 620", + "first_action": "Contact customer support and send the appropriate logs.", + "full_action": "Contact customer support and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "621": { "code": 621, - "desc": "Não foi possível to conectar to bpcoord", - "first_action": "Submit um problema relatório along com o appropriate logs.", - "full_action": "Submit um problema relatório along com o appropriate logs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "desc": "Unable to connect to bpcoord", + "first_action": "Submit a problem report along with the appropriate logs.", + "full_action": "Submit a problem report along with the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "622": { "code": 622, - "desc": "Conexão to o peer process does não exist", - "first_action": "Contate customer support e send o appropriate logs.", - "full_action": "Contate customer support e send o appropriate logs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "desc": "Connection to the peer process does not exist", + "first_action": "Contact customer support and send the appropriate logs.", + "full_action": "Contact customer support and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "623": { "code": 623, - "desc": "Execution de um comando in um forked process falhou", + "desc": "Execution of a command in a forked process failed", "first_action": "Retrythejobandiftheproblempersists,contactcustomer", - "full_action": "Retrythejobandiftheproblempersists,contactcustomer\nsupport e send o appropriate logs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "full_action": "Retrythejobandiftheproblempersists,contactcustomer\nsupport and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "624": { "code": 624, - "desc": "Unabletosendastartcommandtoareaderorawriterprocessonmedia servidor", + "desc": "Unabletosendastartcommandtoareaderorawriterprocessonmedia server", "first_action": "Ensurethatnetworkconnectivityexistsbetweenthemaster", - "full_action": "Ensurethatnetworkconnectivityexistsbetweenthemaster\ne o mídia servidor. Look para additional erro messages in o NetBackup erro\nlog. More detailed informação está present in o debug logs para bpsynth (on master\nservidor) e bptm ou bpdm on o mídia servidor. If o problema persists, contate\ncustomer support e send o appropriate logs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "full_action": "Ensurethatnetworkconnectivityexistsbetweenthemaster\nand the media server. Look for additional error messages in the NetBackup error\nlog. More detailed information is present in the debug logs for bpsynth (on master\nserver) and bptm or bpdm on the media server. If the problem persists, contact\ncustomer support and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "625": { "code": 625, - "desc": "Data marshalling erro", - "first_action": "Contate customer support e send o appropriate logs.", - "full_action": "Contate customer support e send o appropriate logs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "desc": "Data marshalling error", + "first_action": "Contact customer support and send the appropriate logs.", + "full_action": "Contact customer support and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "626": { "code": 626, - "desc": "Data un-marshalling erro", - "first_action": "Contate customer support e send o appropriate logs.", - "full_action": "Contate customer support e send o appropriate logs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "desc": "Data un-marshalling error", + "first_action": "Contact customer support and send the appropriate logs.", + "full_action": "Contact customer support and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "627": { "code": 627, "desc": "Unexpected message received from bpsynth", - "first_action": "Submit um problema relatório along com o appropriate logs.", - "full_action": "Submit um problema relatório along com o appropriate logs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "first_action": "Submit a problem report along with the appropriate logs.", + "full_action": "Submit a problem report along with the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "628": { "code": 628, "desc": "Insufficient data received", - "first_action": "If this erro causes o bpsynth binary to hang ou", - "full_action": "If this erro causes o bpsynth binary to hang ou\nmalfunction, contate customer support e send o appropriate logs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "first_action": "If this error causes the bpsynth binary to hang or", + "full_action": "If this error causes the bpsynth binary to hang or\nmalfunction, contact customer support and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "629": { "code": 629, - "desc": "Não message foi received from bptm", - "first_action": "Look para additional erro messages in o seguinte logs:", - "full_action": "Look para additional erro messages in o seguinte logs:\no NetBackup erro log e o debug logs para bpsynth on o master servidor e\nbptm on o mídia servidor. Um system condition (insufficient memória, arquivo system cheio,\ninsufficient swap space) on o mídia servidor may prevent o bptm process from\nsending o response. Verifique o rede connectivity between o master e o\nmídia servidor. If não explanation está found para o falha e o problema persists,\ncontate customer support e send o appropriate logs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "desc": "No message was received from bptm", + "first_action": "Look for additional error messages in the following logs:", + "full_action": "Look for additional error messages in the following logs:\nthe NetBackup error log and the debug logs for bpsynth on the master server and\nbptm on the media server. A system condition (insufficient memory, file system full,\ninsufficient swap space) on the media server may prevent the bptm process from\nsending the response. Verify the network connectivity between the master and the\nmedia server. If no explanation is found for the failure and the problem persists,\ncontact customer support and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "630": { "code": 630, - "desc": "Unexpected message foi received from bptm", - "first_action": "Contate customer support e send o appropriate logs.", - "full_action": "Contate customer support e send o appropriate logs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "desc": "Unexpected message was received from bptm", + "first_action": "Contact customer support and send the appropriate logs.", + "full_action": "Contact customer support and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "631": { "code": 631, - "desc": "Received um erro from bptm request to suspend mídia", - "first_action": "Examine o bptm debug log para more informação on o", - "full_action": "Examine o bptm debug log para more informação on o\nreasonforthesuspendfailure.Thebpsynthprocessignoresthiserrorandcontinues\nto process. It has o potential to fail later if o mídia com o images to be ler\ngets assigned to another backup ou restauração job. If o synthetic backup job fails, fix\no condition que lead to o suspend falha e retry o job." + "desc": "Received an error from bptm request to suspend media", + "first_action": "Examine the bptm debug log for more information on the", + "full_action": "Examine the bptm debug log for more information on the\nreasonforthesuspendfailure.Thebpsynthprocessignoresthiserrorandcontinues\nto process. It has the potential to fail later if the media with the images to be read\ngets assigned to another backup or restore job. If the synthetic backup job fails, fix\nthe condition that lead to the suspend failure and retry the job." }, "632": { "code": 632, - "desc": "Received um erro from bptm request to un-suspend mídia", - "first_action": "Look at o debug log para o bptm process on o mídia", - "full_action": "Look at o debug log para o bptm process on o mídia\nservidor para um explanation de o un-suspend falha e o mídia ID. Try to\nun-suspend o tape manually por usando o bpmedia comando." + "desc": "Received an error from bptm request to un-suspend media", + "first_action": "Look at the debug log for the bptm process on the media", + "full_action": "Look at the debug log for the bptm process on the media\nserver for an explanation of the un-suspend failure and the media ID. Try to\nun-suspend the tape manually by using the bpmedia command." }, "633": { "code": 633, - "desc": "Não foi possível to listen e register service por vnetd", - "first_action": "Submit um problema relatório along com o appropriate logs.", - "full_action": "Submit um problema relatório along com o appropriate logs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "desc": "Unable to listen and register service by vnetd", + "first_action": "Submit a problem report along with the appropriate logs.", + "full_action": "Submit a problem report along with the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "634": { "code": 634, - "desc": "Não drives disponível to start o writer process", - "first_action": "Garanta que o target armazenamento unidade que está configurado para", - "full_action": "Garanta que o target armazenamento unidade que está configurado para\no synthetic backup schedule has um disponível drive to gravar o synthetic backup\nimage." + "desc": "No drives available to start the writer process", + "first_action": "Ensure that the target storage unit that is configured for", + "full_action": "Ensure that the target storage unit that is configured for\nthe synthetic backup schedule has an available drive to write the synthetic backup\nimage." }, "635": { "code": 635, - "desc": "Não foi possível to register handle com o reactor", - "first_action": "Examine NetBackup erro log para qualquer errors que foram", - "full_action": "Examine NetBackup erro log para qualquer errors que foram\nlogged para o job. Refer to o debug logs para bpsynth para more informação. Retry\no synthetic backup job. If o problema persists, contate customer support e\nsend o appropriate logs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "desc": "Unable to register handle with the reactor", + "first_action": "Examine NetBackup error log for any errors that were", + "full_action": "Examine NetBackup error log for any errors that were\nlogged for the job. Refer to the debug logs for bpsynth for more information. Retry\nthe synthetic backup job. If the problem persists, contact customer support and\nsend the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "636": { "code": 636, - "desc": "Ler from input socket falhou", - "first_action": "O bpsynth process encontrado um erro while reading", - "full_action": "O bpsynth process encontrado um erro while reading\nfrom um input socket. O socket may be between bpsynth e bptm ou bpdm.\nO errno que foi logged to o NetBackup erro log indicates o reason para o\nfalha. Para more informação, refer to o seguinte: o debug log para bpsynth (on\no master servidor) e para o bptm ou o bpdm reader ou writer processos (on o\nmídia servidor). Verifique o rede connectivity between o master e o mídia\nservidor. Rerun o synthetic backup job. If o problema persists, contate customer\nsupport e send o appropriate logs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "desc": "Read from input socket failed", + "first_action": "The bpsynth process encountered an error while reading", + "full_action": "The bpsynth process encountered an error while reading\nfrom an input socket. The socket may be between bpsynth and bptm or bpdm.\nThe errno that was logged to the NetBackup error log indicates the reason for the\nfailure. For more information, refer to the following: the debug log for bpsynth (on\nthe master server) and for the bptm or the bpdm reader or writer processes (on the\nmedia server). Check the network connectivity between the master and the media\nserver. Rerun the synthetic backup job. If the problem persists, contact customer\nsupport and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "637": { "code": 637, - "desc": "Gravar on output socket falhou", - "first_action": "O bpsynth process encontrado um erro while writing", - "full_action": "O bpsynth process encontrado um erro while writing\nto um output socket. O socket está between bpsynth e bptm ou bpdm.\nTheerrnothatloggedtotheNetBackuperrorlogindicatesthereasonforthefailure.\nPara more informação, refer to o seguinte: o debug log para bpsynth (on o\nmaster servidor) e para o bptm ou o bpdm reader ou writer process (on o mídia\nservidor). Verifique o connectivity between o master e o mídia servidor. Retry\no synthetic backup job. If o problema persists, contate customer support e\nsend o appropriate logs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "desc": "Write on output socket failed", + "first_action": "The bpsynth process encountered an error while writing", + "full_action": "The bpsynth process encountered an error while writing\nto an output socket. The socket is between bpsynth and bptm or bpdm.\nTheerrnothatloggedtotheNetBackuperrorlogindicatesthereasonforthefailure.\nFor more information, refer to the following: the debug log for bpsynth (on the\nmaster server) and for the bptm or the bpdm reader or writer process (on the media\nserver). Check the connectivity between the master and the media server. Retry\nthe synthetic backup job. If the problem persists, contact customer support and\nsend the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "638": { "code": 638, - "desc": "Inválido arguments specified", + "desc": "Invalid arguments specified", "first_action": "Help)forthecorrectargumentspecification.Ifthesyntheticbackupjobwasstarted", - "full_action": "Refer to o bpsynth comando line arguments (por usando\n-help)forthecorrectargumentspecification.Ifthesyntheticbackupjobwasstarted\nmanually por o comando line, correct o arguments to bpsynth e rerun o\njob. If o synthetic backup job foi scheduled ou started com o console, garanta\nque o bpsynth e o nbjm binaries match o instalado NetBackup version." + "full_action": "Refer to the bpsynth command line arguments (by using\n-help)forthecorrectargumentspecification.Ifthesyntheticbackupjobwasstarted\nmanually by the command line, correct the arguments to bpsynth and rerun the\njob. If the synthetic backup job was scheduled or started with the console, ensure\nthat the bpsynth and the nbjm binaries match the installed NetBackup version." }, "639": { "code": 639, - "desc": "Specified policy does não exist", - "first_action": "O synthetic backup job foi scheduled ou started por usando o NetBackup", - "full_action": "If bpsynth está initiated com o comando line, rerun o\ncommandforanexistingpolicy.Iftheproblempersistsafteryouverifythefollowing,\ncontate customer support e send o appropriate logs:\n■ O synthetic backup job foi scheduled ou started por usando o NetBackup\nAdministration Console (manual start).\n■ O policy exists in o bppllist comando configuration.\n■ Verifique o logs para nbjm, which uses unified logging (OID 117).\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "desc": "Specified policy does not exist", + "first_action": "The synthetic backup job was scheduled or started by using the NetBackup", + "full_action": "If bpsynth is initiated with the command line, rerun the\ncommandforanexistingpolicy.Iftheproblempersistsafteryouverifythefollowing,\ncontact customer support and send the appropriate logs:\n■ The synthetic backup job was scheduled or started by using the NetBackup\nAdministration Console (manual start).\n■ The policy exists in the bppllist command configuration.\n■ Check the logs for nbjm, which uses unified logging (OID 117).\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "640": { "code": 640, - "desc": "Specified schedule foi não found", - "first_action": "If o comando line initiated bpsynth, do o seguinte:", - "full_action": "If o comando line initiated bpsynth, do o seguinte:\nrerun o comando com o correct synthetic schedule label defined in o policy\nde o synthetic backup job to be run. If o synthetic backup job foi scheduled ou\nstarted com o NetBackup Administration Console, define um new schedule in\no policy e retry o job. If o problema persists, contate customer support e\nsend o appropriate logs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "desc": "Specified schedule was not found", + "first_action": "If the command line initiated bpsynth, do the following:", + "full_action": "If the command line initiated bpsynth, do the following:\nrerun the command with the correct synthetic schedule label defined in the policy\nof the synthetic backup job to be run. If the synthetic backup job was scheduled or\nstarted with the NetBackup Administration Console, define a new schedule in\nthe policy and retry the job. If the problem persists, contact customer support and\nsend the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "641": { "code": 641, - "desc": "Inválido mídia type specified in o armazenamento unidade", - "first_action": "Garanta que o target armazenamento unidade que foi configurado", - "full_action": "Garanta que o target armazenamento unidade que foi configurado\npara synthetic backup está um disco, disco staging, ou Mídia Manager type (não NDMP\ntype). Rerun synthetic backup com o appropriate armazenamento unidade." + "desc": "Invalid media type specified in the storage unit", + "first_action": "Ensure that the target storage unit that was configured", + "full_action": "Ensure that the target storage unit that was configured\nfor synthetic backup is a disk, disk staging, or Media Manager type (not NDMP\ntype). Rerun synthetic backup with the appropriate storage unit." }, "642": { "code": 642, - "desc": "Duplicate backup images foram found", - "first_action": "Contate customer support e send o appropriate logs.", - "full_action": "Contate customer support e send o appropriate logs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "desc": "Duplicate backup images were found", + "first_action": "Contact customer support and send the appropriate logs.", + "full_action": "Contact customer support and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "643": { "code": 643, "desc": "Unexpected message received from bpcoord", - "first_action": "Submit um problema relatório along com o appropriate logs.", - "full_action": "Submit um problema relatório along com o appropriate logs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "first_action": "Submit a problem report along with the appropriate logs.", + "full_action": "Submit a problem report along with the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "644": { "code": 644, - "desc": "Extent directive contained um unknown mídia ID", - "first_action": "Contate customer support e send o appropriate logs.", - "full_action": "Contate customer support e send o appropriate logs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "desc": "Extent directive contained an unknown media ID", + "first_action": "Contact customer support and send the appropriate logs.", + "full_action": "Contact customer support and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "645": { "code": 645, - "desc": "Não foi possível to start o writer on o mídia servidor", + "desc": "Unable to start the writer on the media server", "first_action": "ExaminetheNetBackuperrorlogforanymessagesthatbpsynthlogged.Formore", - "full_action": "ExaminetheNetBackuperrorlogforanymessagesthatbpsynthlogged.Formore\ninformação, refer to o seguinte: o debug logs para bpsynth on o master servidor\ne bpcd e bptm ou bpdm on o mídia servidor. Garanta que o bptm ou o bpdm\nbinaries on o mídia servidor estão executable e estão não corrupt. Try to run o\nbptm ou o bpdm commands locally on o mídia servidor to garanta que o binary\nestá executable e não corrupt. Para instance, you can run o seguinte comando:\ninstall_path/netbackup/bin/bptm -count -rn 0 -rt 8\nonde robot number está 0 e robot type está 8. O robot type que corresponds to\no robot number can be taken from o comando line que está logged in o debug\nlog para bptm. This comando displays o counts para o up, shared, e assigned\ndrives in o robot. In case o synthetic image está to be written to um disco armazenamento\nunidade, verifique o bpdm binary por executando o seguinte comando:\ninstall_path/netbackup/bin/bpdm\nIt should print o seguinte:\nbpdm: mídia manager operation não specified\nRetry o synthetic backup job. If o problema persists, contate customer support\ne send o appropriate logs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "full_action": "ExaminetheNetBackuperrorlogforanymessagesthatbpsynthlogged.Formore\ninformation, refer to the following: the debug logs for bpsynth on the master server\nand bpcd and bptm or bpdm on the media server. Ensure that the bptm or the bpdm\nbinaries on the media server are executable and are not corrupt. Try to run the\nbptm or the bpdm commands locally on the media server to ensure that the binary\nis executable and not corrupt. For instance, you can run the following command:\ninstall_path/netbackup/bin/bptm -count -rn 0 -rt 8\nwhere robot number is 0 and robot type is 8. The robot type that corresponds to\nthe robot number can be taken from the command line that is logged in the debug\nlog for bptm. This command displays the counts for the up, shared, and assigned\ndrives in the robot. In case the synthetic image is to be written to a disk storage\nunit, verify the bpdm binary by running the following command:\ninstall_path/netbackup/bin/bpdm\nIt should print the following:\nbpdm: media manager operation not specified\nRetry the synthetic backup job. If the problem persists, contact customer support\nand send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "646": { "code": 646, - "desc": "Não foi possível to get o address de o local listen socket", - "first_action": "Rerun o synthetic backup job. If o problema persists,", - "full_action": "Rerun o synthetic backup job. If o problema persists,\ncontate customer support e send o appropriate logs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "desc": "Unable to get the address of the local listen socket", + "first_action": "Rerun the synthetic backup job. If the problem persists,", + "full_action": "Rerun the synthetic backup job. If the problem persists,\ncontact customer support and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "647": { "code": 647, - "desc": "Validation de synthetic image falhou", - "first_action": "This erro may indicate um problema in o synthetic backup", - "full_action": "This erro may indicate um problema in o synthetic backup\nprocess. Examine o NetBackup erro log para qualquer messages que o seguinte\nprocessos logged: bpsynth e bptm ou bpdm. Look at o debug logs para these\nprocessos para additional informação. If you não é possível resolve o problema, contate\ncustomer support e send o appropriate logs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "desc": "Validation of synthetic image failed", + "first_action": "This error may indicate a problem in the synthetic backup", + "full_action": "This error may indicate a problem in the synthetic backup\nprocess. Examine the NetBackup error log for any messages that the following\nprocesses logged: bpsynth and bptm or bpdm. Look at the debug logs for these\nprocesses for additional information. If you cannot resolve the problem, contact\ncustomer support and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "648": { "code": 648, - "desc": "Não foi possível to send extent message to BPXM", - "first_action": "This erro indicates um communication problema between", - "full_action": "This erro indicates um communication problema between\nbpsynth e o bptm ou o bpdm reader process on o mídia servidor. Garanta que\no mídia servidor está accessible e que o bptm ou o bpdm process está executando on\no mídia servidor. Examine o NetBackup erro log para qualquer errors que o seguinte\nlogged: bpsynth (on o master servidor) e o bptm ou o bpdm reader process\n(on o mídia servidor). Examine o debug logs para bpsynth e bptm ou bpdm para\nadditional informação. Rerun o synthetic backup job. If o problema persists,\ncontate customer support e send o appropriate logs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "desc": "Unable to send extent message to BPXM", + "first_action": "This error indicates a communication problem between", + "full_action": "This error indicates a communication problem between\nbpsynth and the bptm or the bpdm reader process on the media server. Ensure that\nthe media server is accessible and that the bptm or the bpdm process is running on\nthe media server. Examine the NetBackup error log for any errors that the following\nlogged: bpsynth (on the master server) and the bptm or the bpdm reader process\n(on the media server). Examine the debug logs for bpsynth and bptm or bpdm for\nadditional information. Rerun the synthetic backup job. If the problem persists,\ncontact customer support and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "649": { "code": 649, "desc": "Unexpected message received from BPXM", - "first_action": "Submit um problema relatório along com o appropriate logs.", - "full_action": "Submit um problema relatório along com o appropriate logs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "first_action": "Submit a problem report along with the appropriate logs.", + "full_action": "Submit a problem report along with the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "650": { "code": 650, - "desc": "Não foi possível to send extent message to bpcoord", - "first_action": "Submit um problema relatório along com o appropriate logs.", - "full_action": "Submit um problema relatório along com o appropriate logs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "desc": "Unable to send extent message to bpcoord", + "first_action": "Submit a problem report along with the appropriate logs.", + "full_action": "Submit a problem report along with the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "651": { "code": 651, - "desc": "Não foi possível to issue o banco de dados query para policy", - "first_action": "This erro indicates um communication problema between", - "full_action": "This erro indicates um communication problema between\nbpsynth e bpdbm. Garanta que bpdbm está executando e o bpdbm binary matches\no instalado NetBackup version. Examine o NetBackup erro log para qualquer errors\nque bpdbm e bpsynth logged. Examine o debug logs para bpsynth e bpdbm\npara additional informação. Restart o bpdbm process (on UNIX) ou o NetBackup\nBanco de dados Manager Service (on Windows) e rerun o synthetic backup job. If\no problema persists, contate customer support e send o appropriate logs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "desc": "Unable to issue the database query for policy", + "first_action": "This error indicates a communication problem between", + "full_action": "This error indicates a communication problem between\nbpsynth and bpdbm. Ensure that bpdbm is running and the bpdbm binary matches\nthe installed NetBackup version. Examine the NetBackup error log for any errors\nthat bpdbm and bpsynth logged. Examine the debug logs for bpsynth and bpdbm\nfor additional information. Restart the bpdbm process (on UNIX) or the NetBackup\nDatabase Manager Service (on Windows) and rerun the synthetic backup job. If\nthe problem persists, contact customer support and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "652": { "code": 652, - "desc": "Não foi possível to issue o banco de dados query para policy informação", - "first_action": "This erro indicates um communication problema between", - "full_action": "This erro indicates um communication problema between\nbpsynth e bpdbm. Garanta que bpdbm está executando e o bpdbm binary matches\no instalado NetBackup version. Examine o NetBackup erro log para qualquer errors\nque bpdbm e bpsynth logged. Examine o debug logs para bpsynth e bpdbm\npara additional informação. Restart o bpdbm process (on UNIX) ou o NetBackup\nBanco de dados Manager Service (on Windows) e rerun o synthetic backup job. If\no problema persists, contate customer support e send o appropriate logs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "desc": "Unable to issue the database query for policy information", + "first_action": "This error indicates a communication problem between", + "full_action": "This error indicates a communication problem between\nbpsynth and bpdbm. Ensure that bpdbm is running and the bpdbm binary matches\nthe installed NetBackup version. Examine the NetBackup error log for any errors\nthat bpdbm and bpsynth logged. Examine the debug logs for bpsynth and bpdbm\nfor additional information. Restart the bpdbm process (on UNIX) or the NetBackup\nDatabase Manager Service (on Windows) and rerun the synthetic backup job. If\nthe problem persists, contact customer support and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "653": { "code": 653, - "desc": "Não foi possível to send um message to bpccord", - "first_action": "Contate customer support e send o appropriate logs.", - "full_action": "Contate customer support e send o appropriate logs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "desc": "Unable to send a message to bpccord", + "first_action": "Contact customer support and send the appropriate logs.", + "full_action": "Contact customer support and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "654": { "code": 654, - "desc": "Internal erro 654", - "first_action": "Contate customer support e send o appropriate logs.", - "full_action": "Contate customer support e send o appropriate logs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "desc": "Internal error 654", + "first_action": "Contact customer support and send the appropriate logs.", + "full_action": "Contact customer support and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "655": { "code": 655, - "desc": "Não target armazenamento unidade foi specified por comando line", - "first_action": "Rerun bpsynth com o target armazenamento unidade specified por", - "full_action": "Rerun bpsynth com o target armazenamento unidade specified por\no -S option." + "desc": "No target storage unit was specified by command line", + "first_action": "Rerun bpsynth with the target storage unit specified by", + "full_action": "Rerun bpsynth with the target storage unit specified by\nthe -S option." }, "656": { "code": 656, - "desc": "Não foi possível to send start synth message to bpcoord", - "first_action": "Contate customer support e send o appropriate logs.", - "full_action": "Contate customer support e send o appropriate logs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "desc": "Unable to send start synth message to bpcoord", + "first_action": "Contact customer support and send the appropriate logs.", + "full_action": "Contact customer support and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "657": { "code": 657, - "desc": "Não foi possível to accept conexão from o reader", - "first_action": "Examine o NetBackup erro log para qualquer errors que", - "full_action": "Examine o NetBackup erro log para qualquer errors que\nbpsynth e bptm ou o bpdm reader process logged. O message que bpsynth\nlogged includes o erro (errno) reported por o system call. Refer to o debug\nlogs para bpsynth on o master servidor e bptm ou o bpdm process on o mídia\nservers para more informação. Garanta que rede connectivity exists between o\nmaster e o mídia servers. If o problema persists, contate customer support\ne send o appropriate logs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "desc": "Unable to accept connection from the reader", + "first_action": "Examine the NetBackup error log for any errors that", + "full_action": "Examine the NetBackup error log for any errors that\nbpsynth and bptm or the bpdm reader process logged. The message that bpsynth\nlogged includes the error (errno) reported by the system call. Refer to the debug\nlogs for bpsynth on the master server and bptm or the bpdm process on the media\nservers for more information. Ensure that network connectivity exists between the\nmaster and the media servers. If the problem persists, contact customer support\nand send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "658": { "code": 658, - "desc": "Não foi possível to accept conexão from o writer", - "first_action": "Examine o NetBackup erro log para qualquer errors que", - "full_action": "Examine o NetBackup erro log para qualquer errors que\nbpsynthandthebptmorthebpdmwriterprocesslogged.Themessagethatbpsynth\nlogged includes o erro (errno) reported por o system call. Also refer to o\ndebug logs para bpsynth on o master servidor e bptm ou o bpdm process on o\nmediaserverformoreinformation.Ensurethatnetworkconnectivityexistsbetween\nthemasterandthemediaservers.Iftheproblempersists,contactcustomersupport\ne send o appropriate logs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "desc": "Unable to accept connection from the writer", + "first_action": "Examine the NetBackup error log for any errors that", + "full_action": "Examine the NetBackup error log for any errors that\nbpsynthandthebptmorthebpdmwriterprocesslogged.Themessagethatbpsynth\nlogged includes the error (errno) reported by the system call. Also refer to the\ndebug logs for bpsynth on the master server and bptm or the bpdm process on the\nmediaserverformoreinformation.Ensurethatnetworkconnectivityexistsbetween\nthemasterandthemediaservers.Iftheproblempersists,contactcustomersupport\nand send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "659": { "code": 659, - "desc": "Não foi possível to send um message to o writer child process", - "first_action": "Examine o NetBackup erro log para qualquer errors que", - "full_action": "Examine o NetBackup erro log para qualquer errors que\nbpsynth e o bptm ou o bpdm writer process logged. Refer to o seguinte para\nmore informação: o debug logs para bpsynth on o master servidor e o bptm\nou o bpdm process on o mídia servidor. Garanta que rede connectivity exists\nbetweenthemasterandthemediaservers.Iftheproblempersists,contactcustomer\nsupport e send o appropriate logs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "desc": "Unable to send a message to the writer child process", + "first_action": "Examine the NetBackup error log for any errors that", + "full_action": "Examine the NetBackup error log for any errors that\nbpsynth and the bptm or the bpdm writer process logged. Refer to the following for\nmore information: the debug logs for bpsynth on the master server and the bptm\nor the bpdm process on the media server. Ensure that network connectivity exists\nbetweenthemasterandthemediaservers.Iftheproblempersists,contactcustomer\nsupport and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "660": { "code": 660, - "desc": "Um synthetic backup request para mídia resources falhou", - "first_action": "Create logs como explained in o seguinte topic:", - "full_action": "Create logs como explained in o seguinte topic:\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide.\nRerun o job e send o logs to customer support." + "desc": "A synthetic backup request for media resources failed", + "first_action": "Create logs as explained in the following topic:", + "full_action": "Create logs as explained in the following topic:\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide.\nRerun the job and send the logs to customer support." }, "661": { "code": 661, - "desc": "Não foi possível to send exit message to o BPXM reader", - "first_action": "Verifique o rede connectivity between o master e", - "full_action": "Verifique o rede connectivity between o master e\no mídia servidor. Examine o NetBackup erro log para qualquer errors que bpsynth\ne bptm ou o bpdm reader process logged. Examine o debug logs para bpsynth\non o master servidor e bptm ou o bpdm reader process on o mídia servers\nformoredetailedinformation.Iftheproblempersists,contactcustomersupportand\nprovide o appropriate logs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "desc": "Unable to send exit message to the BPXM reader", + "first_action": "Check the network connectivity between the master and", + "full_action": "Check the network connectivity between the master and\nthe media server. Examine the NetBackup error log for any errors that bpsynth\nand bptm or the bpdm reader process logged. Examine the debug logs for bpsynth\non the master server and bptm or the bpdm reader process on the media servers\nformoredetailedinformation.Iftheproblempersists,contactcustomersupportand\nprovide the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "662": { "code": 662, - "desc": "Unknown image referenced in o synth context message from BPXM", - "first_action": "Contate customer support e provide o appropriate", - "full_action": "Contate customer support e provide o appropriate\nlogs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "desc": "Unknown image referenced in the synth context message from BPXM", + "first_action": "Contact customer support and provide the appropriate", + "full_action": "Contact customer support and provide the appropriate\nlogs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "663": { "code": 663, - "desc": "Image does não have um fragment map", - "first_action": "Contate customer support e provide o appropriate", - "full_action": "Contate customer support e provide o appropriate\nlogs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "desc": "Image does not have a fragment map", + "first_action": "Contact customer support and provide the appropriate", + "full_action": "Contact customer support and provide the appropriate\nlogs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "664": { "code": 664, - "desc": "Zero extents in o synthetic image, não é possível proceed", - "first_action": "Contate customer support e provide o appropriate", - "full_action": "Contate customer support e provide o appropriate\nlogs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "desc": "Zero extents in the synthetic image, cannot proceed", + "first_action": "Contact customer support and provide the appropriate", + "full_action": "Contact customer support and provide the appropriate\nlogs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "665": { "code": 665, - "desc": "Termination solicitado por bpcoord", - "first_action": "Contate customer support e send o appropriate logs.", - "full_action": "Contate customer support e send o appropriate logs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "desc": "Termination requested by bpcoord", + "first_action": "Contact customer support and send the appropriate logs.", + "full_action": "Contact customer support and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "667": { "code": 667, - "desc": "Não foi possível to abrir pipe between bpsynth e bpcoord", - "first_action": "Contate customer support e send o appropriate logs.", - "full_action": "Contate customer support e send o appropriate logs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "desc": "Unable to open pipe between bpsynth and bpcoord", + "first_action": "Contact customer support and send the appropriate logs.", + "full_action": "Contact customer support and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "668": { "code": 668, - "desc": "Pipe fgets call from bpcoord falhou", - "first_action": "Contate customer support e send o appropriate logs.", - "full_action": "Contate customer support e send o appropriate logs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "desc": "Pipe fgets call from bpcoord failed", + "first_action": "Contact customer support and send the appropriate logs.", + "full_action": "Contact customer support and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "669": { "code": 669, - "desc": "Bpcoord startup validation falha", - "first_action": "Contate customer support e send o appropriate logs.", - "full_action": "Contate customer support e send o appropriate logs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "desc": "Bpcoord startup validation failure", + "first_action": "Contact customer support and send the appropriate logs.", + "full_action": "Contact customer support and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "670": { "code": 670, - "desc": "Send buffer está cheio", - "first_action": "Contate customer support e provide o appropriate", - "full_action": "Contate customer support e provide o appropriate\nlogs.\nUm complete list de requerido logs e configuration informação está disponível.\nVeja \"Logs to accompany problema relatórios para synthetic backups\" in o NetBackup\nLogging Reference Guide." + "desc": "Send buffer is full", + "first_action": "Contact customer support and provide the appropriate", + "full_action": "Contact customer support and provide the appropriate\nlogs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide." }, "671": { "code": 671, - "desc": "Query para list de component images falhou", - "first_action": "Run um non-synthetic backup (either um new cheio ou new", - "full_action": "Run um non-synthetic backup (either um new cheio ou new\ncumulative), depending on o type de backup que falhou." + "desc": "Query for list of component images failed", + "first_action": "Run a non-synthetic backup (either a new full or new", + "full_action": "Run a non-synthetic backup (either a new full or new\ncumulative), depending on the type of backup that failed." }, "800": { "code": 800, - "desc": "Resource request falhou", - "first_action": "Locate o EMM reason string, correct o problema, e", - "full_action": "Locate o EMM reason string, correct o problema, e\nrerun o job.\nSome generic EMM reason strings (such como Disco volume está down) may require\ngenerating some relatórios to determinar o cause de o falha. Generate o relatório\npor usando either bperror ou various log entry relatórios, such como Relatórios > Disco\nRelatórios > Disco Logs in o NetBackup Administration Console." + "desc": "Resource request failed", + "first_action": "Locate the EMM reason string, correct the problem, and", + "full_action": "Locate the EMM reason string, correct the problem, and\nrerun the job.\nSome generic EMM reason strings (such as Disk volume is down) may require\ngenerating some reports to determine the cause of the failure. Generate the report\nby using either bperror or various log entry reports, such as Reports > Disk\nReports > Disk Logs in the NetBackup Administration Console." }, "801": { "code": 801, - "desc": "JM internal erro", + "desc": "JM internal error", "first_action": "UnifiedloggingfilesontheNetBackupserverfornbpem(originatorID116),nbjm", - "full_action": "If o problema persists, submit um relatório com o seguinte\nitems.\n■ UnifiedloggingfilesontheNetBackupserverfornbpem(originatorID116),nbjm\n(117), nbrb (118), e PBX (103). Todos unified logging está written to\n/usr/openv/logs (UNIX) ou install_path\\NetBackup\\logs (Windows).\n■ Legacy logs:\n■ On o NetBackup master servidor para bpbrm, bpjobd, bpcompatd, bpdbm,\ne nbproxy\n■ On o mídia servidor para bpcd, bpbrm, e bptm ou bpdm\n■ On o cliente para bpcd e bpbkar\nLegacylogsareinsubdirectoriesunder/usr/openv/netbackup/logs/(UNIX)\nou install_path\\NetBackup\\logs\\ (Windows). If o directories do não exist,\ncreate directories para each de these processos e rerun o job.\n■ Contents de /usr/openv/db/jobs/trylogs (UNIX) ou\ninstall_path\\NetBackup\\db\\jobs\\trylogs (Windows).\n■ bpdbjobs output: run bpdbjobs to obtain o state e status de todos jobs." + "full_action": "If the problem persists, submit a report with the following\nitems.\n■ UnifiedloggingfilesontheNetBackupserverfornbpem(originatorID116),nbjm\n(117), nbrb (118), and PBX (103). All unified logging is written to\n/usr/openv/logs (UNIX) or install_path\\NetBackup\\logs (Windows).\n■ Legacy logs:\n■ On the NetBackup master server for bpbrm, bpjobd, bpcompatd, bpdbm,\nand nbproxy\n■ On the media server for bpcd, bpbrm, and bptm or bpdm\n■ On the client for bpcd and bpbkar\nLegacylogsareinsubdirectoriesunder/usr/openv/netbackup/logs/(UNIX)\nor install_path\\NetBackup\\logs\\ (Windows). If the directories do not exist,\ncreate directories for each of these processes and rerun the job.\n■ Contents of /usr/openv/db/jobs/trylogs (UNIX) or\ninstall_path\\NetBackup\\db\\jobs\\trylogs (Windows).\n■ bpdbjobs output: run bpdbjobs to obtain the state and status of all jobs." }, "802": { "code": 802, - "desc": "JM internal protocol erro", + "desc": "JM internal protocol error", "first_action": "UnifiedloggingfilesontheNetBackupserverfornbpem(originatorID116),nbjm", - "full_action": "Garanta que o NetBackup software on o master e\no mídia servidor está from um official NetBackup release.\nIf o problema persists, submit um relatório com o seguinte items.\n■ UnifiedloggingfilesontheNetBackupserverfornbpem(originatorID116),nbjm\n(117), nbrb (118), e PBX (103). Todos unified logging está written to\n/usr/openv/logs (UNIX) ou install_path\\NetBackup\\logs (Windows).\n■ Legacy logs:\n■ On o NetBackup master servidor para bpbrm, bpjobd, bpcompatd, bpdbm,\ne nbproxy\n■ On o mídia servidor para bpcd, bpbrm, e bptm ou bpdm\n■ On o cliente para bpcd e bpbkar\nLegacylogsareinsubdirectoriesunder/usr/openv/netbackup/logs/(UNIX)\nou install_path\\NetBackup\\logs\\ (Windows). If o directories do não exist,\ncreate directories para each de these processos e rerun o job.\n■ Contents de /usr/openv/db/jobs/trylogs (UNIX) ou\ninstall_path\\NetBackup\\db\\jobs\\trylogs (Windows).\n■ bpdbjobs output: run bpdbjobs to obtain o state e status de todos jobs." + "full_action": "Ensure that the NetBackup software on the master and\nthe media server is from an official NetBackup release.\nIf the problem persists, submit a report with the following items.\n■ UnifiedloggingfilesontheNetBackupserverfornbpem(originatorID116),nbjm\n(117), nbrb (118), and PBX (103). All unified logging is written to\n/usr/openv/logs (UNIX) or install_path\\NetBackup\\logs (Windows).\n■ Legacy logs:\n■ On the NetBackup master server for bpbrm, bpjobd, bpcompatd, bpdbm,\nand nbproxy\n■ On the media server for bpcd, bpbrm, and bptm or bpdm\n■ On the client for bpcd and bpbkar\nLegacylogsareinsubdirectoriesunder/usr/openv/netbackup/logs/(UNIX)\nor install_path\\NetBackup\\logs\\ (Windows). If the directories do not exist,\ncreate directories for each of these processes and rerun the job.\n■ Contents of /usr/openv/db/jobs/trylogs (UNIX) or\ninstall_path\\NetBackup\\db\\jobs\\trylogs (Windows).\n■ bpdbjobs output: run bpdbjobs to obtain the state and status of all jobs." }, "803": { "code": 803, - "desc": "JM encerrando", + "desc": "JM terminating", "first_action": "UnifiedloggingfilesontheNetBackupserverfornbpem(originatorID116),nbjm", - "full_action": "If nbjm foi não terminated explicitly (por entering o\n/usr/openv/netbackup/bin/bp.kill_all comando on UNIX ou\ninstall_path\\NetBackup\\bin\\bpdown on Windows), submit um relatório com o\nseguinte items.\n■ UnifiedloggingfilesontheNetBackupserverfornbpem(originatorID116),nbjm\n(117), nbrb (118), e PBX (103). Todos unified logging está written to\n/usr/openv/logs (UNIX) ou install_path\\NetBackup\\logs (Windows).\n■ Legacy logs:\n■ On o NetBackup master servidor para bpbrm, bpjobd, bpcompatd, bpdbm,\ne nbproxy\n■ On o mídia servidor para bpcd, bpbrm, e bptm ou bpdm\n■ On o cliente para bpcd e bpbkar\nLegacylogsareinsubdirectoriesunder/usr/openv/netbackup/logs/(UNIX)\nou install_path\\NetBackup\\logs\\ (Windows). If o directories do não exist,\ncreate directories para each de these processos e rerun o job.\n■ Contents de /usr/openv/db/jobs/trylogs (UNIX) ou\ninstall_path\\NetBackup\\db\\jobs\\trylogs (Windows).\n■ bpdbjobs output: run bpdbjobs to obtain o state e status de todos jobs." + "full_action": "If nbjm was not terminated explicitly (by entering the\n/usr/openv/netbackup/bin/bp.kill_all command on UNIX or\ninstall_path\\NetBackup\\bin\\bpdown on Windows), submit a report with the\nfollowing items.\n■ UnifiedloggingfilesontheNetBackupserverfornbpem(originatorID116),nbjm\n(117), nbrb (118), and PBX (103). All unified logging is written to\n/usr/openv/logs (UNIX) or install_path\\NetBackup\\logs (Windows).\n■ Legacy logs:\n■ On the NetBackup master server for bpbrm, bpjobd, bpcompatd, bpdbm,\nand nbproxy\n■ On the media server for bpcd, bpbrm, and bptm or bpdm\n■ On the client for bpcd and bpbkar\nLegacylogsareinsubdirectoriesunder/usr/openv/netbackup/logs/(UNIX)\nor install_path\\NetBackup\\logs\\ (Windows). If the directories do not exist,\ncreate directories for each of these processes and rerun the job.\n■ Contents of /usr/openv/db/jobs/trylogs (UNIX) or\ninstall_path\\NetBackup\\db\\jobs\\trylogs (Windows).\n■ bpdbjobs output: run bpdbjobs to obtain the state and status of all jobs." }, "805": { "code": 805, - "desc": "Inválido jobid", + "desc": "Invalid jobid", "first_action": "UnifiedloggingfilesontheNetBackupserverfornbpem(originatorID116),nbjm", - "full_action": "O solicitado operation may refer to um job que não longer exists ou está não known to\nnbjm. Ou o job ID está inválido (less than ou equal to 0). Garanta que o comando\nused to start o job did não specify um job ID already in use por another job.\nIf o problema persists, submit um relatório com o seguinte items.\n■ UnifiedloggingfilesontheNetBackupserverfornbpem(originatorID116),nbjm\n(117), nbrb (118), e PBX (103). Todos unified logging está written to\n/usr/openv/logs (UNIX) ou install_path\\NetBackup\\logs (Windows).\n■ Legacy logs:\n■ On o NetBackup master servidor para bpbrm, bpjobd, bpcompatd, bpdbm, e\nnbproxy\n■ On o mídia servidor para bpcd, bpbrm, e bptm ou bpdm\n■ On o cliente para bpcd e bpbkar\nLegacylogsareinsubdirectoriesunder/usr/openv/netbackup/logs/(UNIX)\nou install_path\\NetBackup\\logs\\ (Windows). If o directories do não exist,\nyou must create directories para each de these processos e rerun o job.\n■ Contents de /usr/openv/db/jobs/trylogs (UNIX) ou\ninstall_path\\NetBackup\\db\\jobs\\trylogs (Windows).\n■ bpdbjobs output: run bpdbjobs to obtain o state e status de todos jobs." + "full_action": "The requested operation may refer to a job that no longer exists or is not known to\nnbjm. Or the job ID is invalid (less than or equal to 0). Ensure that the command\nused to start the job did not specify a job ID already in use by another job.\nIf the problem persists, submit a report with the following items.\n■ UnifiedloggingfilesontheNetBackupserverfornbpem(originatorID116),nbjm\n(117), nbrb (118), and PBX (103). All unified logging is written to\n/usr/openv/logs (UNIX) or install_path\\NetBackup\\logs (Windows).\n■ Legacy logs:\n■ On the NetBackup master server for bpbrm, bpjobd, bpcompatd, bpdbm, and\nnbproxy\n■ On the media server for bpcd, bpbrm, and bptm or bpdm\n■ On the client for bpcd and bpbkar\nLegacylogsareinsubdirectoriesunder/usr/openv/netbackup/logs/(UNIX)\nor install_path\\NetBackup\\logs\\ (Windows). If the directories do not exist,\nyou must create directories for each of these processes and rerun the job.\n■ Contents of /usr/openv/db/jobs/trylogs (UNIX) or\ninstall_path\\NetBackup\\db\\jobs\\trylogs (Windows).\n■ bpdbjobs output: run bpdbjobs to obtain the state and status of all jobs." }, "806": { "code": 806, - "desc": "This mpx group está unjoinable", - "first_action": "If o falhou job está scheduled e o retry count allows it,", - "full_action": "If o falhou job está scheduled e o retry count allows it,\nnbpem submits o job again. If o falhou job foi initiated manually, submit it again." + "desc": "This mpx group is unjoinable", + "first_action": "If the failed job is scheduled and the retry count allows it,", + "full_action": "If the failed job is scheduled and the retry count allows it,\nnbpem submits the job again. If the failed job was initiated manually, submit it again." }, "807": { "code": 807, - "desc": "Não externalized", - "first_action": "Não disponível", - "full_action": "Não disponível" + "desc": "Not externalized", + "first_action": "Not available", + "full_action": "Not available" }, "811": { "code": 811, - "desc": "Falhou to communicate com resource requester", - "first_action": "Verifique o connectivity between o master e o mídia servidor.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Verifique o connectivity between o master e o mídia servidor.\n■ VerifythePrivateBranchExchange(PBX)configurationandpermissions.More\ninformação on PBX está disponível.\nVeja \"resolvendo PBX problemas\" in o NetBackup Troubleshooting Guide." + "desc": "Failed to communicate with resource requester", + "first_action": "Verify the connectivity between the master and the media server.", + "full_action": "Do the following, as appropriate:\n■ Verify the connectivity between the master and the media server.\n■ VerifythePrivateBranchExchange(PBX)configurationandpermissions.More\ninformation on PBX is available.\nSee \"Resolving PBX problems\" in the NetBackup Troubleshooting Guide." }, "812": { "code": 812, - "desc": "Falhou to communicate com Resource Broker", - "first_action": "Verifique o connectivity between o master servidor e o EMM servidor.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Verifique o connectivity between o master servidor e o EMM servidor.\n■ VerifythePrivateBranchExchange(PBX)configurationandpermissions.More\ninformação on PBX está disponível.\nVeja \"resolvendo PBX problemas\" in o NetBackup Troubleshooting Guide." + "desc": "Failed to communicate with Resource Broker", + "first_action": "Verify the connectivity between the master server and the EMM server.", + "full_action": "Do the following, as appropriate:\n■ Verify the connectivity between the master server and the EMM server.\n■ VerifythePrivateBranchExchange(PBX)configurationandpermissions.More\ninformation on PBX is available.\nSee \"Resolving PBX problems\" in the NetBackup Troubleshooting Guide." }, "813": { "code": 813, "desc": "Duplicate reference string specified", - "first_action": "Choose um unique name que está não already in use.", - "full_action": "Choose um unique name que está não already in use." + "first_action": "Choose a unique name that is not already in use.", + "full_action": "Choose a unique name that is not already in use." }, "818": { "code": 818, "desc": "Retention level mismatch", - "first_action": "Contate Cohesity Technical Support e provide relevant", - "full_action": "Contate Cohesity Technical Support e provide relevant\nsupporting materials." + "first_action": "Contact Cohesity Technical Support and provide relevant", + "full_action": "Contact Cohesity Technical Support and provide relevant\nsupporting materials." }, "819": { "code": 819, - "desc": "Não foi possível to communicate com JM proxy", - "first_action": "Restart o Job Manager. If o condition persists, por favor", - "full_action": "Restart o Job Manager. If o condition persists, por favor\ncontate NetBackup Support e provide relevant supporting materials." + "desc": "Unable to communicate with JM proxy", + "first_action": "Restart the Job Manager. If the condition persists, please", + "full_action": "Restart the Job Manager. If the condition persists, please\ncontact NetBackup Support and provide relevant supporting materials." }, "823": { "code": 823, - "desc": "Não BRMComm to join", + "desc": "No BRMComm to join", "first_action": "UnifiedloggingfilesontheNetBackupserverfornbpem(originatorID116),nbjm", - "full_action": "Submit um relatório com o seguinte items.\n■ UnifiedloggingfilesontheNetBackupserverfornbpem(originatorID116),nbjm\n(117), nbrb (118), e PBX (103). Todos unified logging está written to\n/usr/openv/logs (UNIX) ou install_path\\NetBackup\\logs (Windows).\n■ O seguinte legacy logs:\n■ On o NetBackup master servidor para bpbrm, bpjobd, bpcompatd, bpdbm, e\nnbproxy\n■ On o mídia servidor para bpcd, bpbrm, e bptm ou bpdm\n■ On o cliente para bpcd e bpbkar\nLegacylogsareinsubdirectoriesunder/usr/openv/netbackup/logs/(UNIX)\nou install_path\\NetBackup\\logs\\ (Windows). If o directories do não exist,\ncreate directories para each de these processos e rerun o job.\n■ Contents de /usr/openv/db/jobs/trylogs (UNIX) ou\ninstall_path\\NetBackup\\db\\jobs\\trylogs (Windows).\n■ bpdbjobs output: run bpdbjobs to obtain o state e status de todos jobs." + "full_action": "Submit a report with the following items.\n■ UnifiedloggingfilesontheNetBackupserverfornbpem(originatorID116),nbjm\n(117), nbrb (118), and PBX (103). All unified logging is written to\n/usr/openv/logs (UNIX) or install_path\\NetBackup\\logs (Windows).\n■ The following legacy logs:\n■ On the NetBackup master server for bpbrm, bpjobd, bpcompatd, bpdbm, and\nnbproxy\n■ On the media server for bpcd, bpbrm, and bptm or bpdm\n■ On the client for bpcd and bpbkar\nLegacylogsareinsubdirectoriesunder/usr/openv/netbackup/logs/(UNIX)\nor install_path\\NetBackup\\logs\\ (Windows). If the directories do not exist,\ncreate directories for each of these processes and rerun the job.\n■ Contents of /usr/openv/db/jobs/trylogs (UNIX) or\ninstall_path\\NetBackup\\db\\jobs\\trylogs (Windows).\n■ bpdbjobs output: run bpdbjobs to obtain the state and status of all jobs." }, "830": { "code": 830, - "desc": "Drive(s) unavailable ou down", - "first_action": "Make sure que o drives e drive paths estão up e correct para o mídia que", - "full_action": "Do o seguinte:\n■ Make sure que o drives e drive paths estão up e correct para o mídia que\nyou configure.\n■ Verifique que ltid está executando on o requerido mídia servidor, e que o mídia\nservidor está active para tape.\n■ Use o dispositivo monitor to startup o drives paths if they estão down.\n■ If o drives estão downed again, clean o drives." + "desc": "Drive(s) unavailable or down", + "first_action": "Make sure that the drives and drive paths are up and correct for the media that", + "full_action": "Do the following:\n■ Make sure that the drives and drive paths are up and correct for the media that\nyou configure.\n■ Verify that ltid is running on the required media server, and that the media\nserver is active for tape.\n■ Use the device monitor to startup the drives paths if they are down.\n■ If the drives are downed again, clean the drives." }, "831": { "code": 831, "desc": "Image has been validated", - "first_action": "Não corrective ação está requerido.", - "full_action": "Não corrective ação está requerido." + "first_action": "No corrective action is required.", + "full_action": "No corrective action is required." }, "832": { "code": 832, - "desc": "Falhou to gravar discover data to um arquivo", - "first_action": "Make sure que o arquivo system está não cheio.", - "full_action": "Make sure que o arquivo system está não cheio." + "desc": "Failed to write discover data to a file", + "first_action": "Make sure that the file system is not full.", + "full_action": "Make sure that the file system is not full." }, "833": { "code": 833, - "desc": "Erro parsing discovered XML data", + "desc": "Error parsing discovered XML data", "first_action": "UnifiedloggingfilesontheNetBackupserverfornbpem(originatorID116),nbjm", - "full_action": "Submit um relatório com o seguinte items:\n■ UnifiedloggingfilesontheNetBackupserverfornbpem(originatorID116),nbjm\n(117), nbrb (118), e PBX (103). Todos unified logging está written to\n/usr/openv/logs (UNIX) ou install_path\\NetBackup\\logs (Windows).\n■ O seguinte legacy logs:\n■ On o NetBackup master servidor para bpbrm, bpjobd, bpcompatd, bpdbm, e\nnbproxy\n■ On o mídia servidor para bpcd, bpbrm, e bptm ou bpdm\n■ On o cliente para bpcd e bpbkar\nLegacylogsareinsubdirectoriesunder/usr/openv/netbackup/logs/(UNIX)\nou install_path\\NetBackup\\logs\\ (Windows). If o directories do não exist,\ncreate directories para each de these processos e rerun o job.\n■ Contents de /usr/openv/db/jobs/trylogs (UNIX) ou\ninstall_path\\NetBackup\\db\\jobs\\trylogs (Windows).\n■ bpdbjobs output: run bpdbjobs to obtain o state e status de todos jobs." + "full_action": "Submit a report with the following items:\n■ UnifiedloggingfilesontheNetBackupserverfornbpem(originatorID116),nbjm\n(117), nbrb (118), and PBX (103). All unified logging is written to\n/usr/openv/logs (UNIX) or install_path\\NetBackup\\logs (Windows).\n■ The following legacy logs:\n■ On the NetBackup master server for bpbrm, bpjobd, bpcompatd, bpdbm, and\nnbproxy\n■ On the media server for bpcd, bpbrm, and bptm or bpdm\n■ On the client for bpcd and bpbkar\nLegacylogsareinsubdirectoriesunder/usr/openv/netbackup/logs/(UNIX)\nor install_path\\NetBackup\\logs\\ (Windows). If the directories do not exist,\ncreate directories for each of these processes and rerun the job.\n■ Contents of /usr/openv/db/jobs/trylogs (UNIX) or\ninstall_path\\NetBackup\\db\\jobs\\trylogs (Windows).\n■ bpdbjobs output: run bpdbjobs to obtain the state and status of all jobs." }, "859": { "code": 859, "desc": "Exceededmaximumnumberofretries,unabletodeactivatedeployment host.", - "first_action": "Retry o deployment job on o target host.", - "full_action": "Retry o deployment job on o target host." + "first_action": "Retry the deployment job on the target host.", + "full_action": "Retry the deployment job on the target host." }, "860": { "code": 860, - "desc": "Excedido maximum number de retries, não foi possível to activate deployment host.", - "first_action": "Activate_host -h hostname to activate o host.", - "full_action": "Wait until o host está active, ou run vmoprcmd\n-activate_host -h hostname to activate o host." + "desc": "Exceeded maximum number of retries, unable to activate deployment host.", + "first_action": "Activate_host -h hostname to activate the host.", + "full_action": "Wait until the host is active, or run vmoprcmd\n-activate_host -h hostname to activate the host." }, "861": { "code": 861, "desc": "Theentryforexclude_file_listparameterinthejob paramfileisnot present.", - "first_action": "Retry o backup job again. If o issue persists, update", - "full_action": "Retry o backup job again. If o issue persists, update\no backup policy to reconfigure o exclude selections." + "first_action": "Retry the backup job again. If the issue persists, update", + "full_action": "Retry the backup job again. If the issue persists, update\nthe backup policy to reconfigure the exclude selections." }, "900": { "code": 900, "desc": "Retry nbrb request later", - "first_action": "Para detailed informação, examine o unified logging arquivos on o NetBackup", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Para detailed informação, examine o unified logging arquivos on o NetBackup\nservidor para o nbrb service (originator ID 118). Todos unified logging está written to\n/usr/openv/logs (UNIX) ou install_path\\NetBackup\\logs (Windows).\n■ If necessary, set global logging to um higher level por usando Host Properties >\nMaster Servidor > Properties > Logging. Retry o operation e examine o\nnbrb logs." + "first_action": "For detailed information, examine the unified logging files on the NetBackup", + "full_action": "Do the following, as appropriate:\n■ For detailed information, examine the unified logging files on the NetBackup\nserver for the nbrb service (originator ID 118). All unified logging is written to\n/usr/openv/logs (UNIX) or install_path\\NetBackup\\logs (Windows).\n■ If necessary, set global logging to a higher level by using Host Properties >\nMaster Server > Properties > Logging. Retry the operation and examine the\nnbrb logs." }, "901": { "code": 901, - "desc": "RB internal erro", - "first_action": "Para detailed informação, examine o unified logging arquivos on o NetBackup", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Para detailed informação, examine o unified logging arquivos on o NetBackup\nservidor para o nbrb service (originator ID 118). Todos unified logging está written to\n/usr/openv/logs (UNIX) ou install_path\\NetBackup\\logs (Windows).\n■ If necessary, set global logging to um higher level, por usando Host Properties >\nMaster Servidor > Properties > Logging. Retry o operation e examine o\nnbrb logs." + "desc": "RB internal error", + "first_action": "For detailed information, examine the unified logging files on the NetBackup", + "full_action": "Do the following, as appropriate:\n■ For detailed information, examine the unified logging files on the NetBackup\nserver for the nbrb service (originator ID 118). All unified logging is written to\n/usr/openv/logs (UNIX) or install_path\\NetBackup\\logs (Windows).\n■ If necessary, set global logging to a higher level, by using Host Properties >\nMaster Server > Properties > Logging. Retry the operation and examine the\nnbrb logs." }, "902": { "code": 902, - "desc": "RB inválido argument", - "first_action": "Para detailed informação, examine o unified logging arquivos on o NetBackup", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Para detailed informação, examine o unified logging arquivos on o NetBackup\nservidor para o nbrb service (originator ID 118). Todos unified logging está written to\n/usr/openv/logs (UNIX) ou install_path\\NetBackup\\logs (Windows).\n■ If necessary, set global logging to um higher level, por usando Host Properties >\nMaster Servidor > Properties > Logging. Retry o operation e examine o\nnbrb logs." + "desc": "RB invalid argument", + "first_action": "For detailed information, examine the unified logging files on the NetBackup", + "full_action": "Do the following, as appropriate:\n■ For detailed information, examine the unified logging files on the NetBackup\nserver for the nbrb service (originator ID 118). All unified logging is written to\n/usr/openv/logs (UNIX) or install_path\\NetBackup\\logs (Windows).\n■ If necessary, set global logging to a higher level, by using Host Properties >\nMaster Server > Properties > Logging. Retry the operation and examine the\nnbrb logs." }, "903": { "code": 903, - "desc": "RB communication erro", - "first_action": "Para detailed informação, examine o unified logging arquivos on o NetBackup", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Para detailed informação, examine o unified logging arquivos on o NetBackup\nservidor para o nbrb service (originator ID 118). Todos unified logging está written to\n/usr/openv/logs (UNIX) ou install_path\\NetBackup\\logs (Windows).\n■ If necessary, set global logging to um higher level, por usando Host Properties >\nMaster Servidor > Properties > Logging. Retry o operation e examine o\nnbrb logs." + "desc": "RB communication error", + "first_action": "For detailed information, examine the unified logging files on the NetBackup", + "full_action": "Do the following, as appropriate:\n■ For detailed information, examine the unified logging files on the NetBackup\nserver for the nbrb service (originator ID 118). All unified logging is written to\n/usr/openv/logs (UNIX) or install_path\\NetBackup\\logs (Windows).\n■ If necessary, set global logging to a higher level, by using Host Properties >\nMaster Server > Properties > Logging. Retry the operation and examine the\nnbrb logs." }, "904": { "code": 904, - "desc": "RB max reallocation tries excedido", - "first_action": "Para detailed informação, examine o unified logging arquivos", - "full_action": "Para detailed informação, examine o unified logging arquivos\non o NetBackup servidor para o nbrb service (originator ID 118) e para nbemm\n(originator ID 111). Todos unified logging está written to /usr/openv/logs (UNIX) ou\ninstall_path\\NetBackup\\logs (Windows). Also examine o legacy bptm log." + "desc": "RB max reallocation tries exceeded", + "first_action": "For detailed information, examine the unified logging files", + "full_action": "For detailed information, examine the unified logging files\non the NetBackup server for the nbrb service (originator ID 118) and for nbemm\n(originator ID 111). All unified logging is written to /usr/openv/logs (UNIX) or\ninstall_path\\NetBackup\\logs (Windows). Also examine the legacy bptm log." }, "905": { "code": 905, - "desc": "RB mídia servidor mismatch", - "first_action": "Configure o backup schedule com um armazenamento unidade ou armazenamento unidade groups que", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Configure o backup schedule com um armazenamento unidade ou armazenamento unidade groups que\ncan be run on o same mídia servidor.\n■ Para detailed informação, examine o unified logging arquivos on o NetBackup\nservidor para o nbrb service (originator ID 118). Todos unified logging está written to\n/usr/openv/logs (UNIX) ou install_path\\NetBackup\\logs (Windows)." + "desc": "RB media server mismatch", + "first_action": "Configure the backup schedule with a storage unit or storage unit groups that", + "full_action": "Do the following, as appropriate:\n■ Configure the backup schedule with a storage unit or storage unit groups that\ncan be run on the same media server.\n■ For detailed information, examine the unified logging files on the NetBackup\nserver for the nbrb service (originator ID 118). All unified logging is written to\n/usr/openv/logs (UNIX) or install_path\\NetBackup\\logs (Windows)." }, "906": { "code": 906, - "desc": "RB operator negada mount request NetBackup status codes 329 NetBackup status codes", - "first_action": "Determinar o cause de o mount request denial e retry o job.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Determinar o cause de o mount request denial e retry o job.\n■ Para detailed informação, examine o unified logging arquivos on o NetBackup\nservidor para o nbrb service (originator ID 118). Todos unified logging está written to\n/usr/openv/logs (UNIX) ou install_path\\NetBackup\\logs (Windows)." + "desc": "RB operator denied mount request NetBackup status codes 329 NetBackup status codes", + "first_action": "Determine the cause of the mount request denial and retry the job.", + "full_action": "Do the following, as appropriate:\n■ Determine the cause of the mount request denial and retry the job.\n■ For detailed information, examine the unified logging files on the NetBackup\nserver for the nbrb service (originator ID 118). All unified logging is written to\n/usr/openv/logs (UNIX) or install_path\\NetBackup\\logs (Windows)." }, "907": { "code": 907, - "desc": "RB usuário canceled resource request", - "first_action": "Determinar o ação que resulted in cancelation de o resource request.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Determinar o ação que resulted in cancelation de o resource request.\n■ Para detailed informação, examine o unified logging arquivos on o NetBackup\nservidor para o nbrb service (originator ID 118). Todos unified logging está written to\n/usr/openv/logs (UNIX) ou install_path\\NetBackup\\logs (Windows)." + "desc": "RB user canceled resource request", + "first_action": "Determine the action that resulted in cancelation of the resource request.", + "full_action": "Do the following, as appropriate:\n■ Determine the action that resulted in cancelation of the resource request.\n■ For detailed information, examine the unified logging files on the NetBackup\nserver for the nbrb service (originator ID 118). All unified logging is written to\n/usr/openv/logs (UNIX) or install_path\\NetBackup\\logs (Windows)." }, "908": { "code": 908, - "desc": "RB foi reset", - "first_action": "Determinar o ação que reset nbrb resources e o nbemm banco de dados.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Determinar o ação que reset nbrb resources e o nbemm banco de dados.\n■ Para detailed informação, examine o unified logging arquivos on o NetBackup\nservidor para o nbrb service (originator ID 118). Todos unified logging está written to\n/usr/openv/logs (UNIX) ou install_path\\NetBackup\\logs (Windows)." + "desc": "RB was reset", + "first_action": "Determine the action that reset nbrb resources and the nbemm database.", + "full_action": "Do the following, as appropriate:\n■ Determine the action that reset nbrb resources and the nbemm database.\n■ For detailed information, examine the unified logging files on the NetBackup\nserver for the nbrb service (originator ID 118). All unified logging is written to\n/usr/openv/logs (UNIX) or install_path\\NetBackup\\logs (Windows)." }, "912": { "code": 912, - "desc": "RB disco volume mount falhou", - "first_action": "Para detailed informação, examine o unified logging arquivos on o NetBackup", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Para detailed informação, examine o unified logging arquivos on o NetBackup\nservidor para o nbrb service (originator ID 118). Unified logging está written to\n/usr/openv/logs (UNIX) ou install_path\\NetBackup\\logs (Windows).\n■ If necessary, set global logging to um higher level: Host Properties > Master\nServidor > Properties > Logging. Retry o operation e examine o nbrb\nlogs." + "desc": "RB disk volume mount failed", + "first_action": "For detailed information, examine the unified logging files on the NetBackup", + "full_action": "Do the following, as appropriate:\n■ For detailed information, examine the unified logging files on the NetBackup\nserver for the nbrb service (originator ID 118). Unified logging is written to\n/usr/openv/logs (UNIX) or install_path\\NetBackup\\logs (Windows).\n■ If necessary, set global logging to a higher level: Host Properties > Master\nServer > Properties > Logging. Retry the operation and examine the nbrb\nlogs." }, "914": { "code": 914, - "desc": "RB mídia reservation não found", - "first_action": "Examine o unified logging arquivos on o NetBackup servidor para o nbrb service", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Examine o unified logging arquivos on o NetBackup servidor para o nbrb service\n(originator ID 118). Unified logging está written to /usr/openv/logs (UNIX) ou to\ninstall_path\\NetBackup\\logs (Windows).\n■ If necessary, set global logging to um higher level: Host Properties > Master\nServidor > Properties > Logging. Retry o operation e examine o nbrb\nlogs." + "desc": "RB media reservation not found", + "first_action": "Examine the unified logging files on the NetBackup server for the nbrb service", + "full_action": "Do the following, as appropriate:\n■ Examine the unified logging files on the NetBackup server for the nbrb service\n(originator ID 118). Unified logging is written to /usr/openv/logs (UNIX) or to\ninstall_path\\NetBackup\\logs (Windows).\n■ If necessary, set global logging to a higher level: Host Properties > Master\nServer > Properties > Logging. Retry the operation and examine the nbrb\nlogs." }, "915": { "code": 915, - "desc": "RB disco volume mount must retry NetBackup status codes 331 NetBackup status codes", + "desc": "RB disk volume mount must retry NetBackup status codes 331 NetBackup status codes", "first_action": "Verifythatprocessesarenotinthediskvolumemountdirectories,whichprevents", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Verifythatprocessesarenotinthediskvolumemountdirectories,whichprevents\nthem from being unmounted. If o problema persists, restart NetBackup on o\nmídia servidor." + "full_action": "Do the following, as appropriate:\n■ Verifythatprocessesarenotinthediskvolumemountdirectories,whichprevents\nthem from being unmounted. If the problem persists, restart NetBackup on the\nmedia server." }, "916": { "code": 916, - "desc": "Resource request esgotado fora", + "desc": "Resource request timed out", "first_action": "Distributethescheduledjobstarttimesoverawiderperiod", - "full_action": "Distributethescheduledjobstarttimesoverawiderperiod\nde time." + "full_action": "Distributethescheduledjobstarttimesoverawiderperiod\nof time." }, "917": { "code": 917, - "desc": "RB multiplexing group não found", - "first_action": "Restart nbjm e nbrb. If o problema persists, gravar um", - "full_action": "Restart nbjm e nbrb. If o problema persists, gravar um\nproblema relatório com o appropriate logs including o nbjm e nbrb logs." + "desc": "RB multiplexing group not found", + "first_action": "Restart nbjm and nbrb. If the problem persists, write a", + "full_action": "Restart nbjm and nbrb. If the problem persists, write a\nproblem report with the appropriate logs including the nbjm and nbrb logs." }, "918": { "code": 918, - "desc": "RB does não have um multiplexing group que uses this mídia ID ou drive name NetBackup status codes 332 NetBackup status codes", - "first_action": "O nbrbutil comando may cause this erro. Rerun o", - "full_action": "O nbrbutil comando may cause this erro. Rerun o\ncomando com um allocated mídia ID ou drive. Also, this erro may be internal. If\no problema persists, gravar um problema relatório com o appropriate logs including\nnbjm e nbrb." + "desc": "RB does not have a multiplexing group that uses this media ID or drive name NetBackup status codes 332 NetBackup status codes", + "first_action": "The nbrbutil command may cause this error. Rerun the", + "full_action": "The nbrbutil command may cause this error. Rerun the\ncommand with an allocated media ID or drive. Also, this error may be internal. If\nthe problem persists, write a problem report with the appropriate logs including\nnbjm and nbrb." }, "925": { "code": 925, - "desc": "Backup host pool name está não provided in o Resource Broker request.", - "first_action": "Garanta que o backup host pool está configurado in o", - "full_action": "Garanta que o backup host pool está configurado in o\nbackup policy." + "desc": "Backup host pool name is not provided in the Resource Broker request.", + "first_action": "Ensure that the backup host pool is configured in the", + "full_action": "Ensure that the backup host pool is configured in the\nbackup policy." }, "927": { "code": 927, - "desc": "Não backup host from configurado backup host pool está disponível para job execution.", - "first_action": "Garanta todos NetBackup services estão up e executando on", - "full_action": "Garanta todos NetBackup services estão up e executando on\nbackup host. If o services estão already executando, then o backup host está executando\natfullcapacityfordynamicstreaming.Youmustwaitfortheactivejobstocomplete." + "desc": "No backup host from configured backup host pool is available for job execution.", + "first_action": "Ensure all NetBackup services are up and running on", + "full_action": "Ensure all NetBackup services are up and running on\nbackup host. If the services are already running, then the backup host is running\natfullcapacityfordynamicstreaming.Youmustwaitfortheactivejobstocomplete." }, "928": { "code": 928, - "desc": "O NetBackup version de o backup hosts e o configurado backup host pool must be de o same version.", - "first_action": "Garanta que todos backup hosts in um backup host pool estão", - "full_action": "Garanta que todos backup hosts in um backup host pool estão\no same NetBackup version." + "desc": "The NetBackup version of the backup hosts and the configured backup host pool must be of the same version.", + "first_action": "Ensure that all backup hosts in a backup host pool are", + "full_action": "Ensure that all backup hosts in a backup host pool are\nthe same NetBackup version." }, "930": { "code": 930, - "desc": "Não supported mídia servidor disponível, in o All_Media_Server_Pool, como backup host to run o job.", - "first_action": "Volume backup from snapshot usando multiple backup hosts: NetBackup 10.4", - "full_action": "Confirm que you have um Windows mídia servidor if you\nback up o NAS shares com o SMB protocol. Confirm que you have um Linux\nmídia servidor if you back up o NAS shares com o NFS protocol.\nRecomendada Ação: Para Windows mídia servers, you must log on to o\nNetBackup Cliente Service e NetBackup legacy rede service services como um\ndomain usuário.\nRecomendada Ação: Garanta que o NetBackup mídia servidor version está equal\nto ou higher than o minimum requerido version, based on these parameters de o\nNAS data protection policy:\n■ Volume backup from snapshot usando multiple backup hosts: NetBackup 10.4\n■ VCT enabled index from snapshot: NetBackup 10.3\n■ VCT enabled backup from snapshot: NetBackup 10.2\n■ Todos other scenarios: NetBackup 10.1.1" + "desc": "No supported media server available, in the All_Media_Server_Pool, as backup host to run the job.", + "first_action": "Volume backup from snapshot using multiple backup hosts: NetBackup 10.4", + "full_action": "Confirm that you have a Windows media server if you\nback up the NAS shares with the SMB protocol. Confirm that you have a Linux\nmedia server if you back up the NAS shares with the NFS protocol.\nRecommended Action: For Windows media servers, you must log on to the\nNetBackup Client Service and NetBackup legacy network service services as a\ndomain user.\nRecommended Action: Ensure that the NetBackup media server version is equal\nto or higher than the minimum required version, based on these parameters of the\nNAS data protection policy:\n■ Volume backup from snapshot using multiple backup hosts: NetBackup 10.4\n■ VCT enabled index from snapshot: NetBackup 10.3\n■ VCT enabled backup from snapshot: NetBackup 10.2\n■ All other scenarios: NetBackup 10.1.1" }, "1000": { "code": 1000, - "desc": "Cliente está offline", - "first_action": "Wait until o cliente está brought online ou manually bring", - "full_action": "Wait until o cliente está brought online ou manually bring\no cliente online por usando o GUI ou o bpclient comando before you submit o\nmanual job." + "desc": "Client is offline", + "first_action": "Wait until the client is brought online or manually bring", + "full_action": "Wait until the client is brought online or manually bring\nthe client online by using the GUI or the bpclient command before you submit the\nmanual job." }, "1001": { "code": 1001, - "desc": "Discovery document erro NetBackup status codes 334 NetBackup status codes", + "desc": "Discovery document error NetBackup status codes 334 NetBackup status codes", "first_action": "UnifiedloggingfilesontheNetBackupserverfornbpem(originatorID116),nbjm", - "full_action": "Submit um relatório com o seguinte items.\n■ UnifiedloggingfilesontheNetBackupserverfornbpem(originatorID116),nbjm\n(117), nbrb (118), e PBX (103). Todos unified logging está written to\n/usr/openv/logs (UNIX e Linux) ou install_path\\NetBackup\\logs\n(Windows).\n■ O seguinte legacy logs:\n■ On o NetBackup master servidor para bpbrm, bpjobd, bpcompatd, bpdbm, e\nnbproxy\n■ On o mídia servidor para bpcd, bpbrm, e bptm ou bpdm\n■ On o cliente para bpcd e bpbkar\nLegacy logs estão in subdirectories under /usr/openv/netbackup/logs/ (UNIX\ne Linux) ou install_path\\NetBackup\\logs\\ (Windows). If o directories\ndo não exist, create directories para each de these processos e rerun o job.\n■ Contents de /usr/openv/db/jobs/trylogs (UNIX e Linux) ou\ninstall_path\\NetBackup\\db\\jobs\\trylogs (Windows).\n■ bpdbjobs output: run bpdbjobs to obtain o state e status de todos jobs." + "full_action": "Submit a report with the following items.\n■ UnifiedloggingfilesontheNetBackupserverfornbpem(originatorID116),nbjm\n(117), nbrb (118), and PBX (103). All unified logging is written to\n/usr/openv/logs (UNIX and Linux) or install_path\\NetBackup\\logs\n(Windows).\n■ The following legacy logs:\n■ On the NetBackup master server for bpbrm, bpjobd, bpcompatd, bpdbm, and\nnbproxy\n■ On the media server for bpcd, bpbrm, and bptm or bpdm\n■ On the client for bpcd and bpbkar\nLegacy logs are in subdirectories under /usr/openv/netbackup/logs/ (UNIX\nand Linux) or install_path\\NetBackup\\logs\\ (Windows). If the directories\ndo not exist, create directories for each of these processes and rerun the job.\n■ Contents of /usr/openv/db/jobs/trylogs (UNIX and Linux) or\ninstall_path\\NetBackup\\db\\jobs\\trylogs (Windows).\n■ bpdbjobs output: run bpdbjobs to obtain the state and status of all jobs." }, "1002": { "code": 1002, - "desc": "Discovery detected um falhou cliente", - "first_action": "Veja o job details log para more specific informação.", - "full_action": "Veja o job details log para more specific informação." + "desc": "Discovery detected a failed client", + "first_action": "See the job details log for more specific information.", + "full_action": "See the job details log for more specific information." }, "1004": { "code": 1004, - "desc": "Falhou to get o Snapshot Manager name.", + "desc": "Failed to get the Snapshot Manager name.", "first_action": "CheckiftheNetBackupWebManagementConsole(nbwmc)", - "full_action": "CheckiftheNetBackupWebManagementConsole(nbwmc)\nservice está up e executando. Then stop e restart o service if necessary." + "full_action": "CheckiftheNetBackupWebManagementConsole(nbwmc)\nservice is up and running. Then stop and restart the service if necessary." }, "1005": { "code": 1005, - "desc": "Missing one ou more de o requerido policy values para unix_eca_cert_path, unix_eca_trust_store_path, ou unix_eca_private_key_path.", + "desc": "Missing one or more of the required policy values for unix_eca_cert_path, unix_eca_trust_store_path, or unix_eca_private_key_path.", "first_action": "Reset policy fields unix_eca_crl_path,", - "full_action": "Reset policy fields unix_eca_crl_path,\nunix_eca_crl_check_level,andunix_eca_key_passphrasefileifyouonlyhave\nwindows clients. Otherwise, set requerido fields unix_eca_cert_path,\nunix_eca_trust_store_path, e unix_eca_private_key_path." + "full_action": "Reset policy fields unix_eca_crl_path,\nunix_eca_crl_check_level,andunix_eca_key_passphrasefileifyouonlyhave\nwindows clients. Otherwise, set required fields unix_eca_cert_path,\nunix_eca_trust_store_path, and unix_eca_private_key_path." }, "1006": { "code": 1006, - "desc": "Missingoneormoreoftherequiredpolicyvaluesforwin_eca_cert_path, win_eca_trust_store_path, ou win_eca_private_key_path.", + "desc": "Missingoneormoreoftherequiredpolicyvaluesforwin_eca_cert_path, win_eca_trust_store_path, or win_eca_private_key_path.", "first_action": "Reset policy fields win_eca_crl_path,", - "full_action": "Reset policy fields win_eca_crl_path,\nwin_eca_crl_check_level, e win_eca_key_passphrasefile if you apenas have\nUNIX clients. Otherwise, set requerido fields win_eca_cert_path,\nwin_eca_trust_store_path, e win_eca_private_key_path." + "full_action": "Reset policy fields win_eca_crl_path,\nwin_eca_crl_check_level, and win_eca_key_passphrasefile if you only have\nUNIX clients. Otherwise, set required fields win_eca_cert_path,\nwin_eca_trust_store_path, and win_eca_private_key_path." }, "1007": { "code": 1007, - "desc": "Não é possível specify policy values para win_eca_cert_path, win_eca_trust_store_path, win_eca_private_key_path, e win_eca_key_passphrasefile when o policy value win_eca_cert_store está specified.", - "first_action": "Set o requerido policy field win_eca_crl_check_level", - "full_action": "Set o requerido policy field win_eca_crl_check_level\ne reset policy fields win_eca_cert_path, win_eca_trust_store_path,\nwin_eca_private_key_path, e win_eca_key_passphrasefile ou reset o\npolicy field win_eca_cert_store." + "desc": "Cannot specify policy values for win_eca_cert_path, win_eca_trust_store_path, win_eca_private_key_path, and win_eca_key_passphrasefile when the policy value win_eca_cert_store is specified.", + "first_action": "Set the required policy field win_eca_crl_check_level", + "full_action": "Set the required policy field win_eca_crl_check_level\nand reset policy fields win_eca_cert_path, win_eca_trust_store_path,\nwin_eca_private_key_path, and win_eca_key_passphrasefile or reset the\npolicy field win_eca_cert_store." }, "1008": { "code": 1008, - "desc": "Missing requerido field unix_eca_crl_path.", - "first_action": "Set o policy field unix_eca_crl_path ou change", - "full_action": "Set o policy field unix_eca_crl_path ou change\nunix_eca_crl_check_level to either use_cdp ou disabled." + "desc": "Missing required field unix_eca_crl_path.", + "first_action": "Set the policy field unix_eca_crl_path or change", + "full_action": "Set the policy field unix_eca_crl_path or change\nunix_eca_crl_check_level to either use_cdp or disabled." }, "1009": { "code": 1009, - "desc": "Missing requerido field win_eca_crl_path.", - "first_action": "Set o policy field win_eca_crl_path ou change", - "full_action": "Set o policy field win_eca_crl_path ou change\nwin_eca_crl_check_level to either use_cdp ou disabled." + "desc": "Missing required field win_eca_crl_path.", + "first_action": "Set the policy field win_eca_crl_path or change", + "full_action": "Set the policy field win_eca_crl_path or change\nwin_eca_crl_check_level to either use_cdp or disabled." }, "1010": { "code": 1010, - "desc": "Field unix_eca_crl_check_level must be use_path if field unix_eca_crl_path está specified.", - "first_action": "Set o policy field unix_eca_crl_check_level to", - "full_action": "Set o policy field unix_eca_crl_check_level to\nuse_path ou reset o policy field unix_eca_crl_path." + "desc": "Field unix_eca_crl_check_level must be use_path if field unix_eca_crl_path is specified.", + "first_action": "Set the policy field unix_eca_crl_check_level to", + "full_action": "Set the policy field unix_eca_crl_check_level to\nuse_path or reset the policy field unix_eca_crl_path." }, "1011": { "code": 1011, - "desc": "Field win_eca_crl_check_level must be use_path if field win_eca_crl_path está specified.", + "desc": "Field win_eca_crl_check_level must be use_path if field win_eca_crl_path is specified.", "first_action": "Setthepolicyfieldwin_eca_crl_check_leveltouse_path", - "full_action": "Setthepolicyfieldwin_eca_crl_check_leveltouse_path\nou reset o policy field win_eca_crl_path." + "full_action": "Setthepolicyfieldwin_eca_crl_check_leveltouse_path\nor reset the policy field win_eca_crl_path." }, "1012": { "code": 1012, - "desc": "Missing requerido field win_eca_crl_check_level.", - "first_action": "Set o policy field win_eca_crl_check_level e also", - "full_action": "Set o policy field win_eca_crl_check_level e also\nset o policy field win_eca_crl_path if win_eca_crl_check_level está use_path." + "desc": "Missing required field win_eca_crl_check_level.", + "first_action": "Set the policy field win_eca_crl_check_level and also", + "full_action": "Set the policy field win_eca_crl_check_level and also\nset the policy field win_eca_crl_path if win_eca_crl_check_level is use_path." }, "1013": { "code": 1013, - "desc": "Inválido deployment_cert_source value, arquivo must be specified.", + "desc": "Invalid deployment_cert_source value, file must be specified.", "first_action": "Changedeployment_cert_sourcevaluefromcert_store", - "full_action": "Changedeployment_cert_sourcevaluefromcert_store\nto arquivo." + "full_action": "Changedeployment_cert_sourcevaluefromcert_store\nto file." }, "1014": { "code": 1014, "desc": "Invaliddeployment_cert_sourcevalue,cert_storemustbespecified.", - "first_action": "Change o deployment_cert_source value from arquivo", - "full_action": "Change o deployment_cert_source value from arquivo\nto cert_store." + "first_action": "Change the deployment_cert_source value from file", + "full_action": "Change the deployment_cert_source value from file\nto cert_store." }, "1019": { "code": 1019, - "desc": "Falhou to get Snapshot Manager capability.", - "first_action": "Garanta que o NetBackup service - nbemm está up e executando.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Garanta que o NetBackup service - nbemm está up e executando.\n■ Executar um refresh configuration operation de o Snapshot Manager usando o\ntpconfig comando to reset capability parameters in EMM." + "desc": "Failed to get Snapshot Manager capability.", + "first_action": "Ensure that the NetBackup service - nbemm is up and running.", + "full_action": "Perform the following, as appropriate:\n■ Ensure that the NetBackup service - nbemm is up and running.\n■ Perform a refresh configuration operation of the Snapshot Manager using the\ntpconfig command to reset capability parameters in EMM." }, "1020": { "code": 1020, - "desc": "Falhou to get o last backup snapshot ID.", - "first_action": "Garanta que o last reference snapshot image exists", - "full_action": "Garanta que o last reference snapshot image exists\nbefore you retry um VCT-based incremental backup." + "desc": "Failed to get the last backup snapshot ID.", + "first_action": "Ensure that the last reference snapshot image exists", + "full_action": "Ensure that the last reference snapshot image exists\nbefore you retry a VCT-based incremental backup." }, "1021": { "code": 1021, - "desc": "O maintenance version que está specified está não o same base version como instalado version.", - "first_action": "If package o name está maint.nbclient_8.2.3.2 then change to", - "full_action": "Change package name to match o base version.\nPara example:\n■ If package o name está maint.nbclient_8.2.3.2 then change to\nmaint.nbclient.8.2.2.2 which matches o base release version 8.2.2 de\no instalado package maint.nbclient.8.2.2.1." + "desc": "The maintenance version that is specified is not the same base version as installed version.", + "first_action": "If package the name is maint.nbclient_8.2.3.2 then change to", + "full_action": "Change package name to match the base version.\nFor example:\n■ If package the name is maint.nbclient_8.2.3.2 then change to\nmaint.nbclient.8.2.2.2 which matches the base release version 8.2.2 of\nthe installed package maint.nbclient.8.2.2.1." }, "1022": { "code": 1022, - "desc": "O maintenance version que está specified não é possível be older than instalado version, ou não update requerido.", + "desc": "The maintenance version that is specified cannot be older than installed version, or no update required.", "first_action": "Ifinstalledpackageismaint.nbclient_8.3.0.5thenanynewmaint.nbclient", - "full_action": "Change o maint.client ou maint.nbserver package\nnames version to be o same ou newer than o instalado package version. Para\nexample:\nPara example:\n■ Ifinstalledpackageismaint.nbclient_8.3.0.5thenanynewmaint.nbclient\npackage names version must be 8.3.0.[5-9]." + "full_action": "Change the maint.client or maint.nbserver package\nnames version to be the same or newer than the installed package version. For\nexample:\nFor example:\n■ Ifinstalledpackageismaint.nbclient_8.3.0.5thenanynewmaint.nbclient\npackage names version must be 8.3.0.[5-9]." }, "1023": { "code": 1023, - "desc": "Inválido package name specified.", + "desc": "Invalid package name specified.", "first_action": "8.2.1.", - "full_action": "Change package name to match o format requerido\n_. Onde o Está um valid um NetBackup release like\n8.2.1.\nO format de o package name must be one de o seguinte:\n■ nbclient_\n■ nbserver_\n■ nbeeb_\n■ nbeeb.client_\n■ nbeeb.server_\n■ maint.nbclient_\n■ maint.nbserver_" + "full_action": "Change package name to match the format required\n_. Where the Is a valid a NetBackup release like\n8.2.1.\nThe format of the package name must be one of the following:\n■ nbclient_\n■ nbserver_\n■ nbeeb_\n■ nbeeb.client_\n■ nbeeb.server_\n■ maint.nbclient_\n■ maint.nbserver_" }, "1024": { "code": 1024, - "desc": "O BigData policy não é possível be used to protect Nutanix AHV VMs usando um backup host com NetBackup version 8.3 ou later.", - "first_action": "Migrate o policy por editing o existing BigData policy", - "full_action": "Migrate o policy por editing o existing BigData policy\ne selecting o policy type como Hypervisor. Refer to o Migrating BigData policy\nto Hypervisor policy topic in o NetBackup para Nutanix Acropolis Hypervisor (AHV)\nAdministrator’s Guide." + "desc": "The BigData policy cannot be used to protect Nutanix AHV VMs using a backup host with NetBackup version 8.3 or later.", + "first_action": "Migrate the policy by editing the existing BigData policy", + "full_action": "Migrate the policy by editing the existing BigData policy\nand selecting the policy type as Hypervisor. Refer to the Migrating BigData policy\nto Hypervisor policy topic in the NetBackup for Nutanix Acropolis Hypervisor (AHV)\nAdministrator’s Guide." }, "1026": { "code": 1026, - "desc": "Não é possível start o backup job, como another backup para o same asset, usando o same policy está already executando.", - "first_action": "Wait para o current backup to finish before you initiate um", - "full_action": "Wait para o current backup to finish before you initiate um\nnew backup para o same asset, com o same policy." + "desc": "Cannot start the backup job, as another backup for the same asset, using the same policy is already running.", + "first_action": "Wait for the current backup to finish before you initiate a", + "full_action": "Wait for the current backup to finish before you initiate a\nnew backup for the same asset, with the same policy." }, "1057": { "code": 1057, - "desc": "Um data corruption has been detected.", - "first_action": "Search storaged.log on o servidor para o affected", - "full_action": "Search storaged.log on o servidor para o affected\nbackups e contate Cohesity Technical Support." + "desc": "A data corruption has been detected.", + "first_action": "Search storaged.log on the server for the affected", + "full_action": "Search storaged.log on the server for the affected\nbackups and contact Cohesity Technical Support." }, "1058": { "code": 1058, - "desc": "Um data inconsistency has been detected e corrected automatically.", - "first_action": "Search o storaged.log arquivo on o pertinent mídia", - "full_action": "Search o storaged.log arquivo on o pertinent mídia\nservidor. Contate support to investigate o raiz cause if o problema persists." + "desc": "A data inconsistency has been detected and corrected automatically.", + "first_action": "Search the storaged.log file on the pertinent media", + "full_action": "Search the storaged.log file on the pertinent media\nserver. Contact support to investigate the root cause if the problem persists." }, "1227": { "code": 1227, - "desc": "Key group does não have um active key.", - "first_action": "Run o seguinte to verifique que o key record está in um active state: nbkmscmd", - "full_action": "Veja o errorDetails in o JSON output para additional\ndetails.\nVerifique whether requerido keys estão present in Key Management Service (KMS) por\nexecutando o seguinte commands:\n■ Run o seguinte to verifique que o key record está in um active state: nbkmscmd\n-listkeys -name -keyGroupName \n■ Run o seguinte to create um new key if key está não present in um group: nbkmscmd\n-createKey -name -KeyName -keyGroupName < key group name>\n■ Runthefollowingtoactivatethekeyifanyofthekeyrecordsarenotinanactive\nstate in um group: nbkmsutil -modifykey -keyname -kgname\n -activate\nIf o issue persists, visit o Cohesity Technical Support website. O Cohesity\nTechnical Support website offers additional informação to help you troubleshoot\nthis issue." + "desc": "Key group does not have an active key.", + "first_action": "Run the following to verify that the key record is in an active state: nbkmscmd", + "full_action": "See the errorDetails in the JSON output for additional\ndetails.\nCheck whether required keys are present in Key Management Service (KMS) by\nrunning the following commands:\n■ Run the following to verify that the key record is in an active state: nbkmscmd\n-listkeys -name -keyGroupName \n■ Run the following to create a new key if key is not present in a group: nbkmscmd\n-createKey -name -KeyName -keyGroupName < key group name>\n■ Runthefollowingtoactivatethekeyifanyofthekeyrecordsarenotinanactive\nstate in a group: nbkmsutil -modifykey -keyname -kgname\n -activate\nIf the issue persists, visit the Cohesity Technical Support website. The Cohesity\nTechnical Support website offers additional information to help you troubleshoot\nthis issue." }, "1229": { "code": 1229, - "desc": "Key group foi não found.", - "first_action": "Run o seguinte to verifique whether o group está present in o KMS servidor:", - "full_action": "Veja o errorDetails in o JSON output para additional\ndetails.\n■ Run o seguinte to verifique whether o group está present in o KMS servidor:\nnbkmscmd -listkeys -name -keyGroupName \n■ Run o seguinte to create um key group in o KMS servidor: nbkmscmd\n-createKey -name -KeyName -keyGroupName \nIf o issue persists, visit o Cohesity Technical Support website. O Cohesity\nTechnical Support website offers additional informação to help you troubleshoot\nthis issue." + "desc": "Key group was not found.", + "first_action": "Run the following to verify whether the group is present in the KMS server:", + "full_action": "See the errorDetails in the JSON output for additional\ndetails.\n■ Run the following to verify whether the group is present in the KMS server:\nnbkmscmd -listkeys -name -keyGroupName \n■ Run the following to create a key group in the KMS server: nbkmscmd\n-createKey -name -KeyName -keyGroupName \nIf the issue persists, visit the Cohesity Technical Support website. The Cohesity\nTechnical Support website offers additional information to help you troubleshoot\nthis issue." }, "1260": { "code": 1260, - "desc": "Key record foi não found.", + "desc": "Key record was not found.", "first_action": "1. GetconfiguredKMSinformationbyrunning:nbkmscmd -listKMSConfig -name", - "full_action": "Veja o errorDetails in o JSON output para additional\ndetails.\nVerifique whether requerido keys estão present in Key Management Service (KMS) por\nexecutando o seguinte commands:\n1. GetconfiguredKMSinformationbyrunning:nbkmscmd -listKMSConfig -name\n\n■ IftheEnabled para BackupoptionissettofalsefortheexistingKMSserver\nthen set it to true state por executando: nbkmscmd -updateKMSConfig\n■ If o KMS configuration está não present para o KMS servidor then add um new\nKMS configuration com o Enabled para Backup option por executando:\nnbkmscmd -configureKMS\nVerifythatthedesiredkeygroupsarepresentintheKMSserverwhereEnabled\nPara Backup está set to true.\n2. Get list de keys por executando: nbkmscmd -listKeys -name\n\n3. If o key está não present then run nbkmscmd -createKey -name\n -KeyName \n-keyGroupName to\nadd o key record to o KMS servidor.\nIf o issue persists, visit o Cohesity Technical Support website. O Cohesity\nTechnical Support website offers additional informação to help you troubleshoot\nthis issue." + "full_action": "See the errorDetails in the JSON output for additional\ndetails.\nCheck whether required keys are present in Key Management Service (KMS) by\nrunning the following commands:\n1. GetconfiguredKMSinformationbyrunning:nbkmscmd -listKMSConfig -name\n\n■ IftheEnabled for BackupoptionissettofalsefortheexistingKMSserver\nthen set it to true state by running: nbkmscmd -updateKMSConfig\n■ If the KMS configuration is not present for the KMS server then add a new\nKMS configuration with the Enabled for Backup option by running:\nnbkmscmd -configureKMS\nVerifythatthedesiredkeygroupsarepresentintheKMSserverwhereEnabled\nFor Backup is set to true.\n2. Get list of keys by running: nbkmscmd -listKeys -name\n\n3. If the key is not present then run nbkmscmd -createKey -name\n -KeyName \n-keyGroupName to\nadd the key record to the KMS server.\nIf the issue persists, visit the Cohesity Technical Support website. The Cohesity\nTechnical Support website offers additional information to help you troubleshoot\nthis issue." }, "1288": { "code": 1288, - "desc": "Falhou to retrieve o Key Management Service (KMS) details.", - "first_action": "1. Run o nbkmscmd -listKMSConfig -name ", - "full_action": "Veja o errorDetails in JSON output para additional\ndetails.\nThis erro can occur due to NetBackup Key Management Service (KMS) está não\nexecutando ou o NetBackup Key Management Service (KMS) está não configurado.\nVerifique if o NetBackup Key Management Service (KMS) está executando e configurado\npor executando o seguinte:\n1. Run o nbkmscmd -listKMSConfig -name \ncomando to verifique if o nbkms service está configurado.\n2. If o nbkms service está não configurado then run o nbkmscmd -configureKMS\nto configure o NetBackup KMS service.\n3. Runthenbkmscmd -discoverNBkmscommandifthenbkmscmd -configureKMS\ncomando recommends executando this comando.\n4. Verifique que o nbkms service está configurado por executando o nbkmscmd\n-listKMSConfig -name comando.\n5. Verifique que o nbkms service está up e in um executando state por executing o\nnbkmscmd -validateKMSConfig -name \ncomando.\nIf o issue persists, visit o Cohesity Technical Support website. O Cohesity\nTechnical Support website offers additional informação to help you troubleshoot\nthis issue." + "desc": "Failed to retrieve the Key Management Service (KMS) details.", + "first_action": "1. Run the nbkmscmd -listKMSConfig -name ", + "full_action": "See the errorDetails in JSON output for additional\ndetails.\nThis error can occur due to NetBackup Key Management Service (KMS) is not\nrunning or the NetBackup Key Management Service (KMS) is not configured.\nVerify if the NetBackup Key Management Service (KMS) is running and configured\nby running the following:\n1. Run the nbkmscmd -listKMSConfig -name \ncommand to verify if the nbkms service is configured.\n2. If the nbkms service is not configured then run the nbkmscmd -configureKMS\nto configure the NetBackup KMS service.\n3. Runthenbkmscmd -discoverNBkmscommandifthenbkmscmd -configureKMS\ncommand recommends running this command.\n4. Verify that the nbkms service is configured by running the nbkmscmd\n-listKMSConfig -name command.\n5. Verify that the nbkms service is up and in a running state by executing the\nnbkmscmd -validateKMSConfig -name \ncommand.\nIf the issue persists, visit the Cohesity Technical Support website. The Cohesity\nTechnical Support website offers additional information to help you troubleshoot\nthis issue." }, "1289": { "code": 1289, - "desc": "Falhou to create o Key Management Service (KMS) configuration.", - "first_action": "Veja o errorDetails in JSON output para additional", - "full_action": "Veja o errorDetails in JSON output para additional\ndetails. Retry o operation e if o issue persists, visit o Cohesity Technical\nSupport website. O Cohesity Technical Support website offers additional\ninformação to help you troubleshoot this issue." + "desc": "Failed to create the Key Management Service (KMS) configuration.", + "first_action": "See the errorDetails in JSON output for additional", + "full_action": "See the errorDetails in JSON output for additional\ndetails. Retry the operation and if the issue persists, visit the Cohesity Technical\nSupport website. The Cohesity Technical Support website offers additional\ninformation to help you troubleshoot this issue." }, "1290": { "code": 1290, - "desc": "Falhou to update o KMS configuration.", + "desc": "Failed to update the KMS configuration.", "first_action": "Provide at least one attribute.", - "full_action": "When you update o KMS configuration, garanta o\nseguinte:\n■ Provide at least one attribute.\n■ To update o NetBackup KMS configuration, garanta que o KMIP attributes\nestão não provided." + "full_action": "When you update the KMS configuration, ensure the\nfollowing:\n■ Provide at least one attribute.\n■ To update the NetBackup KMS configuration, ensure that the KMIP attributes\nare not provided." }, "1291": { "code": 1291, - "desc": "TheNetBackupKeyManagementService(NBKMS)isalreadyconfigured, but não registered.", + "desc": "TheNetBackupKeyManagementService(NBKMS)isalreadyconfigured, but not registered.", "first_action": "RunthenbkmscmdcommandtodiscoverNetBackupKMS.", - "full_action": "RunthenbkmscmdcommandtodiscoverNetBackupKMS.\nPara more informação on o nbkmscmd comando, veja o NetBackup Commands\nReference Guide." + "full_action": "RunthenbkmscmdcommandtodiscoverNetBackupKMS.\nFor more information on the nbkmscmd command, see the NetBackup Commands\nReference Guide." }, "1292": { "code": 1292, - "desc": "TheNetBackupKeyManagementService(NBKMS)cannotberegistered because it está não configurado.", - "first_action": "Run o nbkmscmd comando to configure NetBackup", - "full_action": "Run o nbkmscmd comando to configure NetBackup\nKMS. This step automatically registers NetBackup KMS. Para more informação on\no nbkmscmd comando, veja o NetBackup Commands Reference Guide." + "desc": "TheNetBackupKeyManagementService(NBKMS)cannotberegistered because it is not configured.", + "first_action": "Run the nbkmscmd command to configure NetBackup", + "full_action": "Run the nbkmscmd command to configure NetBackup\nKMS. This step automatically registers NetBackup KMS. For more information on\nthe nbkmscmd command, see the NetBackup Commands Reference Guide." }, "1293": { "code": 1293, - "desc": "O JSON string não é possível be processed.", - "first_action": "Veja o errorDetails in o response JSON output para", - "full_action": "Veja o errorDetails in o response JSON output para\nadditional details. Um retry de o same operation should resolve o issue. Para more\ndetails, review o nbkmiputil e nbwebservice logs. If o issue persists, visit\no Cohesity Technical Support website. O Cohesity Technical Support website\noffers additional informação to help you troubleshoot this issue." + "desc": "The JSON string cannot be processed.", + "first_action": "See the errorDetails in the response JSON output for", + "full_action": "See the errorDetails in the response JSON output for\nadditional details. A retry of the same operation should resolve the issue. For more\ndetails, review the nbkmiputil and nbwebservice logs. If the issue persists, visit\nthe Cohesity Technical Support website. The Cohesity Technical Support website\noffers additional information to help you troubleshoot this issue." }, "1294": { "code": 1294, - "desc": "Time-out has ocorreu sending o JSON string to o NetBackup key management utility.", - "first_action": "Veja o errorDetails in o JSON output para additional", - "full_action": "Veja o errorDetails in o JSON output para additional\ndetails.\nVerifique o KMS servidor name e o port number in o KMS configuration usando\no nbkmscmd -listKMSConfig comando. If everything seems to proper in o\nKMS configuration, run o nbkmscmd -validateKMSConfig -name comando.\nUm retry de o same operation can resolve o issue. Para more details, review o\nnbkmiputil e nbwebservice logs. If o issue persists, visit o Cohesity\nTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffersadditional\ninformação to help you troubleshoot this issue." + "desc": "Time-out has occurred sending the JSON string to the NetBackup key management utility.", + "first_action": "See the errorDetails in the JSON output for additional", + "full_action": "See the errorDetails in the JSON output for additional\ndetails.\nVerify the KMS server name and the port number in the KMS configuration using\nthe nbkmscmd -listKMSConfig command. If everything seems to proper in the\nKMS configuration, run the nbkmscmd -validateKMSConfig -name command.\nA retry of the same operation can resolve the issue. For more details, review the\nnbkmiputil and nbwebservice logs. If the issue persists, visit the Cohesity\nTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffersadditional\ninformation to help you troubleshoot this issue." }, "1295": { "code": 1295, - "desc": "O JSON string não é possível be ler from o NetBackup key management utility como o utility está executed.", - "first_action": "Veja o errorDetails in JSON output para additional", - "full_action": "Veja o errorDetails in JSON output para additional\ndetails.Aretryofthesameoperationcanresolvetheissue.Formoredetails,review\no nbkmiputil e nbwebservice logs. If o issue persists, visit o Cohesity\nTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffersadditional\ninformação to help you troubleshoot this issue." + "desc": "The JSON string cannot be read from the NetBackup key management utility as the utility is executed.", + "first_action": "See the errorDetails in JSON output for additional", + "full_action": "See the errorDetails in JSON output for additional\ndetails.Aretryofthesameoperationcanresolvetheissue.Formoredetails,review\nthe nbkmiputil and nbwebservice logs. If the issue persists, visit the Cohesity\nTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffersadditional\ninformation to help you troubleshoot this issue." }, "1296": { "code": 1296, - "desc": "O KMS configuration não é possível be validated.", - "first_action": "Garanta que o nbkms service está up e executando.", - "full_action": "Garanta que o nbkms service está up e executando." + "desc": "The KMS configuration cannot be validated.", + "first_action": "Ensure that the nbkms service is up and running.", + "full_action": "Ensure that the nbkms service is up and running." }, "1297": { "code": 1297, - "desc": "O KMS key não é possível be created.", + "desc": "The KMS key cannot be created.", "first_action": "EnsurethattherequiredKMSkeyattributesareprovided.", "full_action": "EnsurethattherequiredKMSkeyattributesareprovided." }, "1298": { "code": 1298, - "desc": "Não é possível communicate com one ou more key management servers.", - "first_action": "Run o nbkmscmd -validateKMSConfig -name comando to retrieve e review o erro details. You can\nuse o nbkmscmd -listKMSConfig comando to veja o configurado KMS servidor\ne o ." + "desc": "Cannot communicate with one or more key management servers.", + "first_action": "Run the nbkmscmd -validateKMSConfig -name command to retrieve and review the error details. You can\nuse the nbkmscmd -listKMSConfig command to see the configured KMS server\nand the ." }, "1299": { "code": 1299, - "desc": "O KMS configuration pre-check falhou.", - "first_action": "You need to specify either credId ou pkiAttributes. Do não specify both at", - "full_action": "Verifique o seguinte como needed:\n■ You need to specify either credId ou pkiAttributes. Do não specify both at\no same time.\n■ Verifique que you have one de o seguinte mandatory fields: credId ou\npkiAttributes.\n■ Verifique que o mandatory field kmsServerAttributes está não blank.\n■ Review o certificate. O certificate está mandatory e it não é possível be blank.\n■ Review o CA Certificate. O CA Certificate está mandatory e it não é possível be\nblank.\n■ Review o private key. O private key está mandatory e it não é possível be blank.\n■ Verifique que NBKMS está não used. O operation está não supported para que KMS type." + "desc": "The KMS configuration pre-check failed.", + "first_action": "You need to specify either credId or pkiAttributes. Do not specify both at", + "full_action": "Verify the following as needed:\n■ You need to specify either credId or pkiAttributes. Do not specify both at\nthe same time.\n■ Verify that you have one of the following mandatory fields: credId or\npkiAttributes.\n■ Verify that the mandatory field kmsServerAttributes is not blank.\n■ Review the certificate. The certificate is mandatory and it cannot be blank.\n■ Review the CA Certificate. The CA Certificate is mandatory and it cannot be\nblank.\n■ Review the private key. The private key is mandatory and it cannot be blank.\n■ Verify that NBKMS is not used. The operation is not supported for that KMS type." }, "1304": { "code": 1304, - "desc": "Falhou to update key in KMS.", - "first_action": "Confirm que o NetBackup KMS está configurado.", - "full_action": "Executar o seguinte como appropriate:\n■ Confirm que o NetBackup KMS está configurado.\n■ If o operation runs com o REST API, o request payload may be inválido.\nReview o API documentation para o correct request payload.\n■ If o operation continues to fail, contate Cohesity Technical Support." + "desc": "Failed to update key in KMS.", + "first_action": "Confirm that the NetBackup KMS is configured.", + "full_action": "Perform the following as appropriate:\n■ Confirm that the NetBackup KMS is configured.\n■ If the operation runs with the REST API, the request payload may be invalid.\nReview the API documentation for the correct request payload.\n■ If the operation continues to fail, contact Cohesity Technical Support." }, "1305": { "code": 1305, - "desc": "Falhou to update key group in KMS.", - "first_action": "Confirm que o NetBackup KMS está configurado.", - "full_action": "Executar o seguinte como appropriate:\n■ Confirm que o NetBackup KMS está configurado.\n■ If o operation runs com o REST API, o request payload may be inválido.\nReview o API documentation para o correct request payload.\n■ If o operation continues to fail, contate Cohesity Technical Support." + "desc": "Failed to update key group in KMS.", + "first_action": "Confirm that the NetBackup KMS is configured.", + "full_action": "Perform the following as appropriate:\n■ Confirm that the NetBackup KMS is configured.\n■ If the operation runs with the REST API, the request payload may be invalid.\nReview the API documentation for the correct request payload.\n■ If the operation continues to fail, contact Cohesity Technical Support." }, "1306": { "code": 1306, - "desc": "Falhou to excluir key in KMS.", - "first_action": "Confirm que o NetBackup KMS está configurado.", - "full_action": "Executar o seguinte como appropriate:\n■ Confirm que o NetBackup KMS está configurado.\n■ If o operation continues to fail, contate Cohesity Technical Support." + "desc": "Failed to delete key in KMS.", + "first_action": "Confirm that the NetBackup KMS is configured.", + "full_action": "Perform the following as appropriate:\n■ Confirm that the NetBackup KMS is configured.\n■ If the operation continues to fail, contact Cohesity Technical Support." }, "1307": { "code": 1307, - "desc": "Falhou to excluir key group in KMS.", - "first_action": "Confirm que o NetBackup KMS está configurado.", - "full_action": "Executar o seguinte como appropriate:\n■ Confirm que o NetBackup KMS está configurado.\n■ If o operation continues to fail, contate Cohesity Technical Support." + "desc": "Failed to delete key group in KMS.", + "first_action": "Confirm that the NetBackup KMS is configured.", + "full_action": "Perform the following as appropriate:\n■ Confirm that the NetBackup KMS is configured.\n■ If the operation continues to fail, contact Cohesity Technical Support." }, "1308": { "code": 1308, - "desc": "Falhou to create key group in KMS.", - "first_action": "Confirm que o NetBackup KMS está configurado.", - "full_action": "Executar o seguinte como appropriate:\n■ Confirm que o NetBackup KMS está configurado.\n■ If o operation runs com o REST API, o request payload may be inválido.\nReview o API documentation para o correct request payload.\n■ If o operation continues to fail, contate Cohesity Technical Support." + "desc": "Failed to create key group in KMS.", + "first_action": "Confirm that the NetBackup KMS is configured.", + "full_action": "Perform the following as appropriate:\n■ Confirm that the NetBackup KMS is configured.\n■ If the operation runs with the REST API, the request payload may be invalid.\nReview the API documentation for the correct request payload.\n■ If the operation continues to fail, contact Cohesity Technical Support." }, "1309": { "code": 1309, - "desc": "Falhou to modify Host Master Key.", - "first_action": "Confirm que o NetBackup KMS está configurado.", - "full_action": "Executar o seguinte como appropriate:\n■ Confirm que o NetBackup KMS está configurado.\n■ If o operation continues to fail, contate Cohesity Technical Support." + "desc": "Failed to modify Host Master Key.", + "first_action": "Confirm that the NetBackup KMS is configured.", + "full_action": "Perform the following as appropriate:\n■ Confirm that the NetBackup KMS is configured.\n■ If the operation continues to fail, contact Cohesity Technical Support." }, "1310": { "code": 1310, - "desc": "Falhou to modify Key Protection Key.", - "first_action": "Confirm que o NetBackup KMS está configurado.", - "full_action": "Executar o seguinte como appropriate:\n■ Confirm que o NetBackup KMS está configurado.\n■ If o operation continues to fail, contate Cohesity Technical Support." + "desc": "Failed to modify Key Protection Key.", + "first_action": "Confirm that the NetBackup KMS is configured.", + "full_action": "Perform the following as appropriate:\n■ Confirm that the NetBackup KMS is configured.\n■ If the operation continues to fail, contact Cohesity Technical Support." }, "1311": { "code": 1311, - "desc": "Falhou to recover key from KMS.", - "first_action": "Confirm que o NetBackup KMS está configurado.", - "full_action": "Executar o seguinte como appropriate:\n■ Confirm que o NetBackup KMS está configurado.\n■ If o operation runs com o REST API, o request payload may be inválido.\nReview o API documentation para o correct request payload.\n■ If o operation continues to fail, contate Cohesity Technical Support." + "desc": "Failed to recover key from KMS.", + "first_action": "Confirm that the NetBackup KMS is configured.", + "full_action": "Perform the following as appropriate:\n■ Confirm that the NetBackup KMS is configured.\n■ If the operation runs with the REST API, the request payload may be invalid.\nReview the API documentation for the correct request payload.\n■ If the operation continues to fail, contact Cohesity Technical Support." }, "1312": { "code": 1312, - "desc": "Falhou to fetch key group from KMS.", - "first_action": "Confirm que o NetBackup KMS está configurado.", - "full_action": "Executar o seguinte como appropriate:\n■ Confirm que o NetBackup KMS está configurado.\n■ If o operation continues to fail, contate Cohesity Technical Support." + "desc": "Failed to fetch key group from KMS.", + "first_action": "Confirm that the NetBackup KMS is configured.", + "full_action": "Perform the following as appropriate:\n■ Confirm that the NetBackup KMS is configured.\n■ If the operation continues to fail, contact Cohesity Technical Support." }, "1401": { "code": 1401, - "desc": "Inválido arguments received", - "first_action": "Garanta que todos o requerido parameters estão passed com", - "full_action": "Garanta que todos o requerido parameters estão passed com\no correct values." + "desc": "Invalid arguments received", + "first_action": "Ensure that all the required parameters are passed with", + "full_action": "Ensure that all the required parameters are passed with\nthe correct values." }, "1402": { "code": 1402, - "desc": "Hold ID ou Hold name argument está inválido", + "desc": "Hold ID or Hold name argument is invalid", "first_action": "Checkthe-holdidand-holdnameoptionsforvalidvalues.", "full_action": "Checkthe-holdidand-holdnameoptionsforvalidvalues." }, "1403": { "code": 1403, - "desc": "Backup ID argument está inválido", - "first_action": "Verifique o -backupid option para um valid value.", - "full_action": "Verifique o -backupid option para um valid value." + "desc": "Backup ID argument is invalid", + "first_action": "Check the -backupid option for a valid value.", + "full_action": "Check the -backupid option for a valid value." }, "1405": { "code": 1405, - "desc": "Não images estão found.", - "first_action": "Verifique que o -backupid option está para um valid image.", - "full_action": "Verifique que o -backupid option está para um valid image." + "desc": "No images are found.", + "first_action": "Check that the -backupid option is for a valid image.", + "full_action": "Check that the -backupid option is for a valid image." }, "1407": { "code": 1407, - "desc": "Inválido hold state", - "first_action": "Retry o operation e if o issue persists, visit", - "full_action": "Retry o operation e if o issue persists, visit\nsupport.veritas.com. O Cohesity Technical Support website site offers additional\ninformação to help you troubleshoot this issue." + "desc": "Invalid hold state", + "first_action": "Retry the operation and if the issue persists, visit", + "full_action": "Retry the operation and if the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support website site offers additional\ninformation to help you troubleshoot this issue." }, "1408": { "code": 1408, - "desc": "Banco de dados erro", - "first_action": "Make sure que o Hold banco de dados e o DBM services", - "full_action": "Make sure que o Hold banco de dados e o DBM services\nestão executando." + "desc": "Database error", + "first_action": "Make sure that the Hold database and the DBM services", + "full_action": "Make sure that the Hold database and the DBM services\nare running." }, "1409": { "code": 1409, - "desc": "Não foi possível to conectar to banco de dados", - "first_action": "Make sure que o Hold banco de dados e o DBM services", - "full_action": "Make sure que o Hold banco de dados e o DBM services\nestão executando." + "desc": "Unable to connect to database", + "first_action": "Make sure that the Hold database and the DBM services", + "full_action": "Make sure that the Hold database and the DBM services\nare running." }, "1410": { "code": 1410, - "desc": "Não data found", - "first_action": "Make sure que todos o requerido parameters estão passed", - "full_action": "Make sure que todos o requerido parameters estão passed\ncom their correct values." + "desc": "No data found", + "first_action": "Make sure that all the required parameters are passed", + "full_action": "Make sure that all the required parameters are passed\nwith their correct values." }, "1411": { "code": 1411, - "desc": "Catalog erro", - "first_action": "Verifique que o image copy on which o hold operation", - "full_action": "Verifique que o image copy on which o hold operation\nestá applied está valid e não expired." + "desc": "Catalog error", + "first_action": "Check that the image copy on which the hold operation", + "full_action": "Check that the image copy on which the hold operation\nis applied is valid and not expired." }, "1412": { "code": 1412, - "desc": "Hold record está being updated", - "first_action": "Retry o operation at um later time ou restart o nbim", - "full_action": "Retry o operation at um later time ou restart o nbim\nservice." + "desc": "Hold record is being updated", + "first_action": "Retry the operation at a later time or restart the nbim", + "full_action": "Retry the operation at a later time or restart the nbim\nservice." }, "1413": { "code": 1413, - "desc": "Solicitado hold está não found", - "first_action": "Verifique o -holdname e -holdid options. You can use", - "full_action": "Verifique o -holdname e -holdid options. You can use\nnbholdutil -list comando." + "desc": "Requested hold is not found", + "first_action": "Check the -holdname and -holdid options. You can use", + "full_action": "Check the -holdname and -holdid options. You can use\nnbholdutil -list command." }, "1414": { "code": 1414, "desc": "Duplicate hold found", - "first_action": "Try um different name.", - "full_action": "Try um different name." + "first_action": "Try a different name.", + "full_action": "Try a different name." }, "1415": { "code": 1415, "desc": "Duplicate image found", - "first_action": "Não disponível", - "full_action": "Não disponível" + "first_action": "Not available", + "full_action": "Not available" }, "1416": { "code": 1416, - "desc": "Partially falhou due to duplicate image", - "first_action": "Não disponível", - "full_action": "Não disponível" + "desc": "Partially failed due to duplicate image", + "first_action": "Not available", + "full_action": "Not available" }, "1417": { "code": 1417, - "desc": "Partially falhou due to unhold image", - "first_action": "Make sure que you provide o correct backup ID e", - "full_action": "Make sure que you provide o correct backup ID e\nque it está present in o current hold." + "desc": "Partially failed due to unhold image", + "first_action": "Make sure that you provide the correct backup ID and", + "full_action": "Make sure that you provide the correct backup ID and\nthat it is present in the current hold." }, "1418": { "code": 1418, - "desc": "Solicitado image está não found", - "first_action": "Não disponível", - "full_action": "Não disponível" + "desc": "Requested image is not found", + "first_action": "Not available", + "full_action": "Not available" }, "1419": { "code": 1419, - "desc": "Partially falhou due to inválido image copy", - "first_action": "Não disponível", - "full_action": "Não disponível" + "desc": "Partially failed due to invalid image copy", + "first_action": "Not available", + "full_action": "Not available" }, "1420": { "code": 1420, - "desc": "Não é possível expire on hold image copy.", - "first_action": "Remove todos holds from this backup image. Ou remove", - "full_action": "Remove todos holds from this backup image. Ou remove\nholds from todos images on this backup ID to expire o backup image." + "desc": "Cannot expire on hold image copy.", + "first_action": "Remove all holds from this backup image. Or remove", + "full_action": "Remove all holds from this backup image. Or remove\nholds from all images on this backup ID to expire the backup image." }, "1421": { "code": 1421, - "desc": "Active holds não é possível be changed", - "first_action": "Restart o NBIM service", - "full_action": "Restart o NBIM service" + "desc": "Active holds cannot be changed", + "first_action": "Restart the NBIM service", + "full_action": "Restart the NBIM service" }, "1422": { "code": 1422, - "desc": "Não é possível deassign mídia on hold", - "first_action": "Lift o holds on o image copies que estão salvo up on", - "full_action": "Lift o holds on o image copies que estão salvo up on\no mídia being de-assigned." + "desc": "Cannot deassign media on hold", + "first_action": "Lift the holds on the image copies that are backed up on", + "full_action": "Lift the holds on the image copies that are backed up on\nthe media being de-assigned." }, "1423": { "code": 1423, - "desc": "Não foi possível to retrieve hold status de o image copies", - "first_action": "Não disponível", - "full_action": "Não disponível" + "desc": "Unable to retrieve hold status of the image copies", + "first_action": "Not available", + "full_action": "Not available" }, "1425": { "code": 1425, - "desc": "Solicitado hold está não found", - "first_action": "Use o nbholdutil -list to list todos holds. Verifique que", - "full_action": "Use o nbholdutil -list to list todos holds. Verifique que\no specified -holdname e -holdid options estão valid." + "desc": "Requested hold is not found", + "first_action": "Use the nbholdutil -list to list all holds. Check that", + "full_action": "Use the nbholdutil -list to list all holds. Check that\nthe specified -holdname and -holdid options are valid." }, "1426": { "code": 1426, - "desc": "Retired holds não é possível be changed", - "first_action": "Não disponível", - "full_action": "Não disponível" + "desc": "Retired holds cannot be changed", + "first_action": "Not available", + "full_action": "Not available" }, "1500": { "code": 1500, - "desc": "Armazenamento unidade does não exist ou não é possível be used onde specified", + "desc": "Storage unit does not exist or cannot be used where specified", "first_action": "VerifythatthespecifiedstorageunitorstorageunitgroupexistsintheNetBackup", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ VerifythatthespecifiedstorageunitorstorageunitgroupexistsintheNetBackup\nbanco de dados.\n■ Verifique que o specified armazenamento unidade está não de type BasicDisk ou Staging,\nbecause armazenamento lifecycle policies do não support them.\n■ Verifique que o armazenamento unidade está não specified para snapshot destinations in armazenamento\nlifecyclepolicy.Snapshotdestinationsdonotrequireastorageunitinthestorage\nlifecycle policy." + "full_action": "Do the following, as appropriate:\n■ VerifythatthespecifiedstorageunitorstorageunitgroupexistsintheNetBackup\ndatabase.\n■ Verify that the specified storage unit is not of type BasicDisk or Staging,\nbecause storage lifecycle policies do not support them.\n■ Verify that the storage unit is not specified for snapshot destinations in storage\nlifecyclepolicy.Snapshotdestinationsdonotrequireastorageunitinthestorage\nlifecycle policy." }, "1501": { "code": 1501, - "desc": "Source operation não é possível be used onde specified", - "first_action": "Verifique que o specified source refers to um valid destination in o list de", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Verifique que o specified source refers to um valid destination in o list de\ndestinations in armazenamento lifecycle policy.\n■ Verifique que o Backup ou Snapshot destination type does não have qualquer source\nspecified. If you use nbstl to configure armazenamento lifecycle policy, use value zero\n(0) como o source para um backup ou um snapshot destination type.\n■ Verifique que o destination que refers to o specified source está não um Snapshot\ndestinationtype.NetBackupcannotduplicateabackupimagethatusessnapshot\ncopy como um source.\n■ Verifique que o specified source does não refer to o destination itself para which\no source está mentioned.\n■ Verifique que o specified list de destinations in um armazenamento lifecycle has um circular\ndependency para o source.\n■ Para cloud snapshot replication, o source must be snapshot operation." + "desc": "Source operation cannot be used where specified", + "first_action": "Verify that the specified source refers to a valid destination in the list of", + "full_action": "Do the following, as appropriate:\n■ Verify that the specified source refers to a valid destination in the list of\ndestinations in storage lifecycle policy.\n■ Verify that the Backup or Snapshot destination type does not have any source\nspecified. If you use nbstl to configure storage lifecycle policy, use value zero\n(0) as the source for a backup or a snapshot destination type.\n■ Verify that the destination that refers to the specified source is not a Snapshot\ndestinationtype.NetBackupcannotduplicateabackupimagethatusessnapshot\ncopy as a source.\n■ Verify that the specified source does not refer to the destination itself for which\nthe source is mentioned.\n■ Verify that the specified list of destinations in a storage lifecycle has a circular\ndependency for the source.\n■ For cloud snapshot replication, the source must be snapshot operation." }, "1502": { "code": 1502, - "desc": "Retention type não é possível be used onde specified", - "first_action": "Verifique que o retention type que you specify in o armazenamento lifecycle policy está", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Verifique que o retention type que you specify in o armazenamento lifecycle policy está\neither de Fixed, Staged capacity managed, ou Expire after duplication.\n■ Verifique que o Expire after duplication retention type está used para um destination\napenas if it está specified como um source to other destinations in armazenamento lifecycle policy.\n■ Verifique que o Staged capacity managed retention type está used in armazenamento\nlifecyclepolicyonlyforthediskdestinationsthatsupportCapacitymanagement\ncapabilities.\n■ Verifique que o Snapshot destination type in armazenamento lifecycle policy uses Fixed\nretention type apenas.\n■ Para cloud snapshot replication apenas, fixed retention type está supported." + "desc": "Retention type cannot be used where specified", + "first_action": "Verify that the retention type that you specify in the storage lifecycle policy is", + "full_action": "Do the following, as appropriate:\n■ Verify that the retention type that you specify in the storage lifecycle policy is\neither of Fixed, Staged capacity managed, or Expire after duplication.\n■ Verify that the Expire after duplication retention type is used for a destination\nonly if it is specified as a source to other destinations in storage lifecycle policy.\n■ Verify that the Staged capacity managed retention type is used in storage\nlifecyclepolicyonlyforthediskdestinationsthatsupportCapacitymanagement\ncapabilities.\n■ Verify that the Snapshot destination type in storage lifecycle policy uses Fixed\nretention type only.\n■ For cloud snapshot replication only, fixed retention type is supported." }, "1503": { "code": 1503, - "desc": "Volume pool does não exist ou não é possível be used onde specified", - "first_action": "Verifique que o specified volume pool exists in NetBackup banco de dados.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Verifique que o specified volume pool exists in NetBackup banco de dados.\n■ Verifique que o volume pool está não specified para o Backup destination type in\narmazenamento lifecycle policy.\n■ Verifique que o volume pool está não specified para o Snapshot destination type\nin armazenamento lifecycle policy.\n■ Verifique que o volume pool está não specified para o Duplication destination type\nque uses disco armazenamento units in armazenamento lifecycle policy." + "desc": "Volume pool does not exist or cannot be used where specified", + "first_action": "Verify that the specified volume pool exists in NetBackup database.", + "full_action": "Do the following, as appropriate:\n■ Verify that the specified volume pool exists in NetBackup database.\n■ Verify that the volume pool is not specified for the Backup destination type in\nstorage lifecycle policy.\n■ Verify that the volume pool is not specified for the Snapshot destination type\nin storage lifecycle policy.\n■ Verify that the volume pool is not specified for the Duplication destination type\nthat uses disk storage units in storage lifecycle policy." }, "1504": { "code": 1504, - "desc": "Servidor group does não exist ou não é possível be used onde specified", - "first_action": "Verifique que o specified mídia servidor group exists in NetBackup banco de dados.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Verifique que o specified mídia servidor group exists in NetBackup banco de dados.\n■ Verifique que o mídia servidor group está não specified para Backup destination types\nin armazenamento lifecycle policy.\n■ Verifique que o servidor group está não specified para Snapshot destination types in\narmazenamento lifecycle policy.\n■ Verifique que o mídia servidor group está não specified para Duplication destination\ntypes que use disco armazenamento unidade in armazenamento lifecycle policy." + "desc": "Server group does not exist or cannot be used where specified", + "first_action": "Verify that the specified media server group exists in NetBackup database.", + "full_action": "Do the following, as appropriate:\n■ Verify that the specified media server group exists in NetBackup database.\n■ Verify that the media server group is not specified for Backup destination types\nin storage lifecycle policy.\n■ Verify that the server group is not specified for Snapshot destination types in\nstorage lifecycle policy.\n■ Verify that the media server group is not specified for Duplication destination\ntypes that use disk storage unit in storage lifecycle policy." }, "1505": { "code": 1505, - "desc": "Alternate ler servidor does não exist ou não é possível be used onde specified", + "desc": "Alternate read server does not exist or cannot be used where specified", "first_action": "VerifythatthespecifiedalternatereadserverexistsintheNetBackupdatabase.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ VerifythatthespecifiedalternatereadserverexistsintheNetBackupdatabase.\n■ VerifythatthealternatereadserverisnotspecifiedforBackupdestinationtypes\nin armazenamento lifecycle policy.\n■ Verifique que o alternate ler servidor está não specified para Snapshot destination\ntypes in armazenamento lifecycle policy." + "full_action": "Do the following, as appropriate:\n■ VerifythatthespecifiedalternatereadserverexistsintheNetBackupdatabase.\n■ VerifythatthealternatereadserverisnotspecifiedforBackupdestinationtypes\nin storage lifecycle policy.\n■ Verify that the alternate read server is not specified for Snapshot destination\ntypes in storage lifecycle policy." }, "1506": { "code": 1506, - "desc": "Data classification does não exist", - "first_action": "Verifique que o specified data classification exists in o", - "full_action": "Verifique que o specified data classification exists in o\nNetBackup banco de dados." + "desc": "Data classification does not exist", + "first_action": "Verify that the specified data classification exists in the", + "full_action": "Verify that the specified data classification exists in the\nNetBackup database." }, "1507": { "code": 1507, - "desc": "Inválido deferred operation flag", + "desc": "Invalid deferred operation flag", "first_action": "Ifyouusedthenbstl -defopcommand,makesurethatthespecifiedargument", - "full_action": "Do o seguinte:\n■ Ifyouusedthenbstl -defopcommand,makesurethatthespecifiedargument\nestá one de o seguinte: f, F, t, ou T.\nPara more informação on o nbstl comando, veja o NetBackup Commands\nReference Guide.\n■ Make sure que o flag está não set para o primary SLP operations: Backup,\nsnapshot, e import.\n■ Make sure que o source copy has fixed retention.\n■ Refer to o detailed log messages para more details." + "full_action": "Do the following:\n■ Ifyouusedthenbstl -defopcommand,makesurethatthespecifiedargument\nis one of the following: f, F, t, or T.\nFor more information on the nbstl command, see the NetBackup Commands\nReference Guide.\n■ Make sure that the flag is not set for the primary SLP operations: Backup,\nsnapshot, and import.\n■ Make sure that the source copy has fixed retention.\n■ Refer to the detailed log messages for more details." }, "1508": { "code": 1508, - "desc": "Armazenamento lifecycle policy exceeds maximum copies", - "first_action": "Verifique que o number de destinations que you specify in", - "full_action": "Verifique que o number de destinations que you specify in\no armazenamento lifecycle policy does não exceed 10." + "desc": "Storage lifecycle policy exceeds maximum copies", + "first_action": "Verify that the number of destinations that you specify in", + "full_action": "Verify that the number of destinations that you specify in\nthe storage lifecycle policy does not exceed 10." }, "1509": { "code": 1509, - "desc": "Armazenamento lifecycle policy exceeds maximum backup operations", + "desc": "Storage lifecycle policy exceeds maximum backup operations", "first_action": "4.)", - "full_action": "Verifique que o number de Backup type destinations que\nyou specify in o armazenamento lifecycle policy está less than ou equal to 4. (o default\nvalue de o maximum number de allowed simultaneous copies parâmetro está\n4.)" + "full_action": "Verify that the number of Backup type destinations that\nyou specify in the storage lifecycle policy is less than or equal to 4. (The default\nvalue of the maximum number of allowed simultaneous copies parameter is\n4.)" }, "1510": { "code": 1510, - "desc": "Armazenamento lifecycle policy não é possível have more than one snapshot operation", - "first_action": "Verifique que o armazenamento lifecycle policy está não configurado", - "full_action": "Verifique que o armazenamento lifecycle policy está não configurado\ncom more than one “snapshot” type de destinations." + "desc": "Storage lifecycle policy cannot have more than one snapshot operation", + "first_action": "Verify that the storage lifecycle policy is not configured", + "full_action": "Verify that the storage lifecycle policy is not configured\nwith more than one “Snapshot” type of destinations." }, "1511": { "code": 1511, "desc": "Storagelifecyclepolicymusthaveatleastonefixedretentionorsnapshot rotation operation", - "first_action": "Verifique que o specified armazenamento lifecycle policy has at", - "full_action": "Verifique que o specified armazenamento lifecycle policy has at\nleast one destination que está configurado com um Fixed retention type." + "first_action": "Verify that the specified storage lifecycle policy has at", + "full_action": "Verify that the specified storage lifecycle policy has at\nleast one destination that is configured with a Fixed retention type." }, "1512": { "code": 1512, "desc": "Storagelifecyclepolicymusthaveatleastonebackup,import,orsnapshot operation", - "first_action": "Verifique que o armazenamento lifecycle policy has at least one", - "full_action": "Verifique que o armazenamento lifecycle policy has at least one\nBackup type de destination." + "first_action": "Verify that the storage lifecycle policy has at least one", + "full_action": "Verify that the storage lifecycle policy has at least one\nBackup type of destination." }, "1513": { "code": 1513, - "desc": "Inválido priority", - "first_action": "Verifique que o duplication priority que you specify in o", - "full_action": "Verifique que o duplication priority que you specify in o\narmazenamento lifecycle policy está in o range de 0 to 99999." + "desc": "Invalid priority", + "first_action": "Verify that the duplication priority that you specify in the", + "full_action": "Verify that the duplication priority that you specify in the\nstorage lifecycle policy is in the range of 0 to 99999." }, "1514": { "code": 1514, - "desc": "Inválido operation type", - "first_action": "Verifique que o destination type que you specify on each destination in armazenamento", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Verifique que o destination type que you specify on each destination in armazenamento\nlifecycle policy está either Backup, Duplication, ou Snapshot.\n■ If you estão use o nbstl comando to configure armazenamento lifecycle policy, o\nseguinte estão o valid values para o destination type: 0 indicates Backup, 1\nindicates Duplication, e 2 indicates Snapshot." + "desc": "Invalid operation type", + "first_action": "Verify that the destination type that you specify on each destination in storage", + "full_action": "Do the following, as appropriate:\n■ Verify that the destination type that you specify on each destination in storage\nlifecycle policy is either Backup, Duplication, or Snapshot.\n■ If you are use the nbstl command to configure storage lifecycle policy, the\nfollowing are the valid values for the destination type: 0 indicates Backup, 1\nindicates Duplication, and 2 indicates Snapshot." }, "1515": { "code": 1515, - "desc": "Multiplexing value está não valid ou não é possível be used onde specified NetBackup status codes 363 NetBackup status codes", - "first_action": "If you use o nbstl comando to configure armazenamento lifecycle policy, then verifique", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ If you use o nbstl comando to configure armazenamento lifecycle policy, then verifique\nque o valid values estão used to indicate o preserve multiplexing flag para each\ndestination.Thevalue“T”or“t”indicatestrue(Preservemultiplexing).Thevalue\n“F” ou “f” indicates false (do não preserve multiplexing).\n■ Verifique que destinations de type Backup estão não configurado to preserve\nmultiplexing.\n■ Verifique que destinations de type Snapshot estão não configurado to preserve\nmultiplexing.\n■ VerifythatdestinationsoftypeDuplicationthatare usingdisk storageunitsare\nnão configurado to preserve multiplexing." + "desc": "Multiplexing value is not valid or cannot be used where specified NetBackup status codes 363 NetBackup status codes", + "first_action": "If you use the nbstl command to configure storage lifecycle policy, then verify", + "full_action": "Do the following, as appropriate:\n■ If you use the nbstl command to configure storage lifecycle policy, then verify\nthat the valid values are used to indicate the preserve multiplexing flag for each\ndestination.Thevalue“T”or“t”indicatestrue(Preservemultiplexing).Thevalue\n“F” or “f” indicates false (do not preserve multiplexing).\n■ Verify that destinations of type Backup are not configured to preserve\nmultiplexing.\n■ Verify that destinations of type Snapshot are not configured to preserve\nmultiplexing.\n■ VerifythatdestinationsoftypeDuplicationthatare usingdisk storageunitsare\nnot configured to preserve multiplexing." }, "1516": { "code": 1516, - "desc": "Todos armazenamento units ou groups must be on o same mídia servidor", - "first_action": "Verifique que todos o destinations de type Backup estão", - "full_action": "Verifique que todos o destinations de type Backup estão\naccessible por at least one common mídia servidor." + "desc": "All storage units or groups must be on the same media server", + "first_action": "Verify that all the destinations of type Backup are", + "full_action": "Verify that all the destinations of type Backup are\naccessible by at least one common media server." }, "1517": { "code": 1517, - "desc": "Inválido retention level", - "first_action": "Verifique que o retention level que you specify on each", - "full_action": "Verifique que o retention level que you specify on each\ndestination in armazenamento lifecycle policy está in o range de 0 to 100." + "desc": "Invalid retention level", + "first_action": "Verify that the retention level that you specify on each", + "full_action": "Verify that the retention level that you specify on each\ndestination in storage lifecycle policy is in the range of 0 to 100." }, "1518": { "code": 1518, - "desc": "Backup image está não supported por armazenamento lifecycle policy", - "first_action": "Verifique que if um NetBackup policy está configurado to executar snapshot backups e", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Verifique que if um NetBackup policy está configurado to executar snapshot backups e\nusesstoragelifecyclepolicyasitsstoragedestination,thenthespecifiedstorage\nlifecycle policy must be configurado com um snapshot destination. Otherwise,\nbackupimagesthatarecreatedbythoseNetBackuppoliciesarenotprocessed\nfurther por armazenamento lifecycle policy para qualquer lifecycle operations.\n■ Verifique que NetBackup policies que use o armazenamento lifecycle policy como um armazenamento\ndestination estão não configurado to executar “snapshots-only” operations. They\nmustcreatebackupsinadditiontosnapshots.TheStoragelifecyclepolicyeven\nthoughconfiguredwithasnapshotdestination,performslifecycleoperationson\nsuch images apenas if they have at least one backup copy." + "desc": "Backup image is not supported by storage lifecycle policy", + "first_action": "Verify that if a NetBackup policy is configured to perform snapshot backups and", + "full_action": "Do the following, as appropriate:\n■ Verify that if a NetBackup policy is configured to perform snapshot backups and\nusesstoragelifecyclepolicyasitsstoragedestination,thenthespecifiedstorage\nlifecycle policy must be configured with a snapshot destination. Otherwise,\nbackupimagesthatarecreatedbythoseNetBackuppoliciesarenotprocessed\nfurther by storage lifecycle policy for any lifecycle operations.\n■ Verify that NetBackup policies that use the storage lifecycle policy as a storage\ndestination are not configured to perform “snapshots-only” operations. They\nmustcreatebackupsinadditiontosnapshots.TheStoragelifecyclepolicyeven\nthoughconfiguredwithasnapshotdestination,performslifecycleoperationson\nsuch images only if they have at least one backup copy." }, "1519": { "code": 1519, - "desc": "Images estão in process", - "first_action": "Wait until o image processing está done, then retry o", - "full_action": "Wait until o image processing está done, then retry o\noperation. Ou, terminate o SLP processing para o needed images." + "desc": "Images are in process", + "first_action": "Wait until the image processing is done, then retry the", + "full_action": "Wait until the image processing is done, then retry the\noperation. Or, terminate the SLP processing for the needed images." }, "1521": { "code": 1521, - "desc": "Banco de dados não disponível", - "first_action": "Make sure que o banco de dados service está executando.", - "full_action": "Do one de o seguinte:\n■ Make sure que o banco de dados service está executando.\n■ Make sure que o disco está não cheio." + "desc": "Database not available", + "first_action": "Make sure that the database service is running.", + "full_action": "Do one of the following:\n■ Make sure that the database service is running.\n■ Make sure that the disk is not full." }, "1522": { "code": 1522, - "desc": "Erro executing banco de dados query", + "desc": "Error executing database query", "first_action": "Examinethelogfilesforthenbstservprocessororiginator", - "full_action": "Examinethelogfilesforthenbstservprocessororiginator\nID 369 para more informação." + "full_action": "Examinethelogfilesforthenbstservprocessororiginator\nID 369 for more information." }, "1523": { "code": 1523, - "desc": "Inválido fragment", - "first_action": "Verifique o NetBackup Problemas Relatório para details.", - "full_action": "Verifique o NetBackup Problemas Relatório para details." + "desc": "Invalid fragment", + "first_action": "Check the NetBackup Problems Report for details.", + "full_action": "Check the NetBackup Problems Report for details." }, "1524": { "code": 1524, "desc": "Duplicate image record", - "first_action": "Verifique o NetBackup Problemas Relatório para details.", - "full_action": "Do one de o seguinte:\n■ Verifique o NetBackup Problemas Relatório para details.\n■ Excluir o duplicate image from armazenamento because NetBackup não é possível do it." + "first_action": "Check the NetBackup Problems Report for details.", + "full_action": "Do one of the following:\n■ Check the NetBackup Problems Report for details.\n■ Delete the duplicate image from storage because NetBackup cannot do it." }, "1525": { "code": 1525, - "desc": "Inválido lsu", - "first_action": "Configure o LSU como um valid disco volume in um valid disco pool, e create um valid", - "full_action": "Do one de o seguinte:\n■ Configure o LSU como um valid disco volume in um valid disco pool, e create um valid\narmazenamento unidade para it. Associate this armazenamento unidade com um import armazenamento lifecycle\npolicy.\n■ Reconfigure o replication on seu armazenamento devices to use um replication target\ndisco volume (LSU) que NetBackup recognizes." + "desc": "Invalid lsu", + "first_action": "Configure the LSU as a valid disk volume in a valid disk pool, and create a valid", + "full_action": "Do one of the following:\n■ Configure the LSU as a valid disk volume in a valid disk pool, and create a valid\nstorage unit for it. Associate this storage unit with an import storage lifecycle\npolicy.\n■ Reconfigure the replication on your storage devices to use a replication target\ndisk volume (LSU) that NetBackup recognizes." }, "1526": { "code": 1526, - "desc": "Armazenamento lifecycle policy exceeds maximum import operations", + "desc": "Storage lifecycle policy exceeds maximum import operations", "first_action": "Configurethestoragelifecyclepolicywithonlyoneimport", "full_action": "Configurethestoragelifecyclepolicywithonlyoneimport\ndestination." }, @@ -3507,307 +3507,307 @@ "code": 1527, "desc": "Storagelifecyclepolicycanhaveonlyoneofbackup,import,andsnapshot operations", "first_action": "Configurethestoragelifecyclepolicywithonlyoneimport", - "full_action": "Configurethestoragelifecyclepolicywithonlyoneimport\ndestination e additional destinations de type duplication apenas." + "full_action": "Configurethestoragelifecyclepolicywithonlyoneimport\ndestination and additional destinations of type duplication only." }, "1528": { "code": 1528, - "desc": "O source copy para um Auto Image Replication está não capable de replication", + "desc": "The source copy for an Auto Image Replication is not capable of replication", "first_action": "Ifyouusethecommandline,ensurethatyouspecifythecorrectSLPdestination", - "full_action": "Do one de o seguinte:\n■ Ifyouusethecommandline,ensurethatyouspecifythecorrectSLPdestination\nindex number para o source copy.\n■ Use o appropriate indentation to indicate o correct source armazenamento lifecycle\npolicy destination in o GUI.\n■ Garanta que o source uses um armazenamento unidade que está capable de replication. O\nstorageunitisspecifiedbytheSLPdestinationindexontheCLIorbyindentation\nin o GUI. Que está, verifique o properties de o disco volumes within o disco pool\nque o armazenamento unidade specifies.\n■ After you set um replication target, you must refresh o disco pool. In o\nNetBackup Administration Console, in o left pane, expand Mídia e\nDispositivo Management Devices > Disco Pools. In o right pane, select o disco\npoolthatyouwanttoupdate.IntheChangeDiskPooldialogbox,clickRefresh\nto configure o replication settings para o disco pool." + "full_action": "Do one of the following:\n■ Ifyouusethecommandline,ensurethatyouspecifythecorrectSLPdestination\nindex number for the source copy.\n■ Use the appropriate indentation to indicate the correct source storage lifecycle\npolicy destination in the GUI.\n■ Ensure that the source uses a storage unit that is capable of replication. The\nstorageunitisspecifiedbytheSLPdestinationindexontheCLIorbyindentation\nin the GUI. That is, check the properties of the disk volumes within the disk pool\nthat the storage unit specifies.\n■ After you set a replication target, you must refresh the disk pool. In the\nNetBackup Administration Console, in the left pane, expand Media and\nDevice Management Devices > Disk Pools. In the right pane, select the disk\npoolthatyouwanttoupdate.IntheChangeDiskPooldialogbox,clickRefresh\nto configure the replication settings for the disk pool." }, "1529": { "code": 1529, "desc": "ThesourcecopyforAutoImageReplicationmustspecifyastorageunit", "first_action": "Ifyouusethecommandline,ensurethatyouspecifythecorrectstoragelifecycle", - "full_action": "Do one ou more de o seguinte:\n■ Ifyouusethecommandline,ensurethatyouspecifythecorrectstoragelifecycle\npolicy destination index number para o source copy.\n■ Garanta que you use o appropriate indentation to indicate o correct source\narmazenamento lifecycle policy destination in o GUI.\n■ Garanta que o source que está specified por either o armazenamento lifecycle policy\ndestination index on o CLI ou por indentation in o GUI uses um armazenamento unidade\n(notastorageunitgroup,storagelifecyclepolicyorAnyAvailable)thatiscapable\nde replication. Que está, verifique o properties de o disco volumes within o disco\npool que o armazenamento unidade specifies.\n■ Ensurethatyouarenotusingastorageunitgroupforreplication.Forthesource\ncopy, select um armazenamento unidade que está não in um armazenamento unidade group. Para o target, do\nnão select um armazenamento unidade group." + "full_action": "Do one or more of the following:\n■ Ifyouusethecommandline,ensurethatyouspecifythecorrectstoragelifecycle\npolicy destination index number for the source copy.\n■ Ensure that you use the appropriate indentation to indicate the correct source\nstorage lifecycle policy destination in the GUI.\n■ Ensure that the source that is specified by either the storage lifecycle policy\ndestination index on the CLI or by indentation in the GUI uses a storage unit\n(notastorageunitgroup,storagelifecyclepolicyorAnyAvailable)thatiscapable\nof replication. That is, check the properties of the disk volumes within the disk\npool that the storage unit specifies.\n■ Ensurethatyouarenotusingastorageunitgroupforreplication.Forthesource\ncopy, select a storage unit that is not in a storage unit group. For the target, do\nnot select a storage unit group." }, "1530": { "code": 1530, - "desc": "Apenas one Auto Image Replication allowed per copy", + "desc": "Only one Auto Image Replication allowed per copy", "first_action": "Ifyouusethecommandline,ensurethatyouspecifythecorrectstoragelifecycle", - "full_action": "Do one de o seguinte:\n■ Ifyouusethecommandline,ensurethatyouspecifythecorrectstoragelifecycle\npolicy destination index number para o source copy.\n■ Garanta que you use o appropriate indentation to indicate o correct source\narmazenamento lifecycle policy destination in o GUI.\n■ Garanta que o source que está specified por either o armazenamento lifecycle policy\ndestination index on o CLI ou por indentation in o GUI does não have more\nthan one Auto Image Replication destination specifying it como its source copy." + "full_action": "Do one of the following:\n■ Ifyouusethecommandline,ensurethatyouspecifythecorrectstoragelifecycle\npolicy destination index number for the source copy.\n■ Ensure that you use the appropriate indentation to indicate the correct source\nstorage lifecycle policy destination in the GUI.\n■ Ensure that the source that is specified by either the storage lifecycle policy\ndestination index on the CLI or by indentation in the GUI does not have more\nthan one Auto Image Replication destination specifying it as its source copy." }, "1531": { "code": 1531, "desc": "Animportstoragelifecyclepolicyrequiresonecopywithremoteretention type", - "first_action": "Change one de o destinations in o armazenamento lifecycle policy to use o remote", - "full_action": "Add um destination to o armazenamento lifecycle policy que uses\no remote retention type.\nDo one de o seguinte:\n■ Change one de o destinations in o armazenamento lifecycle policy to use o remote\nretention type. If o armazenamento lifecycle policy has apenas one destination que está um\nimport destination, then it must be um remote retention type.\n■ Addadestinationtothestoragelifecyclepolicywhichusestheremoteretention\ntype." + "first_action": "Change one of the destinations in the storage lifecycle policy to use the remote", + "full_action": "Add a destination to the storage lifecycle policy that uses\nthe remote retention type.\nDo one of the following:\n■ Change one of the destinations in the storage lifecycle policy to use the remote\nretention type. If the storage lifecycle policy has only one destination that is an\nimport destination, then it must be a remote retention type.\n■ Addadestinationtothestoragelifecyclepolicywhichusestheremoteretention\ntype." }, "1532": { "code": 1532, - "desc": "Import falhou because o imported image specifies um SLP name which does não exist", + "desc": "Import failed because the imported image specifies an SLP name which does not exist", "first_action": "Verifythatthestoragelifecyclepolicyinthesourcedomainwhereyouconfigured", - "full_action": "Do one de o seguinte:\n■ Verifythatthestoragelifecyclepolicyinthesourcedomainwhereyouconfigured\nanAutoImageReplicationmatchesthestoragelifecyclepolicyinthedestination\ndomain onde you configurado o import. O match está case-sensitive.\n■ Add um armazenamento lifecycle policy com um import destination usando o same name\ncomo seu armazenamento lifecycle policy in o source domain." + "full_action": "Do one of the following:\n■ Verifythatthestoragelifecyclepolicyinthesourcedomainwhereyouconfigured\nanAutoImageReplicationmatchesthestoragelifecyclepolicyinthedestination\ndomain where you configured the import. The match is case-sensitive.\n■ Add a storage lifecycle policy with an import destination using the same name\nas your storage lifecycle policy in the source domain." }, "1533": { "code": 1533, - "desc": "Import falhou because o imported image data class está different than o SLP data class", + "desc": "Import failed because the imported image data class is different than the SLP data class", "first_action": "Changethedataclassificationofthestoragelifecyclepolicyinthesourcedomain", - "full_action": "Do one de o seguinte:\n■ Changethedataclassificationofthestoragelifecyclepolicyinthesourcedomain\nonde you configurado um Auto Image Replication to match o seguinte: o\ndata classification in o destination domain onde you have configurado o\nimport. O match está case-sensitive.\nVerifythatthestoragelifecyclepolicyinthesourcedomainwhereyouconfigured\num Auto Image Replication matches o seguinte: o armazenamento lifecycle policy in\no destination domain onde you configurado o import. O match está\ncase-sensitive.\n■ Change o data classification de o armazenamento lifecycle policy in o destination\ndomainwhereyouconfiguredanAutoImageReplicationtomatchthefollowing:\no data classification in o source domain onde you have configurado o\nimport. O match está case-sensitive." + "full_action": "Do one of the following:\n■ Changethedataclassificationofthestoragelifecyclepolicyinthesourcedomain\nwhere you configured an Auto Image Replication to match the following: the\ndata classification in the destination domain where you have configured the\nimport. The match is case-sensitive.\nVerifythatthestoragelifecyclepolicyinthesourcedomainwhereyouconfigured\nan Auto Image Replication matches the following: the storage lifecycle policy in\nthe destination domain where you configured the import. The match is\ncase-sensitive.\n■ Change the data classification of the storage lifecycle policy in the destination\ndomainwhereyouconfiguredanAutoImageReplicationtomatchthefollowing:\nthe data classification in the source domain where you have configured the\nimport. The match is case-sensitive." }, "1534": { "code": 1534, - "desc": "Import falhou because o imported image specifies um SLP name com não import operation", + "desc": "Import failed because the imported image specifies an SLP name with no import operation", "first_action": "Useadifferentstoragelifecyclepolicynameinthesource", - "full_action": "Useadifferentstoragelifecyclepolicynameinthesource\ndomain onde you configurado um Auto Image Replication. This name must match\num armazenamento lifecycle policy name com um import destination in o destination domain\nonde you have configurado o import. O match está case-sensitive." + "full_action": "Useadifferentstoragelifecyclepolicynameinthesource\ndomain where you configured an Auto Image Replication. This name must match\na storage lifecycle policy name with an import destination in the destination domain\nwhere you have configured the import. The match is case-sensitive." }, "1535": { "code": 1535, - "desc": "Import falhou because o imported image backup ID conflicts com um existing image", - "first_action": "Excluir o duplicate image from armazenamento because", - "full_action": "Excluir o duplicate image from armazenamento because\nNetBackup não é possível excluir it. Use o seguinte comando:\n# bpimage -deletecopy # -backupid backupid\nonde # está o copy number de o image que you desejar to excluir." + "desc": "Import failed because the imported image backup ID conflicts with an existing image", + "first_action": "Delete the duplicate image from storage because", + "full_action": "Delete the duplicate image from storage because\nNetBackup cannot delete it. Use the following command:\n# bpimage -deletecopy # -backupid backupid\nwhere # is the copy number of the image that you want to delete." }, "1536": { "code": 1536, - "desc": "O armazenamento unidade ou armazenamento unidade group não é possível be deleted because um SLP references it", - "first_action": "Run o seguinte comando to display todos versions de each SLP:", - "full_action": "Use o nbstl comando to view e change o older\nSLP versions. Do o seguinte in o order listed:\n■ Run o seguinte comando to display todos versions de each SLP:\n# nbstl -L -all_versions\n■ Determinar o name e version de each SLP que references o armazenamento unidade\nou armazenamento unidade group.\n■ Run o seguinte comando to replace o armazenamento unidade (group) to be deleted\ncom o name de um different armazenamento unidade.\n# nbstl -modify_version ...\nPara more informação on armazenamento lifecycle policy versions, veja o NetBackup\nAdministrator’s Guide, Volume I." + "desc": "The storage unit or storage unit group cannot be deleted because an SLP references it", + "first_action": "Run the following command to display all versions of each SLP:", + "full_action": "Use the nbstl command to view and change the older\nSLP versions. Do the following in the order listed:\n■ Run the following command to display all versions of each SLP:\n# nbstl -L -all_versions\n■ Determine the name and version of each SLP that references the storage unit\nor storage unit group.\n■ Run the following command to replace the storage unit (group) to be deleted\nwith the name of a different storage unit.\n# nbstl -modify_version ...\nFor more information on storage lifecycle policy versions, see the NetBackup\nAdministrator’s Guide, Volume I." }, "1537": { "code": 1537, "desc": "Backuppolicyandstoragelifecyclepolicyhaveconflictingconfigurations", - "first_action": "In o NetBackup Administration Console, locate o", - "full_action": "In o NetBackup Administration Console, locate o\nChange Armazenamento Lifecycle Policy dialog para o SLP in question. Then run o\nValidation Relatório to display o specific conflicts que pertain to o SLP. Correct\nthose conflicts." + "first_action": "In the NetBackup Administration Console, locate the", + "full_action": "In the NetBackup Administration Console, locate the\nChange Storage Lifecycle Policy dialog for the SLP in question. Then run the\nValidation Report to display the specific conflicts that pertain to the SLP. Correct\nthose conflicts." }, "1538": { "code": 1538, - "desc": "Data classification in o SLP conflicts com backup policy", - "first_action": "Change o policy to reference um SLP com um matching data classification", - "full_action": "Do one de o seguinte:\n■ Change o policy to reference um SLP com um matching data classification\n■ Change o data classification in either o backup policy ou o SLP so que\nthey match." + "desc": "Data classification in the SLP conflicts with backup policy", + "first_action": "Change the policy to reference an SLP with a matching data classification", + "full_action": "Do one of the following:\n■ Change the policy to reference an SLP with a matching data classification\n■ Change the data classification in either the backup policy or the SLP so that\nthey match." }, "1539": { "code": 1539, "desc": "Backuppolicygeneratessnapshotsbutstoragelifecyclepolicydoesnot handle them", - "first_action": "Change o backup policy to use um SLP que provides snapshot support.", - "full_action": "Do one de o seguinte:\n■ Change o backup policy to use um SLP que provides snapshot support.\n■ Change o backup policy so it does não generate snapshots.\n■ Change o SLP to include um snapshot operation." + "first_action": "Change the backup policy to use an SLP that provides snapshot support.", + "full_action": "Do one of the following:\n■ Change the backup policy to use an SLP that provides snapshot support.\n■ Change the backup policy so it does not generate snapshots.\n■ Change the SLP to include a snapshot operation." }, "1540": { "code": 1540, - "desc": "SLP expects snapshots but backup policy does não create them com SLP management enabled", - "first_action": "Find e expire o existing snapshot which está não longer", - "full_action": "Find e expire o existing snapshot which está não longer\nneeded." + "desc": "SLP expects snapshots but backup policy does not create them with SLP management enabled", + "first_action": "Find and expire the existing snapshot which is no longer", + "full_action": "Find and expire the existing snapshot which is no longer\nneeded." }, "1541": { "code": 1541, - "desc": "Snapshotcreationfailed.Themaximumsnapshotlimitforthepolicyhas been excedido e não existing snapshots estão eligible para expiration.", - "first_action": "Do não try to expire um snapshot copy que está still pending", - "full_action": "Do não try to expire um snapshot copy que está still pending\nou has não reached its retention period. Verifique o maximum snapshot limite setting\nin seu Backup Policy>Attributes>Snapshot Options." + "desc": "Snapshotcreationfailed.Themaximumsnapshotlimitforthepolicyhas been exceeded and no existing snapshots are eligible for expiration.", + "first_action": "Do not try to expire a snapshot copy that is still pending", + "full_action": "Do not try to expire a snapshot copy that is still pending\nor has not reached its retention period. Check the maximum snapshot limit setting\nin your Backup Policy>Attributes>Snapshot Options." }, "1542": { "code": 1542, - "desc": "Um existing snapshot está não longer valid ou não é possível be mounted para subsequent operations", - "first_action": "Run um new backup job to generate um new snapshot.", - "full_action": "Run um new backup job to generate um new snapshot." + "desc": "An existing snapshot is no longer valid or cannot be mounted for subsequent operations", + "first_action": "Run a new backup job to generate a new snapshot.", + "full_action": "Run a new backup job to generate a new snapshot." }, "1543": { "code": 1543, - "desc": "Policy type está não compatible com SLP operations", - "first_action": "Choose um different SLP que está compatible com o policy", - "full_action": "Choose um different SLP que está compatible com o policy\ntype." + "desc": "Policy type is not compatible with SLP operations", + "first_action": "Choose a different SLP that is compatible with the policy", + "full_action": "Choose a different SLP that is compatible with the policy\ntype." }, "1545": { "code": 1545, - "desc": "Schedule type está não compatible com SLP operations", + "desc": "Schedule type is not compatible with SLP operations", "first_action": "ChooseadifferentSLPthatiscompatiblewiththeschedule", "full_action": "ChooseadifferentSLPthatiscompatiblewiththeschedule\ntype." }, "1546": { "code": 1546, - "desc": "Capacity managed retention type está não compatible com SLP operations", + "desc": "Capacity managed retention type is not compatible with SLP operations", "first_action": "ChooseadifferentSLPthatiscompatiblewiththeschedule", "full_action": "ChooseadifferentSLPthatiscompatiblewiththeschedule\ntype." }, "1547": { "code": 1547, - "desc": "Expire after copy retention requires um dependent copy", - "first_action": "Não operations can be performed on this snapshot. Expire", - "full_action": "Não operations can be performed on this snapshot. Expire\nit from o catalog." + "desc": "Expire after copy retention requires a dependent copy", + "first_action": "No operations can be performed on this snapshot. Expire", + "full_action": "No operations can be performed on this snapshot. Expire\nit from the catalog." }, "1548": { "code": 1548, - "desc": "Retention type está não compatible com snapshot operation", - "first_action": "Choose um different retention type.", - "full_action": "Do one de o seguinte:\n■ Choose um different retention type.\n■ If o backup policy está configurado para Replication Director, abrir o backup\npolicy. In o Attributes tab, click Options to display o Replication Director\noptions. If o values para o Maximum Snapshots do não include Managed\npor SLP Retention, select 0 (zero) instead. Um value de 0 indicates o Managed\npor SLP Retention selection.\n■ Para cloud snapshot replication apenas, fixed retention type está supported." + "desc": "Retention type is not compatible with snapshot operation", + "first_action": "Choose a different retention type.", + "full_action": "Do one of the following:\n■ Choose a different retention type.\n■ If the backup policy is configured for Replication Director, open the backup\npolicy. In the Attributes tab, click Options to display the Replication Director\noptions. If the values for the Maximum Snapshots do not include Managed\nby SLP Retention, select 0 (zero) instead. A value of 0 indicates the Managed\nby SLP Retention selection.\n■ For cloud snapshot replication only, fixed retention type is supported." }, "1549": { "code": 1549, - "desc": "TIR informação selection está não compatible com SLP operations", - "first_action": "Remove o TIR informação selection from o backup policy.", - "full_action": "Do one de o seguinte:\n■ Remove o TIR informação selection from o backup policy.\n■ Choose um different SLP to use com o backup policy." + "desc": "TIR information selection is not compatible with SLP operations", + "first_action": "Remove the TIR information selection from the backup policy.", + "full_action": "Do one of the following:\n■ Remove the TIR information selection from the backup policy.\n■ Choose a different SLP to use with the backup policy." }, "1552": { "code": 1552, - "desc": "O source e target armazenamento units estão não valid replication partners.", - "first_action": "Run o seguinte comando to get um list de matching target armazenamento units ou", - "full_action": "Do one de o seguinte:\n■ Run o seguinte comando to get um list de matching target armazenamento units ou\ngroups para o given source armazenamento unidade ou group:\n# nbdevquery -listreptargets -stunit source_stu_or_group\n■ Rerun o nbstl comando com o target armazenamento unidade ou group from o list\nque o nbdevquery comando displays.\n■ Run o bpstsinfo -li comando e verifique o output para o armazenamento servidor\nname. O name que you use to create o armazenamento servidor must match this\nname.\n■ Garanta que NetBackup está configurado after o armazenamento servidor configuration está\ncomplete. If não, use o Change Disco Pool dialog de o NetBackup\nAdministration Console ou o nbdevconfig -updatedp comando to refresh\neach disco pool de o armazenamento servidor." + "desc": "The source and target storage units are not valid replication partners.", + "first_action": "Run the following command to get a list of matching target storage units or", + "full_action": "Do one of the following:\n■ Run the following command to get a list of matching target storage units or\ngroups for the given source storage unit or group:\n# nbdevquery -listreptargets -stunit source_stu_or_group\n■ Rerun the nbstl command with the target storage unit or group from the list\nthat the nbdevquery command displays.\n■ Run the bpstsinfo -li command and check the output for the storage server\nname. The name that you use to create the storage server must match this\nname.\n■ Ensure that NetBackup is configured after the storage server configuration is\ncomplete. If not, use the Change Disk Pool dialog of the NetBackup\nAdministration Console or the nbdevconfig -updatedp command to refresh\neach disk pool of the storage server." }, "1553": { "code": 1553, - "desc": "Checkpoints estão não allowed com SLP operations", - "first_action": "Remove o checkpoint restart selection from o backup policy.", - "full_action": "Do one de o seguinte:\n■ Remove o checkpoint restart selection from o backup policy.\n■ Choose um different SLP to use com o backup policy." + "desc": "Checkpoints are not allowed with SLP operations", + "first_action": "Remove the checkpoint restart selection from the backup policy.", + "full_action": "Do one of the following:\n■ Remove the checkpoint restart selection from the backup policy.\n■ Choose a different SLP to use with the backup policy." }, "1554": { "code": 1554, - "desc": "Armazenamento unidade snapshot capability está não compatible com operation characteristics", + "desc": "Storage unit snapshot capability is not compatible with operation characteristics", "first_action": "Chooseastorageunitthatsupportsthecorrectcapabilities.", "full_action": "Chooseastorageunitthatsupportsthecorrectcapabilities." }, "1556": { "code": 1556, - "desc": "O SLP deletion falhou because um backup policy refers to it.", - "first_action": "Change o backup policies to use other SLPs ou armazenamento", - "full_action": "Change o backup policies to use other SLPs ou armazenamento\nunits. Then try again to excluir o SLP." + "desc": "The SLP deletion failed because a backup policy refers to it.", + "first_action": "Change the backup policies to use other SLPs or storage", + "full_action": "Change the backup policies to use other SLPs or storage\nunits. Then try again to delete the SLP." }, "1557": { "code": 1557, - "desc": "Must specify mirror retention when target armazenamento unidade está mirror capable.", - "first_action": "If you used um nbstl comando to configure o armazenamento", - "full_action": "If you used um nbstl comando to configure o armazenamento\nlifecycle policy, rerun o comando after o seguinte: Specify o mirror retention\ntype para o replication operation corresponding to o armazenamento unidade que está\nmirror-capable.Usethebpstulist -Ucommandtoviewthestorageunitproperties.\nIf o erro occurs when you configure o armazenamento lifecycle policy por usando o GUI,\nsubmit um problema relatório e provide o appropriate logs." + "desc": "Must specify mirror retention when target storage unit is mirror capable.", + "first_action": "If you used a nbstl command to configure the storage", + "full_action": "If you used a nbstl command to configure the storage\nlifecycle policy, rerun the command after the following: Specify the mirror retention\ntype for the replication operation corresponding to the storage unit that is\nmirror-capable.Usethebpstulist -Ucommandtoviewthestorageunitproperties.\nIf the error occurs when you configure the storage lifecycle policy by using the GUI,\nsubmit a problem report and provide the appropriate logs." }, "1558": { "code": 1558, - "desc": "Mirror retention está não allowed when target armazenamento unidade está não mirror capable.", - "first_action": "U comando to view o armazenamento unidade properties. If o erro occurs when you", - "full_action": "If you used um nbstl comando to configure o armazenamento\nlifecycle policy, rerun o comando after you do o seguinte: Specify o\nappropriate retention type (other than mirror retention) para o replication operation\ncorresponding to o armazenamento unidade que está non-mirror capable. Use o bpstulist\n-U comando to view o armazenamento unidade properties. If o erro occurs when you\nconfigurethestoragelifecyclepolicybyusingtheGUI,submitaproblemreportand\nprovide o appropriate logs." + "desc": "Mirror retention is not allowed when target storage unit is not mirror capable.", + "first_action": "U command to view the storage unit properties. If the error occurs when you", + "full_action": "If you used a nbstl command to configure the storage\nlifecycle policy, rerun the command after you do the following: Specify the\nappropriate retention type (other than mirror retention) for the replication operation\ncorresponding to the storage unit that is non-mirror capable. Use the bpstulist\n-U command to view the storage unit properties. If the error occurs when you\nconfigurethestoragelifecyclepolicybyusingtheGUI,submitaproblemreportand\nprovide the appropriate logs." }, "1559": { "code": 1559, - "desc": "SLP referenced in policy ou schedule não found", - "first_action": "Verifique o spelling de o SLP used in o policy. O SLP", - "full_action": "Verifique o spelling de o SLP used in o policy. O SLP\ndisplayed in o NetBackup Administration Console ou o nbstl comando can\nbe used to list o SLPs que have been defined. Select one de o defined SLPs to\nuse in o backup policy ou create one com o desired name." + "desc": "SLP referenced in policy or schedule not found", + "first_action": "Check the spelling of the SLP used in the policy. The SLP", + "full_action": "Check the spelling of the SLP used in the policy. The SLP\ndisplayed in the NetBackup Administration Console or the nbstl command can\nbe used to list the SLPs that have been defined. Select one of the defined SLPs to\nuse in the backup policy or create one with the desired name." }, "1560": { "code": 1560, - "desc": "Fixed ou rotation retention requerido without um replication operation", - "first_action": "Add um operation com o requerido retention ou change", - "full_action": "Add um operation com o requerido retention ou change\no retention de um existing operation." + "desc": "Fixed or rotation retention required without a replication operation", + "first_action": "Add an operation with the required retention or change", + "full_action": "Add an operation with the required retention or change\nthe retention of an existing operation." }, "1561": { "code": 1561, - "desc": "Policy usando NDMP conflicts com multiple Backup From Snapshot operations in armazenamento lifecycle policy", - "first_action": "Change o policy type ou data mover type so que it está não NDMP.", - "full_action": "Do one de o seguinte:\n■ Change o policy type ou data mover type so que it está não NDMP.\n■ Use um different SLP que does não contain multiple Backup From Snapshot\noperations." + "desc": "Policy using NDMP conflicts with multiple Backup From Snapshot operations in storage lifecycle policy", + "first_action": "Change the policy type or data mover type so that it is not NDMP.", + "full_action": "Do one of the following:\n■ Change the policy type or data mover type so that it is not NDMP.\n■ Use a different SLP that does not contain multiple Backup From Snapshot\noperations." }, "1562": { "code": 1562, - "desc": "Backup schedule generates snapshots but armazenamento lifecycle policy does não handle them", - "first_action": "Select um SLP que begins com um Snapshot operation so", - "full_action": "Select um SLP que begins com um Snapshot operation so\nque it can process o snapshot generated por o backup policy e schedule." + "desc": "Backup schedule generates snapshots but storage lifecycle policy does not handle them", + "first_action": "Select an SLP that begins with a Snapshot operation so", + "full_action": "Select an SLP that begins with a Snapshot operation so\nthat it can process the snapshot generated by the backup policy and schedule." }, "1563": { "code": 1563, - "desc": "SLP expects snapshots but backup schedule does não create them", - "first_action": "Select um SLP que does não begin com um Snapshot", - "full_action": "Select um SLP que does não begin com um Snapshot\noperation." + "desc": "SLP expects snapshots but backup schedule does not create them", + "first_action": "Select an SLP that does not begin with a Snapshot", + "full_action": "Select an SLP that does not begin with a Snapshot\noperation." }, "1564": { "code": 1564, - "desc": "Armazenamento lifecycle policy contains errors", - "first_action": "Verifique o other errors que estão displayed.", - "full_action": "Verifique o other errors que estão displayed." + "desc": "Storage lifecycle policy contains errors", + "first_action": "Check the other errors that are displayed.", + "full_action": "Check the other errors that are displayed." }, "1565": { "code": 1565, "desc": "PolicysnapshotmethodisnotcompatiblewithSLPsnapshotoperations NetBackup status codes 380 NetBackup status codes", - "first_action": "Use um different SLP que does não contain unsupported", - "full_action": "Use um different SLP que does não contain unsupported\noperations." + "first_action": "Use a different SLP that does not contain unsupported", + "full_action": "Use a different SLP that does not contain unsupported\noperations." }, "1566": { "code": 1566, - "desc": "Armazenamento unidade requerido para snapshot operation when não other operation present", - "first_action": "Add um armazenamento unidade to o Snapshot operation.", - "full_action": "Add um armazenamento unidade to o Snapshot operation." + "desc": "Storage unit required for snapshot operation when no other operation present", + "first_action": "Add a storage unit to the Snapshot operation.", + "full_action": "Add a storage unit to the Snapshot operation." }, "1567": { "code": 1567, - "desc": "Apenas one NDMP backup de um snapshot per backup ID está allowed", - "first_action": "Modify o SLP so que it contains apenas one Backup From Snapshot operation.", - "full_action": "Do one de o seguinte:\n■ Modify o SLP so que it contains apenas one Backup From Snapshot operation.\n■ Modify o backup policy so que it uses um different SLP." + "desc": "Only one NDMP backup of a snapshot per backup ID is allowed", + "first_action": "Modify the SLP so that it contains only one Backup From Snapshot operation.", + "full_action": "Do one of the following:\n■ Modify the SLP so that it contains only one Backup From Snapshot operation.\n■ Modify the backup policy so that it uses a different SLP." }, "1568": { "code": 1568, "desc": "OnlyoneIndexFromSnapshotoperationisallowedperstoragelifecycle policy", - "first_action": "Change o backup policies to use other SLPs ou armazenamento", - "full_action": "Change o backup policies to use other SLPs ou armazenamento\nunits. Then try again to excluir o SLP." + "first_action": "Change the backup policies to use other SLPs or storage", + "full_action": "Change the backup policies to use other SLPs or storage\nunits. Then try again to delete the SLP." }, "1569": { "code": 1569, - "desc": "Snapshot armazenamento unidade está não configurado para primary snapshots. It não é possível be used in snapshot operation.", - "first_action": "Select um different armazenamento unidade que está snapshot-capable to use in o Snapshot", - "full_action": "Do one de o seguinte:\n■ Select um different armazenamento unidade que está snapshot-capable to use in o Snapshot\noperation.\n■ Change o configuration de o desired armazenamento unidade so que it supports primary\nsnapshot operations." + "desc": "Snapshot storage unit is not configured for primary snapshots. It cannot be used in snapshot operation.", + "first_action": "Select a different storage unit that is snapshot-capable to use in the Snapshot", + "full_action": "Do one of the following:\n■ Select a different storage unit that is snapshot-capable to use in the Snapshot\noperation.\n■ Change the configuration of the desired storage unit so that it supports primary\nsnapshot operations." }, "1570": { "code": 1570, - "desc": "Policy type does não support Index from Snapshot", - "first_action": "Select um different SLP que does não contain um Index", - "full_action": "Select um different SLP que does não contain um Index\nfrom Snapshot operation" + "desc": "Policy type does not support Index from Snapshot", + "first_action": "Select a different SLP that does not contain an Index", + "full_action": "Select a different SLP that does not contain an Index\nfrom Snapshot operation" }, "1571": { "code": 1571, - "desc": "Data mover type specified in policy does não support Index from Snapshot", - "first_action": "Select um different SLP que does não contain um Index", - "full_action": "Select um different SLP que does não contain um Index\nfrom Snapshot operation." + "desc": "Data mover type specified in policy does not support Index from Snapshot", + "first_action": "Select a different SLP that does not contain an Index", + "full_action": "Select a different SLP that does not contain an Index\nfrom Snapshot operation." }, "1572": { "code": 1572, - "desc": "Armazenamento unidade must be specified para this operation", - "first_action": "Add um armazenamento unidade to o SLP operation.", - "full_action": "Add um armazenamento unidade to o SLP operation." + "desc": "Storage unit must be specified for this operation", + "first_action": "Add a storage unit to the SLP operation.", + "full_action": "Add a storage unit to the SLP operation." }, "1573": { "code": 1573, - "desc": "Backup image não é possível be expired because its SLP processing está não yet complete", - "first_action": "Wait until SLP processing para que image está complete, then retry o expiration", - "full_action": "Do one de o seguinte:\n■ Wait until SLP processing para que image está complete, then retry o expiration\noperation.\n■ Use o nbstlutil -cancel comando to cancel further processing on o\nrelevant image. Then retry o expiration operation.\n■ Add o -force_not_complete option to o bpexpdate comando to force\nexpiration even if o image-copy está não SLP complete." + "desc": "Backup image cannot be expired because its SLP processing is not yet complete", + "first_action": "Wait until SLP processing for that image is complete, then retry the expiration", + "full_action": "Do one of the following:\n■ Wait until SLP processing for that image is complete, then retry the expiration\noperation.\n■ Use the nbstlutil -cancel command to cancel further processing on the\nrelevant image. Then retry the expiration operation.\n■ Add the -force_not_complete option to the bpexpdate command to force\nexpiration even if the image-copy is not SLP complete." }, "1574": { "code": 1574, - "desc": "Data Classification name não é possível be 'Any' while creating new data classification", - "first_action": "Use um different name e try again.", - "full_action": "Use um different name e try again." + "desc": "Data Classification name cannot be 'Any' while creating new data classification", + "first_action": "Use a different name and try again.", + "full_action": "Use a different name and try again." }, "1575": { "code": 1575, - "desc": "Data Classification auto creation falhou", - "first_action": "Manually create o data classification on o master", - "full_action": "Manually create o data classification on o master\nservidor com o same name como que de o image being imported." + "desc": "Data Classification auto creation failed", + "first_action": "Manually create the data classification on the master", + "full_action": "Manually create the data classification on the master\nserver with the same name as that of the image being imported." }, "1576": { "code": 1576, - "desc": "Topology validation falhou", - "first_action": "Verifique que o mídia servers que estão associated com o armazenamento servers estão", - "full_action": "Do o seguinte:\n■ Verifique que o mídia servers que estão associated com o armazenamento servers estão\nexecutando.\n■ Verifique o connectivity between o mídia servidor (ou cliente) e o armazenamento\nservidor (NetApp OnCommand servidor).\n■ Verifique o detailed messages supplied com this erro to determinar o\nvendor-specific errors." + "desc": "Topology validation failed", + "first_action": "Check that the media servers that are associated with the storage servers are", + "full_action": "Do the following:\n■ Check that the media servers that are associated with the storage servers are\nrunning.\n■ Check the connectivity between the media server (or client) and the storage\nserver (NetApp OnCommand server).\n■ Check the detailed messages supplied with this error to determine the\nvendor-specific errors." }, "1577": { "code": 1577, "desc": "StorageunitintheSLPdoesnotmatchtheacceleratorattributeinpolicy", "first_action": "SelectadifferentstorageunitfortheSLPthatdoessupport", - "full_action": "SelectadifferentstorageunitfortheSLPthatdoessupport\no accelerator backup operation." + "full_action": "SelectadifferentstorageunitfortheSLPthatdoessupport\nthe accelerator backup operation." }, "1578": { "code": 1578, - "desc": "Inválido window fechar options", - "first_action": "If you used o nbstl -wcopt comando, make sure que", - "full_action": "If you used o nbstl -wcopt comando, make sure que\no specified argument está either SFN ou SHN.\nFormoreinformationonthenbstlcommand,pleaseseetheNetBackupCommands\nReference Guide." + "desc": "Invalid window close options", + "first_action": "If you used the nbstl -wcopt command, make sure that", + "full_action": "If you used the nbstl -wcopt command, make sure that\nthe specified argument is either SFN or SHN.\nFormoreinformationonthenbstlcommand,pleaseseetheNetBackupCommands\nReference Guide." }, "1579": { "code": 1579, - "desc": "One ou more images foram não processed because o window closed", - "first_action": "This behavior está expected e não ação está necessary.", - "full_action": "This behavior está expected e não ação está necessary.\nProcessing resumes when o next window opens." + "desc": "One or more images were not processed because the window closed", + "first_action": "This behavior is expected and no action is necessary.", + "full_action": "This behavior is expected and no action is necessary.\nProcessing resumes when the next window opens." }, "1580": { "code": 1580, - "desc": "VMware policy com PFI enabled requires um SLP", - "first_action": "Use o VMware policy without Replication Director, ou", - "full_action": "Use o VMware policy without Replication Director, ou\nprovide um SLP que has at least um Snapshot operation." + "desc": "VMware policy with PFI enabled requires an SLP", + "first_action": "Use the VMware policy without Replication Director, or", + "full_action": "Use the VMware policy without Replication Director, or\nprovide an SLP that has at least a Snapshot operation." }, "1581": { "code": 1581, - "desc": "Non-application consistent VMware policy está não compatible com snapdupe operations", - "first_action": "Enable Application Consistency, ou remove o Backup", - "full_action": "Enable Application Consistency, ou remove o Backup\nfrom Snapshot operation from o SLP definition." + "desc": "Non-application consistent VMware policy is not compatible with snapdupe operations", + "first_action": "Enable Application Consistency, or remove the Backup", + "full_action": "Enable Application Consistency, or remove the Backup\nfrom Snapshot operation from the SLP definition." }, "1582": { "code": 1582, @@ -3817,7797 +3817,7797 @@ }, "1583": { "code": 1583, - "desc": "VMware policy com PFI enabled requires VIP auto discovery", - "first_action": "Enable automatic discovery de virtual machines.", - "full_action": "Enable automatic discovery de virtual machines." + "desc": "VMware policy with PFI enabled requires VIP auto discovery", + "first_action": "Enable automatic discovery of virtual machines.", + "full_action": "Enable automatic discovery of virtual machines." }, "1584": { "code": 1584, - "desc": "VMwarepolicywith'PersistentFrozenImage'enabledrequiresschedule type de Cheio Backup", + "desc": "VMwarepolicywith'PersistentFrozenImage'enabledrequiresschedule type of Full Backup", "first_action": "Useafullscheduleandremoveallincrementalschedules.", "full_action": "Useafullscheduleandremoveallincrementalschedules." }, "1585": { "code": 1585, - "desc": "Backup image não é possível be expired because não todos dependent copies estão expired", + "desc": "Backup image cannot be expired because not all dependent copies are expired", "first_action": "Waitforthedependentimagestobeeligibleforexpiration", - "full_action": "Waitforthedependentimagestobeeligibleforexpiration\nwhen their SLP state transitions into IMAGE_COMPLETE state. Also, you can\ncancel o SLP operations on o dependent images." + "full_action": "Waitforthedependentimagestobeeligibleforexpiration\nwhen their SLP state transitions into IMAGE_COMPLETE state. Also, you can\ncancel the SLP operations on the dependent images." }, "1586": { "code": 1586, - "desc": "SLP operation foi canceled", - "first_action": "Não ação está requerido.", - "full_action": "Não ação está requerido." + "desc": "SLP operation was canceled", + "first_action": "No action is required.", + "full_action": "No action is required." }, "1587": { "code": 1587, - "desc": "Armazenamento lifecycle policy não é possível have both target e untarget replication to remote master", - "first_action": "Do não mix o targeted e untargeted replication", - "full_action": "Do não mix o targeted e untargeted replication\noperation to um remote master." + "desc": "Storage lifecycle policy cannot have both target and untarget replication to remote master", + "first_action": "Do not mix the targeted and untargeted replication", + "full_action": "Do not mix the targeted and untargeted replication\noperation to a remote master." }, "1588": { "code": 1588, - "desc": "Target master servidor está already used in one de o replications to remote master NetBackup status codes 387 NetBackup status codes", - "first_action": "Define todos targeted replication operations com distinct", - "full_action": "Define todos targeted replication operations com distinct\ntarget master servidor." + "desc": "Target master server is already used in one of the replications to remote master NetBackup status codes 387 NetBackup status codes", + "first_action": "Define all targeted replication operations with distinct", + "full_action": "Define all targeted replication operations with distinct\ntarget master server." }, "1589": { "code": 1589, - "desc": "Não é possível conectar to specified target master servidor", - "first_action": "Verifique que todos services on source domain e target", - "full_action": "Verifique que todos services on source domain e target\ndomain estão executando." + "desc": "Cannot connect to specified target master server", + "first_action": "Check that all services on source domain and target", + "full_action": "Check that all services on source domain and target\ndomain are running." }, "1590": { "code": 1590, - "desc": "Não é possível find specified target import SLP", - "first_action": "Enter um valid name de o target domain SLP com o", - "full_action": "Enter um valid name de o target domain SLP com o\nimport operation, in o targeted replication operation de o source domain’s SLP." + "desc": "Cannot find specified target import SLP", + "first_action": "Enter a valid name of the target domain SLP with the", + "full_action": "Enter a valid name of the target domain SLP with the\nimport operation, in the targeted replication operation of the source domain’s SLP." }, "1591": { "code": 1591, - "desc": "Não import SLP(s) found com compatible replication target dispositivo.", - "first_action": "Correct one ou more de o possible problemas.", - "full_action": "Correct one ou more de o possible problemas." + "desc": "No import SLP(s) found with compatible replication target device.", + "first_action": "Correct one or more of the possible problems.", + "full_action": "Correct one or more of the possible problems." }, "1592": { "code": 1592, - "desc": "Trusted master servers estão being referred por one ou more Armazenamento Lifecycle Policies (SLPs) on o source ou target domain. NetBackup status codes 388 NetBackup status codes", - "first_action": "Excluir ou change o SLPs so they do não refer to domain", - "full_action": "Excluir ou change o SLPs so they do não refer to domain\nB, then try to excluir domain B from domain Um again." + "desc": "Trusted master servers are being referred by one or more Storage Lifecycle Policies (SLPs) on the source or target domain. NetBackup status codes 388 NetBackup status codes", + "first_action": "Delete or change the SLPs so they do not refer to domain", + "full_action": "Delete or change the SLPs so they do not refer to domain\nB, then try to delete domain B from domain A again." }, "1593": { "code": 1593, - "desc": "Replication Director para VMware policy requires mapped backups", + "desc": "Replication Director for VMware policy requires mapped backups", "first_action": "Enable mapping.", "full_action": "Enable mapping." }, "1594": { "code": 1594, - "desc": "Falhou to determinar disco mídia ID", - "first_action": "Recheck o armazenamento servidor, disco pool, e armazenamento unidade", - "full_action": "Recheck o armazenamento servidor, disco pool, e armazenamento unidade\nconfigurations." + "desc": "Failed to determine disk media ID", + "first_action": "Recheck the storage server, disk pool, and storage unit", + "full_action": "Recheck the storage server, disk pool, and storage unit\nconfigurations." }, "1596": { "code": 1596, - "desc": "Select um armazenamento lifecycle policy que has não snapshot operation como um policy’s Armazenamento Destination NetBackup status codes 389 NetBackup status codes", - "first_action": "Select um armazenamento lifecycle policy que has não snapshot", - "full_action": "Select um armazenamento lifecycle policy que has não snapshot\noperation como o policy armazenamento destination." + "desc": "Select a storage lifecycle policy that has no snapshot operation as a policy’s Storage Destination NetBackup status codes 389 NetBackup status codes", + "first_action": "Select a storage lifecycle policy that has no snapshot", + "full_action": "Select a storage lifecycle policy that has no snapshot\noperation as the policy storage destination." }, "1597": { "code": 1597, - "desc": "Replication Director para Oracle policy requires um SLP", - "first_action": "Configure um SLP com um Snapshot como o first operation", - "full_action": "Configure um SLP com um Snapshot como o first operation\nandReplicationasasubsequentoperation.SpecifythisSLPastheOverridepolicy\narmazenamento selection on o Cheio schedule." + "desc": "Replication Director for Oracle policy requires an SLP", + "first_action": "Configure an SLP with a Snapshot as the first operation", + "full_action": "Configure an SLP with a Snapshot as the first operation\nandReplicationasasubsequentoperation.SpecifythisSLPastheOverridepolicy\nstorage selection on the Full schedule." }, "1598": { "code": 1598, - "desc": "Oracle policy com PFI e FI enabled requires um SLP", - "first_action": "Configure um SLP com um Snapshot como o first operation.", - "full_action": "Configure um SLP com um Snapshot como o first operation.\nSpecify this SLP como o Override policy armazenamento selection on o Cheio schedule." + "desc": "Oracle policy with PFI and FI enabled requires an SLP", + "first_action": "Configure an SLP with a Snapshot as the first operation.", + "full_action": "Configure an SLP with a Snapshot as the first operation.\nSpecify this SLP as the Override policy storage selection on the Full schedule." }, "1599": { "code": 1599, - "desc": "Application schedule armazenamento selection não é possível be um snapshot SLP", - "first_action": "Specify um non-SLP armazenamento (basic disco, tape, advanced", - "full_action": "Specify um non-SLP armazenamento (basic disco, tape, advanced\ndisk,etc.)oranSLPwithBackupasthefirstoperationforanOverridepolicystorage\nselection on o Application schedule" + "desc": "Application schedule storage selection cannot be a snapshot SLP", + "first_action": "Specify a non-SLP storage (basic disk, tape, advanced", + "full_action": "Specify a non-SLP storage (basic disk, tape, advanced\ndisk,etc.)oranSLPwithBackupasthefirstoperationforanOverridepolicystorage\nselection on the Application schedule" }, "1600": { "code": 1600, - "desc": "ThePolicystorageisasnapshotSLPandtheApplicationscheduledoes não override o policy armazenamento selection. Snapshot SLP armazenamento está não allowed on um Application schedule.", - "first_action": "Specify um non-SLP armazenamento (basic disco, tape, advanced", - "full_action": "Specify um non-SLP armazenamento (basic disco, tape, advanced\ndisco, etc.) ou um SLP com Backup como o first operation para o Policy armazenamento ou como\no Override policy armazenamento selection on o Application schedule." + "desc": "ThePolicystorageisasnapshotSLPandtheApplicationscheduledoes not override the policy storage selection. Snapshot SLP storage is not allowed on an Application schedule.", + "first_action": "Specify a non-SLP storage (basic disk, tape, advanced", + "full_action": "Specify a non-SLP storage (basic disk, tape, advanced\ndisk, etc.) or an SLP with Backup as the first operation for the Policy storage or as\nthe Override policy storage selection on the Application schedule." }, "1601": { "code": 1601, - "desc": "Cheio schedule requires um snapshot SLP", - "first_action": "Configure um SLP com um Snapshot como o first operation.", - "full_action": "Configure um SLP com um Snapshot como o first operation.\nSpecify this SLP como o Override policy armazenamento selection on o Cheio schedule." + "desc": "Full schedule requires a snapshot SLP", + "first_action": "Configure an SLP with a Snapshot as the first operation.", + "full_action": "Configure an SLP with a Snapshot as the first operation.\nSpecify this SLP as the Override policy storage selection on the Full schedule." }, "1602": { "code": 1602, - "desc": "O Policy armazenamento está não um snapshot SLP e o Cheio schedule does não override o policy armazenamento selection. Snapshot SLP armazenamento está requerido on o Cheio schedule.", + "desc": "The Policy storage is not a snapshot SLP and the Full schedule does not override the policy storage selection. Snapshot SLP storage is required on the Full schedule.", "first_action": "SpecifyeitheranSLPwithaSnapshotasthefirstoperation", - "full_action": "SpecifyeitheranSLPwithaSnapshotasthefirstoperation\npara o Policy armazenamento ou como o Override policy armazenamento selection on o Cheio\nschedule." + "full_action": "SpecifyeitheranSLPwithaSnapshotasthefirstoperation\nfor the Policy storage or as the Override policy storage selection on the Full\nschedule." }, "1603": { "code": 1603, - "desc": "Falhou to save target SLP volume informação", - "first_action": "Take ação como dictated por o EMM logs.", - "full_action": "Take ação como dictated por o EMM logs." + "desc": "Failed to save target SLP volume information", + "first_action": "Take action as dictated by the EMM logs.", + "full_action": "Take action as dictated by the EMM logs." }, "1604": { "code": 1604, - "desc": "Não import SLP(s) found com compatible data class.", - "first_action": "Nenhuma ação recomendada específica encontrada não manual.", + "desc": "No import SLP(s) found with compatible data class.", + "first_action": "No specific recommended action found in the manual.", "full_action": "" }, "1608": { "code": 1608, - "desc": "Theregionassetthatisusedasacloudsnapshotreplicationdestination does não exist. Enter um valid region asset.", + "desc": "Theregionassetthatisusedasacloudsnapshotreplicationdestination does not exist. Enter a valid region asset.", "first_action": "VerifytheregionassetIDandperformtheoperationagain.", "full_action": "VerifytheregionassetIDandperformtheoperationagain." }, "1609": { "code": 1609, - "desc": "O region asset está already used como um cloud snapshot replication destination. Provide um different region asset. NetBackup status codes 392 NetBackup status codes", - "first_action": "Use multiple schedules ou use um different region asset.", - "full_action": "Use multiple schedules ou use um different region asset." + "desc": "The region asset is already used as a cloud snapshot replication destination. Provide a different region asset. NetBackup status codes 392 NetBackup status codes", + "first_action": "Use multiple schedules or use a different region asset.", + "full_action": "Use multiple schedules or use a different region asset." }, "1610": { "code": 1610, - "desc": "TheprovidedregionassetsassociatewithadifferentSnapshotManagers. O provided region assets must associate com o same Snapshot Manager.", - "first_action": "Garanta que specified region assets associate com o", - "full_action": "Garanta que specified region assets associate com o\nsame Snapshot Manager. Update o cloud provider plug-in configuration details\naccordingly." + "desc": "TheprovidedregionassetsassociatewithadifferentSnapshotManagers. The provided region assets must associate with the same Snapshot Manager.", + "first_action": "Ensure that specified region assets associate with the", + "full_action": "Ensure that specified region assets associate with the\nsame Snapshot Manager. Update the cloud provider plug-in configuration details\naccordingly." }, "1611": { "code": 1611, - "desc": "O assets que estão subscribed to o protection plan belong to different Snapshot Managers. Subscribed assets must belong to o same Snapshot Manager.", + "desc": "The assets that are subscribed to the protection plan belong to different Snapshot Managers. Subscribed assets must belong to the same Snapshot Manager.", "first_action": "FortheassetsthatareassociatedwithdifferentSnapshot", "full_action": "FortheassetsthatareassociatedwithdifferentSnapshot\nManagers, create different protection plans." }, "1612": { "code": 1612, - "desc": "Some de o selected assets belong to um Snapshot Manager other than o Snapshot Manager de o snapshot replication destination region asset. O assets must belong to o same Snapshot Manager.", - "first_action": "Garanta que o region assets associate com o same", - "full_action": "Garanta que o region assets associate com o same\nSnapshot Manager. Update o cloud provider plug-in configuration details\naccordingly." + "desc": "Some of the selected assets belong to a Snapshot Manager other than the Snapshot Manager of the snapshot replication destination region asset. The assets must belong to the same Snapshot Manager.", + "first_action": "Ensure that the region assets associate with the same", + "full_action": "Ensure that the region assets associate with the same\nSnapshot Manager. Update the cloud provider plug-in configuration details\naccordingly." }, "1613": { "code": 1613, - "desc": "Para some de o selected assets, o source region está same como o cloud snapshot replication destination region. O source region e o cloud snapshot replication destination region must be different.", - "first_action": "O source region e o cloud snapshot replication", - "full_action": "O source region e o cloud snapshot replication\ndestination region must be different." + "desc": "For some of the selected assets, the source region is same as the cloud snapshot replication destination region. The source region and the cloud snapshot replication destination region must be different.", + "first_action": "The source region and the cloud snapshot replication", + "full_action": "The source region and the cloud snapshot replication\ndestination region must be different." }, "1614": { "code": 1614, - "desc": "Cloud snapshot replication está supported apenas para Amazon cloud assets.", - "first_action": "Skip o assets que do não belong to Amazon cloud", - "full_action": "Skip o assets que do não belong to Amazon cloud\nprovider." + "desc": "Cloud snapshot replication is supported only for Amazon cloud assets.", + "first_action": "Skip the assets that do not belong to Amazon cloud", + "full_action": "Skip the assets that do not belong to Amazon cloud\nprovider." }, "1615": { "code": 1615, - "desc": "Cloud snapshot replication está não supported para o asset type region.", - "first_action": "Skip o asset com type region.", - "full_action": "Skip o asset com type region." + "desc": "Cloud snapshot replication is not supported for the asset type region.", + "first_action": "Skip the asset with type region.", + "full_action": "Skip the asset with type region." }, "1616": { "code": 1616, - "desc": "Checkpoints estão apenas allowed para o Backup from Snapshot armazenamento lifecycle policy operation. NetBackup status codes 394 NetBackup status codes", + "desc": "Checkpoints are only allowed for the Backup from Snapshot storage lifecycle policy operation. NetBackup status codes 394 NetBackup status codes", "first_action": "UpdatethebackuppolicytouseBackupfromSnapshot", - "full_action": "UpdatethebackuppolicytouseBackupfromSnapshot\narmazenamento lifecycle operation before checkpoint functionality está enabled." + "full_action": "UpdatethebackuppolicytouseBackupfromSnapshot\nstorage lifecycle operation before checkpoint functionality is enabled." }, "1617": { "code": 1617, - "desc": "Cloud snapshot indexing está não supported para o specified asset.", - "first_action": "Garanta que o Snapshot Manager está deployed in o same region como o", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Garanta que o Snapshot Manager está deployed in o same region como o\nspecified asset.\n■ Review o Snapshot Manager supported versions para indexing." + "desc": "Cloud snapshot indexing is not supported for the specified asset.", + "first_action": "Ensure that the Snapshot Manager is deployed in the same region as the", + "full_action": "Perform the following, as appropriate:\n■ Ensure that the Snapshot Manager is deployed in the same region as the\nspecified asset.\n■ Review the Snapshot Manager supported versions for indexing." }, "1618": { "code": 1618, - "desc": "This retention period está incompatible com WORM armazenamento expiration duration. O lock minimum e maximum duration can be found in disco pool properties.Anupdatetodiskpoolpropertiesmaybeneededifconfigurationchanges have been made to o underlying armazenamento.", - "first_action": "O seguinte procedure may be necessary once you estão", - "full_action": "O seguinte procedure may be necessary once you estão\nsure que o retention level matches o range o underlying o armazenamento volume\nallows. This procedure apenas aplica-se if o NetBackup Administration Console está in\nuse to create o policy.\nTo adjust o retention level\n1 Save o policy schedule com o desired retention level, but com armazenamento\nselected como qualquer disponível.\n2 Edit o policy again, e now select o desired armazenamento unidade in o policy\nattributes." + "desc": "This retention period is incompatible with WORM storage expiration duration. The lock minimum and maximum duration can be found in disk pool properties.Anupdatetodiskpoolpropertiesmaybeneededifconfigurationchanges have been made to the underlying storage.", + "first_action": "The following procedure may be necessary once you are", + "full_action": "The following procedure may be necessary once you are\nsure that the retention level matches the range the underlying the storage volume\nallows. This procedure only applies if the NetBackup Administration Console is in\nuse to create the policy.\nTo adjust the retention level\n1 Save the policy schedule with the desired retention level, but with storage\nselected as any available.\n2 Edit the policy again, and now select the desired storage unit in the policy\nattributes." }, "1630": { "code": 1630, - "desc": "WhileconfiguringaNetBackuppolicywiththeCohesitysnapshotoption (VSO) FIM, you must select um SLP como Policy armazenamento destination.", - "first_action": "Select Policy armazenamento como armazenamento lifecycle policy. If you", - "full_action": "Select Policy armazenamento como armazenamento lifecycle policy. If you\nselectSTUasthePolicystorageoption,selectOverridepolicystorageselection\ncom o SLP option." + "desc": "WhileconfiguringaNetBackuppolicywiththeCohesitysnapshotoption (VSO) FIM, you must select an SLP as Policy storage destination.", + "first_action": "Select Policy storage as storage lifecycle policy. If you", + "full_action": "Select Policy storage as storage lifecycle policy. If you\nselectSTUasthePolicystorageoption,selectOverridepolicystorageselection\nwith the SLP option." }, "1633": { "code": 1633, - "desc": "Inválido mídia servidor está provided in o API request.", - "first_action": "Provide um valid NetBackup mídia servidor name.", - "full_action": "Provide um valid NetBackup mídia servidor name." + "desc": "Invalid media server is provided in the API request.", + "first_action": "Provide a valid NetBackup media server name.", + "full_action": "Provide a valid NetBackup media server name." }, "1634": { "code": 1634, - "desc": "Não foi possível to process o EMM request.", - "first_action": "Verifique whether o EMM service está up e executando.", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique whether o EMM service está up e executando.\n■ To diagnose o issue, review o EMM servidor logs para issues e troubleshoot\ncomo necessary." + "desc": "Unable to process the EMM request.", + "first_action": "Check whether the EMM service is up and running.", + "full_action": "Perform the following as appropriate:\n■ Check whether the EMM service is up and running.\n■ To diagnose the issue, review the EMM server logs for issues and troubleshoot\nas necessary." }, "1635": { "code": 1635, - "desc": "Não foi possível to conectar com o EMM servidor.", - "first_action": "Troubleshoot qualquer EMM servidor conexão falha issues.", - "full_action": "Troubleshoot qualquer EMM servidor conexão falha issues." + "desc": "Unable to connect with the EMM server.", + "first_action": "Troubleshoot any EMM server connection failure issues.", + "full_action": "Troubleshoot any EMM server connection failure issues." }, "1636": { "code": 1636, - "desc": "Backup time range filter está não supported in o API request.", + "desc": "Backup time range filter is not supported in the API request.", "first_action": "ChangetheAPIrequestsothatitdoesnotusethebackup", - "full_action": "ChangetheAPIrequestsothatitdoesnotusethebackup\ntime range filter (greater than e lesser than)." + "full_action": "ChangetheAPIrequestsothatitdoesnotusethebackup\ntime range filter (greater than and lesser than)." }, "1637": { "code": 1637, - "desc": "Duplicate filters estão não supported in o API request.", - "first_action": "You não é possível use o same filter twice in o API request.", - "full_action": "You não é possível use o same filter twice in o API request.\nReview o API request e remove qualquer de o same filters que estão used twice." + "desc": "Duplicate filters are not supported in the API request.", + "first_action": "You cannot use the same filter twice in the API request.", + "full_action": "You cannot use the same filter twice in the API request.\nReview the API request and remove any of the same filters that are used twice." }, "1641": { "code": 1641, "desc": "TrueimagerestoreissupportedonlyforSLPswithbackupfromsnapshot.", - "first_action": "Configure um policy usando um SLP which has backup from", - "full_action": "Configure um policy usando um SLP which has backup from\nsnapshot e select o True image restauração option." + "first_action": "Configure a policy using an SLP which has backup from", + "full_action": "Configure a policy using an SLP which has backup from\nsnapshot and select the True image restore option." }, "1642": { "code": 1642, - "desc": "Para ISM on-premises replication, o cliente ou alternate cliente configurado in o policy está não supported.", - "first_action": "Update o policy por selecting o cliente ou o alternate", - "full_action": "Update o policy por selecting o cliente ou o alternate\ncliente to version NetBackup 10.5 ou higher." + "desc": "For ISM on-premises replication, the client or alternate client configured in the policy is not supported.", + "first_action": "Update the policy by selecting the client or the alternate", + "full_action": "Update the policy by selecting the client or the alternate\nclient to version NetBackup 10.5 or higher." }, "1643": { "code": 1643, - "desc": "Accelerator option está não supported para SLPs com index from snapshot.", - "first_action": "Clear o Use Accelerator option in o policy", - "full_action": "Clear o Use Accelerator option in o policy\nconfiguration." + "desc": "Accelerator option is not supported for SLPs with index from snapshot.", + "first_action": "Clear the Use Accelerator option in the policy", + "full_action": "Clear the Use Accelerator option in the policy\nconfiguration." }, "1800": { "code": 1800, - "desc": "Inválido cliente list", + "desc": "Invalid client list", "first_action": "Specifyonlyoneclientinthepolicy,orremovethedirective", - "full_action": "Specifyonlyoneclientinthepolicy,orremovethedirective\nfrom o backup selection que does não support multiple cliente.\nVeja o Troubleshooting section de o NetBackup para Enterprise Vault Agent\nAdministrator’s Guide." + "full_action": "Specifyonlyoneclientinthepolicy,orremovethedirective\nfrom the backup selection that does not support multiple client.\nSee the Troubleshooting section of the NetBackup for Enterprise Vault Agent\nAdministrator’s Guide." }, "1915": { "code": 1915, - "desc": "Não é possível excluir instance group que contains instances (excluir ou move instances first)", - "first_action": "First excluir o instances individually por selecting them", - "full_action": "First excluir o instances individually por selecting them\nunder o instances node in o NetBackup Administration Console ou por usando\no comando. After todos o instances in o group have been deleted, try again to\nexcluir o group." + "desc": "Cannot delete instance group that contains instances (delete or move instances first)", + "first_action": "First delete the instances individually by selecting them", + "full_action": "First delete the instances individually by selecting them\nunder the instances node in the NetBackup Administration Console or by using\nthe command. After all the instances in the group have been deleted, try again to\ndelete the group." }, "1916": { "code": 1916, - "desc": "Banco de dados erro, não é possível access o instance repository", - "first_action": "Make sure que todos NetBackup services estão started e", - "full_action": "Make sure que todos NetBackup services estão started e\nque nbdb instalado correctly." + "desc": "Database error, cannot access the instance repository", + "first_action": "Make sure that all NetBackup services are started and", + "full_action": "Make sure that all NetBackup services are started and\nthat nbdb installed correctly." }, "1917": { "code": 1917, - "desc": "Não é possível add instance group, this group name está already in use", - "first_action": "Type um different group name in o appropriate field, e", - "full_action": "Type um different group name in o appropriate field, e\ntry to add o group again." + "desc": "Cannot add instance group, this group name is already in use", + "first_action": "Type a different group name in the appropriate field, and", + "full_action": "Type a different group name in the appropriate field, and\ntry to add the group again." }, "1918": { "code": 1918, - "desc": "Não é possível find um group por this name", - "first_action": "Refresh o view (F5 key).", - "full_action": "Refresh o view (F5 key)." + "desc": "Cannot find a group by this name", + "first_action": "Refresh the view (F5 key).", + "full_action": "Refresh the view (F5 key)." }, "1919": { "code": 1919, - "desc": "Another process modified this instance, banco de dados, ou instance group.", - "first_action": "When o Oracle APIs estão used, if o If-Match header value does não match", - "full_action": "Refresh o view (F5 key) in o NetBackup\nAdministration Console.\nDo o seguinte como appropriate:\n■ When o Oracle APIs estão used, if o If-Match header value does não match\no returned ETag value para o object you attempt to modify. Retrieve o latest\nversion de o object’s ETag e attempt seu operation again." + "desc": "Another process modified this instance, database, or instance group.", + "first_action": "When the Oracle APIs are used, if the If-Match header value does not match", + "full_action": "Refresh the view (F5 key) in the NetBackup\nAdministration Console.\nDo the following as appropriate:\n■ When the Oracle APIs are used, if the If-Match header value does not match\nthe returned ETag value for the object you attempt to modify. Retrieve the latest\nversion of the object’s ETag and attempt your operation again." }, "1920": { "code": 1920, - "desc": "Um instance com this name e cliente already exists", + "desc": "An instance with this name and client already exists", "first_action": "CLI:Usenboracmd list instancesornbsqlcmd list instancestoviewthe", - "full_action": "Do one de o seguinte:\n■ CLI:Usenboracmd list instancesornbsqlcmd list instancestoviewthe\ninstances que already exist.\n■ GUI: Refresh o view (F5 key)." + "full_action": "Do one of the following:\n■ CLI:Usenboracmd list instancesornbsqlcmd list instancestoviewthe\ninstances that already exist.\n■ GUI: Refresh the view (F5 key)." }, "1921": { "code": 1921, - "desc": "O specified instance ou banco de dados não é possível be found.", - "first_action": "CLI: Make sure que o instance ou o banco de dados name está spelled correctly. If", - "full_action": "Do one de o seguinte:\n■ CLI: Make sure que o instance ou o banco de dados name está spelled correctly. If\nworking com um RAC banco de dados, o banco de dados unique name está case-sensitive.\nOn Windows, o instance name está não case-sensitive. On UNIX, o instance\nname está case-sensitive.\n■ GUI: Refresh o view (F5 key)." + "desc": "The specified instance or database cannot be found.", + "first_action": "CLI: Make sure that the instance or the database name is spelled correctly. If", + "full_action": "Do one of the following:\n■ CLI: Make sure that the instance or the database name is spelled correctly. If\nworking with a RAC database, the database unique name is case-sensitive.\nOn Windows, the instance name is not case-sensitive. On UNIX, the instance\nname is case-sensitive.\n■ GUI: Refresh the view (F5 key)." }, "1924": { "code": 1924, - "desc": "Domain está um requerido field para Windows instances", - "first_action": "Specify um domain in o domain field, then try to register", - "full_action": "Specify um domain in o domain field, then try to register\no instance again." + "desc": "Domain is a required field for Windows instances", + "first_action": "Specify a domain in the domain field, then try to register", + "full_action": "Specify a domain in the domain field, then try to register\nthe instance again." }, "1925": { "code": 1925, - "desc": "O solicitado operation(s) falhou", + "desc": "The requested operation(s) failed", "first_action": "Recheckthecommandlinearguments.Iftheerrorpersists,", - "full_action": "Recheckthecommandlinearguments.Iftheerrorpersists,\nverifique o debug logs para pistas ou contate Cohesity Technical Support." + "full_action": "Recheckthecommandlinearguments.Iftheerrorpersists,\ncheck the debug logs for clues or contact Cohesity Technical Support." }, "1926": { "code": 1926, - "desc": "O entry specified already exists", + "desc": "The entry specified already exists", "first_action": "TheDBAhasalreadybeenadded,sonoactionisneeded.", "full_action": "TheDBAhasalreadybeenadded,sonoactionisneeded." }, "1927": { "code": 1927, - "desc": "O entry specified does não exist", - "first_action": "O entry has already been deleted, so não ação está likely", - "full_action": "O entry has already been deleted, so não ação está likely\nneeded." + "desc": "The entry specified does not exist", + "first_action": "The entry has already been deleted, so no action is likely", + "full_action": "The entry has already been deleted, so no action is likely\nneeded." }, "1928": { "code": 1928, - "desc": "O credentials para 1 ou more instances could não be verified NetBackup status codes 402 NetBackup status codes", - "first_action": "Make sure que o cliente está executando at least this version", - "full_action": "Make sure que o cliente está executando at least this version\nde NetBackup, e está configurado to use o correct master servidor. Make sure que\nyoucorrectlyenteredtheusername,password,andauxiliaryfieldssuchasdomain\n(Windows) ou TNS (Oracle ou RMAN)." + "desc": "The credentials for 1 or more instances could not be verified NetBackup status codes 402 NetBackup status codes", + "first_action": "Make sure that the client is running at least this version", + "full_action": "Make sure that the client is running at least this version\nof NetBackup, and is configured to use the correct master server. Make sure that\nyoucorrectlyenteredtheusername,password,andauxiliaryfieldssuchasdomain\n(Windows) or TNS (Oracle or RMAN)." }, "1932": { "code": 1932, - "desc": "Aninstance,database,orinstancegroupcannotbedeletedorrenamed when it está included in um policy.", - "first_action": "Remove o instance, banco de dados, ou instance group from", - "full_action": "Remove o instance, banco de dados, ou instance group from\ntodos policies. Once o instance, banco de dados, ou instance group está removed from todos\npolicies you can retry o deletion ou o modification process." + "desc": "Aninstance,database,orinstancegroupcannotbedeletedorrenamed when it is included in a policy.", + "first_action": "Remove the instance, database, or instance group from", + "full_action": "Remove the instance, database, or instance group from\nall policies. Once the instance, database, or instance group is removed from all\npolicies you can retry the deletion or the modification process." }, "1933": { "code": 1933, - "desc": "Não é possível change instance ou banco de dados state without credentials.", - "first_action": "Verifique que o banco de dados está registered before you attempt", - "full_action": "Verifique que o banco de dados está registered before you attempt\nto change o banco de dados state." + "desc": "Cannot change instance or database state without credentials.", + "first_action": "Verify that the database is registered before you attempt", + "full_action": "Verify that the database is registered before you attempt\nto change the database state." }, "1946": { "code": 1946, - "desc": "O current version de NetBackup on o cliente está incorrect para o validation de o solicitado credential type. NetBackup status codes 403 NetBackup status codes", - "first_action": "Upgrade o NetBackup cliente to o current version de", - "full_action": "Upgrade o NetBackup cliente to o current version de\nNetBackup." + "desc": "The current version of NetBackup on the client is incorrect for the validation of the requested credential type. NetBackup status codes 403 NetBackup status codes", + "first_action": "Upgrade the NetBackup client to the current version of", + "full_action": "Upgrade the NetBackup client to the current version of\nNetBackup." }, "1952": { "code": 1952, - "desc": "Um availability group não é possível be deleted when it está included in um policy. First remove o availability group from todos policies.", - "first_action": "Remove o availability group from o policies in which", - "full_action": "Remove o availability group from o policies in which\nit está included. Then try again to excluir o availability group." + "desc": "An availability group cannot be deleted when it is included in a policy. First remove the availability group from all policies.", + "first_action": "Remove the availability group from the policies in which", + "full_action": "Remove the availability group from the policies in which\nit is included. Then try again to delete the availability group." }, "1953": { "code": 1953, - "desc": "Não foi possível to excluir o asset because metadata para it exists. Expire qualquer backup images que contain o asset e try again.", - "first_action": "Expire qualquer backup images que contain o asset e try", - "full_action": "Expire qualquer backup images que contain o asset e try\no operation again." + "desc": "Unable to delete the asset because metadata for it exists. Expire any backup images that contain the asset and try again.", + "first_action": "Expire any backup images that contain the asset and try", + "full_action": "Expire any backup images that contain the asset and try\nthe operation again." }, "1954": { "code": 1954, - "desc": "Moving um instance to um different RAC cluster está não allowed.", - "first_action": "O instance must be excluir e added into um different", - "full_action": "O instance must be excluir e added into um different\nRAC cluster." + "desc": "Moving an instance to a different RAC cluster is not allowed.", + "first_action": "The instance must be delete and added into a different", + "full_action": "The instance must be delete and added into a different\nRAC cluster." }, "1955": { "code": 1955, - "desc": "Registering um RAC instance está não allowed.", - "first_action": "Credentials must be provided para todos nodes de o RAC", - "full_action": "Credentials must be provided para todos nodes de o RAC\ncluster at o banco de dados level. If you need to back up um node in o RAC cluster como\num single instance you must excluir o instance. After you excluir que instance you\nmust add it como um single instance e add o single instance to o backup policy." + "desc": "Registering a RAC instance is not allowed.", + "first_action": "Credentials must be provided for all nodes of the RAC", + "full_action": "Credentials must be provided for all nodes of the RAC\ncluster at the database level. If you need to back up a node in the RAC cluster as\na single instance you must delete the instance. After you delete that instance you\nmust add it as a single instance and add the single instance to the backup policy." }, "1956": { "code": 1956, - "desc": "Um registered, single instance não é possível be moved to um RAC cluster.", - "first_action": "To add um existing instance to um existing RAC cluster", - "full_action": "To add um existing instance to um existing RAC cluster\nyou must excluir que instance e then add it into o RAC cluster." + "desc": "A registered, single instance cannot be moved to a RAC cluster.", + "first_action": "To add an existing instance to an existing RAC cluster", + "full_action": "To add an existing instance to an existing RAC cluster\nyou must delete that instance and then add it into the RAC cluster." }, "1957": { "code": 1957, - "desc": "Não foi possível to register um RAC cluster como it does não contain qualquer RAC instances.", - "first_action": "Add at least one RAC instance to seu RAC cluster within", - "full_action": "Add at least one RAC instance to seu RAC cluster within\nNetBackup." + "desc": "Unable to register a RAC cluster as it does not contain any RAC instances.", + "first_action": "Add at least one RAC instance to your RAC cluster within", + "full_action": "Add at least one RAC instance to your RAC cluster within\nNetBackup." }, "1958": { "code": 1958, - "desc": "Oracle Wallet credentials não é possível be used com Oracle ou OS credentials. NetBackup status codes 405 NetBackup status codes", + "desc": "Oracle Wallet credentials cannot be used with Oracle or OS credentials. NetBackup status codes 405 NetBackup status codes", "first_action": "Oracle Wallet", - "full_action": "Retry o operation por reevaluating what types de\ncredentials estão allowed to be used com que operation.\nExamples de valid credential usages para single instances e instance groups:\n■ Oracle Wallet\n■ Oracle Wallet e RMAN\n■ OS\n■ OS e RMAN\n■ OS e Oracle\n■ OS, Oracle, e RMAN\n■ Oracle\n■ Oracle e RMAN\nExamples de valid credential usages para Oracle RAC:\n■ Wallet\n■ Oracle Wallet e RMAN\n■ Oracle\n■ Oracle e RMAN" + "full_action": "Retry the operation by reevaluating what types of\ncredentials are allowed to be used with that operation.\nExamples of valid credential usages for single instances and instance groups:\n■ Oracle Wallet\n■ Oracle Wallet and RMAN\n■ OS\n■ OS and RMAN\n■ OS and Oracle\n■ OS, Oracle, and RMAN\n■ Oracle\n■ Oracle and RMAN\nExamples of valid credential usages for Oracle RAC:\n■ Wallet\n■ Oracle Wallet and RMAN\n■ Oracle\n■ Oracle and RMAN" }, "1960": { "code": 1960, - "desc": "Addition de um Oracle alias did não succeed.", - "first_action": "Garanta que o provided parameters correspond to um", - "full_action": "Garanta que o provided parameters correspond to um\neligible Oracle instance e alias.\nArquivo system mount caminho." + "desc": "Addition of an Oracle alias did not succeed.", + "first_action": "Ensure that the provided parameters correspond to an", + "full_action": "Ensure that the provided parameters correspond to an\neligible Oracle instance and alias.\nFile system mount path." }, "1961": { "code": 1961, - "desc": "Deletion de um Oracle alias did não succeed. NetBackup status codes 406 NetBackup status codes", - "first_action": "Garanta que o provided parameters correspond to um", - "full_action": "Garanta que o provided parameters correspond to um\neligible Oracle instance e alias. Confirm que o alias exists in NetBackup para\no instance." + "desc": "Deletion of an Oracle alias did not succeed. NetBackup status codes 406 NetBackup status codes", + "first_action": "Ensure that the provided parameters correspond to an", + "full_action": "Ensure that the provided parameters correspond to an\neligible Oracle instance and alias. Confirm that the alias exists in NetBackup for\nthe instance." }, "1962": { "code": 1962, - "desc": "RMAN catalog credentials que estão stored in um Oracle Wallet não é possível be used com Oracle ou OS credentials.", - "first_action": "Review o existing credential configuration e make", - "full_action": "Review o existing credential configuration e make\nsure que o configuration you try to switch to ou try to add to, está supported." + "desc": "RMAN catalog credentials that are stored in an Oracle Wallet cannot be used with Oracle or OS credentials.", + "first_action": "Review the existing credential configuration and make", + "full_action": "Review the existing credential configuration and make\nsure that the configuration you try to switch to or try to add to, is supported." }, "1967": { "code": 1967, - "desc": "Addition de um Oracle Data Guard did não succeed.", - "first_action": "Review o nbars debug log para additional informação.", - "full_action": "Review o nbars debug log para additional informação." + "desc": "Addition of an Oracle Data Guard did not succeed.", + "first_action": "Review the nbars debug log for additional information.", + "full_action": "Review the nbars debug log for additional information." }, "1968": { "code": 1968, - "desc": "Deletion de um Oracle Data Guard did não succeed.", - "first_action": "Review o nbars debug log para additional informação.", - "full_action": "Review o nbars debug log para additional informação." + "desc": "Deletion of an Oracle Data Guard did not succeed.", + "first_action": "Review the nbars debug log for additional information.", + "full_action": "Review the nbars debug log for additional information." }, "1969": { "code": 1969, - "desc": "O specified Oracle Data Guard não é possível be found.", - "first_action": "Verifique que o Oracle Data Guard has been entered into", - "full_action": "Verifique que o Oracle Data Guard has been entered into\no NetBackup banco de dados. Review o bprd e o nbars debug logs para additional\ninformação." + "desc": "The specified Oracle Data Guard cannot be found.", + "first_action": "Verify that the Oracle Data Guard has been entered into", + "full_action": "Verify that the Oracle Data Guard has been entered into\nthe NetBackup database. Review the bprd and the nbars debug logs for additional\ninformation." }, "1970": { "code": 1970, - "desc": "Update de um Oracle Data Guard configuration did não succeed.", - "first_action": "To troubleshoot o Oracle Data Guard configuration update", - "full_action": "Executar o seguinte procedure:\nTo troubleshoot o Oracle Data Guard configuration update\n1 Verifique que o Oracle Data Guard exists in o NetBackup banco de dados.\n2 Verifique que o Oracle instance ou o RAC banco de dados exists in o NetBackup\nbanco de dados.\n3 Review o nbars debug log para additional informação." + "desc": "Update of an Oracle Data Guard configuration did not succeed.", + "first_action": "To troubleshoot the Oracle Data Guard configuration update", + "full_action": "Perform the following procedure:\nTo troubleshoot the Oracle Data Guard configuration update\n1 Verify that the Oracle Data Guard exists in the NetBackup database.\n2 Verify that the Oracle instance or the RAC database exists in the NetBackup\ndatabase.\n3 Review the nbars debug log for additional information." }, "1974": { "code": 1974, - "desc": "Clone may fail without um valid set de redo logs.", - "first_action": "Review o Oracle cloning chapter in o NetBackup para", - "full_action": "Review o Oracle cloning chapter in o NetBackup para\nOracle Administrator's Guide para more informação.\nO seguinte example RMAN steps may resolve o issue after um clone:\nSQL> alter banco de dados drop standby logfile group 1;\nBanco de dados altered.\nSQL> alter banco de dados drop standby logfile group 2;\nBanco de dados altered.\nSQL> alter banco de dados drop standby logfile group 3;\nBanco de dados altered.\nSQL> ALTER Banco de dados ADD LOGFILE group 1 ('c:\\clone\\REDO01.LOG') size 5M;\nBanco de dados altered.\nSQL> ALTER Banco de dados ADD LOGFILE group 2 ('c:\\clone\\REDO02.LOG') size 5M;\nBanco de dados altered.\nSQL> alter banco de dados activate standby banco de dados;\nBanco de dados altered.\nSQL> alter banco de dados abrir;\nBanco de dados altered.\nSQL>" + "desc": "Clone may fail without a valid set of redo logs.", + "first_action": "Review the Oracle cloning chapter in the NetBackup for", + "full_action": "Review the Oracle cloning chapter in the NetBackup for\nOracle Administrator's Guide for more information.\nThe following example RMAN steps may resolve the issue after a clone:\nSQL> alter database drop standby logfile group 1;\nDatabase altered.\nSQL> alter database drop standby logfile group 2;\nDatabase altered.\nSQL> alter database drop standby logfile group 3;\nDatabase altered.\nSQL> ALTER DATABASE ADD LOGFILE group 1 ('c:\\clone\\REDO01.LOG') size 5M;\nDatabase altered.\nSQL> ALTER DATABASE ADD LOGFILE group 2 ('c:\\clone\\REDO02.LOG') size 5M;\nDatabase altered.\nSQL> alter database activate standby database;\nDatabase altered.\nSQL> alter database open;\nDatabase altered.\nSQL>" }, "2000": { "code": 2000, "desc": "Unabletoallocatenewmediaforbackup,storageunithasnoneavailable.", - "first_action": "Verifique o NetBackup Problemas relatório to determinar o armazenamento unidade que está fora", - "full_action": "Try o seguinte:\n■ Verifique o NetBackup Problemas relatório to determinar o armazenamento unidade que está fora\nde mídia.\n■ If o armazenamento unidade está um robot com vazio slots, add more volumes e specify\nthecorrectvolumepool.Ifnoemptyslotsexist,movesomemediatonon-robotic\ne add new volumes. If you have difficulty keeping track de seu disponível\nvolumes, try o available_media script located in o seguinte diretório:\nOn UNIX: /usr/openv/netbackup/bin/goodies/available_media\nOnWindows:install_path\\NetBackup\\bin\\goodies\\available_media.cmd\nThis script lists todos volumes in o volume configuration, e informação on o\nvolumes currently assigned to NetBackup.\n■ Set up um scratch volume pool como um reserve de unassigned tapes. If NetBackup\nneeds um new tape e nenhum estão disponível in o current volume pool, it moves\num tape from o scratch pool into o volume pool que o backup uses.\n■ If o armazenamento unidade e volume pool appear to have mídia, verifique o seguinte:\n■ Use o NetBackup Mídia List relatório to verifique if o volume está FROZEN ou\nSUSPENDED.If so, use o bpmedia comando to unfreeze it ou unsuspend\nit, if so desired.\n■ O volume has não expired ou excedido its maximum number de mounts.\n■ O EMM banco de dados host name para o dispositivo está correct. If you change o\nEMM banco de dados host name, stop e restart o Mídia Manager dispositivo\ndaemon(ltidforaUNIXserver)ortheNetBackupDeviceManagerservice\n(Windows servidor).\n■ O correct host está specified para o armazenamento unidade in o NetBackup\nconfiguration. O host conexão must be o servidor (master ou mídia)\ncom drives connected to it.\n■ O Mídia e Dispositivo Management volume configuration has mídia in o\ncorrect volume pool. Unassigned ou active mídia está disponível at o requerido\nretention level. Use o NetBackup Mídia List relatório to show o retention\nlevels, volume pools, e status para todos volumes. Use o NetBackup Mídia\nSummary relatório to verifique para active volumes at o correct retention levels.\n■ Create o bptm debug log diretório, e set o MDS VxUL logging (OID 143)\nto debug level 2. Then retry o operation.\n■ If this armazenamento unidade está new e this attempt to use it está o first, stop e restart\nNetBackup on o master servidor. O MDS unified logging arquivos (OID 143) at\ndebug level 2 usually show o NetBackup mídia selection process." + "first_action": "Check the NetBackup Problems report to determine the storage unit that is out", + "full_action": "Try the following:\n■ Check the NetBackup Problems report to determine the storage unit that is out\nof media.\n■ If the storage unit is a robot with empty slots, add more volumes and specify\nthecorrectvolumepool.Ifnoemptyslotsexist,movesomemediatonon-robotic\nand add new volumes. If you have difficulty keeping track of your available\nvolumes, try the available_media script located in the following directory:\nOn UNIX: /usr/openv/netbackup/bin/goodies/available_media\nOnWindows:install_path\\NetBackup\\bin\\goodies\\available_media.cmd\nThis script lists all volumes in the volume configuration, and information on the\nvolumes currently assigned to NetBackup.\n■ Set up a scratch volume pool as a reserve of unassigned tapes. If NetBackup\nneeds a new tape and none are available in the current volume pool, it moves\na tape from the scratch pool into the volume pool that the backup uses.\n■ If the storage unit and volume pool appear to have media, verify the following:\n■ Use the NetBackup Media List report to check if the volume is FROZEN or\nSUSPENDED.If so, use the bpmedia command to unfreeze it or unsuspend\nit, if so desired.\n■ The volume has not expired or exceeded its maximum number of mounts.\n■ The EMM database host name for the device is correct. If you change the\nEMM database host name, stop and restart the Media Manager device\ndaemon(ltidforaUNIXserver)ortheNetBackupDeviceManagerservice\n(Windows server).\n■ The correct host is specified for the storage unit in the NetBackup\nconfiguration. The host connection must be the server (master or media)\nwith drives connected to it.\n■ The Media and Device Management volume configuration has media in the\ncorrect volume pool. Unassigned or active media is available at the required\nretention level. Use the NetBackup Media List report to show the retention\nlevels, volume pools, and status for all volumes. Use the NetBackup Media\nSummary report to check for active volumes at the correct retention levels.\n■ Create the bptm debug log directory, and set the MDS VxUL logging (OID 143)\nto debug level 2. Then retry the operation.\n■ If this storage unit is new and this attempt to use it is the first, stop and restart\nNetBackup on the master server. The MDS unified logging files (OID 143) at\ndebug level 2 usually show the NetBackup media selection process." }, "2001": { "code": 2001, - "desc": "Não drives estão disponível para this job NetBackup status codes 410 NetBackup status codes", - "first_action": "Verifique que o requerido drives e robots estão configurado e up.", - "full_action": "Try o seguinte:\n■ Verifique que o requerido drives e robots estão configurado e up.\n■ Verifique que ltid está active e um drive caminho exists que está configurado on o drive\npara o mídia servidor que o armazenamento unidade requires.\n■ If o job requires um NDMP drive caminho, verifique que one exists." + "desc": "No drives are available for this job NetBackup status codes 410 NetBackup status codes", + "first_action": "Verify that the required drives and robots are configured and up.", + "full_action": "Try the following:\n■ Verify that the required drives and robots are configured and up.\n■ Verify that ltid is active and a drive path exists that is configured on the drive\nfor the media server that the storage unit requires.\n■ If the job requires an NDMP drive path, verify that one exists." }, "2002": { "code": 2002, - "desc": "Inválido STU identifier type", - "first_action": "O mds unified logging arquivos (OID 143) from o master servidor at debug level", - "full_action": "This erro está internal. If o problema persists, por favor call\nNetBackup support para resolution.\nVerifique o seguinte logs:\n■ O mds unified logging arquivos (OID 143) from o master servidor at debug level\n2.\n■ O nbrb unified logging arquivos (OID 118) from o master servidor at debug level\n3." + "desc": "Invalid STU identifier type", + "first_action": "The mds unified logging files (OID 143) from the master server at debug level", + "full_action": "This error is internal. If the problem persists, please call\nNetBackup support for resolution.\nCheck the following logs:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3." }, "2003": { "code": 2003, - "desc": "Drive está não allocated.", - "first_action": "O MDS unified logging arquivos (OID 143) from o master servidor at debug level", - "full_action": "ThiserrorisinternaltotheMDScomponentofNetBackup.\nVerifique o seguinte logs:\n■ O MDS unified logging arquivos (OID 143) from o master servidor at debug level\n2.\n■ O nbrb unified logging arquivos (OID 118) from o master servidor at debug level\n3." + "desc": "Drive is not allocated.", + "first_action": "The MDS unified logging files (OID 143) from the master server at debug level", + "full_action": "ThiserrorisinternaltotheMDScomponentofNetBackup.\nCheck the following logs:\n■ The MDS unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3." }, "2004": { "code": 2004, - "desc": "Drive está already allocated", - "first_action": "Um drive may have been reset while it foi allocated para um", - "full_action": "Um drive may have been reset while it foi allocated para um\njob. Wait para o jobs que use o drive to complete." + "desc": "Drive is already allocated", + "first_action": "A drive may have been reset while it was allocated for a", + "full_action": "A drive may have been reset while it was allocated for a\njob. Wait for the jobs that use the drive to complete." }, "2005": { "code": 2005, - "desc": "MDS has received um inválido message from um mídia servidor.", - "first_action": "O mds unified logging arquivos (OID 143) from o master servidor at debug level", - "full_action": "This erro está internal. If o problema persists, por favor call\nNetBackup support para resolution.\nVerifique o seguinte logs:\n■ O mds unified logging arquivos (OID 143) from o master servidor at debug level\n2.\n■ O nbrb unified logging arquivos (OID 118) from o master servidor at debug level\n3.\n■ O bptm legacy log from o mídia servidor, com VERBOSE=5." + "desc": "MDS has received an invalid message from a media server.", + "first_action": "The mds unified logging files (OID 143) from the master server at debug level", + "full_action": "This error is internal. If the problem persists, please call\nNetBackup support for resolution.\nCheck the following logs:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3.\n■ The bptm legacy log from the media server, with VERBOSE=5." }, "2006": { "code": 2006, - "desc": "NDMP credentials estão não defined in EMM.", - "first_action": "If o job uses um NDMP dispositivo, verifique que o mídia", - "full_action": "If o job uses um NDMP dispositivo, verifique que o mídia\nservidor has NDMP credentials que estão configurado para o filer." + "desc": "NDMP credentials are not defined in EMM.", + "first_action": "If the job uses an NDMP device, verify that the media", + "full_action": "If the job uses an NDMP device, verify that the media\nserver has NDMP credentials that are configured for the filer." }, "2007": { "code": 2007, - "desc": "Armazenamento unidade está não compatible com requesting job", - "first_action": "Catalog backups estão directed to shared disco armazenamento units.", - "full_action": "Um job tries to run on um mídia servidor que está executando um\nolder version de NetBackup. O job may require um recurso que está não disponível on\no mídia servidor being solicitado. Verifique que o armazenamento unidade type e o mídia\nservidor que o policy e armazenamento unidade call fora support o recurso.\nThis erro can occur when o policy being run está não compatible com o armazenamento\nunits solicitado por o policy:\n■ Catalog backups estão directed to shared disco armazenamento units.\n■ Multiplexed jobs estão directed to armazenamento units que do não have o multiplex\nrecurso configurado.\n■ NDMP backup policies estão directed to non-NDMP armazenamento units." + "desc": "Storage unit is not compatible with requesting job", + "first_action": "Catalog backups are directed to shared disk storage units.", + "full_action": "A job tries to run on a media server that is running an\nolder version of NetBackup. The job may require a feature that is not available on\nthe media server being requested. Verify that the storage unit type and the media\nserver that the policy and storage unit call out support the feature.\nThis error can occur when the policy being run is not compatible with the storage\nunits requested by the policy:\n■ Catalog backups are directed to shared disk storage units.\n■ Multiplexed jobs are directed to storage units that do not have the multiplex\nfeature configured.\n■ NDMP backup policies are directed to non-NDMP storage units." }, "2008": { "code": 2008, - "desc": "Todos compatible drive paths estão down", - "first_action": "Verifique que ltid está executando on o requerido mídia servidor,", - "full_action": "Verifique que ltid está executando on o requerido mídia servidor,\ne que o mídia servidor está active para tape. Usando um dispositivo monitor, bring up o\ndrive paths if they estão down. If o drives estão downed again, clean o drives." + "desc": "All compatible drive paths are down", + "first_action": "Verify that ltid is running on the required media server,", + "full_action": "Verify that ltid is running on the required media server,\nand that the media server is active for tape. Using a device monitor, bring up the\ndrive paths if they are down. If the drives are downed again, clean the drives." }, "2009": { "code": 2009, - "desc": "Todos compatible drive paths estão down but mídia está disponível", - "first_action": "Verifique que ltid está executando on o requerido mídia servidor,", - "full_action": "Verifique que ltid está executando on o requerido mídia servidor,\ne que o mídia servidor está active para tape. Usando um dispositivo monitor, bring up o\ndrive paths if they estão down. If o drives estão downed again, clean o drives." + "desc": "All compatible drive paths are down but media is available", + "first_action": "Verify that ltid is running on the required media server,", + "full_action": "Verify that ltid is running on the required media server,\nand that the media server is active for tape. Using a device monitor, bring up the\ndrive paths if they are down. If the drives are downed again, clean the drives." }, "2010": { "code": 2010, - "desc": "Job type está inválido", - "first_action": "O mds unified logging arquivos (OID 143) from o master servidor at debug level", - "full_action": "This erro está internal. If o problema persists, por favor call\nNetBackup support para resolution.\nVerifique o seguinte logs:\n■ O mds unified logging arquivos (OID 143) from o master servidor at debug level\n2.\n■ O nbrb unified logging arquivos (OID 118) from o master servidor at debug level\n3." + "desc": "Job type is invalid", + "first_action": "The mds unified logging files (OID 143) from the master server at debug level", + "full_action": "This error is internal. If the problem persists, please call\nNetBackup support for resolution.\nCheck the following logs:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3." }, "2011": { "code": 2011, - "desc": "O mídia servidor reported um system erro", - "first_action": "O mds unified logging arquivos (OID 143) from o master servidor at debug level", - "full_action": "This erro está internal. If o problema persists, por favor call\nNetBackup support para resolution.\nVerifique o seguinte logs:\n■ O mds unified logging arquivos (OID 143) from o master servidor at debug level\n2.\n■ O nbrb unified logging arquivos (OID 118) from o master servidor at debug level\n3." + "desc": "The media server reported a system error", + "first_action": "The mds unified logging files (OID 143) from the master server at debug level", + "full_action": "This error is internal. If the problem persists, please call\nNetBackup support for resolution.\nCheck the following logs:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3." }, "2012": { "code": 2012, - "desc": "Mídia has conflicts in EMM", - "first_action": "O mídia está marked como having conflicts. O upgrade", - "full_action": "O mídia está marked como having conflicts. O upgrade\nfrom NetBackup 5.x has found multiple volume databases onde two tapes in\ndifferent volume databases have o same mídia ID. This erro está internal. If o\nproblema persists, por favor call NetBackup support para resolution." + "desc": "Media has conflicts in EMM", + "first_action": "The media is marked as having conflicts. The upgrade", + "full_action": "The media is marked as having conflicts. The upgrade\nfrom NetBackup 5.x has found multiple volume databases where two tapes in\ndifferent volume databases have the same media ID. This error is internal. If the\nproblem persists, please call NetBackup support for resolution." }, "2013": { "code": 2013, - "desc": "Erro record insert falhou", - "first_action": "O mds unified logging arquivos (OID 143) from o master servidor at debug level", - "full_action": "This erro está internal. If o problema persists, por favor call\nNetBackup support para resolution.\nVerifique o seguinte logs:\n■ O mds unified logging arquivos (OID 143) from o master servidor at debug level\n2.\n■ O nbrb unified logging arquivos (OID 118) from o master servidor at debug level\n3." + "desc": "Error record insert failed", + "first_action": "The mds unified logging files (OID 143) from the master server at debug level", + "full_action": "This error is internal. If the problem persists, please call\nNetBackup support for resolution.\nCheck the following logs:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3." }, "2014": { "code": 2014, - "desc": "Mídia está não assigned", - "first_action": "O mds unified logging arquivos (OID 143) from o master servidor at debug level", - "full_action": "Verifique que o job solicitado o desired mídia. Para\nexample,ifyouwanttolistcontentsofthemedia,makesurethatyouhavespecified\no correct mídia ID.\nVerifique o seguinte logs:\n■ O mds unified logging arquivos (OID 143) from o master servidor at debug level\n2.\n■ O nbrb unified logging arquivos (OID 118) from o master servidor at debug level\n3." + "desc": "Media is not assigned", + "first_action": "The mds unified logging files (OID 143) from the master server at debug level", + "full_action": "Verify that the job requested the desired media. For\nexample,ifyouwanttolistcontentsofthemedia,makesurethatyouhavespecified\nthe correct media ID.\nCheck the following logs:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3." }, "2015": { "code": 2015, - "desc": "Mídia está expired", - "first_action": "O mds unified logging arquivos (OID 143) from o master servidor at debug level", - "full_action": "Make sure que non-expired mídia está disponível para o job.\nVerifique o seguinte logs:\n■ O mds unified logging arquivos (OID 143) from o master servidor at debug level\n2.\n■ O nbrb unified logging arquivos (OID 118) from o master servidor at debug level\n3." + "desc": "Media is expired", + "first_action": "The mds unified logging files (OID 143) from the master server at debug level", + "full_action": "Make sure that non-expired media is available for the job.\nCheck the following logs:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3." }, "2016": { "code": 2016, - "desc": "Mídia está assigned to another servidor", - "first_action": "O mds unified logging arquivos (OID 143) from o master servidor at debug level", - "full_action": "Verifique o seguinte logs:\n■ O mds unified logging arquivos (OID 143) from o master servidor at debug level\n2.\n■ O nbrb unified logging arquivos (OID 118) from o master servidor at debug level\n3." + "desc": "Media is assigned to another server", + "first_action": "The mds unified logging files (OID 143) from the master server at debug level", + "full_action": "Check the following logs:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3." }, "2017": { "code": 2017, - "desc": "Mídia needs to be unmounted from um drive", + "desc": "Media needs to be unmounted from a drive", "first_action": "Identifythemediathatis requestedby thejobthatreturns", - "full_action": "Identifythemediathatis requestedby thejobthatreturns\nthis erro. If it está used por another job, wait para que job to complete." + "full_action": "Identifythemediathatis requestedby thejobthatreturns\nthis error. If it is used by another job, wait for that job to complete." }, "2018": { "code": 2018, - "desc": "Number de cleanings está inválido", + "desc": "Number of cleanings is invalid", "first_action": "OntheChangeMediascreen,setthenumberofcleanings", - "full_action": "OntheChangeMediascreen,setthenumberofcleanings\nremaining para o cleaning mídia to um number greater than ou equal to zero (0)." + "full_action": "OntheChangeMediascreen,setthenumberofcleanings\nremaining for the cleaning media to a number greater than or equal to zero (0)." }, "2019": { "code": 2019, - "desc": "Mídia está in um drive que está não configurado on local system", - "first_action": "If drive paths estão down, identify o mídia servidor que está", - "full_action": "If drive paths estão down, identify o mídia servidor que está\nconfigurado para use por o armazenamento unidade, e bring up o drive caminho to que mídia\nservidor." + "desc": "Media is in a drive that is not configured on local system", + "first_action": "If drive paths are down, identify the media server that is", + "full_action": "If drive paths are down, identify the media server that is\nconfigured for use by the storage unit, and bring up the drive path to that media\nserver." }, "2020": { "code": 2020, - "desc": "Robotic library está down on servidor", - "first_action": "Verifique que o mídia servidor que está requerido para this", - "full_action": "Verifique que o mídia servidor que está requerido para this\nallocation está executando, e verifique que ltid está up on que mídia servidor." + "desc": "Robotic library is down on server", + "first_action": "Verify that the media server that is required for this", + "full_action": "Verify that the media server that is required for this\nallocation is running, and verify that ltid is up on that media server." }, "2021": { "code": 2021, - "desc": "Allocation record insert falhou", - "first_action": "O mds unified logging arquivos (OID 143) from o master servidor at debug level", - "full_action": "This erro está internal. Verifique o seguinte logs:\n■ O mds unified logging arquivos (OID 143) from o master servidor at debug level\n2.\n■ O nbrb unified logging arquivos (OID 118) from o master servidor at debug level\n3." + "desc": "Allocation record insert failed", + "first_action": "The mds unified logging files (OID 143) from the master server at debug level", + "full_action": "This error is internal. Check the following logs:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3." }, "2022": { "code": 2022, - "desc": "Allocation status record insert falhou", - "first_action": "O mds unified logging arquivos (OID 143) from o master servidor at debug level", - "full_action": "This erro está internal. Verifique o seguinte logs to help\nidentify o problema:\n■ O mds unified logging arquivos (OID 143) from o master servidor at debug level\n2.\n■ O nbrb unified logging arquivos (OID 118) from o master servidor at debug level\n3." + "desc": "Allocation status record insert failed", + "first_action": "The mds unified logging files (OID 143) from the master server at debug level", + "full_action": "This error is internal. Check the following logs to help\nidentify the problem:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3." }, "2023": { "code": 2023, - "desc": "Allocation identifier está não known to EMM", - "first_action": "O mds unified logging arquivos (OID 143) from o master servidor at debug level", - "full_action": "This erro está internal. Verifique o seguinte logs to help\nidentify o problema:\n■ O mds unified logging arquivos (OID 143) from o master servidor at debug level\n2.\n■ O nbrb unified logging arquivos (OID 118) from o master servidor at debug level\n3." + "desc": "Allocation identifier is not known to EMM", + "first_action": "The mds unified logging files (OID 143) from the master server at debug level", + "full_action": "This error is internal. Check the following logs to help\nidentify the problem:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3." }, "2024": { "code": 2024, - "desc": "Allocation request update falhou NetBackup status codes 418 NetBackup status codes", - "first_action": "O mds unified logging arquivos (OID 143) from o master servidor at debug level", - "full_action": "This erro está internal. Verifique o seguinte logs to help\nidentify o problema:\n■ O mds unified logging arquivos (OID 143) from o master servidor at debug level\n2.\n■ O nbrb unified logging arquivos (OID 118) from o master servidor at debug level\n3." + "desc": "Allocation request update failed NetBackup status codes 418 NetBackup status codes", + "first_action": "The mds unified logging files (OID 143) from the master server at debug level", + "full_action": "This error is internal. Check the following logs to help\nidentify the problem:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3." }, "2025": { "code": 2025, - "desc": "Allocation request excluir falhou", - "first_action": "O mds unified logging arquivos (OID 143) from o master servidor at debug level", - "full_action": "This erro está internal. Verifique o seguinte logs to help\nidentify o problema:\n■ O mds unified logging arquivos (OID 143) from o master servidor at debug level\n2.\n■ O nbrb unified logging arquivos (OID 118) from o master servidor at debug level\n3." + "desc": "Allocation request delete failed", + "first_action": "The mds unified logging files (OID 143) from the master server at debug level", + "full_action": "This error is internal. Check the following logs to help\nidentify the problem:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3." }, "2026": { "code": 2026, - "desc": "Allocation status request excluir falhou", - "first_action": "O mds unified logging arquivos (OID 143) from o master servidor at debug level", - "full_action": "This erro está internal. Verifique o seguinte logs to help\nidentify o problema:\n■ O mds unified logging arquivos (OID 143) from o master servidor at debug level\n2.\n■ O nbrb unified logging arquivos (OID 118) from o master servidor at debug level\n3." + "desc": "Allocation status request delete failed", + "first_action": "The mds unified logging files (OID 143) from the master server at debug level", + "full_action": "This error is internal. Check the following logs to help\nidentify the problem:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3." }, "2027": { "code": 2027, - "desc": "Mídia servidor está não active", - "first_action": "Verifique que o mídia servidor que está requerido para this allocation está executando.", - "full_action": "Do one ou more de o seguinte:\n■ Verifique que o mídia servidor que está requerido para this allocation está executando.\n■ If this está um tape job, verifique que ltid está executando on o mídia servidor. If um mídia\nservidor has gone offline e returned online, um delay de several minutes may\noccur before um job can use que mídia servidor.\n■ Use o vmoprcmd comando to show o state de o mídia servidor. If o job está\ntrying to access um disco armazenamento unidade, verifique que o nbrmms process está executando\non o mídia servidor. If o job está trying to access um tape armazenamento unidade, verifique que\nltid está executando on o mídia servidor." + "desc": "Media server is not active", + "first_action": "Verify that the media server that is required for this allocation is running.", + "full_action": "Do one or more of the following:\n■ Verify that the media server that is required for this allocation is running.\n■ If this is a tape job, verify that ltid is running on the media server. If a media\nserver has gone offline and returned online, a delay of several minutes may\noccur before a job can use that media server.\n■ Use the vmoprcmd command to show the state of the media server. If the job is\ntrying to access a disk storage unit, verify that the nbrmms process is running\non the media server. If the job is trying to access a tape storage unit, verify that\nltid is running on the media server." }, "2028": { "code": 2028, - "desc": "Mídia está reserved", - "first_action": "O mds unified logging arquivos (OID 143) from o master servidor at debug level", - "full_action": "If multiple duplication jobs attempt to use o same tape\nmídia para ler, each job reserves o mídia. NetBackup should allow more than\none job to get um reservation para o tape mídia.\nThis erro está internal. Verifique o seguinte logs to help identify o problema:\n■ O mds unified logging arquivos (OID 143) from o master servidor at debug level\n2.\n■ O nbrb unified logging arquivos (OID 118) from o master servidor at debug level\n3." + "desc": "Media is reserved", + "first_action": "The mds unified logging files (OID 143) from the master server at debug level", + "full_action": "If multiple duplication jobs attempt to use the same tape\nmedia for read, each job reserves the media. NetBackup should allow more than\none job to get a reservation for the tape media.\nThis error is internal. Check the following logs to help identify the problem:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3." }, "2029": { "code": 2029, - "desc": "EMM banco de dados está inconsistent NetBackup status codes 420 NetBackup status codes", - "first_action": "O mds unified logging arquivos (OID 143) from o master servidor at debug level", - "full_action": "This erro está internal. Verifique o seguinte logs to help\nidentify o problema:\n■ O mds unified logging arquivos (OID 143) from o master servidor at debug level\n2.\n■ O nbrb unified logging arquivos (OID 118) from o master servidor at debug level\n3.\nRun thenbrbutil -resetallcommand togettheNetBackupallocationdatabase\nbackintoaconsistentstate.Notethatthiscommandcancelsalljobsincludingthose\nque estão currently executando." + "desc": "EMM database is inconsistent NetBackup status codes 420 NetBackup status codes", + "first_action": "The mds unified logging files (OID 143) from the master server at debug level", + "full_action": "This error is internal. Check the following logs to help\nidentify the problem:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3.\nRun thenbrbutil -resetallcommand togettheNetBackupallocationdatabase\nbackintoaconsistentstate.Notethatthiscommandcancelsalljobsincludingthose\nthat are currently running." }, "2030": { "code": 2030, - "desc": "Insufficient disco space ou high water mark would be excedido", - "first_action": "If there estão images on o disco que can be expired, expire them, e run", - "full_action": "Try o seguinte possible solutions:\n■ If there estão images on o disco que can be expired, expire them, e run\nnbdelete to excluir o images from disco.\n■ It may be que NetBackup creates disco images more quickly than they expire. If\nso, modifications to policies may be necessary to change o rate de image\ncreation e expiration para o disco.\n■ It may be helpful to lower o high water mark e low water mark para o disco\ngroup." + "desc": "Insufficient disk space or high water mark would be exceeded", + "first_action": "If there are images on the disk that can be expired, expire them, and run", + "full_action": "Try the following possible solutions:\n■ If there are images on the disk that can be expired, expire them, and run\nnbdelete to delete the images from disk.\n■ It may be that NetBackup creates disk images more quickly than they expire. If\nso, modifications to policies may be necessary to change the rate of image\ncreation and expiration for the disk.\n■ It may be helpful to lower the high water mark and low water mark for the disk\ngroup." }, "2031": { "code": 2031, - "desc": "Mídia está não defined in EMM", + "desc": "Media is not defined in EMM", "first_action": "Amediavolumethatisrequiredforarestorejobhasbeen", - "full_action": "Amediavolumethatisrequiredforarestorejobhasbeen\ndeleted from o EMM banco de dados. If o mídia está disponível, use bpimport to import\nit." + "full_action": "Amediavolumethatisrequiredforarestorejobhasbeen\ndeleted from the EMM database. If the media is available, use bpimport to import\nit." }, "2032": { "code": 2032, - "desc": "Mídia está in use according to EMM", - "first_action": "O mds unified logging arquivos (OID 143) from o master servidor at debug level", - "full_action": "This erro está internal. Verifique o seguinte logs to help\nidentify o problema:\n■ O mds unified logging arquivos (OID 143) from o master servidor at debug level\n2.\n■ O nbrb unified logging arquivos (OID 118) from o master servidor at debug level\n3." + "desc": "Media is in use according to EMM", + "first_action": "The mds unified logging files (OID 143) from the master server at debug level", + "full_action": "This error is internal. Check the following logs to help\nidentify the problem:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3." }, "2033": { "code": 2033, - "desc": "Mídia has been misplaced", - "first_action": "O mds unified logging arquivos (OID 143) from o master servidor at debug level", - "full_action": "Verifique que o mídia que está requerido por o job está in o\nproper robotic slot como shown por vmquery.\nIf o erro persists, o seguinte logs may be useful in understanding o problema:\n■ O mds unified logging arquivos (OID 143) from o master servidor at debug level\n2.\n■ O nbrb unified logging arquivos (OID 118) from o master servidor at debug level\n3.\n■ O verbose bptm logs on o mídia server(s) que access this mídia." + "desc": "Media has been misplaced", + "first_action": "The mds unified logging files (OID 143) from the master server at debug level", + "full_action": "Verify that the media that is required by the job is in the\nproper robotic slot as shown by vmquery.\nIf the error persists, the following logs may be useful in understanding the problem:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3.\n■ The verbose bptm logs on the media server(s) that access this media." }, "2034": { "code": 2034, - "desc": "Retry o allocation request later", - "first_action": "This erro should never appear como um job return status. In", - "full_action": "This erro should never appear como um job return status. In\nthemdsandnbrb vxullogs,itindicatesthatajobshouldqueuebecauseresources\nestão ocupado." + "desc": "Retry the allocation request later", + "first_action": "This error should never appear as a job return status. In", + "full_action": "This error should never appear as a job return status. In\nthemdsandnbrb vxullogs,itindicatesthatajobshouldqueuebecauseresources\nare busy." }, "2035": { "code": 2035, "desc": "Request needs to pend", - "first_action": "This erro should never appear como um job return status. In", - "full_action": "This erro should never appear como um job return status. In\nthemdsandnbrb vxullogs,itindicatesthatajobshouldpostarequestforoperator\nintervention to o NetBackup dispositivo monitor." + "first_action": "This error should never appear as a job return status. In", + "full_action": "This error should never appear as a job return status. In\nthemdsandnbrb vxullogs,itindicatesthatajobshouldpostarequestforoperator\nintervention to the NetBackup device monitor." }, "2036": { "code": 2036, - "desc": "Drive está in um robotic library que está up", - "first_action": "Um request para non-robotic mídia may have caused um", - "full_action": "Um request para non-robotic mídia may have caused um\npending request in o dispositivo monitor, e o operator has assigned o request\nto um drive que está não um standalone drive. This erro está não fatal. O request will pend\nagain in o NetBackup dispositivo monitor. Assign o pending mount to um standalone\ndrive ou to um drive que está in AVR mode (non-robotic)." + "desc": "Drive is in a robotic library that is up", + "first_action": "A request for non-robotic media may have caused a", + "full_action": "A request for non-robotic media may have caused a\npending request in the device monitor, and the operator has assigned the request\nto a drive that is not a standalone drive. This error is not fatal. The request will pend\nagain in the NetBackup device monitor. Assign the pending mount to a standalone\ndrive or to a drive that is in AVR mode (non-robotic)." }, "2037": { "code": 2037, - "desc": "Drive está não ready", + "desc": "Drive is not ready", "first_action": "Thiserrormayoccurwhenarequestfornon-roboticmedia", - "full_action": "Thiserrormayoccurwhenarequestfornon-roboticmedia\nhadcausedapendingrequestinthedevicemonitor,andtheoperatorhasassigned\no request to um drive que está não in um ready state. This erro está não um fatal erro. O\nrequest will pend again in o NetBackup dispositivo monitor. Verifique que requerido tape\nestá in o drive it está assigned to, e que o drive ready light has come on. It may\ntake some time para o drive to become ready after o tape has been inserted. If\no drive never goes to um ready state after um tape has been inserted, there may be\num problema com o drive." + "full_action": "Thiserrormayoccurwhenarequestfornon-roboticmedia\nhadcausedapendingrequestinthedevicemonitor,andtheoperatorhasassigned\nthe request to a drive that is not in a ready state. This error is not a fatal error. The\nrequest will pend again in the NetBackup device monitor. Verify that required tape\nis in the drive it is assigned to, and that the drive ready light has come on. It may\ntake some time for the drive to become ready after the tape has been inserted. If\nthe drive never goes to a ready state after a tape has been inserted, there may be\na problem with the drive." }, "2038": { "code": 2038, - "desc": "Mídia loaded in drive está não write-enabled", - "first_action": "This está não um fatal erro. O request will pend again in o", - "full_action": "This está não um fatal erro. O request will pend again in o\nNetBackup dispositivo monitor. If you estão sure que it está OK to gravar on this tape, verifique\nque o requerido tape has its gravar enable switch set to allow gravar." + "desc": "Media loaded in drive is not write-enabled", + "first_action": "This is not a fatal error. The request will pend again in the", + "full_action": "This is not a fatal error. The request will pend again in the\nNetBackup device monitor. If you are sure that it is OK to write on this tape, verify\nthat the required tape has its write enable switch set to allow write." }, "2039": { "code": 2039, "desc": "SCSI reservation conflict detected", - "first_action": "This erro should never occur at job resource allocation", - "full_action": "This erro should never occur at job resource allocation\ntime, but may occur during i/o para um tape job. O verbose bptm logs on o mídia\nservidor may be useful in understanding o problema." + "first_action": "This error should never occur at job resource allocation", + "full_action": "This error should never occur at job resource allocation\ntime, but may occur during i/o for a tape job. The verbose bptm logs on the media\nserver may be useful in understanding the problem." }, "2040": { "code": 2040, - "desc": "Maximum job count has been reached para o armazenamento unidade", - "first_action": "Target um different armazenamento unidade com one de o copies, ou", - "full_action": "Target um different armazenamento unidade com one de o copies, ou\naumentar o maximum job count para o armazenamento unidade." + "desc": "Maximum job count has been reached for the storage unit", + "first_action": "Target a different storage unit with one of the copies, or", + "full_action": "Target a different storage unit with one of the copies, or\nincrease the maximum job count for the storage unit." }, "2041": { "code": 2041, - "desc": "Armazenamento unidade está down", - "first_action": "Run o bperror -disco comando to indicate por que o", - "full_action": "Run o bperror -disco comando to indicate por que o\ndisco está considered down." + "desc": "Storage unit is down", + "first_action": "Run the bperror -disk command to indicate why the", + "full_action": "Run the bperror -disk command to indicate why the\ndisk is considered down." }, "2042": { "code": 2042, "desc": "Density mismatch detected", - "first_action": "Restauração o jobs request tape mídia por mídia ID density.", - "full_action": "Restauração o jobs request tape mídia por mídia ID density.\nIf o solicitado density does não match o configurado density para o mídia, it\nnão é possível be allocated." + "first_action": "Restore the jobs request tape media by media ID density.", + "full_action": "Restore the jobs request tape media by media ID density.\nIf the requested density does not match the configured density for the media, it\ncannot be allocated." }, "2043": { "code": 2043, - "desc": "Solicitado slot está vazio", - "first_action": "O robot may need to be inventoried.", - "full_action": "O robot may need to be inventoried." + "desc": "Requested slot is empty", + "first_action": "The robot may need to be inventoried.", + "full_action": "The robot may need to be inventoried." }, "2044": { "code": 2044, - "desc": "Mídia está assigned to another application", + "desc": "Media is assigned to another application", "first_action": "Verifythatthemediathatisrequiredforthejobisassigned", "full_action": "Verifythatthemediathatisrequiredforthejobisassigned\nto NetBackup." }, "2045": { "code": 2045, - "desc": "Armazenamento unidade está disabled since max job count está less than 1", + "desc": "Storage unit is disabled since max job count is less than 1", "first_action": "Increasethemaximumjobcount(ormaximumconcurrent", - "full_action": "Increasethemaximumjobcount(ormaximumconcurrent\ndrive count) to um value greater than 0." + "full_action": "Increasethemaximumjobcount(ormaximumconcurrent\ndrive count) to a value greater than 0." }, "2046": { "code": 2046, - "desc": "Mídia está unmountable", - "first_action": "Clean o drives in o media's robot. Determinar if qualquer de", - "full_action": "Clean o drives in o media's robot. Determinar if qualquer de\no mídia está bad." + "desc": "Media is unmountable", + "first_action": "Clean the drives in the media's robot. Determine if any of", + "full_action": "Clean the drives in the media's robot. Determine if any of\nthe media is bad." }, "2047": { "code": 2047, - "desc": "Mídia está gravar protected", - "first_action": "Make sure que mídia in o scratch pool está não gravar", - "full_action": "Make sure que mídia in o scratch pool está não gravar\nprotected." + "desc": "Media is write protected", + "first_action": "Make sure that media in the scratch pool is not write", + "full_action": "Make sure that media in the scratch pool is not write\nprotected." }, "2048": { "code": 2048, - "desc": "Mídia está in use por o ACS robotic library", + "desc": "Media is in use by the ACS robotic library", "first_action": "Makesurethattherequiredmediaisnotinusebyanother", "full_action": "Makesurethattherequiredmediaisnotinusebyanother\napplication." }, "2049": { "code": 2049, - "desc": "Mídia não found in o ACS robotic library", + "desc": "Media not found in the ACS robotic library", "first_action": "Make sure thattherequiredmediais availablein theACS", - "full_action": "Make sure thattherequiredmediais availablein theACS\nrobot.\nFormoreinformation,seethesectiononconfiguringACSLSrobotsintheNetBackup\nDispositivo Configuration Guide." + "full_action": "Make sure thattherequiredmediais availablein theACS\nrobot.\nFormoreinformation,seethesectiononconfiguringACSLSrobotsintheNetBackup\nDevice Configuration Guide." }, "2050": { "code": 2050, - "desc": "ACS mídia has um unreadable external label", - "first_action": "Correct o barcode label problema para this mídia.", - "full_action": "Correct o barcode label problema para this mídia.\nFormoreinformation,seethesectiononconfiguringACSLSrobotsintheNetBackup\nDispositivo Configuration Guide." + "desc": "ACS media has an unreadable external label", + "first_action": "Correct the barcode label problem for this media.", + "full_action": "Correct the barcode label problem for this media.\nFormoreinformation,seethesectiononconfiguringACSLSrobotsintheNetBackup\nDevice Configuration Guide." }, "2051": { "code": 2051, - "desc": "ACS mídia está não in o drive's domain", - "first_action": "Verifique que o robot que contains o requerido mídia está", - "full_action": "Verifique que o robot que contains o requerido mídia está\naccessible to um NetBackup mídia servidor.\nPara more informação, refer to o section on configuring ACSLS robots in o\nNetBackup Dispositivo Configuration Guide." + "desc": "ACS media is not in the drive's domain", + "first_action": "Verify that the robot that contains the required media is", + "full_action": "Verify that the robot that contains the required media is\naccessible to a NetBackup media server.\nFor more information, refer to the section on configuring ACSLS robots in the\nNetBackup Device Configuration Guide." }, "2052": { "code": 2052, - "desc": "Um ACS Library Armazenamento Module (LSM) está offline", - "first_action": "Bring o ACS LSM online.", - "full_action": "Bring o ACS LSM online.\nFormoreinformation,seethesectiononconfiguringACSLSrobotsintheNetBackup\nDispositivo Configuration Guide." + "desc": "An ACS Library Storage Module (LSM) is offline", + "first_action": "Bring the ACS LSM online.", + "full_action": "Bring the ACS LSM online.\nFormoreinformation,seethesectiononconfiguringACSLSrobotsintheNetBackup\nDevice Configuration Guide." }, "2053": { "code": 2053, - "desc": "Mídia está in um inaccessible drive", + "desc": "Media is in an inaccessible drive", "first_action": "Locatethemediaandcorrecttheproblemthathascaused", - "full_action": "Locatethemediaandcorrecttheproblemthathascaused\no drive ou drive caminho to be down." + "full_action": "Locatethemediaandcorrecttheproblemthathascaused\nthe drive or drive path to be down." }, "2054": { "code": 2054, - "desc": "Mídia está in um drive que está currently in um DOWN state", + "desc": "Media is in a drive that is currently in a DOWN state", "first_action": "Locatethemediaandcorrecttheproblemthathascaused", - "full_action": "Locatethemediaandcorrecttheproblemthathascaused\no drive ou drive caminho to be down." + "full_action": "Locatethemediaandcorrecttheproblemthathascaused\nthe drive or drive path to be down." }, "2055": { "code": 2055, - "desc": "ACS physical drive está não disponível", - "first_action": "Locate e install um ACS drive.", - "full_action": "Locate e install um ACS drive." + "desc": "ACS physical drive is not available", + "first_action": "Locate and install an ACS drive.", + "full_action": "Locate and install an ACS drive." }, "2056": { "code": 2056, - "desc": "O arquivo name used para o mount request already exists", + "desc": "The file name used for the mount request already exists", "first_action": "Specifyadifferentfilenamefortpreq,orrunthetpunmount", - "full_action": "Specifyadifferentfilenamefortpreq,orrunthetpunmount\ncomando para o mídia which has been loaded usando tpreq com o conflicting arquivo\nname." + "full_action": "Specifyadifferentfilenamefortpreq,orrunthetpunmount\ncommand for the media which has been loaded using tpreq with the conflicting file\nname." }, "2057": { "code": 2057, - "desc": "O scan host de o drive está não active", - "first_action": "If o problema persists, restart o NetBackup mídia", - "full_action": "If o problema persists, restart o NetBackup mídia\nservers que have paths to this drive." + "desc": "The scan host of the drive is not active", + "first_action": "If the problem persists, restart the NetBackup media", + "full_action": "If the problem persists, restart the NetBackup media\nservers that have paths to this drive." }, "2058": { "code": 2058, - "desc": "LTID needs to be restarted on mídia servers before o dispositivo can be used", - "first_action": "When o mídia servidor está não in um ocupado state, stop e", - "full_action": "When o mídia servidor está não in um ocupado state, stop e\nrestart ltid on que mídia servidor." + "desc": "LTID needs to be restarted on media servers before the device can be used", + "first_action": "When the media server is not in a busy state, stop and", + "full_action": "When the media server is not in a busy state, stop and\nrestart ltid on that media server." }, "2059": { "code": 2059, - "desc": "O robotic library está não disponível", - "first_action": "Verifique que o robot que o jobs require está properly", - "full_action": "Verifique que o robot que o jobs require está properly\nconfigurado. If o erro persists, o seguinte logs may be useful in understanding\ntheproblem:Themdsunifiedloggingfiles(OID143)fromthemasterserveratdebug\nlevel 2." + "desc": "The robotic library is not available", + "first_action": "Verify that the robot that the jobs require is properly", + "full_action": "Verify that the robot that the jobs require is properly\nconfigured. If the error persists, the following logs may be useful in understanding\ntheproblem:Themdsunifiedloggingfiles(OID143)fromthemasterserveratdebug\nlevel 2." }, "2060": { "code": 2060, - "desc": "Mídia needs to be rewound ou unmounted from um drive", - "first_action": "Não applicable.", - "full_action": "Não applicable." + "desc": "Media needs to be rewound or unmounted from a drive", + "first_action": "Not applicable.", + "full_action": "Not applicable." }, "2061": { "code": 2061, - "desc": "O host está não um active node de um cluster", - "first_action": "Restart o falhou job.", - "full_action": "Restart o falhou job." + "desc": "The host is not an active node of a cluster", + "first_action": "Restart the failed job.", + "full_action": "Restart the failed job." }, "2062": { "code": 2062, - "desc": "Throttled job count has been reached para o armazenamento unidade", - "first_action": "Não disponível", - "full_action": "Não disponível" + "desc": "Throttled job count has been reached for the storage unit", + "first_action": "Not available", + "full_action": "Not available" }, "2063": { "code": 2063, - "desc": "Servidor está não licensed para o Remote Cliente Option NetBackup status codes 430 NetBackup status codes", - "first_action": "Backup this cliente on um mídia servidor que está licensed to", - "full_action": "Backup this cliente on um mídia servidor que está licensed to\ndo so. Verifique que o mídia servidor has connectivity to o master servidor when\nadding its licenses." + "desc": "Server is not licensed for the Remote Client Option NetBackup status codes 430 NetBackup status codes", + "first_action": "Backup this client on a media server that is licensed to", + "full_action": "Backup this client on a media server that is licensed to\ndo so. Verify that the media server has connectivity to the master server when\nadding its licenses." }, "2064": { "code": 2064, - "desc": "Job history indicates que não mídia está disponível", - "first_action": "Make sure que mídia está disponível para o armazenamento unidade. If", - "full_action": "Make sure que mídia está disponível para o armazenamento unidade. If\nnecessary, upgrade o software on o mídia servidor. Add mídia if necessary. If\nmídia está disponível, wait 12 hours until o armazenamento unidade can be used again. To make\no armazenamento unidade immediately usable, run o seguinte comando on o master\nservidor to release o hold:\nnbrbutil -releaseAllocHolds" + "desc": "Job history indicates that no media is available", + "first_action": "Make sure that media is available for the storage unit. If", + "full_action": "Make sure that media is available for the storage unit. If\nnecessary, upgrade the software on the media server. Add media if necessary. If\nmedia is available, wait 12 hours until the storage unit can be used again. To make\nthe storage unit immediately usable, run the following command on the master\nserver to release the hold:\nnbrbutil -releaseAllocHolds" }, "2065": { "code": 2065, - "desc": "Job history indicates que não drive está disponível", - "first_action": "Upgrade o mídia servidor software. Make sure todos de o", - "full_action": "Upgrade o mídia servidor software. Make sure todos de o\ndrives in o armazenamento unidade estão up e disponível para use. Clean todos drives que need\ncleaning." + "desc": "Job history indicates that no drive is available", + "first_action": "Upgrade the media server software. Make sure all of the", + "full_action": "Upgrade the media server software. Make sure all of the\ndrives in the storage unit are up and available for use. Clean all drives that need\ncleaning." }, "2066": { "code": 2066, - "desc": "Disco pool não found", - "first_action": "Verifique que o armazenamento unidade que this job uses está configurado", - "full_action": "Verifique que o armazenamento unidade que this job uses está configurado\npara use com um properly configurado disco pool." + "desc": "Disk pool not found", + "first_action": "Verify that the storage unit that this job uses is configured", + "full_action": "Verify that the storage unit that this job uses is configured\nfor use with a properly configured disk pool." }, "2067": { "code": 2067, - "desc": "Disco volume não found", - "first_action": "Verifythatthedisk storagethatthisjob uses está configurado", - "full_action": "Verifythatthedisk storagethatthisjob uses está configurado\npara use com um disco pool que has volumes configurado. Para um ler job, verifique que o\nvolume que está requerido para reading exists in o nbemm banco de dados." + "desc": "Disk volume not found", + "first_action": "Verifythatthedisk storagethatthisjob uses is configured", + "full_action": "Verifythatthedisk storagethatthisjob uses is configured\nfor use with a disk pool that has volumes configured. For a read job, verify that the\nvolume that is required for reading exists in the nbemm database." }, "2068": { "code": 2068, - "desc": "Disco volume mount point não found", - "first_action": "Verifique que o configuration está correct para o disco group", - "full_action": "Verifique que o configuration está correct para o disco group\ne para o disco volumes in o disco group." + "desc": "Disk volume mount point not found", + "first_action": "Verify that the configuration is correct for the disk group", + "full_action": "Verify that the configuration is correct for the disk group\nand for the disk volumes in the disk group." }, "2069": { "code": 2069, - "desc": "Disco volume mount point record insert falhou", - "first_action": "O mds unified logging arquivos (OID 143) from o master servidor at debug level", - "full_action": "This erro está internal. If o problema persists, por favor call\nNetBackup support para resolution. Verifique o seguinte logs to help identify o\nproblema:\n■ O mds unified logging arquivos (OID 143) from o master servidor at debug level\n2.\n■ O nbrb unified logging arquivos (OID 118) from o master servidor at debug level\n3." + "desc": "Disk volume mount point record insert failed", + "first_action": "The mds unified logging files (OID 143) from the master server at debug level", + "full_action": "This error is internal. If the problem persists, please call\nNetBackup support for resolution. Check the following logs to help identify the\nproblem:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3." }, "2070": { "code": 2070, - "desc": "O specified mount caminho will não fit in o allocated space", - "first_action": "O mds unified logging arquivos (OID 143) from o master servidor at debug level", - "full_action": "This erro está internal. If o problema persists, por favor call\nNetBackup support para resolution. Verifique o seguinte logs to help identify o\nproblema:\n■ O mds unified logging arquivos (OID 143) from o master servidor at debug level\n2.\n■ O nbrb unified logging arquivos (OID 118) from o master servidor at debug level\n3." + "desc": "The specified mount path will not fit in the allocated space", + "first_action": "The mds unified logging files (OID 143) from the master server at debug level", + "full_action": "This error is internal. If the problem persists, please call\nNetBackup support for resolution. Check the following logs to help identify the\nproblem:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3." }, "2071": { "code": 2071, - "desc": "Não foi possível to find qualquer armazenamento servers para o request", - "first_action": "Verifique que o armazenamento servers serving o disco group que", - "full_action": "Verifique que o armazenamento servers serving o disco group que\no job requires estão configurado e enabled. Verifique que they estão in um UP state." + "desc": "Unable to find any storage servers for the request", + "first_action": "Verify that the storage servers serving the disk group that", + "full_action": "Verify that the storage servers serving the disk group that\nthe job requires are configured and enabled. Verify that they are in an UP state." }, "2072": { "code": 2072, - "desc": "Inválido operation on static mount point", - "first_action": "O mds unified logging arquivos (OID 143) from o master servidor at debug level", - "full_action": "This erro está internal. If o problema persists, por favor call\nNetBackup support para resolution. Verifique o seguinte logs to help identify o\nproblema:\n■ O mds unified logging arquivos (OID 143) from o master servidor at debug level\n2.\n■ O nbrb unified logging arquivos (OID 118) from o master servidor at debug level\n3." + "desc": "Invalid operation on static mount point", + "first_action": "The mds unified logging files (OID 143) from the master server at debug level", + "full_action": "This error is internal. If the problem persists, please call\nNetBackup support for resolution. Check the following logs to help identify the\nproblem:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3." }, "2073": { "code": 2073, - "desc": "Disco pool está down", - "first_action": "Run o bperror -disco comando to determinar por que o", - "full_action": "Run o bperror -disco comando to determinar por que o\ndiskpoolwasputintoaDOWNstate.Correcttheproblem,andusethenbdevconfig\ncomando to return o disco pool to um UP state." + "desc": "Disk pool is down", + "first_action": "Run the bperror -disk command to determine why the", + "full_action": "Run the bperror -disk command to determine why the\ndiskpoolwasputintoaDOWNstate.Correcttheproblem,andusethenbdevconfig\ncommand to return the disk pool to an UP state." }, "2074": { "code": 2074, - "desc": "Disco volume está down", - "first_action": "You may be able to veja por que o disco volume foi put into", - "full_action": "You may be able to veja por que o disco volume foi put into\num DOWN state por runningbperror -disco. Correct o problema, e use\nnbdevconfig to return o disco volume to um UP state." + "desc": "Disk volume is down", + "first_action": "You may be able to see why the disk volume was put into", + "full_action": "You may be able to see why the disk volume was put into\na DOWN state by runningbperror -disk. Correct the problem, and use\nnbdevconfig to return the disk volume to an UP state." }, "2075": { "code": 2075, - "desc": "Fibre Transport resources estão não disponível", - "first_action": "O mds unified logging arquivos (OID 143) from o master servidor at debug level", - "full_action": "Configure o job to switch to LAN transport if Fibre\nTransport está não disponível. Verifique que o job type being run está compatible com Fibre\nTransport. Usando nbdevquery, verifique que o Disco Pool being solicitado está enabled\npara use com Fibre Transport. Verifique que there estão Fibre Transport connections que\nareupbetweentheclientandmediaserverrequiredforthejob.Checkthefollowing\nlogs to help identify o problema:\n■ O mds unified logging arquivos (OID 143) from o master servidor at debug level\n2.\n■ O nbrb unified logging arquivos (OID 118) from o master servidor at debug level\n3." + "desc": "Fibre Transport resources are not available", + "first_action": "The mds unified logging files (OID 143) from the master server at debug level", + "full_action": "Configure the job to switch to LAN transport if Fibre\nTransport is not available. Verify that the job type being run is compatible with Fibre\nTransport. Using nbdevquery, verify that the Disk Pool being requested is enabled\nfor use with Fibre Transport. Verify that there are Fibre Transport connections that\nareupbetweentheclientandmediaserverrequiredforthejob.Checkthefollowing\nlogs to help identify the problem:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3." }, "2076": { "code": 2076, - "desc": "DSM returned um unexpected erro", - "first_action": "O mds unified logging arquivos (OID 143) from o master servidor at debug level", - "full_action": "This erro está internal. If o problema persists, por favor call\nNetBackup support para resolution. Verifique o seguinte logs to help identify o\nproblema:\n■ O mds unified logging arquivos (OID 143) from o master servidor at debug level\n2.\n■ O nbrb unified logging arquivos (OID 118) from o master servidor at debug level\n3." + "desc": "DSM returned an unexpected error", + "first_action": "The mds unified logging files (OID 143) from the master server at debug level", + "full_action": "This error is internal. If the problem persists, please call\nNetBackup support for resolution. Check the following logs to help identify the\nproblem:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3." }, "2078": { "code": 2078, "desc": "Themaximumnumberofmountsforthediskvolumehavebeenexceeded", - "first_action": "O mds unified logging arquivos (OID 143) from o master servidor at debug level", - "full_action": "This erro está internal. If o problema persists, por favor call\nNetBackup support para resolution. Verifique o seguinte logs to help identify o\nproblema:\n■ O mds unified logging arquivos (OID 143) from o master servidor at debug level\n2.\n■ O nbrb unified logging arquivos (OID 118) from o master servidor at debug level\n3." + "first_action": "The mds unified logging files (OID 143) from the master server at debug level", + "full_action": "This error is internal. If the problem persists, please call\nNetBackup support for resolution. Check the following logs to help identify the\nproblem:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3." }, "2079": { "code": 2079, - "desc": "DSM has detected que um inválido arquivo system está mounted on o volume", - "first_action": "Verifique que o disco volumes e their associated mount", - "full_action": "Verifique que o disco volumes e their associated mount\npoints que NetBackup uses estão não used por other applications." + "desc": "DSM has detected that an invalid file system is mounted on the volume", + "first_action": "Verify that the disk volumes and their associated mount", + "full_action": "Verify that the disk volumes and their associated mount\npoints that NetBackup uses are not used by other applications." }, "2080": { "code": 2080, - "desc": "Disco volume has não max writers count", - "first_action": "O mds unified logging arquivos (OID 143) from o master servidor at debug level", - "full_action": "Verifique proper disco configuration por usando nbdevquery.\nThis erro está internal. If o problema persists, por favor call NetBackup support para\nresolution. Verifique o seguinte logs to help identify o problema:\n■ O mds unified logging arquivos (OID 143) from o master servidor at debug level\n2.\n■ O nbrb unified logging arquivos (OID 118) from o master servidor at debug level\n3." + "desc": "Disk volume has no max writers count", + "first_action": "The mds unified logging files (OID 143) from the master server at debug level", + "full_action": "Verify proper disk configuration by using nbdevquery.\nThis error is internal. If the problem persists, please call NetBackup support for\nresolution. Check the following logs to help identify the problem:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3." }, "2081": { "code": 2081, - "desc": "Disco volume has não max readers count", - "first_action": "O mds unified logging arquivos (OID 143) from o master servidor at debug level", - "full_action": "Verifique o proper disco configuration por usando nbdevquery.\nThis erro está internal. If o problema persists, por favor call NetBackup support para\nresolution. Verifique o seguinte logs to help identify o problema:\n■ O mds unified logging arquivos (OID 143) from o master servidor at debug level\n2.\n■ O nbrb unified logging arquivos (OID 118) from o master servidor at debug level\n3." + "desc": "Disk volume has no max readers count", + "first_action": "The mds unified logging files (OID 143) from the master server at debug level", + "full_action": "Verify the proper disk configuration by using nbdevquery.\nThis error is internal. If the problem persists, please call NetBackup support for\nresolution. Check the following logs to help identify the problem:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3." }, "2082": { "code": 2082, - "desc": "O drive needs to be marked como disponível", - "first_action": "ReleaseMDS comando to release o allocation para o drive so it can be used.", - "full_action": "Run o nbrbutil -dump comando on o master servidor\nto show allocations para this job. If o problema persists, run o nbrbutil\n-releaseMDS comando to release o allocation para o drive so it can be used." + "desc": "The drive needs to be marked as available", + "first_action": "ReleaseMDS command to release the allocation for the drive so it can be used.", + "full_action": "Run the nbrbutil -dump command on the master server\nto show allocations for this job. If the problem persists, run the nbrbutil\n-releaseMDS command to release the allocation for the drive so it can be used." }, "2083": { "code": 2083, - "desc": "O mídia affinity group está não defined in EMM", - "first_action": "O mds unified logging arquivos (OID 143) from o master servidor at debug level", - "full_action": "This erro está internal. If o problema persists, verifique o\nseguinte logs to help identify o problema:\n■ O mds unified logging arquivos (OID 143) from o master servidor at debug level\n2.\n■ O nbrb unified logging arquivos (OID 118) from o master servidor at debug level\n3." + "desc": "The media affinity group is not defined in EMM", + "first_action": "The mds unified logging files (OID 143) from the master server at debug level", + "full_action": "This error is internal. If the problem persists, check the\nfollowing logs to help identify the problem:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3." }, "2084": { "code": 2084, - "desc": "Mídia affinity group record insert falhou", - "first_action": "O mds unified logging arquivos (OID 143) from o master servidor at debug level", - "full_action": "This erro está internal. If o problema persists, verifique o\nseguinte logs to help identify o problema:\n■ O mds unified logging arquivos (OID 143) from o master servidor at debug level\n2.\n■ O nbrb unified logging arquivos (OID 118) from o master servidor at debug level\n3." + "desc": "Media affinity group record insert failed", + "first_action": "The mds unified logging files (OID 143) from the master server at debug level", + "full_action": "This error is internal. If the problem persists, check the\nfollowing logs to help identify the problem:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3." }, "2085": { "code": 2085, - "desc": "Disco volume está não disponível", - "first_action": "Garanta que o disco group has disco volumes configurado.", - "full_action": "Garanta que o disco group has disco volumes configurado.\nUm multiple copy job não é possível target two copies para o same disco volume." + "desc": "Disk volume is not available", + "first_action": "Ensure that the disk group has disk volumes configured.", + "full_action": "Ensure that the disk group has disk volumes configured.\nA multiple copy job cannot target two copies for the same disk volume." }, "2086": { "code": 2086, - "desc": "Disco volume não é possível be used para more than one copy in o same job", - "first_action": "Use o nbdevquery -listdv comando to verifique thatthe", - "full_action": "Use o nbdevquery -listdv comando to verifique thatthe\nexpected disco volume está configurado. Para um multiple copy job, garanta que unique\neligible disco volumes exist para each copy. Um multiple copy job não é possível target two\ncopies para o same disco volume." + "desc": "Disk volume cannot be used for more than one copy in the same job", + "first_action": "Use the nbdevquery -listdv command to verify thatthe", + "full_action": "Use the nbdevquery -listdv command to verify thatthe\nexpected disk volume is configured. For a multiple copy job, ensure that unique\neligible disk volumes exist for each copy. A multiple copy job cannot target two\ncopies for the same disk volume." }, "2087": { "code": 2087, - "desc": "Mídia allocation would exceed maximum partially cheio mídia limite", - "first_action": "This erro may occur com um multiple copy job ou um", - "full_action": "This erro may occur com um multiple copy job ou um\nduplicationjob.Iftheproblempersists,youmayneedtoincreasemaximumpartially\ncheio mídia setting on o disco pool." + "desc": "Media allocation would exceed maximum partially full media limit", + "first_action": "This error may occur with a multiple copy job or a", + "full_action": "This error may occur with a multiple copy job or a\nduplicationjob.Iftheproblempersists,youmayneedtoincreasemaximumpartially\nfull media setting on the disk pool." }, "2088": { "code": 2088, - "desc": "Cleaning mídia está não disponível", - "first_action": "Add um cleaning volume to o robot containing o drive.", - "full_action": "Add um cleaning volume to o robot containing o drive." + "desc": "Cleaning media is not available", + "first_action": "Add a cleaning volume to the robot containing the drive.", + "full_action": "Add a cleaning volume to the robot containing the drive." }, "2089": { "code": 2089, - "desc": "FT cliente está não executando", - "first_action": "Verifique que o Private Branch Exchange (PBX) service está instalado e executando.", - "full_action": "Do one ou more de o seguinte:\n■ Verifique que o Private Branch Exchange (PBX) service está instalado e executando.\nRun o bpps -x comando to garanta que pbx_exchange está listed in o\nprocessos que estão executando.\n■ Verifique que o cliente está configurado como um SAN Cliente. Run o bpclntcmd\n-sanclient comando to return o current state de o SAN Cliente. Um response\nde 0 (zero) indicates que SAN Cliente está não configurado. Rerun o comando como\nbpclntcmd -sanclient 1.\n■ Verifique que o cliente está não also um mídia servidor, master servidor, ou EMM servidor.\nO SAN Cliente process runs apenas on um NetBackup cliente.\n■ VerifythatavalidlicensefortheSANClientfeatureresidesonthemasterserver.\nSAN Cliente está um separately licensed recurso which requires um key called \"SAN\nCliente\" on o master servidor.\n■ Verifique que não servidor entradas para o SAN Cliente exist on o NetBackup master\nserver.RemoveanySERVER=clientnameentryinthemasterserverfortheSAN\nCliente. If o master servidor has o SAN Cliente listed also como um servidor, it may\nshutdown o SAN Cliente.\n■ RestarttheSANClientservice.TheSANClientrestartswhentheserverreboots,\nbut does não automatically restart after you run o bpclntcmd comando. To\nstart o SAN Cliente service, run o cliente startup script ou use o Service\nManager in Windows.\nFormoreinformation,seetheTroubleshootingchapteroftheNetBackupSANClient\ne Fibre Transport Guide." + "desc": "FT client is not running", + "first_action": "Verify that the Private Branch Exchange (PBX) service is installed and running.", + "full_action": "Do one or more of the following:\n■ Verify that the Private Branch Exchange (PBX) service is installed and running.\nRun the bpps -x command to ensure that pbx_exchange is listed in the\nprocesses that are running.\n■ Verify that the client is configured as a SAN Client. Run the bpclntcmd\n-sanclient command to return the current state of the SAN Client. A response\nof 0 (zero) indicates that SAN Client is not configured. Rerun the command as\nbpclntcmd -sanclient 1.\n■ Verify that the client is not also a media server, master server, or EMM server.\nThe SAN Client process runs only on a NetBackup client.\n■ VerifythatavalidlicensefortheSANClientfeatureresidesonthemasterserver.\nSAN Client is a separately licensed feature which requires a key called \"SAN\nClient\" on the master server.\n■ Verify that no server entries for the SAN Client exist on the NetBackup master\nserver.RemoveanySERVER=clientnameentryinthemasterserverfortheSAN\nClient. If the master server has the SAN Client listed also as a server, it may\nshutdown the SAN Client.\n■ RestarttheSANClientservice.TheSANClientrestartswhentheserverreboots,\nbut does not automatically restart after you run the bpclntcmd command. To\nstart the SAN Client service, run the client startup script or use the Service\nManager in Windows.\nFormoreinformation,seetheTroubleshootingchapteroftheNetBackupSANClient\nand Fibre Transport Guide." }, "2090": { "code": 2090, - "desc": "FT cliente has não devices configurado NetBackup status codes 439 NetBackup status codes", - "first_action": "Verifique que Fibre Transport devices estão instalado on o", - "full_action": "Verifique que Fibre Transport devices estão instalado on o\ncliente.\nPara further informação, veja o Troubleshooting chapter de o NetBackup SAN\nCliente e Fibre Transport Guide." + "desc": "FT client has no devices configured NetBackup status codes 439 NetBackup status codes", + "first_action": "Verify that Fibre Transport devices are installed on the", + "full_action": "Verify that Fibre Transport devices are installed on the\nclient.\nFor further information, see the Troubleshooting chapter of the NetBackup SAN\nClient and Fibre Transport Guide." }, "2091": { "code": 2091, - "desc": "FT cliente devices estão offline", - "first_action": "Verifique que o Private Branch Exchange (PBX) service está instalado e executando.", - "full_action": "Do one ou more de o seguinte:\n■ Verifique que o Private Branch Exchange (PBX) service está instalado e executando.\nRun o bpps -x comando to garanta que pbx_exchange está listed in o\nprocessos que estão executando.\n■ Verifique que o cliente está configurado como um SAN Cliente. Run o bpclntcmd\n-sanclient comando to return o current state de o SAN Cliente. Um response\nde 0 (zero) indicates que SAN Cliente está não configurado. Rerun o comando como\nbpclntcmd -sanclient 1.\n■ Verifique que o cliente está não also um mídia servidor, master servidor, ou EMM servidor.\nO SAN Cliente process runs apenas on um NetBackup cliente.\n■ VerifythatavalidlicensefortheSANClientfeatureresidesonthemasterserver.\nSAN Cliente está um separately licensed recurso which requires um key called \"SAN\nCliente\" on o master servidor.\n■ Verifique que não servidor entradas para o SAN Cliente exist on o NetBackup master\nserver.RemoveanySERVER=clientnameentryinthemasterserverfortheSAN\nCliente. If o master servidor has o SAN Cliente also listed como um servidor, it may\nshutdown o SAN Cliente.\n■ RestarttheSANClientservice.TheSANClientrestartswhentheserverrestarts,\nbut does não automatically restart after you run o bpclntcmd comando. To\nstart o SAN Cliente service, run o cliente startup script ou use o Service\nManager in Windows.\nPara further informação, veja o Troubleshooting chapter de o NetBackup SAN\nCliente e Fibre Transport Guide." + "desc": "FT client devices are offline", + "first_action": "Verify that the Private Branch Exchange (PBX) service is installed and running.", + "full_action": "Do one or more of the following:\n■ Verify that the Private Branch Exchange (PBX) service is installed and running.\nRun the bpps -x command to ensure that pbx_exchange is listed in the\nprocesses that are running.\n■ Verify that the client is configured as a SAN Client. Run the bpclntcmd\n-sanclient command to return the current state of the SAN Client. A response\nof 0 (zero) indicates that SAN Client is not configured. Rerun the command as\nbpclntcmd -sanclient 1.\n■ Verify that the client is not also a media server, master server, or EMM server.\nThe SAN Client process runs only on a NetBackup client.\n■ VerifythatavalidlicensefortheSANClientfeatureresidesonthemasterserver.\nSAN Client is a separately licensed feature which requires a key called \"SAN\nClient\" on the master server.\n■ Verify that no server entries for the SAN Client exist on the NetBackup master\nserver.RemoveanySERVER=clientnameentryinthemasterserverfortheSAN\nClient. If the master server has the SAN Client also listed as a server, it may\nshutdown the SAN Client.\n■ RestarttheSANClientservice.TheSANClientrestartswhentheserverrestarts,\nbut does not automatically restart after you run the bpclntcmd command. To\nstart the SAN Client service, run the client startup script or use the Service\nManager in Windows.\nFor further information, see the Troubleshooting chapter of the NetBackup SAN\nClient and Fibre Transport Guide." }, "2092": { "code": 2092, - "desc": "FT servidor devices para cliente estão offline", - "first_action": "Verifique que marked QLogic Target ports exist in o servidor. O nbftsrvr e", - "full_action": "Do one de o seguinte:\n■ Verifique que marked QLogic Target ports exist in o servidor. O nbftsrvr e\nnbfdrv64 processos exit if o system has não ports disponível para Target Mode\nuse.\n■ VerifythatavalidlicensefortheSANClientfeatureresidesonthemasterserver.\nSAN Cliente está um separately licensed recurso que requires um key called \"SAN\nCliente\" on o master servidor. O Fibre Transport servidor performs um license\nverifique during startup.\n■ DetermineifarebootisrequiredfortheinstallationoftheFibreTransportserver.\nSolaris installations require que you reboot o mídia servidor after you install\nFibre Transport to load o Fibre Transport drivers on o marked target ports.\nIn addition, reboot o Linux servers if you choose to não unload o existing\nQLogic drivers during o installation de Fibre Transport.\nPara further informação, veja o Troubleshooting chapter de o NetBackup SAN\nCliente e Fibre Transport Guide." + "desc": "FT server devices for client are offline", + "first_action": "Verify that marked QLogic Target ports exist in the server. The nbftsrvr and", + "full_action": "Do one of the following:\n■ Verify that marked QLogic Target ports exist in the server. The nbftsrvr and\nnbfdrv64 processes exit if the system has no ports available for Target Mode\nuse.\n■ VerifythatavalidlicensefortheSANClientfeatureresidesonthemasterserver.\nSAN Client is a separately licensed feature that requires a key called \"SAN\nClient\" on the master server. The Fibre Transport server performs a license\ncheck during startup.\n■ DetermineifarebootisrequiredfortheinstallationoftheFibreTransportserver.\nSolaris installations require that you reboot the media server after you install\nFibre Transport to load the Fibre Transport drivers on the marked target ports.\nIn addition, reboot the Linux servers if you choose to not unload the existing\nQLogic drivers during the installation of Fibre Transport.\nFor further information, see the Troubleshooting chapter of the NetBackup SAN\nClient and Fibre Transport Guide." }, "2093": { "code": 2093, - "desc": "Não FT servers para this cliente estão executando", - "first_action": "Verifique que marked QLogic Target ports exist in o servidor. O nbftsrvr e", - "full_action": "Do one de o seguinte:\n■ Verifique que marked QLogic Target ports exist in o servidor. O nbftsrvr e\nnbfdrv64 processos exit if o system has não ports disponível para Target Mode\nuse.\n■ VerifythatavalidlicensefortheSANClientfeatureresidesonthemasterserver.\nSAN Cliente está um separately licensed recurso which requires um key called \"SAN\nCliente\" on o master servidor. O Fibre Transport servidor performs um license\nverifique during startup.\n■ DetermineifarebootisrequiredfortheinstallationoftheFibreTransportserver.\nSolaris installations require que you reboot o mídia servidor after you install\nFibre Transport to load o Fibre Transport drivers on o marked target ports.\nIn addition, reboot o Linux servers if you choose to não unload o existing\nQLogic drivers during o installation de Fibre Transport.\nPara further informação, veja o NetBackup SAN Cliente e Fibre Transport\nTroubleshooting Guide." + "desc": "No FT servers for this client are running", + "first_action": "Verify that marked QLogic Target ports exist in the server. The nbftsrvr and", + "full_action": "Do one of the following:\n■ Verify that marked QLogic Target ports exist in the server. The nbftsrvr and\nnbfdrv64 processes exit if the system has no ports available for Target Mode\nuse.\n■ VerifythatavalidlicensefortheSANClientfeatureresidesonthemasterserver.\nSAN Client is a separately licensed feature which requires a key called \"SAN\nClient\" on the master server. The Fibre Transport server performs a license\ncheck during startup.\n■ DetermineifarebootisrequiredfortheinstallationoftheFibreTransportserver.\nSolaris installations require that you reboot the media server after you install\nFibre Transport to load the Fibre Transport drivers on the marked target ports.\nIn addition, reboot the Linux servers if you choose to not unload the existing\nQLogic drivers during the installation of Fibre Transport.\nFor further information, see the NetBackup SAN Client and Fibre Transport\nTroubleshooting Guide." }, "2094": { "code": 2094, - "desc": "STU não é possível run Lifecycle backups", - "first_action": "Run o nbdevquery -listdp comando to verifique o", - "full_action": "Run o nbdevquery -listdp comando to verifique o\nconfiguration de o disco pool. If o Lifecycle attribute está não enabled para o disco\npool, run o nbdevconfig -changedp -setattribute comando to enable it." + "desc": "STU cannot run Lifecycle backups", + "first_action": "Run the nbdevquery -listdp command to check the", + "full_action": "Run the nbdevquery -listdp command to check the\nconfiguration of the disk pool. If the Lifecycle attribute is not enabled for the disk\npool, run the nbdevconfig -changedp -setattribute command to enable it." }, "2095": { "code": 2095, - "desc": "STU não é possível run VMware backup", - "first_action": "To run um VMware backup, o mídia servidor must run um", - "full_action": "To run um VMware backup, o mídia servidor must run um\nvalid version de NetBackup. Verifique que um valid version de NetBackup está executando ou\nconfigure o backup para um mídia servidor que runs um valid version de NetBackup." + "desc": "STU cannot run VMware backup", + "first_action": "To run a VMware backup, the media server must run a", + "full_action": "To run a VMware backup, the media server must run a\nvalid version of NetBackup. Verify that a valid version of NetBackup is running or\nconfigure the backup for a media server that runs a valid version of NetBackup." }, "2096": { "code": 2096, - "desc": "NDMP operation does não support multiple inline copies", + "desc": "NDMP operation does not support multiple inline copies", "first_action": "NetBackupcannotmakemultiplecopiesofNDMPpolicies.", - "full_action": "NetBackupcannotmakemultiplecopiesofNDMPpolicies.\nConfigure o backup para um single armazenamento unidade destination." + "full_action": "NetBackupcannotmakemultiplecopiesofNDMPpolicies.\nConfigure the backup for a single storage unit destination." }, "2097": { "code": 2097, - "desc": "Armazenamento unidade group does não exist in EMM configuration", - "first_action": "Reconfigure o policy to use um armazenamento unidade ou armazenamento", - "full_action": "Reconfigure o policy to use um armazenamento unidade ou armazenamento\nunidade group que exists in o configuration." + "desc": "Storage unit group does not exist in EMM configuration", + "first_action": "Reconfigure the policy to use a storage unit or storage", + "full_action": "Reconfigure the policy to use a storage unit or storage\nunit group that exists in the configuration." }, "2098": { "code": 2098, - "desc": "Mídia pool está não eligible para this job", - "first_action": "Change o configurado mídia pool para o job to use um", - "full_action": "Change o configurado mídia pool para o job to use um\npoolthatisconfigured,orcreatetherequiredmediapool.Makesurethatthemedia\npool you have configurado para o job está não um scratch pool." + "desc": "Media pool is not eligible for this job", + "first_action": "Change the configured media pool for the job to use a", + "full_action": "Change the configured media pool for the job to use a\npoolthatisconfigured,orcreatetherequiredmediapool.Makesurethatthemedia\npool you have configured for the job is not a scratch pool." }, "2099": { "code": 2099, - "desc": "Requerido drive ou drive caminho está não configurado", - "first_action": "Run o vmoprcmd comando to verifique o drive", - "full_action": "Run o vmoprcmd comando to verifique o drive\nconfiguration. Configure o drives que estão necessary para o mídia type que está\nused." + "desc": "Required drive or drive path is not configured", + "first_action": "Run the vmoprcmd command to verify the drive", + "full_action": "Run the vmoprcmd command to verify the drive\nconfiguration. Configure the drives that are necessary for the media type that is\nused." }, "2100": { "code": 2100, - "desc": "Maximum number de mounts has been excedido para tape mídia", - "first_action": "Aumentar o maximum allowed mounts para o mídia.", - "full_action": "Aumentar o maximum allowed mounts para o mídia.\nYoumayneedtoretirethismediaifithasexceededthemaximumnumberofmounts\nyou have configurado." + "desc": "Maximum number of mounts has been exceeded for tape media", + "first_action": "Increase the maximum allowed mounts for the media.", + "full_action": "Increase the maximum allowed mounts for the media.\nYoumayneedtoretirethismediaifithasexceededthemaximumnumberofmounts\nyou have configured." }, "2101": { "code": 2101, - "desc": "Mídia servidor não found in EMM banco de dados", - "first_action": "Para um restauração from tape, you can use o Force Mídia Servidor Restauração option to", - "full_action": "Do o seguinte como appropriate:\n■ Para um restauração from tape, you can use o Force Mídia Servidor Restauração option to\nforce NetBackup to replace o missing mídia servidor com um new mídia servidor.\n■ Para optimized duplication, garanta que o mídia servidor in common has\ncredentials para both armazenamento servers. More informação about OpenStorage\noptimized duplication está disponível.\nVeja o NetBackup OpenStorage Solutions Guide para Disco." + "desc": "Media server not found in EMM database", + "first_action": "For a restore from tape, you can use the Force Media Server Restore option to", + "full_action": "Do the following as appropriate:\n■ For a restore from tape, you can use the Force Media Server Restore option to\nforce NetBackup to replace the missing media server with a new media server.\n■ For optimized duplication, ensure that the media server in common has\ncredentials for both storage servers. More information about OpenStorage\noptimized duplication is available.\nSee the NetBackup OpenStorage Solutions Guide for Disk." }, "2102": { "code": 2102, - "desc": "Armazenamento unidade does não support spanning", - "first_action": "Some disco types do não support spanning. Run o", - "full_action": "Some disco types do não support spanning. Run o\nnbdevconfig -listdg comando to determinar if um disco group supports spanning.\nIf this erro persists, garanta que enough space está disponível on seu disco armazenamento\nunits para o new jobs que estão executando." + "desc": "Storage unit does not support spanning", + "first_action": "Some disk types do not support spanning. Run the", + "full_action": "Some disk types do not support spanning. Run the\nnbdevconfig -listdg command to determine if a disk group supports spanning.\nIf this error persists, ensure that enough space is available on your disk storage\nunits for the new jobs that are running." }, "2103": { "code": 2103, - "desc": "Mídia servidor mismatch", - "first_action": "Todos copies de um multiple copy job must run on o same", - "full_action": "Todos copies de um multiple copy job must run on o same\nmediaserver.Configurethestorageunitsthathavedrivepathsordiskaccessfrom\num common mídia servidor." + "desc": "Media server mismatch", + "first_action": "All copies of a multiple copy job must run on the same", + "full_action": "All copies of a multiple copy job must run on the same\nmediaserver.Configurethestorageunitsthathavedrivepathsordiskaccessfrom\na common media server." }, "2104": { "code": 2104, - "desc": "Armazenamento units estão não disponível", - "first_action": "Verifique que todos criteria in met para o policy com o armazenamento", - "full_action": "Verifique que todos criteria in met para o policy com o armazenamento\nunits que estão configurado." + "desc": "Storage units are not available", + "first_action": "Verify that all criteria in met for the policy with the storage", + "full_action": "Verify that all criteria in met for the policy with the storage\nunits that are configured." }, "2105": { "code": 2105, - "desc": "Armazenamento unidade solicitado para replication job está não replication capable", - "first_action": "Make sure que replication jobs include status configurado", - "full_action": "Make sure que replication jobs include status configurado\npara replication enabled disks in their armazenamento unidade specifiers." + "desc": "Storage unit requested for replication job is not replication capable", + "first_action": "Make sure that replication jobs include status configured", + "full_action": "Make sure that replication jobs include status configured\nfor replication enabled disks in their storage unit specifiers." }, "2106": { "code": 2106, - "desc": "Disco armazenamento servidor está down NetBackup status codes 445 NetBackup status codes", + "desc": "Disk storage server is down NetBackup status codes 445 NetBackup status codes", "first_action": "TheNetBackupCloudStoreServiceisrunningonthemasterandmediaservers.", - "full_action": "Verifique que todos mídia servers que estão configurado para o\nstorageservercancommunicatewiththestorageserver.Thebpstsinfocommand\nqueries o armazenamento servidor periodically, so you can use o bpstsinfo log set to\nverbosity level 5 on o mídia servidor.\nIftheerrorisrelatedtoacloudstoragebackupfailure,youshouldverifythefollowing\ninformação:\n■ TheNetBackupCloudStoreServiceisrunningonthemasterandmediaservers.\nVeja o NetBackup CloudStore Service Container startup e shutdown\ntroubleshooting section in o NetBackup Cloud Administrator's Guide para\ninformação on how to start o service.\n■ TheNetBackupcertificatesarestale/unavailableontheconfiguredmediaserver,\nwhich can cause o armazenamento servidor to go down. Garanta que you deploy todos de\no requerido certificates on que mídia servidor to keep o armazenamento servidor up. Para\nmore informação, veja o NetBackup Security Encryption Guide.\n■ O Enable insecure communication com 8.0 e earlier hosts option on\no NetBackup master servidor está selected if o mídia servidor está version 8.0 ou\nearlier. O option está disponível in o NetBackup Administration Console on\no Security Management > Global Security Settings > Secure\nCommunication tab." + "full_action": "Verify that all media servers that are configured for the\nstorageservercancommunicatewiththestorageserver.Thebpstsinfocommand\nqueries the storage server periodically, so you can use the bpstsinfo log set to\nverbosity level 5 on the media server.\nIftheerrorisrelatedtoacloudstoragebackupfailure,youshouldverifythefollowing\ninformation:\n■ TheNetBackupCloudStoreServiceisrunningonthemasterandmediaservers.\nSee the NetBackup CloudStore Service Container startup and shutdown\ntroubleshooting section in the NetBackup Cloud Administrator's Guide for\ninformation on how to start the service.\n■ TheNetBackupcertificatesarestale/unavailableontheconfiguredmediaserver,\nwhich can cause the storage server to go down. Ensure that you deploy all of\nthe required certificates on that media server to keep the storage server up. For\nmore information, see the NetBackup Security Encryption Guide.\n■ The Enable insecure communication with 8.0 and earlier hosts option on\nthe NetBackup master server is selected if the media server is version 8.0 or\nearlier. The option is available in the NetBackup Administration Console on\nthe Security Management > Global Security Settings > Secure\nCommunication tab." }, "2107": { "code": 2107, - "desc": "Solicitado mídia servidor does não have credentials ou está não configurado para o armazenamento servidor", - "first_action": "Optimized duplication requires um mídia servidor com", - "full_action": "Optimized duplication requires um mídia servidor com\ncredentials para both o ler side e gravar side armazenamento servers. Add o needed\ncredentials ou limite o mídia servers que o gravar side armazenamento unidade calls fora to\nthose que estão credentialed para o ler mídia." + "desc": "Requested media server does not have credentials or is not configured for the storage server", + "first_action": "Optimized duplication requires a media server with", + "full_action": "Optimized duplication requires a media server with\ncredentials for both the read side and write side storage servers. Add the needed\ncredentials or limit the media servers that the write side storage unit calls out to\nthose that are credentialed for the read media." }, "2108": { "code": 2108, "desc": "RequestedNDMPmachinedoesnothavecredentialsorisnotconfigured in NetBackup", - "first_action": "Jobs para NDMP policies require que o NDMP host que", - "full_action": "Jobs para NDMP policies require que o NDMP host que\nestá specified como o cliente in o policy be configurado in NetBackup. O credentials\nque estão defined para qualquer servidor must access o NDMP host.\nVerifique que o requerido NDMP host está configurado. If o configurado NDMP host está\nafullyqualifiednameandtheNDMPhostnameinthepolicyisnot,runthefollowing\ncomando to add um alias to o NDMP host:\n# nbemmcmd -machinealias -addalias -alias string -machinename string" + "first_action": "Jobs for NDMP policies require that the NDMP host that", + "full_action": "Jobs for NDMP policies require that the NDMP host that\nis specified as the client in the policy be configured in NetBackup. The credentials\nthat are defined for any server must access the NDMP host.\nVerify that the required NDMP host is configured. If the configured NDMP host is\nafullyqualifiednameandtheNDMPhostnameinthepolicyisnot,runthefollowing\ncommand to add an alias to the NDMP host:\n# nbemmcmd -machinealias -addalias -alias string -machinename string" }, "2109": { "code": 2109, - "desc": "Solicitado Fibre Transport cliente machine foi não found in NetBackup configuration", - "first_action": "Fibre Transport backup e restauração operations require", - "full_action": "Fibre Transport backup e restauração operations require\neachFibreTransportclienttobeconfiguredinNetBackup.Verifythattheclientthat\nestá solicitado para o job está configurado como um Fibre Transport cliente." + "desc": "Requested Fibre Transport client machine was not found in NetBackup configuration", + "first_action": "Fibre Transport backup and restore operations require", + "full_action": "Fibre Transport backup and restore operations require\neachFibreTransportclienttobeconfiguredinNetBackup.Verifythattheclientthat\nis requested for the job is configured as a Fibre Transport client." }, "2110": { "code": 2110, - "desc": "Solicitado machine está não configurado in NetBackup", - "first_action": "O policy que you use to run o job may indicate which", - "full_action": "O policy que you use to run o job may indicate which\nservidor o job requires. If não, find o servidor que o job looks para por setting o\nMDS VxUL logging (OID 143) to debug level 2 e retry o job. O MDS log\nusually indicates which host name caused o problema." + "desc": "Requested machine is not configured in NetBackup", + "first_action": "The policy that you use to run the job may indicate which", + "full_action": "The policy that you use to run the job may indicate which\nserver the job requires. If not, find the server that the job looks for by setting the\nMDS VxUL logging (OID 143) to debug level 2 and retry the job. The MDS log\nusually indicates which host name caused the problem." }, "2111": { "code": 2111, - "desc": "AllstorageunitsareconfiguredwithOnDemandOnlyandarenoteligible para jobs requesting Qualquer armazenamento unidade", - "first_action": "Change o policy to use um specific armazenamento unidade instead", - "full_action": "Change o policy to use um specific armazenamento unidade instead\nde qualquer disponível armazenamento unidade, ou configure at least one armazenamento unidade without o On\nDemand Apenas setting." + "desc": "AllstorageunitsareconfiguredwithOnDemandOnlyandarenoteligible for jobs requesting ANY storage unit", + "first_action": "Change the policy to use a specific storage unit instead", + "full_action": "Change the policy to use a specific storage unit instead\nof any available storage unit, or configure at least one storage unit without the On\nDemand Only setting." }, "2112": { "code": 2112, - "desc": "NetBackup mídia servidor version está too low para o operation", - "first_action": "Point o armazenamento unidade to um mídia servidor com um newer", - "full_action": "Point o armazenamento unidade to um mídia servidor com um newer\nversion de software." + "desc": "NetBackup media server version is too low for the operation", + "first_action": "Point the storage unit to a media server with a newer", + "full_action": "Point the storage unit to a media server with a newer\nversion of software." }, "2113": { "code": 2113, - "desc": "Inválido ou não disco array credentials estão added para vserver", + "desc": "Invalid or no disk array credentials are added for vserver", "first_action": "UndertheDiskArrayHostscredentialssection,addadmin", - "full_action": "UndertheDiskArrayHostscredentialssection,addadmin\ncredentials de NetApp Armazenamento Virtual Machine's interface que has management\naccess enabled. Garanta que o right Armazenamento Virtual Machine's interface name está\nentered que holds o snapshot/replica to be indexed. Garanta que o Armazenamento\nVirtual Machine (SVM) usuário account com o ONTAPi application está in o unlocked\nstate.\nVeja o NetBackup Replication Director Solutions Guide para more informação." + "full_action": "UndertheDiskArrayHostscredentialssection,addadmin\ncredentials of NetApp Storage Virtual Machine's interface that has management\naccess enabled. Ensure that the right Storage Virtual Machine's interface name is\nentered that holds the snapshot/replica to be indexed. Ensure that the Storage\nVirtual Machine (SVM) user account with the ONTAPi application is in the unlocked\nstate.\nSee the NetBackup Replication Director Solutions Guide for more information." }, "2114": { "code": 2114, - "desc": "Mídia servidor está não recognized.", - "first_action": "Add authorization para o mídia servidor on o master servidor e restart o", - "full_action": "This erro does não necessarily mean que um configuration\nchange está requerido. However, repeated instances de this erro indicate que um\nconfiguration change should be considered to maintain good master servidor\nperformance.\nExecutar o seguinte como appropriate:\n■ Add authorization para o mídia servidor on o master servidor e restart o\nNetBackup services on o mídia servidor.\n■ Add mídia servidor to o PBX BLOCK_SERVER_SERVICE list on o master servidor.\nO services que should be blocked estão EMM e NBREM.\nFormoreinformationaboutblockingincomingconnections,refertothefollowing\narticle on o Cohesity Technical Support website:\nhttps://www.veritas.com/content/support/en_US/article.100048495\n■ Uninstall mídia servidor software.\n■ Shut down o mídia servidor.\nWarning: In um NetBackup DNAT environment, o identified IP address e host\nname may point to um gateway e não o mídia servidor. Verifique o host informação\nbefore attempting additional steps to resolve o problema." + "desc": "Media server is not recognized.", + "first_action": "Add authorization for the media server on the master server and restart the", + "full_action": "This error does not necessarily mean that a configuration\nchange is required. However, repeated instances of this error indicate that a\nconfiguration change should be considered to maintain good master server\nperformance.\nPerform the following as appropriate:\n■ Add authorization for the media server on the master server and restart the\nNetBackup services on the media server.\n■ Add media server to the PBX BLOCK_SERVER_SERVICE list on the master server.\nThe services that should be blocked are EMM and NBREM.\nFormoreinformationaboutblockingincomingconnections,refertothefollowing\narticle on the Cohesity Technical Support website:\nhttps://www.veritas.com/content/support/en_US/article.100048495\n■ Uninstall media server software.\n■ Shut down the media server.\nWarning: In a NetBackup DNAT environment, the identified IP address and host\nname may point to a gateway and not the media server. Verify the host information\nbefore attempting additional steps to resolve the problem." }, "2205": { "code": 2205, - "desc": "Snapshot replication está não supported para o specified details.", - "first_action": "You must change o protection plan configuration to fix", - "full_action": "You must change o protection plan configuration to fix\nthese issues. NetBackup does não retry o replication job." + "desc": "Snapshot replication is not supported for the specified details.", + "first_action": "You must change the protection plan configuration to fix", + "full_action": "You must change the protection plan configuration to fix\nthese issues. NetBackup does not retry the replication job." }, "2206": { "code": 2206, "desc": "SnapshotManagerfailedtoretrievenetworksecuritygroupsagainstthe specified plug-in instance.", - "first_action": "You must select um valid subnetId from one de o regions", - "full_action": "You must select um valid subnetId from one de o regions\nque estão mentioned in o cloud provider configuration." + "first_action": "You must select a valid subnetId from one of the regions", + "full_action": "You must select a valid subnetId from one of the regions\nthat are mentioned in the cloud provider configuration." }, "2213": { "code": 2213, - "desc": "Falhou to excluir configurado plug-in instance in Snapshot Manager.", - "first_action": "If um plug-in excluir está needed, then excluir todos active", - "full_action": "If um plug-in excluir está needed, then excluir todos active\nsnapshots e attempt to excluir o plug-in again. If you need to excluir o plug-in\nwithoutclearingasnapshot,youcanpasstheX-NetBackup-Force-Plugin-Delete\nheader como TRUE. O snapshots remain in o cloud so you must remove those\nmanually." + "desc": "Failed to delete configured plug-in instance in Snapshot Manager.", + "first_action": "If a plug-in delete is needed, then delete all active", + "full_action": "If a plug-in delete is needed, then delete all active\nsnapshots and attempt to delete the plug-in again. If you need to delete the plug-in\nwithoutclearingasnapshot,youcanpasstheX-NetBackup-Force-Plugin-Delete\nheader as TRUE. The snapshots remain in the cloud so you must remove those\nmanually." }, "2228": { "code": 2228, - "desc": "Security Group ou Subnet configuration não é possível be provided when you retain o rede configuration para cloud VM restauração.", - "first_action": "Retain either o original rede configuration ou specify", - "full_action": "Retain either o original rede configuration ou specify\num destination subnet ou security group." + "desc": "Security Group or Subnet configuration cannot be provided when you retain the network configuration for cloud VM restore.", + "first_action": "Retain either the original network configuration or specify", + "full_action": "Retain either the original network configuration or specify\na destination subnet or security group." }, "2229": { "code": 2229, "desc": "Cannotretainnetworkconfigurationwhilerestoringacrosscloudservice providers.", - "first_action": "Through API, excluir o retainNetworkConfig flag ou", - "full_action": "Through API, excluir o retainNetworkConfig flag ou\nset it to False in o recovery ou pre-recovery payload. Through o UI, deselect\no Restauração rede configuration option." + "first_action": "Through API, delete the retainNetworkConfig flag or", + "full_action": "Through API, delete the retainNetworkConfig flag or\nset it to False in the recovery or pre-recovery payload. Through the UI, deselect\nthe Restore network configuration option." }, "2230": { "code": 2230, - "desc": "Falhou to create snapshot due to um missing asset.", - "first_action": "Unsubscribe o asset from o protection plan.", - "full_action": "Unsubscribe o asset from o protection plan." + "desc": "Failed to create snapshot due to a missing asset.", + "first_action": "Unsubscribe the asset from the protection plan.", + "full_action": "Unsubscribe the asset from the protection plan." }, "2231": { "code": 2231, - "desc": "Não enough liberar space on host.", + "desc": "Not enough free space on host.", "first_action": "CreatesomespaceonthehostwhereNetBackupprimary", - "full_action": "CreatesomespaceonthehostwhereNetBackupprimary\nservidor está instalado." + "full_action": "CreatesomespaceonthehostwhereNetBackupprimary\nserver is installed." }, "2232": { "code": 2232, - "desc": "Arquivo already exists.", - "first_action": "Determinar if o arquivo being uploaded está um duplicate arquivo.", - "full_action": "Executar o seguinte como appropriate:\n■ Determinar if o arquivo being uploaded está um duplicate arquivo.\n■ Change o name de o arquivo you desejar to upload." + "desc": "File already exists.", + "first_action": "Determine if the file being uploaded is a duplicate file.", + "full_action": "Perform the following as appropriate:\n■ Determine if the file being uploaded is a duplicate file.\n■ Change the name of the file you want to upload." }, "2233": { "code": 2233, - "desc": "Falhou to upload telemetry arquivo.", - "first_action": "Correct qualquer errors que you find in o nbwebservice logs", - "full_action": "Correct qualquer errors que you find in o nbwebservice logs\nque ocorreu when you attempted to create ou to upload o telemetry arquivo." + "desc": "Failed to upload telemetry file.", + "first_action": "Correct any errors that you find in the nbwebservice logs", + "full_action": "Correct any errors that you find in the nbwebservice logs\nthat occurred when you attempted to create or to upload the telemetry file." }, "2250": { "code": 2250, "desc": "TherequesthastimedoutwhileNetBackupretrievedtheerrorlogresults page.", - "first_action": "Narrow o date range, then run o query again. If you", - "full_action": "Narrow o date range, then run o query again. If you\nuse o APIs, you can also change o page size." + "first_action": "Narrow the date range, then run the query again. If you", + "full_action": "Narrow the date range, then run the query again. If you\nuse the APIs, you can also change the page size." }, "2251": { "code": 2251, - "desc": "O cursor value está inválido. NetBackup status codes 452 NetBackup status codes", - "first_action": "Review o previous API response e use o correct", - "full_action": "Review o previous API response e use o correct\nvalue para o page[after] value. If o request contains um inválido value, in o\nerro log locate o pagination meta tag in o response. O value de \"next\" está\no value que you desejar to use para page[after].\n\"meta\": {\n\"pagination\":\n{ \"next\": \"28002872c601fd648f3154e58532558e429c9632035c3bf042a6accdd77d8356\", \"limite\": 5 }\n}" + "desc": "The cursor value is invalid. NetBackup status codes 452 NetBackup status codes", + "first_action": "Review the previous API response and use the correct", + "full_action": "Review the previous API response and use the correct\nvalue for the page[after] value. If the request contains an invalid value, in the\nerror log locate the pagination meta tag in the response. The value of \"next\" is\nthe value that you want to use for page[after].\n\"meta\": {\n\"pagination\":\n{ \"next\": \"28002872c601fd648f3154e58532558e429c9632035c3bf042a6accdd77d8356\", \"limit\": 5 }\n}" }, "2252": { "code": 2252, - "desc": "O number de simultaneous erro log requests has been excedido.", - "first_action": "Wait until one ou more active requests para erro logs estão", - "full_action": "Wait until one ou more active requests para erro logs estão\ncomplete. Then try to run o new erro log request again." + "desc": "The number of simultaneous error log requests has been exceeded.", + "first_action": "Wait until one or more active requests for error logs are", + "full_action": "Wait until one or more active requests for error logs are\ncomplete. Then try to run the new error log request again." }, "2300": { "code": 2300, - "desc": "O vmRecoveryDestination field must be specified in o recovery request. NetBackup status codes 453 NetBackup status codes", - "first_action": "Verifique que o vmRecoveryDestination field está specified", - "full_action": "Verifique que o vmRecoveryDestination field está specified\ne que it está não vazio." + "desc": "The vmRecoveryDestination field must be specified in the recovery request. NetBackup status codes 453 NetBackup status codes", + "first_action": "Verify that the vmRecoveryDestination field is specified", + "full_action": "Verify that the vmRecoveryDestination field is specified\nand that it is not empty." }, "2301": { "code": 2301, - "desc": "O alternateLocationDirectory field must não be blank.", - "first_action": "O alternateLocationDirectory field está optional. If", - "full_action": "O alternateLocationDirectory field está optional. If\nthis field está included, you must specify um diretório value para o\nalternateLocationDirectory field que está não vazio." + "desc": "The alternateLocationDirectory field must not be blank.", + "first_action": "The alternateLocationDirectory field is optional. If", + "full_action": "The alternateLocationDirectory field is optional. If\nthis field is included, you must specify a directory value for the\nalternateLocationDirectory field that is not empty." }, "2302": { "code": 2302, - "desc": "O instanceUuid field must não be blank.", - "first_action": "Verifique o instanceUuid field de o pre-recovery verifique", - "full_action": "Verifique o instanceUuid field de o pre-recovery verifique\nrequestis specifiedand notempty.TheinstanceUuidfieldoftherecovery request\nestá optional. If o field está included, you must specify um value que está não vazio." + "desc": "The instanceUuid field must not be blank.", + "first_action": "Verify the instanceUuid field of the pre-recovery check", + "full_action": "Verify the instanceUuid field of the pre-recovery check\nrequestis specifiedand notempty.TheinstanceUuidfieldoftherecovery request\nis optional. If the field is included, you must specify a value that is not empty." }, "2303": { "code": 2303, - "desc": "O stagingLocation field must não be blank.", - "first_action": "O stagingLocation field está optional. If this field está", - "full_action": "O stagingLocation field está optional. If this field está\nincluded, you must specify um caminho value que está não vazio." + "desc": "The stagingLocation field must not be blank.", + "first_action": "The stagingLocation field is optional. If this field is", + "full_action": "The stagingLocation field is optional. If this field is\nincluded, you must specify a path value that is not empty." }, "2304": { "code": 2304, - "desc": "O datastore field must não be blank.", - "first_action": "Verifique o datastore field de o pre-recovery verifique", - "full_action": "Verifique o datastore field de o pre-recovery verifique\nrequest está specified e não vazio. O datastore field de o recovery request está\noptional. If que field está included, you must specify um value que está não vazio." + "desc": "The datastore field must not be blank.", + "first_action": "Verify the datastore field of the pre-recovery check", + "full_action": "Verify the datastore field of the pre-recovery check\nrequest is specified and not empty. The datastore field of the recovery request is\noptional. If that field is included, you must specify a value that is not empty." }, "2305": { "code": 2305, - "desc": "Inválido virtual machine usuário name ou password.", - "first_action": "Verifique que o vmUsername e vmPassword fields estão", - "full_action": "Verifique que o vmUsername e vmPassword fields estão\nspecified e que they estão não vazio." + "desc": "Invalid virtual machine user name or password.", + "first_action": "Verify that the vmUsername and vmPassword fields are", + "full_action": "Verify that the vmUsername and vmPassword fields are\nspecified and that they are not empty." }, "2306": { "code": 2306, - "desc": "O vmFiles field must não be blank.", - "first_action": "Verifique que o vmFiles field está specified e que it está não", - "full_action": "Verifique que o vmFiles field está specified e que it está não\nvazio." + "desc": "The vmFiles field must not be blank.", + "first_action": "Verify that the vmFiles field is specified and that it is not", + "full_action": "Verify that the vmFiles field is specified and that it is not\nempty." }, "2307": { "code": 2307, - "desc": "O source field de virtual machine arquivos must não be blank.", - "first_action": "Verifique que o arquivo source field está specified e que it está", - "full_action": "Verifique que o arquivo source field está specified e que it está\nnão vazio." + "desc": "The source field of virtual machine files must not be blank.", + "first_action": "Verify that the file source field is specified and that it is", + "full_action": "Verify that the file source field is specified and that it is\nnot empty." }, "2308": { "code": 2308, - "desc": "O destination field de virtual machine arquivos must não be blank.", - "first_action": "O destination field está optional. If this field está included,", - "full_action": "O destination field está optional. If this field está included,\nyou must specify um destination caminho value que está não vazio." + "desc": "The destination field of virtual machine files must not be blank.", + "first_action": "The destination field is optional. If this field is included,", + "full_action": "The destination field is optional. If this field is included,\nyou must specify a destination path value that is not empty." }, "2309": { "code": 2309, - "desc": "Falhou to create o agentless recovery restauração specification.", - "first_action": "O JSON request syntax está inválido.", - "full_action": "O JSON request syntax está inválido." + "desc": "Failed to create the agentless recovery restore specification.", + "first_action": "The JSON request syntax is invalid.", + "full_action": "The JSON request syntax is invalid." }, "2310": { "code": 2310, - "desc": "O size field must não be blank.", - "first_action": "Verifique que o size field está specified e que it está não", - "full_action": "Verifique que o size field está specified e que it está não\nvazio." + "desc": "The size field must not be blank.", + "first_action": "Verify that the size field is specified and that it is not", + "full_action": "Verify that the size field is specified and that it is not\nempty." }, "2311": { "code": 2311, - "desc": "Falhou to add guest virtual machine credentials.", - "first_action": "Verifique o NetBackup services estão executando on o master", - "full_action": "Verifique o NetBackup services estão executando on o master\nservidor." + "desc": "Failed to add guest virtual machine credentials.", + "first_action": "Verify the NetBackup services are running on the master", + "full_action": "Verify the NetBackup services are running on the master\nserver." }, "2312": { "code": 2312, - "desc": "O alternateLocationDirectory must begin com um /.", - "first_action": "You must specify um forward slash (/) at o beginning de", - "full_action": "You must specify um forward slash (/) at o beginning de\no alternateLocationDirectory caminho." + "desc": "The alternateLocationDirectory must begin with a /.", + "first_action": "You must specify a forward slash (/) at the beginning of", + "full_action": "You must specify a forward slash (/) at the beginning of\nthe alternateLocationDirectory path." }, "2313": { "code": 2313, - "desc": "O source caminho de virtual machine arquivos must begin com /.", - "first_action": "You must specify um forward slash (/) at o beginning de", - "full_action": "You must specify um forward slash (/) at o beginning de\no arquivo source caminho." + "desc": "The source path of virtual machine files must begin with /.", + "first_action": "You must specify a forward slash (/) at the beginning of", + "full_action": "You must specify a forward slash (/) at the beginning of\nthe file source path." }, "2314": { "code": 2314, - "desc": "O destination caminho de virtual machine arquivos must begin com /.", - "first_action": "You must specify um forward slash (/) at o beginning de", - "full_action": "You must specify um forward slash (/) at o beginning de\no arquivo destination caminho." + "desc": "The destination path of virtual machine files must begin with /.", + "first_action": "You must specify a forward slash (/) at the beginning of", + "full_action": "You must specify a forward slash (/) at the beginning of\nthe file destination path." }, "2317": { "code": 2317, - "desc": "Falhou to remove guest virtual machine credentials.", - "first_action": "Manually remove o credentials from o guest virtual", - "full_action": "Manually remove o credentials from o guest virtual\nmachine." + "desc": "Failed to remove guest virtual machine credentials.", + "first_action": "Manually remove the credentials from the guest virtual", + "full_action": "Manually remove the credentials from the guest virtual\nmachine." }, "2318": { "code": 2318, - "desc": "O appendString field must não be blank.", + "desc": "The appendString field must not be blank.", "first_action": "TheappendStringfieldisoptional.Ifthisfieldisincluded,", - "full_action": "TheappendStringfieldisoptional.Ifthisfieldisincluded,\nyou must specify um string value para o appendString field que está não vazio." + "full_action": "TheappendStringfieldisoptional.Ifthisfieldisincluded,\nyou must specify a string value for the appendString field that is not empty." }, "2319": { "code": 2319, - "desc": "Append string to arquivo names está não supported para directories.", + "desc": "Append string to file names is not supported for directories.", "first_action": "TheappendStringfieldisonlysupportedforfiles.Remove", - "full_action": "TheappendStringfieldisonlysupportedforfiles.Remove\nqualquer directories que estão specified in o list de entradas to be restored." + "full_action": "TheappendStringfieldisonlysupportedforfiles.Remove\nany directories that are specified in the list of entries to be restored." }, "2320": { "code": 2320, - "desc": "Flatten diretório structures está não supported para directories.", + "desc": "Flatten directory structures is not supported for directories.", "first_action": "TheflattenDirectoryStructurefieldisonlysupported", "full_action": "TheflattenDirectoryStructurefieldisonlysupported\nforfiles.Removeanydirectoriesthatarespecifiedinthelistofentriestoberestored." }, "2322": { "code": 2322, - "desc": "Falhou to create o staging location caminho.", - "first_action": "O staging location defaults to /usr/openv/var/stagingloc ou", - "full_action": "Use o default staging location caminho ou garanta que o\nuser-configured staging location caminho está valid.\nStaging location setup informação:\n■ O staging location defaults to /usr/openv/var/stagingloc ou\nVERITAS\\NetBackup\\var\\stagingloc.Thislocationisusedtostagefilesduring\nRestricted Restauração Mode restauração.\n■ You can override o caminho usando o bp.conf parâmetro\nAGENTLESS_RHOST_STAGING_PATH = \"caminho\" configurado on o recovery host.\nIfthepathdoesnotexistontherecoveryhost,NetBackupautomaticallycreates\nit com appropriate permissions." + "desc": "Failed to create the staging location path.", + "first_action": "The staging location defaults to /usr/openv/var/stagingloc or", + "full_action": "Use the default staging location path or ensure that the\nuser-configured staging location path is valid.\nStaging location setup information:\n■ The staging location defaults to /usr/openv/var/stagingloc or\nVERITAS\\NetBackup\\var\\stagingloc.Thislocationisusedtostagefilesduring\nRestricted Restore Mode restore.\n■ You can override the path using the bp.conf parameter\nAGENTLESS_RHOST_STAGING_PATH = \"path\" configured on the recovery host.\nIfthepathdoesnotexistontherecoveryhost,NetBackupautomaticallycreates\nit with appropriate permissions." }, "2323": { "code": 2323, - "desc": "O staging location exists but ACLs e ou permissão bits set to on estão insecure.", + "desc": "The staging location exists but ACLs and or permission bits set to on are insecure.", "first_action": "OnWindows:TheACLsdefinedmustbeexplicitandshouldnotrelyoninherited", - "full_action": "Garanta que o staging location caminho está secure.\n■ OnWindows:TheACLsdefinedmustbeexplicitandshouldnotrelyoninherited\npermissions from o parent folder.\n■ On UNIX: Accessible apenas to o owner ou o group. Permissão bits para other\nshould look like 07?0 ou drxw???---." + "full_action": "Ensure that the staging location path is secure.\n■ OnWindows:TheACLsdefinedmustbeexplicitandshouldnotrelyoninherited\npermissions from the parent folder.\n■ On UNIX: Accessible only to the owner or the group. Permission bits for other\nshould look like 07?0 or drxw???---." }, "2324": { "code": 2324, - "desc": "Falhou to remove o staging location e qualquer arquivos que estão left on o recovery host.", - "first_action": "Remove qualquer arquivos e folders from o staging location", - "full_action": "Remove qualquer arquivos e folders from o staging location\nfolder que foram left behind. Review o logs to determinar por que NetBackup falhou to\nexcluir o folder. Garanta não other process e ou usuário blocks NetBackup from\nremoving this folder." + "desc": "Failed to remove the staging location and any files that are left on the recovery host.", + "first_action": "Remove any files and folders from the staging location", + "full_action": "Remove any files and folders from the staging location\nfolder that were left behind. Review the logs to determine why NetBackup failed to\ndelete the folder. Ensure no other process and or user blocks NetBackup from\nremoving this folder." }, "2325": { "code": 2325, - "desc": "SpecifiedrecoveryhostneedstobeatNetBackupversion9.0orgreater to support Restricted Restauração Mode restores.", - "first_action": "Select um recovery host que está NetBackup 9.0 ou newer.", - "full_action": "Select um recovery host que está NetBackup 9.0 ou newer." + "desc": "SpecifiedrecoveryhostneedstobeatNetBackupversion9.0orgreater to support Restricted Restore Mode restores.", + "first_action": "Select a recovery host that is NetBackup 9.0 or newer.", + "full_action": "Select a recovery host that is NetBackup 9.0 or newer." }, "2326": { "code": 2326, - "desc": "Falhou to update o recovery state arquivo.", - "first_action": "Review logs to determinar por que NetBackup did não ler ou", - "full_action": "Review logs to determinar por que NetBackup did não ler ou\ngravar to o recovery state arquivo." + "desc": "Failed to update the recovery state file.", + "first_action": "Review logs to determine why NetBackup did not read or", + "full_action": "Review logs to determine why NetBackup did not read or\nwrite to the recovery state file." }, "2328": { "code": 2328, - "desc": "O communicationType field não é possível be vazio.", - "first_action": "O communicationType field está mandatory. O value", - "full_action": "O communicationType field está mandatory. O value\nmust be either set to SSH ou WMI." + "desc": "The communicationType field cannot be empty.", + "first_action": "The communicationType field is mandatory. The value", + "full_action": "The communicationType field is mandatory. The value\nmust be either set to SSH or WMI." }, "2329": { "code": 2329, - "desc": "O targetHost field está either vazio ou o name está inválido", - "first_action": "O targetHost field está mandatory. Provide um valid host", - "full_action": "O targetHost field está mandatory. Provide um valid host\nname ou um IP address de o target host." + "desc": "The targetHost field is either empty or the name is invalid", + "first_action": "The targetHost field is mandatory. Provide a valid host", + "full_action": "The targetHost field is mandatory. Provide a valid host\nname or an IP address of the target host." }, "2330": { "code": 2330, - "desc": "O sshFingerprint field não é possível be vazio.", - "first_action": "O sshFingerprint field está mandatory. Provide um SSH", - "full_action": "O sshFingerprint field está mandatory. Provide um SSH\nkey fingerprint de o target host." + "desc": "The sshFingerprint field cannot be empty.", + "first_action": "The sshFingerprint field is mandatory. Provide an SSH", + "full_action": "The sshFingerprint field is mandatory. Provide an SSH\nkey fingerprint of the target host." }, "2331": { "code": 2331, - "desc": "O specified recovery host must be at NetBackup version 9.1 ou later to support agentless restores.", + "desc": "The specified recovery host must be at NetBackup version 9.1 or later to support agentless restores.", "first_action": "VerifytheNetBackupversiononrecoveryhost.Theversion", - "full_action": "VerifytheNetBackupversiononrecoveryhost.Theversion\nshould be 9.1 ou later." + "full_action": "VerifytheNetBackupversiononrecoveryhost.Theversion\nshould be 9.1 or later." }, "2334": { "code": 2334, - "desc": "Recovery host staging location does não exist.", + "desc": "Recovery host staging location does not exist.", "first_action": "Windows:", - "full_action": "Verifique que o default staging location caminho ou o\nuser-configured staging location caminho para o recovery host está valid.\nNetBackup uses o seguinte locations on o recovery host como default staging\nlocations:\n■ Windows:\ninstallpath\\Veritas\\NetBackup\\var\\tmp\\staging\\\n■ UNIX\n/usr/openv/var/tmp/staging/\nVerifique que o staging location caminho que está used exists. Para o user-configured\nstaginglocation,checkifavalidpathontherecoveryhostisspecifiedinthebp.conf\nparâmetro AGENTLESS_RHOST_STAGING_PATH = \\\"caminho\\\"." + "full_action": "Verify that the default staging location path or the\nuser-configured staging location path for the recovery host is valid.\nNetBackup uses the following locations on the recovery host as default staging\nlocations:\n■ Windows:\ninstallpath\\Veritas\\NetBackup\\var\\tmp\\staging\\\n■ UNIX\n/usr/openv/var/tmp/staging/\nVerify that the staging location path that is used exists. For the user-configured\nstaginglocation,checkifavalidpathontherecoveryhostisspecifiedinthebp.conf\nparameter AGENTLESS_RHOST_STAGING_PATH = \\\"path\\\"." }, "2335": { "code": 2335, - "desc": "Um tar image foi não found at o staging location on o recovery host.", - "first_action": "O tar image foi não found at o recovery host staging", - "full_action": "O tar image foi não found at o recovery host staging\nlocation.Retrytheoperationandiftheissuepersists,visitsupport.veritas.com.The\nCohesityTechnicalSupportsiteoffersadditionalinformationtohelpyoutroubleshoot\nthis issue." + "desc": "A tar image was not found at the staging location on the recovery host.", + "first_action": "The tar image was not found at the recovery host staging", + "full_action": "The tar image was not found at the recovery host staging\nlocation.Retrytheoperationandiftheissuepersists,visitsupport.veritas.com.The\nCohesityTechnicalSupportsiteoffersadditionalinformationtohelpyoutroubleshoot\nthis issue." }, "2336": { "code": 2336, - "desc": "Internal erro has caused falha de recovery validation.", - "first_action": "Save o bpVMutil logs on o recovery host e contate", - "full_action": "Save o bpVMutil logs on o recovery host e contate\nCohesity Technical Support." + "desc": "Internal error has caused failure of recovery validation.", + "first_action": "Save the bpVMutil logs on the recovery host and contact", + "full_action": "Save the bpVMutil logs on the recovery host and contact\nCohesity Technical Support." }, "2337": { "code": 2337, - "desc": "Não enough space disponível on recovery host.", - "first_action": "Verifique que there está sufficient liberar space disponível on o", - "full_action": "Verifique que there está sufficient liberar space disponível on o\nrecovery host staging location por comparing it to o total size de arquivos ou folders\nselected.Or,selectadifferentrecoveryhostwithsufficientfreespaceforperforming\num agentless restauração." + "desc": "Not enough space available on recovery host.", + "first_action": "Verify that there is sufficient free space available on the", + "full_action": "Verify that there is sufficient free space available on the\nrecovery host staging location by comparing it to the total size of files or folders\nselected.Or,selectadifferentrecoveryhostwithsufficientfreespaceforperforming\nan agentless restore." }, "2339": { "code": 2339, - "desc": "Não enough space disponível on target host.", + "desc": "Not enough space available on target host.", "first_action": "Ifnotexplicitlyprovided,NetBackupusestheuser’shome", - "full_action": "Ifnotexplicitlyprovided,NetBackupusestheuser’shome\ndirectoryasadefaultstaginglocationontargethost.Verifythatsufficientfreespace\nestá disponível on o target host ou select um different staging location on same target\nhost com sufficient liberar space." + "full_action": "Ifnotexplicitlyprovided,NetBackupusestheuser’shome\ndirectoryasadefaultstaginglocationontargethost.Verifythatsufficientfreespace\nis available on the target host or select a different staging location on same target\nhost with sufficient free space." }, "2340": { "code": 2340, - "desc": "Tar está não present on o target host.", + "desc": "Tar is not present on the target host.", "first_action": "Thetarutilityisnotpresentonthetargethost.Thesystem", - "full_action": "Thetarutilityisnotpresentonthetargethost.Thesystem\ntar utility está requerido to be present on target host com UNIX operating system para\nperforming um agentless restauração on it usando NetBackup. Retry o operation after\ndeploying o tar utility." + "full_action": "Thetarutilityisnotpresentonthetargethost.Thesystem\ntar utility is required to be present on target host with UNIX operating system for\nperforming an agentless restore on it using NetBackup. Retry the operation after\ndeploying the tar utility." }, "2341": { "code": 2341, - "desc": "O usuário does não have requerido permissão on o target host staging location.", - "first_action": "Verifique que o usuário has sufficient permissions to access", - "full_action": "Verifique que o usuário has sufficient permissions to access\no location e o target host staging location exists." + "desc": "The user does not have required permission on the target host staging location.", + "first_action": "Verify that the user has sufficient permissions to access", + "full_action": "Verify that the user has sufficient permissions to access\nthe location and the target host staging location exists." }, "2342": { "code": 2342, - "desc": "O usuário does não have raiz ou administrator privileges. To restauração arquivos e folders, provide usuário com raiz ou administrator privileges.", - "first_action": "O provided credentials do não have o requerido", - "full_action": "O provided credentials do não have o requerido\npermissions on o target host para agentless arquivos ou folders restauração. Para Windows,\nyou must use o credential which está part de o local administrator group on o\ntarget host. Para o UNIX target host, use o credential which está o raiz ou o\nsudo account com Todos permissions." + "desc": "The user does not have root or administrator privileges. To restore files and folders, provide user with root or administrator privileges.", + "first_action": "The provided credentials do not have the required", + "full_action": "The provided credentials do not have the required\npermissions on the target host for agentless files or folders restore. For Windows,\nyou must use the credential which is part of the local administrator group on the\ntarget host. For the UNIX target host, use the credential which is the root or the\nsudo account with ALL permissions." }, "2343": { "code": 2343, - "desc": "O administrator share de o target host está não accessible from o recovery host.", - "first_action": "Firewall exceptions estão set up correctly", - "full_action": "Thiserrorisusuallyseenwhenthetargethostforagentless\nrestauração has um Windows OS. Verifique que o seguinte items estão set up correctly on\ntarget host:\n■ Firewall exceptions estão set up correctly\n■ Arquivo e printer sharing está enabled.\n■ GPO/SoftwareRestrictionPolicyoranantivirussoftwaredoesnotblockaccess.\n■ O target host está accessible com valid credentials." + "desc": "The administrator share of the target host is not accessible from the recovery host.", + "first_action": "Firewall exceptions are set up correctly", + "full_action": "Thiserrorisusuallyseenwhenthetargethostforagentless\nrestore has a Windows OS. Verify that the following items are set up correctly on\ntarget host:\n■ Firewall exceptions are set up correctly\n■ File and printer sharing is enabled.\n■ GPO/SoftwareRestrictionPolicyoranantivirussoftwaredoesnotblockaccess.\n■ The target host is accessible with valid credentials." }, "2344": { "code": 2344, - "desc": "O provided credentials estão para um local administrator usuário.", - "first_action": "Para agentless restauração in um Usuário Account Control (UAC)", - "full_action": "Para agentless restauração in um Usuário Account Control (UAC)\nenvironment, you must provide o credentials de um domain usuário. O domain usuário\nmust be part de o local administrator group on o Windows target host." + "desc": "The provided credentials are for a local administrator user.", + "first_action": "For agentless restore in a User Account Control (UAC)", + "full_action": "For agentless restore in a User Account Control (UAC)\nenvironment, you must provide the credentials of a domain user. The domain user\nmust be part of the local administrator group on the Windows target host." }, "2345": { "code": 2345, - "desc": "Agentless restauração está não possible.", - "first_action": "Agentless arquivos ou folders restauração has falhou due to um", - "full_action": "Agentless arquivos ou folders restauração has falhou due to um\nunexpected reason. Retry o operation e if o issue persists, visit\nsupport.veritas.com. O Cohesity Technical Support site offers additional\ninformação to help you troubleshoot this issue." + "desc": "Agentless restore is not possible.", + "first_action": "Agentless files or folders restore has failed due to an", + "full_action": "Agentless files or folders restore has failed due to an\nunexpected reason. Retry the operation and if the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support site offers additional\ninformation to help you troubleshoot this issue." }, "2346": { "code": 2346, - "desc": "Operating systems do não match. Garanta que o operating system de recovery host matches com o backed-up VM operating system.", - "first_action": "Use um alternate recovery host que has same operating", - "full_action": "Use um alternate recovery host que has same operating\nsystem como o backed-up VM." + "desc": "Operating systems do not match. Ensure that the operating system of recovery host matches with the backed-up VM operating system.", + "first_action": "Use an alternate recovery host that has same operating", + "full_action": "Use an alternate recovery host that has same operating\nsystem as the backed-up VM." }, "2347": { "code": 2347, - "desc": "Falhou to retrieve o backup image operating system.", - "first_action": "Retry o operation e if o issue persists, visit", - "full_action": "Retry o operation e if o issue persists, visit\nsupport.veritas.com. O Cohesity Technical Support site offers additional\ninformação to help you troubleshoot this issue." + "desc": "Failed to retrieve the backup image operating system.", + "first_action": "Retry the operation and if the issue persists, visit", + "full_action": "Retry the operation and if the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support site offers additional\ninformation to help you troubleshoot this issue." }, "2348": { "code": 2348, - "desc": "Recovery host operating system está não compatible com o provided communication mode.", - "first_action": "O recovery host OS type e o communication type", - "full_action": "O recovery host OS type e o communication type\nmust be compatible. If o recovery host está um UNIX OS, communication type should\nbe SSH. If o recovery host está um Windows OS, o communication type should be\nWMI." + "desc": "Recovery host operating system is not compatible with the provided communication mode.", + "first_action": "The recovery host OS type and the communication type", + "full_action": "The recovery host OS type and the communication type\nmust be compatible. If the recovery host is a UNIX OS, communication type should\nbe SSH. If the recovery host is a Windows OS, the communication type should be\nWMI." }, "2349": { "code": 2349, - "desc": "Target host SSH private key está inválido.", + "desc": "Target host SSH private key is invalid.", "first_action": "IftheauthenticationtypeisSSH_KEY,verifythatthesshKey", - "full_action": "IftheauthenticationtypeisSSH_KEY,verifythatthesshKey\nfield está specified e não vazio." + "full_action": "IftheauthenticationtypeisSSH_KEY,verifythatthesshKey\nfield is specified and not empty." }, "2351": { "code": 2351, - "desc": "Inválido input foi received para configuring o service operation.", + "desc": "Invalid input was received for configuring the service operation.", "first_action": "MakesurethattheinputJSONpassedtotheAPIiscorrect", - "full_action": "MakesurethattheinputJSONpassedtotheAPIiscorrect\ncomo per o API specification. Review o nbwebservice logs para more informação." + "full_action": "MakesurethattheinputJSONpassedtotheAPIiscorrect\nas per the API specification. Review the nbwebservice logs for more information." }, "2352": { "code": 2352, - "desc": "Falhou to generate response para o specified service operation.", - "first_action": "Review o bpVMutil logs para more informação.", - "full_action": "Review o bpVMutil logs para more informação." + "desc": "Failed to generate response for the specified service operation.", + "first_action": "Review the bpVMutil logs for more information.", + "full_action": "Review the bpVMutil logs for more information." }, "2353": { "code": 2353, - "desc": "System call execution fails para o service operation.", - "first_action": "Review o bpVMutil logs e retry o operation.", - "full_action": "Review o bpVMutil logs e retry o operation." + "desc": "System call execution fails for the service operation.", + "first_action": "Review the bpVMutil logs and retry the operation.", + "full_action": "Review the bpVMutil logs and retry the operation." }, "2354": { "code": 2354, - "desc": "Unknown erro has ocorreu while o service operation request foi processed.", - "first_action": "Retry o operation e if o issue persists, visit", - "full_action": "Retry o operation e if o issue persists, visit\nsupport.veritas.com. O Cohesity Technical Support site offers additional\ninformação to help you troubleshoot this issue." + "desc": "Unknown error has occurred while the service operation request was processed.", + "first_action": "Retry the operation and if the issue persists, visit", + "full_action": "Retry the operation and if the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support site offers additional\ninformation to help you troubleshoot this issue." }, "2355": { "code": 2355, - "desc": "Falhou to start nbcctd para o specified host.", - "first_action": "Review o bpVMutil logs para qualquer errors e retry o", - "full_action": "Review o bpVMutil logs para qualquer errors e retry o\noperation." + "desc": "Failed to start nbcctd for the specified host.", + "first_action": "Review the bpVMutil logs for any errors and retry the", + "full_action": "Review the bpVMutil logs for any errors and retry the\noperation." }, "2356": { "code": 2356, - "desc": "O specified diretório caminho does não exist.", - "first_action": "Garanta que o staging diretório caminho que está specified in", - "full_action": "Garanta que o staging diretório caminho que está specified in\no CDP gateway configuration request exists on o CDP gateway." + "desc": "The specified directory path does not exist.", + "first_action": "Ensure that the staging directory path that is specified in", + "full_action": "Ensure that the staging directory path that is specified in\nthe CDP gateway configuration request exists on the CDP gateway." }, "2357": { "code": 2357, - "desc": "SQLite banco de dados erro ocorreu.", + "desc": "SQLite database error occurred.", "first_action": "CheckthestagingareafilesystemIO.Also,trytominimize", - "full_action": "CheckthestagingareafilesystemIO.Also,trytominimize\no number parallel CDP operations, if qualquer." + "full_action": "CheckthestagingareafilesystemIO.Also,trytominimize\nthe number parallel CDP operations, if any." }, "2358": { "code": 2358, - "desc": "O specified staging size validation falhou.", - "first_action": "Depending on what foi specified in o API, you need", - "full_action": "Depending on what foi specified in o API, you need\ntoincreasethesizeofthestagingdirectory.Thesizeofthestagingdirectoryshould\nnão be less than 100 GB." + "desc": "The specified staging size validation failed.", + "first_action": "Depending on what was specified in the API, you need", + "full_action": "Depending on what was specified in the API, you need\ntoincreasethesizeofthestagingdirectory.Thesizeofthestagingdirectoryshould\nnot be less than 100 GB." }, "2359": { "code": 2359, - "desc": "Falhou to register o specified virtual machine to o backup host.", - "first_action": "O nbwebservice log on o master servidor.", - "full_action": "Refer to o seguinte logs para more details:\n■ O nbwebservice log on o master servidor.\n■ O bpVMutil log e o nbcctd log on o CDP gateway" + "desc": "Failed to register the specified virtual machine to the backup host.", + "first_action": "The nbwebservice log on the master server.", + "full_action": "Refer to the following logs for more details:\n■ The nbwebservice log on the master server.\n■ The bpVMutil log and the nbcctd log on the CDP gateway" }, "2360": { "code": 2360, - "desc": "Service configuration pre-checks estão não met.", - "first_action": "Aumentar o staging banco de dados size to more than 100 GB.", - "full_action": "Executar o seguinte como appropriate:\n■ Aumentar o staging banco de dados size to more than 100 GB.\n■ Aumentar memória to more than 4 GB." + "desc": "Service configuration pre-checks are not met.", + "first_action": "Increase the staging database size to more than 100 GB.", + "full_action": "Perform the following as appropriate:\n■ Increase the staging database size to more than 100 GB.\n■ Increase memory to more than 4 GB." }, "2361": { "code": 2361, - "desc": "Falhou to configure o specified backup host.", - "first_action": "Verifique if todos de o NetBackup processos estão executando.", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique if todos de o NetBackup processos estão executando.\n■ Verifique if o specified CDP gateway está correct e reachable." + "desc": "Failed to configure the specified backup host.", + "first_action": "Check if all of the NetBackup processes are running.", + "full_action": "Perform the following as appropriate:\n■ Check if all of the NetBackup processes are running.\n■ Check if the specified CDP gateway is correct and reachable." }, "2362": { "code": 2362, - "desc": "Falhou to retrieve o service configuration.", + "desc": "Failed to retrieve the service configuration.", "first_action": "Verifythatthe/usr/openv/netbackup/nbcct/nbcct.conf", - "full_action": "Verifythatthe/usr/openv/netbackup/nbcct/nbcct.conf\narquivo exists e está accessible por o nbcctd service." + "full_action": "Verifythatthe/usr/openv/netbackup/nbcct/nbcct.conf\nfile exists and is accessible by the nbcctd service." }, "2363": { "code": 2363, - "desc": "Falhou to remove o service configuration.", - "first_action": "Review o reason por que o unlinking de o arquivo falhou.", - "full_action": "Executar o seguinte como appropriate:\n■ Review o reason por que o unlinking de o arquivo falhou.\n■ O NBCCTD service está executando, stop o service." + "desc": "Failed to remove the service configuration.", + "first_action": "Review the reason why the unlinking of the file failed.", + "full_action": "Perform the following as appropriate:\n■ Review the reason why the unlinking of the file failed.\n■ The NBCCTD service is running, stop the service." }, "2364": { "code": 2364, - "desc": "Falhou to stop o service.", - "first_action": "Verifique o state de nbcctd process.", - "full_action": "Executar o seguinte:\n■ Verifique o state de nbcctd process.\n■ Stop o nbcctd service manually." + "desc": "Failed to stop the service.", + "first_action": "Check the state of nbcctd process.", + "full_action": "Perform the following:\n■ Check the state of nbcctd process.\n■ Stop the nbcctd service manually." }, "2365": { "code": 2365, - "desc": "Watermarks validation falhou.", - "first_action": "1. Verifique o specified value para low watermark e o high watermark.", - "full_action": "Executar o seguinte:\n1. Verifique o specified value para low watermark e o high watermark.\n2. Specify o values in o given range.\n■ Low watermark - (0-99)\n■ High watermark - (1-100)\n■ Verifique que o low watermark value should be less than high watermark\nvalue." + "desc": "Watermarks validation failed.", + "first_action": "1. Check the specified value for low watermark and the high watermark.", + "full_action": "Perform the following:\n1. Check the specified value for low watermark and the high watermark.\n2. Specify the values in the given range.\n■ Low watermark - (0-99)\n■ High watermark - (1-100)\n■ Verify that the low watermark value should be less than high watermark\nvalue." }, "2367": { "code": 2367, - "desc": "O specified host already has um active configuration.", - "first_action": "Remove o currently configurado CDP gateway e", - "full_action": "Remove o currently configurado CDP gateway e\nconfigure um new gateway." + "desc": "The specified host already has an active configuration.", + "first_action": "Remove the currently configured CDP gateway and", + "full_action": "Remove the currently configured CDP gateway and\nconfigure a new gateway." }, "2368": { "code": 2368, - "desc": "O host de this VM está não in um executando state.", - "first_action": "Turn on o VM e put it into um executando state manually.", - "full_action": "Turn on o VM e put it into um executando state manually." + "desc": "The host of this VM is not in a running state.", + "first_action": "Turn on the VM and put it into a running state manually.", + "full_action": "Turn on the VM and put it into a running state manually." }, "2369": { "code": 2369, - "desc": "Falhou to unregister o specified VM from o backup host.", - "first_action": "Refer to o bpVMutil e nbcctd logs on o CDP", - "full_action": "Refer to o bpVMutil e nbcctd logs on o CDP\ngateway para more details." + "desc": "Failed to unregister the specified VM from the backup host.", + "first_action": "Refer to the bpVMutil and nbcctd logs on the CDP", + "full_action": "Refer to the bpVMutil and nbcctd logs on the CDP\ngateway for more details." }, "2370": { "code": 2370, - "desc": "Another CDP enabled backup está executando para this VM.", + "desc": "Another CDP enabled backup is running for this VM.", "first_action": "Scheduledormanuallytriggeredjobssucceedifthereare", - "full_action": "Scheduledormanuallytriggeredjobssucceedifthereare\nnão concurrent jobs executando para same VM. If jobs keep failing, review o backup\nschedule e remove concurrent jobs para this VM." + "full_action": "Scheduledormanuallytriggeredjobssucceedifthereare\nno concurrent jobs running for same VM. If jobs keep failing, review the backup\nschedule and remove concurrent jobs for this VM." }, "2372": { "code": 2372, - "desc": "You can update CDP policy apenas com o same VM.", - "first_action": "Specify o correct instance in o UUID in o policy", - "full_action": "Specify o correct instance in o UUID in o policy\nupdate request." + "desc": "You can update CDP policy only with the same VM.", + "first_action": "Specify the correct instance in the UUID in the policy", + "full_action": "Specify the correct instance in the UUID in the policy\nupdate request." }, "2373": { "code": 2373, - "desc": "O staging diretório está não vazio.", - "first_action": "Verifique que o staging diretório caminho que está specified in", - "full_action": "Verifique que o staging diretório caminho que está specified in\nCDP configuration request está vazio." + "desc": "The staging directory is not empty.", + "first_action": "Verify that the staging directory path that is specified in", + "full_action": "Verify that the staging directory path that is specified in\nCDP configuration request is empty." }, "2374": { "code": 2374, - "desc": "NetBackup Accelerator must be enabled para CDP policies.", - "first_action": "Enable o Accelerator option para o policy.", - "full_action": "Enable o Accelerator option para o policy." + "desc": "NetBackup Accelerator must be enabled for CDP policies.", + "first_action": "Enable the Accelerator option for the policy.", + "full_action": "Enable the Accelerator option for the policy." }, "2375": { "code": 2375, - "desc": "Intelligent policy está não supported para CDP policies.", - "first_action": "Change o VMware policy to não include CDP.", - "full_action": "Change o VMware policy to não include CDP." + "desc": "Intelligent policy is not supported for CDP policies.", + "first_action": "Change the VMware policy to not include CDP.", + "full_action": "Change the VMware policy to not include CDP." }, "2376": { "code": 2376, - "desc": "You não é possível select multiple VMs para backup in CDP policies.", - "first_action": "Specify um single VM in o CDP policy creation request.", - "full_action": "Specify um single VM in o CDP policy creation request." + "desc": "You cannot select multiple VMs for backup in CDP policies.", + "first_action": "Specify a single VM in the CDP policy creation request.", + "full_action": "Specify a single VM in the CDP policy creation request." }, "2377": { "code": 2377, - "desc": "O VM está already subscribed to another policy.", + "desc": "The VM is already subscribed to another policy.", "first_action": "UnsubscribetheVMfromthecurrentCDPprotectionplan", - "full_action": "UnsubscribetheVMfromthecurrentCDPprotectionplan\ne retry o operation." + "full_action": "UnsubscribetheVMfromthecurrentCDPprotectionplan\nand retry the operation." }, "2378": { "code": 2378, - "desc": "Falhou to remove o specified CDP host configuration.", - "first_action": "Unsubscribe o CDP gateway from todos o protection", - "full_action": "Unsubscribe o CDP gateway from todos o protection\nplans which use o CDP gateway e retry o operation." + "desc": "Failed to remove the specified CDP host configuration.", + "first_action": "Unsubscribe the CDP gateway from all the protection", + "full_action": "Unsubscribe the CDP gateway from all the protection\nplans which use the CDP gateway and retry the operation." }, "2379": { "code": 2379, - "desc": "Falhou to start o CDP gateway service because o memória size validation falhou.", - "first_action": "Aumentar o size de CDP host memória to greater than 4", - "full_action": "Aumentar o size de CDP host memória to greater than 4\nGB." + "desc": "Failed to start the CDP gateway service because the memory size validation failed.", + "first_action": "Increase the size of CDP host memory to greater than 4", + "full_action": "Increase the size of CDP host memory to greater than 4\nGB." }, "2380": { "code": 2380, - "desc": "Falhou to start o CDP gateway service.", - "first_action": "Review o CCT_POOL_SIZE_QUOTA_PERCENTAGE value in", - "full_action": "Review o CCT_POOL_SIZE_QUOTA_PERCENTAGE value in\no nbcct.conf arquivo e aumentar o CCT_POOL_SIZE_QUOTA_PERCENTAGE to more\nthan 1 GB." + "desc": "Failed to start the CDP gateway service.", + "first_action": "Review the CCT_POOL_SIZE_QUOTA_PERCENTAGE value in", + "full_action": "Review the CCT_POOL_SIZE_QUOTA_PERCENTAGE value in\nthe nbcct.conf file and increase the CCT_POOL_SIZE_QUOTA_PERCENTAGE to more\nthan 1 GB." }, "2381": { "code": 2381, - "desc": "Apenas cheio backup schedule está supported para CDP policies.", + "desc": "Only full backup schedule is supported for CDP policies.", "first_action": "Removeanynon-fullbackupschedulesfrompolicycreation", - "full_action": "Removeanynon-fullbackupschedulesfrompolicycreation\npayload e retry o operation." + "full_action": "Removeanynon-fullbackupschedulesfrompolicycreation\npayload and retry the operation." }, "2382": { "code": 2382, - "desc": "Insufficient space disponível on o staging caminho para o CDP gateway. NetBackup status codes 474 NetBackup status codes", - "first_action": "Aumentar o size de o staging diretório to minimum de", - "full_action": "Aumentar o size de o staging diretório to minimum de\n100 GB." + "desc": "Insufficient space available on the staging path for the CDP gateway. NetBackup status codes 474 NetBackup status codes", + "first_action": "Increase the size of the staging directory to minimum of", + "full_action": "Increase the size of the staging directory to minimum of\n100 GB." }, "2383": { "code": 2383, - "desc": "NBCCTD está down para o specified host.", - "first_action": "Garanta que o NBCCTD service está executando on o CDP", - "full_action": "Garanta que o NBCCTD service está executando on o CDP\ngateway." + "desc": "NBCCTD is down for the specified host.", + "first_action": "Ensure that the NBCCTD service is running on the CDP", + "full_action": "Ensure that the NBCCTD service is running on the CDP\ngateway." }, "2384": { "code": 2384, - "desc": "Armazenamento caminho does não have um supported arquivo system.", - "first_action": "Change o staging caminho to um non-root arquivo system com um", - "full_action": "Change o staging caminho to um non-root arquivo system com um\nsupported arquivo system type (XFS, EXT3, EXT4, NFS, VxFS)." + "desc": "Storage path does not have a supported file system.", + "first_action": "Change the staging path to a non-root file system with a", + "full_action": "Change the staging path to a non-root file system with a\nsupported file system type (XFS, EXT3, EXT4, NFS, VxFS)." }, "2385": { "code": 2385, - "desc": "Providedpathistotherootfilesystem.ProvideaCDPstagingareapath on non-root arquivo system.", + "desc": "Providedpathistotherootfilesystem.ProvideaCDPstagingareapath on non-root file system.", "first_action": "Changethestagingdirectorypathtoanon-rootfilesystem.", "full_action": "Changethestagingdirectorypathtoanon-rootfilesystem." }, "2386": { "code": 2386, - "desc": "Não mount point found para o provided staging area caminho.", - "first_action": "Change o staging caminho to um non-root arquivo system com um", - "full_action": "Change o staging caminho to um non-root arquivo system com um\nvalid mount point." + "desc": "No mount point found for the provided staging area path.", + "first_action": "Change the staging path to a non-root file system with a", + "full_action": "Change the staging path to a non-root file system with a\nvalid mount point." }, "2387": { "code": 2387, - "desc": "Não é possível update accelerator forced rescan property, para o CDP policy.", - "first_action": "Updating o accelerator forced rescan attribute para schedules in CDP policy está", - "full_action": "Executar o seguinte como appropriate:\n■ Updating o accelerator forced rescan attribute para schedules in CDP policy está\nnão allowed.\n■ Excluir o current schedules usando update (PUT) API, e create new schedule\ncom o accelerator forced rescan attribute value que you desejar to set." + "desc": "Cannot update accelerator forced rescan property, for the CDP policy.", + "first_action": "Updating the accelerator forced rescan attribute for schedules in CDP policy is", + "full_action": "Perform the following as appropriate:\n■ Updating the accelerator forced rescan attribute for schedules in CDP policy is\nnot allowed.\n■ Delete the current schedules using update (PUT) API, and create new schedule\nwith the accelerator forced rescan attribute value that you want to set." }, "2388": { "code": 2388, - "desc": "Apenas one accelerator force rescan schedule está supported para continuous data protection policies.", - "first_action": "Remove qualquer extra acceleratorForcedRescan enabled", - "full_action": "Remove qualquer extra acceleratorForcedRescan enabled\nschedules." + "desc": "Only one accelerator force rescan schedule is supported for continuous data protection policies.", + "first_action": "Remove any extra acceleratorForcedRescan enabled", + "full_action": "Remove any extra acceleratorForcedRescan enabled\nschedules." }, "2389": { "code": 2389, - "desc": "Onlyoneacceleratorforcerescanschedule,andatleastonefullbackup schedule com não accelerator force rescan, estão requerido para CDP policies.", - "first_action": "Remove qualquer extra acceleratorForcedRescan enabled schedules.", - "full_action": "Executar o seguinte como appropriate:\n■ Remove qualquer extra acceleratorForcedRescan enabled schedules.\n■ Add at least one regular, cheio backup schedule in um CDP policy." + "desc": "Onlyoneacceleratorforcerescanschedule,andatleastonefullbackup schedule with no accelerator force rescan, are required for CDP policies.", + "first_action": "Remove any extra acceleratorForcedRescan enabled schedules.", + "full_action": "Perform the following as appropriate:\n■ Remove any extra acceleratorForcedRescan enabled schedules.\n■ Add at least one regular, full backup schedule in a CDP policy." }, "2390": { "code": 2390, - "desc": "Inválido backup host.", - "first_action": "Specify um correct ou um reachable backup host.", - "full_action": "Specify um correct ou um reachable backup host." + "desc": "Invalid backup host.", + "first_action": "Specify a correct or a reachable backup host.", + "full_action": "Specify a correct or a reachable backup host." }, "2391": { "code": 2391, - "desc": "Não é possível subscribe o VM. Não space disponível in o staging area.", - "first_action": "Subscribe o VM to another gateway.", - "full_action": "Subscribe o VM to another gateway." + "desc": "Cannot subscribe the VM. No space available in the staging area.", + "first_action": "Subscribe the VM to another gateway.", + "full_action": "Subscribe the VM to another gateway." }, "2392": { "code": 2392, - "desc": "Não é possível subscribe o VM. Insufficient memória disponível.", - "first_action": "Subscribe o VM to another gateway.", - "full_action": "Subscribe o VM to another gateway." + "desc": "Cannot subscribe the VM. Insufficient memory available.", + "first_action": "Subscribe the VM to another gateway.", + "full_action": "Subscribe the VM to another gateway." }, "2393": { "code": 2393, - "desc": "O nbcctd service usuário on o CDP host does não have sufficient permissions to o staging diretório.", - "first_action": "O nbcctd usuário must have sufficient permissions to be", - "full_action": "O nbcctd usuário must have sufficient permissions to be\nable to access o staging diretório." + "desc": "The nbcctd service user on the CDP host does not have sufficient permissions to the staging directory.", + "first_action": "The nbcctd user must have sufficient permissions to be", + "full_action": "The nbcctd user must have sufficient permissions to be\nable to access the staging directory." }, "2395": { "code": 2395, - "desc": "VM quota size in GB validation has falhou para CDP configuration.", - "first_action": "You must enter um value de o VM quota size (in GB) que", - "full_action": "You must enter um value de o VM quota size (in GB) que\nestá within 10 GB to 1024 GB." + "desc": "VM quota size in GB validation has failed for CDP configuration.", + "first_action": "You must enter a value of the VM quota size (in GB) that", + "full_action": "You must enter a value of the VM quota size (in GB) that\nis within 10 GB to 1024 GB." }, "2396": { "code": 2396, "desc": "VMquotareservepercentagevalidationhasfailedforCDPconfiguration.", - "first_action": "You must enter um value para o VM quota reserve", - "full_action": "You must enter um value para o VM quota reserve\npercentage que está within o limits de 25 to 50." + "first_action": "You must enter a value for the VM quota reserve", + "full_action": "You must enter a value for the VM quota reserve\npercentage that is within the limits of 25 to 50." }, "2397": { "code": 2397, - "desc": "Max full-sync validation has falhou para CDP configuration.", - "first_action": "You must enter um value para o max full-sync que está within", - "full_action": "You must enter um value para o max full-sync que está within\no limits de 2 to 25." + "desc": "Max full-sync validation has failed for CDP configuration.", + "first_action": "You must enter a value for the max full-sync that is within", + "full_action": "You must enter a value for the max full-sync that is within\nthe limits of 2 to 25." }, "2398": { "code": 2398, - "desc": "VMquotasizeinGBvalidationhasfailedforCDPconfigurationbecause o VM quota size in GB must be less than staging space.", - "first_action": "You must enter um value para o VM quota size in GB que", - "full_action": "You must enter um value para o VM quota size in GB que\nestá less than o staging area size." + "desc": "VMquotasizeinGBvalidationhasfailedforCDPconfigurationbecause the VM quota size in GB must be less than staging space.", + "first_action": "You must enter a value for the VM quota size in GB that", + "full_action": "You must enter a value for the VM quota size in GB that\nis less than the staging area size." }, "2399": { "code": 2399, - "desc": "CDP service configuration foi successful but falhou to add CDP host configurado entry in o bp.conf arquivo on o CDP gateway.", - "first_action": "Verifique que o bp.conf arquivo está present at install_path/openv/netbackup", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique que o bp.conf arquivo está present at install_path/openv/netbackup\nlocation e o service usuário has permissão to modify.\n■ You can also add theCCT_IS_HOST_CONFIGURED=YESentry manually e try o\nconfiguration operation again." + "desc": "CDP service configuration was successful but failed to add CDP host configured entry in the bp.conf file on the CDP gateway.", + "first_action": "Verify that the bp.conf file is present at install_path/openv/netbackup", + "full_action": "Perform the following as appropriate:\n■ Verify that the bp.conf file is present at install_path/openv/netbackup\nlocation and the service user has permission to modify.\n■ You can also add theCCT_IS_HOST_CONFIGURED=YESentry manually and try the\nconfiguration operation again." }, "2400": { "code": 2400, - "desc": "CDP configuration migration está não complete. First start o CDP service manually e complete o migration.", - "first_action": "First, start o CDP service manually e then complete", - "full_action": "First, start o CDP service manually e then complete\no migration (upgrade). Next, try o configuration update operation, if necessary." + "desc": "CDP configuration migration is not complete. First start the CDP service manually and complete the migration.", + "first_action": "First, start the CDP service manually and then complete", + "full_action": "First, start the CDP service manually and then complete\nthe migration (upgrade). Next, try the configuration update operation, if necessary." }, "2401": { "code": 2401, - "desc": "Não é possível conectar to o back-end services on o primary servidor ou o CDP gateway.", - "first_action": "Start o services on o CDP gateway e o primary", - "full_action": "Start o services on o CDP gateway e o primary\nservidor usando bp.start_all. Also, verifique que there está rede connectivity between\no primary servidor e o CDP gateway." + "desc": "Cannot connect to the back-end services on the primary server or the CDP gateway.", + "first_action": "Start the services on the CDP gateway and the primary", + "full_action": "Start the services on the CDP gateway and the primary\nserver using bp.start_all. Also, verify that there is network connectivity between\nthe primary server and the CDP gateway." }, "2402": { "code": 2402, - "desc": "Não é possível executar o solicitado CDP operation because um internal erro ocorreu.", - "first_action": "Review o nbwebservice, bprd, bpVMutil, e o", - "full_action": "Review o nbwebservice, bprd, bpVMutil, e o\nnbcctd logs para more informação. Retry o operation e if o issue persists, visit\nsupport.veritas.com. O Cohesity Technical Support website site offers additional\ninformação to help you troubleshoot this issue." + "desc": "Cannot perform the requested CDP operation because an internal error occurred.", + "first_action": "Review the nbwebservice, bprd, bpVMutil, and the", + "full_action": "Review the nbwebservice, bprd, bpVMutil, and the\nnbcctd logs for more information. Retry the operation and if the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support website site offers additional\ninformation to help you troubleshoot this issue." }, "2450": { "code": 2450, - "desc": "Target host operating system está não supported para o agentless arquivos ou folders restauração.", - "first_action": "SUSE Linux Enterprise Servidor, Microsoft Windows, e", - "full_action": "SUSE Linux Enterprise Servidor, Microsoft Windows, e\nRed Hat Enterprise Linux (RHEL) estão supported platforms. Refer to o NetBackup\nCliente Compatibility List para o supported platforms para agentless restauração." + "desc": "Target host operating system is not supported for the agentless files or folders restore.", + "first_action": "SUSE Linux Enterprise Server, Microsoft Windows, and", + "full_action": "SUSE Linux Enterprise Server, Microsoft Windows, and\nRed Hat Enterprise Linux (RHEL) are supported platforms. Refer to the NetBackup\nClient Compatibility List for the supported platforms for agentless restore." }, "2451": { "code": 2451, - "desc": "Inválido target host usuário name ou password.", - "first_action": "Verifique que o usuário name e password fields, in o", - "full_action": "Verifique que o usuário name e password fields, in o\nauthenticationdetailsoftherecoveryandpre-recoverycheckrequest,arespecified\ne estão não vazio." + "desc": "Invalid target host user name or password.", + "first_action": "Verify that the user name and password fields, in the", + "full_action": "Verify that the user name and password fields, in the\nauthenticationdetailsoftherecoveryandpre-recoverycheckrequest,arespecified\nand are not empty." }, "2504": { "code": 2504, - "desc": "Direct expiration de um mirror copy está não allowed", - "first_action": "Nenhum", - "full_action": "Nenhum" + "desc": "Direct expiration of a mirror copy is not allowed", + "first_action": "None", + "full_action": "None" }, "2505": { "code": 2505, - "desc": "Não foi possível to conectar to o banco de dados", - "first_action": "In this case, o semmni value foi insufficient at 128. Por", - "full_action": "In this case, o semmni value foi insufficient at 128. Por\nincreasingthisvalueto1024,theODBCconnectionwassuccessfulandNetBackup\nthenransuccessfully.Althoughthiscouldaffectotherplatforms,thiserrorhasbeen\nseen in multiple RedHat Enterprise Linux (RHEL) environments, usually when o\nRHELsystemistheNetBackupmasterserver.AnysupportedversionofNetBackup\ncould be affected por this environmental issue. Veja o Recomendada NetBackup\nUNIX / Linux semaphore tuning values (Linux/Solaris/HP-UX/AIX) article at o\nseguinte location para general recommendations e refer to o platform vendor\nsupport para additional details:\nhttps://www.veritas.com/support/en_US/article.100023842" + "desc": "Unable to connect to the database", + "first_action": "In this case, the semmni value was insufficient at 128. By", + "full_action": "In this case, the semmni value was insufficient at 128. By\nincreasingthisvalueto1024,theODBCconnectionwassuccessfulandNetBackup\nthenransuccessfully.Althoughthiscouldaffectotherplatforms,thiserrorhasbeen\nseen in multiple RedHat Enterprise Linux (RHEL) environments, usually when the\nRHELsystemistheNetBackupmasterserver.AnysupportedversionofNetBackup\ncould be affected by this environmental issue. See the Recommended NetBackup\nUNIX / Linux semaphore tuning values (Linux/Solaris/HP-UX/AIX) article at the\nfollowing location for general recommendations and refer to the platform vendor\nsupport for additional details:\nhttps://www.veritas.com/support/en_US/article.100023842" }, "2517": { "code": 2517, - "desc": "Backup set identifier may apenas contain a-z, A-Z, 0-9 e .-+_", + "desc": "Backup set identifier may only contain a-z, A-Z, 0-9 and .-+_", "first_action": "Removetheinvalidcharacterfromthebackupsetidentifier.", - "full_action": "Removetheinvalidcharacterfromthebackupsetidentifier.\nThis value está specified in o Attributes tab de o GUI Policy utility." + "full_action": "Removetheinvalidcharacterfromthebackupsetidentifier.\nThis value is specified in the Attributes tab of the GUI Policy utility." }, "2521": { "code": 2521, - "desc": "Datafile copy tag may apenas contain a-z, A-Z, 0-9 e .-+_", - "first_action": "Remove o inválido character from o Datafile copy tag.", - "full_action": "Remove o inválido character from o Datafile copy tag.\nThis value está specified in o Oracle tab de o GUI Policy utility." + "desc": "Datafile copy tag may only contain a-z, A-Z, 0-9 and .-+_", + "first_action": "Remove the invalid character from the Datafile copy tag.", + "full_action": "Remove the invalid character from the Datafile copy tag.\nThis value is specified in the Oracle tab of the GUI Policy utility." }, "2522": { "code": 2522, - "desc": "Oracle policy não é possível include um pluggable banco de dados com um FRA backup.", + "desc": "Oracle policy cannot include a pluggable database with a FRA backup.", "first_action": "ChecktheOracleIntelligentPolicy.IfthepolicyhasProtect", - "full_action": "ChecktheOracleIntelligentPolicy.IfthepolicyhasProtect\nInstances e Databases selected e includes pluggable databases, then o\nbackup selection não é possível be Fast Recovery Area (FRA). You can either select um\ndifferent backup selection ou select o Oracle 12c instance e Fast Recovery\nArea (FRA)." + "full_action": "ChecktheOracleIntelligentPolicy.IfthepolicyhasProtect\nInstances and Databases selected and includes pluggable databases, then the\nbackup selection cannot be Fast Recovery Area (FRA). You can either select a\ndifferent backup selection or select the Oracle 12c instance and Fast Recovery\nArea (FRA)." }, "2523": { "code": 2523, - "desc": "Falhou to add cliente to NetBackup configuration.", - "first_action": "Save o nbemm e bpdbm logs e contate Cohesity", - "full_action": "Save o nbemm e bpdbm logs e contate Cohesity\nTechnical Support." + "desc": "Failed to add client to NetBackup configuration.", + "first_action": "Save the nbemm and bpdbm logs and contact Cohesity", + "full_action": "Save the nbemm and bpdbm logs and contact Cohesity\nTechnical Support." }, "2524": { "code": 2524, - "desc": "Catalogbackupfailedbecausethepassphraseforthedisasterrecovery package está não set.", - "first_action": "In o NetBackup Administration Console, expand Security Management", - "full_action": "To set o passphrase para o disaster recovery package,\ndo one de o seguinte:\n■ In o NetBackup Administration Console, expand Security Management\n>GlobalSecuritySettings.OntheDisasterRecoverytab,setthepassphrase.\n■ Use o nbseccmd -drpkgpassphrase comando." + "desc": "Catalogbackupfailedbecausethepassphraseforthedisasterrecovery package is not set.", + "first_action": "In the NetBackup Administration Console, expand Security Management", + "full_action": "To set the passphrase for the disaster recovery package,\ndo one of the following:\n■ In the NetBackup Administration Console, expand Security Management\n>GlobalSecuritySettings.OntheDisasterRecoverytab,setthepassphrase.\n■ Use the nbseccmd -drpkgpassphrase command." }, "2525": { "code": 2525, - "desc": "O passphrase para o disaster recovery package está não set. You must set it para o catalog backups to be successful.", - "first_action": "In o NetBackup Administration Console, expand Security Management", - "full_action": "To set o passphrase para o disaster recovery package,\ndo one de o seguinte:\n■ In o NetBackup Administration Console, expand Security Management\n>GlobalSecuritySettings.OntheDisasterRecoverytab,setthepassphrase.\n■ Use o nbseccmd -drpkgpassphrase comando." + "desc": "The passphrase for the disaster recovery package is not set. You must set it for the catalog backups to be successful.", + "first_action": "In the NetBackup Administration Console, expand Security Management", + "full_action": "To set the passphrase for the disaster recovery package,\ndo one of the following:\n■ In the NetBackup Administration Console, expand Security Management\n>GlobalSecuritySettings.OntheDisasterRecoverytab,setthepassphrase.\n■ Use the nbseccmd -drpkgpassphrase command." }, "2526": { "code": 2526, - "desc": "O master servidor certificate não é possível be salvo up from Windows certificate store during catalog backup.", - "first_action": "O private key de o master server’s certificate arquivo está marked como exportable", - "full_action": "Garanta o seguinte to resolve o issue:\n■ O private key de o master server’s certificate arquivo está marked como exportable\nwhile you store it in o Windows certificate store.\n■ O certificate está disponível como um arquivo in o arquivo system e o ECA_CERT_PATH,\nECA_TRUST_STORE_PATH,andECA_PRIVATE_KEY_PATHconfigurationoptionsare\nset to appropriate values. Para more informação on o NetBackup configuration\noptions, refer to o NetBackup Administrator’s Guide, Volume I." + "desc": "The master server certificate cannot be backed up from Windows certificate store during catalog backup.", + "first_action": "The private key of the master server’s certificate file is marked as exportable", + "full_action": "Ensure the following to resolve the issue:\n■ The private key of the master server’s certificate file is marked as exportable\nwhile you store it in the Windows certificate store.\n■ The certificate is available as a file in the file system and the ECA_CERT_PATH,\nECA_TRUST_STORE_PATH,andECA_PRIVATE_KEY_PATHconfigurationoptionsare\nset to appropriate values. For more information on the NetBackup configuration\noptions, refer to the NetBackup Administrator’s Guide, Volume I." }, "2527": { "code": 2527, - "desc": "Changes estão não allowed para um template que um protection plan manages.", - "first_action": "Use o NetBackup web UI to update ou excluir protection", - "full_action": "Use o NetBackup web UI to update ou excluir protection\nplan." + "desc": "Changes are not allowed for a template that a protection plan manages.", + "first_action": "Use the NetBackup web UI to update or delete protection", + "full_action": "Use the NetBackup web UI to update or delete protection\nplan." }, "2528": { "code": 2528, - "desc": "Changes estão não allowed para um SLP que um protection plan manages.", - "first_action": "Use o NetBackup web UI to update ou excluir protection", - "full_action": "Use o NetBackup web UI to update ou excluir protection\nplan." + "desc": "Changes are not allowed for an SLP that a protection plan manages.", + "first_action": "Use the NetBackup web UI to update or delete protection", + "full_action": "Use the NetBackup web UI to update or delete protection\nplan." }, "2531": { "code": 2531, - "desc": "Thedisasterrecoverypackagewassuccessfullycreated.However,one ou more users who have permissions to o identity arquivos from o package do não exist on o system.", - "first_action": "Identify whether o Access Control Lists (ACL) de these", - "full_action": "Identify whether o Access Control Lists (ACL) de these\nnon-existing users estão requerido ou não. Review e compare o ACLs de o same\nidentity arquivo on um host onde NetBackup está freshly instalado. If these users do não\nneed to have permissão to o identity arquivos, excluir o ACLs de o associated\nidentity arquivos.\nRetrytheoperationandiftheissuepersists,visitsupport.veritas.com.TheCohesity\nTechnical Support site offers additional informação to help you troubleshoot this\nissue." + "desc": "Thedisasterrecoverypackagewassuccessfullycreated.However,one or more users who have permissions to the identity files from the package do not exist on the system.", + "first_action": "Identify whether the Access Control Lists (ACL) of these", + "full_action": "Identify whether the Access Control Lists (ACL) of these\nnon-existing users are required or not. Review and compare the ACLs of the same\nidentity file on a host where NetBackup is freshly installed. If these users do not\nneed to have permission to the identity files, delete the ACLs of the associated\nidentity files.\nRetrytheoperationandiftheissuepersists,visitsupport.veritas.com.TheCohesity\nTechnical Support site offers additional information to help you troubleshoot this\nissue." }, "2532": { "code": 2532, - "desc": "Schedule copies have armazenamento units from different mídia servers.", - "first_action": "If you use multiple copies para um schedule, make sure que", - "full_action": "If you use multiple copies para um schedule, make sure que\no armazenamento units que estão assigned to each schedule estão from same mídia servidor." + "desc": "Schedule copies have storage units from different media servers.", + "first_action": "If you use multiple copies for a schedule, make sure that", + "full_action": "If you use multiple copies for a schedule, make sure that\nthe storage units that are assigned to each schedule are from same media server." }, "2607": { "code": 2607, - "desc": "Servidor informação está não disponível.", - "first_action": "Garanta que o MySQL installation está present, e o", - "full_action": "Garanta que o MySQL installation está present, e o\nservices estão up.\nIf you need to contate Cohesity Technical Support, you must have o ncfnbcs log\nfrom o NetBackup cliente host." + "desc": "Server information is not available.", + "first_action": "Ensure that the MySQL installation is present, and the", + "full_action": "Ensure that the MySQL installation is present, and the\nservices are up.\nIf you need to contact Cohesity Technical Support, you must have the ncfnbcs log\nfrom the NetBackup client host." }, "2610": { "code": 2610, - "desc": "MySQL library caminho está não present in Backup Selection como well como environment variables.", - "first_action": "Set o LIB_MYSQL_CLIENT Caminho in o Environment", - "full_action": "Set o LIB_MYSQL_CLIENT Caminho in o Environment\nVariables e o Caminho Variable para Windows e Linux, respectively. Also, garanta\no symbolic link para o MySQL cliente library está correctly created in o same\nLIB_MYSQL_CLIENT diretório.\nIf you need to contate Cohesity Technical Support, you must have o ncfnbcs e\nbphdb logs from o NetBackup cliente host." + "desc": "MySQL library path is not present in Backup Selection as well as environment variables.", + "first_action": "Set the LIB_MYSQL_CLIENT Path in the Environment", + "full_action": "Set the LIB_MYSQL_CLIENT Path in the Environment\nVariables and the Path Variable for Windows and Linux, respectively. Also, ensure\nthe symbolic link for the MySQL client library is correctly created in the same\nLIB_MYSQL_CLIENT directory.\nIf you need to contact Cohesity Technical Support, you must have the ncfnbcs and\nbphdb logs from the NetBackup client host." }, "2611": { "code": 2611, - "desc": "Banco de dados name foi não found para o MySQL backup dump.", - "first_action": "Garanta que o protection plan está properly attached com", - "full_action": "Garanta que o protection plan está properly attached com\no databases to be salvo up.\nIf you need to contate Cohesity Technical Support, you must have o ncfnbcs e\nbphdb logs from o NetBackup cliente host." + "desc": "Database name was not found for the MySQL backup dump.", + "first_action": "Ensure that the protection plan is properly attached with", + "full_action": "Ensure that the protection plan is properly attached with\nthe databases to be backed up.\nIf you need to contact Cohesity Technical Support, you must have the ncfnbcs and\nbphdb logs from the NetBackup client host." }, "2612": { "code": 2612, - "desc": "Inválido library caminho foi given para MySQL backup.", - "first_action": "Set o LIB_MYSQL_CLIENT Caminho in o Environment", - "full_action": "Set o LIB_MYSQL_CLIENT Caminho in o Environment\nVariables e Caminho Variable para Windows e Linux, respectively. Also, garanta o\nsymbolic link para o MySQL cliente library está correctly created in o same\nLIB_MYSQL_CLIENT diretório.\nIf you need to contate Cohesity Technical Support, you must have o ncfnbcs e\nbphdb logs from o NetBackup cliente host." + "desc": "Invalid library path was given for MySQL backup.", + "first_action": "Set the LIB_MYSQL_CLIENT Path in the Environment", + "full_action": "Set the LIB_MYSQL_CLIENT Path in the Environment\nVariables and Path Variable for Windows and Linux, respectively. Also, ensure the\nsymbolic link for the MySQL client library is correctly created in the same\nLIB_MYSQL_CLIENT directory.\nIf you need to contact Cohesity Technical Support, you must have the ncfnbcs and\nbphdb logs from the NetBackup client host." }, "2613": { "code": 2613, - "desc": "Não foi possível to obtain MySQL credentials.", - "first_action": "Garanta que o specific banco de dados credentials estão correct.", - "full_action": "Garanta que o specific banco de dados credentials estão correct.\nIf you need to contate Cohesity Technical Support, you must have o bphdb log\nfrom o NetBackup cliente host." + "desc": "Unable to obtain MySQL credentials.", + "first_action": "Ensure that the specific database credentials are correct.", + "full_action": "Ensure that the specific database credentials are correct.\nIf you need to contact Cohesity Technical Support, you must have the bphdb log\nfrom the NetBackup client host." }, "2800": { "code": 2800, - "desc": "Standard policy restauração erro", - "first_action": "Garanta que o cliente servidor list contains entradas para o master servidor e qualquer", - "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Garanta que o cliente servidor list contains entradas para o master servidor e qualquer\nmídia servers que can be used during um backup ou restauração.\n■ Examine o status ou o progress log on o cliente para messages about por que\no restauração falhou. Also, verifique o Todos Log Entradas relatório on o servidor.\n■ Verifique o seguinte logs para additional falha informação:\n■ NetBackup tar log\n■ Master servidor: bprd, nbjm\n■ Mídia servidor: bpbrm, bptm, bpdm\n■ Cliente: tar\n■ Make sure que o requerido mídia servidor está disponível para o restauração, ou use o\nMídia host override option.\n■ Verifique que o mídia que está requerido para o restauração está present e que o robot\nhas been inventoried.\n■ Verifique que não rede issues exist between o mídia servidor e o cliente.\n■ Select o original caminho que está listed in o Backup Selections tab." + "desc": "Standard policy restore error", + "first_action": "Ensure that the client server list contains entries for the master server and any", + "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Ensure that the client server list contains entries for the master server and any\nmedia servers that can be used during a backup or restore.\n■ Examine the status or the progress log on the client for messages about why\nthe restore failed. Also, check the All Log Entries report on the server.\n■ Check the following logs for additional failure information:\n■ NetBackup tar log\n■ Master server: bprd, nbjm\n■ Media server: bpbrm, bptm, bpdm\n■ Client: tar\n■ Make sure that the required media server is available for the restore, or use the\nMedia host override option.\n■ Verify that the media that is required for the restore is present and that the robot\nhas been inventoried.\n■ Verify that no network issues exist between the media server and the client.\n■ Select the original path that is listed in the Backup Selections tab." }, "2801": { "code": 2801, - "desc": "Oracle policy restauração erro", - "first_action": "Garanta que o cliente servidor list contains entradas para o master servidor e qualquer", - "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Garanta que o cliente servidor list contains entradas para o master servidor e qualquer\nmídia servers que can be used during um backup ou restauração.\n■ Examine o status ou o progress log on o cliente para messages on por que o\nrestauração falhou. Also, verifique o Todos Log Entradas relatório on o servidor.\n■ Verifique ownership e permissão on directories onde arquivos estão restored.\n■ Verifique ownership e permissão on o Oracle instance que you restauração.\n■ Verifique o NetBackup dbclient e user_ops logs para additional falha\ninformação.\n■ If restoring to um alternate cliente usando RMAN, more informação está disponível in\no seguinte technical article:\nhttps://www.veritas.com/support/en_US/article.100022605\nVerifique que o Oracle usuário on o cliente can successfully communicate com o\nmaster servidor por usando o bpclntcmd -pn comando.\n■ Verifique que o Oracle usuário on o cliente can veja o backup images on o\nmaster por usando o bplist comando.\n■ On UNIX e Linux hosts, verifique que o oracle usuário has sufficient permissions\nto ler /etc/services, /etc/nsswitch.conf, e\n/usr/openv/netbackup/bp.conf.\n■ Garanta thatthe Oracle databaseis linked correctly, according to o NetBackup\nforOracleAdministrator'sGuide(forexample,$ORACLE_HOME/lib/libobk.so).\nMore informação está disponível in o seguinte technical article:\nhttps://www.veritas.com/support/en_US/article.100021454\n■ Correct o problemas que you find e retry o restauração." + "desc": "Oracle policy restore error", + "first_action": "Ensure that the client server list contains entries for the master server and any", + "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Ensure that the client server list contains entries for the master server and any\nmedia servers that can be used during a backup or restore.\n■ Examine the status or the progress log on the client for messages on why the\nrestore failed. Also, check the All Log Entries report on the server.\n■ Check ownership and permission on directories where files are restored.\n■ Check ownership and permission on the Oracle instance that you restore.\n■ Check the NetBackup dbclient and user_ops logs for additional failure\ninformation.\n■ If restoring to an alternate client using RMAN, more information is available in\nthe following technical article:\nhttps://www.veritas.com/support/en_US/article.100022605\nCheck that the Oracle user on the client can successfully communicate with the\nmaster server by using the bpclntcmd -pn command.\n■ Check that the Oracle user on the client can see the backup images on the\nmaster by using the bplist command.\n■ On UNIX and Linux hosts, check that the oracle user has sufficient permissions\nto read /etc/services, /etc/nsswitch.conf, and\n/usr/openv/netbackup/bp.conf.\n■ Ensure thatthe Oracle databaseis linked correctly, according to the NetBackup\nforOracleAdministrator'sGuide(forexample,$ORACLE_HOME/lib/libobk.so).\nMore information is available in the following technical article:\nhttps://www.veritas.com/support/en_US/article.100021454\n■ Correct the problems that you find and retry the restore." }, "2802": { "code": 2802, - "desc": "Informix-On-BAR policy restauração erro", - "first_action": "Garanta que o cliente servidor list contains entradas para o master servidor e qualquer", - "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Garanta que o cliente servidor list contains entradas para o master servidor e qualquer\nmídia servers que can be used during um backup ou restauração.\n■ Examine o status ou o progress log on o cliente para messages on por que o\nrestauração falhou. Also, verifique o Todos Log Entradas relatório on o servidor.\n■ Verifique ownership e permissão on directories onde arquivos estão restored.\n■ Verifique ownership e permissão on o Informix instance que you restauração.\n■ Verifique o NetBackup infxbsa e user_ops logs from o cliente, e o bprd\nlog from o master servidor para additional falha informação.\n■ Verifique o Informix BAR_ACT_LOG, BAR_DEBUG_LOG, e MSGPATH logs\npara additional falha informação.\n■ Para large banco de dados restores, you may need to aumentar o cliente ler tempo limite esgotado\nvalue.\n■ If you estão restoring to um alternate cliente, review o checklist in o seguinte\narticle:\nhttps://www.veritas.com/support/en_US/article.100010442\n■ Correct o problemas que you find e retry o restauração." + "desc": "Informix-On-BAR policy restore error", + "first_action": "Ensure that the client server list contains entries for the master server and any", + "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Ensure that the client server list contains entries for the master server and any\nmedia servers that can be used during a backup or restore.\n■ Examine the status or the progress log on the client for messages on why the\nrestore failed. Also, check the All Log Entries report on the server.\n■ Check ownership and permission on directories where files are restored.\n■ Check ownership and permission on the Informix instance that you restore.\n■ Check the NetBackup infxbsa and user_ops logs from the client, and the bprd\nlog from the master server for additional failure information.\n■ Check the Informix BAR_ACT_LOG, BAR_DEBUG_LOG, and MSGPATH logs\nfor additional failure information.\n■ For large database restores, you may need to increase the client read timeout\nvalue.\n■ If you are restoring to an alternate client, review the checklist in the following\narticle:\nhttps://www.veritas.com/support/en_US/article.100010442\n■ Correct the problems that you find and retry the restore." }, "2803": { "code": 2803, - "desc": "Sybase policy restauração erro", - "first_action": "Garanta que o cliente servidor list contains entradas para o master servidor e qualquer", - "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Garanta que o cliente servidor list contains entradas para o master servidor e qualquer\nmídia servers que can be used during um backup ou restauração.\n■ Examine o status ou o progress log on o cliente para messages on por que o\nrestauração falhou. Also, verifique o Todos Log Entradas relatório on o servidor.\n■ Verifique ownership e permissão on o Sybase instance que you restauração e\non o directories onde arquivos estão restored.\n■ Verifique o NetBackup sybackup log para additional falha informação.\n■ Create o seguinte log folders, then retry o restauração:\nOn o cliente:\n/usr/openv/netbackup/logs/bphdb\n/usr/openv/netbackup/logs/bprestore\n/usr/openv/netbackup/logs/tar\n/usr/openv/netbackup/logs/sybackup\nOn o mídia servidor:\n/usr/openv/netbackup/logs/bptm\n/usr/openv/netbackup/logs/bpbrm\nOn o master servidor:\n/usr/openv/netbackup/logs/bprd\n■ Correct o problemas que you find e retry o restauração.\nTo set o debug level on UNIX e Linux clients, enter o seguinte line in o\nbp.conf arquivo:\nVERBOSE = 5\nPara um Sybase alternate cliente restauração, o usuário ID (UID) de o restoring Sybase\nbackup servidor must match o UID de o Sybase backup servidor from o source\nhost.\nPara um alternate cliente restauração, authorize o alternate cliente to access images para\no original cliente.\nVerifique que o alternate cliente can browse o backup images para o original cliente:\n# /usr/openv/netbackup/bin/bplist -C -t 7 -l -R /\n# install_path\\netbackup\\bin\\bplist -t 7 -l -R /\nOn o alternate cliente, use o bpclntcmd comando to test connectivity e name\nresolution. O comando should display o name de o master servidor on o first\nline. O second line must contain o IP address de o rede interface que o\nalternate cliente used when communicating com o master servidor. O first word\non o second line está o name de o alternate cliente como resolved on o master\nservidor from o IP address. O second word on o second line may be 'NULL' if\nthealternateclientisnotbeingbackedup.Otherwise,itisthenameofthealternate\ncliente (ou um alias) which está defined in um backup policy on o master servidor.\n# /usr/openv/netbackup/bin/bpclntcmd -pn\nMakesurethatCLIENT_READ_TIMEOUTonthealternateclientandmediaserver\nestá set large enough to allow o tapes to be ler, o data transferred, e o\nbanco de dados instance to gravar o data to disco.\nVeja o seguinte technical article para informação about o steps para um Sybase\nalternative cliente restauração operation:\nhttps://www.veritas.com/support/en_US/article.100016002" + "desc": "Sybase policy restore error", + "first_action": "Ensure that the client server list contains entries for the master server and any", + "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Ensure that the client server list contains entries for the master server and any\nmedia servers that can be used during a backup or restore.\n■ Examine the status or the progress log on the client for messages on why the\nrestore failed. Also, check the All Log Entries report on the server.\n■ Check ownership and permission on the Sybase instance that you restore and\non the directories where files are restored.\n■ Check the NetBackup sybackup log for additional failure information.\n■ Create the following log folders, then retry the restore:\nOn the client:\n/usr/openv/netbackup/logs/bphdb\n/usr/openv/netbackup/logs/bprestore\n/usr/openv/netbackup/logs/tar\n/usr/openv/netbackup/logs/sybackup\nOn the media server:\n/usr/openv/netbackup/logs/bptm\n/usr/openv/netbackup/logs/bpbrm\nOn the master server:\n/usr/openv/netbackup/logs/bprd\n■ Correct the problems that you find and retry the restore.\nTo set the debug level on UNIX and Linux clients, enter the following line in the\nbp.conf file:\nVERBOSE = 5\nFor a Sybase alternate client restore, the user ID (UID) of the restoring Sybase\nbackup server must match the UID of the Sybase backup server from the source\nhost.\nFor an alternate client restore, authorize the alternate client to access images for\nthe original client.\nVerify that the alternate client can browse the backup images for the original client:\n# /usr/openv/netbackup/bin/bplist -C -t 7 -l -R /\n# install_path\\netbackup\\bin\\bplist -t 7 -l -R /\nOn the alternate client, use the bpclntcmd command to test connectivity and name\nresolution. The command should display the name of the master server on the first\nline. The second line must contain the IP address of the network interface that the\nalternate client used when communicating with the master server. The first word\non the second line is the name of the alternate client as resolved on the master\nserver from the IP address. The second word on the second line may be 'NULL' if\nthealternateclientisnotbeingbackedup.Otherwise,itisthenameofthealternate\nclient (or an alias) which is defined in a backup policy on the master server.\n# /usr/openv/netbackup/bin/bpclntcmd -pn\nMakesurethatCLIENT_READ_TIMEOUTonthealternateclientandmediaserver\nis set large enough to allow the tapes to be read, the data transferred, and the\ndatabase instance to write the data to disk.\nSee the following technical article for information about the steps for a Sybase\nalternative client restore operation:\nhttps://www.veritas.com/support/en_US/article.100016002" }, "2804": { "code": 2804, - "desc": "MS-SharePoint policy restauração erro", - "first_action": "Garanta que o cliente servidor list contains entradas para o master servidor e qualquer", - "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Garanta que o cliente servidor list contains entradas para o master servidor e qualquer\nmídia servers que can be used during um backup ou restauração.\n■ Examine o status ou o progress log on o cliente para messages on por que o\nrestauração falhou. Also, verifique o Todos Log Entradas relatório on o servidor.\n■ Verifique ownership e permissão on directories onde arquivos estão restored.\n■ Create o seguinte log folders on o SQL Servidor, o front-end web servidor,\no mídia servidor, e o master servidor:\ninstall_path\\NetBackup\\logs\\tar\ninstall_path\\NetBackup\\logs\\bpresolver\ninstall_path\\NetBackup\\logs\\bpbrm (mídia servidor)\ninstall_path\\NetBackup\\logs\\bprd (master servidor)\nIf you use granular restauração technology (GRT), o seguinte log folders also\napply:\ninstall_path\\NetBackup\\logs\\ncf\ninstall_path\\NetBackup\\logs\\ncflbc\ninstall_path\\NetBackup\\logs\\ncfgre\ninstall_path\\NetBackup\\logs\\nbfsd\ninstall_path\\NetBackup\\logs\\spsv2ra\n■ Verifique todos SharePoint servidor Event Viewers (application e system) para qualquer\nerrors.\n■ Conectar to o servidor onde o SharePoint front-end servidor runs e launch\no restauração usando Backup, Archive, e Restauração GUI.\n■ Make sure que o restauração está being launched correctly.\nVeja o NetBackup para Microsoft SharePoint Administrator’s Guide.\n■ Correct o problemas que you find e retry o restauração.\n■ If you need to restauração um VMware job, you must garanta que o mídia servidor está\nadded to o additional servidor list. To access this list in o NetBackup\nAdministration Console, expand Host Properties > Master Servidor.\nDouble-click o name de o servidor to view o properties. Select o Servers\ntab to display o servidor list. In o Servers properties dialog box, select o\nAdditional Servers tab e add o mídia servidor to o servidor list." + "desc": "MS-SharePoint policy restore error", + "first_action": "Ensure that the client server list contains entries for the master server and any", + "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Ensure that the client server list contains entries for the master server and any\nmedia servers that can be used during a backup or restore.\n■ Examine the status or the progress log on the client for messages on why the\nrestore failed. Also, check the All Log Entries report on the server.\n■ Check ownership and permission on directories where files are restored.\n■ Create the following log folders on the SQL Server, the front-end web server,\nthe media server, and the master server:\ninstall_path\\NetBackup\\logs\\tar\ninstall_path\\NetBackup\\logs\\bpresolver\ninstall_path\\NetBackup\\logs\\bpbrm (media server)\ninstall_path\\NetBackup\\logs\\bprd (master server)\nIf you use granular restore technology (GRT), the following log folders also\napply:\ninstall_path\\NetBackup\\logs\\ncf\ninstall_path\\NetBackup\\logs\\ncflbc\ninstall_path\\NetBackup\\logs\\ncfgre\ninstall_path\\NetBackup\\logs\\nbfsd\ninstall_path\\NetBackup\\logs\\spsv2ra\n■ Check all SharePoint server Event Viewers (application and system) for any\nerrors.\n■ Connect to the server where the SharePoint front-end server runs and launch\nthe restore using Backup, Archive, and Restore GUI.\n■ Make sure that the restore is being launched correctly.\nSee the NetBackup for Microsoft SharePoint Administrator’s Guide.\n■ Correct the problems that you find and retry the restore.\n■ If you need to restore a VMware job, you must ensure that the media server is\nadded to the additional server list. To access this list in the NetBackup\nAdministration Console, expand Host Properties > Master Server.\nDouble-click the name of the server to view the properties. Select the Servers\ntab to display the server list. In the Servers properties dialog box, select the\nAdditional Servers tab and add the media server to the server list." }, "2805": { "code": 2805, - "desc": "MS-Windows policy restauração erro", - "first_action": "Garanta que o cliente servidor list contains entradas para o master servidor e qualquer", - "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Garanta que o cliente servidor list contains entradas para o master servidor e qualquer\nmídia servers que can be used during um backup ou restauração.\n■ Examine o status ou o progress log on o cliente para messages on por que o\nrestauração falhou. Also, verifique o Todos Log Entradas relatório on o servidor.\n■ Verifique que you have selected o correct restauração type on o Backup, Archive,\ne Restauração GUI.\n■ Verifique ownership e permissão on directories onde arquivos estão restored.\n■ Verifique o seguinte logs para additional falha informação:\n■ Master servidor: bprd, nbjm\n■ Mídia servidor: bpbrm, bptm, bpdm\n■ Cliente: tar\n■ Correct o problemas que you find e retry o restauração." + "desc": "MS-Windows policy restore error", + "first_action": "Ensure that the client server list contains entries for the master server and any", + "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Ensure that the client server list contains entries for the master server and any\nmedia servers that can be used during a backup or restore.\n■ Examine the status or the progress log on the client for messages on why the\nrestore failed. Also, check the All Log Entries report on the server.\n■ Check that you have selected the correct restore type on the Backup, Archive,\nand Restore GUI.\n■ Check ownership and permission on directories where files are restored.\n■ Check the following logs for additional failure information:\n■ Master server: bprd, nbjm\n■ Media server: bpbrm, bptm, bpdm\n■ Client: tar\n■ Correct the problems that you find and retry the restore." }, "2806": { "code": 2806, - "desc": "NetWare policy restauração erro", - "first_action": "Garanta que o cliente servidor list contains entradas para o master servidor e qualquer", - "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Garanta que o cliente servidor list contains entradas para o master servidor e qualquer\nmídia servers que can be used during um backup ou restauração.\n■ Examine o status ou o progress log on o cliente para messages on por que o\nrestauração falhou. Also, verifique o Todos Log Entradas relatório on o servidor.\n■ Verifique ownership e permissão on directories onde arquivos estão restored.\n■ Verifique o NetBackup tar log para additional falha informação. Also verifique o\nseguinte log arquivos: bpcd, bpsrv, bprest, e user_ops.\n■ Para target restores, garanta que you have create e gravar rights to o volume\nque you estão trying to restauração. In o BP.INI arquivo, garanta que o\nAllow_Server_Write parâmetro está set to yes.\n■ If you launched um non-target restauração from o NetBackup Administration\nConsole,ensurethattheAllowserverdirectedrestoresparameterisselected.\n■ Correct o problemas que you find e retry o restauração." + "desc": "NetWare policy restore error", + "first_action": "Ensure that the client server list contains entries for the master server and any", + "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Ensure that the client server list contains entries for the master server and any\nmedia servers that can be used during a backup or restore.\n■ Examine the status or the progress log on the client for messages on why the\nrestore failed. Also, check the All Log Entries report on the server.\n■ Check ownership and permission on directories where files are restored.\n■ Check the NetBackup tar log for additional failure information. Also check the\nfollowing log files: bpcd, bpsrv, bprest, and user_ops.\n■ For target restores, ensure that you have create and write rights to the volume\nthat you are trying to restore. In the BP.INI file, ensure that the\nAllow_Server_Write parameter is set to yes.\n■ If you launched a non-target restore from the NetBackup Administration\nConsole,ensurethattheAllowserverdirectedrestoresparameterisselected.\n■ Correct the problems that you find and retry the restore." }, "2807": { "code": 2807, - "desc": "SQL-BackTrack policy restauração erro", - "first_action": "Garanta que o cliente servidor list contains entradas para o master servidor e qualquer", - "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Garanta que o cliente servidor list contains entradas para o master servidor e qualquer\nmídia servers que can be used during um backup ou restauração.\n■ Examine o status ou o progress log on o cliente para messages on por que o\nrestauração falhou. Also, verifique o Todos Log Entradas relatório on o servidor.\n■ Verifique ownership e permissão on directories onde arquivos estão restored e on\no SQL-BackTrack instance que you estão restoring.\n■ Verifique o NetBackup backtrack log para additional falha informação.\n■ Correct o problemas que you find e retry o restauração." + "desc": "SQL-BackTrack policy restore error", + "first_action": "Ensure that the client server list contains entries for the master server and any", + "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Ensure that the client server list contains entries for the master server and any\nmedia servers that can be used during a backup or restore.\n■ Examine the status or the progress log on the client for messages on why the\nrestore failed. Also, check the All Log Entries report on the server.\n■ Check ownership and permission on directories where files are restored and on\nthe SQL-BackTrack instance that you are restoring.\n■ Check the NetBackup backtrack log for additional failure information.\n■ Correct the problems that you find and retry the restore." }, "2808": { "code": 2808, - "desc": "Windows Arquivo System policy restauração erro", - "first_action": "Garanta que o cliente servidor list contains entradas para o master servidor e qualquer", - "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Garanta que o cliente servidor list contains entradas para o master servidor e qualquer\nmídia servers que can be used during um backup ou restauração.\n■ Examine o status ou o progress log on o cliente para messages on por que o\nrestauração falhou. Also, verifique o Todos Log Entradas relatório on o servidor.\n■ Verifique que you have selected o correct restauração type on o Backup, Archive,\ne Restauração GUI.\n■ Verifique ownership e permissão on directories onde arquivos estão restored.\n■ Verifique que o destination directories ou arquivos exist. If so, select o Overwrite\nexisting arquivos option on o Backup, Archive, e Restauração GUI.\n■ Verifique o seguinte logs para additional falha informação:\n■ Master servidor: bprd, nbjm\n■ Mídia servidor: bpbrm, bptm, bpdm\n■ Cliente: tar\n■ Correct o problemas que you find e retry o restauração." + "desc": "Windows File System policy restore error", + "first_action": "Ensure that the client server list contains entries for the master server and any", + "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Ensure that the client server list contains entries for the master server and any\nmedia servers that can be used during a backup or restore.\n■ Examine the status or the progress log on the client for messages on why the\nrestore failed. Also, check the All Log Entries report on the server.\n■ Check that you have selected the correct restore type on the Backup, Archive,\nand Restore GUI.\n■ Check ownership and permission on directories where files are restored.\n■ Check that the destination directories or files exist. If so, select the Overwrite\nexisting files option on the Backup, Archive, and Restore GUI.\n■ Check the following logs for additional failure information:\n■ Master server: bprd, nbjm\n■ Media server: bpbrm, bptm, bpdm\n■ Client: tar\n■ Correct the problems that you find and retry the restore." }, "2809": { "code": 2809, - "desc": "MS-SQL-Server policy restauração erro", - "first_action": "Garanta que o cliente servidor list contains entradas para o master servidor e qualquer", - "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Garanta que o cliente servidor list contains entradas para o master servidor e qualquer\nmídia servers que can be used during um backup ou restauração.\n■ Examine o status ou o progress log on o cliente para messages on por que o\nrestauração falhou. Also, verifique o Todos Log Entradas relatório on o servidor.\n■ Verifique ownership e permissão on directories onde arquivos estão restored e on\no SQL instance que you estão restoring.\n■ Verifique ownership e permissão on o SQL Servidor instance e on o\ndirectories onde arquivos estão restored.\n■ Verifique o seguinte logs para additional falha informação on o cliente side:\ninstall_path\\NetBackup\\logs\\dbclient\ninstall_path\\NetBackup\\logs\\bpbkar (snapshot Cliente)\ninstall_path\\NetBackup\\logs\\bpfis (snapshot Cliente)\ninstall_path\\NetBackup\\logs\\bppfi (instant recovery)\n■ Verifique o SQL servidor Event Viewers (application e system) para qualquer errors\nou messages que estão related to o restauração operation.\n■ Aumentar restauração verbose levels.\nVeja o NetBackup para SQL Servidor Administrator’s Guide.\nReview this guide to verifique que you launched o restauração correctly.\n■ Conectar to o servidor onde SQL está executando e launch o restauração from que\nservidor usando o Backup, Archive, e Restauração GUI.\n■ Correct o problemas que you find e retry o restauração." + "desc": "MS-SQL-Server policy restore error", + "first_action": "Ensure that the client server list contains entries for the master server and any", + "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Ensure that the client server list contains entries for the master server and any\nmedia servers that can be used during a backup or restore.\n■ Examine the status or the progress log on the client for messages on why the\nrestore failed. Also, check the All Log Entries report on the server.\n■ Check ownership and permission on directories where files are restored and on\nthe SQL instance that you are restoring.\n■ Check ownership and permission on the SQL Server instance and on the\ndirectories where files are restored.\n■ Check the following logs for additional failure information on the client side:\ninstall_path\\NetBackup\\logs\\dbclient\ninstall_path\\NetBackup\\logs\\bpbkar (Snapshot Client)\ninstall_path\\NetBackup\\logs\\bpfis (Snapshot Client)\ninstall_path\\NetBackup\\logs\\bppfi (instant recovery)\n■ Check the SQL server Event Viewers (application and system) for any errors\nor messages that are related to the restore operation.\n■ Increase restore verbose levels.\nSee the NetBackup for SQL Server Administrator’s Guide.\nReview this guide to verify that you launched the restore correctly.\n■ Connect to the server where SQL is running and launch the restore from that\nserver using the Backup, Archive, and Restore GUI.\n■ Correct the problems that you find and retry the restore." }, "2810": { "code": 2810, - "desc": "MS-Exchange policy restauração erro", - "first_action": "Garanta que o cliente servidor list contains entradas para o master servidor e qualquer", - "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Garanta que o cliente servidor list contains entradas para o master servidor e qualquer\nmídia servers que can be used during um backup ou restauração.\n■ Examine o status ou o progress log on o cliente para messages on por que o\nrestauração falhou. Also, verifique o Todos Log Entradas relatório on o servidor.\n■ Verifique ownership e permissão de o Exchange instance que you restauração\ne o directories onde arquivos estão restored.\n■ Verifique o seguinte log arquivos depending on o type de restauração being performed.\nTodos o log folders estão located in o install_path\\NetBackup\\logs folder.\n■ beds - Todos restauração operations.\n■ tar - Todos restauração operations.\nRestores com Granular Recovery Technology (GRT):\n■ nbfsd - This log appears on o cliente e o mídia servidor.\n■ ncf - This log uses unified logging e appears on o destination cliente ou\nproxy cliente.\n■ ncflbc - This log está para nblbc.exe. It appears on o destination cliente ou\nproxy cliente.\n■ ncfgre - This log está para nbgre.exe. It appears on o destination cliente ou\nproxy cliente.\nInstant Recovery e Instant Recovery off-host:\n■ bpbkar-Foroff-hostInstantRecoveryrestores,bpbkarlogsonthealternate\ncliente.\n■ bpfis - This log aplica-se to Instant Recovery rollback restores. Para off-host\nInstant Recovery backups, bpfis logs exist on both o primary e o\nalternate clients.\n■ bppfi-Foroff-hostInstantRecoveryrestores,bppfilogsonboththeprimary\ne o alternate clients.\n■ ChecktheExchangeServerEventViewerforApplicationandSystemmessages\nque estão related to o restauração operation.\n■ Conectar to o servidor onde Exchange está executando e launch o restauração from\nque servidor usando o Backup, Archive, e Restauração GUI.\n■ Verifique que you launched o restauração correctly.\nVeja o NetBackup para Microsoft Exchange Servidor Administrator’s Guide.\n■ Correct o problemas que you find e retry o restauração." + "desc": "MS-Exchange policy restore error", + "first_action": "Ensure that the client server list contains entries for the master server and any", + "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Ensure that the client server list contains entries for the master server and any\nmedia servers that can be used during a backup or restore.\n■ Examine the status or the progress log on the client for messages on why the\nrestore failed. Also, check the All Log Entries report on the server.\n■ Check ownership and permission of the Exchange instance that you restore\nand the directories where files are restored.\n■ Verify the following log files depending on the type of restore being performed.\nAll the log folders are located in the install_path\\NetBackup\\logs folder.\n■ beds - All restore operations.\n■ tar - All restore operations.\nRestores with Granular Recovery Technology (GRT):\n■ nbfsd - This log appears on the client and the media server.\n■ ncf - This log uses unified logging and appears on the destination client or\nproxy client.\n■ ncflbc - This log is for nblbc.exe. It appears on the destination client or\nproxy client.\n■ ncfgre - This log is for nbgre.exe. It appears on the destination client or\nproxy client.\nInstant Recovery and Instant Recovery off-host:\n■ bpbkar-Foroff-hostInstantRecoveryrestores,bpbkarlogsonthealternate\nclient.\n■ bpfis - This log applies to Instant Recovery rollback restores. For off-host\nInstant Recovery backups, bpfis logs exist on both the primary and the\nalternate clients.\n■ bppfi-Foroff-hostInstantRecoveryrestores,bppfilogsonboththeprimary\nand the alternate clients.\n■ ChecktheExchangeServerEventViewerforApplicationandSystemmessages\nthat are related to the restore operation.\n■ Connect to the server where Exchange is running and launch the restore from\nthat server using the Backup, Archive, and Restore GUI.\n■ Verify that you launched the restore correctly.\nSee the NetBackup for Microsoft Exchange Server Administrator’s Guide.\n■ Correct the problems that you find and retry the restore." }, "2811": { "code": 2811, - "desc": "SAP policy restauração erro", - "first_action": "Garanta que o cliente servidor list contains entradas para o master servidor e qualquer", - "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Garanta que o cliente servidor list contains entradas para o master servidor e qualquer\nmídia servers que can be used during um backup ou restauração.\n■ Examine o status ou o progress log on o cliente para messages on por que o\nrestauração falhou. Also, verifique o Todos Log Entradas relatório on o servidor.\n■ Verifique ownership e permissão de o SAP instance que you restauração e o\ndirectories onde o arquivos estão restored.\n■ Verifique o seguinte logs para additional falha informação: backint, tar,\ndbclient, bprestore, e user_ops.\n■ Correct o problemas que you find e retry o restauração." + "desc": "SAP policy restore error", + "first_action": "Ensure that the client server list contains entries for the master server and any", + "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Ensure that the client server list contains entries for the master server and any\nmedia servers that can be used during a backup or restore.\n■ Examine the status or the progress log on the client for messages on why the\nrestore failed. Also, check the All Log Entries report on the server.\n■ Check ownership and permission of the SAP instance that you restore and the\ndirectories where the files are restored.\n■ Check the following logs for additional failure information: backint, tar,\ndbclient, bprestore, and user_ops.\n■ Correct the problems that you find and retry the restore." }, "2812": { "code": 2812, - "desc": "DB2 policy restauração erro", - "first_action": "Garanta que o cliente servidor list contains entradas para o master servidor e qualquer", - "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Garanta que o cliente servidor list contains entradas para o master servidor e qualquer\nmídia servers que can be used during um backup ou restauração.\n■ Examine o status ou o progress log on o cliente para messages on por que o\nrestauração falhou. Also, verifique o Todos Log Entradas relatório on o servidor.\n■ Verifique ownership e permissão de o DB2 instance que you restauração e o\ndirectories onde o arquivos estão restored.\n■ Verifique o NetBackup bpdb2 log para additional falha informação.\n■ Garanta que you configurado o clients to allow redirected restores. Veja o\nNetBackup para DB2 Administrator’s Guide para details.\n■ Correct o problemas que you find e retry o restauração." + "desc": "DB2 policy restore error", + "first_action": "Ensure that the client server list contains entries for the master server and any", + "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Ensure that the client server list contains entries for the master server and any\nmedia servers that can be used during a backup or restore.\n■ Examine the status or the progress log on the client for messages on why the\nrestore failed. Also, check the All Log Entries report on the server.\n■ Check ownership and permission of the DB2 instance that you restore and the\ndirectories where the files are restored.\n■ Check the NetBackup bpdb2 log for additional failure information.\n■ Ensure that you configured the clients to allow redirected restores. See the\nNetBackup for DB2 Administrator’s Guide for details.\n■ Correct the problems that you find and retry the restore." }, "2813": { "code": 2813, - "desc": "NDMP policy restauração erro", - "first_action": "Garanta que o cliente servidor list contains entradas para o master servidor e qualquer", - "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Garanta que o cliente servidor list contains entradas para o master servidor e qualquer\nmídia servers que can be used during um backup ou restauração.\n■ Examine o status ou o progress log on o cliente para messages on por que o\nrestauração falhou. Also, verifique o Todos Log Entradas relatório on o servidor.\n■ Verifique o ownership e permissão on directories onde arquivos estão restored.\n■ Verifique que o destination NDMP host supports DAR. If não, disable DAR.\n■ Verifique o ndmpagent (Originator ID 134) log para additional falha informação.\n■ Verifique o NetBackup bptm log para additional falha informação.\n■ Verifique que o Force rollback even if it destroy snapshots option de o\npoint-in-time rollback restauração está set (checked) ou não set (unchecked).\nFormoreinformationonrollbackrestore,pleaseseetheNetBackupReplication\nDirector Solutions Guide.\n■ Correct o problemas que you find e retry o restauração." + "desc": "NDMP policy restore error", + "first_action": "Ensure that the client server list contains entries for the master server and any", + "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Ensure that the client server list contains entries for the master server and any\nmedia servers that can be used during a backup or restore.\n■ Examine the status or the progress log on the client for messages on why the\nrestore failed. Also, check the All Log Entries report on the server.\n■ Check the ownership and permission on directories where files are restored.\n■ Verify that the destination NDMP host supports DAR. If not, disable DAR.\n■ Check the ndmpagent (Originator ID 134) log for additional failure information.\n■ Check the NetBackup bptm log for additional failure information.\n■ Check that the Force rollback even if it destroy snapshots option of the\npoint-in-time rollback restore is set (checked) or not set (unchecked).\nFormoreinformationonrollbackrestore,pleaseseetheNetBackupReplication\nDirector Solutions Guide.\n■ Correct the problems that you find and retry the restore." }, "2814": { "code": 2814, - "desc": "FlashBackup policy restauração erro", - "first_action": "Garanta que o cliente servidor list contains entradas para o master servidor e qualquer", - "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Garanta que o cliente servidor list contains entradas para o master servidor e qualquer\nmídia servers que can be used during um backup ou restauração.\n■ Examine o status ou o progress log on o cliente para messages on por que o\nrestauração falhou. Also, verifique o Todos Log Entradas relatório on o servidor.\n■ Verifique ownership e permissão on directories onde arquivos estão restored.\n■ Verifique o NetBackup tar log para additional falha informação.\n■ Enable e verifique VxMS logs para additional falha informação.\n■ Para VMware restores, enable o bpvmutil logs.\n■ If you run um VMware restauração, make sure que o usuário account que está specified\nin o VMware credentials has cheio administration rights on o target vCenter\ne o ESX servidor.\n■ Correct o problemas que you find e retry o restauração." + "desc": "FlashBackup policy restore error", + "first_action": "Ensure that the client server list contains entries for the master server and any", + "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Ensure that the client server list contains entries for the master server and any\nmedia servers that can be used during a backup or restore.\n■ Examine the status or the progress log on the client for messages on why the\nrestore failed. Also, check the All Log Entries report on the server.\n■ Check ownership and permission on directories where files are restored.\n■ Check the NetBackup tar log for additional failure information.\n■ Enable and verify VxMS logs for additional failure information.\n■ For VMware restores, enable the bpvmutil logs.\n■ If you run a VMware restore, make sure that the user account that is specified\nin the VMware credentials has full administration rights on the target vCenter\nand the ESX server.\n■ Correct the problems that you find and retry the restore." }, "2815": { "code": 2815, - "desc": "AFS policy restauração erro", - "first_action": "Garanta que o cliente servidor list contains entradas para o master servidor e qualquer", - "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Garanta que o cliente servidor list contains entradas para o master servidor e qualquer\nmídia servers que can be used during um backup ou restauração.\n■ Examine o status ou o progress log on o cliente para messages on por que o\nrestauração falhou. Also, verifique o Todos Log Entradas relatório on o servidor.\n■ Verifique ownership e permissão on directories onde arquivos estão restored.\n■ Verifique o NetBackup tar log para additional falha informação.\n■ Correct o problemas que you find e retry o restauração." + "desc": "AFS policy restore error", + "first_action": "Ensure that the client server list contains entries for the master server and any", + "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Ensure that the client server list contains entries for the master server and any\nmedia servers that can be used during a backup or restore.\n■ Examine the status or the progress log on the client for messages on why the\nrestore failed. Also, check the All Log Entries report on the server.\n■ Check ownership and permission on directories where files are restored.\n■ Check the NetBackup tar log for additional failure information.\n■ Correct the problems that you find and retry the restore." }, "2816": { "code": 2816, - "desc": "DataStore policy restauração erro", - "first_action": "Garanta que o cliente servidor list contains entradas para o master servidor e qualquer", - "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Garanta que o cliente servidor list contains entradas para o master servidor e qualquer\nmídia servers que can be used during um backup ou restauração.\n■ Examine o status ou o progress log on o cliente para messages on por que o\nrestauração falhou. If you run one PureDisk disaster recovery, verifique o output from\no /opt/pdinstall/DR_Restore_all.sh script on o PureDisk node. Also,\nverifique o Todos Log Entradas relatório on o servidor.\n■ Verifique ownership e permissão on directories onde arquivos estão restored.\n■ Verifique ownership e permissão on o banco de dados instance que you restauração.\n■ Verifique o NetBackup exten_client log para additional falha informação.\n■ If you restauração um Netezza appliance, collect o log arquivos from\n/nz/kit/log/restoresvf/*.\n■ Correct o problemas que you find e retry o restauração." + "desc": "DataStore policy restore error", + "first_action": "Ensure that the client server list contains entries for the master server and any", + "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Ensure that the client server list contains entries for the master server and any\nmedia servers that can be used during a backup or restore.\n■ Examine the status or the progress log on the client for messages on why the\nrestore failed. If you run one PureDisk disaster recovery, check the output from\nthe /opt/pdinstall/DR_Restore_all.sh script on the PureDisk node. Also,\ncheck the All Log Entries report on the server.\n■ Check ownership and permission on directories where files are restored.\n■ Check ownership and permission on the database instance that you restore.\n■ Check the NetBackup exten_client log for additional failure information.\n■ If you restore a Netezza appliance, collect the log files from\n/nz/kit/log/restoresvf/*.\n■ Correct the problems that you find and retry the restore." }, "2817": { "code": 2817, - "desc": "FlashBackup Windows policy restauração erro", - "first_action": "Garanta que o cliente servidor list contains entradas para o master servidor e qualquer", - "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Garanta que o cliente servidor list contains entradas para o master servidor e qualquer\nmídia servers que can be used during um backup ou restauração.\n■ Examine o status ou o progress log on o cliente para messages on por que o\nrestauração falhou. Also, verifique o Todos Log Entradas relatório on o servidor.\n■ Verifique ownership e permissão on directories onde arquivos estão restored.\n■ Verifique o NetBackup tar log para additional falha informação.\n■ Correct o problemas que you find e retry o restauração." + "desc": "FlashBackup Windows policy restore error", + "first_action": "Ensure that the client server list contains entries for the master server and any", + "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Ensure that the client server list contains entries for the master server and any\nmedia servers that can be used during a backup or restore.\n■ Examine the status or the progress log on the client for messages on why the\nrestore failed. Also, check the All Log Entries report on the server.\n■ Check ownership and permission on directories where files are restored.\n■ Check the NetBackup tar log for additional failure information.\n■ Correct the problems that you find and retry the restore." }, "2818": { "code": 2818, - "desc": "NetBackup Catalog policy restauração erro", - "first_action": "Garanta que o cliente servidor list contains entradas para o master servidor e qualquer", - "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Garanta que o cliente servidor list contains entradas para o master servidor e qualquer\nmídia servers que can be used during um backup ou restauração.\n■ Examine o status ou o progress log on o cliente para messages on por que o\nrestauração falhou. Also, verifique o Todos Log Entradas relatório on o servidor.\n■ Garanta que NetBackup está at o same version e patch level como o computer\nonde o catalog image foi created.\n■ Garanta que o caminho onde you restauração o catalog está same como when it foi\nsalvo up.\n■ Garanta que sufficient disco space exists on o target system onde o restauração\nruns.\n■ Garanta que o current master servidor host name matches o host name de o\ncomputer onde o catalog image foi created.\n■ Verifique ownership e permissão on directories onde arquivos estão restored.\n■ Verifique o NetBackup tar, admin, bptm, e bpbrm logs para additional falha\ninformação.\n■ Correct o problemas que you find e retry o restauração." + "desc": "NetBackup Catalog policy restore error", + "first_action": "Ensure that the client server list contains entries for the master server and any", + "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Ensure that the client server list contains entries for the master server and any\nmedia servers that can be used during a backup or restore.\n■ Examine the status or the progress log on the client for messages on why the\nrestore failed. Also, check the All Log Entries report on the server.\n■ Ensure that NetBackup is at the same version and patch level as the computer\nwhere the catalog image was created.\n■ Ensure that the path where you restore the catalog is same as when it was\nbacked up.\n■ Ensure that sufficient disk space exists on the target system where the restore\nruns.\n■ Ensure that the current master server host name matches the host name of the\ncomputer where the catalog image was created.\n■ Check ownership and permission on directories where files are restored.\n■ Check the NetBackup tar, admin, bptm, and bpbrm logs for additional failure\ninformation.\n■ Correct the problems that you find and retry the restore." }, "2819": { "code": 2819, - "desc": "Enterprise Vault policy restauração erro", - "first_action": "Garanta que o cliente servidor list contains entradas para o master servidor e qualquer", - "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Garanta que o cliente servidor list contains entradas para o master servidor e qualquer\nmídia servers que can be used during um backup ou restauração.\n■ Examine o status ou o progress log on o cliente para messages on por que o\nrestauração falhou. Also, verifique o Todos Log Entradas relatório on o servidor.\n■ Verifique ownership e permissão on directories onde arquivos estão restored.\n■ Verifique o NetBackup tar log para additional falha informação. Also, verifique o\nEnterprise Vault servidor Event Viewer (application e system) para errors ou\npistas.\n■ Conectar to o servidor onde o Enterprise Vault front-end runs. Launch o\nrestauração por usando o Backup, Archive, e Restauração GUI.\n■ Verifique que you launched o restauração correctly.\nVeja o NetBackup para Enterprise Vault Agent Servidor Administrator’s Guide.\n■ Correct o problemas que you find e retry o restauração." + "desc": "Enterprise Vault policy restore error", + "first_action": "Ensure that the client server list contains entries for the master server and any", + "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Ensure that the client server list contains entries for the master server and any\nmedia servers that can be used during a backup or restore.\n■ Examine the status or the progress log on the client for messages on why the\nrestore failed. Also, check the All Log Entries report on the server.\n■ Check ownership and permission on directories where files are restored.\n■ Check the NetBackup tar log for additional failure information. Also, check the\nEnterprise Vault server Event Viewer (application and system) for errors or\nclues.\n■ Connect to the server where the Enterprise Vault front-end runs. Launch the\nrestore by using the Backup, Archive, and Restore GUI.\n■ Verify that you launched the restore correctly.\nSee the NetBackup for Enterprise Vault Agent Server Administrator’s Guide.\n■ Correct the problems that you find and retry the restore." }, "2820": { "code": 2820, - "desc": "NetBackup VMware policy restauração erro", - "first_action": "Garanta que um .ISO arquivo que está presented to um virtual machine como um virtual CD ou", - "full_action": "Review o seguinte lists para solutions to this erro.\nVerifique o job details in o Activity Monitor e take ação como dictated por que\ninformação, como follows:\n■ Garanta que um .ISO arquivo que está presented to um virtual machine como um virtual CD ou\nDVD during backup está disponível on o destination host.\n■ Para um successful hotadd restauração, garanta que o two virtual machines estão in o\nsame VMware data center.\n■ Select um different transport mode e retry o restauração.\n■ You não é possível restauração restauração um arquivo que has um caminho name longer than 1023\ncharacters.\n■ If possible, restauração o VM to um VMware servidor que supports o VM's hardware\nversion.\n■ In Backup, Archive, e Restauração, change o restored virtual disco to Thick\nProvision Lazy Zeroed ou Thin Provisioning.\nWhen um VMware agentless restauração está performed, o restauração can cause one de o\nseguinte issues:\n■ FailedtoidentifythenewlyattacheddeviceondestinationVM%s.Onepossible\ncause está que o destination VM usuário credentials have insufficient permissions.\nIt está recomendada target VM usuário credentials com raiz ou administrative\nprivileges.\n■ Falhou to attach o temporary vmdk %s to o destination VM %s com erro\n%d.\nMakesurethatthetargetVMhasatleastoneparavirtualcontrollerwithavailable\nLUNs.\n■ Falhou to upload o process rename arquivo to o destination VM %s com erro\n%d.\nMake sure there está sufficient space disponível in target VM.\n■ Falhou to restauração o selected arquivos e folders.\nReview o tar log to troubleshoot this issue." + "desc": "NetBackup VMware policy restore error", + "first_action": "Ensure that an .ISO file that is presented to a virtual machine as a virtual CD or", + "full_action": "Review the following lists for solutions to this error.\nCheck the job details in the Activity Monitor and take action as dictated by that\ninformation, as follows:\n■ Ensure that an .ISO file that is presented to a virtual machine as a virtual CD or\nDVD during backup is available on the destination host.\n■ For a successful hotadd restore, ensure that the two virtual machines are in the\nsame VMware data center.\n■ Select a different transport mode and retry the restore.\n■ You cannot restore restore a file that has a path name longer than 1023\ncharacters.\n■ If possible, restore the VM to a VMware server that supports the VM's hardware\nversion.\n■ In Backup, Archive, and Restore, change the restored virtual disk to Thick\nProvision Lazy Zeroed or Thin Provisioning.\nWhen a VMware agentless restore is performed, the restore can cause one of the\nfollowing issues:\n■ FailedtoidentifythenewlyattacheddeviceondestinationVM%s.Onepossible\ncause is that the destination VM user credentials have insufficient permissions.\nIt is recommended target VM user credentials with root or administrative\nprivileges.\n■ Failed to attach the temporary vmdk %s to the destination VM %s with error\n%d.\nMakesurethatthetargetVMhasatleastoneparavirtualcontrollerwithavailable\nLUNs.\n■ Failed to upload the process rename file to the destination VM %s with error\n%d.\nMake sure there is sufficient space available in target VM.\n■ Failed to restore the selected files and folders.\nReview the tar log to troubleshoot this issue." }, "2821": { "code": 2821, - "desc": "Hyper-V policy restauração erro", - "first_action": "Update o NIC drivers e firmware if necessary.", - "full_action": "Try o seguinte:\n■ Update o NIC drivers e firmware if necessary.\n■ Garanta que o rede hardware between o mídia servidor e o cliente\noperates properly.\n■ Add NetBackup processos e directories to o Antivirus Exclusion List since\nantivirus applications may fechar o established socket.\n■ Aumentar TCP resiliency on o Windows hosts (master servers, mídia servers,\ne clients) por setting o TcpMaxDataRetransmissions registry key to um value\nde 10. O default value está 5.\nMore informação está disponível from Microsoft about o\nTcpMaxDataRetransmissions registry key:\nhttp://msdn.microsoft.com/en-us/library/aa915651.aspx" + "desc": "Hyper-V policy restore error", + "first_action": "Update the NIC drivers and firmware if necessary.", + "full_action": "Try the following:\n■ Update the NIC drivers and firmware if necessary.\n■ Ensure that the network hardware between the media server and the client\noperates properly.\n■ Add NetBackup processes and directories to the Antivirus Exclusion List since\nantivirus applications may close the established socket.\n■ Increase TCP resiliency on the Windows hosts (master servers, media servers,\nand clients) by setting the TcpMaxDataRetransmissions registry key to a value\nof 10. The default value is 5.\nMore information is available from Microsoft about the\nTcpMaxDataRetransmissions registry key:\nhttp://msdn.microsoft.com/en-us/library/aa915651.aspx" }, "2822": { "code": 2822, - "desc": "Hypervisor policy restauração erro.", - "first_action": "Review o job details from o Activity Monitor para issue details. Refer to o", - "full_action": "Pleasereview thefollowinginformationforyour particular\nworkload.\n■ Review o job details from o Activity Monitor para issue details. Refer to o\nbpVMutil logs para more informação. If o issue persists, visit o Cohesity\nTechnical Support website. O Cohesity Technical Support website offers\nadditional informação to help you troubleshoot this issue.\n■ Garanta que there está enough space disponível on o destination armazenamento domain\nto restauração o disks. O disco creation can take some time to complete.\n■ Verifique que o entradas in o rename arquivo estão in o correct format.\n■ Refer to o bpVMutil logs para more informação. If o issue persists, visit o\nCohesity Technical Support website. O Cohesity Technical Support website\noffers additional informação to help you troubleshoot this issue.\nRHV:\n■ VerifytheRHV_CREATEDISK_TIMEOUTconfigurationentryandupdateitifrequired.\n■ VerifythatthetargetstoragedomaintypeissupportedforrestoresbyNetBackup.\n■ Refer to o bpVMutil logs para more informação. If o issue persists, visit o\nCohesity Technical Support website. O Cohesity Technical Support website\noffers additional informação to help you troubleshoot this issue.\n■ RefertotheRHVdocumentationforthesupportedVMdisplaynamecharacters\ne length.\nNutanix AHV:\n■ Refer to o Nutanix AHV documentation para o supported VM display name\ncharacters e length." + "desc": "Hypervisor policy restore error.", + "first_action": "Review the job details from the Activity Monitor for issue details. Refer to the", + "full_action": "Pleasereview thefollowinginformationforyour particular\nworkload.\n■ Review the job details from the Activity Monitor for issue details. Refer to the\nbpVMutil logs for more information. If the issue persists, visit the Cohesity\nTechnical Support website. The Cohesity Technical Support website offers\nadditional information to help you troubleshoot this issue.\n■ Ensure that there is enough space available on the destination storage domain\nto restore the disks. The disk creation can take some time to complete.\n■ Verify that the entries in the rename file are in the correct format.\n■ Refer to the bpVMutil logs for more information. If the issue persists, visit the\nCohesity Technical Support website. The Cohesity Technical Support website\noffers additional information to help you troubleshoot this issue.\nRHV:\n■ VerifytheRHV_CREATEDISK_TIMEOUTconfigurationentryandupdateitifrequired.\n■ VerifythatthetargetstoragedomaintypeissupportedforrestoresbyNetBackup.\n■ Refer to the bpVMutil logs for more information. If the issue persists, visit the\nCohesity Technical Support website. The Cohesity Technical Support website\noffers additional information to help you troubleshoot this issue.\n■ RefertotheRHVdocumentationforthesupportedVMdisplaynamecharacters\nand length.\nNutanix AHV:\n■ Refer to the Nutanix AHV documentation for the supported VM display name\ncharacters and length." }, "2824": { "code": 2824, - "desc": "Cloud policy restauração erro.", - "first_action": "Para VM-based deployment, if não external", - "full_action": "O seguinte tables list o nbcs level erro messages\nwhich estão displayed in Job Details on o Activity Monitor e o ação you\nneed to take to fix o issue.\nTable 1-2 Restauração falhou como o pre-requisites para restauração operation foram\nnão satisfied para o asset\nMessage Recomendada ação\nDiskResource group doesnotexist. O resource group in o disco destination\npathdoesnotexist.Selecttheresourcegroup\nwhich está present in o cloud.\nDisco subscription ID <> must be o Garanta que o given subscription ID como part\nsame como o host subscription ID. de o disco destination caminho, match com\nsubscription ID from VM destination caminho.\nVM com name <> already exists. Retrytheoperationafterchangingthedisplay\nname.\nVM display name <> está unsupported. Garanta que o VM name está compliant com\no cloud provider’s naming convention.\nDestinationPath <>: está não configurado O provided subscription está não configurado\npara selected config. inthegivendestinationconfiguration.Provide\num subscription que exists in o configurado\ncloud provider.\nTable 1-2 Restauração falhou como o pre-requisites para restauração operation foram\nnão satisfied para o asset (continued)\nMessage Recomendada ação\nSubnet does não exist. Thedestinationnetworkthatisselecteddoes\nnão exist in o selected subscription. Select\num rede which está present on o cloud.\nGaranta que discovery has run after o\ncreation de um new subnet.\nDestination Resource group does O resource group in o VM destination\nnão exist. caminho does não exist. Select um resource group\nwhich está present on o cloud.\nRegion <> está não configurado. Garanta que o selected region está part de o\ndestination configuration.\nFalhou to find sqlpackage cliente utility on um Installtherequiredsqlpackageutilityonthe\ngiven host. mídia servidor.\nConfigure e mount Universal Share ■ Para VM-based deployment if um external\nAccelerator falhou. disco está attached to o NetBackup\nSnapshot Manager host e mounted como\n/datamover_storage then garanta at\nleast 500GB de disco space está disponível.\n■ Para VM-based deployment, if não external\ndisco está attached to o NetBackup\nSnapshot Manager host ou if it está não\nmountedas/datamover_storage:then\ngaranta que o raiz partition has at least\n500GB de disco space disponível.\nFalhou to get export caminho e vpfs servidor. ■ InCloudScaledeploymentensurethatall\nMSDP pods have at least 500GB de disco\nspace disponível.\n■ In VM-based deployment garanta que o\narmazenamento servidor should have at least\n500GB de disco space disponível at o\nconfigurado armazenamento caminho.\nO seguinte estão apenas applicable para Azure Stack restauração from backup.\nRestauração falhou due to o staging location não correctly specified. Verifique que o\n/cloudpoint/azurestack.conf has um correct entry para o staging location.\nTable 1-2 Restauração falhou como o pre-requisites para restauração operation foram\nnão satisfied para o asset (continued)\nMessage Recomendada ação\nFalhou to get um staging location para o Garanta que staging location details (para\nsubscription: {id}. example:storageaccountandcontainer)are\nadded in o arquivo\n/cloudpoint/azurestack.conf para o\nselected target subscription.\nO armazenamento account:, does não exist. o target subscription.\nO container: {container name}, Garanta que o armazenamento account container está\ndoes não exist in o armazenamento account: present in o armazenamento account.\n{account name}.\nTable 1-3 Falhou to executar um recovery operation para o asset\nMessage Recomendada ação\nFalhou to create um asset . One de o probable reasons can be que o\nquota limite has excedido. Verifique if o\nrequerido resource limite está disponível.\nAsset <> não found. Garanta que o asset está present in o cloud\ne it está discovered.\nTable 1-4 RestorefailedduetoSSLcertificateissuesorconnectivityissues\nbetween Snapshot Manager e Azure ou Azure Stack\nMessage Recomendada ação\nNão foi possível to retrieve o certificate CRL. If you CopythelatestCRLintotheECA_CRL_PATH\nhaveconfiguredtheECA_CRL_PATH,ensure caminho ou garanta o CRL distribution point\nque valid CRLs estão present at o location. URL, from o respective host certificate, está\nCheckiftheCRLURLisaccessiblefromthe accessible from o Snapshot Manager.\nSnapshot Manager.\nTheAzureorAzureStackservers’certificate O certificate de o servidor has been\nestá revoked. Garanta que o certificates estão revoked. Contate seu security administrator\nnão revoked por certificate authority. para assistance.\nTable 1-4 RestorefailedduetoSSLcertificateissuesorconnectivityissues\nbetween Snapshot Manager e Azure ou Azure Stack\n(continued)\nMessage Recomendada ação\nThecertificaterevocationlist(CRL)isexpired. Garanta que o latest CRL’s estão uploaded at\nGaranta que o ECA_CRL_PATH está updated o ECA_CRL_PATH caminho.\ncom o latest CRL.\nYou can update o NetBackup CRL cache\nmanuallybyusingthefollowingcommandon\nSnapshot Manager:\ndocker exec -i flexsnap-certauth bash -c\n'/usr/openv/pdde/pdopensource\n/nbcertcmdtool/nbcertcmdtool -atLibPath\n/usr/openv/pdde/pdopensource/nbcertcmdtool\n-updateCRLCache'\nThecertificaterevocationlist(CRL)isnotyet Review seu Snapshot Manager’s system\nvalid. time ou provide um valid CRL.\nO date de o last update de o certificate ChecktheCRLusingtheopensslcommand\nrevocation list (CRL) está não in um valid format. ou contate seu Security Administrator.\nO date de o next update de o certificate ChecktheCRLusingtheopensslcommand\nrevocation list (CRL) está não in um valid format. ou contate seu Security Administrator.\nO Azure ou Azure Stack servidor certificate Reviewthecertificateandensurethevalidity\nisexpired.Ensurethattheserverhasavalid de it por checking o certificate to make sure\ncertificate. que o end date está valid.\nVerifique if o Snapshot Manager’s clock está in\nsync com o specified servidor. Correct o\ntime on o host, if necessary, e rerun o\noperation. If o problema continues, save todos\nde o erro log informação e contate\nCohesity Technical Support.\nO Azure ou Azure stack servers certificate Verifique if o Snapshot Manager’s clock está in\nestá não yet valid. sync com o specified servidor. Correct o\ntime on o host, if necessary, e rerun o\noperation. If o problema continues, save todos\nde o erro log informação e contate\nCohesity Technical Support.\nTable 1-4 RestorefailedduetoSSLcertificateissuesorconnectivityissues\nbetween Snapshot Manager e Azure ou Azure Stack\n(continued)\nMessage Recomendada ação\nUnabletofindthepublicrootandintermediate Garanta que o certificate arquivo está configurado\ncertificates de o Azure Stack servidor. correctly at o ECA_TRUST_STORE_PATH\nlocated in o bp.conf arquivo on o Snapshot\nManager.\nRerun o operation. If o problema persists,\nsave todos de o erro log informação e\ncontate Cohesity Technical Support.\nFalhou to load o Certificate Revocation List Garanta que o valid CRL arquivo está configurado\n(CRL) from o CRL cache. Garanta que o ontheSnapshotManagerforAzureorAzure\nvalid CRL arquivo está configurado on o Snapshot Stack por o ECA_CRL_PATH.\nManager para Azure ou Azure Stack por\nECA_CRL_PATH.\nFailedtoconnecttotheAzureorAzureStack Garanta rede connectivity between o\nserver.Ensurenetworkconnectivitybetween Snapshot Manager e o Azure ou Azure\nSnapshot Manager e o Azure ou Azure Stack servidor.\nStack servidor.\nNão é possível use o specified SSL cipher para Contate Cohesity Technical Support.\nAzure ou Azure Stack servidor.\nOperation falhou com cURL erro: Rerun o operation. If o problema persists,\nsave todos de o erro log informação e\ncontate Cohesity Technical Support." + "desc": "Cloud policy restore error.", + "first_action": "For VM-based deployment, if no external", + "full_action": "The following tables list the nbcs level error messages\nwhich are displayed in Job Details on the Activity Monitor and the action you\nneed to take to fix the issue.\nTable 1-2 Restore failed as the pre-requisites for restore operation were\nnot satisfied for the asset\nMessage Recommended action\nDiskResource group doesnotexist. The resource group in the disk destination\npathdoesnotexist.Selecttheresourcegroup\nwhich is present in the cloud.\nDisk subscription ID <> must be the Ensure that the given subscription ID as part\nsame as the host subscription ID. of the disk destination path, match with\nsubscription ID from VM destination path.\nVM with name <> already exists. Retrytheoperationafterchangingthedisplay\nname.\nVM display name <> is unsupported. Ensure that the VM name is compliant with\nthe cloud provider’s naming convention.\nDestinationPath <>: is not configured The provided subscription is not configured\nfor selected config. inthegivendestinationconfiguration.Provide\na subscription that exists in the configured\ncloud provider.\nTable 1-2 Restore failed as the pre-requisites for restore operation were\nnot satisfied for the asset (continued)\nMessage Recommended action\nSubnet does not exist. Thedestinationnetworkthatisselecteddoes\nnot exist in the selected subscription. Select\na network which is present on the cloud.\nEnsure that discovery has run after the\ncreation of a new subnet.\nDestination Resource group does The resource group in the VM destination\nnot exist. path does not exist. Select a resource group\nwhich is present on the cloud.\nRegion <> is not configured. Ensure that the selected region is part of the\ndestination configuration.\nFailed to find sqlpackage client utility on a Installtherequiredsqlpackageutilityonthe\ngiven host. media server.\nConfigure and mount Universal Share ■ For VM-based deployment if an external\nAccelerator failed. disk is attached to the NetBackup\nSnapshot Manager host and mounted as\n/datamover_storage then ensure at\nleast 500GB of disk space is available.\n■ For VM-based deployment, if no external\ndisk is attached to the NetBackup\nSnapshot Manager host or if it is not\nmountedas/datamover_storage:then\nensure that the root partition has at least\n500GB of disk space available.\nFailed to get export path and vpfs server. ■ InCloudScaledeploymentensurethatall\nMSDP pods have at least 500GB of disk\nspace available.\n■ In VM-based deployment ensure that the\nstorage server should have at least\n500GB of disk space available at the\nconfigured storage path.\nThe following are only applicable for Azure Stack restore from backup.\nRestore failed due to the staging location not correctly specified. Verify that the\n/cloudpoint/azurestack.conf has a correct entry for the staging location.\nTable 1-2 Restore failed as the pre-requisites for restore operation were\nnot satisfied for the asset (continued)\nMessage Recommended action\nFailed to get a staging location for the Ensure that staging location details (for\nsubscription: {id}. example:storageaccountandcontainer)are\nadded in the file\n/cloudpoint/azurestack.conf for the\nselected target subscription.\nThe storage account:, does not exist. the target subscription.\nThe container: {container name}, Ensure that the storage account container is\ndoes not exist in the storage account: present in the storage account.\n{account name}.\nTable 1-3 Failed to perform a recovery operation for the asset\nMessage Recommended action\nFailed to create an asset . One of the probable reasons can be that the\nquota limit has exceeded. Check if the\nrequired resource limit is available.\nAsset <> not found. Ensure that the asset is present in the cloud\nand it is discovered.\nTable 1-4 RestorefailedduetoSSLcertificateissuesorconnectivityissues\nbetween Snapshot Manager and Azure or Azure Stack\nMessage Recommended action\nUnable to retrieve the certificate CRL. If you CopythelatestCRLintotheECA_CRL_PATH\nhaveconfiguredtheECA_CRL_PATH,ensure path or ensure the CRL distribution point\nthat valid CRLs are present at the location. URL, from the respective host certificate, is\nCheckiftheCRLURLisaccessiblefromthe accessible from the Snapshot Manager.\nSnapshot Manager.\nTheAzureorAzureStackservers’certificate The certificate of the server has been\nis revoked. Ensure that the certificates are revoked. Contact your security administrator\nnot revoked by certificate authority. for assistance.\nTable 1-4 RestorefailedduetoSSLcertificateissuesorconnectivityissues\nbetween Snapshot Manager and Azure or Azure Stack\n(continued)\nMessage Recommended action\nThecertificaterevocationlist(CRL)isexpired. Ensure that the latest CRL’s are uploaded at\nEnsure that the ECA_CRL_PATH is updated the ECA_CRL_PATH path.\nwith the latest CRL.\nYou can update the NetBackup CRL cache\nmanuallybyusingthefollowingcommandon\nSnapshot Manager:\ndocker exec -i flexsnap-certauth bash -c\n'/usr/openv/pdde/pdopensource\n/nbcertcmdtool/nbcertcmdtool -atLibPath\n/usr/openv/pdde/pdopensource/nbcertcmdtool\n-updateCRLCache'\nThecertificaterevocationlist(CRL)isnotyet Review your Snapshot Manager’s system\nvalid. time or provide a valid CRL.\nThe date of the last update of the certificate ChecktheCRLusingtheopensslcommand\nrevocation list (CRL) is not in a valid format. or contact your Security Administrator.\nThe date of the next update of the certificate ChecktheCRLusingtheopensslcommand\nrevocation list (CRL) is not in a valid format. or contact your Security Administrator.\nThe Azure or Azure Stack server certificate Reviewthecertificateandensurethevalidity\nisexpired.Ensurethattheserverhasavalid of it by checking the certificate to make sure\ncertificate. that the end date is valid.\nCheck if the Snapshot Manager’s clock is in\nsync with the specified server. Correct the\ntime on the host, if necessary, and rerun the\noperation. If the problem continues, save all\nof the error log information and contact\nCohesity Technical Support.\nThe Azure or Azure stack servers certificate Check if the Snapshot Manager’s clock is in\nis not yet valid. sync with the specified server. Correct the\ntime on the host, if necessary, and rerun the\noperation. If the problem continues, save all\nof the error log information and contact\nCohesity Technical Support.\nTable 1-4 RestorefailedduetoSSLcertificateissuesorconnectivityissues\nbetween Snapshot Manager and Azure or Azure Stack\n(continued)\nMessage Recommended action\nUnabletofindthepublicrootandintermediate Ensure that the certificate file is configured\ncertificates of the Azure Stack server. correctly at the ECA_TRUST_STORE_PATH\nlocated in the bp.conf file on the Snapshot\nManager.\nRerun the operation. If the problem persists,\nsave all of the error log information and\ncontact Cohesity Technical Support.\nFailed to load the Certificate Revocation List Ensure that the valid CRL file is configured\n(CRL) from the CRL cache. Ensure that the ontheSnapshotManagerforAzureorAzure\nvalid CRL file is configured on the Snapshot Stack by the ECA_CRL_PATH.\nManager for Azure or Azure Stack by\nECA_CRL_PATH.\nFailedtoconnecttotheAzureorAzureStack Ensure network connectivity between the\nserver.Ensurenetworkconnectivitybetween Snapshot Manager and the Azure or Azure\nSnapshot Manager and the Azure or Azure Stack server.\nStack server.\nCannot use the specified SSL cipher for Contact Cohesity Technical Support.\nAzure or Azure Stack server.\nOperation failed with cURL error: Rerun the operation. If the problem persists,\nsave all of the error log information and\ncontact Cohesity Technical Support." }, "2826": { "code": 2826, - "desc": "Master servidor falhou to conectar to backup restauração manager on mídia servidor para restauração", + "desc": "Master server failed to connect to backup restore manager on media server for restore", "first_action": "Fromthemasterserver,pingthemasterandallmediaserversbyusingthehost", - "full_action": "Try o seguinte possible solution in o order presented:\n■ Fromthemasterserver,pingthemasterandallmediaserversbyusingthehost\nnames in o armazenamento unidade configuration.\n■ From each de o mídia servers, ping o master servidor por usando o name que\nestá specified in o NetBackup servidor list. On um UNIX ou Linux servidor, this master\nestá o first Servidor entry in o bp.conf arquivo. On um Windows servidor, o master\nestá designated on o Servers tab in o Master Servidor Properties dialog box.\n■ Verifique que todos de o services estão executando on o mídia servidor." + "full_action": "Try the following possible solution in the order presented:\n■ Fromthemasterserver,pingthemasterandallmediaserversbyusingthehost\nnames in the storage unit configuration.\n■ From each of the media servers, ping the master server by using the name that\nis specified in the NetBackup server list. On a UNIX or Linux server, this master\nis the first SERVER entry in the bp.conf file. On a Windows server, the master\nis designated on the Servers tab in the Master Server Properties dialog box.\n■ Check that all of the services are running on the media server." }, "2827": { "code": 2827, - "desc": "Cliente falhou to conectar to o mídia servidor para restauração", + "desc": "Client failed to connect to the media server for restore", "first_action": "Fromthemasterserver,pingthemasterandallmediaserversbyusingthehost", - "full_action": "Try o seguinte possible solution in o order presented:\n■ Fromthemasterserver,pingthemasterandallmediaserversbyusingthehost\nnames in o armazenamento unidade configuration.\n■ Verifique que todos services estão executando on o mídia servidor." + "full_action": "Try the following possible solution in the order presented:\n■ Fromthemasterserver,pingthemasterandallmediaserversbyusingthehost\nnames in the storage unit configuration.\n■ Check that all services are running on the media server." }, "2828": { "code": 2828, - "desc": "Restauração falhou because o MS-SQL-Server services estão down", - "first_action": "Verifique que o SQL Servidor instance service está executando", - "full_action": "Verifique que o SQL Servidor instance service está executando\nandthatNetBackupprocesseshavepermissiontoaccesstheSQLServerinstance\nservice." + "desc": "Restore failed because the MS-SQL-Server services are down", + "first_action": "Check that the SQL Server instance service is running", + "full_action": "Check that the SQL Server instance service is running\nandthatNetBackupprocesseshavepermissiontoaccesstheSQLServerinstance\nservice." }, "2829": { "code": 2829, - "desc": "Restauração falhou due to MS-SQL-Server banco de dados in use NetBackup status codes 510 NetBackup status codes", - "first_action": "After o banco de dados finishes its current operation, try to", - "full_action": "After o banco de dados finishes its current operation, try to\nrestorethedatabase.Or,thedatabaseadministratorneedstocheckifthedatabase\nestá ocupado e what operation it está performing." + "desc": "Restore failed due to MS-SQL-Server database in use NetBackup status codes 510 NetBackup status codes", + "first_action": "After the database finishes its current operation, try to", + "full_action": "After the database finishes its current operation, try to\nrestorethedatabase.Or,thedatabaseadministratorneedstocheckifthedatabase\nis busy and what operation it is performing." }, "2830": { "code": 2830, - "desc": "Restauração falhou due to um incorrect caminho in o MS-SQL-Server MOVE script", - "first_action": "Verifique o MOVE script e correct o caminho que foi", - "full_action": "Verifique o MOVE script e correct o caminho que foi\nspecified para o banco de dados log arquivo para o keyword TO." + "desc": "Restore failed due to an incorrect path in the MS-SQL-Server MOVE script", + "first_action": "Check the MOVE script and correct the path that was", + "full_action": "Check the MOVE script and correct the path that was\nspecified for the database log file for the keyword TO." }, "2831": { "code": 2831, - "desc": "Restauração erro", - "first_action": "Garanta que o cliente servidor list contains entradas para o master servidor e qualquer", - "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Garanta que o cliente servidor list contains entradas para o master servidor e qualquer\nmídia servers que can be used during um backup ou restauração.\n■ Examine o status ou o progress log on o cliente para messages on por que o\nrestauração falhou. Also, verifique o Todos Log Entradas relatório on o servidor.\n■ Verifique ownership e permissão on directories onde arquivos estão restored.\n■ Correct o problemas que you find e retry o restauração." + "desc": "Restore error", + "first_action": "Ensure that the client server list contains entries for the master server and any", + "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Ensure that the client server list contains entries for the master server and any\nmedia servers that can be used during a backup or restore.\n■ Examine the status or the progress log on the client for messages on why the\nrestore failed. Also, check the All Log Entries report on the server.\n■ Check ownership and permission on directories where files are restored.\n■ Correct the problems that you find and retry the restore." }, "2832": { "code": 2832, - "desc": "Restauração falhou due to rename arquivo format erro NetBackup status codes 511 NetBackup status codes", - "first_action": "If you desejar to execute o nbrestorevm comando e", - "full_action": "If you desejar to execute o nbrestorevm comando e\nmanuallyentertherenamefile,verifythatthefilecomplieswiththeformatspecified\nin o NetBackup Commands Reference Guide. Para additional informação, verifique\no job details in o Activity Monitor e o bprd log on o master servidor." + "desc": "Restore failed due to rename file format error NetBackup status codes 511 NetBackup status codes", + "first_action": "If you want to execute the nbrestorevm command and", + "full_action": "If you want to execute the nbrestorevm command and\nmanuallyentertherenamefile,verifythatthefilecomplieswiththeformatspecified\nin the NetBackup Commands Reference Guide. For additional information, check\nthe job details in the Activity Monitor and the bprd log on the master server." }, "2833": { "code": 2833, - "desc": "Restauração falhou due to partition restauração erro", + "desc": "Restore failed due to partition restore error", "first_action": "Ifanotherbackupcopyexists,makethatimagetheprimary", - "full_action": "Ifanotherbackupcopyexists,makethatimagetheprimary\ncopy e attempt to restauração from it. Para additional informação, verifique o job details\nin o Activity Monitor, o bprd log on o master servidor, e o bptm log on o\nmídia servidor." + "full_action": "Ifanotherbackupcopyexists,makethatimagetheprimary\ncopy and attempt to restore from it. For additional information, check the job details\nin the Activity Monitor, the bprd log on the master server, and the bptm log on the\nmedia server." }, "2834": { "code": 2834, - "desc": "Restauração falhou due to falha to ler change block bitmap", + "desc": "Restore failed due to failure to read change block bitmap", "first_action": "Ifanotherbackupcopyexists,makethatimagetheprimary", - "full_action": "Ifanotherbackupcopyexists,makethatimagetheprimary\ncopy e attempt to restauração from it. Para additional informação, verifique o job details\nin o Activity Monitor, o bprd log on o master servidor, e o bptm log on o\nmídia servidor." + "full_action": "Ifanotherbackupcopyexists,makethatimagetheprimary\ncopy and attempt to restore from it. For additional information, check the job details\nin the Activity Monitor, the bprd log on the master server, and the bptm log on the\nmedia server." }, "2835": { "code": 2835, - "desc": "Restauração falhou due to corrupt image", + "desc": "Restore failed due to corrupt image", "first_action": "Ifanotherbackupcopyexists,makethatimagetheprimary", - "full_action": "Ifanotherbackupcopyexists,makethatimagetheprimary\ncopy e attempt to restauração from it. Para additional informação, verifique o job details\nin o Activity Monitor, o bprd log on o master servidor, e o bptm log on o\nmídia servidor." + "full_action": "Ifanotherbackupcopyexists,makethatimagetheprimary\ncopy and attempt to restore from it. For additional information, check the job details\nin the Activity Monitor, the bprd log on the master server, and the bptm log on the\nmedia server." }, "2836": { "code": 2836, - "desc": "Restauração falhou because o bitmap size ler from o image header differs from o expected size.", + "desc": "Restore failed because the bitmap size read from the image header differs from the expected size.", "first_action": "Ifanotherbackupcopyexists,makethatimagetheprimary", - "full_action": "Ifanotherbackupcopyexists,makethatimagetheprimary\ncopy e attempt to restauração from it. Para additional informação, verifique o job details\nin o Activity Monitor, o bprd log on o master servidor, e o bptm log on o\nmídia servidor." + "full_action": "Ifanotherbackupcopyexists,makethatimagetheprimary\ncopy and attempt to restore from it. For additional information, check the job details\nin the Activity Monitor, the bprd log on the master server, and the bptm log on the\nmedia server." }, "2837": { "code": 2837, - "desc": "Restauração falhou due to inválido metadata", + "desc": "Restore failed due to invalid metadata", "first_action": "Ifanotherbackupcopyexists,makethatimagetheprimary", - "full_action": "Ifanotherbackupcopyexists,makethatimagetheprimary\ncopy e attempt to restauração from it. Para additional informação, verifique o job details\nin o Activity Monitor, o bprd log on o master servidor, e o bptm log on o\nmídia servidor." + "full_action": "Ifanotherbackupcopyexists,makethatimagetheprimary\ncopy and attempt to restore from it. For additional information, check the job details\nin the Activity Monitor, the bprd log on the master server, and the bptm log on the\nmedia server." }, "2838": { "code": 2838, - "desc": "Restauração falhou because não raw partitions foram found", + "desc": "Restore failed because no raw partitions were found", "first_action": "Verifythatthebackupimagecontainsalistofrawpartitions.", - "full_action": "Verifythatthebackupimagecontainsalistofrawpartitions.\nThiserrormayindicatethatthebackupimageisdefective.Foradditionalinformation,\nverifique o job details in o Activity Monitor, o bprd log on o master servidor, e\no bptm log on o mídia servidor." + "full_action": "Verifythatthebackupimagecontainsalistofrawpartitions.\nThiserrormayindicatethatthebackupimageisdefective.Foradditionalinformation,\ncheck the job details in the Activity Monitor, the bprd log on the master server, and\nthe bptm log on the media server." }, "2839": { "code": 2839, - "desc": "Restauração falhou due to inválido raw partition ID", + "desc": "Restore failed due to invalid raw partition ID", "first_action": "Ifanotherbackupcopyexists,makethatimagetheprimary", - "full_action": "Ifanotherbackupcopyexists,makethatimagetheprimary\ncopy e attempt to restauração from it. Para additional informação, verifique o job details\nin o Activity Monitor, o bprd log on o master servidor, e o bptm log on o\nmídia servidor." + "full_action": "Ifanotherbackupcopyexists,makethatimagetheprimary\ncopy and attempt to restore from it. For additional information, check the job details\nin the Activity Monitor, the bprd log on the master server, and the bptm log on the\nmedia server." }, "2840": { "code": 2840, - "desc": "Restauração falhou due to fora de sequence raw partitions", + "desc": "Restore failed due to out of sequence raw partitions", "first_action": "Ifanotherbackupcopyexists,makethatimagetheprimary", - "full_action": "Ifanotherbackupcopyexists,makethatimagetheprimary\ncopy e attempt to restauração from it. Para additional informação, verifique o job details\nin o Activity Monitor, o bprd log on o master servidor, e o bptm log on o\nmídia servidor." + "full_action": "Ifanotherbackupcopyexists,makethatimagetheprimary\ncopy and attempt to restore from it. For additional information, check the job details\nin the Activity Monitor, the bprd log on the master server, and the bptm log on the\nmedia server." }, "2841": { "code": 2841, - "desc": "Restauração falhou due to falha to ler o header from o backup image", + "desc": "Restore failed due to failure to read the header from the backup image", "first_action": "Ifanotherbackupcopyexists,makethatimagetheprimary", - "full_action": "Ifanotherbackupcopyexists,makethatimagetheprimary\ncopy e attempt to restauração from it. Para additional informação, verifique o job details\nin o Activity Monitor, o bprd log on o master servidor, e o bptm log on o\nmídia servidor." + "full_action": "Ifanotherbackupcopyexists,makethatimagetheprimary\ncopy and attempt to restore from it. For additional information, check the job details\nin the Activity Monitor, the bprd log on the master server, and the bptm log on the\nmedia server." }, "2842": { "code": 2842, - "desc": "Restauração falhou due to falha to ler o VMware bitmap", + "desc": "Restore failed due to failure to read the VMware bitmap", "first_action": "Ifanotherbackupcopyexists,makethatimagetheprimary", - "full_action": "Ifanotherbackupcopyexists,makethatimagetheprimary\ncopy e attempt to restauração from it. Para additional informação, verifique o job details\nin o Activity Monitor, o bprd log on o master servidor, e o bptm log on o\nmídia servidor." + "full_action": "Ifanotherbackupcopyexists,makethatimagetheprimary\ncopy and attempt to restore from it. For additional information, check the job details\nin the Activity Monitor, the bprd log on the master server, and the bptm log on the\nmedia server." }, "2843": { "code": 2843, - "desc": "Restauração falhou due to falha to start VxMS", - "first_action": "Verifique que o mídia servidor e o recovery host", - "full_action": "Verifique que o mídia servidor e o recovery host\nenvironment has adequate memória e correct arquivo permissions. Para additional\ninformação, verifique o job details in o Activity Monitor e o bprd log on o\nmaster servidor." + "desc": "Restore failed due to failure to start VxMS", + "first_action": "Verify that the media server and the recovery host", + "full_action": "Verify that the media server and the recovery host\nenvironment has adequate memory and correct file permissions. For additional\ninformation, check the job details in the Activity Monitor and the bprd log on the\nmaster server." }, "2844": { "code": 2844, - "desc": "Restauração falhou due to falha to ler o FIID arquivo", + "desc": "Restore failed due to failure to read the FIID file", "first_action": "Ifanotherbackupcopyexists,makethatimagetheprimary", - "full_action": "Ifanotherbackupcopyexists,makethatimagetheprimary\ncopy e attempt to restauração from it. Para additional informação, verifique o job details\nin o Activity Monitor, o bprd log on o master servidor, e o bptm log on o\nmídia servidor." + "full_action": "Ifanotherbackupcopyexists,makethatimagetheprimary\ncopy and attempt to restore from it. For additional information, check the job details\nin the Activity Monitor, the bprd log on the master server, and the bptm log on the\nmedia server." }, "2845": { "code": 2845, - "desc": "Restauração falhou due to falha to retrieve o bitmap", + "desc": "Restore failed due to failure to retrieve the bitmap", "first_action": "Ifanotherbackupcopyexists,makethatimagetheprimary", - "full_action": "Ifanotherbackupcopyexists,makethatimagetheprimary\ncopy e attempt to restauração from it. Para additional informação, verifique o job details\nin o Activity Monitor, o bprd log on o master servidor, e o bptm log on o\nmídia servidor." + "full_action": "Ifanotherbackupcopyexists,makethatimagetheprimary\ncopy and attempt to restore from it. For additional information, check the job details\nin the Activity Monitor, the bprd log on the master server, and the bptm log on the\nmedia server." }, "2846": { "code": 2846, - "desc": "Restauração falhou due to falha to retrieve o fsmap", + "desc": "Restore failed due to failure to retrieve the fsmap", "first_action": "Ifanotherbackupcopyexists,makethatimagetheprimary", - "full_action": "Ifanotherbackupcopyexists,makethatimagetheprimary\ncopy e attempt to restauração from it. Para additional informação, verifique o job details\nin o Activity Monitor, o bprd log on o master servidor, e o bptm log on o\nmídia servidor." + "full_action": "Ifanotherbackupcopyexists,makethatimagetheprimary\ncopy and attempt to restore from it. For additional information, check the job details\nin the Activity Monitor, the bprd log on the master server, and the bptm log on the\nmedia server." }, "2847": { "code": 2847, - "desc": "Restauração falhou due to falha to start o bptm writer", - "first_action": "Verifique que o mídia servidor e o recovery host", - "full_action": "Verifique que o mídia servidor e o recovery host\nenvironment has adequate memória e correct arquivo permissions. Para additional\ninformação, verifique o job details in o Activity Monitor e o bprd log on o\nmaster servidor." + "desc": "Restore failed due to failure to start the bptm writer", + "first_action": "Verify that the media server and the recovery host", + "full_action": "Verify that the media server and the recovery host\nenvironment has adequate memory and correct file permissions. For additional\ninformation, check the job details in the Activity Monitor and the bprd log on the\nmaster server." }, "2848": { "code": 2848, - "desc": "Restauração falhou due to falha to create o virtual machine", - "first_action": "Verifique que o VMware servidor has sufficient permissions.", - "full_action": "Do o seguinte:\n■ Verifique que o VMware servidor has sufficient permissions.\n■ Aumentar o space disponível para o datastore.\n■ Resolve qualquer configuration incompatibilities." + "desc": "Restore failed due to failure to create the virtual machine", + "first_action": "Check that the VMware server has sufficient permissions.", + "full_action": "Do the following:\n■ Check that the VMware server has sufficient permissions.\n■ Increase the space available for the datastore.\n■ Resolve any configuration incompatibilities." }, "2849": { "code": 2849, - "desc": "Restauração falhou due to falha to excluir o virtual machine snapshot", - "first_action": "Verifique que o VMware servidor has sufficient permissions to excluir um virtual", - "full_action": "Do o seguinte:\n■ Verifique que o VMware servidor has sufficient permissions to excluir um virtual\nmachine snapshot.\n■ Aumentar o space disponível para o datastore.\n■ Erro ou task cancellation on o VMware servidor.\nPara additional informação, verifique o job details in o Activity Monitor, o bprd log\non o master servidor, e o bptm log on o mídia servidor." + "desc": "Restore failed due to failure to delete the virtual machine snapshot", + "first_action": "Check that the VMware server has sufficient permissions to delete a virtual", + "full_action": "Do the following:\n■ Check that the VMware server has sufficient permissions to delete a virtual\nmachine snapshot.\n■ Increase the space available for the datastore.\n■ Error or task cancellation on the VMware server.\nFor additional information, check the job details in the Activity Monitor, the bprd log\non the master server, and the bptm log on the media server." }, "2850": { "code": 2850, - "desc": "Restauração erro", - "first_action": "Garanta que o client-server list contains entradas para o master servidor e qualquer", - "full_action": "Thisstatuscodecanappearformultipleworkloads.Please\nreview o seguinte informação para seu particular workload.\nPara general troubleshooting, try o seguinte possible solutions in o order\npresented:\n■ Garanta que o client-server list contains entradas para o master servidor e qualquer\nmídia servers que can be used during um backup ou restauração.\n■ Examine o status ou o progress log on o cliente para messages on por que o\nrestauração falhou. Also, verifique o Todos Log Entradas relatório on o servidor.\n■ Verifique ownership e permissão on directories onde arquivos estão restored.\n■ Correct o problemas que you find e retry o restauração.\nIn o case de Hadoop e HBase:\n■ Thiserrorisencounteredwhenanimportofanimageisusedtocreateacatalog\nentry e then afterwards um restauração está triggered. To troubleshoot this erro, refer\nto o seguinte procedure:\nTo troubleshoot o restauração falha:\n1 Create um rename arquivo com o ALT_APPLICATION_SERVER como o application\nservidor name. Provide o primary name node apenas (instead de alternate name\nnode). Garanta que o credentials para primary name node estão already present.\n2 Executar o restauração usando o bprestore comando.\nIn o case de Azure Stack e OpenStack:\n■ If o erro occurs para um AIR restauração scenario, restauração o catalog before you\nrestauração o AIR images.\nIn o case de Hadoop com Kerberos:\n■ ThisissuearisesiftheHDFSownerdoesnotsetownershipforfilesanddirectories\nou if there estão issues com Kerberos configuration. Before restoring, garanta o\nseguinte:\n■ Garanta que o HDFS owner usuário está used para Kerberos backup.\n■ Garanta que com o current Kerberos usuário, it está possible to set o\nowners/ACLSmanuallyusingHDFScommands,suchaschownandsetfacl." + "desc": "Restore error", + "first_action": "Ensure that the client-server list contains entries for the master server and any", + "full_action": "Thisstatuscodecanappearformultipleworkloads.Please\nreview the following information for your particular workload.\nFor general troubleshooting, try the following possible solutions in the order\npresented:\n■ Ensure that the client-server list contains entries for the master server and any\nmedia servers that can be used during a backup or restore.\n■ Examine the status or the progress log on the client for messages on why the\nrestore failed. Also, check the All Log Entries report on the server.\n■ Check ownership and permission on directories where files are restored.\n■ Correct the problems that you find and retry the restore.\nIn the case of Hadoop and HBase:\n■ Thiserrorisencounteredwhenanimportofanimageisusedtocreateacatalog\nentry and then afterwards a restore is triggered. To troubleshoot this error, refer\nto the following procedure:\nTo troubleshoot the restore failure:\n1 Create a rename file with the ALT_APPLICATION_SERVER as the application\nserver name. Provide the primary name node only (instead of alternate name\nnode). Ensure that the credentials for primary name node are already present.\n2 Perform the restore using the bprestore command.\nIn the case of Azure Stack and OpenStack:\n■ If the error occurs for an AIR restore scenario, restore the catalog before you\nrestore the AIR images.\nIn the case of Hadoop with Kerberos:\n■ ThisissuearisesiftheHDFSownerdoesnotsetownershipforfilesanddirectories\nor if there are issues with Kerberos configuration. Before restoring, ensure the\nfollowing:\n■ Ensure that the HDFS owner user is used for Kerberos backup.\n■ Ensure that with the current Kerberos user, it is possible to set the\nowners/ACLSmanuallyusingHDFScommands,suchaschownandsetfacl." }, "2864": { "code": 2864, - "desc": "O disaster recovery package could não be imported.", - "first_action": "Garanta que you estão usando o disaster recovery package", - "full_action": "Garanta que you estão usando o disaster recovery package\nque foi emailed to you ou um copy de o same package." + "desc": "The disaster recovery package could not be imported.", + "first_action": "Ensure that you are using the disaster recovery package", + "full_action": "Ensure that you are using the disaster recovery package\nthat was emailed to you or a copy of the same package." }, "2865": { "code": 2865, - "desc": "O banco de dados table could não be loaded.", + "desc": "The database table could not be loaded.", "first_action": "On UNIX: /usr/openv/db/bin/nbdb_ping", - "full_action": "Garanta que o NetBackup banco de dados está accessible while\no NetBackup banco de dados process está executando. Use o seguinte comando to verifique\nif o banco de dados está accessible:\n■ On UNIX: /usr/openv/db/bin/nbdb_ping\n■ On Windows: install_path\\NetBackup\\bin\\nbdb_ping" + "full_action": "Ensure that the NetBackup database is accessible while\nthe NetBackup database process is running. Use the following command to check\nif the database is accessible:\n■ On UNIX: /usr/openv/db/bin/nbdb_ping\n■ On Windows: install_path\\NetBackup\\bin\\nbdb_ping" }, "2866": { "code": 2866, - "desc": "O specified passphrase está incorrect.", - "first_action": "Garanta que o specified passphrase está o same como o", - "full_action": "Garanta que o specified passphrase está o same como o\nonethatyousetatthetimeofthecatalogbackupthatisassociatedwiththisdisaster\nrecovery package." + "desc": "The specified passphrase is incorrect.", + "first_action": "Ensure that the specified passphrase is the same as the", + "full_action": "Ensure that the specified passphrase is the same as the\nonethatyousetatthetimeofthecatalogbackupthatisassociatedwiththisdisaster\nrecovery package." }, "2869": { "code": 2869, - "desc": "O identity package está corrupt. NetBackup status codes 519 NetBackup status codes", - "first_action": "Use um different DR identity package ou use o steps que", - "full_action": "Use um different DR identity package ou use o steps que\nestão disponível in o seguinte article:\nhttps://www.veritas.com/support/en_US/article.000125933" + "desc": "The identity package is corrupt. NetBackup status codes 519 NetBackup status codes", + "first_action": "Use a different DR identity package or use the steps that", + "full_action": "Use a different DR identity package or use the steps that\nare available in the following article:\nhttps://www.veritas.com/support/en_US/article.000125933" }, "2870": { "code": 2870, - "desc": "O master servidor certificate não é possível be imported from o DR package to Windows certificate store.", - "first_action": "PFX arquivo caminho para o alternate diretório import :", - "full_action": "Try to restauração o disaster recovery (DR) package to um\nalternate diretório location e manually import o PFX arquivos into o Windows\ncertificate store. You can manually import o arquivos por double-clicking o PFX arquivos\nin o seguinte locations:\n■ PFX arquivo caminho para o alternate diretório import :\n■ alternate_directory\\directory_name\\usr\\openv\\netbackup\\tmp\\tempWinCredStore\\*.pfx\n■ Arquivo caminho de o PFX file’s password:\n■ alternate_directory\\directory_name\\usr\\openv\\netbackup\\tmp\\tempWinCredStore\\pfxPwdFile.txt" + "desc": "The master server certificate cannot be imported from the DR package to Windows certificate store.", + "first_action": "PFX file path for the alternate directory import :", + "full_action": "Try to restore the disaster recovery (DR) package to an\nalternate directory location and manually import the PFX files into the Windows\ncertificate store. You can manually import the files by double-clicking the PFX files\nin the following locations:\n■ PFX file path for the alternate directory import :\n■ alternate_directory\\directory_name\\usr\\openv\\netbackup\\tmp\\tempWinCredStore\\*.pfx\n■ File path of the PFX file’s password:\n■ alternate_directory\\directory_name\\usr\\openv\\netbackup\\tmp\\tempWinCredStore\\pfxPwdFile.txt" }, "2877": { "code": 2877, - "desc": "Hypervisor pre-restore operation falhou.", + "desc": "Hypervisor pre-restore operation failed.", "first_action": "Iftheproblempersists,contactCohesityTechnicalSupport.", "full_action": "Iftheproblempersists,contactCohesityTechnicalSupport." }, "2880": { "code": 2880, - "desc": "O recovery host in o restauração specification does não support in-place virtual machine disco restores. NetBackup status codes 520 NetBackup status codes", - "first_action": "To executar um in-place disco restauração, specify um recovery", - "full_action": "To executar um in-place disco restauração, specify um recovery\nhost com NetBackup version 8.3 ou later." + "desc": "The recovery host in the restore specification does not support in-place virtual machine disk restores. NetBackup status codes 520 NetBackup status codes", + "first_action": "To perform an in-place disk restore, specify a recovery", + "full_action": "To perform an in-place disk restore, specify a recovery\nhost with NetBackup version 8.3 or later." }, "2881": { "code": 2881, - "desc": "Falhou to query o data specific to disaster recovery package.", - "first_action": "Retry o operation e if o issue persists, visit", - "full_action": "Retry o operation e if o issue persists, visit\nsupport.veritas.com. O Cohesity Technical Support site offers additional\ninformação to help you troubleshoot this issue." + "desc": "Failed to query the data specific to disaster recovery package.", + "first_action": "Retry the operation and if the issue persists, visit", + "full_action": "Retry the operation and if the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support site offers additional\ninformation to help you troubleshoot this issue." }, "2882": { "code": 2882, - "desc": "Thespecifieddisasterrecoverypackageisbeingrestoredonahostwith um name que está different from o one onde o package foi created.", + "desc": "Thespecifieddisasterrecoverypackageisbeingrestoredonahostwith a name that is different from the one where the package was created.", "first_action": "Ensurethatthehostnamesmatchincaseofbothbackup", - "full_action": "Ensurethatthehostnamesmatchincaseofbothbackup\ne restauração de o disaster recovery package." + "full_action": "Ensurethatthehostnamesmatchincaseofbothbackup\nand restore of the disaster recovery package." }, "2883": { "code": 2883, - "desc": "One ou more users who have permissions to o identity arquivos que need to be salvo up como part de o DR package do não exist on o system.", - "first_action": "Either map o non-existing users to o appropriate users on o host ou skip", - "full_action": "Executar o seguinte como appropriate:\n■ Either map o non-existing users to o appropriate users on o host ou skip\nthem while retrying.\n■ If you install NetBackup in um disaster recovery mode, set o DR_PKG_MAPUSER\nenvironment variable com o mapping.\n■ Use o -mapuser option to provide o mapping ou skipping o ACLs de usuário.\nRefer to o NetBackup Commands Reference Guide para more details.\nIf o issue persists, visit support.veritas.com. O Cohesity Technical Support site\noffers additional informação to help you troubleshoot this issue." + "desc": "One or more users who have permissions to the identity files that need to be backed up as part of the DR package do not exist on the system.", + "first_action": "Either map the non-existing users to the appropriate users on the host or skip", + "full_action": "Perform the following as appropriate:\n■ Either map the non-existing users to the appropriate users on the host or skip\nthem while retrying.\n■ If you install NetBackup in a disaster recovery mode, set the DR_PKG_MAPUSER\nenvironment variable with the mapping.\n■ Use the -mapuser option to provide the mapping or skipping the ACLs of user.\nRefer to the NetBackup Commands Reference Guide for more details.\nIf the issue persists, visit support.veritas.com. The Cohesity Technical Support site\noffers additional information to help you troubleshoot this issue." }, "2887": { "code": 2887, - "desc": "Import de VM to vApp falhou.", - "first_action": "Garanta que o maximum number de VMs has não been excedido.", - "full_action": "Executar o seguinte como appropriate:\n■ Garanta que o maximum number de VMs has não been excedido.\n■ Garanta que there está enough allocated armazenamento." + "desc": "Import of VM to vApp failed.", + "first_action": "Ensure that the maximum number of VMs has not been exceeded.", + "full_action": "Perform the following as appropriate:\n■ Ensure that the maximum number of VMs has not been exceeded.\n■ Ensure that there is enough allocated storage." }, "2888": { "code": 2888, - "desc": "VM has been left at vCenter after import falha.", - "first_action": "O VM needs to be deleted ou imported manually.", - "full_action": "Executar o seguinte como appropriate:\n■ O VM needs to be deleted ou imported manually.\n■ Garanta que o maximum number de VMs has não been excedido.\n■ Garanta que there está enough allocated armazenamento.\n■ NetBackup can automatically excluir um VM on import falha. To enable this\noption, set DELETE_VM_ON_IMPORT_FAILURE = 1 in o bp.conf arquivo ou in o\nregistry on o master servidor." + "desc": "VM has been left at vCenter after import failure.", + "first_action": "The VM needs to be deleted or imported manually.", + "full_action": "Perform the following as appropriate:\n■ The VM needs to be deleted or imported manually.\n■ Ensure that the maximum number of VMs has not been exceeded.\n■ Ensure that there is enough allocated storage.\n■ NetBackup can automatically delete a VM on import failure. To enable this\noption, set DELETE_VM_ON_IMPORT_FAILURE = 1 in the bp.conf file or in the\nregistry on the master server." }, "2889": { "code": 2889, - "desc": "Kubernetes pre-restore operation falhou.", - "first_action": "Verifique if o data mover image está properly set in o data mover ConfigMap e", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique if o data mover image está properly set in o data mover ConfigMap e\no usuário have access to pull o image from o repository.\n■ Garanta que o armazenamento classes have o requerido NetBackup labels.\n■ Garanta que there estão enough resources on o cluster para spawning pods.\n■ Verifique NetBackup Kubernetes operator logs to know more details about o\nerro." + "desc": "Kubernetes pre-restore operation failed.", + "first_action": "Check if the data mover image is properly set in the data mover ConfigMap and", + "full_action": "Perform the following as appropriate:\n■ Check if the data mover image is properly set in the data mover ConfigMap and\nthe user have access to pull the image from the repository.\n■ Ensure that the storage classes have the required NetBackup labels.\n■ Ensure that there are enough resources on the cluster for spawning pods.\n■ Check NetBackup Kubernetes operator logs to know more details about the\nerror." }, "2890": { "code": 2890, - "desc": "Kubernetes restauração data operation falhou.", - "first_action": "Garanta que o data mover está executando properly.", - "full_action": "Executar o seguinte como appropriate:\n■ Garanta que o data mover está executando properly.\n■ Garanta que o mídia servidor está reachable from o data mover pod.\n■ Garanta que o host aliases estão present in o data mover ConfigMap if short\nnames estão in use.\n■ Garanta que o backupservercert está configurado in um correct manner on o\nKubernetes operator cluster." + "desc": "Kubernetes restore data operation failed.", + "first_action": "Ensure that the data mover is running properly.", + "full_action": "Perform the following as appropriate:\n■ Ensure that the data mover is running properly.\n■ Ensure that the media server is reachable from the data mover pod.\n■ Ensure that the host aliases are present in the data mover ConfigMap if short\nnames are in use.\n■ Ensure that the backupservercert is configured in a correct manner on the\nKubernetes operator cluster." }, "2891": { "code": 2891, - "desc": "Kubernetes post-restore operation falhou.", - "first_action": "To restauração um PVC to o original namespace, garanta que o PVC está não present", - "full_action": "Executar o seguinte como appropriate:\n■ To restauração um PVC to o original namespace, garanta que o PVC está não present\nin o original namespace before you start um restauração operation.\n■ Review o NetBackup Kubernetes operator logs to get more details about o\nerro." + "desc": "Kubernetes post-restore operation failed.", + "first_action": "To restore a PVC to the original namespace, ensure that the PVC is not present", + "full_action": "Perform the following as appropriate:\n■ To restore a PVC to the original namespace, ensure that the PVC is not present\nin the original namespace before you start a restore operation.\n■ Review the NetBackup Kubernetes operator logs to get more details about the\nerror." }, "2892": { "code": 2892, - "desc": "Kubernetes restauração from backup operation falhou.", - "first_action": "Garanta que o namespace has o NetBackup supported resources.", - "full_action": "Executar o seguinte como appropriate:\n■ Garanta que o namespace has o NetBackup supported resources.\n■ Verifique Kubernetes operator logs para more details about o erro." + "desc": "Kubernetes restore from backup operation failed.", + "first_action": "Ensure that the namespace has the NetBackup supported resources.", + "full_action": "Perform the following as appropriate:\n■ Ensure that the namespace has the NetBackup supported resources.\n■ Check Kubernetes operator logs for more details about the error." }, "2893": { "code": 2893, - "desc": "NetBackup FIPS mode está enabled e o specified disaster recovery package foi created on um host onde FIPS mode foi disabled.", - "first_action": "If you import um disaster recovery package from um system", - "full_action": "If you import um disaster recovery package from um system\nonde FIPS foi disabled, then disable FIPS on o current NetBackup system.\nThen you can try to import o disaster recovery package.\nPara more informação about disabling FIPS in NetBackup, refer to o NetBackup\nSecurity e Encryption Guide." + "desc": "NetBackup FIPS mode is enabled and the specified disaster recovery package was created on a host where FIPS mode was disabled.", + "first_action": "If you import a disaster recovery package from a system", + "full_action": "If you import a disaster recovery package from a system\nwhere FIPS was disabled, then disable FIPS on the current NetBackup system.\nThen you can try to import the disaster recovery package.\nFor more information about disabling FIPS in NetBackup, refer to the NetBackup\nSecurity and Encryption Guide." }, "2894": { "code": 2894, - "desc": "Falhou to create o instant access mount para cloud backup image.", - "first_action": "Reduce o number de instant access mounts e retry", - "full_action": "Reduce o number de instant access mounts e retry\no operation." + "desc": "Failed to create the instant access mount for cloud backup image.", + "first_action": "Reduce the number of instant access mounts and retry", + "full_action": "Reduce the number of instant access mounts and retry\nthe operation." }, "2897": { "code": 2897, "desc": "Instant access mount point already exists.", - "first_action": "Para detailed troubleshooting informação, create um debug", - "full_action": "Para detailed troubleshooting informação, create um debug\nlogdirectoryfortheprocessthatreturnedthisstatuscode.Thenretrytheoperation\ne verifique o resulting bprd logs on o master servidor." + "first_action": "For detailed troubleshooting information, create a debug", + "full_action": "For detailed troubleshooting information, create a debug\nlogdirectoryfortheprocessthatreturnedthisstatuscode.Thenretrytheoperation\nand check the resulting bprd logs on the master server." }, "3000": { "code": 3000, "desc": "TousetheAllowdynamicmulti-streamingoption,theVSOFIMshould be selected in snapshot options.", - "first_action": "Update o policy configuration to select o VSO como", - "full_action": "Update o policy configuration to select o VSO como\nsnapshot method." + "first_action": "Update the policy configuration to select the VSO as", + "full_action": "Update the policy configuration to select the VSO as\nsnapshot method." }, "3002": { "code": 3002, - "desc": "Clienttimed-outwaitingfor sistema de arquivos crawler to populatethe filelist in o shared memória.", - "first_action": "Garanta rede connectivity between o backup host", - "full_action": "Garanta rede connectivity between o backup host\ne volume está consistent. Resume ou restart o policy backup." + "desc": "Clienttimed-outwaitingfor filesystem crawler to populatethe filelist in the shared memory.", + "first_action": "Ensure network connectivity between the backup host", + "full_action": "Ensure network connectivity between the backup host\nand volume is consistent. Resume or restart the policy backup." }, "3003": { "code": 3003, - "desc": "O arquivo system crawler process timed-out waiting para streams to attach com shared memória. NetBackup status codes 525 NetBackup status codes", - "first_action": "Garanta que rede connectivity de o backup host está", - "full_action": "Garanta que rede connectivity de o backup host está\nconsistent." + "desc": "The file system crawler process timed-out waiting for streams to attach with shared memory. NetBackup status codes 525 NetBackup status codes", + "first_action": "Ensure that network connectivity of the backup host is", + "full_action": "Ensure that network connectivity of the backup host is\nconsistent." }, "3004": { "code": 3004, "desc": "Theoff-hostbackupfortheNAS-Data-Protectionpolicywasnotselected.", - "first_action": "Configure o policy to enable o off-host backup e", - "full_action": "Configure o policy to enable o off-host backup e\nselect um backup host pool." + "first_action": "Configure the policy to enable the off-host backup and", + "full_action": "Configure the policy to enable the off-host backup and\nselect a backup host pool." }, "3005": { "code": 3005, - "desc": "InstantRecoverysnapshotonlyoptionisnotsupportedifthecheckpoint option está selected.", - "first_action": "Change o policy type to Armazenamento Lifecycle Policies.", - "full_action": "Change o policy type to Armazenamento Lifecycle Policies." + "desc": "InstantRecoverysnapshotonlyoptionisnotsupportedifthecheckpoint option is selected.", + "first_action": "Change the policy type to Storage Lifecycle Policies.", + "full_action": "Change the policy type to Storage Lifecycle Policies." }, "3006": { "code": 3006, - "desc": "Para NAS-Data-Protection policy, o policy armazenamento must be Armazenamento Lifecycle Policies ou select o Override policy armazenamento selection option while schedules estão configurado.", - "first_action": "Change o policy type to Armazenamento Lifecycle Policies.", - "full_action": "Change o policy type to Armazenamento Lifecycle Policies." + "desc": "For NAS-Data-Protection policy, the policy storage must be Storage Lifecycle Policies or select the Override policy storage selection option while schedules are configured.", + "first_action": "Change the policy type to Storage Lifecycle Policies.", + "full_action": "Change the policy type to Storage Lifecycle Policies." }, "3007": { "code": 3007, - "desc": "Para NAS-Data-Protection policy, o destination cliente não é possível be used to restauração.", + "desc": "For NAS-Data-Protection policy, the destination client cannot be used to restore.", "first_action": "SelectasourceclientasaNASarrayheadanddestination", - "full_action": "SelectasourceclientasaNASarrayheadanddestination\ncliente como backup host to mount o volume ou o share." + "full_action": "SelectasourceclientasaNASarrayheadanddestination\nclient as backup host to mount the volume or the share." }, "3008": { "code": 3008, - "desc": "Falhou to get requerido value from MediaDescription.", - "first_action": "Garanta que connectivity to master servidor está consistent to", - "full_action": "Garanta que connectivity to master servidor está consistent to\navoid partial retrieval de image data." + "desc": "Failed to get required value from MediaDescription.", + "first_action": "Ensure that connectivity to master server is consistent to", + "full_action": "Ensure that connectivity to master server is consistent to\navoid partial retrieval of image data." }, "3009": { "code": 3009, - "desc": "Para NAS-Data-Protection policy, o value de o Maximum jobs per policyattributemustbegreaterthantheMaximumnumberofstreamspervolume attribute", - "first_action": "Update o values de Maximum jobs per policy in o", - "full_action": "Update o values de Maximum jobs per policy in o\nhost properties to accommodate selected streams." + "desc": "For NAS-Data-Protection policy, the value of the Maximum jobs per policyattributemustbegreaterthantheMaximumnumberofstreamspervolume attribute", + "first_action": "Update the values of Maximum jobs per policy in the", + "full_action": "Update the values of Maximum jobs per policy in the\nhost properties to accommodate selected streams." }, "3010": { "code": 3010, - "desc": "Para NAS-Data-Protection policy, o off-host backup e use backup host pool options must be selected.", - "first_action": "Configure o policy to enable off-host backup e then", - "full_action": "Configure o policy to enable off-host backup e then\nselect o backup host pool." + "desc": "For NAS-Data-Protection policy, the off-host backup and use backup host pool options must be selected.", + "first_action": "Configure the policy to enable off-host backup and then", + "full_action": "Configure the policy to enable off-host backup and then\nselect the backup host pool." }, "3011": { "code": 3011, - "desc": "Para NAS-Data-Protection policy, um backup host pool name must be configurado in o policy.", - "first_action": "Configure o NAS-Data-Protection policy to enable", - "full_action": "Configure o NAS-Data-Protection policy to enable\noff-host backup e select o backup host pool." + "desc": "For NAS-Data-Protection policy, a backup host pool name must be configured in the policy.", + "first_action": "Configure the NAS-Data-Protection policy to enable", + "full_action": "Configure the NAS-Data-Protection policy to enable\noff-host backup and select the backup host pool." }, "3012": { "code": 3012, - "desc": "Falhou to get local host name.", - "first_action": "Garanta todos NetBackup services estão up e executando on o", - "full_action": "Garanta todos NetBackup services estão up e executando on o\nbackup host." + "desc": "Failed to get local host name.", + "first_action": "Ensure all NetBackup services are up and running on the", + "full_action": "Ensure all NetBackup services are up and running on the\nbackup host." }, "3013": { "code": 3013, - "desc": "O SnapshotonlySLPis não supportedfor o NAS-Data-Protection policy.", - "first_action": "Configure o Backup From Snapshot to existing SLP", - "full_action": "Configure o Backup From Snapshot to existing SLP\ncomo um second operation." + "desc": "The SnapshotonlySLPis not supportedfor the NAS-Data-Protection policy.", + "first_action": "Configure the Backup From Snapshot to existing SLP", + "full_action": "Configure the Backup From Snapshot to existing SLP\nas a second operation." }, "3014": { "code": 3014, - "desc": "Falhou to generate vendor change tracking informação.", - "first_action": "Retry o operation. If o issue persists, review o", - "full_action": "Retry o operation. If o issue persists, review o\nflexsnap logs." + "desc": "Failed to generate vendor change tracking information.", + "first_action": "Retry the operation. If the issue persists, review the", + "full_action": "Retry the operation. If the issue persists, review the\nflexsnap logs." }, "3016": { "code": 3016, - "desc": "Falhou to fetch o vendor change tracking task details.", - "first_action": "Garanta que o Snapshot Manager services estão up e", - "full_action": "Garanta que o Snapshot Manager services estão up e\nexecutando." + "desc": "Failed to fetch the vendor change tracking task details.", + "first_action": "Ensure that the Snapshot Manager services are up and", + "full_action": "Ensure that the Snapshot Manager services are up and\nrunning." }, "3017": { "code": 3017, - "desc": "Falhou to get snapshot diff.", + "desc": "Failed to get snapshot diff.", "first_action": "Retrytheoperation.Iftheissuepersists,refertoflexsnap", "full_action": "Retrytheoperation.Iftheissuepersists,refertoflexsnap\nlogs." }, "3018": { "code": 3018, - "desc": "Snapshot does não support diff capability.", - "first_action": "Clear o Enable vendor change tracking para", - "full_action": "Clear o Enable vendor change tracking para\nincremental backups verifique box in o policy configuration." + "desc": "Snapshot does not support diff capability.", + "first_action": "Clear the Enable vendor change tracking for", + "full_action": "Clear the Enable vendor change tracking for\nincremental backups check box in the policy configuration." }, "3019": { "code": 3019, - "desc": "Base snapshot ID está unknown to get diff.", - "first_action": "Update o policy schedule to create cheio backup first e then create um", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Update o policy schedule to create cheio backup first e then create um\nincremental backup.\n■ When um new NAS volume está added ou discovered in o NAS-Data-Protection\npolicy, executar um backup usando o cheio schedule.\n■ Adjustthesnapshotcopyretentionsettingtoensurethatthesnapshotisavailable\nwhen um incremental backup starts." + "desc": "Base snapshot ID is unknown to get diff.", + "first_action": "Update the policy schedule to create full backup first and then create an", + "full_action": "Perform the following, as appropriate:\n■ Update the policy schedule to create full backup first and then create an\nincremental backup.\n■ When a new NAS volume is added or discovered in the NAS-Data-Protection\npolicy, perform a backup using the full schedule.\n■ Adjustthesnapshotcopyretentionsettingtoensurethatthesnapshotisavailable\nwhen an incremental backup starts." }, "3021": { "code": 3021, - "desc": "Falhou to get todos snapshot diffs.", + "desc": "Failed to get all snapshot diffs.", "first_action": "Retrytheoperation.Iftheissuepersists,refertoflexsnap", "full_action": "Retrytheoperation.Iftheissuepersists,refertoflexsnap\nlogs." }, "3022": { "code": 3022, - "desc": "Falhou to parse o response de o create vendor change tracking informação.", - "first_action": "Refer o NetBackup Compatibility List to verifique que o", - "full_action": "Refer o NetBackup Compatibility List to verifique que o\ninstalado version de Snapshot Manager está supported." + "desc": "Failed to parse the response of the create vendor change tracking information.", + "first_action": "Refer the NetBackup Compatibility List to verify that the", + "full_action": "Refer the NetBackup Compatibility List to verify that the\ninstalled version of Snapshot Manager is supported." }, "3023": { "code": 3023, - "desc": "Falhou to parse o response de o get vendor change tracking informação. NetBackup status codes 530 NetBackup status codes", - "first_action": "Refer o NetBackup Compatibility List to verifique que o", - "full_action": "Refer o NetBackup Compatibility List to verifique que o\ninstalado version de Snapshot Manager está supported." + "desc": "Failed to parse the response of the get vendor change tracking information. NetBackup status codes 530 NetBackup status codes", + "first_action": "Refer the NetBackup Compatibility List to verify that the", + "full_action": "Refer the NetBackup Compatibility List to verify that the\ninstalled version of Snapshot Manager is supported." }, "3024": { "code": 3024, - "desc": "Falhou to parse o response de get todos snapshot diffs.", - "first_action": "Refer o NetBackup Compatibility List to verifique que o", - "full_action": "Refer o NetBackup Compatibility List to verifique que o\ninstalado version de Snapshot Manager está supported." + "desc": "Failed to parse the response of get all snapshot diffs.", + "first_action": "Refer the NetBackup Compatibility List to verify that the", + "full_action": "Refer the NetBackup Compatibility List to verify that the\ninstalled version of Snapshot Manager is supported." }, "3025": { "code": 3025, - "desc": "Falhou to find o existing diff para given snapshots.", - "first_action": "Update o policy schedule to create um cheio backup first.", - "full_action": "Update o policy schedule to create um cheio backup first." + "desc": "Failed to find the existing diff for given snapshots.", + "first_action": "Update the policy schedule to create a full backup first.", + "full_action": "Update the policy schedule to create a full backup first." }, "3026": { "code": 3026, - "desc": "Para o NAS-Data-Protection policy, o snapshot method argument max_snapshots está não supported.", - "first_action": "Configure o snapshot arguments e add o", - "full_action": "Configure o snapshot arguments e add o\nconfigurations again to o policy." + "desc": "For the NAS-Data-Protection policy, the snapshot method argument max_snapshots is not supported.", + "first_action": "Configure the snapshot arguments and add the", + "full_action": "Configure the snapshot arguments and add the\nconfigurations again to the policy." }, "3027": { "code": 3027, - "desc": "Para o NAS-Data-Protection policy, o Maximum snapshot limite retention option está não supported in SLP.", - "first_action": "Configure time-based retention ou expire after copy", - "full_action": "Configure time-based retention ou expire after copy\nretention in o SLP." + "desc": "For the NAS-Data-Protection policy, the Maximum snapshot limit retention option is not supported in SLP.", + "first_action": "Configure time-based retention or expire after copy", + "full_action": "Configure time-based retention or expire after copy\nretention in the SLP." }, "3028": { "code": 3028, - "desc": "Para o NAS-Data-Protection policy, if o Enable vendor change tracking para incremental backup option está enabled, o Expire after copy option retention está não supported.", - "first_action": "Update o SLP to set time-based retention.", - "full_action": "Update o SLP to set time-based retention." + "desc": "For the NAS-Data-Protection policy, if the Enable vendor change tracking for incremental backup option is enabled, the Expire after copy option retention is not supported.", + "first_action": "Update the SLP to set time-based retention.", + "full_action": "Update the SLP to set time-based retention." }, "3030": { "code": 3030, "desc": "Failedtocreateacheckpointdirectoryfordynamicdatastreambackups.", - "first_action": "Garanta que connectivity to o backup host está consistent", - "full_action": "Garanta que connectivity to o backup host está consistent\ne NetBackup services estão up e executando." + "first_action": "Ensure that connectivity to the backup host is consistent", + "full_action": "Ensure that connectivity to the backup host is consistent\nand NetBackup services are up and running." }, "3031": { "code": 3031, - "desc": "Falhou to create um checkpoint arquivo para saving o shared memória state.", - "first_action": "Garanta que connectivity to o backup host está consistent", - "full_action": "Garanta que connectivity to o backup host está consistent\ne NetBackup services estão up e executando." + "desc": "Failed to create a checkpoint file for saving the shared memory state.", + "first_action": "Ensure that connectivity to the backup host is consistent", + "full_action": "Ensure that connectivity to the backup host is consistent\nand NetBackup services are up and running." }, "3032": { "code": 3032, - "desc": "Falhou to save shared memória state in checkpoint arquivo.", - "first_action": "Garanta que connectivity to o backup host está consistent", - "full_action": "Garanta que connectivity to o backup host está consistent\ne NetBackup services estão up e executando." + "desc": "Failed to save shared memory state in checkpoint file.", + "first_action": "Ensure that connectivity to the backup host is consistent", + "full_action": "Ensure that connectivity to the backup host is consistent\nand NetBackup services are up and running." }, "3033": { "code": 3033, - "desc": "Failedtorenametemporarycheckpointfile.Resumeoperationforcurrent job might não be able to use checkpoint informação.", - "first_action": "Garanta que connectivity to backup host está consistent e", - "full_action": "Garanta que connectivity to backup host está consistent e\nNetBackup services estão up e executando." + "desc": "Failedtorenametemporarycheckpointfile.Resumeoperationforcurrent job might not be able to use checkpoint information.", + "first_action": "Ensure that connectivity to backup host is consistent and", + "full_action": "Ensure that connectivity to backup host is consistent and\nNetBackup services are up and running." }, "3034": { "code": 3034, - "desc": "Falhou to access checkpoint diretório. Resume operation para o current job commences from o start.", - "first_action": "Garanta que connectivity to o backup host está consistent", - "full_action": "Garanta que connectivity to o backup host está consistent\ne NetBackup services estão up e executando." + "desc": "Failed to access checkpoint directory. Resume operation for the current job commences from the start.", + "first_action": "Ensure that connectivity to the backup host is consistent", + "full_action": "Ensure that connectivity to the backup host is consistent\nand NetBackup services are up and running." }, "3035": { "code": 3035, - "desc": "Failedtoreaddatafromcheckpointfile.Resumeoperationforthecurrent job commences from o start.", - "first_action": "Garanta que connectivity to o backup host está consistent", - "full_action": "Garanta que connectivity to o backup host está consistent\ne NetBackup services estão up e executando." + "desc": "Failedtoreaddatafromcheckpointfile.Resumeoperationforthecurrent job commences from the start.", + "first_action": "Ensure that connectivity to the backup host is consistent", + "full_action": "Ensure that connectivity to the backup host is consistent\nand NetBackup services are up and running." }, "3036": { "code": 3036, - "desc": "Falhou to fetch o checkpoint arquivo para reading o shared memória state from master servidor.", - "first_action": "Garanta que connectivity to o backup host está consistent", - "full_action": "Garanta que connectivity to o backup host está consistent\ne NetBackup services estão up e executando." + "desc": "Failed to fetch the checkpoint file for reading the shared memory state from master server.", + "first_action": "Ensure that connectivity to the backup host is consistent", + "full_action": "Ensure that connectivity to the backup host is consistent\nand NetBackup services are up and running." }, "3037": { "code": 3037, - "desc": "Failedtopushcheckpointfiletostoresharedmemorystatefiletomaster servidor.", - "first_action": "Garanta que connectivity to o backup host está consistent", - "full_action": "Garanta que connectivity to o backup host está consistent\ne NetBackup services estão up e executando." + "desc": "Failedtopushcheckpointfiletostoresharedmemorystatefiletomaster server.", + "first_action": "Ensure that connectivity to the backup host is consistent", + "full_action": "Ensure that connectivity to the backup host is consistent\nand NetBackup services are up and running." }, "3041": { "code": 3041, - "desc": "Falhou to get shared memória identifier.", + "desc": "Failed to get shared memory identifier.", "first_action": "Ensurethatenoughmemoryisavailabletocreateashared", - "full_action": "Ensurethatenoughmemoryisavailabletocreateashared\nmemória on o backup host." + "full_action": "Ensurethatenoughmemoryisavailabletocreateashared\nmemory on the backup host." }, "3042": { "code": 3042, - "desc": "Falhou to attach com shared memória identifier.", - "first_action": "Retry o backup operation.", - "full_action": "Retry o backup operation." + "desc": "Failed to attach with shared memory identifier.", + "first_action": "Retry the backup operation.", + "full_action": "Retry the backup operation." }, "3043": { "code": 3043, "desc": "Failedtocreatesharedmemoryconfigurationdirectoryfordynamicdata stream backups.", - "first_action": "Garanta que connectivity to o backup host está consistent", - "full_action": "Garanta que connectivity to o backup host está consistent\ne NetBackup services estão up e executando." + "first_action": "Ensure that connectivity to the backup host is consistent", + "full_action": "Ensure that connectivity to the backup host is consistent\nand NetBackup services are up and running." }, "3044": { "code": 3044, - "desc": "Falhou to abrir shared memória configuration arquivo.", - "first_action": "Garanta que connectivity to o backup host está consistent", - "full_action": "Garanta que connectivity to o backup host está consistent\ne NetBackup services estão up e executando." + "desc": "Failed to open shared memory configuration file.", + "first_action": "Ensure that connectivity to the backup host is consistent", + "full_action": "Ensure that connectivity to the backup host is consistent\nand NetBackup services are up and running." }, "3045": { "code": 3045, - "desc": "Falhou to save shared memória informação in configuration arquivo.", - "first_action": "Garanta que connectivity to o backup host está consistent", - "full_action": "Garanta que connectivity to o backup host está consistent\ne NetBackup services estão up e executando." + "desc": "Failed to save shared memory information in configuration file.", + "first_action": "Ensure that connectivity to the backup host is consistent", + "full_action": "Ensure that connectivity to the backup host is consistent\nand NetBackup services are up and running." }, "3047": { "code": 3047, - "desc": "Para NAS-Data-Protection policy, armazenamento unidade disco type should be AdvancedDisk ou PureDisk.", - "first_action": "Garanta que o destination armazenamento in armazenamento lifecycle", - "full_action": "Garanta que o destination armazenamento in armazenamento lifecycle\npolicy está AdvancedDisk, PureDisk, ou um armazenamento unidade group de these disco types." + "desc": "For NAS-Data-Protection policy, storage unit disk type should be AdvancedDisk or PureDisk.", + "first_action": "Ensure that the destination storage in storage lifecycle", + "full_action": "Ensure that the destination storage in storage lifecycle\npolicy is AdvancedDisk, PureDisk, or a storage unit group of these disk types." }, "3049": { "code": 3049, - "desc": "Vendor change tracking enabled backups estão não supported para NetApp armazenamento array.", - "first_action": "Garanta o Vendor Change Tracking (VCT) verifique box está cleared in o policy ou", - "full_action": "Executar o seguinte como appropriate:\nGaranta o Vendor Change Tracking (VCT) verifique box está cleared in o policy ou\nque o backup from snapshot operation está removed from SLP when you executar\num backup de NetApp array volume." + "desc": "Vendor change tracking enabled backups are not supported for NetApp storage array.", + "first_action": "Ensure the Vendor Change Tracking (VCT) check box is cleared in the policy or", + "full_action": "Perform the following as appropriate:\nEnsure the Vendor Change Tracking (VCT) check box is cleared in the policy or\nthat the backup from snapshot operation is removed from SLP when you perform\na backup of NetApp array volume." }, "3050": { "code": 3050, - "desc": "O vendor change tracking enabled index from um snapshot job has falhou to synthesize o catalog.", - "first_action": "Disable VCT in o policy e run o index from snapshot job com cheio schedule.", - "full_action": "Executar o seguinte como appropriate:\nDisable VCT in o policy e run o index from snapshot job com cheio schedule." + "desc": "The vendor change tracking enabled index from a snapshot job has failed to synthesize the catalog.", + "first_action": "Disable VCT in the policy and run the index from snapshot job with full schedule.", + "full_action": "Perform the following as appropriate:\nDisable VCT in the policy and run the index from snapshot job with full schedule." }, "3052": { "code": 3052, - "desc": "Não foi possível to retrieve o NetBackup version para o host.", - "first_action": "Garanta que you have selected o correct destination", - "full_action": "Garanta que you have selected o correct destination\nservidor e o primary servidor services estão up e executando." + "desc": "Unable to retrieve the NetBackup version for the host.", + "first_action": "Ensure that you have selected the correct destination", + "full_action": "Ensure that you have selected the correct destination\nserver and the primary server services are up and running." }, "3053": { "code": 3053, - "desc": "ThemounthostmustbeatNetBackupversion10.5orgreatertosupport Parallel Restauração usando Snapshot Copy.", - "first_action": "Use um single stream to restauração o data from o snapshot ou o replica copy.", - "full_action": "Executar o seguinte como appropriate:\n■ Use um single stream to restauração o data from o snapshot ou o replica copy.\n■ To executar um restauração com parallel streams, upgrade o existing mount host to\nNetBackup version 10.5 ou higher. Seu mount host está o backup host que you\nuse to executar o snapshot operation." + "desc": "ThemounthostmustbeatNetBackupversion10.5orgreatertosupport Parallel Restore using Snapshot Copy.", + "first_action": "Use a single stream to restore the data from the snapshot or the replica copy.", + "full_action": "Perform the following as appropriate:\n■ Use a single stream to restore the data from the snapshot or the replica copy.\n■ To perform a restore with parallel streams, upgrade the existing mount host to\nNetBackup version 10.5 or higher. Your mount host is the backup host that you\nuse to perform the snapshot operation." }, "3054": { "code": 3054, - "desc": "O destination cliente must be at NetBackup version 10.5 ou greater to support Parallel Restauração usando Snapshot Copy.", - "first_action": "Use um single stream to restauração o data from o snapshot ou o replica copy.", - "full_action": "Executar o seguinte como appropriate:\n■ Use um single stream to restauração o data from o snapshot ou o replica copy.\n■ To executar um restauração com parallel streams, upgrade o existing destination\ncliente to NetBackup version 10.5 ou higher." + "desc": "The destination client must be at NetBackup version 10.5 or greater to support Parallel Restore using Snapshot Copy.", + "first_action": "Use a single stream to restore the data from the snapshot or the replica copy.", + "full_action": "Perform the following as appropriate:\n■ Use a single stream to restore the data from the snapshot or the replica copy.\n■ To perform a restore with parallel streams, upgrade the existing destination\nclient to NetBackup version 10.5 or higher." }, "3200": { "code": 3200, - "desc": "Um arquivo foi skipped because it foi in o process de being salvo up.", - "first_action": "Garanta que o backup arquivo está não in use e está ready para", - "full_action": "Garanta que o backup arquivo está não in use e está ready para\nbackup. Also, you can verifique que o arquivo está in o process de being salvo up." + "desc": "A file was skipped because it was in the process of being backed up.", + "first_action": "Ensure that the backup file is not in use and is ready for", + "full_action": "Ensure that the backup file is not in use and is ready for\nbackup. Also, you can verify that the file is in the process of being backed up." }, "3201": { "code": 3201, - "desc": "Cassandra version está não supported.", - "first_action": "Verifique if NetBackup supports o instalado Cassandra", - "full_action": "Verifique if NetBackup supports o instalado Cassandra\nversion por reviewing o seguinte:\nNetBackup Compatibility List para todos Versions" + "desc": "Cassandra version is not supported.", + "first_action": "Verify if NetBackup supports the installed Cassandra", + "full_action": "Verify if NetBackup supports the installed Cassandra\nversion by reviewing the following:\nNetBackup Compatibility List for all Versions" }, "3202": { "code": 3202, - "desc": "O OS platform version está não supported.", - "first_action": "Verifique if NetBackup supports o OS platform versions para", - "full_action": "Verifique if NetBackup supports o OS platform versions para\no Cassandra clusters por reviewing o seguinte:\nNetBackup Compatibility List para todos Versions" + "desc": "The OS platform version is not supported.", + "first_action": "Verify if NetBackup supports the OS platform versions for", + "full_action": "Verify if NetBackup supports the OS platform versions for\nthe Cassandra clusters by reviewing the following:\nNetBackup Compatibility List for all Versions" }, "3203": { "code": 3203, - "desc": "O CBR node hash in o tpconfig comando e Cassandra configuration does não match.", - "first_action": "Verifique que o CBR node hash in both o Cassandra", - "full_action": "Verifique que o CBR node hash in both o Cassandra\nconfiguration arquivo e o tpconfig comando match." + "desc": "The CBR node hash in the tpconfig command and Cassandra configuration does not match.", + "first_action": "Verify that the CBR node hash in both the Cassandra", + "full_action": "Verify that the CBR node hash in both the Cassandra\nconfiguration file and the tpconfig command match." }, "3204": { "code": 3204, - "desc": "Data Staging Servidor node parameters estão não specified.", - "first_action": "Verifique que o Data Staging Servidor node entradas estão", - "full_action": "Verifique que o Data Staging Servidor node entradas estão\ndisponível in o Cassandra configuration arquivo." + "desc": "Data Staging Server node parameters are not specified.", + "first_action": "Verify that the Data Staging Server node entries are", + "full_action": "Verify that the Data Staging Server node entries are\navailable in the Cassandra configuration file." }, "3205": { "code": 3205, - "desc": "O username de o Data Staging Servidor node está não specified para o Secure Shell conexão.", - "first_action": "Verifique que o username de o Data Staging Servidor node", - "full_action": "Verifique que o username de o Data Staging Servidor node\nestá specified in o tpconfig comando." + "desc": "The username of the Data Staging Server node is not specified for the Secure Shell connection.", + "first_action": "Verify that the username of the Data Staging Server node", + "full_action": "Verify that the username of the Data Staging Server node\nis specified in the tpconfig command." }, "3206": { "code": 3206, - "desc": "DataStagingServernodepasswordisnotspecifiedfortheSecureShell conexão.", - "first_action": "Verifique if o password de o Data Staging Servidor node está", - "full_action": "Verifique if o password de o Data Staging Servidor node está\nspecified in o tpconfig comando." + "desc": "DataStagingServernodepasswordisnotspecifiedfortheSecureShell connection.", + "first_action": "Verify if the password of the Data Staging Server node is", + "full_action": "Verify if the password of the Data Staging Server node is\nspecified in the tpconfig command." }, "3207": { "code": 3207, - "desc": "Data folder está não specified in o configuration para Data Staging Servidor node. NetBackup status codes 539 NetBackup status codes", - "first_action": "Garanta que o Cassandra Data folder está specified in o", - "full_action": "Garanta que o Cassandra Data folder está specified in o\nCassandra configuration arquivo para o Data Staging Servidor node." + "desc": "Data folder is not specified in the configuration for Data Staging Server node. NetBackup status codes 539 NetBackup status codes", + "first_action": "Ensure that the Cassandra Data folder is specified in the", + "full_action": "Ensure that the Cassandra Data folder is specified in the\nCassandra configuration file for the Data Staging Server node." }, "3208": { "code": 3208, - "desc": "Data Staging Servidor node keyhashes estão não specified.", - "first_action": "Verifique que o Data Staging Servidor node keyhashes estão", - "full_action": "Verifique que o Data Staging Servidor node keyhashes estão\nspecified in o Cassandra configuration arquivo." + "desc": "Data Staging Server node keyhashes are not specified.", + "first_action": "Verify that the Data Staging Server node keyhashes are", + "full_action": "Verify that the Data Staging Server node keyhashes are\nspecified in the Cassandra configuration file." }, "3209": { "code": 3209, "desc": "TheusernameofDataStagingServerCassandraclusterisnotspecified.", - "first_action": "Verifique que o username de o Data Staging Servidor", - "full_action": "Verifique que o username de o Data Staging Servidor\nCassandra cluster está specified in o tpconfig comando." + "first_action": "Verify that the username of the Data Staging Server", + "full_action": "Verify that the username of the Data Staging Server\nCassandra cluster is specified in the tpconfig command." }, "3210": { "code": 3210, "desc": "DataStagingServerpasswordfortheCassandraclusterisnotspecified.", - "first_action": "Verifique que o password de o Data Staging Servidor para", - "full_action": "Verifique que o password de o Data Staging Servidor para\no Cassandra cluster está mentioned in tpconfig comando." + "first_action": "Verify that the password of the Data Staging Server for", + "full_action": "Verify that the password of the Data Staging Server for\nthe Cassandra cluster is mentioned in tpconfig command." }, "3211": { "code": 3211, - "desc": "Cassandra cluster name de Data Staging Servidor node está não specified.", + "desc": "Cassandra cluster name of Data Staging Server node is not specified.", "first_action": "VerifythattheCassandraclusternameoftheDataStaging", - "full_action": "VerifythattheCassandraclusternameoftheDataStaging\nServidor node está specified in o tpconfig comando." + "full_action": "VerifythattheCassandraclusternameoftheDataStaging\nServer node is specified in the tpconfig command." }, "3212": { "code": 3212, - "desc": "Snapshot name está não specified.", - "first_action": "Review o nbaapidiscv log ou o nbaapireq_handler", - "full_action": "Review o nbaapidiscv log ou o nbaapireq_handler\nlog para more details." + "desc": "Snapshot name is not specified.", + "first_action": "Review the nbaapidiscv log or the nbaapireq_handler", + "full_action": "Review the nbaapidiscv log or the nbaapireq_handler\nlog for more details." }, "3213": { "code": 3213, - "desc": "Backup type está não specified.", - "first_action": "Review o nbaapidiscv log ou o nbaapireq_handler", - "full_action": "Review o nbaapidiscv log ou o nbaapireq_handler\nlog para more details." + "desc": "Backup type is not specified.", + "first_action": "Review the nbaapidiscv log or the nbaapireq_handler", + "full_action": "Review the nbaapidiscv log or the nbaapireq_handler\nlog for more details." }, "3214": { "code": 3214, - "desc": "Backup arquivo name está não specified.", - "first_action": "Review o nbaapidiscv log ou o nbaapireq_handler", - "full_action": "Review o nbaapidiscv log ou o nbaapireq_handler\nlog para more details." + "desc": "Backup file name is not specified.", + "first_action": "Review the nbaapidiscv log or the nbaapireq_handler", + "full_action": "Review the nbaapidiscv log or the nbaapireq_handler\nlog for more details." }, "3215": { "code": 3215, - "desc": "Controller ID está não specified.", - "first_action": "Review o nbaapidiscv log ou o nbaapireq_handler", - "full_action": "Review o nbaapidiscv log ou o nbaapireq_handler\nlog para more details." + "desc": "Controller ID is not specified.", + "first_action": "Review the nbaapidiscv log or the nbaapireq_handler", + "full_action": "Review the nbaapidiscv log or the nbaapireq_handler\nlog for more details." }, "3216": { "code": 3216, - "desc": "Controller ID de o claim comando did não match com controller ID de o upload done comando.", - "first_action": "Review o nbaapidiscv log ou o nbaapireq_handler", - "full_action": "Review o nbaapidiscv log ou o nbaapireq_handler\nlog para more details." + "desc": "Controller ID of the claim command did not match with controller ID of the upload done command.", + "first_action": "Review the nbaapidiscv log or the nbaapireq_handler", + "full_action": "Review the nbaapidiscv log or the nbaapireq_handler\nlog for more details." }, "3217": { "code": 3217, - "desc": "CBR node está não specified in configuration settings.", - "first_action": "Verifique que o CBR node está specified in o Cassandra", - "full_action": "Verifique que o CBR node está specified in o Cassandra\nconfiguration arquivo." + "desc": "CBR node is not specified in configuration settings.", + "first_action": "Verify that the CBR node is specified in the Cassandra", + "full_action": "Verify that the CBR node is specified in the Cassandra\nconfiguration file." }, "3218": { "code": 3218, - "desc": "Falhou to create o diretório.", + "desc": "Failed to create the directory.", "first_action": "VerifyallnodesinboththeDatastagingserverCassandra", - "full_action": "VerifyallnodesinboththeDatastagingserverCassandra\ncluster e Production Cassandra cluster estão reachable. Also, verifique que o usuário\nhas o correct access permissions to create o directories que estão specified in\no Cassandra configuration arquivo.\nReview o nbaapidiscv log ou o nbaapireq_handler log para more details." + "full_action": "VerifyallnodesinboththeDatastagingserverCassandra\ncluster and Production Cassandra cluster are reachable. Also, verify that the user\nhas the correct access permissions to create the directories that are specified in\nthe Cassandra configuration file.\nReview the nbaapidiscv log or the nbaapireq_handler log for more details." }, "3219": { "code": 3219, - "desc": "Erro ocorreu when o arquivo foi copied.", - "first_action": "Verifique que o usuário has proper access permissions para", - "full_action": "Verifique que o usuário has proper access permissions para\nboth o arquivo e o destination caminho. Review o nbaapidiscv log ou\nnbaapireq_handler log para more details." + "desc": "Error occurred when the file was copied.", + "first_action": "Verify that the user has proper access permissions for", + "full_action": "Verify that the user has proper access permissions for\nboth the file and the destination path. Review the nbaapidiscv log or\nnbaapireq_handler log for more details." }, "3220": { "code": 3220, - "desc": "Falhou to excluir o data diretório.", + "desc": "Failed to delete the data directory.", "first_action": "Verifyiftheuserhascorrectaccesspermissionstodelete", "full_action": "Verifyiftheuserhascorrectaccesspermissionstodelete\nthedatadirectory.Reviewthenbaapidiscvlogornbaapireq_handlerlogformore\ndetails." }, "3221": { "code": 3221, "desc": "ProductionCassandraclusterpasswordisnotspecifiedinthecommand.", - "first_action": "Verifique que o Production Cassandra cluster password está", - "full_action": "Verifique que o Production Cassandra cluster password está\nspecified in o tpconfig comando." + "first_action": "Verify that the Production Cassandra cluster password is", + "full_action": "Verify that the Production Cassandra cluster password is\nspecified in the tpconfig command." }, "3222": { "code": 3222, "desc": "ProductionCassandraclusterusernameisnotspecifiedinthecommand. NetBackup status codes 543 NetBackup status codes", - "first_action": "Verifique if o Production Cassandra cluster username está", - "full_action": "Verifique if o Production Cassandra cluster username está\nspecified in o tpconfig comando." + "first_action": "Verify if the Production Cassandra cluster username is", + "full_action": "Verify if the Production Cassandra cluster username is\nspecified in the tpconfig command." }, "3223": { "code": 3223, - "desc": "Security mode está não specified.", - "first_action": "Verifique que um valid Security mode está specified in o", - "full_action": "Verifique que um valid Security mode está specified in o\nCassandra configuration arquivo." + "desc": "Security mode is not specified.", + "first_action": "Verify that a valid Security mode is specified in the", + "full_action": "Verify that a valid Security mode is specified in the\nCassandra configuration file." }, "3224": { "code": 3224, - "desc": "Não foi possível to abrir o progress arquivo to ler.", - "first_action": "Verifique que o usuário access permissions estão correct para", - "full_action": "Verifique que o usuário access permissions estão correct para\no progress arquivo. Refer to o nbaapidiscv log ou o nbaapireq_handler log para\nmore details." + "desc": "Unable to open the progress file to read.", + "first_action": "Verify that the user access permissions are correct for", + "full_action": "Verify that the user access permissions are correct for\nthe progress file. Refer to the nbaapidiscv log or the nbaapireq_handler log for\nmore details." }, "3225": { "code": 3225, - "desc": "Não data foi found to copy.", - "first_action": "Verifique que um valid caminho está specified para o Data Staging", - "full_action": "Verifique que um valid caminho está specified para o Data Staging\nServidor in o Cassandra configuration arquivo." + "desc": "No data was found to copy.", + "first_action": "Verify that a valid path is specified for the Data Staging", + "full_action": "Verify that a valid path is specified for the Data Staging\nServer in the Cassandra configuration file." }, "3232": { "code": 3232, - "desc": "Data diretório armazenamento de Data Staging Servidor does não have enough armazenamento.", - "first_action": "Verifique que o data diretório de o Data Staging Servidor has enough armazenamento", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique que o data diretório de o Data Staging Servidor has enough armazenamento\nspace e does não contain qualquer contents de previous jobs.\n■ Verifique que o Cassandra data diretório de o Data Staging Servidor does não\ncontain contents de previous jobs.\n■ Garanta que o ScriptHome diretório de o Data Staging Servidor has enough\narmazenamento space to executar o restauração operation.\n■ Verifique que o ScriptHome diretório, which está specified in o Cassandra\nconfiguration arquivo, está present on Data Staging Servidor. If o arquivo está não present,\ncreate o ScriptHome diretório on Data Staging Servidor e retry o restauração\noperation." + "desc": "Data directory storage of Data Staging Server does not have enough storage.", + "first_action": "Verify that the data directory of the Data Staging Server has enough storage", + "full_action": "Perform the following as appropriate:\n■ Verify that the data directory of the Data Staging Server has enough storage\nspace and does not contain any contents of previous jobs.\n■ Verify that the Cassandra data directory of the Data Staging Server does not\ncontain contents of previous jobs.\n■ Ensure that the ScriptHome directory of the Data Staging Server has enough\nstorage space to perform the restore operation.\n■ Verify that the ScriptHome directory, which is specified in the Cassandra\nconfiguration file, is present on Data Staging Server. If the file is not present,\ncreate the ScriptHome directory on Data Staging Server and retry the restore\noperation." }, "3234": { "code": 3234, - "desc": "Parse erro.", - "first_action": "Verifique que todos o parameters e attributes que estão", - "full_action": "Verifique que todos o parameters e attributes que estão\nmentioned in cassandra.conf estão correct." + "desc": "Parse error.", + "first_action": "Verify that all the parameters and attributes that are", + "full_action": "Verify that all the parameters and attributes that are\nmentioned in cassandra.conf are correct." }, "3235": { "code": 3235, - "desc": "Down node’s threshold value exceeds permissible limite.", + "desc": "Down node’s threshold value exceeds permissible limit.", "first_action": "Turnuptheproductionnodesorincreasethedownnodes", - "full_action": "Turnuptheproductionnodesorincreasethedownnodes\nthreshold value to match o percentage de nodes que estão down." + "full_action": "Turnuptheproductionnodesorincreasethedownnodes\nthreshold value to match the percentage of nodes that are down." }, "3236": { "code": 3236, - "desc": "JSON format está não valid.", - "first_action": "Verifique que todos o parameters e attributes que estão contained in o", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique que todos o parameters e attributes que estão contained in o\ncassandra.conf arquivo estão correct.\n■ Verifique que o cassandra.conf arquivo format está in um valid JSON format." + "desc": "JSON format is not valid.", + "first_action": "Verify that all the parameters and attributes that are contained in the", + "full_action": "Perform the following as appropriate:\n■ Verify that all the parameters and attributes that are contained in the\ncassandra.conf file are correct.\n■ Verify that the cassandra.conf file format is in a valid JSON format." }, "3245": { "code": 3245, - "desc": "Falhou to get Production Cassandra cluster IP addresses.", + "desc": "Failed to get Production Cassandra cluster IP addresses.", "first_action": "Fortheprovidedclustername,verifythattheclusternodes", - "full_action": "Fortheprovidedclustername,verifythattheclusternodes\nestão up e executando." + "full_action": "Fortheprovidedclustername,verifythattheclusternodes\nare up and running." }, "3246": { "code": 3246, - "desc": "Um exception has ocorreu during Production Cassandra cluster validation.", - "first_action": "Para o provided cluster name, verifique que o cluster nodes estão up e executando.", - "full_action": "Executar o seguinte como appropriate:\n■ Para o provided cluster name, verifique que o cluster nodes estão up e executando.\n■ Verifique que o nodes estão accessible from o CBR nodes.\n■ Verifique que o production cluster has um supported Cassandra version.\n■ VerifythattheproductionclusternodesaredeployedonasupportedOSplatform." + "desc": "An exception has occurred during Production Cassandra cluster validation.", + "first_action": "For the provided cluster name, verify that the cluster nodes are up and running.", + "full_action": "Perform the following as appropriate:\n■ For the provided cluster name, verify that the cluster nodes are up and running.\n■ Verify that the nodes are accessible from the CBR nodes.\n■ Verify that the production cluster has a supported Cassandra version.\n■ VerifythattheproductionclusternodesaredeployedonasupportedOSplatform." }, "3251": { "code": 3251, "desc": "ProductionCassandraclusternamedidnotmatchwiththeconfiguration settings.", - "first_action": "Verifique que o Cassandra cluster name que está in o", - "full_action": "Verifique que o Cassandra cluster name que está in o\ncassandra.yaml arquivo está correct on o production node." + "first_action": "Verify that the Cassandra cluster name that is in the", + "full_action": "Verify that the Cassandra cluster name that is in the\ncassandra.yaml file is correct on the production node." }, "3252": { "code": 3252, - "desc": "Falhou to run Cassandra Query Language Shell comando.", - "first_action": "Verifique o Cassandra Username e Password que estão provided in o", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o Cassandra Username e Password que estão provided in o\napplication configuration arquivo para o specified Cassandra cluster e its\nassociated entradas estão correct.\n■ Verifique o Cassandra node status. Todos nodes on o data staging servidor e o\nproduction cluster should be up e executando.\n■ Verifique que o firewall settings on o cluster nodes estão correct. Port 7000/9042\nshould be abrir." + "desc": "Failed to run Cassandra Query Language Shell command.", + "first_action": "Verify the Cassandra Username and Password that are provided in the", + "full_action": "Perform the following as appropriate:\n■ Verify the Cassandra Username and Password that are provided in the\napplication configuration file for the specified Cassandra cluster and its\nassociated entries are correct.\n■ Verify the Cassandra node status. All nodes on the data staging server and the\nproduction cluster should be up and running.\n■ Verify that the firewall settings on the cluster nodes are correct. Port 7000/9042\nshould be open." }, "3253": { "code": 3253, - "desc": "Não valid nodes foram found para restauração.", - "first_action": "Verifique que o production cluster node ou nodes estão up", - "full_action": "Verifique que o production cluster node ou nodes estão up\ne executando." + "desc": "No valid nodes were found for restore.", + "first_action": "Verify that the production cluster node or nodes are up", + "full_action": "Verify that the production cluster node or nodes are up\nand running." }, "3254": { "code": 3254, - "desc": "Falhou to start Cassandra service.", - "first_action": "Verifique que o Cassandra cluster node status está up e in um normal state.", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique que o Cassandra cluster node status está up e in um normal state.\n■ Verifique que o node Username ou Password details in o cassandra.yaml arquivo\nestão correct.\n■ Verifique que o firewall settings on o cluster nodes estão correct. Port 7000/9042\nshould be abrir." + "desc": "Failed to start Cassandra service.", + "first_action": "Verify that the Cassandra cluster node status is up and in a normal state.", + "full_action": "Perform the following as appropriate:\n■ Verify that the Cassandra cluster node status is up and in a normal state.\n■ Verify that the node Username or Password details in the cassandra.yaml file\nare correct.\n■ Verify that the firewall settings on the cluster nodes are correct. Port 7000/9042\nshould be open." }, "3255": { "code": 3255, - "desc": "Falhou to stop Cassandra service.", - "first_action": "Verifique que o Cassandra cluster node status está up e in um normal state.", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique que o Cassandra cluster node status está up e in um normal state.\n■ Verifique que o node Username ou Password details in o cassandra.yaml arquivo\nestão correct.\n■ Verifique que o firewall settings on o cluster nodes estão correct. Port 7000/9042\nshould be abrir." + "desc": "Failed to stop Cassandra service.", + "first_action": "Verify that the Cassandra cluster node status is up and in a normal state.", + "full_action": "Perform the following as appropriate:\n■ Verify that the Cassandra cluster node status is up and in a normal state.\n■ Verify that the node Username or Password details in the cassandra.yaml file\nare correct.\n■ Verify that the firewall settings on the cluster nodes are correct. Port 7000/9042\nshould be open." }, "3256": { "code": 3256, - "desc": "Falhou to start Cassandra servidor.", - "first_action": "Verifique que o nodes in o Cassandra cluster estão up e", - "full_action": "Verifique que o nodes in o Cassandra cluster estão up e\nin um normal state. Also, verifique que o firewall settings on o cluster nodes estão\ncorrect. Port 7000/9042 should be abrir." + "desc": "Failed to start Cassandra server.", + "first_action": "Verify that the nodes in the Cassandra cluster are up and", + "full_action": "Verify that the nodes in the Cassandra cluster are up and\nin a normal state. Also, verify that the firewall settings on the cluster nodes are\ncorrect. Port 7000/9042 should be open." }, "3257": { "code": 3257, - "desc": "Falhou to stop Cassandra servidor.", - "first_action": "Verifique que o nodes in o Cassandra cluster estão up e", - "full_action": "Verifique que o nodes in o Cassandra cluster estão up e\nin um normal state. Also, verifique que o firewall settings on o cluster nodes estão\ncorrect. Port 7000/9042 should be abrir." + "desc": "Failed to stop Cassandra server.", + "first_action": "Verify that the nodes in the Cassandra cluster are up and", + "full_action": "Verify that the nodes in the Cassandra cluster are up and\nin a normal state. Also, verify that the firewall settings on the cluster nodes are\ncorrect. Port 7000/9042 should be open." }, "3258": { "code": 3258, - "desc": "Falhou to set Cassandra yaml arquivo on Data Staging servidor cluster.", - "first_action": "Verifique if o data staging servidor node ou nodes estão up e", - "full_action": "Verifique if o data staging servidor node ou nodes estão up e\nexecutando." + "desc": "Failed to set Cassandra yaml file on Data Staging server cluster.", + "first_action": "Verify if the data staging server node or nodes are up and", + "full_action": "Verify if the data staging server node or nodes are up and\nrunning." }, "3259": { "code": 3259, - "desc": "Um exception has ocorreu while Cassandra schema foi fetched.", - "first_action": "Verifique que o Cassandra Username e Password on o production cluster", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique que o Cassandra Username e Password on o production cluster\nestão correct.\n■ Verifique que o cluster node onde o schema resides from está up e executando.\n■ Verifique que o firewall settings on o cluster nodes estão correct. Port 7000/9042\nshould be abrir." + "desc": "An exception has occurred while Cassandra schema was fetched.", + "first_action": "Verify that the Cassandra Username and Password on the production cluster", + "full_action": "Perform the following as appropriate:\n■ Verify that the Cassandra Username and Password on the production cluster\nare correct.\n■ Verify that the cluster node where the schema resides from is up and running.\n■ Verify that the firewall settings on the cluster nodes are correct. Port 7000/9042\nshould be open." }, "3260": { "code": 3260, - "desc": "Não foi possível to fetch banco de dados schema.", - "first_action": "Verifique o Cassandra Username e Password on o production cluster estão", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o Cassandra Username e Password on o production cluster estão\ncorrect.\n■ Verifique que o node status de Cassandra cluster está up e in um normal state.\n■ Verifique que o firewall settings on o cluster nodes estão correct. Port 7000/9042\nshould be abrir." + "desc": "Unable to fetch database schema.", + "first_action": "Verify the Cassandra Username and Password on the production cluster are", + "full_action": "Perform the following as appropriate:\n■ Verify the Cassandra Username and Password on the production cluster are\ncorrect.\n■ Verify that the node status of Cassandra cluster is up and in a normal state.\n■ Verify that the firewall settings on the cluster nodes are correct. Port 7000/9042\nshould be open." }, "3261": { "code": 3261, - "desc": "Falhou to run Cassandra Query Language query on o cluster.", - "first_action": "Verifique o Cassandra Username e Password on o production cluster estão", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o Cassandra Username e Password on o production cluster estão\ncorrect.\n■ Verifique que o node status de Cassandra cluster está up e in um normal state.\n■ Verifique que o firewall settings on o cluster nodes estão correct. Port 7000/9042\nshould be abrir." + "desc": "Failed to run Cassandra Query Language query on the cluster.", + "first_action": "Verify the Cassandra Username and Password on the production cluster are", + "full_action": "Perform the following as appropriate:\n■ Verify the Cassandra Username and Password on the production cluster are\ncorrect.\n■ Verify that the node status of Cassandra cluster is up and in a normal state.\n■ Verify that the firewall settings on the cluster nodes are correct. Port 7000/9042\nshould be open." }, "3262": { "code": 3262, - "desc": "Não table schema found.", - "first_action": "Verifique que não column family ou table está identified como part", - "full_action": "Verifique que não column family ou table está identified como part\nde o keyspace." + "desc": "No table schema found.", + "first_action": "Verify that no column family or table is identified as part", + "full_action": "Verify that no column family or table is identified as part\nof the keyspace." }, "3263": { "code": 3263, - "desc": "Falhou to create keyspaces.", - "first_action": "Verifique o Cassandra Username e Password on o production cluster estão", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o Cassandra Username e Password on o production cluster estão\ncorrect.\n■ Verifique que o node status de Cassandra cluster está up e in um normal state.\n■ Verifique que o firewall settings on o cluster nodes estão correct. Port 7000/9042\nshould be abrir." + "desc": "Failed to create keyspaces.", + "first_action": "Verify the Cassandra Username and Password on the production cluster are", + "full_action": "Perform the following as appropriate:\n■ Verify the Cassandra Username and Password on the production cluster are\ncorrect.\n■ Verify that the node status of Cassandra cluster is up and in a normal state.\n■ Verify that the firewall settings on the cluster nodes are correct. Port 7000/9042\nshould be open." }, "3264": { "code": 3264, - "desc": "Falhou to create tables.", - "first_action": "Verifique o Cassandra Username e Password on o production cluster estão", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o Cassandra Username e Password on o production cluster estão\ncorrect.\n■ Verifique que o node status de Cassandra cluster está up e in um normal state.\n■ Verifique que o firewall settings on o cluster nodes estão correct. Port 7000/9042\nshould be abrir." + "desc": "Failed to create tables.", + "first_action": "Verify the Cassandra Username and Password on the production cluster are", + "full_action": "Perform the following as appropriate:\n■ Verify the Cassandra Username and Password on the production cluster are\ncorrect.\n■ Verify that the node status of Cassandra cluster is up and in a normal state.\n■ Verify that the firewall settings on the cluster nodes are correct. Port 7000/9042\nshould be open." }, "3265": { "code": 3265, - "desc": "Falhou to alter tables.", - "first_action": "Verifique o Cassandra Username e Password on o production cluster estão", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o Cassandra Username e Password on o production cluster estão\ncorrect.\n■ Verifique que o node status de Cassandra cluster está up e in um normal state.\n■ Verifique que o firewall settings on o cluster nodes estão correct. Port 7000/9042\nshould be abrir." + "desc": "Failed to alter tables.", + "first_action": "Verify the Cassandra Username and Password on the production cluster are", + "full_action": "Perform the following as appropriate:\n■ Verify the Cassandra Username and Password on the production cluster are\ncorrect.\n■ Verify that the node status of Cassandra cluster is up and in a normal state.\n■ Verify that the firewall settings on the cluster nodes are correct. Port 7000/9042\nshould be open." }, "3266": { "code": 3266, - "desc": "Cassandra Query Language comando está vazio.", + "desc": "Cassandra Query Language command is empty.", "first_action": "Reviewthenbaapidiscvorthenbaapireq_handlerlogs", - "full_action": "Reviewthenbaapidiscvorthenbaapireq_handlerlogs\npara more detail about o falha." + "full_action": "Reviewthenbaapidiscvorthenbaapireq_handlerlogs\nfor more detail about the failure." }, "3267": { "code": 3267, - "desc": "Falhou to drop keyspaces. NetBackup status codes 553 NetBackup status codes", - "first_action": "Verifique o Cassandra Username e Password on o production cluster estão", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o Cassandra Username e Password on o production cluster estão\ncorrect.\n■ Verifique que o node status de Cassandra cluster está up e in um normal state.\n■ Verifique que o firewall settings on o cluster nodes estão correct. Port 7000/9042\nshould be abrir." + "desc": "Failed to drop keyspaces. NetBackup status codes 553 NetBackup status codes", + "first_action": "Verify the Cassandra Username and Password on the production cluster are", + "full_action": "Perform the following as appropriate:\n■ Verify the Cassandra Username and Password on the production cluster are\ncorrect.\n■ Verify that the node status of Cassandra cluster is up and in a normal state.\n■ Verify that the firewall settings on the cluster nodes are correct. Port 7000/9042\nshould be open." }, "3268": { "code": 3268, - "desc": "Não foi possível to fetch o datacenter from o Cassandra cluster.", - "first_action": "Verifique que o correct data center entry está in o cassandra.conf in o", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique que o correct data center entry está in o cassandra.conf in o\nproduction cluster.\n■ Verifique o Cassandra Username e Password on o production cluster estão\ncorrect.\n■ Verifique que o node status de Cassandra cluster está up e in um normal state.\n■ Verifique que o firewall settings on o cluster nodes estão correct. Port 7000/9042\nshould be abrir." + "desc": "Unable to fetch the datacenter from the Cassandra cluster.", + "first_action": "Verify that the correct data center entry is in the cassandra.conf in the", + "full_action": "Perform the following as appropriate:\n■ Verify that the correct data center entry is in the cassandra.conf in the\nproduction cluster.\n■ Verify the Cassandra Username and Password on the production cluster are\ncorrect.\n■ Verify that the node status of Cassandra cluster is up and in a normal state.\n■ Verify that the firewall settings on the cluster nodes are correct. Port 7000/9042\nshould be open." }, "3269": { "code": 3269, - "desc": "Um exception has ocorreu when um attempt foi made to fetch o datacenter.", - "first_action": "Review o Detailed status in o Activity monitor.", - "full_action": "Executar o seguinte como appropriate:\n■ Review o Detailed status in o Activity monitor.\n■ Review o nbaapidiscv log ou o nbaapireq_handler log para more detail." + "desc": "An exception has occurred when an attempt was made to fetch the datacenter.", + "first_action": "Review the Detailed status in the Activity monitor.", + "full_action": "Perform the following as appropriate:\n■ Review the Detailed status in the Activity monitor.\n■ Review the nbaapidiscv log or the nbaapireq_handler log for more detail." }, "3270": { "code": 3270, - "desc": "Não foi possível to fetch o datacenter para um node.", - "first_action": "Verifique que o datacenter settings in o application", - "full_action": "Verifique que o datacenter settings in o application\nconfiguration arquivo para o specified Cassandra cluster e its associated entradas estão\ncorrect.Also,verifythatthefirewallsettingsontheclusternodesarecorrectbecause\nport 7000/9042 should be abrir." + "desc": "Unable to fetch the datacenter for a node.", + "first_action": "Verify that the datacenter settings in the application", + "full_action": "Verify that the datacenter settings in the application\nconfiguration file for the specified Cassandra cluster and its associated entries are\ncorrect.Also,verifythatthefirewallsettingsontheclusternodesarecorrectbecause\nport 7000/9042 should be open." }, "3271": { "code": 3271, - "desc": "Falhou to set up backup Cassandra cluster.", - "first_action": "Verifique o Cassandra Username e Password on o production cluster estão", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o Cassandra Username e Password on o production cluster estão\ncorrect.\n■ Verifique que o node status de Cassandra cluster está up e in um normal state.\n■ Verifique que o firewall settings on o cluster nodes estão correct. Port 7000/9042\nshould be abrir." + "desc": "Failed to set up backup Cassandra cluster.", + "first_action": "Verify the Cassandra Username and Password on the production cluster are", + "full_action": "Perform the following as appropriate:\n■ Verify the Cassandra Username and Password on the production cluster are\ncorrect.\n■ Verify that the node status of Cassandra cluster is up and in a normal state.\n■ Verify that the firewall settings on the cluster nodes are correct. Port 7000/9042\nshould be open." }, "3272": { "code": 3272, - "desc": "Não keyspace found para Cassandra cluster backup.", - "first_action": "Use cqlsh to access o production node e verifique que", - "full_action": "Use cqlsh to access o production node e verifique que\none non-empty keyspace está present in o cluster." + "desc": "No keyspace found for Cassandra cluster backup.", + "first_action": "Use cqlsh to access the production node and verify that", + "full_action": "Use cqlsh to access the production node and verify that\none non-empty keyspace is present in the cluster." }, "3273": { "code": 3273, - "desc": "Job cleanup time-out está não valid.", - "first_action": "Um integer", - "full_action": "Verifique que o value de o jobCleanupTimeoutSec in\ncassandra.conf arquivo está:\n■ Um integer\n■ Greater than zero" + "desc": "Job cleanup time-out is not valid.", + "first_action": "An integer", + "full_action": "Verify that the value of the jobCleanupTimeoutSec in\ncassandra.conf file is:\n■ An integer\n■ Greater than zero" }, "3274": { "code": 3274, - "desc": "Falhou to prepare backup.", - "first_action": "Review o Detailed status in o Activity Monitor.", - "full_action": "Executar o seguinte como appropriate:\n■ Review o Detailed status in o Activity Monitor.\n■ Review o nbaapidiscv log ou o nbaapireq_handler log para more detail." + "desc": "Failed to prepare backup.", + "first_action": "Review the Detailed status in the Activity Monitor.", + "full_action": "Perform the following as appropriate:\n■ Review the Detailed status in the Activity Monitor.\n■ Review the nbaapidiscv log or the nbaapireq_handler log for more detail." }, "3275": { "code": 3275, - "desc": "BigDatabackupimagegroupvalidationhasfailedasthespecifiedimage selection consists de cheio backup images from multiple image groups.", + "desc": "BigDatabackupimagegroupvalidationhasfailedasthespecifiedimage selection consists of full backup images from multiple image groups.", "first_action": "Verifythattheimagegroupthatisprovidedinthebprestorecommandiscorrect.", - "full_action": "Executar o seguinte como appropriate:\n■ Verifythattheimagegroupthatisprovidedinthebprestorecommandiscorrect.\n■ Verifythatthestartandtheendtimethatisprovidedinthebprestorecommand\nestá correct." + "full_action": "Perform the following as appropriate:\n■ Verifythattheimagegroupthatisprovidedinthebprestorecommandiscorrect.\n■ Verifythatthestartandtheendtimethatisprovidedinthebprestorecommand\nis correct." }, "3276": { "code": 3276, - "desc": "BigDatabackupimagegroupvalidationhasfailedasthespecifiedimage selection does não contain todos backup images from o image group. NetBackup status codes 557 NetBackup status codes", - "first_action": "Verifique que um image group está provided to o bprestore comando e verifique", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique que um image group está provided to o bprestore comando e verifique\nque it está o correct image group.\n■ Review o start e o end time que o bprestore comando returns e\nverifique que they estão correct." + "desc": "BigDatabackupimagegroupvalidationhasfailedasthespecifiedimage selection does not contain all backup images from the image group. NetBackup status codes 557 NetBackup status codes", + "first_action": "Verify that an image group is provided to the bprestore command and verify", + "full_action": "Perform the following as appropriate:\n■ Verify that an image group is provided to the bprestore command and verify\nthat it is the correct image group.\n■ Review the start and the end time that the bprestore command returns and\nverify that they are correct." }, "3277": { "code": 3277, - "desc": "Falhou to excluir stale banco de dados schema.", - "first_action": "Clear o contents in o data diretório de o DSS nodes", - "full_action": "Clear o contents in o data diretório de o DSS nodes\ne try to run o job again." + "desc": "Failed to delete stale database schema.", + "first_action": "Clear the contents in the data directory of the DSS nodes", + "full_action": "Clear the contents in the data directory of the DSS nodes\nand try to run the job again." }, "3280": { "code": 3280, - "desc": "Data Staging Servidor nodes do não have enough space.", - "first_action": "Verifique que o Data Staging Servidor node has sufficient", - "full_action": "Verifique que o Data Staging Servidor node has sufficient\nspace." + "desc": "Data Staging Server nodes do not have enough space.", + "first_action": "Verify that the Data Staging Server node has sufficient", + "full_action": "Verify that the Data Staging Server node has sufficient\nspace." }, "3281": { "code": 3281, - "desc": "Falhou to disassemble o Data Staging Servidor cluster.", - "first_action": "1. Stop o Cassandra service on todos DSS nodes.", - "full_action": "Executar o seguinte procedure:\n1. Stop o Cassandra service on todos DSS nodes.\n2. Change o seed node IP address in o Cassandra yaml arquivo de todos DSS nodes\nto their respective IP addresses.\n3. Start o Cassandra service on todos DSS nodes.\n4. Retry o job." + "desc": "Failed to disassemble the Data Staging Server cluster.", + "first_action": "1. Stop the Cassandra service on all DSS nodes.", + "full_action": "Perform the following procedure:\n1. Stop the Cassandra service on all DSS nodes.\n2. Change the seed node IP address in the Cassandra yaml file of all DSS nodes\nto their respective IP addresses.\n3. Start the Cassandra service on all DSS nodes.\n4. Retry the job." }, "3282": { "code": 3282, - "desc": "Falhou to get o backup status.", - "first_action": "Review o Detailed status in o Activity Monitor.", - "full_action": "Executar o seguinte como appropriate:\n■ Review o Detailed status in o Activity Monitor.\n■ Review o nbaapireq_handler logs para more details." + "desc": "Failed to get the backup status.", + "first_action": "Review the Detailed status in the Activity Monitor.", + "full_action": "Perform the following as appropriate:\n■ Review the Detailed status in the Activity Monitor.\n■ Review the nbaapireq_handler logs for more details." }, "3283": { "code": 3283, - "desc": "Falhou to set o incremental backup flag.", - "first_action": "Verifique que o Cassandra yaml caminho que está specified in", - "full_action": "Verifique que o Cassandra yaml caminho que está specified in\no Cassandra configuration arquivo está valid e has proper permissions.\nReview o nbaapireq_handler logs para more details." + "desc": "Failed to set the incremental backup flag.", + "first_action": "Verify that the Cassandra yaml path that is specified in", + "full_action": "Verify that the Cassandra yaml path that is specified in\nthe Cassandra configuration file is valid and has proper permissions.\nReview the nbaapireq_handler logs for more details." }, "3284": { "code": 3284, - "desc": "Falhou to flush o nodetool buffer. NetBackup status codes 559 NetBackup status codes", - "first_action": "Verifique que o nodetool works properly.", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique que o nodetool works properly.\n■ Verifique if Cassandra services estão active e CQLSH está executando.\n■ Verifique if o incremental_backup parâmetro in o Cassandra yaml arquivo está set\nto true.\n■ Verifique nbaapireq_handler logs para more details." + "desc": "Failed to flush the nodetool buffer. NetBackup status codes 559 NetBackup status codes", + "first_action": "Verify that the nodetool works properly.", + "full_action": "Perform the following as appropriate:\n■ Verify that the nodetool works properly.\n■ Verify if Cassandra services are active and CQLSH is running.\n■ Check if the incremental_backup parameter in the Cassandra yaml file is set\nto true.\n■ Check nbaapireq_handler logs for more details." }, "3286": { "code": 3286, - "desc": "Um erro has ocorreu during Backup Prepare due to inválido input.", - "first_action": "Verifique o configuration in o Cassandra configuration", - "full_action": "Verifique o configuration in o Cassandra configuration\narquivo para o specified Cassandra cluster e its associated entradas estão correct." + "desc": "An error has occurred during Backup Prepare due to invalid input.", + "first_action": "Verify the configuration in the Cassandra configuration", + "full_action": "Verify the configuration in the Cassandra configuration\nfile for the specified Cassandra cluster and its associated entries are correct." }, "3287": { "code": 3287, - "desc": "O keyspace ou o column family already exists on o Production Cassandra cluster.", - "first_action": "Verifique if o overwrite parâmetro está set to true in o", - "full_action": "Verifique if o overwrite parâmetro está set to true in o\nrenamedfile.Ifitissettofalse,thenmakesurethatyouhavedeletedthekeyspace\ne ou column family before o restauração job." + "desc": "The keyspace or the column family already exists on the Production Cassandra cluster.", + "first_action": "Verify if the overwrite parameter is set to true in the", + "full_action": "Verify if the overwrite parameter is set to true in the\nrenamedfile.Ifitissettofalse,thenmakesurethatyouhavedeletedthekeyspace\nand or column family before the restore job." }, "3288": { "code": 3288, - "desc": "Minimum RAM requerido está não specified para o Data Staging Servidor cluster.", - "first_action": "Verifique que o dssMinRam parâmetro está mentioned in o", - "full_action": "Verifique que o dssMinRam parâmetro está mentioned in o\nCassandra configuration arquivo." + "desc": "Minimum RAM required is not specified for the Data Staging Server cluster.", + "first_action": "Verify that the dssMinRam parameter is mentioned in the", + "full_action": "Verify that the dssMinRam parameter is mentioned in the\nCassandra configuration file." }, "3289": { "code": 3289, - "desc": "Minimum Armazenamento per backup node está não specified para o Data Staging Servidor cluster.", - "first_action": "Verifique que o dssMinStoragePerBkupNode parâmetro está", - "full_action": "Verifique que o dssMinStoragePerBkupNode parâmetro está\nmentioned in o Cassandra configuration arquivo." + "desc": "Minimum Storage per backup node is not specified for the Data Staging Server cluster.", + "first_action": "Verify that the dssMinStoragePerBkupNode parameter is", + "full_action": "Verify that the dssMinStoragePerBkupNode parameter is\nmentioned in the Cassandra configuration file." }, "3290": { "code": 3290, - "desc": "Cassandra yaml arquivo caminho está não specified para o Data Staging Servidor cluster.", - "first_action": "Verifique que o Cassandra yaml caminho está specified in o", - "full_action": "Verifique que o Cassandra yaml caminho está specified in o\nCassandra configuration arquivo e que o arquivo caminho está correct." + "desc": "Cassandra yaml file path is not specified for the Data Staging Server cluster.", + "first_action": "Verify that the Cassandra yaml path is specified in the", + "full_action": "Verify that the Cassandra yaml path is specified in the\nCassandra configuration file and that the file path is correct." }, "3291": { "code": 3291, - "desc": "O concurrent_compactors parâmetro está não specified para o Data Staging Servidor cluster.", - "first_action": "Verifique que o concurrent_compactors parâmetro está", - "full_action": "Verifique que o concurrent_compactors parâmetro está\nspecified e it must be non-empty in o Cassandra configuration arquivo." + "desc": "The concurrent_compactors parameter is not specified for the Data Staging Server cluster.", + "first_action": "Verify that the concurrent_compactors parameter is", + "full_action": "Verify that the concurrent_compactors parameter is\nspecified and it must be non-empty in the Cassandra configuration file." }, "3292": { "code": 3292, - "desc": "Memória size de o sstableloaderMemsize parâmetro está não specified para o Data Staging Servidor cluster.", - "first_action": "Verifique que o sstableloaderMemsize parâmetro está", - "full_action": "Verifique que o sstableloaderMemsize parâmetro está\nspecified e it must be non-empty in o Cassandra configuration arquivo." + "desc": "Memory size of the sstableloaderMemsize parameter is not specified for the Data Staging Server cluster.", + "first_action": "Verify that the sstableloaderMemsize parameter is", + "full_action": "Verify that the sstableloaderMemsize parameter is\nspecified and it must be non-empty in the Cassandra configuration file." }, "3293": { "code": 3293, - "desc": "Concurrent transfers parâmetro está não specified para Data Staging Servidor cluster.", + "desc": "Concurrent transfers parameter is not specified for Data Staging Server cluster.", "first_action": "Verifythattheconcurrenttransfersparameteris specified", - "full_action": "Verifythattheconcurrenttransfersparameteris specified\ne it must be non-empty in o Cassandra configuration arquivo." + "full_action": "Verifythattheconcurrenttransfersparameteris specified\nand it must be non-empty in the Cassandra configuration file." }, "3294": { "code": 3294, - "desc": "Script home está não specified para o Data Staging Servidor cluster.", - "first_action": "Verifique if um valid script home caminho está specified in o", - "full_action": "Verifique if um valid script home caminho está specified in o\nCassandra configuration arquivo." + "desc": "Script home is not specified for the Data Staging Server cluster.", + "first_action": "Verify if a valid script home path is specified in the", + "full_action": "Verify if a valid script home path is specified in the\nCassandra configuration file." }, "3295": { "code": 3295, - "desc": "Um working diretório caminho está não specified para o Cassandra backup e restauração node.", - "first_action": "Verifique if um working diretório caminho está specified in o", - "full_action": "Verifique if um working diretório caminho está specified in o\nCassandra configuration arquivo." + "desc": "A working directory path is not specified for the Cassandra backup and restore node.", + "first_action": "Verify if a working directory path is specified in the", + "full_action": "Verify if a working directory path is specified in the\nCassandra configuration file." }, "3296": { "code": 3296, - "desc": "O dssDist caminho está não specified para o Data Staging Servidor cluster.", - "first_action": "Verifique que um valid dssDist caminho está specified in o", - "full_action": "Verifique que um valid dssDist caminho está specified in o\nCassandra configuration arquivo." + "desc": "The dssDist path is not specified for the Data Staging Server cluster.", + "first_action": "Verify that a valid dssDist path is specified in the", + "full_action": "Verify that a valid dssDist path is specified in the\nCassandra configuration file." }, "3297": { "code": 3297, - "desc": "O cph parâmetro está não specified para o Data Staging Servidor cluster.", - "first_action": "Verifique que o cph parâmetro está mentioned in o", - "full_action": "Verifique que o cph parâmetro está mentioned in o\nCassandra configuration arquivo." + "desc": "The cph parameter is not specified for the Data Staging Server cluster.", + "first_action": "Verify that the cph parameter is mentioned in the", + "full_action": "Verify that the cph parameter is mentioned in the\nCassandra configuration file." }, "3298": { "code": 3298, - "desc": "Backup has falhou.", - "first_action": "Review o Detailed status in o Activity Monitor.", - "full_action": "Executar o seguinte como appropriate:\n■ Review o Detailed status in o Activity Monitor.\n■ Review o nbaapidiscv ou nbaapireq_handler logs para more detail." + "desc": "Backup has failed.", + "first_action": "Review the Detailed status in the Activity Monitor.", + "full_action": "Perform the following as appropriate:\n■ Review the Detailed status in the Activity Monitor.\n■ Review the nbaapidiscv or nbaapireq_handler logs for more detail." }, "3299": { "code": 3299, - "desc": "Backup has falhou after retrying.", - "first_action": "Review o Detailed status in o Activity Monitor.", - "full_action": "Executar o seguinte como appropriate:\n■ Review o Detailed status in o Activity Monitor.\n■ Review o nbaapidiscv ou nbaapireq_handler logs para more detail." + "desc": "Backup has failed after retrying.", + "first_action": "Review the Detailed status in the Activity Monitor.", + "full_action": "Perform the following as appropriate:\n■ Review the Detailed status in the Activity Monitor.\n■ Review the nbaapidiscv or nbaapireq_handler logs for more detail." }, "3300": { "code": 3300, - "desc": "Um exception has ocorreu during backup task execution.", - "first_action": "Review o Detailed status in o Activity Monitor.", - "full_action": "Executar o seguinte como appropriate:\n■ Review o Detailed status in o Activity Monitor.\n■ Review o nbaapidiscv ou nbaapireq_handler logs para more detail." + "desc": "An exception has occurred during backup task execution.", + "first_action": "Review the Detailed status in the Activity Monitor.", + "full_action": "Perform the following as appropriate:\n■ Review the Detailed status in the Activity Monitor.\n■ Review the nbaapidiscv or nbaapireq_handler logs for more detail." }, "3301": { "code": 3301, - "desc": "Finalize status está não specified para backup task.", - "first_action": "Verifique o parameters para backup_finalize.", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o parameters para backup_finalize.\n■ Review o nbaapidiscv logs ou nbaapireq_handler logs para more detail." + "desc": "Finalize status is not specified for backup task.", + "first_action": "Verify the parameters for backup_finalize.", + "full_action": "Perform the following as appropriate:\n■ Verify the parameters for backup_finalize.\n■ Review the nbaapidiscv logs or nbaapireq_handler logs for more detail." }, "3304": { "code": 3304, - "desc": "Um exception has ocorreu during restauração prepare.", - "first_action": "Verifique que you use valid combinations de selection arquivo e rename arquivo from o", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique que you use valid combinations de selection arquivo e rename arquivo from o\nRestauração Combinations.\n■ Reviewthenbcbrlogsinnbaapireq_handlerformoredetailabouttheschema\nfailures." + "desc": "An exception has occurred during restore prepare.", + "first_action": "Verify that you use valid combinations of selection file and rename file from the", + "full_action": "Perform the following as appropriate:\n■ Verify that you use valid combinations of selection file and rename file from the\nRestore Combinations.\n■ Reviewthenbcbrlogsinnbaapireq_handlerformoredetailabouttheschema\nfailures." }, "3306": { "code": 3306, - "desc": "Falhou to get o arquivo status.", - "first_action": "Verifique o permissions de o workingDir caminho on DSS node estão correct.", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o permissions de o workingDir caminho on DSS node estão correct.\n■ Review o nbaapidiscv logs ou nbaapireq_handler logs para more detail." + "desc": "Failed to get the file status.", + "first_action": "Verify the permissions of the workingDir path on DSS node are correct.", + "full_action": "Perform the following as appropriate:\n■ Verify the permissions of the workingDir path on DSS node are correct.\n■ Review the nbaapidiscv logs or nbaapireq_handler logs for more detail." }, "3307": { "code": 3307, - "desc": "Falhou to create upload done arquivo.", - "first_action": "Verifique que o workingDir caminho exists on o CBR e if", - "full_action": "Verifique que o workingDir caminho exists on o CBR e if\no caminho does exist, does it have o correct informação." + "desc": "Failed to create upload done file.", + "first_action": "Verify that the workingDir path exists on the CBR and if", + "full_action": "Verify that the workingDir path exists on the CBR and if\nthe path does exist, does it have the correct information." }, "3308": { "code": 3308, - "desc": "Falhou to create upload falhou arquivo.", - "first_action": "Verifique que o workingDir caminho exists on o CBR e if", - "full_action": "Verifique que o workingDir caminho exists on o CBR e if\no caminho does exist, does it have o correct informação." + "desc": "Failed to create upload failed file.", + "first_action": "Verify that the workingDir path exists on the CBR and if", + "full_action": "Verify that the workingDir path exists on the CBR and if\nthe path does exist, does it have the correct information." }, "3309": { "code": 3309, - "desc": "Target arquivo está não ready.", - "first_action": "Verifique que o backup job has completed. Review o", - "full_action": "Verifique que o backup job has completed. Review o\nnbaapidiscv logs ou nbaapireq_handler logs para more details about o issue." + "desc": "Target file is not ready.", + "first_action": "Verify that the backup job has completed. Review the", + "full_action": "Verify that the backup job has completed. Review the\nnbaapidiscv logs or nbaapireq_handler logs for more details about the issue." }, "3310": { "code": 3310, - "desc": "Falhou to lock o arquivo.", - "first_action": "Verifique que o workingDir caminho exists on o CBR e if", - "full_action": "Verifique que o workingDir caminho exists on o CBR e if\no caminho does exist, does it have o correct informação." + "desc": "Failed to lock the file.", + "first_action": "Verify that the workingDir path exists on the CBR and if", + "full_action": "Verify that the workingDir path exists on the CBR and if\nthe path does exist, does it have the correct information." }, "3311": { "code": 3311, - "desc": "Arquivo está already locked.", - "first_action": "Verifique que o workingDir caminho exists on o CBR e if", - "full_action": "Verifique que o workingDir caminho exists on o CBR e if\no caminho does exist, does it have o correct informação." + "desc": "File is already locked.", + "first_action": "Verify that the workingDir path exists on the CBR and if", + "full_action": "Verify that the workingDir path exists on the CBR and if\nthe path does exist, does it have the correct information." }, "3312": { "code": 3312, - "desc": "Persisted task list está vazio.", - "first_action": "Verifique whether new data foi present on o Cassandra", - "full_action": "Verifique whether new data foi present on o Cassandra\nCluster para o incremental backup." + "desc": "Persisted task list is empty.", + "first_action": "Verify whether new data was present on the Cassandra", + "full_action": "Verify whether new data was present on the Cassandra\nCluster for the incremental backup." }, "3313": { "code": 3313, - "desc": "Job status está inválido.", - "first_action": "Deletion de o workingDir e scriptHome on todos DSS Node e Production", - "full_action": "Verifique o cleanup process para backup ou restauração para DSS\ne Production nodes. Review o nbaapidiscv logs ou nbaapireq_handler logs\npara more detail.\nPara successful cleanup, verifique que o seguinte items completed successfully:\n■ Deletion de o workingDir e scriptHome on todos DSS Node e Production\nNode.\n■ Deletion de o lock arquivos on todos DSS Node e Production Node.\n■ O Cassandra services foram started ou stopped on todos DSS nodes e\nProduction Node.\n■ O data directories on apenas o DSS node foram deleted.\n■ Disassembled o DSS cluster por replacing o seed node com o respective\nIP.\n■ Deletion de o backup e o snapshots directories within o data diretório\ncaminho on o Production Node." + "desc": "Job status is invalid.", + "first_action": "Deletion of the workingDir and scriptHome on all DSS Node and Production", + "full_action": "Check the cleanup process for backup or restore for DSS\nand Production nodes. Review the nbaapidiscv logs or nbaapireq_handler logs\nfor more detail.\nFor successful cleanup, verify that the following items completed successfully:\n■ Deletion of the workingDir and scriptHome on all DSS Node and Production\nNode.\n■ Deletion of the lock files on all DSS Node and Production Node.\n■ The Cassandra services were started or stopped on all DSS nodes and\nProduction Node.\n■ The data directories on only the DSS node were deleted.\n■ Disassembled the DSS cluster by replacing the seed node with the respective\nIP.\n■ Deletion of the backup and the snapshots directories within the data directory\npath on the Production Node." }, "3314": { "code": 3314, - "desc": "Um exception foi encontrado during performing finalize.", - "first_action": "Deletion de o workingDir e scriptHome on todos DSS Node e Production", - "full_action": "Verifique que o cleanup has succeeded.\nPara successful cleanup, verifique que o seguinte items completed successfully:\n■ Deletion de o workingDir e scriptHome on todos DSS Node e Production\nNode.\n■ Deletion de o lock arquivos on todos DSS Node e Production Node.\n■ O Cassandra services foram started ou stopped on todos DSS nodes e\nProduction Node.\n■ O data directories on apenas o DSS node foram deleted.\n■ Disassembled o DSS cluster por replacing o seed node com o respective\nIP.\n■ Deletion de o backup e o snapshots directories within o data diretório\ncaminho on o Production Node." + "desc": "An exception was encountered during performing finalize.", + "first_action": "Deletion of the workingDir and scriptHome on all DSS Node and Production", + "full_action": "Verify that the cleanup has succeeded.\nFor successful cleanup, verify that the following items completed successfully:\n■ Deletion of the workingDir and scriptHome on all DSS Node and Production\nNode.\n■ Deletion of the lock files on all DSS Node and Production Node.\n■ The Cassandra services were started or stopped on all DSS nodes and\nProduction Node.\n■ The data directories on only the DSS node were deleted.\n■ Disassembled the DSS cluster by replacing the seed node with the respective\nIP.\n■ Deletion of the backup and the snapshots directories within the data directory\npath on the Production Node." }, "3315": { "code": 3315, - "desc": "O solicitado arquivo está already claimed.", + "desc": "The requested file is already claimed.", "first_action": "Verifythatthefilethatiscontainedinthefilepathisclaimed", - "full_action": "Verifythatthefilethatiscontainedinthefilepathisclaimed\nin o backup." + "full_action": "Verifythatthefilethatiscontainedinthefilepathisclaimed\nin the backup." }, "3316": { "code": 3316, - "desc": "Falhou to truncate o column family.", - "first_action": "Executar o truncate operation on DSS. Review o", - "full_action": "Executar o truncate operation on DSS. Review o\nnbaapidiscv logs ou nbaapireq_handler logs para more detail." + "desc": "Failed to truncate the column family.", + "first_action": "Perform the truncate operation on DSS. Review the", + "full_action": "Perform the truncate operation on DSS. Review the\nnbaapidiscv logs or nbaapireq_handler logs for more detail." }, "3317": { "code": 3317, - "desc": "O specified hosts estão não found in o Datacenter ou Cluster.", - "first_action": "Verifique que o specified production nodes estão present in", - "full_action": "Verifique que o specified production nodes estão present in\ndatacenter. Verifique que o credentials ou configurations estão correct." + "desc": "The specified hosts are not found in the Datacenter or Cluster.", + "first_action": "Verify that the specified production nodes are present in", + "full_action": "Verify that the specified production nodes are present in\ndatacenter. Verify that the credentials or configurations are correct." }, "3318": { "code": 3318, - "desc": "Inválido value para o nodeDownThresholdPercentage parâmetro.", - "first_action": "Verifique que o value de nodeDownThresholdPercentage", - "full_action": "Verifique que o value de nodeDownThresholdPercentage\nin Cassandra configuration arquivo está um value que it está greater than 0 ou less than 100." + "desc": "Invalid value for the nodeDownThresholdPercentage parameter.", + "first_action": "Verify that the value of nodeDownThresholdPercentage", + "full_action": "Verify that the value of nodeDownThresholdPercentage\nin Cassandra configuration file is a value that it is greater than 0 or less than 100." }, "3319": { "code": 3319, "desc": "Thebackuphasfailedasoneofthetaskshasfailedtostartinthebackup.", - "first_action": "Review o nbaapidiscv logs ou nbaapireq_handler logs para more detail.", - "full_action": "Executar o seguinte como appropriate:\n■ Review o nbaapidiscv logs ou nbaapireq_handler logs para more detail.\n■ EnsurethattheSStableloaderutilityworks betweentheproductionnodes e\no data staging servers." + "first_action": "Review the nbaapidiscv logs or nbaapireq_handler logs for more detail.", + "full_action": "Perform the following as appropriate:\n■ Review the nbaapidiscv logs or nbaapireq_handler logs for more detail.\n■ EnsurethattheSStableloaderutilityworks betweentheproductionnodes and\nthe data staging servers." }, "3321": { "code": 3321, - "desc": "Specified download diretório caminho does não exist.", - "first_action": "Verifique que o data diretório caminho doesn’t exist on o", - "full_action": "Verifique que o data diretório caminho doesn’t exist on o\nProduction Nodes." + "desc": "Specified download directory path does not exist.", + "first_action": "Verify that the data directory path doesn’t exist on the", + "full_action": "Verify that the data directory path doesn’t exist on the\nProduction Nodes." }, "3322": { "code": 3322, - "desc": "Specified download diretório está vazio.", - "first_action": "Verifique que o contents de o data diretório caminho doesn't", - "full_action": "Verifique que o contents de o data diretório caminho doesn't\nexist on o Production Nodes." + "desc": "Specified download directory is empty.", + "first_action": "Verify that the contents of the data directory path doesn't", + "full_action": "Verify that the contents of the data directory path doesn't\nexist on the Production Nodes." }, "3323": { "code": 3323, - "desc": "Falhou to transfer o Sorted Strings Table. NetBackup status codes 569 NetBackup status codes", - "first_action": "Verifique que o directories named backups e snapshots exist on o Data", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique que o directories named backups e snapshots exist on o Data\nStaging Servidor ou o Production Nodes.\n■ Review o nbaapidiscv logs ou nbaapireq_handler logs para more detail." + "desc": "Failed to transfer the Sorted Strings Table. NetBackup status codes 569 NetBackup status codes", + "first_action": "Verify that the directories named backups and snapshots exist on the Data", + "full_action": "Perform the following as appropriate:\n■ Verify that the directories named backups and snapshots exist on the Data\nStaging Server or the Production Nodes.\n■ Review the nbaapidiscv logs or nbaapireq_handler logs for more detail." }, "3324": { "code": 3324, - "desc": "Parallel transfer task has falhou.", - "first_action": "Review o nbaapidiscv ou nbaapireq_handler logs para", - "full_action": "Review o nbaapidiscv ou nbaapireq_handler logs para\nmore details." + "desc": "Parallel transfer task has failed.", + "first_action": "Review the nbaapidiscv or nbaapireq_handler logs for", + "full_action": "Review the nbaapidiscv or nbaapireq_handler logs for\nmore details." }, "3325": { "code": 3325, - "desc": "Backup Optimize task has falhou.", - "first_action": "Review o nbaapidiscv ou nbaapireq_handler logs para", - "full_action": "Review o nbaapidiscv ou nbaapireq_handler logs para\nmore details." + "desc": "Backup Optimize task has failed.", + "first_action": "Review the nbaapidiscv or nbaapireq_handler logs for", + "full_action": "Review the nbaapidiscv or nbaapireq_handler logs for\nmore details." }, "3326": { "code": 3326, - "desc": "Backup Transfer task has falhou.", - "first_action": "Verifique que o Cassandra cluster nodes estão up e accessible.", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique que o Cassandra cluster nodes estão up e accessible.\n■ Verifique que o usuário accounts specified estão correct e have access privileges\non o Cassandra cluster nodes." + "desc": "Backup Transfer task has failed.", + "first_action": "Verify that the Cassandra cluster nodes are up and accessible.", + "full_action": "Perform the following as appropriate:\n■ Verify that the Cassandra cluster nodes are up and accessible.\n■ Verify that the user accounts specified are correct and have access privileges\non the Cassandra cluster nodes." }, "3327": { "code": 3327, - "desc": "Um erro has ocorreu during backup in production data transfer due to inválido comando parameters.", - "first_action": "Verifique que o settings in o application configuration arquivo", - "full_action": "Verifique que o settings in o application configuration arquivo\npara o specified Cassandra cluster e its associated entradas estão correct." + "desc": "An error has occurred during backup in production data transfer due to invalid command parameters.", + "first_action": "Verify that the settings in the application configuration file", + "full_action": "Verify that the settings in the application configuration file\nfor the specified Cassandra cluster and its associated entries are correct." }, "3328": { "code": 3328, - "desc": "Anerrorhasoccurredduringtherestoreinthedatatransferduetoinvalid comando parameters.", - "first_action": "Verifique que o settings in o application configuration arquivo", - "full_action": "Verifique que o settings in o application configuration arquivo\npara o specified Cassandra cluster e its associated entradas estão correct." + "desc": "Anerrorhasoccurredduringtherestoreinthedatatransferduetoinvalid command parameters.", + "first_action": "Verify that the settings in the application configuration file", + "full_action": "Verify that the settings in the application configuration file\nfor the specified Cassandra cluster and its associated entries are correct." }, "3329": { "code": 3329, - "desc": "Um erro has ocorreu during o backup in o optimize task due to inválido comando parameters.", - "first_action": "Verifique que o settings in o application configuration arquivo", - "full_action": "Verifique que o settings in o application configuration arquivo\npara o specified Cassandra cluster e its associated entradas estão correct." + "desc": "An error has occurred during the backup in the optimize task due to invalid command parameters.", + "first_action": "Verify that the settings in the application configuration file", + "full_action": "Verify that the settings in the application configuration file\nfor the specified Cassandra cluster and its associated entries are correct." }, "3330": { "code": 3330, - "desc": "Um active job está currently executando para this Cassandra cluster.", - "first_action": "Garanta que não other parallel operation está executando on o Data staging servers", - "full_action": "Executar o seguinte como appropriate:\n■ Garanta que não other parallel operation está executando on o Data staging servers\nou Cassandra cluster nodes.\n■ Retry o job after waiting para o current job to finish.\n■ If there estão não jobs executando in parallel create um setting in cassandra.conf arquivo\nunder o settings key como follows:\n\"jobCleanupTimeoutSec\": 0\nRetry o job.\nRemove this setting once o jobs start executando again. O default time-out está\n8 hours." + "desc": "An active job is currently running for this Cassandra cluster.", + "first_action": "Ensure that no other parallel operation is running on the Data staging servers", + "full_action": "Perform the following as appropriate:\n■ Ensure that no other parallel operation is running on the Data staging servers\nor Cassandra cluster nodes.\n■ Retry the job after waiting for the current job to finish.\n■ If there are no jobs running in parallel create a setting in cassandra.conf file\nunder the settings key as follows:\n\"jobCleanupTimeoutSec\": 0\nRetry the job.\nRemove this setting once the jobs start running again. The default time-out is\n8 hours." }, "3331": { "code": 3331, - "desc": "One ou more de o input parameters ou arguments para restauração está inválido.", + "desc": "One or more of the input parameters or arguments for restore is invalid.", "first_action": "ChecktherestoreSelectionsandalternateRecoveryOptionsfiles.Thefiles", - "full_action": "Executar o seguinte como appropriate:\n■ ChecktherestoreSelectionsandalternateRecoveryOptionsfiles.Thefiles\nmust contain valid keyspace e alternate column family names.\n■ If um alternate column family ou keyspace specified, make sure que they\nestão specified como part de o restauração selection ou o restoreSelections está para\no cheio cluster.\nO seguinte table contains non-supported restauração combinations e o solution\npara o issue.\nTable 1-5 Non-supported combinations\nErro Details Scenario Solution\nKeyspace e its Restoringbothkeyspace Specifyeitherthekeyspace’snewName\ncolumn family não é possível be e its column family orthecolumnfamily’snewNameinthe\nrenamed together. com new names. alternateRecoveryOptions.\nNão selection should be When performing um cheio Remove selectionCriteria from\ngiven when Todos recovery e restoreSelections.\nKEYSPACES está keyspaces estão\nrecovered. selected.\nMissing ou blank Performing um selective Add o keyspace in o\nkeyspace in selection recovery e selecting selectionCriteria to identify o\ncolumn family without columnFamilies que belong to o\nspecifyingitskeyspace. corresponding keyspace.\nKeyspace não é possível be Performing um selective Add o same keyspace in o\nrenamed if it está não recovery e there está um selectionCriteria que está also\nselected in GRANULAR missingkeyspacename specified in\nrecovery. in alternateRecoveryOptions.\nrestoreSelections.\nMissingkeyspaceorthe Renaming um column Add o keyspace in\nkeyspacenameisblank family without alternateRecoveryOptions to\npara o corresponding specifyingitskeyspace. identify which columnFamilies\ncolumn family being belong to which corresponding\nrenamed. keyspace.\nO seguinte table contains input validation errors e o solution para o issue.\nTable 1-6 Basic input validation errors\nErro Details Scenario Solution\nMissing ou blank O Add um valid keyspace value in\nkeyspace in selection. restoreSelections selectionCriteria.\ncontains um inválido\nkeyspace name.\nBlank column family O Add um valid column family value in\nin selection. restoreSelections selectionCriteria.\ncontains um inválido\ncolumn family name.\nTable 1-6 Basic input validation errors (continued)\nErro Details Scenario Solution\nMissingkeyspaceorthe O Add um valid keyspace name value in\nkeyspacenameisblank alternateRecoveryOptions alternateRecoveryOptions.\nin o renaming. contains um inválido\nkeyspace name.\nMissingorblankcolumn O Add um valid column family name\nfamily name in o alternateRecoveryOptions value in\nrenaming. contains um inválido alternateRecoveryOptions.\ncolumn family name.\nO strategy name O AddSIMPLEorNETWORKasvaluesin\nmust be either SIMPLE alternateRecoveryOptions thestrategy nameforthereplication\nou Rede. contains um inválido strategy que está requerido para o\nstrategy name value. respective keyspace in\nalternateRecoveryOptions.\nMissing o strategy O AddSIMPLEorNETWORKasvaluesin\nname e it must be alternateRecoveryOptions strategy name para o replication\neither SIMPLE ou does não contain um strategy que está requerido para o\nRede. strategy name value. respective keyspace in\nalternateRecoveryOptions." + "full_action": "Perform the following as appropriate:\n■ ChecktherestoreSelectionsandalternateRecoveryOptionsfiles.Thefiles\nmust contain valid keyspace and alternate column family names.\n■ If an alternate column family or keyspace specified, make sure that they\nare specified as part of the restore selection or the restoreSelections is for\nthe full cluster.\nThe following table contains non-supported restore combinations and the solution\nfor the issue.\nTable 1-5 Non-supported combinations\nError Details Scenario Solution\nKeyspace and its Restoringbothkeyspace Specifyeitherthekeyspace’snewName\ncolumn family cannot be and its column family orthecolumnfamily’snewNameinthe\nrenamed together. with new names. alternateRecoveryOptions.\nNo selection should be When performing a full Remove selectionCriteria from\ngiven when ALL recovery and restoreSelections.\nKEYSPACES is keyspaces are\nrecovered. selected.\nMissing or blank Performing a selective Add the keyspace in the\nkeyspace in selection recovery and selecting selectionCriteria to identify the\ncolumn family without columnFamilies that belong to the\nspecifyingitskeyspace. corresponding keyspace.\nKeyspace cannot be Performing a selective Add the same keyspace in the\nrenamed if it is not recovery and there is a selectionCriteria that is also\nselected in GRANULAR missingkeyspacename specified in\nrecovery. in alternateRecoveryOptions.\nrestoreSelections.\nMissingkeyspaceorthe Renaming a column Add the keyspace in\nkeyspacenameisblank family without alternateRecoveryOptions to\nfor the corresponding specifyingitskeyspace. identify which columnFamilies\ncolumn family being belong to which corresponding\nrenamed. keyspace.\nThe following table contains input validation errors and the solution for the issue.\nTable 1-6 Basic input validation errors\nError Details Scenario Solution\nMissing or blank The Add a valid keyspace value in\nkeyspace in selection. restoreSelections selectionCriteria.\ncontains an invalid\nkeyspace name.\nBlank column family The Add a valid column family value in\nin selection. restoreSelections selectionCriteria.\ncontains an invalid\ncolumn family name.\nTable 1-6 Basic input validation errors (continued)\nError Details Scenario Solution\nMissingkeyspaceorthe The Add a valid keyspace name value in\nkeyspacenameisblank alternateRecoveryOptions alternateRecoveryOptions.\nin the renaming. contains an invalid\nkeyspace name.\nMissingorblankcolumn The Add a valid column family name\nfamily name in the alternateRecoveryOptions value in\nrenaming. contains an invalid alternateRecoveryOptions.\ncolumn family name.\nThe strategy name The AddSIMPLEorNETWORKasvaluesin\nmust be either SIMPLE alternateRecoveryOptions thestrategy nameforthereplication\nor NETWORK. contains an invalid strategy that is required for the\nstrategy name value. respective keyspace in\nalternateRecoveryOptions.\nMissing the strategy The AddSIMPLEorNETWORKasvaluesin\nname and it must be alternateRecoveryOptions strategy name for the replication\neither SIMPLE or does not contain a strategy that is required for the\nNETWORK. strategy name value. respective keyspace in\nalternateRecoveryOptions." }, "3332": { "code": 3332, - "desc": "BackupfailedduetoaninvalidqueryintheCassandraQueryLanguage shell comando.", - "first_action": "Garanta que o Cassandra version e configuration on", - "full_action": "Garanta que o Cassandra version e configuration on\no data staging servers match que de o Cassandra production nodes." + "desc": "BackupfailedduetoaninvalidqueryintheCassandraQueryLanguage shell command.", + "first_action": "Ensure that the Cassandra version and configuration on", + "full_action": "Ensure that the Cassandra version and configuration on\nthe data staging servers match that of the Cassandra production nodes." }, "3333": { "code": 3333, - "desc": "Restauração has falhou.", - "first_action": "Verifique que o selections in o restoreSelections e", - "full_action": "Verifique que o selections in o restoreSelections e\no alternateRestoreOptions, como mentioned in o Cassandra documentation,\nestão correct. Review o restauração prerequisites." + "desc": "Restore has failed.", + "first_action": "Verify that the selections in the restoreSelections and", + "full_action": "Verify that the selections in the restoreSelections and\nthe alternateRestoreOptions, as mentioned in the Cassandra documentation,\nare correct. Review the restore prerequisites." }, "3335": { "code": 3335, - "desc": "Column family must be selected when you rename o arquivo.", - "first_action": "Select o name de o column family in o", - "full_action": "Select o name de o column family in o\nrestoreSelections if you desejar to rename o column family. Refer to o restauração\nprerequisites in o Cassandra documentation." + "desc": "Column family must be selected when you rename the file.", + "first_action": "Select the name of the column family in the", + "full_action": "Select the name of the column family in the\nrestoreSelections if you want to rename the column family. Refer to the restore\nprerequisites in the Cassandra documentation." }, "3336": { "code": 3336, - "desc": "Keyspace não é possível be changed when column family está selected.", - "first_action": "If you desejar to rename um keyspace, don’t select um granular", - "full_action": "If you desejar to rename um keyspace, don’t select um granular\nrestauração de um column family. Select o keyspace to rename e restauração o whole\nkeyspace." + "desc": "Keyspace cannot be changed when column family is selected.", + "first_action": "If you want to rename a keyspace, don’t select a granular", + "full_action": "If you want to rename a keyspace, don’t select a granular\nrestore of a column family. Select the keyspace to rename and restore the whole\nkeyspace." }, "3337": { "code": 3337, - "desc": "Strategy não é possível be changed when column family está selected.", - "first_action": "If you desejar to change o strategy you should apenas select", - "full_action": "If you desejar to change o strategy you should apenas select\no keyspace to be restored e não um individual column family in que keyspace.\nSelect o keyspace como um whole to be restored if you desejar to change o strategy." + "desc": "Strategy cannot be changed when column family is selected.", + "first_action": "If you want to change the strategy you should only select", + "full_action": "If you want to change the strategy you should only select\nthe keyspace to be restored and not an individual column family in that keyspace.\nSelect the keyspace as a whole to be restored if you want to change the strategy." }, "3340": { "code": 3340, - "desc": "Verbose está não specified. NetBackup status codes 575 NetBackup status codes", + "desc": "Verbose is not specified. NetBackup status codes 575 NetBackup status codes", "first_action": "Youmustspecifyaverbosesettinginthecassandra.conf", - "full_action": "Youmustspecifyaverbosesettinginthecassandra.conf\narquivo." + "full_action": "Youmustspecifyaverbosesettinginthecassandra.conf\nfile." }, "3341": { "code": 3341, - "desc": "Maximum log size está não specified.", - "first_action": "You must specify um maximum log size in o settings in", - "full_action": "You must specify um maximum log size in o settings in\no cassandra.conf arquivo." + "desc": "Maximum log size is not specified.", + "first_action": "You must specify a maximum log size in the settings in", + "full_action": "You must specify a maximum log size in the settings in\nthe cassandra.conf file." }, "3342": { "code": 3342, - "desc": "Falhou to clean up Production Cassandra cluster.", - "first_action": "You must manually clear o folder que está specified in", - "full_action": "You must manually clear o folder que está specified in\nsettings on o Cassandra cluster nodes." + "desc": "Failed to clean up Production Cassandra cluster.", + "first_action": "You must manually clear the folder that is specified in", + "full_action": "You must manually clear the folder that is specified in\nsettings on the Cassandra cluster nodes." }, "3346": { "code": 3346, - "desc": "Optional threshold está não specified.", - "first_action": "You must set o optional threshold value to um max de 32", - "full_action": "You must set o optional threshold value to um max de 32\nin o cassandra.conf arquivo." + "desc": "Optional threshold is not specified.", + "first_action": "You must set the optional threshold value to a max of 32", + "full_action": "You must set the optional threshold value to a max of 32\nin the cassandra.conf file." }, "3361": { "code": 3361, - "desc": "MongoDB Ops Manager recovery falhou.", - "first_action": "Collect e review o logs que estão shown para additional", - "full_action": "Collect e review o logs que estão shown para additional\ninformação: bprd, tar, e nbaapireq_handler. If o problema persists, collect\no logs que estão indicated e contate Cohesity Technical Support.\nThelogsarefoundat:Windows:install_path\\NetBackup\\logs\\UNIXandLinux:\n/usr/openv/netbackup/logs/." + "desc": "MongoDB Ops Manager recovery failed.", + "first_action": "Collect and review the logs that are shown for additional", + "full_action": "Collect and review the logs that are shown for additional\ninformation: bprd, tar, and nbaapireq_handler. If the problem persists, collect\nthe logs that are indicated and contact Cohesity Technical Support.\nThelogsarefoundat:Windows:install_path\\NetBackup\\logs\\UNIXandLinux:\n/usr/openv/netbackup/logs/." }, "3362": { "code": 3362, - "desc": "O missing MongoDB oplogs estão requerido para recovery.", + "desc": "The missing MongoDB oplogs are required for recovery.", "first_action": "Selectanothersetofbackupandincrementalimagesand", - "full_action": "Selectanothersetofbackupandincrementalimagesand\nretry o recovery operation." + "full_action": "Selectanothersetofbackupandincrementalimagesand\nretry the recovery operation." }, "3363": { "code": 3363, - "desc": "Either o cluster ou one de its nodes está down.", - "first_action": "Make sure que o cluster e todos o nodes de o cluster", - "full_action": "Make sure que o cluster e todos o nodes de o cluster\nestão in um Active state in MongoDB Ops." + "desc": "Either the cluster or one of its nodes is down.", + "first_action": "Make sure that the cluster and all the nodes of the cluster", + "full_action": "Make sure that the cluster and all the nodes of the cluster\nare in an Active state in MongoDB Ops." }, "3364": { "code": 3364, - "desc": "O selected cluster está não um third party managed cluster.", - "first_action": "Garanta que o target MongoDB Cluster está Third party", - "full_action": "Garanta que o target MongoDB Cluster está Third party\nmanaged in MongoDB Ops Manager e retry o recovery operation." + "desc": "The selected cluster is not a third party managed cluster.", + "first_action": "Ensure that the target MongoDB Cluster is Third party", + "full_action": "Ensure that the target MongoDB Cluster is Third party\nmanaged in MongoDB Ops Manager and retry the recovery operation." }, "3365": { "code": 3365, - "desc": "Falhou to mark o snapshot como FINISHED.", - "first_action": "Collect e review o logs que estão shown para additional", - "full_action": "Collect e review o logs que estão shown para additional\ninformação: bpbrm, nbaapidiscv, e bpbkar. If o problema persists, collect o\nlogs que estão indicated e contate Cohesity Technical Support.\nThelogsarefoundat:Windows:install_path\\NetBackup\\logs\\UNIXandLinux:\n/usr/openv/netbackup/logs/." + "desc": "Failed to mark the snapshot as FINISHED.", + "first_action": "Collect and review the logs that are shown for additional", + "full_action": "Collect and review the logs that are shown for additional\ninformation: bpbrm, nbaapidiscv, and bpbkar. If the problem persists, collect the\nlogs that are indicated and contact Cohesity Technical Support.\nThelogsarefoundat:Windows:install_path\\NetBackup\\logs\\UNIXandLinux:\n/usr/openv/netbackup/logs/." }, "3366": { "code": 3366, - "desc": "Falhou to mark o snapshot como Falhou.", - "first_action": "Collect e review o logs que estão shown para additional", - "full_action": "Collect e review o logs que estão shown para additional\ninformação: bpbrm, nbaapidiscv, e bpbkar. If o problema persists, collect o\nlogs que estão indicated e contate Cohesity Technical Support.\nThelogsarefoundat:Windows:install_path\\NetBackup\\logs\\UNIXandLinux:\n/usr/openv/netbackup/logs/." + "desc": "Failed to mark the snapshot as FAILED.", + "first_action": "Collect and review the logs that are shown for additional", + "full_action": "Collect and review the logs that are shown for additional\ninformation: bpbrm, nbaapidiscv, and bpbkar. If the problem persists, collect the\nlogs that are indicated and contact Cohesity Technical Support.\nThelogsarefoundat:Windows:install_path\\NetBackup\\logs\\UNIXandLinux:\n/usr/openv/netbackup/logs/." }, "3367": { "code": 3367, - "desc": "NetBackup found um gap in o MongoDB oplogs.", + "desc": "NetBackup found a gap in the MongoDB oplogs.", "first_action": "Startafullbackupandconfirmthattheoplogsaredumped", - "full_action": "Startafullbackupandconfirmthattheoplogsaredumped\nat o oplog location." + "full_action": "Startafullbackupandconfirmthattheoplogsaredumped\nat the oplog location." }, "3600": { "code": 3600, - "desc": "Não é possível executar o COSP operation.", + "desc": "Cannot perform the COSP operation.", "first_action": "/usr/openv/netbackup/logs/bpbkar", - "full_action": "Review o seguinte COSP logs para more details:\nPara backup operations:\n■ /usr/openv/netbackup/logs/bpbkar\n■ /usr/openv/netbackup/logs/nbcosp\nPara restauração operations:\n■ /usr/openv/netbackup/logs/tar\n■ /usr/openv/netbackup/logs/bptm\n■ /usr/openv/netbackup/logs/nbcosp" + "full_action": "Review the following COSP logs for more details:\nFor backup operations:\n■ /usr/openv/netbackup/logs/bpbkar\n■ /usr/openv/netbackup/logs/nbcosp\nFor restore operations:\n■ /usr/openv/netbackup/logs/tar\n■ /usr/openv/netbackup/logs/bptm\n■ /usr/openv/netbackup/logs/nbcosp" }, "3601": { "code": 3601, - "desc": "Não é possível complete o cloud operation.", - "first_action": "Garanta que o backup host ou recovery host has connectivity to o cloud", - "full_action": "Executar o seguinte como appropriate:\n■ Garanta que o backup host ou recovery host has connectivity to o cloud\nendpoint.\n■ Garanta que o COSP account has valid credentials.\n■ Garanta que o bucket ou container exists e o provided credentials have\no requerido permissions to access them.\nYoucanvalidateusinganycloudproviderCLIorcURLcommandstovalidateREST\nAPI para cloud operation works from o backup ou o recovery host." + "desc": "Cannot complete the cloud operation.", + "first_action": "Ensure that the backup host or recovery host has connectivity to the cloud", + "full_action": "Perform the following as appropriate:\n■ Ensure that the backup host or recovery host has connectivity to the cloud\nendpoint.\n■ Ensure that the COSP account has valid credentials.\n■ Ensure that the bucket or container exists and the provided credentials have\nthe required permissions to access them.\nYoucanvalidateusinganycloudproviderCLIorcURLcommandstovalidateREST\nAPI for cloud operation works from the backup or the recovery host." }, "3602": { "code": 3602, - "desc": "Não é possível run o operation because de insufficient permissions.", - "first_action": "Use o credentials que have todos o proper permissions", - "full_action": "Use o credentials que have todos o proper permissions\nto executar um backup e restauração operation." + "desc": "Cannot run the operation because of insufficient permissions.", + "first_action": "Use the credentials that have all the proper permissions", + "full_action": "Use the credentials that have all the proper permissions\nto perform a backup and restore operation." }, "3603": { "code": 3603, - "desc": "Não é possível find o object in o specified container ou bucket.", - "first_action": "During policy configuration, provide o object que exists", - "full_action": "During policy configuration, provide o object que exists\nin o selected bucket ou container." + "desc": "Cannot find the object in the specified container or bucket.", + "first_action": "During policy configuration, provide the object that exists", + "full_action": "During policy configuration, provide the object that exists\nin the selected bucket or container." }, "3605": { "code": 3605, - "desc": "Falhou to conectar to NetBackup COSP process.", - "first_action": "Make sure que o nbcosp process está executando usando bpps", - "full_action": "Make sure que o nbcosp process está executando usando bpps\ncomando.\nYou can manually start o nbcosp process por usando o seguinte:\n/usr/openv/pdde/pdcr/bin/nbcosp start" + "desc": "Failed to connect to NetBackup COSP process.", + "first_action": "Make sure that the nbcosp process is running using bpps", + "full_action": "Make sure that the nbcosp process is running using bpps\ncommand.\nYou can manually start the nbcosp process by using the following:\n/usr/openv/pdde/pdcr/bin/nbcosp start" }, "3606": { "code": 3606, - "desc": "Inválido backup selection format foi used to specify o value.", - "first_action": "Make sure que o backup selection format para specifying", - "full_action": "Make sure que o backup selection format para specifying\nvalues está followed e correct. Values estão specified within single quotes in o\nbackup selection." + "desc": "Invalid backup selection format was used to specify the value.", + "first_action": "Make sure that the backup selection format for specifying", + "full_action": "Make sure that the backup selection format for specifying\nvalues is followed and correct. Values are specified within single quotes in the\nbackup selection." }, "3607": { "code": 3607, - "desc": "Inválido backup selection format.", - "first_action": "Verifique que o backup selection format está correct.", - "full_action": "Verifique que o backup selection format está correct." + "desc": "Invalid backup selection format.", + "first_action": "Verify that the backup selection format is correct.", + "full_action": "Verify that the backup selection format is correct." }, "3608": { "code": 3608, - "desc": "Inválido filter query type ou backup selection format.", - "first_action": "Verifique que o backup selection format está correct.", - "full_action": "Verifique que o backup selection format está correct." + "desc": "Invalid filter query type or backup selection format.", + "first_action": "Verify that the backup selection format is correct.", + "full_action": "Verify that the backup selection format is correct." }, "3609": { "code": 3609, - "desc": "Não é possível process response from o COSP process.", + "desc": "Cannot process response from the COSP process.", "first_action": "/usr/openv/netbackup/logs/bpbkar", - "full_action": "Review o seguinte COSP logs para more details:\nPara backup operations:\n■ /usr/openv/netbackup/logs/bpbkar\n■ /usr/openv/netbackup/logs/nbcosp\nPara restauração operations:\n■ /usr/openv/netbackup/logs/tar\n■ /usr/openv/netbackup/logs/bptm\n■ /usr/openv/netbackup/logs/nbcosp" + "full_action": "Review the following COSP logs for more details:\nFor backup operations:\n■ /usr/openv/netbackup/logs/bpbkar\n■ /usr/openv/netbackup/logs/nbcosp\nFor restore operations:\n■ /usr/openv/netbackup/logs/tar\n■ /usr/openv/netbackup/logs/bptm\n■ /usr/openv/netbackup/logs/nbcosp" }, "3612": { "code": 3612, - "desc": "Bucket ou container does não exist.", - "first_action": "Apenas add um existing container ou bucket from o policy", - "full_action": "Apenas add um existing container ou bucket from o policy\nconfiguration." + "desc": "Bucket or container does not exist.", + "first_action": "Only add an existing container or bucket from the policy", + "full_action": "Only add an existing container or bucket from the policy\nconfiguration." }, "3613": { "code": 3613, - "desc": "ACLs estão não enabled in o bucket e o restauração does não attempt to set ACLs para o object ou blob.", - "first_action": "You must enable ACLs para o selected provider.", - "full_action": "You must enable ACLs para o selected provider." + "desc": "ACLs are not enabled in the bucket and the restore does not attempt to set ACLs for the object or blob.", + "first_action": "You must enable ACLs for the selected provider.", + "full_action": "You must enable ACLs for the selected provider." }, "3614": { "code": 3614, - "desc": "Não é possível set ACL on o object.", - "first_action": "Verifique que o ACL on o bucket está enabled.", - "full_action": "Verifique que o ACL on o bucket está enabled." + "desc": "Cannot set ACL on the object.", + "first_action": "Verify that the ACL on the bucket is enabled.", + "full_action": "Verify that the ACL on the bucket is enabled." }, "3615": { "code": 3615, - "desc": "Não é possível confirm upload to o object ou blob.", + "desc": "Cannot confirm upload to the object or blob.", "first_action": "/usr/openv/netbackup/logs/bpbkar", - "full_action": "Verifique que o metadata está valid e supported por o\ncloud provider. Review o seguinte COSP logs para more details:\nPara backup operations:\n■ /usr/openv/netbackup/logs/bpbkar\n■ /usr/openv/netbackup/logs/nbcosp\nPara restauração operations:\n■ /usr/openv/netbackup/logs/tar\n■ /usr/openv/netbackup/logs/bptm\n■ /usr/openv/netbackup/logs/nbcosp" + "full_action": "Check that the metadata is valid and supported by the\ncloud provider. Review the following COSP logs for more details:\nFor backup operations:\n■ /usr/openv/netbackup/logs/bpbkar\n■ /usr/openv/netbackup/logs/nbcosp\nFor restore operations:\n■ /usr/openv/netbackup/logs/tar\n■ /usr/openv/netbackup/logs/bptm\n■ /usr/openv/netbackup/logs/nbcosp" }, "3616": { "code": 3616, - "desc": "Falhou to fetch metadata para o blob.", + "desc": "Failed to fetch metadata for the blob.", "first_action": "/usr/openv/netbackup/logs/bpbkar", - "full_action": "Review o seguinte COSP logs para more details:\nPara backup operations:\n■ /usr/openv/netbackup/logs/bpbkar\n■ /usr/openv/netbackup/logs/nbcosp\nPara restauração operations:\n■ /usr/openv/netbackup/logs/tar\n■ /usr/openv/netbackup/logs/bptm\n■ /usr/openv/netbackup/logs/nbcosp" + "full_action": "Review the following COSP logs for more details:\nFor backup operations:\n■ /usr/openv/netbackup/logs/bpbkar\n■ /usr/openv/netbackup/logs/nbcosp\nFor restore operations:\n■ /usr/openv/netbackup/logs/tar\n■ /usr/openv/netbackup/logs/bptm\n■ /usr/openv/netbackup/logs/nbcosp" }, "3617": { "code": 3617, - "desc": "Vazio metadata received.", - "first_action": "Minimum requerido metadata fields should be salvo up.", - "full_action": "Minimum requerido metadata fields should be salvo up.\nPara example: Stats" + "desc": "Empty metadata received.", + "first_action": "Minimum required metadata fields should be backed up.", + "full_action": "Minimum required metadata fields should be backed up.\nFor example: Stats" }, "3618": { "code": 3618, - "desc": "Um erro occurs during ACL fetch para object.", - "first_action": "Review o appropriate logs. Also, verifique if um ACL está", - "full_action": "Review o appropriate logs. Also, verifique if um ACL está\nenabled on o bucket." + "desc": "An error occurs during ACL fetch for object.", + "first_action": "Review the appropriate logs. Also, check if an ACL is", + "full_action": "Review the appropriate logs. Also, check if an ACL is\nenabled on the bucket." }, "3619": { "code": 3619, - "desc": "Não é possível restauração vazio ACLs de o object ou blob.", - "first_action": "Verifique if o ACL está salvo up e if não, then this issue", - "full_action": "Verifique if o ACL está salvo up e if não, then this issue\nisexpectedbehavior.NeedtoenabletheACLonthebucketandthenrunabackup." + "desc": "Cannot restore empty ACLs of the object or blob.", + "first_action": "Check if the ACL is backed up and if not, then this issue", + "full_action": "Check if the ACL is backed up and if not, then this issue\nisexpectedbehavior.NeedtoenabletheACLonthebucketandthenrunabackup." }, "3620": { "code": 3620, - "desc": "Provider does não support tag on objects.", - "first_action": "Remove o tags e retry o operation.", - "full_action": "Remove o tags e retry o operation." + "desc": "Provider does not support tag on objects.", + "first_action": "Remove the tags and retry the operation.", + "full_action": "Remove the tags and retry the operation." }, "3621": { "code": 3621, - "desc": "Não é possível back up o object ou blob due to inconsistent data.", - "first_action": "In o Activity monitor, note todos o inconsistent objects", - "full_action": "In o Activity monitor, note todos o inconsistent objects\nfrom o backup. Determinar which processos modified these objects during o\nbackup. Take appropriate steps to prevent this issue in future backups. Executar um\ncheio backup. Confirm que o inconsistent objects estão successfully salvo up." + "desc": "Cannot back up the object or blob due to inconsistent data.", + "first_action": "In the Activity monitor, note all the inconsistent objects", + "full_action": "In the Activity monitor, note all the inconsistent objects\nfrom the backup. Determine which processes modified these objects during the\nbackup. Take appropriate steps to prevent this issue in future backups. Perform a\nfull backup. Confirm that the inconsistent objects are successfully backed up." }, "3633": { "code": 3633, - "desc": "Não é possível retrieve o shared memória identifier.", - "first_action": "Garanta que there está enough armazenamento space.", - "full_action": "Executar o seguinte como appropriate:\n■ Garanta que there está enough armazenamento space.\n■ Restart o computer to clear qualquer shared memória which está não in use.\n■ Veja o ncfnbcs logs para more informação." + "desc": "Cannot retrieve the shared memory identifier.", + "first_action": "Ensure that there is enough storage space.", + "full_action": "Perform the following as appropriate:\n■ Ensure that there is enough storage space.\n■ Restart the computer to clear any shared memory which is not in use.\n■ See the ncfnbcs logs for more information." }, "3634": { "code": 3634, - "desc": "Não é possível attach o shared memória identifier.", - "first_action": "Provide o necessary access rights to o NetBackup usuário.", - "full_action": "Executar o seguinte como appropriate:\n■ Provide o necessary access rights to o NetBackup usuário.\n■ Veja o ncfnbcs logs para more informação." + "desc": "Cannot attach the shared memory identifier.", + "first_action": "Provide the necessary access rights to the NetBackup user.", + "full_action": "Perform the following as appropriate:\n■ Provide the necessary access rights to the NetBackup user.\n■ See the ncfnbcs logs for more information." }, "3635": { "code": 3635, - "desc": "Não é possível create o shared memória configuration diretório para dynamic data stream backups.", - "first_action": "Garanta que there está adequate armazenamento space ou number de nodes.", - "full_action": "Executar o seguinte como appropriate:\n■ Garanta que there está adequate armazenamento space ou number de nodes.\n■ Garanta que NetBackup has o permissions to create arquivos e folders in o\nlocation: install_path/db/config/.\n■ Veja o ncfnbcs logs para more informação." + "desc": "Cannot create the shared memory configuration directory for dynamic data stream backups.", + "first_action": "Ensure that there is adequate storage space or number of nodes.", + "full_action": "Perform the following as appropriate:\n■ Ensure that there is adequate storage space or number of nodes.\n■ Ensure that NetBackup has the permissions to create files and folders in the\nlocation: install_path/db/config/.\n■ See the ncfnbcs logs for more information." }, "3636": { "code": 3636, - "desc": "Não é possível abrir o shared memória configuration arquivo.", - "first_action": "Garanta que there está adequate armazenamento space ou number de nodes.", - "full_action": "Executar o seguinte como appropriate:\n■ Garanta que there está adequate armazenamento space ou number de nodes.\n■ Garanta que NetBackup has o permissions to create arquivos e folders in o\nlocation: install_path/db/config/shm/.\n■ Veja o ncfnbcs logs para more informação." + "desc": "Cannot open the shared memory configuration file.", + "first_action": "Ensure that there is adequate storage space or number of nodes.", + "full_action": "Perform the following as appropriate:\n■ Ensure that there is adequate storage space or number of nodes.\n■ Ensure that NetBackup has the permissions to create files and folders in the\nlocation: install_path/db/config/shm/.\n■ See the ncfnbcs logs for more information." }, "3637": { "code": 3637, - "desc": "Não é possível save o shared memória informação in o configuration arquivo.", - "first_action": "Garanta que there está adequate armazenamento space ou number de nodes.", - "full_action": "Executar o seguinte como appropriate:\n■ Garanta que there está adequate armazenamento space ou number de nodes.\n■ Garanta que NetBackup has o permissions to create arquivos e folders in o\nlocation: install_path/db/config/shm/parent_job_stream_number.\n■ Veja o ncfnbcs logs para more informação." + "desc": "Cannot save the shared memory information in the configuration file.", + "first_action": "Ensure that there is adequate storage space or number of nodes.", + "full_action": "Perform the following as appropriate:\n■ Ensure that there is adequate storage space or number of nodes.\n■ Ensure that NetBackup has the permissions to create files and folders in the\nlocation: install_path/db/config/shm/parent_job_stream_number.\n■ See the ncfnbcs logs for more information." }, "3638": { "code": 3638, - "desc": "O crawler esgotado fora waiting para o streams to attach.", - "first_action": "Confirm que o Maximum number de concurrent jobs", - "full_action": "Confirm que o Maximum number de concurrent jobs\nparâmetro in o policy configuration has um value greater than 1. Review o status\nofthesharedmemoryandconfirmthereisenoughsharedmemoryfortheoperation\nto run. Then retry o backup." + "desc": "The crawler timed out waiting for the streams to attach.", + "first_action": "Confirm that the Maximum number of concurrent jobs", + "full_action": "Confirm that the Maximum number of concurrent jobs\nparameter in the policy configuration has a value greater than 1. Review the status\nofthesharedmemoryandconfirmthereisenoughsharedmemoryfortheoperation\nto run. Then retry the backup." }, "3639": { "code": 3639, "desc": "Cannotcreateobjectpropertydirectoryfordynamicdatastreambackups.", - "first_action": "Garanta que there está adequate armazenamento space ou number de nodes.", - "full_action": "Executar o seguinte como appropriate:\n■ Garanta que there está adequate armazenamento space ou number de nodes.\n■ Garanta que NetBackup has o permissions to create arquivos e folders in o\nlocation: install_path/db/config/nbcosp/\n■ Veja o ncfnbcs logs para more informação." + "first_action": "Ensure that there is adequate storage space or number of nodes.", + "full_action": "Perform the following as appropriate:\n■ Ensure that there is adequate storage space or number of nodes.\n■ Ensure that NetBackup has the permissions to create files and folders in the\nlocation: install_path/db/config/nbcosp/\n■ See the ncfnbcs logs for more information." }, "3640": { "code": 3640, - "desc": "Não é possível abrir o object property configuration arquivo.", - "first_action": "Garanta que there está adequate armazenamento space ou number de nodes.", - "full_action": "Executar o seguinte como appropriate:\n■ Garanta que there está adequate armazenamento space ou number de nodes.\n■ Garanta que NetBackup has o permissions to create arquivos e folders in o\nlocation: install_path/db/config/nbcosp/parent_job\n■ Veja o ncfnbcs logs para more informação." + "desc": "Cannot open the object property configuration file.", + "first_action": "Ensure that there is adequate storage space or number of nodes.", + "full_action": "Perform the following as appropriate:\n■ Ensure that there is adequate storage space or number of nodes.\n■ Ensure that NetBackup has the permissions to create files and folders in the\nlocation: install_path/db/config/nbcosp/parent_job\n■ See the ncfnbcs logs for more information." }, "3641": { "code": 3641, - "desc": "Não é possível save o object property informação in o configuration arquivo.", - "first_action": "Garanta que there está adequate armazenamento space ou number de nodes.", - "full_action": "Executar o seguinte como appropriate:\n■ Garanta que there está adequate armazenamento space ou number de nodes.\n■ Garanta que NetBackup has gravar permissions para arquivos in o location:\ninstall_path/db/config/nbcosp/parent_job/stream_number/batch_number/filename.\n■ Veja o ncfnbcs logs para more informação." + "desc": "Cannot save the object property information in the configuration file.", + "first_action": "Ensure that there is adequate storage space or number of nodes.", + "full_action": "Perform the following as appropriate:\n■ Ensure that there is adequate storage space or number of nodes.\n■ Ensure that NetBackup has write permissions for files in the location:\ninstall_path/db/config/nbcosp/parent_job/stream_number/batch_number/filename.\n■ See the ncfnbcs logs for more information." }, "3642": { "code": 3642, - "desc": "Não é possível list o objects.", - "first_action": "Garanta que o nbcosp daemon está executando.", - "full_action": "Executar o seguinte como appropriate:\n■ Garanta que o nbcosp daemon está executando.\n■ Garanta que o bucket ou container exists.\n■ Veja o nbcosp e ncfnbcs logs para more informação." + "desc": "Cannot list the objects.", + "first_action": "Ensure that the nbcosp daemon is running.", + "full_action": "Perform the following as appropriate:\n■ Ensure that the nbcosp daemon is running.\n■ Ensure that the bucket or container exists.\n■ See the nbcosp and ncfnbcs logs for more information." }, "3643": { "code": 3643, - "desc": "Falhou to start backup operation.", - "first_action": "Confirm que o nbcosp service está active. Review o", - "full_action": "Confirm que o nbcosp service está active. Review o\nmessages in o Activity monitor e take corrective ação como necessary. Then\nretry o backup." + "desc": "Failed to start backup operation.", + "first_action": "Confirm that the nbcosp service is active. Review the", + "full_action": "Confirm that the nbcosp service is active. Review the\nmessages in the Activity monitor and take corrective action as necessary. Then\nretry the backup." }, "3644": { "code": 3644, - "desc": "O staging caminho que está provided in o policy está inválido. NetBackup status codes 588 NetBackup status codes", - "first_action": "Specify um valid caminho in o policy e retry o backup.", - "full_action": "Specify um valid caminho in o policy e retry o backup." + "desc": "The staging path that is provided in the policy is invalid. NetBackup status codes 588 NetBackup status codes", + "first_action": "Specify a valid path in the policy and retry the backup.", + "full_action": "Specify a valid path in the policy and retry the backup." }, "3645": { "code": 3645, - "desc": "Falhou to create ou insert into banco de dados.", + "desc": "Failed to create or insert into database.", "first_action": "Verifythatthetemporarydatabaseexistsatthetemporary", - "full_action": "Verifythatthetemporarydatabaseexistsatthetemporary\nstaging location. Confirm que o NetBackup service usuário has o requerido ler\ne gravar permissions para que banco de dados. Then retry o operation." + "full_action": "Verifythatthetemporarydatabaseexistsatthetemporary\nstaging location. Confirm that the NetBackup service user has the required read\nand write permissions for that database. Then retry the operation." }, "3646": { "code": 3646, - "desc": "Não é possível create o staging location diretório.", + "desc": "Cannot create the staging location directory.", "first_action": "ConfirmthattheNetBackupserviceuserhasthenecessary", - "full_action": "ConfirmthattheNetBackupserviceuserhasthenecessary\nler e gravar permissions to create directories at o temporary staging location.\nRetry o backup." + "full_action": "ConfirmthattheNetBackupserviceuserhasthenecessary\nread and write permissions to create directories at the temporary staging location.\nRetry the backup." }, "3647": { "code": 3647, - "desc": "Falhou to download object.", - "first_action": "Review o Activity monitor para details about o reason", - "full_action": "Review o Activity monitor para details about o reason\npara o falha e take appropriate corrective ação. Then retry o backup. If o\nreason para o falha está um API call, retry o backup." + "desc": "Failed to download object.", + "first_action": "Review the Activity monitor for details about the reason", + "full_action": "Review the Activity monitor for details about the reason\nfor the failure and take appropriate corrective action. Then retry the backup. If the\nreason for the failure is an API call, retry the backup." }, "3648": { "code": 3648, - "desc": "Arquivo está não found in o staging area.", - "first_action": "Review o Activity monitor para details about o falha", - "full_action": "Review o Activity monitor para details about o falha\ne take appropriate corrective ação. Then retry o backup." + "desc": "File is not found in the staging area.", + "first_action": "Review the Activity monitor for details about the failure", + "full_action": "Review the Activity monitor for details about the failure\nand take appropriate corrective action. Then retry the backup." }, "3649": { "code": 3649, - "desc": "Falhou to interpret o response from o cloud API.", + "desc": "Failed to interpret the response from the cloud API.", "first_action": "ReviewtheActivitymonitorforthereasonforfailureand", - "full_action": "ReviewtheActivitymonitorforthereasonforfailureand\ntake appropriate corrective ação. Then retry o backup." + "full_action": "ReviewtheActivitymonitorforthereasonforfailureand\ntake appropriate corrective action. Then retry the backup." }, "3650": { "code": 3650, - "desc": "Themultifactorauthenticationstatetokenisinvalidorexpiredornouser exists ou está associated com o specified token.", - "first_action": "Re-authenticate com o username e password to receive new state token.", - "full_action": "Executar o seguinte como appropriate:\nRe-authenticate com o username e password to receive new state token." + "desc": "Themultifactorauthenticationstatetokenisinvalidorexpiredornouser exists or is associated with the specified token.", + "first_action": "Re-authenticate with the username and password to receive new state token.", + "full_action": "Perform the following as appropriate:\nRe-authenticate with the username and password to receive new state token." }, "3651": { "code": 3651, - "desc": "O authorization header está não present, o token está inválido, ou you do não have permissão para this ação.", + "desc": "The authorization header is not present, the token is invalid, or you do not have permission for this action.", "first_action": "EnsurethatmultifactorauthenticationwebAPIsarecalledwithrequiredauthorization", - "full_action": "Executar o seguinte como appropriate:\nEnsurethatmultifactorauthenticationwebAPIsarecalledwithrequiredauthorization\nheader." + "full_action": "Perform the following as appropriate:\nEnsurethatmultifactorauthenticationwebAPIsarecalledwithrequiredauthorization\nheader." }, "3652": { "code": 3652, - "desc": "Falhou to validate o one-time password.", + "desc": "Failed to validate the one-time password.", "first_action": "Enter new one-time password.", - "full_action": "Executar o seguinte como appropriate:\nEnter new one-time password." + "full_action": "Perform the following as appropriate:\nEnter new one-time password." }, "3653": { "code": 3653, - "desc": "O multifactor authentication request não é possível be processed.", - "first_action": "Reconfigure o multifactor authentication so que um new state token está generated.", - "full_action": "Executar o seguinte como appropriate:\nReconfigure o multifactor authentication so que um new state token está generated." + "desc": "The multifactor authentication request cannot be processed.", + "first_action": "Reconfigure the multifactor authentication so that a new state token is generated.", + "full_action": "Perform the following as appropriate:\nReconfigure the multifactor authentication so that a new state token is generated." }, "3654": { "code": 3654, - "desc": "Falhou to configure multifactor authentication.", - "first_action": "Determinar if o usuário account has already registered multifactor authentication ou", - "full_action": "Executar o seguinte como appropriate:\nDeterminar if o usuário account has already registered multifactor authentication ou\nif o input secret key está valid. O secret key está shared secret between o\nauthenticator application e NetBackup. It está shown in o form de QR code on\nscreen." + "desc": "Failed to configure multifactor authentication.", + "first_action": "Determine if the user account has already registered multifactor authentication or", + "full_action": "Perform the following as appropriate:\nDetermine if the user account has already registered multifactor authentication or\nif the input secret key is valid. The secret key is shared secret between the\nauthenticator application and NetBackup. It is shown in the form of QR code on\nscreen." }, "3655": { "code": 3655, - "desc": "You do não have permissions to executar o operation.", - "first_action": "Set o correct RBAC permissions on o usuário account que allows o usuário to reset", - "full_action": "Executar o seguinte como appropriate:\nSet o correct RBAC permissions on o usuário account que allows o usuário to reset\nother users. Refer to o NetBackup API documentation para more details about\nRBAC permissions." + "desc": "You do not have permissions to perform the operation.", + "first_action": "Set the correct RBAC permissions on the user account that allows the user to reset", + "full_action": "Perform the following as appropriate:\nSet the correct RBAC permissions on the user account that allows the user to reset\nother users. Refer to the NetBackup API documentation for more details about\nRBAC permissions." }, "3656": { "code": 3656, - "desc": "Seu usuário account está não registered para multifactor authentication.", - "first_action": "This erro está apenas seen in o case de direct web API execution. If you veja this erro", - "full_action": "Executar o seguinte como appropriate:\nThis erro está apenas seen in o case de direct web API execution. If you veja this erro\nin regular operation, Cohesity recommends que you review o multifactor\nauthentication status de que usuário account." + "desc": "Your user account is not registered for multifactor authentication.", + "first_action": "This error is only seen in the case of direct web API execution. If you see this error", + "full_action": "Perform the following as appropriate:\nThis error is only seen in the case of direct web API execution. If you see this error\nin regular operation, Cohesity recommends that you review the multifactor\nauthentication status of that user account." }, "3657": { "code": 3657, - "desc": "Failedtocheckwhethermultifactorauthenticationisenabledfortheuser account ou não.", - "first_action": "Review o bpjava-msvc log arquivo on o primary servidor para more details.", - "full_action": "Executar o seguinte como appropriate:\nReview o bpjava-msvc log arquivo on o primary servidor para more details." + "desc": "Failedtocheckwhethermultifactorauthenticationisenabledfortheuser account or not.", + "first_action": "Review the bpjava-msvc log file on the primary server for more details.", + "full_action": "Perform the following as appropriate:\nReview the bpjava-msvc log file on the primary server for more details." }, "3658": { "code": 3658, - "desc": "Multifactor authentication está enforced in o domain, however seu usuário account está não configurado para multifactor authentication.", - "first_action": "Configure multifactor authentication para um given usuário account e then try usuário", - "full_action": "Executar o seguinte como appropriate:\nConfigure multifactor authentication para um given usuário account e then try usuário\nauthentication." + "desc": "Multifactor authentication is enforced in the domain, however your user account is not configured for multifactor authentication.", + "first_action": "Configure multifactor authentication for a given user account and then try user", + "full_action": "Perform the following as appropriate:\nConfigure multifactor authentication for a given user account and then try user\nauthentication." }, "3660": { "code": 3660, - "desc": "Pagination filter string está não in o correct format.", - "first_action": "Provide OData filter in o correct format when you invoke o NetBackup web API", - "full_action": "Executar o seguinte como appropriate:\nProvide OData filter in o correct format when you invoke o NetBackup web API\nto list multifactor authentication configurado users." + "desc": "Pagination filter string is not in the correct format.", + "first_action": "Provide OData filter in the correct format when you invoke the NetBackup web API", + "full_action": "Perform the following as appropriate:\nProvide OData filter in the correct format when you invoke the NetBackup web API\nto list multifactor authentication configured users." }, "3661": { "code": 3661, - "desc": "O specified operation está não allowed on this NetBackup solution.", + "desc": "The specified operation is not allowed on this NetBackup solution.", "first_action": "RefertothecorrectNetBackupsolutionguidetoconfiguremultifactorauthentication,", - "full_action": "Executar o seguinte como appropriate:\nRefertothecorrectNetBackupsolutionguidetoconfiguremultifactorauthentication,\nsuch como o NetBackup Flex Scale documentation set." + "full_action": "Perform the following as appropriate:\nRefertothecorrectNetBackupsolutionguidetoconfiguremultifactorauthentication,\nsuch as the NetBackup Flex Scale documentation set." }, "3662": { "code": 3662, - "desc": "Falhou to validate o one-time password during configuration de multifactor authentication.", - "first_action": "Make o clocks correct como per o current time at o primary servidor ou at o", - "full_action": "Executar o seguinte como appropriate:\nMake o clocks correct como per o current time at o primary servidor ou at o\nhandheld smart dispositivo onde authenticator application está executando." + "desc": "Failed to validate the one-time password during configuration of multifactor authentication.", + "first_action": "Make the clocks correct as per the current time at the primary server or at the", + "full_action": "Perform the following as appropriate:\nMake the clocks correct as per the current time at the primary server or at the\nhandheld smart device where authenticator application is running." }, "3675": { "code": 3675, - "desc": "O multifactor authentication request ID does não exist.", - "first_action": "Specify o valid multifactor authentication request ID in", - "full_action": "Specify o valid multifactor authentication request ID in\no API." + "desc": "The multifactor authentication request ID does not exist.", + "first_action": "Specify the valid multifactor authentication request ID in", + "full_action": "Specify the valid multifactor authentication request ID in\nthe API." }, "3676": { "code": 3676, - "desc": "O configuration não é possível be changed usando this host.", - "first_action": "Use o NetBackup web UI to executar o operation.", - "full_action": "Use o NetBackup web UI to executar o operation." + "desc": "The configuration cannot be changed using this host.", + "first_action": "Use the NetBackup web UI to perform the operation.", + "full_action": "Use the NetBackup web UI to perform the operation." }, "3677": { "code": 3677, - "desc": "O multifactor authentication request has esgotado fora.", - "first_action": "Garanta que you enter o one-time password within 180", - "full_action": "Garanta que you enter o one-time password within 180\nseconds during multifactor authentication." + "desc": "The multifactor authentication request has timed out.", + "first_action": "Ensure that you enter the one-time password within 180", + "full_action": "Ensure that you enter the one-time password within 180\nseconds during multifactor authentication." }, "3678": { "code": 3678, - "desc": "O multifactor authentication request está não valid.", - "first_action": "Use o same JWT token para both o API calls.", - "full_action": "Use o same JWT token para both o API calls." + "desc": "The multifactor authentication request is not valid.", + "first_action": "Use the same JWT token for both the API calls.", + "full_action": "Use the same JWT token for both the API calls." }, "3700": { "code": 3700, - "desc": "Falhou to configure o Hardware Security Module in NetBackup ou to update o existing configuration in NetBackup.", - "first_action": "Garanta que todos input parameters estão valid when configuring HSM.", - "full_action": "Executar o seguinte como appropriate:\n■ Garanta que todos input parameters estão valid when configuring HSM.\n■ ConfirmthattheserviceuserhasaccesstothetokendirectoryandthePKCS#11\nlibrary.\n■ Confirm HSM está instalado, o key está created, e you can log on to HSM.\n■ Garanta que o correct PKCS#11 library está in use, o HSM key está valid, e\no right HSM token está in use.\n■ Verifique que o configuration uses supported key algorithms.\n■ Review o logs at install_path/netbackup/logs/nbhsmcmd para debug\ninformação." + "desc": "Failed to configure the Hardware Security Module in NetBackup or to update the existing configuration in NetBackup.", + "first_action": "Ensure that all input parameters are valid when configuring HSM.", + "full_action": "Perform the following as appropriate:\n■ Ensure that all input parameters are valid when configuring HSM.\n■ ConfirmthattheserviceuserhasaccesstothetokendirectoryandthePKCS#11\nlibrary.\n■ Confirm HSM is installed, the key is created, and you can log on to HSM.\n■ Ensure that the correct PKCS#11 library is in use, the HSM key is valid, and\nthe right HSM token is in use.\n■ Verify that the configuration uses supported key algorithms.\n■ Review the logs at install_path/netbackup/logs/nbhsmcmd for debug\ninformation." }, "3701": { "code": 3701, "desc": "TherequestedHardwareSecurityModuleoperationcannotbeperformed.", - "first_action": "Garanta que todos input parameters estão valid when configuring HSM.", - "full_action": "Executar o seguinte como appropriate:\n■ Garanta que todos input parameters estão valid when configuring HSM.\n■ ConfirmthattheserviceuserhasaccesstothetokendirectoryandthePKCS#11\nlibrary.\n■ Confirm HSM está instalado, o key está created, e you can log on to HSM.\n■ Garanta que o correct PKCS#11 library está in use, o HSM key está valid, e\no right token está in use.\n■ Verifique que o configuration uses supported key algorithms.\n■ Review o logs at install_path/netbackup/logs/nbhsmcmd para debug\ninformação." + "first_action": "Ensure that all input parameters are valid when configuring HSM.", + "full_action": "Perform the following as appropriate:\n■ Ensure that all input parameters are valid when configuring HSM.\n■ ConfirmthattheserviceuserhasaccesstothetokendirectoryandthePKCS#11\nlibrary.\n■ Confirm HSM is installed, the key is created, and you can log on to HSM.\n■ Ensure that the correct PKCS#11 library is in use, the HSM key is valid, and\nthe right token is in use.\n■ Verify that the configuration uses supported key algorithms.\n■ Review the logs at install_path/netbackup/logs/nbhsmcmd for debug\ninformation." }, "3702": { "code": 3702, - "desc": "Falhou to find o PKCS library on o specified caminho.", - "first_action": "Confirm que o caminho informação está correct e que o", - "full_action": "Confirm que o caminho informação está correct e que o\nservice usuário has o requerido access permissions to o PKCS#11 library." + "desc": "Failed to find the PKCS library on the specified path.", + "first_action": "Confirm that the path information is correct and that the", + "full_action": "Confirm that the path information is correct and that the\nservice user has the required access permissions to the PKCS#11 library." }, "3703": { "code": 3703, - "desc": "O Hardware Security Module logon falhou.", - "first_action": "Provide o correct pin ou token label. Garanta que o", - "full_action": "Provide o correct pin ou token label. Garanta que o\nservice usuário has appropriate permissão to access HSM token object. Refer to o\nNetBackup Security e Encryption Guide para more details." + "desc": "The Hardware Security Module logon failed.", + "first_action": "Provide the correct pin or token label. Ensure that the", + "full_action": "Provide the correct pin or token label. Ensure that the\nservice user has appropriate permission to access HSM token object. Refer to the\nNetBackup Security and Encryption Guide for more details." }, "3704": { "code": 3704, - "desc": "O specified key does não exist in o Hardware Security Module.", + "desc": "The specified key does not exist in the Hardware Security Module.", "first_action": "ReviewtheavailablekeysintheHardwareSecurityModule", - "full_action": "ReviewtheavailablekeysintheHardwareSecurityModule\ne use o correct one." + "full_action": "ReviewtheavailablekeysintheHardwareSecurityModule\nand use the correct one." }, "3705": { "code": 3705, - "desc": "O desired cryptographic operation falhou.", - "first_action": "Garanta que todos input parameters estão valid when configuring HSM.", - "full_action": "Executar o seguinte como appropriate:\n■ Garanta que todos input parameters estão valid when configuring HSM.\n■ ConfirmthattheserviceuserhasaccesstothetokendirectoryandthePKCS#11\nlibrary.\n■ Confirm HSM está instalado, o key está created, e you can log on to HSM.\n■ Garanta que o correct PKCS#11 library está in use, o HSM key está valid, e\no right token está in use.\n■ Verifique que o configuration uses supported key algorithms.\n■ Review o logs at install_path/netbackup/logs/nbhsmcmd para debug\ninformação." + "desc": "The desired cryptographic operation failed.", + "first_action": "Ensure that all input parameters are valid when configuring HSM.", + "full_action": "Perform the following as appropriate:\n■ Ensure that all input parameters are valid when configuring HSM.\n■ ConfirmthattheserviceuserhasaccesstothetokendirectoryandthePKCS#11\nlibrary.\n■ Confirm HSM is installed, the key is created, and you can log on to HSM.\n■ Ensure that the correct PKCS#11 library is in use, the HSM key is valid, and\nthe right token is in use.\n■ Verify that the configuration uses supported key algorithms.\n■ Review the logs at install_path/netbackup/logs/nbhsmcmd for debug\ninformation." }, "3706": { "code": 3706, - "desc": "Falhou to retrieve o Hardware Security Module configuration in NetBackup.", - "first_action": "Garanta que o Hardware Security Module está configurado.", - "full_action": "Executar o seguinte como appropriate:\n■ Garanta que o Hardware Security Module está configurado.\n■ Reviewthelogsatinstall_path/netbackup/logs/nbhsmcmdforfurtherdebug\ninformação." + "desc": "Failed to retrieve the Hardware Security Module configuration in NetBackup.", + "first_action": "Ensure that the Hardware Security Module is configured.", + "full_action": "Perform the following as appropriate:\n■ Ensure that the Hardware Security Module is configured.\n■ Reviewthelogsatinstall_path/netbackup/logs/nbhsmcmdforfurtherdebug\ninformation." }, "3707": { "code": 3707, - "desc": "Hardware Security Module está não configurado in NetBackup.", - "first_action": "Configure o Hardware Security Module e retry o", - "full_action": "Configure o Hardware Security Module e retry o\ndesired operation." + "desc": "Hardware Security Module is not configured in NetBackup.", + "first_action": "Configure the Hardware Security Module and retry the", + "full_action": "Configure the Hardware Security Module and retry the\ndesired operation." }, "3708": { "code": 3708, - "desc": "O specified PKCS library caminho está inválido.", - "first_action": "Review o location de o PKCS library e provide o", - "full_action": "Review o location de o PKCS library e provide o\ncorrect PKCS library caminho." + "desc": "The specified PKCS library path is invalid.", + "first_action": "Review the location of the PKCS library and provide the", + "full_action": "Review the location of the PKCS library and provide the\ncorrect PKCS library path." }, "3709": { "code": 3709, - "desc": "O specified token label de o Hardware Security Module está inválido.", - "first_action": "Review o token label de o Hardware Security Module", - "full_action": "Review o token label de o Hardware Security Module\ne provide o valid HSM token label." + "desc": "The specified token label of the Hardware Security Module is invalid.", + "first_action": "Review the token label of the Hardware Security Module", + "full_action": "Review the token label of the Hardware Security Module\nand provide the valid HSM token label." }, "3710": { "code": 3710, - "desc": "O specified key identifier está inválido.", - "first_action": "Enter um valid e um unique HSM key identifier.", - "full_action": "Enter um valid e um unique HSM key identifier." + "desc": "The specified key identifier is invalid.", + "first_action": "Enter a valid and a unique HSM key identifier.", + "full_action": "Enter a valid and a unique HSM key identifier." }, "3711": { "code": 3711, - "desc": "O specified key label de o Hardware Security Module está inválido. NetBackup status codes 598 NetBackup status codes", - "first_action": "Enter um valid HSM key label.", - "full_action": "Enter um valid HSM key label." + "desc": "The specified key label of the Hardware Security Module is invalid. NetBackup status codes 598 NetBackup status codes", + "first_action": "Enter a valid HSM key label.", + "full_action": "Enter a valid HSM key label." }, "3712": { "code": 3712, - "desc": "O specified key algorithm está inválido.", + "desc": "The specified key algorithm is invalid.", "first_action": "Provideasupportedkeyalgorithm.RefertotheNetBackup", - "full_action": "Provideasupportedkeyalgorithm.RefertotheNetBackup\nSecurity Encryption Guide para more details." + "full_action": "Provideasupportedkeyalgorithm.RefertotheNetBackup\nSecurity Encryption Guide for more details." }, "3713": { "code": 3713, - "desc": "O specified key identifier already exists.", - "first_action": "Provide um unique identifier para o HSM key.", - "full_action": "Provide um unique identifier para o HSM key." + "desc": "The specified key identifier already exists.", + "first_action": "Provide a unique identifier for the HSM key.", + "full_action": "Provide a unique identifier for the HSM key." }, "3800": { "code": 3800, - "desc": "Não é possível retrieve o operation type.", - "first_action": "Para detailed troubleshooting informação, create um debug", - "full_action": "Para detailed troubleshooting informação, create um debug\nlogdirectoryfortheprocessthatreturnedthisstatuscode.Thenretrytheoperation\ne verifique o resulting dbagentsutil logs on o mídia servidor." + "desc": "Cannot retrieve the operation type.", + "first_action": "For detailed troubleshooting information, create a debug", + "full_action": "For detailed troubleshooting information, create a debug\nlogdirectoryfortheprocessthatreturnedthisstatuscode.Thenretrytheoperation\nand check the resulting dbagentsutil logs on the media server." }, "3801": { "code": 3801, - "desc": "Não é possível complete o solicitado operation.", - "first_action": "Para detailed troubleshooting informação, create um debug", - "full_action": "Para detailed troubleshooting informação, create um debug\nlogdirectoryfortheprocessthatreturnedthisstatuscode.Thenretrytheoperation\ne verifique o resulting dbagentsutil logs on o mídia servidor." + "desc": "Cannot complete the requested operation.", + "first_action": "For detailed troubleshooting information, create a debug", + "full_action": "For detailed troubleshooting information, create a debug\nlogdirectoryfortheprocessthatreturnedthisstatuscode.Thenretrytheoperation\nand check the resulting dbagentsutil logs on the media server." }, "3802": { "code": 3802, - "desc": "Não é possível run o comando.", - "first_action": "Verifique que o utility which está used in o solicitado", - "full_action": "Verifique que o utility which está used in o solicitado\noperation está instalado ou não.\nPara detailed troubleshooting informação, refer to o dbagentsutil logs on o\nmídia servidor." + "desc": "Cannot run the command.", + "first_action": "Check that the utility which is used in the requested", + "full_action": "Check that the utility which is used in the requested\noperation is installed or not.\nFor detailed troubleshooting information, refer to the dbagentsutil logs on the\nmedia server." }, "3803": { "code": 3803, - "desc": "Não é possível test o conexão to o banco de dados.", - "first_action": "Garanta que o requerido credentials para o banco de dados estão valid.", - "full_action": "If o conexão between o mídia servidor e o\nbanco de dados fails, executar o seguinte:\n■ Garanta que o requerido credentials para o banco de dados estão valid.\n■ Verifique que o mídia servidor está able to reach o banco de dados.\nPara detailed troubleshooting informação, refer to o dbagentsutil logs on o\nmídia servidor." + "desc": "Cannot test the connection to the database.", + "first_action": "Ensure that the required credentials for the database are valid.", + "full_action": "If the connection between the media server and the\ndatabase fails, perform the following:\n■ Ensure that the required credentials for the database are valid.\n■ Verify that the media server is able to reach the database.\nFor detailed troubleshooting information, refer to the dbagentsutil logs on the\nmedia server." }, "3804": { "code": 3804, - "desc": "Não é possível parse o argument.", - "first_action": "Para detailed troubleshooting informação, create um debug", - "full_action": "Para detailed troubleshooting informação, create um debug\nlogdirectoryfortheprocessthatreturnedthisstatuscode.Thenretrytheoperation\ne verifique o resulting dbagentsutil logs on o mídia servidor." + "desc": "Cannot parse the argument.", + "first_action": "For detailed troubleshooting information, create a debug", + "full_action": "For detailed troubleshooting information, create a debug\nlogdirectoryfortheprocessthatreturnedthisstatuscode.Thenretrytheoperation\nand check the resulting dbagentsutil logs on the media server." }, "3805": { "code": 3805, - "desc": "Fora de memória.", - "first_action": "Review o memória uso e configuration de o", - "full_action": "Review o memória uso e configuration de o\nbanco de dados servidor e then retry o operation com increased memória.\nPara detailed troubleshooting informação, refer to o dbagentsutil logs on mídia\nservidor." + "desc": "Out of memory.", + "first_action": "Review the memory usage and configuration of the", + "full_action": "Review the memory usage and configuration of the\ndatabase server and then retry the operation with increased memory.\nFor detailed troubleshooting information, refer to the dbagentsutil logs on media\nserver." }, "3806": { "code": 3806, - "desc": "Não é possível complete pre-backup operation, o banco de dados does não exist.", - "first_action": "Verifique que o banco de dados exists. Executar o discovery", - "full_action": "Verifique que o banco de dados exists. Executar o discovery\nagain e retry o solicitado operation." + "desc": "Cannot complete pre-backup operation, the database does not exist.", + "first_action": "Verify that the database exists. Perform the discovery", + "full_action": "Verify that the database exists. Perform the discovery\nagain and retry the requested operation." }, "3807": { "code": 3807, - "desc": "Não é possível complete o post-backup operation.", + "desc": "Cannot complete the post-backup operation.", "first_action": "Reviewthelogsandcheckwhichresourcesarenotcleaned", - "full_action": "Reviewthelogsandcheckwhichresourcesarenotcleaned\nup in o post backup operation." + "full_action": "Reviewthelogsandcheckwhichresourcesarenotcleaned\nup in the post backup operation." }, "3808": { "code": 3808, - "desc": "Não é possível verifique if o banco de dados exists.", - "first_action": "Garanta que o banco de dados está present before o solicitado", - "full_action": "Garanta que o banco de dados está present before o solicitado\noperation está performed." + "desc": "Cannot check if the database exists.", + "first_action": "Ensure that the database is present before the requested", + "full_action": "Ensure that the database is present before the requested\noperation is performed." }, "3809": { "code": 3809, - "desc": "Não é possível run o backup comando.", - "first_action": "Review o logs para verification de o comando e its", - "full_action": "Review o logs para verification de o comando e its\nattributes." + "desc": "Cannot run the backup command.", + "first_action": "Review the logs for verification of the command and its", + "full_action": "Review the logs for verification of the command and its\nattributes." }, "3810": { "code": 3810, - "desc": "Não é possível find o backup arquivo at o specified location.", - "first_action": "Para detailed troubleshooting informação, create um debug", - "full_action": "Para detailed troubleshooting informação, create um debug\nlogdirectoryfortheprocessthatreturnedthisstatuscode.Thenretrytheoperation\ne verifique o resulting dbagentsutil logs on o mídia servidor." + "desc": "Cannot find the backup file at the specified location.", + "first_action": "For detailed troubleshooting information, create a debug", + "full_action": "For detailed troubleshooting information, create a debug\nlogdirectoryfortheprocessthatreturnedthisstatuscode.Thenretrytheoperation\nand check the resulting dbagentsutil logs on the media server." }, "3811": { "code": 3811, - "desc": "Não é possível executar o PIT restauração.", - "first_action": "Garanta que o cloud armazenamento está disponível to executar o PIT restauração operation.", - "full_action": "Executar o seguinte como appropriate:\n■ Garanta que o cloud armazenamento está disponível to executar o PIT restauração operation.\n■ Refer to o dbagentsutil logs para o exact cause de failures." + "desc": "Cannot perform the PIT restore.", + "first_action": "Ensure that the cloud storage is available to perform the PIT restore operation.", + "full_action": "Perform the following as appropriate:\n■ Ensure that the cloud storage is available to perform the PIT restore operation.\n■ Refer to the dbagentsutil logs for the exact cause of failures." }, "3812": { "code": 3812, - "desc": "Não é possível executar pre-restore operation, banco de dados already exists.", + "desc": "Cannot perform pre-restore operation, database already exists.", "first_action": "Ensurethatthedatabasenameisuniqueandnotpresent", "full_action": "Ensurethatthedatabasenameisuniqueandnotpresent\nalready." }, "3813": { "code": 3813, - "desc": "Não é possível run o restauração comando.", - "first_action": "Verifique o dbagentsutil logs para verification de o", - "full_action": "Verifique o dbagentsutil logs para verification de o\ncomando e its attributes." + "desc": "Cannot run the restore command.", + "first_action": "Check the dbagentsutil logs for verification of the", + "full_action": "Check the dbagentsutil logs for verification of the\ncommand and its attributes." }, "3814": { "code": 3814, - "desc": "Não é possível create vazio banco de dados.", - "first_action": "Garanta que o banco de dados com o new name does não exist.", - "full_action": "Executar o seguinte como appropriate:\n■ Garanta que o banco de dados com o new name does não exist.\n■ Garanta there estão enough permissions to create o new databases.\n■ Ensurethatthereisenoughstoragespaceavailabletocreatethenewdatabase." + "desc": "Cannot create empty database.", + "first_action": "Ensure that the database with the new name does not exist.", + "full_action": "Perform the following as appropriate:\n■ Ensure that the database with the new name does not exist.\n■ Ensure there are enough permissions to create the new databases.\n■ Ensurethatthereisenoughstoragespaceavailabletocreatethenewdatabase." }, "3815": { "code": 3815, - "desc": "Não é possível complete o post-restore operation. NetBackup status codes 603 NetBackup status codes", + "desc": "Cannot complete the post-restore operation. NetBackup status codes 603 NetBackup status codes", "first_action": "Reviewthelogstocheckwhichresourcesarenotcleaned", - "full_action": "Reviewthelogstocheckwhichresourcesarenotcleaned\nup in o post-restore operation." + "full_action": "Reviewthelogstocheckwhichresourcesarenotcleaned\nup in the post-restore operation." }, "3816": { "code": 3816, - "desc": "Não é possível retrieve o list de databases.", - "first_action": "Garanta there estão enough permissions to retrieve o list de todos databases para o", - "full_action": "Executar o seguinte como appropriate:\n■ Garanta there estão enough permissions to retrieve o list de todos databases para o\nbanco de dados servidor.\n■ Review o logs para more informação." + "desc": "Cannot retrieve the list of databases.", + "first_action": "Ensure there are enough permissions to retrieve the list of all databases for the", + "full_action": "Perform the following as appropriate:\n■ Ensure there are enough permissions to retrieve the list of all databases for the\ndatabase server.\n■ Review the logs for more information." }, "3817": { "code": 3817, - "desc": "Não é possível complete o pre-backup operation.", - "first_action": "Para detailed troubleshooting informação, create um debug", - "full_action": "Para detailed troubleshooting informação, create um debug\nlogdirectoryfortheprocessthatreturnedthisstatuscode.Thenretrytheoperation\ne verifique o resulting dbagentsutil logs on o mídia servidor." + "desc": "Cannot complete the pre-backup operation.", + "first_action": "For detailed troubleshooting information, create a debug", + "full_action": "For detailed troubleshooting information, create a debug\nlogdirectoryfortheprocessthatreturnedthisstatuscode.Thenretrytheoperation\nand check the resulting dbagentsutil logs on the media server." }, "3818": { "code": 3818, - "desc": "Não é possível complete o pre-restore operation.", - "first_action": "Para detailed troubleshooting informação, create um debug", - "full_action": "Para detailed troubleshooting informação, create um debug\nlogdirectoryfortheprocessthatreturnedthisstatuscode.Thenretrytheoperation\ne verifique o resulting dbagentsutil logs on o mídia servidor." + "desc": "Cannot complete the pre-restore operation.", + "first_action": "For detailed troubleshooting information, create a debug", + "full_action": "For detailed troubleshooting information, create a debug\nlogdirectoryfortheprocessthatreturnedthisstatuscode.Thenretrytheoperation\nand check the resulting dbagentsutil logs on the media server." }, "3819": { "code": 3819, - "desc": "Não é possível complete o restauração operation.", - "first_action": "Para detailed troubleshooting informação, create um debug", - "full_action": "Para detailed troubleshooting informação, create um debug\nlogdirectoryfortheprocessthatreturnedthisstatuscode.Thenretrytheoperation\ne verifique o resulting dbagentsutil logs on o mídia servidor." + "desc": "Cannot complete the restore operation.", + "first_action": "For detailed troubleshooting information, create a debug", + "full_action": "For detailed troubleshooting information, create a debug\nlogdirectoryfortheprocessthatreturnedthisstatuscode.Thenretrytheoperation\nand check the resulting dbagentsutil logs on the media server." }, "3820": { "code": 3820, - "desc": "Internal servidor erro.", - "first_action": "Retry o operation e if o issue persists, visit", - "full_action": "Retry o operation e if o issue persists, visit\nsupport.veritas.com. O Cohesity Technical Support website site offers additional\ninformação to help you troubleshoot this issue." + "desc": "Internal server error.", + "first_action": "Retry the operation and if the issue persists, visit", + "full_action": "Retry the operation and if the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support website site offers additional\ninformation to help you troubleshoot this issue." }, "3821": { "code": 3821, - "desc": "Não é possível complete o credential validate operation.", - "first_action": "Garanta que servidor credentials estão correct.", - "full_action": "Garanta que servidor credentials estão correct." + "desc": "Cannot complete the credential validate operation.", + "first_action": "Ensure that server credentials are correct.", + "full_action": "Ensure that server credentials are correct." }, "3822": { "code": 3822, - "desc": "Não é possível excluir o banco de dados.", - "first_action": "Para detailed troubleshooting informação, create um debug", - "full_action": "Para detailed troubleshooting informação, create um debug\nlogdirectoryfortheprocessthatreturnedthisstatuscode.Thenretrytheoperation\ne verifique o resulting dbagentsutil logs on o mídia servidor." + "desc": "Cannot delete the database.", + "first_action": "For detailed troubleshooting information, create a debug", + "full_action": "For detailed troubleshooting information, create a debug\nlogdirectoryfortheprocessthatreturnedthisstatuscode.Thenretrytheoperation\nand check the resulting dbagentsutil logs on the media server." }, "3823": { "code": 3823, - "desc": "O cloud provider type não supported.", - "first_action": "Para detailed troubleshooting informação, create um debug", - "full_action": "Para detailed troubleshooting informação, create um debug\nlogdirectoryfortheprocessthatreturnedthisstatuscode.Thenretrytheoperation\ne verifique o resulting dbagentsutil logs on o mídia servidor." + "desc": "The cloud provider type not supported.", + "first_action": "For detailed troubleshooting information, create a debug", + "full_action": "For detailed troubleshooting information, create a debug\nlogdirectoryfortheprocessthatreturnedthisstatuscode.Thenretrytheoperation\nand check the resulting dbagentsutil logs on the media server." }, "3824": { "code": 3824, - "desc": "Falhou to fetch credentials from CMS.", + "desc": "Failed to fetch credentials from CMS.", "first_action": "Ensurethatthecorrectcredentialsareaddedandverified", - "full_action": "Ensurethatthecorrectcredentialsareaddedandverified\npara o requerido asset before o solicitado operation begins." + "full_action": "Ensurethatthecorrectcredentialsareaddedandverified\nfor the required asset before the requested operation begins." }, "3825": { "code": 3825, - "desc": "Não é possível executar o operation because não matching banco de dados agent found.", + "desc": "Cannot perform the operation because no matching database agent found.", "first_action": "Thedbutiliy(InternalCall)foundaninvalidagent.Retry", - "full_action": "Thedbutiliy(InternalCall)foundaninvalidagent.Retry\no operation com um supported configuration." + "full_action": "Thedbutiliy(InternalCall)foundaninvalidagent.Retry\nthe operation with a supported configuration." }, "3826": { "code": 3826, - "desc": "Não é possível executar o solicitado operation because o associated credentials foram não found.", + "desc": "Cannot perform the requested operation because the associated credentials were not found.", "first_action": "Ensurethatthecorrectcredentialsareaddedandverified.", "full_action": "Ensurethatthecorrectcredentialsareaddedandverified." }, "3827": { "code": 3827, - "desc": "Não é possível executar o restauração due to um inválido banco de dados name.", - "first_action": "Enter um banco de dados name usando supported characters que", - "full_action": "Enter um banco de dados name usando supported characters que\no cloud provider supports." + "desc": "Cannot perform the restore due to an invalid database name.", + "first_action": "Enter a database name using supported characters that", + "full_action": "Enter a database name using supported characters that\nthe cloud provider supports." }, "3828": { "code": 3828, - "desc": "Não foi possível to reach o banco de dados servidor host.", - "first_action": "Verifique o rede connectivity ou firewall rules to garanta", - "full_action": "Verifique o rede connectivity ou firewall rules to garanta\nthere está um conexão to o banco de dados servidor from o NetBackup mídia servidor que\nestá used during backup e restauração operations." + "desc": "Unable to reach the database server host.", + "first_action": "Check the network connectivity or firewall rules to ensure", + "full_action": "Check the network connectivity or firewall rules to ensure\nthere is a connection to the database server from the NetBackup media server that\nis used during backup and restore operations." }, "3829": { "code": 3829, - "desc": "Não é possível executar o solicitado operation because o native cliente utility does não exist on o provided host.", - "first_action": "Garanta que o DBPaaS Native Cliente utility package está", - "full_action": "Garanta que o DBPaaS Native Cliente utility package está\ninstalado on o mídia servidor." + "desc": "Cannot perform the requested operation because the native client utility does not exist on the provided host.", + "first_action": "Ensure that the DBPaaS Native Client utility package is", + "full_action": "Ensure that the DBPaaS Native Client utility package is\ninstalled on the media server." }, "3830": { "code": 3830, - "desc": "NetBackupWindowsprimaryserverdoesnotsupportbackupandrestore de databases com multi-byte ou non-English characters in their name.", - "first_action": "You can use um primary servidor executando on um Linux platform", - "full_action": "You can use um primary servidor executando on um Linux platform\nto run o backup de o AWS RDS instance que has multi-byte ou non-English\ncharacters in o display name." + "desc": "NetBackupWindowsprimaryserverdoesnotsupportbackupandrestore of databases with multi-byte or non-English characters in their name.", + "first_action": "You can use a primary server running on a Linux platform", + "full_action": "You can use a primary server running on a Linux platform\nto run the backup of the AWS RDS instance that has multi-byte or non-English\ncharacters in the display name." }, "3831": { "code": 3831, - "desc": "Não é possível create instant access para DBPaaS.", - "first_action": "Para detailed troubleshooting informação, create um debug", - "full_action": "Para detailed troubleshooting informação, create um debug\nlogdirectoryfortheprocessthatreturnedthisstatuscode.Thenretrytheoperation\ne verifique o resulting bprd logs on master servidor." + "desc": "Cannot create instant access for DBPaaS.", + "first_action": "For detailed troubleshooting information, create a debug", + "full_action": "For detailed troubleshooting information, create a debug\nlogdirectoryfortheprocessthatreturnedthisstatuscode.Thenretrytheoperation\nand check the resulting bprd logs on master server." }, "3832": { "code": 3832, - "desc": "Não é possível retrieve details de DBPaaS instant access.", - "first_action": "Para detailed troubleshooting informação, create um debug", - "full_action": "Para detailed troubleshooting informação, create um debug\nlogdirectoryfortheprocessthatreturnedthisstatuscode.Thenretrytheoperation\ne verifique o resulting bprd logs on master servidor." + "desc": "Cannot retrieve details of DBPaaS instant access.", + "first_action": "For detailed troubleshooting information, create a debug", + "full_action": "For detailed troubleshooting information, create a debug\nlogdirectoryfortheprocessthatreturnedthisstatuscode.Thenretrytheoperation\nand check the resulting bprd logs on master server." }, "3883": { "code": 3883, - "desc": "Não é possível excluir o DBPaaS instant access export caminho.", - "first_action": "Para detailed troubleshooting informação, create um debug", - "full_action": "Para detailed troubleshooting informação, create um debug\nlogdirectoryfortheprocessthatreturnedthisstatuscode.Thenretrytheoperation\ne verifique o resulting bprd logs on master servidor." + "desc": "Cannot delete the DBPaaS instant access export path.", + "first_action": "For detailed troubleshooting information, create a debug", + "full_action": "For detailed troubleshooting information, create a debug\nlogdirectoryfortheprocessthatreturnedthisstatuscode.Thenretrytheoperation\nand check the resulting bprd logs on master server." }, "3834": { "code": 3834, - "desc": "Falhou to fetch cloud plug-in credentials from Snapshot Manager. NetBackup status codes 608 NetBackup status codes", - "first_action": "Verifique que o Snapshot Manager está up e executando", - "full_action": "Verifique que o Snapshot Manager está up e executando\nbecause this erro occurs when NetBackup attempts to retrieve o cloud plug-in\ncredentials from Snapshot manager." + "desc": "Failed to fetch cloud plug-in credentials from Snapshot Manager. NetBackup status codes 608 NetBackup status codes", + "first_action": "Verify that the Snapshot Manager is up and running", + "full_action": "Verify that the Snapshot Manager is up and running\nbecause this error occurs when NetBackup attempts to retrieve the cloud plug-in\ncredentials from Snapshot manager." }, "3835": { "code": 3835, - "desc": "Falhou to unmount instant access caminho.", - "first_action": "Para detailed troubleshooting informação, create um debug", - "full_action": "Para detailed troubleshooting informação, create um debug\nlogdirectoryfortheprocessthatreturnedthisstatuscode.Thenretrytheoperation\ne verifique o resulting nbtar logs on mídia servidor." + "desc": "Failed to unmount instant access path.", + "first_action": "For detailed troubleshooting information, create a debug", + "full_action": "For detailed troubleshooting information, create a debug\nlogdirectoryfortheprocessthatreturnedthisstatuscode.Thenretrytheoperation\nand check the resulting nbtar logs on media server." }, "3836": { "code": 3836, - "desc": "Não é possível retrieve todos o DBPaaS instant access mounts.", - "first_action": "Para detailed troubleshooting informação, create um debug", - "full_action": "Para detailed troubleshooting informação, create um debug\nlogdirectoryfortheprocessthatreturnedthisstatuscode.Thenretrytheoperation\ne verifique o resulting bprd logs on master servidor." + "desc": "Cannot retrieve all the DBPaaS instant access mounts.", + "first_action": "For detailed troubleshooting information, create a debug", + "full_action": "For detailed troubleshooting information, create a debug\nlogdirectoryfortheprocessthatreturnedthisstatuscode.Thenretrytheoperation\nand check the resulting bprd logs on master server." }, "3837": { "code": 3837, - "desc": "Falhou to get Azure Managed Identity Access token.", - "first_action": "Retry o operation e if o issue persists, visit", - "full_action": "Retry o operation e if o issue persists, visit\nsupport.veritas.com. O Cohesity Technical Support website site offers additional\ninformação to help you troubleshoot this issue." + "desc": "Failed to get Azure Managed Identity Access token.", + "first_action": "Retry the operation and if the issue persists, visit", + "full_action": "Retry the operation and if the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support website site offers additional\ninformation to help you troubleshoot this issue." }, "3838": { "code": 3838, - "desc": "Falhou to verifique if banco de dados usuário has o super privilege.", - "first_action": "Review o dbagents logs para o verifique superuser", - "full_action": "Review o dbagents logs para o verifique superuser\ncomando e its attributes." + "desc": "Failed to check if database user has the super privilege.", + "first_action": "Review the dbagents logs for the check superuser", + "full_action": "Review the dbagents logs for the check superuser\ncommand and its attributes." }, "3839": { "code": 3839, - "desc": "O banco de dados usuário does não have super privilege.", - "first_action": "O banco de dados usuário must have o super privilege.", - "full_action": "O banco de dados usuário must have o super privilege." + "desc": "The database user does not have super privilege.", + "first_action": "The database user must have the super privilege.", + "full_action": "The database user must have the super privilege." }, "3840": { "code": 3840, - "desc": "Falhou to create o temporary restauração arquivo.", - "first_action": "Retry o restauração job.", - "full_action": "Retry o restauração job." + "desc": "Failed to create the temporary restore file.", + "first_action": "Retry the restore job.", + "full_action": "Retry the restore job." }, "3841": { "code": 3841, - "desc": "Não é possível complete o universal share operation.", + "desc": "Cannot complete the universal share operation.", "first_action": "Reviewthevpfslogsatthestoragepathofthedatamover", "full_action": "Reviewthevpfslogsatthestoragepathofthedatamover\ncontainer." }, "3842": { "code": 3842, - "desc": "O solicitado backup type para o corresponding DBPaaS asset está unsupported. NetBackup status codes 610 NetBackup status codes", + "desc": "The requested backup type for the corresponding DBPaaS asset is unsupported. NetBackup status codes 610 NetBackup status codes", "first_action": "VerifythatthebackuptypeforthecorrespondingDBPaaS", - "full_action": "VerifythatthebackuptypeforthecorrespondingDBPaaS\nasset está supported e if não you must correct o backup type." + "full_action": "VerifythatthebackuptypeforthecorrespondingDBPaaS\nasset is supported and if not you must correct the backup type." }, "3843": { "code": 3843, - "desc": "Falhou to enable CDC.", - "first_action": "Verifique que o DBPaaS asset usuário has access to enable", - "full_action": "Verifique que o DBPaaS asset usuário has access to enable\nCDC e if não, o usuário needs access enabled to CDC para o DBPaaS asset." + "desc": "Failed to enable CDC.", + "first_action": "Verify that the DBPaaS asset user has access to enable", + "full_action": "Verify that the DBPaaS asset user has access to enable\nCDC and if not, the user needs access enabled to CDC for the DBPaaS asset." }, "3844": { "code": 3844, - "desc": "Falhou to disable CDC.", - "first_action": "Verifique que o DBPaaS asset usuário has access to disable", - "full_action": "Verifique que o DBPaaS asset usuário has access to disable\nCDC e if não, o usuário needs access to disable CDC para o DBPaaS asset." + "desc": "Failed to disable CDC.", + "first_action": "Verify that the DBPaaS asset user has access to disable", + "full_action": "Verify that the DBPaaS asset user has access to disable\nCDC and if not, the user needs access to disable CDC for the DBPaaS asset." }, "3845": { "code": 3845, - "desc": "O banco de dados servidor does não support Azure Managed Identity.", - "first_action": "Try o operation com banco de dados credentials.", - "full_action": "Try o operation com banco de dados credentials." + "desc": "The database server does not support Azure Managed Identity.", + "first_action": "Try the operation with database credentials.", + "full_action": "Try the operation with database credentials." }, "3846": { "code": 3846, - "desc": "Não é possível enable version 2 de o variable length deduplication algorithm.", + "desc": "Cannot enable version 2 of the variable length deduplication algorithm.", "first_action": "-imageId --segment vldv2 --sw_min 16 --sw_max 32", - "full_action": "Manually run o vpfs_actions comando on armazenamento\nservidor to enable vldv2 per o seguinte example:\n/usr/openv/pdde/vpfs/bin/vpfs_actions -um tune\n--imageId --segment vldv2 --sw_min 16 --sw_max 32" + "full_action": "Manually run the vpfs_actions command on storage\nserver to enable vldv2 per the following example:\n/usr/openv/pdde/vpfs/bin/vpfs_actions -a tune\n--imageId --segment vldv2 --sw_min 16 --sw_max 32" }, "3847": { "code": 3847, - "desc": "Não é possível create o S3 bucket because you do não have o requerido permissions.", - "first_action": "Add o permissão createbucket to o usuário que needs", - "full_action": "Add o permissão createbucket to o usuário que needs\nto create o S3 bucket." + "desc": "Cannot create the S3 bucket because you do not have the required permissions.", + "first_action": "Add the permission createbucket to the user that needs", + "full_action": "Add the permission createbucket to the user that needs\nto create the S3 bucket." }, "3849": { "code": 3849, - "desc": "Não é possível retrieve GCP Service object.", - "first_action": "Associate o appropriate permissions to o service", - "full_action": "Associate o appropriate permissions to o service\naccount que está used." + "desc": "Cannot retrieve GCP Service object.", + "first_action": "Associate the appropriate permissions to the service", + "full_action": "Associate the appropriate permissions to the service\naccount that is used." }, "3851": { "code": 3851, - "desc": "Não é possível complete o operation, another operation foi already in progress.", - "first_action": "Wait para o current job to complete e rerun o first job.", - "full_action": "Wait para o current job to complete e rerun o first job." + "desc": "Cannot complete the operation, another operation was already in progress.", + "first_action": "Wait for the current job to complete and rerun the first job.", + "full_action": "Wait for the current job to complete and rerun the first job." }, "3852": { "code": 3852, - "desc": "Não é possível clean up o DBPaaS instant access staging caminho.", + "desc": "Cannot clean up the DBPaaS instant access staging path.", "first_action": "EnsurethatavalidAWSElasticfilesystemismountedonthecorrespondingstaging", - "full_action": "Executar o seguinte como appropriate:\nEnsurethatavalidAWSElasticfilesystemismountedonthecorrespondingstaging\ncaminho." + "full_action": "Perform the following as appropriate:\nEnsurethatavalidAWSElasticfilesystemismountedonthecorrespondingstaging\npath." }, "3854": { "code": 3854, - "desc": "Não é possível executar o solicitado operation como o native cliente utility does não have o requerido permissions to run.", - "first_action": "Assign executable permissions to o service usuário on o", - "full_action": "Assign executable permissions to o service usuário on o\nmediaserverforallthird-partyutilitiesthatareusedforcredentialvalidation,backup,\ne restauração." + "desc": "Cannot perform the requested operation as the native client utility does not have the required permissions to run.", + "first_action": "Assign executable permissions to the service user on the", + "full_action": "Assign executable permissions to the service user on the\nmediaserverforallthird-partyutilitiesthatareusedforcredentialvalidation,backup,\nand restore." }, "3900": { "code": 3900, - "desc": "O page offset está inválido.", - "first_action": "Review o parameters from o External Credential", - "full_action": "Review o parameters from o External Credential\nManagement System provider e retry o operation." + "desc": "The page offset is invalid.", + "first_action": "Review the parameters from the External Credential", + "full_action": "Review the parameters from the External Credential\nManagement System provider and retry the operation." }, "3901": { "code": 3901, - "desc": "O External Credential Management System provider details foram não found com o supplied configuration name. NetBackup status codes 613 NetBackup status codes", - "first_action": "Create um configuration com o supplied configuration", - "full_action": "Create um configuration com o supplied configuration\nname through o NetBackup web UI in o Credential management." + "desc": "The External Credential Management System provider details were not found with the supplied configuration name. NetBackup status codes 613 NetBackup status codes", + "first_action": "Create a configuration with the supplied configuration", + "full_action": "Create a configuration with the supplied configuration\nname through the NetBackup web UI in the Credential management." }, "3902": { "code": 3902, - "desc": "O credential name does não exist.", - "first_action": "Create o requerido External Credential Management", - "full_action": "Create o requerido External Credential Management\nSystem servidor credentials before you configure ou update o External Credential\nManagement System servidor. If you get this erro when o external credentials estão\ncreated, retry o operation." + "desc": "The credential name does not exist.", + "first_action": "Create the required External Credential Management", + "full_action": "Create the required External Credential Management\nSystem server credentials before you configure or update the External Credential\nManagement System server. If you get this error when the external credentials are\ncreated, retry the operation." }, "3903": { "code": 3903, - "desc": "O External Credential Management System provider type está inválido.", - "first_action": "O apenas supported provider type está CyberArk.", - "full_action": "O apenas supported provider type está CyberArk." + "desc": "The External Credential Management System provider type is invalid.", + "first_action": "The only supported provider type is CyberArk.", + "full_action": "The only supported provider type is CyberArk." }, "3904": { "code": 3904, - "desc": "Conexão to o External Credential Management System servidor fails usando o provided credential name ou port number.", + "desc": "Connection to the External Credential Management System server fails using the provided credential name or port number.", "first_action": "Verifyifthehostname,port,certificates,orcredentialsare", "full_action": "Verifyifthehostname,port,certificates,orcredentialsare\nvalidsothattheconnectionwiththeExternalCredentialManagementSystemserver\ncan be established." }, "3905": { "code": 3905, - "desc": "Inválido credential response foi received from o external credential management system servidor.", + "desc": "Invalid credential response was received from the external credential management system server.", "first_action": "Ensurethatthecredentialsthatwere createdin CyberArk", - "full_action": "Ensurethatthecredentialsthatwere createdin CyberArk\nmaptothesupportedworkloadinNetBackup.Forexample,theMSSQLcredentials\nin CyberArk must apenas be used com Microsoft SQL assets in NetBackup." + "full_action": "Ensurethatthecredentialsthatwere createdin CyberArk\nmaptothesupportedworkloadinNetBackup.Forexample,theMSSQLcredentials\nin CyberArk must only be used with Microsoft SQL assets in NetBackup." }, "3906": { "code": 3906, - "desc": "DeletingtheselectedNamedcredentialisnotpossibleasitisassociated com o Configuration name de o External Credential Management System servidor. Excluir o associated entry first.", - "first_action": "O External Credential Management System servidor", - "full_action": "O External Credential Management System servidor\nconfiguration must be deleted first to excluir um named credential." + "desc": "DeletingtheselectedNamedcredentialisnotpossibleasitisassociated with the Configuration name of the External Credential Management System server. Delete the associated entry first.", + "first_action": "The External Credential Management System server", + "full_action": "The External Credential Management System server\nconfiguration must be deleted first to delete a named credential." }, "3907": { "code": 3907, - "desc": "Deleting o selected External Credential Management System servidor isnotpossibleasitisassociatedwiththeNamedcredentials.Deletetheassociated entry first.", - "first_action": "To excluir um External Credential Management System", - "full_action": "To excluir um External Credential Management System\nservidor, you must first excluir o Named credentials which use o External\nCredential Management System servidor." + "desc": "Deleting the selected External Credential Management System server isnotpossibleasitisassociatedwiththeNamedcredentials.Deletetheassociated entry first.", + "first_action": "To delete an External Credential Management System", + "full_action": "To delete an External Credential Management System\nserver, you must first delete the Named credentials which use the External\nCredential Management System server." }, "3908": { "code": 3908, - "desc": "O agent details de o External Credential Management System estão não found.", - "first_action": "Create new external credentials com o provided name", - "full_action": "Create new external credentials com o provided name\nou review o ID de o credentials you desejar to excluir." + "desc": "The agent details of the External Credential Management System are not found.", + "first_action": "Create new external credentials with the provided name", + "full_action": "Create new external credentials with the provided name\nor review the ID of the credentials you want to delete." }, "3909": { "code": 3909, - "desc": "TherequesttoupdatetheinformationofExternalCredentialManagement System provider está inválido.", + "desc": "TherequesttoupdatetheinformationofExternalCredentialManagement System provider is invalid.", "first_action": "ConfigName", - "full_action": "Garanta que o seguinte fields estão set com valid values:\n■ configName\n■ ecmsHostName\n■ credentialName" + "full_action": "Ensure that the following fields are set with valid values:\n■ configName\n■ ecmsHostName\n■ credentialName" }, "3910": { "code": 3910, - "desc": "Application ID está não defined.", - "first_action": "Garanta que o Application ID exists on o CyberArk", - "full_action": "Garanta que o Application ID exists on o CyberArk\nservidor.\nNote: Application ID - Specifies o unique ID de o application issuing o\npassword request." + "desc": "Application ID is not defined.", + "first_action": "Ensure that the Application ID exists on the CyberArk", + "full_action": "Ensure that the Application ID exists on the CyberArk\nserver.\nNote: Application ID - Specifies the unique ID of the application issuing the\npassword request." }, "3911": { "code": 3911, - "desc": "Object ou Safe name está não defined.", + "desc": "Object or Safe name is not defined.", "first_action": "EnsurethatObjectorSafeexistsontheCyberArkserver.", - "full_action": "EnsurethatObjectorSafeexistsontheCyberArkserver.\nNote: Object - Specifies o name de o password object to retrieve.\nSafe - Specifies o name de o safe onde o password está stored." + "full_action": "EnsurethatObjectorSafeexistsontheCyberArkserver.\nNote: Object - Specifies the name of the password object to retrieve.\nSafe - Specifies the name of the safe where the password is stored." }, "3912": { "code": 3912, - "desc": "O Common Name ou Subject Alternative Name de o certificate does não contain o host name de o servidor ou o certificate está inválido.", - "first_action": "You must garanta que o certificate que está deployed on", - "full_action": "You must garanta que o certificate que está deployed on\ntheECMSserverhasaCommonNameoraSubjectAlternativeNamethatmatches\no host name." + "desc": "The Common Name or Subject Alternative Name of the certificate does not contain the host name of the server or the certificate is invalid.", + "first_action": "You must ensure that the certificate that is deployed on", + "full_action": "You must ensure that the certificate that is deployed on\ntheECMSserverhasaCommonNameoraSubjectAlternativeNamethatmatches\nthe host name." }, "3913": { "code": 3913, - "desc": "O credential type está inválido.", - "first_action": "Make sure que o category de o credentials que estão", - "full_action": "Make sure que o category de o credentials que estão\nused when o EMCS servidor está configurado, estão o credentials para CyberArk." + "desc": "The credential type is invalid.", + "first_action": "Make sure that the category of the credentials that are", + "full_action": "Make sure that the category of the credentials that are\nused when the EMCS server is configured, are the credentials for CyberArk." }, "4000": { "code": 4000, - "desc": "Armazenamento web servidor login falhou.", - "first_action": "Verifique que o NBU Deduplication Armazenamento Server's", - "full_action": "Verifique que o NBU Deduplication Armazenamento Server's\ncredentials(storedintheNetBackupdatabase)arecurrentandvalidforthespecified\narmazenamento servidor. These credentials estão those que estão accessed from o Java GUI." + "desc": "Storage web server login failed.", + "first_action": "Verify that the NBU Deduplication Storage Server's", + "full_action": "Verify that the NBU Deduplication Storage Server's\ncredentials(storedintheNetBackupdatabase)arecurrentandvalidforthespecified\nstorage server. These credentials are those that are accessed from the Java GUI." }, "4001": { "code": 4001, - "desc": "Falhou to create o instant access mount.", - "first_action": "Verifique o NetBackup web service logs para o specific", - "full_action": "Verifique o NetBackup web service logs para o specific\ncause de o falha." + "desc": "Failed to create the instant access mount.", + "first_action": "Check the NetBackup web service logs for the specific", + "full_action": "Check the NetBackup web service logs for the specific\ncause of the failure." }, "4002": { "code": 4002, - "desc": "Falhou to fetch o instant access mount list.", - "first_action": "Verifique o NetBackup web service logs para o specific", - "full_action": "Verifique o NetBackup web service logs para o specific\ncause de o falha." + "desc": "Failed to fetch the instant access mount list.", + "first_action": "Check the NetBackup web service logs for the specific", + "full_action": "Check the NetBackup web service logs for the specific\ncause of the failure." }, "4003": { "code": 4003, - "desc": "Falhou to fetch o instant access mount details.", - "first_action": "Verifique o NetBackup web service logs para o specific", - "full_action": "Verifique o NetBackup web service logs para o specific\ncause de o falha." + "desc": "Failed to fetch the instant access mount details.", + "first_action": "Check the NetBackup web service logs for the specific", + "full_action": "Check the NetBackup web service logs for the specific\ncause of the failure." }, "4004": { "code": 4004, - "desc": "Falhou to create um instant access virtual machine (VM).", - "first_action": "Verifique que o rede configuration está correct e o NFS port está opened in", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Verifique que o rede configuration está correct e o NFS port está opened in\no firewall settings. If IPv6 está enabled in o ESXi host, also verifique o IPv6\nconnectivity between o ESXi host e o armazenamento servidor.\n■ Verifique que o VM name does não conflict com qualquer existing VM in o ESXi\nhost/cluster.\n■ Verifique o VMWare usuário privileges to garanta que o usuário está allowed to create\no VM on o vCenter/ESXi host." + "desc": "Failed to create an instant access virtual machine (VM).", + "first_action": "Verify that the network configuration is correct and the NFS port is opened in", + "full_action": "Do the following, as appropriate:\n■ Verify that the network configuration is correct and the NFS port is opened in\nthe firewall settings. If IPv6 is enabled in the ESXi host, also verify the IPv6\nconnectivity between the ESXi host and the storage server.\n■ Verify that the VM name does not conflict with any existing VM in the ESXi\nhost/cluster.\n■ Check the VMWare user privileges to ensure that the user is allowed to create\nthe VM on the vCenter/ESXi host." }, "4005": { "code": 4005, - "desc": "Um backup image from um unsupported policy type foi specified. Apenas PureDisk está supported.", + "desc": "A backup image from an unsupported policy type was specified. Only PureDisk is supported.", "first_action": "TheInstantAccessfeatureisonlysupportedontheMSDP", - "full_action": "TheInstantAccessfeatureisonlysupportedontheMSDP\narmazenamento servidor, so garanta que o correct armazenamento servidor está selected in o policy." + "full_action": "TheInstantAccessfeatureisonlysupportedontheMSDP\nstorage server, so ensure that the correct storage server is selected in the policy." }, "4006": { "code": 4006, - "desc": "Um backup image from um unsupported policy type foi specified. Apenas o VMware policy type está supported.", - "first_action": "O Instant Access recurso está apenas supported on o", - "full_action": "O Instant Access recurso está apenas supported on o\nVMware workload, so garanta que o correct policy type está selected." + "desc": "A backup image from an unsupported policy type was specified. Only the VMware policy type is supported.", + "first_action": "The Instant Access feature is only supported on the", + "full_action": "The Instant Access feature is only supported on the\nVMware workload, so ensure that the correct policy type is selected." }, "4007": { "code": 4007, - "desc": "Falhou to fetch o armazenamento servidor name.", - "first_action": "Verifique o NetBackup web service logs para o specific", - "full_action": "Verifique o NetBackup web service logs para o specific\ncause de o falha." + "desc": "Failed to fetch the storage server name.", + "first_action": "Check the NetBackup web service logs for the specific", + "full_action": "Check the NetBackup web service logs for the specific\ncause of the failure." }, "4008": { "code": 4008, - "desc": "Unexpected response from o armazenamento web servidor.", - "first_action": "Verifique o armazenamento web service logs on o appliance para", - "full_action": "Verifique o armazenamento web service logs on o appliance para\no specific reason de o falha." + "desc": "Unexpected response from the storage web server.", + "first_action": "Check the storage web service logs on the appliance for", + "full_action": "Check the storage web service logs on the appliance for\nthe specific reason of the failure." }, "4011": { "code": 4011, - "desc": "Falhou to restauração um single arquivo to o specified virtual machine (VM).", - "first_action": "Verifique o NetBackup web service logs para o specific", - "full_action": "Verifique o NetBackup web service logs para o specific\ncause de o falha." + "desc": "Failed to restore a single file to the specified virtual machine (VM).", + "first_action": "Check the NetBackup web service logs for the specific", + "full_action": "Check the NetBackup web service logs for the specific\ncause of the failure." }, "4012": { "code": 4012, - "desc": "Falhou to list instant access mount diretório.", - "first_action": "Verifique o NetBackup web service logs para o specific", - "full_action": "Verifique o NetBackup web service logs para o specific\ncause de o falha." + "desc": "Failed to list instant access mount directory.", + "first_action": "Check the NetBackup web service logs for the specific", + "full_action": "Check the NetBackup web service logs for the specific\ncause of the failure." }, "4013": { "code": 4013, - "desc": "Falhou to excluir o instant access mount.", - "first_action": "Verifique o NetBackup web service logs para o specific", - "full_action": "Verifique o NetBackup web service logs para o specific\ncause de o falha." + "desc": "Failed to delete the instant access mount.", + "first_action": "Check the NetBackup web service logs for the specific", + "full_action": "Check the NetBackup web service logs for the specific\ncause of the failure." }, "4014": { "code": 4014, - "desc": "Inválido instant access mount ID.", - "first_action": "Verifique o NetBackup web service logs para o specific", - "full_action": "Verifique o NetBackup web service logs para o specific\ncause de o falha." + "desc": "Invalid instant access mount ID.", + "first_action": "Check the NetBackup web service logs for the specific", + "full_action": "Check the NetBackup web service logs for the specific\ncause of the failure." }, "4015": { "code": 4015, - "desc": "Instant access mount está não yet ready. Try again later.", - "first_action": "Um VM que está being created não é possível be deleted. Wait um few", - "full_action": "Um VM que está being created não é possível be deleted. Wait um few\nminutes para o VM creation process to complete e then try again." + "desc": "Instant access mount is not yet ready. Try again later.", + "first_action": "A VM that is being created cannot be deleted. Wait a few", + "full_action": "A VM that is being created cannot be deleted. Wait a few\nminutes for the VM creation process to complete and then try again." }, "4016": { "code": 4016, - "desc": "Falhou to get o download URL from o instant access mount.", - "first_action": "Garanta que o download arquivo exists; um arquivo que does não exist não é possível be", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Garanta que o download arquivo exists; um arquivo que does não exist não é possível be\ndownloaded.\n■ Verifique que o download usuário has enough access permissão to download o\narquivo.\n■ Verifique que o rede conexão between o browser e o mídia servidor\nestá working." + "desc": "Failed to get the download URL from the instant access mount.", + "first_action": "Ensure that the download file exists; a file that does not exist cannot be", + "full_action": "Do the following, as appropriate:\n■ Ensure that the download file exists; a file that does not exist cannot be\ndownloaded.\n■ Verify that the download user has enough access permission to download the\nfile.\n■ Verify that the network connection between the browser and the media server\nis working." }, "4017": { "code": 4017, - "desc": "Falhou to get RSA public keys from o armazenamento web servidor.", - "first_action": "Garanta que seu servidor está executando properly.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Garanta que seu servidor está executando properly.\n■ Garanta que seu certificate está valid.\n■ Garanta que there está não um host name mismatch in o certificate.\nIf o public key está still unavailable, por favor verifique o web servidor logs." + "desc": "Failed to get RSA public keys from the storage web server.", + "first_action": "Ensure that your server is running properly.", + "full_action": "Do the following, as appropriate:\n■ Ensure that your server is running properly.\n■ Ensure that your certificate is valid.\n■ Ensure that there is not a host name mismatch in the certificate.\nIf the public key is still unavailable, please check the web server logs." }, "4019": { "code": 4019, - "desc": "Falhou to fetch o armazenamento servidor credentials.", + "desc": "Failed to fetch the storage server credentials.", "first_action": "VerifythattheNetBackupWebManagementConsolecan", - "full_action": "VerifythattheNetBackupWebManagementConsolecan\nler o armazenamento servidor credentials." + "full_action": "VerifythattheNetBackupWebManagementConsolecan\nread the storage server credentials." }, "4020": { "code": 4020, - "desc": "Falhou to fetch VMware servidor credentials", + "desc": "Failed to fetch VMware server credentials", "first_action": "VerifythattheNetBackupWebManagementConsolecan", - "full_action": "VerifythattheNetBackupWebManagementConsolecan\nler o VMware servidor credentials." + "full_action": "VerifythattheNetBackupWebManagementConsolecan\nread the VMware server credentials." }, "4021": { "code": 4021, - "desc": "Inválido arquivo caminho specified.", - "first_action": "Verifique que o download arquivo exists; um arquivo não é possível be downloaded if it does não", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Verifique que o download arquivo exists; um arquivo não é possível be downloaded if it does não\nexist.\n■ Verifique que o download usuário has enough access permissão to download o\narquivo." + "desc": "Invalid file path specified.", + "first_action": "Check that the download file exists; a file cannot be downloaded if it does not", + "full_action": "Do the following, as appropriate:\n■ Check that the download file exists; a file cannot be downloaded if it does not\nexist.\n■ Verify that the download user has enough access permission to download the\nfile." }, "4022": { "code": 4022, - "desc": "Inválido virtual machine (VM) username/password.", - "first_action": "Specify um username e um password.", - "full_action": "Specify um username e um password." + "desc": "Invalid virtual machine (VM) username/password.", + "first_action": "Specify a username and a password.", + "full_action": "Specify a username and a password." }, "4023": { "code": 4023, - "desc": "Oneoftherequiredparameters(BIOSUUID,instanceUUID,VMname) está inválido.", - "first_action": "Specify o requerido parameters (BIOS UUID, instance", - "full_action": "Specify o requerido parameters (BIOS UUID, instance\nUUID, e VM name)." + "desc": "Oneoftherequiredparameters(BIOSUUID,instanceUUID,VMname) is invalid.", + "first_action": "Specify the required parameters (BIOS UUID, instance", + "full_action": "Specify the required parameters (BIOS UUID, instance\nUUID, and VM name)." }, "4024": { "code": 4024, - "desc": "Inválido virtual machine (VM) name specified.", - "first_action": "When you create um VM, you must specify um name que está", - "full_action": "When you create um VM, you must specify um name que está\nnão blank e que está não longer than 80 characters." + "desc": "Invalid virtual machine (VM) name specified.", + "first_action": "When you create a VM, you must specify a name that is", + "full_action": "When you create a VM, you must specify a name that is\nnot blank and that is not longer than 80 characters." }, "4025": { "code": 4025, - "desc": "Falhou to fetch image details.", - "first_action": "Verifique o NetBackup web service logs para o specific", - "full_action": "Verifique o NetBackup web service logs para o specific\ncause de o falha." + "desc": "Failed to fetch image details.", + "first_action": "Check the NetBackup web service logs for the specific", + "full_action": "Check the NetBackup web service logs for the specific\ncause of the failure." }, "4026": { "code": 4026, - "desc": "Backup image does não support instant access.", - "first_action": "Back up o image to supported armazenamento: Mídia Servidor", - "full_action": "Back up o image to supported armazenamento: Mídia Servidor\nDeduplication Pool (MSDP)." + "desc": "Backup image does not support instant access.", + "first_action": "Back up the image to supported storage: Media Server", + "full_action": "Back up the image to supported storage: Media Server\nDeduplication Pool (MSDP)." }, "4027": { "code": 4027, - "desc": "Falhou to create o instant access mount.", - "first_action": "Reduce o number de instant access mounts e try o", - "full_action": "Reduce o number de instant access mounts e try o\noperation again." + "desc": "Failed to create the instant access mount.", + "first_action": "Reduce the number of instant access mounts and try the", + "full_action": "Reduce the number of instant access mounts and try the\noperation again." }, "4028": { "code": 4028, - "desc": "Falhou to reload Mídia Servidor Deduplication Pool metadata.", - "first_action": "Review o NetBackup Web Service logs para o specific", - "full_action": "Review o NetBackup Web Service logs para o specific\ncause de o falha." + "desc": "Failed to reload Media Server Deduplication Pool metadata.", + "first_action": "Review the NetBackup Web Service logs for the specific", + "full_action": "Review the NetBackup Web Service logs for the specific\ncause of the failure." }, "4029": { "code": 4029, - "desc": "Falhou to get images from Amazon S3.", - "first_action": "Review o NetBackup Web Service logs para o specific", - "full_action": "Review o NetBackup Web Service logs para o specific\ncause de o falha." + "desc": "Failed to get images from Amazon S3.", + "first_action": "Review the NetBackup Web Service logs for the specific", + "full_action": "Review the NetBackup Web Service logs for the specific\ncause of the failure." }, "4030": { "code": 4030, - "desc": "Internal API call falhou.", - "first_action": "Review o NetBackup Web Service logs para o specific", - "full_action": "Review o NetBackup Web Service logs para o specific\ncause de o falha." + "desc": "Internal API call failed.", + "first_action": "Review the NetBackup Web Service logs for the specific", + "full_action": "Review the NetBackup Web Service logs for the specific\ncause of the failure." }, "4031": { "code": 4031, - "desc": "Internal API call to o catalog falhou.", - "first_action": "Review o NetBackup Web Service logs para o specific", - "full_action": "Review o NetBackup Web Service logs para o specific\ncause de o falha." + "desc": "Internal API call to the catalog failed.", + "first_action": "Review the NetBackup Web Service logs for the specific", + "full_action": "Review the NetBackup Web Service logs for the specific\ncause of the failure." }, "4032": { "code": 4032, - "desc": "Falhou to get version from o Armazenamento Platform Web Service (SPWS). Garanta que NGINX está executando e configurado correctly on o selected MSDP armazenamento servidor.", + "desc": "Failed to get version from the Storage Platform Web Service (SPWS). Ensure that NGINX is running and configured correctly on the selected MSDP storage server.", "first_action": "FortheNetBackupAppliance,reviewtheNetBackupWeb", - "full_action": "FortheNetBackupAppliance,reviewtheNetBackupWeb\nService logs para o specific cause de o falha. Para um NetBackup build-your-own\narmazenamento servidor, por favor verifique que NGINX está instalado e executando. Depending on\nworkload, refer to NetBackup para VMware Administrator’s Guide ou o NetBackup\nforMicrosoftSQLServerAdministrator’sGuidefordetailedinstructionaboutInstant\nAccess." + "full_action": "FortheNetBackupAppliance,reviewtheNetBackupWeb\nService logs for the specific cause of the failure. For a NetBackup build-your-own\nstorage server, please verify that NGINX is installed and running. Depending on\nworkload, refer to NetBackup for VMware Administrator’s Guide or the NetBackup\nforMicrosoftSQLServerAdministrator’sGuidefordetailedinstructionaboutInstant\nAccess." }, "4033": { "code": 4033, - "desc": "Verification de o JSON Web Token signature falhou.", - "first_action": "Review o NetBackup Web Service logs para o specific", - "full_action": "Review o NetBackup Web Service logs para o specific\ncause de o falha." + "desc": "Verification of the JSON Web Token signature failed.", + "first_action": "Review the NetBackup Web Service logs for the specific", + "full_action": "Review the NetBackup Web Service logs for the specific\ncause of the failure." }, "4034": { "code": 4034, - "desc": "Falhou to create um NetBackup job para o instant access operation.", - "first_action": "Review o NetBackup Web Service logs para o specific", - "full_action": "Review o NetBackup Web Service logs para o specific\ncause de o falha." + "desc": "Failed to create a NetBackup job for the instant access operation.", + "first_action": "Review the NetBackup Web Service logs for the specific", + "full_action": "Review the NetBackup Web Service logs for the specific\ncause of the failure." }, "4035": { "code": 4035, - "desc": "Falhou to update o NetBackup job para o instant access operation.", - "first_action": "Review o NetBackup Web Service logs para o specific", - "full_action": "Review o NetBackup Web Service logs para o specific\ncause de o falha." + "desc": "Failed to update the NetBackup job for the instant access operation.", + "first_action": "Review the NetBackup Web Service logs for the specific", + "full_action": "Review the NetBackup Web Service logs for the specific\ncause of the failure." }, "4036": { "code": 4036, - "desc": "Falhou to fetch o NetBackup instant access job details. NetBackup status codes 626 NetBackup status codes", - "first_action": "Review o NetBackup Web Service logs para o specific", - "full_action": "Review o NetBackup Web Service logs para o specific\ncause de o falha." + "desc": "Failed to fetch the NetBackup instant access job details. NetBackup status codes 626 NetBackup status codes", + "first_action": "Review the NetBackup Web Service logs for the specific", + "full_action": "Review the NetBackup Web Service logs for the specific\ncause of the failure." }, "4037": { "code": 4037, - "desc": "Falhou to excluir um instant access virtual machine (VM).", - "first_action": "Review o NetBackup Web Service logs para o specific", - "full_action": "Review o NetBackup Web Service logs para o specific\ncause de o falha." + "desc": "Failed to delete an instant access virtual machine (VM).", + "first_action": "Review the NetBackup Web Service logs for the specific", + "full_action": "Review the NetBackup Web Service logs for the specific\ncause of the failure." }, "4038": { "code": 4038, - "desc": "Falhou to get o instant access folder attributes.", - "first_action": "Review o NetBackup Web Service logs para o specific", - "full_action": "Review o NetBackup Web Service logs para o specific\ncause de o falha." + "desc": "Failed to get the instant access folder attributes.", + "first_action": "Review the NetBackup Web Service logs for the specific", + "full_action": "Review the NetBackup Web Service logs for the specific\ncause of the failure." }, "4039": { "code": 4039, - "desc": "O requerido parâmetro caminho está inválido.", - "first_action": "Correct o caminho parâmetro e try o operation again.", - "full_action": "Correct o caminho parâmetro e try o operation again." + "desc": "The required parameter path is invalid.", + "first_action": "Correct the path parameter and try the operation again.", + "full_action": "Correct the path parameter and try the operation again." }, "4040": { "code": 4040, - "desc": "O armazenamento servidor has um earlier version de NetBackup.", + "desc": "The storage server has an earlier version of NetBackup.", "first_action": "UpgradethestorageservertothelatestNetBackupversion.", "full_action": "UpgradethestorageservertothelatestNetBackupversion." }, "4041": { "code": 4041, - "desc": "Falhou to create o universal share.", - "first_action": "Review o NetBackup Web Service logs para o specific", - "full_action": "Review o NetBackup Web Service logs para o specific\ncause de o falha." + "desc": "Failed to create the universal share.", + "first_action": "Review the NetBackup Web Service logs for the specific", + "full_action": "Review the NetBackup Web Service logs for the specific\ncause of the failure." }, "4042": { "code": 4042, - "desc": "Falhou to fetch o instant access universal share details.", - "first_action": "Review o NetBackup Web Service logs para o specific", - "full_action": "Review o NetBackup Web Service logs para o specific\ncause de o falha." + "desc": "Failed to fetch the instant access universal share details.", + "first_action": "Review the NetBackup Web Service logs for the specific", + "full_action": "Review the NetBackup Web Service logs for the specific\ncause of the failure." }, "4043": { "code": 4043, - "desc": "Falhou to fetch o instant access universal share list.", - "first_action": "Review o NetBackup Web Service logs para o specific", - "full_action": "Review o NetBackup Web Service logs para o specific\ncause de o falha." + "desc": "Failed to fetch the instant access universal share list.", + "first_action": "Review the NetBackup Web Service logs for the specific", + "full_action": "Review the NetBackup Web Service logs for the specific\ncause of the failure." }, "4044": { "code": 4044, - "desc": "Falhou to excluir o instant access universal share.", - "first_action": "Review o NetBackup Web Service logs para o specific", - "full_action": "Review o NetBackup Web Service logs para o specific\ncause de o falha." + "desc": "Failed to delete the instant access universal share.", + "first_action": "Review the NetBackup Web Service logs for the specific", + "full_action": "Review the NetBackup Web Service logs for the specific\ncause of the failure." }, "4045": { "code": 4045, - "desc": "Universal share capability está não supported.", - "first_action": "Review o NetBackup Web Service logs para o specific", - "full_action": "Review o NetBackup Web Service logs para o specific\ncause de o falha." + "desc": "Universal share capability is not supported.", + "first_action": "Review the NetBackup Web Service logs for the specific", + "full_action": "Review the NetBackup Web Service logs for the specific\ncause of the failure." }, "4046": { "code": 4046, - "desc": "Falhou to fetch asset informação.", - "first_action": "Review o NetBackup Web Service logs para o specific", - "full_action": "Review o NetBackup Web Service logs para o specific\ncause de o falha." + "desc": "Failed to fetch asset information.", + "first_action": "Review the NetBackup Web Service logs for the specific", + "full_action": "Review the NetBackup Web Service logs for the specific\ncause of the failure." }, "4047": { "code": 4047, - "desc": "Falhou to ping Armazenamento Platform Web Service.", - "first_action": "Review o NetBackup Web Service logs para o specific", - "full_action": "Review o NetBackup Web Service logs para o specific\ncause de o falha." + "desc": "Failed to ping Storage Platform Web Service.", + "first_action": "Review the NetBackup Web Service logs for the specific", + "full_action": "Review the NetBackup Web Service logs for the specific\ncause of the failure." }, "4048": { "code": 4048, - "desc": "Falhou to create o instant sync VM.", - "first_action": "Review o NetBackup Web Service logs para o specific", - "full_action": "Review o NetBackup Web Service logs para o specific\ncause de o falha." + "desc": "Failed to create the instant sync VM.", + "first_action": "Review the NetBackup Web Service logs for the specific", + "full_action": "Review the NetBackup Web Service logs for the specific\ncause of the failure." }, "4049": { "code": 4049, - "desc": "Falhou to fetch instant sync VM details.", - "first_action": "Review o NetBackup Web Service logs para o specific", - "full_action": "Review o NetBackup Web Service logs para o specific\ncause de o falha." + "desc": "Failed to fetch instant sync VM details.", + "first_action": "Review the NetBackup Web Service logs for the specific", + "full_action": "Review the NetBackup Web Service logs for the specific\ncause of the failure." }, "4050": { "code": 4050, - "desc": "Falhou to configure instant access.", - "first_action": "Review o NetBackup Web Service logs para o specific", - "full_action": "Review o NetBackup Web Service logs para o specific\ncause de o falha." + "desc": "Failed to configure instant access.", + "first_action": "Review the NetBackup Web Service logs for the specific", + "full_action": "Review the NetBackup Web Service logs for the specific\ncause of the failure." }, "4200": { "code": 4200, - "desc": "Operation falhou: Não foi possível to acquire snapshot lock", - "first_action": "Retry o operation when o snapshot está não longer used", - "full_action": "Retry o operation when o snapshot está não longer used\npor another operation." + "desc": "Operation failed: Unable to acquire snapshot lock", + "first_action": "Retry the operation when the snapshot is no longer used", + "full_action": "Retry the operation when the snapshot is no longer used\nby another operation." }, "4201": { "code": 4201, - "desc": "Incorrect snapshot method configuration ou snapshot method não compatible para protecting backup selection entradas", + "desc": "Incorrect snapshot method configuration or snapshot method not compatible for protecting backup selection entries", "first_action": "Therequiredcorrectstoragearraycredentialforthesnapshotmethod(wherever", - "full_action": "Verifique o seguinte:\n■ Therequiredcorrectstoragearraycredentialforthesnapshotmethod(wherever\napplicable) está configurado in NetBackup.\n■ O requerido software para o snapshot method está configurado correctly on o\ncliente.\n■ You can choose o snapshot method to protect o entradas de o backup\nselection (para example, arquivo system).\n■ O entradas que estão specified in o backup selection estão compatible com o\nsnapshot method configurado in o policy.\nVeja o NetBackup Snapshot Cliente Administration Guide para more informação\nabout configuring um snapshot method." + "full_action": "Verify the following:\n■ Therequiredcorrectstoragearraycredentialforthesnapshotmethod(wherever\napplicable) is configured in NetBackup.\n■ The required software for the snapshot method is configured correctly on the\nclient.\n■ You can choose the snapshot method to protect the entries of the backup\nselection (for example, file system).\n■ The entries that are specified in the backup selection are compatible with the\nsnapshot method configured in the policy.\nSee the NetBackup Snapshot Client Administration Guide for more information\nabout configuring a snapshot method." }, "4202": { "code": 4202, - "desc": "Inválido ou incompatible armazenamento unidade configurado", - "first_action": "O armazenamento destination que está used para o policy está compatible. Para example,", - "full_action": "Verifique o seguinte:\n■ O armazenamento destination que está used para o policy está compatible. Para example,\no snapshot method OST_FIM operates apenas on um SLP configurado como armazenamento\ndestination.\n■ O configuration parâmetro que foi provided para o snapshot method está\ncorrect. Para example, verifique que o snapshot resources estão correct e o\nconfiguration parameters para o configurado snapshot method estão correct.\n■ You can choose o snapshot method to protect o entradas de o backup\nselection (para example, arquivo system).\nVeja o NetBackup Snapshot Cliente Administration Guide para more informação\nabout configuring um snapshot method." + "desc": "Invalid or incompatible storage unit configured", + "first_action": "The storage destination that is used for the policy is compatible. For example,", + "full_action": "Verify the following:\n■ The storage destination that is used for the policy is compatible. For example,\nthe snapshot method OST_FIM operates only on an SLP configured as storage\ndestination.\n■ The configuration parameter that was provided for the snapshot method is\ncorrect. For example, verify that the snapshot resources are correct and the\nconfiguration parameters for the configured snapshot method are correct.\n■ You can choose the snapshot method to protect the entries of the backup\nselection (for example, file system).\nSee the NetBackup Snapshot Client Administration Guide for more information\nabout configuring a snapshot method." }, "4203": { "code": 4203, - "desc": "Inválido ou unsupported backup selection filelist", - "first_action": "O entradas que estão given in o backup selection can be protected por o", - "full_action": "Verifique o seguinte:\n■ O entradas que estão given in o backup selection can be protected por o\nsnapshot method. Para example, um arquivo system que foi created on top de um HP\nEVA disco não é possível be protected usando o snapshot method para IBM.\n■ O volume está mounted on o specified caminho para NAS volumes (NFS mount\npoints ou CIFS share)." + "desc": "Invalid or unsupported backup selection filelist", + "first_action": "The entries that are given in the backup selection can be protected by the", + "full_action": "Verify the following:\n■ The entries that are given in the backup selection can be protected by the\nsnapshot method. For example, a file system that was created on top of an HP\nEVA disk cannot be protected using the snapshot method for IBM.\n■ The volume is mounted on the specified path for NAS volumes (NFS mount\npoints or CIFS share)." }, "4204": { "code": 4204, - "desc": "Incompatible cliente found", + "desc": "Incompatible client found", "first_action": "Youhaveloggedintotheclientwiththesamedomain-userastheoneregistered", - "full_action": "Verifique o seguinte:\n■ Youhaveloggedintotheclientwiththesamedomain-userastheoneregistered\ncom o NetBackup cliente service.\n■ O primary cliente e target ou remote cliente estão compatible." + "full_action": "Verify the following:\n■ Youhaveloggedintotheclientwiththesamedomain-userastheoneregistered\nwith the NetBackup client service.\n■ The primary client and target or remote client are compatible." }, "4205": { "code": 4205, - "desc": "Incorrect ou não credentials found", - "first_action": "If you created um NDMP policy ou configurado um NAS Data Mover, verifique que", - "full_action": "Verifique o seguinte:\n■ If you created um NDMP policy ou configurado um NAS Data Mover, verifique que\no NDMP host está configurado com o correct credentials.\n■ O disco array host ou armazenamento servidor credentials estão correct.\n■ Thethirdpartysoftwareorsupportingsoftwarethatisrequiredbytheconfigured\nsnapshot method está instalado on o cliente.\nVeja o NetBackup Snapshot Cliente Administration Guide para more informação\nabout snapshot methods." + "desc": "Incorrect or no credentials found", + "first_action": "If you created an NDMP policy or configured an NAS Data Mover, check that", + "full_action": "Verify the following:\n■ If you created an NDMP policy or configured an NAS Data Mover, check that\nthe NDMP host is configured with the correct credentials.\n■ The disk array host or storage server credentials are correct.\n■ Thethirdpartysoftwareorsupportingsoftwarethatisrequiredbytheconfigured\nsnapshot method is installed on the client.\nSee the NetBackup Snapshot Client Administration Guide for more information\nabout snapshot methods." }, "4206": { "code": 4206, - "desc": "Authentication erro ocorreu. NetBackup Cliente Service está executando como Local System, this está likely incorrect. NetBackup status codes 632 NetBackup status codes", - "first_action": "Update o NetBackup Cliente Service in o Windows", - "full_action": "Update o NetBackup Cliente Service in o Windows\nservices to use o proper credentials que allow access to o armazenamento servidor." + "desc": "Authentication error occurred. NetBackup Client Service is running as Local System, this is likely incorrect. NetBackup status codes 632 NetBackup status codes", + "first_action": "Update the NetBackup Client Service in the Windows", + "full_action": "Update the NetBackup Client Service in the Windows\nservices to use the proper credentials that allow access to the storage server." }, "4207": { "code": 4207, - "desc": "Could não fetch snapshot metadata ou state arquivos", - "first_action": "O NetBackup cliente can communicate com o NetBackup master.", - "full_action": "Verifique o seguinte:\n■ O NetBackup cliente can communicate com o NetBackup master.\n■ O state arquivo location on o NetBackup cliente has gravar permissão. O typical\nlocation de o NetBackup state arquivo on o NetBackup cliente está como follows:\nWindows: C:\\Program Files\\Veritas\\NetBackup\\online_util\\fi_cntl\\\nUNIX: /usr/openv/netbackup/online_util/fi_cntl" + "desc": "Could not fetch snapshot metadata or state files", + "first_action": "The NetBackup client can communicate with the NetBackup master.", + "full_action": "Verify the following:\n■ The NetBackup client can communicate with the NetBackup master.\n■ The state file location on the NetBackup client has write permission. The typical\nlocation of the NetBackup state file on the NetBackup client is as follows:\nWindows: C:\\Program Files\\Veritas\\NetBackup\\online_util\\fi_cntl\\\nUNIX: /usr/openv/netbackup/online_util/fi_cntl" }, "4208": { "code": 4208, - "desc": "Could não send snapshot metadata ou statefiles", - "first_action": "O NetBackup cliente can communicate com o NetBackup master.", - "full_action": "Verifique o seguinte:\n■ O NetBackup cliente can communicate com o NetBackup master.\n■ O state arquivo location on o NetBackup cliente has gravar permissão. O typical\nlocation de o NetBackup state arquivo on o NetBackup cliente está como follows:\nWindows: C:\\Program Files\\Veritas\\NetBackup\\db\\snapshot\\\nUNIX: /usr/openv/netbackup/db/snapshot/" + "desc": "Could not send snapshot metadata or statefiles", + "first_action": "The NetBackup client can communicate with the NetBackup master.", + "full_action": "Verify the following:\n■ The NetBackup client can communicate with the NetBackup master.\n■ The state file location on the NetBackup client has write permission. The typical\nlocation of the NetBackup state file on the NetBackup client is as follows:\nWindows: C:\\Program Files\\Veritas\\NetBackup\\db\\snapshot\\\nUNIX: /usr/openv/netbackup/db/snapshot/" }, "4209": { "code": 4209, - "desc": "Snapshot metadata ou statefiles não é possível be created", - "first_action": "O logs contain um falha que precedes this erro which restricts o creation", - "full_action": "Verifique o seguinte:\n■ O logs contain um falha que precedes this erro which restricts o creation\nde metadata content.\n■ O state arquivo location on o NetBackup cliente has gravar permissão. O typical\nlocation de o NetBackup state arquivo on o NetBackup cliente está como follows:\nWindows: C:\\Program Files\\Veritas\\NetBackup\\db\\snapshot\\\nUNIX: /usr/openv/netbackup/db/snapshot/" + "desc": "Snapshot metadata or statefiles cannot be created", + "first_action": "The logs contain a failure that precedes this error which restricts the creation", + "full_action": "Verify the following:\n■ The logs contain a failure that precedes this error which restricts the creation\nof metadata content.\n■ The state file location on the NetBackup client has write permission. The typical\nlocation of the NetBackup state file on the NetBackup client is as follows:\nWindows: C:\\Program Files\\Veritas\\NetBackup\\db\\snapshot\\\nUNIX: /usr/openv/netbackup/db/snapshot/" }, "4210": { "code": 4210, - "desc": "Incorrect ou não content found in snapshot metadata", + "desc": "Incorrect or no content found in snapshot metadata", "first_action": "Windows: C:\\Program Files\\Veritas\\NetBackup\\online_util\\fi_cntl\\", - "full_action": "Verifique que o specified state arquivo está present on o host.\nO NetBackup state arquivo está normally located in o seguinte NetBackup cliente\ndiretório:\n■ Windows: C:\\Program Files\\Veritas\\NetBackup\\online_util\\fi_cntl\\\n■ UNIX: /usr/openv/netbackup/online_util/fi_cntl\nContate Cohesity NetBackup support para assistance." + "full_action": "Verify that the specified state file is present on the host.\nThe NetBackup state file is normally located in the following NetBackup client\ndirectory:\n■ Windows: C:\\Program Files\\Veritas\\NetBackup\\online_util\\fi_cntl\\\n■ UNIX: /usr/openv/netbackup/online_util/fi_cntl\nContact Cohesity NetBackup support for assistance." }, "4211": { "code": 4211, - "desc": "Snapshot não accessible ou inválido snapshot", - "first_action": "O conexão between o NetBackup cliente e o armazenamento management", - "full_action": "Verifique o seguinte:\n■ O conexão between o NetBackup cliente e o armazenamento management\nhost-array está intact.\n■ O host-specific permissão está enabled on o armazenamento array.\n■ O snapshot exists on o armazenamento array ou filer.\n■ O snapshot target dispositivo está não mapped to multiple HBAs. If it está, unmap one\nde o HBAs e continue. Support de multiple paths para um dispositivo que requires\no multi-path software." + "desc": "Snapshot not accessible or invalid snapshot", + "first_action": "The connection between the NetBackup client and the storage management", + "full_action": "Verify the following:\n■ The connection between the NetBackup client and the storage management\nhost-array is intact.\n■ The host-specific permission is enabled on the storage array.\n■ The snapshot exists on the storage array or filer.\n■ The snapshot target device is not mapped to multiple HBAs. If it is, unmap one\nof the HBAs and continue. Support of multiple paths for a device that requires\nthe multi-path software." }, "4212": { "code": 4212, - "desc": "Recreation de snapshot falhou", - "first_action": "Verifique que o restauração flow de operations has succeeded.", - "full_action": "Verifique que o restauração flow de operations has succeeded." + "desc": "Recreation of snapshot failed", + "first_action": "Verify that the restore flow of operations has succeeded.", + "full_action": "Verify that the restore flow of operations has succeeded." }, "4213": { "code": 4213, - "desc": "Snapshot import falhou", - "first_action": "O snapshot dispositivo está accessible on o cliente.", - "full_action": "Verifique o seguinte:\n■ O snapshot dispositivo está accessible on o cliente.\n■ O cliente has todos o requerido software para building o snapshot I/O stack. This\nshould be equivalent to o I/O stack de o primary cliente whose entity foi\nrequerido to be protected.\n■ O communication between o NetBackup cliente e o master servidor está\nintact.\n■ O copy-back restauração target dispositivo está não mapped to multiple HBAs. If it está,\nunmap one de o HBAs e continue. Support de multiple paths para um dispositivo\nrequires o multi-path software.\n■ Make sure que o iSCSI session está established between o node e o\ntarget." + "desc": "Snapshot import failed", + "first_action": "The snapshot device is accessible on the client.", + "full_action": "Verify the following:\n■ The snapshot device is accessible on the client.\n■ The client has all the required software for building the snapshot I/O stack. This\nshould be equivalent to the I/O stack of the primary client whose entity was\nrequired to be protected.\n■ The communication between the NetBackup client and the master server is\nintact.\n■ The copy-back restore target device is not mapped to multiple HBAs. If it is,\nunmap one of the HBAs and continue. Support of multiple paths for a device\nrequires the multi-path software.\n■ Make sure that the iSCSI session is established between the node and the\ntarget." }, "4214": { "code": 4214, - "desc": "Snapshot mount falhou", - "first_action": "You can use o requerido arquivo system type to mount o given snapshot.", - "full_action": "Verifique o seguinte:\n■ You can use o requerido arquivo system type to mount o given snapshot.\n■ O requerido permissão exists on o cliente to enable snapshots para reading\ne traversing." + "desc": "Snapshot mount failed", + "first_action": "You can use the required file system type to mount the given snapshot.", + "full_action": "Verify the following:\n■ You can use the required file system type to mount the given snapshot.\n■ The required permission exists on the client to enable snapshots for reading\nand traversing." }, "4215": { "code": 4215, - "desc": "Snapshot deletion falhou", - "first_action": "Garanta que o appropriate plug-in está configurado in o web UI com o", - "full_action": "Verifique o seguinte:\n■ Garanta que o appropriate plug-in está configurado in o web UI com o\nappropriate credentials. If o credentials estão changed, garanta que they estão\nupdated from o web UI.\n■ Garanta que o snapshot limite de o cloud provider está sufficient." + "desc": "Snapshot deletion failed", + "first_action": "Ensure that the appropriate plug-in is configured in the web UI with the", + "full_action": "Verify the following:\n■ Ensure that the appropriate plug-in is configured in the web UI with the\nappropriate credentials. If the credentials are changed, ensure that they are\nupdated from the web UI.\n■ Ensure that the snapshot limit of the cloud provider is sufficient." }, "4216": { "code": 4216, - "desc": "Snapshot cleanup falhou", - "first_action": "Verifique que you have enabled o permissão to excluir o", - "full_action": "Verifique que you have enabled o permissão to excluir o\narquivos." + "desc": "Snapshot cleanup failed", + "first_action": "Verify that you have enabled the permission to delete the", + "full_action": "Verify that you have enabled the permission to delete the\nfiles." }, "4217": { "code": 4217, - "desc": "Snapshot restauração falhou", - "first_action": "O snapshot exists.", - "full_action": "Verifique o seguinte:\n■ O snapshot exists.\n■ You have enough permissão to overwrite ou create arquivos in o restauração diretório\nou folder.\n■ O communication between NetBackup e o armazenamento array-filer está intact." + "desc": "Snapshot restore failed", + "first_action": "The snapshot exists.", + "full_action": "Verify the following:\n■ The snapshot exists.\n■ You have enough permission to overwrite or create files in the restore directory\nor folder.\n■ The communication between NetBackup and the storage array-filer is intact." }, "4218": { "code": 4218, - "desc": "Snapshot deport falhou", - "first_action": "O snapshot exists.", - "full_action": "Verifique o seguinte:\n■ O snapshot exists.\n■ O communication between NetBackup e o armazenamento array-filer está intact.\n■ TherequiredcredentialsforthestorageserverhavebeensuppliedinNetBackup.\n■ Qualquer requerido software e license para o third-party software estão configurado." + "desc": "Snapshot deport failed", + "first_action": "The snapshot exists.", + "full_action": "Verify the following:\n■ The snapshot exists.\n■ The communication between NetBackup and the storage array-filer is intact.\n■ TherequiredcredentialsforthestorageserverhavebeensuppliedinNetBackup.\n■ Any required software and license for the third-party software are configured." }, "4219": { "code": 4219, "desc": "Commandoperationfailed:Third-partycommandorAPIexecutionfailed", - "first_action": "From o NetBackup logs, identify o failing comando ou API.", - "full_action": "Do o seguinte:\n■ From o NetBackup logs, identify o failing comando ou API.\n■ Garanta que you have o requerido permissão to execute these commands.\n■ If possible, execute o comando manually to gather more details about o\nfalha.\n■ Verifique seu configuration to determinar o cause de o failing comando ou o\nAPI." + "first_action": "From the NetBackup logs, identify the failing command or API.", + "full_action": "Do the following:\n■ From the NetBackup logs, identify the failing command or API.\n■ Ensure that you have the required permission to execute these commands.\n■ If possible, execute the command manually to gather more details about the\nfailure.\n■ Check your configuration to determine the cause of the failing command or the\nAPI." }, "4220": { "code": 4220, - "desc": "Comando operation falhou: System comando ou API execution falhou", - "first_action": "From o NetBackup logs, identify o failing comando ou API.", - "full_action": "Verifique o seguinte:\n■ From o NetBackup logs, identify o failing comando ou API.\n■ Take corrective actions based on o erro que está reported como um result de o\ncomando execution.\n■ Garanta que you have o requerido permissão to execute these commands.\n■ If possible, execute o comando manually to gather more details about o\nfalha." + "desc": "Command operation failed: System command or API execution failed", + "first_action": "From the NetBackup logs, identify the failing command or API.", + "full_action": "Verify the following:\n■ From the NetBackup logs, identify the failing command or API.\n■ Take corrective actions based on the error that is reported as a result of the\ncommand execution.\n■ Ensure that you have the required permission to execute these commands.\n■ If possible, execute the command manually to gather more details about the\nfailure." }, "4221": { "code": 4221, - "desc": "Found um inválido ou unsupported configuration", - "first_action": "From o NetBackup logs, identify o failing entity e its erro.", - "full_action": "Verifique o seguinte:\n■ From o NetBackup logs, identify o failing entity e its erro.\n■ Verifique o support matrix to determinar o correct setup para o configuration." + "desc": "Found an invalid or unsupported configuration", + "first_action": "From the NetBackup logs, identify the failing entity and its error.", + "full_action": "Verify the following:\n■ From the NetBackup logs, identify the failing entity and its error.\n■ Check the support matrix to determine the correct setup for the configuration." }, "4222": { "code": 4222, - "desc": "Operation falhou: Não foi possível to acquire policy lock to take snapshot", + "desc": "Operation failed: Unable to acquire policy lock to take snapshot", "first_action": "Nomanualinterventionisrequired.TheNetBackupPolicy", - "full_action": "Nomanualinterventionisrequired.TheNetBackupPolicy\nExecution Manager (NBPEM) retries o job based on o Job retry delay setting\non o master servidor. To view ou set this property, go to Host Properties>Master\nServer>Global Parameters. Contate NetBackup Support if you continue to get\nthis erro e you have ensured que não overlapping snapshot jobs estão in progress." + "full_action": "Nomanualinterventionisrequired.TheNetBackupPolicy\nExecution Manager (NBPEM) retries the job based on the Job retry delay setting\non the master server. To view or set this property, go to Host Properties>Master\nServer>Global Parameters. Contact NetBackup Support if you continue to get\nthis error and you have ensured that no overlapping snapshot jobs are in progress." }, "4223": { "code": 4223, - "desc": "Operation não completed", - "first_action": "Make sure que Armazenamento vMotion está completed e que", - "full_action": "Make sure que Armazenamento vMotion está completed e que\nyou move o VM from NetBackup armazenamento to o production datastore." + "desc": "Operation not completed", + "first_action": "Make sure that Storage vMotion is completed and that", + "full_action": "Make sure that Storage vMotion is completed and that\nyou move the VM from NetBackup storage to the production datastore." }, "4224": { "code": 4224, - "desc": "STS Internal Erro", - "first_action": "Contate Cohesity Technical Support para assistance.", - "full_action": "Contate Cohesity Technical Support para assistance." + "desc": "STS Internal Error", + "first_action": "Contact Cohesity Technical Support for assistance.", + "full_action": "Contact Cohesity Technical Support for assistance." }, "4225": { "code": 4225, - "desc": "Unauthorized operation attempted por cliente ou mídia on armazenamento servidor", - "first_action": "Valid armazenamento servidor credentials estão configurado.", - "full_action": "Verifique o seguinte:\n■ Valid armazenamento servidor credentials estão configurado.\n■ O cliente has o requerido privileges per o vendor specification. Por favor refer\nto o NetBackup Replication Director Solutions Guide para more details." + "desc": "Unauthorized operation attempted by client or media on storage server", + "first_action": "Valid storage server credentials are configured.", + "full_action": "Verify the following:\n■ Valid storage server credentials are configured.\n■ The client has the required privileges per the vendor specification. Please refer\nto the NetBackup Replication Director Solutions Guide for more details." }, "4226": { "code": 4226, - "desc": "Communication falha ocorreu com armazenamento servidor.", - "first_action": "Garanta que o correct Snapshot Manager está registered com o correct port", - "full_action": "Verifique o seguinte:\n■ Garanta que o correct Snapshot Manager está registered com o correct port\nnumber.\n■ If o Snapshot Manager host name ou port number está changed, garanta que it\nestá updated in NetBackup.\n■ Garanta que o Snapshot Manager host name está accessible from o mídia\nservidor. To verifique, try to log on to o Snapshot Manager host from o browser\nde o mídia servidor.\n■ VerifyifthemediaserverorSnapshotManagercertificatesareinvalidormissing.\nO certificates estão não generated if o Snapshot Manager foi configurado to\nskip certificate generation por adding o seguinte entry in\n/cloudpoint/flexsnap.conf arquivo: [client_registration]\nskip_certificate_generation = yes\nExecutar o seguinte to generate o certificates:\n■ Garanta que o primary servidor hostname está accessible from o Snapshot\nManager. To verifique, try to log on to o Snapshot Manager e telnet to o\nprimary servidor usando ports 1556 e 443.\n■ If you use private names para installing certificates e communicating com\nNetBackup, which have to be resolved usando /etc/hosts, executar o\nseguinte:\n■ Add entradas similar to /etc/hosts arquivo in o\n/cloudpoint/openv/etc/hosts arquivo.\n■ EnsurethatyouusethesameprivatenameduringtheSnapshotManager\ninstallation como well como o Snapshot Manager registration.\n■ Remove o seguinte entry from /cloudpoint/flexsnap.conf arquivo:\n[client_registration] skip_certificate_generation = yes\n■ Re-register Snapshot Manager in o Cloud workload, usando o Edit option\ndisponível in o Snapshot Manager tab in o web UI." + "desc": "Communication failure occurred with storage server.", + "first_action": "Ensure that the correct Snapshot Manager is registered with the correct port", + "full_action": "Verify the following:\n■ Ensure that the correct Snapshot Manager is registered with the correct port\nnumber.\n■ If the Snapshot Manager host name or port number is changed, ensure that it\nis updated in NetBackup.\n■ Ensure that the Snapshot Manager host name is accessible from the media\nserver. To verify, try to log on to the Snapshot Manager host from the browser\nof the media server.\n■ VerifyifthemediaserverorSnapshotManagercertificatesareinvalidormissing.\nThe certificates are not generated if the Snapshot Manager was configured to\nskip certificate generation by adding the following entry in\n/cloudpoint/flexsnap.conf file: [client_registration]\nskip_certificate_generation = yes\nPerform the following to generate the certificates:\n■ Ensure that the primary server hostname is accessible from the Snapshot\nManager. To verify, try to log on to the Snapshot Manager and telnet to the\nprimary server using ports 1556 and 443.\n■ If you use private names for installing certificates and communicating with\nNetBackup, which have to be resolved using /etc/hosts, perform the\nfollowing:\n■ Add entries similar to /etc/hosts file in the\n/cloudpoint/openv/etc/hosts file.\n■ EnsurethatyouusethesameprivatenameduringtheSnapshotManager\ninstallation as well as the Snapshot Manager registration.\n■ Remove the following entry from /cloudpoint/flexsnap.conf file:\n[client_registration] skip_certificate_generation = yes\n■ Re-register Snapshot Manager in the Cloud workload, using the Edit option\navailable in the Snapshot Manager tab in the web UI." }, "4227": { "code": 4227, - "desc": "STS Plug-in erro ocorreu", - "first_action": "Contate Cohesity Technical Support para assistance.", - "full_action": "Contate Cohesity Technical Support para assistance." + "desc": "STS Plug-in error occurred", + "first_action": "Contact Cohesity Technical Support for assistance.", + "full_action": "Contact Cohesity Technical Support for assistance." }, "4228": { "code": 4228, - "desc": "Armazenamento servidor ou plug-in version mismatch", - "first_action": "Verifique que o cliente e o mídia servidor support o", - "full_action": "Verifique que o cliente e o mídia servidor support o\nversion de o armazenamento servidor." + "desc": "Storage server or plug-in version mismatch", + "first_action": "Verify that the client and the media server support the", + "full_action": "Verify that the client and the media server support the\nversion of the storage server." }, "4229": { "code": 4229, - "desc": "Insufficient resources ou capabilities found por armazenamento servidor", - "first_action": "O armazenamento servidor recognizes o identified dispositivo from o backup selection.", - "full_action": "Verifique o seguinte:\n■ O armazenamento servidor recognizes o identified dispositivo from o backup selection.\n■ O requerido features estão enabled on o armazenamento.\n■ O requerido recurso licenses estão applied on o armazenamento.\n■ ThestorageserverhassufficientavailablestoragespaceforNetBackuptriggered\nsnapshots." + "desc": "Insufficient resources or capabilities found by storage server", + "first_action": "The storage server recognizes the identified device from the backup selection.", + "full_action": "Verify the following:\n■ The storage server recognizes the identified device from the backup selection.\n■ The required features are enabled on the storage.\n■ The required feature licenses are applied on the storage.\n■ ThestorageserverhassufficientavailablestoragespaceforNetBackuptriggered\nsnapshots." }, "4230": { "code": 4230, - "desc": "Inválido armazenamento topology ou armazenamento servidor configuration erro", - "first_action": "Verifique que o armazenamento está correctly configurado per o vendor specification.", - "full_action": "Do o seguinte:\n■ Verifique que o armazenamento está correctly configurado per o vendor specification.\n■ Verifique que o underlying armazenamento supports o topology que está specified in o\narmazenamento lifecycle policy." + "desc": "Invalid storage topology or storage server configuration error", + "first_action": "Verify that the storage is correctly configured per the vendor specification.", + "full_action": "Do the following:\n■ Verify that the storage is correctly configured per the vendor specification.\n■ Verify that the underlying storage supports the topology that is specified in the\nstorage lifecycle policy." }, "4231": { "code": 4231, - "desc": "STS Unexpected Erro", - "first_action": "Contate Cohesity Technical Support para assistance.", - "full_action": "Contate Cohesity Technical Support para assistance." + "desc": "STS Unexpected Error", + "first_action": "Contact Cohesity Technical Support for assistance.", + "full_action": "Contact Cohesity Technical Support for assistance." }, "4232": { "code": 4232, - "desc": "Inválido Discovery Query URI", - "first_action": "Examine o URI usando o policy editor para syntax errors.", - "full_action": "Examine o URI usando o policy editor para syntax errors." + "desc": "Invalid Discovery Query URI", + "first_action": "Examine the URI using the policy editor for syntax errors.", + "full_action": "Examine the URI using the policy editor for syntax errors." }, "4233": { "code": 4233, - "desc": "BIOS UUID cliente reference não allowed para vCloud NetBackup status codes 642 NetBackup status codes", - "first_action": "Select another form de cliente reference para o policy,", - "full_action": "Select another form de cliente reference para o policy,\npossibly instance UUID." + "desc": "BIOS UUID client reference not allowed for vCloud NetBackup status codes 642 NetBackup status codes", + "first_action": "Select another form of client reference for the policy,", + "full_action": "Select another form of client reference for the policy,\npossibly instance UUID." }, "4234": { "code": 4234, - "desc": "VMware servidor login falha", - "first_action": "Correct o credentials que estão configurado para o", - "full_action": "Correct o credentials que estão configurado para o\ndesignated servidor." + "desc": "VMware server login failure", + "first_action": "Correct the credentials that are configured for the", + "full_action": "Correct the credentials that are configured for the\ndesignated server." }, "4235": { "code": 4235, - "desc": "VCloud keyword used when vCloud não enabled", - "first_action": "Configure um vCloud director credential, ou remove qualquer", - "full_action": "Configure um vCloud director credential, ou remove qualquer\nvCloud related keywords from o policy query." + "desc": "VCloud keyword used when vCloud not enabled", + "first_action": "Configure a vCloud director credential, or remove any", + "full_action": "Configure a vCloud director credential, or remove any\nvCloud related keywords from the policy query." }, "4236": { "code": 4236, "desc": "VCloud policy includes multiple organizations", - "first_action": "Correct o policy query to select apenas VMs from um single", - "full_action": "Correct o policy query to select apenas VMs from um single\norganization, ou change o policy to enable VMs from multiple organizations." + "first_action": "Correct the policy query to select only VMs from a single", + "full_action": "Correct the policy query to select only VMs from a single\norganization, or change the policy to enable VMs from multiple organizations." }, "4237": { "code": 4237, - "desc": "Cliente does não meet policy requirements", + "desc": "Client does not meet policy requirements", "first_action": "ModifytheVMtomeettherequirementsfortheconfigured", - "full_action": "ModifytheVMtomeettherequirementsfortheconfigured\ncliente reference, ou change o policy to use um different cliente reference." + "full_action": "ModifytheVMtomeettherequirementsfortheconfigured\nclient reference, or change the policy to use a different client reference." }, "4238": { "code": 4238, - "desc": "Não servidor credentials configurado para policy", - "first_action": "Verifique que o appropriate servidor credentials have been", - "full_action": "Verifique que o appropriate servidor credentials have been\nentered para o type de discovery policy." + "desc": "No server credentials configured for policy", + "first_action": "Verify that the appropriate server credentials have been", + "full_action": "Verify that the appropriate server credentials have been\nentered for the type of discovery policy." }, "4239": { "code": 4239, - "desc": "Não foi possível to find o virtual machine", - "first_action": "O virtual machine identifier configurado para o policy e o name (display", - "full_action": "Verifique o seguinte:\n■ O virtual machine identifier configurado para o policy e o name (display\nname, host name, UUID) entered para o virtual machine on o policy agree.\n■ You can view o virtual machine in o VMware usuário interface." + "desc": "Unable to find the virtual machine", + "first_action": "The virtual machine identifier configured for the policy and the name (display", + "full_action": "Verify the following:\n■ The virtual machine identifier configured for the policy and the name (display\nname, host name, UUID) entered for the virtual machine on the policy agree.\n■ You can view the virtual machine in the VMware user interface." }, "4240": { "code": 4240, - "desc": "Operation não supported", - "first_action": "Contate Cohesity Technical Support para assistance.", - "full_action": "Contate Cohesity Technical Support para assistance." + "desc": "Operation not supported", + "first_action": "Contact Cohesity Technical Support for assistance.", + "full_action": "Contact Cohesity Technical Support for assistance." }, "4241": { "code": 4241, - "desc": "Block-level incremental backups estão não supported para this dispositivo", - "first_action": "Upgrade o virtual machine hardware to version 7 ou", - "full_action": "Upgrade o virtual machine hardware to version 7 ou\nhigher (veja o appropriate VMware documentation)." + "desc": "Block-level incremental backups are not supported for this device", + "first_action": "Upgrade the virtual machine hardware to version 7 or", + "full_action": "Upgrade the virtual machine hardware to version 7 or\nhigher (see the appropriate VMware documentation)." }, "4243": { "code": 4243, - "desc": "Não foi possível to conectar to o VirtualCenter servidor", - "first_action": "If there estão too many VM snapshot jobs, limite o VM jobs", - "full_action": "If there estão too many VM snapshot jobs, limite o VM jobs\nusando o VMware Resource Limite to limite o concurrent jobs." + "desc": "Unable to connect to the VirtualCenter server", + "first_action": "If there are too many VM snapshot jobs, limit the VM jobs", + "full_action": "If there are too many VM snapshot jobs, limit the VM jobs\nusing the VMware Resource Limit to limit the concurrent jobs." }, "4245": { "code": 4245, - "desc": "Inválido pathname para backup selection", - "first_action": "O IP address não é possível be used in o pathname.", - "full_action": "O IP address não é possível be used in o pathname." + "desc": "Invalid pathname for backup selection", + "first_action": "The IP address cannot be used in the pathname.", + "full_action": "The IP address cannot be used in the pathname." }, "4246": { "code": 4246, - "desc": "A operação solicitada foi parcialmente bem-sucedida.", - "first_action": "Create um separate policy para each cliente", - "full_action": "Do o seguinte:\n■ Create um separate policy para each cliente\n■ Specify o correct volume name para o Vserver\n■ Specify um volume name e não um diretório within um volume" + "desc": "The requested operation was partially successful.", + "first_action": "Create a separate policy for each client", + "full_action": "Do the following:\n■ Create a separate policy for each client\n■ Specify the correct volume name for the Vserver\n■ Specify a volume name and not a directory within a volume" }, "4248": { "code": 4248, - "desc": "Index from snapshot operation falhou com um internal erro", + "desc": "Index from snapshot operation failed with an internal error", "first_action": "ChecktheNetBackupadministrationlogsformoredetails.", "full_action": "ChecktheNetBackupadministrationlogsformoredetails.\nEnsurethatthereisenoughspaceonthemediaservertocreatetheindexdatabase." }, "4249": { "code": 4249, - "desc": "Index from snapshot operation falhou, catalog already exists NetBackup status codes 646 NetBackup status codes", - "first_action": "Verifique que there está não existing catalog para o specified", - "full_action": "Verifique que there está não existing catalog para o specified\nsource image. Verifique o NetBackup administration logs para more details." + "desc": "Index from snapshot operation failed, catalog already exists NetBackup status codes 646 NetBackup status codes", + "first_action": "Check that there is no existing catalog for the specified", + "full_action": "Check that there is no existing catalog for the specified\nsource image. Check the NetBackup administration logs for more details." }, "4250": { "code": 4250, - "desc": "Index from snapshot operation falhou, não foi possível to find child image ou arquivo informação", + "desc": "Index from snapshot operation failed, unable to find child image or file information", "first_action": "ChecktheNetBackupadministrationlogsformoredetails.", "full_action": "ChecktheNetBackupadministrationlogsformoredetails." }, "4251": { "code": 4251, "desc": "Indexfromsnapshotoperationfailed.Failedtowriteintoindexdatabase.", - "first_action": "Typically, o index banco de dados está created under", - "full_action": "Typically, o index banco de dados está created under\nNB_INSTALL_DIR/tmp; para example, /usr/openv/netbackup/tmp. It can be\noverridden por SNAPDIFF_DB_PATH in o NetBackup configuration arquivo. Garanta\nthatthereisenoughspaceonthemediaservertocreatetheindexdatabase.Check\no NetBackup administration logs para more details." + "first_action": "Typically, the index database is created under", + "full_action": "Typically, the index database is created under\nNB_INSTALL_DIR/tmp; for example, /usr/openv/netbackup/tmp. It can be\noverridden by SNAPDIFF_DB_PATH in the NetBackup configuration file. Ensure\nthatthereisenoughspaceonthemediaservertocreatetheindexdatabase.Check\nthe NetBackup administration logs for more details." }, "4252": { "code": 4252, - "desc": "Index from snapshot operation falhou. Entry does não belong to qualquer de o backup selection entradas.", + "desc": "Index from snapshot operation failed. Entry does not belong to any of the backup selection entries.", "first_action": "ChecktheNetBackupadministrationlogsformoredetails.", "full_action": "ChecktheNetBackupadministrationlogsformoredetails." }, "4253": { "code": 4253, - "desc": "Index from snapshot operation falhou. SLP version mismatch para current e previous backup image.", + "desc": "Index from snapshot operation failed. SLP version mismatch for current and previous backup image.", "first_action": "ChecktheNetBackupadministrationlogsformoredetails.", "full_action": "ChecktheNetBackupadministrationlogsformoredetails." }, "4254": { "code": 4254, - "desc": "Inválido ou não caminho found to create index banco de dados", - "first_action": "Typically, o index banco de dados está created under", - "full_action": "Typically, o index banco de dados está created under\nNB_INSTALL_DIR/tmp; para example, /usr/openv/netbackup/tmp. It can be\noverriddenbyaddingSNAPDIFF_DB_PATHintheNetBackupconfiguration.Check\nif o defined caminho exists." + "desc": "Invalid or no path found to create index database", + "first_action": "Typically, the index database is created under", + "full_action": "Typically, the index database is created under\nNB_INSTALL_DIR/tmp; for example, /usr/openv/netbackup/tmp. It can be\noverriddenbyaddingSNAPDIFF_DB_PATHintheNetBackupconfiguration.Check\nif the defined path exists." }, "4255": { "code": 4255, - "desc": "Index from snapshot usando SnapDiff está disabled por o usuário", - "first_action": "Set to 0; do não executar o index from snapshot operation por usando SnapDiff.", - "full_action": "To enable o index from snapshot por usando SnapDiff,\nchange o value de o NetBackup configuration key USE_SNAPDIFF por usando\no bpsetconfig CLI. O possible values de o key estão como follows:\n■ Set to 0; do não executar o index from snapshot operation por usando SnapDiff.\n■ Set to 1; o index from snapshot por usando SnapDiff está enabled apenas para o\nincremental schedule.\n■ Set to 2; o index from snapshot por usando SnapDiff está enabled para todos schedule\ntypes." + "desc": "Index from snapshot using SnapDiff is disabled by the user", + "first_action": "Set to 0; do not perform the index from snapshot operation by using SnapDiff.", + "full_action": "To enable the index from snapshot by using SnapDiff,\nchange the value of the NetBackup configuration key USE_SNAPDIFF by using\nthe bpsetconfig CLI. The possible values of the key are as follows:\n■ Set to 0; do not perform the index from snapshot operation by using SnapDiff.\n■ Set to 1; the index from snapshot by using SnapDiff is enabled only for the\nincremental schedule.\n■ Set to 2; the index from snapshot by using SnapDiff is enabled for all schedule\ntypes." }, "4256": { "code": 4256, - "desc": "Index from snapshot está não supported para o arquivo system associated com backup selection", - "first_action": "Currently, o index from o snapshot operation usando", - "full_action": "Currently, o index from o snapshot operation usando\nSnapDiff está supported para NFS, CIFS arquivo systems. It está also supported when o\npolicy type está NDMP. Change o policy com o backup selection entradas que have\num arquivo system que está supported para o index from snapshot operations por usando\nSnapDiff." + "desc": "Index from snapshot is not supported for the file system associated with backup selection", + "first_action": "Currently, the index from the snapshot operation using", + "full_action": "Currently, the index from the snapshot operation using\nSnapDiff is supported for NFS, CIFS file systems. It is also supported when the\npolicy type is NDMP. Change the policy with the backup selection entries that have\na file system that is supported for the index from snapshot operations by using\nSnapDiff." }, "4257": { "code": 4257, - "desc": "Index from snapshot está não supported para o armazenamento servidor", + "desc": "Index from snapshot is not supported for the storage server", "first_action": "PleasecheckthattheindexfromsnapshotusingSnapDiff", - "full_action": "PleasecheckthattheindexfromsnapshotusingSnapDiff\nestá supported para o armazenamento servidor. If it está não, then change o SLP com o STU\nassociated com o armazenamento servidor having support para index from snapshot usando\nSnapDiff." + "full_action": "PleasecheckthattheindexfromsnapshotusingSnapDiff\nis supported for the storage server. If it is not, then change the SLP with the STU\nassociated with the storage server having support for index from snapshot using\nSnapDiff." }, "4258": { "code": 4258, - "desc": "Transient erro encontrado while taking Hyper-V VM snapshot", - "first_action": "Verifique o event log para Hyper-V VMMS (Log Name:", - "full_action": "Verifique o event log para Hyper-V VMMS (Log Name:\nMicrosoft-Windows-Hyper-V-VMMS/Admin) para more informação." + "desc": "Transient error encountered while taking Hyper-V VM snapshot", + "first_action": "Check the event log for Hyper-V VMMS (Log Name:", + "full_action": "Check the event log for Hyper-V VMMS (Log Name:\nMicrosoft-Windows-Hyper-V-VMMS/Admin) for more information." }, "4259": { "code": 4259, - "desc": "Falhou to find VirtualCenter host name in VMware Lookup Service", - "first_action": "Use o system name como configurado in o Platform", - "full_action": "Use o system name como configurado in o Platform\nServices Controller como o NetBackup virtual machine servidor name." + "desc": "Failed to find VirtualCenter host name in VMware Lookup Service", + "first_action": "Use the system name as configured in the Platform", + "full_action": "Use the system name as configured in the Platform\nServices Controller as the NetBackup virtual machine server name." }, "4260": { "code": 4260, - "desc": "Encontrado SSO login falha", - "first_action": "Garanta que o credentials que you entered para o", - "full_action": "Garanta que o credentials que you entered para o\nNetBackup virtual machine servidor estão authorized para Single Sign-On." + "desc": "Encountered SSO login failure", + "first_action": "Ensure that the credentials that you entered for the", + "full_action": "Ensure that the credentials that you entered for the\nNetBackup virtual machine server are authorized for Single Sign-On." }, "4261": { "code": 4261, - "desc": "Encontrado VMware Internal Servidor Erro", - "first_action": "Refer to o details que estão given in o erro message", - "full_action": "Refer to o details que estão given in o erro message\ne o related VMware Knowledge Base article. Verifique o NetBackup VxUL logs\n(libvcloudsuite).\nRelated VMware Knowledge Base article: http://kb.vmware.com/kb/2124204" + "desc": "Encountered VMware Internal Server Error", + "first_action": "Refer to the details that are given in the error message", + "full_action": "Refer to the details that are given in the error message\nand the related VMware Knowledge Base article. Check the NetBackup VxUL logs\n(libvcloudsuite).\nRelated VMware Knowledge Base article: http://kb.vmware.com/kb/2124204" }, "4262": { "code": 4262, - "desc": "Encontrado VMware vCloud Suite API falha", - "first_action": "Refer to o VMware vCenter Servidor 6.0 Deployment", - "full_action": "Refer to o VMware vCenter Servidor 6.0 Deployment\nGuide e o related VMware Knowledge Base article.\nRelated VMware Knowledge Base article: http://kb.vmware.com/kb/2106283" + "desc": "Encountered VMware vCloud Suite API failure", + "first_action": "Refer to the VMware vCenter Server 6.0 Deployment", + "full_action": "Refer to the VMware vCenter Server 6.0 Deployment\nGuide and the related VMware Knowledge Base article.\nRelated VMware Knowledge Base article: http://kb.vmware.com/kb/2106283" }, "4263": { "code": 4263, - "desc": "Encontrado VMware SOAP API falha", - "first_action": "Refer to o details que estão given in o erro message", - "full_action": "Refer to o details que estão given in o erro message\ne o related VMware Knowledge Base article. Verifique o NetBackup VxUL logs\n(libvcloudsuite).\nVMware Knowledge Base article: http://kb.vmware.com/kb/2125193" + "desc": "Encountered VMware SOAP API failure", + "first_action": "Refer to the details that are given in the error message", + "full_action": "Refer to the details that are given in the error message\nand the related VMware Knowledge Base article. Check the NetBackup VxUL logs\n(libvcloudsuite).\nVMware Knowledge Base article: http://kb.vmware.com/kb/2125193" }, "4264": { "code": 4264, - "desc": "Encontrado unexpected erro while processing TagView XML", - "first_action": "If o erro está from um test query, try o operation again. If", - "full_action": "If o erro está from um test query, try o operation again. If\no parent (Discovery) job fails, try o job again com um Reuse VMware selection\nquery results value de 0 in o failing policy clients tab to regenerate o XML arquivo." + "desc": "Encountered unexpected error while processing TagView XML", + "first_action": "If the error is from a test query, try the operation again. If", + "full_action": "If the error is from a test query, try the operation again. If\nthe parent (Discovery) job fails, try the job again with a Reuse VMware selection\nquery results value of 0 in the failing policy clients tab to regenerate the XML file." }, "4265": { "code": 4265, - "desc": "Encontrado um VMware Virtual Machine Servidor que does não support Tags NetBackup status codes 651 NetBackup status codes", + "desc": "Encountered a VMware Virtual Machine Server that does not support Tags NetBackup status codes 651 NetBackup status codes", "first_action": "RefertotheNetBackupforVMwareAdministrator'sGuide.", "full_action": "RefertotheNetBackupforVMwareAdministrator'sGuide." }, "4266": { "code": 4266, - "desc": "Encontrado um VMware Virtual Machine Servidor que does não offer Tag APIs", + "desc": "Encountered a VMware Virtual Machine Server that does not offer Tag APIs", "first_action": "RefertotheNetBackupforVMwareAdministrator'sGuide.", "full_action": "RefertotheNetBackupforVMwareAdministrator'sGuide." }, "4267": { "code": 4267, - "desc": "Falhou to initialize Java Runtime Environment", + "desc": "Failed to initialize Java Runtime Environment", "first_action": "InstalltheversionoftheNetBackupRemoteAdministration", - "full_action": "InstalltheversionoftheNetBackupRemoteAdministration\nConsole que corresponds to o NetBackup Cliente installation. O version de o\nNetBackup Remote Administration Console must match o NetBackup Cliente\nversion." + "full_action": "InstalltheversionoftheNetBackupRemoteAdministration\nConsole that corresponds to the NetBackup Client installation. The version of the\nNetBackup Remote Administration Console must match the NetBackup Client\nversion." }, "4268": { "code": 4268, - "desc": "Falhou to retrieve resource pool informação", - "first_action": "Verifique o resource pool caminho. If it está incorrect, specify o", - "full_action": "Verifique o resource pool caminho. If it está incorrect, specify o\ncorrect resource pool caminho que exists in destination vCenter servidor." + "desc": "Failed to retrieve resource pool information", + "first_action": "Check the resource pool path. If it is incorrect, specify the", + "full_action": "Check the resource pool path. If it is incorrect, specify the\ncorrect resource pool path that exists in destination vCenter server." }, "4269": { "code": 4269, - "desc": "Found multiple virtual machines com same identity", - "first_action": "Select um different display name para restauração ou rename o", - "full_action": "Select um different display name para restauração ou rename o\nvirtualmachinesinthedestinationresourcepoolorvApp.Onlyonevirtualmachine\ncom o same display name can exist in o resource pool ou vApp." + "desc": "Found multiple virtual machines with same identity", + "first_action": "Select a different display name for restore or rename the", + "full_action": "Select a different display name for restore or rename the\nvirtualmachinesinthedestinationresourcepoolorvApp.Onlyonevirtualmachine\nwith the same display name can exist in the resource pool or vApp." }, "4270": { "code": 4270, - "desc": "Um snapshot de o virtual machine exists e o policy option specifies aborting o backup", - "first_action": "Either remove o snapshot e restart o backup job ou", - "full_action": "Either remove o snapshot e restart o backup job ou\nmodify o policy to ignore ou remove existing snapshots. NetBackup removes\nexisting snapshots apenas if NetBackup created them." + "desc": "A snapshot of the virtual machine exists and the policy option specifies aborting the backup", + "first_action": "Either remove the snapshot and restart the backup job or", + "full_action": "Either remove the snapshot and restart the backup job or\nmodify the policy to ignore or remove existing snapshots. NetBackup removes\nexisting snapshots only if NetBackup created them." }, "4271": { "code": 4271, - "desc": "Maximum virtual machine snapshots excedido", - "first_action": "Remove o virtual machine's snapshots e restart o", - "full_action": "Remove o virtual machine's snapshots e restart o\nbackup job." + "desc": "Maximum virtual machine snapshots exceeded", + "first_action": "Remove the virtual machine's snapshots and restart the", + "full_action": "Remove the virtual machine's snapshots and restart the\nbackup job." }, "4272": { "code": 4272, - "desc": "Maximum delta arquivos excedido NetBackup status codes 653 NetBackup status codes", - "first_action": "Consolidate o virtual machine’s disks e restart o", - "full_action": "Consolidate o virtual machine’s disks e restart o\nbackup job." + "desc": "Maximum delta files exceeded NetBackup status codes 653 NetBackup status codes", + "first_action": "Consolidate the virtual machine’s disks and restart the", + "full_action": "Consolidate the virtual machine’s disks and restart the\nbackup job." }, "4273": { "code": 4273, - "desc": "Não foi possível to lock o backup ou restauração host para virtual machine snapshot operations", - "first_action": "Restart o backup job when não other virtual machine", - "full_action": "Restart o backup job when não other virtual machine\nsnapshotoperationsareinprocess.IfNetBackupcannotacquirethelockfrequently,\nadjust o NetBackup job configuration como necessary to allow o virtual machine\nsnapshots to run at different times ou to run on different hosts. Alternatively,\nreconfigure NetBackup so que o snapshot serialization está não requerido." + "desc": "Unable to lock the backup or restore host for virtual machine snapshot operations", + "first_action": "Restart the backup job when no other virtual machine", + "full_action": "Restart the backup job when no other virtual machine\nsnapshotoperationsareinprocess.IfNetBackupcannotacquirethelockfrequently,\nadjust the NetBackup job configuration as necessary to allow the virtual machine\nsnapshots to run at different times or to run on different hosts. Alternatively,\nreconfigure NetBackup so that the snapshot serialization is not required." }, "4274": { "code": 4274, - "desc": "Falhou to remove virtual machine snapshot", - "first_action": "Excluir o virtual machine snapshot manually.", - "full_action": "Excluir o virtual machine snapshot manually." + "desc": "Failed to remove virtual machine snapshot", + "first_action": "Delete the virtual machine snapshot manually.", + "full_action": "Delete the virtual machine snapshot manually." }, "4275": { "code": 4275, - "desc": "Não foi possível to consolidate Virtual Machine Disks", - "first_action": "Consolidate o virtual machine’s disks manually e", - "full_action": "Consolidate o virtual machine’s disks manually e\nrestart o job." + "desc": "Unable to consolidate Virtual Machine Disks", + "first_action": "Consolidate the virtual machine’s disks manually and", + "full_action": "Consolidate the virtual machine’s disks manually and\nrestart the job." }, "4276": { "code": 4276, - "desc": "Não foi possível to retrieve Virtual Machine Disco informação", + "desc": "Unable to retrieve Virtual Machine Disk information", "first_action": "Reviewthejobdetailsandthebpfislogforanyadditional", - "full_action": "Reviewthejobdetailsandthebpfislogforanyadditional\ninformação que está related to o erro. Correct o underlying issues que cause o\nfalha e restart o job." + "full_action": "Reviewthejobdetailsandthebpfislogforanyadditional\ninformation that is related to the error. Correct the underlying issues that cause the\nfailure and restart the job." }, "4277": { "code": 4277, - "desc": "Virtual machine caminho contains unsupported characters", + "desc": "Virtual machine path contains unsupported characters", "first_action": "Renamethevirtualmachineand/orfolderpathtoonethat", - "full_action": "Renamethevirtualmachineand/orfolderpathtoonethat\ncontains apenas supported characters." + "full_action": "Renamethevirtualmachineand/orfolderpathtoonethat\ncontains only supported characters." }, "4278": { "code": 4278, - "desc": "Não foi possível to retrieve virtual machine informação", + "desc": "Unable to retrieve virtual machine information", "first_action": "Reviewthejobdetailsandthebpfislogforanyadditional", - "full_action": "Reviewthejobdetailsandthebpfislogforanyadditional\ninformação que está related to o erro. Correct o underlying issues que cause o\nfalha e restart o job." + "full_action": "Reviewthejobdetailsandthebpfislogforanyadditional\ninformation that is related to the error. Correct the underlying issues that cause the\nfailure and restart the job." }, "4279": { "code": 4279, - "desc": "Não foi possível to retrieve virtual machine vCloud informação", + "desc": "Unable to retrieve virtual machine vCloud information", "first_action": "Reviewthejobdetailsandthebpfislogforanyadditional", - "full_action": "Reviewthejobdetailsandthebpfislogforanyadditional\ninformação que está related to o erro. Correct o underlying issues que caused\no falha e restart o job." + "full_action": "Reviewthejobdetailsandthebpfislogforanyadditional\ninformation that is related to the error. Correct the underlying issues that caused\nthe failure and restart the job." }, "4280": { "code": 4280, - "desc": "Virtual machine contains independent e Raw Dispositivo Mapping disks apenas", - "first_action": "Remove o virtual machine from o backup policy", - "full_action": "Remove o virtual machine from o backup policy\nselection ou modify o virtual machine to include additional disks." + "desc": "Virtual machine contains independent and Raw Device Mapping disks only", + "first_action": "Remove the virtual machine from the backup policy", + "full_action": "Remove the virtual machine from the backup policy\nselection or modify the virtual machine to include additional disks." }, "4281": { "code": 4281, - "desc": "Virtual machine contains independent disks apenas", - "first_action": "Remove o virtual machine from o backup policy", - "full_action": "Remove o virtual machine from o backup policy\nselection ou modify o virtual machine to include additional disks." + "desc": "Virtual machine contains independent disks only", + "first_action": "Remove the virtual machine from the backup policy", + "full_action": "Remove the virtual machine from the backup policy\nselection or modify the virtual machine to include additional disks." }, "4282": { "code": 4282, - "desc": "Virtual machine contains Raw Dispositivo Mapping disks apenas", - "first_action": "Remove o virtual machine from o backup policy", - "full_action": "Remove o virtual machine from o backup policy\nselection ou modify o virtual machine to include additional disks." + "desc": "Virtual machine contains Raw Device Mapping disks only", + "first_action": "Remove the virtual machine from the backup policy", + "full_action": "Remove the virtual machine from the backup policy\nselection or modify the virtual machine to include additional disks." }, "4283": { "code": 4283, - "desc": "Erro detected while processing disco identifiers", - "first_action": "Modify o virtual machine so que nenhum de o UUIDs para", - "full_action": "Modify o virtual machine so que nenhum de o UUIDs para\nits disks duplicate o UUID para qualquer other virtual machine." + "desc": "Error detected while processing disk identifiers", + "first_action": "Modify the virtual machine so that none of the UUIDs for", + "full_action": "Modify the virtual machine so that none of the UUIDs for\nits disks duplicate the UUID for any other virtual machine." }, "4287": { "code": 4287, - "desc": "ANetBackupsnapshotofthevirtualmachineexistsandthepolicyoption specifies aborting o backup", - "first_action": "Manually remove o orphaned snapshot.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Manually remove o orphaned snapshot.\nPara VMware, you can use o VMware vSphere interface to remove virtual\nmachine snapshots. Para Hyper-V, you can use nbhypervtool.exe to remove\nNetBackupsnapshotsthatwerecreatedwiththeWMIbackupmethod.Formore\ninformationonnbhypervtool.exe,refertotheNetBackupCommandsReference\nGuide.\n■ Reduce o likelihood de orphaned snapshots por changing o resource limits\nto reduce o load on o appropriate VMware ou Hyper-V resource. O\nResource Limite dialog está in o NetBackup Administration Console under\nHost Properties > Master Servers. O NetBackup guides para VMware e\nHyper-V describe o disponível settings.\n■ Change o NetBackup policy schedules to avoid simultaneous backups de o\nvirtual machine.\n■ ForVMwareonly:ChangetheNetBackuppolicy’sExistingsnapshothandling\nparâmetro to um different option (such como Continue Backup).\n■ Para RHV apenas: Refer to o seguinte article para steps to unlock o disco:\nhttps://access.redhat.com/solutions/396753. Then manually remove o older\nsnapshots from o RHV manager.\n■ Para Nutanix AHV, refer to o Nutanix AHV Administrator’s Guide to remove o\nVM snapshots." + "desc": "ANetBackupsnapshotofthevirtualmachineexistsandthepolicyoption specifies aborting the backup", + "first_action": "Manually remove the orphaned snapshot.", + "full_action": "Do the following, as appropriate:\n■ Manually remove the orphaned snapshot.\nFor VMware, you can use the VMware vSphere interface to remove virtual\nmachine snapshots. For Hyper-V, you can use nbhypervtool.exe to remove\nNetBackupsnapshotsthatwerecreatedwiththeWMIbackupmethod.Formore\ninformationonnbhypervtool.exe,refertotheNetBackupCommandsReference\nGuide.\n■ Reduce the likelihood of orphaned snapshots by changing the resource limits\nto reduce the load on the appropriate VMware or Hyper-V resource. The\nResource Limit dialog is in the NetBackup Administration Console under\nHost Properties > Master Servers. The NetBackup guides for VMware and\nHyper-V describe the available settings.\n■ Change the NetBackup policy schedules to avoid simultaneous backups of the\nvirtual machine.\n■ ForVMwareonly:ChangetheNetBackuppolicy’sExistingsnapshothandling\nparameter to a different option (such as Continue Backup).\n■ For RHV only: Refer to the following article for steps to unlock the disk:\nhttps://access.redhat.com/solutions/396753. Then manually remove the older\nsnapshots from the RHV manager.\n■ For Nutanix AHV, refer to the Nutanix AHV Administrator’s Guide to remove the\nVM snapshots." }, "4290": { "code": 4290, - "desc": "Falhou to create virtual machine snapshot. Virtual machine está ocupado performing another operation.", - "first_action": "Retry o snapshot job after o virtual machine has", - "full_action": "Retry o snapshot job after o virtual machine has\ncompleted o conflicting operation." + "desc": "Failed to create virtual machine snapshot. Virtual machine is busy performing another operation.", + "first_action": "Retry the snapshot job after the virtual machine has", + "full_action": "Retry the snapshot job after the virtual machine has\ncompleted the conflicting operation." }, "4292": { "code": 4292, "desc": "Unabletoactivatechangeblocktrackingincurrentstateofvirtualmachine", - "first_action": "Excluir ou consolidate o snapshots on virtual machines", - "full_action": "Excluir ou consolidate o snapshots on virtual machines\non vSphere version 6.5 e above so que NetBackup can enable change block\ntracking." + "first_action": "Delete or consolidate the snapshots on virtual machines", + "full_action": "Delete or consolidate the snapshots on virtual machines\non vSphere version 6.5 and above so that NetBackup can enable change block\ntracking." }, "4293": { "code": 4293, - "desc": "Inválido credentials ou um access violation", - "first_action": "Verifique que there estão valid credentials configurado para o", - "full_action": "Verifique que there estão valid credentials configurado para o\nhost/server que está being accessed e que o usuário has valid privileges to make\no request." + "desc": "Invalid credentials or an access violation", + "first_action": "Verify that there are valid credentials configured for the", + "full_action": "Verify that there are valid credentials configured for the\nhost/server that is being accessed and that the user has valid privileges to make\nthe request." }, "4294": { "code": 4294, - "desc": "O virtual machine está disconnected", - "first_action": "Garanta que o ESXi host está powered on e o vCenter", - "full_action": "Garanta que o ESXi host está powered on e o vCenter\nServidor agent (vpxa) está executando." + "desc": "The virtual machine is disconnected", + "first_action": "Ensure that the ESXi host is powered on and the vCenter", + "full_action": "Ensure that the ESXi host is powered on and the vCenter\nServer agent (vpxa) is running." }, "4295": { "code": 4295, - "desc": "VM retrieval falhou.", + "desc": "VM retrieval failed.", "first_action": "EnsurethattheRHVmanagercredentialsarecorrectand", - "full_action": "EnsurethattheRHVmanagercredentialsarecorrectand\no RHV manager está accessible from o backup host." + "full_action": "EnsurethattheRHVmanagercredentialsarecorrectand\nthe RHV manager is accessible from the backup host." }, "4296": { "code": 4296, - "desc": "Não servidor credentials configurado.", - "first_action": "Add o RHV virtualization servidor credentials.", - "full_action": "Add o RHV virtualization servidor credentials." + "desc": "No server credentials configured.", + "first_action": "Add the RHV virtualization server credentials.", + "full_action": "Add the RHV virtualization server credentials." }, "4297": { "code": 4297, - "desc": "Não foi possível to obtain RHV servidor credentials.", - "first_action": "Garanta que o RHV manager está accessible from o", - "full_action": "Garanta que o RHV manager está accessible from o\nbackuphostandthebackuphostisaddedtotheRHVAccessHostsfromNetBackup\nAdministration Console." + "desc": "Unable to obtain RHV server credentials.", + "first_action": "Ensure that the RHV manager is accessible from the", + "full_action": "Ensure that the RHV manager is accessible from the\nbackuphostandthebackuphostisaddedtotheRHVAccessHostsfromNetBackup\nAdministration Console." }, "4298": { "code": 4298, - "desc": "Não foi possível to obtain RHV manager version.", - "first_action": "Verifique o RHV versions que NetBackup supports para VM", - "full_action": "Verifique o RHV versions que NetBackup supports para VM\nbackup ou restauração. If o RHV version has changed, you might veja this falha if o\nresponse body de some RHV APIs has changed. Garanta que o RHV manager\nname has 95 ou fewer characters. Refer to o logs para more informação." + "desc": "Unable to obtain RHV manager version.", + "first_action": "Check the RHV versions that NetBackup supports for VM", + "full_action": "Check the RHV versions that NetBackup supports for VM\nbackup or restore. If the RHV version has changed, you might see this failure if the\nresponse body of some RHV APIs has changed. Ensure that the RHV manager\nname has 95 or fewer characters. Refer to the logs for more information." }, "4299": { "code": 4299, - "desc": "Não foi possível to get topology view tree.", + "desc": "Unable to get topology view tree.", "first_action": "Iftheproblempersists,contactCohesityTechnicalSupport.", "full_action": "Iftheproblempersists,contactCohesityTechnicalSupport." }, "4301": { "code": 4301, - "desc": "Single arquivo restauração está não supported para this policy type.", + "desc": "Single file restore is not supported for this policy type.", "first_action": "Disablethesinglefilerestoreoptioninthepolicyandrerun", - "full_action": "Disablethesinglefilerestoreoptioninthepolicyandrerun\no backup." + "full_action": "Disablethesinglefilerestoreoptioninthepolicyandrerun\nthe backup." }, "4302": { "code": 4302, - "desc": "O VM está unavailable on o current host. If o VM está um highly disponível VM, it may have moved to another host.", - "first_action": "When SCVMM está used to manage um VM, dynamic", - "full_action": "When SCVMM está used to manage um VM, dynamic\noptimization can trigger more frequent migration. If there estão too frequent retries\nhappening, configure VM optimization actions correctly to manage VM migrations.\nAfter you have configurado VM optimization actions, retry o operation." + "desc": "The VM is unavailable on the current host. If the VM is a highly available VM, it may have moved to another host.", + "first_action": "When SCVMM is used to manage a VM, dynamic", + "full_action": "When SCVMM is used to manage a VM, dynamic\noptimization can trigger more frequent migration. If there are too frequent retries\nhappening, configure VM optimization actions correctly to manage VM migrations.\nAfter you have configured VM optimization actions, retry the operation." }, "4307": { "code": 4307, - "desc": "Authentication erro. NetBackup legacy rede service está executando como local system.", - "first_action": "Log on to o NetBackup legacy rede service como o", - "full_action": "Log on to o NetBackup legacy rede service como o\ndomain usuário e try again." + "desc": "Authentication error. NetBackup legacy network service is running as local system.", + "first_action": "Log on to the NetBackup legacy network service as the", + "full_action": "Log on to the NetBackup legacy network service as the\ndomain user and try again." }, "4308": { "code": 4308, - "desc": "Authentication erro. O service usuário para NetBackup cliente service e NetBackup legacy rede service, must be o same. NetBackup status codes 661 NetBackup status codes", - "first_action": "Log on to o NetBackup cliente service e NetBackup", - "full_action": "Log on to o NetBackup cliente service e NetBackup\nlegacy rede service como o domain usuário e try again." + "desc": "Authentication error. The service user for NetBackup client service and NetBackup legacy network service, must be the same. NetBackup status codes 661 NetBackup status codes", + "first_action": "Log on to the NetBackup client service and NetBackup", + "full_action": "Log on to the NetBackup client service and NetBackup\nlegacy network service as the domain user and try again." }, "4309": { "code": 4309, - "desc": "Authentication erro. Não foi possível to retrieve o usuário para o service.", + "desc": "Authentication error. Unable to retrieve the user for the service.", "first_action": "RestartalloftheNetBackupservicesandtrytheoperation", "full_action": "RestartalloftheNetBackupservicesandtrytheoperation\nagain." }, "4310": { "code": 4310, - "desc": "Não é possível retrieve snapshot informação.", + "desc": "Cannot retrieve snapshot information.", "first_action": "WhileasnapshotwastakenforSANdevice,someinternal", - "full_action": "WhileasnapshotwastakenforSANdevice,someinternal\nissuesoccurred.NetBackupcannotcorrectlystorethesnapshot-relatedinformation.\nVerifique o bpfis logs e retry o operation." + "full_action": "WhileasnapshotwastakenforSANdevice,someinternal\nissuesoccurred.NetBackupcannotcorrectlystorethesnapshot-relatedinformation.\nCheck the bpfis logs and retry the operation." }, "4311": { "code": 4311, - "desc": "Thedevicelistbasedontherestoreselectiondoesnotmatchthedevice’s consistencygroup ou groups thatwere foundon thestoragearray. Rollback restauração may affect data on consistency group devices.", - "first_action": "Log on to o armazenamento array e correct o inconsistency in o consistency", - "full_action": "Executar o seguinte como appropriate:\n■ Log on to o armazenamento array e correct o inconsistency in o consistency\ngroup.\n■ To go ahead com o restauração process, use o option Force rollback even if it\ndestroys o consistency group’s state on o armazenamento array disponível in\nBackup, Archive, e Restauração GUI ou use -force_group_rollback option com\nbprestore comando. Refer to o NetBackup Commands Reference Guide to\nget more informação about this rollback option." + "desc": "Thedevicelistbasedontherestoreselectiondoesnotmatchthedevice’s consistencygroup or groups thatwere foundon thestoragearray. Rollback restore may affect data on consistency group devices.", + "first_action": "Log on to the storage array and correct the inconsistency in the consistency", + "full_action": "Perform the following as appropriate:\n■ Log on to the storage array and correct the inconsistency in the consistency\ngroup.\n■ To go ahead with the restore process, use the option Force rollback even if it\ndestroys the consistency group’s state on the storage array available in\nBackup, Archive, and Restore GUI or use -force_group_rollback option with\nbprestore command. Refer to the NetBackup Commands Reference Guide to\nget more information about this rollback option." }, "4312": { "code": 4312, - "desc": "O job did não complete because o /etc/fstab arquivo contains um entry de um backup selection in o UUID ou LABEL form.", - "first_action": "When you use o configuration que está detailed in o", - "full_action": "When you use o configuration que está detailed in o\nExplanation, de o /etc/fstab arquivo on o primary host, you must use um alternate\ncliente como backup host in o policy." + "desc": "The job did not complete because the /etc/fstab file contains an entry of a backup selection in the UUID or LABEL form.", + "first_action": "When you use the configuration that is detailed in the", + "full_action": "When you use the configuration that is detailed in the\nExplanation, of the /etc/fstab file on the primary host, you must use an alternate\nclient as backup host in the policy." }, "4313": { "code": 4313, - "desc": "O rollback restauração did não complete because o /etc/fstab arquivo contains um entry de backup selection in UUID ou LABEL form.", - "first_action": "When you use o configuration que está detailed in o", - "full_action": "When you use o configuration que está detailed in o\nExplanation, de o /etc/fstab arquivo on o primary host, you must temporarily\nremove o policy backup selection entry from o /etc/fstab arquivo. After remoção\noftheentry,retrytherollbackrestoreagain.Whentherollbackrestoreissuccessful,\nyou can add o entradas back to o /etc/fstab arquivo." + "desc": "The rollback restore did not complete because the /etc/fstab file contains an entry of backup selection in UUID or LABEL form.", + "first_action": "When you use the configuration that is detailed in the", + "full_action": "When you use the configuration that is detailed in the\nExplanation, of the /etc/fstab file on the primary host, you must temporarily\nremove the policy backup selection entry from the /etc/fstab file. After removal\noftheentry,retrytherollbackrestoreagain.Whentherollbackrestoreissuccessful,\nyou can add the entries back to the /etc/fstab file." }, "4315": { "code": 4315, - "desc": "Não é possível replicate o on-premises snapshot.", - "first_action": "Retry o operation e if o issue persists, visit", - "full_action": "Retry o operation e if o issue persists, visit\nsupport.veritas.com. O Cohesity Technical Support website site offers additional\ninformação to help you troubleshoot this issue." + "desc": "Cannot replicate the on-premises snapshot.", + "first_action": "Retry the operation and if the issue persists, visit", + "full_action": "Retry the operation and if the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support website site offers additional\ninformation to help you troubleshoot this issue." }, "4500": { "code": 4500, - "desc": "O number de images to be imported está more than o limite.", - "first_action": "Reduce o number de images to import to 64 ou fewer.", - "full_action": "Reduce o number de images to import to 64 ou fewer." + "desc": "The number of images to be imported is more than the limit.", + "first_action": "Reduce the number of images to import to 64 or fewer.", + "full_action": "Reduce the number of images to import to 64 or fewer." }, "4501": { "code": 4501, - "desc": "Incorrect mídia ID está used while importing o image.", - "first_action": "Use o correct mídia ID while importing o image. Use", - "full_action": "Use o correct mídia ID while importing o image. Use\no bpmedialist comando to get o informação." + "desc": "Incorrect media ID is used while importing the image.", + "first_action": "Use the correct media ID while importing the image. Use", + "full_action": "Use the correct media ID while importing the image. Use\nthe bpmedialist command to get the information." }, "4502": { "code": 4502, - "desc": "Inválido informação about o master ou o mídia servidor. NetBackup status codes 664 NetBackup status codes", - "first_action": "Use o correct host name during o image import.", - "full_action": "Use o correct host name during o image import." + "desc": "Invalid information about the master or the media server. NetBackup status codes 664 NetBackup status codes", + "first_action": "Use the correct host name during the image import.", + "full_action": "Use the correct host name during the image import." }, "4503": { "code": 4503, "desc": "Current active job count exceeds active job count limitation.", - "first_action": "Wait para o import job to finish before qualquer new import", - "full_action": "Wait para o import job to finish before qualquer new import\njobs estão initiated." + "first_action": "Wait for the import job to finish before any new import", + "full_action": "Wait for the import job to finish before any new import\njobs are initiated." }, "4504": { "code": 4504, - "desc": "O number de images to import está zero.", - "first_action": "Aumentar o number de images to import.", - "full_action": "Aumentar o number de images to import." + "desc": "The number of images to import is zero.", + "first_action": "Increase the number of images to import.", + "full_action": "Increase the number of images to import." }, "4505": { "code": 4505, - "desc": "Input cliente name está inconsistent com cliente name in backup ID.", - "first_action": "Verifique que you used o correct cliente name e backup", - "full_action": "Verifique que you used o correct cliente name e backup\nID when you imported ou recovered images." + "desc": "Input client name is inconsistent with client name in backup ID.", + "first_action": "Verify that you used the correct client name and backup", + "full_action": "Verify that you used the correct client name and backup\nID when you imported or recovered images." }, "4506": { "code": 4506, - "desc": "Falhou to get images from cloud armazenamento.", - "first_action": "Retry o operation e if o issue persists, visit o", - "full_action": "Retry o operation e if o issue persists, visit o\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional informação to help you troubleshoot this issue." + "desc": "Failed to get images from cloud storage.", + "first_action": "Retry the operation and if the issue persists, visit the", + "full_action": "Retry the operation and if the issue persists, visit the\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional information to help you troubleshoot this issue." }, "4507": { "code": 4507, - "desc": "Falhou to reload MSDP metadata.", - "first_action": "Retry o operation e if o issue persists, visit o", - "full_action": "Retry o operation e if o issue persists, visit o\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional informação to help you troubleshoot this issue." + "desc": "Failed to reload MSDP metadata.", + "first_action": "Retry the operation and if the issue persists, visit the", + "full_action": "Retry the operation and if the issue persists, visit the\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional information to help you troubleshoot this issue." }, "4508": { "code": 4508, - "desc": "Falhou to get AMI IDs from AWS.", - "first_action": "Verifique seu rede conexão to Amazon Web Service.", - "full_action": "Verifique seu rede conexão to Amazon Web Service.\nRetry o operation e if o issue persists, visit o Cohesity Technical Support\nwebsite. O Cohesity Technical Support website offers additional informação to\nhelp you troubleshoot this issue." + "desc": "Failed to get AMI IDs from AWS.", + "first_action": "Verify your network connection to Amazon Web Service.", + "full_action": "Verify your network connection to Amazon Web Service.\nRetry the operation and if the issue persists, visit the Cohesity Technical Support\nwebsite. The Cohesity Technical Support website offers additional information to\nhelp you troubleshoot this issue." }, "4509": { "code": 4509, - "desc": "Falhou to get DR in cloud status.", - "first_action": "Retry o operation e if o issue persists, visit o", - "full_action": "Retry o operation e if o issue persists, visit o\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional informação to help you troubleshoot this issue." + "desc": "Failed to get DR in cloud status.", + "first_action": "Retry the operation and if the issue persists, visit the", + "full_action": "Retry the operation and if the issue persists, visit the\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional information to help you troubleshoot this issue." }, "4510": { "code": 4510, - "desc": "Cloud DR LSU name está não specified.", - "first_action": "Specify o LSU name para o cloud DR in o request de", - "full_action": "Specify o LSU name para o cloud DR in o request de\no RESTful API." + "desc": "Cloud DR LSU name is not specified.", + "first_action": "Specify the LSU name for the cloud DR in the request of", + "full_action": "Specify the LSU name for the cloud DR in the request of\nthe RESTful API." }, "4511": { "code": 4511, - "desc": "Specified cloud DR LSU name does não exist.", - "first_action": "Use o correct LSU name in o request de RESTful API.", - "full_action": "Use o correct LSU name in o request de RESTful API." + "desc": "Specified cloud DR LSU name does not exist.", + "first_action": "Use the correct LSU name in the request of RESTful API.", + "full_action": "Use the correct LSU name in the request of RESTful API." }, "4512": { "code": 4512, - "desc": "Não cloud DR LSU está present.", - "first_action": "Configure um cloud DR LSU in o NetBackup servidor.", - "full_action": "Configure um cloud DR LSU in o NetBackup servidor." + "desc": "No cloud DR LSU is present.", + "first_action": "Configure a cloud DR LSU in the NetBackup server.", + "full_action": "Configure a cloud DR LSU in the NetBackup server." }, "4513": { "code": 4513, - "desc": "Input LSU name must be um string.", - "first_action": "Set o LSU name to o correct JSON formatted string", - "full_action": "Set o LSU name to o correct JSON formatted string\nin o POST body de o RESTful API." + "desc": "Input LSU name must be a string.", + "first_action": "Set the LSU name to the correct JSON formatted string", + "full_action": "Set the LSU name to the correct JSON formatted string\nin the POST body of the RESTful API." }, "4514": { "code": 4514, - "desc": "Falhou to get armazenamento servers.", - "first_action": "Retry o operation e if o issue persists, visit o", - "full_action": "Retry o operation e if o issue persists, visit o\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional informação to help you troubleshoot this issue." + "desc": "Failed to get storage servers.", + "first_action": "Retry the operation and if the issue persists, visit the", + "full_action": "Retry the operation and if the issue persists, visit the\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional information to help you troubleshoot this issue." }, "4515": { "code": 4515, - "desc": "Armazenamento servidor name está não specified.", - "first_action": "Specify o armazenamento servidor name para o cloud DR in o", - "full_action": "Specify o armazenamento servidor name para o cloud DR in o\nrequest de o RESTful API." + "desc": "Storage server name is not specified.", + "first_action": "Specify the storage server name for the cloud DR in the", + "full_action": "Specify the storage server name for the cloud DR in the\nrequest of the RESTful API." }, "4516": { "code": 4516, - "desc": "Specified armazenamento servidor name does não exist.", - "first_action": "Use o correct armazenamento servidor name in o request de o", - "full_action": "Use o correct armazenamento servidor name in o request de o\nRESTful API." + "desc": "Specified storage server name does not exist.", + "first_action": "Use the correct storage server name in the request of the", + "full_action": "Use the correct storage server name in the request of the\nRESTful API." }, "4517": { "code": 4517, - "desc": "Não armazenamento servidor está present.", - "first_action": "Configure um armazenamento servidor in NetBackup.", - "full_action": "Configure um armazenamento servidor in NetBackup." + "desc": "No storage server is present.", + "first_action": "Configure a storage server in NetBackup.", + "full_action": "Configure a storage server in NetBackup." }, "4518": { "code": 4518, - "desc": "Input armazenamento servidor name must be um string.", + "desc": "Input storage server name must be a string.", "first_action": "SetthestorageservernametothecorrectJSONformatted", - "full_action": "SetthestorageservernametothecorrectJSONformatted\nstring in o POST body de o RESTful API." + "full_action": "SetthestorageservernametothecorrectJSONformatted\nstring in the POST body of the RESTful API." }, "4519": { "code": 4519, - "desc": "Falhou to get active import job count.", - "first_action": "Retry o operation e if o issue persists, visit o", - "full_action": "Retry o operation e if o issue persists, visit o\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional informação to help you troubleshoot this issue." + "desc": "Failed to get active import job count.", + "first_action": "Retry the operation and if the issue persists, visit the", + "full_action": "Retry the operation and if the issue persists, visit the\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional information to help you troubleshoot this issue." }, "4520": { "code": 4520, - "desc": "This operation está não supported on current cloud provider.", - "first_action": "Review seu request e confirm que it está supported on", - "full_action": "Review seu request e confirm que it está supported on\no cloud provider." + "desc": "This operation is not supported on current cloud provider.", + "first_action": "Review your request and confirm that it is supported on", + "full_action": "Review your request and confirm that it is supported on\nthe cloud provider." }, "4521": { "code": 4521, - "desc": "This operation está não supported on solicitado workload.", - "first_action": "Review que o solicitado workload está supported on o", - "full_action": "Review que o solicitado workload está supported on o\nRESTful API." + "desc": "This operation is not supported on requested workload.", + "first_action": "Review that the requested workload is supported on the", + "full_action": "Review that the requested workload is supported on the\nRESTful API." }, "4604": { "code": 4604, - "desc": "You do não have o requerido permissions to excluir o license key.", - "first_action": "Verifique que you have sufficient permissions para o excluir", - "full_action": "Verifique que you have sufficient permissions para o excluir\nlicensefileoperation.Verifythatthelicensefilehassufficientpermissionsfordelete\noperation." + "desc": "You do not have the required permissions to delete the license key.", + "first_action": "Verify that you have sufficient permissions for the delete", + "full_action": "Verify that you have sufficient permissions for the delete\nlicensefileoperation.Verifythatthelicensefilehassufficientpermissionsfordelete\noperation." }, "4605": { "code": 4605, - "desc": "O license key não é possível be deleted.", - "first_action": "Review o OS-based erro e take appropriate ação.", - "full_action": "Review o OS-based erro e take appropriate ação." + "desc": "The license key cannot be deleted.", + "first_action": "Review the OS-based error and take appropriate action.", + "full_action": "Review the OS-based error and take appropriate action." }, "4606": { "code": 4606, - "desc": "O specified entitlement ID does não exist.", - "first_action": "Verifique que o ID specified está correct.", - "full_action": "Verifique que o ID specified está correct." + "desc": "The specified entitlement ID does not exist.", + "first_action": "Verify that the ID specified is correct.", + "full_action": "Verify that the ID specified is correct." }, "4607": { "code": 4607, - "desc": "ThespecifiedoperationontheNetBackupentitlementcannotbecarried fora.", - "first_action": "Verifique o erro details mentioned in RESTful API response e executar", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o erro details mentioned in RESTful API response e executar\nnecessary corrective ação.\n■ Retry o operation e if o issue persists, visit support.veritas.com. O\nCohesity Technical Support website site offers additional informação to help\nyou troubleshoot this issue." + "desc": "ThespecifiedoperationontheNetBackupentitlementcannotbecarried out.", + "first_action": "Check the error details mentioned in RESTful API response and perform", + "full_action": "Perform the following as appropriate:\n■ Check the error details mentioned in RESTful API response and perform\nnecessary corrective action.\n■ Retry the operation and if the issue persists, visit support.veritas.com. The\nCohesity Technical Support website site offers additional information to help\nyou troubleshoot this issue." }, "4608": { "code": 4608, - "desc": "License com o specified entitlement ID already exists in NetBackup.", - "first_action": "Excluir o existing license if it está necessary to add it to", - "full_action": "Excluir o existing license if it está necessary to add it to\nNetBackup again. Não ação está needed when o addition de o license está não\nnecessary." + "desc": "License with the specified entitlement ID already exists in NetBackup.", + "first_action": "Delete the existing license if it is necessary to add it to", + "full_action": "Delete the existing license if it is necessary to add it to\nNetBackup again. No action is needed when the addition of the license is not\nnecessary." }, "4609": { "code": 4609, - "desc": "O specified license arquivo está corrupted.", - "first_action": "You must use o license arquivo que está downloaded from o", - "full_action": "You must use o license arquivo que está downloaded from o\nCohesity licensing portal e add it to o NetBackup software." + "desc": "The specified license file is corrupted.", + "first_action": "You must use the license file that is downloaded from the", + "full_action": "You must use the license file that is downloaded from the\nCohesity licensing portal and add it to the NetBackup software." }, "4610": { "code": 4610, - "desc": "O entitlements do não exist in NetBackup.", - "first_action": "Verifique que you have at least one license in NetBackup.", - "full_action": "Verifique que you have at least one license in NetBackup." + "desc": "The entitlements do not exist in NetBackup.", + "first_action": "Verify that you have at least one license in NetBackup.", + "full_action": "Verify that you have at least one license in NetBackup." }, "4611": { "code": 4611, - "desc": "Não é possível add new license when um existing license de um different edition está present.", + "desc": "Cannot add new license when an existing license of a different edition is present.", "first_action": "Makesurethatlicensesofdifferenteditionsarenotadded", - "full_action": "Makesurethatlicensesofdifferenteditionsarenotadded\nat o same time. Make sure que o perpetual license não é possível be added on to o\nsubscription license." + "full_action": "Makesurethatlicensesofdifferenteditionsarenotadded\nat the same time. Make sure that the perpetual license cannot be added on to the\nsubscription license." }, "4612": { "code": 4612, - "desc": "O expired license não é possível be added.", - "first_action": "Make sure que o license está não expired e renew o license before you add um", - "full_action": "Executar o seguinte como appropriate:\nMake sure que o license está não expired e renew o license before you add um\nnew license." + "desc": "The expired license cannot be added.", + "first_action": "Make sure that the license is not expired and renew the license before you add a", + "full_action": "Perform the following as appropriate:\nMake sure that the license is not expired and renew the license before you add a\nnew license." }, "4700": { "code": 4700, - "desc": "Não foi possível to attach restored disks to target VM.", - "first_action": "Verifique o RHV, VMware, ou Nutanix AHV versions", - "full_action": "Verifique o RHV, VMware, ou Nutanix AHV versions\nNetBackupsupportsforVMbackup ou restore.RefertothebpVMutil logs formore\ninformação e if o issue persists, visit o Cohesity Technical Support website.\nO Cohesity Technical Support website offers additional informação to help you\ntroubleshoot this issue." + "desc": "Unable to attach restored disks to target VM.", + "first_action": "Check the RHV, VMware, or Nutanix AHV versions", + "full_action": "Check the RHV, VMware, or Nutanix AHV versions\nNetBackupsupportsforVMbackup or restore.RefertothebpVMutil logs formore\ninformation and if the issue persists, visit the Cohesity Technical Support website.\nThe Cohesity Technical Support website offers additional information to help you\ntroubleshoot this issue." }, "4701": { "code": 4701, - "desc": "Não foi possível to get virtual machine configuration para VM. NetBackup status codes 672 NetBackup status codes", - "first_action": "Retry o operation e if o issue persists, visit o", - "full_action": "Retry o operation e if o issue persists, visit o\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional informação to help you troubleshoot this issue." + "desc": "Unable to get virtual machine configuration for VM. NetBackup status codes 672 NetBackup status codes", + "first_action": "Retry the operation and if the issue persists, visit the", + "full_action": "Retry the operation and if the issue persists, visit the\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional information to help you troubleshoot this issue." }, "4702": { "code": 4702, - "desc": "Excluir de existing VM falhou com erro.", - "first_action": "Garanta que o VM está turned off. If possible, try to excluir", - "full_action": "Garanta que o VM está turned off. If possible, try to excluir\no VM manually e then run o restauração operation. Refer to o bpVMutil logs\npara more informação e contate Cohesity Technical Support if requerido." + "desc": "Delete of existing VM failed with error.", + "first_action": "Ensure that the VM is turned off. If possible, try to delete", + "full_action": "Ensure that the VM is turned off. If possible, try to delete\nthe VM manually and then run the restore operation. Refer to the bpVMutil logs\nfor more information and contact Cohesity Technical Support if required." }, "4703": { "code": 4703, - "desc": "Virtual machine creation falhou, não é possível proceed com restauração.", - "first_action": "Garanta que enough resources estão disponível on o RHV,", - "full_action": "Garanta que enough resources estão disponível on o RHV,\nVMware, ou Nutanix AHV servidor para o creation de o VM. Refer to o bpVMutil\nlogs para more informação e if o issue persists, visit o Cohesity Technical\nSupport website. O Cohesity Technical Support website offers additional\ninformação to help you troubleshoot this issue." + "desc": "Virtual machine creation failed, cannot proceed with restore.", + "first_action": "Ensure that enough resources are available on the RHV,", + "full_action": "Ensure that enough resources are available on the RHV,\nVMware, or Nutanix AHV server for the creation of the VM. Refer to the bpVMutil\nlogs for more information and if the issue persists, visit the Cohesity Technical\nSupport website. The Cohesity Technical Support website offers additional\ninformation to help you troubleshoot this issue." }, "4704": { "code": 4704, - "desc": "Falhou to create virtual machine com specified disks.", - "first_action": "Garanta que enough resources estão disponível on o RHV", - "full_action": "Garanta que enough resources estão disponível on o RHV\nservidor para creation de o disks. Refer to o bpVMutil logs para more informação\ne contate Cohesity Technical Support if requerido." + "desc": "Failed to create virtual machine with specified disks.", + "first_action": "Ensure that enough resources are available on the RHV", + "full_action": "Ensure that enough resources are available on the RHV\nserver for creation of the disks. Refer to the bpVMutil logs for more information\nand contact Cohesity Technical Support if required." }, "4705": { "code": 4705, - "desc": "Não foi possível to retrieve virtual disco configuration.", + "desc": "Unable to retrieve virtual disk configuration.", "first_action": "Iftheproblempersists,contactCohesityTechnicalSupport.", "full_action": "Iftheproblempersists,contactCohesityTechnicalSupport." }, "4706": { "code": 4706, - "desc": "Incorrect virtual disco configuration retrieved.", - "first_action": "Garanta que o disks que estão specified in o rename arquivo", - "full_action": "Garanta que o disks que estão specified in o rename arquivo\nfollow o correct syntax como per specification. Refer to o bpVMutil logs para more\ninformação e contate Cohesity Technical Support if requerido." + "desc": "Incorrect virtual disk configuration retrieved.", + "first_action": "Ensure that the disks that are specified in the rename file", + "full_action": "Ensure that the disks that are specified in the rename file\nfollow the correct syntax as per specification. Refer to the bpVMutil logs for more\ninformation and contact Cohesity Technical Support if required." }, "4707": { "code": 4707, - "desc": "Não foi possível to attach restored networks to target VM.", - "first_action": "Verifique o RHV, VMware, ou Nutanix AHV versions que", - "full_action": "Verifique o RHV, VMware, ou Nutanix AHV versions que\nNetBackupsupportsforVMbackup ou restore.RefertothebpVMutil logs formore\ninformação e if o issue persists, visit o Cohesity Technical Support website.\nO Cohesity Technical Support website offers additional informação to help you\ntroubleshoot this issue." + "desc": "Unable to attach restored networks to target VM.", + "first_action": "Check the RHV, VMware, or Nutanix AHV versions that", + "full_action": "Check the RHV, VMware, or Nutanix AHV versions that\nNetBackupsupportsforVMbackup or restore.RefertothebpVMutil logs formore\ninformation and if the issue persists, visit the Cohesity Technical Support website.\nThe Cohesity Technical Support website offers additional information to help you\ntroubleshoot this issue." }, "4708": { "code": 4708, - "desc": "Não foi possível to attach restored tags to target VM.", - "first_action": "Verifique o RHV, VMware, ou Nutanix AHV versions que", - "full_action": "Verifique o RHV, VMware, ou Nutanix AHV versions que\nNetBackupsupportsforVMbackup ou restore.RefertothebpVMutil logs formore\ninformação e if o issue persists, visit o Cohesity Technical Support website.\nO Cohesity Technical Support website offers additional informação to help you\ntroubleshoot this issue." + "desc": "Unable to attach restored tags to target VM.", + "first_action": "Check the RHV, VMware, or Nutanix AHV versions that", + "full_action": "Check the RHV, VMware, or Nutanix AHV versions that\nNetBackupsupportsforVMbackup or restore.RefertothebpVMutil logs formore\ninformation and if the issue persists, visit the Cohesity Technical Support website.\nThe Cohesity Technical Support website offers additional information to help you\ntroubleshoot this issue." }, "4709": { "code": 4709, - "desc": "Não foi possível to set high availability option on target VM.", - "first_action": "Verifique o RHV, VMware, ou Nutanix AHV versions que", - "full_action": "Verifique o RHV, VMware, ou Nutanix AHV versions que\nNetBackupsupportsforVMbackup ou restore.RefertothebpVMutil logs formore\ninformação e if o issue persists, visit o Cohesity Technical Support website.\nO Cohesity Technical Support website offers additional informação to help you\ntroubleshoot this issue." + "desc": "Unable to set high availability option on target VM.", + "first_action": "Check the RHV, VMware, or Nutanix AHV versions that", + "full_action": "Check the RHV, VMware, or Nutanix AHV versions that\nNetBackupsupportsforVMbackup or restore.RefertothebpVMutil logs formore\ninformation and if the issue persists, visit the Cohesity Technical Support website.\nThe Cohesity Technical Support website offers additional information to help you\ntroubleshoot this issue." }, "4710": { "code": 4710, - "desc": "Falhou to get VM Tags Informação.", - "first_action": "Verifique o RHV, VMware, ou Nutanix AHV versions que", - "full_action": "Verifique o RHV, VMware, ou Nutanix AHV versions que\nNetBackupsupportsforVMbackup ou restore.RefertothebpVMutil logs formore\ninformação e if o issue persists, visit o Cohesity Technical Support website.\nO Cohesity Technical Support website offers additional informação to help you\ntroubleshoot this issue." + "desc": "Failed to get VM Tags Information.", + "first_action": "Check the RHV, VMware, or Nutanix AHV versions that", + "full_action": "Check the RHV, VMware, or Nutanix AHV versions that\nNetBackupsupportsforVMbackup or restore.RefertothebpVMutil logs formore\ninformation and if the issue persists, visit the Cohesity Technical Support website.\nThe Cohesity Technical Support website offers additional information to help you\ntroubleshoot this issue." }, "4711": { "code": 4711, - "desc": "CURLencounteredanerror.Insufficientmemoryorinadequateresources disponível to complete o job.", + "desc": "CURLencounteredanerror.Insufficientmemoryorinadequateresources available to complete the job.", "first_action": "Iftheproblempersists,contactCohesityTechnicalSupport.", "full_action": "Iftheproblempersists,contactCohesityTechnicalSupport." }, "4712": { "code": 4712, - "desc": "Resource name está vazio.", - "first_action": "Enter o appropriate VM display name. Refer to o", - "full_action": "Enter o appropriate VM display name. Refer to o\nbpVMutil logs para more informação e contate Cohesity Technical Support if\nrequerido." + "desc": "Resource name is empty.", + "first_action": "Enter the appropriate VM display name. Refer to the", + "full_action": "Enter the appropriate VM display name. Refer to the\nbpVMutil logs for more information and contact Cohesity Technical Support if\nrequired." }, "4713": { "code": 4713, "desc": "Resource name contains unsupported characters.", - "first_action": "Use supported characters in o VM display name. Refer", - "full_action": "Use supported characters in o VM display name. Refer\nto o bpVMutil logs para more informação e contate Cohesity Technical Support\nif requerido." + "first_action": "Use supported characters in the VM display name. Refer", + "full_action": "Use supported characters in the VM display name. Refer\nto the bpVMutil logs for more information and contact Cohesity Technical Support\nif required." }, "4714": { "code": 4714, "desc": "Resource name length exceeds supported maximum length.", - "first_action": "Garanta que o length de o VM display name está within", - "full_action": "Garanta que o length de o VM display name está within\no supported length. Refer to o bpVMutil logs para more informação e contate\nCohesity Technical Support if requerido." + "first_action": "Ensure that the length of the VM display name is within", + "full_action": "Ensure that the length of the VM display name is within\nthe supported length. Refer to the bpVMutil logs for more information and contact\nCohesity Technical Support if required." }, "4715": { "code": 4715, - "desc": "Pre-recovery verifique falha.", + "desc": "Pre-recovery check failure.", "first_action": "Iftheproblempersists,contactCohesityTechnicalSupport.", "full_action": "Iftheproblempersists,contactCohesityTechnicalSupport." }, "4716": { "code": 4716, "desc": "Unsupported hypervisor type.", - "first_action": "Refer to o bpVMutil logs para more informação. If o", - "full_action": "Refer to o bpVMutil logs para more informação. If o\nproblema persists, contate Cohesity Technical Support." + "first_action": "Refer to the bpVMutil logs for more information. If the", + "full_action": "Refer to the bpVMutil logs for more information. If the\nproblem persists, contact Cohesity Technical Support." }, "4718": { "code": 4718, - "desc": "Inválido API request parâmetro.", + "desc": "Invalid API request parameter.", "first_action": "Iftheproblempersists,contactCohesityTechnicalSupport.", "full_action": "Iftheproblempersists,contactCohesityTechnicalSupport." }, "4719": { "code": 4719, - "desc": "Não foi possível to ler e understand virtual disco metadata.", - "first_action": "Verifique o disco types que estão attached to VM e make", - "full_action": "Verifique o disco types que estão attached to VM e make\nsurethatNetBackupsupportsthediskformat.Verifythatthedisksthatareattached\nto VMs estão properly visible inside o VM." + "desc": "Unable to read and understand virtual disk metadata.", + "first_action": "Check the disk types that are attached to VM and make", + "full_action": "Check the disk types that are attached to VM and make\nsurethatNetBackupsupportsthediskformat.Verifythatthedisksthatareattached\nto VMs are properly visible inside the VM." }, "4720": { "code": 4720, - "desc": "Encrypted Virtual Disco está não supported.", - "first_action": "Verifique o list de options que NetBackup supports para", - "full_action": "Verifique o list de options que NetBackup supports para\nbacking up o RHV, VMware, ou Nutanix AHV VMs." + "desc": "Encrypted Virtual Disk is not supported.", + "first_action": "Verify the list of options that NetBackup supports for", + "full_action": "Verify the list of options that NetBackup supports for\nbacking up the RHV, VMware, or Nutanix AHV VMs." }, "4721": { "code": 4721, - "desc": "Compressed Virtual Disco está não supported.", - "first_action": "Verifique o list de options que NetBackup supports para", - "full_action": "Verifique o list de options que NetBackup supports para\nbacking up o RHV, VMware, ou Nutanix AHV VMs." + "desc": "Compressed Virtual Disk is not supported.", + "first_action": "Verify the list of options that NetBackup supports for", + "full_action": "Verify the list of options that NetBackup supports for\nbacking up the RHV, VMware, or Nutanix AHV VMs." }, "4722": { "code": 4722, - "desc": "Falhou to ler from Virtual Disco.", - "first_action": "Retry o backup operation. Refer to o vxms logs para", - "full_action": "Retry o backup operation. Refer to o vxms logs para\nmore informação about o erro." + "desc": "Failed to read from Virtual Disk.", + "first_action": "Retry the backup operation. Refer to the vxms logs for", + "full_action": "Retry the backup operation. Refer to the vxms logs for\nmore information about the error." }, "4723": { "code": 4723, - "desc": "Falhou to gravar into Virtual Disco.", - "first_action": "Retry o restauração operation. Refer to o vxms logs para", - "full_action": "Retry o restauração operation. Refer to o vxms logs para\nmore informação about o erro." + "desc": "Failed to write into Virtual Disk.", + "first_action": "Retry the restore operation. Refer to the vxms logs for", + "full_action": "Retry the restore operation. Refer to the vxms logs for\nmore information about the error." }, "4724": { "code": 4724, - "desc": "Inválido Disco Transfer Info.", - "first_action": "Refer to o vxms logs para more informação about this", - "full_action": "Refer to o vxms logs para more informação about this\nerro e if o issue persists, visit o Cohesity Technical Support website. O\nCohesity Technical Support website offers additional informação to help you\ntroubleshoot this issue." + "desc": "Invalid Disk Transfer Info.", + "first_action": "Refer to the vxms logs for more information about this", + "full_action": "Refer to the vxms logs for more information about this\nerror and if the issue persists, visit the Cohesity Technical Support website. The\nCohesity Technical Support website offers additional information to help you\ntroubleshoot this issue." }, "4725": { "code": 4725, - "desc": "Um internal erro ocorreu.", - "first_action": "Retry o operation. Refer to o vxms ou vfms logs para", - "full_action": "Retry o operation. Refer to o vxms ou vfms logs para\nmore informação." + "desc": "An internal error occurred.", + "first_action": "Retry the operation. Refer to the vxms or vfms logs for", + "full_action": "Retry the operation. Refer to the vxms or vfms logs for\nmore information." }, "4726": { "code": 4726, - "desc": "Falhou to create snapshot de o specified VM.", - "first_action": "Make sure que o VM está unlocked before o backup", - "full_action": "Make sure que o VM está unlocked before o backup\nstarts. Try to create temporary usuário snapshot to make sure que there está não issue\nwiththeRHVplatform.RefertothevxmslogsorcontactCohesityTechnicalSupport\nif requerido.\nBefore um CDP backup job runs, make sure que there está não issue com o nbcctd\nservice. Review o job details in o activity monitor ou o bpfis e nbcctd logs\non CDP gateway para more details." + "desc": "Failed to create snapshot of the specified VM.", + "first_action": "Make sure that the VM is unlocked before the backup", + "full_action": "Make sure that the VM is unlocked before the backup\nstarts. Try to create temporary user snapshot to make sure that there is no issue\nwiththeRHVplatform.RefertothevxmslogsorcontactCohesityTechnicalSupport\nif required.\nBefore a CDP backup job runs, make sure that there is no issue with the nbcctd\nservice. Review the job details in the activity monitor or the bpfis and nbcctd logs\non CDP gateway for more details." }, "4727": { "code": 4727, - "desc": "Falhou to fetch VM snapshot informação.", - "first_action": "Verifique o virtualization servidor events ou logs para more", - "full_action": "Verifique o virtualization servidor events ou logs para more\ninformação about this erro." + "desc": "Failed to fetch VM snapshot information.", + "first_action": "Check the virtualization server events or logs for more", + "full_action": "Check the virtualization server events or logs for more\ninformation about this error." }, "4728": { "code": 4728, - "desc": "Falhou to abrir o specified disco.", - "first_action": "If it está o backup operation, verifique if o VM disks estão", - "full_action": "If it está o backup operation, verifique if o VM disks estão\nunlocked before o backup starts. Follow o RHV, VMware, ou Nutanix AHV\ndocumentation to unlock o disco ou VMs if requerido e retry o backup. If it está o\nrestoreoperation,refertothevxmslogsformoreinformationandiftheissuepersists,\nvisit o Cohesity Technical Support website. O Cohesity Technical Support\nwebsite offers additional informação to help you troubleshoot this issue." + "desc": "Failed to open the specified disk.", + "first_action": "If it is the backup operation, check if the VM disks are", + "full_action": "If it is the backup operation, check if the VM disks are\nunlocked before the backup starts. Follow the RHV, VMware, or Nutanix AHV\ndocumentation to unlock the disk or VMs if required and retry the backup. If it is the\nrestoreoperation,refertothevxmslogsformoreinformationandiftheissuepersists,\nvisit the Cohesity Technical Support website. The Cohesity Technical Support\nwebsite offers additional information to help you troubleshoot this issue." }, "4729": { "code": 4729, - "desc": "Falhou to ler o specified disco.", - "first_action": "Refer to o vxms logs para more informação about this", - "full_action": "Refer to o vxms logs para more informação about this\nerro e if o issue persists, visit o Cohesity Technical Support website. O\nCohesity Technical Support website offers additional informação to help you\ntroubleshoot this issue." + "desc": "Failed to read the specified disk.", + "first_action": "Refer to the vxms logs for more information about this", + "full_action": "Refer to the vxms logs for more information about this\nerror and if the issue persists, visit the Cohesity Technical Support website. The\nCohesity Technical Support website offers additional information to help you\ntroubleshoot this issue." }, "4730": { "code": 4730, - "desc": "Falhou to fechar o specified disco.", - "first_action": "Verifique o virtualization servidor events ou logs para more", - "full_action": "Verifique o virtualization servidor events ou logs para more\ninformação about this erro." + "desc": "Failed to close the specified disk.", + "first_action": "Check the virtualization server events or logs for more", + "full_action": "Check the virtualization server events or logs for more\ninformation about this error." }, "4731": { "code": 4731, - "desc": "Received inválido response.", - "first_action": "Verifique o RHV versions que NetBackup supports para", - "full_action": "Verifique o RHV versions que NetBackup supports para\nbackupandrestore.Refertothelogsformoreinformationandthenretrythebackup\nou restauração operation." + "desc": "Received invalid response.", + "first_action": "Check the RHV versions that NetBackup supports for", + "full_action": "Check the RHV versions that NetBackup supports for\nbackupandrestore.Refertothelogsformoreinformationandthenretrythebackup\nor restore operation." }, "4732": { "code": 4732, - "desc": "Erro in parsing o HTTP response.", - "first_action": "Verifique o RHV, VMware, ou Nutanix AHV versions que", - "full_action": "Verifique o RHV, VMware, ou Nutanix AHV versions que\nNetBackup supports para VM backup e restauração. If o version has changed, you\nmight veja this falha if o response body de some APIs has changed. Refer to o\nlogs para more informação e if o issue persists, visit o Cohesity Technical\nSupport website. O Cohesity Technical Support website offers additional\ninformação to help you troubleshoot this issue." + "desc": "Error in parsing the HTTP response.", + "first_action": "Check the RHV, VMware, or Nutanix AHV versions that", + "full_action": "Check the RHV, VMware, or Nutanix AHV versions that\nNetBackup supports for VM backup and restore. If the version has changed, you\nmight see this failure if the response body of some APIs has changed. Refer to the\nlogs for more information and if the issue persists, visit the Cohesity Technical\nSupport website. The Cohesity Technical Support website offers additional\ninformation to help you troubleshoot this issue." }, "4733": { "code": 4733, - "desc": "Operation falhou due to locked status de VM.", - "first_action": "Retry o backup operation. Make sure que o VM", - "full_action": "Retry o backup operation. Make sure que o VM\nsnapshot creation operation happens properly on o RHV servidor. Try creating um\nVMsnapshotmanuallyfromtheRHVmanagementconsole.Ifthesnapshotcreation\noperationisunresponsive,contactRHVsupport.Ifthesnapshotiscreatedproperly,\nretry o backup operation." + "desc": "Operation failed due to locked status of VM.", + "first_action": "Retry the backup operation. Make sure that the VM", + "full_action": "Retry the backup operation. Make sure that the VM\nsnapshot creation operation happens properly on the RHV server. Try creating a\nVMsnapshotmanuallyfromtheRHVmanagementconsole.Ifthesnapshotcreation\noperationisunresponsive,contactRHVsupport.Ifthesnapshotiscreatedproperly,\nretry the backup operation." }, "4734": { "code": 4734, - "desc": "Falhou to update catalog metadata de VM.", - "first_action": "Contate Cohesity Technical Support para assistance.", - "full_action": "Contate Cohesity Technical Support para assistance." + "desc": "Failed to update catalog metadata of VM.", + "first_action": "Contact Cohesity Technical Support for assistance.", + "full_action": "Contact Cohesity Technical Support for assistance." }, "4735": { "code": 4735, - "desc": "Falhou to ler armazenamento details de VM.", - "first_action": "Retry o backup operation.", - "full_action": "Retry o backup operation." + "desc": "Failed to read storage details of VM.", + "first_action": "Retry the backup operation.", + "full_action": "Retry the backup operation." }, "4736": { "code": 4736, - "desc": "Falhou to set power state de VM.", - "first_action": "Try to turn on o VM manually. Refer to o bpVMutil", - "full_action": "Try to turn on o VM manually. Refer to o bpVMutil\nlogs para more informação e contate Cohesity Technical Support if requerido." + "desc": "Failed to set power state of VM.", + "first_action": "Try to turn on the VM manually. Refer to the bpVMutil", + "full_action": "Try to turn on the VM manually. Refer to the bpVMutil\nlogs for more information and contact Cohesity Technical Support if required." }, "4737": { "code": 4737, - "desc": "Não é possível create VM, VM already exists.", + "desc": "Cannot create VM, VM already exists.", "first_action": "UseadifferentVMname,deletetheexistingVM,orcreate", - "full_action": "UseadifferentVMname,deletetheexistingVM,orcreate\no VM on um alternate hypervisor. Refer to o bpVMutil logs para more informação\ne contate Cohesity Technical Support if requerido." + "full_action": "UseadifferentVMname,deletetheexistingVM,orcreate\nthe VM on an alternate hypervisor. Refer to the bpVMutil logs for more information\nand contact Cohesity Technical Support if required." }, "4739": { "code": 4739, - "desc": "Não disks estão attached to o specified VM.", - "first_action": "When you protect um VM, garanta que o VM has at least", - "full_action": "When you protect um VM, garanta que o VM has at least\none disco attached." + "desc": "No disks are attached to the specified VM.", + "first_action": "When you protect a VM, ensure that the VM has at least", + "full_action": "When you protect a VM, ensure that the VM has at least\none disk attached." }, "4740": { "code": 4740, - "desc": "Falhou to parse catalog entry.", + "desc": "Failed to parse catalog entry.", "first_action": "Iftheproblempersists,contactCohesityTechnicalSupport.", "full_action": "Iftheproblempersists,contactCohesityTechnicalSupport." }, "4741": { "code": 4741, "desc": "Access forbidden.", - "first_action": "Make sure que o credentials de o virtualization servidor", - "full_action": "Make sure que o credentials de o virtualization servidor\ndonotchangeduringthebackuporrestore.Ifthecredentialshavechanged,modify\n(ou excluir e again add) o virtualization servidor credentials in NetBackup." + "first_action": "Make sure that the credentials of the virtualization server", + "full_action": "Make sure that the credentials of the virtualization server\ndonotchangeduringthebackuporrestore.Ifthecredentialshavechanged,modify\n(or delete and again add) the virtualization server credentials in NetBackup." }, "4743": { "code": 4743, - "desc": "Inválido HTTP method.", + "desc": "Invalid HTTP method.", "first_action": "Refertothevxmslogsformoreinformation.Iftheproblem", - "full_action": "Refertothevxmslogsformoreinformation.Iftheproblem\npersists, contate Cohesity Technical Support." + "full_action": "Refertothevxmslogsformoreinformation.Iftheproblem\npersists, contact Cohesity Technical Support." }, "4744": { "code": 4744, - "desc": "Falhou to make HTTP request.", - "first_action": "Rerun o operation. If o problema persists, save todos de", - "full_action": "Rerun o operation. If o problema persists, save todos de\no erro log informação e contate Cohesity Technical Support." + "desc": "Failed to make HTTP request.", + "first_action": "Rerun the operation. If the problem persists, save all of", + "full_action": "Rerun the operation. If the problem persists, save all of\nthe error log information and contact Cohesity Technical Support." }, "4745": { "code": 4745, - "desc": "FailedtogetthesignedtickettodownloadthediskfromtheRHVserver. O disco might be in locked state.", - "first_action": "Garanta que o disco de o VM being salvo up está não in", - "full_action": "Garanta que o disco de o VM being salvo up está não in\nlocked state. If it está locked, refer to o RHV documentation to unlock it e then\nretry o backup operation." + "desc": "FailedtogetthesignedtickettodownloadthediskfromtheRHVserver. The disk might be in locked state.", + "first_action": "Ensure that the disk of the VM being backed up is not in", + "full_action": "Ensure that the disk of the VM being backed up is not in\nlocked state. If it is locked, refer to the RHV documentation to unlock it and then\nretry the backup operation." }, "4746": { "code": 4746, - "desc": "Encontrado unaligned page table entry in o Qcow2 disco. Repair o disco e retry o operation.", - "first_action": "Um unexpected alignment de page table entry in Qcow2", - "full_action": "Um unexpected alignment de page table entry in Qcow2\ndisco está observed. Garanta que o VM está up e executando com o disco attached, e\ntodos o VM disks estão properly accessible from o VM." + "desc": "Encountered unaligned page table entry in the Qcow2 disk. Repair the disk and retry the operation.", + "first_action": "An unexpected alignment of page table entry in Qcow2", + "full_action": "An unexpected alignment of page table entry in Qcow2\ndisk is observed. Ensure that the VM is up and running with the disk attached, and\nall the VM disks are properly accessible from the VM." }, "4747": { "code": 4747, - "desc": "Armazenamento domain type está undefined. Disco creation falhou", - "first_action": "Verifique o list armazenamento domain types que NetBackup", - "full_action": "Verifique o list armazenamento domain types que NetBackup\nsupports para restoring o RHV VMs." + "desc": "Storage domain type is undefined. Disk creation failed", + "first_action": "Check the list storage domain types that NetBackup", + "full_action": "Check the list storage domain types that NetBackup\nsupports for restoring the RHV VMs." }, "4748": { "code": 4748, - "desc": "Não foi possível to retrieve o VM. NetBackup status codes 684 NetBackup status codes", + "desc": "Unable to retrieve the VM. NetBackup status codes 684 NetBackup status codes", "first_action": "Ensurethatthevirtualizationservercredentialsarecorrect,", - "full_action": "Ensurethatthevirtualizationservercredentialsarecorrect,\ne o virtualization servidor está accessible from o backup host. Refer to o\nbpVMutil logs para more informação e contate Cohesity Technical Support if\nrequerido." + "full_action": "Ensurethatthevirtualizationservercredentialsarecorrect,\nand the virtualization server is accessible from the backup host. Refer to the\nbpVMutil logs for more information and contact Cohesity Technical Support if\nrequired." }, "4749": { "code": 4749, - "desc": "Não servidor credentials configurado.", - "first_action": "Add o virtualization servidor credentials to NetBackup.", - "full_action": "Add o virtualization servidor credentials to NetBackup." + "desc": "No server credentials configured.", + "first_action": "Add the virtualization server credentials to NetBackup.", + "full_action": "Add the virtualization server credentials to NetBackup." }, "4750": { "code": 4750, - "desc": "Não foi possível to obtain servidor credentials.", + "desc": "Unable to obtain server credentials.", "first_action": "Ensurethatthevirtualizationservercredentialsareadded", - "full_action": "Ensurethatthevirtualizationservercredentialsareadded\nin o Virtual Machine Servers dialog box from o NetBackup Administration\nConsole." + "full_action": "Ensurethatthevirtualizationservercredentialsareadded\nin the Virtual Machine Servers dialog box from the NetBackup Administration\nConsole." }, "4751": { "code": 4751, - "desc": "Falhou to excluir o snapshot de o specified VM.", - "first_action": "On o virtualization servidor, manually excluir o VM", - "full_action": "On o virtualization servidor, manually excluir o VM\nsnapshotthatNetBackupcreated.Ensurethatnobackupjobisrunningforbacking\nup o VM." + "desc": "Failed to delete the snapshot of the specified VM.", + "first_action": "On the virtualization server, manually delete the VM", + "full_action": "On the virtualization server, manually delete the VM\nsnapshotthatNetBackupcreated.Ensurethatnobackupjobisrunningforbacking\nup the VM." }, "4755": { "code": 4755, - "desc": "Não foi possível to obtain servidor version.", - "first_action": "Garanta que o provided host details (host name, IP, e", - "full_action": "Garanta que o provided host details (host name, IP, e\nport number) estão correct. Also garanta que o host está active e executando." + "desc": "Unable to obtain server version.", + "first_action": "Ensure that the provided host details (host name, IP, and", + "full_action": "Ensure that the provided host details (host name, IP, and\nport number) are correct. Also ensure that the host is active and running." }, "4769": { "code": 4769, - "desc": "Não foi possível to retrieve o list de containers.", - "first_action": "Garanta que you have entered o correct credentials de", - "full_action": "Garanta que you have entered o correct credentials de\no virtualization servidor e que o servidor está disponível e accessible." + "desc": "Unable to retrieve the list of containers.", + "first_action": "Ensure that you have entered the correct credentials of", + "full_action": "Ensure that you have entered the correct credentials of\nthe virtualization server and that the server is available and accessible." }, "4770": { "code": 4770, - "desc": "Enter um valid primary VM identifier, NetBackup uses this VM identifier to select e backup virtual machines.", - "first_action": "Before you begin um backup operation, enter o primary", - "full_action": "Before you begin um backup operation, enter o primary\nVM identifier to select e back up o VMs." + "desc": "Enter a valid primary VM identifier, NetBackup uses this VM identifier to select and backup virtual machines.", + "first_action": "Before you begin a backup operation, enter the primary", + "full_action": "Before you begin a backup operation, enter the primary\nVM identifier to select and back up the VMs." }, "4771": { "code": 4771, - "desc": "Falhou to start IOTAPPING para o virtual machine on o VM servidor.", - "first_action": "Review o bpVMutil logs on o CDP gateway e o", - "full_action": "Review o bpVMutil logs on o CDP gateway e o\nCIM service logs on o ESX host para more details." + "desc": "Failed to start IOTAPPING for the virtual machine on the VM server.", + "first_action": "Review the bpVMutil logs on the CDP gateway and the", + "full_action": "Review the bpVMutil logs on the CDP gateway and the\nCIM service logs on the ESX host for more details." }, "4772": { "code": 4772, - "desc": "Inválido request foi received to start IOTAPPING para o virtual machine on o VM servidor.", + "desc": "Invalid request was received to start IOTAPPING for the virtual machine on the VM server.", "first_action": "VerifythattheinputJSONreceivedbybpVMutiliscorrect.", - "full_action": "VerifythattheinputJSONreceivedbybpVMutiliscorrect.\nReview o bpVMutil logs on o CDP gateway para more details." + "full_action": "VerifythattheinputJSONreceivedbybpVMutiliscorrect.\nReview the bpVMutil logs on the CDP gateway for more details." }, "4773": { "code": 4773, - "desc": "Falhou to retrieve o virtual machine host informação.", - "first_action": "Verifique que there estão não issues com o vCenter e o", - "full_action": "Verifique que there estão não issues com o vCenter e o\nESX host. Review o bpVMutil logs on o CDP gateway para more details." + "desc": "Failed to retrieve the virtual machine host information.", + "first_action": "Verify that there are no issues with the vCenter and the", + "full_action": "Verify that there are no issues with the vCenter and the\nESX host. Review the bpVMutil logs on the CDP gateway for more details." }, "4774": { "code": 4774, - "desc": "Falhou to interact ou operate com o VM servidor services.", + "desc": "Failed to interact or operate with the VM server services.", "first_action": "VerifythattherearenoissueswiththeCIMservicerunning", - "full_action": "VerifythattherearenoissueswiththeCIMservicerunning\non o ESX. Review o bpVMutil logs on o CDP gateway para more details." + "full_action": "VerifythattherearenoissueswiththeCIMservicerunning\non the ESX. Review the bpVMutil logs on the CDP gateway for more details." }, "4775": { "code": 4775, - "desc": "Inválido request foi received to stop IOTAPPING para o virtual machine on o VM servidor.", + "desc": "Invalid request was received to stop IOTAPPING for the virtual machine on the VM server.", "first_action": "VerifythattheinputJSONreceivedbybpVMutiliscorrect.", - "full_action": "VerifythattheinputJSONreceivedbybpVMutiliscorrect.\nReview bpVMutil logs on o CDP gateway para more details." + "full_action": "VerifythattheinputJSONreceivedbybpVMutiliscorrect.\nReview bpVMutil logs on the CDP gateway for more details." }, "4776": { "code": 4776, - "desc": "Falhou to stop IOTAPPING para o virtual machine on o VM servidor.", - "first_action": "Review o bpVMutil logs on o CDP gateway e o", - "full_action": "Review o bpVMutil logs on o CDP gateway e o\nCIM service logs on o ESX host para more details." + "desc": "Failed to stop IOTAPPING for the virtual machine on the VM server.", + "first_action": "Review the bpVMutil logs on the CDP gateway and the", + "full_action": "Review the bpVMutil logs on the CDP gateway and the\nCIM service logs on the ESX host for more details." }, "4777": { "code": 4777, - "desc": "Armazenamento policy está não detached from one ou more virtual disks de virtual machine.", - "first_action": "Detach o armazenamento policy para todos o disks de o VM e", - "full_action": "Detach o armazenamento policy para todos o disks de o VM e\nretry o operation." + "desc": "Storage policy is not detached from one or more virtual disks of virtual machine.", + "first_action": "Detach the storage policy for all the disks of the VM and", + "full_action": "Detach the storage policy for all the disks of the VM and\nretry the operation." }, "4778": { "code": 4778, - "desc": "Power state de specified virtual machine to be registered para IO tapping está não on.", - "first_action": "Turn on o VM to be protected e retry o operation.", - "full_action": "Turn on o VM to be protected e retry o operation." + "desc": "Power state of specified virtual machine to be registered for IO tapping is not on.", + "first_action": "Turn on the VM to be protected and retry the operation.", + "full_action": "Turn on the VM to be protected and retry the operation." }, "4779": { "code": 4779, "desc": "Unsupported ESXi version.", - "first_action": "Use ESXi version 6.7 ou higher com CDP recurso.", - "full_action": "Use ESXi version 6.7 ou higher com CDP recurso." + "first_action": "Use ESXi version 6.7 or higher with CDP feature.", + "full_action": "Use ESXi version 6.7 or higher with CDP feature." }, "4780": { "code": 4780, - "desc": "Falhou to retrieve ou parse o version de Cohesity IO filter.", - "first_action": "Restart o CIM servidor service on o ESXi servidor e", - "full_action": "Restart o CIM servidor service on o ESXi servidor e\nretry o VM subscription to o CDP protection plan. You can find o CIM servidor\nservice de o ESXi servidor inConfigure > Services section de o ESXi." + "desc": "Failed to retrieve or parse the version of Cohesity IO filter.", + "first_action": "Restart the CIM server service on the ESXi server and", + "full_action": "Restart the CIM server service on the ESXi server and\nretry the VM subscription to the CDP protection plan. You can find the CIM server\nservice of the ESXi server inConfigure > Services section of the ESXi." }, "4781": { "code": 4781, "desc": "Unsupported Veritas IO filter version.", - "first_action": "Install ou upgrade VAIO VIB to um version de 4.0 ou higher.", - "full_action": "Install ou upgrade VAIO VIB to um version de 4.0 ou higher." + "first_action": "Install or upgrade VAIO VIB to a version of 4.0 or higher.", + "full_action": "Install or upgrade VAIO VIB to a version of 4.0 or higher." }, "4782": { "code": 4782, - "desc": "Armazenamento policy está não attached to one ou more virtual disks de virtual machine to be registered para IOTAPPING.", - "first_action": "Attach o armazenamento policy to todos o disks de o VM e", - "full_action": "Attach o armazenamento policy to todos o disks de o VM e\nretry." + "desc": "Storage policy is not attached to one or more virtual disks of virtual machine to be registered for IOTAPPING.", + "first_action": "Attach the storage policy to all the disks of the VM and", + "full_action": "Attach the storage policy to all the disks of the VM and\nretry." }, "4783": { "code": 4783, - "desc": "O operation foi canceled because another operation está in progress para o Cohesity IO filter. NetBackup status codes 689 NetBackup status codes", - "first_action": "Subscribe ou unsubscribe o VMs in batches de five ou", - "full_action": "Subscribe ou unsubscribe o VMs in batches de five ou\nless." + "desc": "The operation was canceled because another operation is in progress for the Cohesity IO filter. NetBackup status codes 689 NetBackup status codes", + "first_action": "Subscribe or unsubscribe the VMs in batches of five or", + "full_action": "Subscribe or unsubscribe the VMs in batches of five or\nless." }, "4784": { "code": 4784, - "desc": "Virtual machine está already registered para IO tapping to some gateway.", + "desc": "Virtual machine is already registered for IO tapping to some gateway.", "first_action": "Another CDP gateway protects this VM. You may need", "full_action": "Another CDP gateway protects this VM. You may need\ntounsubscribetheVMfromtheoldergatewayandsubscribetoanewCDPgateway." }, "4785": { "code": 4785, - "desc": "ISCSI initiator on o backup ou o recovery host está either não executando ou não foi possível to conectar e ou authenticate.", - "first_action": "Garanta que o iSCSI initiator service está instalado e", - "full_action": "Garanta que o iSCSI initiator service está instalado e\nexecutando e ou enabled on o backup ou o recovery host. Para more informação\nabout o iSCSI initiator service installation e enablement on Windows ou UNIX\nplatforms, refer to o NetBackup Web UI AHV Administrator’s Guide." + "desc": "ISCSI initiator on the backup or the recovery host is either not running or unable to connect and or authenticate.", + "first_action": "Ensure that the iSCSI initiator service is installed and", + "full_action": "Ensure that the iSCSI initiator service is installed and\nrunning and or enabled on the backup or the recovery host. For more information\nabout the iSCSI initiator service installation and enablement on Windows or UNIX\nplatforms, refer to the NetBackup Web UI AHV Administrator’s Guide." }, "4786": { "code": 4786, - "desc": "External data service IP para iSCSI está não set on o AHV cluster.", + "desc": "External data service IP for iSCSI is not set on the AHV cluster.", "first_action": "AsrecommendedbyNutanix,thedataservicesIPaddress", - "full_action": "AsrecommendedbyNutanix,thedataservicesIPaddress\nmust be set para o iSCSI data transfer. To configure: Logon to Nutanix AHV cluster\nPrism console > Settings > Cluster Details > Set iSCSI Data Services IP." + "full_action": "AsrecommendedbyNutanix,thedataservicesIPaddress\nmust be set for the iSCSI data transfer. To configure: Logon to Nutanix AHV cluster\nPrism console > Settings > Cluster Details > Set iSCSI Data Services IP." }, "4787": { "code": 4787, - "desc": "Não foi possível to retrieve o list de Nutanix AHV hosts.", - "first_action": "Garanta que o provided credentials de o virtualization", - "full_action": "Garanta que o provided credentials de o virtualization\nservidor estão correct e que o servidor está disponível e accessible." + "desc": "Unable to retrieve the list of Nutanix AHV hosts.", + "first_action": "Ensure that the provided credentials of the virtualization", + "full_action": "Ensure that the provided credentials of the virtualization\nserver are correct and that the server is available and accessible." }, "4788": { "code": 4788, - "desc": "Não foi possível to verifique data integrity.", + "desc": "Unable to verify data integrity.", "first_action": "IncreasetheCDP_DATA_CHECKSUM_VERIFICATION_TIMEOUT", - "full_action": "IncreasetheCDP_DATA_CHECKSUM_VERIFICATION_TIMEOUT\nvalue in o bp.conf arquivo on o CDP host." + "full_action": "IncreasetheCDP_DATA_CHECKSUM_VERIFICATION_TIMEOUT\nvalue in the bp.conf file on the CDP host." }, "4789": { "code": 4789, - "desc": "Inválido Hypervisor type.", - "first_action": "O mídia servidor que está associated com o STU must", - "full_action": "O mídia servidor que está associated com o STU must\nhave NetBackup version 9.1 ou higher." + "desc": "Invalid Hypervisor type.", + "first_action": "The media server that is associated with the STU must", + "full_action": "The media server that is associated with the STU must\nhave NetBackup version 9.1 or higher." }, "4790": { "code": 4790, - "desc": "O trial backup operation está não supported para o NetBackup version de o remote host. NetBackup status codes 691 NetBackup status codes", + "desc": "The trial backup operation is not supported for the NetBackup version of the remote host. NetBackup status codes 691 NetBackup status codes", "first_action": "Torunthetrialbackup,verifythatthemediaserver’slatest", - "full_action": "Torunthetrialbackup,verifythatthemediaserver’slatest\nversion está 10.0 ou newer. If o mídia server's version está older than 10.0, you must\nupgrade que mídia servidor." + "full_action": "Torunthetrialbackup,verifythatthemediaserver’slatest\nversion is 10.0 or newer. If the media server's version is older than 10.0, you must\nupgrade that media server." }, "4793": { "code": 4793, - "desc": "Rede interface restauração está supported apenas para original restauração location. Select o remove rede interface e try again.", - "first_action": "O Rede interface restauração option está não supported", - "full_action": "O Rede interface restauração option está não supported\nforanalternaterestorescenario.SelecttheRemovenetworkinterfaceoptionand\ninitiate restauração again." + "desc": "Network interface restore is supported only for original restore location. Select the remove network interface and try again.", + "first_action": "The Network interface restore option is not supported", + "full_action": "The Network interface restore option is not supported\nforanalternaterestorescenario.SelecttheRemovenetworkinterfaceoptionand\ninitiate restore again." }, "4794": { "code": 4794, - "desc": "Não foi possível to retrieve o cluster details.", - "first_action": "Garanta que o backup host can communicate com o", - "full_action": "Garanta que o backup host can communicate com o\nNetBackup primary servidor." + "desc": "Unable to retrieve the cluster details.", + "first_action": "Ensure that the backup host can communicate with the", + "full_action": "Ensure that the backup host can communicate with the\nNetBackup primary server." }, "4795": { "code": 4795, - "desc": "Não foi possível to find o Prism Central para o AHV cluster.", + "desc": "Unable to find the Prism Central for the AHV cluster.", "first_action": "EnsurethatthecorrectPrismCentralisconfiguredforthe", "full_action": "EnsurethatthecorrectPrismCentralisconfiguredforthe\nAHV cluster." }, "4900": { "code": 4900, - "desc": "O NetBackup UI Compatibility Service está não executando.", - "first_action": "Contate seu NetBackup administrator para assistance.", - "full_action": "Contate seu NetBackup administrator para assistance." + "desc": "The NetBackup UI Compatibility Service is not running.", + "first_action": "Contact your NetBackup administrator for assistance.", + "full_action": "Contact your NetBackup administrator for assistance." }, "5100": { "code": 5100, - "desc": "Não foi possível to create o robot inventory arquivo.", - "first_action": "If o arquivo está não created, confirm que you have enough space disponível on o", - "full_action": "Executar o seguinte como appropriate:\n■ If o arquivo está não created, confirm que you have enough space disponível on o\nsystem.\n■ If NetBackup falhou to correctly set permissions on o arquivo, it could be due to\nincorrect arquivo permissions. Garanta que you have o necessary permissão to\naccess o folder ou o arquivo. Select o arquivo ou folder, right-click, e select\nProperties. Then, select o Security tab e confirm que seu usuário account\nhas o necessary permissions.\n■ If NetBackup falhou to gravar o contents to o arquivo enable o gravar privileges\non o arquivo." + "desc": "Unable to create the robot inventory file.", + "first_action": "If the file is not created, confirm that you have enough space available on the", + "full_action": "Perform the following as appropriate:\n■ If the file is not created, confirm that you have enough space available on the\nsystem.\n■ If NetBackup failed to correctly set permissions on the file, it could be due to\nincorrect file permissions. Ensure that you have the necessary permission to\naccess the folder or the file. Select the file or folder, right-click, and select\nProperties. Then, select the Security tab and confirm that your user account\nhas the necessary permissions.\n■ If NetBackup failed to write the contents to the file enable the write privileges\non the file." }, "5400": { "code": 5400, - "desc": "Backup erro - Nenhum de o request objects foram found in o banco de dados", - "first_action": "Verifique o backup selection list. Add o objects que estão", - "full_action": "Verifique o backup selection list. Add o objects que estão\npart de o banco de dados ou remove o banco de dados instance from o policy." + "desc": "Backup error - None of the request objects were found in the database", + "first_action": "Check the backup selection list. Add the objects that are", + "full_action": "Check the backup selection list. Add the objects that are\npart of the database or remove the database instance from the policy." }, "5401": { "code": 5401, - "desc": "Backup erro - FRA (Fast Recovery Area) foi solicitado, but it foi não found in o banco de dados", + "desc": "Backup error - FRA (Fast Recovery Area) was requested, but it was not found in the database", "first_action": "AddanFRAareatothedatabaseorremovethedatabase", - "full_action": "AddanFRAareatothedatabaseorremovethedatabase\ninstance from o policy." + "full_action": "AddanFRAareatothedatabaseorremovethedatabase\ninstance from the policy." }, "5402": { "code": 5402, - "desc": "OS Authentication erro - Could não conectar to o banco de dados. Por favor verifique o OS credentials", + "desc": "OS Authentication error - Could not connect to the database. Please check the OS credentials", "first_action": "Confirmthatthecredentialsareproperlyset.OnWindows,", - "full_action": "Confirmthatthecredentialsareproperlyset.OnWindows,\nyou may need to replace um process level token. First, select Start>Control\nPanel>AdministrativeTools>LocalSecurityPolicy.Then,expandLocalPolicies\nintheleftpane,clickUserRightsAssignment,anddouble-clickReplaceaprocess\nlevel token in o right pane. Add o usuário you desejar to run o cliente policies como.\nRestart o servidor para this right to take effect." + "full_action": "Confirmthatthecredentialsareproperlyset.OnWindows,\nyou may need to replace a process level token. First, select Start>Control\nPanel>AdministrativeTools>LocalSecurityPolicy.Then,expandLocalPolicies\nintheleftpane,clickUserRightsAssignment,anddouble-clickReplaceaprocess\nlevel token in the right pane. Add the user you want to run the client policies as.\nRestart the server for this right to take effect." }, "5403": { "code": 5403, - "desc": "Oracle Authentication erro - Could não conectar to o banco de dados. Por favor verifique o Oracle credentials", - "first_action": "Confirm que o credentials estão properly set.", - "full_action": "Confirm que o credentials estão properly set." + "desc": "Oracle Authentication error - Could not connect to the database. Please check the Oracle credentials", + "first_action": "Confirm that the credentials are properly set.", + "full_action": "Confirm that the credentials are properly set." }, "5404": { "code": 5404, - "desc": "ASM validation erro - PROXY backup está não supported para ASM", - "first_action": "Move o banco de dados to non-ASM armazenamento ou remove o", - "full_action": "Move o banco de dados to non-ASM armazenamento ou remove o\nbanco de dados instance from o policy." + "desc": "ASM validation error - PROXY backup is not supported for ASM", + "first_action": "Move the database to non-ASM storage or remove the", + "full_action": "Move the database to non-ASM storage or remove the\ndatabase instance from the policy." }, "5405": { "code": 5405, - "desc": "Recovery Catalog Authentication erro - Could não conectar to o Recovery Catalog. Por favor verifique o Recovery Catalog credentials. NetBackup status codes 695 NetBackup status codes", + "desc": "Recovery Catalog Authentication error - Could not connect to the Recovery Catalog. Please check the Recovery Catalog credentials. NetBackup status codes 695 NetBackup status codes", "first_action": "ConfirmthattheRecoveryCatalogcredentialsareproperly", "full_action": "ConfirmthattheRecoveryCatalogcredentialsareproperly\nset." }, "5406": { "code": 5406, "desc": "Archivelogonlybackuprequested,butdatabaseisnotinARCHIVELOG Mode", - "first_action": "Confirm que o banco de dados archive log mode está properly", - "full_action": "Confirm que o banco de dados archive log mode está properly\nset to either ARCHIVELOG ou MANUAL." + "first_action": "Confirm that the database archive log mode is properly", + "full_action": "Confirm that the database archive log mode is properly\nset to either ARCHIVELOG or MANUAL." }, "5407": { "code": 5407, "desc": "Databaseisinthewrongstate(mustbeOPEN)fortherequestedaction.", - "first_action": "Confirm que o banco de dados mode está set to Abrir. Possible Oracle commands", - "full_action": "Executar o seguinte como appropriate:\n■ Confirm que o banco de dados mode está set to Abrir. Possible Oracle commands\nstartup, startup opens ler apenas, ou startup abrir.\n■ Abrir o target container banco de dados in read-write mode before initiating um PDB\nclone." + "first_action": "Confirm that the database mode is set to OPEN. Possible Oracle commands", + "full_action": "Perform the following as appropriate:\n■ Confirm that the database mode is set to OPEN. Possible Oracle commands\nstartup, startup opens read only, or startup open.\n■ Open the target container database in read-write mode before initiating a PDB\nclone." }, "5408": { "code": 5408, - "desc": "OS Authentication erro - Could não find credentials. If this instance está part de um instance group, make sure que o group has o credentials que match this OS Type NetBackup status codes 696 NetBackup status codes", - "first_action": "If o instance está on um UNIX cliente, make sure que its", - "full_action": "If o instance está on um UNIX cliente, make sure que its\ninstance group contains UNIX credentials. If o instance está on um Windows cliente,\nmake sure que its instance group contains Windows credentials." + "desc": "OS Authentication error - Could not find credentials. If this instance is part of an instance group, make sure that the group has the credentials that match this OS Type NetBackup status codes 696 NetBackup status codes", + "first_action": "If the instance is on a UNIX client, make sure that its", + "full_action": "If the instance is on a UNIX client, make sure that its\ninstance group contains UNIX credentials. If the instance is on a Windows client,\nmake sure that its instance group contains Windows credentials." }, "5409": { "code": 5409, - "desc": "Cloning está Não supported para this cliente platform", - "first_action": "Refer to o NetBackup Release Notes ou o NetBackup", - "full_action": "Refer to o NetBackup Release Notes ou o NetBackup\nMaster Compatibility List para o supported platforms para o cloning recurso at o\nseguinte URL:\nhttp://www.netbackup.com/compatibility" + "desc": "Cloning is NOT supported for this client platform", + "first_action": "Refer to the NetBackup Release Notes or the NetBackup", + "full_action": "Refer to the NetBackup Release Notes or the NetBackup\nMaster Compatibility List for the supported platforms for the cloning feature at the\nfollowing URL:\nhttp://www.netbackup.com/compatibility" }, "5410": { "code": 5410, - "desc": "Oracle Intelligent Policy está Não supported para this cliente platform", - "first_action": "Refer to o NetBackup Release Notes ou o NetBackup", - "full_action": "Refer to o NetBackup Release Notes ou o NetBackup\nMasterCompatibilityListforthesupportedplatformsforthisfeatureatthefollowing\nURL:\nhttp://www.netbackup.com/compatibility" + "desc": "Oracle Intelligent Policy is NOT supported for this client platform", + "first_action": "Refer to the NetBackup Release Notes or the NetBackup", + "full_action": "Refer to the NetBackup Release Notes or the NetBackup\nMasterCompatibilityListforthesupportedplatformsforthisfeatureatthefollowing\nURL:\nhttp://www.netbackup.com/compatibility" }, "5411": { "code": 5411, - "desc": "Não é possível do um hot backup de um banco de dados in NOARCHIVELOG mode", - "first_action": "Confirm que o banco de dados archive log mode está properly", - "full_action": "Confirm que o banco de dados archive log mode está properly\nset to ARCHIVELOG ou change to um offline (cold) banco de dados backup." + "desc": "Cannot do a hot backup of a database in NOARCHIVELOG mode", + "first_action": "Confirm that the database archive log mode is properly", + "full_action": "Confirm that the database archive log mode is properly\nset to ARCHIVELOG or change to an offline (cold) database backup." }, "5412": { "code": 5412, - "desc": "Banco de dados está in o wrong state (must be Abrir ou MOUNTED) para um Archive Log Backup", - "first_action": "Put o banco de dados in um Abrir ou MOUNTED state e", - "full_action": "Put o banco de dados in um Abrir ou MOUNTED state e\nretry o backup." + "desc": "Database is in the wrong state (must be OPEN or MOUNTED) for an Archive Log Backup", + "first_action": "Put the database in an OPEN or MOUNTED state and", + "full_action": "Put the database in an OPEN or MOUNTED state and\nretry the backup." }, "5413": { "code": 5413, - "desc": "Banco de dados está in o wrong state (must be Abrir ou MOUNTED) para um FRA backup", - "first_action": "Put o banco de dados in um Abrir ou MOUNTED state e", - "full_action": "Put o banco de dados in um Abrir ou MOUNTED state e\nretry o backup." + "desc": "Database is in the wrong state (must be OPEN or MOUNTED) for an FRA backup", + "first_action": "Put the database in an OPEN or MOUNTED state and", + "full_action": "Put the database in an OPEN or MOUNTED state and\nretry the backup." }, "5414": { "code": 5414, - "desc": "O solicitado operation está não supported com this cliente version", - "first_action": "Upgrade o NetBackup Cliente service to enable this", - "full_action": "Upgrade o NetBackup Cliente service to enable this\noperation." + "desc": "The requested operation is not supported with this client version", + "first_action": "Upgrade the NetBackup Client service to enable this", + "full_action": "Upgrade the NetBackup Client service to enable this\noperation." }, "5415": { "code": 5415, - "desc": "Não é possível shut down read-only standby banco de dados", - "first_action": "Do não select o cold banco de dados backup option on o", - "full_action": "Do não select o cold banco de dados backup option on o\nOracle tab de o policy." + "desc": "Cannot shut down read-only standby database", + "first_action": "Do not select the cold database backup option on the", + "full_action": "Do not select the cold database backup option on the\nOracle tab of the policy." }, "5416": { "code": 5416, - "desc": "Oracle não é possível resolve o TNS conexão identifier", - "first_action": "O correct TNS identifier.", - "full_action": "Verifique o seguinte:\n■ O correct TNS identifier.\n■ O correctly configurado tnsnames.ora arquivo.\n■ O correct caminho para o TNS_ADMIN environment variable." + "desc": "Oracle cannot resolve the TNS connection identifier", + "first_action": "The correct TNS identifier.", + "full_action": "Verify the following:\n■ The correct TNS identifier.\n■ The correctly configured tnsnames.ora file.\n■ The correct path for the TNS_ADMIN environment variable." }, "5417": { "code": 5417, - "desc": "Um erro has ocorreu checking if o NFS servidor está um appliance.", - "first_action": "Verifique que o banco de dados backup share está exported from um", - "full_action": "Verifique que o banco de dados backup share está exported from um\nNetBackup appliance." + "desc": "An error has occurred checking if the NFS server is an appliance.", + "first_action": "Verify that the database backup share is exported from a", + "full_action": "Verify that the database backup share is exported from a\nNetBackup appliance." }, "5418": { "code": 5418, - "desc": "O NFS servidor está não um appliance.", - "first_action": "Verifique que o banco de dados backup share está exported from um", - "full_action": "Verifique que o banco de dados backup share está exported from um\nNetBackup appliance." + "desc": "The NFS server is not an appliance.", + "first_action": "Verify that the database backup share is exported from a", + "full_action": "Verify that the database backup share is exported from a\nNetBackup appliance." }, "5419": { "code": 5419, - "desc": "O banco de dados backup share diretório está não disponível on o appliance.", - "first_action": "Verifique que o banco de dados backup share diretório exists on", - "full_action": "Verifique que o banco de dados backup share diretório exists on\no NetBackup appliance." + "desc": "The database backup share directory is not available on the appliance.", + "first_action": "Verify that the database backup share directory exists on", + "full_action": "Verify that the database backup share directory exists on\nthe NetBackup appliance." }, "5420": { "code": 5420, - "desc": "Whole Banco de dados - Datafile Copy Share selection está não supported para this cliente platform.", - "first_action": "Back up o banco de dados usando um different method.", - "full_action": "Back up o banco de dados usando um different method." + "desc": "Whole Database - Datafile Copy Share selection is not supported for this client platform.", + "first_action": "Back up the database using a different method.", + "full_action": "Back up the database using a different method." }, "5421": { "code": 5421, - "desc": "Nenhum de o solicitado pluggable databases foram found.", - "first_action": "Verifique o detailed status de o associated jobs in o", - "full_action": "Verifique o detailed status de o associated jobs in o\nactivity monitor para more informação. Confirm o list de o pluggable databases\nque estão specified in o Oracle Intelligent Policy estão correct e in o solicitado\nbanco de dados. Update o list de pluggable databases in policy. If o pluggable\ndatabases foram specified usando o comando line, por favor confirm their spelling.\nRetry o backup once o updates estão complete." + "desc": "None of the requested pluggable databases were found.", + "first_action": "Check the detailed status of the associated jobs in the", + "full_action": "Check the detailed status of the associated jobs in the\nactivity monitor for more information. Confirm the list of the pluggable databases\nthat are specified in the Oracle Intelligent Policy are correct and in the requested\ndatabase. Update the list of pluggable databases in policy. If the pluggable\ndatabases were specified using the command line, please confirm their spelling.\nRetry the backup once the updates are complete." }, "5422": { "code": 5422, - "desc": "Partial success - one ou more de o solicitado pluggable databases foram não found.", - "first_action": "Verifique o detailed status de o associated jobs in o", - "full_action": "Verifique o detailed status de o associated jobs in o\nactivity monitor para more informação. Confirm o list de pluggable databases que\nestão specified in o Oracle Intelligent Policy estão correct e in o solicitado\nbanco de dados. Update o list de pluggable databases in policy. If o pluggable\ndatabases foram specified usando o comando line, por favor confirm their spelling.\nRetry o backup once o updates estão complete." + "desc": "Partial success - one or more of the requested pluggable databases were not found.", + "first_action": "Check the detailed status of the associated jobs in the", + "full_action": "Check the detailed status of the associated jobs in the\nactivity monitor for more information. Confirm the list of pluggable databases that\nare specified in the Oracle Intelligent Policy are correct and in the requested\ndatabase. Update the list of pluggable databases in policy. If the pluggable\ndatabases were specified using the command line, please confirm their spelling.\nRetry the backup once the updates are complete." }, "5423": { "code": 5423, "desc": "Noneoftherequestedtablespaceswerefoundintherequestedpluggable databases.", - "first_action": "Verifique o detailed status de o associated jobs in o", - "full_action": "Verifique o detailed status de o associated jobs in o\nactivitymonitorformoreinformation.Confirmthelistoftablespacesthatarespecified\nintheOracleIntelligentPolicyarecorrectandintherequestedpluggabledatabases.\nUpdate o lists, onde applicable, in policy. If o pluggable databases ou\ntablespaces foram specified usando o comando line, por favor confirm their spelling.\nRetry o backup once o updates estão complete." + "first_action": "Check the detailed status of the associated jobs in the", + "full_action": "Check the detailed status of the associated jobs in the\nactivitymonitorformoreinformation.Confirmthelistoftablespacesthatarespecified\nintheOracleIntelligentPolicyarecorrectandintherequestedpluggabledatabases.\nUpdate the lists, where applicable, in policy. If the pluggable databases or\ntablespaces were specified using the command line, please confirm their spelling.\nRetry the backup once the updates are complete." }, "5424": { "code": 5424, - "desc": "Partial success - one ou more de o solicitado pluggable databases did não contain qualquer de o solicitado tablespaces.", - "first_action": "Verifique o detailed status de o associated jobs in o", - "full_action": "Verifique o detailed status de o associated jobs in o\nactivitymonitorformoreinformation.Confirmthelistoftablespacesthatarespecified\nintheOracleIntelligentPolicyarecorrectandintherequestedpluggabledatabases.\nUpdate o lists, onde applicable, in policy. If o pluggable databases ou\ntablespaces foram specified usando o comando line, por favor confirm their spelling.\nRetry o backup once o updates estão complete." + "desc": "Partial success - one or more of the requested pluggable databases did not contain any of the requested tablespaces.", + "first_action": "Check the detailed status of the associated jobs in the", + "full_action": "Check the detailed status of the associated jobs in the\nactivitymonitorformoreinformation.Confirmthelistoftablespacesthatarespecified\nintheOracleIntelligentPolicyarecorrectandintherequestedpluggabledatabases.\nUpdate the lists, where applicable, in policy. If the pluggable databases or\ntablespaces were specified using the command line, please confirm their spelling.\nRetry the backup once the updates are complete." }, "5425": { "code": 5425, - "desc": "Nenhum de o solicitado data arquivos foram found in o solicitado pluggable databases.", - "first_action": "Verifique o detailed status de o associated jobs in o", - "full_action": "Verifique o detailed status de o associated jobs in o\nactivity monitor para more informação. Confirm o list de data arquivos que estão specified\nintheOracleIntelligentPolicyarecorrectandintherequestedpluggabledatabases.\nUpdatethelists,whereapplicable,inpolicy.Ifthepluggabledatabasesordatafiles\nforam specified usando o comando line, por favor confirm their spelling. Retry o\nbackup once o updates estão complete." + "desc": "None of the requested data files were found in the requested pluggable databases.", + "first_action": "Check the detailed status of the associated jobs in the", + "full_action": "Check the detailed status of the associated jobs in the\nactivity monitor for more information. Confirm the list of data files that are specified\nintheOracleIntelligentPolicyarecorrectandintherequestedpluggabledatabases.\nUpdatethelists,whereapplicable,inpolicy.Ifthepluggabledatabasesordatafiles\nwere specified using the command line, please confirm their spelling. Retry the\nbackup once the updates are complete." }, "5426": { "code": 5426, - "desc": "Partial success - one ou more de o solicitado pluggable databases did não contain qualquer de o solicitado data arquivos.", - "first_action": "Verifique o detailed status de o associated jobs in o", - "full_action": "Verifique o detailed status de o associated jobs in o\nactivity monitor para more informação. Confirm o list de data arquivos que estão specified\nintheOracleIntelligentPolicyarecorrectandintherequestedpluggabledatabases.\nUpdatethelists,whereapplicable,inpolicy.Ifthepluggabledatabasesordatafiles\nforam specified usando o comando line, por favor confirm their spelling. Retry o\nbackup once o updates estão complete." + "desc": "Partial success - one or more of the requested pluggable databases did not contain any of the requested data files.", + "first_action": "Check the detailed status of the associated jobs in the", + "full_action": "Check the detailed status of the associated jobs in the\nactivity monitor for more information. Confirm the list of data files that are specified\nintheOracleIntelligentPolicyarecorrectandintherequestedpluggabledatabases.\nUpdatethelists,whereapplicable,inpolicy.Ifthepluggabledatabasesordatafiles\nwere specified using the command line, please confirm their spelling. Retry the\nbackup once the updates are complete." }, "5427": { "code": 5427, - "desc": "Partial success - more than one erro foi encontrado, por favor refer to o Detailed Status tab in o Job Details e review logs para more informação.", - "first_action": "Verifique o detailed status de o associated jobs in o", - "full_action": "Verifique o detailed status de o associated jobs in o\nactivity monitor para more informação on o errors. Depending on o errors, make\no appropriate changes to o policy. Retry o backup once o updates estão\ncomplete." + "desc": "Partial success - more than one error was encountered, please refer to the Detailed Status tab in the Job Details and review logs for more information.", + "first_action": "Check the detailed status of the associated jobs in the", + "full_action": "Check the detailed status of the associated jobs in the\nactivity monitor for more information on the errors. Depending on the errors, make\nthe appropriate changes to the policy. Retry the backup once the updates are\ncomplete." }, "5428": { "code": 5428, - "desc": "Não banco de dados backup shares foram found.", + "desc": "No database backup shares were found.", "first_action": "Configuretheappliancedatabasebackupshareandthen", - "full_action": "Configuretheappliancedatabasebackupshareandthen\nbackup o arquivos to o share usando o banco de dados vendor’s tools. NetBackup does\nnão retry this job after falha." + "full_action": "Configuretheappliancedatabasebackupshareandthen\nbackup the files to the share using the database vendor’s tools. NetBackup does\nnot retry this job after failure." }, "5429": { "code": 5429, - "desc": "Não new arquivos ou arquivos que estão related to o instance ou banco de dados foram found in o banco de dados backup share.", + "desc": "No new files or files that are related to the instance or database were found in the database backup share.", "first_action": "Makesurethatabackupisonthedatabasebackupshare", - "full_action": "Makesurethatabackupisonthedatabasebackupshare\nbefore o policy está executed. If o policy contained um incremental schedule, then\nverifique que o banco de dados backup share contained new arquivos. NetBackup does não\nretry this job after falha." + "full_action": "Makesurethatabackupisonthedatabasebackupshare\nbefore the policy is executed. If the policy contained an incremental schedule, then\nverify that the database backup share contained new files. NetBackup does not\nretry this job after failure." }, "5430": { "code": 5430, - "desc": "Banco de dados must be in ARCHIVELOG mode to executar um cold backup de um pluggable banco de dados.", + "desc": "Database must be in ARCHIVELOG mode to perform a cold backup of a pluggable database.", "first_action": "ChangethedatabasetoARCHIVELOGmodeorchangethe", - "full_action": "ChangethedatabasetoARCHIVELOGmodeorchangethe\nbackup request from um cold backup to um hot backup. Retry o backup once o\nupdates estão complete." + "full_action": "ChangethedatabasetoARCHIVELOGmodeorchangethe\nbackup request from a cold backup to a hot backup. Retry the backup once the\nupdates are complete." }, "5431": { "code": 5431, - "desc": "O solicitado operation did não get um response from o NetBackup appliance.", - "first_action": "On Windows: Add um registry DWORD entry que está called APPLIANCE_TIMEOUT com", - "full_action": "Thedefaulttimeoutis setto60 seconds.Configurea new\ntempo limite esgotado on o NetBackup master servidor. After o tempo limite esgotado está configurado on o\nmaster servidor, confirm o NetBackup appliance está active e retry o operation.\n■ On Windows: Add um registry DWORD entry que está called APPLIANCE_TIMEOUT com\num value in seconds at\nHKEY_LOCAL_MACHINE\\SOFTWARE\\Veritas\\NetBackup\\CurrentVersion\\Config\n■ On UNIX: Change o APPLIANCE_TIMEOUT setting in o bp.conf arquivo" + "desc": "The requested operation did not get a response from the NetBackup appliance.", + "first_action": "On Windows: Add a registry DWORD entry that is called APPLIANCE_TIMEOUT with", + "full_action": "Thedefaulttimeoutis setto60 seconds.Configurea new\ntimeout on the NetBackup master server. After the timeout is configured on the\nmaster server, confirm the NetBackup appliance is active and retry the operation.\n■ On Windows: Add a registry DWORD entry that is called APPLIANCE_TIMEOUT with\na value in seconds at\nHKEY_LOCAL_MACHINE\\SOFTWARE\\Veritas\\NetBackup\\CurrentVersion\\Config\n■ On UNIX: Change the APPLIANCE_TIMEOUT setting in the bp.conf file" }, "5432": { "code": 5432, - "desc": "O solicitado NetBackup appliance operation está unsuccessful.", - "first_action": "Review o NetBackup appliance erro message log, o", - "full_action": "Review o NetBackup appliance erro message log, o\nNetBackup Appliance Troubleshooting Guide, ou contate o NetBackup appliance\nadministrator para help." + "desc": "The requested NetBackup appliance operation is unsuccessful.", + "first_action": "Review the NetBackup appliance error message log, the", + "full_action": "Review the NetBackup appliance error message log, the\nNetBackup Appliance Troubleshooting Guide, or contact the NetBackup appliance\nadministrator for help." }, "5433": { "code": 5433, - "desc": "O NetBackup request did não complete due to um NetBackup appliance communication issue.", - "first_action": "Review o NetBackup appliance erro message log, o", - "full_action": "Review o NetBackup appliance erro message log, o\nNetBackup Appliance Troubleshooting Guide, ou contate o NetBackup appliance\nadministrator para help." + "desc": "The NetBackup request did not complete due to a NetBackup appliance communication issue.", + "first_action": "Review the NetBackup appliance error message log, the", + "full_action": "Review the NetBackup appliance error message log, the\nNetBackup Appliance Troubleshooting Guide, or contact the NetBackup appliance\nadministrator for help." }, "5434": { "code": 5434, - "desc": "Não é possível validate o identity de o NetBackup appliance.", - "first_action": "Review o NetBackup appliance erro message log, o", - "full_action": "Review o NetBackup appliance erro message log, o\nNetBackup Appliance Troubleshooting Guide, ou contate o NetBackup appliance\nadministrator para help." + "desc": "Cannot validate the identity of the NetBackup appliance.", + "first_action": "Review the NetBackup appliance error message log, the", + "full_action": "Review the NetBackup appliance error message log, the\nNetBackup Appliance Troubleshooting Guide, or contact the NetBackup appliance\nadministrator for help." }, "5435": { "code": 5435, - "desc": "Recoverypointoperations(-create,-delete,or-list)mustbeinitiated from um master servidor.", - "first_action": "Create, -excluir, ou -list comando options from o master servidor. O", - "full_action": "Contate o NetBackup administrator to run o nborair\n-create, -excluir, ou -list comando options from o master servidor. O\nNetBackup administrator must have raiz usuário (UNIX) ou administrator (Windows)\naccess on o master servidor." + "desc": "Recoverypointoperations(-create,-delete,or-list)mustbeinitiated from a master server.", + "first_action": "Create, -delete, or -list command options from the master server. The", + "full_action": "Contact the NetBackup administrator to run the nborair\n-create, -delete, or -list command options from the master server. The\nNetBackup administrator must have root user (UNIX) or administrator (Windows)\naccess on the master server." }, "5436": { "code": 5436, - "desc": "Não recovery point foi found.", - "first_action": "Confirm there está um recovery point created. If there está não", - "full_action": "Confirm there está um recovery point created. If there está não\nrecovery point, create um recovery point e retry o operation." + "desc": "No recovery point was found.", + "first_action": "Confirm there is a recovery point created. If there is no", + "full_action": "Confirm there is a recovery point created. If there is no\nrecovery point, create a recovery point and retry the operation." }, "5437": { "code": 5437, - "desc": "Partial success - recovery points from one ou more banco de dados shares foram não found.", - "first_action": "Review o NetBackup debug logs (bprd, nboarir) para", - "full_action": "Review o NetBackup debug logs (bprd, nboarir) para\nmore details about o erro. Also, review o NetBackup appliance debug logs para\nfurther details." + "desc": "Partial success - recovery points from one or more database shares were not found.", + "first_action": "Review the NetBackup debug logs (bprd, nboarir) for", + "full_action": "Review the NetBackup debug logs (bprd, nboarir) for\nmore details about the error. Also, review the NetBackup appliance debug logs for\nfurther details." }, "5438": { "code": 5438, - "desc": "O solicitado export caminho informação está não found.", - "first_action": "List todos recovery points e veja if o solicitado export", - "full_action": "List todos recovery points e veja if o solicitado export\ncaminho /recovery point está disponível. Review o NetBackup debug logs (bprd,\nnboarir) para more details about o erro. Also, review o NetBackup appliance\ndebug logs para further details." + "desc": "The requested export path information is not found.", + "first_action": "List all recovery points and see if the requested export", + "full_action": "List all recovery points and see if the requested export\npath /recovery point is available. Review the NetBackup debug logs (bprd,\nnboarir) for more details about the error. Also, review the NetBackup appliance\ndebug logs for further details." }, "5439": { "code": 5439, - "desc": "Validation unsuccessful. O recovery point foi não created from o specified backup ID.", - "first_action": "Confirm que you solicitado o correct mount caminho. Also,", - "full_action": "Confirm que you solicitado o correct mount caminho. Also,\nconfirm que you have solicitado o correct backup ID in o create recovery point\nprocess. Verifique com o NetBackup administrator para o correct backup ID in o\ncreaterecoverypointprocessandsystemadministratorforthecorrectexportmount\ncaminho." + "desc": "Validation unsuccessful. The recovery point was not created from the specified backup ID.", + "first_action": "Confirm that you requested the correct mount path. Also,", + "full_action": "Confirm that you requested the correct mount path. Also,\nconfirm that you have requested the correct backup ID in the create recovery point\nprocess. Check with the NetBackup administrator for the correct backup ID in the\ncreaterecoverypointprocessandsystemadministratorforthecorrectexportmount\npath." }, "5440": { "code": 5440, - "desc": "Requerido environment variable está não set.", - "first_action": "You need to set o requerido environment variable", - "full_action": "You need to set o requerido environment variable\nORACLE_HOME com o appropriate value e executar o validate operation again.\nReview o NetBackup debug logs (nborair) para more informação." + "desc": "Required environment variable is not set.", + "first_action": "You need to set the required environment variable", + "full_action": "You need to set the required environment variable\nORACLE_HOME with the appropriate value and perform the validate operation again.\nReview the NetBackup debug logs (nborair) for more information." }, "5441": { "code": 5441, - "desc": "Attempt to abrir Oracle direct NFS arquivo foi unsuccessful.", - "first_action": "When NetBackup performs o validate operation on", - "full_action": "When NetBackup performs o validate operation on\nWindows, we get o mount caminho que está associated com o set export caminho from\nOracle direct NFS arquivo. Confirm que o correct value está set in o environment\nvariable ORACLE_HOME. Review o NetBackup debug logs (nborair) para more\ninformação." + "desc": "Attempt to open Oracle direct NFS file was unsuccessful.", + "first_action": "When NetBackup performs the validate operation on", + "full_action": "When NetBackup performs the validate operation on\nWindows, we get the mount path that is associated with the set export path from\nOracle direct NFS file. Confirm that the correct value is set in the environment\nvariable ORACLE_HOME. Review the NetBackup debug logs (nborair) for more\ninformation." }, "5442": { "code": 5442, - "desc": "Attempt to retrieve o dispositivo informação from o NFS mount caminho foi unsuccessful.", - "first_action": "Confirm que o provided mount caminho está correct e que", - "full_action": "Confirm que o provided mount caminho está correct e que\no caminho está rightly mounted (UNIX) ou Oracle direct NFS arquivo (Windows) has o\ncorrect entradas. Review o NetBackup debug logs (nborair) para more informação." + "desc": "Attempt to retrieve the device information from the NFS mount path was unsuccessful.", + "first_action": "Confirm that the provided mount path is correct and that", + "full_action": "Confirm that the provided mount path is correct and that\nthe path is rightly mounted (UNIX) or Oracle direct NFS file (Windows) has the\ncorrect entries. Review the NetBackup debug logs (nborair) for more information." }, "5443": { "code": 5443, - "desc": "Backup ID não é possível be used para Oracle instant recovery.", - "first_action": "Use o nborair comando com -list_images option to", - "full_action": "Use o nborair comando com -list_images option to\nview which images should be used para instant recovery e specify um different\nbackup ID." + "desc": "Backup ID cannot be used for Oracle instant recovery.", + "first_action": "Use the nborair command with -list_images option to", + "full_action": "Use the nborair command with -list_images option to\nview which images should be used for instant recovery and specify a different\nbackup ID." }, "5444": { "code": 5444, - "desc": "O NetBackup appliance credentials retrieval foi unsuccessful.", - "first_action": "Review o NetBackup appliance erro message log, o", - "full_action": "Review o NetBackup appliance erro message log, o\nNetBackup Appliance Troubleshooting Guide, ou contate o NetBackup appliance\nadministrator para help." + "desc": "The NetBackup appliance credentials retrieval was unsuccessful.", + "first_action": "Review the NetBackup appliance error message log, the", + "full_action": "Review the NetBackup appliance error message log, the\nNetBackup Appliance Troubleshooting Guide, or contact the NetBackup appliance\nadministrator for help." }, "5445": { "code": 5445, - "desc": "Oracle instant recovery share não é possível be used para backup operations.", - "first_action": "Um Copilot instant recovery share não é possível be used in um", - "full_action": "Um Copilot instant recovery share não é possível be used in um\nbackup policy." + "desc": "Oracle instant recovery share cannot be used for backup operations.", + "first_action": "A Copilot instant recovery share cannot be used in a", + "full_action": "A Copilot instant recovery share cannot be used in a\nbackup policy." }, "5446": { "code": 5446, - "desc": "Partial success - backup de one ou more de o solicitado shares unsuccessful.", - "first_action": "Review o detailed status de o backup job e o", - "full_action": "Review o detailed status de o backup job e o\nbpdbsbora debug logs." + "desc": "Partial success - backup of one or more of the requested shares unsuccessful.", + "first_action": "Review the detailed status of the backup job and the", + "full_action": "Review the detailed status of the backup job and the\nbpdbsbora debug logs." }, "5447": { "code": 5447, - "desc": "Could não resolve appliance host name from IP address.", - "first_action": "Update o NetBackup servidor list ou mídia servidor list to", - "full_action": "Update o NetBackup servidor list ou mídia servidor list to\nuse o appliance host name." + "desc": "Could not resolve appliance host name from IP address.", + "first_action": "Update the NetBackup server list or media server list to", + "full_action": "Update the NetBackup server list or media server list to\nuse the appliance host name." }, "5448": { "code": 5448, - "desc": "Could não match o appliance to um servidor in o client’s servidor list.", - "first_action": "Add o appliance host name to o client’s servidor list.", - "full_action": "Add o appliance host name to o client’s servidor list." + "desc": "Could not match the appliance to a server in the client’s server list.", + "first_action": "Add the appliance host name to the client’s server list.", + "full_action": "Add the appliance host name to the client’s server list." }, "5449": { "code": 5449, - "desc": "O script está não approved para execution. NetBackup status codes 709 NetBackup status codes", - "first_action": "Move o script to o default location ou add o caminho como", - "full_action": "Move o script to o default location ou add o caminho como\num authorized location usando o nbsetconfig ou bpsetconfig comando. O\ndefault location para UNIX está: /usr/openv/netbackup/ext/db_ext. O default\nlocation para Windows está: install_path\\netbackup\\dbext." + "desc": "The script is not approved for execution. NetBackup status codes 709 NetBackup status codes", + "first_action": "Move the script to the default location or add the path as", + "full_action": "Move the script to the default location or add the path as\nan authorized location using the nbsetconfig or bpsetconfig command. The\ndefault location for UNIX is: /usr/openv/netbackup/ext/db_ext. The default\nlocation for Windows is: install_path\\netbackup\\dbext." }, "5450": { "code": 5450, - "desc": "Não scripts ou paths estão approved para execution on this cliente.", - "first_action": "Consult o cliente administrator para informação como to por que", - "full_action": "Consult o cliente administrator para informação como to por que\nnenhum foi set on this cliente." + "desc": "No scripts or paths are approved for execution on this client.", + "first_action": "Consult the client administrator for information as to why", + "full_action": "Consult the client administrator for information as to why\nnone was set on this client." }, "5451": { "code": 5451, - "desc": "O script está stored in um remote location.", + "desc": "The script is stored in a remote location.", "first_action": "Movethescripttoalocalauthorizedlocationforexecution.", "full_action": "Movethescripttoalocalauthorizedlocationforexecution." }, "5452": { "code": 5452, - "desc": "O script não é possível be accessed para execution.", - "first_action": "Confirm que o script e its location estão on o local", - "full_action": "Confirm que o script e its location estão on o local\nsystemandNetBackupcanaccessthescript.ForWindowsclients,besuretoverify\nque o usuário executando o NetBackup cliente service has ler e execute\npermissions para o script." + "desc": "The script cannot be accessed for execution.", + "first_action": "Confirm that the script and its location are on the local", + "full_action": "Confirm that the script and its location are on the local\nsystemandNetBackupcanaccessthescript.ForWindowsclients,besuretoverify\nthat the user running the NetBackup client service has read and execute\npermissions for the script." }, "5453": { "code": 5453, - "desc": "O discovered Banco de dados ID ou Banco de dados Unique Name did não match o ID ou Name que foi expected ou provided.", - "first_action": "Confirm que o registered RAC banco de dados has todos o", - "full_action": "Confirm que o registered RAC banco de dados has todos o\ncorrectinformation.Reviewthescanname,servicename,port,DBID,uniquename,\ne anything else que foi provided. Retry o operation." + "desc": "The discovered Database ID or Database Unique Name did not match the ID or Name that was expected or provided.", + "first_action": "Confirm that the registered RAC database has all the", + "full_action": "Confirm that the registered RAC database has all the\ncorrectinformation.Reviewthescanname,servicename,port,DBID,uniquename,\nand anything else that was provided. Retry the operation." }, "5454": { "code": 5454, - "desc": "O cliente está não part de o specified RAC cluster.", - "first_action": "Run o comando from um cliente que está part de o RAC", - "full_action": "Run o comando from um cliente que está part de o RAC\ncluster." + "desc": "The client is not part of the specified RAC cluster.", + "first_action": "Run the command from a client that is part of the RAC", + "full_action": "Run the command from a client that is part of the RAC\ncluster." }, "5455": { "code": 5455, - "desc": "O Oracle backup did não start.", - "first_action": "Verifique que seu banco de dados e o arquivo system estão in um", - "full_action": "Verifique que seu banco de dados e o arquivo system estão in um\nnormal state. Confirm que there estão não memória constraints, locked arquivos, rogue\nprocessos, ou qualquer other issues que can prevent um backup. Review erro logs if\npossible.Oncethesystemisverifiedfunctional,retrytheOraclebackup.Iftheissue\npersists, visit o Cohesity Technical Support website. O Cohesity Technical\nSupport website offers additional informação to help you troubleshoot this issue" + "desc": "The Oracle backup did not start.", + "first_action": "Check that your database and the file system are in a", + "full_action": "Check that your database and the file system are in a\nnormal state. Confirm that there are no memory constraints, locked files, rogue\nprocesses, or any other issues that can prevent a backup. Review error logs if\npossible.Oncethesystemisverifiedfunctional,retrytheOraclebackup.Iftheissue\npersists, visit the Cohesity Technical Support website. The Cohesity Technical\nSupport website offers additional information to help you troubleshoot this issue" }, "5456": { "code": 5456, - "desc": "Não Oracle RAC instance connections. NetBackup status codes 711 NetBackup status codes", - "first_action": "Verifique que one ou more Oracle RAC instances estão up e executando e can be", - "full_action": "Retry o backup after you verifique o seguinte:\n■ Verifique que one ou more Oracle RAC instances estão up e executando e can be\nconnected to.\n■ Verifique o credentials que estão used to conectar to o Oracle RAC instance estão\ncorrect in NetBackup." + "desc": "No Oracle RAC instance connections. NetBackup status codes 711 NetBackup status codes", + "first_action": "Verify that one or more Oracle RAC instances are up and running and can be", + "full_action": "Retry the backup after you verify the following:\n■ Verify that one or more Oracle RAC instances are up and running and can be\nconnected to.\n■ Verify the credentials that are used to connect to the Oracle RAC instance are\ncorrect in NetBackup." }, "5457": { "code": 5457, - "desc": "Banco de dados must não contain qualquer data arquivos que estão in backup mode.", - "first_action": "NetBackup fails qualquer jobs onde Oracle data arquivos estão", - "full_action": "NetBackup fails qualquer jobs onde Oracle data arquivos estão\ndetected to be in backup mode. Take o affected data arquivo fora de backup mode e\nre-run o backup." + "desc": "Database must not contain any data files that are in backup mode.", + "first_action": "NetBackup fails any jobs where Oracle data files are", + "full_action": "NetBackup fails any jobs where Oracle data files are\ndetected to be in backup mode. Take the affected data file out of backup mode and\nre-run the backup." }, "5458": { "code": 5458, - "desc": "O collection e backup de metadata foi unsuccessful.", - "first_action": "Examine o bpdbsbora e dbclient logs on o cliente", - "full_action": "Examine o bpdbsbora e dbclient logs on o cliente\n(Oracle servidor) to determinar o cause de o falha." + "desc": "The collection and backup of metadata was unsuccessful.", + "first_action": "Examine the bpdbsbora and dbclient logs on the client", + "full_action": "Examine the bpdbsbora and dbclient logs on the client\n(Oracle server) to determine the cause of the failure." }, "5459": { "code": 5459, - "desc": "Oracle e DB2 templates estão não supported.", + "desc": "Oracle and DB2 templates are not supported.", "first_action": "Oracle backups:", - "full_action": "You must convert o template into um Oracle Intelligent\nPolicy (OIP), scripts para Oracle, ou scripts para DB2 in o seguinte ways:\nOracle templates:\n■ Oracle backups:\n■ Convert o policy e template into um Oracle Intelligent Policy (OIP) usando\ntheNetBackupAdministrationConsoleortheNetBackupwebUI.Thisoption\nestá o one que está recomendada.\n■ Convert o template into um RMAN backup script. Replace o template in\no policy com this new backup script.\n■ Oracle restores:\n■ Convert o template into um RMAN restauração script.\nDB2 templates:\n■ DB2 backup\n■ ConvertthebackuptemplateintoaDB2backupscript.Replacethetemplate\nin o policy com this new backup script.\n■ DB2 restores:\n■ Convert o template into um DB2 restauração script." + "full_action": "You must convert the template into an Oracle Intelligent\nPolicy (OIP), scripts for Oracle, or scripts for DB2 in the following ways:\nOracle templates:\n■ Oracle backups:\n■ Convert the policy and template into an Oracle Intelligent Policy (OIP) using\ntheNetBackupAdministrationConsoleortheNetBackupwebUI.Thisoption\nis the one that is recommended.\n■ Convert the template into an RMAN backup script. Replace the template in\nthe policy with this new backup script.\n■ Oracle restores:\n■ Convert the template into an RMAN restore script.\nDB2 templates:\n■ DB2 backup\n■ ConvertthebackuptemplateintoaDB2backupscript.Replacethetemplate\nin the policy with this new backup script.\n■ DB2 restores:\n■ Convert the template into a DB2 restore script." }, "5461": { "code": 5461, - "desc": "Não data arquivo copies foram found on o NFS share.", - "first_action": "Um RMAN crosscheck must be performed.", - "full_action": "Um RMAN crosscheck must be performed." + "desc": "No data file copies were found on the NFS share.", + "first_action": "An RMAN crosscheck must be performed.", + "full_action": "An RMAN crosscheck must be performed." }, "5462": { "code": 5462, - "desc": "O Oracle clone operation foi unsuccessful.", - "first_action": "Review o job details to veja what falhou. You can also", - "full_action": "Review o job details to veja what falhou. You can also\nreview o bphdb, bpdbsbora, e dbclient logs on o cliente (Oracle servidor) e\nNBARS (NetBackup primary servidor) para more details." + "desc": "The Oracle clone operation was unsuccessful.", + "first_action": "Review the job details to see what failed. You can also", + "full_action": "Review the job details to see what failed. You can also\nreview the bphdb, bpdbsbora, and dbclient logs on the client (Oracle server) and\nNBARS (NetBackup primary server) for more details." }, "5464": { "code": 5464, - "desc": "Data corruption foi detected in o banco de dados during backup.", - "first_action": "Review o banco de dados para corruption.", - "full_action": "Executar o seguinte como appropriate:\n■ Review o banco de dados para corruption.\nIf corruption está confirmed, restauração o banco de dados from o most recent backup\nyou know está good.\n■ Validate o backup integrity before you restauração o databases.\n■ Investigatetherootcauseofthecorruptionandimplementpreventivemeasures\nlike regular backups e integrity checks." + "desc": "Data corruption was detected in the database during backup.", + "first_action": "Review the database for corruption.", + "full_action": "Perform the following as appropriate:\n■ Review the database for corruption.\nIf corruption is confirmed, restore the database from the most recent backup\nyou know is good.\n■ Validate the backup integrity before you restore the databases.\n■ Investigatetherootcauseofthecorruptionandimplementpreventivemeasures\nlike regular backups and integrity checks." }, "5500": { "code": 5500, - "desc": "Target destination foi não provided to recover o object.", - "first_action": "Add cloudObjectStoreRecoveryDestination in o", - "full_action": "Add cloudObjectStoreRecoveryDestination in o\nrecovery API. Para more informação, go to o SORT website\n(https://sort.veritas.com/), e under Supported Products select NetBackup.\nThen search para NetBackup Recovery API." + "desc": "Target destination was not provided to recover the object.", + "first_action": "Add cloudObjectStoreRecoveryDestination in the", + "full_action": "Add cloudObjectStoreRecoveryDestination in the\nrecovery API. For more information, go to the SORT website\n(https://sort.veritas.com/), and under Supported Products select NetBackup.\nThen search for NetBackup Recovery API." }, "5501": { "code": 5501, "desc": "Bucket name must be specified.", "first_action": "AddthetargetbucketnameintherecoveryAPI.Formore", - "full_action": "AddthetargetbucketnameintherecoveryAPI.Formore\ninformation,gototheSORTwebsite(https://sort.veritas.com/),andunderSupported\nProducts select NetBackup. Then search para NetBackup Recovery API." + "full_action": "AddthetargetbucketnameintherecoveryAPI.Formore\ninformation,gototheSORTwebsite(https://sort.veritas.com/),andunderSupported\nProducts select NetBackup. Then search for NetBackup Recovery API." }, "5502": { "code": 5502, "desc": "Provider name must be specified.", - "first_action": "Add o provider name in o recovery API. Para more", - "full_action": "Add o provider name in o recovery API. Para more\ninformation,gototheSORTwebsite(https://sort.veritas.com/),andunderSupported\nProducts select NetBackup. Then search para NetBackup Recovery API." + "first_action": "Add the provider name in the recovery API. For more", + "full_action": "Add the provider name in the recovery API. For more\ninformation,gototheSORTwebsite(https://sort.veritas.com/),andunderSupported\nProducts select NetBackup. Then search for NetBackup Recovery API." }, "5503": { "code": 5503, "desc": "Cloud object store account must be specified.", - "first_action": "Add o cloud object store account name in o recovery", - "full_action": "Add o cloud object store account name in o recovery\nAPI. Para more informação, go to o SORT website (https://sort.veritas.com/), e\nunder Supported Products select NetBackup. Then search para NetBackup\nRecovery API." + "first_action": "Add the cloud object store account name in the recovery", + "full_action": "Add the cloud object store account name in the recovery\nAPI. For more information, go to the SORT website (https://sort.veritas.com/), and\nunder Supported Products select NetBackup. Then search for NetBackup\nRecovery API." }, "5504": { "code": 5504, "desc": "Object/Blobs type must be specified.", - "first_action": "Add valid Object/Blobs type in o recovery API. Para", - "full_action": "Add valid Object/Blobs type in o recovery API. Para\nmore informação, go to o SORT website (https://sort.veritas.com/), e under\nSupported Products select NetBackup. Then search para NetBackup Recovery\nAPI." + "first_action": "Add valid Object/Blobs type in the recovery API. For", + "full_action": "Add valid Object/Blobs type in the recovery API. For\nmore information, go to the SORT website (https://sort.veritas.com/), and under\nSupported Products select NetBackup. Then search for NetBackup Recovery\nAPI." }, "5505": { "code": 5505, - "desc": "Recovery type must be specified como part de recovery request.", - "first_action": "Add um valid recovery type in o recovery API. Para more", - "full_action": "Add um valid recovery type in o recovery API. Para more\ninformation,gototheSORTwebsite(https://sort.veritas.com/),andunderSupported\nProducts select NetBackup. Then search para NetBackup Recovery API." + "desc": "Recovery type must be specified as part of recovery request.", + "first_action": "Add a valid recovery type in the recovery API. For more", + "full_action": "Add a valid recovery type in the recovery API. For more\ninformation,gototheSORTwebsite(https://sort.veritas.com/),andunderSupported\nProducts select NetBackup. Then search for NetBackup Recovery API." }, "5506": { "code": 5506, "desc": "Recovery Object/Blobs must be specified.", - "first_action": "Add recovery Object/Blobs if includeAll está false. Para", - "full_action": "Add recovery Object/Blobs if includeAll está false. Para\nmore informação, go to o SORT website (https://sort.veritas.com/), e under\nSupported Products select NetBackup. Then search para NetBackup Recovery\nAPI." + "first_action": "Add recovery Object/Blobs if includeAll is false. For", + "full_action": "Add recovery Object/Blobs if includeAll is false. For\nmore information, go to the SORT website (https://sort.veritas.com/), and under\nSupported Products select NetBackup. Then search for NetBackup Recovery\nAPI." }, "5507": { "code": 5507, - "desc": "Recovery Object/Blobs source não provided. NetBackup status codes 716 NetBackup status codes", - "first_action": "Add o Object/Blobs source in o recovery API. Para", - "full_action": "Add o Object/Blobs source in o recovery API. Para\nmore informação, go to o SORT website (https://sort.veritas.com/), e under\nSupported Products select NetBackup. Then search para NetBackup Recovery\nAPI." + "desc": "Recovery Object/Blobs source not provided. NetBackup status codes 716 NetBackup status codes", + "first_action": "Add the Object/Blobs source in the recovery API. For", + "full_action": "Add the Object/Blobs source in the recovery API. For\nmore information, go to the SORT website (https://sort.veritas.com/), and under\nSupported Products select NetBackup. Then search for NetBackup Recovery\nAPI." }, "5508": { "code": 5508, - "desc": "Não destination details provided como part de recovery request.", - "first_action": "Add o recovery destination details in o recovery API.", - "full_action": "Add o recovery destination details in o recovery API.\nFormoreinformation,gototheSORTwebsite(https://sort.veritas.com/),andunder\nSupported Products select NetBackup. Then search para NetBackup Recovery\nAPI." + "desc": "No destination details provided as part of recovery request.", + "first_action": "Add the recovery destination details in the recovery API.", + "full_action": "Add the recovery destination details in the recovery API.\nFormoreinformation,gototheSORTwebsite(https://sort.veritas.com/),andunder\nSupported Products select NetBackup. Then search for NetBackup Recovery\nAPI." }, "5509": { "code": 5509, - "desc": "Specified recovery type está não valid.", - "first_action": "Add um valid recovery type in o recovery API. Para more", - "full_action": "Add um valid recovery type in o recovery API. Para more\ninformation,gototheSORTwebsite(https://sort.veritas.com/),andunderSupported\nProducts select NetBackup. Then search para NetBackup Recovery API." + "desc": "Specified recovery type is not valid.", + "first_action": "Add a valid recovery type in the recovery API. For more", + "full_action": "Add a valid recovery type in the recovery API. For more\ninformation,gototheSORTwebsite(https://sort.veritas.com/),andunderSupported\nProducts select NetBackup. Then search for NetBackup Recovery API." }, "5510": { "code": 5510, - "desc": "Specified provider está não valid.", - "first_action": "Add um valid provider name in o recovery API. Para more", - "full_action": "Add um valid provider name in o recovery API. Para more\ninformation,gototheSORTwebsite(https://sort.veritas.com/),andunderSupported\nProducts select NetBackup. Then search para NetBackup Recovery API." + "desc": "Specified provider is not valid.", + "first_action": "Add a valid provider name in the recovery API. For more", + "full_action": "Add a valid provider name in the recovery API. For more\ninformation,gototheSORTwebsite(https://sort.veritas.com/),andunderSupported\nProducts select NetBackup. Then search for NetBackup Recovery API." }, "5511": { "code": 5511, - "desc": "O specified Object/Blobs value está inválido.", - "first_action": "Add um valid Object/Blobs value in o recovery API. Para", - "full_action": "Add um valid Object/Blobs value in o recovery API. Para\nmore informação, go to o SORT website (https://sort.veritas.com/), e under\nSupported Products select NetBackup. Then search para NetBackup Recovery\nAPI." + "desc": "The specified Object/Blobs value is invalid.", + "first_action": "Add a valid Object/Blobs value in the recovery API. For", + "full_action": "Add a valid Object/Blobs value in the recovery API. For\nmore information, go to the SORT website (https://sort.veritas.com/), and under\nSupported Products select NetBackup. Then search for NetBackup Recovery\nAPI." }, "5512": { "code": 5512, - "desc": "Não é possível retrieve qualquer objects com o specified prefix.", + "desc": "Cannot retrieve any objects with the specified prefix.", "first_action": "AddavalidprefixintherecoveryAPI.Formoreinformation,", - "full_action": "AddavalidprefixintherecoveryAPI.Formoreinformation,\ngototheSORTwebsite(https://sort.veritas.com/),andunderSupportedProducts\nselect NetBackup. Then search para NetBackup Recovery API." + "full_action": "AddavalidprefixintherecoveryAPI.Formoreinformation,\ngototheSORTwebsite(https://sort.veritas.com/),andunderSupportedProducts\nselect NetBackup. Then search for NetBackup Recovery API." }, "5513": { "code": 5513, - "desc": "Inválido destination bucket name provided.", - "first_action": "Add um valid bucket in o recovery API. Para more", - "full_action": "Add um valid bucket in o recovery API. Para more\ninformation,gototheSORTwebsite(https://sort.veritas.com/),andunderSupported\nProducts select NetBackup. Then search para NetBackup Recovery API." + "desc": "Invalid destination bucket name provided.", + "first_action": "Add a valid bucket in the recovery API. For more", + "full_action": "Add a valid bucket in the recovery API. For more\ninformation,gototheSORTwebsite(https://sort.veritas.com/),andunderSupported\nProducts select NetBackup. Then search for NetBackup Recovery API." }, "5514": { "code": 5514, - "desc": "Specified destination object/Prefix name está não valid. NetBackup status codes 718 NetBackup status codes", - "first_action": "Add um valid object/Prefix name in o recovery API.", - "full_action": "Add um valid object/Prefix name in o recovery API.\nFormoreinformation,gototheSORTwebsite(https://sort.veritas.com/),andunder\nSupported Products select NetBackup. Then search para NetBackup Recovery\nAPI." + "desc": "Specified destination object/Prefix name is not valid. NetBackup status codes 718 NetBackup status codes", + "first_action": "Add a valid object/Prefix name in the recovery API.", + "full_action": "Add a valid object/Prefix name in the recovery API.\nFormoreinformation,gototheSORTwebsite(https://sort.veritas.com/),andunder\nSupported Products select NetBackup. Then search for NetBackup Recovery\nAPI." }, "5517": { "code": 5517, - "desc": "Either o NetBackup version ou o operating system de o recovery host does não meet o minimum requirements.", - "first_action": "Review o operating system e version de o NetBackup mídia servidor.", - "full_action": "Executar o seguinte como appropriate:\n■ Review o operating system e version de o NetBackup mídia servidor.\n■ If o mídia servidor está RHEL, you must use NetBackup version 10.1 ou later.\n■ If o mídia servidor está SUSE, you must use NetBackup version está 11.0.0.1\nou later.\n■ If o configuration does não meet these requirements, either upgrade o\nNetBackup mídia servidor ou migrate o mídia servidor to um supported operating\nsystem.\n■ After you make o requerido changes, reconfigure o Cloud object store\ncredentials e retry o operation." + "desc": "Either the NetBackup version or the operating system of the recovery host does not meet the minimum requirements.", + "first_action": "Review the operating system and version of the NetBackup media server.", + "full_action": "Perform the following as appropriate:\n■ Review the operating system and version of the NetBackup media server.\n■ If the media server is RHEL, you must use NetBackup version 10.1 or later.\n■ If the media server is SUSE, you must use NetBackup version is 11.0.0.1\nor later.\n■ If the configuration does not meet these requirements, either upgrade the\nNetBackup media server or migrate the media server to a supported operating\nsystem.\n■ After you make the required changes, reconfigure the Cloud object store\ncredentials and retry the operation." }, "5532": { "code": 5532, - "desc": "Não é possível retrieve armazenamento unidade informação.", - "first_action": "Garanta que o armazenamento unidade está up e executando.", - "full_action": "Executar o seguinte como appropriate:\n■ Garanta que o armazenamento unidade está up e executando.\n■ Restart o mídia servidor on which o armazenamento unidade está configurado." + "desc": "Cannot retrieve storage unit information.", + "first_action": "Ensure that the storage unit is up and running.", + "full_action": "Perform the following as appropriate:\n■ Ensure that the storage unit is up and running.\n■ Restart the media server on which the storage unit is configured." }, "5533": { "code": 5533, - "desc": "O armazenamento unidade Qualquer está não supported para Cloud object store dynamic multistreaming.", - "first_action": "Select um specific Policy armazenamento option. Do não select o", - "full_action": "Select um specific Policy armazenamento option. Do não select o\noption Qualquer." + "desc": "The storage unit ANY is not supported for Cloud object store dynamic multistreaming.", + "first_action": "Select a specific Policy storage option. Do not select the", + "full_action": "Select a specific Policy storage option. Do not select the\noption ANY." }, "5534": { "code": 5534, - "desc": "Não é possível complete o backup because de um inválido input.", + "desc": "Cannot complete the backup because of an invalid input.", "first_action": "ReviewtheActivitymonitorforthereasonforfailureand", - "full_action": "ReviewtheActivitymonitorforthereasonforfailureand\ntake appropriate corrective ação. Then retry o backup." + "full_action": "ReviewtheActivitymonitorforthereasonforfailureand\ntake appropriate corrective action. Then retry the backup." }, "5535": { "code": 5535, - "desc": "Falhou to stop backup operation.", - "first_action": "Review o Activity monitor para o cause de o falha.", - "full_action": "Review o Activity monitor para o cause de o falha.\nConfirm que o backup image foi created e está recoverable. NetBackup\nautomatically cleans o stale data. If o backup image foi created e está\nrecoverable, não further ação está requerido." + "desc": "Failed to stop backup operation.", + "first_action": "Review the Activity monitor for the cause of the failure.", + "full_action": "Review the Activity monitor for the cause of the failure.\nConfirm that the backup image was created and is recoverable. NetBackup\nautomatically cleans the stale data. If the backup image was created and is\nrecoverable, no further action is required." }, "5536": { "code": 5536, - "desc": "Falhou to abrir o SQLite banco de dados.", - "first_action": "Confirm que o temporary banco de dados está accessible e", - "full_action": "Confirm que o temporary banco de dados está accessible e\nque o NetBackup usuário has o necessary permissions. Then retry o backup." + "desc": "Failed to open the SQLite database.", + "first_action": "Confirm that the temporary database is accessible and", + "full_action": "Confirm that the temporary database is accessible and\nthat the NetBackup user has the necessary permissions. Then retry the backup." }, "5537": { "code": 5537, - "desc": "Incorrectreadorwritepermissionsarespecifiedforthedownloadstaging caminho.", - "first_action": "Confirm que o NetBackup usuário has o correct", - "full_action": "Confirm que o NetBackup usuário has o correct\npermissions to ler e gravar o retry o backup." + "desc": "Incorrectreadorwritepermissionsarespecifiedforthedownloadstaging path.", + "first_action": "Confirm that the NetBackup user has the correct", + "full_action": "Confirm that the NetBackup user has the correct\npermissions to read and write the retry the backup." }, "5538": { "code": 5538, - "desc": "Incorrect ownership está specified para o download staging caminho.", - "first_action": "Provide o correct ownership to o NetBackup usuário para", - "full_action": "Provide o correct ownership to o NetBackup usuário para\no temporary staging area. O NetBackup usuário must have ler, gravar, e run\npermissions to o specified folder. Then retry o backup." + "desc": "Incorrect ownership is specified for the download staging path.", + "first_action": "Provide the correct ownership to the NetBackup user for", + "full_action": "Provide the correct ownership to the NetBackup user for\nthe temporary staging area. The NetBackup user must have read, write, and run\npermissions to the specified folder. Then retry the backup." }, "5540": { "code": 5540, - "desc": "Backup performance está slowed como o staging space nears capacity.", - "first_action": "Aumentar o amount de armazenamento space disponível at o", - "full_action": "Aumentar o amount de armazenamento space disponível at o\nstaging location." + "desc": "Backup performance is slowed as the staging space nears capacity.", + "first_action": "Increase the amount of storage space available at the", + "full_action": "Increase the amount of storage space available at the\nstaging location." }, "5541": { "code": 5541, - "desc": "Insufficient space at o specified staging location.", - "first_action": "Confirm que o staging location has sufficient space e", - "full_action": "Confirm que o staging location has sufficient space e\nthen retry o operation." + "desc": "Insufficient space at the specified staging location.", + "first_action": "Confirm that the staging location has sufficient space and", + "full_action": "Confirm that the staging location has sufficient space and\nthen retry the operation." }, "5542": { "code": 5542, - "desc": "O heartbeat listening service has esgotado fora.", - "first_action": "Review o Activity monitor para o causes de o falha", - "full_action": "Review o Activity monitor para o causes de o falha\ne take appropriate corrective ação. Then retry o backup." + "desc": "The heartbeat listening service has timed out.", + "first_action": "Review the Activity monitor for the causes of the failure", + "full_action": "Review the Activity monitor for the causes of the failure\nand take appropriate corrective action. Then retry the backup." }, "5543": { "code": 5543, - "desc": "O Cloud object store backup encontrado um internal erro.", - "first_action": "Review o Activity monitor para o causes de o falha", - "full_action": "Review o Activity monitor para o causes de o falha\ne take appropriate corrective ação. Then retry o backup." + "desc": "The Cloud object store backup encountered an internal error.", + "first_action": "Review the Activity monitor for the causes of the failure", + "full_action": "Review the Activity monitor for the causes of the failure\nand take appropriate corrective action. Then retry the backup." }, "5544": { "code": 5544, - "desc": "Backup falhou como erro ocorreu while fetching latest log object.", - "first_action": "Review o Activity monitor para o causes de o falha", - "full_action": "Review o Activity monitor para o causes de o falha\ne take appropriate corrective ação. Then retry o backup." + "desc": "Backup failed as error occurred while fetching latest log object.", + "first_action": "Review the Activity monitor for the causes of the failure", + "full_action": "Review the Activity monitor for the causes of the failure\nand take appropriate corrective action. Then retry the backup." }, "5545": { "code": 5545, - "desc": "Backup falhou como NetBackup não é possível parse records from o log object.", - "first_action": "Review o Activity monitor para o causes de o falha", - "full_action": "Review o Activity monitor para o causes de o falha\ne take appropriate corrective ação. Then retry o backup." + "desc": "Backup failed as NetBackup cannot parse records from the log object.", + "first_action": "Review the Activity monitor for the causes of the failure", + "full_action": "Review the Activity monitor for the causes of the failure\nand take appropriate corrective action. Then retry the backup." }, "5546": { "code": 5546, - "desc": "Não é possível retrieve o bucket logging informação from o source bucket.", - "first_action": "Review o configurations para o causes de o falha", - "full_action": "Review o configurations para o causes de o falha\ne take appropriate corrective ação. Then retry o backup." + "desc": "Cannot retrieve the bucket logging information from the source bucket.", + "first_action": "Review the configurations for the causes of the failure", + "full_action": "Review the configurations for the causes of the failure\nand take appropriate corrective action. Then retry the backup." }, "5547": { "code": 5547, - "desc": "Backup falhou due to um inválido marker, ou error(s) in reading, writing, ou extracting marker data.", - "first_action": "Garanta que bucket logging está enabled, confirm que o", - "full_action": "Garanta que bucket logging está enabled, confirm que o\npolicy está properly set on o target bucket, e retry o backup." + "desc": "Backup failed due to an invalid marker, or error(s) in reading, writing, or extracting marker data.", + "first_action": "Ensure that bucket logging is enabled, confirm that the", + "full_action": "Ensure that bucket logging is enabled, confirm that the\npolicy is properly set on the target bucket, and retry the backup." }, "5548": { "code": 5548, - "desc": "Um erro ocorreu while fetching cloud object properties. NetBackup status codes 723 NetBackup status codes", - "first_action": "Verifique o configuration, resolve o issue, e retry o", - "full_action": "Verifique o configuration, resolve o issue, e retry o\nbackup." + "desc": "An error occurred while fetching cloud object properties. NetBackup status codes 723 NetBackup status codes", + "first_action": "Check the configuration, resolve the issue, and retry the", + "full_action": "Check the configuration, resolve the issue, and retry the\nbackup." }, "5549": { "code": 5549, - "desc": "Não é possível validate bucket logging informação.", - "first_action": "Each source bucket must have um unique prefix. O prefix não é possível be vazio.", - "full_action": "Verifique o configuration e retry o backup operation.\nConfigurations should be like:\n■ Each source bucket must have um unique prefix. O prefix não é possível be vazio.\n■ O LoggingType attribute must be Journal.\n■ Set o TargetObjectKeyFormat attribute como PartitionedPrefix.\n■ Set o PartitionDateSource attribute como EventTime." + "desc": "Cannot validate bucket logging information.", + "first_action": "Each source bucket must have a unique prefix. The prefix cannot be empty.", + "full_action": "Check the configuration and retry the backup operation.\nConfigurations should be like:\n■ Each source bucket must have a unique prefix. The prefix cannot be empty.\n■ The LoggingType attribute must be Journal.\n■ Set the TargetObjectKeyFormat attribute as PartitionedPrefix.\n■ Set the PartitionDateSource attribute as EventTime." }, "5576": { "code": 5576, - "desc": "O maximum number de concurrent jobs specified para um armazenamento unidade, must be greater than ou equal to o number de streams specified in o policy.", - "first_action": "Aumentar o concurrent jobs setting para o armazenamento unidade", - "full_action": "Aumentar o concurrent jobs setting para o armazenamento unidade\nto match o number de streams specified in o policy." + "desc": "The maximum number of concurrent jobs specified for a storage unit, must be greater than or equal to the number of streams specified in the policy.", + "first_action": "Increase the concurrent jobs setting for the storage unit", + "full_action": "Increase the concurrent jobs setting for the storage unit\nto match the number of streams specified in the policy." }, "5577": { "code": 5577, - "desc": "Não é possível parse o specified field ou object.", - "first_action": "Verifique o Activity monitor para o exact reason para o", - "full_action": "Verifique o Activity monitor para o exact reason para o\nfalha. Resolve o issue, then retry o backup." + "desc": "Cannot parse the specified field or object.", + "first_action": "Check the Activity monitor for the exact reason for the", + "full_action": "Check the Activity monitor for the exact reason for the\nfailure. Resolve the issue, then retry the backup." }, "5578": { "code": 5578, - "desc": "CannotretrievetheimageinfofromNetBackupdatabaseforthespecified field ou object.", - "first_action": "Verifique o Activity monitor para o exact reason para", - "full_action": "Verifique o Activity monitor para o exact reason para\nmissing data. Resolve o issue, then retry o backup." + "desc": "CannotretrievetheimageinfofromNetBackupdatabaseforthespecified field or object.", + "first_action": "Check the Activity monitor for the exact reason for", + "full_action": "Check the Activity monitor for the exact reason for\nmissing data. Resolve the issue, then retry the backup." }, "5579": { "code": 5579, - "desc": "Fallingbacktoobjectlistingforchangedetection,notconsideringobject change tracking para this bucket, specified in o policy.", + "desc": "Fallingbacktoobjectlistingforchangedetection,notconsideringobject change tracking for this bucket, specified in the policy.", "first_action": "Thereisnoworkaroundforthisissue.Forallthesereasons,", - "full_action": "Thereisnoworkaroundforthisissue.Forallthesereasons,\nNetBackup uses object listing para change detection. NetBackup will revert to object\nchange tracking para o subsequent backups." + "full_action": "Thereisnoworkaroundforthisissue.Forallthesereasons,\nNetBackup uses object listing for change detection. NetBackup will revert to object\nchange tracking for the subsequent backups." }, "5580": { "code": 5580, - "desc": "O specified failover strategy para o armazenamento unidade group está incompatible com o Cloud object store policy, com dynamic multistreaming.", + "desc": "The specified failover strategy for the storage unit group is incompatible with the Cloud object store policy, with dynamic multistreaming.", "first_action": "UseacompatiblestorageunitgroupwiththeCloudobject", - "full_action": "UseacompatiblestorageunitgroupwiththeCloudobject\nstore policy.\nTo change armazenamento unidade selection\n1 In o NetBackup UI, on o left click Armazenamento, e then click Armazenamento units.\nClick o Armazenamento unidade group tab.\n2 Click Add to add um new armazenamento unidade, ou edit um existing one.\n3 UnderStorageunitselectionoptions,selectanyoftheseoptionsasrequired:\nPrioritized, Round Robin, ou Mídia Servidor Load Balancing.\nRetry o backup." + "full_action": "UseacompatiblestorageunitgroupwiththeCloudobject\nstore policy.\nTo change storage unit selection\n1 In the NetBackup UI, on the left click Storage, and then click Storage units.\nClick the Storage unit group tab.\n2 Click Add to add a new storage unit, or edit an existing one.\n3 UnderStorageunitselectionoptions,selectanyoftheseoptionsasrequired:\nPrioritized, Round Robin, or Media Server Load Balancing.\nRetry the backup." }, "5581": { "code": 5581, - "desc": "Não é possível parse o falhou object arquivo.", - "first_action": "Verifique o Activity monitor para o exact reason para o", - "full_action": "Verifique o Activity monitor para o exact reason para o\nfalha. Resolve o issue, then retry o backup." + "desc": "Cannot parse the failed object file.", + "first_action": "Check the Activity monitor for the exact reason for the", + "full_action": "Check the Activity monitor for the exact reason for the\nfailure. Resolve the issue, then retry the backup." }, "5582": { "code": 5582, - "desc": "Não é possível retrieve image handle.", - "first_action": "Verifique o Activity monitor para o exact reason para o", - "full_action": "Verifique o Activity monitor para o exact reason para o\nfalha. Resolve o issue, then retry o backup." + "desc": "Cannot retrieve image handle.", + "first_action": "Check the Activity monitor for the exact reason for the", + "full_action": "Check the Activity monitor for the exact reason for the\nfailure. Resolve the issue, then retry the backup." }, "5626": { "code": 5626, - "desc": "After you upgrade both o source e o target master servidor, you must update o trust relationship on both de o servers. After you update o trust relationship, you can make configuration changes related to o trusted master servers.", + "desc": "After you upgrade both the source and the target master server, you must update the trust relationship on both of the servers. After you update the trust relationship, you can make configuration changes related to the trusted master servers.", "first_action": "Domainname domain_name -username username -fpfile filename", - "full_action": "Run one de o seguinte commands on both o source\ne o target master servidor.\nRun o seguinte comando if you estão usando usuário credentials; you estão prompted to\nprovide o password:\nnbseccmd -setuptrustedmaster -update -masterserver\nmaster_server_name -remotemasterserver remote_master_server\n-domainname domain_name -username username -fpfile filename\nRun o seguinte comando if you estão usando um authorization token; you estão\nprompted to provide o token:\nnbseccmd -setuptrustedmaster -update -masterserver\nmaster_server_name -remotemasterserver remote_master_server\n-domainname domain_name -fpfile filename\nRun o seguinte comando if you estão usando o answer arquivo:\nnbseccmd -setuptrustedmaster -update -info answer_file\nFormoreinformationaboutthenbseccmdcommand,seetheNetBackupCommands\nReference Guide." + "full_action": "Run one of the following commands on both the source\nand the target master server.\nRun the following command if you are using user credentials; you are prompted to\nprovide the password:\nnbseccmd -setuptrustedmaster -update -masterserver\nmaster_server_name -remotemasterserver remote_master_server\n-domainname domain_name -username username -fpfile filename\nRun the following command if you are using an authorization token; you are\nprompted to provide the token:\nnbseccmd -setuptrustedmaster -update -masterserver\nmaster_server_name -remotemasterserver remote_master_server\n-domainname domain_name -fpfile filename\nRun the following command if you are using the answer file:\nnbseccmd -setuptrustedmaster -update -info answer_file\nFormoreinformationaboutthenbseccmdcommand,seetheNetBackupCommands\nReference Guide." }, "5631": { "code": 5631, - "desc": "O source master servidor uses um NetBackup CA-signed certificate e o target master servidor uses um external CA-signed certificate. Configure um external certificate on o source master servidor, which should be compatible com o target master servidor. NetBackup status codes 727 NetBackup status codes", - "first_action": "Garanta que you have configurado um external certificate", - "full_action": "Garanta que you have configurado um external certificate\non o source master servidor que está compatible com o target master servidor." + "desc": "The source master server uses a NetBackup CA-signed certificate and the target master server uses an external CA-signed certificate. Configure an external certificate on the source master server, which should be compatible with the target master server. NetBackup status codes 727 NetBackup status codes", + "first_action": "Ensure that you have configured an external certificate", + "full_action": "Ensure that you have configured an external certificate\non the source master server that is compatible with the target master server." }, "5761": { "code": 5761, - "desc": "Falhou to initialize Windows Socket library", - "first_action": "Nenhum", - "full_action": "Nenhum" + "desc": "Failed to initialize Windows Socket library", + "first_action": "None", + "full_action": "None" }, "5762": { "code": 5762, - "desc": "Peer está não um NetBackup Master ou Mídia Servidor", - "first_action": "Verifique que o requesting NetBackup servidor está indeed o", - "full_action": "Verifique que o requesting NetBackup servidor está indeed o\nmaster servidor como recognized por o NetBackup host returning this status code." + "desc": "Peer is not a NetBackup Master or Media Server", + "first_action": "Verify that the requesting NetBackup server is indeed the", + "full_action": "Verify that the requesting NetBackup server is indeed the\nmaster server as recognized by the NetBackup host returning this status code." }, "5763": { "code": 5763, - "desc": "Encontrado erro during socket communication", - "first_action": "If NetBackup está otherwise functioning correctly, this erro", - "full_action": "If NetBackup está otherwise functioning correctly, this erro\nrequires Cohesity Technical Support assistance." + "desc": "Encountered error during socket communication", + "first_action": "If NetBackup is otherwise functioning correctly, this error", + "full_action": "If NetBackup is otherwise functioning correctly, this error\nrequires Cohesity Technical Support assistance." }, "5764": { "code": 5764, - "desc": "Comando specified para execution está inválido ou não allowed", - "first_action": "Contate Cohesity Technical Support para assistance.", - "full_action": "Contate Cohesity Technical Support para assistance." + "desc": "Command specified for execution is invalid or not allowed", + "first_action": "Contact Cohesity Technical Support for assistance.", + "full_action": "Contact Cohesity Technical Support for assistance." }, "5765": { "code": 5765, - "desc": "Falhou to execute specified comando (CreateProcess ou exec)", + "desc": "Failed to execute specified command (CreateProcess or exec)", "first_action": "RetrytheLoggingAssistantaction.Iftheproblempersists,", - "full_action": "RetrytheLoggingAssistantaction.Iftheproblempersists,\ncontate Cohesity Technical Support." + "full_action": "RetrytheLoggingAssistantaction.Iftheproblempersists,\ncontact Cohesity Technical Support." }, "5766": { "code": 5766, - "desc": "Falhou to execute specified comando (fork)", + "desc": "Failed to execute specified command (fork)", "first_action": "RetrytheLoggingAssistantaction.Iftheproblempersists,", - "full_action": "RetrytheLoggingAssistantaction.Iftheproblempersists,\ncontate Cohesity Technical Support." + "full_action": "RetrytheLoggingAssistantaction.Iftheproblempersists,\ncontact Cohesity Technical Support." }, "5767": { "code": 5767, - "desc": "Falhou to get exit code de child process", + "desc": "Failed to get exit code of child process", "first_action": "Ifthiserrorisnottheresultofmanualintervention,contact", "full_action": "Ifthiserrorisnottheresultofmanualintervention,contact\nCohesity Technical Support." }, "5768": { "code": 5768, - "desc": "Falhou to ler complete output de executed comando", + "desc": "Failed to read complete output of executed command", "first_action": "RetrytheLoggingAssistantaction.Iftheproblempersists,", - "full_action": "RetrytheLoggingAssistantaction.Iftheproblempersists,\ncontate Cohesity Technical Support." + "full_action": "RetrytheLoggingAssistantaction.Iftheproblempersists,\ncontact Cohesity Technical Support." }, "5769": { "code": 5769, - "desc": "Falhou to reap exit code de child process", + "desc": "Failed to reap exit code of child process", "first_action": "Ifthiserrorisnottheresultofmanualintervention,contact", "full_action": "Ifthiserrorisnottheresultofmanualintervention,contact\nCohesity Technical Support." }, "5770": { "code": 5770, - "desc": "Falhou to get cluster configuration", - "first_action": "Nenhum", - "full_action": "Nenhum" + "desc": "Failed to get cluster configuration", + "first_action": "None", + "full_action": "None" }, "5771": { "code": 5771, - "desc": "Falhou to gravar output received from remote comando", + "desc": "Failed to write output received from remote command", "first_action": "Ifthiserrorisnottheresultofmanualintervention,contact", "full_action": "Ifthiserrorisnottheresultofmanualintervention,contact\nCohesity Technical Support." }, "5772": { "code": 5772, - "desc": "Falhou to ler unified logging configuration arquivo", - "first_action": "Verifique o existence e o format de o VxUL", - "full_action": "Verifique o existence e o format de o VxUL\nconfigurationfilethatwasmentionedalongwiththeerrormessageonthespecified\nNetBackup host." + "desc": "Failed to read unified logging configuration file", + "first_action": "Check the existence and the format of the VxUL", + "full_action": "Check the existence and the format of the VxUL\nconfigurationfilethatwasmentionedalongwiththeerrormessageonthespecified\nNetBackup host." }, "5773": { "code": 5773, - "desc": "Falhou to get virtual name de primary servidor", - "first_action": "Nenhum", - "full_action": "Nenhum" + "desc": "Failed to get virtual name of primary server", + "first_action": "None", + "full_action": "None" }, "5774": { "code": 5774, - "desc": "Specified logs estão não valid", - "first_action": "Contate Cohesity Technical Support para assistance.", - "full_action": "Contate Cohesity Technical Support para assistance." + "desc": "Specified logs are not valid", + "first_action": "Contact Cohesity Technical Support for assistance.", + "full_action": "Contact Cohesity Technical Support for assistance." }, "5775": { "code": 5775, - "desc": "Inválido option specified", - "first_action": "Contate Cohesity Technical Support para assistance.", - "full_action": "Contate Cohesity Technical Support para assistance." + "desc": "Invalid option specified", + "first_action": "Contact Cohesity Technical Support for assistance.", + "full_action": "Contact Cohesity Technical Support for assistance." }, "5776": { "code": 5776, - "desc": "Falhou to spawn new process", - "first_action": "Contate Cohesity Technical Support para assistance.", - "full_action": "Contate Cohesity Technical Support para assistance." + "desc": "Failed to spawn new process", + "first_action": "Contact Cohesity Technical Support for assistance.", + "full_action": "Contact Cohesity Technical Support for assistance." }, "5777": { "code": 5777, - "desc": "Falhou to create staging diretório on primary servidor", - "first_action": "Verifique que o specified caminho already exists. If não, try to", - "full_action": "Verifique que o specified caminho already exists. If não, try to\ncreate it manually." + "desc": "Failed to create staging directory on primary server", + "first_action": "Verify that the specified path already exists. If not, try to", + "full_action": "Verify that the specified path already exists. If not, try to\ncreate it manually." }, "5778": { "code": 5778, - "desc": "Falhou to ler Logging Assistant banco de dados", + "desc": "Failed to read Logging Assistant database", "first_action": "CheckpermissionsoftheLoggingAssistantdatabasefile:", "full_action": "CheckpermissionsoftheLoggingAssistantdatabasefile:\nUNIX: /usr/openv/var/global/logasst.db\nWindows: \\Veritas\\NetBackup\\var\\global\\logasst.db" }, "5779": { "code": 5779, - "desc": "Falhou to lock Logging Assistant banco de dados", + "desc": "Failed to lock Logging Assistant database", "first_action": "Iftheproblempersists,contactCohesityTechnicalSupport.", "full_action": "Iftheproblempersists,contactCohesityTechnicalSupport." }, "5780": { "code": 5780, - "desc": "Falhou to set non-inherit flag on banco de dados arquivo handle", - "first_action": "Contate Cohesity Technical Support para assistance.", - "full_action": "Contate Cohesity Technical Support para assistance." + "desc": "Failed to set non-inherit flag on database file handle", + "first_action": "Contact Cohesity Technical Support for assistance.", + "full_action": "Contact Cohesity Technical Support for assistance." }, "5781": { "code": 5781, - "desc": "Falhou to prepare to save Logging Assistant banco de dados", + "desc": "Failed to prepare to save Logging Assistant database", "first_action": "Iftheproblempersists,contactCohesityTechnicalSupport.", "full_action": "Iftheproblempersists,contactCohesityTechnicalSupport." }, "5782": { "code": 5782, - "desc": "Falhou to start to gravar Logging Assistant banco de dados", + "desc": "Failed to start to write Logging Assistant database", "first_action": "Iftheproblempersists,contactCohesityTechnicalSupport.", "full_action": "Iftheproblempersists,contactCohesityTechnicalSupport." }, "5783": { "code": 5783, - "desc": "Falhou to save Logging Assistant banco de dados", + "desc": "Failed to save Logging Assistant database", "first_action": "Iftheproblempersists,contactCohesityTechnicalSupport.", "full_action": "Iftheproblempersists,contactCohesityTechnicalSupport." }, "5784": { "code": 5784, - "desc": "Falhou to access ou gravar o readme ou progress arquivo", - "first_action": "Por favor verifique o specified caminho.", - "full_action": "Por favor verifique o specified caminho." + "desc": "Failed to access or write the readme or progress file", + "first_action": "Please check the specified path.", + "full_action": "Please check the specified path." }, "5786": { "code": 5786, - "desc": "Logging Assistant record does não exist", - "first_action": "Refresh o Logging Assistant GUI, then verifique if o", - "full_action": "Refresh o Logging Assistant GUI, then verifique if o\nrecord has been deleted." + "desc": "Logging Assistant record does not exist", + "first_action": "Refresh the Logging Assistant GUI, then check if the", + "full_action": "Refresh the Logging Assistant GUI, then check if the\nrecord has been deleted." }, "5787": { "code": 5787, "desc": "Logging Assistant record already exists", - "first_action": "Nenhum", - "full_action": "Nenhum" + "first_action": "None", + "full_action": "None" }, "5788": { "code": 5788, - "desc": "Debug logging has não been set up para Logging Assistant record", - "first_action": "Refresh o Logging Assistant GUI view e retry.", - "full_action": "Refresh o Logging Assistant GUI view e retry." + "desc": "Debug logging has not been set up for Logging Assistant record", + "first_action": "Refresh the Logging Assistant GUI view and retry.", + "full_action": "Refresh the Logging Assistant GUI view and retry." }, "5789": { "code": 5789, - "desc": "Falhou to interpret bpdbjobs output para job detail", - "first_action": "Manually select o debug logging to set up. Contate", - "full_action": "Manually select o debug logging to set up. Contate\nCohesity Technical Support to investigate o Job Analysis falha." + "desc": "Failed to interpret bpdbjobs output for job detail", + "first_action": "Manually select the debug logging to set up. Contact", + "full_action": "Manually select the debug logging to set up. Contact\nCohesity Technical Support to investigate the Job Analysis failure." }, "5790": { "code": 5790, - "desc": "Falhou to fetch PureDisk configuration setting from Windows registry", - "first_action": "Contate Cohesity Technical Support para assistance.", - "full_action": "Contate Cohesity Technical Support para assistance." + "desc": "Failed to fetch PureDisk configuration setting from Windows registry", + "first_action": "Contact Cohesity Technical Support for assistance.", + "full_action": "Contact Cohesity Technical Support for assistance." }, "5794": { "code": 5794, - "desc": "Falhou to calculate debug logs size para preview", + "desc": "Failed to calculate debug logs size for preview", "first_action": "Iftheproblempersists,contactCohesityTechnicalSupport.", "full_action": "Iftheproblempersists,contactCohesityTechnicalSupport." }, "5796": { "code": 5796, - "desc": "LoggingAssistantagentencounteredfailurewritingonsockettoprimary servidor", + "desc": "LoggingAssistantagentencounteredfailurewritingonsockettoprimary server", "first_action": "RetrytheLoggingAssistantaction.Iftheproblempersists,", - "full_action": "RetrytheLoggingAssistantaction.Iftheproblempersists,\ncontate Cohesity Technical Support." + "full_action": "RetrytheLoggingAssistantaction.Iftheproblempersists,\ncontact Cohesity Technical Support." }, "5798": { "code": 5798, - "desc": "Falhou to list disco volumes on primary servidor usando bpmount", + "desc": "Failed to list disk volumes on primary server using bpmount", "first_action": "Iftheproblempersists,contactCohesityTechnicalSupport.", - "full_action": "Iftheproblempersists,contactCohesityTechnicalSupport.\nYou may still be able to manually establish liberar space informação e initiate o\nintended ação such como log collection." + "full_action": "Iftheproblempersists,contactCohesityTechnicalSupport.\nYou may still be able to manually establish free space information and initiate the\nintended action such as log collection." }, "5799": { "code": 5799, - "desc": "Falhou to get disco space informação de volumes ou mount points", + "desc": "Failed to get disk space information of volumes or mount points", "first_action": "Iftheproblempersists,contactCohesityTechnicalSupport.", - "full_action": "Iftheproblempersists,contactCohesityTechnicalSupport.\nYou may still be able to manually establish liberar space informação e initiate o\nintended ação such como log collection." + "full_action": "Iftheproblempersists,contactCohesityTechnicalSupport.\nYou may still be able to manually establish free space information and initiate the\nintended action such as log collection." }, "5800": { "code": 5800, - "desc": "Falhou to execute bpdbjobs to fetch job details", + "desc": "Failed to execute bpdbjobs to fetch job details", "first_action": "Iftheproblempersists,contactCohesityTechnicalSupport.", "full_action": "Iftheproblempersists,contactCohesityTechnicalSupport." }, "5801": { "code": 5801, - "desc": "Falhou to fetch job details. Verifique if job exists.", + "desc": "Failed to fetch job details. Check if job exists.", "first_action": "IfthespecifiedjobIDdoesexist,contactCohesityTechnical", "full_action": "IfthespecifiedjobIDdoesexist,contactCohesityTechnical\nSupport." }, "5803": { "code": 5803, - "desc": "Falhou to modify PureDisk configuration arquivo", - "first_action": "Contate Cohesity Technical Support para assistance.", - "full_action": "Contate Cohesity Technical Support para assistance." + "desc": "Failed to modify PureDisk configuration file", + "first_action": "Contact Cohesity Technical Support for assistance.", + "full_action": "Contact Cohesity Technical Support for assistance." }, "5804": { "code": 5804, - "desc": "Falhou to modify Java GUI configuration arquivo (Debug.properties)", - "first_action": "Contate Cohesity Technical Support para assistance.", - "full_action": "Contate Cohesity Technical Support para assistance." + "desc": "Failed to modify Java GUI configuration file (Debug.properties)", + "first_action": "Contact Cohesity Technical Support for assistance.", + "full_action": "Contact Cohesity Technical Support for assistance." }, "5805": { "code": 5805, "desc": "RemotehostNetBackupversionnotsupportedbytheLoggingAssistant", - "first_action": "Nenhum", - "full_action": "Nenhum" + "first_action": "None", + "full_action": "None" }, "5806": { "code": 5806, - "desc": "Unexpected contents de PureDisk configuration arquivo (pdregistry.cfg)", - "first_action": "Contate Cohesity Technical Support para assistance.", - "full_action": "Contate Cohesity Technical Support para assistance." + "desc": "Unexpected contents of PureDisk configuration file (pdregistry.cfg)", + "first_action": "Contact Cohesity Technical Support for assistance.", + "full_action": "Contact Cohesity Technical Support for assistance." }, "5807": { "code": 5807, - "desc": "Falhou to copy nbcplogs/nbsu output arquivo from remote host", - "first_action": "Verifique que o conexão from o master servidor to bpcd", - "full_action": "Verifique que o conexão from o master servidor to bpcd\ncan be set up por usando bptestbpcd." + "desc": "Failed to copy nbcplogs/nbsu output file from remote host", + "first_action": "Check that the connection from the master server to bpcd", + "full_action": "Check that the connection from the master server to bpcd\ncan be set up by using bptestbpcd." }, "5808": { "code": 5808, - "desc": "Falhou to load PBX configuration to change log level NetBackup status codes 737 NetBackup status codes", - "first_action": "Verifique o existence e format de o PBX configuration", - "full_action": "Verifique o existence e format de o PBX configuration\narquivo e o erro message on o specified NetBackup host." + "desc": "Failed to load PBX configuration to change log level NetBackup status codes 737 NetBackup status codes", + "first_action": "Check the existence and format of the PBX configuration", + "full_action": "Check the existence and format of the PBX configuration\nfile and the error message on the specified NetBackup host." }, "5809": { "code": 5809, - "desc": "Inválido PBX Debug Log Level specified", - "first_action": "Set o PBX logging level to um appropriate value.", - "full_action": "Set o PBX logging level to um appropriate value." + "desc": "Invalid PBX Debug Log Level specified", + "first_action": "Set the PBX logging level to an appropriate value.", + "full_action": "Set the PBX logging level to an appropriate value." }, "5811": { "code": 5811, - "desc": "Temporary diretório to use para logs collection does não exist", - "first_action": "Verifique o diretório permissions on o NetBackup host.", - "full_action": "Verifique o diretório permissions on o NetBackup host.\nAlso verifique que o parent diretório de o specified temporary diretório exists." + "desc": "Temporary directory to use for logs collection does not exist", + "first_action": "Check the directory permissions on the NetBackup host.", + "full_action": "Check the directory permissions on the NetBackup host.\nAlso verify that the parent directory of the specified temporary directory exists." }, "5812": { "code": 5812, - "desc": "Nbcplogs exited com erro", - "first_action": "Contate Cohesity Technical Support para assistance.", - "full_action": "Contate Cohesity Technical Support para assistance." + "desc": "Nbcplogs exited with error", + "first_action": "Contact Cohesity Technical Support for assistance.", + "full_action": "Contact Cohesity Technical Support for assistance." }, "5813": { "code": 5813, - "desc": "Nbcplogs did não collect qualquer logs", - "first_action": "Verifique que o debug logs on o host estão disponível to", - "full_action": "Verifique que o debug logs on o host estão disponível to\ncollect. If o debug logs relevant to o Logging Assistant record exist on o host,\ncontate Cohesity Technical Support." + "desc": "Nbcplogs did not collect any logs", + "first_action": "Check that the debug logs on the host are available to", + "full_action": "Check that the debug logs on the host are available to\ncollect. If the debug logs relevant to the Logging Assistant record exist on the host,\ncontact Cohesity Technical Support." }, "5814": { "code": 5814, - "desc": "Nbsu exited com erro", - "first_action": "Contate Cohesity Technical Support para assistance.", - "full_action": "Contate Cohesity Technical Support para assistance." + "desc": "Nbsu exited with error", + "first_action": "Contact Cohesity Technical Support for assistance.", + "full_action": "Contact Cohesity Technical Support for assistance." }, "5815": { "code": 5815, - "desc": "Não activity para o Logging Assistant record está in progress", - "first_action": "Refresh o Logging Assistant GUI e retry.", - "full_action": "Refresh o Logging Assistant GUI e retry." + "desc": "No activity for the Logging Assistant record is in progress", + "first_action": "Refresh the Logging Assistant GUI and retry.", + "full_action": "Refresh the Logging Assistant GUI and retry." }, "5816": { "code": 5816, "desc": "Collect debug logs operation canceled", - "first_action": "Retry o operation e if o issue persists, visit", - "full_action": "Retry o operation e if o issue persists, visit\nsupport.veritas.com. O Cohesity Technical Support website site offers additional\ninformação to help you troubleshoot this issue." + "first_action": "Retry the operation and if the issue persists, visit", + "full_action": "Retry the operation and if the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support website site offers additional\ninformation to help you troubleshoot this issue." }, "5817": { "code": 5817, "desc": "Collect nbsu operation canceled.", - "first_action": "Retry o operation e if o issue persists, visit", - "full_action": "Retry o operation e if o issue persists, visit\nsupport.veritas.com. O Cohesity Technical Support website site offers additional\ninformação to help you troubleshoot this issue." + "first_action": "Retry the operation and if the issue persists, visit", + "full_action": "Retry the operation and if the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support website site offers additional\ninformation to help you troubleshoot this issue." }, "5819": { "code": 5819, - "desc": "Cancel operation solicitado", - "first_action": "Retry o operation e if o issue persists, visit", - "full_action": "Retry o operation e if o issue persists, visit\nsupport.veritas.com. O Cohesity Technical Support website site offers additional\ninformação to help you troubleshoot this issue." + "desc": "Cancel operation requested", + "first_action": "Retry the operation and if the issue persists, visit", + "full_action": "Retry the operation and if the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support website site offers additional\ninformation to help you troubleshoot this issue." }, "5820": { "code": 5820, - "desc": "Não um valid Logging Assistant temporary diretório para clean-up", - "first_action": "Enter um valid Logging Assistant temporary diretório e", - "full_action": "Enter um valid Logging Assistant temporary diretório e\nretry o operation. If o issue persists, visit support.veritas.com. O Cohesity\nTechnicalSupportwebsitesiteoffersadditionalinformationtohelpyoutroubleshoot\nthis issue." + "desc": "Not a valid Logging Assistant temporary directory for clean-up", + "first_action": "Enter a valid Logging Assistant temporary directory and", + "full_action": "Enter a valid Logging Assistant temporary directory and\nretry the operation. If the issue persists, visit support.veritas.com. The Cohesity\nTechnicalSupportwebsitesiteoffersadditionalinformationtohelpyoutroubleshoot\nthis issue." }, "5821": { "code": 5821, - "desc": "Falhou to get policy details", + "desc": "Failed to get policy details", "first_action": "Iftheassociatedpolicydoesexist,pleasecontactCohesity", "full_action": "Iftheassociatedpolicydoesexist,pleasecontactCohesity\nTechnical Support." }, "5902": { "code": 5902, - "desc": "Fingerprint de o certificate could não be generated.", - "first_action": "Run o nbcertcmd -getCACertificate comando e", - "full_action": "Run o nbcertcmd -getCACertificate comando e\ntry to generate o CA certificate again." + "desc": "Fingerprint of the certificate could not be generated.", + "first_action": "Run the nbcertcmd -getCACertificate command and", + "full_action": "Run the nbcertcmd -getCACertificate command and\ntry to generate the CA certificate again." }, "5903": { "code": 5903, - "desc": "CA certificate could não be verified.", - "first_action": "O NetBackup host must trust o CA. Verifique if o CA", - "full_action": "O NetBackup host must trust o CA. Verifique if o CA\ncertificate foi added to o trust store com o nbcertcmd -listCACertDetails\ncommand.Runthenbcertcmd -getCACertificatecommandtoaddthecertificate\nto o trust store.\nIf o trust store has multiple certificates com o same (generic) name, contate\nCohesity Technical Support." + "desc": "CA certificate could not be verified.", + "first_action": "The NetBackup host must trust the CA. Check if the CA", + "full_action": "The NetBackup host must trust the CA. Check if the CA\ncertificate was added to the trust store with the nbcertcmd -listCACertDetails\ncommand.Runthenbcertcmd -getCACertificatecommandtoaddthecertificate\nto the trust store.\nIf the trust store has multiple certificates with the same (generic) name, contact\nCohesity Technical Support." }, "5904": { "code": 5904, - "desc": "Internal erro.", - "first_action": "Rerun o operation. If o problema persists, save todos de", - "full_action": "Rerun o operation. If o problema persists, save todos de\no erro log informação e contate Cohesity Technical Support." + "desc": "Internal error.", + "first_action": "Rerun the operation. If the problem persists, save all of", + "full_action": "Rerun the operation. If the problem persists, save all of\nthe error log information and contact Cohesity Technical Support." }, "5905": { "code": 5905, - "desc": "O host ID está não valid. NetBackup status codes 741 NetBackup status codes", - "first_action": "ListCertDetails comando. If o specified NetBackup host está part de multiple", - "full_action": "Verifique o specified host ID usando o nbcertcmd\n-listCertDetails comando. If o specified NetBackup host está part de multiple\nNetBackup domains, garanta que you estão providing o correct host ID que\ncorresponds to o specified NetBackup domain." + "desc": "The host ID is not valid. NetBackup status codes 741 NetBackup status codes", + "first_action": "ListCertDetails command. If the specified NetBackup host is part of multiple", + "full_action": "Check the specified host ID using the nbcertcmd\n-listCertDetails command. If the specified NetBackup host is part of multiple\nNetBackup domains, ensure that you are providing the correct host ID that\ncorresponds to the specified NetBackup domain." }, "5906": { "code": 5906, - "desc": "O token está não valid.", - "first_action": "Redo o ação. If o problema continues, save todos de o", - "full_action": "Redo o ação. If o problema continues, save todos de o\nerro log informação e contate Cohesity Technical Support." + "desc": "The token is not valid.", + "first_action": "Redo the action. If the problem continues, save all of the", + "full_action": "Redo the action. If the problem continues, save all of the\nerror log information and contact Cohesity Technical Support." }, "5907": { "code": 5907, - "desc": "Unknown resource solicitado.", - "first_action": "Verifique o certificate details que you provided. Details can", - "full_action": "Verifique o certificate details que you provided. Details can\ninclude um serial number, host ID, ou host name." + "desc": "Unknown resource requested.", + "first_action": "Verify the certificate details that you provided. Details can", + "full_action": "Verify the certificate details that you provided. Details can\ninclude a serial number, host ID, or host name." }, "5908": { "code": 5908, - "desc": "Unknown erro ocorreu.", - "first_action": "Save o erro log informação para o nbcert log e", - "full_action": "Save o erro log informação para o nbcert log e\ncontate Cohesity Technical Support." + "desc": "Unknown error occurred.", + "first_action": "Save the error log information for the nbcert log and", + "full_action": "Save the error log information for the nbcert log and\ncontact Cohesity Technical Support." }, "5909": { "code": 5909, - "desc": "Token does não exist para this token value.", - "first_action": "Provide o correct token value e rerun o operation.", - "full_action": "Provide o correct token value e rerun o operation." + "desc": "Token does not exist for this token value.", + "first_action": "Provide the correct token value and rerun the operation.", + "full_action": "Provide the correct token value and rerun the operation." }, "5910": { "code": 5910, - "desc": "Host name está não specified.", - "first_action": "Rerun o operation. If o problema continues, save todos de", - "full_action": "Rerun o operation. If o problema continues, save todos de\no erro log informação e contate Cohesity Technical Support." + "desc": "Host name is not specified.", + "first_action": "Rerun the operation. If the problem continues, save all of", + "full_action": "Rerun the operation. If the problem continues, save all of\nthe error log information and contact Cohesity Technical Support." }, "5913": { "code": 5913, - "desc": "Um token com this name already exists.", - "first_action": "Provide um new name e then recreate o token.", - "full_action": "Provide um new name e then recreate o token." + "desc": "A token with this name already exists.", + "first_action": "Provide a new name and then recreate the token.", + "full_action": "Provide a new name and then recreate the token." }, "5914": { "code": 5914, - "desc": "O security service está não disponível.", - "first_action": "Verifique o rede connectivity de o host on which you", - "full_action": "Verifique o rede connectivity de o host on which you\nestão performing o operation. Contate o NetBackup administrator to correct o\nstatus de o NetBackup web service." + "desc": "The security service is not available.", + "first_action": "Check the network connectivity of the host on which you", + "full_action": "Check the network connectivity of the host on which you\nare performing the operation. Contact the NetBackup administrator to correct the\nstatus of the NetBackup web service." }, "5915": { "code": 5915, - "desc": "Tempo limite da requisição esgotado.", - "first_action": "Verifique o rede connectivity de o host on which you", - "full_action": "Verifique o rede connectivity de o host on which you\nestão performing o operation. Contate o NetBackup administrator to correct o\nstatus de o NetBackup web service." + "desc": "Request timed out.", + "first_action": "Check the network connectivity of the host on which you", + "full_action": "Check the network connectivity of the host on which you\nare performing the operation. Contact the NetBackup administrator to correct the\nstatus of the NetBackup web service." }, "5916": { "code": 5916, - "desc": "Token name está não specified.", - "first_action": "Rerun o operation. If o problema persists, save todos de", - "full_action": "Rerun o operation. If o problema persists, save todos de\no erro log informação e contate Cohesity Technical Support." + "desc": "Token name is not specified.", + "first_action": "Rerun the operation. If the problem persists, save all of", + "full_action": "Rerun the operation. If the problem persists, save all of\nthe error log information and contact Cohesity Technical Support." }, "5917": { "code": 5917, - "desc": "O reissue token não é possível have o uso count greater than one.", + "desc": "The reissue token cannot have the usage count greater than one.", "first_action": "Amulti-usetokencannotbeassociatedwiththehost.The", - "full_action": "Amulti-usetokencannotbeassociatedwiththehost.The\nre-issue token não é possível be um multi-use token. Take appropriate ação e generate\no requerido token." + "full_action": "Amulti-usetokencannotbeassociatedwiththehost.The\nre-issue token cannot be a multi-use token. Take appropriate action and generate\nthe required token." }, "5918": { "code": 5918, - "desc": "O maximum uso count para o token should be provided within o valid range, which está from 1 to 99999.", - "first_action": "Select um valid uso count.", - "full_action": "Select um valid uso count." + "desc": "The maximum usage count for the token should be provided within the valid range, which is from 1 to 99999.", + "first_action": "Select a valid usage count.", + "full_action": "Select a valid usage count." }, "5919": { "code": 5919, - "desc": "Validity period specified para this token está não valid. O maximum validity period que you can specify está 999 days.", - "first_action": "Select um valid period.", - "full_action": "Select um valid period." + "desc": "Validity period specified for this token is not valid. The maximum validity period that you can specify is 999 days.", + "first_action": "Select a valid period.", + "full_action": "Select a valid period." }, "5920": { "code": 5920, - "desc": "O specified token está associated com um different host name.", - "first_action": "Verifique que you estão usando o correct token. If o specified", - "full_action": "Verifique que you estão usando o correct token. If o specified\nNetBackup host está associated com multiple NetBackup domains, garanta que you\nestão usando o token que corresponds to o appropriate NetBackup domain." + "desc": "The specified token is associated with a different host name.", + "first_action": "Verify that you are using the correct token. If the specified", + "full_action": "Verify that you are using the correct token. If the specified\nNetBackup host is associated with multiple NetBackup domains, ensure that you\nare using the token that corresponds to the appropriate NetBackup domain." }, "5921": { "code": 5921, - "desc": "O specified token está associated com um different host ID.", - "first_action": "Verifique que you estão usando o correct token.", - "full_action": "Verifique que you estão usando o correct token." + "desc": "The specified token is associated with a different host ID.", + "first_action": "Verify that you are using the correct token.", + "full_action": "Verify that you are using the correct token." }, "5922": { "code": 5922, - "desc": "O reissue token não é possível be associated com o host name.", - "first_action": "Use either o host ID ou o host name e try to", - "full_action": "Use either o host ID ou o host name e try to\nregenerate o token." + "desc": "The reissue token cannot be associated with the host name.", + "first_action": "Use either the host ID or the host name and try to", + "full_action": "Use either the host ID or the host name and try to\nregenerate the token." }, "5925": { "code": 5925, - "desc": "O requerido data está missing.", - "first_action": "Garanta que todos de o requerido inputs provided estão correct", - "full_action": "Garanta que todos de o requerido inputs provided estão correct\nandretrytheoperation.Iftheproblemcontinues,savealloftheerrorloginformation\ne contate Cohesity Technical Support." + "desc": "The required data is missing.", + "first_action": "Ensure that all of the required inputs provided are correct", + "full_action": "Ensure that all of the required inputs provided are correct\nandretrytheoperation.Iftheproblemcontinues,savealloftheerrorloginformation\nand contact Cohesity Technical Support." }, "5926": { "code": 5926, - "desc": "Certificate signing request está não valid.", + "desc": "Certificate signing request is not valid.", "first_action": "Regeneratethecertificaterequestfile,reruntheoperation,", - "full_action": "Regeneratethecertificaterequestfile,reruntheoperation,\ne garanta que o data has não changed in transit." + "full_action": "Regeneratethecertificaterequestfile,reruntheoperation,\nand ensure that the data has not changed in transit." }, "5927": { "code": 5927, - "desc": "O specified arquivo could não be opened.", - "first_action": "Use um valid arquivo name e try to abrir o arquivo ou verifique", - "full_action": "Use um valid arquivo name e try to abrir o arquivo ou verifique\npermissions." + "desc": "The specified file could not be opened.", + "first_action": "Use a valid file name and try to open the file or check", + "full_action": "Use a valid file name and try to open the file or check\npermissions." }, "5929": { "code": 5929, - "desc": "O certificate está não in o Active state, so it não é possível be renewed.", - "first_action": "Send o certificate re-issue request after performing", - "full_action": "Send o certificate re-issue request after performing\ncorrective actions. If you desejar to use o same credential (key pair), then o new\ncertificate can be generated usando o re-issue token. You can use o seguinte\ncomando:\nnbcertcmd -getCertificate\nIfyouplantochangecredentials,seetheNetBackupSecurityandEncryptionGuide\npara workflow details." + "desc": "The certificate is not in the Active state, so it cannot be renewed.", + "first_action": "Send the certificate re-issue request after performing", + "full_action": "Send the certificate re-issue request after performing\ncorrective actions. If you want to use the same credential (key pair), then the new\ncertificate can be generated using the re-issue token. You can use the following\ncommand:\nnbcertcmd -getCertificate\nIfyouplantochangecredentials,seetheNetBackupSecurityandEncryptionGuide\nfor workflow details." }, "5930": { "code": 5930, - "desc": "O request could não be authorized.", - "first_action": "Logintype WEB comando to get um web authentication token.", - "full_action": "Useare-issuetokenwiththenbcertcmd -getCertificate\ncomando. If o usuário has não been authenticated, use o bpnbat -login\n-logintype WEB comando to get um web authentication token." + "desc": "The request could not be authorized.", + "first_action": "Logintype WEB command to get a web authentication token.", + "full_action": "Useare-issuetokenwiththenbcertcmd -getCertificate\ncommand. If the user has not been authenticated, use the bpnbat -login\n-logintype WEB command to get a web authentication token." }, "5931": { "code": 5931, - "desc": "O host ID está vazio.", - "first_action": "Resend o request. If o problema continues, save todos de", - "full_action": "Resend o request. If o problema continues, save todos de\no erro log informação e contate Cohesity Technical Support." + "desc": "The host ID is empty.", + "first_action": "Resend the request. If the problem continues, save all of", + "full_action": "Resend the request. If the problem continues, save all of\nthe error log information and contact Cohesity Technical Support." }, "5932": { "code": 5932, - "desc": "Token uso count está não set.", - "first_action": "Generate um token com valid parameters. O allowable", - "full_action": "Generate um token com valid parameters. O allowable\ncount está from 1 to 99, 999." + "desc": "Token usage count is not set.", + "first_action": "Generate a token with valid parameters. The allowable", + "full_action": "Generate a token with valid parameters. The allowable\ncount is from 1 to 99, 999." }, "5933": { "code": 5933, - "desc": "O maximum token uso limite has been reached.", - "first_action": "Create um new token.", - "full_action": "Create um new token." + "desc": "The maximum token usage limit has been reached.", + "first_action": "Create a new token.", + "full_action": "Create a new token." }, "5934": { "code": 5934, - "desc": "O token has expired.", - "first_action": "Create um new token.", - "full_action": "Create um new token." + "desc": "The token has expired.", + "first_action": "Create a new token.", + "full_action": "Create a new token." }, "5936": { "code": 5936, - "desc": "O specified token name está não in um valid format.", - "first_action": "Specify um valid token name. O valid characters estão A-Z,", - "full_action": "Specify um valid token name. O valid characters estão A-Z,\na-z, 0-9, e _." + "desc": "The specified token name is not in a valid format.", + "first_action": "Specify a valid token name. The valid characters are A-Z,", + "full_action": "Specify a valid token name. The valid characters are A-Z,\na-z, 0-9, and _." }, "5938": { "code": 5938, - "desc": "O revocation reason code está não valid.", - "first_action": "Specify um valid reason code e then try to revoke o", - "full_action": "Specify um valid reason code e then try to revoke o\ncertificate." + "desc": "The revocation reason code is not valid.", + "first_action": "Specify a valid reason code and then try to revoke the", + "full_action": "Specify a valid reason code and then try to revoke the\ncertificate." }, "5939": { "code": 5939, - "desc": "This revocation reason code está não supported por o servidor.", - "first_action": "Specify um valid reason code e then try to revoke o", - "full_action": "Specify um valid reason code e then try to revoke o\ncertificate." + "desc": "This revocation reason code is not supported by the server.", + "first_action": "Specify a valid reason code and then try to revoke the", + "full_action": "Specify a valid reason code and then try to revoke the\ncertificate." }, "5940": { "code": 5940, - "desc": "Reissue token está mandatory; por favor provide um reissue token.", - "first_action": "Generate um reissue token para o requerido host e then", - "full_action": "Generate um reissue token para o requerido host e then\nrequest um certificate reissue. Use o seguinte comando (ou o NetBackup\nAdministration Console) to generate o reissue token:\nnbcertcmd -createToken -name name_of_token -reissue\n[-host host_name | -hostId host_id]" + "desc": "Reissue token is mandatory; please provide a reissue token.", + "first_action": "Generate a reissue token for the required host and then", + "full_action": "Generate a reissue token for the required host and then\nrequest a certificate reissue. Use the following command (or the NetBackup\nAdministration Console) to generate the reissue token:\nnbcertcmd -createToken -name name_of_token -reissue\n[-host host_name | -hostId host_id]" }, "5941": { "code": 5941, - "desc": "O host ID está não associated com qualquer host.", + "desc": "The host ID is not associated with any host.", "first_action": "VerifythatthespecifiedhostIDcorrespondstothespecified", - "full_action": "VerifythatthespecifiedhostIDcorrespondstothespecified\nmaster servidor. Use o nbcertcmd -listCertDetails comando on o specified\nNetBackup host to find o host ID que corresponds to o specified master servidor." + "full_action": "VerifythatthespecifiedhostIDcorrespondstothespecified\nmaster server. Use the nbcertcmd -listCertDetails command on the specified\nNetBackup host to find the host ID that corresponds to the specified master server." }, "5942": { "code": 5942, - "desc": "Certificate could não be ler from o local certificate store.", - "first_action": "O external certificate que está specified in bp.conf/registry against", - "full_action": "Checkifyouhaveadministratorprivilegesonthespecified\nNetBackup host. If you have o requerido privileges, use o -force option com o\nnbcertcmd -getCertificate comando to regenerate o existing certificate. You\nmay have to supply um token com this comando, depending on o certificate\ndeployment security levels specified on o master servidor.\nIf external CA signed certificate está used para communication, it may be lost ou\ncorrupted. Try o seguinte:\n■ O external certificate que está specified in bp.conf/registry against\nECA_CERT_PATH key may be lost ou corrupted. Make sure que o provided\ncertificate caminho está in o correct format. Review o value que está set para o\nECA_CERT_PATH configuration option, verifique if it has o requerido access\npermissions, e it está accessible." + "desc": "Certificate could not be read from the local certificate store.", + "first_action": "The external certificate that is specified in bp.conf/registry against", + "full_action": "Checkifyouhaveadministratorprivilegesonthespecified\nNetBackup host. If you have the required privileges, use the -force option with the\nnbcertcmd -getCertificate command to regenerate the existing certificate. You\nmay have to supply a token with this command, depending on the certificate\ndeployment security levels specified on the master server.\nIf external CA signed certificate is used for communication, it may be lost or\ncorrupted. Try the following:\n■ The external certificate that is specified in bp.conf/registry against\nECA_CERT_PATH key may be lost or corrupted. Make sure that the provided\ncertificate path is in the correct format. Review the value that is set for the\nECA_CERT_PATH configuration option, check if it has the required access\npermissions, and it is accessible." }, "5943": { "code": 5943, - "desc": "Lock não é possível be acquired on o arquivo para writing.", - "first_action": "Rerun o operation. If o problema continues, save todos de", - "full_action": "Rerun o operation. If o problema continues, save todos de\no erro log informação e contate Cohesity Technical Support." + "desc": "Lock cannot be acquired on the file for writing.", + "first_action": "Rerun the operation. If the problem continues, save all of", + "full_action": "Rerun the operation. If the problem continues, save all of\nthe error log information and contact Cohesity Technical Support." }, "5944": { "code": 5944, - "desc": "O host alias list has multiple host names. NetBackup status codes 750 NetBackup status codes", + "desc": "The host alias list has multiple host names. NetBackup status codes 750 NetBackup status codes", "first_action": "Specifyasinglehostnameinthecertificatesigningrequest", - "full_action": "Specifyasinglehostnameinthecertificatesigningrequest\ne resend o request to o master servidor." + "full_action": "Specifyasinglehostnameinthecertificatesigningrequest\nand resend the request to the master server." }, "5945": { "code": 5945, - "desc": "Host alias está não specified.", - "first_action": "Specify um host name in o certificate signing request e", - "full_action": "Specify um host name in o certificate signing request e\nresend o request to o master servidor." + "desc": "Host alias is not specified.", + "first_action": "Specify a host name in the certificate signing request and", + "full_action": "Specify a host name in the certificate signing request and\nresend the request to the master server." }, "5946": { "code": 5946, - "desc": "Token está mandatory; por favor provide um token.", - "first_action": "Generate um authorization token e then run o", - "full_action": "Generate um authorization token e then run o\nnbcertcmd -getCertificate comando to request um certificate." + "desc": "Token is mandatory; please provide a token.", + "first_action": "Generate an authorization token and then run the", + "full_action": "Generate an authorization token and then run the\nnbcertcmd -getCertificate command to request a certificate." }, "5947": { "code": 5947, - "desc": "O host está não registered com o servidor.", - "first_action": "Specifythecorrecthostnameor use um validauthorization", - "full_action": "Specifythecorrecthostnameor use um validauthorization\ntoken e rerun o operation." + "desc": "The host is not registered with the server.", + "first_action": "Specifythecorrecthostnameor use a validauthorization", + "full_action": "Specifythecorrecthostnameor use a validauthorization\ntoken and rerun the operation." }, "5948": { "code": 5948, - "desc": "Certificate could não be written to o local certificate store. NetBackup status codes 751 NetBackup status codes", - "first_action": "Verifique if you have administrator privileges on o given", - "full_action": "Verifique if you have administrator privileges on o given\nNetBackup host. If you have o requerido privileges, redo o ação. If o problema\ncontinues, save todos de o erro log informação e contate Cohesity Technical\nSupport." + "desc": "Certificate could not be written to the local certificate store. NetBackup status codes 751 NetBackup status codes", + "first_action": "Check if you have administrator privileges on the given", + "full_action": "Check if you have administrator privileges on the given\nNetBackup host. If you have the required privileges, redo the action. If the problem\ncontinues, save all of the error log information and contact Cohesity Technical\nSupport." }, "5949": { "code": 5949, - "desc": "Certificate does não exist.", - "first_action": "Garanta que o appropriate certificate está deployed. Veja", - "full_action": "Garanta que o appropriate certificate está deployed. Veja\no NetBackup Security e Encryption Guide para details on how to deploy\ncertificates." + "desc": "Certificate does not exist.", + "first_action": "Ensure that the appropriate certificate is deployed. See", + "full_action": "Ensure that the appropriate certificate is deployed. See\nthe NetBackup Security and Encryption Guide for details on how to deploy\ncertificates." }, "5950": { "code": 5950, "desc": "Certificate already exists.", "first_action": "Usethenbcertcmd -getCertificate -forcecommand", - "full_action": "Usethenbcertcmd -getCertificate -forcecommand\nto overwrite o existing certificate, if requerido." + "full_action": "Usethenbcertcmd -getCertificate -forcecommand\nto overwrite the existing certificate, if required." }, "5953": { "code": 5953, - "desc": "O certificate deployment level está não valid.", - "first_action": "Select um certificate deployment level between 0 - 2 e", - "full_action": "Select um certificate deployment level between 0 - 2 e\nrerun o comando to set o certificate deployment level. Para more informação\noncertificatedeploymentlevels,seetheNetBackupSecurityandEncryptionGuide." + "desc": "The certificate deployment level is not valid.", + "first_action": "Select a certificate deployment level between 0 - 2 and", + "full_action": "Select a certificate deployment level between 0 - 2 and\nrerun the command to set the certificate deployment level. For more information\noncertificatedeploymentlevels,seetheNetBackupSecurityandEncryptionGuide." }, "5954": { "code": 5954, "desc": "Thehostnamecouldnotberesolvedtotherequestinghost'sIPaddress.", - "first_action": "Verifique e correct seu rede configurations so que o", - "full_action": "Verifique e correct seu rede configurations so que o\nmaster servidor can resolve o host name to o peer IP address. Alternatively, you\ncan use um authorization token to deploy o certificate." + "first_action": "Verify and correct your network configurations so that the", + "full_action": "Verify and correct your network configurations so that the\nmaster server can resolve the host name to the peer IP address. Alternatively, you\ncan use an authorization token to deploy the certificate." }, "5955": { "code": 5955, - "desc": "O host name está não known to o primary servidor.", - "first_action": "Garanta que o host entry exists on one de o seguinte", - "full_action": "Garanta que o host entry exists on one de o seguinte\nlocations: o servidor configuration list, o EMM banco de dados, at least 1 catalog image\n(não more than 6 months old), o clients listed in policies, ou o cliente DB entry.\nAlternatively, you can use um authorization token to deploy o certificate." + "desc": "The host name is not known to the primary server.", + "first_action": "Ensure that the host entry exists on one of the following", + "full_action": "Ensure that the host entry exists on one of the following\nlocations: the server configuration list, the EMM database, at least 1 catalog image\n(not more than 6 months old), the clients listed in policies, or the client DB entry.\nAlternatively, you can use an authorization token to deploy the certificate." }, "5956": { "code": 5956, - "desc": "O existing certificate deployment level on o primary servidor does não allow this operation.", + "desc": "The existing certificate deployment level on the primary server does not allow this operation.", "first_action": "GetCertificate option.", - "full_action": "If you veja this erro message while you estão retrieving o\nhost ID-based certificate, garanta que you use um valid authorization token com o\n-getCertificate option." + "full_action": "If you see this error message while you are retrieving the\nhost ID-based certificate, ensure that you use a valid authorization token with the\n-getCertificate option." }, "5957": { "code": 5957, - "desc": "O primary servidor está não foi possível to conectar to o CA.", - "first_action": "Verifique o status de o NetBackup AT broker on o", - "full_action": "Verifique o status de o NetBackup AT broker on o\nprimary servidor. Restart o service, if requerido." + "desc": "The primary server is unable to connect to the CA.", + "first_action": "Check the status of the NetBackup AT broker on the", + "full_action": "Check the status of the NetBackup AT broker on the\nprimary server. Restart the service, if required." }, "5958": { "code": 5958, - "desc": "O primary servidor está não foi possível to access o CA certificate.", - "first_action": "Garanta que o web service usuário has o requerido", - "full_action": "Garanta que o web service usuário has o requerido\npermissions to ler o CA certificate on o primary servidor." + "desc": "The primary server is unable to access the CA certificate.", + "first_action": "Ensure that the web service user has the required", + "full_action": "Ensure that the web service user has the required\npermissions to read the CA certificate on the primary server." }, "5959": { "code": 5959, - "desc": "O NetBackup AT credentials de o web service usuário estão não valid.", - "first_action": "Stop o web service on o master servidor, run o", - "full_action": "Stop o web service on o master servidor, run o\nnbcertconfig -u -usuário webservice_usercommand,andrestartthewebservice." + "desc": "The NetBackup AT credentials of the web service user are not valid.", + "first_action": "Stop the web service on the master server, run the", + "full_action": "Stop the web service on the master server, run the\nnbcertconfig -u -user webservice_usercommand,andrestartthewebservice." }, "5960": { "code": 5960, "desc": "NetBackupATconfigurationontheprimaryservercouldnotbeinitialized.", - "first_action": "Garanta que o web service usuário has o requerido", - "full_action": "Garanta que o web service usuário has o requerido\npermissions to access o certificate store on o primary servidor." + "first_action": "Ensure that the web service user has the required", + "full_action": "Ensure that the web service user has the required\npermissions to access the certificate store on the primary server." }, "5962": { "code": 5962, - "desc": "O host name does não match o existing name in o certificate.", - "first_action": "1. O NetBackup host administrator should ask o NetBackup administrator to", - "full_action": "If o NetBackup host administrator wants to get o\ncertificate para o given host com o new name, then executar o seguinte steps:\n1. O NetBackup host administrator should ask o NetBackup administrator to\nrevoke o certificate de o host por usando o -host host_name | -hostId\nhost_idoptions.TheNetBackupadministratorcanusethefollowingcommand:\nnbcertcmd -revokeCertificate -reasonCode value\n-host old_host_name | -hostId host_id\n2. O NetBackup host administrator should ask o NetBackup administrator to\ngenerate um reissue token para um specific host. O NetBackup administrator can\nuse o seguinte comando:\nnbcertcmd -createToken -name token_name -reissue\n-host old_host_name | -hostId host_id\n3. AftertheNetBackuphostadministratorreceivesthereissuetoken,thefollowing\ncomando can be used (specify o received token when prompted):\nnbcertcmd -getCertificate -token -force" + "desc": "The host name does not match the existing name in the certificate.", + "first_action": "1. The NetBackup host administrator should ask the NetBackup administrator to", + "full_action": "If the NetBackup host administrator wants to get the\ncertificate for the given host with the new name, then perform the following steps:\n1. The NetBackup host administrator should ask the NetBackup administrator to\nrevoke the certificate of the host by using the -host host_name | -hostId\nhost_idoptions.TheNetBackupadministratorcanusethefollowingcommand:\nnbcertcmd -revokeCertificate -reasonCode value\n-host old_host_name | -hostId host_id\n2. The NetBackup host administrator should ask the NetBackup administrator to\ngenerate a reissue token for a specific host. The NetBackup administrator can\nuse the following command:\nnbcertcmd -createToken -name token_name -reissue\n-host old_host_name | -hostId host_id\n3. AftertheNetBackuphostadministratorreceivesthereissuetoken,thefollowing\ncommand can be used (specify the received token when prompted):\nnbcertcmd -getCertificate -token -force" }, "5963": { "code": 5963, - "desc": "Entity does não exist.", + "desc": "Entity does not exist.", "first_action": "Checkthattheargumentvaluessuppliedinthecommand", - "full_action": "Checkthattheargumentvaluessuppliedinthecommand\nestão correct." + "full_action": "Checkthattheargumentvaluessuppliedinthecommand\nare correct." }, "5964": { "code": 5964, - "desc": "Data conversion erro.", - "first_action": "Rerun o operation. If o problema persists, save todos de", - "full_action": "Rerun o operation. If o problema persists, save todos de\no erro log informação e contate Cohesity Technical Support." + "desc": "Data conversion error.", + "first_action": "Rerun the operation. If the problem persists, save all of", + "full_action": "Rerun the operation. If the problem persists, save all of\nthe error log information and contact Cohesity Technical Support." }, "5965": { "code": 5965, - "desc": "O host ID associated com this reissue token está assigned to another host. Before you can reuse o host ID para this host, revoke o existing certificate associated com o host ID e map this host name to o host ID.", - "first_action": "O usuário must revoke o current certificate com o", - "full_action": "O usuário must revoke o current certificate com o\nexisting host name e then use o reissue token to request um certificate usando\no new host name." + "desc": "The host ID associated with this reissue token is assigned to another host. Before you can reuse the host ID for this host, revoke the existing certificate associated with the host ID and map this host name to the host ID.", + "first_action": "The user must revoke the current certificate with the", + "full_action": "The user must revoke the current certificate with the\nexisting host name and then use the reissue token to request a certificate using\nthe new host name." }, "5966": { "code": 5966, - "desc": "O host has um active certificate. You need to revoke o certificate before you can disassociate o host from its host ID.", - "first_action": "O usuário must revoke o certificate para this host e apenas", - "full_action": "O usuário must revoke o certificate para this host e apenas\nthen mark it como decoupled from o associated host ID." + "desc": "The host has an active certificate. You need to revoke the certificate before you can disassociate the host from its host ID.", + "first_action": "The user must revoke the certificate for this host and only", + "full_action": "The user must revoke the certificate for this host and only\nthen mark it as decoupled from the associated host ID." }, "5967": { "code": 5967, - "desc": "O arquivo already exists. NetBackup status codes 756 NetBackup status codes", - "first_action": "O usuário can rename/move/delete o existing arquivo ou", - "full_action": "O usuário can rename/move/delete o existing arquivo ou\nsubmit um new arquivo name." + "desc": "The file already exists. NetBackup status codes 756 NetBackup status codes", + "first_action": "The user can rename/move/delete the existing file or", + "full_action": "The user can rename/move/delete the existing file or\nsubmit a new file name." }, "5968": { "code": 5968, - "desc": "O host informação could não be retrieved while creating o certificate signing request.", - "first_action": "Retry o current operation.", - "full_action": "Try o seguinte possible solutions:\n■ Retry o current operation.\n■ Retry o current operation por restarting o system.\n■ If o problema persists, contate Cohesity Technical Support." + "desc": "The host information could not be retrieved while creating the certificate signing request.", + "first_action": "Retry the current operation.", + "full_action": "Try the following possible solutions:\n■ Retry the current operation.\n■ Retry the current operation by restarting the system.\n■ If the problem persists, contact Cohesity Technical Support." }, "5969": { "code": 5969, - "desc": "ResponsefromtheNetBackupWebManagementConsoleservicecould não be parsed.", - "first_action": "Rerun o operation. If o problema persists, save todos de", - "full_action": "Rerun o operation. If o problema persists, save todos de\no erro log informação e contate Cohesity Technical Support." + "desc": "ResponsefromtheNetBackupWebManagementConsoleservicecould not be parsed.", + "first_action": "Rerun the operation. If the problem persists, save all of", + "full_action": "Rerun the operation. If the problem persists, save all of\nthe error log information and contact Cohesity Technical Support." }, "5970": { "code": 5970, - "desc": "O servidor time could não be fetched.", - "first_action": "Rerun o operation. If o problema continues, save todos de", - "full_action": "Rerun o operation. If o problema continues, save todos de\no erro log informação e contate Cohesity Technical Support." + "desc": "The server time could not be fetched.", + "first_action": "Rerun the operation. If the problem continues, save all of", + "full_action": "Rerun the operation. If the problem continues, save all of\nthe error log information and contact Cohesity Technical Support." }, "5971": { "code": 5971, - "desc": "O token contains characters que estão não supported.", + "desc": "The token contains characters that are not supported.", "first_action": "Checkthetokenvaluepassedinthetokenfileandensure", - "full_action": "Checkthetokenvaluepassedinthetokenfileandensure\nque it contains valid characters (A-Z, a-z, e 0-9). Garanta que o arquivo encoding\nformat está ANSI." + "full_action": "Checkthetokenvaluepassedinthetokenfileandensure\nthat it contains valid characters (A-Z, a-z, and 0-9). Ensure that the file encoding\nformat is ANSI." }, "5972": { "code": 5972, - "desc": "O certificate could não be revoked. It foi already revoked ou expired.", - "first_action": "Specify o active certificate e then try to revoke o", - "full_action": "Specify o active certificate e then try to revoke o\ncertificate." + "desc": "The certificate could not be revoked. It was already revoked or expired.", + "first_action": "Specify the active certificate and then try to revoke the", + "full_action": "Specify the active certificate and then try to revoke the\ncertificate." }, "5973": { "code": 5973, - "desc": "O token type está não valid.", + "desc": "The token type is not valid.", "first_action": "0 - Default token", - "full_action": "Specify one de o seguinte token types:\n■ 0 - Default token\n■ 1 - Reissue token\nIf you have não provided o token type, o default token type (0) está automatically\nselected." + "full_action": "Specify one of the following token types:\n■ 0 - Default token\n■ 1 - Reissue token\nIf you have not provided the token type, the default token type (0) is automatically\nselected." }, "5974": { "code": 5974, - "desc": "O specified token requires um host ID.", - "first_action": "Provide um host ID de o host para which you desejar to create", - "full_action": "Provide um host ID de o host para which you desejar to create\num token." + "desc": "The specified token requires a host ID.", + "first_action": "Provide a host ID of the host for which you want to create", + "full_action": "Provide a host ID of the host for which you want to create\na token." }, "5976": { "code": 5976, - "desc": "O passphrase must contain um minimum de 8 e um maximum de 20 characters.", + "desc": "The passphrase must contain a minimum of 8 and a maximum of 20 characters.", "first_action": "Specifyapassphrasewithaminimumof8andamaximum", - "full_action": "Specifyapassphrasewithaminimumof8andamaximum\nde 20 characters." + "full_action": "Specifyapassphrasewithaminimumof8andamaximum\nof 20 characters." }, "5977": { "code": 5977, - "desc": "O existing passphrase e o new passphrase must be different.", - "first_action": "Specify um passphrase que está different than o existing", - "full_action": "Specify um passphrase que está different than o existing\none." + "desc": "The existing passphrase and the new passphrase must be different.", + "first_action": "Specify a passphrase that is different than the existing", + "full_action": "Specify a passphrase that is different than the existing\none." }, "5978": { "code": 5978, - "desc": "Falhou to refresh o certificate revocation list (CRL) e security level.", - "first_action": "Falhou to save o CRL on o disco", - "full_action": "Falhou to fetch o CRL via o HTTP request\n■ Falhou to save o CRL on o disco\n■ Falhou to fetch o security level via o HTTP request\n■ Failedtoupdatethecertmapinfo.jsonwithCRLandsecuritylevelinformation\n■ Falhou to get o CRL because um cliente in o DMZ could não conectar to o\nHTTP tunnel on o mídia servidor\nRecomendada Ação: Do o seguinte, como appropriate:\n■ On o master servidor, examine o unified logs on o NetBackup servidor para\nnbwebservice (OID 466 e 484).\n■ On o mídia servidor, examine o pbx (OID 103), nbpxytnl (OID 490), e\nnbpxyhelper (OID 486) logs. pbx está logged to o seguinte directories:\nWindows: install_path\\VxPBX\\log\nUNIX: /opt/VRTSpbx/log\n■ Garanta que o seguinte estão online:\n■ NetBackup Master servidor\n■ NetBackup Web Management Console service (nbwmc)\n■ NetBackup relational banco de dados (NBDB)\n■ On o host onde o erro ocorreu, examine o legacy logs para nbcertcmd." + "desc": "Failed to refresh the certificate revocation list (CRL) and security level.", + "first_action": "Failed to save the CRL on the disk", + "full_action": "Failed to fetch the CRL via the HTTP request\n■ Failed to save the CRL on the disk\n■ Failed to fetch the security level via the HTTP request\n■ Failedtoupdatethecertmapinfo.jsonwithCRLandsecuritylevelinformation\n■ Failed to get the CRL because a client in the DMZ could not connect to the\nHTTP tunnel on the media server\nRecommended Action: Do the following, as appropriate:\n■ On the master server, examine the unified logs on the NetBackup server for\nnbwebservice (OID 466 and 484).\n■ On the media server, examine the pbx (OID 103), nbpxytnl (OID 490), and\nnbpxyhelper (OID 486) logs. pbx is logged to the following directories:\nWindows: install_path\\VxPBX\\log\nUNIX: /opt/VRTSpbx/log\n■ Ensure that the following are online:\n■ NetBackup Master server\n■ NetBackup Web Management Console service (nbwmc)\n■ NetBackup relational database (NBDB)\n■ On the host where the error occurred, examine the legacy logs for nbcertcmd." }, "5979": { "code": 5979, - "desc": "O certificate revocation list (CRL) in o certificate está inválido.", - "first_action": "On o host onde o erro ocorreu, examine o legacy logs para nbcertcmd.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ On o host onde o erro ocorreu, examine o legacy logs para nbcertcmd.\nUse these logs to help troubleshoot issues que appear in o web services.\n■ On o master servidor, examine o unified logs para nbwebservice (OIDs 466\ne 484).\n■ Restart o services on o master servidor. Then, retry o seguinte comando\npara o host to fetch o CRL:\n./nbcertcmd -getCrl" + "desc": "The certificate revocation list (CRL) in the certificate is invalid.", + "first_action": "On the host where the error occurred, examine the legacy logs for nbcertcmd.", + "full_action": "Do the following, as appropriate:\n■ On the host where the error occurred, examine the legacy logs for nbcertcmd.\nUse these logs to help troubleshoot issues that appear in the web services.\n■ On the master server, examine the unified logs for nbwebservice (OIDs 466\nand 484).\n■ Restart the services on the master server. Then, retry the following command\nfor the host to fetch the CRL:\n./nbcertcmd -getCrl" }, "5980": { "code": 5980, - "desc": "O security level in o certificate está inválido.", - "first_action": "On o master servidor, examine o unified logs on o NetBackup servidor para", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ On o master servidor, examine o unified logs on o NetBackup servidor para\nnbwebservice (OID 466 e 484).\n■ On o host onde o erro ocorreu, examine o legacy logs para nbcertcmd.\n■ Run o seguinte comando para o host to fetch o CRL e o security level:\n./nbcertcmd -getCrl" + "desc": "The security level in the certificate is invalid.", + "first_action": "On the master server, examine the unified logs on the NetBackup server for", + "full_action": "Do the following, as appropriate:\n■ On the master server, examine the unified logs on the NetBackup server for\nnbwebservice (OID 466 and 484).\n■ On the host where the error occurred, examine the legacy logs for nbcertcmd.\n■ Run the following command for the host to fetch the CRL and the security level:\n./nbcertcmd -getCrl" }, "5982": { "code": 5982, - "desc": "O certificate revocation list (CRL) está unavailable.", - "first_action": "Retry o comando ou operation.", - "full_action": "Execute os seguintes passos conforme apropriado:\nPara Scenario 1, do o seguinte:\n■ Retry o comando ou operation.\n■ Verifique que nbatd está executando on o master servidor, then retry o operation.\n■ Restart o services on o master servidor, then retry o operation.\n■ On o master servidor, examine o unified logs on o NetBackup servidor para\nnbwebservice (todos OIDs).\n■ On o master servidor e on o host onde o erro ocorreu, examine o\nunified logs para nbatd (OID 18).\nPara Scenario 2, do o seguinte:\n■ Run o seguinte comando para o master servidor e then retry o operation:\n./nbcertcmd -getCrl -servidor master servidor name\n■ On todos hosts que estão involved in o communication, examine o unified logs\npara nbpxyhelper (OID 486).\n■ On o host onde o erro ocorreu, examine o legacy logs para nbcertcmd.\n■ (Scenario 3) NetBackup está não configurado com correct CRL caminho ou certificate\ndoes não contain um valid CDP.\n■ If o ECA_CRL_PATH setting está specified in o NetBackup configuration arquivo,\ngaranta o seguinte:\n■ O ECA_CRL_PATH has o correct CRL diretório caminho.\n■ O CRL diretório contains CRLs para todos requerido certificate issuers (como\nper ECA_CRL_CHECK setting).\n■ O CRL está in PEM ou DER format.\n■ O CRL está não expired.\n■ O CRL last update date está não um future date.\n■ If o CDP está used, do o seguinte when appropriate:\n■ Make sure que o certificate has at least one CDP (com HTTP/HTTPS\nprotocol) que points to um CRL que includes revocation informação para todos\nreasons.\n■ CDP URL está accessible.\n■ (Scenario 4) O host does não have um CRL cached in NetBackup CRL cache.\n■ If ECA_CRL_PATH setting está specified in o NetBackup configuration arquivo, run\no seguinte comando on todos hosts que estão involved in o communication\ne retry o operation:\n./nbcertcmd -updateCRLCache\n■ If bpclntcmd está executando, terminate it (bpclntcmd -terminate) e retry o\noperation.\n■ Set VERBOSE e ENABLE_NBCURL_VERBOSE (0|1).\n■ Examine o logs para bpclntcmd.\n■ On todos hosts que estão involved in o communication, examine o unified\nlogs para nbpxyhelper (OID 486).\n■ Onthehostwheretheerroroccurred,examinethelegacylogsfornbcertcmd." + "desc": "The certificate revocation list (CRL) is unavailable.", + "first_action": "Retry the command or operation.", + "full_action": "Do the following, as appropriate:\nFor Scenario 1, do the following:\n■ Retry the command or operation.\n■ Verify that nbatd is running on the master server, then retry the operation.\n■ Restart the services on the master server, then retry the operation.\n■ On the master server, examine the unified logs on the NetBackup server for\nnbwebservice (all OIDs).\n■ On the master server and on the host where the error occurred, examine the\nunified logs for nbatd (OID 18).\nFor Scenario 2, do the following:\n■ Run the following command for the master server and then retry the operation:\n./nbcertcmd -getCrl -server master server name\n■ On all hosts that are involved in the communication, examine the unified logs\nfor nbpxyhelper (OID 486).\n■ On the host where the error occurred, examine the legacy logs for nbcertcmd.\n■ (Scenario 3) NetBackup is not configured with correct CRL path or certificate\ndoes not contain a valid CDP.\n■ If the ECA_CRL_PATH setting is specified in the NetBackup configuration file,\nensure the following:\n■ The ECA_CRL_PATH has the correct CRL directory path.\n■ The CRL directory contains CRLs for all required certificate issuers (as\nper ECA_CRL_CHECK setting).\n■ The CRL is in PEM or DER format.\n■ The CRL is not expired.\n■ The CRL last update date is not a future date.\n■ If the CDP is used, do the following when appropriate:\n■ Make sure that the certificate has at least one CDP (with HTTP/HTTPS\nprotocol) that points to a CRL that includes revocation information for all\nreasons.\n■ CDP URL is accessible.\n■ (Scenario 4) The host does not have a CRL cached in NetBackup CRL cache.\n■ If ECA_CRL_PATH setting is specified in the NetBackup configuration file, run\nthe following command on all hosts that are involved in the communication\nand retry the operation:\n./nbcertcmd -updateCRLCache\n■ If bpclntcmd is running, terminate it (bpclntcmd -terminate) and retry the\noperation.\n■ Set VERBOSE and ENABLE_NBCURL_VERBOSE (0|1).\n■ Examine the logs for bpclntcmd.\n■ On all hosts that are involved in the communication, examine the unified\nlogs for nbpxyhelper (OID 486).\n■ Onthehostwheretheerroroccurred,examinethelegacylogsfornbcertcmd." }, "5983": { "code": 5983, - "desc": "O host certificate está revoked.", + "desc": "The host certificate is revoked.", "first_action": "Onthehostwheretheerroroccurred,examinethelegacylogsontheNetBackup", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Onthehostwheretheerroroccurred,examinethelegacylogsontheNetBackup\nservidor para nbcertcmd.\n■ On todos de o hosts involved in o communication, examine o unified logs para\nnbpxyhelper (OID 486).\n■ If o certificate foi revoked in erro, reissue um certificate para o host.\n■ If o certificate foi revoked como intended, um attempted security breach may\nhave ocorreu.\n■ Contate seu Security Administrator.\n■ To reissue um certificate para o host, veja o NetBackup Security e Encryption\nGuide." + "full_action": "Do the following, as appropriate:\n■ Onthehostwheretheerroroccurred,examinethelegacylogsontheNetBackup\nserver for nbcertcmd.\n■ On all of the hosts involved in the communication, examine the unified logs for\nnbpxyhelper (OID 486).\n■ If the certificate was revoked in error, reissue a certificate for the host.\n■ If the certificate was revoked as intended, an attempted security breach may\nhave occurred.\n■ Contact your Security Administrator.\n■ To reissue a certificate for the host, see the NetBackup Security and Encryption\nGuide." }, "5986": { "code": 5986, - "desc": "Certificaterequestforhostwasrejectedasthehostcouldnotbevalidated como um primary servidor.", - "first_action": "Garanta que you do não send o master server-specific", - "full_action": "Garanta que you do não send o master server-specific\nparameters when you deploy o certificate on um non-master servidor host." + "desc": "Certificaterequestforhostwasrejectedasthehostcouldnotbevalidated as a primary server.", + "first_action": "Ensure that you do not send the master server-specific", + "full_action": "Ensure that you do not send the master server-specific\nparameters when you deploy the certificate on a non-master server host." }, "5987": { "code": 5987, - "desc": "CouldnotfetchthehostIDoftheNetBackupprimaryserver.Theprimary servidor may não have o certificate.", - "first_action": "NBSL está executando on o master servidor", - "full_action": "Garanta que o seguinte occurs:\n■ NBSL está executando on o master servidor\n■ IfNBSLisrunningonthemasterserver,ensurethatthehostID-basedcertificate\nestá deployed on o master servidor\n■ If o host ID-based certificate está deployed e if you still veja this erro, refer to\no Resolvendo o master servidor host name change issue procedure..\nResolvendo o master servidor host name change issue\nThiserrormayoccurifthemasterserverhostnameischangedfromaFullyQualified\nDomain Name (FQDN) to um short name (ou vice versa) in qualquer de o seguinte\nscenarios:\n■ NetBackup installation after um disaster\n■ Manual update in o NetBackup configuration arquivo (bp.conf arquivo on o UNIX ou\nWindows registry).\nIn o seguinte example, NetBackup está instalado on um master servidor com um short\nname e o catalog backup está run. After um disaster, NetBackup está instalado on o\nmaster servidor in um disaster recovery mode, but this time com FQDN. However, o\nidentity de o master servidor (ou disaster recovery package) está restored com o\nshort name. This can cause falha when reissuing o cliente certificates,\nautomatically renewing o cliente certificates e deploying new certificates on\nclients.\nTo resolve this issue, use o seguinte steps:\n1. Log on to o master servidor.\n2. Run seguinte comando:\nUNIX:\n/usr/openv/netbackup/bin/nbcertcmd -ping\nWindows:\nInstall_path\\NetBackup\\bin\\nbcertcmd -ping\n■ If o comando está executed successfully, proceed to next step.\n■ If it fails com o exist status code 8509 (o specified servidor name foi\nnão found in o web service certificate), then carry fora o steps que estão\nprovided in o seguinte technote:\nhttps://www.veritas.com/support/en_US/article.100034092\nProceed to o next step.\n3. StopandstarttheNetBackupWebManagementConsoleserviceonthemaster\nservidor. Use seguinte o NetBackup comando:\nUNIX:\n/usr/openv/netbackup/bin/nbwmc -terminate\n/usr/openv/netbackup/bin/nbwmc -start\nWindows:\ninstall_path\\NetBackup\\wmc\\bin\\nbwmc.exe -stop -srvname \"NetBackup\nWeb Management Console\"\ninstall_path\\NetBackup\\wmc\\bin\\nbwmc.exe -start -srvname\n\"NetBackup Web Management Console\"\n4. Executar o usuário login on o master servidor. Use o seguinte comando:\ninstall_path/netbackup/bin/bpnbat -login -loginType WEB\nPara example:\ninstall_path\\netbackup\\bin\\bpnbat -login -loginType WEB\nAuthentication Broker [abc.example.com está default]:\nAuthentication port [0 está default]:\nAuthentication type (NIS, NISPLUS, WINDOWS, vx, unixpwd, ldap) [WINDOWS está default]:\nDomain [abc.example.com está default]:\nLogin Name [administrator está default]:\nPassword:\nOperation completed successfully.\n5. Note o value de o key Client_Name para o master servidor. Para um clustered\nmaster servidor, note o value de o key Cluster_Name This can be found at\no seguinte locations:\nUNIX:/usr/openv/netbackup/bp.conf\nWindows:HKEY_LOCAL_MACHINE\\SOFTWARE\\Veritas\\NetBackup\\CurrentVersion\\Config\nThis value can either be o FQDN ou o short name. Para example,\nabc.example.com.\n6. Note o host ID de o master servidor. You can obtain its value por usando o\nseguinte comando:\ninstall_path/netbackup/bin/nbcertcmd -listCertDetails\nPara um clustered master setup, use o seguinte comando:\ninstall_path\\netbackup\\bin\\nbcertcmd -listCertDetails -cluster\nThis comando may return multiple records (if apenas one record está returned,\nselect o host ID provided in que record).\n■ If o host name obtained in step 5 está FQDN, then pick o record onde\no “Issued Por” entry matches its short name.\n■ If o host name obtained in step 5 está um short name, then pick o record\nonde o “Issued Por” entry matches its FQDN.\nPara example:\ninstall_path\\netbackup\\bin\\nbcertcmd -listCertDetails\nMaster Servidor : abc\nHost ID : xxxxxx-4201-4c6a-xxxx-xxxxx\nIssued Por : /CN=broker/OU=root@abc/O=vx\nSerial Number : 0x62e108c90000000c\nExpiry Date : Aug 21 08:42:54 2018 GMT\nSHA1 Fingerprint : 50:89:AE:66:12:9A:29:4A:66:E9:DB:71:37:\nC7:EA:94:8C:C6:0C:A0\nMaster Servidor : xyz\nHost ID : yyyyyy-4785-4252-yyyy-yyyyy\nIssued Por : /CN=broker/OU=root@xyz.master1.com/O=vx\nSerial Number : 0x6ede87a70000000a\nExpiry Date : Aug 21 09:52:13 2018 GMT\nSHA1 Fingerprint : FE:08:C2:09:AC:5D:82:57:7A:96:5C:C1:4A:\nE6:EC:CA:CC:99:09:D2\nOperation completed successfully.\nHere, 2 records estão returned. Para o first record, o issuer name provided in\no “Issued Por” field matches o short name de o client_name obtained in\nstep 5. Select o host ID que appears in o first record.\n7. Add um host ID-to-host name mapping. Map o host ID de o master servidor\nque you have obtained in step 6 to o host name que you have obtained in\nstep 5.\nUse o seguinte comando:\ninstall_path/netbackup/bin/admincmd/nbhostmgmt -um -i host_ID -hm\nhost_name\nPara example:\ninstall_path/netbackup/bin/admincmd/nbhostmgmt -um -i\nxxxxxx-4201-4c6a-xxxx-xxxxx -hm abc.example.com\nabc.example.com está successfully mapped to xxxxxx-4201-4c6a-xxxx-xxxxx.\nYou can also add this host ID-to-host name mapping usando o NetBackup\nAdministrationConsole.UsetheSecurityManagement>HostManagement\n> Hosts tab.\n8. RenewthehostID-basedcertificateofthemasterserverbyusingthefollowing\ncomando:\ninstall_path/netbackup/bin/nbcertcmd -renewCertificate\nPara um clustered master servidor, use o seguinte comando:\ninstall_path\\netbackup\\bin\\nbcertcmd -renewCertificate -cluster\n9. Continuewiththecertificatedeploymentonaclient(thiscanbeeitherareissue\ncertificate, o automatic renewal de um certificate, ou um new certificate\ndeployment)." + "desc": "CouldnotfetchthehostIDoftheNetBackupprimaryserver.Theprimary server may not have the certificate.", + "first_action": "NBSL is running on the master server", + "full_action": "Ensure that the following occurs:\n■ NBSL is running on the master server\n■ IfNBSLisrunningonthemasterserver,ensurethatthehostID-basedcertificate\nis deployed on the master server\n■ If the host ID-based certificate is deployed and if you still see this error, refer to\nthe Resolving the master server host name change issue procedure..\nResolving the master server host name change issue\nThiserrormayoccurifthemasterserverhostnameischangedfromaFullyQualified\nDomain Name (FQDN) to a short name (or vice versa) in any of the following\nscenarios:\n■ NetBackup installation after a disaster\n■ Manual update in the NetBackup configuration file (bp.conf file on the UNIX or\nWindows registry).\nIn the following example, NetBackup is installed on a master server with a short\nname and the catalog backup is run. After a disaster, NetBackup is installed on the\nmaster server in a disaster recovery mode, but this time with FQDN. However, the\nidentity of the master server (or disaster recovery package) is restored with the\nshort name. This can cause failure when reissuing the client certificates,\nautomatically renewing the client certificates and deploying new certificates on\nclients.\nTo resolve this issue, use the following steps:\n1. Log on to the master server.\n2. Run following command:\nUNIX:\n/usr/openv/netbackup/bin/nbcertcmd -ping\nWindows:\nInstall_path\\NetBackup\\bin\\nbcertcmd -ping\n■ If the command is executed successfully, proceed to next step.\n■ If it fails with the exist status code 8509 (The specified server name was\nnot found in the web service certificate), then carry out the steps that are\nprovided in the following technote:\nhttps://www.veritas.com/support/en_US/article.100034092\nProceed to the next step.\n3. StopandstarttheNetBackupWebManagementConsoleserviceonthemaster\nserver. Use following the NetBackup command:\nUNIX:\n/usr/openv/netbackup/bin/nbwmc -terminate\n/usr/openv/netbackup/bin/nbwmc -start\nWindows:\ninstall_path\\NetBackup\\wmc\\bin\\nbwmc.exe -stop -srvname \"NetBackup\nWeb Management Console\"\ninstall_path\\NetBackup\\wmc\\bin\\nbwmc.exe -start -srvname\n\"NetBackup Web Management Console\"\n4. Perform the user login on the master server. Use the following command:\ninstall_path/netbackup/bin/bpnbat -login -loginType WEB\nFor example:\ninstall_path\\netbackup\\bin\\bpnbat -login -loginType WEB\nAuthentication Broker [abc.example.com is default]:\nAuthentication port [0 is default]:\nAuthentication type (NIS, NISPLUS, WINDOWS, vx, unixpwd, ldap) [WINDOWS is default]:\nDomain [abc.example.com is default]:\nLogin Name [administrator is default]:\nPassword:\nOperation completed successfully.\n5. Note the value of the key Client_Name for the master server. For a clustered\nmaster server, note the value of the key Cluster_Name This can be found at\nthe following locations:\nUNIX:/usr/openv/netbackup/bp.conf\nWindows:HKEY_LOCAL_MACHINE\\SOFTWARE\\Veritas\\NetBackup\\CurrentVersion\\Config\nThis value can either be the FQDN or the short name. For example,\nabc.example.com.\n6. Note the host ID of the master server. You can obtain its value by using the\nfollowing command:\ninstall_path/netbackup/bin/nbcertcmd -listCertDetails\nFor a clustered master setup, use the following command:\ninstall_path\\netbackup\\bin\\nbcertcmd -listCertDetails -cluster\nThis command may return multiple records (if only one record is returned,\nselect the host ID provided in that record).\n■ If the host name obtained in step 5 is FQDN, then pick the record where\nthe “Issued By” entry matches its short name.\n■ If the host name obtained in step 5 is a short name, then pick the record\nwhere the “Issued By” entry matches its FQDN.\nFor example:\ninstall_path\\netbackup\\bin\\nbcertcmd -listCertDetails\nMaster Server : abc\nHost ID : xxxxxx-4201-4c6a-xxxx-xxxxx\nIssued By : /CN=broker/OU=root@abc/O=vx\nSerial Number : 0x62e108c90000000c\nExpiry Date : Aug 21 08:42:54 2018 GMT\nSHA1 Fingerprint : 50:89:AE:66:12:9A:29:4A:66:E9:DB:71:37:\nC7:EA:94:8C:C6:0C:A0\nMaster Server : xyz\nHost ID : yyyyyy-4785-4252-yyyy-yyyyy\nIssued By : /CN=broker/OU=root@xyz.master1.com/O=vx\nSerial Number : 0x6ede87a70000000a\nExpiry Date : Aug 21 09:52:13 2018 GMT\nSHA1 Fingerprint : FE:08:C2:09:AC:5D:82:57:7A:96:5C:C1:4A:\nE6:EC:CA:CC:99:09:D2\nOperation completed successfully.\nHere, 2 records are returned. For the first record, the issuer name provided in\nthe “Issued By” field matches the short name of the client_name obtained in\nstep 5. Select the host ID that appears in the first record.\n7. Add a host ID-to-host name mapping. Map the host ID of the master server\nthat you have obtained in step 6 to the host name that you have obtained in\nstep 5.\nUse the following command:\ninstall_path/netbackup/bin/admincmd/nbhostmgmt -a -i host_ID -hm\nhost_name\nFor example:\ninstall_path/netbackup/bin/admincmd/nbhostmgmt -a -i\nxxxxxx-4201-4c6a-xxxx-xxxxx -hm abc.example.com\nabc.example.com is successfully mapped to xxxxxx-4201-4c6a-xxxx-xxxxx.\nYou can also add this host ID-to-host name mapping using the NetBackup\nAdministrationConsole.UsetheSecurityManagement>HostManagement\n> Hosts tab.\n8. RenewthehostID-basedcertificateofthemasterserverbyusingthefollowing\ncommand:\ninstall_path/netbackup/bin/nbcertcmd -renewCertificate\nFor a clustered master server, use the following command:\ninstall_path\\netbackup\\bin\\nbcertcmd -renewCertificate -cluster\n9. Continuewiththecertificatedeploymentonaclient(thiscanbeeitherareissue\ncertificate, the automatic renewal of a certificate, or a new certificate\ndeployment)." }, "5988": { "code": 5988, - "desc": "O host name está não part de o host ID-to-host name mapping list.", - "first_action": "Map o host name to o associated host ID. In o", - "full_action": "Map o host name to o associated host ID. In o\nNetBackup Administration Console, use o Security Management > Host\nManagement > Hosts tab ou o nbhostmgmt comando to add mappings." + "desc": "The host name is not part of the host ID-to-host name mapping list.", + "first_action": "Map the host name to the associated host ID. In the", + "full_action": "Map the host name to the associated host ID. In the\nNetBackup Administration Console, use the Security Management > Host\nManagement > Hosts tab or the nbhostmgmt command to add mappings." }, "5989": { "code": 5989, - "desc": "O reissue token está mandatory como um certificate foi already issued to this host. Revoke o existing certificate if it está active e map this host name to o associated host ID. NetBackup status codes 767 NetBackup status codes", - "first_action": "If o host has um active certificate, revoke it.", - "full_action": "To deploy um certificate usando this new name, you need to\nprovide um reissue token para o existing host ID. Para successful re-installation usando\no new host name, garanta o seguinte:\n■ If o host has um active certificate, revoke it.\n■ O host names estão mapped to o associated host ID. In o NetBackup\nAdministrationConsole,usetheSecurityManagement>HostManagement\n> Hosts tab ou o nbhostmgmt comando to add mappings.\n■ O cliente name para o host matches o primary host name associated com\no issued host ID.\nNote: If you desejar to deploy um certificate on um host com um host name que matches\num existing host ID-to-host name mapping de another host, you must either excluir\no existing host ID-to-host name mapping e retry o operation ou add um new\nhost in o host banco de dados.\nPara more informação on how to add um host, veja o NetBackup Security e\nEncryption Guide." + "desc": "The reissue token is mandatory as a certificate was already issued to this host. Revoke the existing certificate if it is active and map this host name to the associated host ID. NetBackup status codes 767 NetBackup status codes", + "first_action": "If the host has an active certificate, revoke it.", + "full_action": "To deploy a certificate using this new name, you need to\nprovide a reissue token for the existing host ID. For successful re-installation using\nthe new host name, ensure the following:\n■ If the host has an active certificate, revoke it.\n■ The host names are mapped to the associated host ID. In the NetBackup\nAdministrationConsole,usetheSecurityManagement>HostManagement\n> Hosts tab or the nbhostmgmt command to add mappings.\n■ The client name for the host matches the primary host name associated with\nthe issued host ID.\nNote: If you want to deploy a certificate on a host with a host name that matches\nan existing host ID-to-host name mapping of another host, you must either delete\nthe existing host ID-to-host name mapping and retry the operation or add a new\nhost in the host database.\nFor more information on how to add a host, see the NetBackup Security and\nEncryption Guide." }, "5990": { "code": 5990, - "desc": "O specified host ID-to-host name mapping está shared por multiple hosts e o auto reissue certificate parâmetro está set para two ou more hosts.", + "desc": "The specified host ID-to-host name mapping is shared by multiple hosts and the auto reissue certificate parameter is set for two or more hosts.", "first_action": "Inthecaseofsharedmapping,ensurethattheautoreissue", - "full_action": "Inthecaseofsharedmapping,ensurethattheautoreissue\ncertificate parâmetro está set apenas para o requerido host. You can reset o parâmetro\npara other hosts por executando o seguinte comando:\nnbhostmgmt -allowautoReissueCert -autoReissue 0\nAlternatively, you can use o NetBackup Administration Console." + "full_action": "Inthecaseofsharedmapping,ensurethattheautoreissue\ncertificate parameter is set only for the required host. You can reset the parameter\nfor other hosts by running the following command:\nnbhostmgmt -allowautoReissueCert -autoReissue 0\nAlternatively, you can use the NetBackup Administration Console." }, "5991": { "code": 5991, - "desc": "O specified host either does não exist ou o auto reissue certificate parâmetro está não set para o host.", - "first_action": "Garanta que o specified host exists e que o auto", - "full_action": "Garanta que o specified host exists e que o auto\nreissue certificate parâmetro está set para o host. If o host to be recovered does\nnotexist,initiatethePreparetoRestoreworkflowagainforthehost.To settheauto\nreissue certificate parâmetro para o host, run o seguinte comando:\nnbhostmgmt -allowautoReissueCert -autoReissue 1\nAlternatively, you can use o NetBackup Administration Console." + "desc": "The specified host either does not exist or the auto reissue certificate parameter is not set for the host.", + "first_action": "Ensure that the specified host exists and that the auto", + "full_action": "Ensure that the specified host exists and that the auto\nreissue certificate parameter is set for the host. If the host to be recovered does\nnotexist,initiatethePreparetoRestoreworkflowagainforthehost.To settheauto\nreissue certificate parameter for the host, run the following command:\nnbhostmgmt -allowautoReissueCert -autoReissue 1\nAlternatively, you can use the NetBackup Administration Console." }, "5992": { "code": 5992, - "desc": "O certificate request has falhou como o host informação não é possível be updated.", - "first_action": "Rerun o operation. If o problema persists, save todos de", - "full_action": "Rerun o operation. If o problema persists, save todos de\no erro log informação e contate Cohesity Technical Support." + "desc": "The certificate request has failed as the host information cannot be updated.", + "first_action": "Rerun the operation. If the problem persists, save all of", + "full_action": "Rerun the operation. If the problem persists, save all of\nthe error log information and contact Cohesity Technical Support." }, "5993": { "code": 5993, - "desc": "O certificate está não valid para this host.", - "first_action": "Verifique que o certificate está issued para o same host e", - "full_action": "Verifique que o certificate está issued para o same host e\nretry o operation. If o problema persists, contate Cohesity Technical Support." + "desc": "The certificate is not valid for this host.", + "first_action": "Verify that the certificate is issued for the same host and", + "full_action": "Verify that the certificate is issued for the same host and\nretry the operation. If the problem persists, contact Cohesity Technical Support." }, "5994": { "code": 5994, - "desc": "O specified fingerprint does não match o CA certificate’s fingerprint.", + "desc": "The specified fingerprint does not match the CA certificate’s fingerprint.", "first_action": "Ensurethatyouhavespecifiedtheappropriatefingerprint", - "full_action": "Ensurethatyouhavespecifiedtheappropriatefingerprint\ne retry o operation. If o problema persists, remove o CA certificate from o\nlocal trust store por usando o nbcertcmd -removeCACertificate comando e\nretry o operation." + "full_action": "Ensurethatyouhavespecifiedtheappropriatefingerprint\nand retry the operation. If the problem persists, remove the CA certificate from the\nlocal trust store by using the nbcertcmd -removeCACertificate command and\nretry the operation." }, "5995": { "code": 5995, - "desc": "O certificate enrollment falhou. O host ID que está associated com o certificate to be enrolled está assigned to another host.", - "first_action": "Provide o certificate que está already enrolled para ou issued to o host.", - "full_action": "Do one de o seguinte:\n■ Provide o certificate que está already enrolled para ou issued to o host.\n■ Add ou update (excluir e then add) o subject name de o certificate in o\nNetBackup banco de dados. Do o seguinte:\n■ Run o nbcertcmd -deleteECACertEntry comando to excluir o\nassociation de o existing host com o certificate.\n■ Run o nbcertcmd -createECACertEntry comando to associate o\ncertificate com o existing host. Para more informação on o commands,\nrefer to o NetBackup Commands Reference Guide." + "desc": "The certificate enrollment failed. The host ID that is associated with the certificate to be enrolled is assigned to another host.", + "first_action": "Provide the certificate that is already enrolled for or issued to the host.", + "full_action": "Do one of the following:\n■ Provide the certificate that is already enrolled for or issued to the host.\n■ Add or update (delete and then add) the subject name of the certificate in the\nNetBackup database. Do the following:\n■ Run the nbcertcmd -deleteECACertEntry command to delete the\nassociation of the existing host with the certificate.\n■ Run the nbcertcmd -createECACertEntry command to associate the\ncertificate with the existing host. For more information on the commands,\nrefer to the NetBackup Commands Reference Guide." }, "5996": { "code": 5996, - "desc": "O certificate enrollment falhou. O request does não contain o certificate ou o certificate está corrupted. NetBackup status codes 770 NetBackup status codes", + "desc": "The certificate enrollment failed. The request does not contain the certificate or the certificate is corrupted. NetBackup status codes 770 NetBackup status codes", "first_action": "Ensurethattheprovidedcertificateis valid.Iftheproblem", - "full_action": "Ensurethattheprovidedcertificateis valid.Iftheproblem\npersists contate Cohesity Technical Support." + "full_action": "Ensurethattheprovidedcertificateis valid.Iftheproblem\npersists contact Cohesity Technical Support." }, "5997": { "code": 5997, - "desc": "O host certificate não é possível be registered. O certificate must contain o Cliente Authentication e Servidor Authentication attributes in o Extended Key Uso field.", - "first_action": "Run o seguinte comando:", - "full_action": "Garanta que o third-party certificate que you desejar to\nregister contains o Cliente Authentication e o Servidor Authentication attributes\nin o Extended Key Uso field. Do o seguinte, como appropriate:\n■ Run o seguinte comando:\nopenssl x509 -in certificatepath -text -noout -purpose\n■ If o certificate contains both o Cliente Authentication e o Servidor\nAuthentication attributes, o seguinte output está displayed:\nCertificate purposes:\nSSL cliente: Yes\nSSL servidor: Yes\nTry to register o third-party certificate again.\n■ Ifoneorbothoftheattributesaremissing,contactyoursecurityadministrator\nto resolve o issue." + "desc": "The host certificate cannot be registered. The certificate must contain the Client Authentication and Server Authentication attributes in the Extended Key Usage field.", + "first_action": "Run the following command:", + "full_action": "Ensure that the third-party certificate that you want to\nregister contains the Client Authentication and the Server Authentication attributes\nin the Extended Key Usage field. Do the following, as appropriate:\n■ Run the following command:\nopenssl x509 -in certificatepath -text -noout -purpose\n■ If the certificate contains both the Client Authentication and the Server\nAuthentication attributes, the following output is displayed:\nCertificate purposes:\nSSL client: Yes\nSSL server: Yes\nTry to register the third-party certificate again.\n■ Ifoneorbothoftheattributesaremissing,contactyoursecurityadministrator\nto resolve the issue." }, "5998": { "code": 5998, - "desc": "O certificate está não enrolled com this primary servidor.", - "first_action": "Enroll o host certificate com o primary servidor por usando", - "full_action": "Enroll o host certificate com o primary servidor por usando\no nbcertcmd -enrollcertificate comando." + "desc": "The certificate is not enrolled with this primary server.", + "first_action": "Enroll the host certificate with the primary server by using", + "full_action": "Enroll the host certificate with the primary server by using\nthe nbcertcmd -enrollcertificate command." }, "5999": { "code": 5999, - "desc": "Theprivatekeyoftheexternalcertificateisencrypted,butthepassphrase está não provided.", - "first_action": "Garanta que o passphrase arquivo caminho está specified para o", - "full_action": "Garanta que o passphrase arquivo caminho está specified para o\nECA_KEY_PASSPHRASEFILE configuration option. Para more informação on o\nNetBackup configuration options, refer to o NetBackup Administrator’s Guide,\nVolume I." + "desc": "Theprivatekeyoftheexternalcertificateisencrypted,butthepassphrase is not provided.", + "first_action": "Ensure that the passphrase file path is specified for the", + "full_action": "Ensure that the passphrase file path is specified for the\nECA_KEY_PASSPHRASEFILE configuration option. For more information on the\nNetBackup configuration options, refer to the NetBackup Administrator’s Guide,\nVolume I." }, "6000": { "code": 6000, - "desc": "O provided caminho está não allowed.", - "first_action": "It está recomendada usando o NetBackup default paths para", - "full_action": "It está recomendada usando o NetBackup default paths para\nprogress logs ou rename arquivo options; para example, use o user_ops folder. If you\ncannotusetheNetBackupdefaultpathinyoursetup,youshouldaddcustompaths\ntotheNetBackupconfiguration.Formoreinformationonhowtoaddacustompath,\nseetheBPCD_ALLOWED_PATHoptionforNetBackupserversandclientssection\nin o NetBackup Administrator’s Guide, Volume I." + "desc": "The provided path is not allowed.", + "first_action": "It is recommended using the NetBackup default paths for", + "full_action": "It is recommended using the NetBackup default paths for\nprogress logs or rename file options; for example, use the user_ops folder. If you\ncannotusetheNetBackupdefaultpathinyoursetup,youshouldaddcustompaths\ntotheNetBackupconfiguration.Formoreinformationonhowtoaddacustompath,\nseetheBPCD_ALLOWED_PATHoptionforNetBackupserversandclientssection\nin the NetBackup Administrator’s Guide, Volume I." }, "6071": { "code": 6071, - "desc": "Credentials de o Cohesity Alta View estão não valid.", + "desc": "Credentials of the Cohesity Alta View are not valid.", "first_action": "Theregistrationtokenhasexpired.Usershoulddownload", - "full_action": "Theregistrationtokenhasexpired.Usershoulddownload\no registration arquivo again from Cohesity Alta View e re-register." + "full_action": "Theregistrationtokenhasexpired.Usershoulddownload\nthe registration file again from Cohesity Alta View and re-register." }, "6072": { "code": 6072, - "desc": "Um internal servidor erro has ocorreu attempting to conectar to o Cohesity Alta View.", - "first_action": "Review o NetBackup Web Service logs para o specific", - "full_action": "Review o NetBackup Web Service logs para o specific\ncause de o falha." + "desc": "An internal server error has occurred attempting to connect to the Cohesity Alta View.", + "first_action": "Review the NetBackup Web Service logs for the specific", + "full_action": "Review the NetBackup Web Service logs for the specific\ncause of the failure." }, "6073": { "code": 6073, - "desc": "Falhou to conectar to o Cohesity Alta View.", - "first_action": "Cohesity Alta View should be reachable from o domain", - "full_action": "Cohesity Alta View should be reachable from o domain\nwheretheNetBackupprimaryserverisinstalledonport443.Confirmthatyouhave\nconnectivity e retry." + "desc": "Failed to connect to the Cohesity Alta View.", + "first_action": "Cohesity Alta View should be reachable from the domain", + "full_action": "Cohesity Alta View should be reachable from the domain\nwheretheNetBackupprimaryserverisinstalledonport443.Confirmthatyouhave\nconnectivity and retry." }, "6074": { "code": 6074, - "desc": "FailedtoestablishapersistentconnectionbetweenthecurrentNetBackup primary servidor e o Cohesity Alta View platform.", - "first_action": "Excluir o domain from o Cohesity Alta View UI e", - "full_action": "Excluir o domain from o Cohesity Alta View UI e\nretry o registration process." + "desc": "FailedtoestablishapersistentconnectionbetweenthecurrentNetBackup primary server and the Cohesity Alta View platform.", + "first_action": "Delete the domain from the Cohesity Alta View UI and", + "full_action": "Delete the domain from the Cohesity Alta View UI and\nretry the registration process." }, "6075": { "code": 6075, - "desc": "Falhou to configure o current NetBackup primary servidor com o Cohesity Alta View platform. NetBackup status codes 773 NetBackup status codes", - "first_action": "Um internal servidor erro occurs when o SSL Handshake foi performed com", - "full_action": "Falhou to establish conexão com Cohesity Alta View\nservidor. Review o seguinte list para possible reasons o falha ocorreu:\n■ Um internal servidor erro occurs when o SSL Handshake foi performed com\no Cohesity Alta View platform.\n■ O Cohesity Alta View servidor está não reachable.\n■ O proxy servidor está não reachable.\nRetry o operation." + "desc": "Failed to configure the current NetBackup primary server with the Cohesity Alta View platform. NetBackup status codes 773 NetBackup status codes", + "first_action": "An internal server error occurs when the SSL Handshake was performed with", + "full_action": "Failed to establish connection with Cohesity Alta View\nserver. Review the following list for possible reasons the failure occurred:\n■ An internal server error occurs when the SSL Handshake was performed with\nthe Cohesity Alta View platform.\n■ The Cohesity Alta View server is not reachable.\n■ The proxy server is not reachable.\nRetry the operation." }, "6078": { "code": 6078, - "desc": "Não foi possível to configure Cohesity Alta View, como it está already configurado.", - "first_action": "O primary servidor está already registered com um Cohesity", - "full_action": "O primary servidor está already registered com um Cohesity\nAlta View servidor. Try to unregister o primary servidor from Cohesity Alta View e\nthen retry registration." + "desc": "Unable to configure Cohesity Alta View, as it is already configured.", + "first_action": "The primary server is already registered with a Cohesity", + "full_action": "The primary server is already registered with a Cohesity\nAlta View server. Try to unregister the primary server from Cohesity Alta View and\nthen retry registration." }, "6079": { "code": 6079, - "desc": "Proxy servidor does não exist.", - "first_action": "Retry o registration com Cohesity Alta View. Review o", - "full_action": "Retry o registration com Cohesity Alta View. Review o\nNetBackup Web Service logs para o specific cause de o falha." + "desc": "Proxy server does not exist.", + "first_action": "Retry the registration with Cohesity Alta View. Review the", + "full_action": "Retry the registration with Cohesity Alta View. Review the\nNetBackup Web Service logs for the specific cause of the failure." }, "6080": { "code": 6080, - "desc": "Falhou to excluir o WebSocket conexão.", - "first_action": "You must clean up o Cohesity Alta View configuration", - "full_action": "You must clean up o Cohesity Alta View configuration\nfilemanually.UsetheDELETECohesityAltaViewServerAPI.Formoreinformation,\ngototheSORTwebsite(https://sort.veritas.com/),andunderSupportedProducts\nselect NetBackup. Then search para NetBackup Alta View API." + "desc": "Failed to delete the WebSocket connection.", + "first_action": "You must clean up the Cohesity Alta View configuration", + "full_action": "You must clean up the Cohesity Alta View configuration\nfilemanually.UsetheDELETECohesityAltaViewServerAPI.Formoreinformation,\ngototheSORTwebsite(https://sort.veritas.com/),andunderSupportedProducts\nselect NetBackup. Then search for NetBackup Alta View API." }, "6082": { "code": 6082, - "desc": "Falhou to get o data collection status para Cohesity Alta View.", - "first_action": "Review o NetBackup Web Service logs para o specific", - "full_action": "Review o NetBackup Web Service logs para o specific\ncause de o falha." + "desc": "Failed to get the data collection status for Cohesity Alta View.", + "first_action": "Review the NetBackup Web Service logs for the specific", + "full_action": "Review the NetBackup Web Service logs for the specific\ncause of the failure." }, "6083": { "code": 6083, - "desc": "Falhou to update o data collection status para Cohesity Alta View.", - "first_action": "Review o NetBackup Web Service logs para o specific", - "full_action": "Review o NetBackup Web Service logs para o specific\ncause de o falha." + "desc": "Failed to update the data collection status for Cohesity Alta View.", + "first_action": "Review the NetBackup Web Service logs for the specific", + "full_action": "Review the NetBackup Web Service logs for the specific\ncause of the failure." }, "6084": { "code": 6084, - "desc": "Falhou to get o servidor informação para o NetBackup primary servidor.", - "first_action": "Review o NetBackup Web Service logs para o specific", - "full_action": "Review o NetBackup Web Service logs para o specific\ncause de o falha." + "desc": "Failed to get the server information for the NetBackup primary server.", + "first_action": "Review the NetBackup Web Service logs for the specific", + "full_action": "Review the NetBackup Web Service logs for the specific\ncause of the failure." }, "6085": { "code": 6085, - "desc": "O proxy servidor está não reachable. O proxy servidor details que estão configurado estão não valid.", - "first_action": "Verifique que o proxy servidor está reachable on o rede", - "full_action": "Verifique que o proxy servidor está reachable on o rede\ne verifique o proxy servidor details que estão configurado para Alta View servidor\ncommunication estão correct." + "desc": "The proxy server is not reachable. The proxy server details that are configured are not valid.", + "first_action": "Verify that the proxy server is reachable on the network", + "full_action": "Verify that the proxy server is reachable on the network\nand verify the proxy server details that are configured for Alta View server\ncommunication are correct." }, "6100": { "code": 6100, - "desc": "Falhou to forward conexão socket to o Private Branch Exchange.", - "first_action": "Verifique o Private Branch Exchange ou o subscriber", - "full_action": "Verifique o Private Branch Exchange ou o subscriber\nprocess logs para more informação. Retry o operation after some time." + "desc": "Failed to forward connection socket to the Private Branch Exchange.", + "first_action": "Check the Private Branch Exchange or the subscriber", + "full_action": "Check the Private Branch Exchange or the subscriber\nprocess logs for more information. Retry the operation after some time." }, "6101": { "code": 6101, - "desc": "Um internal erro has ocorreu during o subscriber process.", - "first_action": "Contate Cohesity Technical Support para assistance.", - "full_action": "Contate Cohesity Technical Support para assistance." + "desc": "An internal error has occurred during the subscriber process.", + "first_action": "Contact Cohesity Technical Support for assistance.", + "full_action": "Contact Cohesity Technical Support for assistance." }, "6102": { "code": 6102, - "desc": "Um socket que connects o subscriber e o message queue broker processos está closed.", - "first_action": "Verifique o subscriber logs.", - "full_action": "Do o seguinte:\n■ Verifique o subscriber logs.\n■ Garanta que o message queue broker process está executando on o servidor." + "desc": "A socket that connects the subscriber and the message queue broker processes is closed.", + "first_action": "Check the subscriber logs.", + "full_action": "Do the following:\n■ Check the subscriber logs.\n■ Ensure that the message queue broker process is running on the server." }, "6103": { "code": 6103, - "desc": "Um socket que connects o publisher e o message queue broker processos está closed.", - "first_action": "Veja o process logs que publish messages to message", - "full_action": "Veja o process logs que publish messages to message\nqueue broker para more logs. Also garanta que message queue broker on o master\nservidor está executando." + "desc": "A socket that connects the publisher and the message queue broker processes is closed.", + "first_action": "See the process logs that publish messages to message", + "full_action": "See the process logs that publish messages to message\nqueue broker for more logs. Also ensure that message queue broker on the master\nserver is running." }, "6104": { "code": 6104, - "desc": "O publisher process não é possível publish messages to o message queue broker.", - "first_action": "Verifique o subscriber process logs de o remote cliente para more details.", - "full_action": "Do o seguinte:\n■ Verifique o subscriber process logs de o remote cliente para more details.\n■ Verifique que remote cliente está up e executando.\n■ Verifique que subscriber service on remote cliente está executando.\n■ Verifique que subscriber service has valid certificate to communicate com master." + "desc": "The publisher process cannot publish messages to the message queue broker.", + "first_action": "Check the subscriber process logs of the remote client for more details.", + "full_action": "Do the following:\n■ Check the subscriber process logs of the remote client for more details.\n■ Check that remote client is up and running.\n■ Check that subscriber service on remote client is running.\n■ Check that subscriber service has valid certificate to communicate with master." }, "6105": { "code": 6105, - "desc": "O publisher e ou subscriber process does não receive um acknowledgment para o published message.", - "first_action": "Garanta que o subscriber está connected to o message", - "full_action": "Garanta que o subscriber está connected to o message\nqueue broker." + "desc": "The publisher and or subscriber process does not receive an acknowledgment for the published message.", + "first_action": "Ensure that the subscriber is connected to the message", + "full_action": "Ensure that the subscriber is connected to the message\nqueue broker." }, "6106": { "code": 6106, - "desc": "Falhou to build um message que está to be published in um JSON format.", - "first_action": "Contate Cohesity Technical Support para assistance.", - "full_action": "Contate Cohesity Technical Support para assistance." + "desc": "Failed to build a message that is to be published in a JSON format.", + "first_action": "Contact Cohesity Technical Support for assistance.", + "full_action": "Contact Cohesity Technical Support for assistance." }, "6107": { "code": 6107, - "desc": "Falhou to parse o JSON message que o message queue broker has sent.", - "first_action": "Contate Cohesity Technical Support para assistance.", - "full_action": "Contate Cohesity Technical Support para assistance." + "desc": "Failed to parse the JSON message that the message queue broker has sent.", + "first_action": "Contact Cohesity Technical Support for assistance.", + "full_action": "Contact Cohesity Technical Support for assistance." }, "6108": { "code": 6108, - "desc": "O message type de o message queue broker está não supported.", - "first_action": "Contate Cohesity Technical Support para assistance.", - "full_action": "Contate Cohesity Technical Support para assistance." + "desc": "The message type of the message queue broker is not supported.", + "first_action": "Contact Cohesity Technical Support for assistance.", + "full_action": "Contact Cohesity Technical Support for assistance." }, "6109": { "code": 6109, - "desc": "Message queue broker details in o JSON response estão não valid.", - "first_action": "Contate Cohesity Technical Support para assistance.", - "full_action": "Contate Cohesity Technical Support para assistance." + "desc": "Message queue broker details in the JSON response are not valid.", + "first_action": "Contact Cohesity Technical Support for assistance.", + "full_action": "Contact Cohesity Technical Support for assistance." }, "6405": { "code": 6405, - "desc": "Specified caminho does não exist on o local disco.", - "first_action": "Specify um staging location on o target host que está on its", - "full_action": "Specify um staging location on o target host que está on its\nlocal disco." + "desc": "Specified path does not exist on the local disk.", + "first_action": "Specify a staging location on the target host that is on its", + "full_action": "Specify a staging location on the target host that is on its\nlocal disk." }, "6172": { "code": 6172, - "desc": "Seu sign in attempt foi negada por o administrator.", + "desc": "Your sign in attempt was denied by the administrator.", "first_action": "ContacttheNetBackupadministratortoresolvethisissue.", "full_action": "ContacttheNetBackupadministratortoresolvethisissue." }, "6173": { "code": 6173, - "desc": "O ticket para seu sign in request has expired.", - "first_action": "Determinar if o approver exists in o system. If they do,", - "full_action": "Determinar if o approver exists in o system. If they do,\nsign in again to generate um new multiperson authorization ticket. If o NetBackup\nadministrator approves seu request, you can log on successfully." + "desc": "The ticket for your sign in request has expired.", + "first_action": "Determine if the approver exists in the system. If they do,", + "full_action": "Determine if the approver exists in the system. If they do,\nsign in again to generate a new multiperson authorization ticket. If the NetBackup\nadministrator approves your request, you can log on successfully." }, "6174": { "code": 6174, - "desc": "Sign-in request foi negada para security reasons.", - "first_action": "If you receive this message when trying to complete um", - "full_action": "If you receive this message when trying to complete um\ntrust primary operation, you can use o nbseccmd to complete o operation. Veja\no NetBackup Commands Reference Guide para more informação." + "desc": "Sign-in request was denied for security reasons.", + "first_action": "If you receive this message when trying to complete a", + "full_action": "If you receive this message when trying to complete a\ntrust primary operation, you can use the nbseccmd to complete the operation. See\nthe NetBackup Commands Reference Guide for more information." }, "6175": { "code": 6175, - "desc": "O sign in request falhou.", - "first_action": "Review o NetBackup Web Services logs para errors e", - "full_action": "Review o NetBackup Web Services logs para errors e\nretry o log on." + "desc": "The sign in request failed.", + "first_action": "Review the NetBackup Web Services logs for errors and", + "full_action": "Review the NetBackup Web Services logs for errors and\nretry the log on." }, "6176": { "code": 6176, - "desc": "Falhou to cancel o sign in request.", - "first_action": "You can ignore this erro message.", - "full_action": "You can ignore this erro message." + "desc": "Failed to cancel the sign in request.", + "first_action": "You can ignore this error message.", + "full_action": "You can ignore this error message." }, "6406": { "code": 6406, - "desc": "WMI conexão to o target host está falhou.", + "desc": "WMI connection to the target host is failed.", "first_action": "ToconnectwithWMIandDCOMservice,usermusthavetherequiredpermission", - "full_action": "O falhou conexão can be due to o seguinte list:\n■ ToconnectwithWMIandDCOMservice,usermusthavetherequiredpermission\nto conectar com o remote WMI service.\n■ Firewall exceptions estão set up to allow WMI traffic through o firewall.\n■ GPO/Software restriction policy ou um antivirus software blocks access.\n■ Garanta que target host está accessible. Validate o given target host credentials.\n■ Garanta que o target host trust relationship com domain está intact. If you\ncommunicate across domains, two-way trust relationship between different\ndomains exists." + "full_action": "The failed connection can be due to the following list:\n■ ToconnectwithWMIandDCOMservice,usermusthavetherequiredpermission\nto connect with the remote WMI service.\n■ Firewall exceptions are set up to allow WMI traffic through the firewall.\n■ GPO/Software restriction policy or an antivirus software blocks access.\n■ Ensure that target host is accessible. Validate the given target host credentials.\n■ Ensure that the target host trust relationship with domain is intact. If you\ncommunicate across domains, two-way trust relationship between different\ndomains exists." }, "6416": { "code": 6416, - "desc": "Não foi possível to find o specified arquivo on o remote servidor.", + "desc": "Unable to find the specified file on the remote server.", "first_action": "Verifythatthespecifiedstaginglocationonthetargethost", - "full_action": "Verifythatthespecifiedstaginglocationonthetargethost\nexists ou specify another valid staging location." + "full_action": "Verifythatthespecifiedstaginglocationonthetargethost\nexists or specify another valid staging location." }, "6423": { "code": 6423, - "desc": "Arquivo exists com same name como o diretório.", - "first_action": "On o remote host, verifique if um arquivo already exists com o", - "full_action": "On o remote host, verifique if um arquivo already exists com o\nsame name e caminho como o staging location. If o arquivo exists, rename ou remove\nque arquivo, ou specify um alternate staging location." + "desc": "File exists with same name as the directory.", + "first_action": "On the remote host, check if a file already exists with the", + "full_action": "On the remote host, check if a file already exists with the\nsame name and path as the staging location. If the file exists, rename or remove\nthat file, or specify an alternate staging location." }, "6430": { "code": 6430, - "desc": "Falhou to validate administrative privileges para o usuário.", - "first_action": "O provided credentials do não have o requerido", - "full_action": "O provided credentials do não have o requerido\npermissions on o target host para agentless arquivos ou folders restauração. Para um Windows\ntarget host, you must use o credentials que estão part de o local administrator\ngrouponthetargethost.ForaUNIXtargethost,usethecredentialsthatarearoot\nou sudo account com Todos permissions." + "desc": "Failed to validate administrative privileges for the user.", + "first_action": "The provided credentials do not have the required", + "full_action": "The provided credentials do not have the required\npermissions on the target host for agentless files or folders restore. For a Windows\ntarget host, you must use the credentials that are part of the local administrator\ngrouponthetargethost.ForaUNIXtargethost,usethecredentialsthatarearoot\nor sudo account with ALL permissions." }, "6431": { "code": 6431, - "desc": "Falhou to conectar um rede resource usando windows API.", - "first_action": "Firewall exceptions estão set up correctly.", - "full_action": "Asapartofagentlessfilesandfoldersrestoresoperation,\no SMB Admin share está created from o recovery host on o target host com o\ncredentials provided por usuário. This erro está seen when o target host para agentless\nrestauração has um Windows OS e o administrator share de o target host está não\naccessible from o recovery host. Verifique o seguinte items on o target host:\n■ Firewall exceptions estão set up correctly.\n■ Arquivo e printer sharing está enabled.\n■ GPO/Software restriction policy ou um antivirus software does não block access.\n■ Target host está accessible com valid credentials." + "desc": "Failed to connect a network resource using windows API.", + "first_action": "Firewall exceptions are set up correctly.", + "full_action": "Asapartofagentlessfilesandfoldersrestoresoperation,\nthe SMB Admin share is created from the recovery host on the target host with the\ncredentials provided by user. This error is seen when the target host for agentless\nrestore has a Windows OS and the administrator share of the target host is not\naccessible from the recovery host. Verify the following items on the target host:\n■ Firewall exceptions are set up correctly.\n■ File and printer sharing is enabled.\n■ GPO/Software restriction policy or an antivirus software does not block access.\n■ Target host is accessible with valid credentials." }, "6435": { "code": 6435, - "desc": "Não foi possível to retrieve user's home diretório on o target host. Specify o custom staging location.", - "first_action": "O user's default staging location, which está o home", - "full_action": "O user's default staging location, which está o home\ndiretório, can't be retrieved on o target host. Retry o operation com um valid\nstaging location." + "desc": "Unable to retrieve user's home directory on the target host. Specify the custom staging location.", + "first_action": "The user's default staging location, which is the home", + "full_action": "The user's default staging location, which is the home\ndirectory, can't be retrieved on the target host. Retry the operation with a valid\nstaging location." }, "6437": { "code": 6437, - "desc": "Falhou to establish SSH session com host.", - "first_action": "Verifique que aes256-ctr está o supported cipher used para communication. Verifique", - "full_action": "Retry o operation after verification de todos o seguinte\ncriteria estão satisfied:\n■ Verifique que aes256-ctr está o supported cipher used para communication. Verifique\nque both o recovery host e o target host support this cipher.\n■ Verifique at least one de o seguinte HMAC protocols estão supported on both\nrecovery host e target host: hmac-sha2-256, hmac-sha2-512.\n■ Verifique que o method que está used para generating o host key está one de o\nseguinte:\n■ ECDSA_SHA2_NISTP256\n■ ECDSA_SHA2_NISTP384\n■ ECDSA_SHA2_NISTP521\n■ SSH_RSA\n■ SSH_DSS" + "desc": "Failed to establish SSH session with host.", + "first_action": "Verify that aes256-ctr is the supported cipher used for communication. Verify", + "full_action": "Retry the operation after verification of all the following\ncriteria are satisfied:\n■ Verify that aes256-ctr is the supported cipher used for communication. Verify\nthat both the recovery host and the target host support this cipher.\n■ Verify at least one of the following HMAC protocols are supported on both\nrecovery host and target host: hmac-sha2-256, hmac-sha2-512.\n■ Verify that the method that is used for generating the host key is one of the\nfollowing:\n■ ECDSA_SHA2_NISTP256\n■ ECDSA_SHA2_NISTP384\n■ ECDSA_SHA2_NISTP521\n■ SSH_RSA\n■ SSH_DSS" }, "6438": { "code": 6438, - "desc": "Falhou to verifique SSH key fingerprint de host.", - "first_action": "Verifique o SSH key fingerprint de o target host e retry", - "full_action": "Verifique o SSH key fingerprint de o target host e retry\no operation." + "desc": "Failed to verify SSH key fingerprint of host.", + "first_action": "Verify the SSH key fingerprint of the target host and retry", + "full_action": "Verify the SSH key fingerprint of the target host and retry\nthe operation." }, "6440": { "code": 6440, - "desc": "Falhou to authenticate o host com provided usuário name ou password.", - "first_action": "Verifique o usuário name e password de o target host e", - "full_action": "Verifique o usuário name e password de o target host e\nretry o operation." + "desc": "Failed to authenticate the host with provided user name or password.", + "first_action": "Verify the user name and password of the target host and", + "full_action": "Verify the user name and password of the target host and\nretry the operation." }, "6441": { "code": 6441, - "desc": "Falhou to authenticate o host com specified SSH key.", + "desc": "Failed to authenticate the host with specified SSH key.", "first_action": "VerifytheSSHprivatekeyandthekeypassphraseifused", - "full_action": "VerifytheSSHprivatekeyandthekeypassphraseifused\nto generate o SSH private key de o target host e retry. Garanta que o\ncorresponding public key está present in o authorized_keys arquivo in /root/.ssh\nfolder at o target host." + "full_action": "VerifytheSSHprivatekeyandthekeypassphraseifused\nto generate the SSH private key of the target host and retry. Ensure that the\ncorresponding public key is present in the authorized_keys file in /root/.ssh\nfolder at the target host." }, "6459": { "code": 6459, - "desc": "Matching SSH key fingerprint host key method foi não found on target host.", + "desc": "Matching SSH key fingerprint host key method was not found on target host.", "first_action": "ThesupportedhostkeymethodofthespecifiedSSHkeyfingerprintisavailable", - "full_action": "Garanta que either:\n■ ThesupportedhostkeymethodofthespecifiedSSHkeyfingerprintisavailable\non target host.\n■ ProvideSSHfingerprintofthehostkeymethodthatisconfiguredontargethost." + "full_action": "Ensure that either:\n■ ThesupportedhostkeymethodofthespecifiedSSHkeyfingerprintisavailable\non target host.\n■ ProvideSSHfingerprintofthehostkeymethodthatisconfiguredontargethost." }, "6530": { "code": 6530, - "desc": "Não foi possível to start SharePoint web service on servidor", - "first_action": "O SharePoint GRT web service,", - "full_action": "O SharePoint GRT web service,\nVeritas.NetBackup.SPServiceHost.exe,isdeployedbydefaultontheNetBackup\nclients e starts apenas during o restores de SharePoint 2016 backups. After o\nrestauração está completed, o web service está stopped.\nVerifique que SharePoint 2016 has been instalado correctly on o front-end servidor.\nYou can also try to manually start o service,\nVeritas.NetBackup.SPServiceHost.exe, from o comando line. Verifique que o\nservice starts during o restauração e stops after o restauração está completed." + "desc": "Unable to start SharePoint web service on server", + "first_action": "The SharePoint GRT web service,", + "full_action": "The SharePoint GRT web service,\nVeritas.NetBackup.SPServiceHost.exe,isdeployedbydefaultontheNetBackup\nclients and starts only during the restores of SharePoint 2016 backups. After the\nrestore is completed, the web service is stopped.\nVerify that SharePoint 2016 has been installed correctly on the front-end server.\nYou can also try to manually start the service,\nVeritas.NetBackup.SPServiceHost.exe, from the command line. Verify that the\nservice starts during the restore and stops after the restore is completed." }, "6531": { "code": 6531, - "desc": "Validation de operating system user/password falhou para cliente", - "first_action": "Configure o SharePoint credentials on todos de o nodes", - "full_action": "Configure o SharePoint credentials on todos de o nodes\nque estão used to browse, backup, ou restauração.\nSee\"ConfiguringthelogonaccountfortheNetBackupClientServiceforNetBackup\npara SharePoint\" in o NetBackup para Microsoft SharePoint Servidor Administrator’s\nGuide." + "desc": "Validation of operating system user/password failed for client", + "first_action": "Configure the SharePoint credentials on all of the nodes", + "full_action": "Configure the SharePoint credentials on all of the nodes\nthat are used to browse, backup, or restore.\nSee\"ConfiguringthelogonaccountfortheNetBackupClientServiceforNetBackup\nfor SharePoint\" in the NetBackup for Microsoft SharePoint Server Administrator’s\nGuide." }, "6600": { "code": 6600, - "desc": "O BigData policy job falhou. Verifique e verifique que you have entered validcredentialsandprovidedcorrectentriesfortheapplicationserverorthebackup hosts.", - "first_action": "Verifique e verifique que you have entered o valid", - "full_action": "Verifique e verifique que you have entered o valid\ncredentials, provided correct entradas para o application servidor ou o backup hosts,\ne resolved qualquer rede connectivity issues." + "desc": "The BigData policy job failed. Check and verify that you have entered validcredentialsandprovidedcorrectentriesfortheapplicationserverorthebackup hosts.", + "first_action": "Check and verify that you have entered the valid", + "full_action": "Check and verify that you have entered the valid\ncredentials, provided correct entries for the application server or the backup hosts,\nand resolved any network connectivity issues." }, "6601": { "code": 6601, - "desc": "One ou more de o input parameters ou arguments estão inválido.", - "first_action": "Verifique e verifique que you have entered valid credentials", - "full_action": "Verifique e verifique que you have entered valid credentials\nandprovidedthecorrectentriesfortheapplicationserverorthebackuphost.Ensure\nque o BigData framework libraries estão correctly instalado on o computer." + "desc": "One or more of the input parameters or arguments are invalid.", + "first_action": "Check and verify that you have entered valid credentials", + "full_action": "Check and verify that you have entered valid credentials\nandprovidedthecorrectentriesfortheapplicationserverorthebackuphost.Ensure\nthat the BigData framework libraries are correctly installed on the computer." }, "6602": { "code": 6602, - "desc": "Insufficient memória ou inadequate resources disponível to complete o job.", - "first_action": "Garanta que sufficient memória está allocated e adequate", - "full_action": "Garanta que sufficient memória está allocated e adequate\nresources estão disponível to o system." + "desc": "Insufficient memory or inadequate resources available to complete the job.", + "first_action": "Ensure that sufficient memory is allocated and adequate", + "full_action": "Ensure that sufficient memory is allocated and adequate\nresources are available to the system." }, "6603": { "code": 6603, - "desc": "Não é possível complete o operation. Access to o servidor está negada due to um lack de system permissions.", - "first_action": "Verifique to veja if o usuário has o requerido permissions to", - "full_action": "Verifique to veja if o usuário has o requerido permissions to\naccesstheapplicationserverandtocompleteabackuporrestoreoperation.Ensure\nque you have added o backup host to o relevant access lists." + "desc": "Cannot complete the operation. Access to the server is denied due to a lack of system permissions.", + "first_action": "Check to see if the user has the required permissions to", + "full_action": "Check to see if the user has the required permissions to\naccesstheapplicationserverandtocompleteabackuporrestoreoperation.Ensure\nthat you have added the backup host to the relevant access lists." }, "6604": { "code": 6604, - "desc": "Falhou to complete o operation. O number de abrir objects on o servidor has reached its limite.", - "first_action": "Aumentar o limite de abrir objects. To aumentar o limite de", - "full_action": "Aumentar o limite de abrir objects. To aumentar o limite de\nabrir objects, veja o appropriate plug-in support guide. Alternatively, you can\nverifique o abrir arquivo settings on o backup host. Para example, ulimit -n on UNIX\nsystems." + "desc": "Failed to complete the operation. The number of open objects on the server has reached its limit.", + "first_action": "Increase the limit of open objects. To increase the limit of", + "full_action": "Increase the limit of open objects. To increase the limit of\nopen objects, see the appropriate plug-in support guide. Alternatively, you can\ncheck the open file settings on the backup host. For example, ulimit -n on UNIX\nsystems." }, "6605": { "code": 6605, - "desc": "Não foi possível to process o request because o servidor resources estão ocupado.", - "first_action": "Retry o operation.", - "full_action": "Retry o operation." + "desc": "Unable to process the request because the server resources are busy.", + "first_action": "Retry the operation.", + "full_action": "Retry the operation." }, "6606": { "code": 6606, - "desc": "Falhou to complete o operation. O object already exists.", + "desc": "Failed to complete the operation. The object already exists.", "first_action": "Ifoneormorevirtualmachinesexistwiththesamename,youcaneitherrename", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Ifoneormorevirtualmachinesexistwiththesamename,youcaneitherrename\nou excluir one de o virtual machines.\n■ Verifique o NetBackup logs (bpbkar logs ou nbappdiscv logs) para more\ninformação.\n■ In addition, you may desejar to remove o relevant state arquivo." + "full_action": "Do the following, as appropriate:\n■ Ifoneormorevirtualmachinesexistwiththesamename,youcaneitherrename\nor delete one of the virtual machines.\n■ Check the NetBackup logs (bpbkar logs or nbappdiscv logs) for more\ninformation.\n■ In addition, you may want to remove the relevant state file." }, "6607": { "code": 6607, - "desc": "O version de NetBackup does não match o version de o BigData framework libraries. NetBackup status codes 787 NetBackup status codes", + "desc": "The version of NetBackup does not match the version of the BigData framework libraries. NetBackup status codes 787 NetBackup status codes", "first_action": "EnsurethatNetBackupandtheBigDataframeworklibraries", - "full_action": "EnsurethatNetBackupandtheBigDataframeworklibraries\nestão correctly instalado." + "full_action": "EnsurethatNetBackupandtheBigDataframeworklibraries\nare correctly installed." }, "6608": { "code": 6608, - "desc": "O version de NetBackup does não match o version de o plug-in libraries.", - "first_action": "Garanta que NetBackup e o relevant plug-in libraries", - "full_action": "Garanta que NetBackup e o relevant plug-in libraries\nestão correctly instalado." + "desc": "The version of NetBackup does not match the version of the plug-in libraries.", + "first_action": "Ensure that NetBackup and the relevant plug-in libraries", + "full_action": "Ensure that NetBackup and the relevant plug-in libraries\nare correctly installed." }, "6609": { "code": 6609, - "desc": "O NetBackup plug-in não é possível complete o operation because o object está inválido.", - "first_action": "Verifique e verifique que you have entered o correct entradas para o application", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Verifique e verifique que you have entered o correct entradas para o application\nservidor ou o backup hosts.\n■ Garanta que you have instalado o correct plug-in to successfully complete o\noperation." + "desc": "The NetBackup plug-in cannot complete the operation because the object is invalid.", + "first_action": "Check and verify that you have entered the correct entries for the application", + "full_action": "Do the following, as appropriate:\n■ Check and verify that you have entered the correct entries for the application\nserver or the backup hosts.\n■ Ensure that you have installed the correct plug-in to successfully complete the\noperation." }, "6610": { "code": 6610, - "desc": "Um internal erro ocorreu in o NetBackup processos.", - "first_action": "Verifique o NetBackup debug logs para more informação.", - "full_action": "Verifique o NetBackup debug logs para more informação." + "desc": "An internal error occurred in the NetBackup processes.", + "first_action": "Check the NetBackup debug logs for more information.", + "full_action": "Check the NetBackup debug logs for more information." }, "6612": { "code": 6612, - "desc": "Não foi possível to process o request because o servidor resources estão either ocupado ou unavailable. Retry o operation.", - "first_action": "Retry o operation.", - "full_action": "Retry o operation." + "desc": "Unable to process the request because the server resources are either busy or unavailable. Retry the operation.", + "first_action": "Retry the operation.", + "full_action": "Retry the operation." }, "6614": { "code": 6614, - "desc": "Falhou to complete o operation.", - "first_action": "Retry o operation after o system está up e executando.", - "full_action": "Retry o operation after o system está up e executando." + "desc": "Failed to complete the operation.", + "first_action": "Retry the operation after the system is up and running.", + "full_action": "Retry the operation after the system is up and running." }, "6616": { "code": 6616, - "desc": "O operation type está currently não supported.", - "first_action": "Garanta o plug-in supports o type de backups ou", - "full_action": "Garanta o plug-in supports o type de backups ou\noperations que you estão trying to complete." + "desc": "The operation type is currently not supported.", + "first_action": "Ensure the plug-in supports the type of backups or", + "full_action": "Ensure the plug-in supports the type of backups or\noperations that you are trying to complete." }, "6617": { "code": 6617, - "desc": "Um system call falhou. NetBackup status codes 789 NetBackup status codes", - "first_action": "Verifique o system logs ou o operating system logs para", - "full_action": "Verifique o system logs ou o operating system logs para\nmore details." + "desc": "A system call failed. NetBackup status codes 789 NetBackup status codes", + "first_action": "Check the system logs or the operating system logs for", + "full_action": "Check the system logs or the operating system logs for\nmore details." }, "6618": { "code": 6618, - "desc": "NetBackup não é possível find o arquivo to complete o operation.", - "first_action": "Verifique o location de o arquivo. Verifique if o arquivo foi deleted", - "full_action": "Verifique o location de o arquivo. Verifique if o arquivo foi deleted\nduring o backup job. Garanta que o arquivo has o requerido access permissions." + "desc": "NetBackup cannot find the file to complete the operation.", + "first_action": "Verify the location of the file. Check if the file was deleted", + "full_action": "Verify the location of the file. Check if the file was deleted\nduring the backup job. Ensure that the file has the required access permissions." }, "6619": { "code": 6619, - "desc": "Um erro ocorreu because de um rede connectivity issue.", - "first_action": "To resolve o rede connectivity issues, verifique o", - "full_action": "To resolve o rede connectivity issues, verifique o\nsystem logs e try again." + "desc": "An error occurred because of a network connectivity issue.", + "first_action": "To resolve the network connectivity issues, check the", + "full_action": "To resolve the network connectivity issues, check the\nsystem logs and try again." }, "6620": { "code": 6620, - "desc": "O servidor has excedido its conexão limite.", - "first_action": "Aumentar o limite de abrir objects. To aumentar o limite de", - "full_action": "Aumentar o limite de abrir objects. To aumentar o limite de\nabrir objects, veja o appropriate plug-in support guide. Alternatively, you can\nverifique o abrir arquivo settings on o backup host. Para example, ulimit -n on UNIX\nsystems." + "desc": "The server has exceeded its connection limit.", + "first_action": "Increase the limit of open objects. To increase the limit of", + "full_action": "Increase the limit of open objects. To increase the limit of\nopen objects, see the appropriate plug-in support guide. Alternatively, you can\ncheck the open file settings on the backup host. For example, ulimit -n on UNIX\nsystems." }, "6621": { "code": 6621, - "desc": "Um erro ocorreu because o rede protocol está não supported.", - "first_action": "Verifique e resolve qualquer rede connectivity issues. To", - "full_action": "Verifique e resolve qualquer rede connectivity issues. To\nresolve o rede connectivity issues, verifique o system logs e try again." + "desc": "An error occurred because the network protocol is not supported.", + "first_action": "Verify and resolve any network connectivity issues. To", + "full_action": "Verify and resolve any network connectivity issues. To\nresolve the network connectivity issues, check the system logs and try again." }, "6622": { "code": 6622, - "desc": "Um internal erro has ocorreu in o NetBackup process.", - "first_action": "In o case de um OpenStack workload, update o image service name to", - "full_action": "Review o NetBackup logs para more details.\n■ In o case de um OpenStack workload, update o image service name to\nglance. Run o seguinte comando in o OpenStack console:\nopenstack service set --name glance name ou ID de image service\n■ In o case de um Hadoop workload, verifique o hadoop.conf JSON arquivo format está\nvalid." + "desc": "An internal error has occurred in the NetBackup process.", + "first_action": "In the case of an OpenStack workload, update the image service name to", + "full_action": "Review the NetBackup logs for more details.\n■ In the case of an OpenStack workload, update the image service name to\nglance. Run the following command in the OpenStack console:\nopenstack service set --name glance name or ID of image service\n■ In the case of a Hadoop workload, verify the hadoop.conf JSON file format is\nvalid." }, "6623": { "code": 6623, - "desc": "Failedtoconnecttotheapplicationserverorthebackuphost.Theserver está either shut down ou não reachable.", + "desc": "Failedtoconnecttotheapplicationserverorthebackuphost.Theserver is either shut down or not reachable.", "first_action": "Verifyandresolveanynetworkconnectivityissues.Ensure", - "full_action": "Verifyandresolveanynetworkconnectivityissues.Ensure\nque o application servidor e o backup host estão up e executando." + "full_action": "Verifyandresolveanynetworkconnectivityissues.Ensure\nthat the application server and the backup host are up and running." }, "6625": { "code": 6625, - "desc": "O backup host está either unauthorized to complete o operation ou it está não foi possível to establish um conexão com o application servidor.", - "first_action": "O backup host has o requerido permissions.", - "full_action": "Garanta o seguinte:\n■ O backup host has o requerido permissions.\n■ Thefirewallissuebetweenthebackuphostandtheapplicationserverisresolved.\n■ O backup host está added to o relevant access lists." + "desc": "The backup host is either unauthorized to complete the operation or it is unable to establish a connection with the application server.", + "first_action": "The backup host has the required permissions.", + "full_action": "Ensure the following:\n■ The backup host has the required permissions.\n■ Thefirewallissuebetweenthebackuphostandtheapplicationserverisresolved.\n■ The backup host is added to the relevant access lists." }, "6626": { "code": 6626, - "desc": "O servidor name está inválido.", - "first_action": "Garanta que you have provided o correct name para o", - "full_action": "Garanta que you have provided o correct name para o\napplication servidor." + "desc": "The server name is invalid.", + "first_action": "Ensure that you have provided the correct name for the", + "full_action": "Ensure that you have provided the correct name for the\napplication server." }, "6628": { "code": 6628, "desc": "UnabletoestablishanetworkconnectionduetoanerrorwiththeDomain Name Service (DNS).", "first_action": "VerifyandresolveanynetworkconnectivityissuesorDNS", - "full_action": "VerifyandresolveanynetworkconnectivityissuesorDNS\nissues. To resolve o rede connectivity issues, verifique o system logs e try\nagain." + "full_action": "VerifyandresolveanynetworkconnectivityissuesorDNS\nissues. To resolve the network connectivity issues, check the system logs and try\nagain." }, "6629": { "code": 6629, - "desc": "Não foi possível to complete o operation. Falhou to authorize o usuário ou o servidor.", - "first_action": "Garanta que o usuário has o requerido permissions e", - "full_action": "Garanta que o usuário has o requerido permissions e\nthattheserver(applicationserverorabackuphost)isaddedtotherelevantaccess\nlists." + "desc": "Unable to complete the operation. Failed to authorize the user or the server.", + "first_action": "Ensure that the user has the required permissions and", + "full_action": "Ensure that the user has the required permissions and\nthattheserver(applicationserverorabackuphost)isaddedtotherelevantaccess\nlists." }, "6630": { "code": 6630, - "desc": "Não foi possível to process o request because o servidor resources estão either ocupado ou unavailable. Retry o operation.", - "first_action": "Garanta que um single job está resorting um particular arquivo ou um", - "full_action": "Garanta que um single job está resorting um particular arquivo ou um\nobject." + "desc": "Unable to process the request because the server resources are either busy or unavailable. Retry the operation.", + "first_action": "Ensure that a single job is resorting a particular file or an", + "full_action": "Ensure that a single job is resorting a particular file or an\nobject." }, "6631": { "code": 6631, - "desc": "There está insufficient armazenamento disponível to o system.", - "first_action": "Garanta que sufficient armazenamento está disponível to o system.", - "full_action": "Garanta que sufficient armazenamento está disponível to o system." + "desc": "There is insufficient storage available to the system.", + "first_action": "Ensure that sufficient storage is available to the system.", + "full_action": "Ensure that sufficient storage is available to the system." }, "6633": { "code": 6633, - "desc": "Não foi possível to complete o operation. Access to o object está negada due to um lack de system permissions.", - "first_action": "Garanta que you have ler e gravar access to o arquivo ou", - "full_action": "Garanta que you have ler e gravar access to o arquivo ou\no object." + "desc": "Unable to complete the operation. Access to the object is denied due to a lack of system permissions.", + "first_action": "Ensure that you have read and write access to the file or", + "full_action": "Ensure that you have read and write access to the file or\nthe object." }, "6634": { "code": 6634, - "desc": "Não foi possível to find o arquivo ou o object.", - "first_action": "Verifique if o arquivo ou o object está disponível at o specified", - "full_action": "Verifique if o arquivo ou o object está disponível at o specified\nlocation. Provide valid entradas to complete o operation." + "desc": "Unable to find the file or the object.", + "first_action": "Check if the file or the object is available at the specified", + "full_action": "Check if the file or the object is available at the specified\nlocation. Provide valid entries to complete the operation." }, "6635": { "code": 6635, - "desc": "O version de o servidor does não support o solicitado operation.", + "desc": "The version of the server does not support the requested operation.", "first_action": "Ensurethattheversionoftheserversupportstheoperation", - "full_action": "Ensurethattheversionoftheserversupportstheoperation\nque you have solicitado." + "full_action": "Ensurethattheversionoftheserversupportstheoperation\nthat you have requested." }, "6640": { "code": 6640, - "desc": "O version de o NetBackup process does não match com o version de o BigData framework libraries.", - "first_action": "Garanta que NetBackup e its framework libraries estão", - "full_action": "Garanta que NetBackup e its framework libraries estão\ncorrectly instalado." + "desc": "The version of the NetBackup process does not match with the version of the BigData framework libraries.", + "first_action": "Ensure that NetBackup and its framework libraries are", + "full_action": "Ensure that NetBackup and its framework libraries are\ncorrectly installed." }, "6641": { "code": 6641, - "desc": "O relevant libraries estão either unavailable ou inaccessible.", - "first_action": "Garanta que NetBackup e its framework libraries estão", - "full_action": "Garanta que NetBackup e its framework libraries estão\ncorrectly instalado e granted relevant access permissions." + "desc": "The relevant libraries are either unavailable or inaccessible.", + "first_action": "Ensure that NetBackup and its framework libraries are", + "full_action": "Ensure that NetBackup and its framework libraries are\ncorrectly installed and granted relevant access permissions." }, "6642": { "code": 6642, - "desc": "O relevant libraries estão either unavailable ou o plug-in does não support o solicitado operation.", + "desc": "The relevant libraries are either unavailable or the plug-in does not support the requested operation.", "first_action": "Toresolvethisissue,checktheNetBackuplogsformissing", "full_action": "Toresolvethisissue,checktheNetBackuplogsformissing\nsymbols." }, "6643": { "code": 6643, - "desc": "Um internal erro ocorreu in o NetBackup processos.", - "first_action": "Verifique o NetBackup logs para more informação.", - "full_action": "Verifique o NetBackup logs para more informação." + "desc": "An internal error occurred in the NetBackup processes.", + "first_action": "Check the NetBackup logs for more information.", + "full_action": "Check the NetBackup logs for more information." }, "6644": { "code": 6644, - "desc": "Um internal erro ocorreu in o NetBackup processos.", - "first_action": "Verifique o system logs ou o operating system logs para", - "full_action": "Verifique o system logs ou o operating system logs para\nmore informação." + "desc": "An internal error occurred in the NetBackup processes.", + "first_action": "Check the system logs or the operating system logs for", + "full_action": "Check the system logs or the operating system logs for\nmore information." }, "6646": { "code": 6646, - "desc": "Não foi possível to communicate com o servidor. NetBackup status codes 795 NetBackup status codes", + "desc": "Unable to communicate with the server. NetBackup status codes 795 NetBackup status codes", "first_action": "Ensurethatyouhaveenteredvalidcredentialsandprovided", - "full_action": "Ensurethatyouhaveenteredvalidcredentialsandprovided\no correct entradas (such como o host name e port number) para o application\nservidor ou o backup host." + "full_action": "Ensurethatyouhaveenteredvalidcredentialsandprovided\nthe correct entries (such as the host name and port number) for the application\nserver or the backup host." }, "6647": { "code": 6647, - "desc": "Não foi possível to create ou access um diretório ou um caminho.", - "first_action": "Garanta que o application servidor lets o backup host", - "full_action": "Garanta que o application servidor lets o backup host\naccess its arquivos ou directories to complete o operations." + "desc": "Unable to create or access a directory or a path.", + "first_action": "Ensure that the application server lets the backup host", + "full_action": "Ensure that the application server lets the backup host\naccess its files or directories to complete the operations." }, "6649": { "code": 6649, - "desc": "O relevant libraries estão either unavailable ou inaccessible.", - "first_action": "Garanta que NetBackup e its framework libraries estão", - "full_action": "Garanta que NetBackup e its framework libraries estão\ncorrectly instalado e have relevant access permissions." + "desc": "The relevant libraries are either unavailable or inaccessible.", + "first_action": "Ensure that NetBackup and its framework libraries are", + "full_action": "Ensure that NetBackup and its framework libraries are\ncorrectly installed and have relevant access permissions." }, "6650": { "code": 6650, - "desc": "O relevant libraries estão either unavailable ou o plug-in does não support o solicitado operation.", - "first_action": "To resolve o issue, verifique o NetBackup logs para um", - "full_action": "To resolve o issue, verifique o NetBackup logs para um\nmissing symbol." + "desc": "The relevant libraries are either unavailable or the plug-in does not support the requested operation.", + "first_action": "To resolve the issue, check the NetBackup logs for a", + "full_action": "To resolve the issue, check the NetBackup logs for a\nmissing symbol." }, "6652": { "code": 6652, - "desc": "Falhou to complete o operation. O version de o plug-in might não support o solicitado operation.", - "first_action": "Garanta que o plug-in version supports o operation", - "full_action": "Garanta que o plug-in version supports o operation\nque you have solicitado." + "desc": "Failed to complete the operation. The version of the plug-in might not support the requested operation.", + "first_action": "Ensure that the plug-in version supports the operation", + "full_action": "Ensure that the plug-in version supports the operation\nthat you have requested." }, "6653": { "code": 6653, - "desc": "O selected schedule type está currently não supported.", + "desc": "The selected schedule type is currently not supported.", "first_action": "WhenyoucreateaBigDatapolicy,ensurethattheplug-in", - "full_action": "WhenyoucreateaBigDatapolicy,ensurethattheplug-in\nsupports o selected schedule type." + "full_action": "WhenyoucreateaBigDatapolicy,ensurethattheplug-in\nsupports the selected schedule type." }, "6654": { "code": 6654, - "desc": "Não foi possível to retrieve o credentials para o servidor.", - "first_action": "Hadoop: When setting o Application_Type parâmetro, you não é possível use qualquer", - "full_action": "Ensurethatyouhaveenteredvalidcredentialsandprovided\ncorrect entradas para o application servidor ou o backup host.\nCreating um BigData policy:\n■ Hadoop: When setting o Application_Type parâmetro, you não é possível use qualquer\nuppercase letters. Example de correct form:\nApplication_Type=hadoop" + "desc": "Unable to retrieve the credentials for the server.", + "first_action": "Hadoop: When setting the Application_Type parameter, you cannot use any", + "full_action": "Ensurethatyouhaveenteredvalidcredentialsandprovided\ncorrect entries for the application server or the backup host.\nCreating a BigData policy:\n■ Hadoop: When setting the Application_Type parameter, you cannot use any\nuppercase letters. Example of correct form:\nApplication_Type=hadoop" }, "6655": { "code": 6655, - "desc": "O virtual machine does não exist.", - "first_action": "Enter um valid name para o virtual machine. O virtual", - "full_action": "Enter um valid name para o virtual machine. O virtual\nmachine display name está case sensitive e it does não allow spaces e certain\nspecial characters." + "desc": "The virtual machine does not exist.", + "first_action": "Enter a valid name for the virtual machine. The virtual", + "full_action": "Enter a valid name for the virtual machine. The virtual\nmachine display name is case sensitive and it does not allow spaces and certain\nspecial characters." }, "6656": { "code": 6656, - "desc": "Inválido credentials. Verifique e enter o correct credentials.", - "first_action": "Verifique e re-enter o valid credentials para o workload.", - "full_action": "Verifique e re-enter o valid credentials para o workload." + "desc": "Invalid credentials. Verify and enter the correct credentials.", + "first_action": "Verify and re-enter the valid credentials for the workload.", + "full_action": "Verify and re-enter the valid credentials for the workload." }, "6657": { "code": 6657, - "desc": "O servidor you estão trying to conectar está não responding.", - "first_action": "Verifique que o application servidor está up e executando e", - "full_action": "Verifique que o application servidor está up e executando e\ntry reconnecting com o servidor." + "desc": "The server you are trying to connect is not responding.", + "first_action": "Verify that the application server is up and running and", + "full_action": "Verify that the application server is up and running and\ntry reconnecting with the server." }, "6658": { "code": 6658, - "desc": "O backup falhou. O snapshot could não be created.", - "first_action": "Refer to o errors listed in o nbaapidiscv log on o", - "full_action": "Refer to o errors listed in o nbaapidiscv log on o\nbackup host e troubleshoot o issues" + "desc": "The backup failed. The snapshot could not be created.", + "first_action": "Refer to the errors listed in the nbaapidiscv log on the", + "full_action": "Refer to the errors listed in the nbaapidiscv log on the\nbackup host and troubleshoot the issues" }, "6659": { "code": 6659, - "desc": "O backup falhou. O workload arquivo could não be created.", - "first_action": "Refer to o errors listed in o nbaapidiscv log on o", - "full_action": "Refer to o errors listed in o nbaapidiscv log on o\nbackup host e troubleshoot o issues." + "desc": "The backup failed. The workload file could not be created.", + "first_action": "Refer to the errors listed in the nbaapidiscv log on the", + "full_action": "Refer to the errors listed in the nbaapidiscv log on the\nbackup host and troubleshoot the issues." }, "6661": { "code": 6661, - "desc": "Não foi possível to find o configuration parâmetro.", - "first_action": "Verifique o content de o azurestack configurations in o credential arquivo que", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Verifique o content de o azurestack configurations in o credential arquivo que\nwasspecifiedwiththetpconfig application_server_confcommandoption.\nBased on o missing configuration parâmetro, modify o configuration que está\nspecified in o credential arquivo e update o tpconfig entry on o master\nservidor.\n■ Verifique o content de o Cassandra production cluster e o DSS cluster\ndetails in o cassandra.conf configuration arquivo." + "desc": "Unable to find the configuration parameter.", + "first_action": "Verify the content of the azurestack configurations in the credential file that", + "full_action": "Perform the following, as appropriate:\n■ Verify the content of the azurestack configurations in the credential file that\nwasspecifiedwiththetpconfig application_server_confcommandoption.\nBased on the missing configuration parameter, modify the configuration that is\nspecified in the credential file and update the tpconfig entry on the master\nserver.\n■ Verify the content of the Cassandra production cluster and the DSS cluster\ndetails in the cassandra.conf configuration file." }, "6662": { "code": 6662, - "desc": "Não foi possível to find o configuration arquivo.", - "first_action": "1. Verifique que o /usr/openv/var/global diretório está whitelisted on o master", - "full_action": "Execute os seguintes passos conforme apropriado:\n1. Verifique que o /usr/openv/var/global diretório está whitelisted on o master\nservidor. Run o bpgetconfig comando.\n2. Verifique que o application_server_name.conf credential arquivo está in o\n/usr/openv/var/global diretório on o master servidor.\n3. If o credential arquivo está não in o /usr/openv/var/global diretório on o\nmasterserver,createa.jsoncredentialfilewiththeazurestackconfigurations\ncom qualquer arquivo name (para example, azurestackserver.conf) at qualquer location on\no master servidor.\n4. Add this arquivo name com o tpconfig add comando. Verifique que o arquivo está in\no /usr/openv/var/global diretório com filename\napplication_server_name.conf after adding tpconfig entry." + "desc": "Unable to find the configuration file.", + "first_action": "1. Verify that the /usr/openv/var/global directory is whitelisted on the master", + "full_action": "Do the following, as appropriate:\n1. Verify that the /usr/openv/var/global directory is whitelisted on the master\nserver. Run the bpgetconfig command.\n2. Verify that the application_server_name.conf credential file is in the\n/usr/openv/var/global directory on the master server.\n3. If the credential file is not in the /usr/openv/var/global directory on the\nmasterserver,createa.jsoncredentialfilewiththeazurestackconfigurations\nwith any file name (for example, azurestackserver.conf) at any location on\nthe master server.\n4. Add this file name with the tpconfig add command. Verify that the file is in\nthe /usr/openv/var/global directory with filename\napplication_server_name.conf after adding tpconfig entry." }, "6663": { "code": 6663, - "desc": "Falhou to establish um Secure Shell conexão com o remote servidor.", - "first_action": "Verifique que you entered o valid credentials para o", - "full_action": "Verifique que you entered o valid credentials para o\napplication servidor." + "desc": "Failed to establish a Secure Shell connection with the remote server.", + "first_action": "Verify that you entered the valid credentials for the", + "full_action": "Verify that you entered the valid credentials for the\napplication server." }, "6664": { "code": 6664, - "desc": "Não foi possível to load JSON object.", - "first_action": "Verifique que o production host usuário password está correct.", - "full_action": "Retry o operation e if o issue persists, visit\nsupport.veritas.com. O Cohesity Technical Support website site offers additional\ninformação to help you troubleshoot this issue.\nWhen performing um backup ou restauração de um Cassandra banco de dados, executar o\nseguinte como appropriate:\n■ Verifique que o production host usuário password está correct.\n■ Verifique que o DSS host usuário password está correct." + "desc": "Unable to load JSON object.", + "first_action": "Verify that the production host user password is correct.", + "full_action": "Retry the operation and if the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support website site offers additional\ninformation to help you troubleshoot this issue.\nWhen performing a backup or restore of a Cassandra database, perform the\nfollowing as appropriate:\n■ Verify that the production host user password is correct.\n■ Verify that the DSS host user password is correct." }, "6665": { "code": 6665, - "desc": "There foi um erro constructing o URL.", + "desc": "There was an error constructing the URL.", "first_action": "Iftheproblempersists,contactCohesityTechnicalSupport.", "full_action": "Iftheproblempersists,contactCohesityTechnicalSupport." }, "6666": { "code": 6666, - "desc": "O MongoDB processos estão não executando on o host.", - "first_action": "To backup ou recover o MongoDB databases, garanta", - "full_action": "To backup ou recover o MongoDB databases, garanta\nque o MongoDB cluster está executando." + "desc": "The MongoDB processes are not running on the host.", + "first_action": "To backup or recover the MongoDB databases, ensure", + "full_action": "To backup or recover the MongoDB databases, ensure\nthat the MongoDB cluster is running." }, "6667": { "code": 6667, - "desc": "O mongod process está não executando on o host.", - "first_action": "To recover o MongoDB databases, garanta que o", - "full_action": "To recover o MongoDB databases, garanta que o\nmongod process está executando." + "desc": "The mongod process is not running on the host.", + "first_action": "To recover the MongoDB databases, ensure that the", + "full_action": "To recover the MongoDB databases, ensure that the\nmongod process is running." }, "6668": { "code": 6668, - "desc": "O mongos process está não executando on o host.", - "first_action": "To recover o MongoDB databases, garanta que o", - "full_action": "To recover o MongoDB databases, garanta que o\nmongos process está executando." + "desc": "The mongos process is not running on the host.", + "first_action": "To recover the MongoDB databases, ensure that the", + "full_action": "To recover the MongoDB databases, ensure that the\nmongos process is running." }, "6669": { "code": 6669, - "desc": "Não foi possível to capture o topology de o MongoDB cluster.", - "first_action": "Garanta que o correct MongoDB credentials estão used ou", - "full_action": "Garanta que o correct MongoDB credentials estão used ou\no MongoDB cluster está executando. Garanta que o MongoDB shards estão connected\nto o config servidor." + "desc": "Unable to capture the topology of the MongoDB cluster.", + "first_action": "Ensure that the correct MongoDB credentials are used or", + "full_action": "Ensure that the correct MongoDB credentials are used or\nthe MongoDB cluster is running. Ensure that the MongoDB shards are connected\nto the config server." }, "6670": { "code": 6670, - "desc": "Não foi possível to capture balancer state.", - "first_action": "Garanta que o correct MongoDB credentials estão used ou", - "full_action": "Garanta que o correct MongoDB credentials estão used ou\no MongoDB cluster está executando. Garanta que o MongoDB shards estão connected\nto o config servidor." + "desc": "Unable to capture balancer state.", + "first_action": "Ensure that the correct MongoDB credentials are used or", + "full_action": "Ensure that the correct MongoDB credentials are used or\nthe MongoDB cluster is running. Ensure that the MongoDB shards are connected\nto the config server." }, "6671": { "code": 6671, - "desc": "Não foi possível to find banco de dados.", - "first_action": "Garanta que o MongoDB cluster está executando e admin", - "full_action": "Garanta que o MongoDB cluster está executando e admin\nbanco de dados está accessible." + "desc": "Unable to find database.", + "first_action": "Ensure that the MongoDB cluster is running and admin", + "full_action": "Ensure that the MongoDB cluster is running and admin\ndatabase is accessible." }, "6672": { "code": 6672, - "desc": "Falhou to shutdown banco de dados servidor. NetBackup status codes 802 NetBackup status codes", - "first_action": "Garanta que o MongoDB cluster está executando e admin", - "full_action": "Garanta que o MongoDB cluster está executando e admin\nbanco de dados está accessible. Garanta que o correct MongoDB credentials estão used." + "desc": "Failed to shutdown database server. NetBackup status codes 802 NetBackup status codes", + "first_action": "Ensure that the MongoDB cluster is running and admin", + "full_action": "Ensure that the MongoDB cluster is running and admin\ndatabase is accessible. Ensure that the correct MongoDB credentials are used." }, "6673": { "code": 6673, - "desc": "Falhou to executar pre-recovery operation.", - "first_action": "To recover o MongoDB databases, garanta que o", - "full_action": "To recover o MongoDB databases, garanta que o\nMongoDBclusterisrunning.EnsurethattheMongoDBclusterisrunningandadmin\nbanco de dados está accessible. Garanta que o correct MongoDB credentials estão used.\nPara more informação, refer to o mdbserver logs." + "desc": "Failed to perform pre-recovery operation.", + "first_action": "To recover the MongoDB databases, ensure that the", + "full_action": "To recover the MongoDB databases, ensure that the\nMongoDBclusterisrunning.EnsurethattheMongoDBclusterisrunningandadmin\ndatabase is accessible. Ensure that the correct MongoDB credentials are used.\nFor more information, refer to the mdbserver logs." }, "6674": { "code": 6674, - "desc": "Falhou to clean o data paths.", + "desc": "Failed to clean the data paths.", "first_action": "EnsurethatthedatapaththatisusedforrunningMongoDB", - "full_action": "EnsurethatthedatapaththatisusedforrunningMongoDB\nprocessos está correct. Para more informação, refer to o mdbserver logs." + "full_action": "EnsurethatthedatapaththatisusedforrunningMongoDB\nprocesses is correct. For more information, refer to the mdbserver logs." }, "6675": { "code": 6675, - "desc": "Data caminho does não exist.", + "desc": "Data path does not exist.", "first_action": "EnsurethatthedatapaththatisusedforrunningMongoDB", - "full_action": "EnsurethatthedatapaththatisusedforrunningMongoDB\nprocessos está correct. Para more informação, refer to o mdbserver logs." + "full_action": "EnsurethatthedatapaththatisusedforrunningMongoDB\nprocesses is correct. For more information, refer to the mdbserver logs." }, "6676": { "code": 6676, - "desc": "UnabletocompletetheoperationbecausetheMongoDBprocessesare executando on o servidor.", - "first_action": "Garanta que o MongoDB processos estão não spawned", - "full_action": "Garanta que o MongoDB processos estão não spawned\nbefore o MongoDB cluster recovery está complete." + "desc": "UnabletocompletetheoperationbecausetheMongoDBprocessesare running on the server.", + "first_action": "Ensure that the MongoDB processes are not spawned", + "full_action": "Ensure that the MongoDB processes are not spawned\nbefore the MongoDB cluster recovery is complete." }, "6677": { "code": 6677, - "desc": "Não foi possível to add um shard to o MongoDB cluster.", - "first_action": "Garanta que o mongos process está executando on o config", - "full_action": "Garanta que o mongos process está executando on o config\nservidor. Garanta que o correct MongoDB credentials estão used." + "desc": "Unable to add a shard to the MongoDB cluster.", + "first_action": "Ensure that the mongos process is running on the config", + "full_action": "Ensure that the mongos process is running on the config\nserver. Ensure that the correct MongoDB credentials are used." }, "6678": { "code": 6678, - "desc": "Falhou to initiate o shard.", - "first_action": "Garanta que o mongod process está executando on o config", - "full_action": "Garanta que o mongod process está executando on o config\nservidor. Garanta que o correct MongoDB credentials estão used." + "desc": "Failed to initiate the shard.", + "first_action": "Ensure that the mongod process is running on the config", + "full_action": "Ensure that the mongod process is running on the config\nserver. Ensure that the correct MongoDB credentials are used." }, "6679": { "code": 6679, - "desc": "Falhou to executar post-recovery operation.", + "desc": "Failed to perform post-recovery operation.", "first_action": "Formoreinformationabouttheerror,refertotheCohesity", - "full_action": "Formoreinformationabouttheerror,refertotheCohesity\nmdbserver logs ou MongoDB logs. If o issue persists, visit support.veritas.com.\nO Cohesity Support site offers additional informação to help you troubleshoot\nthis issue." + "full_action": "Formoreinformationabouttheerror,refertotheCohesity\nmdbserver logs or MongoDB logs. If the issue persists, visit support.veritas.com.\nThe Cohesity Support site offers additional information to help you troubleshoot\nthis issue." }, "6680": { "code": 6680, - "desc": "Não foi possível to recover o MongoDB cluster.", - "first_action": "Para more informação, refer to o mdbserver logs.", - "full_action": "Para more informação, refer to o mdbserver logs." + "desc": "Unable to recover the MongoDB cluster.", + "first_action": "For more information, refer to the mdbserver logs.", + "full_action": "For more information, refer to the mdbserver logs." }, "6681": { "code": 6681, - "desc": "Multiple objects com same name found.", - "first_action": "Garanta que o instance display names estão unique e", - "full_action": "Garanta que o instance display names estão unique e\nreconfigure o policy." + "desc": "Multiple objects with same name found.", + "first_action": "Ensure that the instance display names are unique and", + "full_action": "Ensure that the instance display names are unique and\nreconfigure the policy." }, "6682": { "code": 6682, - "desc": "Host não found.", - "first_action": "Verifique o instance name ou ID e reconfigure o policy.", - "full_action": "Verifique o instance name ou ID e reconfigure o policy." + "desc": "Host not found.", + "first_action": "Verify the instance name or ID and reconfigure the policy.", + "full_action": "Verify the instance name or ID and reconfigure the policy." }, "6683": { "code": 6683, - "desc": "Falhou to create instance snapshot.", - "first_action": "Verifique o OpenStack logs e also garanta que instance", - "full_action": "Verifique o OpenStack logs e also garanta que instance\nsnapshot can be created." + "desc": "Failed to create instance snapshot.", + "first_action": "Verify the OpenStack logs and also ensure that instance", + "full_action": "Verify the OpenStack logs and also ensure that instance\nsnapshot can be created." }, "6684": { "code": 6684, - "desc": "Falhou to create volume snapshot.", - "first_action": "Verifique o OpenStack logs e also garanta que volume", - "full_action": "Verifique o OpenStack logs e also garanta que volume\nsnapshot can be created." + "desc": "Failed to create volume snapshot.", + "first_action": "Verify the OpenStack logs and also ensure that volume", + "full_action": "Verify the OpenStack logs and also ensure that volume\nsnapshot can be created." }, "6685": { "code": 6685, - "desc": "Volume creation está in um inválido state.", - "first_action": "Verifique o OpenStack logs.", - "full_action": "Verifique o OpenStack logs." + "desc": "Volume creation is in an invalid state.", + "first_action": "Verify the OpenStack logs.", + "full_action": "Verify the OpenStack logs." }, "6686": { "code": 6686, - "desc": "Falhou to retrieve volume details.", - "first_action": "Verifique o OpenStack logs.", - "full_action": "Verifique o OpenStack logs." + "desc": "Failed to retrieve volume details.", + "first_action": "Verify the OpenStack logs.", + "full_action": "Verify the OpenStack logs." }, "6687": { "code": 6687, - "desc": "Volume snapshot creation está in um inválido state.", - "first_action": "Verifique o OpenStack logs.", - "full_action": "Verifique o OpenStack logs." + "desc": "Volume snapshot creation is in an invalid state.", + "first_action": "Verify the OpenStack logs.", + "full_action": "Verify the OpenStack logs." }, "6688": { "code": 6688, - "desc": "Falhou to retrieve volume snapshot details.", - "first_action": "Verifique o OpenStack logs.", - "full_action": "Verifique o OpenStack logs." + "desc": "Failed to retrieve volume snapshot details.", + "first_action": "Verify the OpenStack logs.", + "full_action": "Verify the OpenStack logs." }, "6689": { "code": 6689, - "desc": "MongoDBtopologyhaschangedsincethelastbackup.Youmustcreate um cheio backup.", - "first_action": "Run um cheio backup if o topology has changed. Seguinte", - "full_action": "Run um cheio backup if o topology has changed. Seguinte\num successful cheio backup, um incremental backup should be possible." + "desc": "MongoDBtopologyhaschangedsincethelastbackup.Youmustcreate a full backup.", + "first_action": "Run a full backup if the topology has changed. Following", + "full_action": "Run a full backup if the topology has changed. Following\na successful full backup, an incremental backup should be possible." }, "6690": { "code": 6690, - "desc": "O MongoDB rename arquivo está either missing ou inválido.", + "desc": "The MongoDB rename file is either missing or invalid.", "first_action": "Reviewthesyntaxoftheentriesintherenamefile.Incase", - "full_action": "Reviewthesyntaxoftheentriesintherenamefile.Incase\nde recovery to o alternate application servidor, make sure que o alternate\napplication servidor está specified in change entry in format como\nALT_APPLICATION_SERVER=Host:Port.Also,verifythatasingleinstancehost:port\nestá não redirected to multiple host:port." + "full_action": "Reviewthesyntaxoftheentriesintherenamefile.Incase\nof recovery to the alternate application server, make sure that the alternate\napplication server is specified in change entry in format as\nALT_APPLICATION_SERVER=Host:Port.Also,verifythatasingleinstancehost:port\nis not redirected to multiple host:port." }, "6691": { "code": 6691, - "desc": "Não foi possível to create MongoDB restauração specification arquivo.", - "first_action": "Make sure que o backup host (Destination cliente) está", - "full_action": "Make sure que o backup host (Destination cliente) está\nreachable por o NetBackup master servidor." + "desc": "Unable to create MongoDB restore specification file.", + "first_action": "Make sure that the backup host (Destination client) is", + "full_action": "Make sure that the backup host (Destination client) is\nreachable by the NetBackup master server." }, "6692": { "code": 6692, - "desc": "Não foi possível to ler e process o MongoDB restauração specification arquivo.", - "first_action": "Garanta que o NetBackup backup host (Destination", - "full_action": "Garanta que o NetBackup backup host (Destination\ncliente) has o proper access permissions." + "desc": "Unable to read and process the MongoDB restore specification file.", + "first_action": "Ensure that the NetBackup backup host (Destination", + "full_action": "Ensure that the NetBackup backup host (Destination\nclient) has the proper access permissions." }, "6693": { "code": 6693, - "desc": "Não foi possível to ler e process o MongoDB configuration arquivo.", - "first_action": "Garanta que o NetBackup backup host (Destination", - "full_action": "Garanta que o NetBackup backup host (Destination\ncliente) has o proper access permissions." + "desc": "Unable to read and process the MongoDB configuration file.", + "first_action": "Ensure that the NetBackup backup host (Destination", + "full_action": "Ensure that the NetBackup backup host (Destination\nclient) has the proper access permissions." }, "6694": { "code": 6694, - "desc": "Backup de MongoDB está supported apenas on Logical Volume Management based volumes.", - "first_action": "Garanta to mount o banco de dados diretório on um logical", - "full_action": "Garanta to mount o banco de dados diretório on um logical\nvolume." + "desc": "Backup of MongoDB is supported only on Logical Volume Management based volumes.", + "first_action": "Ensure to mount the database directory on a logical", + "full_action": "Ensure to mount the database directory on a logical\nvolume." }, "6695": { "code": 6695, - "desc": "Backup de MongoDB on VxFS volumes está não supported.", - "first_action": "Garanta to mount o banco de dados diretório on um logical", - "full_action": "Garanta to mount o banco de dados diretório on um logical\nvolume." + "desc": "Backup of MongoDB on VxFS volumes is not supported.", + "first_action": "Ensure to mount the database directory on a logical", + "full_action": "Ensure to mount the database directory on a logical\nvolume." }, "6696": { "code": 6696, @@ -11617,6662 +11617,6662 @@ }, "6697": { "code": 6697, - "desc": "Maximum number de supported volumes has been reached.", - "first_action": "O maximum number de attached volumes que estão", - "full_action": "O maximum number de attached volumes que estão\nsupported está 32." + "desc": "Maximum number of supported volumes has been reached.", + "first_action": "The maximum number of attached volumes that are", + "full_action": "The maximum number of attached volumes that are\nsupported is 32." }, "6698": { "code": 6698, - "desc": "Maximum number de supported security groups excedido. NetBackup status codes 809 NetBackup status codes", + "desc": "Maximum number of supported security groups exceeded. NetBackup status codes 809 NetBackup status codes", "first_action": "Themaximumnumberofsecuritygroupsthataresupported", - "full_action": "Themaximumnumberofsecuritygroupsthataresupported\nestá 32. Adjust o number de security groups e retry o operation." + "full_action": "Themaximumnumberofsecuritygroupsthataresupported\nis 32. Adjust the number of security groups and retry the operation." }, "6699": { "code": 6699, - "desc": "Maximum number de supported attached volumes excedido.", + "desc": "Maximum number of supported attached volumes exceeded.", "first_action": "Themaximumnumberofextendedattachedvolumesthat", "full_action": "Themaximumnumberofextendedattachedvolumesthat\naresupportedis32.Adjustthenumberofattachedvolumesandretrytheoperation." }, "6700": { "code": 6700, - "desc": "Maximum number de supported rede interfaces reached.", - "first_action": "O maximum number de rede interfaces que estão", - "full_action": "O maximum number de rede interfaces que estão\nsupported está 100. Adjust o number de rede interfaces e retry o operation." + "desc": "Maximum number of supported network interfaces reached.", + "first_action": "The maximum number of network interfaces that are", + "full_action": "The maximum number of network interfaces that are\nsupported is 100. Adjust the number of network interfaces and retry the operation." }, "6701": { "code": 6701, - "desc": "Não foi possível to abrir o dispositivo.", + "desc": "Unable to open the device.", "first_action": "Verifythatyourstoragesystemisingoodstate.Alsoverify", - "full_action": "Verifythatyourstoragesystemisingoodstate.Alsoverify\nseu backup host e instance to be salvo up estão on o same Hypervisor." + "full_action": "Verifythatyourstoragesystemisingoodstate.Alsoverify\nyour backup host and instance to be backed up are on the same Hypervisor." }, "6702": { "code": 6702, - "desc": "Não foi possível to obtain o authentication token.", + "desc": "Unable to obtain the authentication token.", "first_action": "Thetokenisgeneratedusingacombinationofusername,", - "full_action": "Thetokenisgeneratedusingacombinationofusername,\nusuário password, usuário domain name, project name, e project domain name. Verifique\nque these values estão correctly mentioned in creds arquivo." + "full_action": "Thetokenisgeneratedusingacombinationofusername,\nuser password, user domain name, project name, and project domain name. Verify\nthat these values are correctly mentioned in creds file." }, "6703": { "code": 6703, - "desc": "Backup de um instance com flavor disco size 0 e booting from image está não supported.", - "first_action": "Verifique que NetBackup does não attempt to back up um", - "full_action": "Verifique que NetBackup does não attempt to back up um\ninstance booting from um image e usando um flavor com disco size 0." + "desc": "Backup of an instance with flavor disk size 0 and booting from image is not supported.", + "first_action": "Verify that NetBackup does not attempt to back up an", + "full_action": "Verify that NetBackup does not attempt to back up an\ninstance booting from an image and using a flavor with disk size 0." }, "6704": { "code": 6704, - "desc": "Restoring multiple MongoDB nodes on one replica set está inválido.", - "first_action": "Apenas one node can be restored in um replica set. Select", - "full_action": "Apenas one node can be restored in um replica set. Select\nredirect restauração e edit o caminho to point to one node from o replica set. If seu\nbackup foi done from different nodes due to role changes, select todos nodes to be\nrestored to one node on o destination cluster. This operation should be done por\nselecting o alternate restauração option in o restauração workflow. Use o alternate\nrestauração option in o restauração workflow." + "desc": "Restoring multiple MongoDB nodes on one replica set is invalid.", + "first_action": "Only one node can be restored in a replica set. Select", + "full_action": "Only one node can be restored in a replica set. Select\nredirect restore and edit the path to point to one node from the replica set. If your\nbackup was done from different nodes due to role changes, select all nodes to be\nrestored to one node on the destination cluster. This operation should be done by\nselecting the alternate restore option in the restore workflow. Use the alternate\nrestore option in the restore workflow." }, "6705": { "code": 6705, - "desc": "Restoring MongoDB data on um arbiter node está inválido.", - "first_action": "Select another node in o destination MongoDB cluster", - "full_action": "Select another node in o destination MongoDB cluster\nque está não um arbiter in o destination MongoDB cluster." + "desc": "Restoring MongoDB data on an arbiter node is invalid.", + "first_action": "Select another node in the destination MongoDB cluster", + "full_action": "Select another node in the destination MongoDB cluster\nthat is not an arbiter in the destination MongoDB cluster." }, "6706": { "code": 6706, "desc": "Adiscoveredshardwasfoundindrainstate,cannotproceedwithbackup.", - "first_action": "Retry o backup operation when o shard está fora de o", - "full_action": "Retry o backup operation when o shard está fora de o\ndrain state. Refer to o MongoDB Administrator’s Guide to change o state de o\nshard." + "first_action": "Retry the backup operation when the shard is out of the", + "full_action": "Retry the backup operation when the shard is out of the\ndrain state. Refer to the MongoDB Administrator’s Guide to change the state of the\nshard." }, "6707": { "code": 6707, - "desc": "Um unsupported MongoDB armazenamento engine está detected.", - "first_action": "Change o armazenamento engine to Wired Tiger e resubmit", - "full_action": "Change o armazenamento engine to Wired Tiger e resubmit\nyouroperation.RefertoMongoDBdocumentationforchangingthestorageengine." + "desc": "An unsupported MongoDB storage engine is detected.", + "first_action": "Change the storage engine to Wired Tiger and resubmit", + "full_action": "Change the storage engine to Wired Tiger and resubmit\nyouroperation.RefertoMongoDBdocumentationforchangingthestorageengine." }, "6708": { "code": 6708, - "desc": "Não foi possível to parse comando output.", - "first_action": "Refer to o mdbserver logs to get more details de o", - "full_action": "Refer to o mdbserver logs to get more details de o\ncomando status e its falha. Retry o operation e if o issue persists, visit\no Cohesity Technical Support website. O Cohesity Technical Support website\noffers additional informação to help you troubleshoot this issue." + "desc": "Unable to parse command output.", + "first_action": "Refer to the mdbserver logs to get more details of the", + "full_action": "Refer to the mdbserver logs to get more details of the\ncommand status and its failure. Retry the operation and if the issue persists, visit\nthe Cohesity Technical Support website. The Cohesity Technical Support website\noffers additional information to help you troubleshoot this issue." }, "6709": { "code": 6709, - "desc": "Não foi possível to run o comando.", - "first_action": "Refer to o mdbserver logs to find o erro code e refer to o MongoDB", - "full_action": "Multipleworkloadscanshowthiserror.Reviewthefollowing\ninformação para seu specific workload.\nWhen performing um backup ou restauração de um MongoDB, review o seguinte:\n■ Refer to o mdbserver logs to find o erro code e refer to o MongoDB\nAdministrator’s Guide para o reason de o falha based on o erro code. If\nexecutando um incremental backup on MongoDB version 4.4 ou later, then garanta\nto have o mongodump utility instalado. After installation, retry o operation e\nif o issue persists, visit o Cohesity Technical Support website. O Cohesity\nTechnicalSupportwebsiteoffersadditionalinformationtohelpyoutroubleshoot\nthis issue.\n■ Whencertificate-basedauthenticationisenabled,differentialincrementalbackups\nmayfail.Refertothemdbserverlogstofindtheerrorcodeandcommanddetails.\nIf o mdbserver logs indicate um mongodump comando falha, try executando o\nmongodump comando manually on o MongoDB host e verifique o erro. If\no mongodump comando fails com X509 certificate-related conexão errors,\nyou must fix these errors por updating o MongoDB servidor certificates com o\nsubjectAltName property como per o MongoDB documentation. Then retry o\ndifferential incremental backup.\nWhen performing um backup ou restauração de um Cassandra banco de dados, executar o\nseguinte como appropriate:\n■ Verifique SSH sessions para production nodes. O CBR node should be able to\nuse SSH to conectar to o production nodes.\n■ Garanta que o CBR node está executando e reachable.\n■ Verifique que nbcbr process está executando. If o process está não executando, manually\nclearthefolderthatisspecifiedintheCassandraconfigurationfileonCassandra\ncluster nodes e retry o backup operation again." + "desc": "Unable to run the command.", + "first_action": "Refer to the mdbserver logs to find the error code and refer to the MongoDB", + "full_action": "Multipleworkloadscanshowthiserror.Reviewthefollowing\ninformation for your specific workload.\nWhen performing a backup or restore of a MongoDB, review the following:\n■ Refer to the mdbserver logs to find the error code and refer to the MongoDB\nAdministrator’s Guide for the reason of the failure based on the error code. If\nrunning an incremental backup on MongoDB version 4.4 or later, then ensure\nto have the mongodump utility installed. After installation, retry the operation and\nif the issue persists, visit the Cohesity Technical Support website. The Cohesity\nTechnicalSupportwebsiteoffersadditionalinformationtohelpyoutroubleshoot\nthis issue.\n■ Whencertificate-basedauthenticationisenabled,differentialincrementalbackups\nmayfail.Refertothemdbserverlogstofindtheerrorcodeandcommanddetails.\nIf the mdbserver logs indicate a mongodump command failure, try running the\nmongodump command manually on the MongoDB host and check the error. If\nthe mongodump command fails with X509 certificate-related connection errors,\nyou must fix these errors by updating the MongoDB server certificates with the\nsubjectAltName property as per the MongoDB documentation. Then retry the\ndifferential incremental backup.\nWhen performing a backup or restore of a Cassandra database, perform the\nfollowing as appropriate:\n■ Check SSH sessions for production nodes. The CBR node should be able to\nuse SSH to connect to the production nodes.\n■ Ensure that the CBR node is running and reachable.\n■ Verify that nbcbr process is running. If the process is not running, manually\nclearthefolderthatisspecifiedintheCassandraconfigurationfileonCassandra\ncluster nodes and retry the backup operation again." }, "6710": { "code": 6710, - "desc": "Pre-check para recovery has falhou como WiredTiger log arquivos estão present at o banco de dados caminho.", - "first_action": "Select o overwrite option in o restauração workflow e", - "full_action": "Select o overwrite option in o restauração workflow e\nretry o operation." + "desc": "Pre-check for recovery has failed as WiredTiger log files are present at the database path.", + "first_action": "Select the overwrite option in the restore workflow and", + "full_action": "Select the overwrite option in the restore workflow and\nretry the operation." }, "6711": { "code": 6711, - "desc": "Não foi possível to backup MongoDB configuration arquivo.", - "first_action": "Review o access control para o MongoDB configuration arquivo. Allow o host", - "full_action": "Review o mdbserver logs para more details.\nTry o seguinte como appropriate:\n■ Review o access control para o MongoDB configuration arquivo. Allow o host\nuserthatisspecifiedinthetpconfigforthisnode,alltherightsthatarerequired\nto ler o MongoDB configuration arquivo.\n■ Review o access control rights to o snapshot diretório que está specified in\ntpconfig. Allow o host usuário que está specified in o tpconfig para this node,\no rights to gravar to o snapshot mount diretório.\nRetry o operation e if o issue persists, visit o Cohesity Technical Support\nwebsite. O Cohesity Technical Support website offers additional informação to\nhelp you troubleshoot this issue." + "desc": "Unable to backup MongoDB configuration file.", + "first_action": "Review the access control for the MongoDB configuration file. Allow the host", + "full_action": "Review the mdbserver logs for more details.\nTry the following as appropriate:\n■ Review the access control for the MongoDB configuration file. Allow the host\nuserthatisspecifiedinthetpconfigforthisnode,alltherightsthatarerequired\nto read the MongoDB configuration file.\n■ Review the access control rights to the snapshot directory that is specified in\ntpconfig. Allow the host user that is specified in the tpconfig for this node,\nthe rights to write to the snapshot mount directory.\nRetry the operation and if the issue persists, visit the Cohesity Technical Support\nwebsite. The Cohesity Technical Support website offers additional information to\nhelp you troubleshoot this issue." }, "6712": { "code": 6712, - "desc": "Não foi possível to find operation log para previous backup.", + "desc": "Unable to find operation log for previous backup.", "first_action": "Changethescheduletypetofullandretrythebackupand", - "full_action": "Changethescheduletypetofullandretrythebackupand\nverifique que it completes com não issues. Schedule um incremental backup after o\ncheio backup." + "full_action": "Changethescheduletypetofullandretrythebackupand\nverify that it completes with no issues. Schedule an incremental backup after the\nfull backup." }, "6713": { "code": 6713, "desc": "Operation log roll-over detected.", - "first_action": "Change o schedule type to cheio e retry o backup.", - "full_action": "Change o schedule type to cheio e retry o backup.\nSchedule um incremental backup after o cheio backup. Aumentar o frequency de\nincremental backups ou aumentar o size de o operation logs such que operation\nlogs do não roll over before o next incremental. This step must be done based on\no average number de operations que estão done on MongoDB e o recovery\npoint objective para seu data. Refer to MongoDB Administrator’s Guide to change\no operation log size." + "first_action": "Change the schedule type to full and retry the backup.", + "full_action": "Change the schedule type to full and retry the backup.\nSchedule an incremental backup after the full backup. Increase the frequency of\nincremental backups or increase the size of the operation logs such that operation\nlogs do not roll over before the next incremental. This step must be done based on\nthe average number of operations that are done on MongoDB and the recovery\npoint objective for your data. Refer to MongoDB Administrator’s Guide to change\nthe operation log size." }, "6714": { "code": 6714, - "desc": "Erro while collection foi iterated.", - "first_action": "Refer to mdbserver logs to get details de o erro. Run um", - "full_action": "Refer to mdbserver logs to get details de o erro. Run um\nfullbackupandafterthefullbackupissuccessful,scheduleanincrementalbackup." + "desc": "Error while collection was iterated.", + "first_action": "Refer to mdbserver logs to get details of the error. Run a", + "full_action": "Refer to mdbserver logs to get details of the error. Run a\nfullbackupandafterthefullbackupissuccessful,scheduleanincrementalbackup." }, "6715": { "code": 6715, - "desc": "Operation log verification erro.", - "first_action": "Refer to mdbserver logs to get details de o erro. Run um", - "full_action": "Refer to mdbserver logs to get details de o erro. Run um\nfullbackupandafterthefullbackupissuccessful,scheduleanincrementalbackup." + "desc": "Operation log verification error.", + "first_action": "Refer to mdbserver logs to get details of the error. Run a", + "full_action": "Refer to mdbserver logs to get details of the error. Run a\nfullbackupandafterthefullbackupissuccessful,scheduleanincrementalbackup." }, "6716": { "code": 6716, - "desc": "Falhou I/O operation on operation log store info arquivo.", - "first_action": "Review o nbaapireq_handler logs e o mdbserver", - "full_action": "Review o nbaapireq_handler logs e o mdbserver\nlogs to troubleshoot o issue. If o falha está para deleting operation logs, manually\nexcluir these to bring up o MongoDB instance to get it executando. If o falha está in\nfinding o operation log caminho, visit o Cohesity Technical Support website. O\nCohesity Technical Support website offers additional informação to help you\ntroubleshoot this issue." + "desc": "Failed I/O operation on operation log store info file.", + "first_action": "Review the nbaapireq_handler logs and the mdbserver", + "full_action": "Review the nbaapireq_handler logs and the mdbserver\nlogs to troubleshoot the issue. If the failure is for deleting operation logs, manually\ndelete these to bring up the MongoDB instance to get it running. If the failure is in\nfinding the operation log path, visit the Cohesity Technical Support website. The\nCohesity Technical Support website offers additional information to help you\ntroubleshoot this issue." }, "6717": { "code": 6717, - "desc": "Invaliddeletepathwaspassedforrestoredoperationlogfiles.Operation log arquivos have não been deleted.", - "first_action": "Refer to mdbserver logs para more details. If o issue", - "full_action": "Refer to mdbserver logs para more details. If o issue\npersists, visit o Cohesity Technical Support website. O Cohesity Technical\nSupport website offers additional informação to help you troubleshoot this issue." + "desc": "Invaliddeletepathwaspassedforrestoredoperationlogfiles.Operation log files have not been deleted.", + "first_action": "Refer to mdbserver logs for more details. If the issue", + "full_action": "Refer to mdbserver logs for more details. If the issue\npersists, visit the Cohesity Technical Support website. The Cohesity Technical\nSupport website offers additional information to help you troubleshoot this issue." }, "6718": { "code": 6718, - "desc": "Não foi possível to replay operation logs.", + "desc": "Unable to replay operation logs.", "first_action": "4.4orlater,thenensuretohavethemongorestoreutilityinstalled.Afterinstallation,", - "full_action": "If executando um incremental recovery on MongoDB version\n4.4orlater,thenensuretohavethemongorestoreutilityinstalled.Afterinstallation,\nmanually apply o operation log. Refer to o operation logs restored from\nmdbserver logs e restauração these manually. Refer to MongoDB Administrator’s\nGuide para o mongorestore comando parameters." + "full_action": "If running an incremental recovery on MongoDB version\n4.4orlater,thenensuretohavethemongorestoreutilityinstalled.Afterinstallation,\nmanually apply the operation log. Refer to the operation logs restored from\nmdbserver logs and restore these manually. Refer to MongoDB Administrator’s\nGuide for the mongorestore command parameters." }, "6719": { "code": 6719, - "desc": "Não foi possível to revoke NetBackup replay operation logs role from usuário.", - "first_action": "Review o mdbserver logs para details.", - "full_action": "Review o mdbserver logs para details.\nRun o seguinte comando to manually revoke o NetBackup replay operations\nlogsroleontheuser:\"db.getSiblingDB('admin').revokeRolesFromUser('{user\ninfo}',[{'role':'netbackup-replayoplogs', 'db':'admin'}])" + "desc": "Unable to revoke NetBackup replay operation logs role from user.", + "first_action": "Review the mdbserver logs for details.", + "full_action": "Review the mdbserver logs for details.\nRun the following command to manually revoke the NetBackup replay operations\nlogsroleontheuser:\"db.getSiblingDB('admin').revokeRolesFromUser('{user\ninfo}',[{'role':'netbackup-replayoplogs', 'db':'admin'}])" }, "6720": { "code": 6720, - "desc": "Não foi possível to drop NetBackup replay operation logs role.", - "first_action": "Review o mdbserver logs para details.", - "full_action": "Review o mdbserver logs para details.\nRun o seguinte comando to manually drop o role para o administrator usuário:\n\"db.getSiblingDB('admin').dropRole('netbackup-replayoplogs')" + "desc": "Unable to drop NetBackup replay operation logs role.", + "first_action": "Review the mdbserver logs for details.", + "full_action": "Review the mdbserver logs for details.\nRun the following command to manually drop the role for the administrator user:\n\"db.getSiblingDB('admin').dropRole('netbackup-replayoplogs')" }, "6721": { "code": 6721, - "desc": "Unabletoreplayoperationlogs.Also,failedtorevokeNetBackupreplay operation logs role e drop NetBackup replay operation logs role.", + "desc": "Unabletoreplayoperationlogs.Also,failedtorevokeNetBackupreplay operation logs role and drop NetBackup replay operation logs role.", "first_action": "RunthefollowingcommandtomanuallyrevoketheNetBackupreplayoperations", - "full_action": "Review o mdbserver logs para details.\nExecutar o seguinte:\n■ RunthefollowingcommandtomanuallyrevoketheNetBackupreplayoperations\nlogs role para o usuário:\n\"db.getSiblingDB('admin').revokeRolesFromUser('{user\ninfo}',[{'role':'netbackup-replayoplogs', 'db':'admin'}])\".\n■ Run o seguinte comando to manually drop o role de o administrator usuário:\n\"db.getSiblingDB('admin').dropRole('netbackup-replayoplogs')" + "full_action": "Review the mdbserver logs for details.\nPerform the following:\n■ RunthefollowingcommandtomanuallyrevoketheNetBackupreplayoperations\nlogs role for the user:\n\"db.getSiblingDB('admin').revokeRolesFromUser('{user\ninfo}',[{'role':'netbackup-replayoplogs', 'db':'admin'}])\".\n■ Run the following command to manually drop the role of the administrator user:\n\"db.getSiblingDB('admin').dropRole('netbackup-replayoplogs')" }, "6722": { "code": 6722, - "desc": "Não foi possível to replay o operation logs. Also, falhou to revoke NetBackup replay operation logs role.", - "first_action": "Manually apply o operation log. Refer to o operation", - "full_action": "Manually apply o operation log. Refer to o operation\nlogs restored from mdbserver logs e restauração these manually. Refer to MongoDB\nAdministrator’s Guide para o mongorestore comando parameters.\nRun o seguinte comando to manually revoke o NetBackup replay operations\nlogsroleontheuser:\"db.getSiblingDB('admin').revokeRolesFromUser('{user\ninfo}',[{'role':'netbackup-replayoplogs', 'db':'admin'}])" + "desc": "Unable to replay the operation logs. Also, failed to revoke NetBackup replay operation logs role.", + "first_action": "Manually apply the operation log. Refer to the operation", + "full_action": "Manually apply the operation log. Refer to the operation\nlogs restored from mdbserver logs and restore these manually. Refer to MongoDB\nAdministrator’s Guide for the mongorestore command parameters.\nRun the following command to manually revoke the NetBackup replay operations\nlogsroleontheuser:\"db.getSiblingDB('admin').revokeRolesFromUser('{user\ninfo}',[{'role':'netbackup-replayoplogs', 'db':'admin'}])" }, "6723": { "code": 6723, - "desc": "Não foi possível to replay operation logs. Also, falhou to drop NetBackup replay operation logs role. NetBackup status codes 818 NetBackup status codes", - "first_action": "Manually apply o operation log. Refer to o operation", - "full_action": "Manually apply o operation log. Refer to o operation\nlogs restored from mdbserver logs e restauração these manually. Refer to MongoDB\nAdministrator’s Guide para o mongorestore comando parameters.\nRun o seguinte comando to manually drop o role on o administrator usuário:\n\"db.getSiblingDB('admin').dropRole('netbackup-replayoplogs')" + "desc": "Unable to replay operation logs. Also, failed to drop NetBackup replay operation logs role. NetBackup status codes 818 NetBackup status codes", + "first_action": "Manually apply the operation log. Refer to the operation", + "full_action": "Manually apply the operation log. Refer to the operation\nlogs restored from mdbserver logs and restore these manually. Refer to MongoDB\nAdministrator’s Guide for the mongorestore command parameters.\nRun the following command to manually drop the role on the administrator user:\n\"db.getSiblingDB('admin').dropRole('netbackup-replayoplogs')" }, "6724": { "code": 6724, - "desc": "Restauração node count está inválido.", - "first_action": "Apenas one node can be restored in um replica set. If seu", - "full_action": "Apenas one node can be restored in um replica set. If seu\nbackup foi done from different nodes due to role changes, select todos o nodes to\nberestoredtoonesinglenodeonthedestinationMongoDBcluster.Usethealternate\nrestauração option in o restauração workflow." + "desc": "Restore node count is invalid.", + "first_action": "Only one node can be restored in a replica set. If your", + "full_action": "Only one node can be restored in a replica set. If your\nbackup was done from different nodes due to role changes, select all the nodes to\nberestoredtoonesinglenodeonthedestinationMongoDBcluster.Usethealternate\nrestore option in the restore workflow." }, "6725": { "code": 6725, - "desc": "Não foi possível to find informação about o MongoDB replica set.", - "first_action": "Refer to mdbserver logs para more details. Retry o", - "full_action": "Refer to mdbserver logs para more details. Retry o\noperation e if o issue persists, visit o Cohesity Technical Support website.\nO Cohesity Technical Support website offers additional informação to help you\ntroubleshoot this issue." + "desc": "Unable to find information about the MongoDB replica set.", + "first_action": "Refer to mdbserver logs for more details. Retry the", + "full_action": "Refer to mdbserver logs for more details. Retry the\noperation and if the issue persists, visit the Cohesity Technical Support website.\nThe Cohesity Technical Support website offers additional information to help you\ntroubleshoot this issue." }, "6726": { "code": 6726, - "desc": "Either o backup host que está selected como o destination cliente está inválido ou inaccessible, ou o requerido plug-in está não found on o cliente.", + "desc": "Either the backup host that is selected as the destination client is invalid or inaccessible, or the required plug-in is not found on the client.", "first_action": "Makesurethatthecorrectbackuphosthasbeenselected", - "full_action": "Makesurethatthecorrectbackuphosthasbeenselected\ncomo o destination. Also, make sure que o MongoDB plug-in está instalado on o\nbackup host e retry o operation." + "full_action": "Makesurethatthecorrectbackuphosthasbeenselected\nas the destination. Also, make sure that the MongoDB plug-in is installed on the\nbackup host and retry the operation." }, "6727": { "code": 6727, - "desc": "Falhou to transfer um arquivo to o remote host.", - "first_action": "Review o connectivity between o NetBackup cliente", - "full_action": "Review o connectivity between o NetBackup cliente\ne o MongoDB nodes. Refer to o nbapidiscv e nbaapire_handler logs\npara more details." + "desc": "Failed to transfer a file to the remote host.", + "first_action": "Review the connectivity between the NetBackup client", + "full_action": "Review the connectivity between the NetBackup client\nand the MongoDB nodes. Refer to the nbapidiscv and nbaapire_handler logs\nfor more details." }, "6728": { "code": 6728, - "desc": "Inválido backup host foi used in o policy.", + "desc": "Invalid backup host was used in the policy.", "first_action": "Updatethepolicytospecifythecorrectbackuphost.Verify", - "full_action": "Updatethepolicytospecifythecorrectbackuphost.Verify\nque o appropriate plug-in está instalado on o backup host e retry o backup\noperation." + "full_action": "Updatethepolicytospecifythecorrectbackuphost.Verify\nthat the appropriate plug-in is installed on the backup host and retry the backup\noperation." }, "6729": { "code": 6729, - "desc": "Não foi possível to download o thin cliente from o package repository.", - "first_action": "Garanta que you have added o MongoDB_tc package on", - "full_action": "Garanta que you have added o MongoDB_tc package on\no NetBackup master servidor. Refer to o MongoDB Administrator’s Guide to add\no thin cliente usando o nbrepo --add comando. Add o thin cliente package para\ntherelevantMongoDBnodeoperatingsystemoraddthethinclientsforbothRHEL\ne SUSE on seu master. Then retry o operation." + "desc": "Unable to download the thin client from the package repository.", + "first_action": "Ensure that you have added the MongoDB_tc package on", + "full_action": "Ensure that you have added the MongoDB_tc package on\nthe NetBackup master server. Refer to the MongoDB Administrator’s Guide to add\nthe thin client using the nbrepo --add command. Add the thin client package for\ntherelevantMongoDBnodeoperatingsystemoraddthethinclientsforbothRHEL\nand SUSE on your master. Then retry the operation." }, "6730": { "code": 6730, - "desc": "O selected schedule type está currently não supported para o sharded cluster que has Recurso Compatibility Version 4.2 ou later.", - "first_action": "If you run um incremental on Sharded MongoDB cluster", - "full_action": "If you run um incremental on Sharded MongoDB cluster\nwithversion4.2,refertotheMongoDBAdministrator’sGuidetochangetheFeature\nCompatibility Version de MongoDB to 4.0. Retry o operation com um cheio backup\nfollowed por incremental backup. If you do não desejar to change o Recurso\nCompatibility Version, change o schedule type to apenas do cheio backups de this\nMongoDB instance. Incremental backups estão não supported para um Sharded cluster\ncom MongoDB version 4.4 ou later." + "desc": "The selected schedule type is currently not supported for the sharded cluster that has Feature Compatibility Version 4.2 or later.", + "first_action": "If you run an incremental on Sharded MongoDB cluster", + "full_action": "If you run an incremental on Sharded MongoDB cluster\nwithversion4.2,refertotheMongoDBAdministrator’sGuidetochangetheFeature\nCompatibility Version of MongoDB to 4.0. Retry the operation with a full backup\nfollowed by incremental backup. If you do not want to change the Feature\nCompatibility Version, change the schedule type to only do full backups of this\nMongoDB instance. Incremental backups are not supported for a Sharded cluster\nwith MongoDB version 4.4 or later." }, "6731": { "code": 6731, - "desc": "Todos o requerido parameters para authentication type certificate-based estão não provided.", - "first_action": "Garanta que you have provided todos authentication details", - "full_action": "Garanta que you have provided todos authentication details\nin tpconfig para seu MongoDB cluster e que you provide todos o requerido\nparameters. Refer to o NetBackup para MongoDB Administrator’s Guide para more\ninformação on requerido parameters." + "desc": "All the required parameters for authentication type certificate-based are not provided.", + "first_action": "Ensure that you have provided all authentication details", + "full_action": "Ensure that you have provided all authentication details\nin tpconfig for your MongoDB cluster and that you provide all the required\nparameters. Refer to the NetBackup for MongoDB Administrator’s Guide for more\ninformation on required parameters." }, "6732": { "code": 6732, - "desc": "Garanta que you provide todos o requerido parameters.", - "first_action": "Garanta que you have provided todos authentication details", - "full_action": "Garanta que you have provided todos authentication details\nin tpconfig para seu MongoDB cluster. Refer to o NetBackup MongoDB\nAdministrator’s Guide para more informação on requerido parameters." + "desc": "Ensure that you provide all the required parameters.", + "first_action": "Ensure that you have provided all authentication details", + "full_action": "Ensure that you have provided all authentication details\nin tpconfig for your MongoDB cluster. Refer to the NetBackup MongoDB\nAdministrator’s Guide for more information on required parameters." }, "6733": { "code": 6733, - "desc": "NetBackup does não support protection de o given MongoDB cluster version.", - "first_action": "Refer to NetBackup Enterprise Servidor e Servidor OS", - "full_action": "Refer to NetBackup Enterprise Servidor e Servidor OS\nSoftware Compatibility List para seu NetBackup cliente version to find fora supported\nMongoDB version." + "desc": "NetBackup does not support protection of the given MongoDB cluster version.", + "first_action": "Refer to NetBackup Enterprise Server and Server OS", + "full_action": "Refer to NetBackup Enterprise Server and Server OS\nSoftware Compatibility List for your NetBackup client version to find out supported\nMongoDB version." }, "6734": { "code": 6734, - "desc": "Não foi possível to obtain o MongoDB version.", - "first_action": "Garanta que o MongoDB cluster está up e executando e", - "full_action": "Garanta que o MongoDB cluster está up e executando e\nretry o operation." + "desc": "Unable to obtain the MongoDB version.", + "first_action": "Ensure that the MongoDB cluster is up and running and", + "full_action": "Ensure that the MongoDB cluster is up and running and\nretry the operation." }, "6735": { "code": 6735, - "desc": "Não foi possível to obtain o Recurso Compatibility Version.", - "first_action": "Garanta que o MongoDB cluster está up e executando e", - "full_action": "Garanta que o MongoDB cluster está up e executando e\nretry o operation." + "desc": "Unable to obtain the Feature Compatibility Version.", + "first_action": "Ensure that the MongoDB cluster is up and running and", + "full_action": "Ensure that the MongoDB cluster is up and running and\nretry the operation." }, "6736": { "code": 6736, - "desc": "O source e o target cluster must have o same communication mode para certificate-based authentication. NetBackup status codes 822 NetBackup status codes", - "first_action": "Change o restauração cluster authentication type to match", - "full_action": "Change o restauração cluster authentication type to match\ncom o backup cluster authentication type e retry o restauração." + "desc": "The source and the target cluster must have the same communication mode for certificate-based authentication. NetBackup status codes 822 NetBackup status codes", + "first_action": "Change the restore cluster authentication type to match", + "full_action": "Change the restore cluster authentication type to match\nwith the backup cluster authentication type and retry the restore." }, "6737": { "code": 6737, - "desc": "Não foi possível to stop o balancer on o MongoDB cluster.", - "first_action": "Refer to mdbserver logs para more details. Refer to Mongo", - "full_action": "Refer to mdbserver logs para more details. Refer to Mongo\nlogs para more details about o falha. Retry o operation e if o issue persists,\nvisit o Cohesity Technical Support website. O Cohesity Technical Support\nwebsite offers additional informação to help you troubleshoot this issue." + "desc": "Unable to stop the balancer on the MongoDB cluster.", + "first_action": "Refer to mdbserver logs for more details. Refer to Mongo", + "full_action": "Refer to mdbserver logs for more details. Refer to Mongo\nlogs for more details about the failure. Retry the operation and if the issue persists,\nvisit the Cohesity Technical Support website. The Cohesity Technical Support\nwebsite offers additional information to help you troubleshoot this issue." }, "6738": { "code": 6738, - "desc": "Não foi possível to start o balancer on o MongoDB cluster.", - "first_action": "Refer to mdbserver logs para more details. Refer to Mongo", - "full_action": "Refer to mdbserver logs para more details. Refer to Mongo\nlogs para more details about o falha. Retry o operation e if o issue persists,\nvisit o Cohesity Technical Support website. O Cohesity Technical Support\nwebsite offers additional informação to help you troubleshoot this issue." + "desc": "Unable to start the balancer on the MongoDB cluster.", + "first_action": "Refer to mdbserver logs for more details. Refer to Mongo", + "full_action": "Refer to mdbserver logs for more details. Refer to Mongo\nlogs for more details about the failure. Retry the operation and if the issue persists,\nvisit the Cohesity Technical Support website. The Cohesity Technical Support\nwebsite offers additional information to help you troubleshoot this issue." }, "6739": { "code": 6739, - "desc": "O cluster está created usando o externally sourced configuration arquivo values. NetBackup currently does não support this MongoDB configuration.", - "first_action": "NetBackup doesn't support o externally sourced", - "full_action": "NetBackup doesn't support o externally sourced\nconfiguration arquivos. Por favor change o MongoDB configuration to use local\nconfiguration arquivos e retry o operation." + "desc": "The cluster is created using the externally sourced configuration file values. NetBackup currently does not support this MongoDB configuration.", + "first_action": "NetBackup doesn't support the externally sourced", + "full_action": "NetBackup doesn't support the externally sourced\nconfiguration files. Please change the MongoDB configuration to use local\nconfiguration files and retry the operation." }, "6740": { "code": 6740, - "desc": "Either o MongoDB Version ou o Recurso Compatibility Version de o MongoDB cluster has changed.", + "desc": "Either the MongoDB Version or the Feature Compatibility Version of the MongoDB cluster has changed.", "first_action": "Runafullbackupandthenanincrementalbackupshould", "full_action": "Runafullbackupandthenanincrementalbackupshould\nwork." }, "6741": { "code": 6741, - "desc": "O quota está excedido para volumes.", + "desc": "The quota is exceeded for volumes.", "first_action": "EnsurethattheOpenStackvolumequotais largeenough", - "full_action": "EnsurethattheOpenStackvolumequotais largeenough\nto accommodate o creation de new volumes que estão requerido during backup e\nou restauração operations." + "full_action": "EnsurethattheOpenStackvolumequotais largeenough\nto accommodate the creation of new volumes that are required during backup and\nor restore operations." }, "6742": { "code": 6742, - "desc": "O quota está excedido para instances.", + "desc": "The quota is exceeded for instances.", "first_action": "EnsurethattheOpenStackinstancequotaislargeenough", - "full_action": "EnsurethattheOpenStackinstancequotaislargeenough\nto accommodate o creation de new instance que está requerido during restauração\noperation." + "full_action": "EnsurethattheOpenStackinstancequotaislargeenough\nto accommodate the creation of new instance that is required during restore\noperation." }, "6743": { "code": 6743, - "desc": "Falhou to get o instance name. NetBackup status codes 824 NetBackup status codes", - "first_action": "Para o backup to succeed, garanta que o OpenStack", - "full_action": "Para o backup to succeed, garanta que o OpenStack\ninstance está present in o tenant ou o instance name está não blank." + "desc": "Failed to get the instance name. NetBackup status codes 824 NetBackup status codes", + "first_action": "For the backup to succeed, ensure that the OpenStack", + "full_action": "For the backup to succeed, ensure that the OpenStack\ninstance is present in the tenant or the instance name is not blank." }, "6744": { "code": 6744, - "desc": "O host name on o backup host está vazio.", - "first_action": "Verifique que o host name está properly configurado para o", - "full_action": "Verifique que o host name está properly configurado para o\nbackup host e make sure o /tmp folder de o backup host está mounted com\nexecution permissions." + "desc": "The host name on the backup host is empty.", + "first_action": "Verify that the host name is properly configured for the", + "full_action": "Verify that the host name is properly configured for the\nbackup host and make sure the /tmp folder of the backup host is mounted with\nexecution permissions." }, "6745": { "code": 6745, - "desc": "Falhou to conectar to MongoDB instance.", - "first_action": "Verifique que there está connectivity to o MongoDB instance.", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique que there está connectivity to o MongoDB instance.\n■ If o MongoDB instance target destination ou ALT_APPLICATION_SERVER está um\narbiter, change it to um non-arbiter MongoDB instance." + "desc": "Failed to connect to MongoDB instance.", + "first_action": "Verify that there is connectivity to the MongoDB instance.", + "full_action": "Perform the following as appropriate:\n■ Verify that there is connectivity to the MongoDB instance.\n■ If the MongoDB instance target destination or ALT_APPLICATION_SERVER is an\narbiter, change it to a non-arbiter MongoDB instance." }, "6746": { "code": 6746, - "desc": "Conexão não é possível be established because o backup host falhou to resolve o application servidor. NetBackup status codes 825 NetBackup status codes", - "first_action": "Garanta que you have entered o correct host name de o application servidor.", - "full_action": "Executar o seguinte como appropriate:\n■ Garanta que you have entered o correct host name de o application servidor.\n■ Trytopingthebackuphostfromtheapplicationserverandtheapplicationserver\nfrom o backup host." + "desc": "Connection cannot be established because the backup host failed to resolve the application server. NetBackup status codes 825 NetBackup status codes", + "first_action": "Ensure that you have entered the correct host name of the application server.", + "full_action": "Perform the following as appropriate:\n■ Ensure that you have entered the correct host name of the application server.\n■ Trytopingthebackuphostfromtheapplicationserverandtheapplicationserver\nfrom the backup host." }, "6747": { "code": 6747, "desc": "Thebackuphostcannotestablishaconnectiontotheapplicationserver.", - "first_action": "Garanta que you have provided o correct host name para o application servidor.", - "full_action": "Executar o seguinte como appropriate:\n■ Garanta que you have provided o correct host name para o application servidor.\n■ Trytopingthebackuphostfromtheapplicationserverandtheapplicationserver\nfrom o backup host.\n■ Garanta que o port está updated correctly usando tpconfig ou hadoop.conf." + "first_action": "Ensure that you have provided the correct host name for the application server.", + "full_action": "Perform the following as appropriate:\n■ Ensure that you have provided the correct host name for the application server.\n■ Trytopingthebackuphostfromtheapplicationserverandtheapplicationserver\nfrom the backup host.\n■ Ensure that the port is updated correctly using tpconfig or hadoop.conf." }, "6748": { "code": 6748, - "desc": "Um problema has ocorreu com o SSL ou o TLS communication.", - "first_action": "Garanta que o certificates que estão provided para o SSL", - "full_action": "Garanta que o certificates que estão provided para o SSL\nou o TLS communication have o correct arquivo format, caminho, e permissions." + "desc": "A problem has occurred with the SSL or the TLS communication.", + "first_action": "Ensure that the certificates that are provided for the SSL", + "full_action": "Ensure that the certificates that are provided for the SSL\nor the TLS communication have the correct file format, path, and permissions." }, "6749": { "code": 6749, - "desc": "Falhou in SSL ou TLS communication due to um inválido cliente certificate.", - "first_action": "Garanta que o certificate está accessible e que o", - "full_action": "Garanta que o certificate está accessible e que o\nspecified caminho está correct." + "desc": "Failed in SSL or TLS communication due to an invalid client certificate.", + "first_action": "Ensure that the certificate is accessible and that the", + "full_action": "Ensure that the certificate is accessible and that the\nspecified path is correct." }, "6750": { "code": 6750, - "desc": "Falhou to verifique o application servidor.", - "first_action": "Garanta que o certificates que estão provided para o SSL", - "full_action": "Garanta que o certificates que estão provided para o SSL\northeTLScommunicationhavethecorrectfileformat,path,andpermissions.Also,\nverifique que o certificate está não revoked." + "desc": "Failed to verify the application server.", + "first_action": "Ensure that the certificates that are provided for the SSL", + "full_action": "Ensure that the certificates that are provided for the SSL\northeTLScommunicationhavethecorrectfileformat,path,andpermissions.Also,\nverify that the certificate is not revoked." }, "6751": { "code": 6751, - "desc": "Falhou to ler o SSL CA certificate.", - "first_action": "Garanta que o certificates e o CRL arquivos estão in o", - "full_action": "Garanta que o certificates e o CRL arquivos estão in o\ncorrect format e que o trust store arquivo e o CRL arquivos estão não corrupted." + "desc": "Failed to read the SSL CA certificate.", + "first_action": "Ensure that the certificates and the CRL files are in the", + "full_action": "Ensure that the certificates and the CRL files are in the\ncorrect format and that the trust store file and the CRL files are not corrupted." }, "6752": { "code": 6752, - "desc": "Um unknown Certificate Authority issued o certificate.", - "first_action": "Obtain o CA certificate para o requerido servidor e rerun o operation.", - "full_action": "Executar o seguinte como appropriate:\n■ Obtain o CA certificate para o requerido servidor e rerun o operation.\n■ Retry o operation e save todos o erro log informação. If o issue persists,\nvisit support.veritas.com. O Cohesity Technical Support website offers\nadditional informação to help you troubleshoot this issue." + "desc": "An unknown Certificate Authority issued the certificate.", + "first_action": "Obtain the CA certificate for the required server and rerun the operation.", + "full_action": "Perform the following as appropriate:\n■ Obtain the CA certificate for the required server and rerun the operation.\n■ Retry the operation and save all the error log information. If the issue persists,\nvisit support.veritas.com. The Cohesity Technical Support website offers\nadditional information to help you troubleshoot this issue." }, "6753": { "code": 6753, - "desc": "Garanta que o application servidor clock e o backup host clocks estão synchronized.", + "desc": "Ensure that the application server clock and the backup host clocks are synchronized.", "first_action": "Checkifthebackuphost’sclockisinsyncwiththespecified", - "full_action": "Checkifthebackuphost’sclockisinsyncwiththespecified\napplicationserver.Ifnecessary,correctthetimeontheapplicationserverandrerun\no operation e save todos erro log informação. If o issue persists, visit\nsupport.veritas.com. O Cohesity Technical Support website offers additional\ninformação to help you troubleshoot this issue." + "full_action": "Checkifthebackuphost’sclockisinsyncwiththespecified\napplicationserver.Ifnecessary,correctthetimeontheapplicationserverandrerun\nthe operation and save all error log information. If the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support website offers additional\ninformation to help you troubleshoot this issue." }, "6754": { "code": 6754, - "desc": "O security certificate has expired.", + "desc": "The security certificate has expired.", "first_action": "Checkifthebackuphost’sclockisinsyncwiththespecified", - "full_action": "Checkifthebackuphost’sclockisinsyncwiththespecified\nApplication Servidor. If necessary, correct o time on o Application host e rerun\no operation e save todos erro log informação. If o issue persists, visit\nsupport.veritas.com. O Cohesity Technical Support website offers additional\ninformação to help you troubleshoot this issue." + "full_action": "Checkifthebackuphost’sclockisinsyncwiththespecified\nApplication Server. If necessary, correct the time on the Application host and rerun\nthe operation and save all error log information. If the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support website offers additional\ninformation to help you troubleshoot this issue." }, "6755": { "code": 6755, - "desc": "O certificate revocation list (CRL) está unavailable.", - "first_action": "O ECA_CRL_PATH has o correct certificate revocation list (CRL) diretório", - "full_action": "If o ECA_CRL_PATH setting está specified in o bp.conf\nconfiguration arquivo, garanta o seguinte:\n■ O ECA_CRL_PATH has o correct certificate revocation list (CRL) diretório\ncaminho.\n■ O CRL diretório contains CRLs para todos requerido certificate issuers.\n■ O CRL está in PEM format.\n■ O CRL has não expired.\n■ O CRL last update date está não um future date." + "desc": "The certificate revocation list (CRL) is unavailable.", + "first_action": "The ECA_CRL_PATH has the correct certificate revocation list (CRL) directory", + "full_action": "If the ECA_CRL_PATH setting is specified in the bp.conf\nconfiguration file, ensure the following:\n■ The ECA_CRL_PATH has the correct certificate revocation list (CRL) directory\npath.\n■ The CRL directory contains CRLs for all required certificate issuers.\n■ The CRL is in PEM format.\n■ The CRL has not expired.\n■ The CRL last update date is not a future date." }, "6756": { "code": 6756, - "desc": "O certificate revocation list (CRL) has expired.", - "first_action": "Provide o CRL que has não expired.", - "full_action": "Provide o CRL que has não expired." + "desc": "The certificate revocation list (CRL) has expired.", + "first_action": "Provide the CRL that has not expired.", + "full_action": "Provide the CRL that has not expired." }, "6757": { "code": 6757, - "desc": "O security certificate está revoked.", + "desc": "The security certificate is revoked.", "first_action": "Ensurethatthecertificatethatisprovidedfortheapplication", - "full_action": "Ensurethatthecertificatethatisprovidedfortheapplication\nservidor está não revoked. Also, if o certificate está não revoked e you still veja this\nerro, verifique if o certificate revocation list (CRL) está updated in o CRL cache." + "full_action": "Ensurethatthecertificatethatisprovidedfortheapplication\nserver is not revoked. Also, if the certificate is not revoked and you still see this\nerror, check if the certificate revocation list (CRL) is updated in the CRL cache." }, "6758": { "code": 6758, - "desc": "Não foi possível to decrypt o certificate revocation list (CRL) signature.", + "desc": "Unable to decrypt the certificate revocation list (CRL) signature.", "first_action": "Iftheverificationfails,refertotheOpenSSLdocumentsorcontactyourSecurity", - "full_action": "UsetheOpenSSLverifycommandtocheckthecertificate\ncom o CRL.\nExecutar o seguinte como appropriate:\n■ Iftheverificationfails,refertotheOpenSSLdocumentsorcontactyourSecurity\nAdministrator.\n■ Iftheverificationissuccessfulbuttheproblempersists,visitsupport.veritas.com.\nO Cohesity Technical Support website offers additional informação to help\nyou troubleshoot this issue." + "full_action": "UsetheOpenSSLverifycommandtocheckthecertificate\nwith the CRL.\nPerform the following as appropriate:\n■ Iftheverificationfails,refertotheOpenSSLdocumentsorcontactyourSecurity\nAdministrator.\n■ Iftheverificationissuccessfulbuttheproblempersists,visitsupport.veritas.com.\nThe Cohesity Technical Support website offers additional information to help\nyou troubleshoot this issue." }, "6759": { "code": 6759, - "desc": "Certificate revocation list (CRL) signature falha.", + "desc": "Certificate revocation list (CRL) signature failure.", "first_action": "Iftheverificationfails,refertotheOpenSSLdocumentsorcontactyourSecurity", - "full_action": "UsetheOpenSSLverifycommandtocheckthecertificate\ncom o CRL.\nExecutar o seguinte como appropriate:\n■ Iftheverificationfails,refertotheOpenSSLdocumentsorcontactyourSecurity\nAdministrator.\n■ Iftheverificationissuccessfulbuttheproblempersists,visitsupport.veritas.com.\nO Cohesity Technical Support website offers additional informação to help\nyou troubleshoot this issue." + "full_action": "UsetheOpenSSLverifycommandtocheckthecertificate\nwith the CRL.\nPerform the following as appropriate:\n■ Iftheverificationfails,refertotheOpenSSLdocumentsorcontactyourSecurity\nAdministrator.\n■ Iftheverificationissuccessfulbuttheproblempersists,visitsupport.veritas.com.\nThe Cohesity Technical Support website offers additional information to help\nyou troubleshoot this issue." }, "6760": { "code": 6760, - "desc": "O certificate revocation list (CRL) está não yet valid.", - "first_action": "Verifique seu system time ou provide um valid CRL.", - "full_action": "Verifique seu system time ou provide um valid CRL." + "desc": "The certificate revocation list (CRL) is not yet valid.", + "first_action": "Check your system time or provide a valid CRL.", + "full_action": "Check your system time or provide a valid CRL." }, "6761": { "code": 6761, - "desc": "O certificate revocation list (CRL) last update date está não in um valid format.", - "first_action": "Verifique o CRL usando o OpenSSL comando ou contate", - "full_action": "Verifique o CRL usando o OpenSSL comando ou contate\nseu Security Administrator." + "desc": "The certificate revocation list (CRL) last update date is not in a valid format.", + "first_action": "Check the CRL using the OpenSSL command or contact", + "full_action": "Check the CRL using the OpenSSL command or contact\nyour Security Administrator." }, "6762": { "code": 6762, - "desc": "O certificate revocation list (CRL) next update date está não in um valid format.", - "first_action": "Verifique o CRL usando o OpenSSL comando ou contate", - "full_action": "Verifique o CRL usando o OpenSSL comando ou contate\nseu Security Administrator." + "desc": "The certificate revocation list (CRL) next update date is not in a valid format.", + "first_action": "Check the CRL using the OpenSSL command or contact", + "full_action": "Check the CRL using the OpenSSL command or contact\nyour Security Administrator." }, "6763": { "code": 6763, - "desc": "Não foi possível to retrieve o certificate revocation list (CRL) issuer certificate.", + "desc": "Unable to retrieve the certificate revocation list (CRL) issuer certificate.", "first_action": "Iftheverificationfails,refertotheOpenSSLdocumentsorcontactyourSecurity", - "full_action": "UsetheOpenSSLverifycommandtocheckthecertificate\ncom o CRL.\nExecutar o seguinte como appropriate:\n■ Iftheverificationfails,refertotheOpenSSLdocumentsorcontactyourSecurity\nAdministrator.\n■ Iftheverificationissuccessfulbuttheproblempersists,visitsupport.veritas.com.\nO Cohesity Technical Support website offers additional informação to help\nyou troubleshoot this issue." + "full_action": "UsetheOpenSSLverifycommandtocheckthecertificate\nwith the CRL.\nPerform the following as appropriate:\n■ Iftheverificationfails,refertotheOpenSSLdocumentsorcontactyourSecurity\nAdministrator.\n■ Iftheverificationissuccessfulbuttheproblempersists,visitsupport.veritas.com.\nThe Cohesity Technical Support website offers additional information to help\nyou troubleshoot this issue." }, "6764": { "code": 6764, - "desc": "Key uso does não include certificate revocation list (CRL) signing.", + "desc": "Key usage does not include certificate revocation list (CRL) signing.", "first_action": "Iftheverificationfails,refertotheOpenSSLdocumentsorcontactyourSecurity", - "full_action": "UsetheOpenSSLverifycommandtocheckthecertificate\ncom o CRL.\nExecutar o seguinte como appropriate:\n■ Iftheverificationfails,refertotheOpenSSLdocumentsorcontactyourSecurity\nAdministrator.\n■ Iftheverificationissuccessfulbuttheproblempersists,visitsupport.veritas.com.\nO Cohesity Technical Support site offers additional informação to help you\ntroubleshoot this issue." + "full_action": "UsetheOpenSSLverifycommandtocheckthecertificate\nwith the CRL.\nPerform the following as appropriate:\n■ Iftheverificationfails,refertotheOpenSSLdocumentsorcontactyourSecurity\nAdministrator.\n■ Iftheverificationissuccessfulbuttheproblempersists,visitsupport.veritas.com.\nThe Cohesity Technical Support site offers additional information to help you\ntroubleshoot this issue." }, "6765": { "code": 6765, - "desc": "Critical certificate revocation list (CRL) contains inválido arquivo extensions.", - "first_action": "Verifique o CRL usando o OpenSSL comando ou contate", - "full_action": "Verifique o CRL usando o OpenSSL comando ou contate\nseu Security Administrator." + "desc": "Critical certificate revocation list (CRL) contains invalid file extensions.", + "first_action": "Check the CRL using the OpenSSL command or contact", + "full_action": "Check the CRL using the OpenSSL command or contact\nyour Security Administrator." }, "6766": { "code": 6766, - "desc": "O certificate revocation list (CRL) scope está different, it must cover todos revocation reasons.", - "first_action": "Verifique o CRL usando o OpenSSL comando ou contate", - "full_action": "Verifique o CRL usando o OpenSSL comando ou contate\nseu Security Administrator." + "desc": "The certificate revocation list (CRL) scope is different, it must cover all revocation reasons.", + "first_action": "Check the CRL using the OpenSSL command or contact", + "full_action": "Check the CRL using the OpenSSL command or contact\nyour Security Administrator." }, "6767": { "code": 6767, - "desc": "Certificate revocation list (CRL) caminho validation erro.", + "desc": "Certificate revocation list (CRL) path validation error.", "first_action": "Iftheverificationfails,refertotheOpenSSLdocumentsorcontactyourSecurity", - "full_action": "UsetheOpenSSLverifycommandtocheckthecertificate\ncom o CRL.\nExecutar o seguinte como appropriate:\n■ Iftheverificationfails,refertotheOpenSSLdocumentsorcontactyourSecurity\nAdministrator.\n■ Iftheverificationissuccessfulbuttheproblempersists,visitsupport.veritas.com.\nO Cohesity Technical Support website offers additional informação to help\nyou troubleshoot this issue." + "full_action": "UsetheOpenSSLverifycommandtocheckthecertificate\nwith the CRL.\nPerform the following as appropriate:\n■ Iftheverificationfails,refertotheOpenSSLdocumentsorcontactyourSecurity\nAdministrator.\n■ Iftheverificationissuccessfulbuttheproblempersists,visitsupport.veritas.com.\nThe Cohesity Technical Support website offers additional information to help\nyou troubleshoot this issue." }, "6768": { "code": 6768, - "desc": "Falhou to verifique o application servidor certificate.", + "desc": "Failed to verify the application server certificate.", "first_action": "Retrytheoperationandiftheissuepersists,saveallerror", - "full_action": "Retrytheoperationandiftheissuepersists,saveallerror\nlog informação e visit support.veritas.com. O Cohesity Technical Support\nwebsite offers additional informação to help you troubleshoot this issue." + "full_action": "Retrytheoperationandiftheissuepersists,saveallerror\nlog information and visit support.veritas.com. The Cohesity Technical Support\nwebsite offers additional information to help you troubleshoot this issue." }, "6772": { "code": 6772, - "desc": "Um unsupported protocol foi used to communicate com o application servidor.", + "desc": "An unsupported protocol was used to communicate with the application server.", "first_action": "ECA_TRUST_STORE_PATH", - "full_action": "Verifique o protocol que está used para communication com\no application servidor. If o application servidor uses HTTP, garanta que o port está\nupdated correctly usando tpconfig ou hadoop.conf.\nUpdate o seguinte arquivos in o bp.conf arquivo:\n■ ECA_TRUST_STORE_PATH\n■ ECA_CRL_PATH\n■ HADOOP_SECURE_CONNECT_ENABLED\n■ HADOOP_CRL_CHECK" + "full_action": "Check the protocol that is used for communication with\nthe application server. If the application server uses HTTP, ensure that the port is\nupdated correctly using tpconfig or hadoop.conf.\nUpdate the following files in the bp.conf file:\n■ ECA_TRUST_STORE_PATH\n■ ECA_CRL_PATH\n■ HADOOP_SECURE_CONNECT_ENABLED\n■ HADOOP_CRL_CHECK" }, "6773": { "code": 6773, - "desc": "Não foi possível to retrieve o issuer certificate.", + "desc": "Unable to retrieve the issuer certificate.", "first_action": "Ensurethatthecertificatesfileformats,paths,permissions,", - "full_action": "Ensurethatthecertificatesfileformats,paths,permissions,\ne passwords estão correct." + "full_action": "Ensurethatthecertificatesfileformats,paths,permissions,\nand passwords are correct." }, "6774": { "code": 6774, - "desc": "Um self-signed certificate não é possível be found in o list de trusted certificates.", + "desc": "A self-signed certificate cannot be found in the list of trusted certificates.", "first_action": "Ensurethatthecertificatesfileformats,paths,permissions,", - "full_action": "Ensurethatthecertificatesfileformats,paths,permissions,\ne passwords estão correct. Verifique if o host certificate contents estão part de o\ncertificate que está provided como ECA_TRUST_STORE_PATH." + "full_action": "Ensurethatthecertificatesfileformats,paths,permissions,\nand passwords are correct. Check if the host certificate contents are part of the\ncertificate that is provided as ECA_TRUST_STORE_PATH." }, "6775": { "code": 6775, - "desc": "Não foi possível to verifique o first certificate.", + "desc": "Unable to verify the first certificate.", "first_action": "Ensurethatthecertificatesfileformats,paths,permissions,", - "full_action": "Ensurethatthecertificatesfileformats,paths,permissions,\ne passwords estão correct." + "full_action": "Ensurethatthecertificatesfileformats,paths,permissions,\nand passwords are correct." }, "6776": { "code": 6776, - "desc": "CannotlocatetherequiredVxUpdatepackagefortheNetBackupversion de o backup host e o operating system de o MongoDB host.", - "first_action": "Garanta que you have added o requerido VxUpdate", - "full_action": "Garanta que you have added o requerido VxUpdate\npackage para o MongoDB thin cliente on o NetBackup master servidor. Refer to o\nMongoDB Administrator’s Guide to add o thin cliente usando o nbrepo --add\ncomando. Add o thin cliente package corresponding to o NetBackup version de\no backup host e o operating system de o MongoDB host. Then, retry o\noperation." + "desc": "CannotlocatetherequiredVxUpdatepackagefortheNetBackupversion of the backup host and the operating system of the MongoDB host.", + "first_action": "Ensure that you have added the required VxUpdate", + "full_action": "Ensure that you have added the required VxUpdate\npackage for the MongoDB thin client on the NetBackup master server. Refer to the\nMongoDB Administrator’s Guide to add the thin client using the nbrepo --add\ncommand. Add the thin client package corresponding to the NetBackup version of\nthe backup host and the operating system of the MongoDB host. Then, retry the\noperation." }, "6777": { "code": 6777, "desc": "Partialsuccess-failedtoparseaccessURIformanageddisksnapshot.", - "first_action": "Raise o verbose log level to 5 in o bp.conf arquivo on o backup host e", - "full_action": "Thiscodeisdisplayedduetoabackupjobthatwaspartially\nsuccessful.\nExecutar o seguinte como appropriate:\n■ Raise o verbose log level to 5 in o bp.conf arquivo on o backup host e\nmídia servidor e retry o operation. Review o nbaapidiscv e bpbkar\nlogs.\n■ Add CURL_VERBOSE = true into /usr/openv/var/global/azurestack.conf\nandretrytheoperation.ReviewthefailedRESTAPIrequestandresponsebody.\nPara more informação about granting access, refer to:\nhttps://docs.microsoft.com/en-us/rest/api/compute/disks/grantaccess" + "first_action": "Raise the verbose log level to 5 in the bp.conf file on the backup host and", + "full_action": "Thiscodeisdisplayedduetoabackupjobthatwaspartially\nsuccessful.\nPerform the following as appropriate:\n■ Raise the verbose log level to 5 in the bp.conf file on the backup host and\nmedia server and retry the operation. Review the nbaapidiscv and bpbkar\nlogs.\n■ Add CURL_VERBOSE = true into /usr/openv/var/global/azurestack.conf\nandretrytheoperation.ReviewthefailedRESTAPIrequestandresponsebody.\nFor more information about granting access, refer to:\nhttps://docs.microsoft.com/en-us/rest/api/compute/disks/grantaccess" }, "6778": { "code": 6778, - "desc": "Partial success - disco snapshot export falhou.", - "first_action": "Raise o verbose log level to 5 in o bp.conf arquivo on o backup host e", - "full_action": "Thiscodeisdisplayedduetoabackupjobthatwaspartially\nsuccessful.\nExecutar o seguinte como appropriate:\n■ Raise o verbose log level to 5 in o bp.conf arquivo on o backup host e\nmídia servidor e retry o operation. Review o nbaapidiscv e bpbkar\nlogs.\n■ Add CURL_VERBOSE = true into /usr/openv/var/global/azurestack.conf\nandretrytheoperation.ReviewthefailedRESTAPIrequestandresponsebody.\nPara more informação about granting access, refer to:\nhttps://docs.microsoft.com/en-us/rest/api/compute/disks/grantaccess" + "desc": "Partial success - disk snapshot export failed.", + "first_action": "Raise the verbose log level to 5 in the bp.conf file on the backup host and", + "full_action": "Thiscodeisdisplayedduetoabackupjobthatwaspartially\nsuccessful.\nPerform the following as appropriate:\n■ Raise the verbose log level to 5 in the bp.conf file on the backup host and\nmedia server and retry the operation. Review the nbaapidiscv and bpbkar\nlogs.\n■ Add CURL_VERBOSE = true into /usr/openv/var/global/azurestack.conf\nandretrytheoperation.ReviewthefailedRESTAPIrequestandresponsebody.\nFor more information about granting access, refer to:\nhttps://docs.microsoft.com/en-us/rest/api/compute/disks/grantaccess" }, "6779": { "code": 6779, - "desc": "Partial success - o disco snapshot cancel export falhou.", - "first_action": "Raise o verbose log level to 5 in o bp.conf arquivo on o backup host e", - "full_action": "Thiscodeisdisplayedduetoabackupjobthatwaspartially\nsuccessful.\nExecutar o seguinte como appropriate:\n■ Raise o verbose log level to 5 in o bp.conf arquivo on o backup host e\nmídia servidor e retry o operation. Review o nbaapidiscv e bpbkar\nlogs.\n■ Add CURL_VERBOSE = true into /usr/openv/var/global/azurestack.conf\nandretrytheoperation.ReviewthefailedRESTAPIrequestandresponsebody.\nPara more informação about revoking access to um disco, refer to:\nhttps://docs.microsoft.com/en-us/rest/api/compute/disks/revokeaccess" + "desc": "Partial success - the disk snapshot cancel export failed.", + "first_action": "Raise the verbose log level to 5 in the bp.conf file on the backup host and", + "full_action": "Thiscodeisdisplayedduetoabackupjobthatwaspartially\nsuccessful.\nPerform the following as appropriate:\n■ Raise the verbose log level to 5 in the bp.conf file on the backup host and\nmedia server and retry the operation. Review the nbaapidiscv and bpbkar\nlogs.\n■ Add CURL_VERBOSE = true into /usr/openv/var/global/azurestack.conf\nandretrytheoperation.ReviewthefailedRESTAPIrequestandresponsebody.\nFor more information about revoking access to a disk, refer to:\nhttps://docs.microsoft.com/en-us/rest/api/compute/disks/revokeaccess" }, "6780": { "code": 6780, - "desc": "Partial success - falhou to excluir o managed disco snapshot.", - "first_action": "Raise o verbose log level to 5 in o bp.conf arquivo on o backup host e", - "full_action": "Thiscodeisdisplayedduetoabackupjobthatwaspartially\nsuccessful.\nExecutar o seguinte como appropriate:\n■ Raise o verbose log level to 5 in o bp.conf arquivo on o backup host e\nmídia servidor e retry o operation. Review o nbaapidiscv e bpbkar\nlogs.\n■ Add CURL_VERBOSE = true into /usr/openv/var/global/azurestack.conf\nandretrytheoperation.ReviewthefailedRESTAPIrequestandresponsebody.\nPara more informação about deleting snapshots, refer to:\nhttps://docs.microsoft.com/en-us/rest/api/compute/snapshots/delete" + "desc": "Partial success - failed to delete the managed disk snapshot.", + "first_action": "Raise the verbose log level to 5 in the bp.conf file on the backup host and", + "full_action": "Thiscodeisdisplayedduetoabackupjobthatwaspartially\nsuccessful.\nPerform the following as appropriate:\n■ Raise the verbose log level to 5 in the bp.conf file on the backup host and\nmedia server and retry the operation. Review the nbaapidiscv and bpbkar\nlogs.\n■ Add CURL_VERBOSE = true into /usr/openv/var/global/azurestack.conf\nandretrytheoperation.ReviewthefailedRESTAPIrequestandresponsebody.\nFor more information about deleting snapshots, refer to:\nhttps://docs.microsoft.com/en-us/rest/api/compute/snapshots/delete" }, "6781": { "code": 6781, - "desc": "Partial success - inválido access URI returned when disco snapshot foi exported.", - "first_action": "Raise o verbose log level to 5 in o bp.conf arquivo on o backup host e", - "full_action": "Thiscodeisdisplayedduetoabackupjobthatwaspartially\nsuccessful.\nExecutar o seguinte como appropriate:\n■ Raise o verbose log level to 5 in o bp.conf arquivo on o backup host e\nmídia servidor e retry o operation. Review o nbaapidiscv e bpbkar\nlogs.\n■ Add CURL_VERBOSE = true into /usr/openv/var/global/azurestack.conf\nandretrytheoperation.ReviewthefailedRESTAPIrequestandresponsebody." + "desc": "Partial success - invalid access URI returned when disk snapshot was exported.", + "first_action": "Raise the verbose log level to 5 in the bp.conf file on the backup host and", + "full_action": "Thiscodeisdisplayedduetoabackupjobthatwaspartially\nsuccessful.\nPerform the following as appropriate:\n■ Raise the verbose log level to 5 in the bp.conf file on the backup host and\nmedia server and retry the operation. Review the nbaapidiscv and bpbkar\nlogs.\n■ Add CURL_VERBOSE = true into /usr/openv/var/global/azurestack.conf\nandretrytheoperation.ReviewthefailedRESTAPIrequestandresponsebody." }, "6782": { "code": 6782, - "desc": "Partial success - o abrir object para disco operation falhou.", - "first_action": "Raise o verbose log level to 5 in o bp.conf arquivo on o backup host e", - "full_action": "Thiscodeisdisplayedduetoabackupjobthatwaspartially\nsuccessful.\nExecutar o seguinte como appropriate:\n■ Raise o verbose log level to 5 in o bp.conf arquivo on o backup host e\nmídia servidor e retry o operation. Review o nbaapidiscv e bpbkar\nlogs.\n■ Add CURL_VERBOSE = true into /usr/openv/var/global/azurestack.conf\nandretrytheoperation.ReviewthefailedRESTAPIrequestandresponsebody." + "desc": "Partial success - the open object for disk operation failed.", + "first_action": "Raise the verbose log level to 5 in the bp.conf file on the backup host and", + "full_action": "Thiscodeisdisplayedduetoabackupjobthatwaspartially\nsuccessful.\nPerform the following as appropriate:\n■ Raise the verbose log level to 5 in the bp.conf file on the backup host and\nmedia server and retry the operation. Review the nbaapidiscv and bpbkar\nlogs.\n■ Add CURL_VERBOSE = true into /usr/openv/var/global/azurestack.conf\nandretrytheoperation.ReviewthefailedRESTAPIrequestandresponsebody." }, "6783": { "code": 6783, - "desc": "Partial success - Falhou to obtain o disco snapshot blob.", - "first_action": "Raise o verbose log level to 5 in o bp.conf arquivo on o backup host e", - "full_action": "Thiscodeisdisplayedduetoabackupjobthatwaspartially\nsuccessful.\nExecutar o seguinte como appropriate:\n■ Raise o verbose log level to 5 in o bp.conf arquivo on o backup host e\nmídia servidor e retry o operation. Review o nbaapidiscv e bpbkar\nlogs.\n■ Add CURL_VERBOSE = true into /usr/openv/var/global/azurestack.conf\nandretrytheoperation.ReviewthefailedRESTAPIrequestandresponsebody.\nPara more informação about o Get Blob operation, refer to:\nhttps://docs.microsoft.com/en-us/rest/api/storageservices/get-blob" + "desc": "Partial success - Failed to obtain the disk snapshot blob.", + "first_action": "Raise the verbose log level to 5 in the bp.conf file on the backup host and", + "full_action": "Thiscodeisdisplayedduetoabackupjobthatwaspartially\nsuccessful.\nPerform the following as appropriate:\n■ Raise the verbose log level to 5 in the bp.conf file on the backup host and\nmedia server and retry the operation. Review the nbaapidiscv and bpbkar\nlogs.\n■ Add CURL_VERBOSE = true into /usr/openv/var/global/azurestack.conf\nandretrytheoperation.ReviewthefailedRESTAPIrequestandresponsebody.\nFor more information about the Get Blob operation, refer to:\nhttps://docs.microsoft.com/en-us/rest/api/storageservices/get-blob" }, "6784": { "code": 6784, - "desc": "O asynchronous operation returned um unknown falha.", - "first_action": "Azure-AsyncOperation - O URL para checking o ongoing status de o", - "full_action": "If um asynchronous operation fails ou returns um canceled\nerro como part if o HTTP response, then o backup operation retries.\nYou can monitor o status de o asynchronous operation in two different ways.\nYou can determinar o correct approach to help you correct o issue por examining\no header values que estão returned from seu original request. Primarily, look para:\n■ Azure-AsyncOperation - O URL para checking o ongoing status de o\noperation. If seu operation returns this value, use it to track o status de o\noperation.\n■ Retry-After - O number de seconds to wait before o status de o\nasynchronous operation está checked.\nPara more informação about asynchronous operations, refer to:\nhttps://docs.microsoft.com/en-us/azure/azure-resource-manager/management/async-operations" + "desc": "The asynchronous operation returned an unknown failure.", + "first_action": "Azure-AsyncOperation - The URL for checking the ongoing status of the", + "full_action": "If an asynchronous operation fails or returns a canceled\nerror as part if the HTTP response, then the backup operation retries.\nYou can monitor the status of the asynchronous operation in two different ways.\nYou can determine the correct approach to help you correct the issue by examining\nthe header values that are returned from your original request. Primarily, look for:\n■ Azure-AsyncOperation - The URL for checking the ongoing status of the\noperation. If your operation returns this value, use it to track the status of the\noperation.\n■ Retry-After - The number of seconds to wait before the status of the\nasynchronous operation is checked.\nFor more information about asynchronous operations, refer to:\nhttps://docs.microsoft.com/en-us/azure/azure-resource-manager/management/async-operations" }, "6785": { "code": 6785, - "desc": "O asynchronous operation está in progress.", - "first_action": "Azure-AsyncOperation - O URL para checking o ongoing status de o", - "full_action": "If um asynchronous operation fails ou returns um canceled\nerro como part if o HTTP response, then o backup operation retries.\nYou can monitor o status de o asynchronous operation in two different ways.\nYou can determinar o correct approach to help you correct o issue por examining\no header values que estão returned from seu original request. Primarily, look para:\n■ Azure-AsyncOperation - O URL para checking o ongoing status de o\noperation. If seu operation returns this value, use it to track o status de o\noperation.\n■ Retry-After - O number de seconds to wait before o status de o\nasynchronous operation está checked.\nPara more informação about asynchronous operations, refer to:\nhttps://docs.microsoft.com/en-us/azure/azure-resource-manager/management/async-operations" + "desc": "The asynchronous operation is in progress.", + "first_action": "Azure-AsyncOperation - The URL for checking the ongoing status of the", + "full_action": "If an asynchronous operation fails or returns a canceled\nerror as part if the HTTP response, then the backup operation retries.\nYou can monitor the status of the asynchronous operation in two different ways.\nYou can determine the correct approach to help you correct the issue by examining\nthe header values that are returned from your original request. Primarily, look for:\n■ Azure-AsyncOperation - The URL for checking the ongoing status of the\noperation. If your operation returns this value, use it to track the status of the\noperation.\n■ Retry-After - The number of seconds to wait before the status of the\nasynchronous operation is checked.\nFor more information about asynchronous operations, refer to:\nhttps://docs.microsoft.com/en-us/azure/azure-resource-manager/management/async-operations" }, "6786": { "code": 6786, - "desc": "O asynchronous operation falhou.", - "first_action": "Azure-AsyncOperation - O URL para checking o ongoing status de o", - "full_action": "If um asynchronous operation fails ou returns um canceled\nerro como part if o HTTP response, then o backup operation retries.\nYou can monitor o status de o asynchronous operation in two different ways.\nYou can determinar o correct approach to help you correct o issue por examining\no header values que estão returned from seu original request. Primarily, look para:\n■ Azure-AsyncOperation - O URL para checking o ongoing status de o\noperation. If seu operation returns this value, use it to track o status de o\noperation.\n■ Retry-After - O number de seconds to wait before o status de o\nasynchronous operation está checked.\nPara more informação about asynchronous operations, refer to:\nhttps://docs.microsoft.com/en-us/azure/azure-resource-manager/management/async-operations" + "desc": "The asynchronous operation failed.", + "first_action": "Azure-AsyncOperation - The URL for checking the ongoing status of the", + "full_action": "If an asynchronous operation fails or returns a canceled\nerror as part if the HTTP response, then the backup operation retries.\nYou can monitor the status of the asynchronous operation in two different ways.\nYou can determine the correct approach to help you correct the issue by examining\nthe header values that are returned from your original request. Primarily, look for:\n■ Azure-AsyncOperation - The URL for checking the ongoing status of the\noperation. If your operation returns this value, use it to track the status of the\noperation.\n■ Retry-After - The number of seconds to wait before the status of the\nasynchronous operation is checked.\nFor more information about asynchronous operations, refer to:\nhttps://docs.microsoft.com/en-us/azure/azure-resource-manager/management/async-operations" }, "6787": { "code": 6787, - "desc": "O asynchronous operation foi canceled.", - "first_action": "Azure-AsyncOperation - O URL para checking o ongoing status de o", - "full_action": "If um asynchronous operation fails ou returns um canceled\nerro como part if o HTTP response, then o backup operation retries.\nYou can monitor o status de o asynchronous operation in two different ways.\nYou can determinar o correct approach to help you correct o issue por examining\no header values que estão returned from seu original request. Primarily, look para:\n■ Azure-AsyncOperation - O URL para checking o ongoing status de o\noperation. If seu operation returns this value, use it to track o status de o\noperation.\n■ Retry-After - O number de seconds to wait before o status de o\nasynchronous operation está checked.\nPara more informação about asynchronous operations, refer to:\nhttps://docs.microsoft.com/en-us/azure/azure-resource-manager/management/async-operations" + "desc": "The asynchronous operation was canceled.", + "first_action": "Azure-AsyncOperation - The URL for checking the ongoing status of the", + "full_action": "If an asynchronous operation fails or returns a canceled\nerror as part if the HTTP response, then the backup operation retries.\nYou can monitor the status of the asynchronous operation in two different ways.\nYou can determine the correct approach to help you correct the issue by examining\nthe header values that are returned from your original request. Primarily, look for:\n■ Azure-AsyncOperation - The URL for checking the ongoing status of the\noperation. If your operation returns this value, use it to track the status of the\noperation.\n■ Retry-After - The number of seconds to wait before the status of the\nasynchronous operation is checked.\nFor more information about asynchronous operations, refer to:\nhttps://docs.microsoft.com/en-us/azure/azure-resource-manager/management/async-operations" }, "6788": { "code": 6788, - "desc": "O asynchronous operation returned um unknown erro.", - "first_action": "Azure-AsyncOperation - O URL para checking o ongoing status de o", - "full_action": "If um asynchronous operation fails ou returns um canceled\nerro como part if o HTTP response, then o backup operation retries.\nYou can monitor o status de o asynchronous operation in two different ways.\nYou can determinar o correct approach to help you correct o issue por examining\no header values que estão returned from seu original request. Primarily, look para:\n■ Azure-AsyncOperation - O URL para checking o ongoing status de o\noperation. If seu operation returns this value, use it to track o status de o\noperation.\n■ Retry-After - O number de seconds to wait before o status de o\nasynchronous operation está checked.\nPara more informação about asynchronous operations, refer to:\nhttps://docs.microsoft.com/en-us/azure/azure-resource-manager/management/async-operations" + "desc": "The asynchronous operation returned an unknown error.", + "first_action": "Azure-AsyncOperation - The URL for checking the ongoing status of the", + "full_action": "If an asynchronous operation fails or returns a canceled\nerror as part if the HTTP response, then the backup operation retries.\nYou can monitor the status of the asynchronous operation in two different ways.\nYou can determine the correct approach to help you correct the issue by examining\nthe header values that are returned from your original request. Primarily, look for:\n■ Azure-AsyncOperation - The URL for checking the ongoing status of the\noperation. If your operation returns this value, use it to track the status of the\noperation.\n■ Retry-After - The number of seconds to wait before the status of the\nasynchronous operation is checked.\nFor more information about asynchronous operations, refer to:\nhttps://docs.microsoft.com/en-us/azure/azure-resource-manager/management/async-operations" }, "6789": { "code": 6789, - "desc": "O configuration está inválido para o specified resource.", - "first_action": "Executar um restauração to o original location usando o Restauração everything to it", - "full_action": "Review o tar log arquivo para o exact erro message e como\nper o restauração location.\nTry one de o seguinte como appropriate:\n■ Executar um restauração to o original location usando o Restauração everything to it\noriginal location option.\n■ Verifique que o configuration during o backup operation de o VM que está\nspecified in o erro message está disponível on Azure Stack.\n■ PerformanalternatelocationrestoreusingtheRestoreeverythingtoadifferent\nlocation (maintaining existing structure) option.\n■ Specify o valid armazenamento account type value in o managed disco rename\nentry. This step está requerido apenas in managed disco VM restores.\n■ Specify o disco resource group name que está configurado in o subscription\nID on Azure Stack onde you desejar to restauração. Add this informação in o\nmanaged disco rename entry. This step está requerido apenas in managed disco VM\nrestores.\n■ Specify o correct value de o subscription ID que está configurado on Azure\nStack onde you desejar to restauração para subscription ID rename entry.\n■ Para o RgName rename entry, specify o resource group name que está\nconfiguredforthesubscriptionIDonAzureStackwhereyouwanttorestore.\n■ Para o Nsg rename entry, specify o rede security group que está\nconfiguredforthesubscriptionIDonAzureStackwhereyouwanttorestore.\nIf o resource group para o rede security group está different from o VM\nresource group, it needs to be specified in o Nsg rename entry como:\nNsg=/\n■ Para o Vnet rename entry, specify o virtual rede que está configurado para\nthesubscriptionIDonAzureStackwhereyouwanttorestore.Iftheresource\ngroup para Vnet está different from o VM resource group, it needs to be\nspecified in o Vnet rename entry como:\nVnet=/" + "desc": "The configuration is invalid for the specified resource.", + "first_action": "Perform a restore to the original location using the Restore everything to it", + "full_action": "Review the tar log file for the exact error message and as\nper the restore location.\nTry one of the following as appropriate:\n■ Perform a restore to the original location using the Restore everything to it\noriginal location option.\n■ Verify that the configuration during the backup operation of the VM that is\nspecified in the error message is available on Azure Stack.\n■ PerformanalternatelocationrestoreusingtheRestoreeverythingtoadifferent\nlocation (maintaining existing structure) option.\n■ Specify the valid storage account type value in the managed disk rename\nentry. This step is required only in managed disk VM restores.\n■ Specify the disk resource group name that is configured in the subscription\nID on Azure Stack where you want to restore. Add this information in the\nmanaged disk rename entry. This step is required only in managed disk VM\nrestores.\n■ Specify the correct value of the subscription ID that is configured on Azure\nStack where you want to restore for subscription ID rename entry.\n■ For the RgName rename entry, specify the resource group name that is\nconfiguredforthesubscriptionIDonAzureStackwhereyouwanttorestore.\n■ For the Nsg rename entry, specify the network security group that is\nconfiguredforthesubscriptionIDonAzureStackwhereyouwanttorestore.\nIf the resource group for the network security group is different from the VM\nresource group, it needs to be specified in the Nsg rename entry as:\nNsg=/\n■ For the Vnet rename entry, specify the virtual network that is configured for\nthesubscriptionIDonAzureStackwhereyouwanttorestore.Iftheresource\ngroup for Vnet is different from the VM resource group, it needs to be\nspecified in the Vnet rename entry as:\nVnet=/" }, "6791": { "code": 6791, - "desc": "Falhou to create o disco.", + "desc": "Failed to create the disk.", "first_action": "WhenperformingarestoreusingtheRestoreeverything", - "full_action": "WhenperformingarestoreusingtheRestoreeverything\nto um different location (maintaining existing structure) option, review o HTTP\nresponse ou log message in o tar log arquivo." + "full_action": "WhenperformingarestoreusingtheRestoreeverything\nto a different location (maintaining existing structure) option, review the HTTP\nresponse or log message in the tar log file." }, "6792": { "code": 6792, - "desc": "Não foi possível to find um armazenamento account. NetBackup status codes 842 NetBackup status codes", - "first_action": "Executar um restauração to o original location usando o Restauração everything to it", - "full_action": "Review o tar log arquivo para o exact erro message para o\nrestauração location.\nTry one de o seguinte como appropriate:\n■ Executar um restauração to o original location usando o Restauração everything to it\noriginal location option.\n■ Verifique que o armazenamento account que está specified during o backup de o VM\nestá disponível during o restauração de respective unmanaged e managed VM\nrestauração.\n■ If you restauração um managed disco VM, you need to specify o staging armazenamento\naccount exists in o original restauração location on o azurestack in o\nazurestack.conf arquivo.\n■ PerformanalternatelocationrestoreusingtheRestoreeverythingtoadifferent\nlocation (maintaining existing structure) option.\n■ Para managed disco VM restores, specify o configurado staging armazenamento\naccountinthesubscriptionIDwhereyouwanttemporaryVHDtobecreated\non Azure Stack. Use either o rename arquivo ou o azurestack.conf arquivo.\n■ Para unmanaged disco VM restores, specify o configurado armazenamento account\nin o subscription ID onde you desejar to restauração on Azure Stack. Use o\nrename arquivo para VHD blob rename entry.\n■ VerifythattheHTTPoptionisenabledonthestorageaccountthatisspecified\npara o managed e unmanaged VM restores." + "desc": "Unable to find a storage account. NetBackup status codes 842 NetBackup status codes", + "first_action": "Perform a restore to the original location using the Restore everything to it", + "full_action": "Review the tar log file for the exact error message for the\nrestore location.\nTry one of the following as appropriate:\n■ Perform a restore to the original location using the Restore everything to it\noriginal location option.\n■ Verify that the storage account that is specified during the backup of the VM\nis available during the restore of respective unmanaged and managed VM\nrestore.\n■ If you restore a managed disk VM, you need to specify the staging storage\naccount exists in the original restore location on the azurestack in the\nazurestack.conf file.\n■ PerformanalternatelocationrestoreusingtheRestoreeverythingtoadifferent\nlocation (maintaining existing structure) option.\n■ For managed disk VM restores, specify the configured staging storage\naccountinthesubscriptionIDwhereyouwanttemporaryVHDtobecreated\non Azure Stack. Use either the rename file or the azurestack.conf file.\n■ For unmanaged disk VM restores, specify the configured storage account\nin the subscription ID where you want to restore on Azure Stack. Use the\nrename file for VHD blob rename entry.\n■ VerifythattheHTTPoptionisenabledonthestorageaccountthatisspecified\nfor the managed and unmanaged VM restores." }, "6793": { "code": 6793, - "desc": "Falhou to recover o VM.", + "desc": "Failed to recover the VM.", "first_action": "Reviewthetarlogfilefortheexacterrormessage.Review", - "full_action": "Reviewthetarlogfilefortheexacterrormessage.Review\no HTTP response message, in o tar log arquivo, para exact erro reason." + "full_action": "Reviewthetarlogfilefortheexacterrormessage.Review\nthe HTTP response message, in the tar log file, for exact error reason." }, "6794": { "code": 6794, - "desc": "Falhou to create o resource.", - "first_action": "Executar um restauração to o original location usando o Restauração everything to it", - "full_action": "Review o tar log arquivo para o exact erro message para o\nrestauração location.\nTry one de o seguinte como appropriate:\n■ Executar um restauração to o original location usando o Restauração everything to it\noriginal location option.\n■ Verifique que todos o configurado resources que estão specified during o backup\nde o VM estão disponível during o restauração operation.\n■ Verifique que operation quota está sufficient on o Azure Stack. O quota must\nbe sufficient to create um public IP address if o public IP address option está\nselected at restauração time.\n■ PerformanalternatelocationrestoreusingtheRestoreeverythingtoadifferent\nlocation (maintaining existing structure) option.\n■ In o Vnet rename entry, specify o virtual rede que está configurado para\no subscription ID on Azure Stack onde you desejar to restauração.\n■ IntheNsgrenameentry,specifythenetworksecuritygroupthatisconfigured\npara o subscription ID on Azure Stack onde you desejar to restauração.\n■ In o subnet rename entry, specify o subnet que está configurado para o\nsubscription ID on Azure Stack onde you desejar to restauração." + "desc": "Failed to create the resource.", + "first_action": "Perform a restore to the original location using the Restore everything to it", + "full_action": "Review the tar log file for the exact error message for the\nrestore location.\nTry one of the following as appropriate:\n■ Perform a restore to the original location using the Restore everything to it\noriginal location option.\n■ Verify that all the configured resources that are specified during the backup\nof the VM are available during the restore operation.\n■ Verify that operation quota is sufficient on the Azure Stack. The quota must\nbe sufficient to create a public IP address if the public IP address option is\nselected at restore time.\n■ PerformanalternatelocationrestoreusingtheRestoreeverythingtoadifferent\nlocation (maintaining existing structure) option.\n■ In the Vnet rename entry, specify the virtual network that is configured for\nthe subscription ID on Azure Stack where you want to restore.\n■ IntheNsgrenameentry,specifythenetworksecuritygroupthatisconfigured\nfor the subscription ID on Azure Stack where you want to restore.\n■ In the subnet rename entry, specify the subnet that is configured for the\nsubscription ID on Azure Stack where you want to restore." }, "6795": { "code": 6795, - "desc": "Um inválido backup selection está specified in o policy. NetBackup status codes 844 NetBackup status codes", - "first_action": "Create um policy usando um intelligent group com supported", - "full_action": "Create um policy usando um intelligent group com supported\nassets ou manually adding supported assets in o policy." + "desc": "An invalid backup selection is specified in the policy. NetBackup status codes 844 NetBackup status codes", + "first_action": "Create a policy using an intelligent group with supported", + "full_action": "Create a policy using an intelligent group with supported\nassets or manually adding supported assets in the policy." }, "6797": { "code": 6797, - "desc": "Não foi possível to find o resource.", - "first_action": "Executar um alternate location restauração usando o Restauração", - "full_action": "Executar um alternate location restauração usando o Restauração\neverything to um different location (maintaining existing structure) option.\nAfter you executar o restauração, review o tar log arquivo para o exact erro message.\nVerifique que o virtual rede, rede security group, ou o subnet está configurado\non Azure Stack para o target subscription ID location para o restauração operation." + "desc": "Unable to find the resource.", + "first_action": "Perform an alternate location restore using the Restore", + "full_action": "Perform an alternate location restore using the Restore\neverything to a different location (maintaining existing structure) option.\nAfter you perform the restore, review the tar log file for the exact error message.\nVerify that the virtual network, network security group, or the subnet is configured\non Azure Stack for the target subscription ID location for the restore operation." }, "6798": { "code": 6798, - "desc": "Não foi possível to find um disponível port on MongoDB host para o thin cliente.", - "first_action": "Verifique que o port range que está specified in o mongodb.conf arquivo ou tpconfig", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique que o port range que está specified in o mongodb.conf arquivo ou tpconfig\nglobal settings está disponível on o MongoDB host. O port range está set usando\no mdbserver_port e mdbserver_port_range settings.\n■ Aumentar o port number range por adjusting o setting to um higher value para\nmdbserver_port_range if you have:\n■ Parallel NetBackup backup ou restauração operations executando on this host.\n■ Multiple MongoDB instances executando on this host." + "desc": "Unable to find an available port on MongoDB host for the thin client.", + "first_action": "Verify that the port range that is specified in the mongodb.conf file or tpconfig", + "full_action": "Perform the following as appropriate:\n■ Verify that the port range that is specified in the mongodb.conf file or tpconfig\nglobal settings is available on the MongoDB host. The port range is set using\nthe mdbserver_port and mdbserver_port_range settings.\n■ Increase the port number range by adjusting the setting to a higher value for\nmdbserver_port_range if you have:\n■ Parallel NetBackup backup or restore operations running on this host.\n■ Multiple MongoDB instances running on this host." }, "6800": { "code": 6800, "desc": "NewNetBackupCAofthegivenkeysizecannotbesetupformigration.", - "first_action": "Garanta que todos NetBackup services estão up e retry o", - "full_action": "Garanta que todos NetBackup services estão up e retry o\noperationaftersometime.Iftheissuepersists,visittheCohesityTechnicalSupport\nwebsite. O Cohesity Technical Support website offers additional informação to\nhelp you troubleshoot this issue." + "first_action": "Ensure that all NetBackup services are up and retry the", + "full_action": "Ensure that all NetBackup services are up and retry the\noperationaftersometime.Iftheissuepersists,visittheCohesityTechnicalSupport\nwebsite. The Cohesity Technical Support website offers additional information to\nhelp you troubleshoot this issue." }, "6801": { "code": 6801, "desc": "TheNetBackupCAthatisnewlysetupformigrationcannotbeactivated.", - "first_action": "Garanta que todos NetBackup services estão up e retry o", - "full_action": "Garanta que todos NetBackup services estão up e retry o\noperationaftersometime.Iftheissuepersists,visittheCohesityTechnicalSupport\nwebsite. O Cohesity Technical Support website offers additional informação to\nhelp you troubleshoot this issue." + "first_action": "Ensure that all NetBackup services are up and retry the", + "full_action": "Ensure that all NetBackup services are up and retry the\noperationaftersometime.Iftheissuepersists,visittheCohesityTechnicalSupport\nwebsite. The Cohesity Technical Support website offers additional information to\nhelp you troubleshoot this issue." }, "6802": { "code": 6802, - "desc": "O migration de NetBackup CA não é possível be completed.", - "first_action": "Garanta que todos NetBackup services estão up e retry o", - "full_action": "Garanta que todos NetBackup services estão up e retry o\noperationaftersometime.Iftheissuepersists,visittheCohesityTechnicalSupport\nwebsite. O Cohesity Technical Support website offers additional informação to\nhelp you troubleshoot this issue." + "desc": "The migration of NetBackup CA cannot be completed.", + "first_action": "Ensure that all NetBackup services are up and retry the", + "full_action": "Ensure that all NetBackup services are up and retry the\noperationaftersometime.Iftheissuepersists,visittheCohesityTechnicalSupport\nwebsite. The Cohesity Technical Support website offers additional information to\nhelp you troubleshoot this issue." }, "6803": { "code": 6803, - "desc": "NetBackup CA com o given fingerprint não é possível be decommissioned. NetBackup status codes 846 NetBackup status codes", - "first_action": "Garanta que todos NetBackup services estão up e retry o", - "full_action": "Garanta que todos NetBackup services estão up e retry o\noperationaftersometime.Iftheissuepersists,visittheCohesityTechnicalSupport\nwebsite. O Cohesity Technical Support website offers additional informação to\nhelp you troubleshoot this issue." + "desc": "NetBackup CA with the given fingerprint cannot be decommissioned. NetBackup status codes 846 NetBackup status codes", + "first_action": "Ensure that all NetBackup services are up and retry the", + "full_action": "Ensure that all NetBackup services are up and retry the\noperationaftersometime.Iftheissuepersists,visittheCohesityTechnicalSupport\nwebsite. The Cohesity Technical Support website offers additional information to\nhelp you troubleshoot this issue." }, "6804": { "code": 6804, - "desc": "O key size está não valid. In non-FIPS mode, NetBackup supports 2048, 3072, 4096, e 8192 bits para key size. In FIPS mode, NetBackup supports apenas 2048 e 3072 bits para key size.", - "first_action": "In non-FIPS mode, use 2048, 3072, 4096, e 8192 bits para key size.", - "full_action": "UseoneofthefollowingkeysizesthatNetBackupsupports:\n■ In non-FIPS mode, use 2048, 3072, 4096, e 8192 bits para key size.\n■ In FIPS mode, use apenas 2048 bits e 3072 bits para key size." + "desc": "The key size is not valid. In non-FIPS mode, NetBackup supports 2048, 3072, 4096, and 8192 bits for key size. In FIPS mode, NetBackup supports only 2048 and 3072 bits for key size.", + "first_action": "In non-FIPS mode, use 2048, 3072, 4096, and 8192 bits for key size.", + "full_action": "UseoneofthefollowingkeysizesthatNetBackupsupports:\n■ In non-FIPS mode, use 2048, 3072, 4096, and 8192 bits for key size.\n■ In FIPS mode, use only 2048 bits and 3072 bits for key size." }, "6805": { "code": 6805, - "desc": "O migration de NetBackup CA está não initiated.", - "first_action": "Executar this operation when NetBackup CA migration está", - "full_action": "Executar this operation when NetBackup CA migration está\nin progress e está in um appropriate phase. Refer to o NetBackup Security e\nEncryption Guide to learn more about CA migration phases." + "desc": "The migration of NetBackup CA is not initiated.", + "first_action": "Perform this operation when NetBackup CA migration is", + "full_action": "Perform this operation when NetBackup CA migration is\nin progress and is in an appropriate phase. Refer to the NetBackup Security and\nEncryption Guide to learn more about CA migration phases." }, "6806": { "code": 6806, - "desc": "NetBackup CA com o given fingerprint does não exist.", + "desc": "NetBackup CA with the given fingerprint does not exist.", "first_action": "Use RESTful API GET", - "full_action": "Use RESTful API GET\n/security/certificate-authoritiesorusethenbseccmd -nbcalistcommand\nto get um list de todos certificate authorities que NetBackup supports e to view their\nfingerprints." + "full_action": "Use RESTful API GET\n/security/certificate-authoritiesorusethenbseccmd -nbcalistcommand\nto get a list of all certificate authorities that NetBackup supports and to view their\nfingerprints." }, "6807": { "code": 6807, - "desc": "NetBackup CA com o given fingerprint não é possível be decommissioned. Um NetBackup CA should be in ABANDONED state to be decommissioned.", + "desc": "NetBackup CA with the given fingerprint cannot be decommissioned. A NetBackup CA should be in ABANDONED state to be decommissioned.", "first_action": "UseRESTful GET /security/certificate-authorities", - "full_action": "UseRESTful GET /security/certificate-authorities\norusethenbseccmd -nbcalistcommandtogetalistofCertificateauthoritiesthat\nNetBackup supports e view o certificate authorities que estão in o ABANDONED\nstate." + "full_action": "UseRESTful GET /security/certificate-authorities\norusethenbseccmd -nbcalistcommandtogetalistofCertificateauthoritiesthat\nNetBackup supports and view the certificate authorities that are in the ABANDONED\nstate." }, "6808": { "code": 6808, - "desc": "O trust version does não exist.", - "first_action": "Access o /security/trust-versions API to view o", - "full_action": "Access o /security/trust-versions API to view o\ntrust versions from o banco de dados. Garanta que o trust version de o certificate\nexists." + "desc": "The trust version does not exist.", + "first_action": "Access the /security/trust-versions API to view the", + "full_action": "Access the /security/trust-versions API to view the\ntrust versions from the database. Ensure that the trust version of the certificate\nexists." }, "6809": { "code": 6809, - "desc": "NetBackup CA com o given certificate does não exist.", - "first_action": "Reason comando to synchronize o NetBackup banco de dados e", - "full_action": "Run o nbseccmd -nbcaMigrate -syncMigrationDB\n-reason comando to synchronize o NetBackup banco de dados e\nNetBackup security services. If o issue persists, visit o Cohesity Technical\nSupport website. O Cohesity Technical Support website offers additional\ninformação to help you troubleshoot this issue." + "desc": "NetBackup CA with the given certificate does not exist.", + "first_action": "Reason command to synchronize the NetBackup database and", + "full_action": "Run the nbseccmd -nbcaMigrate -syncMigrationDB\n-reason command to synchronize the NetBackup database and\nNetBackup security services. If the issue persists, visit the Cohesity Technical\nSupport website. The Cohesity Technical Support website offers additional\ninformation to help you troubleshoot this issue." }, "6810": { "code": 6810, - "desc": "O NetBackup CA migration summary não é possível be retrieved.", - "first_action": "Garanta que todos NetBackup services estão up e retry o", - "full_action": "Garanta que todos NetBackup services estão up e retry o\noperationaftersometime.Iftheissuepersists,visittheCohesityTechnicalSupport\nwebsite. O Cohesity Technical Support website offers additional informação to\nhelp you troubleshoot this issue." + "desc": "The NetBackup CA migration summary cannot be retrieved.", + "first_action": "Ensure that all NetBackup services are up and retry the", + "full_action": "Ensure that all NetBackup services are up and retry the\noperationaftersometime.Iftheissuepersists,visittheCohesityTechnicalSupport\nwebsite. The Cohesity Technical Support website offers additional information to\nhelp you troubleshoot this issue." }, "6811": { "code": 6811, - "desc": "O NetBackup CA migration está initiated; however, o CA migration status está incorrect. O expected CA migration status: INITIATED.", - "first_action": "Retry o operation e if o issue persists, visit o", - "full_action": "Retry o operation e if o issue persists, visit o\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional informação to help you troubleshoot this issue." + "desc": "The NetBackup CA migration is initiated; however, the CA migration status is incorrect. The expected CA migration status: INITIATED.", + "first_action": "Retry the operation and if the issue persists, visit the", + "full_action": "Retry the operation and if the issue persists, visit the\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional information to help you troubleshoot this issue." }, "6812": { "code": 6812, - "desc": "Falhou to retrieve o list de hosts que do não have o requerido CA certificates in their trust stores.", - "first_action": "Garanta que todos NetBackup services estão up e retry o", - "full_action": "Garanta que todos NetBackup services estão up e retry o\noperationaftersometime.Iftheissuepersists,visittheCohesityTechnicalSupport\nwebsite. O Cohesity Technical Support website offers additional informação to\nhelp you troubleshoot this issue." + "desc": "Failed to retrieve the list of hosts that do not have the required CA certificates in their trust stores.", + "first_action": "Ensure that all NetBackup services are up and retry the", + "full_action": "Ensure that all NetBackup services are up and retry the\noperationaftersometime.Iftheissuepersists,visittheCohesityTechnicalSupport\nwebsite. The Cohesity Technical Support website offers additional information to\nhelp you troubleshoot this issue." }, "6813": { "code": 6813, - "desc": "O activation phase de o NetBackup CA migration está to be started. O CA migration status should be INITIATED.", - "first_action": "Garanta que o NetBackup CA migration status está", - "full_action": "Garanta que o NetBackup CA migration status está\nINITIATED before o NetBackup CA está activated." + "desc": "The activation phase of the NetBackup CA migration is to be started. The CA migration status should be INITIATED.", + "first_action": "Ensure that the NetBackup CA migration status is", + "full_action": "Ensure that the NetBackup CA migration status is\nINITIATED before the NetBackup CA is activated." }, "6814": { "code": 6814, "desc": "TheactivationphaseoftheNetBackupCAmigrationiscomplete,however theCAmigrationstatusisincorrect.TheexpectedCAmigrationstatus:ACTIVATED.", - "first_action": "Retry o operation e if o issue persists, visit o", - "full_action": "Retry o operation e if o issue persists, visit o\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional informação to help you troubleshoot this issue." + "first_action": "Retry the operation and if the issue persists, visit the", + "full_action": "Retry the operation and if the issue persists, visit the\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional information to help you troubleshoot this issue." }, "6815": { "code": 6815, - "desc": "O completion phase de o NetBackup CA migration está started so o CA migration status should be ACTIVATED.", - "first_action": "Garanta que o current NetBackup CA migration status", - "full_action": "Garanta que o current NetBackup CA migration status\nestá ACTIVATED before o NetBackup CA migration está completed." + "desc": "The completion phase of the NetBackup CA migration is started so the CA migration status should be ACTIVATED.", + "first_action": "Ensure that the current NetBackup CA migration status", + "full_action": "Ensure that the current NetBackup CA migration status\nis ACTIVATED before the NetBackup CA migration is completed." }, "6816": { "code": 6816, - "desc": "O NetBackup CA migration está complete, however o CA migration status está incorrect. O expected CA migration status: NO_MIGRATION. NetBackup status codes 850 NetBackup status codes", - "first_action": "Retry o operation e if o issue persists, visit o", - "full_action": "Retry o operation e if o issue persists, visit o\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional informação to help you troubleshoot this issue." + "desc": "The NetBackup CA migration is complete, however the CA migration status is incorrect. The expected CA migration status: NO_MIGRATION. NetBackup status codes 850 NetBackup status codes", + "first_action": "Retry the operation and if the issue persists, visit the", + "full_action": "Retry the operation and if the issue persists, visit the\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional information to help you troubleshoot this issue." }, "6817": { "code": 6817, - "desc": "One ou more hosts do não have o requerido CA certificates in their trust stores. Communication com these hosts may break. Rerun o comando com o -force option to skip this validation.", - "first_action": "Garanta que o NetBackup CAs estão present in o trust stores de todos hosts in o", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Garanta que o NetBackup CAs estão present in o trust stores de todos hosts in o\ndomain before activating o NetBackup CA migration. O trust está established\nautomatically para um NetBackup 8.2.1 ou later host e can be verified usando o\nRESTful API GET\n/security/certificate-authorities/hosts-pending-trust-propagation\northenbseccmd -nbcamigrate -hostspendingtrustpropagationcommand.\nVerifique o trust propagation para NetBackup 8.2 ou earlier hosts manually. O\nlistofCAsthatshouldbepresentinthetruststoreofthehostcanbelistedusing\no RESTful API GET /security/cacert.\n■ If you desejar to skip o validation, rerun o comando com o -force option." + "desc": "One or more hosts do not have the required CA certificates in their trust stores. Communication with these hosts may break. Rerun the command with the -force option to skip this validation.", + "first_action": "Ensure that the NetBackup CAs are present in the trust stores of all hosts in the", + "full_action": "Do the following, as appropriate:\n■ Ensure that the NetBackup CAs are present in the trust stores of all hosts in the\ndomain before activating the NetBackup CA migration. The trust is established\nautomatically for a NetBackup 8.2.1 or later host and can be verified using the\nRESTful API GET\n/security/certificate-authorities/hosts-pending-trust-propagation\northenbseccmd -nbcamigrate -hostspendingtrustpropagationcommand.\nVerify the trust propagation for NetBackup 8.2 or earlier hosts manually. The\nlistofCAsthatshouldbepresentinthetruststoreofthehostcanbelistedusing\nthe RESTful API GET /security/cacert.\n■ If you want to skip the validation, rerun the command with the -force option." }, "6818": { "code": 6818, - "desc": "Activating o newly set up NetBackup CA está successful, but NetBackup não é possível retrieve o CA migration summary.", - "first_action": "Run o nbseccmd -nbcaMigrate -summary comando", - "full_action": "Run o nbseccmd -nbcaMigrate -summary comando\nto view o CA migration summary after some time. O expected NetBackup CA\nmigrationstatusisACTIVATED.Ifyouseedifferentstatus,visittheCohesityTechnical\nSupport website. O Cohesity Technical Support website offers additional\ninformação to help you troubleshoot this issue." + "desc": "Activating the newly set up NetBackup CA is successful, but NetBackup cannot retrieve the CA migration summary.", + "first_action": "Run the nbseccmd -nbcaMigrate -summary command", + "full_action": "Run the nbseccmd -nbcaMigrate -summary command\nto view the CA migration summary after some time. The expected NetBackup CA\nmigrationstatusisACTIVATED.Ifyouseedifferentstatus,visittheCohesityTechnical\nSupport website. The Cohesity Technical Support website offers additional\ninformation to help you troubleshoot this issue." }, "6819": { "code": 6819, - "desc": "O CA migration banco de dados não é possível be updated com o current NetBackup CA certificate details.", - "first_action": "Garanta que todos NetBackup services estão up e retry after", - "full_action": "Garanta que todos NetBackup services estão up e retry after\nsome time. If o issue persists, visit o Cohesity Technical Support website. O\nCohesity Technical Support website offers additional informação to help you\ntroubleshoot this issue." + "desc": "The CA migration database cannot be updated with the current NetBackup CA certificate details.", + "first_action": "Ensure that all NetBackup services are up and retry after", + "full_action": "Ensure that all NetBackup services are up and retry after\nsome time. If the issue persists, visit the Cohesity Technical Support website. The\nCohesity Technical Support website offers additional information to help you\ntroubleshoot this issue." }, "6820": { "code": 6820, - "desc": "Falhou to retrieve o list de hosts que require certificate renewal.", - "first_action": "Garanta que todos NetBackup services estão up e retry o", - "full_action": "Garanta que todos NetBackup services estão up e retry o\noperationaftersometime.Iftheissuepersists,visittheCohesityTechnicalSupport\nwebsite. O Cohesity Technical Support website offers additional informação to\nhelp you troubleshoot this issue." + "desc": "Failed to retrieve the list of hosts that require certificate renewal.", + "first_action": "Ensure that all NetBackup services are up and retry the", + "full_action": "Ensure that all NetBackup services are up and retry the\noperationaftersometime.Iftheissuepersists,visittheCohesityTechnicalSupport\nwebsite. The Cohesity Technical Support website offers additional information to\nhelp you troubleshoot this issue." }, "6821": { "code": 6821, - "desc": "One ou more hosts have pending certificate renewals com o new CA. Communication com these hosts may break. Rerun o comando com o -force option to skip this validation.", - "first_action": "Garanta que todos NetBackup hosts in o domain have their certificates signed por", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Garanta que todos NetBackup hosts in o domain have their certificates signed por\no active NetBackup CA e can be verified usando o RESTful API GET\n/config/hosts-pending-renewal ou o nbseccmd -nbcamigrate\n-hostspendingrenewal comando. Verifique o certificates para NetBackup 8.2 ou\nearlier hosts manually.\n■ If you desejar to skip o validation, rerun o comando com o -force option." + "desc": "One or more hosts have pending certificate renewals with the new CA. Communication with these hosts may break. Rerun the command with the -force option to skip this validation.", + "first_action": "Ensure that all NetBackup hosts in the domain have their certificates signed by", + "full_action": "Do the following, as appropriate:\n■ Ensure that all NetBackup hosts in the domain have their certificates signed by\nthe active NetBackup CA and can be verified using the RESTful API GET\n/config/hosts-pending-renewal or the nbseccmd -nbcamigrate\n-hostspendingrenewal command. Verify the certificates for NetBackup 8.2 or\nearlier hosts manually.\n■ If you want to skip the validation, rerun the command with the -force option." }, "6822": { "code": 6822, - "desc": "NewNetBackupCAmigrationcannotbeinitiatedbecausethemigration está currently activated.", - "first_action": "Complete o current NetBackup CA migration e then", - "full_action": "Complete o current NetBackup CA migration e then\ninitiate um new one." + "desc": "NewNetBackupCAmigrationcannotbeinitiatedbecausethemigration is currently activated.", + "first_action": "Complete the current NetBackup CA migration and then", + "full_action": "Complete the current NetBackup CA migration and then\ninitiate a new one." }, "6823": { "code": 6823, - "desc": "O NetBackup CA migration summary não é possível be retrieved after o completion de migration.", - "first_action": "Run o nbseccmd -nbcaMigrate -summary comando", - "full_action": "Run o nbseccmd -nbcaMigrate -summary comando\nto view o CA migration summary after some time. O expected NetBackup CA\nmigration status está NO_MIGRATION. If you veja different status, visit o Cohesity\nTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffersadditional\ninformação to help you troubleshoot this issue." + "desc": "The NetBackup CA migration summary cannot be retrieved after the completion of migration.", + "first_action": "Run the nbseccmd -nbcaMigrate -summary command", + "full_action": "Run the nbseccmd -nbcaMigrate -summary command\nto view the CA migration summary after some time. The expected NetBackup CA\nmigration status is NO_MIGRATION. If you see different status, visit the Cohesity\nTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffersadditional\ninformation to help you troubleshoot this issue." }, "6824": { "code": 6824, - "desc": "TheNetBackupCAmigrationsummarycannotberetrievedafterinitiating o migration.", - "first_action": "Run o nbseccmd -nbcaMigrate -summary comando", - "full_action": "Run o nbseccmd -nbcaMigrate -summary comando\nto view o CA migration summary after some time. O expected NetBackup CA\nmigrationstatusisINITIATED.Ifyouseedifferentstatus,visittheCohesityTechnical\nSupport website. O Cohesity Technical Support website offers additional\ninformação to help you troubleshoot this issue." + "desc": "TheNetBackupCAmigrationsummarycannotberetrievedafterinitiating the migration.", + "first_action": "Run the nbseccmd -nbcaMigrate -summary command", + "full_action": "Run the nbseccmd -nbcaMigrate -summary command\nto view the CA migration summary after some time. The expected NetBackup CA\nmigrationstatusisINITIATED.Ifyouseedifferentstatus,visittheCohesityTechnical\nSupport website. The Cohesity Technical Support website offers additional\ninformation to help you troubleshoot this issue." }, "6831": { "code": 6831, - "desc": "Nenhum de o credential IDs map com o given credential name ou ID.", - "first_action": "Configure um credential com provided credential name ou", - "full_action": "Configure um credential com provided credential name ou\nuse already configurado credential ID ou name." + "desc": "None of the credential IDs map with the given credential name or ID.", + "first_action": "Configure a credential with provided credential name or", + "full_action": "Configure a credential with provided credential name or\nuse already configured credential ID or name." }, "6832": { "code": 6832, - "desc": "Multiple credential IDs map com o given credential name ou ID.", - "first_action": "Configure um credential com unique credential name e", - "full_action": "Configure um credential com unique credential name e\nuse this credential para further operations." + "desc": "Multiple credential IDs map with the given credential name or ID.", + "first_action": "Configure a credential with unique credential name and", + "full_action": "Configure a credential with unique credential name and\nuse this credential for further operations." }, "6833": { "code": 6833, - "desc": "One ou more credential configuration checks falhou.", - "first_action": "O certificate caminho está valid.", - "full_action": "Garanta que o seguinte pre-checks succeed para o\ncredential configuration ou o update operation to succeed.\nThese checks estão performed while o credential configuration operation está\nattempted:\n■ O certificate caminho está valid.\n■ O trust store caminho está valid.\n■ O private key caminho está valid.\n■ O certificates in certificate chain estão readable.\n■ O certificates in trust store estão readable.\n■ O private key está readable.\n■ O Common Name field está não vazio.\n■ O certificate está não expired.\n■ O certificate está currently valid.\n■ O private key matches o certificate.\n■ O CRL diretório consists de CRL arquivos - This verifique está optional. It está performed\nif o ECA_CRL_PATH está configurado com o caminho para o CRL diretório.\n■ O CRL verifique level está valid - This verifique está optional. It está performed if o\nECA_CRL_PATH está configurado com o caminho para o CRL diretório e o CRL\nverifique level está anything but Disable.\n■ TheCRLpathisvalid-Thischeckisoptional.ItisperformediftheECA_CRL_PATH\nestá configurado com o caminho para o CRL diretório e o CRL verifique level está\nanything but Disable." + "desc": "One or more credential configuration checks failed.", + "first_action": "The certificate path is valid.", + "full_action": "Ensure that the following pre-checks succeed for the\ncredential configuration or the update operation to succeed.\nThese checks are performed while the credential configuration operation is\nattempted:\n■ The certificate path is valid.\n■ The trust store path is valid.\n■ The private key path is valid.\n■ The certificates in certificate chain are readable.\n■ The certificates in trust store are readable.\n■ The private key is readable.\n■ The Common Name field is not empty.\n■ The certificate is not expired.\n■ The certificate is currently valid.\n■ The private key matches the certificate.\n■ The CRL directory consists of CRL files - This check is optional. It is performed\nif the ECA_CRL_PATH is configured with the path for the CRL directory.\n■ The CRL check level is valid - This check is optional. It is performed if the\nECA_CRL_PATH is configured with the path for the CRL directory and the CRL\ncheck level is anything but Disable.\n■ TheCRLpathisvalid-Thischeckisoptional.ItisperformediftheECA_CRL_PATH\nis configured with the path for the CRL directory and the CRL check level is\nanything but Disable." }, "6882": { "code": 6882, - "desc": "Deletion de um NetBackup Certificate Authority certificate está não allowed.", - "first_action": "Garanta que o ECA certificate está enrolled on o host", - "full_action": "Garanta que o ECA certificate está enrolled on o host\nbefore you attempt to excluir o NBCA certificate. Verifique que o domain está in pure\nECA mode before you attempt to excluir o NBCA certificate de o primary servidor." + "desc": "Deletion of a NetBackup Certificate Authority certificate is not allowed.", + "first_action": "Ensure that the ECA certificate is enrolled on the host", + "full_action": "Ensure that the ECA certificate is enrolled on the host\nbefore you attempt to delete the NBCA certificate. Verify that the domain is in pure\nECA mode before you attempt to delete the NBCA certificate of the primary server." }, "7100": { "code": 7100, - "desc": "O manifest arquivo está não in o input data. Garanta que o manifest arquivo está disponível.", - "first_action": "Make sure que o manifest arquivo está present in o input", - "full_action": "Make sure que o manifest arquivo está present in o input\ndata." + "desc": "The manifest file is not in the input data. Ensure that the manifest file is available.", + "first_action": "Make sure that the manifest file is present in the input", + "full_action": "Make sure that the manifest file is present in the input\ndata." }, "7101": { "code": 7101, - "desc": "Multiple manifest arquivos exist in input data. Garanta que apenas one manifest arquivo exists in o input data.", - "first_action": "Remove o multiple manifest arquivos in o input data.", - "full_action": "Remove o multiple manifest arquivos in o input data." + "desc": "Multiple manifest files exist in input data. Ensure that only one manifest file exists in the input data.", + "first_action": "Remove the multiple manifest files in the input data.", + "full_action": "Remove the multiple manifest files in the input data." }, "7102": { "code": 7102, - "desc": "O manifest arquivo format está incorrect. Change o format e try again.", - "first_action": "Verifique o manifest arquivo format e correct if requerido como", - "full_action": "Verifique o manifest arquivo format e correct if requerido como\nper Sheltered Harbor specification." + "desc": "The manifest file format is incorrect. Change the format and try again.", + "first_action": "Check the manifest file format and correct if required as", + "full_action": "Check the manifest file format and correct if required as\nper Sheltered Harbor specification." }, "7103": { "code": 7103, - "desc": "Account data arquivos estão não disponível. Garanta que o arquivos estão disponível.", - "first_action": "Garanta que o account data arquivos estão present in o input", - "full_action": "Garanta que o account data arquivos estão present in o input\ndata." + "desc": "Account data files are not available. Ensure that the files are available.", + "first_action": "Ensure that the account data files are present in the input", + "full_action": "Ensure that the account data files are present in the input\ndata." }, "7104": { "code": 7104, - "desc": "Hash arquivos estão não present. Garanta que o arquivos estão disponível.", - "first_action": "Garanta que o hash arquivos estão present in o input data.", - "full_action": "Garanta que o hash arquivos estão present in o input data." + "desc": "Hash files are not present. Ensure that the files are available.", + "first_action": "Ensure that the hash files are present in the input data.", + "full_action": "Ensure that the hash files are present in the input data." }, "7105": { "code": 7105, - "desc": "Input data integrity validation has falhou. Garanta que o data está correct.", - "first_action": "Garanta que o input arquivos estão correct in o input data.", - "full_action": "Garanta que o input arquivos estão correct in o input data." + "desc": "Input data integrity validation has failed. Ensure that the data is correct.", + "first_action": "Ensure that the input files are correct in the input data.", + "full_action": "Ensure that the input files are correct in the input data." }, "7106": { "code": 7106, - "desc": "O arquivo name format does não follow o proper naming convention. Correct o arquivo name format e try again.", - "first_action": "Make sure que provided input arquivos estão correct como per", - "full_action": "Make sure que provided input arquivos estão correct como per\nSheltered Harbor specification." + "desc": "The file name format does not follow the proper naming convention. Correct the file name format and try again.", + "first_action": "Make sure that provided input files are correct as per", + "full_action": "Make sure that provided input files are correct as per\nSheltered Harbor specification." }, "7107": { "code": 7107, - "desc": "Inválido zip arquivo. Try o operation again.", + "desc": "Invalid zip file. Try the operation again.", "first_action": "Makesurethattheprovidedinputdataisincorrectformat.", "full_action": "Makesurethattheprovidedinputdataisincorrectformat." }, "7108": { "code": 7108, - "desc": "O diretório caminho que está specified para data restoration contains arquivos ou folders. Remove o existing contents from o diretório caminho e try again.", - "first_action": "Remove ou move o arquivos e ou folder present in o", - "full_action": "Remove ou move o arquivos e ou folder present in o\ndiretório que foi provided at o time de o restoration de data como o restored\ndata armazenamento caminho. Retry o restauração operation." + "desc": "The directory path that is specified for data restoration contains files or folders. Remove the existing contents from the directory path and try again.", + "first_action": "Remove or move the files and or folder present in the", + "full_action": "Remove or move the files and or folder present in the\ndirectory that was provided at the time of the restoration of data as the restored\ndata storage path. Retry the restore operation." }, "7109": { "code": 7109, - "desc": "Input data caminho does não exist. Provide o correct caminho e try again.", - "first_action": "Garanta que o provided input caminho exists at o time de", - "full_action": "Garanta que o provided input caminho exists at o time de\nbackup." + "desc": "Input data path does not exist. Provide the correct path and try again.", + "first_action": "Ensure that the provided input path exists at the time of", + "full_action": "Ensure that the provided input path exists at the time of\nbackup." }, "7110": { "code": 7110, - "desc": "O specified diretório caminho está não valid.", - "first_action": "Provide um valid pathname.", - "full_action": "Provide um valid pathname." + "desc": "The specified directory path is not valid.", + "first_action": "Provide a valid pathname.", + "full_action": "Provide a valid pathname." }, "7112": { "code": 7112, - "desc": "Um call to o nbcryptocmd utility has esgotado fora. Verifique o log arquivo para more informação.", - "first_action": "Por default, o time-out para o nbcryptocmd utility está 30", - "full_action": "Por default, o time-out para o nbcryptocmd utility está 30\nminutes. If you desejar to aumentar o time-out, contate o NetBackup administrator." + "desc": "A call to the nbcryptocmd utility has timed out. Check the log file for more information.", + "first_action": "By default, the time-out for the nbcryptocmd utility is 30", + "full_action": "By default, the time-out for the nbcryptocmd utility is 30\nminutes. If you want to increase the time-out, contact the NetBackup administrator." }, "7113": { "code": 7113, - "desc": "O license validation falhou.", - "first_action": "Make sure que o given license parâmetro está correct como", - "full_action": "Make sure que o given license parâmetro está correct como\nper Sheltered Harbor specification." + "desc": "The license validation failed.", + "first_action": "Make sure that the given license parameter is correct as", + "full_action": "Make sure that the given license parameter is correct as\nper Sheltered Harbor specification." }, "7114": { "code": 7114, - "desc": "O license has expired.", - "first_action": "Get um new license from Sheltered Harbor e update o", - "full_action": "Get um new license from Sheltered Harbor e update o\nlicense arquivo com o new license parameters provided por Sheltered Harbor." + "desc": "The license has expired.", + "first_action": "Get a new license from Sheltered Harbor and update the", + "full_action": "Get a new license from Sheltered Harbor and update the\nlicense file with the new license parameters provided by Sheltered Harbor." }, "7115": { "code": 7115, - "desc": "O extension de o specified arquivo está não supported. O arquivo should have .json extension.", - "first_action": "Provide um valid JSON arquivo com o .json extension.", - "full_action": "Provide um valid JSON arquivo com o .json extension." + "desc": "The extension of the specified file is not supported. The file should have .json extension.", + "first_action": "Provide a valid JSON file with the .json extension.", + "full_action": "Provide a valid JSON file with the .json extension." }, "7116": { "code": 7116, - "desc": "Falhou to create o transfer armazenamento caminho. Verifique o log arquivo para more informação.", - "first_action": "Garanta que o provided transfer armazenamento caminho exists. Ou,", - "full_action": "Garanta que o provided transfer armazenamento caminho exists. Ou,\nverifique que permissions estão correct e create o transfer armazenamento caminho." + "desc": "Failed to create the transfer storage path. Check the log file for more information.", + "first_action": "Ensure that the provided transfer storage path exists. Or,", + "full_action": "Ensure that the provided transfer storage path exists. Or,\nverify that permissions are correct and create the transfer storage path." }, "7117": { "code": 7117, - "desc": "Arquivo does não exist. Verifique o log arquivo para more informação.", - "first_action": "Garanta que o provided arquivo exists at o given location.", - "full_action": "Garanta que o provided arquivo exists at o given location.\nVerifique o nbshvault log para more informação about o arquivo." + "desc": "File does not exist. Check the log file for more information.", + "first_action": "Ensure that the provided file exists at the given location.", + "full_action": "Ensure that the provided file exists at the given location.\nCheck the nbshvault log for more information about the file." }, "7118": { "code": 7118, - "desc": "O JSON format está inválido. Enter o correct format e try again.", - "first_action": "Make sure que JSON arquivo format está correct.", - "full_action": "Make sure que JSON arquivo format está correct." + "desc": "The JSON format is invalid. Enter the correct format and try again.", + "first_action": "Make sure that JSON file format is correct.", + "full_action": "Make sure that JSON file format is correct." }, "7119": { "code": 7119, - "desc": "O cryptographic material arquivo format está incorrect. Contate seu NetBackup administrator para assistance.", - "first_action": "Make sure que cryptographic material arquivo está in o correct", - "full_action": "Make sure que cryptographic material arquivo está in o correct\nformatperShelteredHarborspecifications.Formoredetails,contacttheNetBackup\nadministrator." + "desc": "The cryptographic material file format is incorrect. Contact your NetBackup administrator for assistance.", + "first_action": "Make sure that cryptographic material file is in the correct", + "full_action": "Make sure that cryptographic material file is in the correct\nformatperShelteredHarborspecifications.Formoredetails,contacttheNetBackup\nadministrator." }, "7120": { "code": 7120, - "desc": "O secure envelope arquivo format está incorrect. Contate seu NetBackup administrator para assistance.", - "first_action": "Make sure que o secure envelope arquivo está in o correct", - "full_action": "Make sure que o secure envelope arquivo está in o correct\nformatperShelteredHarborspecifications.Formoredetails,contacttheNetBackup\nadministrator para assistance." + "desc": "The secure envelope file format is incorrect. Contact your NetBackup administrator for assistance.", + "first_action": "Make sure that the secure envelope file is in the correct", + "full_action": "Make sure that the secure envelope file is in the correct\nformatperShelteredHarborspecifications.Formoredetails,contacttheNetBackup\nadministrator for assistance." }, "7121": { "code": 7121, - "desc": "Banco de dados tables do não exist. Garanta que todos o tables estão disponível.", - "first_action": "Contate o NetBackup administrator para more details.", - "full_action": "Contate o NetBackup administrator para more details." + "desc": "Database tables do not exist. Ensure that all the tables are available.", + "first_action": "Contact the NetBackup administrator for more details.", + "full_action": "Contact the NetBackup administrator for more details." }, "7122": { "code": 7122, - "desc": "Banco de dados erro ocorreu. Verifique o log arquivo para more informação.", - "first_action": "Contate o NetBackup administrator para more details.", - "full_action": "Contate o NetBackup administrator para more details." + "desc": "Database error occurred. Check the log file for more information.", + "first_action": "Contact the NetBackup administrator for more details.", + "full_action": "Contact the NetBackup administrator for more details." }, "7123": { "code": 7123, - "desc": "O Sheltered Harbor compliance solution está não configurado. Configure o solution usando o --configure option. NetBackup status codes 861 NetBackup status codes", + "desc": "The Sheltered Harbor compliance solution is not configured. Configure the solution using the --configure option. NetBackup status codes 861 NetBackup status codes", "first_action": "-configure option.", - "full_action": "You need to configure o compliance solution usando o\n--configure option." + "full_action": "You need to configure the compliance solution using the\n--configure option." }, "7125": { "code": 7125, - "desc": "O platform está não supported.", - "first_action": "Make sure to run o nbshvault utility on o NetBackup", - "full_action": "Make sure to run o nbshvault utility on o NetBackup\nservidor platforms." + "desc": "The platform is not supported.", + "first_action": "Make sure to run the nbshvault utility on the NetBackup", + "full_action": "Make sure to run the nbshvault utility on the NetBackup\nserver platforms." }, "7126": { "code": 7126, - "desc": "Data vaulting de o image in isolated recovery environment (IRE) está still in progress. Retry at um later time.", + "desc": "Data vaulting of the image in isolated recovery environment (IRE) is still in progress. Retry at a later time.", "first_action": "Retrythedatavaultingafterthecurrentoperationfinishes", - "full_action": "Retrythedatavaultingafterthecurrentoperationfinishes\nusando o --attest option." + "full_action": "Retrythedatavaultingafterthecurrentoperationfinishes\nusing the --attest option." }, "7127": { "code": 7127, - "desc": "O NetBackup version in o arquivo caminho está não valid. Garanta que o NetBackup installation foi successful.", - "first_action": "Verifique que NetBackup está instalado properly. Para more", - "full_action": "Verifique que NetBackup está instalado properly. Para more\ndetails, contate seu NetBackup Administrator." + "desc": "The NetBackup version in the file path is not valid. Ensure that the NetBackup installation was successful.", + "first_action": "Verify that NetBackup is installed properly. For more", + "full_action": "Verify that NetBackup is installed properly. For more\ndetails, contact your NetBackup Administrator." }, "7128": { "code": 7128, "desc": "ThebackupimageIDismissing.Checkthelogfileformoreinformation.", - "first_action": "Retry o operation. If o issue persists, contate o", - "full_action": "Retry o operation. If o issue persists, contate o\nNetBackup administrator." + "first_action": "Retry the operation. If the issue persists, contact the", + "full_action": "Retry the operation. If the issue persists, contact the\nNetBackup administrator." }, "7129": { "code": 7129, - "desc": "O institution ID does não match o manifest arquivo data. Use o correct institution ID e try again.", - "first_action": "You need to use o correct institution ID e try again.", - "full_action": "You need to use o correct institution ID e try again." + "desc": "The institution ID does not match the manifest file data. Use the correct institution ID and try again.", + "first_action": "You need to use the correct institution ID and try again.", + "full_action": "You need to use the correct institution ID and try again." }, "7130": { "code": 7130, - "desc": "You estão usando um earlier version de NetBackup. Upgrade to o latest version.", - "first_action": "You must run um NetBackup version que está 10.1 ou higher.", - "full_action": "You must run um NetBackup version que está 10.1 ou higher." + "desc": "You are using an earlier version of NetBackup. Upgrade to the latest version.", + "first_action": "You must run a NetBackup version that is 10.1 or higher.", + "full_action": "You must run a NetBackup version that is 10.1 or higher." }, "7131": { "code": 7131, - "desc": "RegistrationresponseJSONisnotintheproperformat.Enterthecorrect format e try again.", - "first_action": "Retry o Sheltered Harbor backup workflow. If o issue", - "full_action": "Retry o Sheltered Harbor backup workflow. If o issue\npersists, contate o NetBackup administrator." + "desc": "RegistrationresponseJSONisnotintheproperformat.Enterthecorrect format and try again.", + "first_action": "Retry the Sheltered Harbor backup workflow. If the issue", + "full_action": "Retry the Sheltered Harbor backup workflow. If the issue\npersists, contact the NetBackup administrator." }, "7132": { "code": 7132, - "desc": "Secure envelope foi não found. Garanta que o secure envelope está disponível.", + "desc": "Secure envelope was not found. Ensure that the secure envelope is available.", "first_action": "Ifthesecureenvelopeisnotfoundinthetransferstorage,", - "full_action": "Ifthesecureenvelopeisnotfoundinthetransferstorage,\nyou can recheck o input data e run o backup operation again." + "full_action": "Ifthesecureenvelopeisnotfoundinthetransferstorage,\nyou can recheck the input data and run the backup operation again." }, "7133": { "code": 7133, - "desc": "Parâmetro está não in o secure envelope. Garanta que o parâmetro está disponível.", - "first_action": "If o secure envelope JSON arquivo parâmetro está não in o", - "full_action": "If o secure envelope JSON arquivo parâmetro está não in o\ntransfer armazenamento caminho, you can recheck o arquivo parameters e run o backup\noperation again." + "desc": "Parameter is not in the secure envelope. Ensure that the parameter is available.", + "first_action": "If the secure envelope JSON file parameter is not in the", + "full_action": "If the secure envelope JSON file parameter is not in the\ntransfer storage path, you can recheck the file parameters and run the backup\noperation again." }, "7134": { "code": 7134, - "desc": "AttestationresponseJSONnotinproperformat.Enterthecorrectformat e try again.", - "first_action": "Garanta que o solution está registered e o Ethereum", - "full_action": "Garanta que o solution está registered e o Ethereum\nprivate key está created in proper format." + "desc": "AttestationresponseJSONnotinproperformat.Enterthecorrectformat and try again.", + "first_action": "Ensure that the solution is registered and the Ethereum", + "full_action": "Ensure that the solution is registered and the Ethereum\nprivate key is created in proper format." }, "7135": { "code": 7135, - "desc": "O JSON input data does não match o respective JSON schema. Enter o correct format.", - "first_action": "Make sure que o given JSON arquivo format está correct como", - "full_action": "Make sure que o given JSON arquivo format está correct como\nper o JSON schema. You have to correct o JSON arquivo format if o format está\nincorrect. Verifique o nbshvault log arquivo para more informação." + "desc": "The JSON input data does not match the respective JSON schema. Enter the correct format.", + "first_action": "Make sure that the given JSON file format is correct as", + "full_action": "Make sure that the given JSON file format is correct as\nper the JSON schema. You have to correct the JSON file format if the format is\nincorrect. Check the nbshvault log file for more information." }, "7136": { "code": 7136, - "desc": "Registration message posting de financial institution falhou. Verifique o log arquivo para more informação.", - "first_action": "Verifique que Sheltered Harbor registration API está reachable", - "full_action": "Verifique que Sheltered Harbor registration API está reachable\nfrom o NetBackup cliente onde nbshvault está executando." + "desc": "Registration message posting of financial institution failed. Check the log file for more information.", + "first_action": "Verify that Sheltered Harbor registration API is reachable", + "full_action": "Verify that Sheltered Harbor registration API is reachable\nfrom the NetBackup client where nbshvault is running." }, "7137": { "code": 7137, "desc": "Attestationmessagepostingfailed.Checkthelogfileformoreinformation.", "first_action": "VerifythattheShelteredHarborattestationAPIisreachable", - "full_action": "VerifythattheShelteredHarborattestationAPIisreachable\nfrom o NetBackup cliente onde nbshvault está executando." + "full_action": "VerifythattheShelteredHarborattestationAPIisreachable\nfrom the NetBackup client where nbshvault is running." }, "7138": { "code": 7138, - "desc": "Não pending attestation found.", - "first_action": "Retry o operation e if o issue persists, contate o", - "full_action": "Retry o operation e if o issue persists, contate o\nNetBackup administrator." + "desc": "No pending attestation found.", + "first_action": "Retry the operation and if the issue persists, contact the", + "full_action": "Retry the operation and if the issue persists, contact the\nNetBackup administrator." }, "7139": { "code": 7139, - "desc": "Falhou to ler key arquivo. Garanta que o key arquivo está disponível.", - "first_action": "Verifique que you have ler access permissions to o", - "full_action": "Verifique que you have ler access permissions to o\nvar/nbshvault/cert arquivo onde o Ethereum private key está created." + "desc": "Failed to read key file. Ensure that the key file is available.", + "first_action": "Verify that you have read access permissions to the", + "full_action": "Verify that you have read access permissions to the\nvar/nbshvault/cert file where the Ethereum private key is created." }, "7140": { "code": 7140, - "desc": "Key arquivo does não exist. Garanta que o key arquivo está disponível.", - "first_action": "Make sure que o Ether private key such como", - "full_action": "Make sure que o Ether private key such como\n JSON arquivo está disponível in o var/nbshvault/cert/\ndiretório. If o institute está não registered, register it usando o --register option." + "desc": "Key file does not exist. Ensure that the key file is available.", + "first_action": "Make sure that the Ether private key such as", + "full_action": "Make sure that the Ether private key such as\n JSON file is available in the var/nbshvault/cert/\ndirectory. If the institute is not registered, register it using the --register option." }, "7141": { "code": 7141, - "desc": "Private key does não exist. Garanta que o private key está disponível.", - "first_action": "Verifique que ether_pri_key está present in o", - "full_action": "Verifique que ether_pri_key está present in o\nvar/nbshvault/cert/.json arquivo." + "desc": "Private key does not exist. Ensure that the private key is available.", + "first_action": "Verify that ether_pri_key is present in the", + "full_action": "Verify that ether_pri_key is present in the\nvar/nbshvault/cert/.json file." }, "7142": { "code": 7142, - "desc": "Recovery armazenamento caminho does não exist. Provide o correct recovery armazenamento caminho. NetBackup status codes 866 NetBackup status codes", + "desc": "Recovery storage path does not exist. Provide the correct recovery storage path. NetBackup status codes 866 NetBackup status codes", "first_action": "Makesurethattheprovidedrecoverystoragepathexists.", "full_action": "Makesurethattheprovidedrecoverystoragepathexists." }, "7143": { "code": 7143, - "desc": "Falhou to create restored data armazenamento caminho. Verifique o log arquivo para more informação.", + "desc": "Failed to create restored data storage path. Check the log file for more information.", "first_action": "Verifythattherestoreddatastoragepathexistsandcheck", "full_action": "Verifythattherestoreddatastoragepathexistsandcheck\nif you have create permissions access." }, "7144": { "code": 7144, "desc": "Archivevolumeisnotpresent.Ensurethatthearchivevolumeisavailable.", - "first_action": "Verifique que o archive volume exists.", - "full_action": "Verifique que o archive volume exists." + "first_action": "Verify that the archive volume exists.", + "full_action": "Verify that the archive volume exists." }, "7146": { "code": 7146, - "desc": "Falhou to extract compressed volume. Verifique o log arquivo para more informação.", + "desc": "Failed to extract compressed volume. Check the log file for more information.", "first_action": "Verifythattheencryptedcompressedvolumesarerestored", - "full_action": "Verifythattheencryptedcompressedvolumesarerestored\ncorrectly. Restauração o data again e then retry o operation." + "full_action": "Verifythattheencryptedcompressedvolumesarerestored\ncorrectly. Restore the data again and then retry the operation." }, "7147": { "code": 7147, - "desc": "O exit code está não valid. Verifique o log arquivo para more informação.", - "first_action": "Retry o operation e if o issue persists, visit", - "full_action": "Retry o operation e if o issue persists, visit\nsupport.veritas.com. O Cohesity Technical Support website site offers additional\ninformação to help you troubleshoot this issue." + "desc": "The exit code is not valid. Check the log file for more information.", + "first_action": "Retry the operation and if the issue persists, visit", + "full_action": "Retry the operation and if the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support website site offers additional\ninformation to help you troubleshoot this issue." }, "7148": { "code": 7148, - "desc": "Unabletoaccessrestoreddatastoragepath.Checkthelogfileformore informação.", - "first_action": "Verifique que you have o ler e gravar access to o", - "full_action": "Verifique que you have o ler e gravar access to o\nrestored data armazenamento caminho." + "desc": "Unabletoaccessrestoreddatastoragepath.Checkthelogfileformore information.", + "first_action": "Verify that you have the read and write access to the", + "full_action": "Verify that you have the read and write access to the\nrestored data storage path." }, "7149": { "code": 7149, - "desc": "O -caminho option está não present in o --generate-template. Provide o correct caminho usando o -caminho option.", - "first_action": "Make sure to use --generate-template -caminho ", - "full_action": "Make sure to use --generate-template -caminho \noption to generate templates." + "desc": "The -path option is not present in the --generate-template. Provide the correct path using the -path option.", + "first_action": "Make sure to use --generate-template -path ", + "full_action": "Make sure to use --generate-template -path \noption to generate templates." }, "7151": { "code": 7151, - "desc": "O NetBackup configuration arquivo não é possível be ler. Verifique o log arquivo para more informação.", - "first_action": "Make sure que you have ler e gravar access to o", - "full_action": "Make sure que you have ler e gravar access to o\nvar/nbshvault/config folder." + "desc": "The NetBackup configuration file cannot be read. Check the log file for more information.", + "first_action": "Make sure that you have read and write access to the", + "full_action": "Make sure that you have read and write access to the\nvar/nbshvault/config folder." }, "7152": { "code": 7152, - "desc": "Falhou to generate o template. Verifique o log arquivo para more informação.", - "first_action": "Make sure que you have o ler e gravar access to o", - "full_action": "Make sure que you have o ler e gravar access to o\ncaminho provided com --caminho option." + "desc": "Failed to generate the template. Check the log file for more information.", + "first_action": "Make sure that you have the read and write access to the", + "full_action": "Make sure that you have the read and write access to the\npath provided with --path option." }, "7153": { "code": 7153, - "desc": "Unknown erro.", - "first_action": "You need to review o nbshvault logs to veja um detailed", - "full_action": "You need to review o nbshvault logs to veja um detailed\nerro message. Para more informação, contate o NetBackup administrator." + "desc": "Unknown error.", + "first_action": "You need to review the nbshvault logs to see a detailed", + "full_action": "You need to review the nbshvault logs to see a detailed\nerror message. For more information, contact the NetBackup administrator." }, "7154": { "code": 7154, - "desc": "FailedtoreadtheinstallationdirectoryfromtheNetBackupconfiguration arquivo. Para more details, contate seu NetBackup Administrator.", - "first_action": "Para more details, contate o NetBackup administrator.", - "full_action": "Para more details, contate o NetBackup administrator." + "desc": "FailedtoreadtheinstallationdirectoryfromtheNetBackupconfiguration file. For more details, contact your NetBackup Administrator.", + "first_action": "For more details, contact the NetBackup administrator.", + "full_action": "For more details, contact the NetBackup administrator." }, "7155": { "code": 7155, "desc": "NoKMSisenabledduringtheShelteredHarborcomplianceconfiguration. NetBackup status codes 869 NetBackup status codes", "first_action": "IfKMSconfigurationisnotenabled,usethe--configure", - "full_action": "IfKMSconfigurationisnotenabled,usethe--configure\noption to update o Sheltered Harbor compliance configuration." + "full_action": "IfKMSconfigurationisnotenabled,usethe--configure\noption to update the Sheltered Harbor compliance configuration." }, "7156": { "code": 7156, - "desc": "Archive generation has esgotado fora.", - "first_action": "Por default, o archive generation time fora está 30 minutes.", - "full_action": "Por default, o archive generation time fora está 30 minutes.\nTo aumentar o time-out, change o archive_generation time-out option in o\nconfigure.json arquivo e use this arquivo to configure o solution." + "desc": "Archive generation has timed out.", + "first_action": "By default, the archive generation time out is 30 minutes.", + "full_action": "By default, the archive generation time out is 30 minutes.\nTo increase the time-out, change the archive_generation time-out option in the\nconfigure.json file and use this file to configure the solution." }, "7157": { "code": 7157, - "desc": "Archive repository backup has esgotado fora.", - "first_action": "Por default, o archive repository time-out está 30 minutes.", - "full_action": "Por default, o archive repository time-out está 30 minutes.\nTo aumentar o time-out, change o archive_repository time-out option in o\nconfigure.json arquivo e use this arquivo to configure o solution." + "desc": "Archive repository backup has timed out.", + "first_action": "By default, the archive repository time-out is 30 minutes.", + "full_action": "By default, the archive repository time-out is 30 minutes.\nTo increase the time-out, change the archive_repository time-out option in the\nconfigure.json file and use this file to configure the solution." }, "7158": { "code": 7158, - "desc": "Vaulting attestation has esgotado fora.", - "first_action": "Por default, o vaulting attestation time-out está 30 minutes.", - "full_action": "Por default, o vaulting attestation time-out está 30 minutes.\nTo aumentar o time-out, change o vaulting_attestation time-out in o\nconfigure.json arquivo e use this arquivo to configure o solution." + "desc": "Vaulting attestation has timed out.", + "first_action": "By default, the vaulting attestation time-out is 30 minutes.", + "full_action": "By default, the vaulting attestation time-out is 30 minutes.\nTo increase the time-out, change the vaulting_attestation time-out in the\nconfigure.json file and use this file to configure the solution." }, "7159": { "code": 7159, - "desc": "Daily backup workflow process has esgotado fora.", - "first_action": "Por default, o daily backup workflow process time fora está", - "full_action": "Por default, o daily backup workflow process time fora está\n120minutes.Toincreasethetime-out,changethedaily_backup_processtime-out\nin o configure.json arquivo e use this arquivo to configure o solution." + "desc": "Daily backup workflow process has timed out.", + "first_action": "By default, the daily backup workflow process time out is", + "full_action": "By default, the daily backup workflow process time out is\n120minutes.Toincreasethetime-out,changethedaily_backup_processtime-out\nin the configure.json file and use this file to configure the solution." }, "7160": { "code": 7160, - "desc": "Restauração workflow process has esgotado fora.", - "first_action": "Por default, o restauração workflow process time-out está 120", - "full_action": "Por default, o restauração workflow process time-out está 120\nminutes. To aumentar o time-out, change o restore_process time-out in o\nconfigure.json arquivo e use this arquivo to configure o solution." + "desc": "Restore workflow process has timed out.", + "first_action": "By default, the restore workflow process time-out is 120", + "full_action": "By default, the restore workflow process time-out is 120\nminutes. To increase the time-out, change the restore_process time-out in the\nconfigure.json file and use this file to configure the solution." }, "7161": { "code": 7161, - "desc": "Air gap image replication has esgotado fora.", - "first_action": "Por default, o restauração workflow process time-out está 30", - "full_action": "Por default, o restauração workflow process time-out está 30\nminutes. To aumentar o time-out, change o air_gap_timeout time-out in o\nconfigure.json arquivo e use this arquivo to configure o solution." + "desc": "Air gap image replication has timed out.", + "first_action": "By default, the restore workflow process time-out is 30", + "full_action": "By default, the restore workflow process time-out is 30\nminutes. To increase the time-out, change the air_gap_timeout time-out in the\nconfigure.json file and use this file to configure the solution." }, "7162": { "code": 7162, - "desc": "O attestation private key size está não correct.", - "first_action": "O attestation private key size está expected to be 256-bit.", - "full_action": "O attestation private key size está expected to be 256-bit.\nIf o institution ID está already registered com Sheltered Harbor, import o private\nkey que foi used at o time de registration usando o --import-key option e\nretry." + "desc": "The attestation private key size is not correct.", + "first_action": "The attestation private key size is expected to be 256-bit.", + "full_action": "The attestation private key size is expected to be 256-bit.\nIf the institution ID is already registered with Sheltered Harbor, import the private\nkey that was used at the time of registration using the --import-key option and\nretry." }, "7163": { "code": 7163, - "desc": "O institution ID está incorrect.", - "first_action": "You need to use o 10-digit institution ID provided por", - "full_action": "You need to use o 10-digit institution ID provided por\nSheltered Harbor." + "desc": "The institution ID is incorrect.", + "first_action": "You need to use the 10-digit institution ID provided by", + "full_action": "You need to use the 10-digit institution ID provided by\nSheltered Harbor." }, "7164": { "code": 7164, - "desc": "O registration key está incorrect. Garanta que o correct registration key está provided.", - "first_action": "You need to use o valid registration key provided por", - "full_action": "You need to use o valid registration key provided por\nSheltered Harbor." + "desc": "The registration key is incorrect. Ensure that the correct registration key is provided.", + "first_action": "You need to use the valid registration key provided by", + "full_action": "You need to use the valid registration key provided by\nSheltered Harbor." }, "7165": { "code": 7165, - "desc": "Um internal erro ocorreu. Verifique o nbcryptocmd logs.", - "first_action": "Review o nbcryptocmd logs to diagnose o problema.", - "full_action": "Review o nbcryptocmd logs to diagnose o problema." + "desc": "An internal error occurred. Check the nbcryptocmd logs.", + "first_action": "Review the nbcryptocmd logs to diagnose the problem.", + "full_action": "Review the nbcryptocmd logs to diagnose the problem." }, "7166": { "code": 7166, - "desc": "O authentication fails during conexão to o cloud KMS.", - "first_action": "Review o cloud KMS configuration parameters de", - "full_action": "Review o cloud KMS configuration parameters de\nnbshvault e verifique if they estão correct." + "desc": "The authentication fails during connection to the cloud KMS.", + "first_action": "Review the cloud KMS configuration parameters of", + "full_action": "Review the cloud KMS configuration parameters of\nnbshvault and verify if they are correct." }, "7167": { "code": 7167, - "desc": "O cloud KMS operation falhou. Verifique o nbcryptocmd logs.", - "first_action": "Review o nbcryptocmd logs to diagnose o problema.", - "full_action": "Review o nbcryptocmd logs to diagnose o problema." + "desc": "The cloud KMS operation failed. Check the nbcryptocmd logs.", + "first_action": "Review the nbcryptocmd logs to diagnose the problem.", + "full_action": "Review the nbcryptocmd logs to diagnose the problem." }, "7168": { "code": 7168, - "desc": "Another instance de o same operation está in progress. Retry at um later time.", - "first_action": "You must wait until o first executando process completes", - "full_action": "You must wait until o first executando process completes\ne then retry o operation." + "desc": "Another instance of the same operation is in progress. Retry at a later time.", + "first_action": "You must wait until the first running process completes", + "full_action": "You must wait until the first running process completes\nand then retry the operation." }, "7200": { "code": 7200, - "desc": "Execution de nbinstallagent in o remote host falhou.", + "desc": "Execution of nbinstallagent in the remote host failed.", "first_action": "On Windows:", - "full_action": "Review o mídia servidor admin log at o seguinte\nlocations:\n■ On Windows:\ninstall_path\\NetBackup\\logs\\admin\\root*.log\n■ On UNIX e Linux:\n/usr/openv/netbackup/logs/admin/root*.log" + "full_action": "Review the media server admin log at the following\nlocations:\n■ On Windows:\ninstall_path\\NetBackup\\logs\\admin\\root*.log\n■ On UNIX and Linux:\n/usr/openv/netbackup/logs/admin/root*.log" }, "7201": { "code": 7201, - "desc": "O arquivo name está não provided.", + "desc": "The file name is not provided.", "first_action": "On Windows:", - "full_action": "Review o Job Manager log at o seguinte locations to\ngaranta que o file_name option está não vazio:\n■ On Windows:\ninstall_path\\NetBackup\\logs\\nbjm\n■ On UNIX e Linux:\n/usr/openv/logs/nbjm" + "full_action": "Review the Job Manager log at the following locations to\nensure that the file_name option is not empty:\n■ On Windows:\ninstall_path\\NetBackup\\logs\\nbjm\n■ On UNIX and Linux:\n/usr/openv/logs/nbjm" }, "7202": { "code": 7202, - "desc": "Não foi possível to retrieve NetBackup version from o remote host.", + "desc": "Unable to retrieve NetBackup version from the remote host.", "first_action": "Ensurethatthebpcdserviceisrunningintheremotehost", - "full_action": "Ensurethatthebpcdserviceisrunningintheremotehost\ne it has connectivity to o mídia servidor." + "full_action": "Ensurethatthebpcdserviceisrunningintheremotehost\nand it has connectivity to the media server." }, "7203": { "code": 7203, - "desc": "Não foi possível to retrieve platform informação from o remote host.", + "desc": "Unable to retrieve platform information from the remote host.", "first_action": "Ensurethatthebpcdserviceisrunningintheremotehost", - "full_action": "Ensurethatthebpcdserviceisrunningintheremotehost\ne it has connectivity to o mídia servidor." + "full_action": "Ensurethatthebpcdserviceisrunningintheremotehost\nand it has connectivity to the media server." }, "7204": { "code": 7204, - "desc": "Remote host name não specified.", - "first_action": "Review o Job Manager log at o seguinte locations to", - "full_action": "Review o Job Manager log at o seguinte locations to\ngaranta que o hostname option está não vazio:\nOn Windows: install_path\\NetBackup\\logs\\nbjm\nOn UNIX e Linux: /usr/openv/logs/nbjm" + "desc": "Remote host name not specified.", + "first_action": "Review the Job Manager log at the following locations to", + "full_action": "Review the Job Manager log at the following locations to\nensure that the hostname option is not empty:\nOn Windows: install_path\\NetBackup\\logs\\nbjm\nOn UNIX and Linux: /usr/openv/logs/nbjm" }, "7205": { "code": 7205, - "desc": "Não foi possível to retrieve NetBackup install diretório from o remote host.", + "desc": "Unable to retrieve NetBackup install directory from the remote host.", "first_action": "Ensurethatthebpcdserviceisrunningintheremotehost", - "full_action": "Ensurethatthebpcdserviceisrunningintheremotehost\ne it has connectivity to o mídia servidor. Garanta que NetBackup está properly\ninstalled.Confirmthatrecentbackupsransuccessfully.Runatestbackup.Confirm\nque o version de NetBackup being upgraded está supported. Para more informação,\npor favor veja o NetBackup Upgrade Guide." + "full_action": "Ensurethatthebpcdserviceisrunningintheremotehost\nand it has connectivity to the media server. Ensure that NetBackup is properly\ninstalled.Confirmthatrecentbackupsransuccessfully.Runatestbackup.Confirm\nthat the version of NetBackup being upgraded is supported. For more information,\nplease see the NetBackup Upgrade Guide." }, "7206": { "code": 7206, - "desc": "Falhou to transfer um arquivo to o remote host.", + "desc": "Failed to transfer a file to the remote host.", "first_action": "Ensurethatthebpcdserviceisrunningintheremotehostandithasconnectivity", - "full_action": "Executar o seguinte como appropriate:\n■ Ensurethatthebpcdserviceisrunningintheremotehostandithasconnectivity\nto o mídia servidor.\n■ Garanta que NetBackup está properly instalado.\n■ Confirm que recent backups ran successfully.\n■ Run um test backup.\n■ Confirm que o version de NetBackup being upgraded está supported.\n■ Verifique que o transfer arquivo exists e has o proper permissions.\n■ Identify o arquivo being transferred por reviewing o admin logs on o servidor\ne o nbinstallagent logs on o target host.\n■ Confirm que o arquivo exists in its expected location e que o source e\no destination locations have appropriate permissions." + "full_action": "Perform the following as appropriate:\n■ Ensurethatthebpcdserviceisrunningintheremotehostandithasconnectivity\nto the media server.\n■ Ensure that NetBackup is properly installed.\n■ Confirm that recent backups ran successfully.\n■ Run a test backup.\n■ Confirm that the version of NetBackup being upgraded is supported.\n■ Verify that the transfer file exists and has the proper permissions.\n■ Identify the file being transferred by reviewing the admin logs on the server\nand the nbinstallagent logs on the target host.\n■ Confirm that the file exists in its expected location and that the source and\nthe destination locations have appropriate permissions." }, "7207": { "code": 7207, - "desc": "Não foi possível to receive o data from o cliente.", - "first_action": "Review o mídia servidor admin log como well como o cliente", - "full_action": "Review o mídia servidor admin log como well como o cliente\nnbinstallagent log at o seguinte locations:\nOn Windows: install_path\\NetBackup\\logs\\admin\\root*.log.\nOn UNIX: /usr/openv/netbackup/logs/admin/root*.log\nOn Windows: install_path\\NetBackup\\logs\\nbinstallagent\nOn UNIX: /usr/openv/netbackup/logs/nbinstallagent\nValidate connectivity between o target host e o staging host. Note que o\nstaging host may be o master servidor ou um mídia servidor que está named in o\ndeployment operation.\nTo configure o amount de time VxUpdate waits para processos to finish before\nreporting 7207 como o job status, you can define o TIMEOUT_SECONDS option. O\nfollowingvaluescanbedefinedintheNetBackupconfigurationonthemasterserver:\nVXUPDATE_CLIENT_READ_TIMEOUT_SECONDS This value controls how long precheck\noperations e cliente upgrade operations\nestão allowed to take, in seconds. O\ndefault value está 1800 (30 minutes). It can\nbe decreased to como little como 600 (10\nminutes)orincreasedtoasmuchas3600\n(60 minutes).\nVXUPDATE_SERVER_READ_TIMEOUT_SECONDS This value controls how long servidor\nupgrade operations estão allowed to take,\nin seconds. O default value está 2700 (45\nminutes). It can be decreased to como little\ncomo 600 (10 minutes) ou increased to como\nmuch como 5400 (90 minutes).\nPara details on how o bpsetconfig comando can be used to add values to o\nNetBackup configuration de um master servidor, veja o NetBackup Commands\nReference Guide." + "desc": "Unable to receive the data from the client.", + "first_action": "Review the media server admin log as well as the client", + "full_action": "Review the media server admin log as well as the client\nnbinstallagent log at the following locations:\nOn Windows: install_path\\NetBackup\\logs\\admin\\root*.log.\nOn UNIX: /usr/openv/netbackup/logs/admin/root*.log\nOn Windows: install_path\\NetBackup\\logs\\nbinstallagent\nOn UNIX: /usr/openv/netbackup/logs/nbinstallagent\nValidate connectivity between the target host and the staging host. Note that the\nstaging host may be the master server or a media server that is named in the\ndeployment operation.\nTo configure the amount of time VxUpdate waits for processes to finish before\nreporting 7207 as the job status, you can define the TIMEOUT_SECONDS option. The\nfollowingvaluescanbedefinedintheNetBackupconfigurationonthemasterserver:\nVXUPDATE_CLIENT_READ_TIMEOUT_SECONDS This value controls how long precheck\noperations and client upgrade operations\nare allowed to take, in seconds. The\ndefault value is 1800 (30 minutes). It can\nbe decreased to as little as 600 (10\nminutes)orincreasedtoasmuchas3600\n(60 minutes).\nVXUPDATE_SERVER_READ_TIMEOUT_SECONDS This value controls how long server\nupgrade operations are allowed to take,\nin seconds. The default value is 2700 (45\nminutes). It can be decreased to as little\nas 600 (10 minutes) or increased to as\nmuch as 5400 (90 minutes).\nFor details on how the bpsetconfig command can be used to add values to the\nNetBackup configuration of a master server, see the NetBackup Commands\nReference Guide." }, "7208": { "code": 7208, - "desc": "Um requerido arquivo não é possível be opened.", + "desc": "A required file cannot be opened.", "first_action": "NetBackup tmp", - "full_action": "Verifique que o usuário que está executando o nbmtrans mídia\nservidor process has permissão to ler o arquivos in o NetBackup directories. Users\nmust have ler permissions to o seguinte directories:\n■ NetBackup tmp\nOn Windows: install_path\\NetBackup\\Temp\nOn UNIX e Linux: /usr/openv/tmp\n■ NetBackup bin\nOn Windows: install_path\\NetBackup\\bin\nOn UNIX e Linux: /usr/openv/netbackup/bin\n■ NetBackup repo\nOn Windows: install_path\\NetBackup\\var\\global\\repo\nOn UNIX e Linux: /usr/openv/var/global/repo" + "full_action": "Verify that the user that is running the nbmtrans media\nserver process has permission to read the files in the NetBackup directories. Users\nmust have read permissions to the following directories:\n■ NetBackup tmp\nOn Windows: install_path\\NetBackup\\Temp\nOn UNIX and Linux: /usr/openv/tmp\n■ NetBackup bin\nOn Windows: install_path\\NetBackup\\bin\nOn UNIX and Linux: /usr/openv/netbackup/bin\n■ NetBackup repo\nOn Windows: install_path\\NetBackup\\var\\global\\repo\nOn UNIX and Linux: /usr/openv/var/global/repo" }, "7209": { "code": 7209, - "desc": "O deployment package foi não found ou foi inválido in o cache mídia servidor.", - "first_action": "Garanta que o package exists in o package repository", - "full_action": "Garanta que o package exists in o package repository\non o master servidor. Como part de o erro handling process, VxUpdate attempts to\nremove o inválido ou o corrupted package e replace it com o valid package." + "desc": "The deployment package was not found or was invalid in the cache media server.", + "first_action": "Ensure that the package exists in the package repository", + "full_action": "Ensure that the package exists in the package repository\non the master server. As part of the error handling process, VxUpdate attempts to\nremove the invalid or the corrupted package and replace it with the valid package." }, "7210": { "code": 7210, - "desc": "Não foi possível to gravar to o specified arquivo.", - "first_action": "Garanta que o diretório has o correct permissão.", - "full_action": "Garanta que o diretório has o correct permissão.\nNetBackup requires gravar e execute permissions para o target arquivo." + "desc": "Unable to write to the specified file.", + "first_action": "Ensure that the directory has the correct permission.", + "full_action": "Ensure that the directory has the correct permission.\nNetBackup requires write and execute permissions for the target file." }, "7211": { "code": 7211, - "desc": "Falhou to convert NetBackup version string.", - "first_action": "O version string que está returned from o remote host", - "full_action": "O version string que está returned from o remote host\nfoi não properly formatted. Por favor conectar to o remote host e verifique que\nNetBackup está instalado properly." + "desc": "Failed to convert NetBackup version string.", + "first_action": "The version string that is returned from the remote host", + "full_action": "The version string that is returned from the remote host\nwas not properly formatted. Please connect to the remote host and verify that\nNetBackup is installed properly." }, "7212": { "code": 7212, - "desc": "O nbinstallagent comando has executed com um vazio argument.", - "first_action": "Review o Job Manager log at o seguinte locations to", - "full_action": "Review o Job Manager log at o seguinte locations to\ngaranta que execute_nbinstallagent has o correct arguments:\nOn Windows: install_path\\NetBackup\\logs\\nbjm\nOn UNIX: /usr/openv/logs/nbjm" + "desc": "The nbinstallagent command has executed with an empty argument.", + "first_action": "Review the Job Manager log at the following locations to", + "full_action": "Review the Job Manager log at the following locations to\nensure that execute_nbinstallagent has the correct arguments:\nOn Windows: install_path\\NetBackup\\logs\\nbjm\nOn UNIX: /usr/openv/logs/nbjm" }, "7213": { "code": 7213, - "desc": "Não foi possível to identify remote host platform.", + "desc": "Unable to identify remote host platform.", "first_action": "Win_x64", - "full_action": "Garanta que o remote host has um supported version de\nNetBackup.\nFrom um NetBackup master ou mídia servidor, run\n/netbackup/bin/adminincmd/bptestbpcd -cliente -verbose. Review o PLATFORM key que this comando returns. This\ntarget host não é possível be upgraded if o PLATFORM key value está não in o seguinte list:\n■ win_x64\n■ linuxR_x86_2.6.18\n■ linuxR_x86_2.6.32\n■ linuxR_x86_3.10.0\n■ linuxR_x86_4.18.0\n■ linuxS_x86_2.6.16\n■ linuxS_x86_3.0.76\n■ linuxS_x86_4.4.73\n■ plinuxR_3.10.0\n■ plinuxR_4.18.0\n■ plinuxS_4.4.21\n■ plinuxS_5.3.18\n■ zlinuxR_2.6.18\n■ zlinuxR_2.6.32\n■ zlinuxR_3.10.0\n■ zlinuxR_4.18.0\n■ zlinuxS_3.0.76\n■ zlinuxS_4.4.\n■ zlinuxS_5.3.18\n■ rs6000_71\n■ solaris10\n■ solaris_x86_10_64" + "full_action": "Ensure that the remote host has a supported version of\nNetBackup.\nFrom a NetBackup master or media server, run\n/netbackup/bin/adminincmd/bptestbpcd -client -verbose. Review the PLATFORM key that this command returns. This\ntarget host cannot be upgraded if the PLATFORM key value is not in the following list:\n■ win_x64\n■ linuxR_x86_2.6.18\n■ linuxR_x86_2.6.32\n■ linuxR_x86_3.10.0\n■ linuxR_x86_4.18.0\n■ linuxS_x86_2.6.16\n■ linuxS_x86_3.0.76\n■ linuxS_x86_4.4.73\n■ plinuxR_3.10.0\n■ plinuxR_4.18.0\n■ plinuxS_4.4.21\n■ plinuxS_5.3.18\n■ zlinuxR_2.6.18\n■ zlinuxR_2.6.32\n■ zlinuxR_3.10.0\n■ zlinuxR_4.18.0\n■ zlinuxS_3.0.76\n■ zlinuxS_4.4.\n■ zlinuxS_5.3.18\n■ rs6000_71\n■ solaris10\n■ solaris_x86_10_64" }, "7214": { "code": 7214, - "desc": "Falhou to copy o specified arquivo.", - "first_action": "Ler permissions on o source arquivo.", - "full_action": "Confirm que o diretório has o correct permissions.\nNetBackup requires o seguinte permissions:\n■ Ler permissions on o source arquivo.\n■ Ler e execute permissions on o source diretório.\n■ Execute e gravar permissions on o target diretório.\nConfirm que there está enough disponível disco space at o arquivo copy destination.\nPara more informação, veja o nbrepo log on o master servidor e o admin log\non o staging servidor at o seguinte locations:\nOn Windows: install_path\\NetBackup\\logs.\nOn UNIX: /usr/openv/netbackup/logs" + "desc": "Failed to copy the specified file.", + "first_action": "Read permissions on the source file.", + "full_action": "Confirm that the directory has the correct permissions.\nNetBackup requires the following permissions:\n■ Read permissions on the source file.\n■ Read and execute permissions on the source directory.\n■ Execute and write permissions on the target directory.\nConfirm that there is enough available disk space at the file copy destination.\nFor more information, see the nbrepo log on the master server and the admin log\non the staging server at the following locations:\nOn Windows: install_path\\NetBackup\\logs.\nOn UNIX: /usr/openv/netbackup/logs" }, "7215": { "code": 7215, - "desc": "Falhou to stat VxUpdate package", - "first_action": "Confirm que o package has originated from um Cohesity", - "full_action": "Confirm que o package has originated from um Cohesity\nsourceandhasnotbeenalteredorcorrupted.Reviewthenbrepologonthemaster\nservidor para more informação." + "desc": "Failed to stat VxUpdate package", + "first_action": "Confirm that the package has originated from a Cohesity", + "full_action": "Confirm that the package has originated from a Cohesity\nsourceandhasnotbeenalteredorcorrupted.Reviewthenbrepologonthemaster\nserver for more information." }, "7216": { "code": 7216, - "desc": "O package name does não comply com VxUpdate package name standard.", - "first_action": "Confirm que o package name has não been modified.", - "full_action": "Confirm que o package name has não been modified.\nView o nbrepo log para details." + "desc": "The package name does not comply with VxUpdate package name standard.", + "first_action": "Confirm that the package name has not been modified.", + "full_action": "Confirm that the package name has not been modified.\nView the nbrepo log for details." }, "7217": { "code": 7217, - "desc": "O package repository location does não exist.", + "desc": "The package repository location does not exist.", "first_action": "Confirmthattherepositorydirectoryexistsatthefollowing", "full_action": "Confirmthattherepositorydirectoryexistsatthefollowing\nlocations:\nOn Windows: install_path\\var\\global\\repo\nOn UNIX: /usr/openv/var/global/repo" }, "7218": { "code": 7218, - "desc": "O package already exists in o repository.", - "first_action": "Confirm que o package que you desejar to add has não", - "full_action": "Confirm que o package que you desejar to add has não\nalready been added. To replace this package, first excluir it usando o nbrepo -d\ncomando." + "desc": "The package already exists in the repository.", + "first_action": "Confirm that the package that you want to add has not", + "full_action": "Confirm that the package that you want to add has not\nalready been added. To replace this package, first delete it using the nbrepo -d\ncommand." }, "7219": { "code": 7219, - "desc": "Inválido package ID", - "first_action": "O package ID must be um positive integer. Confirm que", - "full_action": "O package ID must be um positive integer. Confirm que\no package ID está correct por usando o nbrepo -l comando." + "desc": "Invalid package ID", + "first_action": "The package ID must be a positive integer. Confirm that", + "full_action": "The package ID must be a positive integer. Confirm that\nthe package ID is correct by using the nbrepo -l command." }, "7220": { "code": 7220, - "desc": "O deployment package foi não found in o package repository.", - "first_action": "Use o nbrepo -l comando to list o packages que", - "full_action": "Use o nbrepo -l comando to list o packages que\nestão currently in o repository." + "desc": "The deployment package was not found in the package repository.", + "first_action": "Use the nbrepo -l command to list the packages that", + "full_action": "Use the nbrepo -l command to list the packages that\nare currently in the repository." }, "7221": { "code": 7221, - "desc": "O package excluir operation foi canceled.", - "first_action": "To excluir um package, o usuário must confirm o excluir.", - "full_action": "To excluir um package, o usuário must confirm o excluir." + "desc": "The package delete operation was canceled.", + "first_action": "To delete a package, the user must confirm the delete.", + "full_action": "To delete a package, the user must confirm the delete." }, "7222": { "code": 7222, - "desc": "O package foi não found.", - "first_action": "Requerido VxUpdate package foi não found on o master servidor.", - "full_action": "Confirm que o package exists in o repository. Confirm\nque o package being instalado has não been modified from its original form.\nWhen um VMware ou Nutanix AHV agentless restauração está performed, o restauração can\ncause one de o seguinte issues:\n■ Requerido VxUpdate package foi não found on o master servidor.\nProvision VxUpdate packages para todos platforms para which you have virtual\nmachines onde you desejar to executar agentless recovery. Review o bpVMutil\nlog para additional assistance com this erro message.\nReview o seguinte if o falha está during um deployment ou um MongoDB job:\n■ Para um deployment job, review o nbrepo, admin, e nbinstallagent logs para\nadditional assistance com this erro message.\n■ Para MongoDB jobs, review o mongoDB logs para additional assistance com this\nerro message." + "desc": "The package was not found.", + "first_action": "Required VxUpdate package was not found on the master server.", + "full_action": "Confirm that the package exists in the repository. Confirm\nthat the package being installed has not been modified from its original form.\nWhen a VMware or Nutanix AHV agentless restore is performed, the restore can\ncause one of the following issues:\n■ Required VxUpdate package was not found on the master server.\nProvision VxUpdate packages for all platforms for which you have virtual\nmachines where you want to perform agentless recovery. Review the bpVMutil\nlog for additional assistance with this error message.\nReview the following if the failure is during a deployment or a MongoDB job:\n■ For a deployment job, review the nbrepo, admin, and nbinstallagent logs for\nadditional assistance with this error message.\n■ For MongoDB jobs, review the mongoDB logs for additional assistance with this\nerror message." }, "7223": { "code": 7223, - "desc": "O solicitado operation está não supported.", - "first_action": "Veja o NetBackup Upgrade Guide para informação about", - "full_action": "Veja o NetBackup Upgrade Guide para informação about\no supported operations e platforms para VxUpdate." + "desc": "The requested operation is not supported.", + "first_action": "See the NetBackup Upgrade Guide for information about", + "full_action": "See the NetBackup Upgrade Guide for information about\nthe supported operations and platforms for VxUpdate." }, "7224": { "code": 7224, - "desc": "Could não create um requerido arquivo ou diretório.", + "desc": "Could not create a required file or directory.", "first_action": "On Windows:", - "full_action": "O specific arquivo e caminho estão reported in o\nnbinstallagent log arquivo on o target host ou o admin log on o staging host.\nThenbinstallagentbinaryrequirestheabilitytocreatetemporaryfilesandfolders\nin both o NetBackup tmp e NetBackup bin directories.\nO nbmtrans binary requires o ability to create arquivos in o NetBackup repo\ndiretório.\nVeja o seguinte locations:\n■ On Windows:\ninstall_path\\NetBackup\\Temp\ninstall_path\\NetBackup\\bin\ninstall_path\\NetBackup\\var\\global\\repo\n■ On UNIX:\n/usr/openv/tmp\n/usr/openv/netbackup/bin\n/usr/openv/var/global/repo\nVerifique que o usuário executing o nbinstallagent e nbmtrans commands has\npermissiontocreatefilesandfoldersinthesedirectories.Verifythatthereissufficient\ndisco space in these directories." + "full_action": "The specific file and path are reported in the\nnbinstallagent log file on the target host or the admin log on the staging host.\nThenbinstallagentbinaryrequirestheabilitytocreatetemporaryfilesandfolders\nin both the NetBackup tmp and NetBackup bin directories.\nThe nbmtrans binary requires the ability to create files in the NetBackup repo\ndirectory.\nSee the following locations:\n■ On Windows:\ninstall_path\\NetBackup\\Temp\ninstall_path\\NetBackup\\bin\ninstall_path\\NetBackup\\var\\global\\repo\n■ On UNIX:\n/usr/openv/tmp\n/usr/openv/netbackup/bin\n/usr/openv/var/global/repo\nVerify that the user executing the nbinstallagent and nbmtrans commands has\npermissiontocreatefilesandfoldersinthesedirectories.Verifythatthereissufficient\ndisk space in these directories." }, "7225": { "code": 7225, - "desc": "Um specified arquivo ou diretório foi não found.", + "desc": "A specified file or directory was not found.", "first_action": "Confirmthatthefileexistsinthelocationspecified.Confirm", - "full_action": "Confirmthatthefileexistsinthelocationspecified.Confirm\nthatthepackagebeinginstalledhasnotbeenmodifiedfromitsoriginalform.Confirm\nque o NetBackup installation folder has não been corrupted.\nReview o nbinstallagent, nbrepo, e admin log arquivos para informação about o\nproblematic arquivos e their expected locations." + "full_action": "Confirmthatthefileexistsinthelocationspecified.Confirm\nthatthepackagebeinginstalledhasnotbeenmodifiedfromitsoriginalform.Confirm\nthat the NetBackup installation folder has not been corrupted.\nReview the nbinstallagent, nbrepo, and admin log files for information about the\nproblematic files and their expected locations." }, "7226": { "code": 7226, - "desc": "Um supporting comando falhou.", - "first_action": "Nbcheck.exe (o NetBackup preinstall environment checker)", - "full_action": "O nbinstallagent binary runs many commands como\npart de supporting various operations, including o seguinte:\n■ nbcheck.exe (o NetBackup preinstall environment checker)\n■ O NetBackup EEB installer\n■ NetBackup’s versioninfo comando in o goodies folder\n■ UNIX native packaging commands - rpm, installp, pkgadd, e swinstall.\n■ setup.exe - o NetBackup Windows setup utility\n■ gunzip - o UNIX tar uncompression utility\nO nbinstallagent logic relatórios o specific comando que falhou to execute.\nThisspecificerrorindicatesthatthecommanditselfcannotbeexecutedsuccessfully,\nwhich can be different than o comando executing successfully but returning um\nerror.Possiblecausesincludepermissionsissuesandfilesorfoldersunexpectedly\nabsent from o remote host. Review o nbinstallagent log arquivo on o target\nhost." + "desc": "A supporting command failed.", + "first_action": "Nbcheck.exe (the NetBackup preinstall environment checker)", + "full_action": "The nbinstallagent binary runs many commands as\npart of supporting various operations, including the following:\n■ nbcheck.exe (the NetBackup preinstall environment checker)\n■ The NetBackup EEB installer\n■ NetBackup’s versioninfo command in the goodies folder\n■ UNIX native packaging commands - rpm, installp, pkgadd, and swinstall.\n■ setup.exe - the NetBackup Windows setup utility\n■ gunzip - the UNIX tar uncompression utility\nThe nbinstallagent logic reports the specific command that failed to execute.\nThisspecificerrorindicatesthatthecommanditselfcannotbeexecutedsuccessfully,\nwhich can be different than the command executing successfully but returning an\nerror.Possiblecausesincludepermissionsissuesandfilesorfoldersunexpectedly\nabsent from the remote host. Review the nbinstallagent log file on the target\nhost." }, "7227": { "code": 7227, - "desc": "Não é possível abrir nbinstallagent log arquivo.", - "first_action": "Verifique que o usuário executing o nbinstallagent binary", - "full_action": "Verifique que o usuário executing o nbinstallagent binary\nhas permissão to gravar to NetBackup's log folder. Verifique que there está sufficient disco\nspace on o system." + "desc": "Cannot open nbinstallagent log file.", + "first_action": "Verify that the user executing the nbinstallagent binary", + "full_action": "Verify that the user executing the nbinstallagent binary\nhas permission to write to NetBackup's log folder. Verify that there is sufficient disk\nspace on the system." }, "7228": { "code": 7228, - "desc": "Installation de o target package foi unsuccessful.", - "first_action": "Review o installation log para o target package.", - "full_action": "Review o installation log para o target package.\nWhen you install NetBackup packages para UNIX, o installation log está located at\n/usr/openv/tmp.\nWhen you install NetBackup packages para Windows, o installation log está located\nat %ALLUSERSPROFILE%\\Veritas\\NetBackup\\InstallLogs.\nPara additional informação on installing EEBs como well como logs from o EEB\ninstallation, veja o related article:\nhttps://www.veritas.com/support/en_US/article.100019405" + "desc": "Installation of the target package was unsuccessful.", + "first_action": "Review the installation log for the target package.", + "full_action": "Review the installation log for the target package.\nWhen you install NetBackup packages for UNIX, the installation log is located at\n/usr/openv/tmp.\nWhen you install NetBackup packages for Windows, the installation log is located\nat %ALLUSERSPROFILE%\\Veritas\\NetBackup\\InstallLogs.\nFor additional information on installing EEBs as well as logs from the EEB\ninstallation, see the related article:\nhttps://www.veritas.com/support/en_US/article.100019405" }, "7229": { "code": 7229, "desc": "Couldnotcopynbinstallagenttodestinationpathaspartofself-update process.", - "first_action": "Verifique que o usuário executing nbinstallagent has", - "full_action": "Verifique que o usuário executing nbinstallagent has\npermissão to gravar to o NetBackup directories. Verifique que there está sufficient disco\nspace on o system." + "first_action": "Verify that the user executing nbinstallagent has", + "full_action": "Verify that the user executing nbinstallagent has\npermission to write to the NetBackup directories. Verify that there is sufficient disk\nspace on the system." }, "7230": { "code": 7230, - "desc": "Could não execute nbinstallagent from new caminho.", - "first_action": "Verifique que o usuário executing o nbinstallagent binary", - "full_action": "Verifique que o usuário executing o nbinstallagent binary\nhas permissão to execute arquivos within o NetBackup directories." + "desc": "Could not execute nbinstallagent from new path.", + "first_action": "Verify that the user executing the nbinstallagent binary", + "full_action": "Verify that the user executing the nbinstallagent binary\nhas permission to execute files within the NetBackup directories." }, "7231": { "code": 7231, - "desc": "Could não abrir um requerido registry key.", + "desc": "Could not open a required registry key.", "first_action": "Verifythattheuserexecutingthebinaryhasadministrative", - "full_action": "Verifythattheuserexecutingthebinaryhasadministrative\nprivileges. Verifique que NetBackup’s registry informação at\nHKEY_LOCAL_MACHINE\\SOFTWARE\\Veritas\\NetBackup está não corrupt ou missing." + "full_action": "Verifythattheuserexecutingthebinaryhasadministrative\nprivileges. Verify that NetBackup’s registry information at\nHKEY_LOCAL_MACHINE\\SOFTWARE\\Veritas\\NetBackup is not corrupt or missing." }, "7232": { "code": 7232, - "desc": "Could não query registry value.", - "first_action": "Verifique que o usuário executing o nbinstallagent e", - "full_action": "Verifique que o usuário executing o nbinstallagent e\nnbhostdbcmdbinarieshasadministrativeprivileges.VerifythatNetBackup’sregistry\ninformationatHKEY_LOCAL_MACHINE\\SOFTWARE\\Veritas\\NetBackupisnotcorrupt\nou missing." + "desc": "Could not query registry value.", + "first_action": "Verify that the user executing the nbinstallagent and", + "full_action": "Verify that the user executing the nbinstallagent and\nnbhostdbcmdbinarieshasadministrativeprivileges.VerifythatNetBackup’sregistry\ninformationatHKEY_LOCAL_MACHINE\\SOFTWARE\\Veritas\\NetBackupisnotcorrupt\nor missing." }, "7233": { "code": 7233, - "desc": "Could não resolve o caminho to um NetBackup diretório.", - "first_action": "Verifique que o usuário executing o nbinstallagent binary", - "full_action": "Verifique que o usuário executing o nbinstallagent binary\nhasreadprivilegesontheNetBackupapplicationfolders.VerifythattheNetBackup\napplication folder está não corrupt ou missing." + "desc": "Could not resolve the path to a NetBackup directory.", + "first_action": "Verify that the user executing the nbinstallagent binary", + "full_action": "Verify that the user executing the nbinstallagent binary\nhasreadprivilegesontheNetBackupapplicationfolders.VerifythattheNetBackup\napplication folder is not corrupt or missing." }, "7234": { "code": 7234, - "desc": "Could não remove o nbinstallagent binary’s configuration arquivo.", + "desc": "Could not remove the nbinstallagent binary’s configuration file.", "first_action": "Windows:", - "full_action": "Verifique que o usuário executing o nbinstallagent binary\nhas gravar privileges on NetBackup’s application folders. O nbinstallagent\nconfiguration informação resides in NetBackup’s tmp diretório e está named\nnbinstallagent_conffile.\nLocation de tmp diretório:\n■ Windows:\ninstall_path\\NetBackup\\Temp\n■ UNIX:\n/usr/openv/tmp" + "full_action": "Verify that the user executing the nbinstallagent binary\nhas write privileges on NetBackup’s application folders. The nbinstallagent\nconfiguration information resides in NetBackup’s tmp directory and is named\nnbinstallagent_conffile.\nLocation of tmp directory:\n■ Windows:\ninstall_path\\NetBackup\\Temp\n■ UNIX:\n/usr/openv/tmp" }, "7235": { "code": 7235, - "desc": "Falhou to abrir ou extract um package.", - "first_action": "O specific arquivo que não é possível be operated on está reported in", - "full_action": "O specific arquivo que não é possível be operated on está reported in\no nbinstallagent ou nbrepo log arquivo. Confirm que o package exists in o\nrequerido location. Confirm que o package being instalado has não been modified\nfrom its original form. Verifique que o usuário executing o nbinstallagent binary\nhasreadandwritepermissionsforNetBackup'sapplicationfolders.Verifythatthere\nestá sufficient disco space on o system." + "desc": "Failed to open or extract a package.", + "first_action": "The specific file that cannot be operated on is reported in", + "full_action": "The specific file that cannot be operated on is reported in\nthe nbinstallagent or nbrepo log file. Confirm that the package exists in the\nrequired location. Confirm that the package being installed has not been modified\nfrom its original form. Verify that the user executing the nbinstallagent binary\nhasreadandwritepermissionsforNetBackup'sapplicationfolders.Verifythatthere\nis sufficient disk space on the system." }, "7236": { "code": 7236, - "desc": "O package signature está inválido.", - "first_action": "Confirm que o package has come from um legitimate", - "full_action": "Confirm que o package has come from um legitimate\nCohesity source e has não been altered ou manipulated." + "desc": "The package signature is invalid.", + "first_action": "Confirm that the package has come from a legitimate", + "full_action": "Confirm that the package has come from a legitimate\nCohesity source and has not been altered or manipulated." }, "7237": { "code": 7237, - "desc": "O public key foi não found at o expected location.", - "first_action": "O default location para o public key está at o seguinte", - "full_action": "O default location para o public key está at o seguinte\nlocations:\nOn Windows: install_path\\NetBackup\\var\\VxUpdate\\pubkey.pem\nOn UNIX e Linux: /usr/openv/var/global/vxupdate/pubkey.pem\nThis arquivo está included com o NetBackup Cliente e o NetBackup servidor 8.1.2 e\nlater packages. Verifique que o usuário executing o nbinstallagent, nbrepo, e\nbpvmutil binaries have ler privileges para NetBackup’s application folders. Verifique\nque NetBackup’s application folders estão não corrupt ou missing." + "desc": "The public key was not found at the expected location.", + "first_action": "The default location for the public key is at the following", + "full_action": "The default location for the public key is at the following\nlocations:\nOn Windows: install_path\\NetBackup\\var\\VxUpdate\\pubkey.pem\nOn UNIX and Linux: /usr/openv/var/global/vxupdate/pubkey.pem\nThis file is included with the NetBackup Client and the NetBackup server 8.1.2 and\nlater packages. Verify that the user executing the nbinstallagent, nbrepo, and\nbpvmutil binaries have read privileges for NetBackup’s application folders. Verify\nthat NetBackup’s application folders are not corrupt or missing." }, "7238": { "code": 7238, - "desc": "Windows socket initialization foi unsuccessful.", - "first_action": "This erro está um sign de um socket ou networking issue on o", - "full_action": "This erro está um sign de um socket ou networking issue on o\nremotehost.Formoreinformation,seetheMSDNdocumentationforWSAStartup()\nat o seguinte location:\nhttps://docs.microsoft.com/en-us/windows/win32/api/winsock/nf-winsock-wsastartup" + "desc": "Windows socket initialization was unsuccessful.", + "first_action": "This error is a sign of a socket or networking issue on the", + "full_action": "This error is a sign of a socket or networking issue on the\nremotehost.Formoreinformation,seetheMSDNdocumentationforWSAStartup()\nat the following location:\nhttps://docs.microsoft.com/en-us/windows/win32/api/winsock/nf-winsock-wsastartup" }, "7239": { "code": 7239, - "desc": "Excedido time-out waiting para Windows socket initialization.", + "desc": "Exceeded time-out waiting for Windows socket initialization.", "first_action": "Thenbinstallagentbinarywaitsamaximumof2minutes", - "full_action": "Thenbinstallagentbinarywaitsamaximumof2minutes\npara o socket initialization to complete. This erro está from um socket ou networking\nissue on o remote host. Para more informação, veja o MSDN documentation para\nWSAStartup() at o seguinte location:\nhttps://docs.microsoft.com/en-us/windows/win32/api/winsock/nf-winsock-wsastartup" + "full_action": "Thenbinstallagentbinarywaitsamaximumof2minutes\nfor the socket initialization to complete. This error is from a socket or networking\nissue on the remote host. For more information, see the MSDN documentation for\nWSAStartup() at the following location:\nhttps://docs.microsoft.com/en-us/windows/win32/api/winsock/nf-winsock-wsastartup" }, "7240": { "code": 7240, - "desc": "O Winsock version está unsupported.", - "first_action": "This erro está from um socket ou networking issue on o", - "full_action": "This erro está from um socket ou networking issue on o\nremotehost.ItmaybeasymptomofattemptingtouseVxUpdateonanunsupported\nversion de Windows. Para more informação, veja o MSDN documentation para\nWSAStartup() e, specifically, o WSAVERNOTSUPPORTED return code at o\nseguinte location:\nhttps://docs.microsoft.com/en-us/windows/win32/api/winsock/nf-winsock-wsastartup" + "desc": "The Winsock version is unsupported.", + "first_action": "This error is from a socket or networking issue on the", + "full_action": "This error is from a socket or networking issue on the\nremotehost.ItmaybeasymptomofattemptingtouseVxUpdateonanunsupported\nversion of Windows. For more information, see the MSDN documentation for\nWSAStartup() and, specifically, the WSAVERNOTSUPPORTED return code at the\nfollowing location:\nhttps://docs.microsoft.com/en-us/windows/win32/api/winsock/nf-winsock-wsastartup" }, "7241": { "code": 7241, - "desc": "Could não initialize socket.", - "first_action": "This erro can happen if um operating system function to", - "full_action": "This erro can happen if um operating system function to\naccess ou change o settings para o standard output socket está unsuccessful. O\nnbinstallagent log arquivo relatórios o specific operating system call que falhou, along\ncom um OS-specific erro code." + "desc": "Could not initialize socket.", + "first_action": "This error can happen if an operating system function to", + "full_action": "This error can happen if an operating system function to\naccess or change the settings for the standard output socket is unsuccessful. The\nnbinstallagent log file reports the specific operating system call that failed, along\nwith an OS-specific error code." }, "7242": { "code": 7242, - "desc": "Falhou to add package to o repository.", - "first_action": "Review o nbwebservice log para related messages e", - "full_action": "Review o nbwebservice log para related messages e\nadditional details. Confirm o package (.sja arquivo) está não corrupted e came from\num legitimate source. Confirm que um usuário com appropriate privileges performed o\nVxUpdate operation. Confirm there está adequate disco space on o drive ou volume\nonde o NetBackup application folder resides." + "desc": "Failed to add package to the repository.", + "first_action": "Review the nbwebservice log for related messages and", + "full_action": "Review the nbwebservice log for related messages and\nadditional details. Confirm the package (.sja file) is not corrupted and came from\na legitimate source. Confirm that a user with appropriate privileges performed the\nVxUpdate operation. Confirm there is adequate disk space on the drive or volume\nwhere the NetBackup application folder resides." }, "7243": { "code": 7243, - "desc": "Temporary arquivos não é possível be removed from o system.", + "desc": "Temporary files cannot be removed from the system.", "first_action": "Thenbinstallagentbinaryattemptstocleanupthetemp", - "full_action": "Thenbinstallagentbinaryattemptstocleanupthetemp\narquivos at o beginning e o end de its execution. Verifique que o usuário executing\nnbinstallagenthasreadandwritepermissionsforNetBackup'sapplicationfolders.\nVerifique que other system processos do não maintain handles to NetBackup arquivos.\nOn Windows: install_path\\NetBackup\\Temp\nOn UNIX e Linux: /usr/openv/tmp" + "full_action": "Thenbinstallagentbinaryattemptstocleanupthetemp\nfiles at the beginning and the end of its execution. Verify that the user executing\nnbinstallagenthasreadandwritepermissionsforNetBackup'sapplicationfolders.\nVerify that other system processes do not maintain handles to NetBackup files.\nOn Windows: install_path\\NetBackup\\Temp\nOn UNIX and Linux: /usr/openv/tmp" }, "7245": { "code": 7245, - "desc": "Um unsupported self-update operation foi attempted.", - "first_action": "Verifique que o NetBackup application folder está in um clean", - "full_action": "Verifique que o NetBackup application folder está in um clean\nstate. If o nbinstallagent não é possível clean up temporary arquivos como part de previous\noperations, o falha to remove leftover temporary arquivos may be responsible para\nthis erro." + "desc": "An unsupported self-update operation was attempted.", + "first_action": "Verify that the NetBackup application folder is in a clean", + "full_action": "Verify that the NetBackup application folder is in a clean\nstate. If the nbinstallagent cannot clean up temporary files as part of previous\noperations, the failure to remove leftover temporary files may be responsible for\nthis error." }, "7246": { "code": 7246, - "desc": "Um unsupported registry query foi attempted.", - "first_action": "This erro can happen if um NetBackup registry value foi", - "full_action": "This erro can happen if um NetBackup registry value foi\nmodified from its original type to another type. Para example, if um usuário changed\nHKEY_LOCAL_MACHINE\\SOFTWARE\\Veritas\\NetBackup\\CurrentVersion\\INSTALLDIR\nfromaREG_SZtype(string)toREG_DWORD(integer).ConfirmthatNetBackup'sregistry\nhas não been altered ou corrupted." + "desc": "An unsupported registry query was attempted.", + "first_action": "This error can happen if a NetBackup registry value was", + "full_action": "This error can happen if a NetBackup registry value was\nmodified from its original type to another type. For example, if a user changed\nHKEY_LOCAL_MACHINE\\SOFTWARE\\Veritas\\NetBackup\\CurrentVersion\\INSTALLDIR\nfromaREG_SZtype(string)toREG_DWORD(integer).ConfirmthatNetBackup'sregistry\nhas not been altered or corrupted." }, "7247": { "code": 7247, - "desc": "Could não abrir um pipe to capture comando output.", - "first_action": "Verifique que o usuário executing o nbinstallagent ou", - "full_action": "Verifique que o usuário executing o nbinstallagent ou\nnbhostdbcmd binaries has administrative privileges." + "desc": "Could not open a pipe to capture command output.", + "first_action": "Verify that the user executing the nbinstallagent or", + "full_action": "Verify that the user executing the nbinstallagent or\nnbhostdbcmd binaries has administrative privileges." }, "7248": { "code": 7248, - "desc": "O NetBackup comando to retrieve version informação está não present.", - "first_action": "O default location para o versioninfo comando está at", - "full_action": "O default location para o versioninfo comando está at\no seguinte locations:\nOn Windows: install_path\\NetBackup\\bin\\goodies\\versioninfo.exe\nOn UNIX: /usr/openv/netbackup/bin/goodies/support/versioninfo\nConfirm que NetBackup’s application folder has não been altered ou corrupted." + "desc": "The NetBackup command to retrieve version information is not present.", + "first_action": "The default location for the versioninfo command is at", + "full_action": "The default location for the versioninfo command is at\nthe following locations:\nOn Windows: install_path\\NetBackup\\bin\\goodies\\versioninfo.exe\nOn UNIX: /usr/openv/netbackup/bin/goodies/support/versioninfo\nConfirm that NetBackup’s application folder has not been altered or corrupted." }, "7249": { "code": 7249, - "desc": "Could não abrir process para reading.", - "first_action": "O nbinstallagent found um NetBackup process to be", - "full_action": "O nbinstallagent found um NetBackup process to be\nexecutando, but não é possível abrir it para further processing. Verifique que o usuário executing\no nbinstallagent binary has administrative privileges. Verifique que o existing\nNetBackup processos estão executando under o expected usuário accounts." + "desc": "Could not open process for reading.", + "first_action": "The nbinstallagent found a NetBackup process to be", + "full_action": "The nbinstallagent found a NetBackup process to be\nrunning, but cannot open it for further processing. Verify that the user executing\nthe nbinstallagent binary has administrative privileges. Verify that the existing\nNetBackup processes are running under the expected user accounts." }, "7250": { "code": 7250, - "desc": "Process status não é possível be determined.", - "first_action": "Verifique que o usuário executing o nbinstallagent ou", - "full_action": "Verifique que o usuário executing o nbinstallagent ou\nnbhostdbcmd binaries have administrative privileges. Verifique que o existing\nNetBackup processos estão executando under o expected usuário accounts. Review o\nnbinstallagent e nbhostdbcmd log arquivos to determinar what comando foi run\ne its output." + "desc": "Process status cannot be determined.", + "first_action": "Verify that the user executing the nbinstallagent or", + "full_action": "Verify that the user executing the nbinstallagent or\nnbhostdbcmd binaries have administrative privileges. Verify that the existing\nNetBackup processes are running under the expected user accounts. Review the\nnbinstallagent and nbhostdbcmd log files to determine what command was run\nand its output." }, "7251": { "code": 7251, - "desc": "Process não é possível be stopped.", - "first_action": "Um particular NetBackup process não é possível be terminated.", - "full_action": "Um particular NetBackup process não é possível be terminated.\nO nbinstallagent log arquivo relatórios o specific process. Verifique que o usuário\nexecuting o nbinstallagent binary has administrative privileges. Verifique que o\nexisting NetBackup processos estão executando under o expected usuário accounts." + "desc": "Process cannot be stopped.", + "first_action": "A particular NetBackup process cannot be terminated.", + "full_action": "A particular NetBackup process cannot be terminated.\nThe nbinstallagent log file reports the specific process. Verify that the user\nexecuting the nbinstallagent binary has administrative privileges. Verify that the\nexisting NetBackup processes are running under the expected user accounts." }, "7252": { "code": 7252, - "desc": "O attempt to extract um package foi unsuccessful.", + "desc": "The attempt to extract a package was unsuccessful.", "first_action": "Theissuecanoccurinbothnbinstallagentandnbrepo.", - "full_action": "Theissuecanoccurinbothnbinstallagentandnbrepo.\nReview o associated log arquivos para o name de o problematic arquivo e other\ninformation.VerifythattheuserhaswritepermissionsfortheNetBackupapplication\nfoldersonthemasterserverandtargethost.Verifythatthereissufficientdiskspace\non o master servidor e target." + "full_action": "Theissuecanoccurinbothnbinstallagentandnbrepo.\nReview the associated log files for the name of the problematic file and other\ninformation.VerifythattheuserhaswritepermissionsfortheNetBackupapplication\nfoldersonthemasterserverandtargethost.Verifythatthereissufficientdiskspace\non the master server and target." }, "7253": { "code": 7253, - "desc": "O package está vazio.", - "first_action": "Confirm que o package originated from um Cohesity", - "full_action": "Confirm que o package originated from um Cohesity\nsource e has não been altered ou corrupted." + "desc": "The package is empty.", + "first_action": "Confirm that the package originated from a Cohesity", + "full_action": "Confirm that the package originated from a Cohesity\nsource and has not been altered or corrupted." }, "7254": { "code": 7254, - "desc": "Data in process foi formatted incorrectly.", - "first_action": "O prechecker uses this size como part de its disco space", - "full_action": "O prechecker uses this size como part de its disco space\nreview. This particular status code indicates que o content de o package_sizes\narquivo está in um unexpected format. Confirm que o prechecker package originated\nfrom um Cohesity source e has não been altered ou corrupted." + "desc": "Data in process was formatted incorrectly.", + "first_action": "The prechecker uses this size as part of its disk space", + "full_action": "The prechecker uses this size as part of its disk space\nreview. This particular status code indicates that the content of the package_sizes\nfile is in an unexpected format. Confirm that the prechecker package originated\nfrom a Cohesity source and has not been altered or corrupted." }, "7255": { "code": 7255, - "desc": "Um supporting command’s output foi in um unexpected format.", - "first_action": "Review o nbinstallagent logs to determinar which", - "full_action": "Review o nbinstallagent logs to determinar which\ncomando produced o unexpected output." + "desc": "A supporting command’s output was in an unexpected format.", + "first_action": "Review the nbinstallagent logs to determine which", + "full_action": "Review the nbinstallagent logs to determine which\ncommand produced the unexpected output." }, "7256": { "code": 7256, - "desc": "Could não get o current working diretório caminho.", + "desc": "Could not get the current working directory path.", "first_action": "Collectthenbinstallagentlogsatthefollowinglocations", - "full_action": "Collectthenbinstallagentlogsatthefollowinglocations\npara o remote host:\nOn Windows: install_path\\NetBackup\\logs\nOn UNIX e Linux: /usr/openv/netbackup/logs\nSave todos logs e contate Cohesity Technical Support." + "full_action": "Collectthenbinstallagentlogsatthefollowinglocations\nfor the remote host:\nOn Windows: install_path\\NetBackup\\logs\nOn UNIX and Linux: /usr/openv/netbackup/logs\nSave all logs and contact Cohesity Technical Support." }, "7258": { "code": 7258, - "desc": "Could não determinar o state de security certificates on o local host.", - "first_action": "Review o nbinstallagent log para um copy de o exact", - "full_action": "Review o nbinstallagent log para um copy de o exact\ncomando line executed, its return status, e its output. Consult o NetBackup\nComando Reference Guide para informação on o specific erro." + "desc": "Could not determine the state of security certificates on the local host.", + "first_action": "Review the nbinstallagent log for a copy of the exact", + "full_action": "Review the nbinstallagent log for a copy of the exact\ncommand line executed, its return status, and its output. Consult the NetBackup\nCommand Reference Guide for information on the specific error." }, "7259": { "code": 7259, - "desc": "O deployment policy's external CA certificate configuration specifications estão inválido para this host.", - "first_action": "Para Windows, o nbcertcmdtool logs estão located in o normal install log", - "full_action": "Para more details about this erro, examine o\nnbcertcmdtoollogs.Thenbinstallagentlogreportsthenbcertcmdtoolcommand\nline arguments e output.\n■ Para Windows, o nbcertcmdtool logs estão located in o normal install log\nlocation (which defaults to\n%ALLUSERSPROFILE%\\Veritas\\NetBackup\\InstallLogs). Um separate arquivo está\ncreated para each comando run e o arquivos you desejar to review estão prefixed\ncom ExternalCertificateOp.\n■ Para UNIX, these estão in /usr/openv/tmp/ e o name está prefixed com\ninstall_commands. O PID está appended e para example, um arquivo name can be\n/usr/openv/tmp/install_commands.47832\nPara more informação, veja o NetBackup API Reference Guide.\nReview o external CA certificate values que estão defined in o deployment policy\n(ou o nbinstallcmd comando line) to garanta que they apply to o target host.\nReview o nbinstallagent log para um record de o NetBackup comando que está\nexecuted to resolve o external CA certificate. Review o NetBackup Security\ne Encryption Guide para more informação on how to configure um NetBackup\nenvironment para use com external CA certificates." + "desc": "The deployment policy's external CA certificate configuration specifications are invalid for this host.", + "first_action": "For Windows, the nbcertcmdtool logs are located in the normal install log", + "full_action": "For more details about this error, examine the\nnbcertcmdtoollogs.Thenbinstallagentlogreportsthenbcertcmdtoolcommand\nline arguments and output.\n■ For Windows, the nbcertcmdtool logs are located in the normal install log\nlocation (which defaults to\n%ALLUSERSPROFILE%\\Veritas\\NetBackup\\InstallLogs). A separate file is\ncreated for each command run and the files you want to review are prefixed\nwith ExternalCertificateOp.\n■ For UNIX, these are in /usr/openv/tmp/ and the name is prefixed with\ninstall_commands. The PID is appended and for example, a file name can be\n/usr/openv/tmp/install_commands.47832\nFor more information, see the NetBackup API Reference Guide.\nReview the external CA certificate values that are defined in the deployment policy\n(or the nbinstallcmd command line) to ensure that they apply to the target host.\nReview the nbinstallagent log for a record of the NetBackup command that is\nexecuted to resolve the external CA certificate. Review the NetBackup Security\nand Encryption Guide for more information on how to configure a NetBackup\nenvironment for use with external CA certificates." }, "7260": { "code": 7260, "desc": "CouldnotparsetheJSONstringtoretrievetheexternalcertificatevalues.", - "first_action": "Review o admin log on o mídia servidor (ou master", - "full_action": "Review o admin log on o mídia servidor (ou master\nservidor if um mídia servidor foi não used) para additional informação. In o JSON\nreferencedthere,lookforcommonoffenders-pathswithspaces,excessivequotes,\ne non-English characters. Review NetBackup documentation para details on\nsupported characters in policy values." + "first_action": "Review the admin log on the media server (or master", + "full_action": "Review the admin log on the media server (or master\nserver if a media server was not used) for additional information. In the JSON\nreferencedthere,lookforcommonoffenders-pathswithspaces,excessivequotes,\nand non-English characters. Review NetBackup documentation for details on\nsupported characters in policy values." }, "7261": { "code": 7261, - "desc": "Could não load o JSON string.", - "first_action": "Review o admin log on o mídia servidor (ou master", - "full_action": "Review o admin log on o mídia servidor (ou master\nservidor if um mídia servidor foi não used) para additional informação. In o JSON\nreferencedthere,lookforcommonoffenders-pathswithspaces,excessivequotes,\ne non-English characters. Review NetBackup documentation para details on\nsupported characters in policy values." + "desc": "Could not load the JSON string.", + "first_action": "Review the admin log on the media server (or master", + "full_action": "Review the admin log on the media server (or master\nserver if a media server was not used) for additional information. In the JSON\nreferencedthere,lookforcommonoffenders-pathswithspaces,excessivequotes,\nand non-English characters. Review NetBackup documentation for details on\nsupported characters in policy values." }, "7262": { "code": 7262, - "desc": "Could não determinar o CA certificate type que está configurado on o master servidor.", - "first_action": "Confirm que o master servidor e cliente communicate", - "full_action": "Confirm que o master servidor e cliente communicate\nsuccessfully. Review o nbinstallagent log para um copy de o exact comando\nline executed, its return status, e its output. Consult o NetBackup Commands\nReference Guide para informação on o specific erro." + "desc": "Could not determine the CA certificate type that is configured on the master server.", + "first_action": "Confirm that the master server and client communicate", + "full_action": "Confirm that the master server and client communicate\nsuccessfully. Review the nbinstallagent log for a copy of the exact command\nline executed, its return status, and its output. Consult the NetBackup Commands\nReference Guide for information on the specific error." }, "7263": { "code": 7263, - "desc": "There está insufficient disco space disponível to complete o operation.", - "first_action": "Liberar up space on o disco onde o NetBackup package", - "full_action": "Liberar up space on o disco onde o NetBackup package\nrepository está located e retry o operation." + "desc": "There is insufficient disk space available to complete the operation.", + "first_action": "Free up space on the disk where the NetBackup package", + "full_action": "Free up space on the disk where the NetBackup package\nrepository is located and retry the operation." }, "7264": { "code": 7264, - "desc": "Package release version está não supported.", - "first_action": "Confirm que you have downloaded o appropriate", - "full_action": "Confirm que you have downloaded o appropriate\nVxUpdate SJA package para seu environment." + "desc": "Package release version is not supported.", + "first_action": "Confirm that you have downloaded the appropriate", + "full_action": "Confirm that you have downloaded the appropriate\nVxUpdate SJA package for your environment." }, "7265": { "code": 7265, - "desc": "Package type está inválido.", - "first_action": "Confirm que you have downloaded o appropriate", - "full_action": "Confirm que you have downloaded o appropriate\nVxUpdate SJA package para seu environment." + "desc": "Package type is invalid.", + "first_action": "Confirm that you have downloaded the appropriate", + "full_action": "Confirm that you have downloaded the appropriate\nVxUpdate SJA package for your environment." }, "7266": { "code": 7266, - "desc": "Package operating system está não supported.", - "first_action": "Confirm que you have downloaded o appropriate", - "full_action": "Confirm que you have downloaded o appropriate\nVxUpdate SJA package para seu environment." + "desc": "Package operating system is not supported.", + "first_action": "Confirm that you have downloaded the appropriate", + "full_action": "Confirm that you have downloaded the appropriate\nVxUpdate SJA package for your environment." }, "7267": { "code": 7267, - "desc": "Package EEB version está não supported.", - "first_action": "Confirm que you have downloaded o appropriate", - "full_action": "Confirm que you have downloaded o appropriate\nVxUpdate SJA package para seu environment." + "desc": "Package EEB version is not supported.", + "first_action": "Confirm that you have downloaded the appropriate", + "full_action": "Confirm that you have downloaded the appropriate\nVxUpdate SJA package for your environment." }, "7268": { "code": 7268, - "desc": "EEB install está não supported. NetBackup status codes 897 NetBackup status codes", - "first_action": "You não é possível install servidor EEB on um cliente system. Verifique", - "full_action": "You não é possível install servidor EEB on um cliente system. Verifique\nque o target host está um cliente e o type de EEB being instalado está um cliente EEB.\nPara more informação, review o EEB documentation para proper installation." + "desc": "EEB install is not supported. NetBackup status codes 897 NetBackup status codes", + "first_action": "You cannot install server EEB on a client system. Verify", + "full_action": "You cannot install server EEB on a client system. Verify\nthat the target host is a client and the type of EEB being installed is a client EEB.\nFor more information, review the EEB documentation for proper installation." }, "7269": { "code": 7269, - "desc": "Found active NetBackup jobs on o target host.", - "first_action": "Review o activity monitor to determinar which jobs estão", - "full_action": "Review o activity monitor to determinar which jobs estão\nexecutando on o target mídia servidor. Wait until o jobs estão complete on o target\nmídia servidor e run o VxUpdate job again." + "desc": "Found active NetBackup jobs on the target host.", + "first_action": "Review the activity monitor to determine which jobs are", + "full_action": "Review the activity monitor to determine which jobs are\nrunning on the target media server. Wait until the jobs are complete on the target\nmedia server and run the VxUpdate job again." }, "7270": { "code": 7270, - "desc": "There estão não existing security certificates on o host.", - "first_action": "In o deployment job, supply ECA values instead de", - "full_action": "In o deployment job, supply ECA values instead de\nselecting o Use existing certificates when possible option." + "desc": "There are no existing security certificates on the host.", + "first_action": "In the deployment job, supply ECA values instead of", + "full_action": "In the deployment job, supply ECA values instead of\nselecting the Use existing certificates when possible option." }, "7271": { "code": 7271, - "desc": "O initialization de o nbcertcmdtool utility falhou.", - "first_action": "Validate que o VxUpdate packages estão não corrupted.", - "full_action": "Validate que o VxUpdate packages estão não corrupted.\nReview o target host’s NetBackup temp diretório para remnants de older\nnbcertcmdtool arquivos." + "desc": "The initialization of the nbcertcmdtool utility failed.", + "first_action": "Validate that the VxUpdate packages are not corrupted.", + "full_action": "Validate that the VxUpdate packages are not corrupted.\nReview the target host’s NetBackup temp directory for remnants of older\nnbcertcmdtool files." }, "7272": { "code": 7272, - "desc": "O preinstallation checks falhou.", - "first_action": "Review o nbinstallagent logs to determinar if there", - "full_action": "Review o nbinstallagent logs to determinar if there\nfoi um problema executing nbcheck. If não, review o output from nbcheck to\ndeterminar which verifique has falhou. Note que apenas critical checks can cause o\ninstallation to fail. Correct o condition que o preinstall checker displays e\nre-run o job." + "desc": "The preinstallation checks failed.", + "first_action": "Review the nbinstallagent logs to determine if there", + "full_action": "Review the nbinstallagent logs to determine if there\nwas a problem executing nbcheck. If not, review the output from nbcheck to\ndetermine which check has failed. Note that only critical checks can cause the\ninstallation to fail. Correct the condition that the preinstall checker displays and\nre-run the job." }, "7273": { "code": 7273, - "desc": "O existing security configuration está inválido.", + "desc": "The existing security configuration is invalid.", "first_action": "Verifythatthemasterserverisintheexpectedmode.The", - "full_action": "Verifythatthemasterserverisintheexpectedmode.The\ncommand/netbackup/bin/nbcertcmd -getSecConfig -caUsage\ndisplays o mode." + "full_action": "Verifythatthemasterserverisintheexpectedmode.The\ncommand/netbackup/bin/nbcertcmd -getSecConfig -caUsage\ndisplays the mode." }, "7275": { "code": 7275, - "desc": "O native Package Manager comando falhou.", - "first_action": "Review o nbinstallagent logs to determinar if o", - "full_action": "Review o nbinstallagent logs to determinar if o\nproblema foi com adding ou removing o package." + "desc": "The native Package Manager command failed.", + "first_action": "Review the nbinstallagent logs to determine if the", + "full_action": "Review the nbinstallagent logs to determine if the\nproblem was with adding or removing the package." }, "7276": { "code": 7276, - "desc": "O NetBackup processos não é possível be started.", - "first_action": "Log onto o target host e start processos manually", - "full_action": "Log onto o target host e start processos manually\nusando bp.start_all (UNIX) ou bpup (Windows)." + "desc": "The NetBackup processes cannot be started.", + "first_action": "Log onto the target host and start processes manually", + "full_action": "Log onto the target host and start processes manually\nusing bp.start_all (UNIX) or bpup (Windows)." }, "7277": { "code": 7277, - "desc": "O NetBackup configuration on o host está inválido ou corrupt.", - "first_action": "If o target host está windows inspect o", - "full_action": "If o target host está windows inspect o\nSOFTWARE\\Veritas\\NetBackup\\CurrentVersion\\Install Type key.\nIfthetargethostisUNIX,runbpclntcmd -is_server todetermine\nif it está um cliente ou um servidor. If it está um servidor, run bpclntcmd -is_master_server\n to determinar if o target host está um master ou um mídia servidor." + "desc": "The NetBackup configuration on the host is invalid or corrupt.", + "first_action": "If the target host is windows inspect the", + "full_action": "If the target host is windows inspect the\nSOFTWARE\\Veritas\\NetBackup\\CurrentVersion\\Install Type key.\nIfthetargethostisUNIX,runbpclntcmd -is_server todetermine\nif it is a client or a server. If it is a server, run bpclntcmd -is_master_server\n to determine if the target host is a master or a media server." }, "7278": { "code": 7278, - "desc": "Falhou to get o NetBackup install status from o remote host.", + "desc": "Failed to get the NetBackup install status from the remote host.", "first_action": "Reviewtheinstallationlogsonthetargethosttodetermine", - "full_action": "Reviewtheinstallationlogsonthetargethosttodetermine\nif o upgrade foi successful. If it foi não, review o nbinstallagent logs to\ndeterminar what caused o falha." + "full_action": "Reviewtheinstallationlogsonthetargethosttodetermine\nif the upgrade was successful. If it was not, review the nbinstallagent logs to\ndetermine what caused the failure." }, "7279": { "code": 7279, - "desc": "O host type e package type do não match.", - "first_action": "Specify um different package which está compatible com o host’s type.", - "full_action": "To fix o issue, try one de o seguinte como applicable:\n■ Specify um different package which está compatible com o host’s type.\n■ Change o specified host to um type compatible com o package." + "desc": "The host type and package type do not match.", + "first_action": "Specify a different package which is compatible with the host’s type.", + "full_action": "To fix the issue, try one of the following as applicable:\n■ Specify a different package which is compatible with the host’s type.\n■ Change the specified host to a type compatible with the package." }, "7281": { "code": 7281, - "desc": "O command-line length está too long.", - "first_action": "In most cases, this message está due to larger Servidor e", - "full_action": "In most cases, this message está due to larger Servidor e\nMEDIA_SERVER lists, e o internal commands que require specification de those\nserversonthecommandline.Considerfilteringortrimmingserverlistsforthetarget\nhosts in o bp.conf arquivo (ou Windows registry) e executando o process com smaller\ngroups de Servidor e MEDIA_SERVER lists." + "desc": "The command-line length is too long.", + "first_action": "In most cases, this message is due to larger SERVER and", + "full_action": "In most cases, this message is due to larger SERVER and\nMEDIA_SERVER lists, and the internal commands that require specification of those\nserversonthecommandline.Considerfilteringortrimmingserverlistsforthetarget\nhosts in the bp.conf file (or Windows registry) and running the process with smaller\ngroups of SERVER and MEDIA_SERVER lists." }, "7282": { "code": 7282, - "desc": "Could não query o system para o state de existing instalado packages.", + "desc": "Could not query the system for the state of existing installed packages.", "first_action": "Refertoplatform-specificPackageManagerdocumentation.", - "full_action": "Refertoplatform-specificPackageManagerdocumentation.\nConfirm que o native packaging system está in um healthy state on todos target hosts." + "full_action": "Refertoplatform-specificPackageManagerdocumentation.\nConfirm that the native packaging system is in a healthy state on all target hosts." }, "7283": { "code": 7283, - "desc": "Could não parse o deployment option.", - "first_action": "Verifique que NetBackup passes o deployment options", - "full_action": "Verifique que NetBackup passes o deployment options\ncorrectly: NetBackup Job Manager (nbjm) to NetBackup mídia servidor transport\n(nbmtrans). Review qualquer manually entered deployment options to determinar if they\nestão syntactically correct. Retry o operation e if o issue persists, visit o\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional informação to help you troubleshoot this issue." + "desc": "Could not parse the deployment option.", + "first_action": "Verify that NetBackup passes the deployment options", + "full_action": "Verify that NetBackup passes the deployment options\ncorrectly: NetBackup Job Manager (nbjm) to NetBackup media server transport\n(nbmtrans). Review any manually entered deployment options to determine if they\nare syntactically correct. Retry the operation and if the issue persists, visit the\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional information to help you troubleshoot this issue." }, "7284": { "code": 7284, - "desc": "One ou more package arquivo paths foram não accepted.", - "first_action": "Verifique que o arquivo paths exist e have um sja extension.", - "full_action": "Verifique que o arquivo paths exist e have um sja extension." + "desc": "One or more package file paths were not accepted.", + "first_action": "Verify that the file paths exist and have an sja extension.", + "full_action": "Verify that the file paths exist and have an sja extension." }, "7285": { "code": 7285, - "desc": "Could não find um value para javagui_jre field in o conf arquivo.", - "first_action": "Retry o operation e if o issue persists, visit o", - "full_action": "Retry o operation e if o issue persists, visit o\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional informação to help you troubleshoot this issue." + "desc": "Could not find a value for javagui_jre field in the conf file.", + "first_action": "Retry the operation and if the issue persists, visit the", + "full_action": "Retry the operation and if the issue persists, visit the\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional information to help you troubleshoot this issue." }, "7286": { "code": 7286, - "desc": "Could não extract e verifique o nbjavajre package successfully.", - "first_action": "Confirm que o package has come from um legitimate", - "full_action": "Confirm que o package has come from um legitimate\nsource e has não been altered ou manipulated. Confirm que there está sufficient\ndisco space to extract o package on o target host. Retry o operation e if o\nissuepersists,visittheCohesityTechnicalSupportwebsite.TheCohesityTechnical\nSupport website offers additional informação to help you troubleshoot this issue." + "desc": "Could not extract and verify the nbjavajre package successfully.", + "first_action": "Confirm that the package has come from a legitimate", + "full_action": "Confirm that the package has come from a legitimate\nsource and has not been altered or manipulated. Confirm that there is sufficient\ndisk space to extract the package on the target host. Retry the operation and if the\nissuepersists,visittheCohesityTechnicalSupportwebsite.TheCohesityTechnical\nSupport website offers additional information to help you troubleshoot this issue." }, "7287": { "code": 7287, - "desc": "Incorrect javagui_jre value que está specified in o conf arquivo. O valid values estão include, exclude, ou match.", - "first_action": "Retry o operation e if o issue persists, visit o", - "full_action": "Retry o operation e if o issue persists, visit o\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional informação to help you troubleshoot this issue." + "desc": "Incorrect javagui_jre value that is specified in the conf file. The valid values are include, exclude, or match.", + "first_action": "Retry the operation and if the issue persists, visit the", + "full_action": "Retry the operation and if the issue persists, visit the\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional information to help you troubleshoot this issue." }, "7288": { "code": 7288, - "desc": "Could não query registry info.", - "first_action": "Verifique o registry key", - "full_action": "Verifique o registry key\nSOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Uninstall exists e está não\ncorrupted." + "desc": "Could not query registry info.", + "first_action": "Verify the registry key", + "full_action": "Verify the registry key\nSOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Uninstall exists and is not\ncorrupted." }, "7289": { "code": 7289, - "desc": "O instalado NetBackup packages list exceeds o maximum allowed characters.", - "first_action": "Retry o operation e if o issue persists, visit o", - "full_action": "Retry o operation e if o issue persists, visit o\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional informação to help you troubleshoot this issue." + "desc": "The installed NetBackup packages list exceeds the maximum allowed characters.", + "first_action": "Retry the operation and if the issue persists, visit the", + "full_action": "Retry the operation and if the issue persists, visit the\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional information to help you troubleshoot this issue." }, "7290": { "code": 7290, "desc": "TheVxUpdateplatformnameexceedsthemaximumallowedcharacters.", - "first_action": "Retry o operation e if o issue persists, visit o", - "full_action": "Retry o operation e if o issue persists, visit o\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional informação to help you troubleshoot this issue." + "first_action": "Retry the operation and if the issue persists, visit the", + "full_action": "Retry the operation and if the issue persists, visit the\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional information to help you troubleshoot this issue." }, "7291": { "code": 7291, - "desc": "O definition para o VxUpdate platform está não valid.", - "first_action": "Retry o operation e if o issue persists, visit o", - "full_action": "Retry o operation e if o issue persists, visit o\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional informação to help you troubleshoot this issue." + "desc": "The definition for the VxUpdate platform is not valid.", + "first_action": "Retry the operation and if the issue persists, visit the", + "full_action": "Retry the operation and if the issue persists, visit the\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional information to help you troubleshoot this issue." }, "7292": { "code": 7292, - "desc": "O definition para o VxUpdate platform está não found.", - "first_action": "Retry o operation e if o issue persists, visit o", - "full_action": "Retry o operation e if o issue persists, visit o\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional informação to help you troubleshoot this issue." + "desc": "The definition for the VxUpdate platform is not found.", + "first_action": "Retry the operation and if the issue persists, visit the", + "full_action": "Retry the operation and if the issue persists, visit the\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional information to help you troubleshoot this issue." }, "7293": { "code": 7293, - "desc": "O package está inválido para hosts at this version level.", - "first_action": "Retry o operation usando um maintenance release que está", - "full_action": "Retry o operation usando um maintenance release que está\ncompatible com o version de NetBackup on o target host. You need to use um\nNetBackup maintenance release version que está on o same release line." + "desc": "The package is invalid for hosts at this version level.", + "first_action": "Retry the operation using a maintenance release that is", + "full_action": "Retry the operation using a maintenance release that is\ncompatible with the version of NetBackup on the target host. You need to use a\nNetBackup maintenance release version that is on the same release line." }, "7294": { "code": 7294, - "desc": "O destination release’s agent process did não execute como expected. ConfirmthatthedestinationNetBackupreleaseleveliscompatiblewiththeplatform e OS level de this host.", - "first_action": "Review o NetBackup Software Compatibility List to", - "full_action": "Review o NetBackup Software Compatibility List to\nconfirm que o target host meets operating system e platform requirements.\nConfirm que o operating system e its libraries estão instalado correctly." + "desc": "The destination release’s agent process did not execute as expected. ConfirmthatthedestinationNetBackupreleaseleveliscompatiblewiththeplatform and OS level of this host.", + "first_action": "Review the NetBackup Software Compatibility List to", + "full_action": "Review the NetBackup Software Compatibility List to\nconfirm that the target host meets operating system and platform requirements.\nConfirm that the operating system and its libraries are installed correctly." }, "7295": { "code": 7295, - "desc": "This host está não foi possível to communicate com o master servidor seguinte o upgrade.", + "desc": "This host is unable to communicate with the master server following the upgrade.", "first_action": "ReviewtheNetBackupSecurityand EncryptionGuidefor", - "full_action": "ReviewtheNetBackupSecurityand EncryptionGuidefor\ndetailsonhowtoconfiguresecurecommunicationinthelatestNetBackupreleases.\nSome security modes can be configurado usando VxUpdate. Other security modes\nrequire ação outside de VxUpdate.\nIn cases onde you desejar to force VxUpdate to proceed com o upgrade anyway,\nuse bpsetconfig ou other utilities to add o\nIGNORE_VXUPDATE_PREUPGRADE_COMMUNICATION_CHECK value to o NetBackup\nconfiguration de o target host. Set this value to 1. O next VxUpdate operation\nrelatórios o post-upgrade communication concern, but proceeds com o upgrade.\nUsando this method está não without risk e may cause multiple issues com seu\ninstallation." + "full_action": "ReviewtheNetBackupSecurityand EncryptionGuidefor\ndetailsonhowtoconfiguresecurecommunicationinthelatestNetBackupreleases.\nSome security modes can be configured using VxUpdate. Other security modes\nrequire action outside of VxUpdate.\nIn cases where you want to force VxUpdate to proceed with the upgrade anyway,\nuse bpsetconfig or other utilities to add the\nIGNORE_VXUPDATE_PREUPGRADE_COMMUNICATION_CHECK value to the NetBackup\nconfiguration of the target host. Set this value to 1. The next VxUpdate operation\nreports the post-upgrade communication concern, but proceeds with the upgrade.\nUsing this method is not without risk and may cause multiple issues with your\ninstallation." }, "7296": { "code": 7296, - "desc": "Could não take o host offline.", + "desc": "Could not take the host offline.", "first_action": "IfNetBackupiscurrentlyactiveonthetargetmediaserver", - "full_action": "IfNetBackupiscurrentlyactiveonthetargetmediaserver\n(Example: um backup ou restauração está executando), it's recomendada to wait para que activity\nto finish before VxUpdate está attempted.\nIncaseswhereimmediateinterventionisneeded,relyonNetBackupprocessutilities\nto relatório e potentially stop ou suspend NetBackup processos. Review o\nNetBackup Commands Reference Guide sections para bp.kill_all, bpdown, bpps,\nnbstop, e vmoprcmd." + "full_action": "IfNetBackupiscurrentlyactiveonthetargetmediaserver\n(Example: a backup or restore is running), it's recommended to wait for that activity\nto finish before VxUpdate is attempted.\nIncaseswhereimmediateinterventionisneeded,relyonNetBackupprocessutilities\nto report and potentially stop or suspend NetBackup processes. Review the\nNetBackup Commands Reference Guide sections for bp.kill_all, bpdown, bpps,\nnbstop, and vmoprcmd." }, "7297": { "code": 7297, - "desc": "Falhou to excluir o deployment package arquivo.", + "desc": "Failed to delete the deployment package file.", "first_action": "Verifythattheuserexecutingthenbrepobinaryhasdelete", - "full_action": "Verifythattheuserexecutingthenbrepobinaryhasdelete\nprivileges. Verifique que o arquivo está não in use ou has um lock on it." + "full_action": "Verifythattheuserexecutingthenbrepobinaryhasdelete\nprivileges. Verify that the file is not in use or has a lock on it." }, "7298": { "code": 7298, - "desc": "O specified arquivo exists, but some NetBackup processos não é possível access it.", - "first_action": "Move o arquivo to um location que NetBackup core processos estão permitted to work", - "full_action": "Executar one de o seguinte como appropriate:\n■ Move o arquivo to um location que NetBackup core processos estão permitted to work\ncom, such como /usr/openv/tmp ou \\NetBackup\\Temp.\n■ Use o system chmod comando on UNIX platforms, ou o nbserviceusercmd\ncomando on Windows, to modify permissions on o target arquivo e ou folder so\nque NetBackup core processos have access.\n■ Change o NetBackup daemons e services to run under um usuário account que\nhas permissions to access o target arquivo e ou folder. Remember que there\nestão security implications when performing this operation." + "desc": "The specified file exists, but some NetBackup processes cannot access it.", + "first_action": "Move the file to a location that NetBackup core processes are permitted to work", + "full_action": "Perform one of the following as appropriate:\n■ Move the file to a location that NetBackup core processes are permitted to work\nwith, such as /usr/openv/tmp or \\NetBackup\\Temp.\n■ Use the system chmod command on UNIX platforms, or the nbserviceusercmd\ncommand on Windows, to modify permissions on the target file and or folder so\nthat NetBackup core processes have access.\n■ Change the NetBackup daemons and services to run under a user account that\nhas permissions to access the target file and or folder. Remember that there\nare security implications when performing this operation." }, "7299": { "code": 7299, - "desc": "O library libnsl.so.1 está não present on o target host.", + "desc": "The library libnsl.so.1 is not present on the target host.", "first_action": "Installthelibnsl.so.1libraryonthetargethostandthen", - "full_action": "Installthelibnsl.so.1libraryonthetargethostandthen\nrerun o VxUpdate operation." + "full_action": "Installthelibnsl.so.1libraryonthetargethostandthen\nrerun the VxUpdate operation." }, "7300": { "code": 7300, - "desc": "Uninstall de o target package foi unsuccessful.", - "first_action": "Verifique que you have used o correct target package para", - "full_action": "Verifique que you have used o correct target package para\nthis uninstall. Use o uninstall package que corresponds to o successful install\npackage you used." + "desc": "Uninstall of the target package was unsuccessful.", + "first_action": "Verify that you have used the correct target package for", + "full_action": "Verify that you have used the correct target package for\nthis uninstall. Use the uninstall package that corresponds to the successful install\npackage you used." }, "7301": { "code": 7301, - "desc": "O Windows host does não have o requerido Visual C++ run-time libraries instalado.", - "first_action": "Install Visual C++ run-time libraries 14.36.32532 ou later", - "full_action": "Install Visual C++ run-time libraries 14.36.32532 ou later\non o Windows computer e retry o operation. Para more informação on Visual\nC++ run-time libraries, search Microsoft's website para Redistributing Visual C++\nArquivos." + "desc": "The Windows host does not have the required Visual C++ run-time libraries installed.", + "first_action": "Install Visual C++ run-time libraries 14.36.32532 or later", + "full_action": "Install Visual C++ run-time libraries 14.36.32532 or later\non the Windows computer and retry the operation. For more information on Visual\nC++ run-time libraries, search Microsoft's website for Redistributing Visual C++\nFiles." }, "7302": { "code": 7302, - "desc": "Um transfer request está already in progress para um package arquivo.", - "first_action": "Wait para o existing package transfer to complete e", - "full_action": "Wait para o existing package transfer to complete e\nthen retry o newer package transfer." + "desc": "A transfer request is already in progress for a package file.", + "first_action": "Wait for the existing package transfer to complete and", + "full_action": "Wait for the existing package transfer to complete and\nthen retry the newer package transfer." }, "7303": { "code": 7303, - "desc": "Falhou to move o specified arquivo.", - "first_action": "Review o related log messages to identify o source", - "full_action": "Review o related log messages to identify o source\ne o destination arquivo paths. Confirm que permissions estão correct para those\ndirectories. Confirm um usuário com appropriate privileges attempts o VxUpdate\noperation." + "desc": "Failed to move the specified file.", + "first_action": "Review the related log messages to identify the source", + "full_action": "Review the related log messages to identify the source\nand the destination file paths. Confirm that permissions are correct for those\ndirectories. Confirm a user with appropriate privileges attempts the VxUpdate\noperation." }, "7304": { "code": 7304, - "desc": "Uploaded arquivo name does não match o package name in banco de dados. NetBackup status codes 908 NetBackup status codes", + "desc": "Uploaded file name does not match the package name in database. NetBackup status codes 908 NetBackup status codes", "first_action": "Confirmthepackage(.sjafile)isnotcorruptedandcame", - "full_action": "Confirmthepackage(.sjafile)isnotcorruptedandcame\nfrom um legitimate source." + "full_action": "Confirmthepackage(.sjafile)isnotcorruptedandcame\nfrom a legitimate source." }, "7305": { "code": 7305, - "desc": "O transfer foi started but became inactive ou foi abandoned before completion.", + "desc": "The transfer was started but became inactive or was abandoned before completion.", "first_action": "Knownissuesthatcauseofthiserrorinclude:connectivity", - "full_action": "Knownissuesthatcauseofthiserrorinclude:connectivity\nissues between o source host e o primary servidor, falha de rede services\nonthesourcehost,andfailureofNetBackupservicesontheprimaryserver.Confirm\nque connectivity está healthy between o source host e o primary servidor. Retry\no transfer." + "full_action": "Knownissuesthatcauseofthiserrorinclude:connectivity\nissues between the source host and the primary server, failure of network services\nonthesourcehost,andfailureofNetBackupservicesontheprimaryserver.Confirm\nthat connectivity is healthy between the source host and the primary server. Retry\nthe transfer." }, "7306": { "code": 7306, - "desc": "Package arquivo has falhou to upload.", - "first_action": "Known issues que cause this erro include: connectivity", - "full_action": "Known issues que cause this erro include: connectivity\nissues between o source host e o primary servidor, falha de rede services\nonthesourcehost,andfailureofNetBackupservicesontheprimaryserver.Confirm\nque connectivity está healthy between o source host e o primary servidor. Retry\no transfer." + "desc": "Package file has failed to upload.", + "first_action": "Known issues that cause this error include: connectivity", + "full_action": "Known issues that cause this error include: connectivity\nissues between the source host and the primary server, failure of network services\nonthesourcehost,andfailureofNetBackupservicesontheprimaryserver.Confirm\nthat connectivity is healthy between the source host and the primary server. Retry\nthe transfer." }, "7307": { "code": 7307, - "desc": "Não é possível excluir package while package add operation está executando.", - "first_action": "Wait until o package add attempt está complete e retry", - "full_action": "Wait until o package add attempt está complete e retry\no excluir operation." + "desc": "Cannot delete package while package add operation is running.", + "first_action": "Wait until the package add attempt is complete and retry", + "full_action": "Wait until the package add attempt is complete and retry\nthe delete operation." }, "7400": { "code": 7400, - "desc": "Armazenamento servidor com o same name e type already exists.", - "first_action": "Use um different armazenamento servidor name. Contate Cohesity", - "full_action": "Use um different armazenamento servidor name. Contate Cohesity\nTechnical Support para additional troubleshooting." + "desc": "Storage server with the same name and type already exists.", + "first_action": "Use a different storage server name. Contact Cohesity", + "full_action": "Use a different storage server name. Contact Cohesity\nTechnical Support for additional troubleshooting." }, "7401": { "code": 7401, - "desc": "Falhou to create armazenamento servidor.", - "first_action": "Veja o errorDetails in JSON output para additional", - "full_action": "Veja o errorDetails in JSON output para additional\ndetails. If o issue persists, contate Cohesity Technical Support para additional\ntroubleshooting." + "desc": "Failed to create storage server.", + "first_action": "See the errorDetails in JSON output for additional", + "full_action": "See the errorDetails in JSON output for additional\ndetails. If the issue persists, contact Cohesity Technical Support for additional\ntroubleshooting." }, "7402": { "code": 7402, - "desc": "Falhou to get armazenamento servidor properties.", - "first_action": "Veja o errorDetails in JSON output para additional", - "full_action": "Veja o errorDetails in JSON output para additional\ndetails. If o issue persists, contate Cohesity Technical Support para additional\ntroubleshooting." + "desc": "Failed to get storage server properties.", + "first_action": "See the errorDetails in JSON output for additional", + "full_action": "See the errorDetails in JSON output for additional\ndetails. If the issue persists, contact Cohesity Technical Support for additional\ntroubleshooting." }, "7403": { "code": 7403, - "desc": "Falhou to update armazenamento servidor.", - "first_action": "Veja o errorDetails in JSON output para additional", - "full_action": "Veja o errorDetails in JSON output para additional\ndetails. If o issue persists, contate Cohesity Technical Support para additional\ntroubleshooting." + "desc": "Failed to update storage server.", + "first_action": "See the errorDetails in JSON output for additional", + "full_action": "See the errorDetails in JSON output for additional\ndetails. If the issue persists, contact Cohesity Technical Support for additional\ntroubleshooting." }, "7404": { "code": 7404, - "desc": "Falhou to excluir armazenamento servidor.", - "first_action": "Veja o errorDetails in JSON output para additional", - "full_action": "Veja o errorDetails in JSON output para additional\ndetails. If o issue persists, contate Cohesity Technical Support para additional\ntroubleshooting." + "desc": "Failed to delete storage server.", + "first_action": "See the errorDetails in JSON output for additional", + "full_action": "See the errorDetails in JSON output for additional\ndetails. If the issue persists, contact Cohesity Technical Support for additional\ntroubleshooting." }, "7405": { "code": 7405, - "desc": "Falhou to remove o armazenamento servidor.", - "first_action": "Veja o errorDetails in JSON output para additional", - "full_action": "Veja o errorDetails in JSON output para additional\ndetails. If o issue persists, contate Cohesity Technical Support para additional\ntroubleshooting." + "desc": "Failed to remove the storage server.", + "first_action": "See the errorDetails in JSON output for additional", + "full_action": "See the errorDetails in JSON output for additional\ndetails. If the issue persists, contact Cohesity Technical Support for additional\ntroubleshooting." }, "7406": { "code": 7406, - "desc": "Solicitado data has o seguinte inválido ou missing fields.", - "first_action": "Veja o errorDetails in JSON output para additional", - "full_action": "Veja o errorDetails in JSON output para additional\ndetails. If o issue persists, contate Cohesity Technical Support para additional\ntroubleshooting." + "desc": "Requested data has the following invalid or missing fields.", + "first_action": "See the errorDetails in JSON output for additional", + "full_action": "See the errorDetails in JSON output for additional\ndetails. If the issue persists, contact Cohesity Technical Support for additional\ntroubleshooting." }, "7407": { "code": 7407, - "desc": "Disco pool com o same name already exists.", + "desc": "Disk pool with the same name already exists.", "first_action": "Useadifferentdiskpoolname.Ifissuestillpersistscontact", "full_action": "Useadifferentdiskpoolname.Ifissuestillpersistscontact\nCohesity Technical Support." }, "7408": { "code": 7408, - "desc": "Falhou to get disco pool.", - "first_action": "Veja o errorDetails in JSON output para additional", - "full_action": "Veja o errorDetails in JSON output para additional\ndetails. If o issue persists, contate Cohesity Technical Support para additional\ntroubleshooting." + "desc": "Failed to get disk pool.", + "first_action": "See the errorDetails in JSON output for additional", + "full_action": "See the errorDetails in JSON output for additional\ndetails. If the issue persists, contact Cohesity Technical Support for additional\ntroubleshooting." }, "7409": { "code": 7409, - "desc": "Falhou to update disco pool.", - "first_action": "Veja o errorDetails in JSON output para additional", - "full_action": "Veja o errorDetails in JSON output para additional\ndetails. If o issue persists, contate Cohesity Technical Support para additional\ntroubleshooting." + "desc": "Failed to update disk pool.", + "first_action": "See the errorDetails in JSON output for additional", + "full_action": "See the errorDetails in JSON output for additional\ndetails. If the issue persists, contact Cohesity Technical Support for additional\ntroubleshooting." }, "7410": { "code": 7410, - "desc": "Falhou to excluir disco pool.", - "first_action": "Veja o errorDetails in JSON output para additional", - "full_action": "Veja o errorDetails in JSON output para additional\ndetails. If o issue persists, contate Cohesity Technical Support para additional\ntroubleshooting." + "desc": "Failed to delete disk pool.", + "first_action": "See the errorDetails in JSON output for additional", + "full_action": "See the errorDetails in JSON output for additional\ndetails. If the issue persists, contact Cohesity Technical Support for additional\ntroubleshooting." }, "7411": { "code": 7411, - "desc": "Armazenamento unidade com o same name already exists.", + "desc": "Storage unit with the same name already exists.", "first_action": "Tryadifferentstorageunitname.Iftheissueisstillpersists,", - "full_action": "Tryadifferentstorageunitname.Iftheissueisstillpersists,\ncontate Cohesity Technical Support." + "full_action": "Tryadifferentstorageunitname.Iftheissueisstillpersists,\ncontact Cohesity Technical Support." }, "7412": { "code": 7412, - "desc": "Falhou to create armazenamento unidade.", - "first_action": "Veja o errorDetails in JSON output para additional", - "full_action": "Veja o errorDetails in JSON output para additional\ndetails. If o issue persists, contate Cohesity Technical Support para additional\ntroubleshooting." + "desc": "Failed to create storage unit.", + "first_action": "See the errorDetails in JSON output for additional", + "full_action": "See the errorDetails in JSON output for additional\ndetails. If the issue persists, contact Cohesity Technical Support for additional\ntroubleshooting." }, "7413": { "code": 7413, - "desc": "Falhou to get armazenamento unidade.", - "first_action": "Veja o errorDetails in JSON output para additional", - "full_action": "Veja o errorDetails in JSON output para additional\ndetails. If o issue persists, contate Cohesity Technical Support para additional\ntroubleshooting." + "desc": "Failed to get storage unit.", + "first_action": "See the errorDetails in JSON output for additional", + "full_action": "See the errorDetails in JSON output for additional\ndetails. If the issue persists, contact Cohesity Technical Support for additional\ntroubleshooting." }, "7414": { "code": 7414, - "desc": "Falhou to update armazenamento unidade. NetBackup status codes 913 NetBackup status codes", - "first_action": "Veja o errorDetails in JSON output para additional", - "full_action": "Veja o errorDetails in JSON output para additional\ndetails. If o issue persists, contate Cohesity Technical Support para additional\ntroubleshooting." + "desc": "Failed to update storage unit. NetBackup status codes 913 NetBackup status codes", + "first_action": "See the errorDetails in JSON output for additional", + "full_action": "See the errorDetails in JSON output for additional\ndetails. If the issue persists, contact Cohesity Technical Support for additional\ntroubleshooting." }, "7415": { "code": 7415, - "desc": "Falhou to excluir armazenamento unidade.", - "first_action": "Veja o errorDetails in JSON output para additional", - "full_action": "Veja o errorDetails in JSON output para additional\ndetails. If o issue persists, contate Cohesity Technical Support para additional\ntroubleshooting." + "desc": "Failed to delete storage unit.", + "first_action": "See the errorDetails in JSON output for additional", + "full_action": "See the errorDetails in JSON output for additional\ndetails. If the issue persists, contact Cohesity Technical Support for additional\ntroubleshooting." }, "7416": { "code": 7416, - "desc": "Service method não implementado.", - "first_action": "Verifique o API documentation para o supported method.", - "full_action": "Verifique o API documentation para o supported method.\nIf o issue persists, contate Cohesity Technical Support para additional\ntroubleshooting." + "desc": "Service method unimplemented.", + "first_action": "Check the API documentation for the supported method.", + "full_action": "Check the API documentation for the supported method.\nIf the issue persists, contact Cohesity Technical Support for additional\ntroubleshooting." }, "7417": { "code": 7417, - "desc": "Armazenamento API Management recurso está disabled.", + "desc": "Storage API Management feature is disabled.", "first_action": "Iftheproblempersists,contactCohesityTechnicalSupport.", "full_action": "Iftheproblempersists,contactCohesityTechnicalSupport." }, "7418": { "code": 7418, - "desc": "Access negada on target armazenamento servidor. NetBackup status codes 914 NetBackup status codes", - "first_action": "Veja o errorDetails in JSON output para additional", - "full_action": "Veja o errorDetails in JSON output para additional\ndetails. If o issue persists, contate Cohesity Technical Support para additional\ntroubleshooting." + "desc": "Access denied on target storage server. NetBackup status codes 914 NetBackup status codes", + "first_action": "See the errorDetails in JSON output for additional", + "full_action": "See the errorDetails in JSON output for additional\ndetails. If the issue persists, contact Cohesity Technical Support for additional\ntroubleshooting." }, "7419": { "code": 7419, - "desc": "Falhou to add replication target to o armazenamento servidor.", - "first_action": "Veja o errorDetails in JSON output para additional", - "full_action": "Veja o errorDetails in JSON output para additional\ndetails. If o issue persists, contate Cohesity Technical Support para additional\ntroubleshooting." + "desc": "Failed to add replication target to the storage server.", + "first_action": "See the errorDetails in JSON output for additional", + "full_action": "See the errorDetails in JSON output for additional\ndetails. If the issue persists, contact Cohesity Technical Support for additional\ntroubleshooting." }, "7420": { "code": 7420, "desc": "Replication relationship already exists.", - "first_action": "Verifique o input que está specified para errors. If o issue", - "full_action": "Verifique o input que está specified para errors. If o issue\npersists, contate Cohesity Technical Support para additional troubleshooting." + "first_action": "Check the input that is specified for errors. If the issue", + "full_action": "Check the input that is specified for errors. If the issue\npersists, contact Cohesity Technical Support for additional troubleshooting." }, "7421": { "code": 7421, - "desc": "Falhou to get armazenamento servidor configuration properties.", - "first_action": "Veja o errorDetails in JSON output para additional", - "full_action": "Veja o errorDetails in JSON output para additional\ndetails. If o issue persists, contate Cohesity Technical Support para additional\ntroubleshooting." + "desc": "Failed to get storage server configuration properties.", + "first_action": "See the errorDetails in JSON output for additional", + "full_action": "See the errorDetails in JSON output for additional\ndetails. If the issue persists, contact Cohesity Technical Support for additional\ntroubleshooting." }, "7422": { "code": 7422, - "desc": "Falhou to create disco pool.", - "first_action": "Veja o errorDetails in JSON output para additional", - "full_action": "Veja o errorDetails in JSON output para additional\ndetails. If o issue persists, contate Cohesity Technical Support para additional\ntroubleshooting." + "desc": "Failed to create disk pool.", + "first_action": "See the errorDetails in JSON output for additional", + "full_action": "See the errorDetails in JSON output for additional\ndetails. If the issue persists, contact Cohesity Technical Support for additional\ntroubleshooting." }, "7423": { "code": 7423, - "desc": "Falhou to create disco volume.", - "first_action": "Veja o errorDetails in JSON output para additional", - "full_action": "Veja o errorDetails in JSON output para additional\ndetails. If o issue persists, contate Cohesity Technical Support para additional\ntroubleshooting." + "desc": "Failed to create disk volume.", + "first_action": "See the errorDetails in JSON output for additional", + "full_action": "See the errorDetails in JSON output for additional\ndetails. If the issue persists, contact Cohesity Technical Support for additional\ntroubleshooting." }, "7424": { "code": 7424, - "desc": "Falhou to get disco volume.", - "first_action": "Veja o errorDetails in JSON output para additional", - "full_action": "Veja o errorDetails in JSON output para additional\ndetails. If o issue persists, contate Cohesity Technical Support para additional\ntroubleshooting." + "desc": "Failed to get disk volume.", + "first_action": "See the errorDetails in JSON output for additional", + "full_action": "See the errorDetails in JSON output for additional\ndetails. If the issue persists, contact Cohesity Technical Support for additional\ntroubleshooting." }, "7425": { "code": 7425, - "desc": "Falhou to get replication targets.", - "first_action": "Veja o errorDetails in JSON output para additional", - "full_action": "Veja o errorDetails in JSON output para additional\ndetails. If o issue persists, contate Cohesity Technical Support para additional\ntroubleshooting." + "desc": "Failed to get replication targets.", + "first_action": "See the errorDetails in JSON output for additional", + "full_action": "See the errorDetails in JSON output for additional\ndetails. If the issue persists, contact Cohesity Technical Support for additional\ntroubleshooting." }, "7426": { "code": 7426, - "desc": "Falhou to get o replication relationship details.", - "first_action": "Veja o errorDetails in JSON output para additional", - "full_action": "Veja o errorDetails in JSON output para additional\ndetails. Retry o operation e if o issue persists, visit o Cohesity Technical\nSupport website. O Cohesity Technical Support website offers additional\ninformação to help you troubleshoot this issue." + "desc": "Failed to get the replication relationship details.", + "first_action": "See the errorDetails in JSON output for additional", + "full_action": "See the errorDetails in JSON output for additional\ndetails. Retry the operation and if the issue persists, visit the Cohesity Technical\nSupport website. The Cohesity Technical Support website offers additional\ninformation to help you troubleshoot this issue." }, "7427": { "code": 7427, - "desc": "Falhou to create universal share.", - "first_action": "Retry o operation e if o issue persists, visit o", - "full_action": "Retry o operation e if o issue persists, visit o\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional informação to help you troubleshoot this issue." + "desc": "Failed to create universal share.", + "first_action": "Retry the operation and if the issue persists, visit the", + "full_action": "Retry the operation and if the issue persists, visit the\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional information to help you troubleshoot this issue." }, "7428": { "code": 7428, - "desc": "Falhou to update universal share.", - "first_action": "Retry o operation e if o issue persists, visit o", - "full_action": "Retry o operation e if o issue persists, visit o\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional informação to help you troubleshoot this issue." + "desc": "Failed to update universal share.", + "first_action": "Retry the operation and if the issue persists, visit the", + "full_action": "Retry the operation and if the issue persists, visit the\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional information to help you troubleshoot this issue." }, "7429": { "code": 7429, - "desc": "Falhou to fetch o universal share details. NetBackup status codes 917 NetBackup status codes", - "first_action": "Retry o operation e if o issue persists, visit o", - "full_action": "Retry o operation e if o issue persists, visit o\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional informação to help you troubleshoot this issue." + "desc": "Failed to fetch the universal share details. NetBackup status codes 917 NetBackup status codes", + "first_action": "Retry the operation and if the issue persists, visit the", + "full_action": "Retry the operation and if the issue persists, visit the\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional information to help you troubleshoot this issue." }, "7430": { "code": 7430, - "desc": "Falhou to excluir universal share.", - "first_action": "Retry o operation e if o issue persists, visit o", - "full_action": "Retry o operation e if o issue persists, visit o\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional informação to help you troubleshoot this issue." + "desc": "Failed to delete universal share.", + "first_action": "Retry the operation and if the issue persists, visit the", + "full_action": "Retry the operation and if the issue persists, visit the\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional information to help you troubleshoot this issue." }, "7431": { "code": 7431, - "desc": "Falhou to fetch o universal share list.", - "first_action": "Retry o operation e if o issue persists, visit o", - "full_action": "Retry o operation e if o issue persists, visit o\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional informação to help you troubleshoot this issue." + "desc": "Failed to fetch the universal share list.", + "first_action": "Retry the operation and if the issue persists, visit the", + "full_action": "Retry the operation and if the issue persists, visit the\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional information to help you troubleshoot this issue." }, "7432": { "code": 7432, - "desc": "Falhou to add replication target on disco volume.", - "first_action": "Veja o errorDetails in JSON output para additional", - "full_action": "Veja o errorDetails in JSON output para additional\ndetails. Retry o operation e if o issue persists, visit o Cohesity Technical\nSupport website. O Cohesity Technical Support website offers additional\ninformação to help you troubleshoot this issue." + "desc": "Failed to add replication target on disk volume.", + "first_action": "See the errorDetails in JSON output for additional", + "full_action": "See the errorDetails in JSON output for additional\ndetails. Retry the operation and if the issue persists, visit the Cohesity Technical\nSupport website. The Cohesity Technical Support website offers additional\ninformation to help you troubleshoot this issue." }, "7433": { "code": 7433, - "desc": "Falhou to excluir replication target on disco volume.", - "first_action": "Veja o errorDetails in JSON output para additional", - "full_action": "Veja o errorDetails in JSON output para additional\ndetails. Retry o operation e if o issue persists, visit o Cohesity Technical\nSupport website. O Cohesity Technical Support website offers additional\ninformação to help you troubleshoot this issue." + "desc": "Failed to delete replication target on disk volume.", + "first_action": "See the errorDetails in JSON output for additional", + "full_action": "See the errorDetails in JSON output for additional\ndetails. Retry the operation and if the issue persists, visit the Cohesity Technical\nSupport website. The Cohesity Technical Support website offers additional\ninformation to help you troubleshoot this issue." }, "7434": { "code": 7434, - "desc": "Falhou to get replication target details de disco volume.", - "first_action": "Veja o errorDetails in JSON output para additional", - "full_action": "Veja o errorDetails in JSON output para additional\ndetails. Retry o operation e if o issue persists, visit o Cohesity Technical\nSupport website. O Cohesity Technical Support website offers additional\ninformação to help you troubleshoot this issue." + "desc": "Failed to get replication target details of disk volume.", + "first_action": "See the errorDetails in JSON output for additional", + "full_action": "See the errorDetails in JSON output for additional\ndetails. Retry the operation and if the issue persists, visit the Cohesity Technical\nSupport website. The Cohesity Technical Support website offers additional\ninformation to help you troubleshoot this issue." }, "7435": { "code": 7435, - "desc": "Falhou to update disco volume details.", - "first_action": "Veja o errorDetails in JSON output para additional", - "full_action": "Veja o errorDetails in JSON output para additional\ndetails. Retry o operation e if o issue persists, visit o Cohesity Technical\nSupport website. O Cohesity Technical Support website offers additional\ninformação to help you troubleshoot this issue." + "desc": "Failed to update disk volume details.", + "first_action": "See the errorDetails in JSON output for additional", + "full_action": "See the errorDetails in JSON output for additional\ndetails. Retry the operation and if the issue persists, visit the Cohesity Technical\nSupport website. The Cohesity Technical Support website offers additional\ninformation to help you troubleshoot this issue." }, "7436": { "code": 7436, - "desc": "Falhou to list cloud buckets.", - "first_action": "Select um different option e retry o operation. If o", - "full_action": "Select um different option e retry o operation. If o\nissuepersists,visittheCohesityTechnicalSupportwebsite.TheCohesityTechnical\nSupport website offers additional informação to help you troubleshoot this issue." + "desc": "Failed to list cloud buckets.", + "first_action": "Select a different option and retry the operation. If the", + "full_action": "Select a different option and retry the operation. If the\nissuepersists,visittheCohesityTechnicalSupportwebsite.TheCohesityTechnical\nSupport website offers additional information to help you troubleshoot this issue." }, "7437": { "code": 7437, - "desc": "Falhou to create um cloud bucket.", - "first_action": "Select um different option e retry o operation. If o", - "full_action": "Select um different option e retry o operation. If o\nissuepersists,visittheCohesityTechnicalSupportwebsite.TheCohesityTechnical\nSupport website offers additional informação to help you troubleshoot this issue." + "desc": "Failed to create a cloud bucket.", + "first_action": "Select a different option and retry the operation. If the", + "full_action": "Select a different option and retry the operation. If the\nissuepersists,visittheCohesityTechnicalSupportwebsite.TheCohesityTechnical\nSupport website offers additional information to help you troubleshoot this issue." }, "7450": { "code": 7450, - "desc": "O databaseName field must be specified.", - "first_action": "If o databaseName field está specified, verifique que it está não", - "full_action": "If o databaseName field está specified, verifique que it está não\num vazio string. Specify um banco de dados name in o databaseName field." + "desc": "The databaseName field must be specified.", + "first_action": "If the databaseName field is specified, verify that it is not", + "full_action": "If the databaseName field is specified, verify that it is not\nan empty string. Specify a database name in the databaseName field." }, "7451": { "code": 7451, - "desc": "O instanceName field must be specified.", - "first_action": "If o instanceName field está specified, verifique que it está não", - "full_action": "If o instanceName field está specified, verifique que it está não\num vazio string. Specify um instance name in o instanceName field." + "desc": "The instanceName field must be specified.", + "first_action": "If the instanceName field is specified, verify that it is not", + "full_action": "If the instanceName field is specified, verify that it is not\nan empty string. Specify an instance name in the instanceName field." }, "7452": { "code": 7452, - "desc": "O consistencyCheck field must be specified.", - "first_action": "If o consistencyCheck field está specified, verifique que it está", - "full_action": "If o consistencyCheck field está specified, verifique que it está\nnão um vazio string. Specify um instance name in o consistencyCheck field." + "desc": "The consistencyCheck field must be specified.", + "first_action": "If the consistencyCheck field is specified, verify that it is", + "full_action": "If the consistencyCheck field is specified, verify that it is\nnot an empty string. Specify an instance name in the consistencyCheck field." }, "7453": { "code": 7453, - "desc": "O consistencyCheck field must be one de these values: NONE,FULLINCLUDINGINDICES, FULLEXCLUDINGINDICES, CHECKCATALOG, ou PHYSICALCHECKONLY.", - "first_action": "If o consistencyCheck field está provided, verifique que it está", - "full_action": "If o consistencyCheck field está provided, verifique que it está\num valid value. Valid consistencyCheck values estão: NONE,FULLINCLUDINGINDICES,\nFULLEXCLUDINGINDICES, CHECKCATALOG, ou PHYSICALCHECKONLY. Specify um valid\nvalue in o consistencyCheck field." + "desc": "The consistencyCheck field must be one of these values: NONE,FULLINCLUDINGINDICES, FULLEXCLUDINGINDICES, CHECKCATALOG, or PHYSICALCHECKONLY.", + "first_action": "If the consistencyCheck field is provided, verify that it is", + "full_action": "If the consistencyCheck field is provided, verify that it is\na valid value. Valid consistencyCheck values are: NONE,FULLINCLUDINGINDICES,\nFULLEXCLUDINGINDICES, CHECKCATALOG, or PHYSICALCHECKONLY. Specify a valid\nvalue in the consistencyCheck field." }, "7454": { "code": 7454, - "desc": "O maxTransferSize field must be specified.", - "first_action": "If o maxTransferSize field está provided, verifique que it está", - "full_action": "If o maxTransferSize field está provided, verifique que it está\nnão um vazio string. Valid transfer sizes estão: 64K, 128K, 256K, 1M, 2M, ou 4M.\nSpecify um valid transfer size in o maxTransferSize field." + "desc": "The maxTransferSize field must be specified.", + "first_action": "If the maxTransferSize field is provided, verify that it is", + "full_action": "If the maxTransferSize field is provided, verify that it is\nnot an empty string. Valid transfer sizes are: 64K, 128K, 256K, 1M, 2M, or 4M.\nSpecify a valid transfer size in the maxTransferSize field." }, "7455": { "code": 7455, - "desc": "O maxTransferSize field must be one de these values: 64K, 128K, 256K, 1M, 2M, ou 4M.", - "first_action": "If o maxTransferSize field está provided, verifique que it está", - "full_action": "If o maxTransferSize field está provided, verifique que it está\num valid value. Valid transfer sizes estão: 64K, 128K, 256K, 1M, 2M, ou 4M. Specify um\nvalid transfer size in o maxTransferSize field." + "desc": "The maxTransferSize field must be one of these values: 64K, 128K, 256K, 1M, 2M, or 4M.", + "first_action": "If the maxTransferSize field is provided, verify that it is", + "full_action": "If the maxTransferSize field is provided, verify that it is\na valid value. Valid transfer sizes are: 64K, 128K, 256K, 1M, 2M, or 4M. Specify a\nvalid transfer size in the maxTransferSize field." }, "7456": { "code": 7456, - "desc": "O numBuffs field must be between 1 to 32.", - "first_action": "If o numBuffs field está provided, verifique que it está não um", - "full_action": "If o numBuffs field está provided, verifique que it está não um\nvazio string. Specify um valid number de buffers in o numBuffs field. Valid values\nestão in o range de 1 to 32." + "desc": "The numBuffs field must be between 1 to 32.", + "first_action": "If the numBuffs field is provided, verify that it is not an", + "full_action": "If the numBuffs field is provided, verify that it is not an\nempty string. Specify a valid number of buffers in the numBuffs field. Valid values\nare in the range of 1 to 32." }, "7457": { "code": 7457, - "desc": "O recoveredState field must be specified.", + "desc": "The recoveredState field must be specified.", "first_action": "IftherecoveredStatefieldisprovided,verifythatitisnot", - "full_action": "IftherecoveredStatefieldisprovided,verifythatitisnot\num vazio string. Specify um valid recovered state in o recoveredState field. Valid\nrecovered states estão: Recovered, NotRecovered, ou Standby." + "full_action": "IftherecoveredStatefieldisprovided,verifythatitisnot\nan empty string. Specify a valid recovered state in the recoveredState field. Valid\nrecovered states are: Recovered, NotRecovered, or Standby." }, "7458": { "code": 7458, - "desc": "O recoveredState field must be one de these values: Recovered, NotRecovered, ou Standby.", + "desc": "The recoveredState field must be one of these values: Recovered, NotRecovered, or Standby.", "first_action": "IftherecoveredStatefieldisprovided,verifythatitisnot", - "full_action": "IftherecoveredStatefieldisprovided,verifythatitisnot\num vazio string. Specify um valid recovered state in o recoveredState field. Valid\nrecovered states estão: Recovered, NotRecovered, ou Standby." + "full_action": "IftherecoveredStatefieldisprovided,verifythatitisnot\nan empty string. Specify a valid recovered state in the recoveredState field. Valid\nrecovered states are: Recovered, NotRecovered, or Standby." }, "7459": { "code": 7459, - "desc": "O traceLevel field must be specified.", - "first_action": "If o traceLevel field está provided, verifique que it está não um", - "full_action": "If o traceLevel field está provided, verifique que it está não um\nvazio string. Specify um valid trace level in o traceLevel field. Valid trace levels\nestão: Minimum, Medium, ou Maximum." + "desc": "The traceLevel field must be specified.", + "first_action": "If the traceLevel field is provided, verify that it is not an", + "full_action": "If the traceLevel field is provided, verify that it is not an\nempty string. Specify a valid trace level in the traceLevel field. Valid trace levels\nare: Minimum, Medium, or Maximum." }, "7460": { "code": 7460, - "desc": "O traceLevel field must be one de these values: Minimum, Medium, ou Maximum.", - "first_action": "If o traceLevel field está provided, verifique que it está um valid", - "full_action": "If o traceLevel field está provided, verifique que it está um valid\nvalue. Valid trace levels estão: Minimum, Medium, ou Maximum. Specify um valid trace\nlevel in o traceLevel field." + "desc": "The traceLevel field must be one of these values: Minimum, Medium, or Maximum.", + "first_action": "If the traceLevel field is provided, verify that it is a valid", + "full_action": "If the traceLevel field is provided, verify that it is a valid\nvalue. Valid trace levels are: Minimum, Medium, or Maximum. Specify a valid trace\nlevel in the traceLevel field." }, "7461": { "code": 7461, "desc": "Exactly one option in trxLogRecoveryOptions must be specified.", - "first_action": "Verifique que apenas one de o options está provided. Specify", - "full_action": "Verifique que apenas one de o options está provided. Specify\nonlyoneofthetransactionlogrecoveryoptions.Thefollowingisanexamplesubset\nde recovery options: toPointInTime, toTrxLogMark, toTrxLogMarkButAfter,\nbeforeTrxLogMark, e beforeTrxLogMarkButAfter." + "first_action": "Verify that only one of the options is provided. Specify", + "full_action": "Verify that only one of the options is provided. Specify\nonlyoneofthetransactionlogrecoveryoptions.Thefollowingisanexamplesubset\nof recovery options: toPointInTime, toTrxLogMark, toTrxLogMarkButAfter,\nbeforeTrxLogMark, and beforeTrxLogMarkButAfter." }, "7462": { "code": 7462, - "desc": "O toPointInTime field must be specified.", - "first_action": "If o inPointInTime field está specified, verifique que it está não", - "full_action": "If o inPointInTime field está specified, verifique que it está não\num vazio string. Specify um time in o toPointInTime field." + "desc": "The toPointInTime field must be specified.", + "first_action": "If the inPointInTime field is specified, verify that it is not", + "full_action": "If the inPointInTime field is specified, verify that it is not\nan empty string. Specify a time in the toPointInTime field." }, "7463": { "code": 7463, - "desc": "O toTrxLogMark field must be specified.", - "first_action": "If o toTrxLogMark field está specified, verifique que it está não", - "full_action": "If o toTrxLogMark field está specified, verifique que it está não\num vazio string. Specify um log mark in o toTrxLogMark field." + "desc": "The toTrxLogMark field must be specified.", + "first_action": "If the toTrxLogMark field is specified, verify that it is not", + "full_action": "If the toTrxLogMark field is specified, verify that it is not\nan empty string. Specify a log mark in the toTrxLogMark field." }, "7464": { "code": 7464, - "desc": "O toTrxLogMarkButAfter field must be specified.", + "desc": "The toTrxLogMarkButAfter field must be specified.", "first_action": "IfthetoTrxLogMarkButAfterfieldisspecified,verifythat", "full_action": "IfthetoTrxLogMarkButAfterfieldisspecified,verifythat\nitisnotanemptystring.SpecifyatimeandalogmarkinthetoTrxLogMarkButAfter\nfield." }, "7465": { "code": 7465, - "desc": "O beforeTrxLogMark field must be specified. NetBackup status codes 924 NetBackup status codes", - "first_action": "If o beforeTrxLogMark field está specified, verifique que it está", - "full_action": "If o beforeTrxLogMark field está specified, verifique que it está\nnão um vazio string. Specify um log mark in o beforeTrxLogMark field." + "desc": "The beforeTrxLogMark field must be specified. NetBackup status codes 924 NetBackup status codes", + "first_action": "If the beforeTrxLogMark field is specified, verify that it is", + "full_action": "If the beforeTrxLogMark field is specified, verify that it is\nnot an empty string. Specify a log mark in the beforeTrxLogMark field." }, "7466": { "code": 7466, - "desc": "O beforeTrxLogMarkButAfter field must be specified.", + "desc": "The beforeTrxLogMarkButAfter field must be specified.", "first_action": "IfthebeforeTrxLogMarkButAfterfieldisspecified,verify", - "full_action": "IfthebeforeTrxLogMarkButAfterfieldisspecified,verify\nque it está não um vazio string. Specify um time e um log mark in o\nbeforeTrxLogMarkButAfter field." + "full_action": "IfthebeforeTrxLogMarkButAfterfieldisspecified,verify\nthat it is not an empty string. Specify a time and a log mark in the\nbeforeTrxLogMarkButAfter field." }, "7467": { "code": 7467, - "desc": "O standbyPath field must be specified.", - "first_action": "Verifique que o standbyPath field has been included e", - "full_action": "Verifique que o standbyPath field has been included e\nque it está não um vazio string. Specify um fully qualified caminho in o standbyPath field." + "desc": "The standbyPath field must be specified.", + "first_action": "Verify that the standbyPath field has been included and", + "full_action": "Verify that the standbyPath field has been included and\nthat it is not an empty string. Specify a fully qualified path in the standbyPath field." }, "7468": { "code": 7468, - "desc": "O standbyPath field must be um valid arquivo.", - "first_action": "Verifique que o standbyPath field has been provided e", - "full_action": "Verifique que o standbyPath field has been provided e\nque it está não um vazio string. Specify um fully qualified caminho in o standbyPath field." + "desc": "The standbyPath field must be a valid file.", + "first_action": "Verify that the standbyPath field has been provided and", + "full_action": "Verify that the standbyPath field has been provided and\nthat it is not an empty string. Specify a fully qualified path in the standbyPath field." }, "7469": { "code": 7469, - "desc": "O trxLogRecoveryOptions can't be specified.", - "first_action": "If o trxLogRecoveryOptions option está provided, verifique", - "full_action": "If o trxLogRecoveryOptions option está provided, verifique\nque there está um transaction log backup ID associated com it." + "desc": "The trxLogRecoveryOptions can't be specified.", + "first_action": "If the trxLogRecoveryOptions option is provided, verify", + "full_action": "If the trxLogRecoveryOptions option is provided, verify\nthat there is a transaction log backup ID associated with it." }, "7472": { "code": 7472, - "desc": "Could não start banco de dados recovery.", - "first_action": "Try restarting services para o EMM servidor.", - "full_action": "Try o seguinte como appropriate:\n■ Try restarting services para o EMM servidor.\n■ Review o recovery options que foram provided para Microsoft SQL Servidor e\ncorrect qualquer issues." + "desc": "Could not start database recovery.", + "first_action": "Try restarting services for the EMM server.", + "full_action": "Try the following as appropriate:\n■ Try restarting services for the EMM server.\n■ Review the recovery options that were provided for Microsoft SQL Server and\ncorrect any issues." }, "7473": { "code": 7473, - "desc": "Falhou to authenticate instance credentials on o target servidor.", - "first_action": "Verifique o credentials que foram used on o target servidor.", - "full_action": "Verifique o credentials que foram used on o target servidor.\nCorrect qualquer issues e retry o recovery." + "desc": "Failed to authenticate instance credentials on the target server.", + "first_action": "Verify the credentials that were used on the target server.", + "full_action": "Verify the credentials that were used on the target server.\nCorrect any issues and retry the recovery." }, "7476": { "code": 7476, - "desc": "Falhou to get active disco pools details. NetBackup status codes 926 NetBackup status codes", - "first_action": "Review o NetBackup Troubleshooting Guide para additional informação about", - "full_action": "Executar o seguinte como appropriate:\n■ Review o NetBackup Troubleshooting Guide para additional informação about\no erro.\n■ Aumentar o logging level e retry o operation.\n■ Collect o web service logs from o time de o erro e contate Cohesity\nTechnical Support. O web service logs estão located in either\n/usr/openv/netbackup/logs/nbwebservice ou\ninstall_path\\Veritas\\NetBackup\\logs\\nbwebservice." + "desc": "Failed to get active disk pools details. NetBackup status codes 926 NetBackup status codes", + "first_action": "Review the NetBackup Troubleshooting Guide for additional information about", + "full_action": "Perform the following as appropriate:\n■ Review the NetBackup Troubleshooting Guide for additional information about\nthe error.\n■ Increase the logging level and retry the operation.\n■ Collect the web service logs from the time of the error and contact Cohesity\nTechnical Support. The web service logs are located in either\n/usr/openv/netbackup/logs/nbwebservice or\ninstall_path\\Veritas\\NetBackup\\logs\\nbwebservice." }, "7477": { "code": 7477, - "desc": "Falhou to get active e encrypted disco pools details.", - "first_action": "Review o NetBackup Troubleshooting Guide para additional informação about", - "full_action": "Executar o seguinte como appropriate:\n■ Review o NetBackup Troubleshooting Guide para additional informação about\no erro.\n■ Aumentar o logging level e retry o operation.\n■ Collect o web service logs from o time de o erro e contate Cohesity\nTechnical Support. O web service logs estão located in either\n/usr/openv/netbackup/logs/nbwebservice ou\ninstall_path\\Veritas\\NetBackup\\logs\\nbwebservice." + "desc": "Failed to get active and encrypted disk pools details.", + "first_action": "Review the NetBackup Troubleshooting Guide for additional information about", + "full_action": "Perform the following as appropriate:\n■ Review the NetBackup Troubleshooting Guide for additional information about\nthe error.\n■ Increase the logging level and retry the operation.\n■ Collect the web service logs from the time of the error and contact Cohesity\nTechnical Support. The web service logs are located in either\n/usr/openv/netbackup/logs/nbwebservice or\ninstall_path\\Veritas\\NetBackup\\logs\\nbwebservice." }, "7600": { "code": 7600, - "desc": "Um unknown internal erro ocorreu.", - "first_action": "Contate Cohesity Technical Support para assistance.", - "full_action": "Contate Cohesity Technical Support para assistance." + "desc": "An unknown internal error occurred.", + "first_action": "Contact Cohesity Technical Support for assistance.", + "full_action": "Contact Cohesity Technical Support for assistance." }, "7601": { "code": 7601, - "desc": "Falhou to register service com PBX.", - "first_action": "Verifique que o pbx_exchange service está executando. If não, start o service.", - "full_action": "Do o seguinte:\n■ Verifique que o pbx_exchange service está executando. If não, start o service.\n■ If o problema persists, contate Cohesity Technical Support." + "desc": "Failed to register service with PBX.", + "first_action": "Verify that the pbx_exchange service is running. If not, start the service.", + "full_action": "Do the following:\n■ Verify that the pbx_exchange service is running. If not, start the service.\n■ If the problem persists, contact Cohesity Technical Support." }, "7603": { "code": 7603, - "desc": "Falhou to initialize PBX.", - "first_action": "Contate Cohesity Technical Support para assistance.", - "full_action": "Contate Cohesity Technical Support para assistance." + "desc": "Failed to initialize PBX.", + "first_action": "Contact Cohesity Technical Support for assistance.", + "full_action": "Contact Cohesity Technical Support for assistance." }, "7604": { "code": 7604, - "desc": "Falhou to register PBX acceptor com o reactor.", - "first_action": "Contate Cohesity Technical Support para assistance.", - "full_action": "Contate Cohesity Technical Support para assistance." + "desc": "Failed to register PBX acceptor with the reactor.", + "first_action": "Contact Cohesity Technical Support for assistance.", + "full_action": "Contact Cohesity Technical Support for assistance." }, "7607": { "code": 7607, - "desc": "Falhou to set socket to non-blocking mode.", + "desc": "Failed to set socket to non-blocking mode.", "first_action": "Iftheproblempersists,contactCohesityTechnicalSupport.", "full_action": "Iftheproblempersists,contactCohesityTechnicalSupport." }, "7609": { "code": 7609, - "desc": "Falhou to executar um reactor event handler operation.", - "first_action": "Contate Cohesity Technical Support para assistance.", - "full_action": "Contate Cohesity Technical Support para assistance." + "desc": "Failed to perform a reactor event handler operation.", + "first_action": "Contact Cohesity Technical Support for assistance.", + "full_action": "Contact Cohesity Technical Support for assistance." }, "7610": { "code": 7610, - "desc": "Falhou to parse o specified object.", - "first_action": "Contate Cohesity Technical Support para assistance.", - "full_action": "Contate Cohesity Technical Support para assistance." + "desc": "Failed to parse the specified object.", + "first_action": "Contact Cohesity Technical Support for assistance.", + "full_action": "Contact Cohesity Technical Support for assistance." }, "7611": { "code": 7611, - "desc": "Um conexão protocol erro ocorreu.", - "first_action": "Contate Cohesity Technical Support para assistance.", - "full_action": "Contate Cohesity Technical Support para assistance." + "desc": "A connection protocol error occurred.", + "first_action": "Contact Cohesity Technical Support for assistance.", + "full_action": "Contact Cohesity Technical Support for assistance." }, "7612": { "code": 7612, - "desc": "Um unexpected protocol event ocorreu.", - "first_action": "Contate Cohesity Technical Support para assistance.", - "full_action": "Contate Cohesity Technical Support para assistance." + "desc": "An unexpected protocol event occurred.", + "first_action": "Contact Cohesity Technical Support for assistance.", + "full_action": "Contact Cohesity Technical Support for assistance." }, "7613": { "code": 7613, - "desc": "Um lookup falhou para host. NetBackup status codes 929 NetBackup status codes", - "first_action": "Contate Cohesity Technical Support para assistance.", - "full_action": "Contate Cohesity Technical Support para assistance." + "desc": "A lookup failed for host. NetBackup status codes 929 NetBackup status codes", + "first_action": "Contact Cohesity Technical Support for assistance.", + "full_action": "Contact Cohesity Technical Support for assistance." }, "7614": { "code": 7614, - "desc": "Não valid source-target bindings exist para host.", - "first_action": "Contate Cohesity Technical Support para assistance.", - "full_action": "Contate Cohesity Technical Support para assistance." + "desc": "No valid source-target bindings exist for host.", + "first_action": "Contact Cohesity Technical Support for assistance.", + "full_action": "Contact Cohesity Technical Support for assistance." }, "7617": { "code": 7617, - "desc": "Um JSON conversion erro ocorreu.", + "desc": "A JSON conversion error occurred.", "first_action": "Iftheproblempersists,contactCohesityTechnicalSupport.", "full_action": "Iftheproblempersists,contactCohesityTechnicalSupport." }, "7618": { "code": 7618, - "desc": "Falhou to find JSON key.", + "desc": "Failed to find JSON key.", "first_action": "Iftheproblempersists,contactCohesityTechnicalSupport.", "full_action": "Iftheproblempersists,contactCohesityTechnicalSupport." }, "7619": { "code": 7619, - "desc": "O specified state machine está still active.", + "desc": "The specified state machine is still active.", "first_action": "Iftheproblempersists,contactCohesityTechnicalSupport.", "full_action": "Iftheproblempersists,contactCohesityTechnicalSupport." }, "7622": { "code": 7622, - "desc": "Input I/O está requerido.", + "desc": "Input I/O is required.", "first_action": "Under normal circumstances this message may appear", - "full_action": "Under normal circumstances this message may appear\nin o logs de o vnetd proxy. Não usuário ação está requerido. If um problema persists,\ncontate Cohesity Technical Support." + "full_action": "Under normal circumstances this message may appear\nin the logs of the vnetd proxy. No user action is required. If a problem persists,\ncontact Cohesity Technical Support." }, "7623": { "code": 7623, - "desc": "Output I/O está requerido.", + "desc": "Output I/O is required.", "first_action": "Under normal circumstances this message may appear", - "full_action": "Under normal circumstances this message may appear\nin o logs de o NetBackup process. Não usuário ação está requerido. If um problema\npersists, contate Cohesity Technical Support." + "full_action": "Under normal circumstances this message may appear\nin the logs of the NetBackup process. No user action is required. If a problem\npersists, contact Cohesity Technical Support." }, "7624": { "code": 7624, - "desc": "Um SSL socket accept falhou.", - "first_action": "Um missing, expired, ou revoked host certificate on o local ou o remote host.", - "full_action": "Examine o details de o erro message to determinar\npor que o SSL handshake falhou. Possible causes de this erro may be como follows:\n■ Um missing, expired, ou revoked host certificate on o local ou o remote host.\nIn case de o NetBackup CA, verifique que o hosts have um valid host ID-based\ncertificate. In case de um external CA, verifique que o external certificate e\nkeystore paths estão correctly set in o external certificate configuration arquivo. If\no host está configurado to use um encrypted keystore, garanta que o correct\npassphrase para o certificate's private key está specified para o\nECA_KEY_PASSPHRASEFILE configuration option.\n■ Excessiveclockskewoneitherthelocalortheremotehost.Seetheinformation\nabout clock skew in o NetBackup Security e Encryption Guide.\n■ If you use o NetBackup SECURE_PROXY_CIPHER_LIST configuration option on\neitherthelocalortheremotehost,thecipherstringentriesmaybeinvalid.Verify\nque o cipher strings estão compatible between o hosts.\nIf o problema persists, contate Cohesity Technical Support." + "desc": "A SSL socket accept failed.", + "first_action": "A missing, expired, or revoked host certificate on the local or the remote host.", + "full_action": "Examine the details of the error message to determine\nwhy the SSL handshake failed. Possible causes of this error may be as follows:\n■ A missing, expired, or revoked host certificate on the local or the remote host.\nIn case of the NetBackup CA, verify that the hosts have a valid host ID-based\ncertificate. In case of an external CA, verify that the external certificate and\nkeystore paths are correctly set in the external certificate configuration file. If\nthe host is configured to use an encrypted keystore, ensure that the correct\npassphrase for the certificate's private key is specified for the\nECA_KEY_PASSPHRASEFILE configuration option.\n■ Excessiveclockskewoneitherthelocalortheremotehost.Seetheinformation\nabout clock skew in the NetBackup Security and Encryption Guide.\n■ If you use the NetBackup SECURE_PROXY_CIPHER_LIST configuration option on\neitherthelocalortheremotehost,thecipherstringentriesmaybeinvalid.Verify\nthat the cipher strings are compatible between the hosts.\nIf the problem persists, contact Cohesity Technical Support." }, "7625": { "code": 7625, - "desc": "Um SSL socket conectar falhou.", - "first_action": "Um missing, expired, ou revoked host certificate on o local ou o remote host.", - "full_action": "Examine o details de o erro message to determinar\npor que o SSL handshake falhou. Possible causes de this erro may be como follows:\n■ Um missing, expired, ou revoked host certificate on o local ou o remote host.\nIn case de o NetBackup CA, verifique que o hosts have um valid host ID-based\ncertificate. In case de um external CA, verifique que o external certificate e\nkeystore paths estão correctly set in o external certificate configuration arquivo. If\no host está configurado to use um encrypted keystore, garanta que o correct\npassphrase para o certificate's private key está specified para o\nECA_KEY_PASSPHRASEFILE configuration option.\n■ Excessiveclockskewoneitherthelocalortheremotehost.Seetheinformation\nabout clock skew in o NetBackup Security e Encryption Guide.\n■ If you use o NetBackup SECURE_PROXY_CIPHER_LIST configuration option on\neitherthelocalortheremotehost,thecipherstringentriesmaybeinvalid.Verify\nque o cipher strings estão compatible between o hosts.\nIf o problema persists, contate Cohesity Technical Support." + "desc": "A SSL socket connect failed.", + "first_action": "A missing, expired, or revoked host certificate on the local or the remote host.", + "full_action": "Examine the details of the error message to determine\nwhy the SSL handshake failed. Possible causes of this error may be as follows:\n■ A missing, expired, or revoked host certificate on the local or the remote host.\nIn case of the NetBackup CA, verify that the hosts have a valid host ID-based\ncertificate. In case of an external CA, verify that the external certificate and\nkeystore paths are correctly set in the external certificate configuration file. If\nthe host is configured to use an encrypted keystore, ensure that the correct\npassphrase for the certificate's private key is specified for the\nECA_KEY_PASSPHRASEFILE configuration option.\n■ Excessiveclockskewoneitherthelocalortheremotehost.Seetheinformation\nabout clock skew in the NetBackup Security and Encryption Guide.\n■ If you use the NetBackup SECURE_PROXY_CIPHER_LIST configuration option on\neitherthelocalortheremotehost,thecipherstringentriesmaybeinvalid.Verify\nthat the cipher strings are compatible between the hosts.\nIf the problem persists, contact Cohesity Technical Support." }, "7627": { "code": 7627, - "desc": "SSL initialization falhou.", - "first_action": "Um missing, expired, ou revoked host certificate. In case de o NetBackup CA,", - "full_action": "Examine o details de o erro message to determinar\npor que o SSL handshake falhou. Possible causes de this erro may be como follows:\n■ Um missing, expired, ou revoked host certificate. In case de o NetBackup CA,\nverifythatthehostshaveavalidhostID-basedcertificate.Incaseofanexternal\nCA, verifique que o external certificate e keystore paths estão correctly set in o\nexternalcertificateconfigurationfile.Ifthehostisconfiguredtouseanencrypted\nkeystore, garanta que o correct passphrase para o certificate’s private key está\nspecified para o ECA_KEY_PASSPHRASEFILE configuration option.\n■ Excessive clock skew on o host. Veja o informação about clock skew in o\nNetBackup Security e Encryption Guide.\n■ IfyouusetheNetBackupSECURE_PROXY_CIPHER_LISTconfigurationoption,the\ncipher string entradas may be inválido. Verifique que o cipher strings estão permitted\nOpenSSL strings.\n■ Para VMware:\n■ When o VIRTUALIZATION_HOSTS_SECURE_CONNECT_ENABLED option está\nenabled, you must verifique o placement de o certificates e CRLs. Verifique\nwhethertheVMwarevirtualizationserver’s(vCenter,ESX,ESXi)certificates\ne CRLs estão added to o respective ECA configurado trust store e o\nCRL caminho.\n■ Garanta que o certificates e o CRL arquivos estão in o correct format e\no trust store arquivo e o CRL arquivos estão não corrupted.\n■ Apenas PEM certificate format para file-based trust store & Windows trust store\nestão supported para virtualization servers. P7b ou DER format arquivo based trust\nstore está não supported. When this recurso está enabled, o certificate ECA\nstore should either be Windows certificate store ou arquivo based PEM format\nstore.\nIf o problema persists, contate Cohesity Technical Support." + "desc": "SSL initialization failed.", + "first_action": "A missing, expired, or revoked host certificate. In case of the NetBackup CA,", + "full_action": "Examine the details of the error message to determine\nwhy the SSL handshake failed. Possible causes of this error may be as follows:\n■ A missing, expired, or revoked host certificate. In case of the NetBackup CA,\nverifythatthehostshaveavalidhostID-basedcertificate.Incaseofanexternal\nCA, verify that the external certificate and keystore paths are correctly set in the\nexternalcertificateconfigurationfile.Ifthehostisconfiguredtouseanencrypted\nkeystore, ensure that the correct passphrase for the certificate’s private key is\nspecified for the ECA_KEY_PASSPHRASEFILE configuration option.\n■ Excessive clock skew on the host. See the information about clock skew in the\nNetBackup Security and Encryption Guide.\n■ IfyouusetheNetBackupSECURE_PROXY_CIPHER_LISTconfigurationoption,the\ncipher string entries may be invalid. Verify that the cipher strings are permitted\nOpenSSL strings.\n■ For VMware:\n■ When the VIRTUALIZATION_HOSTS_SECURE_CONNECT_ENABLED option is\nenabled, you must verify the placement of the certificates and CRLs. Verify\nwhethertheVMwarevirtualizationserver’s(vCenter,ESX,ESXi)certificates\nand CRLs are added to the respective ECA configured trust store and the\nCRL path.\n■ Ensure that the certificates and the CRL files are in the correct format and\nthe trust store file and the CRL files are not corrupted.\n■ Only PEM certificate format for file-based trust store & Windows trust store\nare supported for virtualization servers. P7b or DER format file based trust\nstore is not supported. When this feature is enabled, the certificate ECA\nstore should either be Windows certificate store or file based PEM format\nstore.\nIf the problem persists, contact Cohesity Technical Support." }, "7628": { "code": 7628, - "desc": "VxSS initialization falhou. NetBackup status codes 933 NetBackup status codes", - "first_action": "Contate Cohesity Technical Support para assistance.", - "full_action": "Contate Cohesity Technical Support para assistance." + "desc": "VxSS initialization failed. NetBackup status codes 933 NetBackup status codes", + "first_action": "Contact Cohesity Technical Support for assistance.", + "full_action": "Contact Cohesity Technical Support for assistance." }, "7631": { "code": 7631, - "desc": "Certificate caminho lookup falhou.", - "first_action": "In case de o NetBackup CA, verifique que o hosts have", - "full_action": "In case de o NetBackup CA, verifique que o hosts have\num valid host ID-based certificate. In case de um external CA, verifique que o hosts\nhave um valid external CA-signed certificate." + "desc": "Certificate path lookup failed.", + "first_action": "In case of the NetBackup CA, verify that the hosts have", + "full_action": "In case of the NetBackup CA, verify that the hosts have\na valid host ID-based certificate. In case of an external CA, verify that the hosts\nhave a valid external CA-signed certificate." }, "7632": { "code": 7632, - "desc": "Um protocol sanity verification falhou.", - "first_action": "Contate Cohesity Technical Support para assistance.", - "full_action": "Contate Cohesity Technical Support para assistance." + "desc": "A protocol sanity verification failed.", + "first_action": "Contact Cohesity Technical Support for assistance.", + "full_action": "Contact Cohesity Technical Support for assistance." }, "7633": { "code": 7633, - "desc": "O state machine foi terminated before completion.", + "desc": "The state machine was terminated before completion.", "first_action": "Under normal circumstances this message may be seen", - "full_action": "Under normal circumstances this message may be seen\nin o logs de o vnetd proxy. Não usuário ação está requerido. If o problema persists,\ncontate Cohesity Technical Support." + "full_action": "Under normal circumstances this message may be seen\nin the logs of the vnetd proxy. No user action is required. If the problem persists,\ncontact Cohesity Technical Support." }, "7634": { "code": 7634, - "desc": "Falhou to set up um UNIX Domain Socket listener para usuário. NetBackup status codes 934 NetBackup status codes", - "first_action": "Examine o status message para additional details. It may", - "full_action": "Examine o status message para additional details. It may\nbe que o process does não have o permissions to create o requerido arquivos ou\no disco volume may be cheio. Examine o state e o contents de (Linux) ou\n(Windows)." + "desc": "Failed to set up a UNIX Domain Socket listener for user. NetBackup status codes 934 NetBackup status codes", + "first_action": "Examine the status message for additional details. It may", + "full_action": "Examine the status message for additional details. It may\nbe that the process does not have the permissions to create the required files or\nthe disk volume may be full. Examine the state and the contents of (Linux) or\n(Windows)." }, "7635": { "code": 7635, - "desc": "Falhou to create um local acceptor.", - "first_action": "Examine o status message para additional details. There", - "full_action": "Examine o status message para additional details. There\nmaybealistenportconflict,orapermissionorfreespaceproblemwiththeproxy.d\ndiretório ou its contents. O diretório está located in ou ." + "desc": "Failed to create a local acceptor.", + "first_action": "Examine the status message for additional details. There", + "full_action": "Examine the status message for additional details. There\nmaybealistenportconflict,orapermissionorfreespaceproblemwiththeproxy.d\ndirectory or its contents. The directory is located in or ." }, "7636": { "code": 7636, - "desc": "Falhou to import socket from remote process.", + "desc": "Failed to import socket from remote process.", "first_action": "Thisfailureislikelyatransientproblem,perhapsbecause", - "full_action": "Thisfailureislikelyatransientproblem,perhapsbecause\nfiledescriptorsareunavailabletemporarily.Therefore,retrytheoperation.Forother\nraiz causes, review o nbpxyhelper logs ou contate Cohesity Technical Support." + "full_action": "Thisfailureislikelyatransientproblem,perhapsbecause\nfiledescriptorsareunavailabletemporarily.Therefore,retrytheoperation.Forother\nroot causes, review the nbpxyhelper logs or contact Cohesity Technical Support." }, "7637": { "code": 7637, - "desc": "Falhou to export socket to remote process.", + "desc": "Failed to export socket to remote process.", "first_action": "Thisfailureislikelyatransientproblem,perhapsbecause", - "full_action": "Thisfailureislikelyatransientproblem,perhapsbecause\nfiledescriptorsareunavailabletemporarily.Therefore,retrytheoperation.Forother\nraiz causes, review o nbpxyhelper logs ou contate Cohesity Technical Support." + "full_action": "Thisfailureislikelyatransientproblem,perhapsbecause\nfiledescriptorsareunavailabletemporarily.Therefore,retrytheoperation.Forother\nroot causes, review the nbpxyhelper logs or contact Cohesity Technical Support." }, "7638": { "code": 7638, - "desc": "Falhou to create um socket pair.", + "desc": "Failed to create a socket pair.", "first_action": "Thisfailureislikelyatransientproblem,perhapsbecause", - "full_action": "Thisfailureislikelyatransientproblem,perhapsbecause\narquivo descriptors ou TCP ports estão unavailable temporarily. Therefore, retry o\noperation. Para other raiz causes, review o nbpxyhelper logs ou contate Cohesity\nTechnical Support." + "full_action": "Thisfailureislikelyatransientproblem,perhapsbecause\nfile descriptors or TCP ports are unavailable temporarily. Therefore, retry the\noperation. For other root causes, review the nbpxyhelper logs or contact Cohesity\nTechnical Support." }, "7639": { "code": 7639, - "desc": "Falhou to create um peer name mapping.", - "first_action": "Examine o status message para additional details. It may", - "full_action": "Examine o status message para additional details. It may\nbe que o process does não have o permissions to create o requerido arquivos ou\no disco volume may be cheio. Examine o state e o contents de (Linux) ou\n(Windows)." + "desc": "Failed to create a peer name mapping.", + "first_action": "Examine the status message for additional details. It may", + "full_action": "Examine the status message for additional details. It may\nbe that the process does not have the permissions to create the required files or\nthe disk volume may be full. Examine the state and the contents of (Linux) or\n(Windows)." }, "7640": { "code": 7640, - "desc": "O peer closed o conexão.", + "desc": "The peer closed the connection.", "first_action": "Under normal circumstances this message may be seen", - "full_action": "Under normal circumstances this message may be seen\nin o vnetd proxy logs. Não usuário ação está requerido. If um problema persists, contate\nCohesity Technical Support.\nPara more informação, review this technical article:\nhttps://www.veritas.com/support/en_US/article.100039945" + "full_action": "Under normal circumstances this message may be seen\nin the vnetd proxy logs. No user action is required. If a problem persists, contact\nCohesity Technical Support.\nFor more information, review this technical article:\nhttps://www.veritas.com/support/en_US/article.100039945" }, "7641": { "code": 7641, - "desc": "Falhou to find um common CA Raiz para secure handshake.", - "first_action": "Recomendada Ação: Missing, expired, ou revoked host certificate on o", - "full_action": "Examine o erro message para o details de which CA\nRoots each NetBackup process advertised. O seguinte estão possible causes de\nthis erro:\n■ Recomendada Ação: Missing, expired, ou revoked host certificate on o\nlocalortheremotehost.IncaseoftheNetBackupCA,verifythatthehostshave\navalidhostID-basedcertificate.IncaseofanexternalCA,verifythattheexternal\ncertificate e keystore paths estão correctly set in o external certificate\nconfiguration arquivo. If o host está configurado to use um encrypted keystore, garanta\nque o correct passphrase para o certificate's private key está specified para o\nECA_KEY_PASSPHRASEFILE configuration option.\n■ Recomendada Ação: O hosts estão não members de o same NetBackup\ndomain.IncaseoftheNetBackupCA,ensurethatbothhostshavehostID-based\ncertificates issued por o requerido master servidor. In case de um external CA,\ngaranta que both hosts have o external certificates que estão enrolled com o\nrequerido master servidor." + "desc": "Failed to find a common CA Root for secure handshake.", + "first_action": "Recommended Action: Missing, expired, or revoked host certificate on the", + "full_action": "Examine the error message for the details of which CA\nRoots each NetBackup process advertised. The following are possible causes of\nthis error:\n■ Recommended Action: Missing, expired, or revoked host certificate on the\nlocalortheremotehost.IncaseoftheNetBackupCA,verifythatthehostshave\navalidhostID-basedcertificate.IncaseofanexternalCA,verifythattheexternal\ncertificate and keystore paths are correctly set in the external certificate\nconfiguration file. If the host is configured to use an encrypted keystore, ensure\nthat the correct passphrase for the certificate's private key is specified for the\nECA_KEY_PASSPHRASEFILE configuration option.\n■ Recommended Action: The hosts are not members of the same NetBackup\ndomain.IncaseoftheNetBackupCA,ensurethatbothhostshavehostID-based\ncertificates issued by the required master server. In case of an external CA,\nensure that both hosts have the external certificates that are enrolled with the\nrequired master server." }, "7642": { "code": 7642, - "desc": "Falhou to verifique Java GUI session token.", - "first_action": "1. Verifique o authorization de o usuário who launched o NetBackup", - "full_action": "Do o seguinte:\n1. Verifique o authorization de o usuário who launched o NetBackup\nAdministration Console.\nVeja “About authorizing NetBackup users” in o NetBackup Administrator's\nGuide, Volume I.\n2. Fechar o NetBackup Administration Console.\n3. Launch um new instance de o NetBackup AdministrationConsole e abrir\no Activity Monitor.\nIf o problema persists, contate Cohesity Technical Support." + "desc": "Failed to verify Java GUI session token.", + "first_action": "1. Verify the authorization of the user who launched the NetBackup", + "full_action": "Do the following:\n1. Verify the authorization of the user who launched the NetBackup\nAdministration Console.\nSee “About authorizing NetBackup users” in the NetBackup Administrator's\nGuide, Volume I.\n2. Close the NetBackup Administration Console.\n3. Launch a new instance of the NetBackup AdministrationConsole and open\nthe Activity Monitor.\nIf the problem persists, contact Cohesity Technical Support." }, "7643": { "code": 7643, - "desc": "Conexão não é possível be established because o host validation não é possível be performed.", + "desc": "Connection cannot be established because the host validation cannot be performed.", "first_action": "Iftheproblempersists,contactCohesityTechnicalSupport.", "full_action": "Iftheproblempersists,contactCohesityTechnicalSupport." }, "7645": { "code": 7645, - "desc": "Could não get name from certificate informação.", - "first_action": "Contate Cohesity Technical Support para assistance.", - "full_action": "Contate Cohesity Technical Support para assistance." + "desc": "Could not get name from certificate information.", + "first_action": "Contact Cohesity Technical Support for assistance.", + "full_action": "Contact Cohesity Technical Support for assistance." }, "7647": { "code": 7647, - "desc": "Proxy peer does não conform to proxy protocol.", - "first_action": "Contate Cohesity Technical Support para assistance.", - "full_action": "Contate Cohesity Technical Support para assistance." + "desc": "Proxy peer does not conform to proxy protocol.", + "first_action": "Contact Cohesity Technical Support for assistance.", + "full_action": "Contact Cohesity Technical Support for assistance." }, "7648": { "code": 7648, - "desc": "Conexão não é possível be established because o host validation falhou.", - "first_action": "Garanta que o NetBackup master servidor name e o", - "full_action": "Garanta que o NetBackup master servidor name e o\nhost name estão configurado correctly." + "desc": "Connection cannot be established because the host validation failed.", + "first_action": "Ensure that the NetBackup master server name and the", + "full_action": "Ensure that the NetBackup master server name and the\nhost name are configured correctly." }, "7649": { "code": 7649, - "desc": "Data retrieved from o cache está não in um valid format.", + "desc": "Data retrieved from the cache is not in a valid format.", "first_action": "Deletethepeerhost'scacheentryandretrytheoperation.", - "full_action": "Deletethepeerhost'scacheentryandretrytheoperation.\nUse bpclntcmd -clear_host_cache. If o problema continues, contate Cohesity\nTechnical Support." + "full_action": "Deletethepeerhost'scacheentryandretrytheoperation.\nUse bpclntcmd -clear_host_cache. If the problem continues, contact Cohesity\nTechnical Support." }, "7650": { "code": 7650, - "desc": "Data que está retrieved from o servidor está não in um valid format.", + "desc": "Data that is retrieved from the server is not in a valid format.", "first_action": "Iftheproblempersists,contactCohesityTechnicalSupport.", "full_action": "Iftheproblempersists,contactCohesityTechnicalSupport." }, "7651": { "code": 7651, - "desc": "Could não process audit reason.", - "first_action": "Encode o X-NetBackup-Audit-Reason HTTP header", - "full_action": "Encode o X-NetBackup-Audit-Reason HTTP header\nusando o appropriate UTF-8 strings to represent o non-ASCII characters, then\nresubmit o HTTP web service request." + "desc": "Could not process audit reason.", + "first_action": "Encode the X-NetBackup-Audit-Reason HTTP header", + "full_action": "Encode the X-NetBackup-Audit-Reason HTTP header\nusing the appropriate UTF-8 strings to represent the non-ASCII characters, then\nresubmit the HTTP web service request." }, "7652": { "code": 7652, - "desc": "Secure communication proxy está não disponível para use.", + "desc": "Secure communication proxy is not available for use.", "first_action": "Number 0", - "full_action": "Determineifthevnetdprocessanditsproxiesarerunning.\nOn Windows, you can use o Task Manager Processos tab (you must show o\nComando Line column). On UNIX e Linux, you can use o NetBackup bpps\ncomando, como follows:\n$ bpps\n…output shortened…\nraiz 13577 1 0 Aug27 ? 00:00:04 /usr/openv/netbackup/bin/vnetd -standalone\nraiz 13606 1 0 Aug27 ? 00:01:55 /usr/openv/netbackup/bin/vnetd -proxy inbound_proxy\n-number 0\nraiz 13608 1 0 Aug27 ? 00:00:06 /usr/openv/netbackup/bin/vnetd -proxy outbound_proxy\n-number 0\nDepending on which vnetd process ou proxy está executando, try o seguinte:\n■ If o vnetd process (-standalone) está não executando, start it.\n■ If o vnetd process está executando, examine o vnetd debug log to confirm que it\ntries to start o proxy processos.\n■ If o vnetd process does try to start o proxy processos, examine o\nnbpxyhelper debug log to determinar por que o proxy process does não listen para\nconnections.\nIf o problema persists, contate Cohesity Technical Support." + "full_action": "Determineifthevnetdprocessanditsproxiesarerunning.\nOn Windows, you can use the Task Manager Processes tab (you must show the\nCommand Line column). On UNIX and Linux, you can use the NetBackup bpps\ncommand, as follows:\n$ bpps\n…output shortened…\nroot 13577 1 0 Aug27 ? 00:00:04 /usr/openv/netbackup/bin/vnetd -standalone\nroot 13606 1 0 Aug27 ? 00:01:55 /usr/openv/netbackup/bin/vnetd -proxy inbound_proxy\n-number 0\nroot 13608 1 0 Aug27 ? 00:00:06 /usr/openv/netbackup/bin/vnetd -proxy outbound_proxy\n-number 0\nDepending on which vnetd process or proxy is running, try the following:\n■ If the vnetd process (-standalone) is not running, start it.\n■ If the vnetd process is running, examine the vnetd debug log to confirm that it\ntries to start the proxy processes.\n■ If the vnetd process does try to start the proxy processes, examine the\nnbpxyhelper debug log to determine why the proxy process does not listen for\nconnections.\nIf the problem persists, contact Cohesity Technical Support." }, "7653": { "code": 7653, - "desc": "O Peer Certificate está revoked Note: This erro may also be thrown while logging on to o NetBackup Administration Console com um different erro message e you will não be able to log in.", - "first_action": "If o certificate foi revoked in erro, reissue um certificate para o host.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ If o certificate foi revoked in erro, reissue um certificate para o host.\n■ If o certificate foi revoked como intended, um attempted security breach may\nhave ocorreu.\n■ Contate seu security administrator." + "desc": "The Peer Certificate is revoked Note: This error may also be thrown while logging on to the NetBackup Administration Console with a different error message and you will not be able to log in.", + "first_action": "If the certificate was revoked in error, reissue a certificate for the host.", + "full_action": "Do the following, as appropriate:\n■ If the certificate was revoked in error, reissue a certificate for the host.\n■ If the certificate was revoked as intended, an attempted security breach may\nhave occurred.\n■ Contact your security administrator." }, "7654": { "code": 7654, - "desc": "O Certificate Revocation List está inválido Note: This erro may also be thrown while logging on to o NetBackup Administration Console com um different erro message e you will não be able to log in.", - "first_action": "On o host que has o inválido CRL, run o seguinte", - "full_action": "On o host que has o inválido CRL, run o seguinte\ncomando como um administrator to get um fresh CRL:\nUNIX:\n/usr/openv/netbackup/bin/nbcertcmd -getCRL\nWindows:\ninstall_path\\Veritas\\NetBackup\\bin\\nbcertcmd -getCRL" + "desc": "The Certificate Revocation List is invalid Note: This error may also be thrown while logging on to the NetBackup Administration Console with a different error message and you will not be able to log in.", + "first_action": "On the host that has the invalid CRL, run the following", + "full_action": "On the host that has the invalid CRL, run the following\ncommand as an administrator to get a fresh CRL:\nUNIX:\n/usr/openv/netbackup/bin/nbcertcmd -getCRL\nWindows:\ninstall_path\\Veritas\\NetBackup\\bin\\nbcertcmd -getCRL" }, "7655": { "code": 7655, - "desc": "Certificate Revocation List está signed incorrectly Note: This erro may also be thrown while logging on to o NetBackup Administration Console com um different erro message e you will não be able to log in.", - "first_action": "O CRL may have been replaced. On o host que has", - "full_action": "O CRL may have been replaced. On o host que has\no incorrectly signed CRL, run o seguinte comando como um administrator to get\num fresh CRL:\nUNIX:\n/usr/openv/netbackup/bin/nbcertcmd -getCRL\nWindows:\ninstall_path\\Veritas\\NetBackup\\bin\\nbcertcmd -getCRL" + "desc": "Certificate Revocation List is signed incorrectly Note: This error may also be thrown while logging on to the NetBackup Administration Console with a different error message and you will not be able to log in.", + "first_action": "The CRL may have been replaced. On the host that has", + "full_action": "The CRL may have been replaced. On the host that has\nthe incorrectly signed CRL, run the following command as an administrator to get\na fresh CRL:\nUNIX:\n/usr/openv/netbackup/bin/nbcertcmd -getCRL\nWindows:\ninstall_path\\Veritas\\NetBackup\\bin\\nbcertcmd -getCRL" }, "7656": { "code": 7656, - "desc": "Certificate Revocation List está fora de date Note: This erro may also be thrown while logging on to o NetBackup Administration Console com um different erro message e you will não be able to log in.", - "first_action": "On o host que has o inválido CRL, run o seguinte", - "full_action": "On o host que has o inválido CRL, run o seguinte\ncomando como um administrator to get um fresh CRL:\nUNIX:\n/usr/openv/netbackup/bin/nbcertcmd -getCRL\nWindows:\ninstall_path\\Veritas\\NetBackup\\bin\\nbcertcmd -getCRL" + "desc": "Certificate Revocation List is out of date Note: This error may also be thrown while logging on to the NetBackup Administration Console with a different error message and you will not be able to log in.", + "first_action": "On the host that has the invalid CRL, run the following", + "full_action": "On the host that has the invalid CRL, run the following\ncommand as an administrator to get a fresh CRL:\nUNIX:\n/usr/openv/netbackup/bin/nbcertcmd -getCRL\nWindows:\ninstall_path\\Veritas\\NetBackup\\bin\\nbcertcmd -getCRL" }, "7657": { "code": 7657, - "desc": "Não é possível identify service type de acceptor", + "desc": "Cannot identify service type of acceptor", "first_action": "Iftheproblempersists,contactCohesityTechnicalSupport.", "full_action": "Iftheproblempersists,contactCohesityTechnicalSupport." }, "7658": { "code": 7658, - "desc": "Conexão não é possível be established because o host validation não é possível be performed on o target host.", + "desc": "Connection cannot be established because the host validation cannot be performed on the target host.", "first_action": "Iftheproblempersists,contactCohesityTechnicalSupport.", "full_action": "Iftheproblempersists,contactCohesityTechnicalSupport." }, "7659": { "code": 7659, - "desc": "Conexão não é possível be established because o host validation falhou on o target host.", - "first_action": "Garanta que o NetBackup master servidor name e other host names estão", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Garanta que o NetBackup master servidor name e other host names estão\ncorrectly configurado on o remote host.\n■ Garanta que o pending mapping requests para this host estão approved, ou, in o\nNetBackup Administration Console, select o Security Management >\nGlobal Security Settings > Secure Communication > Automatically map\nNetBackup host ID to host names option.\n■ If you have recently instalado ou upgraded NetBackup, garanta que o security\ncertificates estão correctly deployed on todos hosts." + "desc": "Connection cannot be established because the host validation failed on the target host.", + "first_action": "Ensure that the NetBackup master server name and other host names are", + "full_action": "Do the following, as appropriate:\n■ Ensure that the NetBackup master server name and other host names are\ncorrectly configured on the remote host.\n■ Ensure that the pending mapping requests for this host are approved, or, in the\nNetBackup Administration Console, select the Security Management >\nGlobal Security Settings > Secure Communication > Automatically map\nNetBackup host ID to host names option.\n■ If you have recently installed or upgraded NetBackup, ensure that the security\ncertificates are correctly deployed on all hosts." }, "7660": { "code": 7660, - "desc": "O peer proxy não é possível find usable certificates para o certificate protocol", - "first_action": "Verifique que certificates have been successfully deployed", - "full_action": "Verifique que certificates have been successfully deployed\non o proxy peer host. If o problema occurs after certificates have been deployed\nsuccessfully, save todos o erro log informação e contate Cohesity Technical\nSupport para assistance." + "desc": "The peer proxy cannot find usable certificates for the certificate protocol", + "first_action": "Verify that certificates have been successfully deployed", + "full_action": "Verify that certificates have been successfully deployed\non the proxy peer host. If the problem occurs after certificates have been deployed\nsuccessfully, save all the error log information and contact Cohesity Technical\nSupport for assistance." }, "7662": { "code": 7662, "desc": "Theexternalcertificatecannotbeautomaticallyenrolled.Thepeerhost’s external certificate must be already enrolled.", - "first_action": "1. Verifique o enrollment status on communicating hosts usando o nbcertcmd", - "full_action": "Do o seguinte:\n1. Verifique o enrollment status on communicating hosts usando o nbcertcmd\n-listEnrollmentStatus comando. If both hosts estão não enrolled, manually\nenroll one de o hosts, preferably o NetBackup servidor, usando o nbcertcmd\n-enrollCertificate comando.\n2. If o problema persists, contate Cohesity Technical Support." + "first_action": "1. Check the enrollment status on communicating hosts using the nbcertcmd", + "full_action": "Do the following:\n1. Check the enrollment status on communicating hosts using the nbcertcmd\n-listEnrollmentStatus command. If both hosts are not enrolled, manually\nenroll one of the hosts, preferably the NetBackup server, using the nbcertcmd\n-enrollCertificate command.\n2. If the problem persists, contact Cohesity Technical Support." }, "7663": { "code": 7663, - "desc": "O matching master servidor name está não disponível in o NetBackup configuration arquivo, which está requerido para o automatic enrollment de o external certificate.", + "desc": "The matching master server name is not available in the NetBackup configuration file, which is required for the automatic enrollment of the external certificate.", "first_action": "1. EnsurethatthemasterservernameisaddedasaserverentryintheNetBackup", - "full_action": "Do o seguinte:\n1. EnsurethatthemasterservernameisaddedasaserverentryintheNetBackup\nconfiguration arquivo de o respective host.\n2. If o servidor entry está present, verifique o subjectAltName extension de o\nNetBackup’s web servidor external certificate. Then, update o NetBackup\nconfiguration arquivo com o correct servidor name entry.\n3. If NetBackup configuration has correct servidor entry, but subjectAltName\nextension does não have o requerido host name, contate seu Security\nAdministrator. You need to get um external certificate com o correct\nsubjetAltName extension.\n4. If o problema persists, contate Cohesity Technical Support." + "full_action": "Do the following:\n1. EnsurethatthemasterservernameisaddedasaserverentryintheNetBackup\nconfiguration file of the respective host.\n2. If the server entry is present, check the subjectAltName extension of the\nNetBackup’s web server external certificate. Then, update the NetBackup\nconfiguration file with the correct server name entry.\n3. If NetBackup configuration has correct server entry, but subjectAltName\nextension does not have the required host name, contact your Security\nAdministrator. You need to get an external certificate with the correct\nsubjetAltName extension.\n4. If the problem persists, contact Cohesity Technical Support." }, "7720": { "code": 7720, - "desc": "External certificate está não configurado para o NetBackup host, therefore it não é possível be removed.", - "first_action": "Garanta que o external certificate está configurado before", - "full_action": "Garanta que o external certificate está configurado before\nyou executar this operation." + "desc": "External certificate is not configured for the NetBackup host, therefore it cannot be removed.", + "first_action": "Ensure that the external certificate is configured before", + "full_action": "Ensure that the external certificate is configured before\nyou perform this operation." }, "7721": { "code": 7721, - "desc": "ExternalcertificateisnotconfiguredfortheNetBackupwebUI,therefore it não é possível be removed.", - "first_action": "Garanta que o external certificate está configurado before", - "full_action": "Garanta que o external certificate está configurado before\nyou executar this operation." + "desc": "ExternalcertificateisnotconfiguredfortheNetBackupwebUI,therefore it cannot be removed.", + "first_action": "Ensure that the external certificate is configured before", + "full_action": "Ensure that the external certificate is configured before\nyou perform this operation." }, "7722": { "code": 7722, - "desc": "NetBackup host communication fails if you remove o given certificate.", - "first_action": "Garanta que either um NetBackup certificate ou um external", - "full_action": "Garanta que either um NetBackup certificate ou um external\ncertificate está present para host communication." + "desc": "NetBackup host communication fails if you remove the given certificate.", + "first_action": "Ensure that either a NetBackup certificate or an external", + "full_action": "Ensure that either a NetBackup certificate or an external\ncertificate is present for host communication." }, "7723": { "code": 7723, - "desc": "Communication com o NetBackup web UI fails if you remove o certificate. NetBackup status codes 945 NetBackup status codes", - "first_action": "Garanta que either um NetBackup certificate ou um external", - "full_action": "Garanta que either um NetBackup certificate ou um external\ncertificate para o web UI está present para communication." + "desc": "Communication with the NetBackup web UI fails if you remove the certificate. NetBackup status codes 945 NetBackup status codes", + "first_action": "Ensure that either a NetBackup certificate or an external", + "full_action": "Ensure that either a NetBackup certificate or an external\ncertificate for the web UI is present for communication." }, "7724": { "code": 7724, - "desc": "O certificate não é possível be removed.", - "first_action": "From o /usr/openv/wmc/webserver/logs/ ou o", - "full_action": "Based on seu operating system, collect o logs que estão\nshown from o time de o erro e contate Cohesity Technical Support.\n■ From o /usr/openv/wmc/webserver/logs/ ou o\ninstall_path\\Veritas\\NetBackup\\wmc\\webserver\\logs\\ diretório, collect\no configureWebServerCerts.log.\n■ From o /usr/openv/netbackup/logs/nbwebservice ou o\ninstall_path\\Veritas\\NetBackup\\logs\\nbwebservicedirectory,collectthe\n*.log.\n■ From o /usr/openv/netbackup/bin/admincmd ou o\ninstall_path\\Veritas\\NetBackup\\bin\\admincmd diretório, use o\nnbauditreport comando to collect o audit records.\n■ From o /usr/openv/netbackup/logs/nblibcurlcmd ou o\ninstall_path\\Veritas\\NetBackup\\logs\\nblibcurlcmddirectory,collectthe\n*.log." + "desc": "The certificate cannot be removed.", + "first_action": "From the /usr/openv/wmc/webserver/logs/ or the", + "full_action": "Based on your operating system, collect the logs that are\nshown from the time of the error and contact Cohesity Technical Support.\n■ From the /usr/openv/wmc/webserver/logs/ or the\ninstall_path\\Veritas\\NetBackup\\wmc\\webserver\\logs\\ directory, collect\nthe configureWebServerCerts.log.\n■ From the /usr/openv/netbackup/logs/nbwebservice or the\ninstall_path\\Veritas\\NetBackup\\logs\\nbwebservicedirectory,collectthe\n*.log.\n■ From the /usr/openv/netbackup/bin/admincmd or the\ninstall_path\\Veritas\\NetBackup\\bin\\admincmd directory, use the\nnbauditreport command to collect the audit records.\n■ From the /usr/openv/netbackup/logs/nblibcurlcmd or the\ninstall_path\\Veritas\\NetBackup\\logs\\nblibcurlcmddirectory,collectthe\n*.log." }, "7725": { "code": 7725, - "desc": "List de certificates não é possível be retrieved.", - "first_action": "From o /usr/openv/wmc/webserver/logs/ ou o", - "full_action": "Based on seu operating system, collect o logs que estão\nshown from o time de o erro e contate Cohesity Technical Support.\n■ From o /usr/openv/wmc/webserver/logs/ ou o\ninstall_path\\Veritas\\NetBackup\\wmc\\webserver\\logs\\ diretório, collect\no configureWebServerCerts.log.\n■ From o /usr/openv/netbackup/logs/nbwebservice ou o\ninstall_path\\Veritas\\NetBackup\\logs\\nbwebservicedirectory,collectthe\n*.log.\n■ From o /usr/openv/netbackup/bin/admincmd ou o\ninstall_path\\Veritas\\NetBackup\\bin\\admincmd diretório, use o\nnbauditreport comando to collect o audit records.\n■ From o /usr/openv/netbackup/logs/nblibcurlcmd ou o\ninstall_path\\Veritas\\NetBackup\\logs\\nblibcurlcmddirectory,collectthe\n*.log." + "desc": "List of certificates cannot be retrieved.", + "first_action": "From the /usr/openv/wmc/webserver/logs/ or the", + "full_action": "Based on your operating system, collect the logs that are\nshown from the time of the error and contact Cohesity Technical Support.\n■ From the /usr/openv/wmc/webserver/logs/ or the\ninstall_path\\Veritas\\NetBackup\\wmc\\webserver\\logs\\ directory, collect\nthe configureWebServerCerts.log.\n■ From the /usr/openv/netbackup/logs/nbwebservice or the\ninstall_path\\Veritas\\NetBackup\\logs\\nbwebservicedirectory,collectthe\n*.log.\n■ From the /usr/openv/netbackup/bin/admincmd or the\ninstall_path\\Veritas\\NetBackup\\bin\\admincmd directory, use the\nnbauditreport command to collect the audit records.\n■ From the /usr/openv/netbackup/logs/nblibcurlcmd or the\ninstall_path\\Veritas\\NetBackup\\logs\\nblibcurlcmddirectory,collectthe\n*.log." }, "7726": { "code": 7726, - "desc": "O certificate ID está não valid.", - "first_action": "1. Configure ou excluir um NetBackup certificate.", - "full_action": "You must specify um valid certificate ID when you executar\nqualquer de o listed actions:\n1. Configure ou excluir um NetBackup certificate.\n2. Configure ou excluir um external certificate para um NetBackup host.\n3. Configure ou excluir um external certificate para o NetBackup web UI." + "desc": "The certificate ID is not valid.", + "first_action": "1. Configure or delete a NetBackup certificate.", + "full_action": "You must specify a valid certificate ID when you perform\nany of the listed actions:\n1. Configure or delete a NetBackup certificate.\n2. Configure or delete an external certificate for a NetBackup host.\n3. Configure or delete an external certificate for the NetBackup web UI." }, "7727": { "code": 7727, "desc": "TheNetBackupCA-issuedcertificatescannotbedeletedusingNetBackup APIs.", - "first_action": "Use o configureWebServerCerts -removeNBCert", - "full_action": "Use o configureWebServerCerts -removeNBCert\ncomando to excluir o certificates." + "first_action": "Use the configureWebServerCerts -removeNBCert", + "full_action": "Use the configureWebServerCerts -removeNBCert\ncommand to delete the certificates." }, "7728": { "code": 7728, - "desc": "O input arquivo de ECA configuration está não valid.", - "first_action": "Garanta que o input arquivo está in o requerido format. Review", - "full_action": "Garanta que o input arquivo está in o requerido format. Review\no permissions on o NetBackup Install\nDirectory/var/global/wsl/credentials folder. If o problema persists, save todos\no erro logs, e contate Cohesity Technical Support." + "desc": "The input file of ECA configuration is not valid.", + "first_action": "Ensure that the input file is in the required format. Review", + "full_action": "Ensure that the input file is in the required format. Review\nthe permissions on the NetBackup Install\nDirectory/var/global/wsl/credentials folder. If the problem persists, save all\nthe error logs, and contact Cohesity Technical Support." }, "7729": { "code": 7729, - "desc": "O specified CRL verifique level value está não valid.", - "first_action": "Specify one de o CRL verifique levels shown: CHAIN, LEAF,", - "full_action": "Specify one de o CRL verifique levels shown: CHAIN, LEAF,\nou DISABLE." + "desc": "The specified CRL check level value is not valid.", + "first_action": "Specify one of the CRL check levels shown: CHAIN, LEAF,", + "full_action": "Specify one of the CRL check levels shown: CHAIN, LEAF,\nor DISABLE." }, "7730": { "code": 7730, - "desc": "O private key não é possível be added.", + "desc": "The private key cannot be added.", "first_action": "Ensurethattheexternalcertificateparameters(certificate", - "full_action": "Ensurethattheexternalcertificateparameters(certificate\nchain, private key, e trust store) estão in o correct format. If o problema persists,\nsave todos o erro logs, e contate Cohesity Technical Support." + "full_action": "Ensurethattheexternalcertificateparameters(certificate\nchain, private key, and trust store) are in the correct format. If the problem persists,\nsave all the error logs, and contact Cohesity Technical Support." }, "7731": { "code": 7731, - "desc": "O trust bundle não é possível be added.", + "desc": "The trust bundle cannot be added.", "first_action": "Ensurethattheexternalcertificateparameters(certificate", - "full_action": "Ensurethattheexternalcertificateparameters(certificate\nchain, private key, e trust store) estão in o correct format. If o problema persists,\nsave todos o erro logs, e contate Cohesity Technical Support." + "full_action": "Ensurethattheexternalcertificateparameters(certificate\nchain, private key, and trust store) are in the correct format. If the problem persists,\nsave all the error logs, and contact Cohesity Technical Support." }, "7732": { "code": 7732, "desc": "TheNetBackupCA-issuedcertificatescannotbeaddedusingNetBackup APIs.", "first_action": "UsetheconfigureWebServerCerts -addNBCertcommand", - "full_action": "UsetheconfigureWebServerCerts -addNBCertcommand\nto configure o certificates." + "full_action": "UsetheconfigureWebServerCerts -addNBCertcommand\nto configure the certificates." }, "7733": { "code": 7733, - "desc": "External certificate de o NetBackup web UI não é possível be removed.", - "first_action": "From o /usr/openv/wmc/webserver/logs/ ou o", - "full_action": "Based on seu operating system, collect o logs que estão\nshown from o time de o erro e contate Cohesity Technical Support.\n■ From o /usr/openv/wmc/webserver/logs/ ou o\ninstall_path\\Veritas\\NetBackup\\wmc\\webserver\\logs\\ diretório, collect\no configureWebServerCerts.log.\n■ From o /usr/openv/netbackup/logs/nbwebservice ou o\ninstall_path\\Veritas\\NetBackup\\logs\\nbwebservicedirectory,collectthe\n*.log.\n■ From o /usr/openv/netbackup/bin/admincmd ou o\ninstall_path\\Veritas\\NetBackup\\bin\\admincmd diretório, use o\nnbauditreport comando to collect o audit records.\n■ From o /usr/openv/netbackup/logs/nblibcurlcmd ou o\ninstall_path\\Veritas\\NetBackup\\logs\\nblibcurlcmddirectory,collectthe\n*.log." + "desc": "External certificate of the NetBackup web UI cannot be removed.", + "first_action": "From the /usr/openv/wmc/webserver/logs/ or the", + "full_action": "Based on your operating system, collect the logs that are\nshown from the time of the error and contact Cohesity Technical Support.\n■ From the /usr/openv/wmc/webserver/logs/ or the\ninstall_path\\Veritas\\NetBackup\\wmc\\webserver\\logs\\ directory, collect\nthe configureWebServerCerts.log.\n■ From the /usr/openv/netbackup/logs/nbwebservice or the\ninstall_path\\Veritas\\NetBackup\\logs\\nbwebservicedirectory,collectthe\n*.log.\n■ From the /usr/openv/netbackup/bin/admincmd or the\ninstall_path\\Veritas\\NetBackup\\bin\\admincmd directory, use the\nnbauditreport command to collect the audit records.\n■ From the /usr/openv/netbackup/logs/nblibcurlcmd or the\ninstall_path\\Veritas\\NetBackup\\logs\\nblibcurlcmddirectory,collectthe\n*.log." }, "7734": { "code": 7734, - "desc": "External certificate de o NetBackup host não é possível be removed. NetBackup status codes 949 NetBackup status codes", - "first_action": "From o /usr/openv/wmc/webserver/logs/ ou o", - "full_action": "Based on seu operating system, collect o logs que estão\nshown from o time de o erro e contate Cohesity Technical Support.\n■ From o /usr/openv/wmc/webserver/logs/ ou o\ninstall_path\\Veritas\\NetBackup\\wmc\\webserver\\logs\\ diretório, collect\no configureWebServerCerts.log.\n■ From o /usr/openv/netbackup/logs/nbwebservice ou o\ninstall_path\\Veritas\\NetBackup\\logs\\nbwebservicedirectory,collectthe\n*.log.\n■ From o /usr/openv/netbackup/bin/admincmd ou o\ninstall_path\\Veritas\\NetBackup\\bin\\admincmd diretório, use o\nnbauditreport comando to collect o audit records.\n■ From o /usr/openv/netbackup/logs/nblibcurlcmd ou o\ninstall_path\\Veritas\\NetBackup\\logs\\nblibcurlcmddirectory,collectthe\n*.log." + "desc": "External certificate of the NetBackup host cannot be removed. NetBackup status codes 949 NetBackup status codes", + "first_action": "From the /usr/openv/wmc/webserver/logs/ or the", + "full_action": "Based on your operating system, collect the logs that are\nshown from the time of the error and contact Cohesity Technical Support.\n■ From the /usr/openv/wmc/webserver/logs/ or the\ninstall_path\\Veritas\\NetBackup\\wmc\\webserver\\logs\\ directory, collect\nthe configureWebServerCerts.log.\n■ From the /usr/openv/netbackup/logs/nbwebservice or the\ninstall_path\\Veritas\\NetBackup\\logs\\nbwebservicedirectory,collectthe\n*.log.\n■ From the /usr/openv/netbackup/bin/admincmd or the\ninstall_path\\Veritas\\NetBackup\\bin\\admincmd directory, use the\nnbauditreport command to collect the audit records.\n■ From the /usr/openv/netbackup/logs/nblibcurlcmd or the\ninstall_path\\Veritas\\NetBackup\\logs\\nblibcurlcmddirectory,collectthe\n*.log." }, "7750": { "code": 7750, - "desc": "O dashboard security status request ou o data que está sent está não valid.", - "first_action": "Retry o operation com valid request e data.", - "full_action": "Retry o operation com valid request e data." + "desc": "The dashboard security status request or the data that is sent is not valid.", + "first_action": "Retry the operation with valid request and data.", + "full_action": "Retry the operation with valid request and data." }, "7751": { "code": 7751, - "desc": "O security status request não é possível be processed.", - "first_action": "Review o NetBackup troubleshooting guide para additional informação about", - "full_action": "Executar o seguinte como appropriate:\n■ Review o NetBackup troubleshooting guide para additional informação about\no erro.\n■ Increasethelogginglevelandretrytheoperation.Iftheproblempersists,contact\nCohesity Technical Support." + "desc": "The security status request cannot be processed.", + "first_action": "Review the NetBackup troubleshooting guide for additional information about", + "full_action": "Perform the following as appropriate:\n■ Review the NetBackup troubleshooting guide for additional information about\nthe error.\n■ Increasethelogginglevelandretrytheoperation.Iftheproblempersists,contact\nCohesity Technical Support." }, "7752": { "code": 7752, - "desc": "O Alta View usuário should executar o operation.", - "first_action": "Executar o operation from Alta View.", - "full_action": "Executar o operation from Alta View." + "desc": "The Alta View user should perform the operation.", + "first_action": "Perform the operation from Alta View.", + "full_action": "Perform the operation from Alta View." }, "7800": { "code": 7800, - "desc": "Não foi possível to display o details para todos identity providers.", - "first_action": "Retry o operation ou verifique o banco de dados conexão.", - "full_action": "Retry o operation ou verifique o banco de dados conexão." + "desc": "Unable to display the details for all identity providers.", + "first_action": "Retry the operation or check the database connection.", + "full_action": "Retry the operation or check the database connection." }, "7801": { "code": 7801, - "desc": "Não foi possível to display o details para o identity provider com o specified name.", - "first_action": "Retry o operation ou verifique o banco de dados conexão.", - "full_action": "Retry o operation ou verifique o banco de dados conexão." + "desc": "Unable to display the details for the identity provider with the specified name.", + "first_action": "Retry the operation or check the database connection.", + "full_action": "Retry the operation or check the database connection." }, "7802": { "code": 7802, - "desc": "Falhou to add o identity provider.", - "first_action": "Retry o operation ou verifique o banco de dados conexão.", - "full_action": "Retry o operation ou verifique o banco de dados conexão." + "desc": "Failed to add the identity provider.", + "first_action": "Retry the operation or check the database connection.", + "full_action": "Retry the operation or check the database connection." }, "7803": { "code": 7803, - "desc": "O IDP configuration contains inválido arguments ou details.", + "desc": "The IDP configuration contains invalid arguments or details.", "first_action": "Reviewallargumentvaluesandverifythattheyarecorrect.", - "full_action": "Reviewallargumentvaluesandverifythattheyarecorrect.\nRetry o operation." + "full_action": "Reviewallargumentvaluesandverifythattheyarecorrect.\nRetry the operation." }, "7804": { "code": 7804, - "desc": "Falhou to excluir o configuration para o identity provider.", - "first_action": "Retry o operation ou verifique o banco de dados conexão.", - "full_action": "Retry o operation ou verifique o banco de dados conexão." + "desc": "Failed to delete the configuration for the identity provider.", + "first_action": "Retry the operation or check the database connection.", + "full_action": "Retry the operation or check the database connection." }, "7805": { "code": 7805, - "desc": "Falhou to update o details para o configurado identity provider com o specified name.", - "first_action": "Retry o operation ou verifique o banco de dados conexão.", - "full_action": "Retry o operation ou verifique o banco de dados conexão." + "desc": "Failed to update the details for the configured identity provider with the specified name.", + "first_action": "Retry the operation or check the database connection.", + "full_action": "Retry the operation or check the database connection." }, "7806": { "code": 7806, - "desc": "Um IDP configuration com o specified name already exists. NetBackup status codes 952 NetBackup status codes", - "first_action": "Verifique o IDP configuration name que you used e add", - "full_action": "Verifique o IDP configuration name que you used e add\nIDP configuration com um different name." + "desc": "An IDP configuration with the specified name already exists. NetBackup status codes 952 NetBackup status codes", + "first_action": "Verify the IDP configuration name that you used and add", + "full_action": "Verify the IDP configuration name that you used and add\nIDP configuration with a different name." }, "7807": { "code": 7807, - "desc": "Um IDP configuration com o specified name does não exist.", - "first_action": "Provide o correct IDP configuration name ou um existing", - "full_action": "Provide o correct IDP configuration name ou um existing\nIDP configuration name." + "desc": "An IDP configuration with the specified name does not exist.", + "first_action": "Provide the correct IDP configuration name or an existing", + "full_action": "Provide the correct IDP configuration name or an existing\nIDP configuration name." }, "7808": { "code": 7808, - "desc": "Um vazio ou um null name foi specified.", - "first_action": "Provide o non-empty ou non-null name. Retry o", - "full_action": "Provide o non-empty ou non-null name. Retry o\noperation." + "desc": "An empty or a null name was specified.", + "first_action": "Provide the non-empty or non-null name. Retry the", + "full_action": "Provide the non-empty or non-null name. Retry the\noperation." }, "7809": { "code": 7809, - "desc": "Um inválido IDP configuration name foi specified. O name can apenas contain o seguinte characters: a-z, A-Z, 0-9, -, _.", - "first_action": "Provide um name com characters from this category: a-z,", - "full_action": "Provide um name com characters from this category: a-z,\nA-Z, 0-9, -, _" + "desc": "An invalid IDP configuration name was specified. The name can only contain the following characters: a-z, A-Z, 0-9, -, _.", + "first_action": "Provide a name with characters from this category: a-z,", + "full_action": "Provide a name with characters from this category: a-z,\nA-Z, 0-9, -, _" }, "7810": { "code": 7810, - "desc": "Falhou to get service provider metadata.", - "first_action": "Review o metadata arquivo e provide o correct IDP metadata content.", - "full_action": "Executar o seguinte como appropriate:\n■ Review o metadata arquivo e provide o correct IDP metadata content.\n■ Generate o Java keystore." + "desc": "Failed to get service provider metadata.", + "first_action": "Review the metadata file and provide the correct IDP metadata content.", + "full_action": "Perform the following as appropriate:\n■ Review the metadata file and provide the correct IDP metadata content.\n■ Generate the Java keystore." }, "7811": { "code": 7811, - "desc": "Um attempt foi made to enable um new ou um existing IDP configuration when there está already um IDP configuration que está enabled.", - "first_action": "Disable o enabled IDP e then retry o requerido", - "full_action": "Disable o enabled IDP e then retry o requerido\noperation." + "desc": "An attempt was made to enable a new or an existing IDP configuration when there is already an IDP configuration that is enabled.", + "first_action": "Disable the enabled IDP and then retry the required", + "full_action": "Disable the enabled IDP and then retry the required\noperation." }, "7812": { "code": 7812, "desc": "At least one IDP configuration must be enabled.", - "first_action": "Review seu IDP configuration e enable at least one de", - "full_action": "Review seu IDP configuration e enable at least one de\no configurations." + "first_action": "Review your IDP configuration and enable at least one of", + "full_action": "Review your IDP configuration and enable at least one of\nthe configurations." }, "7813": { "code": 7813, - "desc": "Theenablefieldorthemetadatafieldisnotpresentintheupdateidentity providerpayload.Oneofthefieldsisrequiredtoupdatethedetailsfortheconfigured identity provider com o specified name. NetBackup status codes 954 NetBackup status codes", - "first_action": "Provide values para either o -e (enable) field ou o -mxp", - "full_action": "Provide values para either o -e (enable) field ou o -mxp\n(metadata) field usando o CLI ou either o enable ou o idpMetadata fields in um\nupdate API payload." + "desc": "Theenablefieldorthemetadatafieldisnotpresentintheupdateidentity providerpayload.Oneofthefieldsisrequiredtoupdatethedetailsfortheconfigured identity provider with the specified name. NetBackup status codes 954 NetBackup status codes", + "first_action": "Provide values for either the -e (enable) field or the -mxp", + "full_action": "Provide values for either the -e (enable) field or the -mxp\n(metadata) field using the CLI or either the enable or the idpMetadata fields in an\nupdate API payload." }, "7814": { "code": 7814, - "desc": "O specified arquivo does não have expected format.", - "first_action": "Verifique que o metadata arquivo está in o correct .xml format.", - "full_action": "Verifique que o metadata arquivo está in o correct .xml format.\nRetry o operation e if o issue persists, visit o Cohesity Technical Support\nwebsite. O Cohesity Technical Support website offers additional informação to\nhelp you troubleshoot this issue." + "desc": "The specified file does not have expected format.", + "first_action": "Verify that the metadata file is in the correct .xml format.", + "full_action": "Verify that the metadata file is in the correct .xml format.\nRetry the operation and if the issue persists, visit the Cohesity Technical Support\nwebsite. The Cohesity Technical Support website offers additional information to\nhelp you troubleshoot this issue." }, "7815": { "code": 7815, - "desc": "Falhou to redirect to o IDP servidor.", - "first_action": "Review o metadata arquivo e provide o correct IDP metadata content.", - "full_action": "Executar o seguinte como appropriate:\n■ Review o metadata arquivo e provide o correct IDP metadata content.\n■ Generate o Java keystore." + "desc": "Failed to redirect to the IDP server.", + "first_action": "Review the metadata file and provide the correct IDP metadata content.", + "full_action": "Perform the following as appropriate:\n■ Review the metadata file and provide the correct IDP metadata content.\n■ Generate the Java keystore." }, "7850": { "code": 7850, - "desc": "Não foi possível to create mount due to um erro in Instant Access.", - "first_action": "Verifique que o BYO para Instant Access está done e que", - "full_action": "Verifique que o BYO para Instant Access está done e que\nInstant Access properly functions. Refer to o NetBackup Administrator’s Guide,\nVolume I para more details." + "desc": "Unable to create mount due to an error in Instant Access.", + "first_action": "Verify that the BYO for Instant Access is done and that", + "full_action": "Verify that the BYO for Instant Access is done and that\nInstant Access properly functions. Refer to the NetBackup Administrator’s Guide,\nVolume I for more details." }, "7851": { "code": 7851, - "desc": "Não foi possível to verifique status de o mount due to um erro in Instant Access.", - "first_action": "Verifique que o BYO para Instant Access está done e que", - "full_action": "Verifique que o BYO para Instant Access está done e que\nInstant Access properly functions. Refer to o NetBackup Administrator’s Guide,\nVolume I para more details." + "desc": "Unable to check status of the mount due to an error in Instant Access.", + "first_action": "Verify that the BYO for Instant Access is done and that", + "full_action": "Verify that the BYO for Instant Access is done and that\nInstant Access properly functions. Refer to the NetBackup Administrator’s Guide,\nVolume I for more details." }, "7852": { "code": 7852, - "desc": "Workload está não supported para malware detection.", - "first_action": "Apenas standard e Windows workloads estão supported para", - "full_action": "Apenas standard e Windows workloads estão supported para\nmalware detection." + "desc": "Workload is not supported for malware detection.", + "first_action": "Only standard and Windows workloads are supported for", + "full_action": "Only standard and Windows workloads are supported for\nmalware detection." }, "7853": { "code": 7853, - "desc": "Não foi possível to get details de o image from o catalog.", - "first_action": "Verifique que o backup image exists in catalog e que it", - "full_action": "Verifique que o backup image exists in catalog e que it\nestá não be expired." + "desc": "Unable to get details of the image from the catalog.", + "first_action": "Verify that the backup image exists in catalog and that it", + "full_action": "Verify that the backup image exists in catalog and that it\nis not be expired." }, "7854": { "code": 7854, - "desc": "Specified scan host pool está inválido.", - "first_action": "You must provide um valid scan host pool.", - "full_action": "You must provide um valid scan host pool." + "desc": "Specified scan host pool is invalid.", + "first_action": "You must provide a valid scan host pool.", + "full_action": "You must provide a valid scan host pool." }, "7855": { "code": 7855, - "desc": "Não foi possível to create um worklist.", - "first_action": "VerifythattheNetBackupservices estão up.Alsoverifythat", - "full_action": "VerifythattheNetBackupservices estão up.Alsoverifythat\no banco de dados está disponível." + "desc": "Unable to create a worklist.", + "first_action": "VerifythattheNetBackupservices are up.Alsoverifythat", + "full_action": "VerifythattheNetBackupservices are up.Alsoverifythat\nthe database is available." }, "7856": { "code": 7856, - "desc": "Inválido backupId.", - "first_action": "If um backup image host pool scan está already in progress.", - "full_action": "Review o seguinte como appropriate:\n■ If um backup image host pool scan está already in progress.\n■ IfthebackupimagehasanInstantAccesscapablecopy.RefertotheNetBackup\nAdministrator’s Guide, Volume I para more details.\n■ O mídia servidor should have Linux e um NetBackup version 9.1.2 ou newer." + "desc": "Invalid backupId.", + "first_action": "If a backup image host pool scan is already in progress.", + "full_action": "Review the following as appropriate:\n■ If a backup image host pool scan is already in progress.\n■ IfthebackupimagehasanInstantAccesscapablecopy.RefertotheNetBackup\nAdministrator’s Guide, Volume I for more details.\n■ The media server should have Linux and a NetBackup version 9.1.2 or newer." }, "7857": { "code": 7857, - "desc": "Scan host pool está não provided in o request.", - "first_action": "You must provide um valid scan host pool.", - "full_action": "You must provide um valid scan host pool." + "desc": "Scan host pool is not provided in the request.", + "first_action": "You must provide a valid scan host pool.", + "full_action": "You must provide a valid scan host pool." }, "7858": { "code": 7858, - "desc": "Malware tool está não specified in o request.", - "first_action": "You must provide um valid malware tool.", - "full_action": "You must provide um valid malware tool." + "desc": "Malware tool is not specified in the request.", + "first_action": "You must provide a valid malware tool.", + "full_action": "You must provide a valid malware tool." }, "7859": { "code": 7859, - "desc": "Scan host name está não specified in o request.", - "first_action": "You must provide um unique scan host name.", - "full_action": "You must provide um unique scan host name." + "desc": "Scan host name is not specified in the request.", + "first_action": "You must provide a unique scan host name.", + "full_action": "You must provide a unique scan host name." }, "7860": { "code": 7860, - "desc": "Scan host pool name está não specified in o request.", - "first_action": "You must provide um unique scan host pool name when um", - "full_action": "You must provide um unique scan host pool name when um\nnew one está created." + "desc": "Scan host pool name is not specified in the request.", + "first_action": "You must provide a unique scan host pool name when a", + "full_action": "You must provide a unique scan host pool name when a\nnew one is created." }, "7861": { "code": 7861, - "desc": "Share type está não specified in o request.", - "first_action": "You must provide um valid share type.", - "full_action": "You must provide um valid share type." + "desc": "Share type is not specified in the request.", + "first_action": "You must provide a valid share type.", + "full_action": "You must provide a valid share type." }, "7862": { "code": 7862, - "desc": "Specified malware tool está inválido.", - "first_action": "You must provide um valid malware tool.", - "full_action": "You must provide um valid malware tool." + "desc": "Specified malware tool is invalid.", + "first_action": "You must provide a valid malware tool.", + "full_action": "You must provide a valid malware tool." }, "7863": { "code": 7863, - "desc": "Specified scan host está inválido.", - "first_action": "You must provide um valid scan host ID.", - "full_action": "You must provide um valid scan host ID." + "desc": "Specified scan host is invalid.", + "first_action": "You must provide a valid scan host ID.", + "full_action": "You must provide a valid scan host ID." }, "7864": { "code": 7864, - "desc": "O scan host não é possível be created because o scan host name already exists in o banco de dados.", - "first_action": "You must provide um unique scan host name.", - "full_action": "You must provide um unique scan host name." + "desc": "The scan host cannot be created because the scan host name already exists in the database.", + "first_action": "You must provide a unique scan host name.", + "full_action": "You must provide a unique scan host name." }, "7865": { "code": 7865, - "desc": "Thescanhostpoolcannotbecreatedbecausethescanhostpoolname already exists in o banco de dados.", - "first_action": "You must provide um unique scan host pool name.", - "full_action": "You must provide um unique scan host pool name." + "desc": "Thescanhostpoolcannotbecreatedbecausethescanhostpoolname already exists in the database.", + "first_action": "You must provide a unique scan host pool name.", + "full_action": "You must provide a unique scan host pool name." }, "7866": { "code": 7866, - "desc": "O specified malware tool does não exist.", - "first_action": "You must provide um valid malware tool ID from o", - "full_action": "You must provide um valid malware tool ID from o\nsupported malware tool list." + "desc": "The specified malware tool does not exist.", + "first_action": "You must provide a valid malware tool ID from the", + "full_action": "You must provide a valid malware tool ID from the\nsupported malware tool list." }, "7867": { "code": 7867, - "desc": "O malware tool não é possível be created because o malware tool name already exists in o banco de dados.", - "first_action": "O malware tool name must be unique.", - "full_action": "O malware tool name must be unique." + "desc": "The malware tool cannot be created because the malware tool name already exists in the database.", + "first_action": "The malware tool name must be unique.", + "full_action": "The malware tool name must be unique." }, "7868": { "code": 7868, - "desc": "O specified scan host does não exist.", - "first_action": "You must provide um valid scan host.", - "full_action": "You must provide um valid scan host." + "desc": "The specified scan host does not exist.", + "first_action": "You must provide a valid scan host.", + "full_action": "You must provide a valid scan host." }, "7869": { "code": 7869, - "desc": "O specified scan host pool does não exist.", - "first_action": "You must provide um valid scan host pool.", - "full_action": "You must provide um valid scan host pool." + "desc": "The specified scan host pool does not exist.", + "first_action": "You must provide a valid scan host pool.", + "full_action": "You must provide a valid scan host pool." }, "7870": { "code": 7870, - "desc": "O specified scan result does não exist.", - "first_action": "O scan result should exist in o system. Retry o", - "full_action": "O scan result should exist in o system. Retry o\noperationandiftheissuepersists,visitsupport.veritas.com.TheCohesityTechnical\nSupportwebsitesiteoffersadditionalinformationtohelpyoutroubleshootthisissue." + "desc": "The specified scan result does not exist.", + "first_action": "The scan result should exist in the system. Retry the", + "full_action": "The scan result should exist in the system. Retry the\noperationandiftheissuepersists,visitsupport.veritas.com.TheCohesityTechnical\nSupportwebsitesiteoffersadditionalinformationtohelpyoutroubleshootthisissue." }, "7871": { "code": 7871, - "desc": "Inválido scan result request.", - "first_action": "Retry o operation e if o issue persists, visit", - "full_action": "Retry o operation e if o issue persists, visit\nsupport.veritas.com. O Cohesity Technical Support website site offers additional\ninformação to help you troubleshoot this issue." + "desc": "Invalid scan result request.", + "first_action": "Retry the operation and if the issue persists, visit", + "full_action": "Retry the operation and if the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support website site offers additional\ninformation to help you troubleshoot this issue." }, "7872": { "code": 7872, - "desc": "Não scan host foi found para o specified scan host pool.", - "first_action": "You must associate um scan host com um scan host pool.", - "full_action": "You must associate um scan host com um scan host pool." + "desc": "No scan host was found for the specified scan host pool.", + "first_action": "You must associate a scan host with a scan host pool.", + "full_action": "You must associate a scan host with a scan host pool." }, "7873": { "code": 7873, - "desc": "Não foi possível to excluir o mount due to um erro in Instant Access.", - "first_action": "Verifique que Instant Access works e has um backup image", - "full_action": "Verifique que Instant Access works e has um backup image\nmounted. Refer to o NetBackup Administrator’s Guide, Volume I para more details." + "desc": "Unable to delete the mount due to an error in Instant Access.", + "first_action": "Verify that Instant Access works and has a backup image", + "full_action": "Verify that Instant Access works and has a backup image\nmounted. Refer to the NetBackup Administrator’s Guide, Volume I for more details." }, "7874": { "code": 7874, - "desc": "Não foi possível to update o backup image por catalog cliente.", - "first_action": "Verifique que o backup image exists in catalog e que", - "full_action": "Verifique que o backup image exists in catalog e que\nimage está não expired." + "desc": "Unable to update the backup image by catalog client.", + "first_action": "Verify that the backup image exists in catalog and that", + "full_action": "Verify that the backup image exists in catalog and that\nimage is not expired." }, "7875": { "code": 7875, - "desc": "Inválido worklistId.", - "first_action": "Verifique que um valid worklistId está tagged in o request.", - "full_action": "Verifique que um valid worklistId está tagged in o request." + "desc": "Invalid worklistId.", + "first_action": "Verify that a valid worklistId is tagged in the request.", + "full_action": "Verify that a valid worklistId is tagged in the request." }, "7876": { "code": 7876, - "desc": "Inválido scan host credentials.", - "first_action": "If o scan host pool has um SMB share, then verifique que", - "full_action": "If o scan host pool has um SMB share, then verifique que\no Active Diretório details estão provided in o credentials que estão associated com\no scan host." + "desc": "Invalid scan host credentials.", + "first_action": "If the scan host pool has an SMB share, then verify that", + "full_action": "If the scan host pool has an SMB share, then verify that\nthe Active Directory details are provided in the credentials that are associated with\nthe scan host." }, "7877": { "code": 7877, - "desc": "Inválido mídia servidor in image catalog.", - "first_action": "Upgrade o mídia servidor to version 9.1.2 ou newer.", - "full_action": "Executar o seguinte como appropriate:\n■ Upgrade o mídia servidor to version 9.1.2 ou newer.\n■ Verifique if o mídia servidor OS está Linux.\n■ Verifique if o supported mídia servidor está disponível e has connectivity to o\nmasterserver.RefertotheNetBackupAdministrator’sGuide,VolumeIformore\ndetails." + "desc": "Invalid media server in image catalog.", + "first_action": "Upgrade the media server to version 9.1.2 or newer.", + "full_action": "Perform the following as appropriate:\n■ Upgrade the media server to version 9.1.2 or newer.\n■ Check if the media server OS is Linux.\n■ Check if the supported media server is available and has connectivity to the\nmasterserver.RefertotheNetBackupAdministrator’sGuide,VolumeIformore\ndetails." }, "7878": { "code": 7878, - "desc": "Não foi possível to initiate o scan on mídia servidor.", - "first_action": "Um scan não é possível be initialized on o mídia servidor. Verifique", - "full_action": "Um scan não é possível be initialized on o mídia servidor. Verifique\nque o mídia servidor está up e que there estão não conexão issues." + "desc": "Unable to initiate the scan on media server.", + "first_action": "A scan cannot be initialized on the media server. Verify", + "full_action": "A scan cannot be initialized on the media server. Verify\nthat the media server is up and that there are no connection issues." }, "7879": { "code": 7879, - "desc": "Não active scan host foi found in o selected scan host pool.", - "first_action": "You must activate o scan host que está associated com", - "full_action": "You must activate o scan host que está associated com\no scan host pool." + "desc": "No active scan host was found in the selected scan host pool.", + "first_action": "You must activate the scan host that is associated with", + "full_action": "You must activate the scan host that is associated with\nthe scan host pool." }, "7880": { "code": 7880, - "desc": "Não foi possível to assign permissions on scan host credentials.", - "first_action": "Verifique if o supported mídia servidor está disponível e then", - "full_action": "Verifique if o supported mídia servidor está disponível e then\nreinitiate scan." + "desc": "Unable to assign permissions on scan host credentials.", + "first_action": "Verify if the supported media server is available and then", + "full_action": "Verify if the supported media server is available and then\nreinitiate scan." }, "7881": { "code": 7881, - "desc": "O specified scan host pool e scan host mapping does não exist.", - "first_action": "You must provide um valid scan host e scan host pool", - "full_action": "You must provide um valid scan host e scan host pool\nID." + "desc": "The specified scan host pool and scan host mapping does not exist.", + "first_action": "You must provide a valid scan host and scan host pool", + "full_action": "You must provide a valid scan host and scan host pool\nID." }, "7882": { "code": 7882, - "desc": "Specified mídia servidor está não supported.", - "first_action": "Upgrade o mídia servidor to um version que está supported.", - "full_action": "Upgrade o mídia servidor to um version que está supported." + "desc": "Specified media server is not supported.", + "first_action": "Upgrade the media server to a version that is supported.", + "full_action": "Upgrade the media server to a version that is supported." }, "7883": { "code": 7883, - "desc": "Specified mídia servidor está não disponível.", - "first_action": "Verifique que o supported mídia servidor está disponível e", - "full_action": "Verifique que o supported mídia servidor está disponível e\nthen reinitiate scan." + "desc": "Specified media server is not available.", + "first_action": "Verify that the supported media server is available and", + "full_action": "Verify that the supported media server is available and\nthen reinitiate scan." }, "7884": { "code": 7884, - "desc": "Armazenamento servidor does não exist.", - "first_action": "Verifique que armazenamento servidor está disponível ou que it exists.", - "full_action": "Verifique que armazenamento servidor está disponível ou que it exists." + "desc": "Storage server does not exist.", + "first_action": "Verify that storage server is available or that it exists.", + "full_action": "Verify that storage server is available or that it exists." }, "7885": { "code": 7885, - "desc": "Scan result data limite exceeds.", - "first_action": "There estão too many infected arquivos que não é possível be exported", - "full_action": "There estão too many infected arquivos que não é possível be exported\nto one arquivo (limite está 200 MB). Review o detailed infected arquivo list in o scan logs." + "desc": "Scan result data limit exceeds.", + "first_action": "There are too many infected files that cannot be exported", + "full_action": "There are too many infected files that cannot be exported\nto one file (limit is 200 MB). Review the detailed infected file list in the scan logs." }, "7886": { "code": 7886, - "desc": "Inválido scan result ID.", - "first_action": "Verifique que o scan job cancellation foi from um inválido", - "full_action": "Verifique que o scan job cancellation foi from um inválido\nscan result ID. Retry o operation." + "desc": "Invalid scan result ID.", + "first_action": "Verify that the scan job cancellation was from an invalid", + "full_action": "Verify that the scan job cancellation was from an invalid\nscan result ID. Retry the operation." }, "7887": { "code": 7887, - "desc": "Specified X-Trigger-Method header está inválido.", + "desc": "Specified X-Trigger-Method header is invalid.", "first_action": "PleaseenteravalidheaderthatcontainseitherAUTOMATIC", - "full_action": "PleaseenteravalidheaderthatcontainseitherAUTOMATIC\nou MANUAL. If não value está entered, o default value está MANUAL está used." + "full_action": "PleaseenteravalidheaderthatcontainseitherAUTOMATIC\nor MANUAL. If no value is entered, the default value is MANUAL is used." }, "7888": { "code": 7888, - "desc": "Large number de infected arquivos.", - "first_action": "Because o results não é possível be exported ou viewed, you", - "full_action": "Because o results não é possível be exported ou viewed, you\nmust review o scan logs to view um detailed list de o infected arquivos para o selected\nscan result." + "desc": "Large number of infected files.", + "first_action": "Because the results cannot be exported or viewed, you", + "full_action": "Because the results cannot be exported or viewed, you\nmust review the scan logs to view a detailed list of the infected files for the selected\nscan result." }, "7889": { "code": 7889, - "desc": "Too many infected arquivos in o selected time range.", - "first_action": "Select o Allow recovery de arquivos impacted por malware option which can be", - "full_action": "Review o scan logs to view o infected arquivos list para o\nbackup images in o selected date range. Update o date range ou recovery arquivos\ne folders selection to reduce o number de infected arquivos. Retry o operation.\nYou can also executar one de o seguinte:\n■ Select o Allow recovery de arquivos impacted por malware option which can be\nused to recover selective clean arquivos.\n■ Skip que backup image from recovery." + "desc": "Too many infected files in the selected time range.", + "first_action": "Select the Allow recovery of files impacted by malware option which can be", + "full_action": "Review the scan logs to view the infected files list for the\nbackup images in the selected date range. Update the date range or recovery files\nand folders selection to reduce the number of infected files. Retry the operation.\nYou can also perform one of the following:\n■ Select the Allow recovery of files impacted by malware option which can be\nused to recover selective clean files.\n■ Skip that backup image from recovery." }, "7890": { "code": 7890, - "desc": "Não foi possível to excluir o scan host pool.", - "first_action": "Review o scan results page to identify o scan jobs", - "full_action": "Review o scan results page to identify o scan jobs\nque estão usando o scan hosts associated com this scan host pool to scan backup\nimages. Wait para o scan jobs to finish e try again." + "desc": "Unable to delete the scan host pool.", + "first_action": "Review the scan results page to identify the scan jobs", + "full_action": "Review the scan results page to identify the scan jobs\nthat are using the scan hosts associated with this scan host pool to scan backup\nimages. Wait for the scan jobs to finish and try again." }, "7891": { "code": 7891, - "desc": "Não foi possível to excluir o scan host.", - "first_action": "Review o scan results page to identify o scan jobs", - "full_action": "Review o scan results page to identify o scan jobs\nque estão usando o selected scan host to scan backup images. Wait para o scan\njobs to finish e try again." + "desc": "Unable to delete the scan host.", + "first_action": "Review the scan results page to identify the scan jobs", + "full_action": "Review the scan results page to identify the scan jobs\nthat are using the selected scan host to scan backup images. Wait for the scan\njobs to finish and try again." }, "7892": { "code": 7892, - "desc": "Não foi possível to remove o scan host from um scan host pool.", - "first_action": "Review o scan results page to identify o scan jobs", - "full_action": "Review o scan results page to identify o scan jobs\nque estão usando o selected scan host to scan backup images. Wait para o scan job\nto finish e try to remove o scan host from o scan host pool again." + "desc": "Unable to remove the scan host from a scan host pool.", + "first_action": "Review the scan results page to identify the scan jobs", + "full_action": "Review the scan results page to identify the scan jobs\nthat are using the selected scan host to scan backup images. Wait for the scan job\nto finish and try to remove the scan host from the scan host pool again." }, "7893": { "code": 7893, - "desc": "Não scan process foi found para o specified scan result.", - "first_action": "Review o scan result ID to get o correct scan process", - "full_action": "Review o scan result ID to get o correct scan process\ninformação." + "desc": "No scan process was found for the specified scan result.", + "first_action": "Review the scan result ID to get the correct scan process", + "full_action": "Review the scan result ID to get the correct scan process\ninformation." }, "7894": { "code": 7894, - "desc": "Falhou to cancel malware scan job.", - "first_action": "Verifique que you have o correct scan result ID e retry", - "full_action": "Verifique que you have o correct scan result ID e retry\no cancel operation com o correct scan result ID." + "desc": "Failed to cancel malware scan job.", + "first_action": "Verify that you have the correct scan result ID and retry", + "full_action": "Verify that you have the correct scan result ID and retry\nthe cancel operation with the correct scan result ID." }, "7895": { "code": 7895, - "desc": "O number de parallel scans should be in o range from 1 to 10.", + "desc": "The number of parallel scans should be in the range from 1 to 10.", "first_action": "Youmustenteravalidnumberofparallelscans.Thevalid", - "full_action": "Youmustenteravalidnumberofparallelscans.Thevalid\nrange de parallel scans está 1 to 10." + "full_action": "Youmustenteravalidnumberofparallelscans.Thevalid\nrange of parallel scans is 1 to 10." }, "7896": { "code": 7896, - "desc": "O solicitado scan host está mapped com um existing scan pool.", - "first_action": "Remove o selected scan host from todos associated scan", - "full_action": "Remove o selected scan host from todos associated scan\nhost pools e try to excluir again." + "desc": "The requested scan host is mapped with an existing scan pool.", + "first_action": "Remove the selected scan host from all associated scan", + "full_action": "Remove the selected scan host from all associated scan\nhost pools and try to delete again." }, "7897": { "code": 7897, - "desc": "O solicitado scan host está associated com um existing scan result.", - "first_action": "To clean up o scan results, adjust o cleanup period", - "full_action": "To clean up o scan results, adjust o cleanup period\ne try to excluir scan host again. Refer to o NetBackup Administrator’s Guide,\nVolume I para more informação." + "desc": "The requested scan host is associated with an existing scan result.", + "first_action": "To clean up the scan results, adjust the cleanup period", + "full_action": "To clean up the scan results, adjust the cleanup period\nand try to delete scan host again. Refer to the NetBackup Administrator’s Guide,\nVolume I for more information." }, "7898": { "code": 7898, - "desc": "Erro in o processing scan e o recover request.", - "first_action": "Review o job details in o Activity Monitor para um erro", - "full_action": "Review o job details in o Activity Monitor para um erro\ne retry o job." + "desc": "Error in the processing scan and the recover request.", + "first_action": "Review the job details in the Activity Monitor for an error", + "full_action": "Review the job details in the Activity Monitor for an error\nand retry the job." }, "7899": { "code": 7899, - "desc": "O solicitado recovery options estão inválido.", + "desc": "The requested recovery options are invalid.", "first_action": "Youmustverifytherecoveryrequestandtryagain.Review", - "full_action": "Youmustverifytherecoveryrequestandtryagain.Review\no webservice logs para more details." + "full_action": "Youmustverifytherecoveryrequestandtryagain.Review\nthe webservice logs for more details." }, "7900": { "code": 7900, - "desc": "Não foi possível to initiate recovery request.", - "first_action": "You must verifique o recovery request e retry. Review", - "full_action": "You must verifique o recovery request e retry. Review\no webservice logs para more details." + "desc": "Unable to initiate recovery request.", + "first_action": "You must verify the recovery request and retry. Review", + "full_action": "You must verify the recovery request and retry. Review\nthe webservice logs for more details." }, "7901": { "code": 7901, - "desc": "O specified malware job does não exist.", - "first_action": "You must verifique o recovery request e retry. Review", - "full_action": "You must verifique o recovery request e retry. Review\no webservice logs para more details." + "desc": "The specified malware job does not exist.", + "first_action": "You must verify the recovery request and retry. Review", + "full_action": "You must verify the recovery request and retry. Review\nthe webservice logs for more details." }, "7902": { "code": 7902, - "desc": "Falhou to cancel malware job because o job está completed.", - "first_action": "Completed malware jobs não é possível be canceled.", - "full_action": "Completed malware jobs não é possível be canceled." + "desc": "Failed to cancel malware job because the job is completed.", + "first_action": "Completed malware jobs cannot be canceled.", + "full_action": "Completed malware jobs cannot be canceled." }, "7903": { "code": 7903, - "desc": "Não foi possível to create um scan e um recovery job.", - "first_action": "Review o webservice logs e try again.", - "full_action": "Review o webservice logs e try again." + "desc": "Unable to create a scan and a recovery job.", + "first_action": "Review the webservice logs and try again.", + "full_action": "Review the webservice logs and try again." }, "7905": { "code": 7905, - "desc": "Não foi possível to create um malware job.", - "first_action": "Review o webservice logs e try again.", - "full_action": "Review o webservice logs e try again." + "desc": "Unable to create a malware job.", + "first_action": "Review the webservice logs and try again.", + "full_action": "Review the webservice logs and try again." }, "7907": { "code": 7907, - "desc": "Too many backup images para scan e recover in selected date range.", - "first_action": "Change o start ou o end date de backup images que", - "full_action": "Change o start ou o end date de backup images que\nyou selected para recovery." + "desc": "Too many backup images for scan and recover in selected date range.", + "first_action": "Change the start or the end date of backup images that", + "full_action": "Change the start or the end date of backup images that\nyou selected for recovery." }, "7910": { "code": 7910, - "desc": "Não able to complete scan job.", - "first_action": "Review o job details in o Activity Monitor para um erro", - "full_action": "Review o job details in o Activity Monitor para um erro\ne retry o job." + "desc": "Not able to complete scan job.", + "first_action": "Review the job details in the Activity Monitor for an error", + "full_action": "Review the job details in the Activity Monitor for an error\nand retry the job." }, "7911": { "code": 7911, - "desc": "Workload está não supported para malware test scan. NetBackup status codes 970 NetBackup status codes", + "desc": "Workload is not supported for malware test scan. NetBackup status codes 970 NetBackup status codes", "first_action": "SelectbackupimageofStandardpolicytypefortestscan.", "full_action": "SelectbackupimageofStandardpolicytypefortestscan." }, "7912": { "code": 7912, - "desc": "Provided backup copy está não Instant Access capable.", - "first_action": "Select um backup image ou copy which está instant access", - "full_action": "Select um backup image ou copy which está instant access\ncapable. Para example, backup image on MSDP armazenamento." + "desc": "Provided backup copy is not Instant Access capable.", + "first_action": "Select a backup image or copy which is instant access", + "full_action": "Select a backup image or copy which is instant access\ncapable. For example, backup image on MSDP storage." }, "7913": { "code": 7913, - "desc": "Não able to initiate scan on given scan host.", - "first_action": "Review o job details in o Activity Monitor para um erro", - "full_action": "Review o job details in o Activity Monitor para um erro\ne retry o job." + "desc": "Not able to initiate scan on given scan host.", + "first_action": "Review the job details in the Activity Monitor for an error", + "full_action": "Review the job details in the Activity Monitor for an error\nand retry the job." }, "7914": { "code": 7914, - "desc": "Não foi possível to excluir scan result.", + "desc": "Unable to delete scan result.", "first_action": "RefreshthewebUIanddetermineifthescanresultexists", - "full_action": "RefreshthewebUIanddetermineifthescanresultexists\nin um falhou ou um canceled state." + "full_action": "RefreshthewebUIanddetermineifthescanresultexists\nin a failed or a canceled state." }, "7915": { "code": 7915, "desc": "Too many scan results to cancel.", - "first_action": "Reduce o number de scan results to cancel to 20 ou", - "full_action": "Reduce o number de scan results to cancel to 20 ou\nfewer." + "first_action": "Reduce the number of scan results to cancel to 20 or", + "full_action": "Reduce the number of scan results to cancel to 20 or\nfewer." }, "8000": { "code": 8000, - "desc": "Usuário does não have permission(s) to executar o solicitado operation.", - "first_action": "To executar o solicitado operation, you must be um raiz", - "full_action": "To executar o solicitado operation, you must be um raiz\nusuário, administrator, ou have o appropriate privileges through Role-Based Access\nControl (RBAC). Contate o NetBackup system administrator." + "desc": "User does not have permission(s) to perform the requested operation.", + "first_action": "To perform the requested operation, you must be a root", + "full_action": "To perform the requested operation, you must be a root\nuser, administrator, or have the appropriate privileges through Role-Based Access\nControl (RBAC). Contact the NetBackup system administrator." }, "8001": { "code": 8001, - "desc": "O JSON Web Token está expired", - "first_action": "O usuário must log on again.", - "full_action": "O usuário must log on again." + "desc": "The JSON Web Token is expired", + "first_action": "The user must log on again.", + "full_action": "The user must log on again." }, "8002": { "code": 8002, - "desc": "JWT Token está inválido", - "first_action": "O usuário must log on again.", - "full_action": "O usuário must log on again." + "desc": "JWT Token is invalid", + "first_action": "The user must log on again.", + "full_action": "The user must log on again." }, "8009": { "code": 8009, - "desc": "Specified permissão não present in JSON Web Token", - "first_action": "O usuário should contate o NetBackup security", - "full_action": "O usuário should contate o NetBackup security\nadministrator to request RBAC permissions para o NetBackup web usuário interface." + "desc": "Specified permission not present in JSON Web Token", + "first_action": "The user should contact the NetBackup security", + "full_action": "The user should contact the NetBackup security\nadministrator to request RBAC permissions for the NetBackup web user interface." }, "8016": { "code": 8016, - "desc": "Não é possível excluir um role based access control resource que está configurado in um access rule.", - "first_action": "Before you can excluir um role ou um object group, you must", - "full_action": "Before you can excluir um role ou um object group, you must\nremove it from todos de o associated access rules." + "desc": "Cannot delete a role based access control resource that is configured in an access rule.", + "first_action": "Before you can delete a role or an object group, you must", + "full_action": "Before you can delete a role or an object group, you must\nremove it from all of the associated access rules." }, "8018": { "code": 8018, - "desc": "Identity não é possível be vazio. Enter um valid usuário ou group.", - "first_action": "O API expects um non-empty input value in order to", - "full_action": "O API expects um non-empty input value in order to\nidentify e validate um usuário ou group. Garanta que o identity input value está não\nvazio." + "desc": "Identity cannot be empty. Enter a valid user or group.", + "first_action": "The API expects a non-empty input value in order to", + "full_action": "The API expects a non-empty input value in order to\nidentify and validate a user or group. Ensure that the identity input value is not\nempty." }, "8019": { "code": 8019, - "desc": "Inválido identity format. When specifying um domain, use either o Usuário Principal Name (UPN) format ou o Down-Level Logon Name format.", + "desc": "Invalid identity format. When specifying a domain, use either the User Principal Name (UPN) format or the Down-Level Logon Name format.", "first_action": "Username@DOMAIN", - "full_action": "TheAPIrequiresthattheinputvaluebeinaspecificformat\nin order to identify e validate um usuário ou group. Garanta que o identity input value\nestá in one de o seguinte formats:\n■ username@DOMAIN\n■ DOMAIN\\username\n■ groupname@DOMAIN\n■ DOMAIN\\groupname\n■ username\n■ groupname" + "full_action": "TheAPIrequiresthattheinputvaluebeinaspecificformat\nin order to identify and validate a user or group. Ensure that the identity input value\nis in one of the following formats:\n■ username@DOMAIN\n■ DOMAIN\\username\n■ groupname@DOMAIN\n■ DOMAIN\\groupname\n■ username\n■ groupname" }, "8021": { "code": 8021, - "desc": "Não foi possível to validate o usuário ou group.", - "first_action": "Use o vssat addldapdomain comando to configure", - "full_action": "Use o vssat addldapdomain comando to configure\no LDAP domain. Para more informação, refer to o NetBackup Commands\nReference Guide." + "desc": "Unable to validate the user or group.", + "first_action": "Use the vssat addldapdomain command to configure", + "full_action": "Use the vssat addldapdomain command to configure\nthe LDAP domain. For more information, refer to the NetBackup Commands\nReference Guide." }, "8051": { "code": 8051, - "desc": "Cheio recovery backup não found.", - "first_action": "You must start ou schedule um cheio backup first e then um", - "full_action": "You must start ou schedule um cheio backup first e then um\nincremental backup can be run ou scheduled. After this incremental backup, o\nimage can be recovered." + "desc": "FULL recovery backup not found.", + "first_action": "You must start or schedule a full backup first and then an", + "full_action": "You must start or schedule a full backup first and then an\nincremental backup can be run or scheduled. After this incremental backup, the\nimage can be recovered." }, "8053": { "code": 8053, - "desc": "Asset type para recovery object does não match com scenario type.", - "first_action": "Set o value de assetType to INSTANCE in o payload.", - "full_action": "Set o value de assetType to INSTANCE in o payload." + "desc": "Asset type for recovery object does not match with scenario type.", + "first_action": "Set the value of assetType to INSTANCE in the payload.", + "full_action": "Set the value of assetType to INSTANCE in the payload." }, "8054": { "code": 8054, - "desc": "Unknown host servidor.", - "first_action": "Verifythatthetargethostis um valid NetBackupclienthost.", - "full_action": "Verifythatthetargethostis um valid NetBackupclienthost." + "desc": "Unknown host server.", + "first_action": "Verifythatthetargethostis a valid NetBackupclienthost.", + "full_action": "Verifythatthetargethostis a valid NetBackupclienthost." }, "8055": { "code": 8055, - "desc": "Erro while renaming arquivo.", - "first_action": "Verifique que o caminho que está provided doesn't contain qualquer", - "full_action": "Verifique que o caminho que está provided doesn't contain qualquer\nnon-ASCII characters.\nIf you need to contate Cohesity Technical Support, you must have o tar log from\no recovery host." + "desc": "Error while renaming file.", + "first_action": "Verify that the path that is provided doesn't contain any", + "full_action": "Verify that the path that is provided doesn't contain any\nnon-ASCII characters.\nIf you need to contact Cohesity Technical Support, you must have the tar log from\nthe recovery host." }, "8056": { "code": 8056, - "desc": "Banco de dados name está inválido input para instance recovery.", - "first_action": "Remove o banco de dados name from payload.", - "full_action": "Remove o banco de dados name from payload." + "desc": "Database name is invalid input for instance recovery.", + "first_action": "Remove the database name from payload.", + "full_action": "Remove the database name from payload." }, "8100": { "code": 8100, - "desc": "O vCloud organization name não é possível be blank.", - "first_action": "Verifique que o vCloud organization name está added. Retry", - "full_action": "Verifique que o vCloud organization name está added. Retry\no operation e if o issue persists, visit support.veritas.com. O Cohesity\nTechnicalSupportwebsitesiteoffersadditionalinformationtohelpyoutroubleshoot\nthis issue." + "desc": "The vCloud organization name cannot be blank.", + "first_action": "Verify that the vCloud organization name is added. Retry", + "full_action": "Verify that the vCloud organization name is added. Retry\nthe operation and if the issue persists, visit support.veritas.com. The Cohesity\nTechnicalSupportwebsitesiteoffersadditionalinformationtohelpyoutroubleshoot\nthis issue." }, "8101": { "code": 8101, - "desc": "O vCloud organization virtual datacenter name não é possível be blank.", + "desc": "The vCloud organization virtual datacenter name cannot be blank.", "first_action": "VerifythatthevCloudorganizationvirtualdatacentername", - "full_action": "VerifythatthevCloudorganizationvirtualdatacentername\nestá added. Retry o operation e if o issue persists, visit support.veritas.com.\nO Cohesity Technical Support website site offers additional informação to help\nyou troubleshoot this issue." + "full_action": "VerifythatthevCloudorganizationvirtualdatacentername\nis added. Retry the operation and if the issue persists, visit support.veritas.com.\nThe Cohesity Technical Support website site offers additional information to help\nyou troubleshoot this issue." }, "8102": { "code": 8102, - "desc": "O vCloud vApp name não é possível be blank.", - "first_action": "Verifique que o vCloud vApp name está added. Retry o", - "full_action": "Verifique que o vCloud vApp name está added. Retry o\noperationandiftheissuepersists,visitsupport.veritas.com.TheCohesityTechnical\nSupportwebsitesiteoffersadditionalinformationtohelpyoutroubleshootthisissue." + "desc": "The vCloud vApp name cannot be blank.", + "first_action": "Verify that the vCloud vApp name is added. Retry the", + "full_action": "Verify that the vCloud vApp name is added. Retry the\noperationandiftheissuepersists,visitsupport.veritas.com.TheCohesityTechnical\nSupportwebsitesiteoffersadditionalinformationtohelpyoutroubleshootthisissue." }, "8103": { "code": 8103, - "desc": "O vCloud catalog name não é possível be blank.", - "first_action": "Verifique que o vCloud catalog name está added. Retry o", - "full_action": "Verifique que o vCloud catalog name está added. Retry o\noperationandiftheissuepersists,visitsupport.veritas.com.TheCohesityTechnical\nSupportwebsitesiteoffersadditionalinformationtohelpyoutroubleshootthisissue." + "desc": "The vCloud catalog name cannot be blank.", + "first_action": "Verify that the vCloud catalog name is added. Retry the", + "full_action": "Verify that the vCloud catalog name is added. Retry the\noperationandiftheissuepersists,visitsupport.veritas.com.TheCohesityTechnical\nSupportwebsitesiteoffersadditionalinformationtohelpyoutroubleshootthisissue." }, "8104": { "code": 8104, - "desc": "O vCloud catalog vApp template name não é possível be blank.", - "first_action": "Verifique que o vCloud catalog vApp template name está", - "full_action": "Verifique que o vCloud catalog vApp template name está\nadded. Retry o operation e if o issue persists, visit support.veritas.com. O\nCohesity Technical Support website site offers additional informação to help you\ntroubleshoot this issue." + "desc": "The vCloud catalog vApp template name cannot be blank.", + "first_action": "Verify that the vCloud catalog vApp template name is", + "full_action": "Verify that the vCloud catalog vApp template name is\nadded. Retry the operation and if the issue persists, visit support.veritas.com. The\nCohesity Technical Support website site offers additional information to help you\ntroubleshoot this issue." }, "8105": { "code": 8105, - "desc": "Specify um valid value para o recovery falha strategy.", - "first_action": "Provide o valid values de recovery falha strategy type", - "full_action": "Provide o valid values de recovery falha strategy type\ncomo Fail Fast, Proceed Ahead, ou Retry." + "desc": "Specify a valid value for the recovery failure strategy.", + "first_action": "Provide the valid values of recovery failure strategy type", + "full_action": "Provide the valid values of recovery failure strategy type\nas Fail Fast, Proceed Ahead, or Retry." }, "8106": { "code": 8106, - "desc": "Specify um valid value para o retry count.", - "first_action": "Provide um valid retry count when o Retry strategy type", - "full_action": "Provide um valid retry count when o Retry strategy type\nestá selected. O valid Retry count range está 2 to 5." + "desc": "Specify a valid value for the retry count.", + "first_action": "Provide a valid retry count when the Retry strategy type", + "full_action": "Provide a valid retry count when the Retry strategy type\nis selected. The valid Retry count range is 2 to 5." }, "8107": { "code": 8107, - "desc": "O recovery falha strategy recurso está disabled on o Kubernetes workload.", - "first_action": "Enable o recurso toggle para AIR, duplication, e o", - "full_action": "Enable o recurso toggle para AIR, duplication, e o\nrestauração falha strategy." + "desc": "The recovery failure strategy feature is disabled on the Kubernetes workload.", + "first_action": "Enable the feature toggle for AIR, duplication, and the", + "full_action": "Enable the feature toggle for AIR, duplication, and the\nrestore failure strategy." }, "8200": { "code": 8200, - "desc": "KMIP internal erro.", + "desc": "KMIP internal error.", "first_action": "Reviewthenbkmiputillegacylogstohelpfindthecause", - "full_action": "Reviewthenbkmiputillegacylogstohelpfindthecause\nde o issue. If o issue persists, visit o Cohesity Technical Support website. O\nCohesity Technical Support website offers additional informação to help you\ntroubleshoot this issue." + "full_action": "Reviewthenbkmiputillegacylogstohelpfindthecause\nof the issue. If the issue persists, visit the Cohesity Technical Support website. The\nCohesity Technical Support website offers additional information to help you\ntroubleshoot this issue." }, "8201": { "code": 8201, - "desc": "Falhou to conectar to o external KMS servidor.", - "first_action": "O external KMS servidor name ou o IP address might", - "full_action": "O external KMS servidor name ou o IP address might\nbe wrong. Verifique o rede connectivity between o master servidor e o\nexternal KMS servidor." + "desc": "Failed to connect to the external KMS server.", + "first_action": "The external KMS server name or the IP address might", + "full_action": "The external KMS server name or the IP address might\nbe wrong. Check the network connectivity between the master server and the\nexternal KMS server." }, "8203": { "code": 8203, - "desc": "Falhou to initialize SSL context to conectar to o external KMS servidor.", - "first_action": "Verifique para qualquer mismatch between private key e", - "full_action": "Verifique para qualquer mismatch between private key e\ncertificate. Verifique para qualquer fora de memória erro." + "desc": "Failed to initialize SSL context to connect to the external KMS server.", + "first_action": "Check for any mismatch between private key and", + "full_action": "Check for any mismatch between private key and\ncertificate. Check for any out of memory error." }, "8204": { "code": 8204, - "desc": "Falhou to establish SSL conexão com o external KMS servidor.", - "first_action": "Review o credentials (private key, certificate, CA", - "full_action": "Review o credentials (private key, certificate, CA\ncertificate, passphrase para private key) que estão used to conectar to EKMS servidor." + "desc": "Failed to establish SSL connection with the external KMS server.", + "first_action": "Review the credentials (private key, certificate, CA", + "full_action": "Review the credentials (private key, certificate, CA\ncertificate, passphrase for private key) that are used to connect to EKMS server." }, "8205": { "code": 8205, - "desc": "FailedtoestablishSSLconnectionwiththeexternalKMSserverbecause o conexão times fora.", - "first_action": "Aumentar o conexão time-out value.", - "full_action": "Aumentar o conexão time-out value." + "desc": "FailedtoestablishSSLconnectionwiththeexternalKMSserverbecause the connection times out.", + "first_action": "Increase the connection time-out value.", + "full_action": "Increase the connection time-out value." }, "8207": { "code": 8207, - "desc": "O KMIP request to external KMS servidor falhou.", - "first_action": "Verifique o conexão com o servidor.", - "full_action": "Try one de o seguinte como appropriate:\n■ Verifique o conexão com o servidor.\n■ Verifique o operation por executando o nbkmiputil comando." + "desc": "The KMIP request to external KMS server failed.", + "first_action": "Check the connection with the server.", + "full_action": "Try one of the following as appropriate:\n■ Check the connection with the server.\n■ Check the operation by running the nbkmiputil command." }, "8208": { "code": 8208, - "desc": "O KMIP request to external KMS servidor has esgotado fora.", - "first_action": "Aumentar o request time-out value. Verifique o servidor", - "full_action": "Aumentar o request time-out value. Verifique o servidor\nresponse usando EKMS CLI ou qualquer other rede tool." + "desc": "The KMIP request to external KMS server has timed out.", + "first_action": "Increase the request time-out value. Check the server", + "full_action": "Increase the request time-out value. Check the server\nresponse using EKMS CLI or any other network tool." }, "8209": { "code": 8209, - "desc": "O KMIP item não é possível be found.", - "first_action": "Verifique whether o KMIP item está present on o EKMS", - "full_action": "Verifique whether o KMIP item está present on o EKMS\nservidor usando EKMS CLI ou qualquer other rede tool." + "desc": "The KMIP item cannot be found.", + "first_action": "Check whether the KMIP item is present on the EKMS", + "full_action": "Check whether the KMIP item is present on the EKMS\nserver using EKMS CLI or any other network tool." }, "8211": { "code": 8211, - "desc": "SSL verification falhou due to host name mismatch.", - "first_action": "Verifique que o connecting host name exists in o KMS", - "full_action": "Verifique que o connecting host name exists in o KMS\nservidor certificate SAN ou CN field. If o host name does não exist, fix o servidor\ncertificate ou bypass o peer host validation por setting o EKMS_VERIFY_HOST=0\nflag in o bp.conf arquivo." + "desc": "SSL verification failed due to host name mismatch.", + "first_action": "Check that the connecting host name exists in the KMS", + "full_action": "Check that the connecting host name exists in the KMS\nserver certificate SAN or CN field. If the host name does not exist, fix the server\ncertificate or bypass the peer host validation by setting the EKMS_VERIFY_HOST=0\nflag in the bp.conf file." }, "8212": { "code": 8212, - "desc": "SSL verification falhou due to IP address mismatch.", - "first_action": "Verifique que o connecting host name IP address exists", - "full_action": "Verifique que o connecting host name IP address exists\nin o KMS servidor certificate SAN ou CN field. If o host name IP address does não\nexist, fix o servidor certificate ou bypass o peer host validation por setting o\nEKMS_VERIFY_HOST=0 flag in o bp.conf arquivo." + "desc": "SSL verification failed due to IP address mismatch.", + "first_action": "Check that the connecting host name IP address exists", + "full_action": "Check that the connecting host name IP address exists\nin the KMS server certificate SAN or CN field. If the host name IP address does not\nexist, fix the server certificate or bypass the peer host validation by setting the\nEKMS_VERIFY_HOST=0 flag in the bp.conf file." }, "8216": { "code": 8216, - "desc": "O KMIP version está não supported.", - "first_action": "O KMIP servidor e o cliente estão mismatched in o", - "full_action": "O KMIP servidor e o cliente estão mismatched in o\nKMIP protocol version. Refer to o Cohesity Software Compatibility List ou o\nNetBackup Security e Encryption Guide para supported KMIP versions." + "desc": "The KMIP version is not supported.", + "first_action": "The KMIP server and the client are mismatched in the", + "full_action": "The KMIP server and the client are mismatched in the\nKMIP protocol version. Refer to the Cohesity Software Compatibility List or the\nNetBackup Security and Encryption Guide for supported KMIP versions." }, "8217": { "code": 8217, - "desc": "Erro foi encontrado at external KMS servidor while o operation foi performed.", - "first_action": "Executar o same operation through EKMS CLI ou qualquer", - "full_action": "Executar o same operation through EKMS CLI ou qualquer\nother rede tool." + "desc": "Error was encountered at external KMS server while the operation was performed.", + "first_action": "Perform the same operation through EKMS CLI or any", + "full_action": "Perform the same operation through EKMS CLI or any\nother network tool." }, "8220": { "code": 8220, - "desc": "O permissão está negada.", - "first_action": "Review usuário permissions at o EKMS servidor whose", - "full_action": "Review usuário permissions at o EKMS servidor whose\ncertificate está used to conectar to EKMS servidor." + "desc": "The permission is denied.", + "first_action": "Review user permissions at the EKMS server whose", + "full_action": "Review user permissions at the EKMS server whose\ncertificate is used to connect to EKMS server." }, "8221": { "code": 8221, - "desc": "O KMIP object está archived.", - "first_action": "O KMIP object must be recovered from o archive", - "full_action": "O KMIP object must be recovered from o archive\nbefore o operation está performed usando o EKMS servidor tool." + "desc": "The KMIP object is archived.", + "first_action": "The KMIP object must be recovered from the archive", + "full_action": "The KMIP object must be recovered from the archive\nbefore the operation is performed using the EKMS server tool." }, "8224": { "code": 8224, - "desc": "NetBackup does não support qualquer de o KMIP versions que o external KMS servidor supports.", - "first_action": "Verifique if o external KMS servidor supports qualquer de o", - "full_action": "Verifique if o external KMS servidor supports qualquer de o\nNetBackup supported KMIP versions e change o external KMS servidor setting\nto use it." + "desc": "NetBackup does not support any of the KMIP versions that the external KMS server supports.", + "first_action": "Check if the external KMS server supports any of the", + "full_action": "Check if the external KMS server supports any of the\nNetBackup supported KMIP versions and change the external KMS server setting\nto use it." }, "8226": { "code": 8226, - "desc": "O KMIP operation está não attempted.", - "first_action": "Debug ou troubleshoot o pre-requisite operation e", - "full_action": "Debug ou troubleshoot o pre-requisite operation e\nthen try again." + "desc": "The KMIP operation is not attempted.", + "first_action": "Debug or troubleshoot the pre-requisite operation and", + "full_action": "Debug or troubleshoot the pre-requisite operation and\nthen try again." }, "8227": { "code": 8227, - "desc": "Não NetBackup keys estão found.", - "first_action": "Verifique o EKMS servidor whether qualquer key está defined com", - "full_action": "Verifique o EKMS servidor whether qualquer key está defined com\ncustomattributex-application=NetBackuptoqualifyasNetBackup(casesensitive)\nkey. Review usuário permissions e verifique que o usuário has o permissão to locate\nkeys como per their privileges." + "desc": "No NetBackup keys are found.", + "first_action": "Check the EKMS server whether any key is defined with", + "full_action": "Check the EKMS server whether any key is defined with\ncustomattributex-application=NetBackuptoqualifyasNetBackup(casesensitive)\nkey. Review user permissions and verify that the user has the permission to locate\nkeys as per their privileges." }, "8228": { "code": 8228, - "desc": "Falhou to executar CRL verifique.", - "first_action": "Verifique que o CRL e o EKMS servidor certificates estão from o same CA.", - "full_action": "Verifique para seguinte things como appropriate:\n■ Verifique que o CRL e o EKMS servidor certificates estão from o same CA.\n■ Verifique que o ECA_CRL_PATH está set in o NetBackup configuration. If o caminho\nexists, confirm que está has EKMS servidor certificate CRLs.\n■ If ECA_CRL_PATH está não set, verifique que o EKMS servidor certificate has CDP\ndefined.\n■ If o CDP está defined, verifique que o CDP servidor está reachable.\n■ If CDP servidor está reachable, then verifique que o downloader vnetd service está up\ne executando.\n■ IfCRLchecklevelisnotdefinedatthetimeofKMSconfigurationthenthedefault\nCRL verifique level está LEAF." + "desc": "Failed to perform CRL check.", + "first_action": "Verify that the CRL and the EKMS server certificates are from the same CA.", + "full_action": "Check for following things as appropriate:\n■ Verify that the CRL and the EKMS server certificates are from the same CA.\n■ Verify that the ECA_CRL_PATH is set in the NetBackup configuration. If the path\nexists, confirm that is has EKMS server certificate CRLs.\n■ If ECA_CRL_PATH is not set, verify that the EKMS server certificate has CDP\ndefined.\n■ If the CDP is defined, verify that the CDP server is reachable.\n■ If CDP server is reachable, then verify that the downloader vnetd service is up\nand running.\n■ IfCRLchecklevelisnotdefinedatthetimeofKMSconfigurationthenthedefault\nCRL check level is LEAF." }, "8229": { "code": 8229, - "desc": "O external KMS servidor certificate está revoked.", - "first_action": "Use o unrevoked certificate para o EKMS servidor ou o", - "full_action": "Use o unrevoked certificate para o EKMS servidor ou o\nCRL verifique can be disabled." + "desc": "The external KMS server certificate is revoked.", + "first_action": "Use the unrevoked certificate for the EKMS server or the", + "full_action": "Use the unrevoked certificate for the EKMS server or the\nCRL check can be disabled." }, "8234": { "code": 8234, - "desc": "Falhou to set certificate in o SSL context.", - "first_action": "Use um PEM encoded certificate.", - "full_action": "Use um PEM encoded certificate." + "desc": "Failed to set certificate in the SSL context.", + "first_action": "Use a PEM encoded certificate.", + "full_action": "Use a PEM encoded certificate." }, "8235": { "code": 8235, - "desc": "Falhou to set CA certificates in o SSL context.", + "desc": "Failed to set CA certificates in the SSL context.", "first_action": "Use PEM encoded CA certificates.", "full_action": "Use PEM encoded CA certificates." }, "8236": { "code": 8236, - "desc": "Falhou to set private key in o SSL context.", - "first_action": "Use um PEM encoded private key. Verifique o key matches", - "full_action": "Use um PEM encoded private key. Verifique o key matches\ncom o provided certificate por usando o openssl utility." + "desc": "Failed to set private key in the SSL context.", + "first_action": "Use a PEM encoded private key. Verify the key matches", + "full_action": "Use a PEM encoded private key. Verify the key matches\nwith the provided certificate by using the openssl utility." }, "8237": { "code": 8237, - "desc": "ThekeysthatwereretrievedfromtheexternalKMSserverarenotusable para encryption.", - "first_action": "Set o Cryptographic Uso mask de o key para encryption.", - "full_action": "Executar o seguinte como appropriate:\n■ Set o Cryptographic Uso mask de o key para encryption.\n■ Correct o Process Start date.\n■ Correct o Protect Stop date.\n■ Verifique if o time e ou date does não match between o NetBackup master\nservidor e o external KMS servidor. If they do não match, correct o time e\nou date." + "desc": "ThekeysthatwereretrievedfromtheexternalKMSserverarenotusable for encryption.", + "first_action": "Set the Cryptographic Usage mask of the key for encryption.", + "full_action": "Perform the following as appropriate:\n■ Set the Cryptographic Usage mask of the key for encryption.\n■ Correct the Process Start date.\n■ Correct the Protect Stop date.\n■ Check if the time and or date does not match between the NetBackup master\nserver and the external KMS server. If they do not match, correct the time and\nor date." }, "8238": { "code": 8238, - "desc": "ThekeysthatwereretrievedfromtheexternalKMSserverarenotusable para decryption.", - "first_action": "Set o Cryptographic Uso mask de o key para decryption.", - "full_action": "Executar o seguinte como appropriate:\n■ Set o Cryptographic Uso mask de o key para decryption.\n■ Correct o Process Start date.\n■ Verifique if o time e ou date does não match between o NetBackup master\nservidor e o external KMS servidor. If they do não match, correct o time e\nou date.\n■ SettheflagEKMS_DISABLE_KEY_USAGE_CHECK=1inbp.conftobypasskeyusage\nverifique." + "desc": "ThekeysthatwereretrievedfromtheexternalKMSserverarenotusable for decryption.", + "first_action": "Set the Cryptographic Usage mask of the key for decryption.", + "full_action": "Perform the following as appropriate:\n■ Set the Cryptographic Usage mask of the key for decryption.\n■ Correct the Process Start date.\n■ Check if the time and or date does not match between the NetBackup master\nserver and the external KMS server. If they do not match, correct the time and\nor date.\n■ SettheflagEKMS_DISABLE_KEY_USAGE_CHECK=1inbp.conftobypasskeyusage\ncheck." }, "8240": { "code": 8240, - "desc": "O KMIP object already exists.", - "first_action": "O KMIP object must be provided com um unique name", - "full_action": "O KMIP object must be provided com um unique name\nwhen o object está created." + "desc": "The KMIP object already exists.", + "first_action": "The KMIP object must be provided with a unique name", + "full_action": "The KMIP object must be provided with a unique name\nwhen the object is created." }, "8250": { "code": 8250, - "desc": "Não é possível create o NetBackup job.", - "first_action": "Retry o operation e if o issue persists, visit", - "full_action": "Retry o operation e if o issue persists, visit\nsupport.veritas.com. O Cohesity Technical Support website site offers additional\ninformação to help you troubleshoot this issue." + "desc": "Cannot create the NetBackup job.", + "first_action": "Retry the operation and if the issue persists, visit", + "full_action": "Retry the operation and if the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support website site offers additional\ninformation to help you troubleshoot this issue." }, "8251": { "code": 8251, - "desc": "Falhou to update NetBackup job.", - "first_action": "Retry o operation e if o issue persists, visit", - "full_action": "Retry o operation e if o issue persists, visit\nsupport.veritas.com. O Cohesity Technical Support website site offers additional\ninformação to help you troubleshoot this issue." + "desc": "Failed to update NetBackup job.", + "first_action": "Retry the operation and if the issue persists, visit", + "full_action": "Retry the operation and if the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support website site offers additional\ninformation to help you troubleshoot this issue." }, "8252": { "code": 8252, "desc": "Unsupported policy type.", - "first_action": "Retry o operation e if o issue persists, visit", - "full_action": "Retry o operation e if o issue persists, visit\nsupport.veritas.com. O Cohesity Technical Support website site offers additional\ninformação to help you troubleshoot this issue." + "first_action": "Retry the operation and if the issue persists, visit", + "full_action": "Retry the operation and if the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support website site offers additional\ninformation to help you troubleshoot this issue." }, "8253": { "code": 8253, - "desc": "Não é possível restauração o solicitado resource.", - "first_action": "Retry o operation e if o issue persists, visit", - "full_action": "Retry o operation e if o issue persists, visit\nsupport.veritas.com. O Cohesity Technical Support website site offers additional\ninformação to help you troubleshoot this issue." + "desc": "Cannot restore the requested resource.", + "first_action": "Retry the operation and if the issue persists, visit", + "full_action": "Retry the operation and if the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support website site offers additional\ninformation to help you troubleshoot this issue." }, "8300": { "code": 8300, - "desc": "Theglobaldata-in-transitencryptionisenforcedintheNetBackupdomain, but it não é possível be enabled como o cliente ou o backup host version está older than 9.1.", - "first_action": "Upgrade o NetBackup cliente ou o backup host to um version que supports", - "full_action": "Executar o seguinte como appropriate:\n■ Upgrade o NetBackup cliente ou o backup host to um version que supports\ndata-in-transit encryption.\n■ Contate seu security administrator e change o data-in-transit encryption\nglobal setting to PREFERRED_ON ou PREFERRED_OFF.\nNote que o data-in-transit encryption está disabled during communication com\nhosts executando um version older than 9.1.\nPara more informação, refer to theConfiguring data-in-transit encryption section in\no NetBackup Security e Encryption Guide." + "desc": "Theglobaldata-in-transitencryptionisenforcedintheNetBackupdomain, but it cannot be enabled as the client or the backup host version is older than 9.1.", + "first_action": "Upgrade the NetBackup client or the backup host to a version that supports", + "full_action": "Perform the following as appropriate:\n■ Upgrade the NetBackup client or the backup host to a version that supports\ndata-in-transit encryption.\n■ Contact your security administrator and change the data-in-transit encryption\nglobal setting to PREFERRED_ON or PREFERRED_OFF.\nNote that the data-in-transit encryption is disabled during communication with\nhosts running a version older than 9.1.\nFor more information, refer to theConfiguring data-in-transit encryption section in\nthe NetBackup Security and Encryption Guide." }, "8301": { "code": 8301, - "desc": "Theglobaldata-in-transitencryptionisenforcedintheNetBackupdomain, but it não é possível be enabled como o mídia servidor version está older than 9.1.", - "first_action": "Upgrade o NetBackup mídia servidor to um version que supports data-in-transit", - "full_action": "Executar one de o seguinte como appropriate:\n■ Upgrade o NetBackup mídia servidor to um version que supports data-in-transit\nencryption.\n■ Changetheconfigurationtoselectthemediaserverwhichsupportsdata-in-transit\nencryption para performing o NetBackup operations.\n■ Contate seu security administrator e change o data-in-transit encryption\nglobal setting to PREFERRED_ON ou PREFERRED_OFF.\nNotethatdata-in-transitencryptionisdisabledduringcommunicationwithhosts\nhaving um version older than 9.1.\nPara more informação, refer to o Configuring data-in-transit encryption section in\no NetBackup Security e Encryption Guide." + "desc": "Theglobaldata-in-transitencryptionisenforcedintheNetBackupdomain, but it cannot be enabled as the media server version is older than 9.1.", + "first_action": "Upgrade the NetBackup media server to a version that supports data-in-transit", + "full_action": "Perform one of the following as appropriate:\n■ Upgrade the NetBackup media server to a version that supports data-in-transit\nencryption.\n■ Changetheconfigurationtoselectthemediaserverwhichsupportsdata-in-transit\nencryption for performing the NetBackup operations.\n■ Contact your security administrator and change the data-in-transit encryption\nglobal setting to PREFERRED_ON or PREFERRED_OFF.\nNotethatdata-in-transitencryptionisdisabledduringcommunicationwithhosts\nhaving a version older than 9.1.\nFor more information, refer to the Configuring data-in-transit encryption section in\nthe NetBackup Security and Encryption Guide." }, "8302": { "code": 8302, - "desc": "O data-in-transit encryption attribute de o backup image não é possível be updated.", - "first_action": "1. Garanta que o bpdbm service está executando on o primary servidor e there está", - "full_action": "Executar o seguinte:\n1. Garanta que o bpdbm service está executando on o primary servidor e there está\nconnectivity between o mídia servidor e o primary servidor.\n2. Retry o operation e if o issue persists, visit support.veritas.com. O\nCohesity Technical Support website offers additional informação to help you\ntroubleshootthisissue.IfyoudocontactCohesityTechnicalSupport,youneed\nto have o mídia servidor bpbrm logs disponível to help troubleshoot o issue." + "desc": "The data-in-transit encryption attribute of the backup image cannot be updated.", + "first_action": "1. Ensure that the bpdbm service is running on the primary server and there is", + "full_action": "Perform the following:\n1. Ensure that the bpdbm service is running on the primary server and there is\nconnectivity between the media server and the primary server.\n2. Retry the operation and if the issue persists, visit support.veritas.com. The\nCohesity Technical Support website offers additional information to help you\ntroubleshootthisissue.IfyoudocontactCohesityTechnicalSupport,youneed\nto have the media server bpbrm logs available to help troubleshoot the issue." }, "8303": { "code": 8303, - "desc": "O data-in-transit encryption attribute de o job não é possível be updated.", - "first_action": "1. Garanta que o bpjobd service está executando on o primary servidor e there está", - "full_action": "Executar o seguinte:\n1. Garanta que o bpjobd service está executando on o primary servidor e there está\nconnectivity between o mídia servidor e o primary servidor.\n2. Retry o operation e if o issue persists, visit support.veritas.com. O\nCohesity Technical Support website offers additional informação to help you\ntroubleshootthisissue.IfyoudocontactCohesityTechnicalSupport,youneed\nto have o mídia servidor e o primary servidor logs disponível to help\ntroubleshoot o issue." + "desc": "The data-in-transit encryption attribute of the job cannot be updated.", + "first_action": "1. Ensure that the bpjobd service is running on the primary server and there is", + "full_action": "Perform the following:\n1. Ensure that the bpjobd service is running on the primary server and there is\nconnectivity between the media server and the primary server.\n2. Retry the operation and if the issue persists, visit support.veritas.com. The\nCohesity Technical Support website offers additional information to help you\ntroubleshootthisissue.IfyoudocontactCohesityTechnicalSupport,youneed\nto have the media server and the primary server logs available to help\ntroubleshoot the issue." }, "8304": { "code": 8304, - "desc": "O global data-in-transit encryption setting não é possível be fetched.", - "first_action": "1. Garanta que o bpcd service está executando on o primary servidor.", - "full_action": "Executar o seguinte:\n1. Garanta que o bpcd service está executando on o primary servidor.\n2. Retry o operation e if o issue persists, visit support.veritas.com. O\nCohesity Technical Support website offers additional informação to help you\ntroubleshootthisissue.IfyoudocontactCohesityTechnicalSupport,youneed\nto have o seguinte primary servidor logs disponível to help troubleshoot o\nissue:\n■ nbwebservice\n■ nbjm\n■ bprd\n■ bpcd" + "desc": "The global data-in-transit encryption setting cannot be fetched.", + "first_action": "1. Ensure that the bpcd service is running on the primary server.", + "full_action": "Perform the following:\n1. Ensure that the bpcd service is running on the primary server.\n2. Retry the operation and if the issue persists, visit support.veritas.com. The\nCohesity Technical Support website offers additional information to help you\ntroubleshootthisissue.IfyoudocontactCohesityTechnicalSupport,youneed\nto have the following primary server logs available to help troubleshoot the\nissue:\n■ nbwebservice\n■ nbjm\n■ bprd\n■ bpcd" }, "8305": { "code": 8305, - "desc": "O data-in-transit encryption setting de o cliente não é possível be fetched. NetBackup status codes 989 NetBackup status codes", - "first_action": "1. Garanta bpcd service está executando on o cliente.", - "full_action": "Executar o seguinte:\n1. Garanta bpcd service está executando on o cliente.\n2. Retry o operation e if o issue persists, visit support.veritas.com. O\nCohesity Technical Support website offers additional informação to help you\ntroubleshootthisissue.IfyoudocontactCohesityTechnicalSupport,youneed\nto have o mídia servidor bpbrm e o cliente bpcd logs disponível to help\ntroubleshoot o issue." + "desc": "The data-in-transit encryption setting of the client cannot be fetched. NetBackup status codes 989 NetBackup status codes", + "first_action": "1. Ensure bpcd service is running on the client.", + "full_action": "Perform the following:\n1. Ensure bpcd service is running on the client.\n2. Retry the operation and if the issue persists, visit support.veritas.com. The\nCohesity Technical Support website offers additional information to help you\ntroubleshootthisissue.IfyoudocontactCohesityTechnicalSupport,youneed\nto have the media server bpbrm and the client bpcd logs available to help\ntroubleshoot the issue." }, "8306": { "code": 8306, - "desc": "O data-in-transit encryption (DTE) mode de o backup image está set to On, therefore NetBackup tries to encrypt o data but o mídia servidor version está older than 9.1.", + "desc": "The data-in-transit encryption (DTE) mode of the backup image is set to On, therefore NetBackup tries to encrypt the data but the media server version is older than 9.1.", "first_action": "1. UpgradetheNetBackupmediaservertoaversionthatsupportsdata-in-transit", - "full_action": "Executar one de o seguinte como appropriate:\n1. UpgradetheNetBackupmediaservertoaversionthatsupportsdata-in-transit\nencryption.\n2. Change o configuration to select o mídia servidor which supports\ndata-in-transit encryption para performing NetBackup operations.\n3. Change o data-in-transit encryption (DTE) mode de o given backup image\nto Off usando o seguinte comando:\nbpimage -update -image_dtemode Off -id \n4. Set DTE_IGNORE_IMAGE_MODE = WHERE_UNSUPPORTED in o NetBackup\nconfiguration arquivo de o primary servidor ou o mídia servidor.\nPara option 3 e option 4, DTE está disabled while o job está performed.\nPara more informação, refer to o Configuring data-in-transit encryption section in\no NetBackup Security e Encryption Guide." + "full_action": "Perform one of the following as appropriate:\n1. UpgradetheNetBackupmediaservertoaversionthatsupportsdata-in-transit\nencryption.\n2. Change the configuration to select the media server which supports\ndata-in-transit encryption for performing NetBackup operations.\n3. Change the data-in-transit encryption (DTE) mode of the given backup image\nto Off using the following command:\nbpimage -update -image_dtemode Off -id \n4. Set DTE_IGNORE_IMAGE_MODE = WHERE_UNSUPPORTED in the NetBackup\nconfiguration file of the primary server or the media server.\nFor option 3 and option 4, DTE is disabled while the job is performed.\nFor more information, refer to the Configuring data-in-transit encryption section in\nthe NetBackup Security and Encryption Guide." }, "8307": { "code": 8307, - "desc": "Theglobaldata-in-transitencryption(DTE)isenforcedintheNetBackup domain, but o DTE setting está disabled on o cliente ou o backup host.", - "first_action": "If data-in-transit está to be enforced para um cliente ou um backup host, then enable", - "full_action": "Executar one de o seguinte como appropriate:\n■ If data-in-transit está to be enforced para um cliente ou um backup host, then enable\ndata-in-transit encryption para que cliente ou um backup host. Enable encryption por\nsetting o DTE_CLIENT_MODE option in o bp.conf configuration arquivo to On.\n■ If data-in-transit encryption está to be off para um particular cliente ou um backup host,\nexecutar o seguinte:\n■ Set o data-in-transit encryption de o domain to PREFERRED_ON.\nPara option 2, DTE está disabled while o job está performed.\nPara more informação, refer to o Configuring data-in-transit encryption section in\no NetBackup Security e Encryption Guide." + "desc": "Theglobaldata-in-transitencryption(DTE)isenforcedintheNetBackup domain, but the DTE setting is disabled on the client or the backup host.", + "first_action": "If data-in-transit is to be enforced for a client or a backup host, then enable", + "full_action": "Perform one of the following as appropriate:\n■ If data-in-transit is to be enforced for a client or a backup host, then enable\ndata-in-transit encryption for that client or a backup host. Enable encryption by\nsetting the DTE_CLIENT_MODE option in the bp.conf configuration file to On.\n■ If data-in-transit encryption is to be off for a particular client or a backup host,\nperform the following:\n■ Set the data-in-transit encryption of the domain to PREFERRED_ON.\nFor option 2, DTE is disabled while the job is performed.\nFor more information, refer to the Configuring data-in-transit encryption section in\nthe NetBackup Security and Encryption Guide." }, "8308": { "code": 8308, - "desc": "O data-in-transit encryption (DTE) mode de o backup image está set to On, therefore NetBackup tries to encrypt o data but o cliente version está older than 9.1.", - "first_action": "1. Upgrade o NetBackup cliente to um version que supports data-in-transit", - "full_action": "Executar one de o seguinte como appropriate:\n1. Upgrade o NetBackup cliente to um version que supports data-in-transit\nencryption.\n2. Change o data-in-transit encryption (DTE) mode de o given backup image\nto Off usando o seguinte comando:\nbpimage -update -image_dtemode Off -id \n3. Set DTE_IGNORE_IMAGE_MODE = WHERE_UNSUPPORTED in o NetBackup\nconfiguration arquivo de o primary servidor.\nPara option 2 e option 3, DTE está disabled while o job está performed.\nPara more informação, refer to o Configuring data-in-transit encryption section in\no NetBackup Security e Encryption Guide." + "desc": "The data-in-transit encryption (DTE) mode of the backup image is set to On, therefore NetBackup tries to encrypt the data but the client version is older than 9.1.", + "first_action": "1. Upgrade the NetBackup client to a version that supports data-in-transit", + "full_action": "Perform one of the following as appropriate:\n1. Upgrade the NetBackup client to a version that supports data-in-transit\nencryption.\n2. Change the data-in-transit encryption (DTE) mode of the given backup image\nto Off using the following command:\nbpimage -update -image_dtemode Off -id \n3. Set DTE_IGNORE_IMAGE_MODE = WHERE_UNSUPPORTED in the NetBackup\nconfiguration file of the primary server.\nFor option 2 and option 3, DTE is disabled while the job is performed.\nFor more information, refer to the Configuring data-in-transit encryption section in\nthe NetBackup Security and Encryption Guide." }, "8310": { "code": 8310, - "desc": "O data-in-transit encryption (DTE) setting está enabled on o cliente, but está disabled on o mídia servidor.", + "desc": "The data-in-transit encryption (DTE) setting is enabled on the client, but is disabled on the media server.", "first_action": "1. ChangetheNetBackupconfigurationtoselectthemediaserverwhichsupports", - "full_action": "Executar one de o seguinte como appropriate:\n1. ChangetheNetBackupconfigurationtoselectthemediaserverwhichsupports\ndata-in-transit encryption para performing o NetBackup operation.\n2. O mídia servidor que handles o given operation needs to have o\ndata-in-transitencryptionsettingenabled.ChangethemediaserverDTEsetting\nde o given mídia servidor to on usando o seguinte comando:\nnbseccmd -setsecurityconfig -dtemediamode on -mediaserver \n3. If o mídia servidor que handles o NetBackup operation needs to have\ndata-in-transitencryptiondisabled,ensurethatthefollowingconfigurationsare\nset:\n■ O global DTE mode should be either PREFERRED_OFF ou PREFERRED_ON.\n■ O DTE cliente mode setting needs to be either OFF ou AUTOMATIC.\nPara option 3, DTE está disabled while o job está performed.\nPara more informação, refer to o Configuring data-in-transit encryption section in\no NetBackup Security e Encryption Guide." + "full_action": "Perform one of the following as appropriate:\n1. ChangetheNetBackupconfigurationtoselectthemediaserverwhichsupports\ndata-in-transit encryption for performing the NetBackup operation.\n2. The media server that handles the given operation needs to have the\ndata-in-transitencryptionsettingenabled.ChangethemediaserverDTEsetting\nof the given media server to on using the following command:\nnbseccmd -setsecurityconfig -dtemediamode on -mediaserver \n3. If the media server that handles the NetBackup operation needs to have\ndata-in-transitencryptiondisabled,ensurethatthefollowingconfigurationsare\nset:\n■ The global DTE mode should be either PREFERRED_OFF or PREFERRED_ON.\n■ The DTE client mode setting needs to be either OFF or AUTOMATIC.\nFor option 3, DTE is disabled while the job is performed.\nFor more information, refer to the Configuring data-in-transit encryption section in\nthe NetBackup Security and Encryption Guide." }, "8311": { "code": 8311, - "desc": "Theglobaldata-in-transitencryption(DTE)isenforcedintheNetBackup domain, but o DTE setting está disabled on o mídia servidor.", + "desc": "Theglobaldata-in-transitencryption(DTE)isenforcedintheNetBackup domain, but the DTE setting is disabled on the media server.", "first_action": "1. ChangetheNetBackupconfigurationtoselectthemediaserverwhichsupports", - "full_action": "Executar one de o seguinte como appropriate:\n1. ChangetheNetBackupconfigurationtoselectthemediaserverwhichsupports\ndata-in-transit encryption para performing o NetBackup operation.\n2. O mídia servidor que handles o secondary operation needs to have o\ndata-in-transitencryptionsettingenabled.ChangethemediaserverDTEsetting\nde o given mídia servidor to on usando o seguinte comando:\nnbseccmd -setsecurityconfig -dtemediamode on -mediaserver \n3. If o mídia servidor que handles o NetBackup operation needs to have\ndata-in-transitencryptiondisabled,ensurethatthefollowingconfigurationsare\nset:\n■ O global DTE mode should be either PREFERRED_OFF ou PREFERRED_ON.\n■ O DTE cliente mode setting needs to be either OFF ou AUTOMATIC.\nPara option 3, DTE está disabled while o job está performed.\nPara more informação, refer to o Configuring data-in-transit encryption section in\no NetBackup Security e Encryption Guide." + "full_action": "Perform one of the following as appropriate:\n1. ChangetheNetBackupconfigurationtoselectthemediaserverwhichsupports\ndata-in-transit encryption for performing the NetBackup operation.\n2. The media server that handles the secondary operation needs to have the\ndata-in-transitencryptionsettingenabled.ChangethemediaserverDTEsetting\nof the given media server to on using the following command:\nnbseccmd -setsecurityconfig -dtemediamode on -mediaserver \n3. If the media server that handles the NetBackup operation needs to have\ndata-in-transitencryptiondisabled,ensurethatthefollowingconfigurationsare\nset:\n■ The global DTE mode should be either PREFERRED_OFF or PREFERRED_ON.\n■ The DTE client mode setting needs to be either OFF or AUTOMATIC.\nFor option 3, DTE is disabled while the job is performed.\nFor more information, refer to the Configuring data-in-transit encryption section in\nthe NetBackup Security and Encryption Guide." }, "8312": { "code": 8312, - "desc": "O data-in-transit encryption (DTE) mode de o backup image está set to On, but o DTE setting está disabled on o mídia servidor. NetBackup status codes 993 NetBackup status codes", + "desc": "The data-in-transit encryption (DTE) mode of the backup image is set to On, but the DTE setting is disabled on the media server. NetBackup status codes 993 NetBackup status codes", "first_action": "1. ChangetheNetBackupconfigurationtoselectthemediaserverwhichsupports", - "full_action": "Executar one de o seguinte como appropriate:\n1. ChangetheNetBackupconfigurationtoselectthemediaserverwhichsupports\ndata-in-transit encryption para performing o NetBackup operations.\n2. O mídia servidor que handles o secondary operation needs to have o\ndata-in-transitencryptionsettingenabled.ChangethemediaserverDTEsetting\nde o given mídia servidor to on usando o seguinte comando:\nnbseccmd -setsecurityconfig -dtemediamode on\n-mediaserver \n3. If o mídia servidor que handles o backup needs to have data-in-transit\nencryption disabled, change o data-in-transit encryption (DTE) mode de o\nbackup image to Off usando o seguinte comando:\nbpimage -update -image_dtemode Off -id \nNote: This option está não applicable para import phase 1.\n4. Set DTE_IGNORE_IMAGE_MODE = ALWAYS in o NetBackup configuration arquivo de\no primary servidor ou mídia servidor (para import phase 1).\nPara option 3 e option 4, DTE está disabled while o job está performed.\nPara more informação, refer to o Configuring data-in-transit encryption section in\no NetBackup Security e Encryption Guide." + "full_action": "Perform one of the following as appropriate:\n1. ChangetheNetBackupconfigurationtoselectthemediaserverwhichsupports\ndata-in-transit encryption for performing the NetBackup operations.\n2. The media server that handles the secondary operation needs to have the\ndata-in-transitencryptionsettingenabled.ChangethemediaserverDTEsetting\nof the given media server to on using the following command:\nnbseccmd -setsecurityconfig -dtemediamode on\n-mediaserver \n3. If the media server that handles the backup needs to have data-in-transit\nencryption disabled, change the data-in-transit encryption (DTE) mode of the\nbackup image to Off using the following command:\nbpimage -update -image_dtemode Off -id \nNote: This option is not applicable for import phase 1.\n4. Set DTE_IGNORE_IMAGE_MODE = ALWAYS in the NetBackup configuration file of\nthe primary server or media server (for import phase 1).\nFor option 3 and option 4, DTE is disabled while the job is performed.\nFor more information, refer to the Configuring data-in-transit encryption section in\nthe NetBackup Security and Encryption Guide." }, "8313": { "code": 8313, - "desc": "O data-in-transit encryption (DTE) mode de o backup image está set to On, but o DTE setting está disabled on o cliente.", - "first_action": "1. If data-in-transit está to be enforced para o cliente, then enable data-in-transit", - "full_action": "Executar one de o seguinte como appropriate:\n1. If data-in-transit está to be enforced para o cliente, then enable data-in-transit\nencryptionforthatclientbysettingtheDTE_CLIENT_MODEoptioninthebp.conf\nconfiguration arquivo to On.\n2. If data-in-transit está to be off para o particular cliente then change o\ndata-in-transit encryption (DTE) mode de o backup image to Off usando o\nseguinte comando:\nbpimage -update -image_dtemode Off -id \n3. Set DTE_IGNORE_IMAGE_MODE = ALWAYS in o NetBackup configuration arquivo de\no primary servidor.\nPara option 2 e option 3, DTE está disabled while o job está performed.\nPara more informação, refer to o Configuring data-in-transit encryption section in\no NetBackup Security e Encryption Guide." + "desc": "The data-in-transit encryption (DTE) mode of the backup image is set to On, but the DTE setting is disabled on the client.", + "first_action": "1. If data-in-transit is to be enforced for the client, then enable data-in-transit", + "full_action": "Perform one of the following as appropriate:\n1. If data-in-transit is to be enforced for the client, then enable data-in-transit\nencryptionforthatclientbysettingtheDTE_CLIENT_MODEoptioninthebp.conf\nconfiguration file to On.\n2. If data-in-transit is to be off for the particular client then change the\ndata-in-transit encryption (DTE) mode of the backup image to Off using the\nfollowing command:\nbpimage -update -image_dtemode Off -id \n3. Set DTE_IGNORE_IMAGE_MODE = ALWAYS in the NetBackup configuration file of\nthe primary server.\nFor option 2 and option 3, DTE is disabled while the job is performed.\nFor more information, refer to the Configuring data-in-transit encryption section in\nthe NetBackup Security and Encryption Guide." }, "8314": { "code": 8314, - "desc": "O mídia está não yet ready para o backup operation.", - "first_action": "Retry o operation e if o issue persists, visit", - "full_action": "Retry o operation e if o issue persists, visit\nsupport.veritas.com. O Cohesity Technical Support website site offers additional\ninformação to help you troubleshoot this issue." + "desc": "The media is not yet ready for the backup operation.", + "first_action": "Retry the operation and if the issue persists, visit", + "full_action": "Retry the operation and if the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support website site offers additional\ninformation to help you troubleshoot this issue." }, "8315": { "code": 8315, - "desc": "O mídia servidor has não completed o backup operation.", - "first_action": "Retry o operation e if o issue persists, visit", - "full_action": "Retry o operation e if o issue persists, visit\nsupport.veritas.com. O Cohesity Technical Support website site offers additional\ninformação to help you troubleshoot this issue." + "desc": "The media server has not completed the backup operation.", + "first_action": "Retry the operation and if the issue persists, visit", + "full_action": "Retry the operation and if the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support website site offers additional\ninformation to help you troubleshoot this issue." }, "8316": { "code": 8316, - "desc": "Falhou to retrieve o pre-shared key which está requerido para TLS communication.", - "first_action": "Retry o operation e if o issue persists, visit", - "full_action": "Retry o operation e if o issue persists, visit\nsupport.veritas.com. O Cohesity Technical Support website site offers additional\ninformação to help you troubleshoot this issue." + "desc": "Failed to retrieve the pre-shared key which is required for TLS communication.", + "first_action": "Retry the operation and if the issue persists, visit", + "full_action": "Retry the operation and if the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support website site offers additional\ninformation to help you troubleshoot this issue." }, "8350": { "code": 8350, - "desc": "O backup job falhou. O protection plan está configurado to fail partially successful backups.", + "desc": "The backup job failed. The protection plan is configured to fail partially successful backups.", "first_action": "Reviewthejob detailstosee theresourcesthatfail.Ifyou", - "full_action": "Reviewthejob detailstosee theresourcesthatfail.Ifyou\ndesejar to retain um backup com o falhou resources, consider disabling this recurso.\nIn o Backup options tab, while configuring um protection plan, clear o option:\nFail um backup job, if qualquer de o resources fail to get protected" + "full_action": "Reviewthejob detailstosee theresourcesthatfail.Ifyou\nwant to retain a backup with the failed resources, consider disabling this feature.\nIn the Backup options tab, while configuring a protection plan, clear the option:\nFail a backup job, if any of the resources fail to get protected" }, "8351": { "code": 8351, - "desc": "Kubernetes Operator Service está down.", - "first_action": "To verifique o status de o deployment, run o", - "full_action": "To verifique o status de o deployment, run o\ncommand:helm list -n \nMake sure que o Kubernetes NetBackup operator está deployed in o cluster." + "desc": "Kubernetes Operator Service is down.", + "first_action": "To verify the status of the deployment, run the", + "full_action": "To verify the status of the deployment, run the\ncommand:helm list -n \nMake sure that the Kubernetes NetBackup operator is deployed in the cluster." }, "8352": { "code": 8352, - "desc": "O asset group doesn’t have valid clusters.", - "first_action": "To run o backup, select um asset group com um valid", - "full_action": "To run o backup, select um asset group com um valid\ncluster ou um cluster que está não deleted." + "desc": "The asset group doesn’t have valid clusters.", + "first_action": "To run the backup, select an asset group with a valid", + "full_action": "To run the backup, select an asset group with a valid\ncluster or a cluster that is not deleted." }, "8401": { "code": 8401, - "desc": "Erro in creating o service in o namespace para o PrimaryServer .", - "first_action": "Verifique o NetBackup operator logs para details usando o seguinte comando:", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o NetBackup operator logs para details usando o seguinte comando:\nkubectl logs netbackup-operator -n\n\n■ Verifique que RBAC permissions estão correct. Refer to o NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Verifique seu cluster configuration e garanta que it meets o expected\nprerequisites.RefertotheNetBackupDeploymentonAzureKubernetesCluster\n(AKS) Administrator’s Guide.\n■ Verifique o Kubernetes documentation para service details:\nhttps://kubernetes.io/docs/concepts/services-networking/service/\n■ If you deploy NetBackup on Azure Kubernetes Cluster para o first time, you can\nexcluir o environment CR usando o seguinte comando:\n■ kubectl excluir -f e recreate it again kubectl\napply -f \nTheNetBackupenvironmentanditsresourcesaredeletedandrecreatedagain." + "desc": "Error in creating the service in the namespace for the PrimaryServer .", + "first_action": "Check the NetBackup operator logs for details using the following command:", + "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs netbackup-operator -n\n\n■ Verify that RBAC permissions are correct. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check your cluster configuration and ensure that it meets the expected\nprerequisites.RefertotheNetBackupDeploymentonAzureKubernetesCluster\n(AKS) Administrator’s Guide.\n■ Check the Kubernetes documentation for service details:\nhttps://kubernetes.io/docs/concepts/services-networking/service/\n■ If you deploy NetBackup on Azure Kubernetes Cluster for the first time, you can\ndelete the environment CR using the following command:\n■ kubectl delete -f and recreate it again kubectl\napply -f \nTheNetBackupenvironmentanditsresourcesaredeletedandrecreatedagain." }, "8402": { "code": 8402, - "desc": "Erro in fetching o service from o namespace para o PrimaryServer . NetBackup status codes 997 NetBackup status codes", - "first_action": "Verifique o NetBackup operator logs para details usando o seguinte comando:", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o NetBackup operator logs para details usando o seguinte comando:\nkubectl logs netbackup-operator -n\n\n■ Verifique que RBAC permissions estão correct. Refer to o NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Verifique if o service está created in o given namespace usando o seguinte\ncomando:\nkubectl get service -n \n■ Verifique o Kubernetes documentation para service\ndetails:https://kubernetes.io/docs/concepts/services-networking/service/" + "desc": "Error in fetching the service from the namespace for the PrimaryServer . NetBackup status codes 997 NetBackup status codes", + "first_action": "Check the NetBackup operator logs for details using the following command:", + "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs netbackup-operator -n\n\n■ Verify that RBAC permissions are correct. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check if the service is created in the given namespace using the following\ncommand:\nkubectl get service -n \n■ Check the Kubernetes documentation for service\ndetails:https://kubernetes.io/docs/concepts/services-networking/service/" }, "8403": { "code": 8403, - "desc": "Erro in creating o service in o namespace para o PrimaryServer because o service está already disponível in o namespace com um unexpected label.", - "first_action": "Verifique o NetBackup operator logs para details usando o seguinte comando:", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o NetBackup operator logs para details usando o seguinte comando:\nkubectl logs netbackup-operator -n\n\n■ Excluir o service usando o seguinte comando:\nkubectl excluir service -n \n■ Verifique que RBAC permissions estão correct. Refer to o NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Verifique seu cluster configuration e verifique que it meets o expected\nprerequisites para NetBackup deployment. Refer to o NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Refer to o Kubernetes documentation para service details:\nhttps://kubernetes.io/docs/concepts/services-networking/service/" + "desc": "Error in creating the service in the namespace for the PrimaryServer because the service is already available in the namespace with an unexpected label.", + "first_action": "Check the NetBackup operator logs for details using the following command:", + "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs netbackup-operator -n\n\n■ Delete the service using the following command:\nkubectl delete service -n \n■ Verify that RBAC permissions are correct. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check your cluster configuration and verify that it meets the expected\nprerequisites for NetBackup deployment. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Refer to the Kubernetes documentation for service details:\nhttps://kubernetes.io/docs/concepts/services-networking/service/" }, "8404": { "code": 8404, - "desc": "Erro in creating o service in o namespace forthePrimaryServer becausetheservice está already disponível in o namespace com um unexpected selector.", - "first_action": "Verifique o NetBackup operator logs para details usando o seguinte comando:", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o NetBackup operator logs para details usando o seguinte comando:\nkubectl logs netbackup-operator -n\n\n■ Excluir o service usando o seguinte comando:\nkubectl excluir service -n \nO NetBackup operator recreates o service.\n■ Verifique que RBAC permissions estão correct. Refer to o NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Verifique o Kubernetes documentation para service details:\nhttps://kubernetes.io/docs/concepts/services-networking/service/" + "desc": "Error in creating the service in the namespace forthePrimaryServer becausetheservice is already available in the namespace with an unexpected selector.", + "first_action": "Check the NetBackup operator logs for details using the following command:", + "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs netbackup-operator -n\n\n■ Delete the service using the following command:\nkubectl delete service -n \nThe NetBackup operator recreates the service.\n■ Verify that RBAC permissions are correct. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check the Kubernetes documentation for service details:\nhttps://kubernetes.io/docs/concepts/services-networking/service/" }, "8405": { "code": 8405, - "desc": "Erro in creating o ConfigMap in o namespace para o PrimaryServer .", - "first_action": "Verifique o NetBackup operator logs para details usando o seguinte comando:", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o NetBackup operator logs para details usando o seguinte comando:\nkubectl logs netbackup-operator -n\n\n■ Verifique que RBAC permissions estão correct. Refer to o NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Verifique seu cluster configuration e verifique que it meets o expected\nprerequisites para NetBackup deployment. Refer to o NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Verifique o Kubernetes documentation para ConfigMap details:\nhttps://kubernetes.io/docs/concepts/configuration/configmap/\n■ If you deploy NetBackup on Azure Kubernetes Cluster para o first time, you can\nexcluir o environment CR usando o seguinte comando:\n■ kubectl excluir -f e recreate it again kubectl\napply -f \nO NetBackup environment e its resources estão deleted e recreated\nagain." + "desc": "Error in creating the ConfigMap in the namespace for the PrimaryServer .", + "first_action": "Check the NetBackup operator logs for details using the following command:", + "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs netbackup-operator -n\n\n■ Verify that RBAC permissions are correct. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check your cluster configuration and verify that it meets the expected\nprerequisites for NetBackup deployment. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check the Kubernetes documentation for ConfigMap details:\nhttps://kubernetes.io/docs/concepts/configuration/configmap/\n■ If you deploy NetBackup on Azure Kubernetes Cluster for the first time, you can\ndelete the environment CR using the following command:\n■ kubectl delete -f and recreate it again kubectl\napply -f \nThe NetBackup environment and its resources are deleted and recreated\nagain." }, "8406": { "code": 8406, - "desc": "Erro in fetching o ConfigMap in o namespace para o PrimaryServer .", - "first_action": "Verifique o NetBackup operator logs para details usando o seguinte comando:", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o NetBackup operator logs para details usando o seguinte comando:\n“”.\nkubectl logs netbackup-operator -n\n\n■ Verifique que RBAC permissions estão correct. Refer to o NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Verifique if ConfigMap está disponível in given namespace usando o seguinte\ncomando:\nkubectl get configmap -n \n■ Verifique o Kubernetes documentation para ConfigMap details:\nhttps://kubernetes.io/docs/concepts/configuration/configmap/" + "desc": "Error in fetching the ConfigMap in the namespace for the PrimaryServer .", + "first_action": "Check the NetBackup operator logs for details using the following command:", + "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\n“”.\nkubectl logs netbackup-operator -n\n\n■ Verify that RBAC permissions are correct. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check if ConfigMap is available in given namespace using the following\ncommand:\nkubectl get configmap -n \n■ Check the Kubernetes documentation for ConfigMap details:\nhttps://kubernetes.io/docs/concepts/configuration/configmap/" }, "8407": { "code": 8407, - "desc": "Erro in creating o ConfigMap in o namespace para o PrimaryServer because o ConfigMap está already present in o namespace.", - "first_action": "Verifique o NetBackup operator logs para details usando o seguinte comando:", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o NetBackup operator logs para details usando o seguinte comando:\nkubectl logs netbackup-operator -n\n\n■ Excluir o existing ConfigMap com o same name in o namespace." + "desc": "Error in creating the ConfigMap in the namespace for the PrimaryServer because the ConfigMap is already present in the namespace.", + "first_action": "Check the NetBackup operator logs for details using the following command:", + "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs netbackup-operator -n\n\n■ Delete the existing ConfigMap with the same name in the namespace." }, "8408": { "code": 8408, - "desc": "ErrorincreatingPVC inthenamespace para o PrimaryServer .", - "first_action": "Verifique o NetBackup operator logs para details usando o seguinte comando:", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o NetBackup operator logs para details usando o seguinte comando:\nkubectl logs netbackup-operator -n\n\n■ Verifique if storageClassName e PVC armazenamento capacity estão correct in o CR\nYAML. If PVC está already disponível in o namespace com o same name, use\ncomando kubectl get pvc -n to verifique armazenamento\ncapacity. O armazenamento capacity must be greater than ou equal to o armazenamento\ncapacity que está mentioned in o CR spec.\n■ Verifique if o storageClassName provided in CR está disponível in o cluster usando\nseguinte comando:\nkubectl get storageclass\n■ Verifique que RBAC permissions estão correct. Refer to o NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Verifique o Kubernetes documentation para PVC details:\nhttps://kubernetes.io/docs/concepts/storage/persistent-volumes/" + "desc": "ErrorincreatingPVC inthenamespace for the PrimaryServer .", + "first_action": "Check the NetBackup operator logs for details using the following command:", + "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs netbackup-operator -n\n\n■ Check if storageClassName and PVC storage capacity are correct in the CR\nYAML. If PVC is already available in the namespace with the same name, use\ncommand kubectl get pvc -n to verify storage\ncapacity. The storage capacity must be greater than or equal to the storage\ncapacity that is mentioned in the CR spec.\n■ Check if the storageClassName provided in CR is available in the cluster using\nfollowing command:\nkubectl get storageclass\n■ Verify that RBAC permissions are correct. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check the Kubernetes documentation for PVC details:\nhttps://kubernetes.io/docs/concepts/storage/persistent-volumes/" }, "8409": { "code": 8409, - "desc": "Erro in fetching o PVC in o namespace para o PrimaryServer .", - "first_action": "Verifique o NetBackup operator logs para details usando o seguinte comando:", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o NetBackup operator logs para details usando o seguinte comando:\nkubectl logs netbackup-operator -n\n\n■ Verifique if o PVC está disponível in namespace usando o seguinte comando:\nkubectl get pvc -n \nIfthePVCisnotavailable,applytheenvironmentYAMLagainusingthefollowing\ncomando:\nkubectl apply -f \n■ Verifique que RBAC permissions estão correct. Refer to o NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Verifique o Kubernetes documentation para PVC details:\nhttps://kubernetes.io/docs/concepts/storage/persistent-volumes/" + "desc": "Error in fetching the PVC in the namespace for the PrimaryServer .", + "first_action": "Check the NetBackup operator logs for details using the following command:", + "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs netbackup-operator -n\n\n■ Check if the PVC is available in namespace using the following command:\nkubectl get pvc -n \nIfthePVCisnotavailable,applytheenvironmentYAMLagainusingthefollowing\ncommand:\nkubectl apply -f \n■ Verify that RBAC permissions are correct. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check the Kubernetes documentation for PVC details:\nhttps://kubernetes.io/docs/concepts/storage/persistent-volumes/" }, "8410": { "code": 8410, - "desc": "ErrorinupdatingPVC inthenamespace para o PrimaryServer .", - "first_action": "Verifique o NetBackup operator logs para details usando o seguinte comando:", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o NetBackup operator logs para details usando o seguinte comando:\nkubectl logs netbackup-operator -n\n\n■ EnsurethenewPVCstoragecapacitythatismentionedintheCRisgreaterthan\ncurrent armazenamento capacity. You não é possível shrink o capacity. In this case, update\ntheCRYAMLwithcorrectsizeandapplytheCRYAMLagainusingthefollowing\ncomando:\nkubectl apply -f \n■ Verifique que RBAC permissions estão correct. Refer to o NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Verifique o Kubernetes documentation para PVC details:\nhttps://kubernetes.io/docs/concepts/storage/persistent-volumes/" + "desc": "ErrorinupdatingPVC inthenamespace for the PrimaryServer .", + "first_action": "Check the NetBackup operator logs for details using the following command:", + "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs netbackup-operator -n\n\n■ EnsurethenewPVCstoragecapacitythatismentionedintheCRisgreaterthan\ncurrent storage capacity. You cannot shrink the capacity. In this case, update\ntheCRYAMLwithcorrectsizeandapplytheCRYAMLagainusingthefollowing\ncommand:\nkubectl apply -f \n■ Verify that RBAC permissions are correct. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check the Kubernetes documentation for PVC details:\nhttps://kubernetes.io/docs/concepts/storage/persistent-volumes/" }, "8411": { "code": 8411, - "desc": "Erro in creating o StatefulSet in o namespace para o PrimaryServer .", - "first_action": "Verifique o NetBackup operator logs para details usando o seguinte comando: “", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o NetBackup operator logs para details usando o seguinte comando: “\nkubectl logs netbackup-operator -n\n\n■ Verifique que RBAC permissions estão correct. Refer to o NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Verifique seu cluster configuration e verifique que it meets o expected\nprerequisites para NetBackup deployment. Refer to o NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Verifique o Kubernetes documentation para statefulset details:\nhttps://kubernetes.io/docs/concepts/workloads/controllers/statefulset/\n■ Verifique if o requerido secrets estão present in o namespace." + "desc": "Error in creating the StatefulSet in the namespace for the PrimaryServer .", + "first_action": "Check the NetBackup operator logs for details using the following command: “", + "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command: “\nkubectl logs netbackup-operator -n\n\n■ Verify that RBAC permissions are correct. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check your cluster configuration and verify that it meets the expected\nprerequisites for NetBackup deployment. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check the Kubernetes documentation for statefulset details:\nhttps://kubernetes.io/docs/concepts/workloads/controllers/statefulset/\n■ Check if the required secrets are present in the namespace." }, "8412": { "code": 8412, - "desc": "Erro in fetching o StatefulSet from o namespace para o PrimaryServer .", - "first_action": "Verifique o NetBackup operator logs para details usando o seguinte comando:", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o NetBackup operator logs para details usando o seguinte comando:\nkubectl logs netbackup-operator -n\n\n■ Verifique que RBAC permissions estão correct. Refer to o NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Verifique seu cluster configuration e verifique que it meets o expected\nprerequisites para NetBackup deployment. Refer to o NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Verifique o Kubernetes documentation para statefulset details:\nhttps://kubernetes.io/docs/concepts/workloads/controllers/statefulset/\n■ If you deploy NetBackup on Azure Kubernetes Cluster para o first time, you can\nexcluir o environment CR usando o seguinte comando:\nkubectl excluir -f andrecreateitagainkubectl apply\n-f \nTheNetBackupenvironmentanditsresourcesaredeletedandrecreatedagain." + "desc": "Error in fetching the StatefulSet from the namespace for the PrimaryServer .", + "first_action": "Check the NetBackup operator logs for details using the following command:", + "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs netbackup-operator -n\n\n■ Verify that RBAC permissions are correct. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check your cluster configuration and verify that it meets the expected\nprerequisites for NetBackup deployment. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check the Kubernetes documentation for statefulset details:\nhttps://kubernetes.io/docs/concepts/workloads/controllers/statefulset/\n■ If you deploy NetBackup on Azure Kubernetes Cluster for the first time, you can\ndelete the environment CR using the following command:\nkubectl delete -f andrecreateitagainkubectl apply\n-f \nTheNetBackupenvironmentanditsresourcesaredeletedandrecreatedagain." }, "8413": { "code": 8413, - "desc": "Erro in creating o StatefulSet in o namespace para o PrimaryServer because o StatefulSet está already disponível in o namespace com um unexpected label.", - "first_action": "Verifique o NetBackup operator logs para details usando o seguinte comando:", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o NetBackup operator logs para details usando o seguinte comando:\nkubectl logs netbackup-operator -n\n\n■ Excluir o existing statefulset usando o seguinte comando:\nkubectl excluir statefulset -n \nO operator recreates o statefulset.\n■ Verifique o Kubernetes documentation para statefulset details:\nhttps://kubernetes.io/docs/concepts/workloads/controllers/statefulset/" + "desc": "Error in creating the StatefulSet in the namespace for the PrimaryServer because the StatefulSet is already available in the namespace with an unexpected label.", + "first_action": "Check the NetBackup operator logs for details using the following command:", + "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs netbackup-operator -n\n\n■ Delete the existing statefulset using the following command:\nkubectl delete statefulset -n \nThe operator recreates the statefulset.\n■ Check the Kubernetes documentation for statefulset details:\nhttps://kubernetes.io/docs/concepts/workloads/controllers/statefulset/" }, "8414": { "code": 8414, - "desc": "Erro in creating o StatefulSet in o namespace para o PrimaryServer because o StatefulSet está already disponível in o namespace com um unexpected selector.", - "first_action": "Verifique o NetBackup operator logs para details usando o seguinte comando:", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o NetBackup operator logs para details usando o seguinte comando:\nkubectl logs netbackup-operator -n\n\n■ Excluir o existing statefulset usando o seguinte comando: “.\nkubectl excluir statefulset -n \nO operator recreates o statefulset.\n■ Verifique o Kubernetes documentation para statefulset details:\nhttps://kubernetes.io/docs/concepts/workloads/controllers/statefulset/" + "desc": "Error in creating the StatefulSet in the namespace for the PrimaryServer because the StatefulSet is already available in the namespace with an unexpected selector.", + "first_action": "Check the NetBackup operator logs for details using the following command:", + "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs netbackup-operator -n\n\n■ Delete the existing statefulset using the following command: “.\nkubectl delete statefulset -n \nThe operator recreates the statefulset.\n■ Check the Kubernetes documentation for statefulset details:\nhttps://kubernetes.io/docs/concepts/workloads/controllers/statefulset/" }, "8415": { "code": 8415, - "desc": "Erro in creating o service in o namespace para o MediaServer .", - "first_action": "Verifique o NetBackup operator logs para details usando o seguinte comando:", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o NetBackup operator logs para details usando o seguinte comando:\nkubectl logs netbackup-operator -n\n\n■ Verifique que RBAC permissions estão correct. Refer to o NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Verifique seu cluster configuration e verifique que it meets o expected\nprerequisites para NetBackup deployment. Refer to o NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Verifique o Kubernetes documentation para service details:\nhttps://kubernetes.io/docs/concepts/services-networking/service/\n■ If o issue still doesn’t resolve, executar o seguinte steps:\n■ Edit o environment CR e decrement o mídia servidor replicas. Change\nthereplicacountinthemediasectionwiththelastsuccessfulcountforwhich\no load balancer service foi created para o mídia replicas. Then, apply\no changes usando o seguinte comando:\nkubectl apply -f \n■ Para example: O mídia replica count está set to three e services estão\nsuccessfully created para apenas two mídia servers replicas. However, there\nisanerrorincreatingserviceforthethirdmediaserver.Youmustchange\no replica count to two.\n■ If there está um erro in creating service para o first mídia replica, change\no replica count to 0.\n■ Verifique if o mídia replica services estão decremented como per provided replica\ncount usando o seguinte comando:\nkubectl get service -n \n■ Edit o environment CR e increment mídia replica count back to o\noriginal count e apply o changes. Verifique if o service está now created para\nrespective mídia servidor." + "desc": "Error in creating the service in the namespace for the MediaServer .", + "first_action": "Check the NetBackup operator logs for details using the following command:", + "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs netbackup-operator -n\n\n■ Verify that RBAC permissions are correct. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check your cluster configuration and verify that it meets the expected\nprerequisites for NetBackup deployment. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check the Kubernetes documentation for service details:\nhttps://kubernetes.io/docs/concepts/services-networking/service/\n■ If the issue still doesn’t resolve, perform the following steps:\n■ Edit the environment CR and decrement the media server replicas. Change\nthereplicacountinthemediasectionwiththelastsuccessfulcountforwhich\nthe load balancer service was created for the media replicas. Then, apply\nthe changes using the following command:\nkubectl apply -f \n■ For example: The media replica count is set to three and services are\nsuccessfully created for only two media servers replicas. However, there\nisanerrorincreatingserviceforthethirdmediaserver.Youmustchange\nthe replica count to two.\n■ If there is an error in creating service for the first media replica, change\nthe replica count to 0.\n■ Verify if the media replica services are decremented as per provided replica\ncount using the following command:\nkubectl get service -n \n■ Edit the environment CR and increment media replica count back to the\noriginal count and apply the changes. Verify if the service is now created for\nrespective media server." }, "8416": { "code": 8416, - "desc": "Erro in fetching o service from o namespace para o MediaServer .", - "first_action": "Verifique o NetBackup operator logs para details usando o seguinte comando:", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o NetBackup operator logs para details usando o seguinte comando:\nkubectl logs netbackup-operator -n\n\n■ Verifique que RBAC permissions estão correct. Refer to o NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Verifique if service está disponível in given namespace usando o seguinte comando:\nkubectl get service -n \n■ Verifique o Kubernetes documentation para service details:\nhttps://kubernetes.io/docs/concepts/services-networking/service/" + "desc": "Error in fetching the service from the namespace for the MediaServer .", + "first_action": "Check the NetBackup operator logs for details using the following command:", + "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs netbackup-operator -n\n\n■ Verify that RBAC permissions are correct. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check if service is available in given namespace using the following command:\nkubectl get service -n \n■ Check the Kubernetes documentation for service details:\nhttps://kubernetes.io/docs/concepts/services-networking/service/" }, "8417": { "code": 8417, - "desc": "Service already disponível in o namespace para o MediaServer com unexpected labels.", - "first_action": "Verifique o NetBackup operator logs para details usando o seguinte comando:", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o NetBackup operator logs para details usando o seguinte comando:\nkubectl logs netbackup-operator -n\n\n■ Excluir o service usando o seguinte comando:\nkubectl excluir service -n \nO operator recreates o service.\n■ Verifique que RBAC permissions estão correct. Refer to o NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Verifique seu cluster configuration e verifique que it meets o expected\nprerequisites para NetBackup deployment. Refer to o NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Verifique o Kubernetes documentation para service details:\nhttps://kubernetes.io/docs/concepts/services-networking/service/" + "desc": "Service already available in the namespace for the MediaServer with unexpected labels.", + "first_action": "Check the NetBackup operator logs for details using the following command:", + "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs netbackup-operator -n\n\n■ Delete the service using the following command:\nkubectl delete service -n \nThe operator recreates the service.\n■ Verify that RBAC permissions are correct. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check your cluster configuration and verify that it meets the expected\nprerequisites for NetBackup deployment. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check the Kubernetes documentation for service details:\nhttps://kubernetes.io/docs/concepts/services-networking/service/" }, "8418": { "code": 8418, - "desc": "Service already disponível in o namespace fortheMediaServer withunexpectedselectors.", - "first_action": "Verifique o NetBackup operator logs para details usando o seguinte comando:", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o NetBackup operator logs para details usando o seguinte comando:\nkubectl logs netbackup-operator -n\n\n■ Excluir o service usando o seguinte comando:\nkubectl excluir service -n \nO operator recreates o service.\n■ Verifique que RBAC permissions estão correct. Refer to o NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Verifique o Kubernetes documentation para service details:\nhttps://kubernetes.io/docs/concepts/services-networking/service/" + "desc": "Service already available in the namespace fortheMediaServer withunexpectedselectors.", + "first_action": "Check the NetBackup operator logs for details using the following command:", + "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs netbackup-operator -n\n\n■ Delete the service using the following command:\nkubectl delete service -n \nThe operator recreates the service.\n■ Verify that RBAC permissions are correct. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check the Kubernetes documentation for service details:\nhttps://kubernetes.io/docs/concepts/services-networking/service/" }, "8419": { "code": 8419, - "desc": "Erro in creating o ConfigMap in o namespace para o MediaServer .", - "first_action": "Verifique o NetBackup operator logs para details usando o seguinte comando:", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o NetBackup operator logs para details usando o seguinte comando:\nkubectl logs netbackup-operator -n\n\n■ Verifique que RBAC permissions estão correct. Refer to o NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Verifique seu cluster configuration e verifique que it meets o expected\nprerequisites para NetBackup deployment. Refer to o NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Verifique o Kubernetes documentation para service details:\nhttps://kubernetes.io/docs/concepts/services-networking/service/\n■ If you deploy NetBackup on Azure Kubernetes Cluster para o first time, you\ncan excluir o mídia CR por removing o mediaServers section in o\nenvironment CR YAML. You need to save o mediaServer data to reuse it\nin next step.\n■ Recreate o MediaServer CR again por updating o environment.yaml\nwiththemediaServerssectionthatwasdeletedearlierandapplythechanges\nusando o seguinte comando:\nkubectl apply -f \nO NetBackup environment e its resources estão deleted e recreated\nagain." + "desc": "Error in creating the ConfigMap in the namespace for the MediaServer .", + "first_action": "Check the NetBackup operator logs for details using the following command:", + "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs netbackup-operator -n\n\n■ Verify that RBAC permissions are correct. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check your cluster configuration and verify that it meets the expected\nprerequisites for NetBackup deployment. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check the Kubernetes documentation for service details:\nhttps://kubernetes.io/docs/concepts/services-networking/service/\n■ If you deploy NetBackup on Azure Kubernetes Cluster for the first time, you\ncan delete the media CR by removing the mediaServers section in the\nenvironment CR YAML. You need to save the mediaServer data to reuse it\nin next step.\n■ Recreate the MediaServer CR again by updating the environment.yaml\nwiththemediaServerssectionthatwasdeletedearlierandapplythechanges\nusing the following command:\nkubectl apply -f \nThe NetBackup environment and its resources are deleted and recreated\nagain." }, "8420": { "code": 8420, - "desc": "Erro in fetching o ConfigMap in o namespace para o MediaServer .", - "first_action": "Verifique o NetBackup operator logs para details usando o seguinte comando:", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o NetBackup operator logs para details usando o seguinte comando:\nkubectl logs netbackup-operator -n\n\n■ Verifique que RBAC permissions estão correct. Refer to o NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Verifique if configmap está disponível in o given namespace usando o seguinte\ncomando:\nkubectl get configmap -n \n■ Verifique o Kubernetes documentation para configmap details:\nhttps://kubernetes.io/docs/concepts/configuration/configmap/" + "desc": "Error in fetching the ConfigMap in the namespace for the MediaServer .", + "first_action": "Check the NetBackup operator logs for details using the following command:", + "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs netbackup-operator -n\n\n■ Verify that RBAC permissions are correct. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check if configmap is available in the given namespace using the following\ncommand:\nkubectl get configmap -n \n■ Check the Kubernetes documentation for configmap details:\nhttps://kubernetes.io/docs/concepts/configuration/configmap/" }, "8421": { "code": 8421, - "desc": "Erro in updating o ConfigMap in o namespace para o MediaServer .", - "first_action": "Verifique o NetBackup operator logs para details usando o seguinte comando:", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o NetBackup operator logs para details usando o seguinte comando:\nkubectl logs netbackup-operator -n\n\n■ Verifique o Kubernetes documentation para configmap details:\nhttps://kubernetes.io/docs/concepts/configuration/configmap/" + "desc": "Error in updating the ConfigMap in the namespace for the MediaServer .", + "first_action": "Check the NetBackup operator logs for details using the following command:", + "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs netbackup-operator -n\n\n■ Check the Kubernetes documentation for configmap details:\nhttps://kubernetes.io/docs/concepts/configuration/configmap/" }, "8422": { "code": 8422, - "desc": "ConfigMap está already disponível in o namespace para o MediaServer com unexpected labels.", - "first_action": "Verifique o NetBackup operator logs para details usando o seguinte comando:", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o NetBackup operator logs para details usando o seguinte comando:\nkubectl logs netbackup-operator -n\n\n■ Verifique o Kubernetes documentation para configmap details:\nhttps://kubernetes.io/docs/concepts/configuration/configmap/" + "desc": "ConfigMap is already available in the namespace for the MediaServer with unexpected labels.", + "first_action": "Check the NetBackup operator logs for details using the following command:", + "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs netbackup-operator -n\n\n■ Check the Kubernetes documentation for configmap details:\nhttps://kubernetes.io/docs/concepts/configuration/configmap/" }, "8423": { "code": 8423, - "desc": "Erro in creating o StatefulSet in o namespace para o MediaServer .", - "first_action": "Verifique o NetBackup operator logs para details usando o seguinte comando:", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o NetBackup operator logs para details usando o seguinte comando:\nkubectl logs netbackup-operator -n\n\n■ Verifique que RBAC permissions estão correct. Refer to o NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Verifique seu cluster configuration e verifique que it meets o expected\nprerequisites para NetBackup deployment. Refer to o NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Verifique o Kubernetes documentation para statefulset details:\nhttps://kubernetes.io/docs/concepts/workloads/controllers/statefulset/" + "desc": "Error in creating the StatefulSet in the namespace for the MediaServer .", + "first_action": "Check the NetBackup operator logs for details using the following command:", + "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs netbackup-operator -n\n\n■ Verify that RBAC permissions are correct. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check your cluster configuration and verify that it meets the expected\nprerequisites for NetBackup deployment. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check the Kubernetes documentation for statefulset details:\nhttps://kubernetes.io/docs/concepts/workloads/controllers/statefulset/" }, "8424": { "code": 8424, - "desc": "Erro in fetching o StatefulSet from o namespace para o MediaServer .", - "first_action": "Verifique o NetBackup operator logs para details usando o seguinte comando:", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o NetBackup operator logs para details usando o seguinte comando:\nkubectl logs netbackup-operator -n\n\n■ Verifique que RBAC permissions estão correct. Refer to o NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Verifique seu cluster para issues e verifique que o configuration está correct. Verifique\nque it meets o expected prerequisites para NetBackup deployment. Refer to\ntheNetBackupDeploymentonAzureKubernetesCluster(AKS)Administrator’s\nGuide.\n■ Verifique o Kubernetes documentation para statefulset details:\nhttps://kubernetes.io/docs/concepts/workloads/controllers/statefulset/\n■ If o setup está um fresh deployment e o backup e o recovery jobs estão não\nconfigurado:\n■ You may excluir o CR por removing mediaServers section in\nenvironment.yaml (usuário needs to save o mediaServer data to reuse it in\nnext step) e apply o changes usando o seguinte comando:\nkubectl apply -f \n■ Recreate o MediaServer CR again por updating o environment.yaml\nwiththeMediaServersectionthatwasdeletedearlierandapplythechanges\nusando o seguinte comando:\nkubectl apply -f \nO NetBackup environment e its resources estão deleted e recreated\nagain." + "desc": "Error in fetching the StatefulSet from the namespace for the MediaServer .", + "first_action": "Check the NetBackup operator logs for details using the following command:", + "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs netbackup-operator -n\n\n■ Verify that RBAC permissions are correct. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check your cluster for issues and verify that the configuration is correct. Verify\nthat it meets the expected prerequisites for NetBackup deployment. Refer to\ntheNetBackupDeploymentonAzureKubernetesCluster(AKS)Administrator’s\nGuide.\n■ Check the Kubernetes documentation for statefulset details:\nhttps://kubernetes.io/docs/concepts/workloads/controllers/statefulset/\n■ If the setup is a fresh deployment and the backup and the recovery jobs are not\nconfigured:\n■ You may delete the CR by removing mediaServers section in\nenvironment.yaml (user needs to save the mediaServer data to reuse it in\nnext step) and apply the changes using the following command:\nkubectl apply -f \n■ Recreate the MediaServer CR again by updating the environment.yaml\nwiththeMediaServersectionthatwasdeletedearlierandapplythechanges\nusing the following command:\nkubectl apply -f \nThe NetBackup environment and its resources are deleted and recreated\nagain." }, "8425": { "code": 8425, - "desc": "Erro in updating o StatefulSet from o namespace para o MediaServer . NetBackup status codes 1011 NetBackup status codes", - "first_action": "Verifique o NetBackup operator logs para details usando o seguinte comando:", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o NetBackup operator logs para details usando o seguinte comando:\nkubectl logs netbackup-operator -n\n\n■ Verifique if o replica count in o mídia servidor section in environment CR está\ngreater than o previously used replica count.\n■ Verifique que RBAC permissions estão correct. Refer to o NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Verifique o Kubernetes documentation para statefulset details:\nhttps://kubernetes.io/docs/concepts/workloads/controllers/statefulset/" + "desc": "Error in updating the StatefulSet from the namespace for the MediaServer . NetBackup status codes 1011 NetBackup status codes", + "first_action": "Check the NetBackup operator logs for details using the following command:", + "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs netbackup-operator -n\n\n■ Check if the replica count in the media server section in environment CR is\ngreater than the previously used replica count.\n■ Verify that RBAC permissions are correct. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check the Kubernetes documentation for statefulset details:\nhttps://kubernetes.io/docs/concepts/workloads/controllers/statefulset/" }, "8426": { "code": 8426, - "desc": "StatefulSet alreadyavailableinthenamespace para o MediaServer com unexpected labels.", - "first_action": "Verifique o NetBackup operator logs para details usando o seguinte comando:", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o NetBackup operator logs para details usando o seguinte comando:\nkubectl logs netbackup-operator -n\n\n■ Excluir o existing statefulset usando o seguinte comando:\nkubectl excluir statefulset -n \nO operator recreates o statefulset.\n■ Verifique o Kubernetes documentation para statefulset details:\nhttps://kubernetes.io/docs/concepts/workloads/controllers/statefulset/" + "desc": "StatefulSet alreadyavailableinthenamespace for the MediaServer with unexpected labels.", + "first_action": "Check the NetBackup operator logs for details using the following command:", + "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs netbackup-operator -n\n\n■ Delete the existing statefulset using the following command:\nkubectl delete statefulset -n \nThe operator recreates the statefulset.\n■ Check the Kubernetes documentation for statefulset details:\nhttps://kubernetes.io/docs/concepts/workloads/controllers/statefulset/" }, "8427": { "code": 8427, - "desc": "StatefulSet alreadyavailableinthenamespace para o MediaServer com unexpected selectors. NetBackup status codes 1012 NetBackup status codes", - "first_action": "Verifique o NetBackup operator logs para details usando o seguinte comando:", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o NetBackup operator logs para details usando o seguinte comando:\nkubectl logs netbackup-operator -n\n\n■ Excluir o existing statefulset usando o seguinte comando:\nkubectl excluir statefulset -n \n■ Verifique o Kubernetes documentation para statefulset details:\nhttps://kubernetes.io/docs/concepts/workloads/controllers/statefulset/" + "desc": "StatefulSet alreadyavailableinthenamespace for the MediaServer with unexpected selectors. NetBackup status codes 1012 NetBackup status codes", + "first_action": "Check the NetBackup operator logs for details using the following command:", + "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs netbackup-operator -n\n\n■ Delete the existing statefulset using the following command:\nkubectl delete statefulset -n \n■ Check the Kubernetes documentation for statefulset details:\nhttps://kubernetes.io/docs/concepts/workloads/controllers/statefulset/" }, "8428": { "code": 8428, - "desc": "Falhou to get um instance de o Primary service.", - "first_action": "Verifique o NetBackup operator logs para details usando o seguinte comando:", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o NetBackup operator logs para details usando o seguinte comando:\nkubectl logs netbackup-operator -n\n\n■ Checkiftheprimaryloadbalancerserviceisavailableingivennamespaceusing\no seguinte comando:\nkubectl get service -n \n■ Verifique seu cluster verifique que o configuration está correct. Verifique que it meets\no expected prerequisites para NetBackup deployment. Refer to o NetBackup\nDeployment on Azure Kubernetes Cluster (AKS) Administrator’s Guide." + "desc": "Failed to get an instance of the Primary service.", + "first_action": "Check the NetBackup operator logs for details using the following command:", + "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs netbackup-operator -n\n\n■ Checkiftheprimaryloadbalancerserviceisavailableingivennamespaceusing\nthe following command:\nkubectl get service -n \n■ Check your cluster verify that the configuration is correct. Verify that it meets\nthe expected prerequisites for NetBackup deployment. Refer to the NetBackup\nDeployment on Azure Kubernetes Cluster (AKS) Administrator’s Guide." }, "8429": { "code": 8429, - "desc": "Falhou to get o load balancer service details de o primary servidor.", - "first_action": "Verifique o NetBackup operator logs para details usando o seguinte comando:", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o NetBackup operator logs para details usando o seguinte comando:\nkubectl logs netbackup-operator -n\n\n■ There might be um issue in fetching o service. Verifique que RBAC permissions\nestão correct. Refer to o NetBackup Deployment on Azure Kubernetes Cluster\n(AKS) Administrator’s Guide." + "desc": "Failed to get the load balancer service details of the primary server.", + "first_action": "Check the NetBackup operator logs for details using the following command:", + "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs netbackup-operator -n\n\n■ There might be an issue in fetching the service. Verify that RBAC permissions\nare correct. Refer to the NetBackup Deployment on Azure Kubernetes Cluster\n(AKS) Administrator’s Guide." }, "8430": { "code": 8430, - "desc": "Falhou to conectar to o primary servidor because o primary servidor may não have started.", - "first_action": "Verifique o NetBackup operator logs para details usando o seguinte comando:", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o NetBackup operator logs para details usando o seguinte comando:\nkubectl logs netbackup-operator -n\n\n■ Ensurethattheclusternetworkisconfiguredcorrectly.Theloadbalancerservice\nmay não be routing requests to o pod correctly.\n■ Verifique o PrimaryServer pod está in o ready state (1/1)." + "desc": "Failed to connect to the primary server because the primary server may not have started.", + "first_action": "Check the NetBackup operator logs for details using the following command:", + "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs netbackup-operator -n\n\n■ Ensurethattheclusternetworkisconfiguredcorrectly.Theloadbalancerservice\nmay not be routing requests to the pod correctly.\n■ Check the PrimaryServer pod is in the ready state (1/1)." }, "8431": { "code": 8431, - "desc": "Falhou to get primary server’s authentication secret in o namespace .", - "first_action": "Verifique o NetBackup operator logs para details usando o seguinte comando:", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o NetBackup operator logs para details usando o seguinte comando:\nkubectl logs netbackup-operator -n\n\n■ Verifique que o respective secret está disponível in o namespace onde o\nPrimaryServer CR está deployed usando o seguinte comando:\nkubectl get secret -n " + "desc": "Failed to get primary server’s authentication secret in the namespace .", + "first_action": "Check the NetBackup operator logs for details using the following command:", + "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs netbackup-operator -n\n\n■ Check that the respective secret is available in the namespace where the\nPrimaryServer CR is deployed using the following command:\nkubectl get secret -n " }, "8432": { "code": 8432, - "desc": "Falhou to get o CA certificate fingerprint ou token from o primary servidor.", - "first_action": "Verifique o NetBackup operator logs para details usando o seguinte comando:", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o NetBackup operator logs para details usando o seguinte comando:\nkubectl logs netbackup-operator -n\n\n■ O PrimaryServer credentials may have expired. Wait para o next reconciler\nloop (wait time para 5 min added).\n■ Look para o primary servidor pod e verifique o ready state (1/1) de o\nPrimaryServer pod usando o seguinte comando:\nkubectl get pod -n \nIf primary pod está não in ready state, verifique o health probe events usando o\nseguinte comando:\nkubectl describe -n\n\n■ Para more informação que está related to health probes, refer to o NetBackup\nDeployment on Azure Kubernetes Cluster (AKS) Administrator’s Guide." + "desc": "Failed to get the CA certificate fingerprint or token from the primary server.", + "first_action": "Check the NetBackup operator logs for details using the following command:", + "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs netbackup-operator -n\n\n■ The PrimaryServer credentials may have expired. Wait for the next reconciler\nloop (wait time for 5 min added).\n■ Look for the primary server pod and check the ready state (1/1) of the\nPrimaryServer pod using the following command:\nkubectl get pod -n \nIf primary pod is not in ready state, check the health probe events using the\nfollowing command:\nkubectl describe -n\n\n■ For more information that is related to health probes, refer to the NetBackup\nDeployment on Azure Kubernetes Cluster (AKS) Administrator’s Guide." }, "8433": { "code": 8433, - "desc": "Erro in updating o bp.conf de o primary servidor in o namespace para o MediaServer .", - "first_action": "Verifique o NetBackup operator logs para details usando o seguinte comando:", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o NetBackup operator logs para details usando o seguinte comando:\nkubectl logs netbackup-operator -n\n\n■ Ensurethattheprimaryservercredentialsthatareinthesecretarenotexpired." + "desc": "Error in updating the bp.conf of the primary server in the namespace for the MediaServer .", + "first_action": "Check the NetBackup operator logs for details using the following command:", + "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs netbackup-operator -n\n\n■ Ensurethattheprimaryservercredentialsthatareinthesecretarenotexpired." }, "8434": { "code": 8434, - "desc": "Apenas one IP can be provided in o iplist de o Custom Resource para um primary servidor.", - "first_action": "In o networkLoadBalancer de o primary section de o environment CR", - "full_action": "Executar o seguinte como appropriate:\n■ In o networkLoadBalancer de o primary section de o environment CR\nYAML, o number de entradas que estão mentioned in o ipList must be equal\nto 1.\nIf não, edit o environment CR com either de seguinte items e garanta que\no number de entradas in ipList de o primary section must be equal to 1.\n■ Edit o environment CR usando seguinte comando e save:\nkubectl edit environments.netbackup.veritas.com\n -n \n■ Edit o environment CR YAML e apply o change usando seguinte\ncomando:\nkubectl apply -f " + "desc": "Only one IP can be provided in the iplist of the Custom Resource for a primary server.", + "first_action": "In the networkLoadBalancer of the primary section of the environment CR", + "full_action": "Perform the following as appropriate:\n■ In the networkLoadBalancer of the primary section of the environment CR\nYAML, the number of entries that are mentioned in the ipList must be equal\nto 1.\nIf not, edit the environment CR with either of following items and ensure that\nthe number of entries in ipList of the primary section must be equal to 1.\n■ Edit the environment CR using following command and save:\nkubectl edit environments.netbackup.veritas.com\n -n \n■ Edit the environment CR YAML and apply the change using following\ncommand:\nkubectl apply -f " }, "8435": { "code": 8435, - "desc": "NumberofIPsprovidedinipListofCustomResourcemustnotbeless than o replica count.", - "first_action": "Verifique o number de IP addresses que estão mentioned in o ipList provided", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o number de IP addresses que estão mentioned in o ipList provided\nin o networkLoadBalancer de o mídia section in o environment CR. O\nnumber must be greater than ou equal to o mídia replica count que está\nmentioned in same section.\nIf não, edit o environment CR e garanta que o number de entradas in o\nipList de o mediaServers section está greater than ou equal to mídia replica\ncount. Edit o environment CR com either de o seguinte items:\n■ Edit o environment CR usando seguinte comando e save:\nkubectl edit environments.netbackup.veritas.com\n -n \n■ Edit o environment CR YAML e apply o change usando seguinte\ncomando:\nkubectl apply -f " + "desc": "NumberofIPsprovidedinipListofCustomResourcemustnotbeless than the replica count.", + "first_action": "Verify the number of IP addresses that are mentioned in the ipList provided", + "full_action": "Perform the following as appropriate:\n■ Verify the number of IP addresses that are mentioned in the ipList provided\nin the networkLoadBalancer of the media section in the environment CR. The\nnumber must be greater than or equal to the media replica count that is\nmentioned in same section.\nIf not, edit the environment CR and ensure that the number of entries in the\nipList of the mediaServers section is greater than or equal to media replica\ncount. Edit the environment CR with either of the following items:\n■ Edit the environment CR using following command and save:\nkubectl edit environments.netbackup.veritas.com\n -n \n■ Edit the environment CR YAML and apply the change using following\ncommand:\nkubectl apply -f " }, "8436": { "code": 8436, - "desc": "ResourceNamePrefix in spec de custom resource de o mídia servidor must não contain o string primary.", - "first_action": "Garanta que o resourceNamePrefix in o mediaServers section de o", - "full_action": "Executar o seguinte como appropriate:\n■ Garanta que o resourceNamePrefix in o mediaServers section de o\nenvironment CR does não have o primary substring.\nIf it does contain o primary substring, edit o environment CR com either de\nseguinte steps e update o resourceNamePrefix in o mediaServers\nsection.\n■ Edit o environment CR usando seguinte comando e save:\nkubectl edit environments.netbackup.veritas.com\n -n \n■ Edit o environment CR YAML e apply o change usando seguinte\ncomando:\nkubectl apply -f " + "desc": "ResourceNamePrefix in spec of custom resource of the media server must not contain the string primary.", + "first_action": "Ensure that the resourceNamePrefix in the mediaServers section of the", + "full_action": "Perform the following as appropriate:\n■ Ensure that the resourceNamePrefix in the mediaServers section of the\nenvironment CR does not have the primary substring.\nIf it does contain the primary substring, edit the environment CR with either of\nfollowing steps and update the resourceNamePrefix in the mediaServers\nsection.\n■ Edit the environment CR using following command and save:\nkubectl edit environments.netbackup.veritas.com\n -n \n■ Edit the environment CR YAML and apply the change using following\ncommand:\nkubectl apply -f " }, "8437": { "code": 8437, - "desc": "ResourceNamePrefix in spec de custom resource de o primary servidor must não contain o string mídia.", - "first_action": "Garanta que o resourceNamePrefix in primary section de environment CR", - "full_action": "Executar o seguinte como appropriate:\n■ Garanta que o resourceNamePrefix in primary section de environment CR\ndoes não have o mídia substring.\nIf não, edit o environment CR com either de seguinte items e update o\nresourceNamePrefix in o primary section.\n■ Edit o environment CR usando seguinte comando e save:\nkubectl edit environments.netbackup.veritas.com\n -n \n■ Edit o environment CR YAML e apply o change usando seguinte\ncomando:\nkubectl apply -f " + "desc": "ResourceNamePrefix in spec of custom resource of the primary server must not contain the string media.", + "first_action": "Ensure that the resourceNamePrefix in primary section of environment CR", + "full_action": "Perform the following as appropriate:\n■ Ensure that the resourceNamePrefix in primary section of environment CR\ndoes not have the media substring.\nIf not, edit the environment CR with either of following items and update the\nresourceNamePrefix in the primary section.\n■ Edit the environment CR using following command and save:\nkubectl edit environments.netbackup.veritas.com\n -n \n■ Edit the environment CR YAML and apply the change using following\ncommand:\nkubectl apply -f " }, "8438": { "code": 8438, - "desc": "External IP está não assigned to service .", - "first_action": "Verifique o service events para um detailed message usando o seguinte comando:", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o service events para um detailed message usando o seguinte comando:\nkubectl describe -n \n■ TheresourcePrefixNameprovidedfortheprimaryandormediaserverssection\nin environment CR YAML must be unique. If it está não unique, update o\nrespective section in o YAML, excluir o environment CR, e apply it again.\n■ Verifique o provided IP address e hostname FQDN estão already created. Also,\nverifique que they correctly used if mentioned in o ipList under o\nnetworkLoadBalancer in o primary e o mídia servers section in o\nenvironment CR YAML. Para more details refer to o load balancer service\nsection in o NetBackup Deployment on Azure Kubernetes Cluster (AKS)\nAdministrator’s Guide.\n■ Verifique que RBAC permissions estão correct. Refer to o NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide." + "desc": "External IP is not assigned to service .", + "first_action": "Check the service events for a detailed message using the following command:", + "full_action": "Perform the following as appropriate:\n■ Check the service events for a detailed message using the following command:\nkubectl describe -n \n■ TheresourcePrefixNameprovidedfortheprimaryandormediaserverssection\nin environment CR YAML must be unique. If it is not unique, update the\nrespective section in the YAML, delete the environment CR, and apply it again.\n■ Verify the provided IP address and hostname FQDN are already created. Also,\nverify that they correctly used if mentioned in the ipList under the\nnetworkLoadBalancer in the primary and the media servers section in the\nenvironment CR YAML. For more details refer to the load balancer service\nsection in the NetBackup Deployment on Azure Kubernetes Cluster (AKS)\nAdministrator’s Guide.\n■ Verify that RBAC permissions are correct. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide." }, "8439": { "code": 8439, - "desc": "Erro in creating o Job in o namespace para o .", - "first_action": "Verifique o NetBackup operator logs para details usando o seguinte comando:", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o NetBackup operator logs para details usando o seguinte comando:\nkubectl logs netbackup-operator -n\n\n■ VerifythattheRBACpermissionsfortheJobarecorrect.RefertotheNetBackup\nDeployment on Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ If this issue happens com um fresh deployment, executar o seguinte:\n■ If o issue está o primaryServer CR, executar o seguinte:\nExcluir o environment CR usando o comando: kubectl excluir -f\n\nRedeploy o environment again usando o comando: kubectl apply -f\n\n■ If o issue está o mediaServer CR, excluir o CR por removing o\nmediaServers section in environment.yaml. Save o mediaServers data\nsomewheresothatitcanbeusedatthetimeofredeployment.Applychanges\nusando o comando: kubectl apply -f \nAfter deleting o mediaServer, update o environment.yaml com o\nmediaServers data que foi deleted earlier. Redeploy it again usando o\ncomando: kubectl apply -f " + "desc": "Error in creating the Job in the namespace for the .", + "first_action": "Check the NetBackup operator logs for details using the following command:", + "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs netbackup-operator -n\n\n■ VerifythattheRBACpermissionsfortheJobarecorrect.RefertotheNetBackup\nDeployment on Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ If this issue happens with a fresh deployment, perform the following:\n■ If the issue is the primaryServer CR, perform the following:\nDelete the environment CR using the command: kubectl delete -f\n\nRedeploy the environment again using the command: kubectl apply -f\n\n■ If the issue is the mediaServer CR, delete the CR by removing the\nmediaServers section in environment.yaml. Save the mediaServers data\nsomewheresothatitcanbeusedatthetimeofredeployment.Applychanges\nusing the command: kubectl apply -f \nAfter deleting the mediaServer, update the environment.yaml with the\nmediaServers data that was deleted earlier. Redeploy it again using the\ncommand: kubectl apply -f " }, "8440": { "code": 8440, - "desc": "Config-checker falhou, ou o configuration requirements foram não met. NetBackup status codes 1019 NetBackup status codes", - "first_action": "Verifique o NetBackup operator logs para details usando o seguinte comando:", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o NetBackup operator logs para details usando o seguinte comando:\nkubectl logs netbackup-operator -n\n\n■ Iftheconfigurationchecksfailed,fixthecheckswithavalidresolution.Forother\nConfig-checkerdetails,refertotheNetBackupDeploymentonAzureKubernetes\nCluster (AKS) Administrator’s Guide." + "desc": "Config-checker failed, or the configuration requirements were not met. NetBackup status codes 1019 NetBackup status codes", + "first_action": "Check the NetBackup operator logs for details using the following command:", + "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs netbackup-operator -n\n\n■ Iftheconfigurationchecksfailed,fixthecheckswithavalidresolution.Forother\nConfig-checkerdetails,refertotheNetBackupDeploymentonAzureKubernetes\nCluster (AKS) Administrator’s Guide." }, "8441": { "code": 8441, - "desc": "Falhou to get Config-checker logs.", - "first_action": "Verifique o NetBackup operator logs para details usando o seguinte comando:", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o NetBackup operator logs para details usando o seguinte comando:\nkubectl logs netbackup-operator -n\n\n■ ChecktheConfig-checkerpodlogsformoredetailedmessageusingthefollowing\ncomando:\nkubectl logs -n " + "desc": "Failed to get Config-checker logs.", + "first_action": "Check the NetBackup operator logs for details using the following command:", + "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs netbackup-operator -n\n\n■ ChecktheConfig-checkerpodlogsformoredetailedmessageusingthefollowing\ncommand:\nkubectl logs -n " }, "8442": { "code": 8442, - "desc": "Config-checker excedido o time-out limite.", - "first_action": "Verifique o NetBackup operator logs para details usando o seguinte comando:", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o NetBackup operator logs para details usando o seguinte comando:\nkubectl logs netbackup-operator -n\n\n■ Garanta que o nodes estão disponível to schedule o pod in o cluster com\nrespective labels.\n■ Verifique events de o config-checker pod usando o seguinte comando:\nkubectl describe -n " + "desc": "Config-checker exceeded the time-out limit.", + "first_action": "Check the NetBackup operator logs for details using the following command:", + "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs netbackup-operator -n\n\n■ Ensure that the nodes are available to schedule the pod in the cluster with\nrespective labels.\n■ Check events of the config-checker pod using the following command:\nkubectl describe -n " }, "8443": { "code": 8443, - "desc": "Incorrect username ou password in o secret in namespace .", - "first_action": "Garanta que o username e password que está defined", - "full_action": "Garanta que o username e password que está defined\nin o secret e used in o PrimaryServer CR estão same como o secret used in\no MediaServer CR." + "desc": "Incorrect username or password in the secret in namespace .", + "first_action": "Ensure that the username and password that is defined", + "full_action": "Ensure that the username and password that is defined\nin the secret and used in the PrimaryServer CR are same as the secret used in\nthe MediaServer CR." }, "8444": { "code": 8444, - "desc": "Erro in creating o role in o namespace .", - "first_action": "Verifique o NetBackup operator logs para details usando o seguinte comando:", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o NetBackup operator logs para details usando o seguinte comando:\nkubectl logs netbackup-operator -n\n\n■ Verifique que RBAC permissions estão correct. Refer to o NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Verifique o Kubernetes documentation para role documentation: Usando RBAC\nAuthorization | Kubernetes" + "desc": "Error in creating the role in the namespace .", + "first_action": "Check the NetBackup operator logs for details using the following command:", + "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs netbackup-operator -n\n\n■ Verify that RBAC permissions are correct. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check the Kubernetes documentation for role documentation: Using RBAC\nAuthorization | Kubernetes" }, "8445": { "code": 8445, - "desc": "Erro in retrieving o role in o namespace .", - "first_action": "Verifique o NetBackup operator logs para details usando o seguinte comando:", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o NetBackup operator logs para details usando o seguinte comando:\nkubectl logs netbackup-operator -n\n\n■ Verifique que RBAC permissions estão correct. Refer to o NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Verifique if role está disponível in given namespace usando o seguinte comando:\nkubectl get role -n \n■ Verifique o Kubernetes documentation para role documentation: Usando RBAC\nAuthorization | Kubernetes" + "desc": "Error in retrieving the role in the namespace .", + "first_action": "Check the NetBackup operator logs for details using the following command:", + "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs netbackup-operator -n\n\n■ Verify that RBAC permissions are correct. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check if role is available in given namespace using the following command:\nkubectl get role -n \n■ Check the Kubernetes documentation for role documentation: Using RBAC\nAuthorization | Kubernetes" }, "8446": { "code": 8446, - "desc": "Inválido format para static IP address provided in custom resource specification.", - "first_action": "Garanta que o format de IP addresses specified in o primaryServers ou", - "full_action": "Executar o seguinte como appropriate:\n■ Garanta que o format de IP addresses specified in o primaryServers ou\nmediaServers section in environment CR estão valid.\n■ If o format de o IP addresses está não correct, edit o environment CR com\neither de seguinte steps e update o IP address format in o respective\nsections.\n■ Edit environment CR usando o seguinte comando e save:\nkubectl edit environments.netbackup.veritas.com\n -n \n■ EdittheenvironmentCRYAMLandapplythechangeusingthefollowing\ncomando:\nkubectl apply -f " + "desc": "Invalid format for static IP address provided in custom resource specification.", + "first_action": "Ensure that the format of IP addresses specified in the primaryServers or", + "full_action": "Perform the following as appropriate:\n■ Ensure that the format of IP addresses specified in the primaryServers or\nmediaServers section in environment CR are valid.\n■ If the format of the IP addresses is not correct, edit the environment CR with\neither of following steps and update the IP address format in the respective\nsections.\n■ Edit environment CR using the following command and save:\nkubectl edit environments.netbackup.veritas.com\n -n \n■ EdittheenvironmentCRYAMLandapplythechangeusingthefollowing\ncommand:\nkubectl apply -f " }, "8453": { "code": 8453, - "desc": "Erro in creating o job in o namespace para o .", - "first_action": "Review o NetBackup operator logs para details usando o seguinte comando:", - "full_action": "Executar o seguinte como appropriate:\n■ Review o NetBackup operator logs para details usando o seguinte comando:\nkubectl logs netbackup-operator\n-n\n■ VerifythattheRBACpermissionsforthejobarecorrect.RefertotheNetBackup\nDeployment para Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ If o issue está com o primary servidor CR, executar o seguinte:\n■ Excluir o environment CR usando o comando: kubectl excluir -f\n\n■ Redeploy o environment again usando o comando: kubectl apply -f\n\n■ If this issue occurs during data migration, executar o seguinte:\n■ Verifique o migration pod logs para details usando o seguinte comando:\nkubectl logs -n\n\n■ If o NetBackup operator pod has one de o seguinte messages:\nErro while getting PVC para renaming.\nErro while deleting old PVC.\nErro while patching old PVC.\nErro while renaming logs PVC.\nErro while renaming catalog PVC.\nExecutar o seguinte steps:\n■ Manually copy ou ignore o arquivos ou continue com o next steps.\n■ Save o PVC’s volume name e armazenamento class como follows:\nkubectl describe pvc \n-n \n■ Excluir o old Azure disco ou arquivos PVC, e rename o new Azure arquivos\nPVC to o old Azure disco ou arquivos PVC name como follows:\nkubectl excluir pvc \n-n \nkubectl patch pv --type json\n-p '[{\"op\": \"remove\", \"caminho\": \"/spec/claimRef\"}]'\n■ Garanta que o PV está disponível after completing o previous steps.\n■ Create um new Azure arquivos PVC com o old PV como follows:\napiVersion: v1\nkind: PersistentVolumeClaim\nmetadata:\nname: \nnamespace: \nspec:\naccessModes:\n- ReadWriteMany\nvolumeName: \nstorageClassName: \nresources:\nrequests:\narmazenamento: 100Gi #previous arquivos size\n■ Enable o probes /opt/veritas/vxapp-manage/nb-health enable.\n■ Set replica count to 1 ou reapply environment.yaml arquivo como follows:\nkubectl scale --replicas=1 -n\norreapplytheenvironment.yaml\narquivo." + "desc": "Error in creating the job in the namespace for the .", + "first_action": "Review the NetBackup operator logs for details using the following command:", + "full_action": "Perform the following as appropriate:\n■ Review the NetBackup operator logs for details using the following command:\nkubectl logs netbackup-operator\n-n\n■ VerifythattheRBACpermissionsforthejobarecorrect.RefertotheNetBackup\nDeployment for Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ If the issue is with the primary server CR, perform the following:\n■ Delete the environment CR using the command: kubectl delete -f\n\n■ Redeploy the environment again using the command: kubectl apply -f\n\n■ If this issue occurs during data migration, perform the following:\n■ Check the migration pod logs for details using the following command:\nkubectl logs -n\n\n■ If the NetBackup operator pod has one of the following messages:\nError while getting PVC for renaming.\nError while deleting old PVC.\nError while patching old PVC.\nError while renaming logs PVC.\nError while renaming catalog PVC.\nPerform the following steps:\n■ Manually copy or ignore the files or continue with the next steps.\n■ Save the PVC’s volume name and storage class as follows:\nkubectl describe pvc \n-n \n■ Delete the old Azure disk or files PVC, and rename the new Azure files\nPVC to the old Azure disk or files PVC name as follows:\nkubectl delete pvc \n-n \nkubectl patch pv --type json\n-p '[{\"op\": \"remove\", \"path\": \"/spec/claimRef\"}]'\n■ Ensure that the PV is available after completing the previous steps.\n■ Create a new Azure files PVC with the old PV as follows:\napiVersion: v1\nkind: PersistentVolumeClaim\nmetadata:\nname: \nnamespace: \nspec:\naccessModes:\n- ReadWriteMany\nvolumeName: \nstorageClassName: \nresources:\nrequests:\nstorage: 100Gi #previous files size\n■ Enable the probes /opt/veritas/vxapp-manage/nb-health enable.\n■ Set replica count to 1 or reapply environment.yaml file as follows:\nkubectl scale --replicas=1 -n\norreapplytheenvironment.yaml\nfile." }, "8454": { "code": 8454, - "desc": "Migration falhou ou o configuration requirements foram não met.", - "first_action": "Verifique o NetBackup operator logs para details usando o seguinte comando:", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o NetBackup operator logs para details usando o seguinte comando:\nkubectl logs netbackup-operator -n\n\n■ Excluir o new PVC com o Azure arquivos created during falhou data migration\nusando o seguinte comando:\nkubectl excluir pvc -n \nReapply o environment.yaml arquivo to reinitiate o data migration. Para other\nmigrationdetails,refertotheNetBackupDeploymentforAzureKubernetesCluster\n(AKS) Administrator’s Guide." + "desc": "Migration failed or the configuration requirements were not met.", + "first_action": "Check the NetBackup operator logs for details using the following command:", + "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs netbackup-operator -n\n\n■ Delete the new PVC with the Azure files created during failed data migration\nusing the following command:\nkubectl delete pvc -n \nReapply the environment.yaml file to reinitiate the data migration. For other\nmigrationdetails,refertotheNetBackupDeploymentforAzureKubernetesCluster\n(AKS) Administrator’s Guide." }, "8455": { "code": 8455, - "desc": "Falhou to get migration logs.", - "first_action": "Review o NetBackup operator logs para details usando o seguinte comando:", - "full_action": "Executar o seguinte como appropriate:\n■ Review o NetBackup operator logs para details usando o seguinte comando:\nkubectl logs netbackup-operator -n\n\n■ Review o migration pod logs para more detailed message usando o seguinte\ncomando:\nkubectl logs -n " + "desc": "Failed to get migration logs.", + "first_action": "Review the NetBackup operator logs for details using the following command:", + "full_action": "Perform the following as appropriate:\n■ Review the NetBackup operator logs for details using the following command:\nkubectl logs netbackup-operator -n\n\n■ Review the migration pod logs for more detailed message using the following\ncommand:\nkubectl logs -n " }, "8456": { "code": 8456, - "desc": "Migration excedido o time-out limite. NetBackup status codes 1025 NetBackup status codes", - "first_action": "Verifique o NetBackup operator logs para details usando o seguinte comando:", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o NetBackup operator logs para details usando o seguinte comando:\nkubectl logs netbackup-operator -n\n\n■ Garanta que o nodes estão disponível to schedule o pod in o cluster com\nrespective labels.\n■ Review o events de o migration pod usando o seguinte comando:\nkubectl describe -n \n■ Excluir o new PVC com o Azure arquivos que o falhou data migration creates\nusando o seguinte comando:\nkubectl excluir pvc -n \nReapply o environment.yaml arquivo to reinitiate o data migration. Para other\nmigrationdetails,refertotheNetBackupDeploymentforAzureKubernetesCluster\n(AKS) Administrator’s Guide." + "desc": "Migration exceeded the time-out limit. NetBackup status codes 1025 NetBackup status codes", + "first_action": "Check the NetBackup operator logs for details using the following command:", + "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs netbackup-operator -n\n\n■ Ensure that the nodes are available to schedule the pod in the cluster with\nrespective labels.\n■ Review the events of the migration pod using the following command:\nkubectl describe -n \n■ Delete the new PVC with the Azure files that the failed data migration creates\nusing the following command:\nkubectl delete pvc -n \nReapply the environment.yaml file to reinitiate the data migration. For other\nmigrationdetails,refertotheNetBackupDeploymentforAzureKubernetesCluster\n(AKS) Administrator’s Guide." }, "8459": { "code": 8459, - "desc": "MigrationStatus: Transfer Falhou.", - "first_action": "Verifique o migration pod logs para details usando o seguinte comando:", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o migration pod logs para details usando o seguinte comando:\nkubectl logs -n\n\n■ Manually copy ou ignore o arquivos ou continue com o next steps.\n■ Save o PVC’s volume name e armazenamento class como follows:\nkubectl describe pvc \n-n \n■ Excluir o old Azure disco ou arquivos PVC, e rename o new Azure arquivos PVC to\no old Azure disco ou arquivos PVC name como follows:\nkubectl excluir pvc \n-n \nkubectl patch pv --type json\n-p '[{\"op\": \"remove\", \"caminho\": \"/spec/claimRef\"}]'\n■ Garanta que o PV está disponível after completing o previous steps.\n■ Create um new Azure arquivos PVC com o old PV como follows:\napiVersion: v1\nkind: PersistentVolumeClaim\nmetadata:\nname: \nnamespace: \nspec:\naccessModes:\n- ReadWriteMany\nvolumeName: \nstorageClassName: \nresources:\nrequests:\narmazenamento: 100Gi #previous arquivos size\n■ Enable o probes /opt/veritas/vxapp-manage/nb-health enable.\n■ Set replica count to 1 ou reapply environment.yaml arquivo como follows:\nkubectl scale --replicas=1 -n\n ou reapply o environment.yaml arquivo." + "desc": "MigrationStatus: Transfer Failed.", + "first_action": "Check the migration pod logs for details using the following command:", + "full_action": "Perform the following as appropriate:\n■ Check the migration pod logs for details using the following command:\nkubectl logs -n\n\n■ Manually copy or ignore the files or continue with the next steps.\n■ Save the PVC’s volume name and storage class as follows:\nkubectl describe pvc \n-n \n■ Delete the old Azure disk or files PVC, and rename the new Azure files PVC to\nthe old Azure disk or files PVC name as follows:\nkubectl delete pvc \n-n \nkubectl patch pv --type json\n-p '[{\"op\": \"remove\", \"path\": \"/spec/claimRef\"}]'\n■ Ensure that the PV is available after completing the previous steps.\n■ Create a new Azure files PVC with the old PV as follows:\napiVersion: v1\nkind: PersistentVolumeClaim\nmetadata:\nname: \nnamespace: \nspec:\naccessModes:\n- ReadWriteMany\nvolumeName: \nstorageClassName: \nresources:\nrequests:\nstorage: 100Gi #previous files size\n■ Enable the probes /opt/veritas/vxapp-manage/nb-health enable.\n■ Set replica count to 1 or reapply environment.yaml file as follows:\nkubectl scale --replicas=1 -n\n or reapply the environment.yaml file." }, "8460": { "code": 8460, - "desc": "MigrationStatus: Verification Falhou", - "first_action": "Verifique o migration pod logs para details usando o seguinte comando:", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o migration pod logs para details usando o seguinte comando:\nkubectl logs -n\n\n■ Manually copy ou ignore o arquivos ou continue com o next steps.\n■ Save o PVC’s volume name e armazenamento class como follows:\nkubectl describe pvc \n-n \n■ Excluir o old Azure disco ou arquivos PVC, e rename o new Azure arquivos PVC to\no old Azure disco ou arquivos PVC name como follows:\nkubectl excluir pvc \n-n \nkubectl patch pv --type json\n-p '[{\"op\": \"remove\", \"caminho\": \"/spec/claimRef\"}]'\n■ Garanta que o PV está disponível after completing o previous steps.\n■ Create um new Azure arquivos PVC com o old PV como follows:\napiVersion: v1\nkind: PersistentVolumeClaim\nmetadata:\nname: \nnamespace: \nspec:\naccessModes:\n- ReadWriteMany\nvolumeName: \nstorageClassName: \nresources:\nrequests:\narmazenamento: 100Gi #previous arquivos size\n■ Enable o probes /opt/veritas/vxapp-manage/nb-health enable.\n■ Set replica count to 1 ou reapply environment.yaml arquivo como follows:\nkubectl scale --replicas=1 -n\n ou reapply o environment.yaml arquivo." + "desc": "MigrationStatus: Verification Failed", + "first_action": "Check the migration pod logs for details using the following command:", + "full_action": "Perform the following as appropriate:\n■ Check the migration pod logs for details using the following command:\nkubectl logs -n\n\n■ Manually copy or ignore the files or continue with the next steps.\n■ Save the PVC’s volume name and storage class as follows:\nkubectl describe pvc \n-n \n■ Delete the old Azure disk or files PVC, and rename the new Azure files PVC to\nthe old Azure disk or files PVC name as follows:\nkubectl delete pvc \n-n \nkubectl patch pv --type json\n-p '[{\"op\": \"remove\", \"path\": \"/spec/claimRef\"}]'\n■ Ensure that the PV is available after completing the previous steps.\n■ Create a new Azure files PVC with the old PV as follows:\napiVersion: v1\nkind: PersistentVolumeClaim\nmetadata:\nname: \nnamespace: \nspec:\naccessModes:\n- ReadWriteMany\nvolumeName: \nstorageClassName: \nresources:\nrequests:\nstorage: 100Gi #previous files size\n■ Enable the probes /opt/veritas/vxapp-manage/nb-health enable.\n■ Set replica count to 1 or reapply environment.yaml file as follows:\nkubectl scale --replicas=1 -n\n or reapply the environment.yaml file." }, "8469": { "code": 8469, - "desc": "Erro in renaming o PVC to in o namespace .", - "first_action": "Verifique o NetBackup operator logs para details usando o seguinte comando:", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o NetBackup operator logs para details usando o seguinte comando:\nkubectl logs netbackup-operator -n\n\n■ Verifique if o storageClassName provided in CR está disponível in o cluster usando\nseguinte comando:\nkubectl get storageclass\n■ Verifique que RBAC permissions estão correct. Refer to o NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Verifique o Kubernetes documentation para PVC details.\n■ Manually rename usando o seguinte steps:\n■ Save o PVC’s volume name e armazenamento class como follows:\nkubectl describe pvc \n-n < netbackup-environment-namespace >\n■ Excluir o old Azure disco ou arquivos PVC:\nkubectl excluir pvc \n-n \nkubectl patch pv --type json\n-p '[{\"op\": \"remove\", \"caminho\": \"/spec/claimRef\"}]'\n■ Garanta que o PV está disponível after completing o previous steps.\n■ Create um new Azure arquivos PVC com o old PV como follows:\napiVersion: v1\nkind: PersistentVolumeClaim\nmetadata:\nname: \nnamespace: \nspec:\naccessModes:\n- ReadWriteMany\nvolumeName: \nstorageClassName: \nresources:\nrequests:\narmazenamento: 100Gi #previous arquivos size\n■ Enable o probes /opt/veritas/vxapp-manage/nb-health enable.\n■ Set replica count to 1 ou reapply environment.yaml arquivo como follows:\nkubectl scale --replicas=1 -n\n ou reapply o environment.yaml\narquivo." + "desc": "Error in renaming the PVC to in the namespace .", + "first_action": "Check the NetBackup operator logs for details using the following command:", + "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs netbackup-operator -n\n\n■ Check if the storageClassName provided in CR is available in the cluster using\nfollowing command:\nkubectl get storageclass\n■ Verify that RBAC permissions are correct. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check the Kubernetes documentation for PVC details.\n■ Manually rename using the following steps:\n■ Save the PVC’s volume name and storage class as follows:\nkubectl describe pvc \n-n < netbackup-environment-namespace >\n■ Delete the old Azure disk or files PVC:\nkubectl delete pvc \n-n \nkubectl patch pv --type json\n-p '[{\"op\": \"remove\", \"path\": \"/spec/claimRef\"}]'\n■ Ensure that the PV is available after completing the previous steps.\n■ Create a new Azure files PVC with the old PV as follows:\napiVersion: v1\nkind: PersistentVolumeClaim\nmetadata:\nname: \nnamespace: \nspec:\naccessModes:\n- ReadWriteMany\nvolumeName: \nstorageClassName: \nresources:\nrequests:\nstorage: 100Gi #previous files size\n■ Enable the probes /opt/veritas/vxapp-manage/nb-health enable.\n■ Set replica count to 1 or reapply environment.yaml file as follows:\nkubectl scale --replicas=1 -n\n or reapply the environment.yaml\nfile." }, "8500": { "code": 8500, - "desc": "Conexão com o web service foi não established", - "first_action": "Verifique que o NetBackup Web Management Console está", - "full_action": "Verifique que o NetBackup Web Management Console está\nup e executando. If it está não executando, start it com o nbwmc -start comando." + "desc": "Connection with the web service was not established", + "first_action": "Check that the NetBackup Web Management Console is", + "full_action": "Check that the NetBackup Web Management Console is\nup and running. If it is not running, start it with the nbwmc -start command." }, "8503": { "code": 8503, - "desc": "CURL has returned um unknown erro.", - "first_action": "Para more informação about this erro code, review o", - "full_action": "Para more informação about this erro code, review o\nfollowingtechnicalarticle:https://www.veritas.com/support/en_US/article.100034053" + "desc": "CURL has returned an unknown error.", + "first_action": "For more information about this error code, review the", + "full_action": "For more information about this error code, review the\nfollowingtechnicalarticle:https://www.veritas.com/support/en_US/article.100034053" }, "8504": { "code": 8504, "desc": "ThewebservicecertificateisissuedbyanunknownCertificateAuthority.", - "first_action": "Fetch o CA certificate para o requerido servidor e rerun o operation.", - "full_action": "Do one de o seguinte:\n■ Fetch o CA certificate para o requerido servidor e rerun o operation.\n■ Garanta que o master servidor está enabled to use um NetBackup CA-signed\ncertificate ou um external CA-signed certificate, whichever está applicable.\nIf o problema continues, save todos de o erro log informação e contate Cohesity\nTechnical Support." + "first_action": "Fetch the CA certificate for the required server and rerun the operation.", + "full_action": "Do one of the following:\n■ Fetch the CA certificate for the required server and rerun the operation.\n■ Ensure that the master server is enabled to use a NetBackup CA-signed\ncertificate or an external CA-signed certificate, whichever is applicable.\nIf the problem continues, save all of the error log information and contact Cohesity\nTechnical Support." }, "8505": { "code": 8505, "desc": "Ensurethatthehostclockandthemasterserverclockaresynchronized.", - "first_action": "Verifique if o host’s clock está in sync com o specified", - "full_action": "Verifique if o host’s clock está in sync com o specified\nservidor. Correct o time on o host, if necessary, e rerun o operation. If o\nproblema continues, save todos de o erro log informação e contate Cohesity\nTechnical Support." + "first_action": "Check if the host’s clock is in sync with the specified", + "full_action": "Check if the host’s clock is in sync with the specified\nserver. Correct the time on the host, if necessary, and rerun the operation. If the\nproblem continues, save all of the error log information and contact Cohesity\nTechnical Support." }, "8506": { "code": 8506, - "desc": "O certificate has expired.", + "desc": "The certificate has expired.", "first_action": "Checkifthehost'sclockisinsyncwiththespecifiedserver.", - "full_action": "Checkifthehost'sclockisinsyncwiththespecifiedserver.\nCorrect o time on o host, if necessary, e rerun o operation. If o problema\ncontinues, save todos de o erro log informação e contate Cohesity Technical\nSupport." + "full_action": "Checkifthehost'sclockisinsyncwiththespecifiedserver.\nCorrect the time on the host, if necessary, and rerun the operation. If the problem\ncontinues, save all of the error log information and contact Cohesity Technical\nSupport." }, "8507": { "code": 8507, - "desc": "O certificate could não be verified.", - "first_action": "Rerun o operation. If o problema persists, save todos de", - "full_action": "Rerun o operation. If o problema persists, save todos de\no erro log informação e contate Cohesity Technical Support." + "desc": "The certificate could not be verified.", + "first_action": "Rerun the operation. If the problem persists, save all of", + "full_action": "Rerun the operation. If the problem persists, save all of\nthe error log information and contact Cohesity Technical Support." }, "8508": { "code": 8508, - "desc": "List de trusted Certificate Authorities não é possível be fetched. NetBackup status codes 1031 NetBackup status codes", - "first_action": "Use o nbcertcmd -listCACertDetails comando to verifique que o CA", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Use o nbcertcmd -listCACertDetails comando to verifique que o CA\ncertificate está added to o trust store. Run o nbcertcmd -getCACertificate\n-servidor master_server_name comando to add o requerido certificate to o\ntrust store.\n■ Para RHV:\n■ When o VIRTUALIZATION_HOSTS_SECURE_CONNECT_ENABLED option está\nenabled, you must verifique o placement de o certificates e CRLs. Verifique\nwhether o RHV virtualization server’s certificates e CRLs estão added to\no respective ECA configurado trust store e o CRL caminho.\n■ Garanta que o certificates e o CRL arquivos estão in o correct format e\no trust store arquivo e o CRL arquivos estão não corrupted.\n■ Apenas PEM certificate format para file-based trust store & Windows trust store\nestão supported para virtualization servers. P7b ou DER format arquivo based trust\nstore está não supported. When this recurso está enabled, o certificate ECA\nstore should either be Windows certificate store ou arquivo based PEM format\nstore." + "desc": "List of trusted Certificate Authorities cannot be fetched. NetBackup status codes 1031 NetBackup status codes", + "first_action": "Use the nbcertcmd -listCACertDetails command to verify that the CA", + "full_action": "Do the following, as appropriate:\n■ Use the nbcertcmd -listCACertDetails command to verify that the CA\ncertificate is added to the trust store. Run the nbcertcmd -getCACertificate\n-server master_server_name command to add the required certificate to the\ntrust store.\n■ For RHV:\n■ When the VIRTUALIZATION_HOSTS_SECURE_CONNECT_ENABLED option is\nenabled, you must verify the placement of the certificates and CRLs. Verify\nwhether the RHV virtualization server’s certificates and CRLs are added to\nthe respective ECA configured trust store and the CRL path.\n■ Ensure that the certificates and the CRL files are in the correct format and\nthe trust store file and the CRL files are not corrupted.\n■ Only PEM certificate format for file-based trust store & Windows trust store\nare supported for virtualization servers. P7b or DER format file based trust\nstore is not supported. When this feature is enabled, the certificate ECA\nstore should either be Windows certificate store or file based PEM format\nstore." }, "8509": { "code": 8509, - "desc": "O specified servidor name foi não found in o web service certificate.", - "first_action": "Rerun o operation usando one de o names listed in o", - "full_action": "Rerun o operation usando one de o names listed in o\nserver’s certificate." + "desc": "The specified server name was not found in the web service certificate.", + "first_action": "Rerun the operation using one of the names listed in the", + "full_action": "Rerun the operation using one of the names listed in the\nserver’s certificate." }, "8510": { "code": 8510, - "desc": "Web servidor certificate verification falhou. NetBackup status codes 1032 NetBackup status codes", - "first_action": "Rerun o operation. If o problema persists, save todos de", - "full_action": "Rerun o operation. If o problema persists, save todos de\no erro log informação e contate Cohesity Technical Support." + "desc": "Web server certificate verification failed. NetBackup status codes 1032 NetBackup status codes", + "first_action": "Rerun the operation. If the problem persists, save all of", + "full_action": "Rerun the operation. If the problem persists, save all of\nthe error log information and contact Cohesity Technical Support." }, "8511": { "code": 8511, - "desc": "Falhou to load o local certificate ou o keystore.", + "desc": "Failed to load the local certificate or the keystore.", "first_action": "Ensurethatthecertificateandthekeystoreareaccessible", - "full_action": "Ensurethatthecertificateandthekeystoreareaccessible\ne que their paths estão correct." + "full_action": "Ensurethatthecertificateandthekeystoreareaccessible\nand that their paths are correct." }, "8512": { "code": 8512, - "desc": "Falhou to retrieve o certificate informação.", - "first_action": "Garanta que o specified certificate trust store arquivo está in", - "full_action": "Garanta que o specified certificate trust store arquivo está in\no correct format e o requerido host certificates estão present in o arquivo." + "desc": "Failed to retrieve the certificate information.", + "first_action": "Ensure that the specified certificate trust store file is in", + "full_action": "Ensure that the specified certificate trust store file is in\nthe correct format and the required host certificates are present in the file." }, "8516": { "code": 8516, - "desc": "SSL handshake erro has ocorreu.", - "first_action": "Garanta que o cipher que está configurado on o remote", - "full_action": "Garanta que o cipher que está configurado on o remote\nhost está present in o cipher list on o host. Also garanta que o remote host\nsupports o TLS version being used." + "desc": "SSL handshake error has occurred.", + "first_action": "Ensure that the cipher that is configured on the remote", + "full_action": "Ensure that the cipher that is configured on the remote\nhost is present in the cipher list on the host. Also ensure that the remote host\nsupports the TLS version being used." }, "8517": { "code": 8517, - "desc": "O specified SSL cipher não é possível be used.", + "desc": "The specified SSL cipher cannot be used.", "first_action": "Ensurethatthecipherthatisconfiguredonthevirtualization", - "full_action": "Ensurethatthecipherthatisconfiguredonthevirtualization\nservidor está present in o cipher list on o host. Also garanta que o specified cipher\nlist está in o correct format." + "full_action": "Ensurethatthecipherthatisconfiguredonthevirtualization\nserver is present in the cipher list on the host. Also ensure that the specified cipher\nlist is in the correct format." }, "8604": { "code": 8604, - "desc": "Não foi possível to validate o certificate para host.", + "desc": "Unable to validate the certificate for host.", "first_action": "WhentheVIRTUALIZATION_HOSTS_SECURE_CONNECT_ENABLEDoptionisenabled,", - "full_action": "Execute os seguintes passos conforme apropriado:\nPara RHV:\n■ WhentheVIRTUALIZATION_HOSTS_SECURE_CONNECT_ENABLEDoptionisenabled,\nyou must verifique o placement de o certificates e CRLs. Verifique whether o\nRHV virtualization server’s certificates e CRLs estão added to o respective\nECA configurado trust store e o CRL caminho.\n■ Garanta que o certificates e o CRL arquivos estão in o correct format e o\ntrust store arquivo e o CRL arquivos estão não corrupted.\n■ Apenas o PEM certificate format para um file-based trust store e Windows trust\nstore está supported para virtualization servers. P7b ou DER format file-based trust\nstore está não supported. When this recurso está enabled, o certificate ECA store\nshould either be Windows certificate store ou file-based PEM format store.\nPara Sheltered Harbor solution:\n■ Verifique que o correct CA certificate arquivo está provided in o Sheltered Harbor\nsolution configuration. You can verifique o configuration de o Sheltered Harbor\nsolution usando o seguinte comando:\nOn UNIX:\n/usr/openv/netbackup/bin/nbshvault --show-config\nOn Windows:\ninstall_path\\NetBackup\\bin\\nbshvault --show-config" + "full_action": "Do the following, as appropriate:\nFor RHV:\n■ WhentheVIRTUALIZATION_HOSTS_SECURE_CONNECT_ENABLEDoptionisenabled,\nyou must verify the placement of the certificates and CRLs. Verify whether the\nRHV virtualization server’s certificates and CRLs are added to the respective\nECA configured trust store and the CRL path.\n■ Ensure that the certificates and the CRL files are in the correct format and the\ntrust store file and the CRL files are not corrupted.\n■ Only the PEM certificate format for a file-based trust store and Windows trust\nstore is supported for virtualization servers. P7b or DER format file-based trust\nstore is not supported. When this feature is enabled, the certificate ECA store\nshould either be Windows certificate store or file-based PEM format store.\nFor Sheltered Harbor solution:\n■ Verify that the correct CA certificate file is provided in the Sheltered Harbor\nsolution configuration. You can verify the configuration of the Sheltered Harbor\nsolution using the following command:\nOn UNIX:\n/usr/openv/netbackup/bin/nbshvault --show-config\nOn Windows:\ninstall_path\\NetBackup\\bin\\nbshvault --show-config" }, "8611": { "code": 8611, - "desc": "Falhou to abrir o conexão to o remote object que está referred to por o URI.", - "first_action": "Verifique if o host name ou o port está valid so que o", - "full_action": "Verifique if o host name ou o port está valid so que o\nconexão com o servidor can be established. Also, make sure if o servidor está\nreachable." + "desc": "Failed to open the connection to the remote object that is referred to by the URI.", + "first_action": "Verify if the host name or the port is valid so that the", + "full_action": "Verify if the host name or the port is valid so that the\nconnection with the server can be established. Also, make sure if the server is\nreachable." }, "8617": { "code": 8617, - "desc": "O conexão continues because insecure communication com hosts está allowed.", + "desc": "The connection continues because insecure communication with hosts is allowed.", "first_action": "8.0, so it can communicate securely.", "full_action": "UpgradethehosttoaNetBackupversionthatislaterthan\n8.0, so it can communicate securely." }, "8618": { "code": 8618, - "desc": "O conexão está dropped because o host ID-to-host name mapping está não approved.", - "first_action": "O NetBackup administrator must approve todos relevant", - "full_action": "O NetBackup administrator must approve todos relevant\nhost ID-to-host name mappings para o given host." + "desc": "The connection is dropped because the host ID-to-host name mapping is not approved.", + "first_action": "The NetBackup administrator must approve all relevant", + "full_action": "The NetBackup administrator must approve all relevant\nhost ID-to-host name mappings for the given host." }, "8619": { "code": 8619, - "desc": "O conexão continues como o host ID-to-host name mapping está automatically approved.", - "first_action": "Não ação está requerido.", - "full_action": "Não ação está requerido." + "desc": "The connection continues as the host ID-to-host name mapping is automatically approved.", + "first_action": "No action is required.", + "full_action": "No action is required." }, "8620": { "code": 8620, - "desc": "O conexão está dropped because insecure communication com hosts está não allowed.", + "desc": "The connection is dropped because insecure communication with hosts is not allowed.", "first_action": "8.0, so it can communicate securely.", "full_action": "UpgradethehosttoaNetBackupversionthatislaterthan\n8.0, so it can communicate securely." }, "8621": { "code": 8621, - "desc": "O conexão está dropped because o host appears to be NetBackup 8.0 ou earlier.", - "first_action": "Verifique que o peer host foi upgraded e then", - "full_action": "Verifique que o peer host foi upgraded e then\ndowngraded to um back-level release. If this está o case, then o NetBackup\nadministrator can mark o given host como insecure.\nIf this está não o case, then another host está trying to spoof o peer host. You can\nuse o rede tools to find fora which host it está e take corrective ação." + "desc": "The connection is dropped because the host appears to be NetBackup 8.0 or earlier.", + "first_action": "Verify that the peer host was upgraded and then", + "full_action": "Verify that the peer host was upgraded and then\ndowngraded to a back-level release. If this is the case, then the NetBackup\nadministrator can mark the given host as insecure.\nIf this is not the case, then another host is trying to spoof the peer host. You can\nuse the network tools to find out which host it is and take corrective action." }, "8622": { "code": 8622, - "desc": "TheconnectionisdroppedbecauseaconflictinthehostID-to-hostname mapping está detected.", - "first_action": "If there estão multiple host IDs in seu environment que estão", - "full_action": "If there estão multiple host IDs in seu environment que estão\nassociated com o same host name, o NetBackup administrator should verifique\ne approve o mapping.\nIf um unknown host tries to spoof o peer host, you can use o disponível rede\ntools to find fora which host it está e take corrective ação." + "desc": "TheconnectionisdroppedbecauseaconflictinthehostID-to-hostname mapping is detected.", + "first_action": "If there are multiple host IDs in your environment that are", + "full_action": "If there are multiple host IDs in your environment that are\nassociated with the same host name, the NetBackup administrator should verify\nand approve the mapping.\nIf an unknown host tries to spoof the peer host, you can use the available network\ntools to find out which host it is and take corrective action." }, "8623": { "code": 8623, - "desc": "Falhou to determinar o conexão type de o host.", - "first_action": "Contate Cohesity Technical Support para assistance.", - "full_action": "Contate Cohesity Technical Support para assistance." + "desc": "Failed to determine the connection type of the host.", + "first_action": "Contact Cohesity Technical Support for assistance.", + "full_action": "Contact Cohesity Technical Support for assistance." }, "8625": { "code": 8625, - "desc": "Servidor está unavailable to process o request. Por favor try later.", - "first_action": "Garanta que o NetBackup services estão up e executando correctly.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Garanta que o NetBackup services estão up e executando correctly.\n■ If o relevant NetBackup services estão up e you still receive this erro code,\nthenthewebserverisunderaheavyload.Retrytheoperationinafewseconds." + "desc": "Server is unavailable to process the request. Please try later.", + "first_action": "Ensure that the NetBackup services are up and running correctly.", + "full_action": "Do the following, as appropriate:\n■ Ensure that the NetBackup services are up and running correctly.\n■ If the relevant NetBackup services are up and you still receive this error code,\nthenthewebserverisunderaheavyload.Retrytheoperationinafewseconds." }, "8629": { "code": 8629, - "desc": "O NetBackup deduplication web server's SSL certificate hash entry foi não found in o NetBackup configuration banco de dados.", - "first_action": "Follow o troubleshooting steps to install o SSL", - "full_action": "Follow o troubleshooting steps to install o SSL\ncertificates on o NetBackup master servidor para o NetBackup appliances." + "desc": "The NetBackup deduplication web server's SSL certificate hash entry was not found in the NetBackup configuration database.", + "first_action": "Follow the troubleshooting steps to install the SSL", + "full_action": "Follow the troubleshooting steps to install the SSL\ncertificates on the NetBackup master server for the NetBackup appliances." }, "8630": { "code": 8630, - "desc": "O NetBackup deduplication web server's SSL certificate record foi não found in o NetBackup configuration banco de dados.", - "first_action": "Follow o troubleshooting steps to install o SSL", - "full_action": "Follow o troubleshooting steps to install o SSL\ncertificates on o NetBackup master servidor para o NetBackup appliances." + "desc": "The NetBackup deduplication web server's SSL certificate record was not found in the NetBackup configuration database.", + "first_action": "Follow the troubleshooting steps to install the SSL", + "full_action": "Follow the troubleshooting steps to install the SSL\ncertificates on the NetBackup master server for the NetBackup appliances." }, "8631": { "code": 8631, - "desc": "O current host ID-to-host name mapping conflicts com o NetBackup deduplication web server's host name in o NetBackup configuration banco de dados. Por favor update o NetBackup deduplication web server's SSL certificate record.", - "first_action": "O current NetBackup host ID-to-hostname mapping está returning um different", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ O current NetBackup host ID-to-hostname mapping está returning um different\nhost name from o host name que está stored in o NetBackup banco de dados record\nfortheMSDPSSLcertificates.UpdatetheNetBackupdeduplicationwebserver's\nSSL certificate record.\n■ FollowthetroubleshootingstepstoinstalltheSSLcertificatesontheNetBackup\nmaster servidor para o NetBackup appliances." + "desc": "The current host ID-to-host name mapping conflicts with the NetBackup deduplication web server's host name in the NetBackup configuration database. Please update the NetBackup deduplication web server's SSL certificate record.", + "first_action": "The current NetBackup host ID-to-hostname mapping is returning a different", + "full_action": "Do the following, as appropriate:\n■ The current NetBackup host ID-to-hostname mapping is returning a different\nhost name from the host name that is stored in the NetBackup database record\nfortheMSDPSSLcertificates.UpdatetheNetBackupdeduplicationwebserver's\nSSL certificate record.\n■ FollowthetroubleshootingstepstoinstalltheSSLcertificatesontheNetBackup\nmaster server for the NetBackup appliances." }, "8632": { "code": 8632, - "desc": "TheNetBackupdeduplicationwebserver'sSSLcertificatewasnotfound in o trust store para o NetBackup deduplication servers.", - "first_action": "There está um NetBackup banco de dados record para o MSDP SSL certificate, but o", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ There está um NetBackup banco de dados record para o MSDP SSL certificate, but o\ncertificate foi não found in o trust store. Garanta que there está um certificate in\no trust store.\n■ FollowthetroubleshootingstepstoinstalltheSSLcertificatesontheNetBackup\nmaster servidor para o NetBackup appliances." + "desc": "TheNetBackupdeduplicationwebserver'sSSLcertificatewasnotfound in the trust store for the NetBackup deduplication servers.", + "first_action": "There is a NetBackup database record for the MSDP SSL certificate, but the", + "full_action": "Do the following, as appropriate:\n■ There is a NetBackup database record for the MSDP SSL certificate, but the\ncertificate was not found in the trust store. Ensure that there is a certificate in\nthe trust store.\n■ FollowthetroubleshootingstepstoinstalltheSSLcertificatesontheNetBackup\nmaster server for the NetBackup appliances." }, "8633": { "code": 8633, - "desc": "O provided SSL certificate hash did não match o SSL certificate presented por o NetBackup deduplication web servidor.", - "first_action": "Verifique que o provided SHA-512 SSL certificate hash está", - "full_action": "Verifique que o provided SHA-512 SSL certificate hash está\npara o certificate que está presented por o web servidor (nginx) on o NetBackup\nappliance host. This host está known to o master servidor por o given host ID." + "desc": "The provided SSL certificate hash did not match the SSL certificate presented by the NetBackup deduplication web server.", + "first_action": "Verify that the provided SHA-512 SSL certificate hash is", + "full_action": "Verify that the provided SHA-512 SSL certificate hash is\nfor the certificate that is presented by the web server (nginx) on the NetBackup\nappliance host. This host is known to the master server by the given host ID." }, "8634": { "code": 8634, "desc": "Duplicate key name.", "first_action": "UNIX: /usr/openv/var/global/wsl/credentials/.credential_keystore", - "full_action": "Verifique o ownership e o permissions de o arquivos\n.credential_keystore e credjkskey. If necessary, allow ler permissão para\no usuário account nbwebsvc. Then, retry o ação.\nO caminho to .credential_keystore está:\n■ UNIX: /usr/openv/var/global/wsl/credentials/.credential_keystore\n■ Windows:\ninstall_path\\NetBackup\\var\\global\\wsl\\credentials\\.credential_keystore\nO caminho to credjskey (o arquivo que holds o password to o credential keystore)\nestá:\n■ UNIX: /usr/openv/var/global/credjkskey\n■ Windows: install_path\\NetBackup\\var\\global\\credjkskey" + "full_action": "Verify the ownership and the permissions of the files\n.credential_keystore and credjkskey. If necessary, allow read permission for\nthe user account nbwebsvc. Then, retry the action.\nThe path to .credential_keystore is:\n■ UNIX: /usr/openv/var/global/wsl/credentials/.credential_keystore\n■ Windows:\ninstall_path\\NetBackup\\var\\global\\wsl\\credentials\\.credential_keystore\nThe path to credjskey (the file that holds the password to the credential keystore)\nis:\n■ UNIX: /usr/openv/var/global/credjkskey\n■ Windows: install_path\\NetBackup\\var\\global\\credjkskey" }, "8635": { "code": 8635, - "desc": "Erro storing o key in o keystore.", + "desc": "Error storing the key in the keystore.", "first_action": "UNIX: /usr/openv/var/global/wsl/credentials/.credential_keystore", - "full_action": "Verifique o ownership e o permissions de o arquivos\n.credential_keystore e credjkskey. If necessary, allow ler permissão para\no usuário account nbwebsvc. Then, retry o ação.\nO caminho to .credential_keystore está:\n■ UNIX: /usr/openv/var/global/wsl/credentials/.credential_keystore\n■ Windows:\ninstall_path\\NetBackup\\var\\global\\wsl\\credentials\\.credential_keystore\nO caminho to credjskey (o arquivo que holds o password to o credential keystore)\nestá:\n■ UNIX: /usr/openv/var/global/credjkskey\n■ Windows: install_path\\NetBackup\\var\\global\\credjkskey" + "full_action": "Verify the ownership and the permissions of the files\n.credential_keystore and credjkskey. If necessary, allow read permission for\nthe user account nbwebsvc. Then, retry the action.\nThe path to .credential_keystore is:\n■ UNIX: /usr/openv/var/global/wsl/credentials/.credential_keystore\n■ Windows:\ninstall_path\\NetBackup\\var\\global\\wsl\\credentials\\.credential_keystore\nThe path to credjskey (the file that holds the password to the credential keystore)\nis:\n■ UNIX: /usr/openv/var/global/credjkskey\n■ Windows: install_path\\NetBackup\\var\\global\\credjkskey" }, "8636": { "code": 8636, - "desc": "Erro loading o keystore.", + "desc": "Error loading the keystore.", "first_action": "UNIX: /usr/openv/var/global/wsl/credentials/.credential_keystore", - "full_action": "Verifique o ownership e o permissions de o arquivos\n.credential_keystore e credjkskey. If necessary, allow ler permissão para\no usuário account nbwebsvc. Then, retry o ação.\nO caminho to .credential_keystore está:\n■ UNIX: /usr/openv/var/global/wsl/credentials/.credential_keystore\n■ Windows:\ninstall_path\\NetBackup\\var\\global\\wsl\\credentials\\.credential_keystore\nO caminho to credjskey (o arquivo que holds o password to o credential keystore)\nestá:\n■ UNIX: /usr/openv/var/global/credjkskey\n■ Windows: install_path\\NetBackup\\var\\global\\credjkskey" + "full_action": "Verify the ownership and the permissions of the files\n.credential_keystore and credjkskey. If necessary, allow read permission for\nthe user account nbwebsvc. Then, retry the action.\nThe path to .credential_keystore is:\n■ UNIX: /usr/openv/var/global/wsl/credentials/.credential_keystore\n■ Windows:\ninstall_path\\NetBackup\\var\\global\\wsl\\credentials\\.credential_keystore\nThe path to credjskey (the file that holds the password to the credential keystore)\nis:\n■ UNIX: /usr/openv/var/global/credjkskey\n■ Windows: install_path\\NetBackup\\var\\global\\credjkskey" }, "8638": { "code": 8638, - "desc": "Erro working com o encryption cipher.", - "first_action": "Garanta que o NetBackup Java Runtime Environment", - "full_action": "Garanta que o NetBackup Java Runtime Environment\n(JRE) security providers estão instalado. Then, restart o NetBackup Web\nManagement Console (nbwmc ou nbwmc.exe) e retry o ação." + "desc": "Error working with the encryption cipher.", + "first_action": "Ensure that the NetBackup Java Runtime Environment", + "full_action": "Ensure that the NetBackup Java Runtime Environment\n(JRE) security providers are installed. Then, restart the NetBackup Web\nManagement Console (nbwmc or nbwmc.exe) and retry the action." }, "8639": { "code": 8639, - "desc": "Encryption key erro.", - "first_action": "Garanta que o NetBackup Java Runtime Environment", - "full_action": "Garanta que o NetBackup Java Runtime Environment\n(JRE) security providers estão instalado. Then, restart o NetBackup Web\nManagement Console (nbwmc ou nbwmc.exe) e retry o ação." + "desc": "Encryption key error.", + "first_action": "Ensure that the NetBackup Java Runtime Environment", + "full_action": "Ensure that the NetBackup Java Runtime Environment\n(JRE) security providers are installed. Then, restart the NetBackup Web\nManagement Console (nbwmc or nbwmc.exe) and retry the action." }, "8640": { "code": 8640, - "desc": "Encryption erro working com key tag.", + "desc": "Encryption error working with key tag.", "first_action": "UNIX: /usr/openv/var/global/wsl/credentials/.credential_keystore", - "full_action": "Verifique o ownership e o permissions de o arquivos\n.credential_keystore e credjkskey. If necessary, allow ler permissão para\no usuário account nbwebsvc. Then, retry o ação.\nO caminho to .credential_keystore está:\n■ UNIX: /usr/openv/var/global/wsl/credentials/.credential_keystore\n■ Windows:\ninstall_path\\NetBackup\\var\\global\\wsl\\credentials\\.credential_keystore\nO caminho to credjskey (o arquivo que holds o password to o credential keystore)\nestá:\n■ UNIX: /usr/openv/var/global/credjkskey\n■ Windows: install_path\\NetBackup\\var\\global\\credjkskey" + "full_action": "Verify the ownership and the permissions of the files\n.credential_keystore and credjkskey. If necessary, allow read permission for\nthe user account nbwebsvc. Then, retry the action.\nThe path to .credential_keystore is:\n■ UNIX: /usr/openv/var/global/wsl/credentials/.credential_keystore\n■ Windows:\ninstall_path\\NetBackup\\var\\global\\wsl\\credentials\\.credential_keystore\nThe path to credjskey (the file that holds the password to the credential keystore)\nis:\n■ UNIX: /usr/openv/var/global/credjkskey\n■ Windows: install_path\\NetBackup\\var\\global\\credjkskey" }, "8641": { "code": 8641, - "desc": "Encryption manager erro.", - "first_action": "Garanta que o NetBackup Java Runtime Environment", - "full_action": "Garanta que o NetBackup Java Runtime Environment\n(JRE) security providers estão instalado. Then, restart o NetBackup Web\nManagement Console (nbwmc ou nbwmc.exe) e retry o ação." + "desc": "Encryption manager error.", + "first_action": "Ensure that the NetBackup Java Runtime Environment", + "full_action": "Ensure that the NetBackup Java Runtime Environment\n(JRE) security providers are installed. Then, restart the NetBackup Web\nManagement Console (nbwmc or nbwmc.exe) and retry the action." }, "8642": { "code": 8642, - "desc": "Encryption erro working com keystore.", + "desc": "Encryption error working with keystore.", "first_action": "UNIX: /usr/openv/var/global/wsl/credentials/.credential_keystore", - "full_action": "Verifique o ownership e o permissions de o arquivos\n.credential_keystore e credjkskey. If necessary, allow ler permissão para\no usuário account nbwebsvc. Then, retry o ação.\nO caminho to .credential_keystore está:\n■ UNIX: /usr/openv/var/global/wsl/credentials/.credential_keystore\n■ Windows:\ninstall_path\\NetBackup\\var\\global\\wsl\\credentials\\.credential_keystore\nO caminho to credjskey (o arquivo que holds o password to o credential keystore)\nestá:\n■ UNIX: /usr/openv/var/global/credjkskey\n■ Windows: install_path\\NetBackup\\var\\global\\credjkskey" + "full_action": "Verify the ownership and the permissions of the files\n.credential_keystore and credjkskey. If necessary, allow read permission for\nthe user account nbwebsvc. Then, retry the action.\nThe path to .credential_keystore is:\n■ UNIX: /usr/openv/var/global/wsl/credentials/.credential_keystore\n■ Windows:\ninstall_path\\NetBackup\\var\\global\\wsl\\credentials\\.credential_keystore\nThe path to credjskey (the file that holds the password to the credential keystore)\nis:\n■ UNIX: /usr/openv/var/global/credjkskey\n■ Windows: install_path\\NetBackup\\var\\global\\credjkskey" }, "8656": { "code": 8656, - "desc": "O SAML certificate already exists.", - "first_action": "If you desejar to re-generate o SAML certificates e", - "full_action": "If you desejar to re-generate o SAML certificates e\nkeystore, send o -f option com o nbidpcmd CLI comando to forcefully\nre-generate o certificate e keystore." + "desc": "The SAML certificate already exists.", + "first_action": "If you want to re-generate the SAML certificates and", + "full_action": "If you want to re-generate the SAML certificates and\nkeystore, send the -f option with the nbidpcmd CLI command to forcefully\nre-generate the certificate and keystore." }, "8657": { "code": 8657, - "desc": "O SAML keystore não é possível be generated.", + "desc": "The SAML keystore cannot be generated.", "first_action": "ForNetBackupissuedSAMLcertificateandkeystore,deleteanyexistingSAML", - "full_action": "Executar o seguinte actions como appropriate:\n■ ForNetBackupissuedSAMLcertificateandkeystore,deleteanyexistingSAML\ncertificates ou keystore e re-generate them.\n■ Para external CA issued SAML keystore configuration, review o seguinte como\nappropriate:\n■ IfyouwanttoreusetheNetBackupECAconfiguration,verifythatthemaster\nserverisECAconfiguredandtheECAkeystoreandpasskeyfilesarepresent\nin o seguinte paths:\n■ Windows:\nECA credentials diretório caminho:\ninstall_path\\var\\global\\wsl\\credentials\\externalcacreds\nECA keystore caminho: install_path\\var\n\\global\\wsl\\credentials\\externalcacreds\\nbwebservice.bcfks\nECA keystore passkey caminho:\ninstall_path\\var\\global\\wsl\\credentials\\externalcacreds\\jkskey\n■ UNIX:\nECA credentials diretório caminho:\nusr/openv/var/global/wsl/credentials/externalcacreds\nECA keystore caminho:\nusr/openv/var/global/wsl/credentials/externalcacreds/nbwebservice.bcfks\nECA keystore passkey caminho:\nusr/openv/var/global/wsl/credentials/externalcacreds/jkskey\n■ IftheexternalCAissuedcertificateandprivatekeyfilesareprovided,verifythat\no provided paths estão correct e o provided arquivos estão in PEM format. Verifique\nque o arquivos estão não corrupted." + "full_action": "Perform the following actions as appropriate:\n■ ForNetBackupissuedSAMLcertificateandkeystore,deleteanyexistingSAML\ncertificates or keystore and re-generate them.\n■ For external CA issued SAML keystore configuration, review the following as\nappropriate:\n■ IfyouwanttoreusetheNetBackupECAconfiguration,verifythatthemaster\nserverisECAconfiguredandtheECAkeystoreandpasskeyfilesarepresent\nin the following paths:\n■ Windows:\nECA credentials directory path:\ninstall_path\\var\\global\\wsl\\credentials\\externalcacreds\nECA keystore path: install_path\\var\n\\global\\wsl\\credentials\\externalcacreds\\nbwebservice.bcfks\nECA keystore passkey path:\ninstall_path\\var\\global\\wsl\\credentials\\externalcacreds\\jkskey\n■ UNIX:\nECA credentials directory path:\nusr/openv/var/global/wsl/credentials/externalcacreds\nECA keystore path:\nusr/openv/var/global/wsl/credentials/externalcacreds/nbwebservice.bcfks\nECA keystore passkey path:\nusr/openv/var/global/wsl/credentials/externalcacreds/jkskey\n■ IftheexternalCAissuedcertificateandprivatekeyfilesareprovided,verifythat\nthe provided paths are correct and the provided files are in PEM format. Verify\nthat the files are not corrupted." }, "8658": { "code": 8658, - "desc": "O SAML keystore não é possível be deleted.", - "first_action": "NetBackup issued SAML certificate e keystore arquivos:", - "full_action": "Garanta que usuário has o requerido permissão to excluir\no SAML certificate e keystore arquivos present in o seguinte paths:\n■ NetBackup issued SAML certificate e keystore arquivos:\n■ Windows:\nSAML credentials diretório caminho:\ninstall_path\\var\\global\\vxss\\samlcreds\nSAML keystore caminho:\ninstall_path\\var\\global\\wsl\\credentials\\nbwebsaml.bcfks\nSAML keystore passkey caminho: install_path\\var\\global\\samljkskey\n■ UNIX:\nSAMLcredentialsdirectorypath:usr/openv/var/global/vxss/samlcreds\nSAML keystore caminho:\nusr/openv/var/global/wsl/credentials/nbwebsaml.bcfks\nSAML keystore passkey caminho: usr/openv/var/global/samljkskey\n■ External CA issued SAML keystore:\n■ Windows:\nSAML credentials diretório caminho:\ninstall_path\\var\\global\\wsl\\credentials\\samlecacreds\nSAML keystore caminho:\ninstall_path\\var\\global\\wsl\\credentials\\samlecacreds\\nbwebsaml.bcfks\nSAML keystore passkey caminho:\ninstall_path\\var\\global\\wsl\\credentials\\samlecacreds\\jkskey\n■ UNIX:\nSAML credentials diretório caminho:\nusr/openv/var/global/wsl/credentials/samlecacreds\nSAML keystore caminho:\nusr/openv/var/global/wsl/credentials/samlecacreds/nbwebsaml.bcfks\nSAML keystore passkey caminho:\nusr/openv/var/global/wsl/credentials/samlecacreds/jkskey" + "desc": "The SAML keystore cannot be deleted.", + "first_action": "NetBackup issued SAML certificate and keystore files:", + "full_action": "Ensure that user has the required permission to delete\nthe SAML certificate and keystore files present in the following paths:\n■ NetBackup issued SAML certificate and keystore files:\n■ Windows:\nSAML credentials directory path:\ninstall_path\\var\\global\\vxss\\samlcreds\nSAML keystore path:\ninstall_path\\var\\global\\wsl\\credentials\\nbwebsaml.bcfks\nSAML keystore passkey path: install_path\\var\\global\\samljkskey\n■ UNIX:\nSAMLcredentialsdirectorypath:usr/openv/var/global/vxss/samlcreds\nSAML keystore path:\nusr/openv/var/global/wsl/credentials/nbwebsaml.bcfks\nSAML keystore passkey path: usr/openv/var/global/samljkskey\n■ External CA issued SAML keystore:\n■ Windows:\nSAML credentials directory path:\ninstall_path\\var\\global\\wsl\\credentials\\samlecacreds\nSAML keystore path:\ninstall_path\\var\\global\\wsl\\credentials\\samlecacreds\\nbwebsaml.bcfks\nSAML keystore passkey path:\ninstall_path\\var\\global\\wsl\\credentials\\samlecacreds\\jkskey\n■ UNIX:\nSAML credentials directory path:\nusr/openv/var/global/wsl/credentials/samlecacreds\nSAML keystore path:\nusr/openv/var/global/wsl/credentials/samlecacreds/nbwebsaml.bcfks\nSAML keystore passkey path:\nusr/openv/var/global/wsl/credentials/samlecacreds/jkskey" }, "8676": { "code": 8676, - "desc": "O access code está não appropriate.", - "first_action": "Garanta que you used o appropriate access code e", - "full_action": "Garanta que you used o appropriate access code e\napproval workflow." + "desc": "The access code is not appropriate.", + "first_action": "Ensure that you used the appropriate access code and", + "full_action": "Ensure that you used the appropriate access code and\napproval workflow." }, "8677": { "code": 8677, - "desc": "O access code está expired.", - "first_action": "Run o bpnbat -login -loginType webUI comando", - "full_action": "Run o bpnbat -login -loginType webUI comando\nto receive o new access code." + "desc": "The access code is expired.", + "first_action": "Run the bpnbat -login -loginType webUI command", + "full_action": "Run the bpnbat -login -loginType webUI command\nto receive the new access code." }, "8678": { "code": 8678, - "desc": "O access code request está declined.", - "first_action": "Contate seu Security Administrator.", - "full_action": "Contate seu Security Administrator." + "desc": "The access code request is declined.", + "first_action": "Contact your Security Administrator.", + "full_action": "Contact your Security Administrator." }, "8679": { "code": 8679, - "desc": "O access code request está already approved.", - "first_action": "Retry o operation e if o issue persists, visit", - "full_action": "Retry o operation e if o issue persists, visit\nsupport.veritas.com. O Cohesity Technical Support website site offers additional\ninformação to help you troubleshoot this issue." + "desc": "The access code request is already approved.", + "first_action": "Retry the operation and if the issue persists, visit", + "full_action": "Retry the operation and if the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support website site offers additional\ninformation to help you troubleshoot this issue." }, "8680": { "code": 8680, - "desc": "O access code request has approval pending.", - "first_action": "Contate o Security Administrator to verifique o access", - "full_action": "Contate o Security Administrator to verifique o access\ncode." + "desc": "The access code request has approval pending.", + "first_action": "Contact the Security Administrator to verify the access", + "full_action": "Contact the Security Administrator to verify the access\ncode." }, "8700": { "code": 8700, - "desc": "O host banco de dados web service está unavailable due to um internal erro.", - "first_action": "Examine o NetBackup erro logs para additional erro", - "full_action": "Examine o NetBackup erro logs para additional erro\nmessages. Additionally, you can refer to o debug logs para this web service (on\no master servidor) to determinar o cause de o erro.\nAlternatively, contate Cohesity Technical Support e send o appropriate logs.\nUm complete list de requerido logs e configuration informação está disponível." + "desc": "The host database web service is unavailable due to an internal error.", + "first_action": "Examine the NetBackup error logs for additional error", + "full_action": "Examine the NetBackup error logs for additional error\nmessages. Additionally, you can refer to the debug logs for this web service (on\nthe master server) to determine the cause of the error.\nAlternatively, contact Cohesity Technical Support and send the appropriate logs.\nA complete list of required logs and configuration information is available." }, "8701": { "code": 8701, - "desc": "O host does não exist.", + "desc": "The host does not exist.", "first_action": "Thehostthatyouaretryingtoaccessmaynotbeaknown", - "full_action": "Thehostthatyouaretryingtoaccessmaynotbeaknown\nNetBackup host. Starting com NetBackup 8.0, um host está added automatically when\nit communicates com um NetBackup 8.0 master servidor.\nAlternatively, contate Cohesity Technical Support e send o appropriate logs.\nUm complete list de requerido logs e configuration informação está disponível." + "full_action": "Thehostthatyouaretryingtoaccessmaynotbeaknown\nNetBackup host. Starting with NetBackup 8.0, a host is added automatically when\nit communicates with a NetBackup 8.0 master server.\nAlternatively, contact Cohesity Technical Support and send the appropriate logs.\nA complete list of required logs and configuration information is available." }, "8702": { "code": 8702, - "desc": "O host não é possível be created because o host name already exists in o host banco de dados. NetBackup status codes 1047 NetBackup status codes", + "desc": "The host cannot be created because the host name already exists in the host database. NetBackup status codes 1047 NetBackup status codes", "first_action": "Toresolveissuesthatarerelatedtodifferenthostshaving", - "full_action": "Toresolveissuesthatarerelatedtodifferenthostshaving\no same name ou alias, verifique o rede host name mapping." + "full_action": "Toresolveissuesthatarerelatedtodifferenthostshaving\nthe same name or alias, verify the network host name mapping." }, "8703": { "code": 8703, - "desc": "O host não é possível be created because o host ID-to-host name mapping already exists in o host banco de dados.", + "desc": "The host cannot be created because the host ID-to-host name mapping already exists in the host database.", "first_action": "Toresolveissuesthatarerelatedtodifferenthostshaving", - "full_action": "Toresolveissuesthatarerelatedtodifferenthostshaving\no same name ou alias, verifique o rede host name mapping." + "full_action": "Toresolveissuesthatarerelatedtodifferenthostshaving\nthe same name or alias, verify the network host name mapping." }, "8704": { "code": 8704, - "desc": "Um conflict ocorreu while updating o host banco de dados. Kindly retry o operation.", + "desc": "A conflict occurred while updating the host database. Kindly retry the operation.", "first_action": "Iftheproblemcontinues,savealloftheerrorloginformation", - "full_action": "Iftheproblemcontinues,savealloftheerrorloginformation\ne contate Cohesity Technical Support. Um complete list de requerido logs e\nconfiguration informação está disponível." + "full_action": "Iftheproblemcontinues,savealloftheerrorloginformation\nand contact Cohesity Technical Support. A complete list of required logs and\nconfiguration information is available." }, "8705": { "code": 8705, - "desc": "O specified host está não um NetBackup cliente host e therefore it não é possível be decommissioned.", - "first_action": "Use o informação in o technical note que está shown to", - "full_action": "Use o informação in o technical note que está shown to\ndeterminar o cause de o erro e o appropriate actions to resolve it:\nhttps://www.veritas.com/content/support/en_US/article.100073398" + "desc": "The specified host is not a NetBackup client host and therefore it cannot be decommissioned.", + "first_action": "Use the information in the technical note that is shown to", + "full_action": "Use the information in the technical note that is shown to\ndetermine the cause of the error and the appropriate actions to resolve it:\nhttps://www.veritas.com/content/support/en_US/article.100073398" }, "8706": { "code": 8706, - "desc": "O requerido field está missing from o input request.", - "first_action": "Enter um valid value para o mandatory fields e try again.", - "full_action": "Enter um valid value para o mandatory fields e try again." + "desc": "The required field is missing from the input request.", + "first_action": "Enter a valid value for the mandatory fields and try again.", + "full_action": "Enter a valid value for the mandatory fields and try again." }, "8707": { "code": 8707, - "desc": "O web service não é possível update o host ID.", - "first_action": "Remove o host ID from o input request to complete", - "full_action": "Remove o host ID from o input request to complete\no remaining operations." + "desc": "The web service cannot update the host ID.", + "first_action": "Remove the host ID from the input request to complete", + "full_action": "Remove the host ID from the input request to complete\nthe remaining operations." }, "8708": { "code": 8708, - "desc": "Constraint violations estão detected para o given attributes in o input request", - "first_action": "Enter um valid input para o input parâmetro e try again.", - "full_action": "Enter um valid input para o input parâmetro e try again." + "desc": "Constraint violations are detected for the given attributes in the input request", + "first_action": "Enter a valid input for the input parameter and try again.", + "full_action": "Enter a valid input for the input parameter and try again." }, "8709": { "code": 8709, - "desc": "O destination arquivo ou diretório already exists.", - "first_action": "Não ação requerido.", - "full_action": "Não ação requerido." + "desc": "The destination file or directory already exists.", + "first_action": "No action required.", + "full_action": "No action required." }, "8710": { "code": 8710, - "desc": "O arquivo não é possível be uploaded because de insufficient disco space on o host.", - "first_action": "To resolve o issue, create space on o master servidor", - "full_action": "To resolve o issue, create space on o master servidor\npara var/global paths." + "desc": "The file cannot be uploaded because of insufficient disk space on the host.", + "first_action": "To resolve the issue, create space on the master server", + "full_action": "To resolve the issue, create space on the master server\nfor var/global paths." }, "8711": { "code": 8711, - "desc": "O folder onde o telemetry data needs to be uploaded does não exist.", - "first_action": "Contate Cohesity Technical Support e send o", - "full_action": "Contate Cohesity Technical Support e send o\nappropriate logs. Um complete list de requerido logs e configuration informação está\ndisponível." + "desc": "The folder where the telemetry data needs to be uploaded does not exist.", + "first_action": "Contact Cohesity Technical Support and send the", + "full_action": "Contact Cohesity Technical Support and send the\nappropriate logs. A complete list of required logs and configuration information is\navailable." }, "8712": { "code": 8712, - "desc": "Falhou to upload o arquivo. NetBackup status codes 1050 NetBackup status codes", - "first_action": "Contate Cohesity Technical Support e send o", - "full_action": "Contate Cohesity Technical Support e send o\nappropriate logs. Um complete list de requerido logs e configuration informação está\ndisponível." + "desc": "Failed to upload the file. NetBackup status codes 1050 NetBackup status codes", + "first_action": "Contact Cohesity Technical Support and send the", + "full_action": "Contact Cohesity Technical Support and send the\nappropriate logs. A complete list of required logs and configuration information is\navailable." }, "8713": { "code": 8713, - "desc": "Falhou to upload o arquivo. O input arquivo não é possível be vazio.", - "first_action": "Verifique que o input arquivo para telemetry está correct.", - "full_action": "Verifique que o input arquivo para telemetry está correct." + "desc": "Failed to upload the file. The input file cannot be empty.", + "first_action": "Verify that the input file for telemetry is correct.", + "full_action": "Verify that the input file for telemetry is correct." }, "8714": { "code": 8714, - "desc": "O mapping não é possível be marked como unshared because it está already shared.", - "first_action": "Excluir o shared mapping entry.", - "full_action": "Excluir o shared mapping entry." + "desc": "The mapping cannot be marked as unshared because it is already shared.", + "first_action": "Delete the shared mapping entry.", + "full_action": "Delete the shared mapping entry." }, "8715": { "code": 8715, - "desc": "Aconflictinthemappingisdetected.Thehostnameisalreadymapped com um different host.", - "first_action": "Mark o conflicting mapping como shared to be able to approve it.", - "full_action": "Dooneofthefollowingtoresolvetheconflictingmapping:\n■ Mark o conflicting mapping como shared to be able to approve it.\n■ Excluir o conflicting mapping." + "desc": "Aconflictinthemappingisdetected.Thehostnameisalreadymapped with a different host.", + "first_action": "Mark the conflicting mapping as shared to be able to approve it.", + "full_action": "Dooneofthefollowingtoresolvetheconflictingmapping:\n■ Mark the conflicting mapping as shared to be able to approve it.\n■ Delete the conflicting mapping." }, "8716": { "code": 8716, - "desc": "O mapping não é possível be added because it está vazio.", - "first_action": "Provide um valid host ID-to-host name mapping.", - "full_action": "Provide um valid host ID-to-host name mapping." + "desc": "The mapping cannot be added because it is empty.", + "first_action": "Provide a valid host ID-to-host name mapping.", + "full_action": "Provide a valid host ID-to-host name mapping." }, "8717": { "code": 8717, - "desc": "O operation falhou como one de o input parameters está inválido.", - "first_action": "Provide um valid input parâmetro. Para more informação,", - "full_action": "Provide um valid input parâmetro. Para more informação,\nveja o NetBackup logs." + "desc": "The operation failed as one of the input parameters is invalid.", + "first_action": "Provide a valid input parameter. For more information,", + "full_action": "Provide a valid input parameter. For more information,\nsee the NetBackup logs." }, "8718": { "code": 8718, - "desc": "O mapping não é possível be deleted como this está o primary host name para o host ID.", - "first_action": "Do não excluir o primary host name que está mapped com", - "full_action": "Do não excluir o primary host name que está mapped com\no host ID." + "desc": "The mapping cannot be deleted as this is the primary host name for the host ID.", + "first_action": "Do not delete the primary host name that is mapped with", + "full_action": "Do not delete the primary host name that is mapped with\nthe host ID." }, "8719": { "code": 8719, - "desc": "O conflicting mapping não é possível be approved because it está não um shared mapping.", - "first_action": "Mark o conflicting mapping como shared to be able to approve it.", - "full_action": "Dooneofthefollowingtoresolvetheconflictingmapping:\n■ Mark o conflicting mapping como shared to be able to approve it.\n■ Excluir o conflicting mapping." + "desc": "The conflicting mapping cannot be approved because it is not a shared mapping.", + "first_action": "Mark the conflicting mapping as shared to be able to approve it.", + "full_action": "Dooneofthefollowingtoresolvetheconflictingmapping:\n■ Mark the conflicting mapping as shared to be able to approve it.\n■ Delete the conflicting mapping." }, "8720": { "code": 8720, - "desc": "O host ID does não exist.", - "first_action": "ListCertDetails comando. If o specified NetBackup host está part de multiple", - "full_action": "Verifique o specified host ID por usando o nbcertcmd\n-listCertDetails comando. If o specified NetBackup host está part de multiple\nNetBackup domains, garanta que you provide o correct host ID que corresponds\nto o specified NetBackup domain." + "desc": "The host ID does not exist.", + "first_action": "ListCertDetails command. If the specified NetBackup host is part of multiple", + "full_action": "Check the specified host ID by using the nbcertcmd\n-listCertDetails command. If the specified NetBackup host is part of multiple\nNetBackup domains, ensure that you provide the correct host ID that corresponds\nto the specified NetBackup domain." }, "8722": { "code": 8722, - "desc": "O specified name exceeds o maximum allowed length de 1024 characters. Enter um valid name para host ID-to-host name mapping.", - "first_action": "Garanta que o mapping que you have entered does não", - "full_action": "Garanta que o mapping que you have entered does não\nexceed 1024 characters." + "desc": "The specified name exceeds the maximum allowed length of 1024 characters. Enter a valid name for host ID-to-host name mapping.", + "first_action": "Ensure that the mapping that you have entered does not", + "full_action": "Ensure that the mapping that you have entered does not\nexceed 1024 characters." }, "8723": { "code": 8723, - "desc": "O specified comment exceeds o maximum allowed length.", + "desc": "The specified comment exceeds the maximum allowed length.", "first_action": "Ensurethatthecommentthatyouprovidedoesnotexceed", "full_action": "Ensurethatthecommentthatyouprovidedoesnotexceed\n2048 bytes." }, "8724": { "code": 8724, - "desc": "O host ID-to-host name mapping não é possível be configurado como um shared mapping because it está associated com um single host. NetBackup status codes 1053 NetBackup status codes", - "first_action": "Garanta que o host ID-to-host name mapping que you", - "full_action": "Garanta que o host ID-to-host name mapping que you\ndesejar to add está não configurado como shared because o mapping está associated com um\nsingle host." + "desc": "The host ID-to-host name mapping cannot be configured as a shared mapping because it is associated with a single host. NetBackup status codes 1053 NetBackup status codes", + "first_action": "Ensure that the host ID-to-host name mapping that you", + "full_action": "Ensure that the host ID-to-host name mapping that you\nwant to add is not configured as shared because the mapping is associated with a\nsingle host." }, "8725": { "code": 8725, - "desc": "O host ID should não be provided in o request along com o subject name.", + "desc": "The host ID should not be provided in the request along with the subject name.", "first_action": "DonotprovidethehostIDwhenyouperformanoperation", - "full_action": "DonotprovidethehostIDwhenyouperformanoperation\nque uses um certificate que está issued por um external CA." + "full_action": "DonotprovidethehostIDwhenyouperformanoperation\nthat uses a certificate that is issued by an external CA." }, "8727": { "code": 8727, - "desc": "External CA certificates não é possível be used para host communication.", - "first_action": "Use o certificate que está issued por o NetBackup CA para seu host.", - "full_action": "Do one de o seguinte:\n■ Use o certificate que está issued por o NetBackup CA para seu host.\n■ Change o setting on o master servidor to enable o use de certificates que\nestão issued por um external CA." + "desc": "External CA certificates cannot be used for host communication.", + "first_action": "Use the certificate that is issued by the NetBackup CA for your host.", + "full_action": "Do one of the following:\n■ Use the certificate that is issued by the NetBackup CA for your host.\n■ Change the setting on the master server to enable the use of certificates that\nare issued by an external CA." }, "8728": { "code": 8728, - "desc": "O certificate operation falhou because o NetBackup CA certificates não é possível be used para host communication in o domain.", - "first_action": "Use o certificate que está issued por o external CA para seu host.", - "full_action": "Do one de o seguinte:\n■ Use o certificate que está issued por o external CA para seu host.\n■ Change o configuration on o master servidor to enable o use de NetBackup\ncertificates." + "desc": "The certificate operation failed because the NetBackup CA certificates cannot be used for host communication in the domain.", + "first_action": "Use the certificate that is issued by the external CA for your host.", + "full_action": "Do one of the following:\n■ Use the certificate that is issued by the external CA for your host.\n■ Change the configuration on the master server to enable the use of NetBackup\ncertificates." }, "8729": { "code": 8729, - "desc": "Não external certificates com o specified subject estão disponível.", - "first_action": "Retrieve o subject name either usando o NetBackup", - "full_action": "Retrieve o subject name either usando o NetBackup\nwebUI(externalcertificatelistview)orthenbhostmgmtcommand.Usethatsubject\nname to executar o excluir ou o reset operation." + "desc": "No external certificates with the specified subject are available.", + "first_action": "Retrieve the subject name either using the NetBackup", + "full_action": "Retrieve the subject name either using the NetBackup\nwebUI(externalcertificatelistview)orthenbhostmgmtcommand.Usethatsubject\nname to perform the delete or the reset operation." }, "8730": { "code": 8730, - "desc": "External certificate com o specified subject está already disponível.", - "first_action": "Use o nbcertcmd -deleteECACertEntry comando to excluir o existing", - "full_action": "If o subject name está associated com um different host, try\none de o seguinte actions:\n■ Use o nbcertcmd -deleteECACertEntry comando to excluir o existing\nentry from o banco de dados.\n■ Use um different subject name." + "desc": "External certificate with the specified subject is already available.", + "first_action": "Use the nbcertcmd -deleteECACertEntry command to delete the existing", + "full_action": "If the subject name is associated with a different host, try\none of the following actions:\n■ Use the nbcertcmd -deleteECACertEntry command to delete the existing\nentry from the database.\n■ Use a different subject name." }, "8731": { "code": 8731, - "desc": "O subject name de o certificate está não in o valid format.", - "first_action": "If you desejar to provide o subject name usando o OpenSSL ou o vxsslcmd", - "full_action": "Do one de o seguinte:\n■ If you desejar to provide o subject name usando o OpenSSL ou o vxsslcmd\nAPI, garanta que it está in o RFC 2253 format. Use o seguinte comando:\n■ Install_Path/goodies/vxsslcmd x509 -noout -in input certificate\narquivo -subject -nameopt RFC2253 ou openssl x509 -noout -in input\ncertificate arquivo -subject -nameopt RFC2253\n■ RetrievethesubjectnameeitherusingtheNetBackupwebUI(externalcertificate\nlist view) ou o nbhostmgmt comando." + "desc": "The subject name of the certificate is not in the valid format.", + "first_action": "If you want to provide the subject name using the OpenSSL or the vxsslcmd", + "full_action": "Do one of the following:\n■ If you want to provide the subject name using the OpenSSL or the vxsslcmd\nAPI, ensure that it is in the RFC 2253 format. Use the following command:\n■ Install_Path/goodies/vxsslcmd x509 -noout -in input certificate\nfile -subject -nameopt RFC2253 or openssl x509 -noout -in input\ncertificate file -subject -nameopt RFC2253\n■ RetrievethesubjectnameeitherusingtheNetBackupwebUI(externalcertificate\nlist view) or the nbhostmgmt command." }, "8732": { "code": 8732, - "desc": "Um entry para o specified subject name que está associated com um host ID already exists in o NetBackup banco de dados.", - "first_action": "Update o existing subject name to host ID association usando o", - "full_action": "Do one de o seguinte:\n■ Update o existing subject name to host ID association usando o\nnetbackup/security/external-certificates API.\n■ Excluir o existing subject name to host ID entry from o banco de dados usando o\nnbcertcmd -deleteECACertEntrycommand(orthroughtheAPI).Thencreate\num new entry usando o createECACertEntry comando.\n■ Use um new subject name." + "desc": "An entry for the specified subject name that is associated with a host ID already exists in the NetBackup database.", + "first_action": "Update the existing subject name to host ID association using the", + "full_action": "Do one of the following:\n■ Update the existing subject name to host ID association using the\nnetbackup/security/external-certificates API.\n■ Delete the existing subject name to host ID entry from the database using the\nnbcertcmd -deleteECACertEntrycommand(orthroughtheAPI).Thencreate\na new entry using the createECACertEntry command.\n■ Use a new subject name." }, "8733": { "code": 8733, - "desc": "Um entry para o specified host ID associated com o subject name already exists in o NetBackup banco de dados.", - "first_action": "Update o existing subject name to host ID association usando o", - "full_action": "Do one de o seguinte:\n■ Update o existing subject name to host ID association usando o\nnetbackup/security/external-certificates API.\n■ RetrievetheconfiguredsubjectnameforthespecifiedhostID.Deletetheexisting\nsubject name to host ID entry from o banco de dados usando o nbcertcmd\n-deleteECACertEntrycommand(orthroughtheAPI).Thencreateanewentry\nusando o createECACertEntry comando." + "desc": "An entry for the specified host ID associated with the subject name already exists in the NetBackup database.", + "first_action": "Update the existing subject name to host ID association using the", + "full_action": "Do one of the following:\n■ Update the existing subject name to host ID association using the\nnetbackup/security/external-certificates API.\n■ RetrievetheconfiguredsubjectnameforthespecifiedhostID.Deletetheexisting\nsubject name to host ID entry from the database using the nbcertcmd\n-deleteECACertEntrycommand(orthroughtheAPI).Thencreateanewentry\nusing the createECACertEntry command." }, "8739": { "code": 8739, - "desc": "ThehostID-to-hostnamemappingcannotbeadded.Automaticmapping está disabled para NAT clients.", + "desc": "ThehostID-to-hostnamemappingcannotbeadded.Automaticmapping is disabled for NAT clients.", "first_action": "AddtherequiredhostID-to-hostnamemappingusingthe", - "full_action": "AddtherequiredhostID-to-hostnamemappingusingthe\nNetBackup web UI ou NetBackup Administration Console. Alternatively, use o\nnbhostmgmt comando to add o requerido name mapping." + "full_action": "AddtherequiredhostID-to-hostnamemappingusingthe\nNetBackup web UI or NetBackup Administration Console. Alternatively, use the\nnbhostmgmt command to add the required name mapping." }, "8740": { "code": 8740, - "desc": "Falhou to fetch o master servidor informação.", - "first_action": "O appropriate license key está used.", - "full_action": "Garanta o seguinte:\n■ O appropriate license key está used.\n■ O NBSL service está up e executando." + "desc": "Failed to fetch the master server information.", + "first_action": "The appropriate license key is used.", + "full_action": "Ensure the following:\n■ The appropriate license key is used.\n■ The NBSL service is up and running." }, "8743": { "code": 8743, - "desc": "O specified host está already decommissioned.", - "first_action": "This request está inválido. O host foi already", - "full_action": "This request está inválido. O host foi already\ndecommissioned e não é possível be decommissioned again." + "desc": "The specified host is already decommissioned.", + "first_action": "This request is invalid. The host was already", + "full_action": "This request is invalid. The host was already\ndecommissioned and cannot be decommissioned again." }, "8744": { "code": 8744, - "desc": "Primary servers não é possível be decommissioned. NetBackup status codes 1057 NetBackup status codes", - "first_action": "This request está inválido. O specified host está um primary", - "full_action": "This request está inválido. O specified host está um primary\nservidor e primary servers não é possível be decommissioned." + "desc": "Primary servers cannot be decommissioned. NetBackup status codes 1057 NetBackup status codes", + "first_action": "This request is invalid. The specified host is a primary", + "full_action": "This request is invalid. The specified host is a primary\nserver and primary servers cannot be decommissioned." }, "8745": { "code": 8745, - "desc": "O specified host está um unknown servidor.", - "first_action": "This request está inválido. O specified host está não known to", - "full_action": "This request está inválido. O specified host está não known to\nNetBackup e não é possível be decommissioned." + "desc": "The specified host is an unknown server.", + "first_action": "This request is invalid. The specified host is not known to", + "full_action": "This request is invalid. The specified host is not known to\nNetBackup and cannot be decommissioned." }, "8747": { "code": 8747, - "desc": "Protected hosts não é possível be decommissioned.", + "desc": "Protected hosts cannot be decommissioned.", "first_action": "Removethehostfromtheassociatedpoliciesorprotection", - "full_action": "Removethehostfromtheassociatedpoliciesorprotection\nplans.Determineifthehostispartofanybackuphostpoolthatisusedinthepolicy\nou o protection plan. If it está present, remove o given host from o backup host\npool e then decommission o host. Alternatively, use o force option to\ndecommission o host." + "full_action": "Removethehostfromtheassociatedpoliciesorprotection\nplans.Determineifthehostispartofanybackuphostpoolthatisusedinthepolicy\nor the protection plan. If it is present, remove the given host from the backup host\npool and then decommission the host. Alternatively, use the force option to\ndecommission the host." }, "8748": { "code": 8748, "desc": "OneormoreimagesforthespecifiedhostexistintheNetBackupcatalog.", - "first_action": "Remove o images present para given host. You can use", - "full_action": "Remove o images present para given host. You can use\no force option to ignore this falha." + "first_action": "Remove the images present for given host. You can use", + "full_action": "Remove the images present for given host. You can use\nthe force option to ignore this failure." }, "8749": { "code": 8749, - "desc": "Policies, protection plans, ou images estão associated com o specified host.", + "desc": "Policies, protection plans, or images are associated with the specified host.", "first_action": "Removethehostfromtheassociatedpoliciesorprotection", - "full_action": "Removethehostfromtheassociatedpoliciesorprotection\nplans,andexpireanyassociatedimages,thendecommissionthehost.Alternatively,\nuse o force option to decommission o host.\nRemove o host from o associated policies ou protection plans. Determinar if o\ngiven host está part de qualquer backup host pool que está used in o policy ou o protection\nplan. If it está present, remove o host from o backup host pool e then\ndecommissionthehost.Expireanyassociatedimagesandthendecommissionthe\nhost. Alternatively, use o force option to decommission o host." + "full_action": "Removethehostfromtheassociatedpoliciesorprotection\nplans,andexpireanyassociatedimages,thendecommissionthehost.Alternatively,\nuse the force option to decommission the host.\nRemove the host from the associated policies or protection plans. Determine if the\ngiven host is part of any backup host pool that is used in the policy or the protection\nplan. If it is present, remove the host from the backup host pool and then\ndecommissionthehost.Expireanyassociatedimagesandthendecommissionthe\nhost. Alternatively, use the force option to decommission the host." }, "8753": { "code": 8753, - "desc": "O certificate enrollment falhou. O host name should be part de o certificate.", - "first_action": "Garanta que o host name está part de o subject name de o certificate.", - "full_action": "Do one de o seguinte:\n■ Garanta que o host name está part de o subject name de o certificate.\n■ Add ou update (excluir e then add) o subject name de o certificate in o\nNetBackupdatabase.Usethenbcertcmd -createECACertEntryandnbcertcmd\n-deleteECACertEntry commands. Para more informação on o commands,\nrefer to o NetBackup Commands Reference Guide." + "desc": "The certificate enrollment failed. The host name should be part of the certificate.", + "first_action": "Ensure that the host name is part of the subject name of the certificate.", + "full_action": "Do one of the following:\n■ Ensure that the host name is part of the subject name of the certificate.\n■ Add or update (delete and then add) the subject name of the certificate in the\nNetBackupdatabase.Usethenbcertcmd -createECACertEntryandnbcertcmd\n-deleteECACertEntry commands. For more information on the commands,\nrefer to the NetBackup Commands Reference Guide." }, "8754": { "code": 8754, - "desc": "O certificate enrollment falhou. O host name should be um primary name.", - "first_action": "Use o primary name de o host during certificate enrollment.", - "full_action": "Do one de o seguinte:\n■ Use o primary name de o host during certificate enrollment.\n■ Add ou update (excluir e then add) o subject name de o certificate in o\nNetBackup banco de dados. Use o nbcertcmd -deleteECACertEntry then o\nnbcertcmd -createECACertEntry commands. Para more informação on o\ncommands, refer to o NetBackup Commands Reference Guide." + "desc": "The certificate enrollment failed. The host name should be a primary name.", + "first_action": "Use the primary name of the host during certificate enrollment.", + "full_action": "Do one of the following:\n■ Use the primary name of the host during certificate enrollment.\n■ Add or update (delete and then add) the subject name of the certificate in the\nNetBackup database. Use the nbcertcmd -deleteECACertEntry then the\nnbcertcmd -createECACertEntry commands. For more information on the\ncommands, refer to the NetBackup Commands Reference Guide." }, "8755": { "code": 8755, - "desc": "O certificate enrollment falhou. O host name should be part de o certificate e it should be um primary name.", - "first_action": "Use o primary name de o host during certificate enrollment e garanta que", - "full_action": "Do one de o seguinte:\n■ Use o primary name de o host during certificate enrollment e garanta que\no host name está part de o subject alternate name de o certificate.\n■ Add ou update (excluir e then add) o subject name de o certificate in o\nNetBackup banco de dados. Use o nbcertcmd -deleteECACertEntry then o\nnbcertcmd -createECACertEntry commands. Para more informação on o\ncommands, refer to o NetBackup Commands Reference Guide." + "desc": "The certificate enrollment failed. The host name should be part of the certificate and it should be a primary name.", + "first_action": "Use the primary name of the host during certificate enrollment and ensure that", + "full_action": "Do one of the following:\n■ Use the primary name of the host during certificate enrollment and ensure that\nthe host name is part of the subject alternate name of the certificate.\n■ Add or update (delete and then add) the subject name of the certificate in the\nNetBackup database. Use the nbcertcmd -deleteECACertEntry then the\nnbcertcmd -createECACertEntry commands. For more information on the\ncommands, refer to the NetBackup Commands Reference Guide." }, "8756": { "code": 8756, - "desc": "O certificate enrollment falhou. O host name está already enrolled com um certificate com um different subject name.", + "desc": "The certificate enrollment failed. The host name is already enrolled with a certificate with a different subject name.", "first_action": "1. Runthenbcertcmd -deleteECACertEntrycommandtodeletetheassociation", - "full_action": "Add ou update (excluir e then add) o subject name de\no certificate in o NetBackup banco de dados. Do o seguinte:\n1. Runthenbcertcmd -deleteECACertEntrycommandtodeletetheassociation\nde o existing host com o certificate.\n2. Run o nbcertcmd -createECACertEntry comando to associate o new\ncertificate com o existing host.\nPara more informação on o commands, refer to o NetBackup Commands\nReference Guide." + "full_action": "Add or update (delete and then add) the subject name of\nthe certificate in the NetBackup database. Do the following:\n1. Runthenbcertcmd -deleteECACertEntrycommandtodeletetheassociation\nof the existing host with the certificate.\n2. Run the nbcertcmd -createECACertEntry command to associate the new\ncertificate with the existing host.\nFor more information on the commands, refer to the NetBackup Commands\nReference Guide." }, "8757": { "code": 8757, - "desc": "Falhou to retrieve o Certificate Authority uso informação de o NetBackup web servidor.", - "first_action": "Try retrieving o Certificate Authority uso informação", - "full_action": "Try retrieving o Certificate Authority uso informação\nde o web servidor again." + "desc": "Failed to retrieve the Certificate Authority usage information of the NetBackup web server.", + "first_action": "Try retrieving the Certificate Authority usage information", + "full_action": "Try retrieving the Certificate Authority usage information\nof the web server again." }, "8759": { "code": 8759, - "desc": "O certificate to be used para enrollment está não yet valid.", + "desc": "The certificate to be used for enrollment is not yet valid.", "first_action": "VerifythetimethatisspecifiedforthenotBeforeparameter", - "full_action": "VerifythetimethatisspecifiedforthenotBeforeparameter\ninthecertificate.Ifthetimeisinthefuture,tryenrollingadifferentexternalcertificate\nque está valid." + "full_action": "VerifythetimethatisspecifiedforthenotBeforeparameter\ninthecertificate.Ifthetimeisinthefuture,tryenrollingadifferentexternalcertificate\nthat is valid." }, "8760": { "code": 8760, - "desc": "O certificate to be used para enrollment está expired.", + "desc": "The certificate to be used for enrollment is expired.", "first_action": "VerifythetimethatisspecifiedforthenotAfterparameter", - "full_action": "VerifythetimethatisspecifiedforthenotAfterparameter\nin o certificate. If o time está in o past, try enrolling um different external certificate\nque está valid." + "full_action": "VerifythetimethatisspecifiedforthenotAfterparameter\nin the certificate. If the time is in the past, try enrolling a different external certificate\nthat is valid." }, "8761": { "code": 8761, - "desc": "O certificate enrollment falhou. O certificate está revoked.", - "first_action": "Contate seu security administrator to get um new external", - "full_action": "Contate seu security administrator to get um new external\ncertificate que está valid. Try enrolling o new external certificate." + "desc": "The certificate enrollment failed. The certificate is revoked.", + "first_action": "Contact your security administrator to get a new external", + "full_action": "Contact your security administrator to get a new external\ncertificate that is valid. Try enrolling the new external certificate." }, "8762": { "code": 8762, - "desc": "Theprivatekeyoftheexternalcertificateisencrypted,butthepassphrase está blank.", - "first_action": "Garanta que o passphrase está defined on o first line de", - "full_action": "Garanta que o passphrase está defined on o first line de\no ECA_KEY_PASSPHRASEFILE configuration option." + "desc": "Theprivatekeyoftheexternalcertificateisencrypted,butthepassphrase is blank.", + "first_action": "Ensure that the passphrase is defined on the first line of", + "full_action": "Ensure that the passphrase is defined on the first line of\nthe ECA_KEY_PASSPHRASEFILE configuration option." }, "8763": { "code": 8763, - "desc": "Thecertificateenrollmentfailed.Anotherhostwiththesameshortname exists in o NetBackup banco de dados.", - "first_action": "Provide o correct CLIENT_NAME de o host. Use o nbhostmgmt -list", - "full_action": "Try one de o seguinte actions:\n■ Provide o correct CLIENT_NAME de o host. Use o nbhostmgmt -list\ncomando to get o cliente name e retry o operation.\n■ If o host para which um external certificate está to be enrolled e o host que está\navailableonthemasterserveraredifferentthenusethenbhostmgmt -addhost\ncomando." + "desc": "Thecertificateenrollmentfailed.Anotherhostwiththesameshortname exists in the NetBackup database.", + "first_action": "Provide the correct CLIENT_NAME of the host. Use the nbhostmgmt -list", + "full_action": "Try one of the following actions:\n■ Provide the correct CLIENT_NAME of the host. Use the nbhostmgmt -list\ncommand to get the client name and retry the operation.\n■ If the host for which an external certificate is to be enrolled and the host that is\navailableonthemasterserveraredifferentthenusethenbhostmgmt -addhost\ncommand." }, "8764": { "code": 8764, - "desc": "O certificate ou o certificate caminho está não valid.", - "first_action": "Garanta que o certificate e o certificate arquivo caminho estão", - "full_action": "Garanta que o certificate e o certificate arquivo caminho estão\nvalid." + "desc": "The certificate or the certificate path is not valid.", + "first_action": "Ensure that the certificate and the certificate file path are", + "full_action": "Ensure that the certificate and the certificate file path are\nvalid." }, "8765": { "code": 8765, - "desc": "O host does não have qualquer security certificate configurado com respect to this master servidor.", - "first_action": "Run o seguinte comando: nbcertcmd - getCertificate", - "full_action": "Carry fora o seguinte steps:\n1 Generate e deploy um NetBackup certificate (ou um host ID-based certificate).\n■ Run o seguinte comando: nbcertcmd - getCertificate\n2 Enroll um external certificate.\n■ Run o seguinte comando: nbcertcmd - enrollCertificate\nPara more details on o certificate deployment e enrollment process, refer to o\nNetBackup Security e Encryption Guide.\nPara more details on o commands, refer to o NetBackup Commands Guide." + "desc": "The host does not have any security certificate configured with respect to this master server.", + "first_action": "Run the following command: nbcertcmd - getCertificate", + "full_action": "Carry out the following steps:\n1 Generate and deploy a NetBackup certificate (or a host ID-based certificate).\n■ Run the following command: nbcertcmd - getCertificate\n2 Enroll an external certificate.\n■ Run the following command: nbcertcmd - enrollCertificate\nFor more details on the certificate deployment and enrollment process, refer to the\nNetBackup Security and Encryption Guide.\nFor more details on the commands, refer to the NetBackup Commands Guide." }, "8766": { "code": 8766, - "desc": "O certificate enrollment falhou. O common name (CN) está não present in o certificate.", - "first_action": "Add o common name de o host in o certificate.", - "full_action": "Do one de o seguinte:\n■ Add o common name de o host in o certificate.\n■ Add o host name in o certificate’s subject alternative name.\n■ Carry fora o seguinte steps in o given order:\n■ Addthehostinthehostdatabaseusingthenbhostmgmt -addhostcommand.\n■ AddthesubjectalternativenameofthecertificateintheNetBackupdatabase\nusando o nbcertcmd -createECACertEntry comando." + "desc": "The certificate enrollment failed. The common name (CN) is not present in the certificate.", + "first_action": "Add the common name of the host in the certificate.", + "full_action": "Do one of the following:\n■ Add the common name of the host in the certificate.\n■ Add the host name in the certificate’s subject alternative name.\n■ Carry out the following steps in the given order:\n■ Addthehostinthehostdatabaseusingthenbhostmgmt -addhostcommand.\n■ AddthesubjectalternativenameofthecertificateintheNetBackupdatabase\nusing the nbcertcmd -createECACertEntry command." }, "8767": { "code": 8767, - "desc": "Thecertificateenrollmentfailed.Theissuerinthecertificateandtheone que you have provided do não match.", + "desc": "Thecertificateenrollmentfailed.Theissuerinthecertificateandtheone that you have provided do not match.", "first_action": "Ensurethatyouprovidethecorrectcertificateissuername.", "full_action": "Ensurethatyouprovidethecorrectcertificateissuername." }, "8768": { "code": 8768, - "desc": "O specified certificate store does não exist on o local machine.", - "first_action": "O certificate store name está specified correctly.", - "full_action": "Garanta o seguinte:\n■ O certificate store name está specified correctly.\n■ O specified certificate store está part de o HKEY_LOCAL_MACHINE certificate\nstore." + "desc": "The specified certificate store does not exist on the local machine.", + "first_action": "The certificate store name is specified correctly.", + "full_action": "Ensure the following:\n■ The certificate store name is specified correctly.\n■ The specified certificate store is part of the HKEY_LOCAL_MACHINE certificate\nstore." }, "8769": { "code": 8769, - "desc": "Certificate caminho está inválido. If seu store name, issuer, ou subject contains qualquer special characters, garanta que they estão included in double quotes.", + "desc": "Certificate path is invalid. If your store name, issuer, or subject contains any special characters, ensure that they are included in double quotes.", "first_action": "1. Ensurethatthecertificatestorenameorcertificatesubjectnamearenotempty.", - "full_action": "Executar o seguinte steps:\n1. Ensurethatthecertificatestorenameorcertificatesubjectnamearenotempty.\n2. If o certificate issuer name está blank, garanta que seu certificate caminho looks\nlike o seguinte: \\\\.\n3. If o store name, issuer name, ou subject name contains special characters,\nuse double quotes to specify these parameters." + "full_action": "Perform the following steps:\n1. Ensurethatthecertificatestorenameorcertificatesubjectnamearenotempty.\n2. If the certificate issuer name is blank, ensure that your certificate path looks\nlike the following: \\\\.\n3. If the store name, issuer name, or subject name contains special characters,\nuse double quotes to specify these parameters." }, "8770": { "code": 8770, - "desc": "O certificate não é possível be found at o specified caminho.", - "first_action": "Garanta que o specified certificate caminho está correct e", - "full_action": "Garanta que o specified certificate caminho está correct e\no certificate está present at o given caminho." + "desc": "The certificate cannot be found at the specified path.", + "first_action": "Ensure that the specified certificate path is correct and", + "full_action": "Ensure that the specified certificate path is correct and\nthe certificate is present at the given path." }, "8771": { "code": 8771, - "desc": "O certificate com o given subject name não é possível be found.", - "first_action": "1. Garanta que o certificate subject name está specified correctly.", - "full_action": "Executar o seguinte steps:\n1. Garanta que o certificate subject name está specified correctly.\n2. Garanta que o certificate store contains o specified certificate.\n3. If o host name está used como o subject name, garanta que o subject name está\nmentioned como $hostname." + "desc": "The certificate with the given subject name cannot be found.", + "first_action": "1. Ensure that the certificate subject name is specified correctly.", + "full_action": "Perform the following steps:\n1. Ensure that the certificate subject name is specified correctly.\n2. Ensure that the certificate store contains the specified certificate.\n3. If the host name is used as the subject name, ensure that the subject name is\nmentioned as $hostname." }, "8772": { "code": 8772, - "desc": "O Windows certificate store não é possível be opened.", - "first_action": "O certificate store name está specified correctly.", - "full_action": "Garanta o seguinte:\n■ O certificate store name está specified correctly.\n■ O specified certificate store está part de o Local Machine certificate store." + "desc": "The Windows certificate store cannot be opened.", + "first_action": "The certificate store name is specified correctly.", + "full_action": "Ensure the following:\n■ The certificate store name is specified correctly.\n■ The specified certificate store is part of the Local Machine certificate store." }, "8773": { "code": 8773, - "desc": "O certificate está não valid como o certificate validity period starts in o future.", + "desc": "The certificate is not valid as the certificate validity period starts in the future.", "first_action": "Reviewthecertificatedate.Useacertificatethatiscurrently", "full_action": "Reviewthecertificatedate.Useacertificatethatiscurrently\nvalid." }, "8774": { "code": 8774, - "desc": "O Windows certificate store não é possível be closed.", - "first_action": "Wait para um few minutes e try enrolling o certificate", - "full_action": "Wait para um few minutes e try enrolling o certificate\nagain." + "desc": "The Windows certificate store cannot be closed.", + "first_action": "Wait for a few minutes and try enrolling the certificate", + "full_action": "Wait for a few minutes and try enrolling the certificate\nagain." }, "8775": { "code": 8775, - "desc": "O host name não é possível be retrieved. NetBackup status codes 1066 NetBackup status codes", + "desc": "The host name cannot be retrieved. NetBackup status codes 1066 NetBackup status codes", "first_action": "Verifythatthehostnameissetandthenretrytheoperation.", "full_action": "Verifythatthehostnameissetandthenretrytheoperation." }, "8776": { "code": 8776, - "desc": "NetBackup does não support o algorithm used, veja logs para more informação regarding o algorithm.", - "first_action": "Use um certificate que está encrypted usando um algorithm que", - "full_action": "Use um certificate que está encrypted usando um algorithm que\nNetBackup supports. Refer to o NetBackup Security e Encryption Guide." + "desc": "NetBackup does not support the algorithm used, see logs for more information regarding the algorithm.", + "first_action": "Use a certificate that is encrypted using an algorithm that", + "full_action": "Use a certificate that is encrypted using an algorithm that\nNetBackup supports. Refer to the NetBackup Security and Encryption Guide." }, "8777": { "code": 8777, - "desc": "O certificate não é possível be enrolled because de um unknown erro.", - "first_action": "Contate Cohesity Technical Support para assistance.", - "full_action": "Contate Cohesity Technical Support para assistance." + "desc": "The certificate cannot be enrolled because of an unknown error.", + "first_action": "Contact Cohesity Technical Support for assistance.", + "full_action": "Contact Cohesity Technical Support for assistance." }, "8778": { "code": 8778, - "desc": "Falhou to get o specified certificate from Windows certificate store.", - "first_action": "Contate Cohesity Technical Support para assistance.", - "full_action": "Contate Cohesity Technical Support para assistance." + "desc": "Failed to get the specified certificate from Windows certificate store.", + "first_action": "Contact Cohesity Technical Support for assistance.", + "full_action": "Contact Cohesity Technical Support for assistance." }, "8779": { "code": 8779, - "desc": "ECA health verifique falhou.", + "desc": "ECA health check failed.", "first_action": "Causes:", - "full_action": "Each falhou validation está associated com um validation ID.\nPara each falha, there may be um specific reason e you can carry fora certain\ntroubleshootingsteps.ReviewthefollowinglistofvalidationsfortheecaHealthCheck\ncomando.\nValidation ID: USER_INPUT_CERT_PATH_VALIDATION\n■ Causes:\n■ O certificate caminho está vazio.\n■ O arquivo at o specified caminho filename não é possível be accessed.\n■ Recomendada actions:\n■ Garanta que o certificate caminho está não blank.\n■ Garanta que o arquivo has o Ler permissions para o corresponding usuário.\nValidation ID: USER_INPUT_CERTIFICATES_VALIDATION\n■ Causes:\n■ Erro in reading o certificate arquivo.\n■ Recomendada actions:\n■ Garanta que o certificate arquivo contains um certificate.\n■ Garanta que o certificate arquivo format está one que NetBackup supports. O\nsupported certificate formats estão PEM, P7BPEM, P7BDER.\nValidation ID: USER_INPUT_PRIVATE_KEY_PATH_VALIDATION\n■ Causes:\n■ O private key caminho está vazio.\n■ O arquivo at o specified caminho filename não é possível be accessed.\n■ Recomendada actions:\n■ Garanta que o private key caminho está não blank.\n■ Garanta que o arquivo has o Ler permissions para o corresponding usuário.\nValidation ID: USER_INPUT_PRIVATE_KEY_READ_VALIDATION\n■ Causes:\n■ Erro in reading o private key: Arquivo ler falhou.\n■ Erro in reading o private key: O private key de o external certificate está\nencrypted, but o passphrase está não provided.\n■ Erro in reading o private key: O private key de o external certificate está\nencrypted, but o passphrase está blank.\n■ Recomendada actions:\n■ Garanta que o private key format ou key algorithms format está one de those\nsupported por NetBackup. O supported key formats estão PEM e DER.\n■ If o private key está encrypted, garanta que o ECA_KEY_PASSPHRASEFILE ou\n-passphraseFile com its value como passphrase arquivo caminho location está given.\n■ If o private key está encrypted e o passphrase arquivo está given, garanta que\no passphrase arquivo está não vazio e o passphrase in it está correct.\nValidation ID: USER_INPUT_TRUST_STORE_PATH_VALIDATION\n■ Causes:\n■ O trust store caminho está vazio.\n■ O arquivo at o specified caminho filename não é possível be accessed.\n■ Recomendada actions:\n■ Garanta que o trust store caminho está não blank.\n■ Garanta que o arquivo has o Ler permissions para o corresponding usuário.\nValidation ID: USER_INPUT_TRUST_STORE_VALIDATION\n■ Causes:\n■ Erro in reading o trust store caminho.\n■ Recomendada actions:\n■ Garanta que o trust store certificate arquivo contains um trusted certificate.\n■ Garanta que o certificate arquivo format está one que NetBackup supports. O\nsupported certificate formats estão PEM, P7BPEM, P7BDER.\nValidation ID: CERTIFICATES_KEYS_ACCESS_VALIDATION\n■ Causes:\n■ Windows:NetBackupservicesarenotabletoreadthecertificate,truststore,\nou private key.\n■ UNIX: NetBackup service usuário está não able to ler o certificate, trust store,\nou private key.\n■ Recomendada actions:\n■ Windows:\n■ EnsurethattheLocalServiceisnotdeniedaccesstothecertificate,trust\nstore, ou private key.\n■ Garanta que o NetBackup services have access to o certificate, trust\nstore, ou private key.\n■ Run o icacls comando to garanta o NetBackup services ou Local\nService have ler permissions. Example:\nicacls \n...\n NT SERVICE\\NetBackup Audit Manager:(R)\n...\nNote: This note apenas applicable to Windows systems.\nThis verifique está não applicable para group members if o Local Service e\nou NetBackup service estão members de um group que está given o\npermissionsdenyandorallow.Thevalidationcheckdoesnotdetecttheir\npermissions.\n■ UNIX:\n■ Garanta que o NetBackup service usuário has access to o certificates,\no private key, e o passphrase arquivo.\nValidation ID: LEAF_CERTIFICATE_ENHANCED_KEY_USAGE_VALIDATION\n■ Causes:\n■ O requerido extended key usages estão não disponível in o given certificate.\n■ Recomendada actions:\n■ Execute o seguinte comando:\n■ Para Windows:\n■ install_path\\bin\\goodies\\vxsslcmd.exe x509 -text -in\nend_entity_certificate\n■ Para UNIX:\n■ install_path/bin/goodies/vxsslcmdx509-text-inend_entity_certificate\n■ If o certificate has um X509v3 Key Uso extension present, it must include\no seguinte key uso purposes:\n■ Forthewebservercertificate:AtleastoneoftheDigitalSignatureorKey\nEncipherment should be present.\n■ Para um NetBackup host certificate: Digital Signature purpose should be\npresent. Key Encipherment may ou may não be present.\n■ Para um certificate que está used para both web servidor e NetBackup host:\nDigital Signature purpose should be present. Key Encipherment may ou\nmay não be present.\n■ O certificate may have other key uso purposes listed in addition to\no purposes specified here. These additional purposes estão ignored.\n■ O X509v3 Key Uso extension may be either critical ou non-critical.\n■ Um certificate without um X509v3 Key Uso extension está also usable com\nNetBackup.\n■ If o certificate has um X509v3 Extended Key Uso extension present, it\nmust include o seguinte key uso purposes:\n■ Para o web servidor certificate: TLS Web Servidor Authentication.\n■ Para um NetBackup host certificate: TLS Web Servidor Authentication e\nTLS Web Cliente Authentication.\n■ Para um certificate que está used para both web servidor e NetBackup host:\nTLS Web Servidor Authentication e TLS Web Cliente Authentication.\n■ O certificate may have other key uso purposes listed in addition to\no purposes specified here. These additional purposes estão ignored.\n■ O X509v3 Extended Key Uso extension may be either critical ou\nnon-critical.\n■ AcertificatewithoutaX509v3ExtendedKeyUsageextensionisalsousable\ncom NetBackup.\n■ If o certificate doesn’t meet o requirements que estão listed in this\nRecommend actions section, contate seu certificate provider to obtain um\nnew certificate.\nValidation ID: CERTIFICATE_SUBJECT_DN_LENGTH_VALIDATION\n■ Causes:\n■ O subject name contains more than 255 characters\n■ Recomendada actions:\n■ Um subject name com um length greater que 255 characters está não supported.\nContate seu external certificate provider.\nValidation ID: CERTIFICATE_SAN_HOSTNAME_VALIDATION\n■ Causes:\n■ O Subject Alternative Name field in o certificate está não vazio e o\nhostname está não present in o field.\n■ Recomendada actions:\n■ If o certificate Subject Alternative Name está non-empty, garanta que it has\nhost name present in it.\n■ To view Subject Alternative Name run o seguinte comando:\n■ vxsslcmd x509 -text -in end_entity_certificate_file\n■ X509v3 SubjectAlternativeName: DNS:host FQDN DNS:host name\nValidation ID: PRIVATE_KEY_VALIDATION\n■ Causes:\n■ O private key does não match o certificate.\n■ Recomendada actions:\n■ Garanta que o certificate e its corresponding private key estão given.\nValidation ID: CERTIFICATE_SUBJECT_DN_ASCII_VALIDATION\n■ Causes:\n■ Um non-ASCII character foi found in o Subject: subject name de o\ncertificate.\n■ Recomendada actions:\n■ Um certificate subject com characters other than ascii 7-bit characters está não\nsupported. Contate seu external certificate provider.\nValidation ID: CERTIFICATE_CHAIN_VALIDATION_AGAINST_TRUST_STORE\n■ Causes:\n■ Certificatechainverificationcanfailduetomanyreasons.Theonlycommon\nsentence que está displayed está O certificate chain verification\nfalhou. O rest de o erro está displayed com whatever openssl returns.\n■ Recomendada actions:\n■ Garanta que certificate com given subject name está present in o provided\ntrust store.\n■ Review o openssl erro e rectify per o erro text.\nValidation ID: CERTIFICATE_CN_EMPTINESS_VALIDATION\n■ Causes:\n■ O Common Name field in o certificate está vazio.\n■ Recomendada actions:\n■ Garanta que certificate common name está não vazio. Contate seu external\ncertificate provider.\n■ Run o seguinte comando to verifique:\n■ vxsslcmd x509 -subject -in certificate_file\n■ Verifique que o value de CN in o subject está não vazio.\nValidation ID: CERTIFICATES_ORDER\n■ Causes:\n■ O signature de o certificate subject name não é possível be verified com o\npublic key de o current certificate subject name.\n■ Recomendada actions:\n■ If you use um PEM-formatted certificate, garanta que in o certificate arquivo, o\nleaf certificate está present first followed por its issuer, followed por o issuer\nde o leaf’s issuer e so on.\nValidation ID: CERTIFICATE_CHAIN_EXPIRY_VALIDATION\n■ Causes:\n■ O certificate com o subject subject name está expired.\n■ Recomendada actions:\n■ Renew seu certificate ou use um certificate que está currently valid.\n■ To garanta, run o seguinte comando:\n■ vxsslcmd x509 -dates -in certificate_file\nOutput:\nnotBefore=date before which certificate está não valid\nnotAfter=date after which certificate está não valid\nValidation ID: CERTIFICATE_CHAIN_CURRENT_ACTIVE_VALIDATION\n■ Causes:\n■ O certificate com o subject subject name está não yet active.\n■ Recomendada actions:\n■ Use um certificate que está currently valid.\n■ To garanta, run o seguinte comando:\n■ vxsslcmd x509 -dates -in certificate_file\nOutput:\nnotBefore=date before which certificate está não valid\nnotAfter=date after which certificate está não valid\nValidation ID: WINDOWS_CERTIFICATE_STORE_PRIVATE_KEY_VALIDATION\n■ Severity: Fail ou Warn\n■ Causes:\n■ Um warning está given when MANAGE_WIN_CERT_STORE_PRIVATE_KEY está set to\nDisabled in o NetBackup configuration e o NetBackup services estão\npermitted to access o private key.\n■ O verifique fails when MANAGE_WIN_CERT_STORE_PRIVATE_KEY está set to\nDisabled in o NetBackup configuration e o NetBackup services estão\nnão permitted to access o private key.\n■ O verifique fails when o Cryptographic Service Provider (CSP) ou Key\nArmazenamento Provider (KSP) do não support o security descriptors.\n■ Recomendada actions:\n■ SetMANAGE_WIN_CERT_STORE_PRIVATE_KEYtoAutomaticsothatNetBackup\nprivileged services can update o ler permissions para private key para\nNetBackup non-privileged services.\n■ If o validation fails, give NetBackup services permissions to access o\nprivate key. You can run o comando: nbcertcmd\n-setwincertprivkeypermissions -force\n■ If o validation returns um warning, garanta que o NetBackup services have\nreadpermissionstoaccesstheprivatekey.Thepermissionsareresetduring\ncertain operations like certificate renewal ou disaster recovery.\n■ If o validation fails because o Cryptographic Service Provider (CSP) ou\nKey Armazenamento Provider (KSP) do não support o security descriptors, then\nuse um provider que supports o security descriptors.\nRefer to o section Limitations de Windows Certificate Store support when\nNetBackup services estão executando in Local Service account context in o\nNetBackup Security e Encryption Guide para more details.\nValidation ID: USER_INPUT_WIN_CERT_PATH_VALIDATION\n■ Causes:\n■ O certificate com o given subject name não é possível be found.\n■ Recomendada actions:\n■ EnsurethattheWindowscertificatestorecertificatepathisprovidedcorrectly\ne o certificate exists in o given certificate store. Refer to o External\nCAsupportinNetBackupfromtheNetBackupSecurityandEncryptionGuide.\nValidation ID: CERTIFICATE_SAN_CN_HOSTNAME_VALIDATION\n■ Causes:\n■ O Subject Alternative Name field in o certificate está vazio e o host\nname hostname está não present in o Common Name field.\n■ Recomendada actions:\n■ IfthecertificateSubjectAlternativeNameisempty,ensurethattheCommon\nName field has um host name present in it.\n■ To view o Subject Alternative Name, run o seguinte comando:\n■ vxsslcmd x509 -text -in end_entity_certificate_file\n■ X509v3 Subject Alternative Name: DNS: host FQDN DNS:host name\n■ To view Common Name, run o seguinte comando:\n■ vxsslcmd x509 -text -in end_entity_certificate_file\n■ X509v3 Subject Alternative Name: DNS: host FQDN DNS:host name\nValidation ID: USER_INPUT_WIN_CERT_VALIDATION\n■ Causes:\n■ Não é possível abrir o provided certificate store.\n■ Issuer de o certificate está não found.\n■ Certificate com o provided subject está não found.\n■ O host name de o computer não é possível be fetched. [Used com special\nkeyword $hostname]\n■ Certificate está não valid yet.\n■ Certificate está expired.\n■ Private key está não found para o certificate.\n■ O requerido purposes (cliente Authentication & Servidor Authentication) estão\nnão present in o certificate.\n■ Recommendedactions:(ThefollowingactionsshouldbeperformedinWindows\ncertificate store)\n■ Garanta que certificate caminho está in correct format:\nstore-name\\issuer-name\\subject\n■ Checkthecertificate’sValid fromfield.Thevalue(date)shouldbeincurrent\ndate range.\n■ Verifique o certificate’s Valid to field. O value (date) should be in current\ndate range.\n■ Garanta que o private key está present que corresponds to o end entity\ncertificate.\n■ EnsurethattheEnhanced Key UsagefieldcontainsServer Authentication\n(1.3.6.1.5.5.7.3.1)andClient Authentication (1.3.6.1.5.5.7.3.2).\nTodos purpose está also accepted.\nValidation ID: USER_INPUT_CRL_PATH_VALIDATION\n■ Causes:\n■ O CRL caminho está não accessible.\n■ O CRL caminho está vazio.\n■ O CRL caminho contains apenas 0-KB arquivos.\n■ Recomendada actions:\n■ Garanta que o CRL caminho está correct e não vazio.\nValidation ID: USER_INPUT_CRL_PATH_CONTAINS_CRLS\n■ Causes:\n■ O CRL caminho does não contain qualquer CRL arquivos.\n■ Recomendada actions:\n■ Garanta que o CRL caminho está correct e não vazio.\nValidation ID: CRL_FILES_ACCESS_VALIDATION\n■ Causes:\n■ Windows: NetBackup services estão não able to ler o CRL arquivos.\n■ UNIX: NetBackup service usuário está não able to ler o CRL arquivos.\n■ Recomendada actions:\n■ Windows:\n■ Garanta que o Local Service está não negada access to o CRL arquivos.\n■ Garanta que o NetBackup services have access to o CRL arquivos.\n■ Run o icacls comando to garanta o NetBackup services ou Local\nService have ler permissão. Example:\nicacls \n...\n NT SERVICE\\NetBackup Audit Manager:(R)\n...\nNote: This note apenas applicable to Windows systems.\nThis verifique está não applicable para group members if o Local Service e\nou NetBackup service estão members de um group que está given o\npermissionsdenyandorallow.Thevalidationcheckdoesnotdetecttheir\npermissions.\n■ UNIX: Garanta que o service usuário has access to o CRL arquivos.\nValidation ID: CRL_CDP_URL_VALIDATION\n■ Causes:\n■ O CRL Distribution Point in o certificate does não contain valid URLs.\nNetBackup supports apenas HTTP ou HTTPS URLs.\n■ Recomendada actions:\n■ Garanta que o CRL Distribution Point contains valid URLs.\nValidation ID: ALL_CRLS_READABLE\n■ Causes:\n■ CRL arquivos disponível estão não readable ou inválido CRLs.\n■ Recomendada actions:\n■ Garanta que valid CRLs estão disponível in o CRL caminho." + "full_action": "Each failed validation is associated with a validation ID.\nFor each failure, there may be a specific reason and you can carry out certain\ntroubleshootingsteps.ReviewthefollowinglistofvalidationsfortheecaHealthCheck\ncommand.\nValidation ID: USER_INPUT_CERT_PATH_VALIDATION\n■ Causes:\n■ The certificate path is empty.\n■ The file at the specified path filename cannot be accessed.\n■ Recommended actions:\n■ Ensure that the certificate path is not blank.\n■ Ensure that the file has the Read permissions for the corresponding user.\nValidation ID: USER_INPUT_CERTIFICATES_VALIDATION\n■ Causes:\n■ Error in reading the certificate file.\n■ Recommended actions:\n■ Ensure that the certificate file contains a certificate.\n■ Ensure that the certificate file format is one that NetBackup supports. The\nsupported certificate formats are PEM, P7BPEM, P7BDER.\nValidation ID: USER_INPUT_PRIVATE_KEY_PATH_VALIDATION\n■ Causes:\n■ The private key path is empty.\n■ The file at the specified path filename cannot be accessed.\n■ Recommended actions:\n■ Ensure that the private key path is not blank.\n■ Ensure that the file has the Read permissions for the corresponding user.\nValidation ID: USER_INPUT_PRIVATE_KEY_READ_VALIDATION\n■ Causes:\n■ Error in reading the private key: File read failed.\n■ Error in reading the private key: The private key of the external certificate is\nencrypted, but the passphrase is not provided.\n■ Error in reading the private key: The private key of the external certificate is\nencrypted, but the passphrase is blank.\n■ Recommended actions:\n■ Ensure that the private key format or key algorithms format is one of those\nsupported by NetBackup. The supported key formats are PEM and DER.\n■ If the private key is encrypted, ensure that the ECA_KEY_PASSPHRASEFILE or\n-passphraseFile with its value as passphrase file path location is given.\n■ If the private key is encrypted and the passphrase file is given, ensure that\nthe passphrase file is not empty and the passphrase in it is correct.\nValidation ID: USER_INPUT_TRUST_STORE_PATH_VALIDATION\n■ Causes:\n■ The trust store path is empty.\n■ The file at the specified path filename cannot be accessed.\n■ Recommended actions:\n■ Ensure that the trust store path is not blank.\n■ Ensure that the file has the Read permissions for the corresponding user.\nValidation ID: USER_INPUT_TRUST_STORE_VALIDATION\n■ Causes:\n■ Error in reading the trust store path.\n■ Recommended actions:\n■ Ensure that the trust store certificate file contains a trusted certificate.\n■ Ensure that the certificate file format is one that NetBackup supports. The\nsupported certificate formats are PEM, P7BPEM, P7BDER.\nValidation ID: CERTIFICATES_KEYS_ACCESS_VALIDATION\n■ Causes:\n■ Windows:NetBackupservicesarenotabletoreadthecertificate,truststore,\nor private key.\n■ UNIX: NetBackup service user is not able to read the certificate, trust store,\nor private key.\n■ Recommended actions:\n■ Windows:\n■ EnsurethattheLocalServiceisnotdeniedaccesstothecertificate,trust\nstore, or private key.\n■ Ensure that the NetBackup services have access to the certificate, trust\nstore, or private key.\n■ Run the icacls command to ensure the NetBackup services or Local\nService have read permissions. Example:\nicacls \n...\n NT SERVICE\\NetBackup Audit Manager:(R)\n...\nNote: This note only applicable to Windows systems.\nThis check is not applicable for group members if the Local Service and\nor NetBackup service are members of a group that is given the\npermissionsdenyandorallow.Thevalidationcheckdoesnotdetecttheir\npermissions.\n■ UNIX:\n■ Ensure that the NetBackup service user has access to the certificates,\nthe private key, and the passphrase file.\nValidation ID: LEAF_CERTIFICATE_ENHANCED_KEY_USAGE_VALIDATION\n■ Causes:\n■ The required extended key usages are not available in the given certificate.\n■ Recommended actions:\n■ Execute the following command:\n■ For Windows:\n■ install_path\\bin\\goodies\\vxsslcmd.exe x509 -text -in\nend_entity_certificate\n■ For UNIX:\n■ install_path/bin/goodies/vxsslcmdx509-text-inend_entity_certificate\n■ If the certificate has a X509v3 Key Usage extension present, it must include\nthe following key usage purposes:\n■ Forthewebservercertificate:AtleastoneoftheDigitalSignatureorKey\nEncipherment should be present.\n■ For a NetBackup host certificate: Digital Signature purpose should be\npresent. Key Encipherment may or may not be present.\n■ For a certificate that is used for both web server and NetBackup host:\nDigital Signature purpose should be present. Key Encipherment may or\nmay not be present.\n■ The certificate may have other key usage purposes listed in addition to\nthe purposes specified here. These additional purposes are ignored.\n■ The X509v3 Key Usage extension may be either critical or non-critical.\n■ A certificate without a X509v3 Key Usage extension is also usable with\nNetBackup.\n■ If the certificate has a X509v3 Extended Key Usage extension present, it\nmust include the following key usage purposes:\n■ For the web server certificate: TLS Web Server Authentication.\n■ For a NetBackup host certificate: TLS Web Server Authentication and\nTLS Web Client Authentication.\n■ For a certificate that is used for both web server and NetBackup host:\nTLS Web Server Authentication and TLS Web Client Authentication.\n■ The certificate may have other key usage purposes listed in addition to\nthe purposes specified here. These additional purposes are ignored.\n■ The X509v3 Extended Key Usage extension may be either critical or\nnon-critical.\n■ AcertificatewithoutaX509v3ExtendedKeyUsageextensionisalsousable\nwith NetBackup.\n■ If the certificate doesn’t meet the requirements that are listed in this\nRecommend actions section, contact your certificate provider to obtain a\nnew certificate.\nValidation ID: CERTIFICATE_SUBJECT_DN_LENGTH_VALIDATION\n■ Causes:\n■ The subject name contains more than 255 characters\n■ Recommended actions:\n■ A subject name with a length greater that 255 characters is not supported.\nContact your external certificate provider.\nValidation ID: CERTIFICATE_SAN_HOSTNAME_VALIDATION\n■ Causes:\n■ The Subject Alternative Name field in the certificate is not empty and the\nhostname is not present in the field.\n■ Recommended actions:\n■ If the certificate Subject Alternative Name is non-empty, ensure that it has\nhost name present in it.\n■ To view Subject Alternative Name run the following command:\n■ vxsslcmd x509 -text -in end_entity_certificate_file\n■ X509v3 SubjectAlternativeName: DNS:host FQDN DNS:host name\nValidation ID: PRIVATE_KEY_VALIDATION\n■ Causes:\n■ The private key does not match the certificate.\n■ Recommended actions:\n■ Ensure that the certificate and its corresponding private key are given.\nValidation ID: CERTIFICATE_SUBJECT_DN_ASCII_VALIDATION\n■ Causes:\n■ A non-ASCII character was found in the Subject: subject name of the\ncertificate.\n■ Recommended actions:\n■ A certificate subject with characters other than ascii 7-bit characters is not\nsupported. Contact your external certificate provider.\nValidation ID: CERTIFICATE_CHAIN_VALIDATION_AGAINST_TRUST_STORE\n■ Causes:\n■ Certificatechainverificationcanfailduetomanyreasons.Theonlycommon\nsentence that is displayed is The certificate chain verification\nfailed. The rest of the error is displayed with whatever openssl returns.\n■ Recommended actions:\n■ Ensure that certificate with given subject name is present in the provided\ntrust store.\n■ Review the openssl error and rectify per the error text.\nValidation ID: CERTIFICATE_CN_EMPTINESS_VALIDATION\n■ Causes:\n■ The Common Name field in the certificate is empty.\n■ Recommended actions:\n■ Ensure that certificate common name is not empty. Contact your external\ncertificate provider.\n■ Run the following command to verify:\n■ vxsslcmd x509 -subject -in certificate_file\n■ Verify that the value of CN in the subject is not empty.\nValidation ID: CERTIFICATES_ORDER\n■ Causes:\n■ The signature of the certificate subject name cannot be verified with the\npublic key of the current certificate subject name.\n■ Recommended actions:\n■ If you use a PEM-formatted certificate, ensure that in the certificate file, the\nleaf certificate is present first followed by its issuer, followed by the issuer\nof the leaf’s issuer and so on.\nValidation ID: CERTIFICATE_CHAIN_EXPIRY_VALIDATION\n■ Causes:\n■ The certificate with the subject subject name is expired.\n■ Recommended actions:\n■ Renew your certificate or use a certificate that is currently valid.\n■ To ensure, run the following command:\n■ vxsslcmd x509 -dates -in certificate_file\nOutput:\nnotBefore=date before which certificate is not valid\nnotAfter=date after which certificate is not valid\nValidation ID: CERTIFICATE_CHAIN_CURRENT_ACTIVE_VALIDATION\n■ Causes:\n■ The certificate with the subject subject name is not yet active.\n■ Recommended actions:\n■ Use a certificate that is currently valid.\n■ To ensure, run the following command:\n■ vxsslcmd x509 -dates -in certificate_file\nOutput:\nnotBefore=date before which certificate is not valid\nnotAfter=date after which certificate is not valid\nValidation ID: WINDOWS_CERTIFICATE_STORE_PRIVATE_KEY_VALIDATION\n■ Severity: Fail or Warn\n■ Causes:\n■ A warning is given when MANAGE_WIN_CERT_STORE_PRIVATE_KEY is set to\nDisabled in the NetBackup configuration and the NetBackup services are\npermitted to access the private key.\n■ The check fails when MANAGE_WIN_CERT_STORE_PRIVATE_KEY is set to\nDisabled in the NetBackup configuration and the NetBackup services are\nnot permitted to access the private key.\n■ The check fails when the Cryptographic Service Provider (CSP) or Key\nStorage Provider (KSP) do not support the security descriptors.\n■ Recommended actions:\n■ SetMANAGE_WIN_CERT_STORE_PRIVATE_KEYtoAutomaticsothatNetBackup\nprivileged services can update the read permissions for private key for\nNetBackup non-privileged services.\n■ If the validation fails, give NetBackup services permissions to access the\nprivate key. You can run the command: nbcertcmd\n-setwincertprivkeypermissions -force\n■ If the validation returns a warning, ensure that the NetBackup services have\nreadpermissionstoaccesstheprivatekey.Thepermissionsareresetduring\ncertain operations like certificate renewal or disaster recovery.\n■ If the validation fails because the Cryptographic Service Provider (CSP) or\nKey Storage Provider (KSP) do not support the security descriptors, then\nuse a provider that supports the security descriptors.\nRefer to the section Limitations of Windows Certificate Store support when\nNetBackup services are running in Local Service account context in the\nNetBackup Security and Encryption Guide for more details.\nValidation ID: USER_INPUT_WIN_CERT_PATH_VALIDATION\n■ Causes:\n■ The certificate with the given subject name cannot be found.\n■ Recommended actions:\n■ EnsurethattheWindowscertificatestorecertificatepathisprovidedcorrectly\nand the certificate exists in the given certificate store. Refer to the External\nCAsupportinNetBackupfromtheNetBackupSecurityandEncryptionGuide.\nValidation ID: CERTIFICATE_SAN_CN_HOSTNAME_VALIDATION\n■ Causes:\n■ The Subject Alternative Name field in the certificate is empty and the host\nname hostname is not present in the Common Name field.\n■ Recommended actions:\n■ IfthecertificateSubjectAlternativeNameisempty,ensurethattheCommon\nName field has a host name present in it.\n■ To view the Subject Alternative Name, run the following command:\n■ vxsslcmd x509 -text -in end_entity_certificate_file\n■ X509v3 Subject Alternative Name: DNS: host FQDN DNS:host name\n■ To view Common Name, run the following command:\n■ vxsslcmd x509 -text -in end_entity_certificate_file\n■ X509v3 Subject Alternative Name: DNS: host FQDN DNS:host name\nValidation ID: USER_INPUT_WIN_CERT_VALIDATION\n■ Causes:\n■ Cannot open the provided certificate store.\n■ Issuer of the certificate is not found.\n■ Certificate with the provided subject is not found.\n■ The host name of the computer cannot be fetched. [Used with special\nkeyword $hostname]\n■ Certificate is not valid yet.\n■ Certificate is expired.\n■ Private key is not found for the certificate.\n■ The required purposes (Client Authentication & Server Authentication) are\nnot present in the certificate.\n■ Recommendedactions:(ThefollowingactionsshouldbeperformedinWindows\ncertificate store)\n■ Ensure that certificate path is in correct format:\nstore-name\\issuer-name\\subject\n■ Checkthecertificate’sValid fromfield.Thevalue(date)shouldbeincurrent\ndate range.\n■ Check the certificate’s Valid to field. The value (date) should be in current\ndate range.\n■ Ensure that the private key is present that corresponds to the end entity\ncertificate.\n■ EnsurethattheEnhanced Key UsagefieldcontainsServer Authentication\n(1.3.6.1.5.5.7.3.1)andClient Authentication (1.3.6.1.5.5.7.3.2).\nAll purpose is also accepted.\nValidation ID: USER_INPUT_CRL_PATH_VALIDATION\n■ Causes:\n■ The CRL path is not accessible.\n■ The CRL path is empty.\n■ The CRL path contains only 0-KB files.\n■ Recommended actions:\n■ Ensure that the CRL path is correct and not empty.\nValidation ID: USER_INPUT_CRL_PATH_CONTAINS_CRLS\n■ Causes:\n■ The CRL path does not contain any CRL files.\n■ Recommended actions:\n■ Ensure that the CRL path is correct and not empty.\nValidation ID: CRL_FILES_ACCESS_VALIDATION\n■ Causes:\n■ Windows: NetBackup services are not able to read the CRL files.\n■ UNIX: NetBackup service user is not able to read the CRL files.\n■ Recommended actions:\n■ Windows:\n■ Ensure that the Local Service is not denied access to the CRL files.\n■ Ensure that the NetBackup services have access to the CRL files.\n■ Run the icacls command to ensure the NetBackup services or Local\nService have read permission. Example:\nicacls \n...\n NT SERVICE\\NetBackup Audit Manager:(R)\n...\nNote: This note only applicable to Windows systems.\nThis check is not applicable for group members if the Local Service and\nor NetBackup service are members of a group that is given the\npermissionsdenyandorallow.Thevalidationcheckdoesnotdetecttheir\npermissions.\n■ UNIX: Ensure that the service user has access to the CRL files.\nValidation ID: CRL_CDP_URL_VALIDATION\n■ Causes:\n■ The CRL Distribution Point in the certificate does not contain valid URLs.\nNetBackup supports only HTTP or HTTPS URLs.\n■ Recommended actions:\n■ Ensure that the CRL Distribution Point contains valid URLs.\nValidation ID: ALL_CRLS_READABLE\n■ Causes:\n■ CRL files available are not readable or invalid CRLs.\n■ Recommended actions:\n■ Ensure that valid CRLs are available in the CRL path." }, "8787": { "code": 8787, "desc": "ThespecifiedprivatekeyoftheexternalcertificateisnotFIPS-compliant.", - "first_action": "Garanta que o private key para o external certificate está", - "full_action": "Garanta que o private key para o external certificate está\ngenerated usando FIPS-compliant algorithms." + "first_action": "Ensure that the private key for the external certificate is", + "full_action": "Ensure that the private key for the external certificate is\ngenerated using FIPS-compliant algorithms." }, "8788": { "code": 8788, - "desc": "O Cryptographic Service Provider ou key armazenamento provider does não support security descriptors.", - "first_action": "Use um Cryptographic Service Provider ou key armazenamento", - "full_action": "Use um Cryptographic Service Provider ou key armazenamento\nprovider que supports security descriptors. Alternatively, use o Local System ou\num administrator account to run o NetBackup non-privileged services.\nPara more informação about changing o service usuário, veja o NetBackup Security\ne Encryption Guide." + "desc": "The Cryptographic Service Provider or key storage provider does not support security descriptors.", + "first_action": "Use a Cryptographic Service Provider or key storage", + "full_action": "Use a Cryptographic Service Provider or key storage\nprovider that supports security descriptors. Alternatively, use the Local System or\nan administrator account to run the NetBackup non-privileged services.\nFor more information about changing the service user, see the NetBackup Security\nand Encryption Guide." }, "8789": { "code": 8789, - "desc": "Falhou to acquire private key corresponding to certificate in Windows certificate store.", - "first_action": "1. Use um certificate que has um private key que está associated com it.", - "full_action": "Executar o seguinte:\n1. Use um certificate que has um private key que está associated com it.\n2. Verifique if o usuário has permissions to ler o private key." + "desc": "Failed to acquire private key corresponding to certificate in Windows certificate store.", + "first_action": "1. Use a certificate that has a private key that is associated with it.", + "full_action": "Perform the following:\n1. Use a certificate that has a private key that is associated with it.\n2. Check if the user has permissions to read the private key." }, "8790": { "code": 8790, - "desc": "Falhou to update security descriptor de private key corresponding to certificate in Windows certificate store.", + "desc": "Failed to update security descriptor of private key corresponding to certificate in Windows certificate store.", "first_action": "1. Checkiftheuserhaspermissionstomodifythesecuritydescriptoroftheprivate", - "full_action": "Executar o seguinte:\n1. Checkiftheuserhaspermissionstomodifythesecuritydescriptoroftheprivate\nkey.\n2. Verifique if o Cryptographic Service Provider ou key armazenamento provider supports\nsecurity descriptors. Use um provider que supports security descriptors ou o\nLocalSystemoranadministratoraccounttoruntheNetBackupnon-privileged\nservices.\nPara more informação about changing o service usuário, veja o NetBackup\nSecurity e Encryption Guide." + "full_action": "Perform the following:\n1. Checkiftheuserhaspermissionstomodifythesecuritydescriptoroftheprivate\nkey.\n2. Check if the Cryptographic Service Provider or key storage provider supports\nsecurity descriptors. Use a provider that supports security descriptors or the\nLocalSystemoranadministratoraccounttoruntheNetBackupnon-privileged\nservices.\nFor more information about changing the service user, see the NetBackup\nSecurity and Encryption Guide." }, "8791": { "code": 8791, - "desc": "Falhou to ler o security descriptor de private key corresponding to certificate in Windows certificate store.", - "first_action": "1. Verifique if o usuário reading o security descriptor de o private key has", - "full_action": "Executar o seguinte:\n1. Verifique if o usuário reading o security descriptor de o private key has\npermissions to ler it.\n2. Verifique if o Cryptographic Service Provider ou key armazenamento provider supports\nsecurity descriptors. Use um provider que supports security descriptors ou o\nLocalSystemoranadministratoraccounttoruntheNetBackupnon-privileged\nservices.\nPara more informação about changing o service usuário, veja o NetBackup\nSecurity e Encryption Guide." + "desc": "Failed to read the security descriptor of private key corresponding to certificate in Windows certificate store.", + "first_action": "1. Check if the user reading the security descriptor of the private key has", + "full_action": "Perform the following:\n1. Check if the user reading the security descriptor of the private key has\npermissions to read it.\n2. Check if the Cryptographic Service Provider or key storage provider supports\nsecurity descriptors. Use a provider that supports security descriptors or the\nLocalSystemoranadministratoraccounttoruntheNetBackupnon-privileged\nservices.\nFor more information about changing the service user, see the NetBackup\nSecurity and Encryption Guide." }, "8792": { "code": 8792, "desc": "FailedtosettheattributesoftheprivatekeyorcertificateinsideWindows certificate store.", - "first_action": "1. Verifique if o certificate está valid.", - "full_action": "Executar o seguinte:\n1. Verifique if o certificate está valid.\n2. Verifique if o usuário has permissions to gravar o attributes de private key." + "first_action": "1. Check if the certificate is valid.", + "full_action": "Perform the following:\n1. Check if the certificate is valid.\n2. Check if the user has permissions to write the attributes of private key." }, "8793": { "code": 8793, - "desc": "Falhou to ler o attributes from o private key ou certificate inside Windows certificate store.", - "first_action": "1. Verifique if o certificate está valid.", - "full_action": "Executar o seguinte:\n1. Verifique if o certificate está valid.\n2. Verifique if o usuário has permissions to ler o attributes de private key." + "desc": "Failed to read the attributes from the private key or certificate inside Windows certificate store.", + "first_action": "1. Check if the certificate is valid.", + "full_action": "Perform the following:\n1. Check if the certificate is valid.\n2. Check if the user has permissions to read the attributes of private key." }, "8794": { "code": 8794, - "desc": "NetBackup está não enabled to manage o private key corresponding to certificate in o Windows certificate store. Verifique NetBackup configuration.", - "first_action": "Change o value de o", - "full_action": "Change o value de o\nMANAGE_WIN_CERT_STORE_PRIVATE_KEY in o NetBackup configuration to\nAutomatic." + "desc": "NetBackup is not enabled to manage the private key corresponding to certificate in the Windows certificate store. Check NetBackup configuration.", + "first_action": "Change the value of the", + "full_action": "Change the value of the\nMANAGE_WIN_CERT_STORE_PRIVATE_KEY in the NetBackup configuration to\nAutomatic." }, "8798": { "code": 8798, - "desc": "O certificate de o host não é possível be validated because FIPS mode está enabled.", - "first_action": "Providerclass e -providerpath estão needed como o trust store está um BCFKS", - "full_action": "To overcome this problema, um temporary FIPS-compliant\ntrust store has been introduced in NetBackup 10.0 which está located at:\ninstall_path/var/global/wsl/credentials/cacerts.bcfks\nWhen um NetBackup primary servidor está executando in FIPS mode, administrators now\nneed to garanta que this trust store has o remote entity’s CA certificate already\ndisponível in it. This verifique must be done before o APIs estão called to fetch o CA\ncertificate de remote entity. NetBackup Web Services API workflows use this trust\nstore to verifique o identity de o remote entity NetBackup communicates com.\nContate seu NetBackup Administrator to populate o trust store com o target\nserver’s CA certificate para validating o server’s authenticity.\nNote: O seguinte steps need to be performed on o NetBackup primary servidor\nwhich está configurado to run in FIPS mode.\nO keytool comando que está disponível on o primary servidor, can be used to\nimport o CA certificates into o trust store\ninstall_path/var/global/wsl/credentials/cacerts.bcfks. O options\n-providerclass e -providerpath estão needed como o trust store está um BCFKS\nformat trust store, o apenas fully FIPS-compliant store format.\nO remote entity’s CA certificate must be disponível in um arquivo in um PEM encoded\nformat. O CA certificate must be copied over to o NetBackup primary servidor\nexecutando in FIPS mode.\nO steps to export o remote entity’s CA certificate into um PEM format arquivo can\nvary. One de o ways to get o informação está por usando o seguinte keytool\ncommands. O NetBackup administrator needs to refer to o documentation de\ntheproduct/sub-systemNetBackupisintendedtobeintegrated.Forexample,while\nadding VRP servidor in NetBackup, steps to get o VRP server’s CA certificate in um\nPEM format will be disponível in VRP documentation.\nUse o seguinte keytool commands to import o CA certificate into\ninstall_path/var/global/wsl/credentials/cacerts.bcfks:\nWindows:\ninstall_path\\java\\jre\\bin\\keytool -storetype BCFKS\n-providerpath install_path\\wmc\\webserver\\lib\\ccj.jar\n-providerclass com.safelogic.cryptocomply.jcajce.provider.CryptoComplyFipsProvider\n-importcert -trustcacerts -arquivo \n-keystore install_path\\var\\global\\wsl\\credentials\\cacerts.bcfks\n-storepass \n-alias \nUNIX:\n/usr/openv/java/jre/bin/keytool -storetype BCFKS\n-providerpath /usr/openv/wmc/webserver/lib/ccj.jar\n-providerclass com.safelogic.cryptocomply.jcajce.provider.CryptoComplyFipsProvider\n-importcert -trustcacerts -arquivo \n-keystore install_path/var/global/wsl/credentials/cacerts.bcfks\n-storepass \n-alias \nNetBackupdoesn’tneedtheseCAcertificatesafterthebootstrappingcallsaredone\n(subsequentAPIcallsmakeuseofadifferenttruststorethathastheseCAcertificate\nentradas populated). Cohesity recommends que entradas estão cleaned up once o\nremote entity está configurado in NetBackup. To excluir um entry from o temporary\nkeystore:\nWindows:\ninstall_path\\java\\jre\\bin\\keytool -storetype BCFKS\n-providerpath install_path\\wmc\\webserver\\lib\\ccj.jar\n-providerclass com.safelogic.cryptocomply.jcajce.provider.CryptoComplyFipsProvider\n-importcert -trustcacerts -arquivo \n-keystore install_path\\var\\global\\wsl\\credentials\\cacerts.bcfks\n-storepass \n-excluir -alias \nUNIX:\n/usr/openv/java/jre/bin/keytool -storetype BCFKS\n-providerpath /usr/openv/wmc/webserver/lib/ccj.jar\n-providerclass com.safelogic.cryptocomply.jcajce.provider.CryptoComplyFipsProvider\n-keystore /usr/openv/var/global/wsl/credentials/cacerts.bcfks\n-storepass -excluir\n-alias \nExecutar o seguinte procedure to configure um trusted primary servidor.\nTo configure um trusted primary servidor\n1 Executar o seguinte on o destination primary servidor:\nExport o CA certificate from um BCFKS format trust store usando o keytool\ncomando:\n/usr/openv/java/jre/bin/keytool -storetype BCFKS\n-providerpath /usr/openv/wmc/lib/ccj.jar\n-providerclass com.safelogic.cryptocomply.jcajce.provider.CryptoComplyFipsProvider\n-exportcert -alias \n-keystore -storepass -rfc\n-arquivo \nExample:\nWindows:\ninstall_path\\jre\\bin\\keytool\n-providerpath install_path\\wmc\\lib\\ccj.jar\n-providerclass com.safelogic.cryptocomply.jcajce.provider.CryptoComplyFipsProvider\n-storetype BCFKS -export -alias nbwmc -rfc\n-arquivo \n-keystore install_path\\var\\global\\wsl\\credentials\\nbwebservice.bcfks\n-storepass \nUNIX:\n/usr/openv/java/jre/bin/keytool -providerpath /usr/openv/wmc/lib/ccj.jar\n-providerclass com.safelogic.cryptocomply.jcajce.provider.CryptoComplyFipsProvider\n-storetype BCFKS -export -alias nbwmc -rfc\n-arquivo /usr/openv/var/global /wsl/credentials/nbwmc.pem\n-keystore /usr/openv/var/global/wsl/credentials/nbwebservice.bcfks\n-storepass \n2 Copy o PEM arquivo que está created como part de o step 1 comando run, from o\ndestination primary servidor to source primary servidor.\n3 On o source primary servidor, import o CA certificate from o PEM arquivo to\ninstall_path/var/global/wsl/credentials/cacerts.bcfks:\nWindows:\ninstall_path\\java\\jre\\bin\\keytool -storetype BCFKS\n-providerpath install_path\\wmc\\webserver\\lib\\ccj.jar\n-providerclass com.safelogic.cryptocomply.jcajce.provider.CryptoComplyFipsProvider\n-importcert -trustcacerts -arquivo \n-keystore install_path\\var\\global\\wsl\\credentials\\cacerts.bcfks\n-storepass \n-alias \nUNIX:\n/usr/openv/java/jre/bin/keytool -storetype BCFKS\n-providerpath /usr/openv/wmc/webserver/lib/ccj.jar\n-providerclass com.safelogic.cryptocomply.jcajce.provider.CryptoComplyFipsProvider\n-importcert -trustcacerts -arquivo \n-keystore install_path/var/global/wsl/credentials/cacerts.bcfks\n-storepass \n-alias \n4 (Conditional)ToimporttheCAcertificateofsourceprimaryservertodestination\nprimary servidor, you must follow steps 1, 2, e 3. Para step 1, o destination\nprimaryserverbecomessourceandsourcebecomesdestination.Thischange\nensures que both primary servers have each other’s CA certificate disponível\nat install_path/var/global/wsl/credentials/cacerts.bcfks.\nIf o remote entity has um JKS formatted keystore, o seguinte comando can\nbe used to export o CA certificate in PEM format.\nExporting um CA certificate from um JKS format trust store usando o keytool\ncomando:\n/usr/openv/java/jre/bin/keytool -exportcert\n-alias \n-keystore \n-storepass -rfc\n-arquivo " + "desc": "The certificate of the host cannot be validated because FIPS mode is enabled.", + "first_action": "Providerclass and -providerpath are needed as the trust store is a BCFKS", + "full_action": "To overcome this problem, a temporary FIPS-compliant\ntrust store has been introduced in NetBackup 10.0 which is located at:\ninstall_path/var/global/wsl/credentials/cacerts.bcfks\nWhen a NetBackup primary server is running in FIPS mode, administrators now\nneed to ensure that this trust store has the remote entity’s CA certificate already\navailable in it. This check must be done before the APIs are called to fetch the CA\ncertificate of remote entity. NetBackup Web Services API workflows use this trust\nstore to verify the identity of the remote entity NetBackup communicates with.\nContact your NetBackup Administrator to populate the trust store with the target\nserver’s CA certificate for validating the server’s authenticity.\nNote: The following steps need to be performed on the NetBackup primary server\nwhich is configured to run in FIPS mode.\nThe keytool command that is available on the primary server, can be used to\nimport the CA certificates into the trust store\ninstall_path/var/global/wsl/credentials/cacerts.bcfks. The options\n-providerclass and -providerpath are needed as the trust store is a BCFKS\nformat trust store, the only fully FIPS-compliant store format.\nThe remote entity’s CA certificate must be available in a file in a PEM encoded\nformat. The CA certificate must be copied over to the NetBackup primary server\nrunning in FIPS mode.\nThe steps to export the remote entity’s CA certificate into a PEM format file can\nvary. One of the ways to get the information is by using the following keytool\ncommands. The NetBackup administrator needs to refer to the documentation of\ntheproduct/sub-systemNetBackupisintendedtobeintegrated.Forexample,while\nadding VRP server in NetBackup, steps to get the VRP server’s CA certificate in a\nPEM format will be available in VRP documentation.\nUse the following keytool commands to import the CA certificate into\ninstall_path/var/global/wsl/credentials/cacerts.bcfks:\nWindows:\ninstall_path\\java\\jre\\bin\\keytool -storetype BCFKS\n-providerpath install_path\\wmc\\webserver\\lib\\ccj.jar\n-providerclass com.safelogic.cryptocomply.jcajce.provider.CryptoComplyFipsProvider\n-importcert -trustcacerts -file \n-keystore install_path\\var\\global\\wsl\\credentials\\cacerts.bcfks\n-storepass \n-alias \nUNIX:\n/usr/openv/java/jre/bin/keytool -storetype BCFKS\n-providerpath /usr/openv/wmc/webserver/lib/ccj.jar\n-providerclass com.safelogic.cryptocomply.jcajce.provider.CryptoComplyFipsProvider\n-importcert -trustcacerts -file \n-keystore install_path/var/global/wsl/credentials/cacerts.bcfks\n-storepass \n-alias \nNetBackupdoesn’tneedtheseCAcertificatesafterthebootstrappingcallsaredone\n(subsequentAPIcallsmakeuseofadifferenttruststorethathastheseCAcertificate\nentries populated). Cohesity recommends that entries are cleaned up once the\nremote entity is configured in NetBackup. To delete an entry from the temporary\nkeystore:\nWindows:\ninstall_path\\java\\jre\\bin\\keytool -storetype BCFKS\n-providerpath install_path\\wmc\\webserver\\lib\\ccj.jar\n-providerclass com.safelogic.cryptocomply.jcajce.provider.CryptoComplyFipsProvider\n-importcert -trustcacerts -file \n-keystore install_path\\var\\global\\wsl\\credentials\\cacerts.bcfks\n-storepass \n-delete -alias \nUNIX:\n/usr/openv/java/jre/bin/keytool -storetype BCFKS\n-providerpath /usr/openv/wmc/webserver/lib/ccj.jar\n-providerclass com.safelogic.cryptocomply.jcajce.provider.CryptoComplyFipsProvider\n-keystore /usr/openv/var/global/wsl/credentials/cacerts.bcfks\n-storepass -delete\n-alias \nPerform the following procedure to configure a trusted primary server.\nTo configure a trusted primary server\n1 Perform the following on the destination primary server:\nExport the CA certificate from a BCFKS format trust store using the keytool\ncommand:\n/usr/openv/java/jre/bin/keytool -storetype BCFKS\n-providerpath /usr/openv/wmc/lib/ccj.jar\n-providerclass com.safelogic.cryptocomply.jcajce.provider.CryptoComplyFipsProvider\n-exportcert -alias \n-keystore -storepass -rfc\n-file \nExample:\nWindows:\ninstall_path\\jre\\bin\\keytool\n-providerpath install_path\\wmc\\lib\\ccj.jar\n-providerclass com.safelogic.cryptocomply.jcajce.provider.CryptoComplyFipsProvider\n-storetype BCFKS -export -alias nbwmc -rfc\n-file \n-keystore install_path\\var\\global\\wsl\\credentials\\nbwebservice.bcfks\n-storepass \nUNIX:\n/usr/openv/java/jre/bin/keytool -providerpath /usr/openv/wmc/lib/ccj.jar\n-providerclass com.safelogic.cryptocomply.jcajce.provider.CryptoComplyFipsProvider\n-storetype BCFKS -export -alias nbwmc -rfc\n-file /usr/openv/var/global /wsl/credentials/nbwmc.pem\n-keystore /usr/openv/var/global/wsl/credentials/nbwebservice.bcfks\n-storepass \n2 Copy the PEM file that is created as part of the step 1 command run, from the\ndestination primary server to source primary server.\n3 On the source primary server, import the CA certificate from the PEM file to\ninstall_path/var/global/wsl/credentials/cacerts.bcfks:\nWindows:\ninstall_path\\java\\jre\\bin\\keytool -storetype BCFKS\n-providerpath install_path\\wmc\\webserver\\lib\\ccj.jar\n-providerclass com.safelogic.cryptocomply.jcajce.provider.CryptoComplyFipsProvider\n-importcert -trustcacerts -file \n-keystore install_path\\var\\global\\wsl\\credentials\\cacerts.bcfks\n-storepass \n-alias \nUNIX:\n/usr/openv/java/jre/bin/keytool -storetype BCFKS\n-providerpath /usr/openv/wmc/webserver/lib/ccj.jar\n-providerclass com.safelogic.cryptocomply.jcajce.provider.CryptoComplyFipsProvider\n-importcert -trustcacerts -file \n-keystore install_path/var/global/wsl/credentials/cacerts.bcfks\n-storepass \n-alias \n4 (Conditional)ToimporttheCAcertificateofsourceprimaryservertodestination\nprimary server, you must follow steps 1, 2, and 3. For step 1, the destination\nprimaryserverbecomessourceandsourcebecomesdestination.Thischange\nensures that both primary servers have each other’s CA certificate available\nat install_path/var/global/wsl/credentials/cacerts.bcfks.\nIf the remote entity has a JKS formatted keystore, the following command can\nbe used to export the CA certificate in PEM format.\nExporting a CA certificate from a JKS format trust store using the keytool\ncommand:\n/usr/openv/java/jre/bin/keytool -exportcert\n-alias \n-keystore \n-storepass -rfc\n-file " }, "8799": { "code": 8799, - "desc": "O validation de o certificate signing algorithm falhou.", - "first_action": "Contate seu Certificate Authority to generate e issue", - "full_action": "Contate seu Certificate Authority to generate e issue\num certificate que está signed usando non-deprecated algorithm." + "desc": "The validation of the certificate signing algorithm failed.", + "first_action": "Contact your Certificate Authority to generate and issue", + "full_action": "Contact your Certificate Authority to generate and issue\na certificate that is signed using non-deprecated algorithm." }, "8800": { "code": 8800, - "desc": "Communication com EMM falhou.", - "first_action": "Garanta que o nbemm service está executando.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Garanta que o nbemm service está executando.\n■ Restart nbemm ou o NetBackup Web Management Console (nbwmc) e retry\no request.\n■ ExaminetheunifiedloggingfilesontheNetBackupmasterserverforthenbemmm\n(OID 111) service e o NetBackup web services. Unified logging está written\nto /usr/openv/logs (UNIX) ou to install_path\\NetBackup\\logs (Windows).\nVeja o NetBackup Troubleshooting Guide e o NetBackup Logging\nReference Guide para details on troubleshooting o web services e on their\nlogs.\n■ If o problema persists, contate Cohesity Technical Support." + "desc": "Communication with EMM failed.", + "first_action": "Ensure that the nbemm service is running.", + "full_action": "Do the following, as appropriate:\n■ Ensure that the nbemm service is running.\n■ Restart nbemm or the NetBackup Web Management Console (nbwmc) and retry\nthe request.\n■ ExaminetheunifiedloggingfilesontheNetBackupmasterserverforthenbemmm\n(OID 111) service and the NetBackup web services. Unified logging is written\nto /usr/openv/logs (UNIX) or to install_path\\NetBackup\\logs (Windows).\nSee the NetBackup Troubleshooting Guide and the NetBackup Logging\nReference Guide for details on troubleshooting the web services and on their\nlogs.\n■ If the problem persists, contact Cohesity Technical Support." }, "8813": { "code": 8813, - "desc": "Policy attributes must be specified usando o property named 'policy'.", - "first_action": "Por favor specify o policy attributes, including qualquer", - "full_action": "Por favor specify o policy attributes, including qualquer\nschedules, clients, e backup selections within o ‘policy’ property in o JSON\npayload. Veja o NetBackup REST API documentation para details about o Policy\nAPI JSON schema." + "desc": "Policy attributes must be specified using the property named 'policy'.", + "first_action": "Please specify the policy attributes, including any", + "full_action": "Please specify the policy attributes, including any\nschedules, clients, and backup selections within the ‘policy’ property in the JSON\npayload. See the NetBackup REST API documentation for details about the Policy\nAPI JSON schema." }, "8814": { "code": 8814, - "desc": "Por favor enter um valid Hyper-V machine name.", + "desc": "Please enter a valid Hyper-V machine name.", "first_action": "EnsurethattheNetBackupclientisinstalledontheHyper-V", - "full_action": "EnsurethattheNetBackupclientisinstalledontheHyper-V\nservidor e que o NetBackup master servidor can communicate com it." + "full_action": "EnsurethattheNetBackupclientisinstalledontheHyper-V\nserver and that the NetBackup master server can communicate with it." }, "8816": { "code": 8816, - "desc": "O ID in o URL does não match o ID in o body.", - "first_action": "Garanta que o ID in o request URL matches o ID in", - "full_action": "Garanta que o ID in o request URL matches o ID in\no request body." + "desc": "The ID in the URL does not match the ID in the body.", + "first_action": "Ensure that the ID in the request URL matches the ID in", + "full_action": "Ensure that the ID in the request URL matches the ID in\nthe request body." }, "8817": { "code": 8817, - "desc": "O credential name que you provided already exists.", + "desc": "The credential name that you provided already exists.", "first_action": "Enteradifferentvalidcredentialnameintherequestbody.", - "full_action": "Enteradifferentvalidcredentialnameintherequestbody.\nDo não leave qualquer spaces between characters. O name must não exceed 256\ncharacters." + "full_action": "Enteradifferentvalidcredentialnameintherequestbody.\nDo not leave any spaces between characters. The name must not exceed 256\ncharacters." }, "8818": { "code": 8818, - "desc": "Inválido policy name.", - "first_action": "Veja o NetBackup Administrator’s Guide Volume I para details on o naming", - "full_action": "Enter um valid name para o policy according to o naming\nrules. Use apenas alphabetic (ASCII A-Z e a-z), numeric (0-9), plus (+), minus (-),\nunderscore(_), ou period (.) characters. Do não use um minus (-) ou period (.) como o\nfirst ou last character. Do não leave qualquer spaces between characters.\nPara more informação on policy names:\n■ Veja o NetBackup Administrator’s Guide Volume I para details on o naming\nconventions.\n■ You may also refer to o Article: 100016372 in o Support Knowledge Base\npara more informação about policy naming." + "desc": "Invalid policy name.", + "first_action": "See the NetBackup Administrator’s Guide Volume I for details on the naming", + "full_action": "Enter a valid name for the policy according to the naming\nrules. Use only alphabetic (ASCII A-Z and a-z), numeric (0-9), plus (+), minus (-),\nunderscore(_), or period (.) characters. Do not use a minus (-) or period (.) as the\nfirst or last character. Do not leave any spaces between characters.\nFor more information on policy names:\n■ See the NetBackup Administrator’s Guide Volume I for details on the naming\nconventions.\n■ You may also refer to the Article: 100016372 in the Support Knowledge Base\nfor more information about policy naming." }, "8819": { "code": 8819, - "desc": "Inválido schedule name.", - "first_action": "Enter um valid name para o policy according to o naming", - "full_action": "Enter um valid name para o policy according to o naming\nrules. Use apenas alphabetic (ASCII A-Z e a-z), numeric (0-9), plus (+), minus (-),\nunderscore(_), ou period (.) characters. Do não use um minus (-) ou period (.) como o\nfirst ou last character. Do não leave qualquer spaces between characters.\nVeja o NetBackup Administrator’s Guide Volume I para details on o naming\nconventions." + "desc": "Invalid schedule name.", + "first_action": "Enter a valid name for the policy according to the naming", + "full_action": "Enter a valid name for the policy according to the naming\nrules. Use only alphabetic (ASCII A-Z and a-z), numeric (0-9), plus (+), minus (-),\nunderscore(_), or period (.) characters. Do not use a minus (-) or period (.) as the\nfirst or last character. Do not leave any spaces between characters.\nSee the NetBackup Administrator’s Guide Volume I for details on the naming\nconventions." }, "8820": { "code": 8820, - "desc": "Falhou to retrieve details de todos o mídia servers.", - "first_action": "Veja o errorDetails in JSON output para additional", - "full_action": "Veja o errorDetails in JSON output para additional\ndetails. Retry o operation e if o issue persists, visit o Cohesity Technical\nSupport website. O Cohesity Technical Support website offers additional\ninformação to help you troubleshoot this issue." + "desc": "Failed to retrieve details of all the media servers.", + "first_action": "See the errorDetails in JSON output for additional", + "full_action": "See the errorDetails in JSON output for additional\ndetails. Retry the operation and if the issue persists, visit the Cohesity Technical\nSupport website. The Cohesity Technical Support website offers additional\ninformation to help you troubleshoot this issue." }, "8821": { "code": 8821, - "desc": "Falhou to retrieve o details de o specified mídia servidor.", - "first_action": "Veja o errorDetails in JSON output para additional", - "full_action": "Veja o errorDetails in JSON output para additional\ndetails. Retry o operation e if o issue persists, visit o Cohesity Technical\nSupport website. O Cohesity Technical Support website offers additional\ninformação to help you troubleshoot this issue." + "desc": "Failed to retrieve the details of the specified media server.", + "first_action": "See the errorDetails in JSON output for additional", + "full_action": "See the errorDetails in JSON output for additional\ndetails. Retry the operation and if the issue persists, visit the Cohesity Technical\nSupport website. The Cohesity Technical Support website offers additional\ninformation to help you troubleshoot this issue." }, "8822": { "code": 8822, - "desc": "Falhou to add o trusted master servidor.", - "first_action": "Veja o errorDetails in JSON output para additional", - "full_action": "Veja o errorDetails in JSON output para additional\ndetails. Retry o operation e if o issue persists, visit o Cohesity Technical\nSupport website. O Cohesity Technical Support website offers additional\ninformação to help you troubleshoot this issue." + "desc": "Failed to add the trusted master server.", + "first_action": "See the errorDetails in JSON output for additional", + "full_action": "See the errorDetails in JSON output for additional\ndetails. Retry the operation and if the issue persists, visit the Cohesity Technical\nSupport website. The Cohesity Technical Support website offers additional\ninformation to help you troubleshoot this issue." }, "8823": { "code": 8823, - "desc": "Falhou to update o trusted master servidor.", - "first_action": "Veja o errorDetails in JSON output para additional", - "full_action": "Veja o errorDetails in JSON output para additional\ndetails. Retry o operation e if o issue persists, visit o Cohesity Technical\nSupport website. O Cohesity Technical Support website offers additional\ninformação to help you troubleshoot this issue." + "desc": "Failed to update the trusted master server.", + "first_action": "See the errorDetails in JSON output for additional", + "full_action": "See the errorDetails in JSON output for additional\ndetails. Retry the operation and if the issue persists, visit the Cohesity Technical\nSupport website. The Cohesity Technical Support website offers additional\ninformation to help you troubleshoot this issue." }, "8824": { "code": 8824, - "desc": "Falhou to retrieve o trusted master servidor details.", - "first_action": "Veja o errorDetails in JSON output para additional", - "full_action": "Veja o errorDetails in JSON output para additional\ndetails. Retry o operation e if o issue persists, visit o Cohesity Technical\nSupport website. O Cohesity Technical Support website offers additional\ninformação to help you troubleshoot this issue." + "desc": "Failed to retrieve the trusted master server details.", + "first_action": "See the errorDetails in JSON output for additional", + "full_action": "See the errorDetails in JSON output for additional\ndetails. Retry the operation and if the issue persists, visit the Cohesity Technical\nSupport website. The Cohesity Technical Support website offers additional\ninformation to help you troubleshoot this issue." }, "8825": { "code": 8825, - "desc": "Falhou to retrieve o remote primary servidor details.", - "first_action": "Veja o errorDetails in JSON output para additional", - "full_action": "Veja o errorDetails in JSON output para additional\ndetails. Retry o operation e if o issue persists, visit o Cohesity Technical\nSupport website. O Cohesity Technical Support website offers additional\ninformação to help you troubleshoot this issue." + "desc": "Failed to retrieve the remote primary server details.", + "first_action": "See the errorDetails in JSON output for additional", + "full_action": "See the errorDetails in JSON output for additional\ndetails. Retry the operation and if the issue persists, visit the Cohesity Technical\nSupport website. The Cohesity Technical Support website offers additional\ninformation to help you troubleshoot this issue." }, "8836": { "code": 8836, - "desc": "Falhou to update o details de o specified mídia servidor.", - "first_action": "O mídia servidor está known to master servidor.", - "full_action": "Verifique o seguinte:\n■ O mídia servidor está known to master servidor.\n■ O mídia servidor está reachable from master servidor." + "desc": "Failed to update the details of the specified media server.", + "first_action": "The media server is known to master server.", + "full_action": "Verify the following:\n■ The media server is known to master server.\n■ The media server is reachable from master server." }, "8837": { "code": 8837, - "desc": "O specified mídia servidor does não support this DTE configuration.", - "first_action": "O mídia servidor está known to o master servidor.", - "full_action": "Verifique o seguinte:\n■ O mídia servidor está known to o master servidor.\n■ O mídia servidor está on NetBackup 10.0 release ou newer.\n■ O mídia servidor está reachable from o master servidor." + "desc": "The specified media server does not support this DTE configuration.", + "first_action": "The media server is known to the master server.", + "full_action": "Verify the following:\n■ The media server is known to the master server.\n■ The media server is on NetBackup 10.0 release or newer.\n■ The media server is reachable from the master server." }, "8842": { "code": 8842, - "desc": "Falhou to save o proxy servidor details.", - "first_action": "1 Call o POST API", - "full_action": "Executar o seguinte steps:\n1 Call o POST API\n(https://{NetbackupUrl}/netbackup/config/proxy-servers) to create\no proxy servidor.\n2 Create o API com proper syntax to validate o request but use some inválido\ndata which shows um erro during run time.\n3 Verifique que o erro está shown in o API response." + "desc": "Failed to save the proxy server details.", + "first_action": "1 Call the POST API", + "full_action": "Perform the following steps:\n1 Call the POST API\n(https://{NetbackupUrl}/netbackup/config/proxy-servers) to create\nthe proxy server.\n2 Create the API with proper syntax to validate the request but use some invalid\ndata which shows an error during run time.\n3 Verify that the error is shown in the API response." }, "8900": { "code": 8900, - "desc": "O host name que foi provided must be associated com um single host ID.", - "first_action": "Garanta que o host name que you desejar to add ou excluir", - "full_action": "Garanta que o host name que you desejar to add ou excluir\npara mapping está associated com um single host ID." + "desc": "The host name that was provided must be associated with a single host ID.", + "first_action": "Ensure that the host name that you want to add or delete", + "full_action": "Ensure that the host name that you want to add or delete\nfor mapping is associated with a single host ID." }, "8901": { "code": 8901, - "desc": "O mapping name que foi provided does não exist.", - "first_action": "Provide um valid mapping name e try again.", - "full_action": "Provide um valid mapping name e try again." + "desc": "The mapping name that was provided does not exist.", + "first_action": "Provide a valid mapping name and try again.", + "full_action": "Provide a valid mapping name and try again." }, "8902": { "code": 8902, - "desc": "Mappings para o specified host do não exist.", - "first_action": "Provide um valid host name e try again.", - "full_action": "Provide um valid host name e try again." + "desc": "Mappings for the specified host do not exist.", + "first_action": "Provide a valid host name and try again.", + "full_action": "Provide a valid host name and try again." }, "8903": { "code": 8903, - "desc": "O host name does não exist in o host ID to host name mapping list.", - "first_action": "Use host name que está present in host ID to host name", - "full_action": "Use host name que está present in host ID to host name\nmapping list. Alternatively, add o given host name to o mapping list com o\nnbhostmgmt -add comando." + "desc": "The host name does not exist in the host ID to host name mapping list.", + "first_action": "Use host name that is present in host ID to host name", + "full_action": "Use host name that is present in host ID to host name\nmapping list. Alternatively, add the given host name to the mapping list with the\nnbhostmgmt -add command." }, "8904": { "code": 8904, - "desc": "O host banco de dados operations estão blocked when disaster recovery está in progress.", - "first_action": "Manually reset o environment variable", - "full_action": "Manually reset o environment variable\nNB_DR_IN_PROGRESS to 0." + "desc": "The host database operations are blocked when disaster recovery is in progress.", + "first_action": "Manually reset the environment variable", + "full_action": "Manually reset the environment variable\nNB_DR_IN_PROGRESS to 0." }, "8951": { "code": 8951, - "desc": "O NetBackup API version está inválido.", - "first_action": "Para more details about this erro, examine o webserver", - "full_action": "Para more details about this erro, examine o webserver\ne nbwebservice logs. Para more informação, veja o NetBackup API Reference\nGuide." + "desc": "The NetBackup API version is invalid.", + "first_action": "For more details about this error, examine the webserver", + "full_action": "For more details about this error, examine the webserver\nand nbwebservice logs. For more information, see the NetBackup API Reference\nGuide." }, "8952": { "code": 8952, - "desc": "Um response não é possível be generated in o mídia type specified por o request accept header.", - "first_action": "Para more details about this erro, examine o webserver", - "full_action": "Para more details about this erro, examine o webserver\ne nbwebservice logs. Para more informação, veja o NetBackup API Reference\nGuide." + "desc": "A response cannot be generated in the media type specified by the request accept header.", + "first_action": "For more details about this error, examine the webserver", + "full_action": "For more details about this error, examine the webserver\nand nbwebservice logs. For more information, see the NetBackup API Reference\nGuide." }, "8953": { "code": 8953, - "desc": "O content type specified por o request content-type header está não supported por o solicitado resource para o solicitado method.", - "first_action": "Para more details about this erro, examine o webserver", - "full_action": "Para more details about this erro, examine o webserver\ne nbwebservice logs. Para more informação, veja o NetBackup API Reference\nGuide." + "desc": "The content type specified by the request content-type header is not supported by the requested resource for the requested method.", + "first_action": "For more details about this error, examine the webserver", + "full_action": "For more details about this error, examine the webserver\nand nbwebservice logs. For more information, see the NetBackup API Reference\nGuide." }, "8954": { "code": 8954, - "desc": "O filter criteria está inválido.", - "first_action": "Para more details about this erro, examine o webserver", - "full_action": "Para more details about this erro, examine o webserver\ne nbwebservice logs. Para more informação, veja o NetBackup API Reference\nGuide." + "desc": "The filter criteria is invalid.", + "first_action": "For more details about this error, examine the webserver", + "full_action": "For more details about this error, examine the webserver\nand nbwebservice logs. For more information, see the NetBackup API Reference\nGuide." }, "8955": { "code": 8955, - "desc": "Um inválido API request está encontrado.", - "first_action": "Para more details about this erro, examine o webserver", - "full_action": "Para more details about this erro, examine o webserver\ne nbwebservice logs. Para more informação, veja o NetBackup API Reference\nGuide." + "desc": "An invalid API request is encountered.", + "first_action": "For more details about this error, examine the webserver", + "full_action": "For more details about this error, examine the webserver\nand nbwebservice logs. For more information, see the NetBackup API Reference\nGuide." }, "8956": { "code": 8956, - "desc": "Multiple authorization headers estão não allowed.", - "first_action": "Remove o extra authorization headers e try again.", - "full_action": "Remove o extra authorization headers e try again." + "desc": "Multiple authorization headers are not allowed.", + "first_action": "Remove the extra authorization headers and try again.", + "full_action": "Remove the extra authorization headers and try again." }, "8957": { "code": 8957, - "desc": "O HTTP method está não supported.", - "first_action": "Para more details about this erro, examine o webserver", - "full_action": "Para more details about this erro, examine o webserver\ne nbwebservice logs. Para more informação, veja o NetBackup API Reference\nGuide." + "desc": "The HTTP method is not supported.", + "first_action": "For more details about this error, examine the webserver", + "full_action": "For more details about this error, examine the webserver\nand nbwebservice logs. For more information, see the NetBackup API Reference\nGuide." }, "8958": { "code": 8958, - "desc": "Um banco de dados system erro ocorreu.", - "first_action": "If you used o recovery point API to call Microsoft SQL", - "full_action": "If you used o recovery point API to call Microsoft SQL\nsource arquivos, review todos API inputs e try again. If o problema persists, contate o\nCohesity Technical Support. Para more informação, veja o NetBackup API\nReference Guide." + "desc": "A database system error occurred.", + "first_action": "If you used the recovery point API to call Microsoft SQL", + "full_action": "If you used the recovery point API to call Microsoft SQL\nsource files, review all API inputs and try again. If the problem persists, contact the\nCohesity Technical Support. For more information, see the NetBackup API\nReference Guide." }, "8959": { "code": 8959, - "desc": "Multiple audit reason headers estão não allowed.", - "first_action": "Choose one audit reason header e remove o other", - "full_action": "Choose one audit reason header e remove o other\nheaders." + "desc": "Multiple audit reason headers are not allowed.", + "first_action": "Choose one audit reason header and remove the other", + "full_action": "Choose one audit reason header and remove the other\nheaders." }, "8960": { "code": 8960, - "desc": "O X-NetBackup-Audit-Reason header está não properly URL-encoded.", + "desc": "The X-NetBackup-Audit-Reason header is not properly URL-encoded.", "first_action": "Ensurethattheauditreasonisproperlypercentencoded.", - "full_action": "Ensurethattheauditreasonisproperlypercentencoded.\nApenas ISO-8859-1 characters estão allowed." + "full_action": "Ensurethattheauditreasonisproperlypercentencoded.\nOnly ISO-8859-1 characters are allowed." }, "8962": { "code": 8962, - "desc": "Solicitado operation falhou.", + "desc": "Requested operation failed.", "first_action": "Formoredetailsaboutthiserror,examinethewebserver", - "full_action": "Formoredetailsaboutthiserror,examinethewebserver\ne nbwebservice logs. If o problema persists, contate o Cohesity Technical\nSupport. Para more informação, veja o NetBackup API Reference Guide." + "full_action": "Formoredetailsaboutthiserror,examinethewebserver\nand nbwebservice logs. If the problem persists, contact the Cohesity Technical\nSupport. For more information, see the NetBackup API Reference Guide." }, "8963": { "code": 8963, - "desc": "O host name que you have specified to conectar to o NetBackup web servidor está não present in o NetBackup web servidor certificate.", - "first_action": "If you desejar to access o NetBackup Web Management", - "full_action": "If you desejar to access o NetBackup Web Management\nConsole functionality usando additional host names e ou IP addresses (other than\no ones present in servidor certificate), refer to o seguinte procedure.\nNote:Thissettingisonlyforamasterserver.Theallowedlist.propertiesneeds\nto have todos o additional names (host names, IP addresses) de o master servidor\nque would be used to conectar from o clients. Examples de clients estão o\nNetBackup Administration Console, web UI, qualquer rest cliente, ou other NetBackup\nclients.\nAccessing o NetBackup Web Management Console functionality usando\nadditional host names e ou IP addresses\n1 Create um arquivo VAR_GLOBAL/wsl/config/allowedlist.properties.\nExample:\nWindows:\n\\NetBackup\\var\\global\\wsl\\config\\allowedlist.properties\nUNIX: /usr/openv/var/global/wsl/config/allowedlist.properties\n2 Garanta que o web service account usuário has ler permissions on this arquivo.\nExample: On UNIX systems chmod a+r\n/usr/openv/var/global/wsl/config/allowedlist.propertiesisoneway\nto garanta requerido permissions on this arquivo.\n3 Add requerido additional valid host.headers e x.forwarded.host.headers\nheader values.\n4 Save o arquivo.\n5 Restart o NetBackup Web Management Console service.\nOnaWindowssystem,theNetBackup Web Management Consoleservicecan\nbe restarted from o Windows Service Control Manager.\nOn UNIX systems /usr/openv/netbackup/bin/nbwmc stop &&\n/usr/openv/netbackup/bin/nbwmc start.\nO seguinte está um example de um allowedlist.properties arquivo looks like:\n#Sample Properties Arquivo#\n#Properties arquivo to allow additional valid HOST e X-FORWARDED-HOST header values\n#Fri Apr 23 16:14:42 CDT 2021\nhost.headers=master_server_additional_name_1,master_server_additional_name_2,\nmaster_server_additional_ip_1,master_server_additional_ip_2\nx.forwarded.host.headers=master_server_additional_name_1,\nmaster_server_additional_name_2 ,master_server_additional_ip_1,\nmaster_server_additional_ip_2\nO key host.headers has comma-separated string values de o host names e\nIP addresses which need to be considered valid para o HOST request header.\nO key x.forwarded.host.headers has comma-separated string values de o\nhost names e IP addresses which need to be considered valid para o\nX-FORWARDED-HOST header." + "desc": "The host name that you have specified to connect to the NetBackup web server is not present in the NetBackup web server certificate.", + "first_action": "If you want to access the NetBackup Web Management", + "full_action": "If you want to access the NetBackup Web Management\nConsole functionality using additional host names and or IP addresses (other than\nthe ones present in server certificate), refer to the following procedure.\nNote:Thissettingisonlyforamasterserver.Theallowedlist.propertiesneeds\nto have all the additional names (host names, IP addresses) of the master server\nthat would be used to connect from the clients. Examples of clients are the\nNetBackup Administration Console, web UI, any rest client, or other NetBackup\nclients.\nAccessing the NetBackup Web Management Console functionality using\nadditional host names and or IP addresses\n1 Create a file VAR_GLOBAL/wsl/config/allowedlist.properties.\nExample:\nWindows:\n\\NetBackup\\var\\global\\wsl\\config\\allowedlist.properties\nUNIX: /usr/openv/var/global/wsl/config/allowedlist.properties\n2 Ensure that the web service account user has read permissions on this file.\nExample: On UNIX systems chmod a+r\n/usr/openv/var/global/wsl/config/allowedlist.propertiesisoneway\nto ensure required permissions on this file.\n3 Add required additional valid host.headers and x.forwarded.host.headers\nheader values.\n4 Save the file.\n5 Restart the NetBackup Web Management Console service.\nOnaWindowssystem,theNetBackup Web Management Consoleservicecan\nbe restarted from the Windows Service Control Manager.\nOn UNIX systems /usr/openv/netbackup/bin/nbwmc stop &&\n/usr/openv/netbackup/bin/nbwmc start.\nThe following is an example of an allowedlist.properties file looks like:\n#Sample Properties File#\n#Properties file to allow additional valid HOST and X-FORWARDED-HOST header values\n#Fri Apr 23 16:14:42 CDT 2021\nhost.headers=master_server_additional_name_1,master_server_additional_name_2,\nmaster_server_additional_ip_1,master_server_additional_ip_2\nx.forwarded.host.headers=master_server_additional_name_1,\nmaster_server_additional_name_2 ,master_server_additional_ip_1,\nmaster_server_additional_ip_2\nThe key host.headers has comma-separated string values of the host names and\nIP addresses which need to be considered valid for the HOST request header.\nThe key x.forwarded.host.headers has comma-separated string values of the\nhost names and IP addresses which need to be considered valid for the\nX-FORWARDED-HOST header." }, "9032": { "code": 9032, - "desc": "Could não conectar to o virtual machine.", + "desc": "Could not connect to the virtual machine.", "first_action": "VerifyifthevirtualmachineisuportheSnapshotManager", - "full_action": "VerifyifthevirtualmachineisuportheSnapshotManager\ncan communicate com o virtual machine. Review o Snapshot Manager logs." + "full_action": "VerifyifthevirtualmachineisuportheSnapshotManager\ncan communicate with the virtual machine. Review the Snapshot Manager logs." }, "9050": { "code": 9050, - "desc": "Não matching relatório found.", - "first_action": "Verifique if o relatório ID está in o GET /netbackup/reports", - "full_action": "Verifique if o relatório ID está in o GET /netbackup/reports\nresponse." + "desc": "No matching report found.", + "first_action": "Check if the report ID is in the GET /netbackup/reports", + "full_action": "Check if the report ID is in the GET /netbackup/reports\nresponse." }, "9051": { "code": 9051, - "desc": "Inválido filter specified in o request.", - "first_action": "Verifique if o filter string que foi passed through o", - "full_action": "Verifique if o filter string que foi passed through o\nrequest body está valid." + "desc": "Invalid filter specified in the request.", + "first_action": "Check if the filter string that was passed through the", + "full_action": "Check if the filter string that was passed through the\nrequest body is valid." }, "9052": { "code": 9052, - "desc": "Inválido relatório request.", - "first_action": "Verifique que o request body está valid.", - "full_action": "Verifique que o request body está valid." + "desc": "Invalid report request.", + "first_action": "Check that the request body is valid.", + "full_action": "Check that the request body is valid." }, "9053": { "code": 9053, - "desc": "Inválido job relatório type found.", + "desc": "Invalid job report type found.", "first_action": "CheckifthereporttypeisintheGET /netbackup/reports", "full_action": "CheckifthereporttypeisintheGET /netbackup/reports\nresponse." }, "9101": { "code": 9101, - "desc": "Falhou to lock o arquivo.", - "first_action": "Examine o logs para o operation you tried to executar.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Examine o logs para o operation you tried to executar.\n■ On o host onde o erro ocorreu, examine o legacy logs para nbcertcmd.\n■ On todos de o hosts involved in o communication, examine o unified logs para\nnbpxyhelper (OID 486)." + "desc": "Failed to lock the file.", + "first_action": "Examine the logs for the operation you tried to perform.", + "full_action": "Do the following, as appropriate:\n■ Examine the logs for the operation you tried to perform.\n■ On the host where the error occurred, examine the legacy logs for nbcertcmd.\n■ On all of the hosts involved in the communication, examine the unified logs for\nnbpxyhelper (OID 486)." }, "9102": { "code": 9102, - "desc": "Falhou to unlock o arquivo.", - "first_action": "Examine o logs para o operation you tried to executar.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Examine o logs para o operation you tried to executar.\n■ Examine legacy logs on o NetBackup servidor para nbcertcmd." + "desc": "Failed to unlock the file.", + "first_action": "Examine the logs for the operation you tried to perform.", + "full_action": "Do the following, as appropriate:\n■ Examine the logs for the operation you tried to perform.\n■ Examine legacy logs on the NetBackup server for nbcertcmd." }, "9103": { "code": 9103, - "desc": "Unexpected response from o web service. NetBackup status codes 1099 NetBackup status codes", - "first_action": "Upgrade o back-level master servidor.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Upgrade o back-level master servidor.\n■ On o master servidor, examine o unified logs on o NetBackup servidor para\nnbwebservice (todos OIDs).\n■ On o host onde o erro ocorreu, examine o legacy logs para nbcertcmd.\n■ On todos de o hosts involved in o communication, examine o unified logs para\nnbpxyhelper (OID 486)." + "desc": "Unexpected response from the web service. NetBackup status codes 1099 NetBackup status codes", + "first_action": "Upgrade the back-level master server.", + "full_action": "Do the following, as appropriate:\n■ Upgrade the back-level master server.\n■ On the master server, examine the unified logs on the NetBackup server for\nnbwebservice (all OIDs).\n■ On the host where the error occurred, examine the legacy logs for nbcertcmd.\n■ On all of the hosts involved in the communication, examine the unified logs for\nnbpxyhelper (OID 486)." }, "9104": { "code": 9104, - "desc": "O certificate verification falhou.", - "first_action": "Verifique o PKI artifacts usando o OpenSSL comando.", - "full_action": "Verifique o PKI artifacts usando o OpenSSL comando." + "desc": "The certificate verification failed.", + "first_action": "Verify the PKI artifacts using the OpenSSL command.", + "full_action": "Verify the PKI artifacts using the OpenSSL command." }, "9108": { "code": 9108, - "desc": "Falhou to conectar to o vnetd service.", - "first_action": "1. Garanta que o vnetd process está executando on o NetBackup host.", - "full_action": "Do o seguinte:\n1. Garanta que o vnetd process está executando on o NetBackup host.\n2. If o problema persists, contate Cohesity Technical Support." + "desc": "Failed to connect to the vnetd service.", + "first_action": "1. Ensure that the vnetd process is running on the NetBackup host.", + "full_action": "Do the following:\n1. Ensure that the vnetd process is running on the NetBackup host.\n2. If the problem persists, contact Cohesity Technical Support." }, "9126": { "code": 9126, - "desc": "O remote server’s certificate está não valid ou doesn’t exist.", - "first_action": "Review o nbcs/bpfis/bppfi level erro messages que estão displayed in Job", - "full_action": "Executar o seguinte como appropriate:\nO table que está shown lists o issue e o associated ação que está requerido to\nfix o issue:\n■ Review o nbcs/bpfis/bppfi level erro messages que estão displayed in Job\ndetails on o Activity monitor. Para more details, review o component logs.\n■ Reviewthenbwebservice/nbemmlevelerrormessagefortheSnapshotManager\ne plug-in configuration. Para more details, review o component logs.\nTable 1-7 Operation falhou due to SSL certificate issues ou connectivity\nissues.\nMessage Recomendada ação\nNão foi possível to retrieve o certificate CRL. If you Copy o latest CRL into o\nhave configurado o ECA_CRL_PATH, ECA_CRL_PATHpathorensurethattheCRL\ngaranta que valid CRLs estão present at o distribution point URL from o respective\nlocation. Confirm que o CRL URL está host certificate está accessible from o\naccessible from o Snapshot Manager. Snapshot Manager.\nThecertificaterevocationlist(CRL)isexpired. Garanta que o latest CRL’s estão uploaded at\nEnsurethattheECA_CRL_PATHisupdated o ECA_CRL_PATH caminho.\ncom o latest CRL.\nO Snapshot Manager CRL cache can be\nupdated manually por usando o seguinte\ncomando on Snapshot Manager host:\nflexsnap_configure renew --token\ntoken\nThecertificaterevocationlist(CRL)isnotyet Review seu Snapshot Manager’s system\nvalid. time ou provide um valid CRL.\nO date de last update de o certificate Review o CRL usando o OpenSSL\nrevocation list (CRL) está não in um valid format. comando ou contate seu Security\nAdministrator.\nO date de next update de o certificate Review o CRL usando o OpenSSL\nrevocation list (CRL) está não in um valid format. comando ou contate seu Security\nAdministrator.\nTable 1-7 Operation falhou due to SSL certificate issues ou connectivity\nissues. (continued)\nMessage Recomendada ação\nO operation has falhou com um cURL erro. Executar o operation again. If o problema\npersists, save todos de o erro log informação\ne contate Cohesity Technical Support.\nO certificate está revoked. Determinar if qualquer de o certificates in o\nchain have been revoked ou contate seu\nSecurity Administrator.\nTo renew Snapshot Manager certificate, run\no seguinte comando on o Snapshot\nManager host:\nPara NBCA: flexsnap_configure renew\n--hostnames FQDN --token token\n--force\nPara ECA: flexsnap_configure renew\n--hostnames FQDN --ca ca_file_path\n--key key_file_path --chain\nchain_file_path\nPara more details, refer to status code 9318.\nO certificate has expired. (não applicable para NBCA) Review o\nexpiration de o certificates ou contate seu\nSecurity Administrator.\nPara ECA, renew o Snapshot Manager\ncertificate manually on Snapshot Manager\nhost usando o seguinte comando.\nflexsnap_configure renew\n--hostnames FQDN --ca ca_file_path\n--key key_file_path --chain\nchain_file_path\nPara NBCA, Snapshot Manager certificates\nareautomaticallyrenewedwithinlast90days\nde o expiration period.\nPara more details, refer to status code 8506.\nOther NetBackup erro codes ou messages can also be referred to para more\ninformação de SSL certificate ou connectivity issues between primary servidor e\nSnapshotManager.Resolvenetworkissuesifany,withnetstatorasimilarnetwork\ndiagnosis tool. O status de certificates que estão issued para Snapshot Manager can\nbeverifiedusingflexsnap_configure serverinfoandhealthofcontainersrunning\ncan be verified usando flexsnap_configure status." + "desc": "The remote server’s certificate is not valid or doesn’t exist.", + "first_action": "Review the nbcs/bpfis/bppfi level error messages that are displayed in Job", + "full_action": "Perform the following as appropriate:\nThe table that is shown lists the issue and the associated action that is required to\nfix the issue:\n■ Review the nbcs/bpfis/bppfi level error messages that are displayed in Job\ndetails on the Activity monitor. For more details, review the component logs.\n■ Reviewthenbwebservice/nbemmlevelerrormessagefortheSnapshotManager\nand plug-in configuration. For more details, review the component logs.\nTable 1-7 Operation failed due to SSL certificate issues or connectivity\nissues.\nMessage Recommended action\nUnable to retrieve the certificate CRL. If you Copy the latest CRL into the\nhave configured the ECA_CRL_PATH, ECA_CRL_PATHpathorensurethattheCRL\nensure that valid CRLs are present at the distribution point URL from the respective\nlocation. Confirm that the CRL URL is host certificate is accessible from the\naccessible from the Snapshot Manager. Snapshot Manager.\nThecertificaterevocationlist(CRL)isexpired. Ensure that the latest CRL’s are uploaded at\nEnsurethattheECA_CRL_PATHisupdated the ECA_CRL_PATH path.\nwith the latest CRL.\nThe Snapshot Manager CRL cache can be\nupdated manually by using the following\ncommand on Snapshot Manager host:\nflexsnap_configure renew --token\ntoken\nThecertificaterevocationlist(CRL)isnotyet Review your Snapshot Manager’s system\nvalid. time or provide a valid CRL.\nThe date of last update of the certificate Review the CRL using the OpenSSL\nrevocation list (CRL) is not in a valid format. command or contact your Security\nAdministrator.\nThe date of next update of the certificate Review the CRL using the OpenSSL\nrevocation list (CRL) is not in a valid format. command or contact your Security\nAdministrator.\nTable 1-7 Operation failed due to SSL certificate issues or connectivity\nissues. (continued)\nMessage Recommended action\nThe operation has failed with a cURL error. Perform the operation again. If the problem\npersists, save all of the error log information\nand contact Cohesity Technical Support.\nThe certificate is revoked. Determine if any of the certificates in the\nchain have been revoked or contact your\nSecurity Administrator.\nTo renew Snapshot Manager certificate, run\nthe following command on the Snapshot\nManager host:\nFor NBCA: flexsnap_configure renew\n--hostnames FQDN --token token\n--force\nFor ECA: flexsnap_configure renew\n--hostnames FQDN --ca ca_file_path\n--key key_file_path --chain\nchain_file_path\nFor more details, refer to status code 9318.\nThe certificate has expired. (Not applicable for NBCA) Review the\nexpiration of the certificates or contact your\nSecurity Administrator.\nFor ECA, renew the Snapshot Manager\ncertificate manually on Snapshot Manager\nhost using the following command.\nflexsnap_configure renew\n--hostnames FQDN --ca ca_file_path\n--key key_file_path --chain\nchain_file_path\nFor NBCA, Snapshot Manager certificates\nareautomaticallyrenewedwithinlast90days\nof the expiration period.\nFor more details, refer to status code 8506.\nOther NetBackup error codes or messages can also be referred to for more\ninformation of SSL certificate or connectivity issues between primary server and\nSnapshotManager.Resolvenetworkissuesifany,withnetstatorasimilarnetwork\ndiagnosis tool. The status of certificates that are issued for Snapshot Manager can\nbeverifiedusingflexsnap_configure serverinfoandhealthofcontainersrunning\ncan be verified using flexsnap_configure status." }, "9128": { "code": 9128, - "desc": "Falhou to obtain o backup ID from o track log arquivo.", - "first_action": "1. Rename o appropriate track journal folder on cliente:", - "full_action": "To address o issue, executar o seguinte:\n1. Rename o appropriate track journal folder on cliente:\ninstall_path\\Veritas\\NetBackup\n\\track\\\\\\\\\n2. Executar um new cheio backup." + "desc": "Failed to obtain the backup ID from the track log file.", + "first_action": "1. Rename the appropriate track journal folder on client:", + "full_action": "To address the issue, perform the following:\n1. Rename the appropriate track journal folder on client:\ninstall_path\\Veritas\\NetBackup\n\\track\\\\\\\\\n2. Perform a new full backup." }, "9129": { "code": 9129, - "desc": "O private key arquivo não é possível be loaded.", - "first_action": "Retry o operation e if o issue persists, visit", - "full_action": "Retry o operation e if o issue persists, visit\nsupport.veritas.com. O Cohesity Technical Support site offers additional\ninformação to help you troubleshoot this issue." + "desc": "The private key file cannot be loaded.", + "first_action": "Retry the operation and if the issue persists, visit", + "full_action": "Retry the operation and if the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support site offers additional\ninformation to help you troubleshoot this issue." }, "9130": { "code": 9130, - "desc": "O private key arquivo não é possível be validated.", - "first_action": "Retry o operation e if o issue persists, visit", - "full_action": "Retry o operation e if o issue persists, visit\nsupport.veritas.com. O Cohesity Technical Support site offers additional\ninformação to help you troubleshoot this issue." + "desc": "The private key file cannot be validated.", + "first_action": "Retry the operation and if the issue persists, visit", + "full_action": "Retry the operation and if the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support site offers additional\ninformation to help you troubleshoot this issue." }, "9131": { "code": 9131, - "desc": "O SSL handshake falhou.", - "first_action": "Retry o operation e if o issue persists, visit", - "full_action": "Retry o operation e if o issue persists, visit\nsupport.veritas.com. O Cohesity Technical Support site offers additional\ninformação to help you troubleshoot this issue." + "desc": "The SSL handshake failed.", + "first_action": "Retry the operation and if the issue persists, visit", + "full_action": "Retry the operation and if the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support site offers additional\ninformation to help you troubleshoot this issue." }, "9132": { "code": 9132, - "desc": "Não é possível conectar to o host because o NetBackup services estão não executando on o host.", + "desc": "Cannot connect to the host because the NetBackup services are not running on the host.", "first_action": "PBX services", - "full_action": "Verifique que o seguinte services estão up e estão executando\non o host:\n■ PBX services\n■ NetBackup services\nIf you continue to have problemas, veja Resolvendo rede communication problemas\nin o NetBackup Troubleshooting Guide." + "full_action": "Verify that the following services are up and are running\non the host:\n■ PBX services\n■ NetBackup services\nIf you continue to have problems, see Resolving network communication problems\nin the NetBackup Troubleshooting Guide." }, "9134": { "code": 9134, - "desc": "Falhou to retrieve o passphrase.", + "desc": "Failed to retrieve the passphrase.", "first_action": "Verifythatthepassphrasefileexistsatthekeystorelocationandhasthecorrect", - "full_action": "Executar o seguinte como appropriate:\n■ Verifythatthepassphrasefileexistsatthekeystorelocationandhasthecorrect\npermissions. If o arquivo está present but lacks o proper permissions, adjust o\npermissions manually e retry o operation.\n■ If o issue persists, remove todos arquivos from o keystore diretório, including qualquer\nhidden arquivos. Depending on seu configuration, o keystore diretório está\ninstall_dir/var/vxss/credentials/keystore,\ninstall_dir/var/global/vxss/credentials/keystore,\ninstall_path\\NetBackup\\var\\vxss\\credentials\\keystore, ou\ninstall_path\\NetBackup\\var\\global\\vxss\\credentials\\keystoredirectory.\n■ Executar nbcertcmd -getCertificate com reissueToken option para todos\nservers com which o host está registered e retry o operation.\n■ If o issue persists, collect o nbcert, nbpxyhelper, e nbwebservice\nlogs e contate Cohesity Technical Support." + "full_action": "Perform the following as appropriate:\n■ Verifythatthepassphrasefileexistsatthekeystorelocationandhasthecorrect\npermissions. If the file is present but lacks the proper permissions, adjust the\npermissions manually and retry the operation.\n■ If the issue persists, remove all files from the keystore directory, including any\nhidden files. Depending on your configuration, the keystore directory is\ninstall_dir/var/vxss/credentials/keystore,\ninstall_dir/var/global/vxss/credentials/keystore,\ninstall_path\\NetBackup\\var\\vxss\\credentials\\keystore, or\ninstall_path\\NetBackup\\var\\global\\vxss\\credentials\\keystoredirectory.\n■ Perform nbcertcmd -getCertificate with reissueToken option for all\nservers with which the host is registered and retry the operation.\n■ If the issue persists, collect the nbcert, nbpxyhelper, and nbwebservice\nlogs and contact Cohesity Technical Support." }, "9135": { "code": 9135, - "desc": "TheNetBackupclientusesaweakcipherforencryption,ortheencryption está de o legacy type.", - "first_action": "Use STANDARD kind de encryption method com strong ciphers like AES.", - "full_action": "Executar o seguinte como appropriate:\nUse STANDARD kind de encryption method com strong ciphers like AES." + "desc": "TheNetBackupclientusesaweakcipherforencryption,ortheencryption is of the legacy type.", + "first_action": "Use STANDARD kind of encryption method with strong ciphers like AES.", + "full_action": "Perform the following as appropriate:\nUse STANDARD kind of encryption method with strong ciphers like AES." }, "9136": { "code": 9136, - "desc": "Rotation de o passphrase key falhou.", - "first_action": "Verifique que o passphrase key arquivo exists at o keystore location e has o", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique que o passphrase key arquivo exists at o keystore location e has o\ncorrectpermissions.Ifthefileispresentbutlackstheproperpermissions,adjust\no permissions manually e retry o operation.\n■ If o issue persists, remove todos arquivos from o keystore diretório, including qualquer\nhidden arquivos. Depending on seu configuration, o keystore diretório está\ninstall_dir/var/vxss/credentials/keystore,\ninstall_dir/var/global/vxss/credentials/keystore,\ninstall_path\\NetBackup\\var\\vxss\\credentials\\keystore, ou\ninstall_path\\NetBackup\\var\\global\\vxss\\credentials\\keystoredirectory.\n■ Executar nbcertcmd -getCertificate com reissueToken option para todos\nservers com which o host está registered e retry o operation.\n■ If o issue persists, collect o nbcert, nbpxyhelper, e nbwebservice\nlogs e contate Cohesity Technical Support." + "desc": "Rotation of the passphrase key failed.", + "first_action": "Verify that the passphrase key file exists at the keystore location and has the", + "full_action": "Perform the following as appropriate:\n■ Verify that the passphrase key file exists at the keystore location and has the\ncorrectpermissions.Ifthefileispresentbutlackstheproperpermissions,adjust\nthe permissions manually and retry the operation.\n■ If the issue persists, remove all files from the keystore directory, including any\nhidden files. Depending on your configuration, the keystore directory is\ninstall_dir/var/vxss/credentials/keystore,\ninstall_dir/var/global/vxss/credentials/keystore,\ninstall_path\\NetBackup\\var\\vxss\\credentials\\keystore, or\ninstall_path\\NetBackup\\var\\global\\vxss\\credentials\\keystoredirectory.\n■ Perform nbcertcmd -getCertificate with reissueToken option for all\nservers with which the host is registered and retry the operation.\n■ If the issue persists, collect the nbcert, nbpxyhelper, and nbwebservice\nlogs and contact Cohesity Technical Support." }, "9139": { "code": 9139, - "desc": "Backup arquivos already present in keystore.", - "first_action": "Remove o backup arquivos in o keystore folder que have o _bkup suffix e", - "full_action": "Executar o seguinte como appropriate:\n■ Remove o backup arquivos in o keystore folder que have o _bkup suffix e\nretry o operation.\n■ If o issue persists, collect o nbcert, nbpxyhelper, e nbwebservice logs\ne contate Cohesity Technical Support." + "desc": "Backup files already present in keystore.", + "first_action": "Remove the backup files in the keystore folder that have the _bkup suffix and", + "full_action": "Perform the following as appropriate:\n■ Remove the backup files in the keystore folder that have the _bkup suffix and\nretry the operation.\n■ If the issue persists, collect the nbcert, nbpxyhelper, and nbwebservice logs\nand contact Cohesity Technical Support." }, "9140": { "code": 9140, - "desc": "Diretório está vazio.", + "desc": "Directory is empty.", "first_action": "Collectthenbcert,nbpxyhelper,andnbwebservicelogs", - "full_action": "Collectthenbcert,nbpxyhelper,andnbwebservicelogs\ne contate Cohesity Technical Support." + "full_action": "Collectthenbcert,nbpxyhelper,andnbwebservicelogs\nand contact Cohesity Technical Support." }, "9141": { "code": 9141, - "desc": "Keystore está in inconsistent state. NetBackup status codes 1106 NetBackup status codes", - "first_action": "Verifique que o private key, passphrase, e passphrase key arquivos exist at o", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique que o private key, passphrase, e passphrase key arquivos exist at o\nkeystorelocationandhavethecorrectserviceuserpermissions.Ifthefilesare\npresent but lack o proper permissions, adjust o permissions manually e\nretry o operation.\n■ If backup arquivos estão present clean-up o backup arquivos com o _bkup suffix e\nretry o operation.\n■ Para qualquer other case:\n■ If o issue persists, remove todos arquivos from o keystore diretório, including\nqualquer hidden arquivos. Depending on seu configuration, o keystore diretório\nestá install_dir/var/vxss/credentials/keystore,\ninstall_dir/var/global/vxss/credentials/keystore,\ninstall_path\\NetBackup\\var\\vxss\\credentials\\keystore, ou\ninstall_path\\NetBackup\\var\\global\\vxss\\credentials\\keystore\ndiretório.\n■ Executar nbcertcmd -getCertificate com reissueToken option para todos\nservers com which o host está registered e retry o operation.\n■ Iftheissuepersists,collectthenbcert,nbpxyhelper,andnbwebservice\nlogs e contate Cohesity Technical Support." + "desc": "Keystore is in inconsistent state. NetBackup status codes 1106 NetBackup status codes", + "first_action": "Verify that the private key, passphrase, and passphrase key files exist at the", + "full_action": "Perform the following as appropriate:\n■ Verify that the private key, passphrase, and passphrase key files exist at the\nkeystorelocationandhavethecorrectserviceuserpermissions.Ifthefilesare\npresent but lack the proper permissions, adjust the permissions manually and\nretry the operation.\n■ If backup files are present clean-up the backup files with the _bkup suffix and\nretry the operation.\n■ For any other case:\n■ If the issue persists, remove all files from the keystore directory, including\nany hidden files. Depending on your configuration, the keystore directory\nis install_dir/var/vxss/credentials/keystore,\ninstall_dir/var/global/vxss/credentials/keystore,\ninstall_path\\NetBackup\\var\\vxss\\credentials\\keystore, or\ninstall_path\\NetBackup\\var\\global\\vxss\\credentials\\keystore\ndirectory.\n■ Perform nbcertcmd -getCertificate with reissueToken option for all\nservers with which the host is registered and retry the operation.\n■ Iftheissuepersists,collectthenbcert,nbpxyhelper,andnbwebservice\nlogs and contact Cohesity Technical Support." }, "9142": { "code": 9142, - "desc": "Arquivo does não exist.", + "desc": "File does not exist.", "first_action": "Collectthenbcert,nbpxyhelper,andnbwebservicelogs", - "full_action": "Collectthenbcert,nbpxyhelper,andnbwebservicelogs\ne contate Cohesity Technical Support." + "full_action": "Collectthenbcert,nbpxyhelper,andnbwebservicelogs\nand contact Cohesity Technical Support." }, "9143": { "code": 9143, - "desc": "Rotation de o passphrase falhou.", + "desc": "Rotation of the passphrase failed.", "first_action": "Verifythatthepassphrasefileexistsatthekeystorelocationandhasthecorrect", - "full_action": "Executar o seguinte como appropriate:\n■ Verifythatthepassphrasefileexistsatthekeystorelocationandhasthecorrect\npermissions. If o arquivo está present but lacks o proper permissions, adjust o\npermissions manually e retry o operation.\n■ If o issue persists, remove todos arquivos from o keystore diretório, including qualquer\nhidden arquivos. Depending on seu configuration, o keystore diretório está\ninstall_dir/var/vxss/credentials/keystore,\ninstall_dir/var/global/vxss/credentials/keystore,\ninstall_path\\NetBackup\\var\\vxss\\credentials\\keystore, ou\ninstall_path\\NetBackup\\var\\global\\vxss\\credentials\\keystoredirectory.\n■ Executar nbcertcmd -getCertificate com reissueToken option para todos\nservers com which o host está registered e retry o operation.\n■ If o issue persists, collect o nbcert, nbpxyhelper, e nbwebservice\nlogs e contate Cohesity Technical Support." + "full_action": "Perform the following as appropriate:\n■ Verifythatthepassphrasefileexistsatthekeystorelocationandhasthecorrect\npermissions. If the file is present but lacks the proper permissions, adjust the\npermissions manually and retry the operation.\n■ If the issue persists, remove all files from the keystore directory, including any\nhidden files. Depending on your configuration, the keystore directory is\ninstall_dir/var/vxss/credentials/keystore,\ninstall_dir/var/global/vxss/credentials/keystore,\ninstall_path\\NetBackup\\var\\vxss\\credentials\\keystore, or\ninstall_path\\NetBackup\\var\\global\\vxss\\credentials\\keystoredirectory.\n■ Perform nbcertcmd -getCertificate with reissueToken option for all\nservers with which the host is registered and retry the operation.\n■ If the issue persists, collect the nbcert, nbpxyhelper, and nbwebservice\nlogs and contact Cohesity Technical Support." }, "9144": { "code": 9144, - "desc": "Rotation de o passphrase e o subsequent restauração falhou.", + "desc": "Rotation of the passphrase and the subsequent restore failed.", "first_action": "Collectthenbcert,nbpxyhelper,andnbwebservicelogs", - "full_action": "Collectthenbcert,nbpxyhelper,andnbwebservicelogs\ne contate Cohesity Technical Support." + "full_action": "Collectthenbcert,nbpxyhelper,andnbwebservicelogs\nand contact Cohesity Technical Support." }, "9145": { "code": 9145, - "desc": "O given tag does não exist in o passphrase key arquivo.", - "first_action": "If o issue persists, remove todos arquivos from o keystore diretório, including qualquer", - "full_action": "Executar o seguinte como appropriate:\n■ If o issue persists, remove todos arquivos from o keystore diretório, including qualquer\nhidden arquivos. Depending on seu configuration, o keystore diretório está\ninstall_dir/var/vxss/credentials/keystore,\ninstall_dir/var/global/vxss/credentials/keystore,\ninstall_path\\NetBackup\\var\\vxss\\credentials\\keystore, ou\ninstall_path\\NetBackup\\var\\global\\vxss\\credentials\\keystoredirectory.\n■ Executar nbcertcmd -getCertificate com reissueToken option para todos\nservers com which o host está registered e retry o operation.\n■ If o issue persists, collect o nbcert, nbpxyhelper, e nbwebservice\nlogs e contate Cohesity Technical Support." + "desc": "The given tag does not exist in the passphrase key file.", + "first_action": "If the issue persists, remove all files from the keystore directory, including any", + "full_action": "Perform the following as appropriate:\n■ If the issue persists, remove all files from the keystore directory, including any\nhidden files. Depending on your configuration, the keystore directory is\ninstall_dir/var/vxss/credentials/keystore,\ninstall_dir/var/global/vxss/credentials/keystore,\ninstall_path\\NetBackup\\var\\vxss\\credentials\\keystore, or\ninstall_path\\NetBackup\\var\\global\\vxss\\credentials\\keystoredirectory.\n■ Perform nbcertcmd -getCertificate with reissueToken option for all\nservers with which the host is registered and retry the operation.\n■ If the issue persists, collect the nbcert, nbpxyhelper, and nbwebservice\nlogs and contact Cohesity Technical Support." }, "9146": { "code": 9146, - "desc": "O passphrase key arquivo does não have qualquer contents.", - "first_action": "If o issue persists, remove todos arquivos from o keystore diretório, including qualquer", - "full_action": "Executar o seguinte como appropriate:\n■ If o issue persists, remove todos arquivos from o keystore diretório, including qualquer\nhidden arquivos. Depending on seu configuration, o keystore diretório está\ninstall_dir/var/vxss/credentials/keystore,\ninstall_dir/var/global/vxss/credentials/keystore,\ninstall_path\\NetBackup\\var\\vxss\\credentials\\keystore, ou\ninstall_path\\NetBackup\\var\\global\\vxss\\credentials\\keystoredirectory.\n■ Executar nbcertcmd -getCertificate com reissueToken option para todos\nservers com which o host está registered e retry o operation.\n■ If o issue persists, collect o nbcert, nbpxyhelper, e nbwebservice\nlogs e contate Cohesity Technical Support." + "desc": "The passphrase key file does not have any contents.", + "first_action": "If the issue persists, remove all files from the keystore directory, including any", + "full_action": "Perform the following as appropriate:\n■ If the issue persists, remove all files from the keystore directory, including any\nhidden files. Depending on your configuration, the keystore directory is\ninstall_dir/var/vxss/credentials/keystore,\ninstall_dir/var/global/vxss/credentials/keystore,\ninstall_path\\NetBackup\\var\\vxss\\credentials\\keystore, or\ninstall_path\\NetBackup\\var\\global\\vxss\\credentials\\keystoredirectory.\n■ Perform nbcertcmd -getCertificate with reissueToken option for all\nservers with which the host is registered and retry the operation.\n■ If the issue persists, collect the nbcert, nbpxyhelper, and nbwebservice\nlogs and contact Cohesity Technical Support." }, "9147": { "code": 9147, - "desc": "Falhou to create encryption tag.", + "desc": "Failed to create encryption tag.", "first_action": "Retrytheoperation.Iftheissuepersists,collectthenbcert,", - "full_action": "Retrytheoperation.Iftheissuepersists,collectthenbcert,\nnbpxyhelper, e nbwebservice logs e contate Cohesity Technical Support." + "full_action": "Retrytheoperation.Iftheissuepersists,collectthenbcert,\nnbpxyhelper, and nbwebservice logs and contact Cohesity Technical Support." }, "9148": { "code": 9148, - "desc": "Falhou to create encryption key.", + "desc": "Failed to create encryption key.", "first_action": "Retrytheoperation.Iftheissuepersists,collectthenbcert,", - "full_action": "Retrytheoperation.Iftheissuepersists,collectthenbcert,\nnbpxyhelper, e nbwebservice logs e contate Cohesity Technical Support." + "full_action": "Retrytheoperation.Iftheissuepersists,collectthenbcert,\nnbpxyhelper, and nbwebservice logs and contact Cohesity Technical Support." }, "9149": { "code": 9149, - "desc": "Falhou to create passphrase key arquivo.", - "first_action": "Verifique que o passphrase key arquivo ou diretório exists at o keystore location", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique que o passphrase key arquivo ou diretório exists at o keystore location\ne has o correct permissions. If o arquivo está present but lacks o proper\npermissions, adjust o permissions manually e retry o operation.\n■ If o issue persists, remove todos arquivos from o keystore diretório, including qualquer\nhidden arquivos. Depending on seu configuration, o keystore diretório está\ninstall_dir/var/vxss/credentials/keystore,\ninstall_dir/var/global/vxss/credentials/keystore,\ninstall_path\\NetBackup\\var\\vxss\\credentials\\keystore, ou\ninstall_path\\NetBackup\\var\\global\\vxss\\credentials\\keystoredirectory.\n■ Executar nbcertcmd -getCertificate com reissueToken option para todos\nservers com which o host está registered e retry o operation.\n■ If o issue persists, collect o nbcert, nbpxyhelper, e nbwebservice\nlogs e contate Cohesity Technical Support." + "desc": "Failed to create passphrase key file.", + "first_action": "Verify that the passphrase key file or directory exists at the keystore location", + "full_action": "Perform the following as appropriate:\n■ Verify that the passphrase key file or directory exists at the keystore location\nand has the correct permissions. If the file is present but lacks the proper\npermissions, adjust the permissions manually and retry the operation.\n■ If the issue persists, remove all files from the keystore directory, including any\nhidden files. Depending on your configuration, the keystore directory is\ninstall_dir/var/vxss/credentials/keystore,\ninstall_dir/var/global/vxss/credentials/keystore,\ninstall_path\\NetBackup\\var\\vxss\\credentials\\keystore, or\ninstall_path\\NetBackup\\var\\global\\vxss\\credentials\\keystoredirectory.\n■ Perform nbcertcmd -getCertificate with reissueToken option for all\nservers with which the host is registered and retry the operation.\n■ If the issue persists, collect the nbcert, nbpxyhelper, and nbwebservice\nlogs and contact Cohesity Technical Support." }, "9150": { "code": 9150, - "desc": "Falhou to rotate passphrase due to o incorrect encryption state de o keystore.", + "desc": "Failed to rotate passphrase due to the incorrect encryption state of the keystore.", "first_action": "Performnbcertcmd -getCertificatewithreissueTokenoptionforallservers", - "full_action": "Executar o seguinte como appropriate:\n■ Performnbcertcmd -getCertificatewithreissueTokenoptionforallservers\ncom which o host está registered e retry o operation.\n■ If o issue persists, collect o nbcert, nbpxyhelper, e nbwebservice logs\ne contate Cohesity Technical Support." + "full_action": "Perform the following as appropriate:\n■ Performnbcertcmd -getCertificatewithreissueTokenoptionforallservers\nwith which the host is registered and retry the operation.\n■ If the issue persists, collect the nbcert, nbpxyhelper, and nbwebservice logs\nand contact Cohesity Technical Support." }, "9151": { "code": 9151, - "desc": "Um internal erro ocorreu.", + "desc": "An internal error occurred.", "first_action": "Collectthenbcert,nbpxyhelper,andnbwebservicelogs", - "full_action": "Collectthenbcert,nbpxyhelper,andnbwebservicelogs\ne contate Cohesity Technical Support." + "full_action": "Collectthenbcert,nbpxyhelper,andnbwebservicelogs\nand contact Cohesity Technical Support." }, "9152": { "code": 9152, - "desc": "O usuário does não have permissão to access o keystore diretório.", - "first_action": "Verifique o arquivo ou o folder permissions.", - "full_action": "Executar o seguinte como appropriate:\n■ Verifique o arquivo ou o folder permissions.\n■ Grant o service usuário ler, gravar, e access permissions if necessary.\n■ Retry o operation." + "desc": "The user does not have permission to access the keystore directory.", + "first_action": "Verify the file or the folder permissions.", + "full_action": "Perform the following as appropriate:\n■ Verify the file or the folder permissions.\n■ Grant the service user read, write, and access permissions if necessary.\n■ Retry the operation." }, "9201": { "code": 9201, - "desc": "O service usuário não é possível switch o context to another usuário.", - "first_action": "Update ou remove o logon details from catalog backup", - "full_action": "Update ou remove o logon details from catalog backup\npolicy." + "desc": "The service user cannot switch the context to another user.", + "first_action": "Update or remove the logon details from catalog backup", + "full_action": "Update or remove the logon details from catalog backup\npolicy." }, "9202": { "code": 9202, - "desc": "O service usuário account does não have o gravar permissions on o specified caminho.", + "desc": "The service user account does not have the write permissions on the specified path.", "first_action": "Windows:", - "full_action": "Verifique que o service account has gravar access on o\nusuário caminho que está specified.\nPara example: If o service usuário account does não have gravar permissions on o\ndisaster recovery package caminho specified in o catalog backup policy, o catalog\nbackup fails com this erro.\nO catalog recovery also fails com this erro if o service usuário account does não\nhave gravar access to o DR caminho e its contents.\nRun o seguinte commands so que service usuário account has gravar access on o\ndisaster recovery caminho:\n■ Windows:\nICACLS \"\" /grant:r\n\"*S-1-5-80-623693008-3165178162-2673590941-1612452212-3346329012:(OI)(CI)F\"\nIn this comando example,\nS-1-5-80-623693008-3165178162-2673590941-1612452212-3346329012 está\nService SID de NetBackup Banco de dados Manager service (bpdbm).\n■ UNIX:\nchown -R \nAfter o chown comando está run, verifique que o service usuário can gravar to o\nspecified caminho usando o su comando.\nsu -c \"touch /test.txt\"" + "full_action": "Verify that the service account has write access on the\nuser path that is specified.\nFor example: If the service user account does not have write permissions on the\ndisaster recovery package path specified in the catalog backup policy, the catalog\nbackup fails with this error.\nThe catalog recovery also fails with this error if the service user account does not\nhave write access to the DR path and its contents.\nRun the following commands so that service user account has write access on the\ndisaster recovery path:\n■ Windows:\nICACLS \"\" /grant:r\n\"*S-1-5-80-623693008-3165178162-2673590941-1612452212-3346329012:(OI)(CI)F\"\nIn this command example,\nS-1-5-80-623693008-3165178162-2673590941-1612452212-3346329012 is\nService SID of NetBackup Database Manager service (bpdbm).\n■ UNIX:\nchown -R \nAfter the chown command is run, verify that the service user can write to the\nspecified path using the su command.\nsu -c \"touch /test.txt\"" }, "9250": { "code": 9250, - "desc": "Host IDs de o target e o source hosts do não match.", - "first_action": "Make sure o reissue token que está generated para o same host está used para o", - "full_action": "Executar o seguinte como appropriate:\nPara NBCA:\n■ Make sure o reissue token que está generated para o same host está used para o\nfetching certificate.\n■ If o reissue token está correct, then excluir o particular entry que caused o\nissue e fetch o certificates from que primary servidor again.\n■ RefertothesectionAboutreissuinghostID-basedcertificatesintheNetBackup\nSecurity e Encryption Guide para more details.\nPara ECA:\n■ This problema may be reported if o certificate used para enrollment está already\nenrolledwithsomeotherhost.Verifythatthecertificatethatisusedforenrollment\nestá associated com o current host. Find e excluir o particular entry que\ncaused o issue e enroll o certificate again.\n■ Refer to o section About external CA support in NetBackup in o NetBackup\nSecurity e Encryption Guide para more details.\nRetrytheoperationandiftheissuepersists,visitsupport.veritas.com.TheCohesity\nTechnicalSupportwebsitesiteoffersadditionalinformationtohelpyoutroubleshoot\nthis issue." + "desc": "Host IDs of the target and the source hosts do not match.", + "first_action": "Make sure the reissue token that is generated for the same host is used for the", + "full_action": "Perform the following as appropriate:\nFor NBCA:\n■ Make sure the reissue token that is generated for the same host is used for the\nfetching certificate.\n■ If the reissue token is correct, then delete the particular entry that caused the\nissue and fetch the certificates from that primary server again.\n■ RefertothesectionAboutreissuinghostID-basedcertificatesintheNetBackup\nSecurity and Encryption Guide for more details.\nFor ECA:\n■ This problem may be reported if the certificate used for enrollment is already\nenrolledwithsomeotherhost.Verifythatthecertificatethatisusedforenrollment\nis associated with the current host. Find and delete the particular entry that\ncaused the issue and enroll the certificate again.\n■ Refer to the section About external CA support in NetBackup in the NetBackup\nSecurity and Encryption Guide for more details.\nRetrytheoperationandiftheissuepersists,visitsupport.veritas.com.TheCohesity\nTechnicalSupportwebsitesiteoffersadditionalinformationtohelpyoutroubleshoot\nthis issue." }, "9251": { "code": 9251, - "desc": "Host IDs de o target e o source master servers do não match.", - "first_action": "Manually excluir o entry para o primary host ID causing", - "full_action": "Manually excluir o entry para o primary host ID causing\no issue e executar o operation again.\nRefer to o section About external CA support in NetBackup in o NetBackup\nSecurity e Encryption Guide para more details.\nIf o issue persists, visit support.veritas.com. O Cohesity Technical Support\nwebsite site offers additional informação to help you troubleshoot this issue." + "desc": "Host IDs of the target and the source master servers do not match.", + "first_action": "Manually delete the entry for the primary host ID causing", + "full_action": "Manually delete the entry for the primary host ID causing\nthe issue and perform the operation again.\nRefer to the section About external CA support in NetBackup in the NetBackup\nSecurity and Encryption Guide for more details.\nIf the issue persists, visit support.veritas.com. The Cohesity Technical Support\nwebsite site offers additional information to help you troubleshoot this issue." }, "9252": { "code": 9252, - "desc": "Either o source host ID ou o target host ID está null.", - "first_action": "Manually excluir o entry que has um null host ID causing", - "full_action": "Manually excluir o entry que has um null host ID causing\no issue e executar o operation again.\nRefer to o section About external CA support in NetBackup in o NetBackup\nSecurity e Encryption Guide para more details.\nIf o issue persists, visit support.veritas.com. O Cohesity Technical Support\nwebsite site offers additional informação to help you troubleshoot this issue." + "desc": "Either the source host ID or the target host ID is null.", + "first_action": "Manually delete the entry that has a null host ID causing", + "full_action": "Manually delete the entry that has a null host ID causing\nthe issue and perform the operation again.\nRefer to the section About external CA support in NetBackup in the NetBackup\nSecurity and Encryption Guide for more details.\nIf the issue persists, visit support.veritas.com. The Cohesity Technical Support\nwebsite site offers additional information to help you troubleshoot this issue." }, "9253": { "code": 9253, - "desc": "Removing JSON array falhou.", - "first_action": "Verifique o gravar arquivo permissão. If o issue persists, visit", - "full_action": "Verifique o gravar arquivo permissão. If o issue persists, visit\nsupport.veritas.com. O Cohesity Technical Support website site offers additional\ninformação to help you troubleshoot this issue." + "desc": "Removing JSON array failed.", + "first_action": "Check the write file permission. If the issue persists, visit", + "full_action": "Check the write file permission. If the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support website site offers additional\ninformation to help you troubleshoot this issue." }, "9270": { "code": 9270, - "desc": "Falhou to retrieve credentials para SpanFS servidor.", - "first_action": "Review o nbemm logs from o primary servidor e o", - "full_action": "Review o nbemm logs from o primary servidor e o\nbptm logs from o mídia servidor para errors. Search o Cohesity Technical Support\nwebsite to determinar o source de those errors. Para additional assistance, collect\no nbemm e bptm logs e contate Cohesity Technical Support." + "desc": "Failed to retrieve credentials for SpanFS server.", + "first_action": "Review the nbemm logs from the primary server and the", + "full_action": "Review the nbemm logs from the primary server and the\nbptm logs from the media server for errors. Search the Cohesity Technical Support\nwebsite to determine the source of those errors. For additional assistance, collect\nthe nbemm and bptm logs and contact Cohesity Technical Support." }, "9271": { "code": 9271, - "desc": "Falhou to retrieve trusted certificate para SpanFS servidor.", + "desc": "Failed to retrieve trusted certificate for SpanFS server.", "first_action": "Storage_server cluster_FQDN -stype SpanFS -media_server", - "full_action": "If o automatic trust certificate retrieval fails, configure\nou update o SpanFS servidor manually, usando REST API ou tpconfig comando.\nTo configure ou update o SpanFS servidor, SpanFS CA certificate está requerido.\nRefer to article to retrieve o SpanFS CA certificate:\nUsando REST API\nTo configure SpanFS servidor, use o POST API\n'/netbackup/storage/storage-server' endpoint.\nTo update SpanFS servidor credentials, use o PATCH API\n'/netbackup/storage/storage-server' endpoint.\nUsando tpconfig CLI\nTo configure SpanFS servidor\n1 Create um armazenamento servidor de type SpanFS usando o fully qualified domain name\n(FQDN) de o cluster.\n/usr/openv/netbackup/bin/admincmd/nbdevconfig -creatests\n-storage_server cluster_FQDN -stype SpanFS -media_server\nmedia_server\n2 Add credentials para o SpanFS servidor.\n/usr/openv/volmgr/bin/tpconfig -add -storage_server server_name\n-stype SpanFS -sts_user_id user_ID [-password password] [-st\nstorage_type] [-ca_file_path SpanFS_CA_certificate_path]\nTo update SpanFS servidor credentials\n◆ /usr/openv/volmgr/bin/tpconfig -update -storage_server server_name\n-stype SpanFS -sts_user_id user_ID [ password password] [\n-ca_file_path SpanFS_CA_certificate_path]" + "full_action": "If the automatic trust certificate retrieval fails, configure\nor update the SpanFS server manually, using REST API or tpconfig command.\nTo configure or update the SpanFS server, SpanFS CA certificate is required.\nRefer to article to retrieve the SpanFS CA certificate:\nUsing REST API\nTo configure SpanFS server, use the POST API\n'/netbackup/storage/storage-server' endpoint.\nTo update SpanFS server credentials, use the PATCH API\n'/netbackup/storage/storage-server' endpoint.\nUsing tpconfig CLI\nTo configure SpanFS server\n1 Create a storage server of type SpanFS using the fully qualified domain name\n(FQDN) of the cluster.\n/usr/openv/netbackup/bin/admincmd/nbdevconfig -creatests\n-storage_server cluster_FQDN -stype SpanFS -media_server\nmedia_server\n2 Add credentials for the SpanFS server.\n/usr/openv/volmgr/bin/tpconfig -add -storage_server server_name\n-stype SpanFS -sts_user_id user_ID [-password password] [-st\nstorage_type] [-ca_file_path SpanFS_CA_certificate_path]\nTo update SpanFS server credentials\n◆ /usr/openv/volmgr/bin/tpconfig -update -storage_server server_name\n-stype SpanFS -sts_user_id user_ID [ password password] [\n-ca_file_path SpanFS_CA_certificate_path]" }, "9300": { "code": 9300, - "desc": "Falhou to encode o certificate revocation list (CRL).", - "first_action": "On o master servidor, examine o unified logs on o NetBackup servidor para", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ On o master servidor, examine o unified logs on o NetBackup servidor para\nnbwebservice (OID 466 e 484).\n■ On todos de o hosts involved in o communication, examine o unified logs para\nnbpxyhelper (OID 486).\n■ On o host onde o erro ocorreu, examine o legacy logs para nbcertcmd.\n■ Garanta que you use o NetBackup SSL libraries.\n■ Contate Cohesity Technical Support." + "desc": "Failed to encode the certificate revocation list (CRL).", + "first_action": "On the master server, examine the unified logs on the NetBackup server for", + "full_action": "Do the following, as appropriate:\n■ On the master server, examine the unified logs on the NetBackup server for\nnbwebservice (OID 466 and 484).\n■ On all of the hosts involved in the communication, examine the unified logs for\nnbpxyhelper (OID 486).\n■ On the host where the error occurred, examine the legacy logs for nbcertcmd.\n■ Ensure that you use the NetBackup SSL libraries.\n■ Contact Cohesity Technical Support." }, "9301": { "code": 9301, - "desc": "Falhou to decode o certificate revocation list (CRL).", - "first_action": "On o master servidor, examine o unified logs on o NetBackup servidor para", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ On o master servidor, examine o unified logs on o NetBackup servidor para\nnbwebservice (OID 466 e 484).\n■ On todos hosts involved in o communication, examine o unified logs para\nnbpxyhelper (OID 486).\n■ On o host onde o erro ocorreu, examine o legacy logs para nbcertcmd.\n■ Run o seguinte comando to get um new CRL para o corresponding domain:\n./nbcertcmd -getCrl [-servidor master servidor name]" + "desc": "Failed to decode the certificate revocation list (CRL).", + "first_action": "On the master server, examine the unified logs on the NetBackup server for", + "full_action": "Do the following, as appropriate:\n■ On the master server, examine the unified logs on the NetBackup server for\nnbwebservice (OID 466 and 484).\n■ On all hosts involved in the communication, examine the unified logs for\nnbpxyhelper (OID 486).\n■ On the host where the error occurred, examine the legacy logs for nbcertcmd.\n■ Run the following command to get a new CRL for the corresponding domain:\n./nbcertcmd -getCrl [-server master server name]" }, "9302": { "code": 9302, - "desc": "Attempted to replace o certificate revocation list (CRL) com um older version. NetBackup status codes 1117 NetBackup status codes", - "first_action": "On o host onde o erro ocorreu, examine o legacy logs para nbcertcmd.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ On o host onde o erro ocorreu, examine o legacy logs para nbcertcmd.\n■ On todos de o hosts involved in o communication, examine o unified logs para\nnbpxyhelper (OID 486)." + "desc": "Attempted to replace the certificate revocation list (CRL) with an older version. NetBackup status codes 1117 NetBackup status codes", + "first_action": "On the host where the error occurred, examine the legacy logs for nbcertcmd.", + "full_action": "Do the following, as appropriate:\n■ On the host where the error occurred, examine the legacy logs for nbcertcmd.\n■ On all of the hosts involved in the communication, examine the unified logs for\nnbpxyhelper (OID 486)." }, "9303": { "code": 9303, - "desc": "O web service request to fetch o certificate revocation list (CRL) falhou.", - "first_action": "On o host onde o erro ocorreu, examine o legacy logs para nbcertcmd.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ On o host onde o erro ocorreu, examine o legacy logs para nbcertcmd.\n■ On o master servidor, examine o unified logs on o NetBackup servidor para\nnbwebservice (OID 466 e 484).\n■ Garanta o seguinte:\n■ O master servidor está online.\n■ O web service (nbwmc) está online." + "desc": "The web service request to fetch the certificate revocation list (CRL) failed.", + "first_action": "On the host where the error occurred, examine the legacy logs for nbcertcmd.", + "full_action": "Do the following, as appropriate:\n■ On the host where the error occurred, examine the legacy logs for nbcertcmd.\n■ On the master server, examine the unified logs on the NetBackup server for\nnbwebservice (OID 466 and 484).\n■ Ensure the following:\n■ The master server is online.\n■ The web service (nbwmc) is online." }, "9304": { "code": 9304, - "desc": "O HTTP request está não complete; it should be checked again later.", - "first_action": "Examine o legacy logs para nbcertcmd e o unified", - "full_action": "Examine o legacy logs para nbcertcmd e o unified\nlogs on o NetBackup servidor para nbwebservice (OID 466 e 484)." + "desc": "The HTTP request is not complete; it should be checked again later.", + "first_action": "Examine the legacy logs for nbcertcmd and the unified", + "full_action": "Examine the legacy logs for nbcertcmd and the unified\nlogs on the NetBackup server for nbwebservice (OID 466 and 484)." }, "9305": { "code": 9305, - "desc": "Um attempt to refresh o certificate revocation list (CRL) e security level foi partially successful.", - "first_action": "Examine o legacy logs para nbcertcmd.", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Examine o legacy logs para nbcertcmd.\n■ Garanta que o HTTP request to fetch o CRL e o security level foi\nsuccessful.OntheNetBackupserver,examinetheunifiedlogsfornbwebservice\n(OID 466 e 484) para HTTP request failures." + "desc": "An attempt to refresh the certificate revocation list (CRL) and security level was partially successful.", + "first_action": "Examine the legacy logs for nbcertcmd.", + "full_action": "Do the following, as appropriate:\n■ Examine the legacy logs for nbcertcmd.\n■ Ensure that the HTTP request to fetch the CRL and the security level was\nsuccessful.OntheNetBackupserver,examinetheunifiedlogsfornbwebservice\n(OID 466 and 484) for HTTP request failures." }, "9306": { "code": 9306, - "desc": "O HTTP request para fetching o security level falhou.", - "first_action": "Examine o legacy logs para nbcertcmd e o unified logs on o NetBackup", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Examine o legacy logs para nbcertcmd e o unified logs on o NetBackup\nservidor para nbwebservice (OID 466 e 484).\n■ Garanta o seguinte:\n■ O master servidor está online.\n■ O web service (nbwmc) está online." + "desc": "The HTTP request for fetching the security level failed.", + "first_action": "Examine the legacy logs for nbcertcmd and the unified logs on the NetBackup", + "full_action": "Do the following, as appropriate:\n■ Examine the legacy logs for nbcertcmd and the unified logs on the NetBackup\nserver for nbwebservice (OID 466 and 484).\n■ Ensure the following:\n■ The master server is online.\n■ The web service (nbwmc) is online." }, "9307": { "code": 9307, - "desc": "O HTTP request to fetch o CRL falhou. O reason para o falha está unknown.", - "first_action": "Examine o legacy logs on o NetBackup host para", - "full_action": "Examine o legacy logs on o NetBackup host para\nnbcertcmd." + "desc": "The HTTP request to fetch the CRL failed. The reason for the failure is unknown.", + "first_action": "Examine the legacy logs on the NetBackup host for", + "full_action": "Examine the legacy logs on the NetBackup host for\nnbcertcmd." }, "9308": { "code": 9308, - "desc": "Falhou to ler o certificate revocation list (CRL).", - "first_action": "If NetBackup CA-signed certificate está used para communication: On todos o hosts", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ If NetBackup CA-signed certificate está used para communication: On todos o hosts\nthatareinvolvedinthecommunication,examinetheunifiedlogsfornbpxyhelper\n(OID 486).\n■ Examine o legacy logs para nbcertcmd.\n■ Para um Windows servidor, verifique que o seguinte directories exist:\ninstall_path\\NetBackup\\var\\vxss\\crl\nPara um clustered master servidor:\ninstall_path\\NetBackup\\var\\global\\vxss\\crl\n■ Para um UNIX servidor, verifique que o seguinte directories exist:\n/usr/openv/var/vxss/crl\nPara um clustered master servidor:\n/usr/openv/var/global/vxss/crl\n■ Para um Windows servidor, verifique in o certmapinfo.json arquivos que o crlPath\nvalues point to um valid caminho para o CRL:\ninstall_path\\NetBackup\\var\\vxss\\certmapinfo.json\nPara um clustered master servidor:\ninstall_path\\NetBackup\\var\\global\\vxss\\certmapinfo.json\n■ ForaUNIXserver,verifyinthecertmapinfo.jsonfilesthatthecrlPathvalues\npoint to um valid caminho para o CRL:\n/usr/openv/var/vxss/certmapinfo.json\nPara um clustered master servidor:\n/usr/openv/var/global/vxss/certmapinfo.json\n■ Run o seguinte comando para o master servidor:\n./nbcertcmd -getCRL -servidor master_server_name\nIf external CA-signed certificate está used para communication:\n■ On todos hosts que estão involved in o communication, examine o unified logs\npara nbpxyhelper (OID 486).\n■ Examine o legacy logs para nbcertcmd.\n■ Para um Windows servidor, verifique que o seguinte directories exist:\ninstall_path\\NetBackup\\var\\vxss\\crl\n■ Para um UNIX servidor, verifique que o seguinte directories exist:\n/usr/openv/var/vxss/crl\n■ Verifique if above diretório contains todos o requerido valid CRLs (como per\nECA_CRL_CHECK setting)." + "desc": "Failed to read the certificate revocation list (CRL).", + "first_action": "If NetBackup CA-signed certificate is used for communication: On all the hosts", + "full_action": "Do the following, as appropriate:\n■ If NetBackup CA-signed certificate is used for communication: On all the hosts\nthatareinvolvedinthecommunication,examinetheunifiedlogsfornbpxyhelper\n(OID 486).\n■ Examine the legacy logs for nbcertcmd.\n■ For a Windows server, verify that the following directories exist:\ninstall_path\\NetBackup\\var\\vxss\\crl\nFor a clustered master server:\ninstall_path\\NetBackup\\var\\global\\vxss\\crl\n■ For a UNIX server, verify that the following directories exist:\n/usr/openv/var/vxss/crl\nFor a clustered master server:\n/usr/openv/var/global/vxss/crl\n■ For a Windows server, verify in the certmapinfo.json files that the crlPath\nvalues point to a valid path for the CRL:\ninstall_path\\NetBackup\\var\\vxss\\certmapinfo.json\nFor a clustered master server:\ninstall_path\\NetBackup\\var\\global\\vxss\\certmapinfo.json\n■ ForaUNIXserver,verifyinthecertmapinfo.jsonfilesthatthecrlPathvalues\npoint to a valid path for the CRL:\n/usr/openv/var/vxss/certmapinfo.json\nFor a clustered master server:\n/usr/openv/var/global/vxss/certmapinfo.json\n■ Run the following command for the master server:\n./nbcertcmd -getCRL -server master_server_name\nIf external CA-signed certificate is used for communication:\n■ On all hosts that are involved in the communication, examine the unified logs\nfor nbpxyhelper (OID 486).\n■ Examine the legacy logs for nbcertcmd.\n■ For a Windows server, verify that the following directories exist:\ninstall_path\\NetBackup\\var\\vxss\\crl\n■ For a UNIX server, verify that the following directories exist:\n/usr/openv/var/vxss/crl\n■ Verify if above directory contains all the required valid CRLs (as per\nECA_CRL_CHECK setting)." }, "9309": { "code": 9309, - "desc": "Falhou to gravar o certificate revocation list (CRL).", - "first_action": "Examine o unified logs on o NetBackup servidor para nbwebservice (OID 466", - "full_action": "Execute os seguintes passos conforme apropriado:\n■ Examine o unified logs on o NetBackup servidor para nbwebservice (OID 466\ne 484) e o legacy logs para nbcertcmd.\n■ Para um Windows servidor, verifique que o seguinte directories exist:\ninstall_path\\NetBackup\\var\\vxss\\crl\nPara um clustered master servidor:\ninstall_path\\NetBackup\\var\\global\\vxss\\crl\n■ Para um UNIX servidor, verifique que o seguinte directories exist:\n/usr/openv/var/vxss/crl\nPara um clustered master servidor:\n/usr/openv/var/global/vxss/crl" + "desc": "Failed to write the certificate revocation list (CRL).", + "first_action": "Examine the unified logs on the NetBackup server for nbwebservice (OID 466", + "full_action": "Do the following, as appropriate:\n■ Examine the unified logs on the NetBackup server for nbwebservice (OID 466\nand 484) and the legacy logs for nbcertcmd.\n■ For a Windows server, verify that the following directories exist:\ninstall_path\\NetBackup\\var\\vxss\\crl\nFor a clustered master server:\ninstall_path\\NetBackup\\var\\global\\vxss\\crl\n■ For a UNIX server, verify that the following directories exist:\n/usr/openv/var/vxss/crl\nFor a clustered master server:\n/usr/openv/var/global/vxss/crl" }, "9310": { "code": 9310, - "desc": "O CRL para o specified issuer não é possível be found in o CRL cache.", - "first_action": "Provide o SHA-1 hash de o correct CRL issuer que", - "full_action": "Provide o SHA-1 hash de o correct CRL issuer que\nyou desejar to clean up from o CRL cache. O caminho para o CRL cache está:\n/usr/openv/var/vxss/crl." + "desc": "The CRL for the specified issuer cannot be found in the CRL cache.", + "first_action": "Provide the SHA-1 hash of the correct CRL issuer that", + "full_action": "Provide the SHA-1 hash of the correct CRL issuer that\nyou want to clean up from the CRL cache. The path for the CRL cache is:\n/usr/openv/var/vxss/crl." }, "9311": { "code": 9311, - "desc": "Falhou to clean up o CRL para o specified issuer from o CRL cache.", - "first_action": "Another process may have locked o CRL arquivo. Retry o", - "full_action": "Another process may have locked o CRL arquivo. Retry o\noperation." + "desc": "Failed to clean up the CRL for the specified issuer from the CRL cache.", + "first_action": "Another process may have locked the CRL file. Retry the", + "full_action": "Another process may have locked the CRL file. Retry the\noperation." }, "9312": { "code": 9312, - "desc": "Falhou to clean up o expired CRLs from o CRL cache.", - "first_action": "Another process may have locked o CRL arquivos. Retry", - "full_action": "Another process may have locked o CRL arquivos. Retry\no operation." + "desc": "Failed to clean up the expired CRLs from the CRL cache.", + "first_action": "Another process may have locked the CRL files. Retry", + "full_action": "Another process may have locked the CRL files. Retry\nthe operation." }, "9313": { "code": 9313, - "desc": "Falhou to clean up some de o expired CRLs from o CRL cache.", - "first_action": "Another process may have locked o CRL arquivos. Retry", - "full_action": "Another process may have locked o CRL arquivos. Retry\no operation." + "desc": "Failed to clean up some of the expired CRLs from the CRL cache.", + "first_action": "Another process may have locked the CRL files. Retry", + "full_action": "Another process may have locked the CRL files. Retry\nthe operation." }, "9314": { "code": 9314, - "desc": "O CRL está expired.", - "first_action": "Provide o CRLs que estão não expired.", - "full_action": "Provide o CRLs que estão não expired." + "desc": "The CRL is expired.", + "first_action": "Provide the CRLs that are not expired.", + "full_action": "Provide the CRLs that are not expired." }, "9315": { "code": 9315, - "desc": "Falhou to update some de o CRLs in o CRL cache.", - "first_action": "CRLs estão não expired.", - "full_action": "Garanta o seguinte:\n■ CRLs estão não expired.\n■ CRLs use um valid format.\n■ CRLs estão updated then o cached copy." + "desc": "Failed to update some of the CRLs in the CRL cache.", + "first_action": "CRLs are not expired.", + "full_action": "Ensure the following:\n■ CRLs are not expired.\n■ CRLs use a valid format.\n■ CRLs are updated then the cached copy." }, "9316": { "code": 9316, - "desc": "Falhou to update o CRLs in o CRL cache.", - "first_action": "CRLs estão não expired.", - "full_action": "Garanta o seguinte:\n■ CRLs estão não expired.\n■ CRLs use um valid format.\n■ CRLs estão updated then o cached copy." + "desc": "Failed to update the CRLs in the CRL cache.", + "first_action": "CRLs are not expired.", + "full_action": "Ensure the following:\n■ CRLs are not expired.\n■ CRLs use a valid format.\n■ CRLs are updated then the cached copy." }, "9317": { "code": 9317, - "desc": "O CRL verifique está disabled.", - "first_action": "Garanta que o ECA_CRL_CHECK configuration option está", - "full_action": "Garanta que o ECA_CRL_CHECK configuration option está\nset to LEAF ou CHAIN." + "desc": "The CRL check is disabled.", + "first_action": "Ensure that the ECA_CRL_CHECK configuration option is", + "full_action": "Ensure that the ECA_CRL_CHECK configuration option is\nset to LEAF or CHAIN." }, "9318": { "code": 9318, - "desc": "O certificate está revoked.", - "first_action": "If o certificate está não revoked e you still veja this erro,", - "full_action": "If o certificate está não revoked e you still veja this erro,\nverifique if o CRL está updated in o CRL cache. If o problema persists, contate seu\nsecurity administrator." + "desc": "The certificate is revoked.", + "first_action": "If the certificate is not revoked and you still see this error,", + "full_action": "If the certificate is not revoked and you still see this error,\ncheck if the CRL is updated in the CRL cache. If the problem persists, contact your\nsecurity administrator." }, "9319": { "code": 9319, - "desc": "O certificate está não revoked.", + "desc": "The certificate is not revoked.", "first_action": "Ifthecertificateis revokedand you stillsee thismessage,", - "full_action": "Ifthecertificateis revokedand you stillsee thismessage,\nverifique if o CRL está updated in o CRL cache. If o problema persists, contate seu\nsecurity administrator." + "full_action": "Ifthecertificateis revokedand you stillsee thismessage,\ncheck if the CRL is updated in the CRL cache. If the problem persists, contact your\nsecurity administrator." }, "9324": { "code": 9324, - "desc": "O CRL cache não é possível be updated. O ECA_CRL_PATH configuration option está não set to um valid CRL diretório caminho.", - "first_action": "Specify o correct diretório caminho para o ECA_CRL_PATH", - "full_action": "Specify o correct diretório caminho para o ECA_CRL_PATH\nconfiguration option." + "desc": "The CRL cache cannot be updated. The ECA_CRL_PATH configuration option is not set to a valid CRL directory path.", + "first_action": "Specify the correct directory path for the ECA_CRL_PATH", + "full_action": "Specify the correct directory path for the ECA_CRL_PATH\nconfiguration option." }, "9325": { "code": 9325, - "desc": "O CRL cache não é possível be updated. CRLs estão não disponível in o diretório que está set para o ECA_CRL_PATH configuration option.", + "desc": "The CRL cache cannot be updated. CRLs are not available in the directory that is set for the ECA_CRL_PATH configuration option.", "first_action": "SpecifyavalidCRLdirectorypaththatcontainsvalidCRL", - "full_action": "SpecifyavalidCRLdirectorypaththatcontainsvalidCRL\narquivos para o ECA_CRL_PATH configuration option." + "full_action": "SpecifyavalidCRLdirectorypaththatcontainsvalidCRL\nfiles for the ECA_CRL_PATH configuration option." }, "9326": { "code": 9326, - "desc": "O CRL está delta CRL.", - "first_action": "NetBackup does não support delta CRLs. You should", - "full_action": "NetBackup does não support delta CRLs. You should\nspecify um cheio CRL para o ECA_CRL_PATH ou para o CDP." + "desc": "The CRL is delta CRL.", + "first_action": "NetBackup does not support delta CRLs. You should", + "full_action": "NetBackup does not support delta CRLs. You should\nspecify a full CRL for the ECA_CRL_PATH or for the CDP." }, "9327": { "code": 9327, - "desc": "Não foi possível to retrieve CRL para o certificate.", - "first_action": "Verifique if o CRL exists in o CRL cache para o certificate issuer based on o", - "full_action": "Executar o seguinte:\n■ Verifique if o CRL exists in o CRL cache para o certificate issuer based on o\nECA_CRL_CHECK configuration option (CHAIN ou LEAF). If o CRL does não exist\nin o cache, do o seguinte:\n■ If o ECA_CRL_PATH configuration option está configurado, run o nbcertcmd\n-updatecrlcache comando.\n■ If CDP está enabled, verifique o bpclntcmd crldownloader logs.\nRefertoSee“" + "desc": "Unable to retrieve CRL for the certificate.", + "first_action": "Check if the CRL exists in the CRL cache for the certificate issuer based on the", + "full_action": "Perform the following:\n■ Check if the CRL exists in the CRL cache for the certificate issuer based on the\nECA_CRL_CHECK configuration option (CHAIN or LEAF). If the CRL does not exist\nin the cache, do the following:\n■ If the ECA_CRL_PATH configuration option is configured, run the nbcertcmd\n-updatecrlcache command.\n■ If CDP is enabled, check the bpclntcmd crldownloader logs.\nRefertoSee“" }, "9328": { "code": 9328, - "desc": "Não foi possível to decrypt o CRL signature.", - "first_action": "Para file-based certificates:", - "full_action": "Executar o seguinte:\n■ Para file-based certificates:\n■ Usetheopenssl verifycommandtocheckthecertificateagainsttheCRL.\n■ Para Windows certificate store:\n■ Exportthecertificateandruntheopenssl verifyorthecertUtilcommand.\n■ Iftheverificationfails,refertotheOpenSSLdocumentsorcontactyourSecurity\nAdministrator.\n■ If o verification está successful but o problema persists, contate Cohesity\nNetBackup support." + "desc": "Unable to decrypt the CRL signature.", + "first_action": "For file-based certificates:", + "full_action": "Perform the following:\n■ For file-based certificates:\n■ Usetheopenssl verifycommandtocheckthecertificateagainsttheCRL.\n■ For Windows certificate store:\n■ Exportthecertificateandruntheopenssl verifyorthecertUtilcommand.\n■ Iftheverificationfails,refertotheOpenSSLdocumentsorcontactyourSecurity\nAdministrator.\n■ If the verification is successful but the problem persists, contact Cohesity\nNetBackup support." }, "9329": { "code": 9329, - "desc": "CRL signature falha.", - "first_action": "Para file-based certificates:", - "full_action": "Executar o seguinte:\n■ Para file-based certificates:\n■ Usetheopenssl verifycommandtocheckthecertificateagainsttheCRL.\n■ Para Windows certificate store:\n■ Exportthecertificateandruntheopenssl verifyorthecertUtilcommand.\n■ Iftheverificationfails,refertotheOpenSSLdocumentsorcontactyourSecurity\nAdministrator.\n■ If o verification está successful but o problema persists, contate Cohesity\nNetBackup support." + "desc": "CRL signature failure.", + "first_action": "For file-based certificates:", + "full_action": "Perform the following:\n■ For file-based certificates:\n■ Usetheopenssl verifycommandtocheckthecertificateagainsttheCRL.\n■ For Windows certificate store:\n■ Exportthecertificateandruntheopenssl verifyorthecertUtilcommand.\n■ Iftheverificationfails,refertotheOpenSSLdocumentsorcontactyourSecurity\nAdministrator.\n■ If the verification is successful but the problem persists, contact Cohesity\nNetBackup support." }, "9330": { "code": 9330, - "desc": "O CRL está não yet valid.", - "first_action": "Verifique seu system time ou provide um valid CRL.", - "full_action": "Verifique seu system time ou provide um valid CRL." + "desc": "The CRL is not yet valid.", + "first_action": "Check your system time or provide a valid CRL.", + "full_action": "Check your system time or provide a valid CRL." }, "9331": { "code": 9331, - "desc": "O CRL last update date está não in um valid format.", - "first_action": "Verifique o CRL usando o openssl comando ou contate", - "full_action": "Verifique o CRL usando o openssl comando ou contate\nseu Security Administrator." + "desc": "The CRL last update date is not in a valid format.", + "first_action": "Check the CRL using the openssl command or contact", + "full_action": "Check the CRL using the openssl command or contact\nyour Security Administrator." }, "9332": { "code": 9332, - "desc": "O CRL next update date está não in um valid format.", - "first_action": "Verifique o CRL usando o openssl comando ou contate", - "full_action": "Verifique o CRL usando o openssl comando ou contate\nseu Security Administrator." + "desc": "The CRL next update date is not in a valid format.", + "first_action": "Check the CRL using the openssl command or contact", + "full_action": "Check the CRL using the openssl command or contact\nyour Security Administrator." }, "9333": { "code": 9333, - "desc": "Não foi possível to retrieve o CRL issuer certificate.", - "first_action": "Para file-based certificates:", - "full_action": "Executar o seguinte:\n■ Para file-based certificates:\n■ Usetheopenssl verifycommandtocheckthecertificateagainsttheCRL.\n■ Para Windows certificate store:\n■ Exportthecertificateandruntheopenssl verifyorthecertUtilcommand.\n■ Iftheverificationfails,refertotheOpenSSLdocumentsorcontactyourSecurity\nAdministrator.\n■ If o verification está successful but o problema persists, contate Cohesity\nNetBackup support." + "desc": "Unable to retrieve the CRL issuer certificate.", + "first_action": "For file-based certificates:", + "full_action": "Perform the following:\n■ For file-based certificates:\n■ Usetheopenssl verifycommandtocheckthecertificateagainsttheCRL.\n■ For Windows certificate store:\n■ Exportthecertificateandruntheopenssl verifyorthecertUtilcommand.\n■ Iftheverificationfails,refertotheOpenSSLdocumentsorcontactyourSecurity\nAdministrator.\n■ If the verification is successful but the problem persists, contact Cohesity\nNetBackup support." }, "9334": { "code": 9334, - "desc": "Key uso does não include CRL signing.", - "first_action": "Para file-based certificates:", - "full_action": "Executar o seguinte:\n■ Para file-based certificates:\n■ Usetheopenssl verifycommandtocheckthecertificateagainsttheCRL.\n■ Para Windows certificate store:\n■ Exportthecertificateandruntheopenssl verifyorthecertUtilcommand.\n■ Iftheverificationfails,refertotheOpenSSLdocumentsorcontactyourSecurity\nAdministrator.\n■ If o verification está successful but o problema persists, contate Cohesity\nNetBackup support." + "desc": "Key usage does not include CRL signing.", + "first_action": "For file-based certificates:", + "full_action": "Perform the following:\n■ For file-based certificates:\n■ Usetheopenssl verifycommandtocheckthecertificateagainsttheCRL.\n■ For Windows certificate store:\n■ Exportthecertificateandruntheopenssl verifyorthecertUtilcommand.\n■ Iftheverificationfails,refertotheOpenSSLdocumentsorcontactyourSecurity\nAdministrator.\n■ If the verification is successful but the problem persists, contact Cohesity\nNetBackup support." }, "9335": { "code": 9335, - "desc": "Critical CRL extension está não valid.", - "first_action": "Verifique o CRL usando o openssl comando ou contate", - "full_action": "Verifique o CRL usando o openssl comando ou contate\nseu Security Administrator." + "desc": "Critical CRL extension is not valid.", + "first_action": "Check the CRL using the openssl command or contact", + "full_action": "Check the CRL using the openssl command or contact\nyour Security Administrator." }, "9336": { "code": 9336, - "desc": "O CRL scope está different, it should cover todos revocation reasons.", - "first_action": "Verifique o CRL usando o openssl comando ou contate", - "full_action": "Verifique o CRL usando o openssl comando ou contate\nseu Security Administrator." + "desc": "The CRL scope is different, it should cover all revocation reasons.", + "first_action": "Check the CRL using the openssl command or contact", + "full_action": "Check the CRL using the openssl command or contact\nyour Security Administrator." }, "9337": { "code": 9337, - "desc": "CRL caminho validation erro.", - "first_action": "Para file-based certificates:", - "full_action": "Executar o seguinte:\n■ Para file-based certificates:\n■ Usetheopenssl verifycommandtocheckthecertificateagainsttheCRL.\n■ Para Windows certificate store:\n■ Exportthecertificateandruntheopenssl verifyorthecertUtilcommand.\n■ Iftheverificationfails,refertotheOpenSSLdocumentsorcontactyourSecurity\nAdministrator.\n■ If o verification está successful but o problema persists, contate Cohesity\nNetBackup support." + "desc": "CRL path validation error.", + "first_action": "For file-based certificates:", + "full_action": "Perform the following:\n■ For file-based certificates:\n■ Usetheopenssl verifycommandtocheckthecertificateagainsttheCRL.\n■ For Windows certificate store:\n■ Exportthecertificateandruntheopenssl verifyorthecertUtilcommand.\n■ Iftheverificationfails,refertotheOpenSSLdocumentsorcontactyourSecurity\nAdministrator.\n■ If the verification is successful but the problem persists, contact Cohesity\nNetBackup support." }, "9338": { "code": 9338, - "desc": "O CRL on o servidor está expired.", - "first_action": "Provide um valid CRL para o issuer de o cliente certificate.", - "full_action": "Provide um valid CRL para o issuer de o cliente certificate." + "desc": "The CRL on the server is expired.", + "first_action": "Provide a valid CRL for the issuer of the client certificate.", + "full_action": "Provide a valid CRL for the issuer of the client certificate." }, "9339": { "code": 9339, - "desc": "O CRL está não disponível on o servidor.", - "first_action": "Provide um valid CRL para o issuer de o cliente certificate", - "full_action": "Provide um valid CRL para o issuer de o cliente certificate\non o servidor host." + "desc": "The CRL is not available on the server.", + "first_action": "Provide a valid CRL for the issuer of the client certificate", + "full_action": "Provide a valid CRL for the issuer of the client certificate\non the server host." }, "9340": { "code": 9340, - "desc": "CRL servidor internal erro.", - "first_action": "Verifique o CRL configuration on o servidor ou refer to o", - "full_action": "Verifique o CRL configuration on o servidor ou refer to o\nAbout certificate revocation lists para external CA section in o NetBackup Security\ne Encryption Guide." + "desc": "CRL server internal error.", + "first_action": "Check the CRL configuration on the server or refer to the", + "full_action": "Check the CRL configuration on the server or refer to the\nAbout certificate revocation lists for external CA section in the NetBackup Security\nand Encryption Guide." }, "9350": { "code": 9350, - "desc": "O API key está não valid.", - "first_action": "Use um valid API key to access NetBackup APIs.", - "full_action": "Use um valid API key to access NetBackup APIs." + "desc": "The API key is not valid.", + "first_action": "Use a valid API key to access NetBackup APIs.", + "full_action": "Use a valid API key to access NetBackup APIs." }, "9351": { "code": 9351, - "desc": "O API key não é possível be generated.", - "first_action": "Contate Cohesity Technical Support para assistance.", - "full_action": "Contate Cohesity Technical Support para assistance." + "desc": "The API key cannot be generated.", + "first_action": "Contact Cohesity Technical Support for assistance.", + "full_action": "Contact Cohesity Technical Support for assistance." }, "9352": { "code": 9352, - "desc": "Um unexpected API key erro ocorreu.", - "first_action": "Contate Cohesity Technical Support para assistance.", - "full_action": "Contate Cohesity Technical Support para assistance." + "desc": "An unexpected API key error occurred.", + "first_action": "Contact Cohesity Technical Support for assistance.", + "full_action": "Contact Cohesity Technical Support for assistance." }, "9353": { "code": 9353, - "desc": "Um API key para o given usuário already exists.", - "first_action": "Excluir o existing API key para o usuário e recreate um", - "full_action": "Excluir o existing API key para o usuário e recreate um\nAPI key." + "desc": "An API key for the given user already exists.", + "first_action": "Delete the existing API key for the user and recreate an", + "full_action": "Delete the existing API key for the user and recreate an\nAPI key." }, "9354": { "code": 9354, - "desc": "O specified API key does não exist.", - "first_action": "O specified API key está não deleted.", - "full_action": "Garanta o seguinte:\n■ O specified API key está não deleted.\n■ O specified API key tag está correct." + "desc": "The specified API key does not exist.", + "first_action": "The specified API key is not deleted.", + "full_action": "Ensure the following:\n■ The specified API key is not deleted.\n■ The specified API key tag is correct." }, "9355": { "code": 9355, - "desc": "O API key has expired.", - "first_action": "Excluir o expired API key.", - "full_action": "Executar o seguinte actions:\n■ Excluir o expired API key.\n■ Create um new API key para o given usuário." + "desc": "The API key has expired.", + "first_action": "Delete the expired API key.", + "full_action": "Perform the following actions:\n■ Delete the expired API key.\n■ Create a new API key for the given user." }, "9356": { "code": 9356, - "desc": "O API key tag in o URL should match o ID from o payload.", - "first_action": "Provide o API key tag que está same como o ID in o", - "full_action": "Provide o API key tag que está same como o ID in o\npayload." + "desc": "The API key tag in the URL should match the ID from the payload.", + "first_action": "Provide the API key tag that is same as the ID in the", + "full_action": "Provide the API key tag that is same as the ID in the\npayload." }, "9357": { "code": 9357, "desc": "TheAPIkeyexpirationdatemustnotbelaterthan9999-12-31 23:59:59 +00:00.", - "first_action": "Provide um valid expiration date para o API key.", - "full_action": "Provide um valid expiration date para o API key." + "first_action": "Provide a valid expiration date for the API key.", + "full_action": "Provide a valid expiration date for the API key." }, "9380": { "code": 9380, "desc": "Themultipersonauthorizationrequestorthedatathatissentisnotvalid.", - "first_action": "Retry o operation com valid request e data.", - "full_action": "Executar o seguinte como appropriate:\nRetry o operation com valid request e data." + "first_action": "Retry the operation with valid request and data.", + "full_action": "Perform the following as appropriate:\nRetry the operation with valid request and data." }, "9381": { "code": 9381, - "desc": "O multiperson authorization request não é possível be processed.", + "desc": "The multiperson authorization request cannot be processed.", "first_action": "ChecktheNetBackupProblemsreportforadditionalinformationabouttheerror.", - "full_action": "Executar o seguinte como appropriate:\n■ ChecktheNetBackupProblemsreportforadditionalinformationabouttheerror.\n■ Aumentar o logging level. Retry o operation e verifique o resulting debug\nlogs." + "full_action": "Perform the following as appropriate:\n■ ChecktheNetBackupProblemsreportforadditionalinformationabouttheerror.\n■ Increase the logging level. Retry the operation and check the resulting debug\nlogs." }, "9382": { "code": 9382, - "desc": "O operation has falhou because it está configurado para multiperson authorization.", - "first_action": "Executar o operation usando NetBackup web UI.", - "full_action": "Executar o seguinte como appropriate:\n■ Executar o operation usando NetBackup web UI.\n■ Usethenbcmdruncommand.SeetheNetBackupCommandsReferenceGuide\npara more informação about o nbcmdrun comando.\n■ Contate o NetBackup Security Administrator to exempt from multiperson\nauthorization." + "desc": "The operation has failed because it is configured for multiperson authorization.", + "first_action": "Perform the operation using NetBackup web UI.", + "full_action": "Perform the following as appropriate:\n■ Perform the operation using NetBackup web UI.\n■ Usethenbcmdruncommand.SeetheNetBackupCommandsReferenceGuide\nfor more information about the nbcmdrun command.\n■ Contact the NetBackup Security Administrator to exempt from multiperson\nauthorization." }, "9383": { "code": 9383, - "desc": "O date está não within o allowed range que está between 01/01/1970 e o current date. NetBackup status codes 1133 NetBackup status codes", - "first_action": "Specify um valid date que está between 01/01/1970 e o current date.", - "full_action": "Executar o seguinte como appropriate:\nSpecify um valid date que está between 01/01/1970 e o current date." + "desc": "The date is not within the allowed range that is between 01/01/1970 and the current date. NetBackup status codes 1133 NetBackup status codes", + "first_action": "Specify a valid date that is between 01/01/1970 and the current date.", + "full_action": "Perform the following as appropriate:\nSpecify a valid date that is between 01/01/1970 and the current date." }, "9384": { "code": 9384, - "desc": "O multiperson authorization ticket com o given ID não é possível be found.", - "first_action": "Specify um valid ticket ID.", - "full_action": "Executar o seguinte como appropriate:\nSpecify um valid ticket ID." + "desc": "The multiperson authorization ticket with the given ID cannot be found.", + "first_action": "Specify a valid ticket ID.", + "full_action": "Perform the following as appropriate:\nSpecify a valid ticket ID." }, "9385": { "code": 9385, - "desc": "O current state de o multiperson authorization ticket está não valid.", - "first_action": "Verifique o current state de o multiperson ticket e take corrective actions before", - "full_action": "Executar o seguinte como appropriate:\nVerifique o current state de o multiperson ticket e take corrective actions before\nyou invoke o operation." + "desc": "The current state of the multiperson authorization ticket is not valid.", + "first_action": "Check the current state of the multiperson ticket and take corrective actions before", + "full_action": "Perform the following as appropriate:\nCheck the current state of the multiperson ticket and take corrective actions before\nyou invoke the operation." }, "9386": { "code": 9386, "desc": "Youdonothavethepermissionstoupdatethemultipersonauthorization ticket.", - "first_action": "Contate o NetBackup Administrator para o requerido permissions.", - "full_action": "Executar o seguinte como appropriate:\nContate o NetBackup Administrator para o requerido permissions." + "first_action": "Contact the NetBackup Administrator for the required permissions.", + "full_action": "Perform the following as appropriate:\nContact the NetBackup Administrator for the required permissions." }, "9387": { "code": 9387, - "desc": "Um multiperson authorization ticket está created para o given operation.", - "first_action": "Use o NetBackup web UI to verifique whether o associated multiperson", - "full_action": "Executar o seguinte como appropriate:\n■ Use o NetBackup web UI to verifique whether o associated multiperson\nauthorization ticket está approved ou não. Contate seu NetBackup administrator\northeNetBackupmultipersonauthorizationapprovertogetyourticketapproved.\n■ To prevent ticket generation para o associated usuário, contate o NetBackup\nSecurity Administrator to exempt o usuário from o multiperson authorization\nprocess." + "desc": "A multiperson authorization ticket is created for the given operation.", + "first_action": "Use the NetBackup web UI to verify whether the associated multiperson", + "full_action": "Perform the following as appropriate:\n■ Use the NetBackup web UI to verify whether the associated multiperson\nauthorization ticket is approved or not. Contact your NetBackup administrator\northeNetBackupmultipersonauthorizationapprovertogetyourticketapproved.\n■ To prevent ticket generation for the associated user, contact the NetBackup\nSecurity Administrator to exempt the user from the multiperson authorization\nprocess." }, "9388": { "code": 9388, - "desc": "O maximum limite de o images to be expired está reached.", - "first_action": "Split o bidfile into multiple arquivos such que each arquivo", - "full_action": "Split o bidfile into multiple arquivos such que each arquivo\ndoes não contain more than 30000 entradas." + "desc": "The maximum limit of the images to be expired is reached.", + "first_action": "Split the bidfile into multiple files such that each file", + "full_action": "Split the bidfile into multiple files such that each file\ndoes not contain more than 30000 entries." }, "9389": { "code": 9389, - "desc": "O operation has falhou because there está um pending ticket para o same entity.", - "first_action": "Make sure que o current request está resolved before you", - "full_action": "Make sure que o current request está resolved before you\nrequest another operation on o same entity." + "desc": "The operation has failed because there is a pending ticket for the same entity.", + "first_action": "Make sure that the current request is resolved before you", + "full_action": "Make sure that the current request is resolved before you\nrequest another operation on the same entity." }, "9391": { "code": 9391, - "desc": "You do não have o permissions to view o multiperson authorization ticket.", - "first_action": "Make sure que o requester has appropriate RBAC", - "full_action": "Make sure que o requester has appropriate RBAC\npermissions to fetch o multiperson authorization ticket informação which foi\ncreated on o behalf de ação de other usuário." + "desc": "You do not have the permissions to view the multiperson authorization ticket.", + "first_action": "Make sure that the requester has appropriate RBAC", + "full_action": "Make sure that the requester has appropriate RBAC\npermissions to fetch the multiperson authorization ticket information which was\ncreated on the behalf of action of other user." }, "9392": { "code": 9392, - "desc": "O authorization data que está associated com this multiperson authorization ticket não é possível be verified.", - "first_action": "Executar o requerido operation again so que um new", - "full_action": "Executar o requerido operation again so que um new\nmultiperson authorization ticket está created com valid authorization data." + "desc": "The authorization data that is associated with this multiperson authorization ticket cannot be verified.", + "first_action": "Perform the required operation again so that a new", + "full_action": "Perform the required operation again so that a new\nmultiperson authorization ticket is created with valid authorization data." }, "9400": { "code": 9400, - "desc": "O OData json está malformed.", + "desc": "The OData json is malformed.", "first_action": "PleasesubmitabugreportwiththeappropriateNetBackup", - "full_action": "PleasesubmitabugreportwiththeappropriateNetBackup\nlogs, including o logs para o process onde o erro foi encontrado e o\nweb service logs." + "full_action": "PleasesubmitabugreportwiththeappropriateNetBackup\nlogs, including the logs for the process where the error was encountered and the\nweb service logs." }, "9401": { "code": 9401, - "desc": "O OData filter criteria está inválido.", - "first_action": "Use um valid OData filter.", - "full_action": "Use um valid OData filter." + "desc": "The OData filter criteria is invalid.", + "first_action": "Use a valid OData filter.", + "full_action": "Use a valid OData filter." }, "9402": { "code": 9402, - "desc": "Um OData operator está não supported.", - "first_action": "Use um valid OData operator in o OData filter. Para OData", - "full_action": "Use um valid OData operator in o OData filter. Para OData\nsupport details, veja o seguinte article:\nhttp://www.veritas.com/docs/100043320" + "desc": "An OData operator is not supported.", + "first_action": "Use a valid OData operator in the OData filter. For OData", + "full_action": "Use a valid OData operator in the OData filter. For OData\nsupport details, see the following article:\nhttp://www.veritas.com/docs/100043320" }, "9403": { "code": 9403, - "desc": "Um OData entity data model (EDM) type está não supported.", - "first_action": "Use um supported OData entity model (EDM) type in o", - "full_action": "Use um supported OData entity model (EDM) type in o\nOData filter. Veja o seguinte article:\nhttp://www.veritas.com/docs/100043320" + "desc": "An OData entity data model (EDM) type is not supported.", + "first_action": "Use a supported OData entity model (EDM) type in the", + "full_action": "Use a supported OData entity model (EDM) type in the\nOData filter. See the following article:\nhttp://www.veritas.com/docs/100043320" }, "9404": { "code": 9404, - "desc": "Um operand para um OData operator ou method está inválido.", - "first_action": "Use um valid operand in o OData filter.", - "full_action": "Use um valid operand in o OData filter." + "desc": "An operand for an OData operator or method is invalid.", + "first_action": "Use a valid operand in the OData filter.", + "full_action": "Use a valid operand in the OData filter." }, "9405": { "code": 9405, - "desc": "Um OData method está não supported.", - "first_action": "Use um supported method in o OData filter. Veja o", - "full_action": "Use um supported method in o OData filter. Veja o\nseguinte article:\nhttp://www.veritas.com/docs/100043320" + "desc": "An OData method is not supported.", + "first_action": "Use a supported method in the OData filter. See the", + "full_action": "Use a supported method in the OData filter. See the\nfollowing article:\nhttp://www.veritas.com/docs/100043320" }, "9480": { "code": 9480, - "desc": "O usuário profile com o given ID não é possível be found.", - "first_action": "Make sure o correct ID está specified when you use o", - "full_action": "Make sure o correct ID está specified when you use o\nRESTful API." + "desc": "The user profile with the given ID cannot be found.", + "first_action": "Make sure the correct ID is specified when you use the", + "full_action": "Make sure the correct ID is specified when you use the\nRESTful API." }, "9481": { "code": 9481, - "desc": "O usuário profile request não é possível be processed.", + "desc": "The user profile request cannot be processed.", "first_action": "CollectthewebservicelogsandcontactCohesityTechnical", "full_action": "CollectthewebservicelogsandcontactCohesityTechnical\nSupport." }, "9482": { "code": 9482, - "desc": "O usuário does não have permissão to access o usuário profile com specified ID.", - "first_action": "Make sure que o requester has o necessary RBAC", - "full_action": "Make sure que o requester has o necessary RBAC\npermissions to fetch o usuário profile informação de other users." + "desc": "The user does not have permission to access the user profile with specified ID.", + "first_action": "Make sure that the requester has the necessary RBAC", + "full_action": "Make sure that the requester has the necessary RBAC\npermissions to fetch the user profile information of other users." }, "9483": { "code": 9483, - "desc": "O usuário does não have permissão to update o usuário profile com specified ID.", - "first_action": "Make sure que o requester has o necessary RBAC", - "full_action": "Make sure que o requester has o necessary RBAC\npermissions to update o usuário profile informação de other users." + "desc": "The user does not have permission to update the user profile with specified ID.", + "first_action": "Make sure that the requester has the necessary RBAC", + "full_action": "Make sure that the requester has the necessary RBAC\npermissions to update the user profile information of other users." }, "9484": { "code": 9484, "desc": "TheuserprofileIDspecifiedinrequestURLandpayloaddoesnotmatch.", - "first_action": "Specify o same ID in o request URL e body when", - "full_action": "Specify o same ID in o request URL e body when\nyou use o API to update o profile de um usuário com o specified ID." + "first_action": "Specify the same ID in the request URL and body when", + "full_action": "Specify the same ID in the request URL and body when\nyou use the API to update the profile of a user with the specified ID." }, "9490": { "code": 9490, - "desc": "Falhou to list o AD ou o LDAP servers.", - "first_action": "Retry o operation e review o logs in o seguinte", - "full_action": "Retry o operation e review o logs in o seguinte\ndiretório para more details.\nOn Windows: install_path\\NetBackup\\logs\\nbatd\nOn UNIX: /usr/openv/logs/nbatd\nPara more informação, refer to o NetBackup Security e Encryption Guide. If o\nissuepersists,visittheCohesityTechnicalSupportwebsite.TheCohesityTechnical\nSupport website offers additional informação to help you troubleshoot this issue." + "desc": "Failed to list the AD or the LDAP servers.", + "first_action": "Retry the operation and review the logs in the following", + "full_action": "Retry the operation and review the logs in the following\ndirectory for more details.\nOn Windows: install_path\\NetBackup\\logs\\nbatd\nOn UNIX: /usr/openv/logs/nbatd\nFor more information, refer to the NetBackup Security and Encryption Guide. If the\nissuepersists,visittheCohesityTechnicalSupportwebsite.TheCohesityTechnical\nSupport website offers additional information to help you troubleshoot this issue." }, "9491": { "code": 9491, - "desc": "Falhou to add o AD ou o LDAP servidor.", - "first_action": "Retry o operation e review o logs in o seguinte", - "full_action": "Retry o operation e review o logs in o seguinte\ndiretório para more details.\nOn Windows: install_path\\NetBackup\\logs\\nbatd\nOn UNIX: /usr/openv/logs/nbatd\nPara more informação, refer to o NetBackup Security e Encryption Guide. If o\nissuepersists,visittheCohesityTechnicalSupportwebsite.TheCohesityTechnical\nSupport website offers additional informação to help you troubleshoot this issue." + "desc": "Failed to add the AD or the LDAP server.", + "first_action": "Retry the operation and review the logs in the following", + "full_action": "Retry the operation and review the logs in the following\ndirectory for more details.\nOn Windows: install_path\\NetBackup\\logs\\nbatd\nOn UNIX: /usr/openv/logs/nbatd\nFor more information, refer to the NetBackup Security and Encryption Guide. If the\nissuepersists,visittheCohesityTechnicalSupportwebsite.TheCohesityTechnical\nSupport website offers additional information to help you troubleshoot this issue." }, "9492": { "code": 9492, - "desc": "Falhou to excluir o AD ou o LDAP servidor.", - "first_action": "Retry o operation e review o logs in o seguinte", - "full_action": "Retry o operation e review o logs in o seguinte\ndiretório para more details.\nOn Windows: install_path\\NetBackup\\logs\\nbatd\nOn UNIX: /usr/openv/logs/nbatd\nPara more informação, refer to o NetBackup Security e Encryption Guide. If o\nissuepersists,visittheCohesityTechnicalSupportwebsite.TheCohesityTechnical\nSupport website offers additional informação to help you troubleshoot this issue." + "desc": "Failed to delete the AD or the LDAP server.", + "first_action": "Retry the operation and review the logs in the following", + "full_action": "Retry the operation and review the logs in the following\ndirectory for more details.\nOn Windows: install_path\\NetBackup\\logs\\nbatd\nOn UNIX: /usr/openv/logs/nbatd\nFor more information, refer to the NetBackup Security and Encryption Guide. If the\nissuepersists,visittheCohesityTechnicalSupportwebsite.TheCohesityTechnical\nSupport website offers additional information to help you troubleshoot this issue." }, "9509": { "code": 9509, - "desc": "Falhou to create email body usando o template.", + "desc": "Failed to create email body using the template.", "first_action": "CollectthewebservicelogsandcontactCohesityTechnical", "full_action": "CollectthewebservicelogsandcontactCohesityTechnical\nSupport." }, "9550": { "code": 9550, - "desc": "Retry attempts foram exhausted para NetBackup OpenStack VM.", - "first_action": "Garanta o proper connectivity between o NetBackup host e NBOSVM", - "full_action": "Executar o seguinte como appropriate:\n■ Garanta o proper connectivity between o NetBackup host e NBOSVM\nservidor.\n■ Garanta que o requerido ports on NBOSVM estão abrir e accessible to o\nNetBackup hosts.\n■ Garanta que o NBOSVM servidor está registered properly com NetBackup." + "desc": "Retry attempts were exhausted for NetBackup OpenStack VM.", + "first_action": "Ensure the proper connectivity between the NetBackup host and NBOSVM", + "full_action": "Perform the following as appropriate:\n■ Ensure the proper connectivity between the NetBackup host and NBOSVM\nserver.\n■ Ensure that the required ports on NBOSVM are open and accessible to the\nNetBackup hosts.\n■ Ensure that the NBOSVM server is registered properly with NetBackup." }, "9551": { "code": 9551, - "desc": "Um internal servidor erro has ocorreu during NetBackup OpenStack VM operation.", - "first_action": "Veja o detailed erro message on o NetBackup activity monitor.", - "full_action": "Executar o seguinte como appropriate:\n■ Veja o detailed erro message on o NetBackup activity monitor.\n■ Verifique o status de o seguinte services on todos NBOSVM nodes:\n■ nbosjm-policies\n■ nbosjm-api\n■ nbosjm-scheduler\n■ nbosjm-cron\n■ Veja o nbosjm logs para more informação." + "desc": "An internal server error has occurred during NetBackup OpenStack VM operation.", + "first_action": "See the detailed error message on the NetBackup activity monitor.", + "full_action": "Perform the following as appropriate:\n■ See the detailed error message on the NetBackup activity monitor.\n■ Check the status of the following services on all NBOSVM nodes:\n■ nbosjm-policies\n■ nbosjm-api\n■ nbosjm-scheduler\n■ nbosjm-cron\n■ See the nbosjm logs for more information." }, "9552": { "code": 9552, - "desc": "NetBackup OpenStack VM authentication falhou.", - "first_action": "Garanta que o NBOSVM servidor está registered properly com NetBackup.", - "full_action": "Executar o seguinte como appropriate:\n■ Garanta que o NBOSVM servidor está registered properly com NetBackup.\n■ Veja o detailed erro message on o NetBackup activity monitor.\n■ Veja o nbosjm logs para more informação." + "desc": "NetBackup OpenStack VM authentication failed.", + "first_action": "Ensure that the NBOSVM server is registered properly with NetBackup.", + "full_action": "Perform the following as appropriate:\n■ Ensure that the NBOSVM server is registered properly with NetBackup.\n■ See the detailed error message on the NetBackup activity monitor.\n■ See the nbosjm logs for more information." }, "9553": { "code": 9553, - "desc": "NetBackup OpenStack VM backup API falhou.", - "first_action": "Veja o detailed erro message on o NetBackup activity monitor.", - "full_action": "Executar o seguinte como appropriate:\n■ Veja o detailed erro message on o NetBackup activity monitor.\n■ EnsurethatthesufficientdiskspaceisavailableonthetargetMSDPserverand\nuniversal share host." + "desc": "NetBackup OpenStack VM backup API failed.", + "first_action": "See the detailed error message on the NetBackup activity monitor.", + "full_action": "Perform the following as appropriate:\n■ See the detailed error message on the NetBackup activity monitor.\n■ EnsurethatthesufficientdiskspaceisavailableonthetargetMSDPserverand\nuniversal share host." }, "9554": { "code": 9554, - "desc": "Inválido snapshot metadata.", - "first_action": "Veja o nbosjm logs para more informação.", - "full_action": "Executar o seguinte como appropriate:\nVeja o nbosjm logs para more informação." + "desc": "Invalid snapshot metadata.", + "first_action": "See the nbosjm logs for more information.", + "full_action": "Perform the following as appropriate:\nSee the nbosjm logs for more information." }, "9555": { "code": 9555, - "desc": "Falhou to generate o NetBackup state arquivo.", - "first_action": "Veja o detailed erro message on o NetBackup activity monitor.", - "full_action": "Executar o seguinte como appropriate:\n■ Veja o detailed erro message on o NetBackup activity monitor.\n■ Veja o ncfnbcs logs para more informação." + "desc": "Failed to generate the NetBackup state file.", + "first_action": "See the detailed error message on the NetBackup activity monitor.", + "full_action": "Perform the following as appropriate:\n■ See the detailed error message on the NetBackup activity monitor.\n■ See the ncfnbcs logs for more information." }, "9556": { "code": 9556, - "desc": "Falhou to fetch o snapshot ID.", - "first_action": "Veja o ncfnbcs logs para more informação.", - "full_action": "Executar o seguinte como appropriate:\nVeja o ncfnbcs logs para more informação." + "desc": "Failed to fetch the snapshot ID.", + "first_action": "See the ncfnbcs logs for more information.", + "full_action": "Perform the following as appropriate:\nSee the ncfnbcs logs for more information." }, "9600": { "code": 9600, - "desc": "Não foi possível to excluir Asset group", + "desc": "Unable to delete Asset group", "first_action": "Removetheassetgroupfromanyprotectionplantowhich", - "full_action": "Removetheassetgroupfromanyprotectionplantowhich\nit belongs. Then, retry to excluir o asset group." + "full_action": "Removetheassetgroupfromanyprotectionplantowhich\nit belongs. Then, retry to delete the asset group." }, "9616": { "code": 9616, - "desc": "O migration process está in progress. O provided data may be inconsistent e incomplete. NetBackup status codes 1143 NetBackup status codes", - "first_action": "O migration process may take some time. Wait para", - "full_action": "O migration process may take some time. Wait para\nmigration to complete, then try o ação again." + "desc": "The migration process is in progress. The provided data may be inconsistent and incomplete. NetBackup status codes 1143 NetBackup status codes", + "first_action": "The migration process may take some time. Wait for", + "full_action": "The migration process may take some time. Wait for\nmigration to complete, then try the action again." }, "9700": { "code": 9700, - "desc": "Não foi possível to create subscription. O asset está covered por o same protection plan.", - "first_action": "Subscribe o same asset to different protection plan.", - "full_action": "Subscribe o same asset to different protection plan.\nGaranta que o asset ID specified está correct ou verifique que o protection plan ID está\ncorrect." + "desc": "Unable to create subscription. The asset is covered by the same protection plan.", + "first_action": "Subscribe the same asset to different protection plan.", + "full_action": "Subscribe the same asset to different protection plan.\nEnsure that the asset ID specified is correct or verify that the protection plan ID is\ncorrect." }, "9701": { "code": 9701, - "desc": "Não é possível complete o operation because o protection plan currently protects um asset.", - "first_action": "Unsubscribe todos o assets que estão subscribed to this", - "full_action": "Unsubscribe todos o assets que estão subscribed to this\nprotection plan e try again. Also, garanta que o asset ID specified está correct ou\nverifique que o protection plan ID está correct." + "desc": "Cannot complete the operation because the protection plan currently protects an asset.", + "first_action": "Unsubscribe all the assets that are subscribed to this", + "full_action": "Unsubscribe all the assets that are subscribed to this\nprotection plan and try again. Also, ensure that the asset ID specified is correct or\nverify that the protection plan ID is correct." }, "9702": { "code": 9702, "desc": "Thescheduleretentionissmallerthanorequaltotheschedulefrequency. This schedule issue may cause some data to be unprotected.", "first_action": "Edittheschedulesin theprotectionplantohaveretention", - "full_action": "Edittheschedulesin theprotectionplantohaveretention\ngreater than o frequency. Then, retry creating o protection plan." + "full_action": "Edittheschedulesin theprotectionplantohaveretention\ngreater than the frequency. Then, retry creating the protection plan." }, "9703": { "code": 9703, - "desc": "O schedule must have um backup window e não overlap está allowed.", - "first_action": "Garanta que each schedule has o same backup window", - "full_action": "Garanta que each schedule has o same backup window\ne make corrections if there estão qualquer overlaps. Then, retry o protection plan\ncreation." + "desc": "The schedule must have a backup window and no overlap is allowed.", + "first_action": "Ensure that each schedule has the same backup window", + "full_action": "Ensure that each schedule has the same backup window\nand make corrections if there are any overlaps. Then, retry the protection plan\ncreation." }, "9704": { "code": 9704, - "desc": "O duplication retention period must be greater than o schedule frequency.", + "desc": "The duplication retention period must be greater than the schedule frequency.", "first_action": "Edittheschedulewithduplicationtohaveretentiongreater", - "full_action": "Edittheschedulewithduplicationtohaveretentiongreater\nthan o schedule frequency. Then, retry creating o protection plan." + "full_action": "Edittheschedulewithduplicationtohaveretentiongreater\nthan the schedule frequency. Then, retry creating the protection plan." }, "9705": { "code": 9705, - "desc": "O PATCH request can apenas be used to update o description ou o armazenamento details de o protection plan.", - "first_action": "Garanta que o PATCH request apenas has um update de o", - "full_action": "Garanta que o PATCH request apenas has um update de o\ndescription ou o armazenamento details." + "desc": "The PATCH request can only be used to update the description or the storage details of the protection plan.", + "first_action": "Ensure that the PATCH request only has an update of the", + "full_action": "Ensure that the PATCH request only has an update of the\ndescription or the storage details." }, "9706": { "code": 9706, - "desc": "Um protection plan already exists com o same name. NetBackup status codes 1145 NetBackup status codes", - "first_action": "O name de o protection plan should be unique e", - "full_action": "O name de o protection plan should be unique e\nnão é possível be repeated. Retry o operation usando um different name para o protection\nplan." + "desc": "A protection plan already exists with the same name. NetBackup status codes 1145 NetBackup status codes", + "first_action": "The name of the protection plan should be unique and", + "full_action": "The name of the protection plan should be unique and\ncannot be repeated. Retry the operation using a different name for the protection\nplan." }, "9708": { "code": 9708, - "desc": "Um schedule must specify um backup armazenamento e um duplication armazenamento option. Replication must have um target master servidor e um target SLP. Todos armazenamento options must be o same para todos schedules.", - "first_action": "Garanta consistency between todos de o schedules com", - "full_action": "Garanta consistency between todos de o schedules com\nrespect to o armazenamento options." + "desc": "A schedule must specify a backup storage and a duplication storage option. Replication must have a target master server and a target SLP. All storage options must be the same for all schedules.", + "first_action": "Ensure consistency between all of the schedules with", + "full_action": "Ensure consistency between all of the schedules with\nrespect to the storage options." }, "9709": { "code": 9709, - "desc": "Protection plan para snapshot armazenamento must não have qualquer duplication, replication, ou armazenamento options.", - "first_action": "Create um protection plan without duplication, replication,", - "full_action": "Create um protection plan without duplication, replication,\ne armazenamento options para snapshot armazenamento." + "desc": "Protection plan for snapshot storage must not have any duplication, replication, or storage options.", + "first_action": "Create a protection plan without duplication, replication,", + "full_action": "Create a protection plan without duplication, replication,\nand storage options for snapshot storage." }, "9710": { "code": 9710, - "desc": "Tape está não um supported armazenamento option in um protection plan.", - "first_action": "Create um protection plan com um supported armazenamento type.", - "full_action": "Create um protection plan com um supported armazenamento type." + "desc": "Tape is not a supported storage option in a protection plan.", + "first_action": "Create a protection plan with a supported storage type.", + "full_action": "Create a protection plan with a supported storage type." }, "9711": { "code": 9711, - "desc": "Basic disco está não supported como part de SLP configuration.", - "first_action": "Create um protection plan com um supported armazenamento type.", - "full_action": "Create um protection plan com um supported armazenamento type." + "desc": "Basic disk is not supported as part of SLP configuration.", + "first_action": "Create a protection plan with a supported storage type.", + "full_action": "Create a protection plan with a supported storage type." }, "9712": { "code": 9712, - "desc": "O update ou create process did não complete. Inválido workload type.", - "first_action": "Set o correct workload type e try to update ou create", - "full_action": "Set o correct workload type e try to update ou create\no protection plan again." + "desc": "The update or create process did not complete. Invalid workload type.", + "first_action": "Set the correct workload type and try to update or create", + "full_action": "Set the correct workload type and try to update or create\nthe protection plan again." }, "9713": { "code": 9713, - "desc": "Não foi possível to create subscription. Schedule list está missing.", - "first_action": "Garanta que o protection plan está created com schedules.", - "full_action": "Garanta que o protection plan está created com schedules." + "desc": "Unable to create subscription. Schedule list is missing.", + "first_action": "Ensure that the protection plan is created with schedules.", + "full_action": "Ensure that the protection plan is created with schedules." }, "9714": { "code": 9714, - "desc": "Não foi possível to create subscription. Asset validation falhou.", - "first_action": "Garanta que o group ou o asset que foi subscribed", - "full_action": "Garanta que o group ou o asset que foi subscribed\nto que protection plan exists. Verifique o proper permissions para o asset ou o\ngroup." + "desc": "Unable to create subscription. Asset validation failed.", + "first_action": "Ensure that the group or the asset that was subscribed", + "full_action": "Ensure that the group or the asset that was subscribed\nto that protection plan exists. Verify the proper permissions for the asset or the\ngroup." }, "9715": { "code": 9715, - "desc": "Could não find asset ou asset group details para o given ID.", - "first_action": "Provide um valid asset ou asset group ID e retry o", - "full_action": "Provide um valid asset ou asset group ID e retry o\noperation." + "desc": "Could not find asset or asset group details for the given ID.", + "first_action": "Provide a valid asset or asset group ID and retry the", + "full_action": "Provide a valid asset or asset group ID and retry the\noperation." }, "9716": { "code": 9716, - "desc": "Não foi possível to create subscription. Cloud Asset provider generated ID está inválido.", - "first_action": "Provide um valid cloud asset e retry o operation.", - "full_action": "Provide um valid cloud asset e retry o operation." + "desc": "Unable to create subscription. Cloud Asset provider generated ID is invalid.", + "first_action": "Provide a valid cloud asset and retry the operation.", + "full_action": "Provide a valid cloud asset and retry the operation." }, "9717": { "code": 9717, - "desc": "Não foi possível to create subscription. Não instance UUID found para o asset.", - "first_action": "Provide um valid instance UUID para o asset e retry o", - "full_action": "Provide um valid instance UUID para o asset e retry o\nprocess." + "desc": "Unable to create subscription. No instance UUID found for the asset.", + "first_action": "Provide a valid instance UUID for the asset and retry the", + "full_action": "Provide a valid instance UUID for the asset and retry the\nprocess." }, "9718": { "code": 9718, - "desc": "Não foi possível to create subscription. Inválido selection type specified.", - "first_action": "Rerun o operation. If o problema persists, save todos de", - "full_action": "Rerun o operation. If o problema persists, save todos de\no erro log informação e contate Cohesity Technical Support." + "desc": "Unable to create subscription. Invalid selection type specified.", + "first_action": "Rerun the operation. If the problem persists, save all of", + "full_action": "Rerun the operation. If the problem persists, save all of\nthe error log information and contact Cohesity Technical Support." }, "9719": { "code": 9719, - "desc": "O replication retention period must be greater than o schedule frequency.", + "desc": "The replication retention period must be greater than the schedule frequency.", "first_action": "Edittheschedulewithreplicationtohaveretentiongreater", - "full_action": "Edittheschedulewithreplicationtohaveretentiongreater\nthan schedule frequency. Then, retry creating o protection plan." + "full_action": "Edittheschedulewithreplicationtohaveretentiongreater\nthan schedule frequency. Then, retry creating the protection plan." }, "9720": { "code": 9720, - "desc": "Não é possível add ou excluir um schedule protection plan. Also, each schedule must specify armazenamento attributes.", - "first_action": "Verifique whether valid armazenamento units estão included para each", - "full_action": "Verifique whether valid armazenamento units estão included para each\nde o selected operations (backup, replication, LTR). Adjust o protection plan\narmazenamento options to include valid options para backup, replication, e LTR." + "desc": "Cannot add or delete a schedule protection plan. Also, each schedule must specify storage attributes.", + "first_action": "Verify whether valid storage units are included for each", + "full_action": "Verify whether valid storage units are included for each\nof the selected operations (backup, replication, LTR). Adjust the protection plan\nstorage options to include valid options for backup, replication, and LTR." }, "9722": { "code": 9722, - "desc": "ID must be same in o request URL e o body.", - "first_action": "Verifique que you use o same protection ID in URL e", - "full_action": "Verifique que you use o same protection ID in URL e\no body." + "desc": "ID must be same in the request URL and the body.", + "first_action": "Verify that you use the same protection ID in URL and", + "full_action": "Verify that you use the same protection ID in URL and\nthe body." }, "9723": { "code": 9723, - "desc": "Não é possível subscribe VMware asset to snapshot armazenamento protection plan ou cloud asset to non-snapshot armazenamento protection plan.", - "first_action": "Subscribe VMware asset to um non-snapshot armazenamento", - "full_action": "Subscribe VMware asset to um non-snapshot armazenamento\nprotection plan ou subscribe um cloud asset to um snapshot armazenamento (cloud) protection\nplan." + "desc": "Cannot subscribe VMware asset to snapshot storage protection plan or cloud asset to non-snapshot storage protection plan.", + "first_action": "Subscribe VMware asset to a non-snapshot storage", + "full_action": "Subscribe VMware asset to a non-snapshot storage\nprotection plan or subscribe a cloud asset to a snapshot storage (cloud) protection\nplan." }, "9724": { "code": 9724, - "desc": "Não foi possível to find o protection plan para o given ID.", + "desc": "Unable to find the protection plan for the given ID.", "first_action": "ReviewtheprotectionplanIDandprovideavalidprotection", "full_action": "ReviewtheprotectionplanIDandprovideavalidprotection\nplan ID." }, "9725": { "code": 9725, - "desc": "O protection plan does não support o SLP operation que o policy uses.", + "desc": "The protection plan does not support the SLP operation that the policy uses.", "first_action": "Use supported SLP operation in policy.", "full_action": "Use supported SLP operation in policy." }, "9726": { "code": 9726, - "desc": "O protection plan does não support multiple copies within um schedule.", + "desc": "The protection plan does not support multiple copies within a schedule.", "first_action": "Use single copy in policy schedule.", "full_action": "Use single copy in policy schedule." }, "9731": { "code": 9731, - "desc": "Não foi possível to find subscription para given ID.", - "first_action": "Specify um valid protection plan ID.", - "full_action": "Specify um valid protection plan ID." + "desc": "Unable to find subscription for given ID.", + "first_action": "Specify a valid protection plan ID.", + "full_action": "Specify a valid protection plan ID." }, "9732": { "code": 9732, - "desc": "O cloud snapshot replication retention period must be greater than o schedule frequency.", - "first_action": "Adjust o cloud snapshot replication retention period ou", - "full_action": "Adjust o cloud snapshot replication retention period ou\nadjust o frequency in o schedule." + "desc": "The cloud snapshot replication retention period must be greater than the schedule frequency.", + "first_action": "Adjust the cloud snapshot replication retention period or", + "full_action": "Adjust the cloud snapshot replication retention period or\nadjust the frequency in the schedule." }, "9733": { "code": 9733, - "desc": "Multi-target cloud snapshot replication está não supported.", - "first_action": "Use o same replication target que está set para cloud", - "full_action": "Use o same replication target que está set para cloud\nreplication." + "desc": "Multi-target cloud snapshot replication is not supported.", + "first_action": "Use the same replication target that is set for cloud", + "full_action": "Use the same replication target that is set for cloud\nreplication." }, "9734": { "code": 9734, - "desc": "O cloud replication está não compatible com specified workload type.", - "first_action": "Set cloud como workload type.", - "full_action": "Set cloud como workload type." + "desc": "The cloud replication is not compatible with specified workload type.", + "first_action": "Set cloud as workload type.", + "full_action": "Set cloud as workload type." }, "9735": { "code": 9735, - "desc": "O assets must be o same workload type to add them to um existing protection plan.", - "first_action": "Subscribe o asset ou o asset group to um protection", - "full_action": "Subscribe o asset ou o asset group to um protection\nplan com o matching workload type." + "desc": "The assets must be the same workload type to add them to an existing protection plan.", + "first_action": "Subscribe the asset or the asset group to a protection", + "full_action": "Subscribe the asset or the asset group to a protection\nplan with the matching workload type." }, "9736": { "code": 9736, - "desc": "Frequency must be specified para frequency-based schedules e includeDatesmustbespecifiedforcalendar-basedschedules.Thesefieldscannot be specified simultaneously.", + "desc": "Frequency must be specified for frequency-based schedules and includeDatesmustbespecifiedforcalendar-basedschedules.Thesefieldscannot be specified simultaneously.", "first_action": "SpecifyexactlyoneoffrequencySecondsorincludeDates", - "full_action": "SpecifyexactlyoneoffrequencySecondsorincludeDates\nattribute when you create ou modify um protection plan ou subscription." + "full_action": "SpecifyexactlyoneoffrequencySecondsorincludeDates\nattribute when you create or modify a protection plan or subscription." }, "9737": { "code": 9737, - "desc": "Schedule type must be specified para calendar-based schedules.", - "first_action": "Specify o schedule type (appropriate para o workload)", - "full_action": "Specify o schedule type (appropriate para o workload)\npara o calendar-based schedule." + "desc": "Schedule type must be specified for calendar-based schedules.", + "first_action": "Specify the schedule type (appropriate for the workload)", + "full_action": "Specify the schedule type (appropriate for the workload)\nfor the calendar-based schedule." }, "9738": { "code": 9738, - "desc": "Subscription edit está não allowed para Cloud workload type.", - "first_action": "Set o allowSubscriptionEdit attribute to false para um", - "full_action": "Set o allowSubscriptionEdit attribute to false para um\nprotection plan com workloadTypeCloud." + "desc": "Subscription edit is not allowed for Cloud workload type.", + "first_action": "Set the allowSubscriptionEdit attribute to false for a", + "full_action": "Set the allowSubscriptionEdit attribute to false for a\nprotection plan with workloadTypeCloud." }, "9739": { "code": 9739, - "desc": "PUT protection plan ou subscription must provide o same inputs como POST. Both schedules e policy attributes must be supplied.", - "first_action": "Supply todos requerido fields para PUT", - "full_action": "Supply todos requerido fields para PUT\n/servicecatalog/slos/{sloId}/subscriptions/{subId} ou PUT\n/servicecatalog/slos/{sloId}. O schedules e policyDefinition estão\nrequerido fields." + "desc": "PUT protection plan or subscription must provide the same inputs as POST. Both schedules and policy attributes must be supplied.", + "first_action": "Supply all required fields for PUT", + "full_action": "Supply all required fields for PUT\n/servicecatalog/slos/{sloId}/subscriptions/{subId} or PUT\n/servicecatalog/slos/{sloId}. The schedules and policyDefinition are\nrequired fields." }, "9740": { "code": 9740, - "desc": "O upgrade de this protection plan to NetBackup 8.2 ou later produced um falha.", + "desc": "The upgrade of this protection plan to NetBackup 8.2 or later produced a failure.", "first_action": "Creatingor deletinga subscriptiondoesnotwork untilthe", - "full_action": "Creatingor deletinga subscriptiondoesnotwork untilthe\nprotection plan has been converted from um 8.2.1 protection plan. Normally, this\nconversion happens automatically. Wait para um few minutes, then retry o operation.\nIf o conversion está não successful, o process can be triggered immediately por\nretrieving o details de o protection plan por modifying o URL. Modify o URL\nin o NetBackup web UI to:\nhttps://:1556/webui/protection-plans/{sloId}\nIf o falha está due to um intermittent problema when NetBackup policies ou armazenamento\nlifecycle policies (SLPs) estão created, um retry may succeed.\nOtherwise,theoldprotectionplanmaybeunusable.Inthiscase,existingsubscribed\nasset protection está still active e backup jobs still run. Consider creating um new\nprotection plan e migrating o subscriptions to this new protection plan. O\ndefinition de o old ProtectionPlan está persisted in o NetBackup banco de dados.\nContate Cohesity Technical Support para assistance in retrieving o old protection\nplan definition." + "full_action": "Creatingor deletinga subscriptiondoesnotwork untilthe\nprotection plan has been converted from an 8.2.1 protection plan. Normally, this\nconversion happens automatically. Wait for a few minutes, then retry the operation.\nIf the conversion is not successful, the process can be triggered immediately by\nretrieving the details of the protection plan by modifying the URL. Modify the URL\nin the NetBackup web UI to:\nhttps://:1556/webui/protection-plans/{sloId}\nIf the failure is due to an intermittent problem when NetBackup policies or storage\nlifecycle policies (SLPs) are created, a retry may succeed.\nOtherwise,theoldprotectionplanmaybeunusable.Inthiscase,existingsubscribed\nasset protection is still active and backup jobs still run. Consider creating a new\nprotection plan and migrating the subscriptions to this new protection plan. The\ndefinition of the old ProtectionPlan is persisted in the NetBackup database.\nContact Cohesity Technical Support for assistance in retrieving the old protection\nplan definition." }, "9741": { "code": 9741, - "desc": "O protection plan updates partially succeeded.", - "first_action": "Verifique com backup administrator to garanta que o jobs", - "full_action": "Verifique com backup administrator to garanta que o jobs\n(created por SLPs) gravar to o correct armazenamento unidade. Run GET PP API to get o\ncorrect state. Retry o update operation com correct armazenamento informação." + "desc": "The protection plan updates partially succeeded.", + "first_action": "Verify with backup administrator to ensure that the jobs", + "full_action": "Verify with backup administrator to ensure that the jobs\n(created by SLPs) write to the correct storage unit. Run GET PP API to get the\ncorrect state. Retry the update operation with correct storage information." }, "9743": { "code": 9743, "desc": "Multiple transaction log schedules found.", - "first_action": "Retry o operation e if o issue persists, visit o", - "full_action": "Retry o operation e if o issue persists, visit o\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional informação to help you troubleshoot this issue." + "first_action": "Retry the operation and if the issue persists, visit the", + "full_action": "Retry the operation and if the issue persists, visit the\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional information to help you troubleshoot this issue." }, "9744": { "code": 9744, - "desc": "O subscription contains one ou more configuration entradas que have não been delegated to this usuário.", - "first_action": "Based on o contents de o erro payload, identify o", - "full_action": "Based on o contents de o erro payload, identify o\nconfigurationentriesthathavenotbeendelegatedtothesubscribinguser.Remove\nthose entradas from o subscription payload, e retry o request. If o subscriber\nnão é possível use o protection plan without changes, they may request delegation de\nadditional subscription customization capabilities on que protection plan. If nenhum de\no delegation rules contain o necessary attributes, um administrator com o\nCREATE operation on o PROTECTION_PLAN namespace must create um protection\nplan com appropriate protection customizations." + "desc": "The subscription contains one or more configuration entries that have not been delegated to this user.", + "first_action": "Based on the contents of the error payload, identify the", + "full_action": "Based on the contents of the error payload, identify the\nconfigurationentriesthathavenotbeendelegatedtothesubscribinguser.Remove\nthose entries from the subscription payload, and retry the request. If the subscriber\ncannot use the protection plan without changes, they may request delegation of\nadditional subscription customization capabilities on that protection plan. If none of\nthe delegation rules contain the necessary attributes, an administrator with the\nCREATE operation on the PROTECTION_PLAN namespace must create a protection\nplan with appropriate protection customizations." }, "9745": { "code": 9745, - "desc": "Um subscription não é possível excluir inherited protection plan schedules.", + "desc": "A subscription cannot delete inherited protection plan schedules.", "first_action": "Whenattemptingtocustomizescheduling,ensurethatall", - "full_action": "Whenattemptingtocustomizescheduling,ensurethatall\nde o schedules from o protection plan estão represented in o schedule payload.\nIf não attempting to customize schedules, do não include o schedule section de\no payload. If o subscriber não é possível use o schedules que estão inherited from o\nprotectionplan,anadministratorwiththeCREATEoperationonthePROTECTION_PLAN\nnamespace must create um protection plan com appropriate schedules." + "full_action": "Whenattemptingtocustomizescheduling,ensurethatall\nof the schedules from the protection plan are represented in the schedule payload.\nIf not attempting to customize schedules, do not include the schedule section of\nthe payload. If the subscriber cannot use the schedules that are inherited from the\nprotectionplan,anadministratorwiththeCREATEoperationonthePROTECTION_PLAN\nnamespace must create a protection plan with appropriate schedules." }, "9746": { "code": 9746, - "desc": "Um subscription não é possível add schedules.", + "desc": "A subscription cannot add schedules.", "first_action": "Ifthesubscribercannotusetheschedulesthatareinherited", - "full_action": "Ifthesubscribercannotusetheschedulesthatareinherited\nfrom o protection plan, um administrator com o CREATE operation on o\nPROTECTION_PLAN namespace must create um protection plan com appropriate\nschedules." + "full_action": "Ifthesubscribercannotusetheschedulesthatareinherited\nfrom the protection plan, an administrator with the CREATE operation on the\nPROTECTION_PLAN namespace must create a protection plan with appropriate\nschedules." }, "9747": { "code": 9747, - "desc": "At least one subscription schedule does não supply o scheduleName field que está requerido to identify o protection plan schedule being edited.", - "first_action": "Review o subscription schedule payload, e garanta", - "full_action": "Review o subscription schedule payload, e garanta\nque todos scheduleName fields estão populated com o name de o schedule to which\no edit aplica-se." + "desc": "At least one subscription schedule does not supply the scheduleName field that is required to identify the protection plan schedule being edited.", + "first_action": "Review the subscription schedule payload, and ensure", + "full_action": "Review the subscription schedule payload, and ensure\nthat all scheduleName fields are populated with the name of the schedule to which\nthe edit applies." }, "9748": { "code": 9748, - "desc": "CannotsubscribeorbackupMicrosoftSQLServeravailabilitygroupwith o protection plan because de incorrect policy options.", - "first_action": "Select o Availability banco de dados backup preference", - "full_action": "Select o Availability banco de dados backup preference\noption in o protection plan. In combination com que option, you can select o\nProtect primary replica option ou o Protect preferred replica option." + "desc": "CannotsubscribeorbackupMicrosoftSQLServeravailabilitygroupwith the protection plan because of incorrect policy options.", + "first_action": "Select the Availability database backup preference", + "full_action": "Select the Availability database backup preference\noption in the protection plan. In combination with that option, you can select the\nProtect primary replica option or the Protect preferred replica option." }, "9749": { "code": 9749, - "desc": "Não é possível subscribe ou backup Microsoft SQL Servidor availability group banco de dados com o protection plan because de incorrect policy options.", - "first_action": "Clear o selection de o Availability banco de dados backup preference option.", - "full_action": "Intheprotectionplan,performoneofthefollowingoptions:\n■ Clear o selection de o Availability banco de dados backup preference option.\n■ Select o Availability banco de dados backup preference option e o Protect\nprimary replica option para o protection plan.\n■ Select o Availability banco de dados backup preference option e o Protect\npreferred replica option para o protection plan." + "desc": "Cannot subscribe or backup Microsoft SQL Server availability group database with the protection plan because of incorrect policy options.", + "first_action": "Clear the selection of the Availability database backup preference option.", + "full_action": "Intheprotectionplan,performoneofthefollowingoptions:\n■ Clear the selection of the Availability database backup preference option.\n■ Select the Availability database backup preference option and the Protect\nprimary replica option for the protection plan.\n■ Select the Availability database backup preference option and the Protect\npreferred replica option for the protection plan." }, "9751": { "code": 9751, - "desc": "O update ou create process did não complete due to um inválido cloud provider type.", - "first_action": "Set o correct cloud provider type e try to update ou", - "full_action": "Set o correct cloud provider type e try to update ou\ncreate o protection plan again." + "desc": "The update or create process did not complete due to an invalid cloud provider type.", + "first_action": "Set the correct cloud provider type and try to update or", + "full_action": "Set the correct cloud provider type and try to update or\ncreate the protection plan again." }, "9752": { "code": 9752, - "desc": "O cloud assets must be o same cloud provider type to add them to um existing protection plan.", - "first_action": "Subscribe o asset ou o asset group to um protection", - "full_action": "Subscribe o asset ou o asset group to um protection\nplan com o matching cloud provider type." + "desc": "The cloud assets must be the same cloud provider type to add them to an existing protection plan.", + "first_action": "Subscribe the asset or the asset group to a protection", + "full_action": "Subscribe the asset or the asset group to a protection\nplan with the matching cloud provider type." }, "9760": { "code": 9760, - "desc": "Um protection plan que has enabled o disco exclusion option can apenas be applied to o cloud VM type assets.", - "first_action": "Make sure que you apply um protection plan com disco", - "full_action": "Make sure que you apply um protection plan com disco\nexclusion option to o VM (host type) assets apenas." + "desc": "A protection plan that has enabled the disk exclusion option can only be applied to the cloud VM type assets.", + "first_action": "Make sure that you apply a protection plan with disk", + "full_action": "Make sure that you apply a protection plan with disk\nexclusion option to the VM (host type) assets only." }, "9764": { "code": 9764, - "desc": "Backup from snapshot operation está supported on o NetBackup mídia servidor 10.0 e later versions.", - "first_action": "10.0, you must upgrade que mídia servidor.", - "full_action": "To run o backup from snapshot, verifique que o mídia\nserver’s latest version está 10.0 ou newer. If o mídia server's version está older than\n10.0, you must upgrade que mídia servidor." + "desc": "Backup from snapshot operation is supported on the NetBackup media server 10.0 and later versions.", + "first_action": "10.0, you must upgrade that media server.", + "full_action": "To run the backup from snapshot, verify that the media\nserver’s latest version is 10.0 or newer. If the media server's version is older than\n10.0, you must upgrade that media server." }, "9765": { "code": 9765, - "desc": "YoucansubscribeorbackuponlycloudPaaSassetsusingaprotection plan com primary backup operation.", - "first_action": "Subscribe um PaaS protection plan apenas to PaaS assets.", - "full_action": "Subscribe um PaaS protection plan apenas to PaaS assets." + "desc": "YoucansubscribeorbackuponlycloudPaaSassetsusingaprotection plan with primary backup operation.", + "first_action": "Subscribe a PaaS protection plan only to PaaS assets.", + "full_action": "Subscribe a PaaS protection plan only to PaaS assets." }, "9766": { "code": 9766, - "desc": "Protection plan com backup armazenamento está não supported com provided operations like replication, backup from snapshot, e cloud index.", - "first_action": "Create um protection plan com um backup armazenamento unidade ou", - "full_action": "Create um protection plan com um backup armazenamento unidade ou\ncom duplication enabled." + "desc": "Protection plan with backup storage is not supported with provided operations like replication, backup from snapshot, and cloud index.", + "first_action": "Create a protection plan with a backup storage unit or", + "full_action": "Create a protection plan with a backup storage unit or\nwith duplication enabled." }, "9767": { "code": 9767, - "desc": "Schedules having não backup armazenamento unidade does não support provided policy attributes.", - "first_action": "Um protection plan com um staging armazenamento caminho PaaS", - "full_action": "Um protection plan com um staging armazenamento caminho PaaS\nprotection flag must have backup armazenamento configurado in o schedule." + "desc": "Schedules having no backup storage unit does not support provided policy attributes.", + "first_action": "A protection plan with a staging storage path PaaS", + "full_action": "A protection plan with a staging storage path PaaS\nprotection flag must have backup storage configured in the schedule." }, "9768": { "code": 9768, - "desc": "Schedules having backup armazenamento units must have PaaS protection enabled com um explicit staging armazenamento caminho.", - "first_action": "Create um PaaS protection enabled protection plan por", - "full_action": "Create um PaaS protection enabled protection plan por\nspecifying um staging armazenamento caminho e PaaS protection flag along com backup\narmazenamento in o schedule." + "desc": "Schedules having backup storage units must have PaaS protection enabled with an explicit staging storage path.", + "first_action": "Create a PaaS protection enabled protection plan by", + "full_action": "Create a PaaS protection enabled protection plan by\nspecifying a staging storage path and PaaS protection flag along with backup\nstorage in the schedule." }, "9769": { "code": 9769, - "desc": "MSDP instant access enabled armazenamento está o apenas supported armazenamento option para um protection plan.", - "first_action": "Provide um MSDP armazenamento com instant access enabled in", - "full_action": "Provide um MSDP armazenamento com instant access enabled in\no protection plan." + "desc": "MSDP instant access enabled storage is the only supported storage option for a protection plan.", + "first_action": "Provide an MSDP storage with instant access enabled in", + "full_action": "Provide an MSDP storage with instant access enabled in\nthe protection plan." }, "9770": { "code": 9770, - "desc": "Associate credentials com o asset ou o parent asset to subscribe it to um PaaS protection plan.", + "desc": "Associate credentials with the asset or the parent asset to subscribe it to a PaaS protection plan.", "first_action": "AddcredentialstotheassetoritsparentusingCredential", "full_action": "AddcredentialstotheassetoritsparentusingCredential\nmanagement option." }, "9771": { "code": 9771, - "desc": "Não é possível subscribe o PaaS assets com multi-byte characters in o displaynamestotheprotectionplanbecausetheyarenotsupportedontheprimary servers executando Windows.", + "desc": "Cannot subscribe the PaaS assets with multi-byte characters in the displaynamestotheprotectionplanbecausetheyarenotsupportedontheprimary servers running Windows.", "first_action": "ThePaaSassetswithmulti-byteornon-Englishcharacters", - "full_action": "ThePaaSassetswithmulti-byteornon-Englishcharacters\nin o display name must be salvo up e restored usando um Linux primary servidor." + "full_action": "ThePaaSassetswithmulti-byteornon-Englishcharacters\nin the display name must be backed up and restored using a Linux primary server." }, "9773": { "code": 9773, - "desc": "Thestorageserverversionisnotsupported.Minimumsupportedversion está 10.1.", - "first_action": "Select um armazenamento servidor com NetBackup version 10.1 ou", - "full_action": "Select um armazenamento servidor com NetBackup version 10.1 ou\nlater." + "desc": "Thestorageserverversionisnotsupported.Minimumsupportedversion is 10.1.", + "first_action": "Select a storage server with NetBackup version 10.1 or", + "full_action": "Select a storage server with NetBackup version 10.1 or\nlater." }, "9778": { "code": 9778, - "desc": "Não é possível subscribe o PaaS asset to o protection plan que supports differential incremental backup.", - "first_action": "Verifique que o DBPaaS asset supports differential", - "full_action": "Verifique que o DBPaaS asset supports differential\nincremental backup. If o DBPaaS asset does não, you must create um protection\nplan que does não have um differential incremental schedule type. Then subscribe\no asset to o new protection plan." + "desc": "Cannot subscribe the PaaS asset to the protection plan that supports differential incremental backup.", + "first_action": "Verify that the DBPaaS asset supports differential", + "full_action": "Verify that the DBPaaS asset supports differential\nincremental backup. If the DBPaaS asset does not, you must create a protection\nplan that does not have a differential incremental schedule type. Then subscribe\nthe asset to the new protection plan." }, "9781": { "code": 9781, "desc": "InvalidpolicyattributeswereprovidedfortheOpenStackprotectionplan.", - "first_action": "Configure o OpenStack protection plan com valid policy attributes.", - "full_action": "Executar o seguinte como appropriate:\nConfigure o OpenStack protection plan com valid policy attributes." + "first_action": "Configure the OpenStack protection plan with valid policy attributes.", + "full_action": "Perform the following as appropriate:\nConfigure the OpenStack protection plan with valid policy attributes." }, "9783": { "code": 9783, - "desc": "Schedules que have o backup armazenamento units configurado estão não supported para o OpenStack protection plan.", + "desc": "Schedules that have the backup storage units configured are not supported for the OpenStack protection plan.", "first_action": "ConfiguretheOpenStackprotectionplanwiththeschedulesthatdonothavebackup", - "full_action": "Executar o seguinte como appropriate:\nConfiguretheOpenStackprotectionplanwiththeschedulesthatdonothavebackup\narmazenamento units." + "full_action": "Perform the following as appropriate:\nConfiguretheOpenStackprotectionplanwiththeschedulesthatdonothavebackup\nstorage units." }, "9784": { "code": 9784, - "desc": "Schedules que have o armazenamento units configurado must have o staging armazenamento caminho e mount caminho.", + "desc": "Schedules that have the storage units configured must have the staging storage path and mount path.", "first_action": "OpenStackprotectionplanisconfiguredwiththeschedulesthathavestorageunits", - "full_action": "Executar o seguinte como appropriate:\nOpenStackprotectionplanisconfiguredwiththeschedulesthathavestorageunits\nconfigurado but do não have o staging armazenamento caminho ou mount caminho." + "full_action": "Perform the following as appropriate:\nOpenStackprotectionplanisconfiguredwiththeschedulesthathavestorageunits\nconfigured but do not have the staging storage path or mount path." }, "9785": { "code": 9785, - "desc": "OpenStack protection está não supported para universal share com SMB protocol.", - "first_action": "Configure o OpenStack protection plan com o supported universal share apenas.", - "full_action": "Executar o seguinte como appropriate:\nConfigure o OpenStack protection plan com o supported universal share apenas." + "desc": "OpenStack protection is not supported for universal share with SMB protocol.", + "first_action": "Configure the OpenStack protection plan with the supported universal share only.", + "full_action": "Perform the following as appropriate:\nConfigure the OpenStack protection plan with the supported universal share only." }, "9786": { "code": 9786, "desc": "Theprovidedstagingpathisnotmountedontheselectedbackupstorage.", - "first_action": "Garanta que o staging caminho que foi provided to create o OpenStack", - "full_action": "Executar o seguinte como appropriate:\n■ Garanta que o staging caminho que foi provided to create o OpenStack\nprotection plan gets mounted on o selected backup armazenamento.\n■ Garanta que o backup armazenamento está mentioned in o universal share host list.\n■ Garanta que o backup armazenamento has o requerido permissions to access e\nmount o staging caminho on itself." + "first_action": "Ensure that the staging path that was provided to create the OpenStack", + "full_action": "Perform the following as appropriate:\n■ Ensure that the staging path that was provided to create the OpenStack\nprotection plan gets mounted on the selected backup storage.\n■ Ensure that the backup storage is mentioned in the universal share host list.\n■ Ensure that the backup storage has the required permissions to access and\nmount the staging path on itself." }, "9787": { "code": 9787, - "desc": "O provided mount caminho does não match com o staging armazenamento caminho.", - "first_action": "Configure o OpenStack protection plan com o valid mount caminho e staging", - "full_action": "Executar o seguinte como appropriate:\nConfigure o OpenStack protection plan com o valid mount caminho e staging\narmazenamento caminho." + "desc": "The provided mount path does not match with the staging storage path.", + "first_action": "Configure the OpenStack protection plan with the valid mount path and staging", + "full_action": "Perform the following as appropriate:\nConfigure the OpenStack protection plan with the valid mount path and staging\nstorage path." }, "9788": { "code": 9788, - "desc": "Unsupported armazenamento servidor version para OpenStack.", - "first_action": "Garanta que o armazenamento servidor version está 11.1.0.2 ou later.", - "full_action": "Executar o seguinte como appropriate:\nGaranta que o armazenamento servidor version está 11.1.0.2 ou later." + "desc": "Unsupported storage server version for OpenStack.", + "first_action": "Ensure that the storage server version is 11.1.0.2 or later.", + "full_action": "Perform the following as appropriate:\nEnsure that the storage server version is 11.1.0.2 or later." }, "9789": { "code": 9789, - "desc": "Não é possível subscribe o PaaS asset to o protection plan que supports Archive redo logs backup.", - "first_action": "To subscribe o asset to o protection plan, remove o", - "full_action": "To subscribe o asset to o protection plan, remove o\narchive redo logs schedule from o protection plan." + "desc": "Cannot subscribe the PaaS asset to the protection plan that supports Archive redo logs backup.", + "first_action": "To subscribe the asset to the protection plan, remove the", + "full_action": "To subscribe the asset to the protection plan, remove the\narchive redo logs schedule from the protection plan." }, "9794": { "code": 9794, - "desc": "Não é possível subscribe o selected PaaS assets to this protection plan, como o assets estão already subscribed to um protection plan com um incremental backup schedule.", - "first_action": "Remove o asset from previously subscribed protection", - "full_action": "Remove o asset from previously subscribed protection\nplans com incremental backup schedules." + "desc": "Cannot subscribe the selected PaaS assets to this protection plan, as the assets are already subscribed to a protection plan with an incremental backup schedule.", + "first_action": "Remove the asset from previously subscribed protection", + "full_action": "Remove the asset from previously subscribed protection\nplans with incremental backup schedules." }, "9795": { "code": 9795, - "desc": "Não é possível subscribe to this protection plan como this plan não é possível protect archive log backup type com um frequency de less than 24 hours.", - "first_action": "Create um protection plan com o archive log backup type", - "full_action": "Create um protection plan com o archive log backup type\ncom um backup frequency de less than 24 hours." + "desc": "Cannot subscribe to this protection plan as this plan cannot protect archive log backup type with a frequency of less than 24 hours.", + "first_action": "Create a protection plan with the archive log backup type", + "full_action": "Create a protection plan with the archive log backup type\nwith a backup frequency of less than 24 hours." }, "9796": { "code": 9796, - "desc": "Não é possível subscribe o PaaS asset to o protection plan como o plan supports differential incremental e archive redo logs backup.", - "first_action": "Create um protection plan com um cheio backup schedule.", - "full_action": "Create um protection plan com um cheio backup schedule." + "desc": "Cannot subscribe the PaaS asset to the protection plan as the plan supports differential incremental and archive redo logs backup.", + "first_action": "Create a protection plan with a full backup schedule.", + "full_action": "Create a protection plan with a full backup schedule." }, "9800": { "code": 9800, - "desc": "Snapshot Manager está não configurado.", - "first_action": "Configure o Snapshot Manager from o NetBackup", - "full_action": "Configure o Snapshot Manager from o NetBackup\nAdministration Console ou use o tpconfig CLI.\nIf o Snapshot Manager está already configurado, garanta que o registration entry\nestá in o NetBackup banco de dados. Use o NetBackup Administration Console ou\nrun o tpconfig utility." + "desc": "Snapshot Manager is not configured.", + "first_action": "Configure the Snapshot Manager from the NetBackup", + "full_action": "Configure the Snapshot Manager from the NetBackup\nAdministration Console or use the tpconfig CLI.\nIf the Snapshot Manager is already configured, ensure that the registration entry\nis in the NetBackup database. Use the NetBackup Administration Console or\nrun the tpconfig utility." }, "9801": { "code": 9801, - "desc": "Snapshot Manager login falhou.", - "first_action": "Update o credentials e port number in NetBackup.", - "full_action": "Dependingonthecause,performonethefollowingtasks:\n■ Update o credentials e port number in NetBackup.\n■ Garanta que o Snapshot Manager está up e reachable on o rede from\no NetBackup master servidor.\nTo verifique, log on to o Snapshot Manager host from o master servidor browser." + "desc": "Snapshot Manager login failed.", + "first_action": "Update the credentials and port number in NetBackup.", + "full_action": "Dependingonthecause,performonethefollowingtasks:\n■ Update the credentials and port number in NetBackup.\n■ Ensure that the Snapshot Manager is up and reachable on the network from\nthe NetBackup master server.\nTo verify, log on to the Snapshot Manager host from the master server browser." }, "9802": { "code": 9802, - "desc": "Falhou to retrieve o supported plug-in list from o Snapshot Manager.", - "first_action": "Verifique if o conexão com o Snapshot Manager está up.", - "full_action": "Verifique if o conexão com o Snapshot Manager está up." + "desc": "Failed to retrieve the supported plug-in list from the Snapshot Manager.", + "first_action": "Verify if the connection with the Snapshot Manager is up.", + "full_action": "Verify if the connection with the Snapshot Manager is up." }, "9803": { "code": 9803, - "desc": "Falhou to retrieve o NetBackup supported plug-in list.", - "first_action": "Verifique o conexão com o master servidor.", - "full_action": "Verifique o conexão com o master servidor." + "desc": "Failed to retrieve the NetBackup supported plug-in list.", + "first_action": "Verify the connection with the master server.", + "full_action": "Verify the connection with the master server." }, "9804": { "code": 9804, - "desc": "O plug-in está não configurado para o cloud provider.", - "first_action": "Configure o requerido plug-in com NetBackup.", - "full_action": "Configure o requerido plug-in com NetBackup." + "desc": "The plug-in is not configured for the cloud provider.", + "first_action": "Configure the required plug-in with NetBackup.", + "full_action": "Configure the required plug-in with NetBackup." }, "9805": { "code": 9805, - "desc": "O specified configuration instance foi não found.", - "first_action": "Specify o correct instance ID.", - "full_action": "Specify o correct instance ID." + "desc": "The specified configuration instance was not found.", + "first_action": "Specify the correct instance ID.", + "full_action": "Specify the correct instance ID." }, "9806": { "code": 9806, - "desc": "Um configuration instance com o same configuration details already exists.", - "first_action": "Either use o same configuration instance ou create um", - "full_action": "Either use o same configuration instance ou create um\nnew configuration instance com different details." + "desc": "A configuration instance with the same configuration details already exists.", + "first_action": "Either use the same configuration instance or create a", + "full_action": "Either use the same configuration instance or create a\nnew configuration instance with different details." }, "9807": { "code": 9807, - "desc": "Internal servidor erro.", - "first_action": "Verifique Snapshot Manager logs.", - "full_action": "Verifique Snapshot Manager logs." + "desc": "Internal server error.", + "first_action": "Verify Snapshot Manager logs.", + "full_action": "Verify Snapshot Manager logs." }, "9808": { "code": 9808, - "desc": "O plug-in type está não supported.", - "first_action": "Verifique que o plug-in está on o NetBackup supported", - "full_action": "Verifique que o plug-in está on o NetBackup supported\nplug-ins list. You can find more informação about supported plug-ins on Cohesity\nServices e Operations Readiness Tools (SORT) ." + "desc": "The plug-in type is not supported.", + "first_action": "Verify that the plug-in is on the NetBackup supported", + "full_action": "Verify that the plug-in is on the NetBackup supported\nplug-ins list. You can find more information about supported plug-ins on Cohesity\nServices and Operations Readiness Tools (SORT) ." }, "9809": { "code": 9809, "desc": "Plugin instance name already exists.", - "first_action": "Specify um different identifier.", - "full_action": "Specify um different identifier." + "first_action": "Specify a different identifier.", + "full_action": "Specify a different identifier." }, "9810": { "code": 9810, - "desc": "Falhou to configure o plug-in instance in Snapshot Manager.", - "first_action": "Veja o nbemm logs on o NetBackup master servidor.", - "full_action": "Veja o nbemm logs on o NetBackup master servidor." + "desc": "Failed to configure the plug-in instance in Snapshot Manager.", + "first_action": "See the nbemm logs on the NetBackup master server.", + "full_action": "See the nbemm logs on the NetBackup master server." }, "9811": { "code": 9811, - "desc": "Falhou to register o plug-in instance in NetBackup.", - "first_action": "Garanta que o CloudPoint_plugin.conf accessible", - "full_action": "Garanta que o CloudPoint_plugin.conf accessible\ne retry o operation." + "desc": "Failed to register the plug-in instance in NetBackup.", + "first_action": "Ensure that the CloudPoint_plugin.conf accessible", + "full_action": "Ensure that the CloudPoint_plugin.conf accessible\nand retry the operation." }, "9812": { "code": 9812, "desc": "Failedtoretrievetheconfiguredplug-ininstancefromSnapshotManager.", - "first_action": "Update o Snapshot Manager usando o existing", - "full_action": "Update o Snapshot Manager usando o existing\ncredentials." + "first_action": "Update the Snapshot Manager using the existing", + "full_action": "Update the Snapshot Manager using the existing\ncredentials." }, "9813": { "code": 9813, - "desc": "Falhou to retrieve o configurado plug-in instance from NetBackup.", - "first_action": "Retry o operation again.", - "full_action": "Retry o operation again." + "desc": "Failed to retrieve the configured plug-in instance from NetBackup.", + "first_action": "Retry the operation again.", + "full_action": "Retry the operation again." }, "9814": { "code": 9814, - "desc": "O instance type para o specified configurado plug-in does não match com o instance type entry in NetBackup.", + "desc": "The instance type for the specified configured plug-in does not match with the instance type entry in NetBackup.", "first_action": "Verifytheinstancetypeentryandupdatetheplug-inagain.", "full_action": "Verifytheinstancetypeentryandupdatetheplug-inagain." }, "9815": { "code": 9815, - "desc": "Falhou to modify o configurado plug-in instance in Snapshot Manager.", - "first_action": "Verifique o Snapshot Manager logs.", - "full_action": "Verifique o Snapshot Manager logs." + "desc": "Failed to modify the configured plug-in instance in Snapshot Manager.", + "first_action": "Verify the Snapshot Manager logs.", + "full_action": "Verify the Snapshot Manager logs." }, "9816": { "code": 9816, "desc": "Failedtoretrievetheconfiguredplug-ininstancefromSnapshotManager.", - "first_action": "Garanta que o Snapshot Manager está up ou verifique o", - "full_action": "Garanta que o Snapshot Manager está up ou verifique o\nSnapshot Manager logs." + "first_action": "Ensure that the Snapshot Manager is up or verify the", + "full_action": "Ensure that the Snapshot Manager is up or verify the\nSnapshot Manager logs." }, "9818": { "code": 9818, - "desc": "SnapshotManageronwhichthespecifiedplug-ininstancewasconfigured está não disponível.", - "first_action": "Garanta que o Snapshot Manager que hosts o plug-in", - "full_action": "Garanta que o Snapshot Manager que hosts o plug-in\ninstance está registered in NetBackup." + "desc": "SnapshotManageronwhichthespecifiedplug-ininstancewasconfigured is not available.", + "first_action": "Ensure that the Snapshot Manager that hosts the plug-in", + "full_action": "Ensure that the Snapshot Manager that hosts the plug-in\ninstance is registered in NetBackup." }, "9819": { "code": 9819, - "desc": "Um Snapshot Manager on which plug-in instances com specified plug-in type estão configurado está não disponível.", + "desc": "A Snapshot Manager on which plug-in instances with specified plug-in type are configured is not available.", "first_action": "EnsurethatalloftheSnapshotManagersthatcontainthe", - "full_action": "EnsurethatalloftheSnapshotManagersthatcontainthe\nplug-in instances estão registered in NetBackup." + "full_action": "EnsurethatalloftheSnapshotManagersthatcontainthe\nplug-in instances are registered in NetBackup." }, "9820": { "code": 9820, - "desc": "Falhou to disable o plug-in instance.", - "first_action": "Verifique if o CloudPoint_plugin.conf está updated.", - "full_action": "Verifique if o CloudPoint_plugin.conf está updated." + "desc": "Failed to disable the plug-in instance.", + "first_action": "Verify if the CloudPoint_plugin.conf is updated.", + "full_action": "Verify if the CloudPoint_plugin.conf is updated." }, "9821": { "code": 9821, - "desc": "Specified plug-in instance does não exist on o Snapshot Manager.", - "first_action": "Retry o operation e save todos de o erro informação.", - "full_action": "Retry o operation e save todos de o erro informação.\nIf o issue persists, visit support.veritas.com. O Cohesity Technical Support\nwebsite site offers additional informação to help you troubleshoot this issue." + "desc": "Specified plug-in instance does not exist on the Snapshot Manager.", + "first_action": "Retry the operation and save all of the error information.", + "full_action": "Retry the operation and save all of the error information.\nIf the issue persists, visit support.veritas.com. The Cohesity Technical Support\nwebsite site offers additional information to help you troubleshoot this issue." }, "9822": { "code": 9822, - "desc": "Plug-in instance already exists in o Snapshot Manager. NetBackup status codes 1169 NetBackup status codes", - "first_action": "Change o configuration attributes. Para example, if it está", - "full_action": "Change o configuration attributes. Para example, if it está\num Amazon AWS plug-in configuration, garanta que o specified region está não\nincluded in qualquer de o existing AWS plug-in configurations que have o same\naccess key. If um region está already specified in um plug-in, its assets estão already\nprotected." + "desc": "Plug-in instance already exists in the Snapshot Manager. NetBackup status codes 1169 NetBackup status codes", + "first_action": "Change the configuration attributes. For example, if it is", + "full_action": "Change the configuration attributes. For example, if it is\nan Amazon AWS plug-in configuration, ensure that the specified region is not\nincluded in any of the existing AWS plug-in configurations that have the same\naccess key. If a region is already specified in a plug-in, its assets are already\nprotected." }, "9823": { "code": 9823, - "desc": "Plug-in authentication falhou. Credentials estão inválido.", - "first_action": "Verifique que o credentials estão correct e executar o", - "full_action": "Verifique que o credentials estão correct e executar o\noperation again.\nGaranta que you enable o preferred regions para o account que está linked to o\nSnapshot Manager instance que está deployed on AWS." + "desc": "Plug-in authentication failed. Credentials are invalid.", + "first_action": "Verify that the credentials are correct and perform the", + "full_action": "Verify that the credentials are correct and perform the\noperation again.\nEnsure that you enable the preferred regions for the account that is linked to the\nSnapshot Manager instance that is deployed on AWS." }, "9830": { "code": 9830, - "desc": "Operation não supported. O associated Snapshot Manager está on um older version.", - "first_action": "Upgrade o Snapshot Manager servidor to um supported", - "full_action": "Upgrade o Snapshot Manager servidor to um supported\nversion equal to o NetBackup primary servidor version." + "desc": "Operation not supported. The associated Snapshot Manager is on an older version.", + "first_action": "Upgrade the Snapshot Manager server to a supported", + "full_action": "Upgrade the Snapshot Manager server to a supported\nversion equal to the NetBackup primary server version." }, "9833": { "code": 9833, - "desc": "NetBackup não é possível conectar to o virtual machine.", + "desc": "NetBackup cannot connect to the virtual machine.", "first_action": "ReviewtheNetBackupnbwebserviceandthenbemmlogs.", "full_action": "ReviewtheNetBackupnbwebserviceandthenbemmlogs." }, "9834": { "code": 9834, - "desc": "O specified asset está não found in o Snapshot Manager banco de dados.", - "first_action": "To verifique o deleted assets, refer to o last discovered", - "full_action": "To verifique o deleted assets, refer to o last discovered\ntime." + "desc": "The specified asset is not found in the Snapshot Manager database.", + "first_action": "To verify the deleted assets, refer to the last discovered", + "full_action": "To verify the deleted assets, refer to the last discovered\ntime." }, "9835": { "code": 9835, - "desc": "Application configuration operation falhou.", - "first_action": "Review o NetBackup nbwebservice e nbemm logs.", - "full_action": "Review o NetBackup nbwebservice e nbemm logs." + "desc": "Application configuration operation failed.", + "first_action": "Review the NetBackup nbwebservice and nbemm logs.", + "full_action": "Review the NetBackup nbwebservice and nbemm logs." }, "9836": { "code": 9836, - "desc": "Application already configurado on o Snapshot Manager.", - "first_action": "Skip o operation.", - "full_action": "Skip o operation." + "desc": "Application already configured on the Snapshot Manager.", + "first_action": "Skip the operation.", + "full_action": "Skip the operation." }, "9837": { "code": 9837, - "desc": "Configure application operation has falhou from NetBackup.", - "first_action": "Review o NetBackup nbwebservice e nbemm logs.", - "full_action": "Review o NetBackup nbwebservice e nbemm logs." + "desc": "Configure application operation has failed from NetBackup.", + "first_action": "Review the NetBackup nbwebservice and nbemm logs.", + "full_action": "Review the NetBackup nbwebservice and nbemm logs." }, "9838": { "code": 9838, - "desc": "O specified operation está não supported com o current Snapshot Manager license in use.", - "first_action": "Apply um license com o appropriate privileges.", - "full_action": "Apply um license com o appropriate privileges." + "desc": "The specified operation is not supported with the current Snapshot Manager license in use.", + "first_action": "Apply a license with the appropriate privileges.", + "full_action": "Apply a license with the appropriate privileges." }, "9839": { "code": 9839, - "desc": "O origiasset está deleted. Apenas snapshot de o asset está disponível.", - "first_action": "Recover o asset from o snapshot.", - "full_action": "Recover o asset from o snapshot." + "desc": "The origiasset is deleted. Only snapshot of the asset is available.", + "first_action": "Recover the asset from the snapshot.", + "full_action": "Recover the asset from the snapshot." }, "9841": { "code": 9841, - "desc": "O Snapshot Manager host name does não match com o associated Snapshot Manager.", - "first_action": "Verifique if o Snapshot Manager host name está configurado", - "full_action": "Verifique if o Snapshot Manager host name está configurado\ncorrectly." + "desc": "The Snapshot Manager host name does not match with the associated Snapshot Manager.", + "first_action": "Verify if the Snapshot Manager host name is configured", + "full_action": "Verify if the Snapshot Manager host name is configured\ncorrectly." }, "9842": { "code": 9842, - "desc": "O virtual machine está already connected.", + "desc": "The virtual machine is already connected.", "first_action": "Thevirtualmachineisalreadyconnected,youcanproceed", - "full_action": "Thevirtualmachineisalreadyconnected,youcanproceed\ncom application configuration." + "full_action": "Thevirtualmachineisalreadyconnected,youcanproceed\nwith application configuration." }, "9843": { "code": 9843, - "desc": "Não foi possível to retrieve virtual machine details.", - "first_action": "Refer to o Snapshot Manager logs.", - "full_action": "Refer to o Snapshot Manager logs." + "desc": "Unable to retrieve virtual machine details.", + "first_action": "Refer to the Snapshot Manager logs.", + "full_action": "Refer to the Snapshot Manager logs." }, "9844": { "code": 9844, - "desc": "Não foi possível to retrieve o application details.", - "first_action": "Refer to o Snapshot Manager logs.", - "full_action": "Refer to o Snapshot Manager logs." + "desc": "Unable to retrieve the application details.", + "first_action": "Refer to the Snapshot Manager logs.", + "full_action": "Refer to the Snapshot Manager logs." }, "9845": { "code": 9845, - "desc": "Falhou to deploy o snapshot agent on o Windows host.", + "desc": "Failed to deploy the snapshot agent on the Windows host.", "first_action": "DeploytheWindowshostmanually.RefertotheSnapshot", - "full_action": "DeploytheWindowshostmanually.RefertotheSnapshot\nManager documentation in o NetBackup Snapshot Cliente Administrator’s Guide." + "full_action": "DeploytheWindowshostmanually.RefertotheSnapshot\nManager documentation in the NetBackup Snapshot Client Administrator’s Guide." }, "9846": { "code": 9846, - "desc": "Falhou to update o asset informação in o banco de dados.", - "first_action": "Restart o nbwebservice e retry o operation.", - "full_action": "Restart o nbwebservice e retry o operation." + "desc": "Failed to update the asset information in the database.", + "first_action": "Restart the nbwebservice and retry the operation.", + "full_action": "Restart the nbwebservice and retry the operation." }, "9847": { "code": 9847, - "desc": "Falhou to retrieve cloud asset type. NetBackup status codes 1173 NetBackup status codes", - "first_action": "Retry o operation.", - "full_action": "Retry o operation." + "desc": "Failed to retrieve cloud asset type. NetBackup status codes 1173 NetBackup status codes", + "first_action": "Retry the operation.", + "full_action": "Retry the operation." }, "9848": { "code": 9848, - "desc": "Inválido Cloud asset type.", - "first_action": "Verifique o ncfnbcs logs.", - "full_action": "Verifique o ncfnbcs logs." + "desc": "Invalid Cloud asset type.", + "first_action": "Verify the ncfnbcs logs.", + "full_action": "Verify the ncfnbcs logs." }, "9849": { "code": 9849, - "desc": "Inválido virtual machine credentials.", - "first_action": "Verifique o virtual machine credentials e provide correct", - "full_action": "Verifique o virtual machine credentials e provide correct\ncredentials." + "desc": "Invalid virtual machine credentials.", + "first_action": "Verify the virtual machine credentials and provide correct", + "full_action": "Verify the virtual machine credentials and provide correct\ncredentials." }, "9850": { "code": 9850, - "desc": "O specified application está não supported com o host’s operating system.", - "first_action": "Review o Snapshot Manager host’s operating system", - "full_action": "Review o Snapshot Manager host’s operating system\ne compare it to o NetBackup Compatibility List." + "desc": "The specified application is not supported with the host’s operating system.", + "first_action": "Review the Snapshot Manager host’s operating system", + "full_action": "Review the Snapshot Manager host’s operating system\nand compare it to the NetBackup Compatibility List." }, "9851": { "code": 9851, - "desc": "Para plug-ins configurado directly com NetBackup, o original instance name e specified plug-in ID must be same.", + "desc": "For plug-ins configured directly with NetBackup, the original instance name and specified plug-in ID must be same.", "first_action": "IftheIDisdifferent,youcanupdatealltheotherparameters", - "full_action": "IftheIDisdifferent,youcanupdatealltheotherparameters\napart from o ID. NetBackup does não support updates to o ID." + "full_action": "IftheIDisdifferent,youcanupdatealltheotherparameters\napart from the ID. NetBackup does not support updates to the ID." }, "9853": { "code": 9853, - "desc": "Inválido copy type.", + "desc": "Invalid copy type.", "first_action": "Iftheproblempersists,contactCohesityTechnicalSupport.", "full_action": "Iftheproblempersists,contactCohesityTechnicalSupport." }, "9854": { "code": 9854, - "desc": "Cloud snapshot replication falhou.", - "first_action": "If you try to replicate um copy de um EC2 instance, create um new key-pair in o", - "full_action": "Executar o seguinte como appropriate:\n■ If you try to replicate um copy de um EC2 instance, create um new key-pair in o\ndestination region. O new key-pair must be consistent com o key-pair in o\nsource region.\n■ Refer to o ncfnbcs logs on o mídia servidor para more informação." + "desc": "Cloud snapshot replication failed.", + "first_action": "If you try to replicate a copy of an EC2 instance, create a new key-pair in the", + "full_action": "Perform the following as appropriate:\n■ If you try to replicate a copy of an EC2 instance, create a new key-pair in the\ndestination region. The new key-pair must be consistent with the key-pair in the\nsource region.\n■ Refer to the ncfnbcs logs on the media server for more information." }, "9855": { "code": 9855, - "desc": "Snapshot export falhou.", + "desc": "Snapshot export failed.", "first_action": "Refertothebpfis logson theclientor thealternateclient", - "full_action": "Refertothebpfis logson theclientor thealternateclient\npara more informação.\nPara cloud backups, review o NCFNBCS logs on o mídia servidor para relevant\ninformação." + "full_action": "Refertothebpfis logson theclientor thealternateclient\nfor more information.\nFor cloud backups, review the NCFNBCS logs on the media server for relevant\ninformation." }, "9856": { "code": 9856, - "desc": "Falhou to parse JSON response from Snapshot Manager.", - "first_action": "Manually clean up o operation-specific copy from o", - "full_action": "Manually clean up o operation-specific copy from o\ncloud." + "desc": "Failed to parse JSON response from Snapshot Manager.", + "first_action": "Manually clean up the operation-specific copy from the", + "full_action": "Manually clean up the operation-specific copy from the\ncloud." }, "9857": { "code": 9857, - "desc": "Falhou to start indexing de snapshot.", - "first_action": "Refer to o ncfnbcs logs on o mídia servidor e o", - "full_action": "Refer to o ncfnbcs logs on o mídia servidor e o\nSnapshot Manager logs." + "desc": "Failed to start indexing of snapshot.", + "first_action": "Refer to the ncfnbcs logs on the media server and the", + "full_action": "Refer to the ncfnbcs logs on the media server and the\nSnapshot Manager logs." }, "9858": { "code": 9858, - "desc": "Falhou to add NetBackup Snapshot Manager.", - "first_action": "Review seu rede connectivity com Snapshot Manager.", - "full_action": "Try one de o seguinte como appropriate:\n■ Review seu rede connectivity com Snapshot Manager.\n■ Resolve qualquer rede issues com netstat ou similar rede diagnosis tool." + "desc": "Failed to add NetBackup Snapshot Manager.", + "first_action": "Review your network connectivity with Snapshot Manager.", + "full_action": "Try one of the following as appropriate:\n■ Review your network connectivity with Snapshot Manager.\n■ Resolve any network issues with netstat or similar network diagnosis tool." }, "9859": { "code": 9859, - "desc": "Falhou to retrieve o Mount Caminho.", - "first_action": "Retry o snapshot operation again. If it still fails, refer to", - "full_action": "Retry o snapshot operation again. If it still fails, refer to\no Snapshot Manager logs." + "desc": "Failed to retrieve the Mount Path.", + "first_action": "Retry the snapshot operation again. If it still fails, refer to", + "full_action": "Retry the snapshot operation again. If it still fails, refer to\nthe Snapshot Manager logs." }, "9860": { "code": 9860, - "desc": "Inválido Cloud FS Mount Caminho.", - "first_action": "Review o mounted arquivo system caminho on o target host", - "full_action": "Review o mounted arquivo system caminho on o target host\ne try to launch o snapshot operation again. If it still fails, refer to o Snapshot\nManager logs." + "desc": "Invalid Cloud FS Mount Path.", + "first_action": "Review the mounted file system path on the target host", + "full_action": "Review the mounted file system path on the target host\nand try to launch the snapshot operation again. If it still fails, refer to the Snapshot\nManager logs." }, "9861": { "code": 9861, - "desc": "Snapshot Manager está already added to um NetBackup master servidor.", - "first_action": "Deploy e add um new Snapshot Manager.", - "full_action": "Deploy e add um new Snapshot Manager." + "desc": "Snapshot Manager is already added to a NetBackup master server.", + "first_action": "Deploy and add a new Snapshot Manager.", + "full_action": "Deploy and add a new Snapshot Manager." }, "9862": { "code": 9862, - "desc": "Falhou to get CA certificate para Snapshot Manager.", - "first_action": "Verifique seu rede connectivity com o Snapshot Manager.", - "full_action": "Try one de o seguinte como appropriate:\n■ Verifique seu rede connectivity com o Snapshot Manager.\n■ Resolve qualquer rede issues com netstat ou similar rede diagnosis tool." + "desc": "Failed to get CA certificate for Snapshot Manager.", + "first_action": "Check your network connectivity with the Snapshot Manager.", + "full_action": "Try one of the following as appropriate:\n■ Check your network connectivity with the Snapshot Manager.\n■ Resolve any network issues with netstat or similar network diagnosis tool." }, "9863": { "code": 9863, - "desc": "Falhou to save CA certificate para Snapshot Manager.", - "first_action": "Confirm o correct permissions para o NetBackup certificate store", - "full_action": "Try one de o seguinte como appropriate:\n■ Confirm o correct permissions para o NetBackup certificate store\n(/usr/openv/var/global/cloudpoint).\n■ Verifique o format de Snapshot Manager certificate usando o\n/config/snapshot-mgmt-servers-cacerts/{snapshotMgmtServer}/ports/{port}\nAPI.\n■ Apenas pem format está supported.\n■ Add ou modify o Snapshot Manager configuration usando o tpconfig\ncomando. Run o tpconfig comando como um raiz usuário. This ação re-assigns\no ownership de o raiz certificate caminho ou o certificate arquivo to o NetBackup\nservice usuário." + "desc": "Failed to save CA certificate for Snapshot Manager.", + "first_action": "Confirm the correct permissions for the NetBackup certificate store", + "full_action": "Try one of the following as appropriate:\n■ Confirm the correct permissions for the NetBackup certificate store\n(/usr/openv/var/global/cloudpoint).\n■ Check the format of Snapshot Manager certificate using the\n/config/snapshot-mgmt-servers-cacerts/{snapshotMgmtServer}/ports/{port}\nAPI.\n■ Only pem format is supported.\n■ Add or modify the Snapshot Manager configuration using the tpconfig\ncommand. Run the tpconfig command as a root user. This action re-assigns\nthe ownership of the root certificate path or the certificate file to the NetBackup\nservice user." }, "9865": { "code": 9865, - "desc": "NetBackup mídia servidor platform should be either Red Hat Enterprise Linux, SUSE Linux Enterprise Servidor, ou Microsoft Windows to be associated com um Snapshot Manager.", - "first_action": "Use SUSE Linux Enterprise Servidor, Microsoft Windows,", - "full_action": "Use SUSE Linux Enterprise Servidor, Microsoft Windows,\nandRHELplatformonly,toassociatethemediaserverwiththeSnapshotManager." + "desc": "NetBackup media server platform should be either Red Hat Enterprise Linux, SUSE Linux Enterprise Server, or Microsoft Windows to be associated with a Snapshot Manager.", + "first_action": "Use SUSE Linux Enterprise Server, Microsoft Windows,", + "full_action": "Use SUSE Linux Enterprise Server, Microsoft Windows,\nandRHELplatformonly,toassociatethemediaserverwiththeSnapshotManager." }, "9866": { "code": 9866, - "desc": "O NetBackup host certificate que está provided to Snapshot Manager está não valid ou does não exist.", - "first_action": "Review o nbcs/bpfis/bppfi level erro messages que estão displayed in Job", - "full_action": "Try one de o seguinte como appropriate:\n■ Review o nbcs/bpfis/bppfi level erro messages que estão displayed in Job\ndetails on o Activity monitor. Para more details, review o component logs.\n■ Reviewthenbwebservice/nbemmlevelerrormessagefortheSnapshotManager\ne plug-in configuration. Para more details, review o component logs.\n■ Review o NetBackup erro codes ou messages appearing in o previously\nspecified logs. These logs can provide additional insight into o actual SSL\ncertificate issue ou connectivity issues between primary servidor e Snapshot\nManager." + "desc": "The NetBackup host certificate that is provided to Snapshot Manager is not valid or does not exist.", + "first_action": "Review the nbcs/bpfis/bppfi level error messages that are displayed in Job", + "full_action": "Try one of the following as appropriate:\n■ Review the nbcs/bpfis/bppfi level error messages that are displayed in Job\ndetails on the Activity monitor. For more details, review the component logs.\n■ Reviewthenbwebservice/nbemmlevelerrormessagefortheSnapshotManager\nand plug-in configuration. For more details, review the component logs.\n■ Review the NetBackup error codes or messages appearing in the previously\nspecified logs. These logs can provide additional insight into the actual SSL\ncertificate issue or connectivity issues between primary server and Snapshot\nManager." }, "9867": { "code": 9867, - "desc": "O ECA_TRUST_STORE_PATH option está não configurado, ou o certificate caminho está não accessible ou doesn’t exist. NetBackup status codes 1179 NetBackup status codes", - "first_action": "Verifique if o ECA_TRUST_STORE_PATH está configurado correctly.", - "full_action": "Try one de o seguinte como appropriate:\n■ Verifique if o ECA_TRUST_STORE_PATH está configurado correctly.\n■ Review todos access rights de certificate caminho estão correct." + "desc": "The ECA_TRUST_STORE_PATH option is not configured, or the certificate path is not accessible or doesn’t exist. NetBackup status codes 1179 NetBackup status codes", + "first_action": "Check if the ECA_TRUST_STORE_PATH is configured correctly.", + "full_action": "Try one of the following as appropriate:\n■ Check if the ECA_TRUST_STORE_PATH is configured correctly.\n■ Review all access rights of certificate path are correct." }, "9868": { "code": 9868, - "desc": "Falhou to get API version para Snapshot Manager.", - "first_action": "Verifique seu rede connectivity com o Snapshot Manager e review o", - "full_action": "Try one de o seguinte como appropriate:\n■ Verifique seu rede connectivity com o Snapshot Manager e review o\nSnapshot Manager credentials you used to conectar.\n■ Resolve qualquer rede issues com netstat ou similar rede diagnosis tool.\n■ Update o Snapshot Manager credentials usando o Edit Servidor option." + "desc": "Failed to get API version for Snapshot Manager.", + "first_action": "Check your network connectivity with the Snapshot Manager and review the", + "full_action": "Try one of the following as appropriate:\n■ Check your network connectivity with the Snapshot Manager and review the\nSnapshot Manager credentials you used to connect.\n■ Resolve any network issues with netstat or similar network diagnosis tool.\n■ Update the Snapshot Manager credentials using the Edit Server option." }, "9869": { "code": 9869, - "desc": "Falhou to get Deployment Summary para Snapshot Manager.", - "first_action": "Verifique seu rede connectivity com o Snapshot Manager, NetBackup, e", - "full_action": "Try one de o seguinte como appropriate:\n■ Verifique seu rede connectivity com o Snapshot Manager, NetBackup, e\ncloud provider.\n■ Resolve qualquer rede issues com netstat ou similar rede diagnosis tool.\n■ ReviewandupdatetheSnapshotManagercredentialsusingEditServeroption.\n■ Review e update o cloud provider credentials ou secret key." + "desc": "Failed to get Deployment Summary for Snapshot Manager.", + "first_action": "Check your network connectivity with the Snapshot Manager, NetBackup, and", + "full_action": "Try one of the following as appropriate:\n■ Check your network connectivity with the Snapshot Manager, NetBackup, and\ncloud provider.\n■ Resolve any network issues with netstat or similar network diagnosis tool.\n■ ReviewandupdatetheSnapshotManagercredentialsusingEditServeroption.\n■ Review and update the cloud provider credentials or secret key." }, "9870": { "code": 9870, - "desc": "Falhou to get version para Snapshot Manager.", - "first_action": "Verifique seu rede connectivity com Snapshot Manager e NetBackup.", - "full_action": "Try one de o seguinte como appropriate:\n■ Verifique seu rede connectivity com Snapshot Manager e NetBackup.\n■ Resolve qualquer rede issues com netstat ou similar rede diagnosis tool.\n■ ReviewandupdateSnapshotManagercredentialsusingtheEditServeroption." + "desc": "Failed to get version for Snapshot Manager.", + "first_action": "Check your network connectivity with Snapshot Manager and NetBackup.", + "full_action": "Try one of the following as appropriate:\n■ Check your network connectivity with Snapshot Manager and NetBackup.\n■ Resolve any network issues with netstat or similar network diagnosis tool.\n■ ReviewandupdateSnapshotManagercredentialsusingtheEditServeroption." }, "9871": { "code": 9871, - "desc": "Operationnotsupported.ThespecifiedmediaservermustbeNetBackup version 8.3 ou later.", - "first_action": "Select um mídia servidor de NetBackup version 8.3 ou later", - "full_action": "Select um mídia servidor de NetBackup version 8.3 ou later\nto associate com Snapshot Manager." + "desc": "Operationnotsupported.ThespecifiedmediaservermustbeNetBackup version 8.3 or later.", + "first_action": "Select a media server of NetBackup version 8.3 or later", + "full_action": "Select a media server of NetBackup version 8.3 or later\nto associate with Snapshot Manager." }, "9872": { "code": 9872, - "desc": "Não foi possível to retrieve o Snapshot Manager on-host agent token details.", - "first_action": "Refer to o nbwebservice e Snapshot Manager log", - "full_action": "Refer to o nbwebservice e Snapshot Manager log\ne garanta que todos Snapshot Manager services estão executando." + "desc": "Unable to retrieve the Snapshot Manager on-host agent token details.", + "first_action": "Refer to the nbwebservice and Snapshot Manager log", + "full_action": "Refer to the nbwebservice and Snapshot Manager log\nand ensure that all Snapshot Manager services are running." }, "9873": { "code": 9873, - "desc": "O Snapshot Manager está disabled.", - "first_action": "Verifique para qualquer underlying maintenance issues que estão", - "full_action": "Verifique para qualquer underlying maintenance issues que estão\nrelated to o disabled Snapshot Manager. If there estão qualquer maintenance issues,\nyou must resolve these issues.\nIf there estão não maintenance issues, executar o seguinte:\n1 Log on to NetBackup web UI.\n2 On o left, click Cloud e then select o Snapshot Manager tab.\n3 Select o appropriate Snapshot Manager.\n4 In o Actions menu on o right, click o Enable option.\n5 Verifythatthediscoveryprocessistriggeredandthatitcompletessuccessfully.\n6 After o Snapshot Manager está enabled, run o operation again." + "desc": "The Snapshot Manager is disabled.", + "first_action": "Check for any underlying maintenance issues that are", + "full_action": "Check for any underlying maintenance issues that are\nrelated to the disabled Snapshot Manager. If there are any maintenance issues,\nyou must resolve these issues.\nIf there are no maintenance issues, perform the following:\n1 Log on to NetBackup web UI.\n2 On the left, click Cloud and then select the Snapshot Manager tab.\n3 Select the appropriate Snapshot Manager.\n4 In the Actions menu on the right, click the Enable option.\n5 Verifythatthediscoveryprocessistriggeredandthatitcompletessuccessfully.\n6 After the Snapshot Manager is enabled, run the operation again." }, "9874": { "code": 9874, - "desc": "Thissnapshotisnotindexed.GRToperationsonnon-indexedsnapshots estão não supported.", - "first_action": "Select um recovery point que está indexed e retry o", - "full_action": "Select um recovery point que está indexed e retry o\noperation." + "desc": "Thissnapshotisnotindexed.GRToperationsonnon-indexedsnapshots are not supported.", + "first_action": "Select a recovery point that is indexed and retry the", + "full_action": "Select a recovery point that is indexed and retry the\noperation." }, "9876": { "code": 9876, - "desc": "Falhou to disconnect VM from Snapshot Manager.", - "first_action": "Refer to o nbwebservice e Snapshot Manager logs.", - "full_action": "Refer to o nbwebservice e Snapshot Manager logs.\nGaranta que todos o Snapshot Manager services estão executando." + "desc": "Failed to disconnect VM from Snapshot Manager.", + "first_action": "Refer to the nbwebservice and Snapshot Manager logs.", + "full_action": "Refer to the nbwebservice and Snapshot Manager logs.\nEnsure that all the Snapshot Manager services are running." }, "9877": { "code": 9877, - "desc": "Falhou to remove application from o Snapshot Manager.", - "first_action": "Refer to o nbwebservice e Snapshot Manager logs.", - "full_action": "Refer to o nbwebservice e Snapshot Manager logs.\nGaranta que todos o Snapshot Manager services estão executando." + "desc": "Failed to remove application from the Snapshot Manager.", + "first_action": "Refer to the nbwebservice and Snapshot Manager logs.", + "full_action": "Refer to the nbwebservice and Snapshot Manager logs.\nEnsure that all the Snapshot Manager services are running." }, "9878": { "code": 9878, - "desc": "O Unconfigure application API falhou due to um discovery foi não performed after o application API foi configurado.", - "first_action": "Manually start o discovery on o Snapshot Manager", - "full_action": "Manually start o discovery on o Snapshot Manager\nou wait para o scheduled discovery operation to complete." + "desc": "The Unconfigure application API failed due to a discovery was not performed after the application API was configured.", + "first_action": "Manually start the discovery on the Snapshot Manager", + "full_action": "Manually start the discovery on the Snapshot Manager\nor wait for the scheduled discovery operation to complete." }, "9879": { "code": 9879, - "desc": "Falhou to unconfigure o application como it has active snapshots.", - "first_action": "Refer to o nbwebservice e Snapshot Manager log", - "full_action": "Refer to o nbwebservice e Snapshot Manager log\ne garanta que todos Snapshot Manager services estão executando." + "desc": "Failed to unconfigure the application as it has active snapshots.", + "first_action": "Refer to the nbwebservice and Snapshot Manager log", + "full_action": "Refer to the nbwebservice and Snapshot Manager log\nand ensure that all Snapshot Manager services are running." }, "9882": { "code": 9882, - "desc": "Falhou to create disks selection arquivo during volume restauração operation.", - "first_action": "Garanta que todos NetBackup services estão executando e try", - "full_action": "Garanta que todos NetBackup services estão executando e try\no operation again." + "desc": "Failed to create disks selection file during volume restore operation.", + "first_action": "Ensure that all NetBackup services are running and try", + "full_action": "Ensure that all NetBackup services are running and try\nthe operation again." }, "9883": { "code": 9883, - "desc": "Falhou to retrieve disks selection informação during volume restauração operation.", - "first_action": "Garanta que todos NetBackup services estão executando e try", - "full_action": "Garanta que todos NetBackup services estão executando e try\no operation again." + "desc": "Failed to retrieve disks selection information during volume restore operation.", + "first_action": "Ensure that all NetBackup services are running and try", + "full_action": "Ensure that all NetBackup services are running and try\nthe operation again." }, "9884": { "code": 9884, - "desc": "Snapshot Manager servidor fails to retrieve o specified cloud domains, against o specified plug-in instance.", + "desc": "Snapshot Manager server fails to retrieve the specified cloud domains, against the specified plug-in instance.", "first_action": "EnsurethattheNetBackupservicesandSnapshotManager", - "full_action": "EnsurethattheNetBackupservicesandSnapshotManager\nservidor containers estão executando. Verifique connectivity between o NetBackup primary\nservidor, o Snapshot Manager servidor, e o cloud service provider. Retry o\noperation again." + "full_action": "EnsurethattheNetBackupservicesandSnapshotManager\nserver containers are running. Check connectivity between the NetBackup primary\nserver, the Snapshot Manager server, and the cloud service provider. Retry the\noperation again." }, "9886": { "code": 9886, - "desc": "Snapshot Manager servidor fails to retrieve o specified cloud domain attributes, against o specified plug-in instance.", + "desc": "Snapshot Manager server fails to retrieve the specified cloud domain attributes, against the specified plug-in instance.", "first_action": "EnsurethattheNetBackupservicesandSnapshotManager", - "full_action": "EnsurethattheNetBackupservicesandSnapshotManager\ncontainers estão executando. Confirm o connectivity between o NetBackup primary\nservidor, o Snapshot Manager servidor, e o cloud service provider. Retry o\noperation." + "full_action": "EnsurethattheNetBackupservicesandSnapshotManager\ncontainers are running. Confirm the connectivity between the NetBackup primary\nserver, the Snapshot Manager server, and the cloud service provider. Retry the\noperation." }, "9888": { "code": 9888, - "desc": "Não é possível access Snapshot Manager extensions from o Snapshot Manager.", - "first_action": "Garanta que o NetBackup services e o Snapshot", - "full_action": "Garanta que o NetBackup services e o Snapshot\nManager containers estão executando. Verifique o connectivity between o NetBackup\nmaster servidor, o Snapshot Manager, e o cloud service provider. Retry o\noperation again." + "desc": "Cannot access Snapshot Manager extensions from the Snapshot Manager.", + "first_action": "Ensure that the NetBackup services and the Snapshot", + "full_action": "Ensure that the NetBackup services and the Snapshot\nManager containers are running. Check the connectivity between the NetBackup\nmaster server, the Snapshot Manager, and the cloud service provider. Retry the\noperation again." }, "9890": { "code": 9890, - "desc": "Falhou to update capability de Snapshot Manager in NetBackup servidor.", + "desc": "Failed to update capability of Snapshot Manager in NetBackup server.", "first_action": "EnsurethattheNetBackupservicesandSnapshotManager", - "full_action": "EnsurethattheNetBackupservicesandSnapshotManager\nestão executando. Verifique o connectivity between o NetBackup master servidor, o\nSnapshot Manager, e o cloud service provider. Retry o operation again." + "full_action": "EnsurethattheNetBackupservicesandSnapshotManager\nare running. Check the connectivity between the NetBackup master server, the\nSnapshot Manager, and the cloud service provider. Retry the operation again." }, "9891": { "code": 9891, "desc": "FailedtoupdateSnapshotManagerextensionsfromSnapshotManager.", - "first_action": "Garanta que o NetBackup services e o Snapshot", - "full_action": "Garanta que o NetBackup services e o Snapshot\nManagercontainersarerunning.CheckconnectivitybetweentheNetBackupmaster\nservidor, o Snapshot Manager, e o cloud service provider. Retry o operation\nagain." + "first_action": "Ensure that the NetBackup services and the Snapshot", + "full_action": "Ensure that the NetBackup services and the Snapshot\nManagercontainersarerunning.CheckconnectivitybetweentheNetBackupmaster\nserver, the Snapshot Manager, and the cloud service provider. Retry the operation\nagain." }, "9894": { "code": 9894, - "desc": "Não é possível retrieve plug-in details para o agent.", - "first_action": "Retry o operation e if o issue persists, visit", - "full_action": "Retry o operation e if o issue persists, visit\nsupport.veritas.com.TheCohesitySupportsiteoffersadditionalinformationtohelp\nyou troubleshoot this issue." + "desc": "Cannot retrieve plug-in details for the agent.", + "first_action": "Retry the operation and if the issue persists, visit", + "full_action": "Retry the operation and if the issue persists, visit\nsupport.veritas.com.TheCohesitySupportsiteoffersadditionalinformationtohelp\nyou troubleshoot this issue." }, "9895": { "code": 9895, - "desc": "Não é possível retrieve configuration details de o plug-in.", - "first_action": "Retry o operation e if o issue persists, visit", - "full_action": "Retry o operation e if o issue persists, visit\nsupport.veritas.com.TheCohesitySupportsiteoffersadditionalinformationtohelp\nyou troubleshoot this issue." + "desc": "Cannot retrieve configuration details of the plug-in.", + "first_action": "Retry the operation and if the issue persists, visit", + "full_action": "Retry the operation and if the issue persists, visit\nsupport.veritas.com.TheCohesitySupportsiteoffersadditionalinformationtohelp\nyou troubleshoot this issue." }, "9896": { "code": 9896, - "desc": "FailedtoaddNetBackupSnapshotManagerduetocertificategeneration falha.", - "first_action": "Review o NetBackup nbemm logs to identify o exact erro.", - "full_action": "Executar one ou more de o seguinte actions, depending\nupon o erro you veja:\n■ Review o NetBackup nbemm logs to identify o exact erro.\n■ Review seu rede connectivity com Snapshot Manager\n■ Resolve rede issues if qualquer, usando netstat ou um similar rede diagnosis\ntool.\n■ Determinar if nbcertcmdtool está able to conectar to o web service executando on\no NetBackup primary servidor to generate o NetBackup certificates.\n■ UsethentpdatecommandtosynchronizeclocktimesfortheNetBackupprimary\nservidor e o Snapshot Manager.\n■ UpdatetheDNSentrieswithDockerandhostentriesfortheSnapshotManager.\nUpdate o /cloudpoint/openv/etc/hosts arquivo com o DNS entradas. Use\ndifferent rede cards, IP addresses, ou host names para registering o\nco-located mídia servidor e o Snapshot Manager. Also, if o mídia servidor\nandtheSnapshotManagerareco-located,andthemediaserverusesport443,\nthen o Snapshot Manager must use um custom SSL port." + "desc": "FailedtoaddNetBackupSnapshotManagerduetocertificategeneration failure.", + "first_action": "Review the NetBackup nbemm logs to identify the exact error.", + "full_action": "Perform one or more of the following actions, depending\nupon the error you see:\n■ Review the NetBackup nbemm logs to identify the exact error.\n■ Review your network connectivity with Snapshot Manager\n■ Resolve network issues if any, using netstat or a similar network diagnosis\ntool.\n■ Determine if nbcertcmdtool is able to connect to the web service running on\nthe NetBackup primary server to generate the NetBackup certificates.\n■ UsethentpdatecommandtosynchronizeclocktimesfortheNetBackupprimary\nserver and the Snapshot Manager.\n■ UpdatetheDNSentrieswithDockerandhostentriesfortheSnapshotManager.\nUpdate the /cloudpoint/openv/etc/hosts file with the DNS entries. Use\ndifferent network cards, IP addresses, or host names for registering the\nco-located media server and the Snapshot Manager. Also, if the media server\nandtheSnapshotManagerareco-located,andthemediaserverusesport443,\nthen the Snapshot Manager must use a custom SSL port." }, "9897": { "code": 9897, - "desc": "Falhou to reassign o ownership de o raiz certificate caminho ou arquivo to o service usuário.", - "first_action": "Add ou modify o Snapshot Manager configuration usando o tpconfig", - "full_action": "Executar o seguinte como appropriate:\n■ Add ou modify o Snapshot Manager configuration usando o tpconfig\ncomando. Run o tpconfig comando como um raiz usuário. This ação re-assigns\no ownership de o raiz certificate caminho ou o certificate arquivo to o NetBackup\nservice usuário.\n■ Review e re-assign o ownership e permissions para o NetBackup\ncertificate store (/usr/openv/var/global/cloudpoint) to o NetBackup\nservice usuário." + "desc": "Failed to reassign the ownership of the root certificate path or file to the service user.", + "first_action": "Add or modify the Snapshot Manager configuration using the tpconfig", + "full_action": "Perform the following as appropriate:\n■ Add or modify the Snapshot Manager configuration using the tpconfig\ncommand. Run the tpconfig command as a root user. This action re-assigns\nthe ownership of the root certificate path or the certificate file to the NetBackup\nservice user.\n■ Review and re-assign the ownership and permissions for the NetBackup\ncertificate store (/usr/openv/var/global/cloudpoint) to the NetBackup\nservice user." }, "9901": { "code": 9901, - "desc": "'backupId' has um inválido syntax", + "desc": "'backupId' has an invalid syntax", "first_action": "Checktoseeif'backupId'hasavalidsyntax;forexample,", "full_action": "Checktoseeif'backupId'hasavalidsyntax;forexample,\ntestclient_1054264097." }, "9902": { "code": 9902, - "desc": "Não recovery request specified", - "first_action": "O recovery request body should não be vazio.", - "full_action": "O recovery request body should não be vazio." + "desc": "No recovery request specified", + "first_action": "The recovery request body should not be empty.", + "full_action": "The recovery request body should not be empty." }, "9903": { "code": 9903, - "desc": "'vmDisplayName' must não contain more than 80 characters.", + "desc": "'vmDisplayName' must not contain more than 80 characters.", "first_action": "Pleasemakesurethat'vmDisplayName'doesnotcontain", "full_action": "Pleasemakesurethat'vmDisplayName'doesnotcontain\nmore than 80 characters." }, "9904": { "code": 9904, - "desc": "'defaultDiskProvisioning' has um inválido value", - "first_action": "O 'defaultDiskProvisioning' identifier should have", - "full_action": "O 'defaultDiskProvisioning' identifier should have\none de o seguinte values: thin, thick-lazy-zeroed, ou thick-eager-zeroed." + "desc": "'defaultDiskProvisioning' has an invalid value", + "first_action": "The 'defaultDiskProvisioning' identifier should have", + "full_action": "The 'defaultDiskProvisioning' identifier should have\none of the following values: thin, thick-lazy-zeroed, or thick-eager-zeroed." }, "9905": { "code": 9905, - "desc": "'type' specified in o recovery request está inválido", - "first_action": "O 'type' identifier in o recovery request must be set", - "full_action": "O 'type' identifier in o recovery request must be set\nto 'recoveryRequest'." + "desc": "'type' specified in the recovery request is invalid", + "first_action": "The 'type' identifier in the recovery request must be set", + "full_action": "The 'type' identifier in the recovery request must be set\nto 'recoveryRequest'." }, "9906": { "code": 9906, - "desc": "'transportMode' has um inválido syntax", - "first_action": "O 'transportMode' identifier must be specified in", - "full_action": "O 'transportMode' identifier must be specified in\nlowercase, com colon-separated values; para example, hotadd:nbd:nbdssl:san.\nO order de o specified modes está significant, como NetBackup attempts each mode\nin order until o recovery está successful." + "desc": "'transportMode' has an invalid syntax", + "first_action": "The 'transportMode' identifier must be specified in", + "full_action": "The 'transportMode' identifier must be specified in\nlowercase, with colon-separated values; for example, hotadd:nbd:nbdssl:san.\nThe order of the specified modes is significant, as NetBackup attempts each mode\nin order until the recovery is successful." }, "9907": { "code": 9907, - "desc": "'recoveryPoint' must be specified in o recovery request", - "first_action": "O 'recoveryPoint' identifier está mandatory para o", - "full_action": "O 'recoveryPoint' identifier está mandatory para o\nrecovery operation, so it must be specified in o recovery request." + "desc": "'recoveryPoint' must be specified in the recovery request", + "first_action": "The 'recoveryPoint' identifier is mandatory for the", + "full_action": "The 'recoveryPoint' identifier is mandatory for the\nrecovery operation, so it must be specified in the recovery request." }, "9909": { "code": 9909, - "desc": "Falhou to fetch todos o requerido images.", - "first_action": "Review o informação para um recovery point e use um", - "full_action": "Review o informação para um recovery point e use um\nrecovery point com um valid, complete set de images." + "desc": "Failed to fetch all the required images.", + "first_action": "Review the information for a recovery point and use a", + "full_action": "Review the information for a recovery point and use a\nrecovery point with a valid, complete set of images." }, "9910": { "code": 9910, - "desc": "'datacenter' must não be blank", + "desc": "'datacenter' must not be blank", "first_action": "Youmustspecifyadatacentervalueforthe'datacenter'", "full_action": "Youmustspecifyadatacentervalueforthe'datacenter'\nidentifier." }, "9911": { "code": 9911, - "desc": "'vmxDatastore' must não be blank", - "first_action": "You must specify o vmx datastore type para o", - "full_action": "You must specify o vmx datastore type para o\n'vmxDatastore' identifier." + "desc": "'vmxDatastore' must not be blank", + "first_action": "You must specify the vmx datastore type for the", + "full_action": "You must specify the vmx datastore type for the\n'vmxDatastore' identifier." }, "9912": { "code": 9912, - "desc": "'diskMediaServer' must não be blank", - "first_action": "You must specify um disco mídia servidor para o", - "full_action": "You must specify um disco mídia servidor para o\n'diskMediaServer' identifier. Para example, \"diskMediaServer\" :\n\"media-server.example.com\"." + "desc": "'diskMediaServer' must not be blank", + "first_action": "You must specify a disk media server for the", + "full_action": "You must specify a disk media server for the\n'diskMediaServer' identifier. For example, \"diskMediaServer\" :\n\"media-server.example.com\"." }, "9913": { "code": 9913, - "desc": "'defaultDiskProvisioning' must não be blank", - "first_action": "You must specify um value para o", - "full_action": "You must specify um value para o\n'defaultDiskProvisioning' identifier. Valid values estão thin, thick-lazy-zeroed,\nou thick-eager-zeroed." + "desc": "'defaultDiskProvisioning' must not be blank", + "first_action": "You must specify a value for the", + "full_action": "You must specify a value for the\n'defaultDiskProvisioning' identifier. Valid values are thin, thick-lazy-zeroed,\nor thick-eager-zeroed." }, "9914": { "code": 9914, - "desc": "'esxiServer' must não be blank", - "first_action": "You must specify um servidor name para o 'esxiServer'", - "full_action": "You must specify um servidor name para o 'esxiServer'\nidentifier. Para example, \"esxiServer\" : \"esx-server.example.com\"." + "desc": "'esxiServer' must not be blank", + "first_action": "You must specify a server name for the 'esxiServer'", + "full_action": "You must specify a server name for the 'esxiServer'\nidentifier. For example, \"esxiServer\" : \"esx-server.example.com\"." }, "9915": { "code": 9915, - "desc": "'vmFolder' must não be blank", - "first_action": "You must specify um VM folder name para o 'vmFolder'", - "full_action": "You must specify um VM folder name para o 'vmFolder'\nidentifier." + "desc": "'vmFolder' must not be blank", + "first_action": "You must specify a VM folder name for the 'vmFolder'", + "full_action": "You must specify a VM folder name for the 'vmFolder'\nidentifier." }, "9916": { "code": 9916, - "desc": "'network' must não be blank", + "desc": "'network' must not be blank", "first_action": "YoumustspecifythenameoftheVirtualMachineNetwork", - "full_action": "YoumustspecifythenameoftheVirtualMachineNetwork\npara o 'network' identifier." + "full_action": "YoumustspecifythenameoftheVirtualMachineNetwork\nfor the 'network' identifier." }, "9917": { "code": 9917, - "desc": "'recoveryHost' must não be blank", - "first_action": "You must specify o recovery host name para o", - "full_action": "You must specify o recovery host name para o\n'recoveryHost' identifier. Para example, \"recoveryHost\" :\n\"recovery-proxy.example.com\"." + "desc": "'recoveryHost' must not be blank", + "first_action": "You must specify the recovery host name for the", + "full_action": "You must specify the recovery host name for the\n'recoveryHost' identifier. For example, \"recoveryHost\" :\n\"recovery-proxy.example.com\"." }, "9918": { "code": 9918, - "desc": "'resourcePoolOrVapp' must não be blank", - "first_action": "You must specify o pathname de either o resource", - "full_action": "You must specify o pathname de either o resource\npool destination ou o vApp para o 'resourcePoolOrVapp' identifier." + "desc": "'resourcePoolOrVapp' must not be blank", + "first_action": "You must specify the pathname of either the resource", + "full_action": "You must specify the pathname of either the resource\npool destination or the vApp for the 'resourcePoolOrVapp' identifier." }, "9919": { "code": 9919, - "desc": "'transportMode' must não be blank", - "first_action": "You must specify o transport mode combination que está", - "full_action": "You must specify o transport mode combination que está\nto be used to executar o recovery. O string must be specified in lowercase, com\ncolon-separatedvaluessuchashotadd:nbd:nbdssl:san.Theorderofthespecified\nmodes está significant, como NetBackup attempts each mode in o specified order until\no recovery está successful. If nenhum de o modes estão successful, o recovery fails." + "desc": "'transportMode' must not be blank", + "first_action": "You must specify the transport mode combination that is", + "full_action": "You must specify the transport mode combination that is\nto be used to perform the recovery. The string must be specified in lowercase, with\ncolon-separatedvaluessuchashotadd:nbd:nbdssl:san.Theorderofthespecified\nmodes is significant, as NetBackup attempts each mode in the specified order until\nthe recovery is successful. If none of the modes are successful, the recovery fails." }, "9920": { "code": 9920, - "desc": "'vCenter' must não be blank", - "first_action": "You must specify o vCenter servidor name; para example,", - "full_action": "You must specify o vCenter servidor name; para example,\n\"vCenter\" : \"vcenter-server.example.com\"." + "desc": "'vCenter' must not be blank", + "first_action": "You must specify the vCenter server name; for example,", + "full_action": "You must specify the vCenter server name; for example,\n\"vCenter\" : \"vcenter-server.example.com\"." }, "9921": { "code": 9921, - "desc": "'datacenter' must begin com um '/'", - "first_action": "O 'datacenter' caminho must begin com um forward slash (/);", - "full_action": "O 'datacenter' caminho must begin com um forward slash (/);\npara example, \"datacenter\" : \"/example-DC\"." + "desc": "'datacenter' must begin with a '/'", + "first_action": "The 'datacenter' path must begin with a forward slash (/);", + "full_action": "The 'datacenter' path must begin with a forward slash (/);\nfor example, \"datacenter\" : \"/example-DC\"." }, "9922": { "code": 9922, - "desc": "'vmFolder' must begin com um '/'", - "first_action": "You must specify um forward slash (/) at o beginning de", - "full_action": "You must specify um forward slash (/) at o beginning de\no 'vmFolder' caminho; para example, \"vmFolder\":\"/example-DC/vm\"." + "desc": "'vmFolder' must begin with a '/'", + "first_action": "You must specify a forward slash (/) at the beginning of", + "full_action": "You must specify a forward slash (/) at the beginning of\nthe 'vmFolder' path; for example, \"vmFolder\":\"/example-DC/vm\"." }, "9923": { "code": 9923, - "desc": "'resourcePoolOrVapp' must begin com um '/' NetBackup status codes 1193 NetBackup status codes", - "first_action": "You must specify um forward slash (/) at o beginning de", - "full_action": "You must specify um forward slash (/) at o beginning de\no 'resourcePoolOrVapp' caminho; para example, \"resourcePoolOrVapp\" :\n\"/example-DC/host/esx.example.com/Resources/example-res-pool\"." + "desc": "'resourcePoolOrVapp' must begin with a '/' NetBackup status codes 1193 NetBackup status codes", + "first_action": "You must specify a forward slash (/) at the beginning of", + "full_action": "You must specify a forward slash (/) at the beginning of\nthe 'resourcePoolOrVapp' path; for example, \"resourcePoolOrVapp\" :\n\"/example-DC/host/esx.example.com/Resources/example-res-pool\"." }, "9926": { "code": 9926, - "desc": "JSON input está inválido", - "first_action": "O JSON request has um inválido syntax.", - "full_action": "O JSON request has um inválido syntax." + "desc": "JSON input is invalid", + "first_action": "The JSON request has an invalid syntax.", + "full_action": "The JSON request has an invalid syntax." }, "9928": { "code": 9928, - "desc": "Não workload está specified", - "first_action": "Specify o workload in o Recovery API endpoint com", - "full_action": "Specify o workload in o Recovery API endpoint com\no seguinte format:\n/recovery/workloads/workload/scenarios/scenario/recover\nPara example, /recovery/workloads/vmware/scenarios/full-vm/recover." + "desc": "No workload is specified", + "first_action": "Specify the workload in the Recovery API endpoint with", + "full_action": "Specify the workload in the Recovery API endpoint with\nthe following format:\n/recovery/workloads/workload/scenarios/scenario/recover\nFor example, /recovery/workloads/vmware/scenarios/full-vm/recover." }, "9929": { "code": 9929, - "desc": "Inválido workload specified", + "desc": "Invalid workload specified", "first_action": "SpecifythecorrectworkloadintherecoveryrequestURL.", "full_action": "SpecifythecorrectworkloadintherecoveryrequestURL." }, "9930": { "code": 9930, - "desc": "Não scenario está specified", - "first_action": "Specify o scenario in o Recovery API endpoint com", - "full_action": "Specify o scenario in o Recovery API endpoint com\no seguinte format:\n/recovery/workloads/workload/scenarios/scenario/recover\nPara example, /recovery/workloads/vmware/scenarios/full-vm/recover." + "desc": "No scenario is specified", + "first_action": "Specify the scenario in the Recovery API endpoint with", + "full_action": "Specify the scenario in the Recovery API endpoint with\nthe following format:\n/recovery/workloads/workload/scenarios/scenario/recover\nFor example, /recovery/workloads/vmware/scenarios/full-vm/recover." }, "9931": { "code": 9931, - "desc": "Inválido scenario specified", - "first_action": "Specify o correct scenario in o recovery request URL.", - "full_action": "Specify o correct scenario in o recovery request URL." + "desc": "Invalid scenario specified", + "first_action": "Specify the correct scenario in the recovery request URL.", + "full_action": "Specify the correct scenario in the recovery request URL." }, "9934": { "code": 9934, - "desc": "O specified end date time in o 'filter' must não be less than o start date time", - "first_action": "Specify um end date in o 'filter' que está não less than o", - "full_action": "Specify um end date in o 'filter' que está não less than o\nstart date. Veja o seguinte example:\n\"filter\" : \"backupTime ge '2017-11-20T23:20:50Z' e backupTime le '2018-12-20T23:20:50Z'\"" + "desc": "The specified end date time in the 'filter' must not be less than the start date time", + "first_action": "Specify an end date in the 'filter' that is not less than the", + "full_action": "Specify an end date in the 'filter' that is not less than the\nstart date. See the following example:\n\"filter\" : \"backupTime ge '2017-11-20T23:20:50Z' and backupTime le '2018-12-20T23:20:50Z'\"" }, "9935": { "code": 9935, - "desc": "O specified date-time values in o 'filter' must use um valid ISO 8601 format", + "desc": "The specified date-time values in the 'filter' must use a valid ISO 8601 format", "first_action": "Specifythedate-timevaluesinthe'filter'usingavalidISO", - "full_action": "Specifythedate-timevaluesinthe'filter'usingavalidISO\n8601format.FormoreinformationabouttheISO8601format,seeISO8601format.\nVeja o seguinte example para um valid ISO 8601 format:\n\"filter\" : \"backupTime ge '2017-11-20T23:20:50Z' e backupTime le '2018-12-20T23:20:50Z'\"" + "full_action": "Specifythedate-timevaluesinthe'filter'usingavalidISO\n8601format.FormoreinformationabouttheISO8601format,seeISO8601format.\nSee the following example for a valid ISO 8601 format:\n\"filter\" : \"backupTime ge '2017-11-20T23:20:50Z' and backupTime le '2018-12-20T23:20:50Z'\"" }, "9936": { "code": 9936, - "desc": "O specified date-time values in o 'filter' must não be in o future", - "first_action": "Specify o date-time values in o 'filter' so they estão less", - "full_action": "Specify o date-time values in o 'filter' so they estão less\nthan o current time." + "desc": "The specified date-time values in the 'filter' must not be in the future", + "first_action": "Specify the date-time values in the 'filter' so they are less", + "full_action": "Specify the date-time values in the 'filter' so they are less\nthan the current time." }, "9937": { "code": 9937, - "desc": "Either 'backupId' ou 'client' must be specified in o recovery request", + "desc": "Either 'backupId' or 'client' must be specified in the recovery request", "first_action": "Specifyeither'backupId'or'client'intherecoveryrequest.", - "full_action": "Specifyeither'backupId'or'client'intherecoveryrequest.\nO recovery request requires either o 'backupId' ou 'client' name." + "full_action": "Specifyeither'backupId'or'client'intherecoveryrequest.\nThe recovery request requires either the 'backupId' or 'client' name." }, "9938": { "code": 9938, - "desc": "'backupId' must não be specified along com 'client' ou 'filter'", - "first_action": "Do não specify 'backupId' com 'client' ou 'filter'.", - "full_action": "Do não specify 'backupId' com 'client' ou 'filter'." + "desc": "'backupId' must not be specified along with 'client' or 'filter'", + "first_action": "Do not specify 'backupId' with 'client' or 'filter'.", + "full_action": "Do not specify 'backupId' with 'client' or 'filter'." }, "9939": { "code": 9939, - "desc": "Inválido 'filter' syntax", - "first_action": "Specify o 'filter' field com um valid Odata syntax. Veja o", - "full_action": "Specify o 'filter' field com um valid Odata syntax. Veja o\nseguinte example:\n\"filter\" : \"backupTime ge '2017-11-20T23:20:50Z' e backupTime le '2018-12-20T23:20:50Z'\"" + "desc": "Invalid 'filter' syntax", + "first_action": "Specify the 'filter' field with a valid Odata syntax. See the", + "full_action": "Specify the 'filter' field with a valid Odata syntax. See the\nfollowing example:\n\"filter\" : \"backupTime ge '2017-11-20T23:20:50Z' and backupTime le '2018-12-20T23:20:50Z'\"" }, "9940": { "code": 9940, - "desc": "'backupId' must não be specified com either 'sourceAsset' ou 'filter'", - "first_action": "Specify 'backupId' without either 'sourceAsset' ou 'filter.'", - "full_action": "Specify 'backupId' without either 'sourceAsset' ou 'filter.'\nO recovery request apenas accepts 'backupId'; it does não work along com\n'sourceAsset' ou filter." + "desc": "'backupId' must not be specified with either 'sourceAsset' or 'filter'", + "first_action": "Specify 'backupId' without either 'sourceAsset' or 'filter.'", + "full_action": "Specify 'backupId' without either 'sourceAsset' or 'filter.'\nThe recovery request only accepts 'backupId'; it does not work along with\n'sourceAsset' or filter." }, "9941": { "code": 9941, - "desc": "'attributes' must be specified in o recovery request", - "first_action": "Specify 'attributes' in o recovery request.", - "full_action": "Specify 'attributes' in o recovery request." + "desc": "'attributes' must be specified in the recovery request", + "first_action": "Specify 'attributes' in the recovery request.", + "full_action": "Specify 'attributes' in the recovery request." }, "9942": { "code": 9942, - "desc": "Either 'backupId' ou 'sourceAsset' must be specified in o recovery request", + "desc": "Either 'backupId' or 'sourceAsset' must be specified in the recovery request", "first_action": "Specifyeither'backupId'or'sourceAssetId'intherecovery", "full_action": "Specifyeither'backupId'or'sourceAssetId'intherecovery\nrequest." }, "9944": { "code": 9944, - "desc": "Não matching backup image found to executar o recovery NetBackup status codes 1197 NetBackup status codes", - "first_action": "Garanta que o cliente exists e, if it exists, then garanta", - "full_action": "Garanta que o cliente exists e, if it exists, then garanta\nque it has been salvo up at least once." + "desc": "No matching backup image found to perform the recovery NetBackup status codes 1197 NetBackup status codes", + "first_action": "Ensure that the client exists and, if it exists, then ensure", + "full_action": "Ensure that the client exists and, if it exists, then ensure\nthat it has been backed up at least once." }, "9946": { "code": 9946, - "desc": "Inválido field foi specified in o 'filter'", - "first_action": "Garanta que o 'filter' está allowed on o specified field.", - "full_action": "Garanta que o 'filter' está allowed on o specified field.\nRefer to o API documentation para o allowable filter operations." + "desc": "Invalid field was specified in the 'filter'", + "first_action": "Ensure that the 'filter' is allowed on the specified field.", + "full_action": "Ensure that the 'filter' is allowed on the specified field.\nRefer to the API documentation for the allowable filter operations." }, "9947": { "code": 9947, - "desc": "Inválido comparison operator specified para o field", - "first_action": "Garanta que o comparison operators specified estão", - "full_action": "Garanta que o comparison operators specified estão\nsupported para o field. Refer to o API documentation para o correct operators para\neach supported field." + "desc": "Invalid comparison operator specified for the field", + "first_action": "Ensure that the comparison operators specified are", + "full_action": "Ensure that the comparison operators specified are\nsupported for the field. Refer to the API documentation for the correct operators for\neach supported field." }, "9948": { "code": 9948, - "desc": "Grouping operator está não allowed in o 'filter'", - "first_action": "O grouping operator está não allowed in o 'filter.' Refer", - "full_action": "O grouping operator está não allowed in o 'filter.' Refer\nto o API documentation para o allowable filter operation." + "desc": "Grouping operator is not allowed in the 'filter'", + "first_action": "The grouping operator is not allowed in the 'filter.' Refer", + "full_action": "The grouping operator is not allowed in the 'filter.' Refer\nto the API documentation for the allowable filter operation." }, "9949": { "code": 9949, - "desc": "Inválido logical operator está specified in o 'filter'", - "first_action": "O logical operator está não allowed in o 'filter.' Refer to", - "full_action": "O logical operator está não allowed in o 'filter.' Refer to\no API documentation para o allowable filter operation." + "desc": "Invalid logical operator is specified in the 'filter'", + "first_action": "The logical operator is not allowed in the 'filter.' Refer to", + "full_action": "The logical operator is not allowed in the 'filter.' Refer to\nthe API documentation for the allowable filter operation." }, "9968": { "code": 9968, - "desc": "Não recovery object specified como part de o recovery request.", - "first_action": "Verifique que o recoveryObject field está specified e que", - "full_action": "Verifique que o recoveryObject field está specified e que\nit está não vazio." + "desc": "No recovery object specified as part of the recovery request.", + "first_action": "Verify that the recoveryObject field is specified and that", + "full_action": "Verify that the recoveryObject field is specified and that\nit is not empty." }, "9969": { "code": 9969, - "desc": "Inválido recovery object specified.", - "first_action": "Verifique que o value de recoveryObject está um object e", - "full_action": "Verifique que o value de recoveryObject está um object e\nque it contains todos requerido fields: credentials e assetId." + "desc": "Invalid recovery object specified.", + "first_action": "Verify that the value of recoveryObject is an object and", + "full_action": "Verify that the value of recoveryObject is an object and\nthat it contains all required fields: credentials and assetId." }, "9970": { "code": 9970, - "desc": "Falhou to get o result de o recovery request.", - "first_action": "Verifique que NetBackup services estão executando e que o", - "full_action": "Verifique que NetBackup services estão executando e que o\nrequest has o proper syntax." + "desc": "Failed to get the result of the recovery request.", + "first_action": "Verify that NetBackup services are running and that the", + "full_action": "Verify that NetBackup services are running and that the\nrequest has the proper syntax." }, "9971": { "code": 9971, - "desc": "O recoveryPoint field must be specified.", - "first_action": "Verifique que o recoveryPoint field has been provided", - "full_action": "Verifique que o recoveryPoint field has been provided\ne que it está não um vazio string. Also garanta que o scenario está um complete\ndatabaserecoveryintheURL.SpecifyarecoverypointintherecoveryPointfield." + "desc": "The recoveryPoint field must be specified.", + "first_action": "Verify that the recoveryPoint field has been provided", + "full_action": "Verify that the recoveryPoint field has been provided\nand that it is not an empty string. Also ensure that the scenario is a complete\ndatabaserecoveryintheURL.SpecifyarecoverypointintherecoveryPointfield." }, "9972": { "code": 9972, - "desc": "O assetId field must be specified.", - "first_action": "Verifique que o assetId field has been provided e que", - "full_action": "Verifique que o assetId field has been provided e que\nit está não um vazio string. Specify um asset ID in o assetId field." + "desc": "The assetId field must be specified.", + "first_action": "Verify that the assetId field has been provided and that", + "full_action": "Verify that the assetId field has been provided and that\nit is not an empty string. Specify an asset ID in the assetId field." }, "9973": { "code": 9973, - "desc": "O domain field must be specified.", - "first_action": "Verifique que o domain field has been provided e que it", - "full_action": "Verifique que o domain field has been provided e que it\nestá não um vazio string. Specify um domain in o domain field." + "desc": "The domain field must be specified.", + "first_action": "Verify that the domain field has been provided and that it", + "full_action": "Verify that the domain field has been provided and that it\nis not an empty string. Specify a domain in the domain field." }, "9974": { "code": 9974, - "desc": "O usuário field must be specified.", - "first_action": "Verifique que o usuário field has been provided e que it está", - "full_action": "Verifique que o usuário field has been provided e que it está\nnão um vazio string. Specify um usuário name in o usuário field." + "desc": "The user field must be specified.", + "first_action": "Verify that the user field has been provided and that it is", + "full_action": "Verify that the user field has been provided and that it is\nnot an empty string. Specify a user name in the user field." }, "9975": { "code": 9975, - "desc": "O password field must be specified.", - "first_action": "Verifique que o password field has been provided e que", - "full_action": "Verifique que o password field has been provided e que\nit está não um vazio string. Specify um password in o password field." + "desc": "The password field must be specified.", + "first_action": "Verify that the password field has been provided and that", + "full_action": "Verify that the password field has been provided and that\nit is not an empty string. Specify a password in the password field." }, "9976": { "code": 9976, "desc": "ExactlyoneoptioninthealternateFileLocationfieldmustbespecified.", - "first_action": "Verifique que apenas one de o options está specified. Specify", - "full_action": "Verifique que apenas one de o options está specified. Specify\napenas one de o alternate arquivo location options in o alternateFileLocation field." + "first_action": "Verify that only one of the options is specified. Specify", + "full_action": "Verify that only one of the options is specified. Specify\nonly one of the alternate file location options in the alternateFileLocation field." }, "9977": { "code": 9977, - "desc": "O renameAllFilesToSameLocation field must be specified.", - "first_action": "If o renameAllFilesToSameLocation field está specified,", - "full_action": "If o renameAllFilesToSameLocation field está specified,\nverifique que it está não um vazio string. Specify um location to which to restauração todos arquivos in\no renameAllFilesToSameLocation field." + "desc": "The renameAllFilesToSameLocation field must be specified.", + "first_action": "If the renameAllFilesToSameLocation field is specified,", + "full_action": "If the renameAllFilesToSameLocation field is specified,\nverify that it is not an empty string. Specify a location to which to restore all files in\nthe renameAllFilesToSameLocation field." }, "9978": { "code": 9978, - "desc": "O renameEachFileToDifferentLocation field must be specified.", - "first_action": "If o renameEachFileToDifferentLocation field está", - "full_action": "If o renameEachFileToDifferentLocation field está\nspecified, verifique que nenhum de o fields de qualquer de its list items está um vazio string.\nSpecify um list de arquivo names e alternate paths in o\nrenameEachFileToDifferentLocation field." + "desc": "The renameEachFileToDifferentLocation field must be specified.", + "first_action": "If the renameEachFileToDifferentLocation field is", + "full_action": "If the renameEachFileToDifferentLocation field is\nspecified, verify that none of the fields of any of its list items is an empty string.\nSpecify a list of file names and alternate paths in the\nrenameEachFileToDifferentLocation field." }, "9979": { "code": 9979, - "desc": "O restorePriority field must be specified.", - "first_action": "If o restorePriority field está specified, verifique que it está", - "full_action": "If o restorePriority field está specified, verifique que it está\nnão um vazio string. Specify um valid restauração priority in o restorePriority field.\nValid values estão in o range 0-99999." + "desc": "The restorePriority field must be specified.", + "first_action": "If the restorePriority field is specified, verify that it is", + "full_action": "If the restorePriority field is specified, verify that it is\nnot an empty string. Specify a valid restore priority in the restorePriority field.\nValid values are in the range 0-99999." }, "9980": { "code": 9980, - "desc": "O destinationAssetId parâmetro está requerido para alternate restauração.", + "desc": "The destinationAssetId parameter is required for alternate restore.", "first_action": "ProvidethedestinationassetIDandre-runtheoperation.", "full_action": "ProvidethedestinationassetIDandre-runtheoperation." }, "9981": { "code": 9981, - "desc": "Inválido parâmetro destinationAssetId provided para restauração to original location.", - "first_action": "Remove o destination asset ID parâmetro e re-run", - "full_action": "Remove o destination asset ID parâmetro e re-run\no operation." + "desc": "Invalid parameter destinationAssetId provided for restore to original location.", + "first_action": "Remove the destination asset ID parameter and re-run", + "full_action": "Remove the destination asset ID parameter and re-run\nthe operation." }, "9982": { "code": 9982, - "desc": "Recovery request contains um inválido value para o image copy. Provide um value between 1 to 10.", - "first_action": "Provide um value between 1 e 10 para o image copy.", - "full_action": "Provide um value between 1 e 10 para o image copy.\nPara primary copy, do não provide qualquer value e skip this step." + "desc": "Recovery request contains an invalid value for the image copy. Provide a value between 1 to 10.", + "first_action": "Provide a value between 1 and 10 for the image copy.", + "full_action": "Provide a value between 1 and 10 for the image copy.\nFor primary copy, do not provide any value and skip this step." }, "9983": { "code": 9983, - "desc": "Inválido asset ID specified in o recovery request.", - "first_action": "Review o asset ID e confirm que it está correct. If o", - "full_action": "Review o asset ID e confirm que it está correct. If o\nissue persists, contate Cohesity Technical Support para additional troubleshooting." + "desc": "Invalid asset ID specified in the recovery request.", + "first_action": "Review the asset ID and confirm that it is correct. If the", + "full_action": "Review the asset ID and confirm that it is correct. If the\nissue persists, contact Cohesity Technical Support for additional troubleshooting." }, "9984": { "code": 9984, - "desc": "Inválido parâmetro destinationAssetId provided para rollback recovery.", - "first_action": "Remove o destination asset ID parâmetro e re-run", - "full_action": "Remove o destination asset ID parâmetro e re-run\no operation." + "desc": "Invalid parameter destinationAssetId provided for rollback recovery.", + "first_action": "Remove the destination asset ID parameter and re-run", + "full_action": "Remove the destination asset ID parameter and re-run\nthe operation." }, "9986": { "code": 9986, - "desc": "Input validation de GRT request falhou.", - "first_action": "Para more informação, refer to o NetBackup Cloud", - "full_action": "Para more informação, refer to o NetBackup Cloud\nFile-Folders restauração request API documentation e sample payload." + "desc": "Input validation of GRT request failed.", + "first_action": "For more information, refer to the NetBackup Cloud", + "full_action": "For more information, refer to the NetBackup Cloud\nFile-Folders restore request API documentation and sample payload." }, "9990": { "code": 9990, - "desc": "O target host staging location caminho contains non-ASCII characters.", - "first_action": "Provide o staging location, on o target host, usando", - "full_action": "Provide o staging location, on o target host, usando\nACSII characters." + "desc": "The target host staging location path contains non-ASCII characters.", + "first_action": "Provide the staging location, on the target host, using", + "full_action": "Provide the staging location, on the target host, using\nACSII characters." }, "9991": { "code": 9991, - "desc": "O backupId, sourceAsset, ou filter não é possível be specified com providerRecoveryPointId.", - "first_action": "If o providerRecoveryPointId está specified, then o", - "full_action": "If o providerRecoveryPointId está specified, then o\nbackupId, sourceAssetId, ou filter não é possível be specified in o API call. O\noptions estão applicable apenas para o provider-generated recovery points." + "desc": "The backupId, sourceAsset, or filter cannot be specified with providerRecoveryPointId.", + "first_action": "If the providerRecoveryPointId is specified, then the", + "full_action": "If the providerRecoveryPointId is specified, then the\nbackupId, sourceAssetId, or filter cannot be specified in the API call. The\noptions are applicable only for the provider-generated recovery points." }, "9992": { "code": 9992, - "desc": "Não é possível executar recovery because o resource foi não found.", - "first_action": "Retry o operation e if o issue persists, visit", - "full_action": "Retry o operation e if o issue persists, visit\nsupport.veritas.com. O Cohesity Technical Support website site offers additional\ninformação to help you troubleshoot this issue." + "desc": "Cannot perform recovery because the resource was not found.", + "first_action": "Retry the operation and if the issue persists, visit", + "full_action": "Retry the operation and if the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support website site offers additional\ninformation to help you troubleshoot this issue." }, "9993": { "code": 9993, - "desc": "Não é possível executar recovery due to um restricted operation.", - "first_action": "To executar o solicitado operation, you must be um raiz", - "full_action": "To executar o solicitado operation, you must be um raiz\nusuário, administrator, ou have o appropriate privileges through RBAC. Contate o\nNetBackup system administrator.\n1204\nNetBackup KMS status codes" + "desc": "Cannot perform recovery due to a restricted operation.", + "first_action": "To perform the requested operation, you must be a root", + "full_action": "To perform the requested operation, you must be a root\nuser, administrator, or have the appropriate privileges through RBAC. Contact the\nNetBackup system administrator.\n1204\nNetBackup KMS status codes" }, "9997": { "code": 9997, - "desc": "Backup from snapshot e indexing está não supported para um Azure disco encryption enabled virtual machine.", - "first_action": "Apenas snapshot e restauração estão supported para Azure disco encryption enabled virtual", - "full_action": "Executar o seguinte como appropriate:\nApenas snapshot e restauração estão supported para Azure disco encryption enabled virtual\nmachine." + "desc": "Backup from snapshot and indexing is not supported for an Azure disk encryption enabled virtual machine.", + "first_action": "Only snapshot and restore are supported for Azure disk encryption enabled virtual", + "full_action": "Perform the following as appropriate:\nOnly snapshot and restore are supported for Azure disk encryption enabled virtual\nmachine." }, "9998": { "code": 9998, - "desc": "Snapshot está não supported para Azure disco encryption-enabled volume.", - "first_action": "Single volume snapshot está não supported. Executar um snapshot de o entire virtual", - "full_action": "Executar o seguinte como appropriate:\nSingle volume snapshot está não supported. Executar um snapshot de o entire virtual\nmachine." + "desc": "Snapshot is not supported for Azure disk encryption-enabled volume.", + "first_action": "Single volume snapshot is not supported. Perform a snapshot of the entire virtual", + "full_action": "Perform the following as appropriate:\nSingle volume snapshot is not supported. Perform a snapshot of the entire virtual\nmachine." } } \ No newline at end of file