Quantcast
Channel: Backup Activity
Viewing all 107 articles
Browse latest View live
↧

Tunneling Connection For Restricted Database Server

February 6, 2012, 10:06 pm
$
0
0
Sometimes, we are facing the situation where our database server (here is Oracle engine) is not permitted to administer with directly connection. The directly connection between database server and our third party client software (such like TOAD) is not allowed anymore. The result is we have to type manually the command line trough the UNIX console. For knowing the table space size and status we have to write some sql script, its very difficult to do.

But, thanks for putty software, a little console client software. By using the tunneling features we will have 'as' direct connection our third party database client software directly to our Oracle database.

Here are the steps:
  • Create new connection configuration. Define hostname/IP Address to a server having connection access to database server (using ssh connection).
  • Choose "Tunnels" option and fill the option. Fill the New forwarded port with specify numeric and fill the destination with IP Address and oracle port (1521).
  • Create new connection string at the tnsnames.ora. Point the host to your localhost where the putty connection is running.
  • Fill the username and password at the TOAD new connection form.
  • Enjoy your free directly access to browse your restricted database object.

I believe, this is not the only one solution, any body else have their own way and tools for doing this. But this is what I have done and go!.

↧
Search

Symantec NetBackup™ 7.5 Features

January 28, 2013, 12:16 am
$
0
0
It's been known if Symantec Netbackup is the most powerfull multi platform backup software known in the industry. Symantec has launched the newews version of Netbackup, to version 7.5. What's new in this version?

Symantec NetBackup™ 7.5 is the single backup solution when recovery is needed, whether from tape, disk, snapshot, cloud–physical or virtual. The Symantec NetBackup™ 7.5 with V-Ray technology can unify backup, deduplication, replication, snapshots, and appliances with support for VMware® and Microsoft Hyper-V® in a single product helping to reduce complexity and cost.

Here are the main features of Symantec NetBackup™ 7.5 :
1. NetBackup Replication Director
This feature integrates the power of array-based snapshot technologies with traditional backup data management. Replication Director is designed to be the single integration point between primary storage and storage array hardware and backup operations.Replication Director solves all of these issues by managing array snapshots and automating replication to any supported secondary and tertiary storage as well as tape creation. Provisioning of replicas, cataloging, and granular file recovery are all controlled by NetBackup.

2. NetBackup Accelerator
This feature facilitates intelligent, streamlined backups to disk by increasing the speed of full backups. The increase in speed is made possible by change detection techniques on the client. The client uses the change detection techniques and the client's current file system to identify changes that occurred since the last backup. The client sends the changed data to the media server in a more efficient backup stream. The media server combines the changed data with the rest of the client's data that is stored in previous backups to create a new full backup image without needing to transfer all the client data. In other words, NetBackup Accelerator provides a full backup, but at the cost and speed of an incremental backup.

3. Search and Hold
NetBackup 7.5 introduces new functionality which allows an administrator to place backups on “Hold” to prevent them expiring on the due expiration date or being manually expired by an administrator. This is accomplished with a new binary that runs on a schedule which will “Index” the existing NetBackup catalog and store the information in a database on a specified media server. This database can then be “Searched” using OpsCenter. When the data is found, and a Hold is placed, the Search process modifies the NetBackup catalog and EMM database and puts a hook in the files to prevent the data from being expired until the Hold is removed.

4. Operational Restores with OpsCenter (ORO)
Operational Restores using OpsCenter (ORO) is functionality that allows other key stakeholders within the organization to recover their own files. These stakeholders may include the Help Desk, Application owners or the VM Administrator. This feature enables searching for files across any Master and/or Client that is configured with OpsCenter and includes wildcard searches, specific file type searches as well as filtering by a number of different methods. It also includes a "Restore Cart" that allows the restores to be placed in the cart for batch restores.

5.Application Protection for VMware Virtual Machines
The last few versions of NetBackup offered extensive features for protecting VMware virtual machines, as well as application agents for Microsoft® Exchange,SharePoint®, and SQL® Server databases. However, databases could only be protected by installing the NetBackup client on the VMware virtual machine running as a database server, and backing it up as if it were a physical machine. This has changed in NetBackup 7.5. It is now possible to use the NetBackup award-winning VMware backup technology while retaining the ability to recover databases using database agents.1 This includes restoring entire databases for disaster recovery purposes as well as individual database objects such as Exchange mail messages and SharePoint documents using the NetBackup patent-pending Granular Recovery Technology (GRT).

6. VMware Policy Enhancements
The design of the NetBackup policy has been refined and improved over many years of use. As backup technologies have evolved, minor changes to the NetBackup policy have been implemented as needed. This has worked very well for network based backups. Shared storage, SAN, and NDMP transfers have also been supported but these configurations are really just variations on client backups and typically require minimal changes to the NetBackup policy.Virtual machine technologies have ramatically changed backup requirements. Standard backup agents are installed on and focus on protecting files that exist within a running operating system. Virtual machine backups can be configured this way as well.

7. Cloud Enhancements
The first integration between NetBackup and a cloud storage provider (the Nirvanix® cloud plug-in) was introduced in NetBackup 7.1. This integration, based on the OpenStorage Technology (OST) API allows customers with Nirvanix accounts to configure Nirvanix cloud storage as a storage target for NetBackup and define storage units that send backup data to the cloud storage.

Source: www.symantec.com
↧
↧

Symantec Netbackup 7.5 Status Codes

January 30, 2013, 8:10 pm
$
0
0
0 the requested operation was successfully completed
1 the requested operation was partially successful
2 none of the requested files were backed up
3 valid archive image produced, but no files deleted due to non-fatal problems
4 archive file removal failed
5 the restore failed to recover the requested files
6 the backup failed to back up the requested files
7 the archive failed to back up the requested files
8 unable to determine the status of rbak
9 a necessary extension package is not installed or not configured properly
10 allocation failed
11 system call failed
12 file open failed
13 file read failed
14 file write failed
15 file close failed
16 unimplemented feature
17 pipe open failed
18 pipe close failed
19 getservbyname failed
20 invalid command parameter
21 socket open failed
22 socket close failed
23 socket read failed
24 socket write failed
25 cannot connect on socket
26 client/server handshaking failed
27 child process killed by signal
28 failed trying to fork a process
29 failed trying to exec a command
30 cannot get passwd information
31 could not set user id for process
32 could not set group id for process
33 failed while trying to send mail
34 failed waiting for child process
35 cannot make required directory
36 failed trying to allocate memory
37 operation requested by an invalid server
38 could not get group information
39 client name mismatch
40 network connection broken
41 network connection timed out
42 network read failed
43 unexpected message received
44 network write failed
45 request attempted on a non reserved port
46 server not allowed access
47 host is unreachable
48 client hostname could not be found
49 client did not start
50 client process aborted
51 timed out waiting for database information
52 timed out waiting for media manager to mount volume
53 backup restore manager failed to read the file list
54 timed out connecting to client
55 permission denied by client during rcmd
56 client’s network is unreachable
57 client connection refused
58 can’t connect to client
59 access to the client was not allowed
60 client cannot read the mount table
63 process was killed by a signal
64 timed out waiting for the client backup to start
65 client timed out waiting for the continue message from the media manager
66 client backup failed to receive the CONTINUE BACKUP message
67 client backup failed to read the file list
68 client timed out waiting for the file list
69 invalid filelist specification
70 an entry in the filelist expanded to too many characters
71 none of the files in the file list exist
72 the client type is incorrect in the configuration database
73 bpstart_notify failed
74 client timed out waiting for bpstart_notify to complete
75 client timed out waiting for bpend_notify to complete
76 client timed out reading file
77 execution of the specified system command returned a nonzero status
78 afs/dfs command failed
79 unsupported image format for the requested database query
80 Media Manager device daemon (ltid) is not active
81 Media Manager volume daemon (vmd) is not active
82 media manager killed by signal
83 media open error
84 media write error
85 media read error
86 media position error
87 media close error
89 problems encountered during setup of shared memory
90 media manager received no data for backup image
91 fatal NB media database error
92 media manager detected image that was not in tar format
93 media manager found wrong tape in drive
94 cannot position to correct image
95 media id is not assigned to this host in the EMM database
96 unable to allocate new media for backup, storage unit has none available
97 requested media id is in use, cannot process request
98 error requesting media (tpreq)
99 NDMP backup failure
100 system error occurred while processing user command
101 failed opening mail pipe
102 failed closing mail pipe
103 error occurred during initialization, check configuration file
104 invalid file pathname
105 file pathname exceeds the maximum length allowed
106 invalid file pathname found, cannot process request
108 Action succeeded but auditing failed
109 invalid date specified
110 Cannot find the NetBackup configuration information
111 No entry was found in the server list
112 no files specified in the file list
114 unimplemented error code
116 VxSS authentication failed
117 VxSS access denied
118 VxSS authorization failed
120 cannot find configuration database record for requested NB database backup
121 no media is defined for the requested NB database backup
122 specified device path does not exist
123 specified disk path is not a directory
124 NB database backup failed, a path was not found or is inaccessible
125 a NetBackup catalog backup is in progress
126 NB database backup header is too large, too many paths specified
127 specified media or path does not contain a valid NB database backup header
128 NB database recovery failed, a process has encountered an exceptional condition
129 Disk storage unit is full
130 system error occurred
131 client is not validated to use the server
132 user is not validated to use the server from this client
133 invalid request
134 unable to process request because the server resources are busy
135 client is not validated to perform the requested operation
136 TIR info was pruned from the image file
140 user id was not superuser
141 file path specified is not absolute
142 file does not exist
143 invalid command protocol
144 invalid command usage
145 daemon is already running
146 cannot get a bound socket
147 required or specified copy was not found
148 daemon fork failed
149 master server request failed
150 termination requested by administrator
151 Backup Exec operation failed
152 required value not set
153 server is not the master server
154 storage unit characteristics mismatched to request
155 disk is full
156 snapshot error encountered
157 suspend requested by administrator
158 failed accessing daemon lock file
159 licensed use has been exceeded
160 authentication failed
161 Evaluation software has expired.
162 incorrect server platform for license
163 media block size changed prior resume
164 unable to mount media because it is in a DOWN, or otherwise not available
165 NB image database contains no image fragments for requested backup id/copy number
166 backups are not allowed to span media
167 cannot find requested volume pool in EMM database
168 cannot overwrite media, data on it is protected
169 media id is either expired or will exceed maximum mounts
170 third party copy backup failure
171 media id must be 6 or less characters
172 cannot read media header, may not be NetBackup media or is corrupted
173 cannot read backup header, media may be corrupted
174 media manager - system error occurred
175 not all requested files were restored
176 cannot perform specified media import operation
177 could not deassign media due to Media Manager error
178 media id is not in NetBackup volume pool
179 density is incorrect for the media id
180 tar was successful
181 tar received an invalid argument
182 tar received an invalid file name
183 tar received an invalid archive
184 tar had an unexpected error
185 tar did not find all the files to be restored
186 tar received no data
189 the server is not allowed to write to the client’s file systems
190 found no images or media matching the selection criteria
191 no images were successfully processed
192 VxSS authentication is required but not available
193 VxSS authentication is requested but not allowed
194 the maximum number of jobs per client is set to 0
195 client backup was not attempted
196 client backup was not attempted because backup window closed
197 the specified schedule does not exist in the specified policy
198 no active policies contain schedules of the requested type for this client
199 operation not allowed during this time period
200 scheduler found no backups due to run
201 handshaking failed with server backup restore manager
202 timed out connecting to server backup restore manager
203 server backup restore manager’s network is unreachable
204 connection refused by server backup restore manager
205 cannot connect to server backup restore manager
206 access to server backup restore manager denied
207 error obtaining date of last backup for client
209 error creating or getting message queue
210 error receiving information on message queue
212 error sending information on message queue
213 no storage units available for use
215 failed reading global config database information
216 failed reading retention database information
217 failed reading storage unit database information
218 failed reading policy database information
219 the required storage unit is unavailable
220 database system error
221 continue
222 done
223 an invalid entry was encountered
224 there was a conflicting specification
225 text exceeded allowed length
226 the entity already exists
227 no entity was found
228 unable to process request
229 events out of sequence - image inconsistency
230 the specified policy does not exist in the configuration database
231 schedule windows overlap
232 a protocol error has occurred
233 premature eof encountered
234 communication interrupted
235 inadequate buffer space
236 the specified client does not exist in an active policy within the configuration database
237 the specified schedule does not exist in an active policy in the configuration database
238 the database contains conflicting or erroneous entries
239 the specified client does not exist in the specified policy
240 no schedules of the correct type exist in this policy
241 the specified schedule is the wrong type for this request
242 operation would cause an illegal duplication
243 the client is not in the configuration
245 the specified policy is not of the correct client type
246 no active policies in the configuration database are of the correct client type
247 the specified policy is not active
248 there are no active policies in the configuration database
249 the file list is incomplete
250 the image was not created with TIR information
251 the tir information is zero length
252 An extended error status has been encountered, check detailed status
253 the catalog image .f file has been archived
254 server name not found in the NetBackup configuration
256 logic error encountered
257 failed to get job data
258 Vault duplication was aborted by administrator request
259 vault configuration file not found
260 failed to send signal
261 vault internal error 261
262 vault internal error 262
263 session id assignment failed
265 session id file is empty or corrupt
266 cannot find robot, vault, or profile in the vault configuration
267 cannot find the local host name
268 the vault session directory is either missing or inaccessible
269 no vault session id was found
270 unable to obtain process id, getpid failed
271 vault XML version mismatch
272 execution of a vault notify script failed
273 invalid job id
274 no profile was specified
275 a session is already running for this vault
276 invalid session id
277 unable to print reports
278 unable to collect pre eject information from the API
279 eject process is complete
280 there are no volumes to eject
281 vault core error
282 cannot connect to nbvault server
283 error(s) occurred during vault report generation
284 error(s) occurred during vault report distribution
285 unable to locate vault directory
286 vault internal error
287 vault eject failed
288 vault eject partially succeeded
289 cannot consolidate reports of sessions from container and slot-based vaults
290 one or more errors detected during eject processing
291 number of media has exceeded capacity of MAP; must perform manual eject using vltopmenu or vlteject
292 eject process failed to start
293 eject process has been aborted
294 vault catalog backup failed
295 eject process could not obtain information about the robot
296 process called but nothing to do
297 all volumes are not available to eject
298 the library is not ready to eject volumes
299 there is no available MAP for ejecting
300 vmchange eject verify not responding
301 vmchange api_eject command failed
302 error encountered trying backup of catalog (multiple tape catalog backup)
303 error encountered executing Media Manager command
304 specified profile not found
305 multiple profiles exist
306 vault duplication partially succeeded
307 eject process has already been run for the requested Vault session
308 no images duplicated
309 report requested without eject being run
310 Updating of Media Manager database failed
311 Iron Mountain Report is already created for this session
312 invalid container database entry
313 container does not exist in container database
314 container database truncate operation failed
315 failed appending to container database
316 container_id is not unique in container database
317 container database close operation failed
318 container database lock operation failed
319 container database open operation failed
320 the specified container is not empty
321 container cannot hold any media from the specified robot
322 cannot find vault in vault configuration file
323 cannot find robot in vault configuration file
324 invalid data found in retention map file for duplication
325 unable to find policy/schedule for image using retention mapping
326 specified file contains no valid entry
327 no media ejected for the specified vault session
328 invalid container id
329 invalid recall status
330 invalid database host
331 invalid container description
332 error getting information from EMM database
333 error getting information from media manager command line
334 unable to receive response from robot; robot not ready
335 failure occurred while suspending media for eject
336 failure occurred while updating session information
337 failure occurred while updating the eject.mstr file
338 vault eject timed out
339 vault configuration file format error
340 vault configuration tag not found
341 vault configuration serialization failed
342 cannot modify - stale view
343 robot already exists
344 vault already exists
345 profile already exists
346 duplicate MAP
347 vault configuration cache not initialized
348 specified report does not exist
349 incorrect catalog backup policy
350 incorrect vault catalog backup schedule
351 all configured vault steps failed
400 Server Group Type is Invalid
401 Server Group Already Exists
402 Server Group Already Exists with a different type
403 Server Group Active State is not valid
404 Server Group does not exist
405 Member’s server type not compatible with Server Group
406 The computer specified is not a member of the server group specified
407 Member’s NetBackup version not compatible with Server Group
408 Server Group is in use
409 Member already exists in server group
501 You are not authorized to use this application
502 No authorization entry exists in the auth.conf file for user name
503 Invalid username.
504 Incorrect password
505 Can not connect to the NB-Java authentication service on host on the configured port - (port_number).
506 connect to the NB-Java user service on host on port port_number.
507 Socket connection to the NB-Java user service has been broken
508 Can not write file.
509 Can not execute program
510 File already exists: file_name
511 NB-Java application server interface error
512 Internal error - a bad status packet was returned by NB-Java application server that did not contain an exit status code
513 bpjava-msvc: the client is not compatible with this server version (server_version).
514 NB-Java: bpjava-msvc is not compatible with this application version (application_version).
516 Could not recognize or initialize the requested locale - (locale_NB-Java_was_started_in).
517 Can not connect to the NB-Java user service via VNETD on host on port configured_port_number. If successfully logged in beforehand, retry your last operation. Check the log file for more details.
518 No ports available in range (port_number) through (port_number) per the NBJAVA_CLIENT_PORT_WINDOW configuration option.
519 Invalid NBJAVA_CLIENT_PORT_WINDOW configuration option value: (option_value).
520 Invalid value for NB-Java configuration option (option_name):(option_value).
521 NB-Java Configuration file (file_name) does not exist.
522 NB-Java Configuration file (file_name) is not readable due to the following error: (message).
523 NB-Java application server protocol error.
525 Cannot connect to the NB-Java authentication service via VNETD on (host) on port (vnetd_configured_port_number). Check the log file for more details.
526 bpjava authentication service connection failed
527 bpjava user service connection if connection to pbx on port 1556 fails
600 an exception condition occurred
601 unable to open listen socket
602 cannot set non blocking mode on the listen socket
603 cannot register handler for accepting new connections
604 no target storage unit specified for the new job
605 received error notification for the job
606 no robot on which the media can be read
607 no images were found to synthesize
608 storage unit query failed
609 reader failed
610 end point terminated with an error
611 no connection to reader
612 cannot send extents to bpsynth
613 cannot connect to read media server
614 cannot start reader on the media server
615 internal error 615. This error code is no longer used
616 internal error 616. This error code is no longer used
617 no drives available to start the reader process
618 internal error 618. This error code is no longer used
619 internal error 619. This error code is no longer used
620 internal error 620. This error code is no longer used
621 unable to connect to bpcoord
622 connection to the peer process does not exist
623 execution of a command in a forked process failed
624 unable to send a start command to a reader or a writer process on media server
625 data marshalling error
626 data un-marshalling error
627 unexpected message received from bpsynth
628 insufficient data received
629 no message was received from bptm
630 unexpected message was received from bptm
631 received an error from bptm request to suspend media
632 received an error from bptm request to un-suspend media
633 unable to listen and register service via vnetd
634 no drives available to start the writer process
635 unable to register handle with the reactor
636 read from input socket failed
637 write on output socket failed
638 invalid arguments specified
639 specified policy does not exist
640 specified schedule was not found
641 invalid media type specified in the storage unit
642 duplicate backup images were found
643 unexpected message received from bpcoord
644 extent directive contained an unknown media id. This error code is no longer used
645 unable to start the writer on the media server
646 unable to get the address of the local listen socket
647 validation of synthetic image failed
648 unable to send extent message to BPXM
649 unexpected message received from BPXM
650 unable to send extent message to bpcoord
651 unable to issue the database query for policy
652 unable to issue the database query for policy information
653 unable to send a message to bpccord. This error code is no longer used
654 internal error 654. This error code is no longer used
655 no target storage unit was specified via command line
656 unable to send start synth message to bpcoord. This error code is no longer used.
657 unable to accept connection from the reader
658 unable to accept connection from the writer
659 unable to send a message to the writer child process
660 a synthetic backup request for media resources failed
661 unable to send exit message to the BPXM reader
662 unknown image referenced in the synth context message from BPXM
663 image does not have a fragment map
664 zero extents in the synthetic image, cannot proceed
665 termination requested by bpcoord. This error code is no longer used
667 unable to open pipe between bpsynth and bpcoord. This error code is no longer used
668 pipe fgets call from bpcoord failed. This error code is no longer used
669 bpcoord startup validation failure. This error code is no longer used
670 send buffer is full
671 query for list of component images failed
800 resource request failed
801 JM internal error
802 JM internal protocol error
803 JM terminating
805 Invalid jobid
806 this mpx group is unjoinable
807 not externalized
811 failed to communicate with resource requester
812 failed to communicate with resource broker
813 duplicate reference string specified
818 retention level mismatch
819 unable to communicate with JM proxy
823 no BRMComm to join
830 drive(s) unavailable or down
831 image has been validated
832 failed to write discover data to a file
833 error parsing discovered XML data
900 retry nbrb request later
901 RB internal error
902 RB invalid argument
903 RB communication error
904 RB max reallocation tries exceeded
905 RB media server mismatch
906 RB operator denied mount request
907 RB user cancelled resource request
908 RB was reset
912 RB disk volume mount failed
913
914 RB media reservation not found
915 RB disk volume mount must retry
916 Resource request timed out
917 RB multiplexing group not found
918 RB does not have a multiplexing group that uses this media id or drive name
1000 Client is offline
1001 discovery document error
1002 Discovery detected a failed client
1057 A data corruption has been detected
1058 A data inconsistency has been detected and corrected automatically.
1401 Invalid arguments received
1402 Hold id or Hold name argument is invalid
1403 Backup id argument is invalid
1404 Image copy number argument is invalid
1405 No images are found
1406 Invalid hold type
1407 Invalid hold state
1408 Database error
1409 Unable to connect to database
1410 No data found
1411 Catalog error
1412 Hold record is being updated
1413 Requested hold is not found
1414 Duplicate hold found
1415 Duplicate image found
1416 Partially failed due to duplicate image
1417 Partially failed due to unhold image
1418 Requested image is not found
1419 Partially failed due to invalid image copy
1420 Cannot expire on hold image copy.
1421 Active holds cannot be changed
1422 Cannot deassign media on hold
1423 Unable to retrieve hold status of the image copies
1424 Requested Legal hold is not found
1425 Requested Local hold is not found
1426 Retired holds cannot be changed
1450 CORBA exception received from Indexing service.
1451 Invalid command line option
1452 Backup ID: does not exists
1453 Invalid Operation ID
1454 Invalid Priority
1455 Missing value for option <-option>
1456 Required option is not found
1457 Too many arguments provided
1458 Unable to connect to Indexing Service
1459 Incorrect file path:
1460 No data found in the file
1461 invalid date
1462 End date is before start date
1463 Hours must be greater than or equal to 1
1464 For -force option, operation ID has to be 1
1465 nbindexutil -list option is missing the -indexserver option
1466 Invalid combination of options
1467 Number of files is 0 and hence not submitting the request for backup image
1468 There are no tar copies for snapshot image
1500 Storage unit does not exist or can't be used where specified
1501 Source operation cannot be used where specified
1502 Retention type cannot be used where specified
1503 Volume pool does not exist or can't be used where specified
1504 Server group does not exist or can't be used where specified
1505 alternate read server does not exist or can't be used where specified
1506 data classification does not exist
1508 Storage lifecycle policy exceeds maximum copies
1509 Storage lifecycle policy exceeds maximum backup operations
1510 storage lifecycle policy cannot have more than one snapshot operation
1511 storage lifecycle policy must have at least one fixed retention or snapshot rotation operation
1512 storage lifecycle policy must have at least one backup, import, or snapshot operation
1513 invalid priority
1514 invalid operation type
1515 multiplexing value is not valid or cannot be used where specified
1516 all storage units or groups must be on the same media server
1517 Invalid retention level
1518 backup image is not supported by storage lifecycle policy
1519 Images are in process
1521 Database not available
1522 Error executing database query
1523 Invalid fragment
1524 Duplicate image record
1525 Invalid lsu
1526 Storage lifecycle policy exceeds maximum import operations
1527 storage lifecycle policy can have only one of backup, import, and snapshot operations
1528 The source copy for an Auto Image Replication is not capable of replication
1529 The source copy for Auto Image Replication must specify a storage unit
1530 Only one Auto Image Replication allowed per copy
1531 An import storage lifecycle policy requires one copy with remote retention type
1532 Import failed because the imported image specifies an SLP name which does not exist
1533 Import failed because the imported image data class is different than the SLP data class
1534 Import failed because the imported image specifies an SLP name with no import operation
1535 Import failed because the imported image backup id conflicts with an existing image
1536 The storage unit or storage unit group cannot be deleted because an SLP references it
1537 Backup policy and storage lifecycle policy have conflicting configurations
1538 Data classification in the SLP conflicts with backup policy
1539 Backup policy generates snapshots but storage lifecycle policy does not handle them
1540 SLP expects snapshots but backup policy does not create them with SLP management enabled
1541 Snapshot creation failed
1542 An existing snapshot is no longer valid and cannot be mounted for subsequent operations
1543 Policy type is not compatible with SLP operations
1545 Schedule type is not compatible with SLP operations
1546 Capacity managed retention type is not compatible with SLP operations
1547 Expire after copy retention requires a dependent copy
1548 Retention type is not compatible with snapshot operation
1549 TIR information selection is not compatible with SLP operations
1552 The source and target storage units are not valid replication partners
1553 Checkpoints are not allowed with SLP operations
1554 Storage unit snapshot capability is not compatible with operation characteristics
1556 The SLP deletion failed because a backup policy refers to it.
1557 Must specify mirror retention when target storage unit is mirror capable.
1558 Mirror retention is not allowed when target storage unit is not mirror capable.
1559 SLP referenced in policy or schedule not found
1560 Fixed or rotation retention required without a replication operation
1561 Policy using NDMP conflicts with multiple Backup From Snapshot operations in storage lifecycle policy
1562 Backup schedule generates snapshots but storage lifecycle policy does not handle them
1563 SLP expects snapshots but backup schedule does not create them
1565 Policy snapshot method is not compatible with SLP snapshot operations
1566 Storage unit required for snapshot operation when no other operation present
1567 Only one NDMP backup of a snapshot per backup ID is allowed
1568 Only one IndexFromSnapshot operation is allowed per storage lifecycle policy
1569 Snapshot storage unit is not configured for primary snapshots. It cannot be used in snapshot operation.
1570 Policy type does not support Index from Snapshot
1571 Data mover type specified in policy does not support Index from Snapshot
1572 Storage unit must be specified for this operation
1573 Backup image cannot be expired because its SLP processing is not yet complete
1800 Invalid client list
2000 Unable to allocate new media for backup, storage unit has none available.
2001 No drives are available for this job
2002 Invalid STU identifier type
2003 Drive is not allocated
2004 Drive is already allocated
2005 MDS has received an invalid message from a media server.
2006 NDMP credentials are not defined in EMM
2007 Storage unit is not compatible with requesting job
2008 All compatible drive paths are down
2009 All compatible drive paths are down but media is available
2010 Job type is invalid
2011 The media server reported a system error.
2012 Media has conflicts in EMM
2013 Error record insert failed
2014 Media is not assigned
2015 Media is expired
2016 Media is assigned to another server
2017 Media needs to be unmounted from a drive
2018 Number of cleanings is invalid
2019 Media is in a drive that is not configured on local system
2020 Robotic library is down on server
2021 Allocation record insert failed
2022 Allocation status record insert failed
2023 Allocation identifier is not known to EMM
2024 Allocation request update failed
2025 Allocation request delete failed
2026 Allocation status request delete failed
2027 Media server is not active
2028 Media is reserved
2029 EMM database is inconsistent
2030 Insufficient disk space or high water mark would be exceeded
2031 Media is not defined in EMM
2032 Media is in use according to EMM
2033 Media has been misplaced
2034 Retry the allocation request later
2035 Request needs to pend
2036 Drive is in a robotic library that is up
2037 Drive is not ready
2038 Media loaded in drive is not write-enabled
2039 SCSI reservation conflict detected
2040 Maximum job count has been reached for the storage unit
2041 Storage unit is down
2042 Density mismatch detected
2043 Requested slot is empty
2044 Media is assigned to another application
2045 Storage unit is disabled since max job count is less than 1
2046 Media is unmountable
2047 Media is write protected
2048 Media is in use by the ACS robotic library
2049 Media not found in the ACS robotic library
2050 ACS media has an unreadable external label
2051 ACS media is not in the drive's domain
2052 An ACS Library Storage Module (LSM) is offline
2053 Media is in an inaccessible drive
2054 Media is in a drive that is currently in a DOWN state
2055 ACS physical drive is not available
2056 The file name used for the mount request already exists
2057 The scan host of the drive is not active
2058 LTID needs to be restarted on media servers before the device can be used
2059 The robotic library is not available
2060 Media needs to be rewound or unmounted from a drive
2061 The host is not an active node of a cluster
2062 Throttled job count has been reached for the storage unit
2063 Server is not licensed for the Remote Client Option
2064 Job history indicates that no media is available
2065 Job history indicates that no drive is available
2066 Disk pool not found
2067 Disk volume not found
2068 Disk volume mount point not found
2069 Disk volume mount point record insert failed
2070 The specified mount path will not fit in the allocated space
2071 Unable to find any storage servers for the request
2072 Invalid operation on static mount point
2073 Disk pool is down
2074 Disk volume is down
2075 Fibre Transport resources are not available
2076 DSM returned an unexpected error
2077 DSM has already mounted the volume
2078 The maximum number of mounts for the disk volume have been exceeded
2079 DSM has detected that an invalid file system is mounted on the volume
2080 Disk volume has no max writers count
2081 Disk volume has no max readers count
2082 The drive needs to be marked as available
2083 The media affinity group is not defined in EMM
2084 Media affinity group record insert failed
2085 Disk volume is not available
2086 Disk volume cannot be used for more than one copy in the same job
2087 Media allocation would exceed maximum partially full media limit
2088 Cleaning media is not available
2089 FT client is not running
2090 FT client has no devices configured
2091 FT client devices are offline
2092 FT server devices for client are offline
2093 No FT servers for this client are running
2094 STU cannot run Lifecycle backups
2095 STU cannot run VMWare backup
2096 NDMP operation does not support multiple inline copies
2097 Storage Unit group does not exist in EMM configuration
2098 Media pool is not eligible for this job
2099 Required drive or drive path is not configured
2100 Maximum number of mounts has been exceeded for tape media
2101 Media server not found in EMM database
2102 Storage unit does not support spanning
2103 Media server mismatch
2104 Storage units are not available
2105 Storage unit requested for replication job is not replication capable
2106 Disk storage server is down
2107 Requested media server does not have credentials for storage server
2504 Direct expiration of a mirror copy is not allowed
2800 Standard policy restore error
2801 Oracle policy restore error
2802 Informix-On-BAR policy restore error
2803 Sybase policy restore error
2804 MS-SharePoint policy restore error
2805 MS-Windows policy restore error
2806 NetWare policy restore error
2807 SQL-BackTrack policy restore error
2808 Windows File System policy restore error
2809 MS-SQL-Server policy restore error
2810 MS-Exchange policy restore error
2811 SAP policy restore error
2812 DB2 policy restore error
2813 NDMP policy restore error
2814 FlashBackup policy restore error
2815 AFS policy restore error
2816 DataStore policy restore error
2817 FlashBackup Windows policy restore error
2818 NBU Catalog policy restore error
2819 Enterprise Vault policy restore error
2820 NBU VMware policy restore error
2826 Master server failed to connect to backup restore manager on media server for restore
2828 Restore failed because the MS-SQL-Server services are down
2829 Restore failed due to MS-SQL-Server database in use
2830 Restore failed due to an incorrect path in the MS-SQL-Server MOVE script
2831 Restore error
4200 Operation failed: Unable to acquire snapshot lock
5000 Indexing service internal failure
5001 Unable to connect to Policy Execution Manager
5002 Backup image is already indexed
5003 Invalid arguments received
5004 Invalid backup image ID
5005 Invalid database key
5006 Invalid machine name for indexing server
5007 Invalid indexing server
5008 Unable to get Master Server key
5009 Invalid indexing state
5010 Invalid date range
5011 No images in sequence to process
5012 No such record found
5013 Backup image is not indexed
5014 Failure in getting image header
5015 Indexing is in progress for backup image
5016 Failure in database connection
5017 Database error occurred
5018 Duplicate record found
5019 Data not found
5020 Indexing server value is not set
5021 Unsupported policy type for indexing
5022 Unknown error occurred
5023 Error in querying indexing schedule windows
5024 Unable to connect to Job Manager
5025 indexing failed
5026 Indexing engine initialization failed
5027 Failed to connect to the indexing engine
5028 The backup image did not have any files that can be indexed
5029 Invalid index specified for indexing
5030 Failed to send the index metadata
5031 Index disk is full
5032 Multiple machine name entries for particular host
5033 Failed to suspend indexing server
5034 Failed to resume indexing server-option>

Source: symantec.com
↧

Netbackup Media Manager Status Code

February 2, 2013, 6:21 am
$
0
0
1 request completed
2 system error
3 user id was not superuser
4 invalid command usage
5 daemon resources are busy
6 invalid protocol request
7 daemon terminated
8 invalid media ID
9 invalid media type
10 invalid barcode
11 invalid description
12 invalid robot type
13 invalid robot number
14 invalid robot host
15 invalid volgroup
16 invalid robot coord1
18 cannot allocate requested memory
19 invalid database host
20 protocol error
21 cannot obtain daemon lockfile
22 pool type change is not allowed for pool
23 database server is down
25 failed making the database directory
26 database open operation failed
27 database read record operation failed
28 database read operation read too few bytes
32 database write record operation failed
34 media ID not unique in database
35 volume does not exist in database
36 barcode not unique in database
37 robotic volume position is already in use
39 network protocol error
40 unexpected data received
41 invalid media ID for naming mode
42 cannot connect to robotic software daemon
43 failed sending to robotic software daemon
44 failed receiving from robotic software daemon
45 failed changing terminal characteristics
46 unexpected data from robotic software daemon
47 no entries changed
48 no entries deleted
49 no entries inserted
50 invalid change-entry request
51 cannot auto-eject this robot type
52 cannot auto-inject this robot type
53 invalid volume move mode
54 robot number and robot type mismatch
55 robot number and volume group mismatch
56 invalid database version header
57 error auto-generating volume group
58 daemon cannot obtain socket
59 daemon failed accepting connection
60 cannot perform operation on this host
61 robot number and robot host mismatch
62 failed redirecting input to pipe
63 child process killed by signal
64 no child process to wait for
65 volume group does not exist
67 unable to send exit status
68 too many volumes in volume group
69 failed sending request to vmd
70 cannot connect to vmd [on host host name]
71 failed sending to vmd
72 failed receiving from vmd
73 invalid query type
74 invalid number of cleanings
75 invalid change type
76 cannot get host name
78 barcode does not exist in database
79 specified robot is unknown to vmd
80 cannot update database due to existing errors
81 robot type and volume group mismatch
82 robot host and volume group mismatch
83 device management error
84 this machine is not the database host
85 volume daemon fork failed
86 failed opening tmp output file
87 failed redirecting tmp output file
88 failed initiating child process
89 another daemon already exists
90 invalid volume pool
92 cannot delete assigned volume
93 volume is already assigned
94 volume is not in specified pool
95 media ID is not the specified media type
96 oprd returned abnormal status
97 rule does not exist in rule database
101 media type and volume group mismatch
102 invalid pool database entry
104 failed appending to pool database
105 poolname is not unique in pool database
109 pool does not exist in pool database
110 pool is in use
111 the specified pool is not empty
112 no pools in the pool list
113 invalid expiration date
114 invalid maximum mounts
115 volume has passed expiration date
116 volume has exceeded maximum mounts
117 operation not allowed on cleaning cartridge
118 cannot delete one of the default volume pools
119 invalid rule database entry
121 failed appending to rule database
122 barcode tag is not unique in rule database
126 not authorized to connect to vmd
127 unable to generate a unique media id
129 invalid drive name
130 requested drive is already reserved
131 requested drive is not registered for host
132 requested drive is not currently registered
133 requested drive is not reserved by host
134 requested drive is not currently reserved
135 requested host is not currently registered
136 invalid host name
137 oprd request is not supported on the remote host
138 media generation rule already exists
139 media generation rule does not exist
140 invalid media generation rule
141 invalid number of mounts
142 invalid offsite location
143 invalid offsite sent date
144 invalid offsite return date
145 requested drive is already reserved by host
146 incompatible database version
147 invalid offsite slot
148 invalid offsite session id
149 current version does not support this configuration
150 registering this host would exceed the maximum allowed
152 global device database record not found
153 device entry is not unique in global device database
155 global device database append operation failed
160 the global device database device type is invalid
162 the global device database device name is invalid
163 the operation requested has failed
164 the robotic daemon returned an invalid volume GUID
165 Evaluation period expired. Go to www.symantec.com to order this product
166 media access port not available
167 ADAMM GUID is not unique in the database
168 ADAMM GUID does not exist in database
169 internal database access failure
171 a scratch pool is already defined
172 pool not defined as a scratch pool
173 invalid scratch pool name
175 unable to open the device test state file
176 unable to find any records in the device test database
177 request can only be performed on the Media and Device Management Domain Server
181 not authorized to connect to robotic daemon
182 device test state file does not exist
185 the robotic library is full and may still have media in its map
186 invalid container id
187 VxSS authentication failed
188 VxSS Access Denied
189 failed to initialize a connection to the Enterprise Media Manager
190 the request sent to the Device Allocator has failed
191 invalid EMM argument
192 unknown EMM error code
193 generic EMM SQL error
194 EMM DB record not found
195 CORBA communication error
196 EMM database error
198 pool not defined as a catalog backup pool
199 the media is allocated for use

Source : symantec.com
↧

Device Configuration Status Codes

February 2, 2013, 7:08 am
$
0
0
Device configuration status codes appear in exit status and command output for the tpconfig and the tpautoconf commands, and in system or debug logs. Programs that call tpconfig and tpautoconf, such as media and device management user interfaces and the vmoprcmd command, also present these codes.

0 Success
1 Cannot execute command, permission denied
2 The device_mappings file has invalid license info
3 Could not get hostname
7 Invalid SCSI port number for the robot
8 Invalid SCSI bus number for the robot
9 Invalid SCSI target for the robot
10 Invalid SCSI logical unit number for the robot
11 Invalid Usage
13 Failed reading drive or robot config file
14 Invalid drive index
15 Invalid robot number
16 A SCSI inquiry sent to the device has failed
17 This robot type does not support multiple media types
18 Invalid robot type
19 Invalid device path name
21 Robot number is already in use
22 Device path is already in use
24 Incomplete robot information
25 Robot drive number in use for this robot
27 Invalid drive type for the robot
28 Invalid robot drive number for the robot type
29 Drive index is in use by another drive
30 Robot number is in use by another robot
31 Robot number does not exist
33 Robot type must be controlled locally
34 Drive name is already in use by another drive
35 Drive name does not exist
36
37 Residence is not licensed for shared drive support
38 Current version does not support remote device host
39 Adding this drive would exceed the maximum allowed
40 Adding this device would exceed the maximum allowed
41 Cannot change terminal mode
42 Cannot create miscellaneous working repository
44 Cannot discover devices. See the Troubleshooting Guide for details.
48 RSM is not supported
49 global device database host name is invalid
51 No compatible device is registered at these SCSI coordinates
52 The device name is not valid, no device responded.
53 Shared Storage Option (SSO) is not licensed
55 Invalid NDMP hostname
56 Invalid NDMP username
57 Internal NDMP error
58 NDMP failed to verify host
59 NDMP is not installed on platform
60 Invalid NDMP password
61 NDMP host exists, use change option
62 NDMP host does not exist
63 NDMP request failed
64 Invalid NDMP device
65 NDMP robot exists, use change option
66 NDMP robot does not exist
67 Unable to connect to NDMP host verify hostname
68 Unable to process NDMP message
69 NDMP host not connected
70 Unable to create NDMP session
71 NDMP get_host_info failed
72 NDMP get_server_info failed
73 Unsupported NDMP version
74 NDMP authorization error, verify username/password
75 NDMP config_get_mover_type failed
76 NDMP config_get_connection_type failed
77 Unable to connect to the EMM server
78 The EMM server failed to process the request
79 Unable to allocate memory for this process
81 This is a drive path operation, use the -drpath option
82 Add Drive Name Rule request failed
83 Update Drive Name Rule request failed
84 Delete Drive Name Rule request failed
85 List Drive Name Rule request failed
86 Invalid Drive Name Rule
87 System Error
88 Invalid host
89 Drive name rule has exceeded its maximum length of 48 characters
90 Another device configuration is already in progress
91 The drive serial number already exists in the device database
92 VxSS access denied
93 Database Server is down
95 The specified Disk Array Host is not configured in NetBackup
96 The specified Disk Array Host is not configured in NetBackup
97 No valid license key for Disk Array configuration
98 Open Storage feature is not licensed
99 Credentials already exist
100 NetBackup Snapshot client not licensed
101 authorization error, verify username/password

Source : symantec.com
↧
↧

About Veritas File System (VxFS)

July 18, 2016, 10:40 pm
$
0
0
A file system is simply a method for storing and organizing computer files and the data the contain to make it easy to find and access them. More formally, a file system is a set of abstract data types that are implemented for the storage, hierarchical organization, manipulation, navigation, access, and retrieval of data.

Veritas File System (VxFS) was the first commercial journaling file system. With journaling, metadata changes are first written to a log (or journal) then to disk. Since changes do not need to be written in multiple places, thougput is much faster as the metadata is written asynchronously.

VxFS major components include :

    Loging
    Extent
    File system disk layouts
↧

Changing Media Density

July 18, 2016, 10:44 pm
$
0
0
Sometimes, for special purpose we need to change the media density. Maybe our customer request restore for data that have been backed up, unfortunately our tape drive has upgrade to higher density. Maybe here is one of the way for changing media density to higher one. Here is the case where tape is written by LTO1 tape drive on L700 and will be restored to LTO3 on ACS-SL8500 tape library :
1. Identify the tape that is required for the restoration. This can be obtained from the catalog. To ensure this can be done with bpmedialist command :
2. Eject the tapes from the TLD library (L700).
3. Perform an inventory of the TLD library to change the RobotType to "standalone".

4. Inject the tape into the ACS library.
Note: Some procedure is necessary to inject the tapes into the correct pool and setting the appropriate ownership.
5. After the tapes are injected into the ACS library, perform a robot inventory of the ACS library.
6. After the volume database is updated, the RobotType of the media will change to "ACS" and the tapes should be recognized as "hcart".
7. Run "vmchange -new_mt -m " to change the density. It should be "hcart3" for the LTO Gen-3 drive and refers to the media barcode. An eg would be "vmchange -new_mt hcart3 -m TD2222".
8. Run "vmquery -m " to check that the density have been updated to "hcart3" from "hcart".
9. One media server that holds this tape run "bpmedia -changeden -new -ev"
Note: This command will take some time to complete. Please be patient and let it complete on it's own. If terminated halfway, strange things may occur later.
10. Run "bpmedialist -m " to check that the density have been updated.
11. Run the normal restoration procedure to restore the data from the LTO Gen1 tapes using the ACS library.
12. Once, we have completed the restoration, the tape should be ejected from the ACS library to prevent it from being used for future backups. If necessary, will need to execute the commands in Step 7 and 9 to change the density back to "hcart".



↧

Screenshoot of stopping netbackup service

July 18, 2016, 10:46 pm
$
0
0
Here is the screenshoot of stoping netbackup service using 'bp.kill_all' command and startup these service using 'netbackup start' command.
↧
Search

Workaround to access raw Veritas Volume Manager volumes from Non-global zones

July 19, 2016, 9:33 am
$
0
0
This post is found in https://www.veritas.com/support/en_US/article.000032145, very useful for anyone who mitigate the problem in accessing the raw Veritas Volume Manager from Non-global zones.


Problem
Workaround to access raw Veritas Volume Manager volumes from Non-global zones
Solution
-----------------------------------------------------------------------------------------------------------------------------------------------------------
Important Note about this Workaround: The information in this TechNote does not apply to the Veritas Storage Foundation (SF) 5.0 Maintenance Pack 1 Rolling Patch 5 (MP1 RP5) and 5.0 Maintenance Pack 3 (MP3) releases.  For non-global zone information relevant to the SF 5.0 MP1 RP5 and 5.0 MP3 releases, see the appendix regarding Veritas Storage Foundation support for Solaris Zones in the Veritas Volume Manager 5.0 MP3 Administrator's Guide.
-----------------------------------------------------------------------------------------------------------------------------------------------------------

Non global zone users do not have direct access to raw Veritas Volume Manager (VxVM) volumes even if the zoneadm device property is used to export these volumes to the non global zone.

The workaround below can be used to grant access to VxVM raw volumes from a non global zone.

Warning: If access to a raw volume is granted to a non global zone, you must ensure that the raw volume is used appropriately to prevent the possibility of data corruption or system failure. In particular, pay attention to any file system that is configured on top of a raw volume in a zone. Data corruption can result if you write directly to the raw volume (for example, by using a utility such as dd).  If data corruption occurs in UFS metadata, this can result in a system wide panic. Potentially, a zone administrator in one zone could disrupt all zones.  It is therefore not recommended that UFS file systems be configured on raw volumes. Instead, a Veritas File System file system is recommended, as it is more tolerant of I/O errors on metadata. For more information, see the ioerror section of the mount_vxfs(1M) manual page.

All VxVM configuration changes, including changes to raw volumes, must be performed in the global zone.


Workaround

Warning: Exporting raw devices is a security risk. Customers using this workaround should ensure that the non global zone has permission to access the global raw devices. It is your responsibility to ensure that the proper security is applied for data protection.

To access VxVM volumes in the global zone from a non global zone:

1. If the non global zone does not already exist, create a zone path with appropriate permissions and use the zonecfg command to create the non-global zone

  The following example shows how to use the zonecfg command to create a non global zone named "myzone":

# zonecfg -z myzone

myzone: No such zone configured
Use 'create' to begin configuring a new zone.

# zonecfg:myzone> create
# zonecfg:myzone> set zonepath=/myzone
# zonecfg:myzone> set autoboot=true
# zonecfg:myzone> verify
# zonecfg:myzone> commit
# zonecfg:myzone> exit

2. Install the non global zone and verify that its status is shown as "installed":

# zoneadm list -iv

ID NAME             STATUS         PATH
0  global           running        /
-  myzone           installed      /myzone

3. Boot the non global zone and verify that its status is shown as "running":

# zoneadm -z myzone boot
# zoneadm list -iv

ID NAME             STATUS         PATH
0  global           running        /
1  myzone           running        /myzone

3. Use the ls -l command to find out the major and minor numbers of the raw volume

  In this example, the volume v1 is in the tcrundg disk group within the global zone.  The raw device in the global zone that corresponds to v1 is /dev/vx/rdsk/tcrundg/v1.
  Running the ls -l command on this device shows that the major number is 289, and the minor number is 45000:

# ls -l /dev/vx/rdsk/tcrundg
crw-------   1 root     root     289, 45000 Aug 24 11:13 v1

4. Use the mknod command to create an entry for the VxVM volume in the non global zone.  In this example, the major number is 289 and the minor number is 45000:

# cd /myzone/dev
# mknod v1 c 289 45000

5. Log into the non global zone and check the device entry for the volume:

# zlogin -l root myzone

[Connected to zone 'myzone' pts/6]
Last login: Thu Aug 24 14:31:41 on pts/5
Sun Microsystems Inc.   SunOS 5.10      Generic January 2005

# ls -l /dev/v1
crw-r--r--   1 root     root     289, 45000 Aug 24 16:10 /dev/v1

6. Verify that you can perform I/O with the device entry in the non global zone:


# dd if=/dev/v1 of=/dev/null
2048+0 records in
2048+0 records out

The iostat command can also be used to observe I/O activity in both the global and non global zones.


Source : https://www.veritas.com/support/en_US/article.000032145
↧
↧

Veritas NetBackup 5330 Appliance Introduced

July 19, 2016, 9:43 am
$
0
0
Veritas NetBackup TM  5330 is an integrated media server with storage. It delivers high performance, scalable capacity, and resiliency to address the most aggressive backup and recovery objectives in the data center while protecting both virtual and physical environments. Built on industry leading NetBackup software, the NetBackup 5330 Appliance offers both client and target deduplication to reduce network bandwidth and
storage capacity requirements. With Auto Image Replication (AIR), the NetBackup Appliance may be geographically dispersed to meet today’s ever-demanding DR requirements. As an integrated backup appliance, it addresses the OpEx and CapEx challenges organizations face today while preparing to modernize for the future.


PRODUCT HIGHLIGHTS
• Ideal for enterprise environments
Starting at 114 TB and expandable to 458 TB usable capacity, NetBackup 5330 is designed for larger enterprises and data centers requiring performance, capacity, and resiliency.
• Media server role
Deploy as a media server with storage within your NetBackup domain.
• Fits into existing NetBackup environments
Easily expand or refresh existing NetBackup environments without disrupting operations.
• Optimum virtual machine protection
Built-in support for VMware vSphere™ and Microsoft Hyper-V®, no proxy servers required.
• Improve resource utilization
Decrease backup storageup to 50 times and bandwidth consumption up to 99 percent.
• Flexible deduplication options
Deduplication at source or target; inline or post-process.
• Dynamic storage Usable capacity can be any combination of
458 TB deduplication pool or Advanced Disk pool (non-deduplicated storage)
• Eliminate point products
Reduce the number of 3rd party point products such as target dedupe appliances, tape, or virtual tape libraries (VTL).
• Address capital and operating expenditures
Consolidate existing media servers and target dedupe appliances into an all-in-one appliance; reduce floor space, power and cooling costs.
• Simple NetBackup Software Licensing
Pay once for NetBackup software and freely replicate, change retention policies, and refresh hardware without penalties.
• Heterogeneous cloud gateway
Serves as a gateway unit for sending backups to supported cloud storage vendors.
• Resilient hardware architecture
Dual RAID controllers and
multiple data paths deliver greater data protection and system availability, along with redundant hot swap components.
• Veritas AutoSupport
Monitors key hardware components and notifies the administrator of fault events

Source : www.veritas.com
↧

NetBackup Enterprise Server Edition End of Support Life (EOSL) Information

July 19, 2016, 10:06 am
$
0
0
Here is the list of Netbackup Enterprise Server editon EOSL. What Netbackup version in your environments is? Do you need to upgrade to the latest version? Check it out.

Version End of Support
Life Date		End of Limited Support DateEnd of Life DateRelease Date
7.7.312/1/201812/1/201712/1/20186/6/2016
7.7.212/1/201812/1/201712/1/20182/1/2016
7.7.112/1/201812/1/201712/1/201810/5/2015
7.712/1/201812/1/201712/1/20187/7/2015
7.6.1.22/1/20172/1/20172/1/20176/1/2015
7.6.1.12/1/20172/1/20172/1/20173/2/2015
7.6.12/1/20172/1/20172/1/20171/14/2015
7.6.0.42/1/20172/1/20172/1/201711/10/2014
7.6.0.32/1/20172/1/20172/1/20177/30/2014
7.6.0.22/1/20172/1/20172/1/20175/8/2014
7.5.0.72/1/2017TBDTBD3/5/2012
7.5.0.62/1/2017TBDTBD3/5/2012
7.5.0.52/1/2017TBDTBD3/5/2012
7.5.0.42/1/2017TBDTBD3/5/2012
7.5.0.32/1/2017TBDTBD3/5/2012
7.5.0.12/1/2017TBDTBD3/5/2012
7.52/1/20172/1/20172/1/20173/5/2012
7.12/1/20172/1/20172/1/20173/17/2011
7.0.12/1/20172/1/20172/1/20178/24/2010
72/1/20172/1/20172/1/20172/1/2010
6.5.610/3/20128/1/20122/1/20105/6/2010
6.5.510/3/20128/1/20122/1/201012/2/2009
6.5.410/3/20128/1/20122/1/20106/17/2009
6.5.310/3/20128/1/20122/1/201012/2/2008
6.5.210/3/20128/1/20122/1/20106/9/2008
6.5.110/3/20128/1/20122/1/201012/5/2007
6.0 MP710/3/20128/1/20122/1/20109/23/2008
6.0 MP610/3/20128/1/20122/1/20102/27/2008
6.0 MP510/3/20128/1/20122/1/20108/6/2007
6.0 MP410/3/20128/1/20122/1/201011/20/2006
6.0 MP310/3/20128/1/20122/1/20106/29/2006
6.0 MP210/3/20128/1/20122/1/20103/27/2006
6.0 MP110/3/20128/1/20122/1/201012/22/2005
610/3/20128/1/20122/1/201010/3/2005
5.1 MP76/30/20093/31/200810/3/20054/16/2008
5.1 MP66/30/20093/31/200810/3/200512/4/2006
5.1 MP56/30/20093/31/200810/3/20054/25/2006
5.1 MP46/30/20093/31/200810/3/200511/2/2005
5.1 MP36/30/20093/31/200810/3/20055/3/2005
5.1 MP26/30/20093/31/200810/3/20051/26/2005
5.1 MP16/30/20093/31/200810/3/20059/28/2004
5.16/30/20093/31/200810/3/20056/7/2004
5.0 MP86/30/20093/31/200810/3/20054/16/2008
5.0 MP76/30/20093/31/200810/3/200511/22/2006
5.0 MP66/30/20093/31/200810/3/200511/29/2005
5.0 MP56/30/20093/31/200810/3/20054/12/2005
5.0 MP46/30/20093/31/200810/3/200512/16/2004
5.0 MP36/30/20093/31/200810/3/20058/17/2004
5.0 MP26/30/20093/31/200810/3/20055/28/2004
5.0 MP16/30/20093/31/200810/3/20054/13/2004
56/30/20093/31/200810/3/200512/1/2003
Source : www.veritas.com
↧

Netbackup Version 7.7 New Features

July 20, 2016, 2:05 am
$
0
0
As data protection is going more complex due to massive data production, the Netbackup 7.7 was introduced to overcome these needs. Veritas NetBackupTM 7.7 reduces the staggering complexity of enterprise data protection through comprehensive integration, a converged platform to trivialize infrastructure management, and efficiencies through automation and self-service operation. The Veritas Netbackup 7.7 was introduced on July 07, 2015.

Here are the new feautures of Veritas Netbackup 7.7, taken from www. veritas.com official website :

1. More cloud storage choices
Whether you are exploring public cloud storage services for offsite protection or as an alternative to tape, NetBackup 7.7 introduces a new cloud connector designed around Amazon Simple Storage ServiceTM (Amazon S3) that will enable connections to Amazon Web ServicesTM  (AWS) as well as potentially any Amazon S3-compatible cloud storage service. For the latest list of cloud storage providers certified for use with NetBackup, please see the latest NetBackup Hardware Compatibility List (HCL).

2. Move more data to and from the cloud faster
The new Amazon S3-compatible cloud connector introduced in NetBackup 7.7 is optimized for performance, taking advantage of multistreaming and other techniques to more fully exploit available network bandwidth. While performance results will vary for different environments, internal NetBackup 7.7 testing has shown performance improvements of up to 30 times faster backups and restores when compared to previous NetBackup releases.

3. Backup and recover VMware® vSphere® Virtual VolumesTM (VVOLs)
Introduced in VMware vSphere 6, VVOLs change the storage management paradigm from LUNs to VMs, enabling better performance and greater control at the hypervisor level. NetBackup 7.7 is built to recognize, protect, and recover VMware virtual machines stored on VVOLs, and NetBackup Intelligent Policies have been enhanced to easily automate these operations.

4. Deliver self-service for Microsoft® Hyper-V® and vSphere administrators
For many VM administrators, having visibility and control of backup and recovery is a necessity. With NetBackup 7.7, Hyper-V and vSphere admins can access an interface add-in or plug-in within Microsoft System Center Virtual Machine Manager (SCVMM) and VMware vSphere Web Client that displays backup status and provides self-service recovery facilities, including access to NetBackup Instant Recovery allowing VMware VMs to boot directly from backup disk storage.

5. Simplify and automate Hyper-V and Microsoft SQL Server® protection
With IT environments becoming even more dynamic and elastic, greater automation is needed to help administrators keep up with all the changes. NetBackup 7.7 introduces Intelligent Policies for Microsoft Hyper-V virtual machines (VMs) and Microsoft SQL Server databases, enabling NetBackup to automatically discover and protect new VMs and database instances and more effectively adapt to changing conditions.

6. Protect NetApp cDOT environments—For enterprises using scale-out NAS architectures based on NetApp Clustered Data ONTAP®
 (cDOT), new enhancements have been added in NetBackup 7.7 to support NDMP backups of data on these systems. In addition, in version 7.7 NetBackup Replication Director is able to orchestrate, index, and manage hardware snapshots within cDOT environments (requires the NetApp Plug-in 2.0 for Symantec NetBackup, available from NetApp).

7. Keep up with the latest platforms and workloads
If you’re a fast-moving organization that quickly upgrades to the latest versions of platform technology and infrastructure, keeping up with the latest version of NetBackup is a must. We prioritize support for new operating systems, applications, databases, and other workloads in our latest major software release.

Source : www.veritas.com
↧

NetBackup status code: 11 (System Call Failed)

July 20, 2016, 3:55 am
$
0
0
NetBackup status code: 11
Message: System Call Failed

Explanation: A system call has failed. This status code is used for a generic system call failure that does not have its own status code.

Recommended Action: Do the following, as appropriate:
■ Check the All Log Entries and Problems reports to determine the system call that failed and other information about the error.
■ nbjm and nbproxy return status code 11 when an exception is processed, such as when nbproxy obtains policy or configuration information. Examine the nbjm
unified log (originator ID 117) or the nbproxy legacy log for more detail on the cause of the error.
■ A frequent cause is that the server’s file system is full. For example, you may
see a message similar to the following in the Problems report or bpdbm debug log:
06/27/95 01:04:00 romb romb db_FLISTsend failed: system call
failed (11)
06/27/95 01:04:01 romb romb media manager terminated by parent process
06/27/95 01:05:15 romb romb backup of client romb that exited withstatus 11 (system call failed)
 
On UNIX systems, run a df command on the /usr/openv/netbackup/db directory.
If the df command does not reveal the problem, check the bpdbm debug logs or do a grep for the message 
system call failed 
In relevant files under the directory /usr/openv/netbackup/db/error/ On Windows systems, verify that the disk partition where NetBackup is installed has enough room.

■ Verify that the system is not running out of virtual memory. If virtual memory isthe problem, turn off unused applications or increase the amount of virtual
memory.

To increase virtual memory on Windows, do the following in the order presented:
■ Display the Control Panel.
■ Double-click System.
■ On the Performance tab, set Virtual Memory to a higher value.

■ The following information applies only to UNIX clients:
Check for a semaphore problem. This error may occur because the system does not have enough allocated semaphores. It is most commonly seen on Solaris servers when an RDBMS is also running. The symptoms of the problem vary. In some cases, error messages in the NetBackup log indicate a backup failure due to an error in semaphore operation.
Another symptom is the inability of the NetBackup device manager daemon, ltid, to acquire a needed semaphore. 
System requirements vary; thus, no definite recommendations can be made. One customer running NetBackup and ORACLE on a Solaris server made the following changes to the /etc/system file and then restarted the system (boot -r). The changes were adequate.
set semsys:seminfo_semmni=300
set semsys:seminfo_semmns=300
set semsys:seminfo_semmsl=300
set semsys:seminfo_semmnu=600

Set these attributes to a value great enough to provide resources to all
applications on your system.
NetBackup status codes 50
NetBackup status codes
■ Examine other debug logs or the progress log or status on the client. Examine the nbjm unified log (originator ID 117) for more detail on the cause of the error.
↧
↧

Media Manager status code 1 (Request Completed)

July 20, 2016, 7:32 pm
$
0
0
Media Manager status code 1
Message: request completed
Explanation: A requested operation was completed. The operation may have
been one of several related operations for a particular task.
Recommended Action: None
↧

Media Manager status code 2 (System Error)

July 20, 2016, 7:33 pm
$
0
0
Media Manager status code 2
Message: system error

Explanation: A system call failed. This status code is used for a generic system call failure that does not have its own status code.

Recommended Action:
■ Check for other error messages in the command or the interface output to determine which system call failed.
Check the system application log for error and warning messages.
■ Verify that the system is not running out of virtual memory. If virtual memory is the problem, shut down unused applications or increase the amount of virtual  memory.
To increase virtual memory on Windows, do the following in the order presented:
■ Display the Control Panel.
■ Double-click System.
■ On the Performance tab, set Virtual Memory to a higher value.
■ Verify that all product binaries are properly installed.
■ Verify that no unexpected media and device management processes are in operation by running vmps. Some processes are expected to continue running. Others that continue to run can indicate a more serious problem, such as a hung system call.

Source : www.veritas.com
↧
Search

Media Manager status code 3 (user ID was not superuser)

July 20, 2016, 7:34 pm
$
0
0
Media Manager status code 3
Message: user ID was not superuser

Explanation: A user or process that did not have root privileges (on UNIX and Linux) or administrator privileges (on Windows) started the process.
Recommended Action: If appropriate, give the user or the process administrator privileges (on Windows) or root privileges (on UNIX and Linux) and retry the operation.

Source : www.veritas.com
↧

Media Manager status code 4 (Invalid Command Usage)

July 20, 2016, 7:35 pm
$
0
0
Media Manager status code 4
Message: invalid command usage

Explanation: A media and device management command was run with improper options, or an incompatibility between components or versions of the product exists.

Recommended Action:
■ Examine command output, debug logs, and system logs for a more detailed message on the error.
See "Setting Media Manager debug logging to a higher level" in the NetBackup Logging Reference Guide.
■ Check the usage statement for expected usage and compare with the parameters being sent to start the new process.
■ Verify that all media and device management binaries are at a compatible version level
Source : www.veritas.com
↧
↧

Media Manager status code 5 (Daemon Resources are Busy)

July 20, 2016, 8:46 pm
$
0
0
Message: daemon resources are busy
Explanation: A requested operation cannot be processed because resources were busy.

Recommended Action: Check the status of any resources that the requested operation uses. On a robotic inventory request, verify that the inventory operation completes within a reasonable time.
↧

Media Manager status code 6 (Invalid Protocol Request)

July 20, 2016, 8:47 pm
$
0
0
Media Manager status code 6
Message: invalid protocol request
Explanation: An invalid request was sent to a robotic process or operator request process.

Recommended Action:
■ Examine command output, debug logs, and system logs for a more detailed message on the error.
See "Setting Media Manager debug logging to a higher level" in the NetBackup Logging Reference Guide.
■ Identify the target components (for example, vmd, nbemm, and robotic processes on local or remote hosts). Then verify that all media and device management binaries are at compatible version level.

Source : www.veritas.com
↧

Media Manager status code 7 (Daemon Terminated)

July 20, 2016, 8:49 pm
$
0
0
Media Manager status code 7
Message: daemon terminated
Explanation: The process is inactive or terminates (or has terminated) from the following: an event or signal or as a direct result of a request from an authorized user or process.

Recommended Action: If the targeted product component is needed but has terminated, restart the daemons or services on the targeted host.

Source : www.veritas.com







↧
Viewing all 107 articles
Browse latest View live
Search