Symantec NetBackup status code 346 to status code 350

SQLServerF1

Symantec NetBackup product is a backup and recovery product designed for enterprise users. Symantec NetBackup tool can be used to perform backups of SQL Server databases and provides various features.

Below are some of the NetBackup status error codes from Status Code 346 to Status Code 350 which may be received while using the Symantec NetBackup tool.

NetBackup status code: 346
Message: duplicate MAP
Explanation: A duplicate MAP was added in the Vault configuration file. It is an
internal error.
Recommended Action: Contact customer support and send appropriate logs.

NetBackup status code: 347
Message: vault configuration cache not initialized
Explanation: This error should never occur.
Recommended Action: Contact customer support and send appropriate logs.

NetBackup status code: 348
Message: specified report does not exist
Explanation: Aninvalid Vault report was requested for generation. It is an internal
error.
Recommended Action: Contact customer support and send appropriate logs.

NetBackup status code: 349
Message: incorrect catalog backup policy
Explanation: This error can occur when a Vault session tries to run a catalog
backup. The specified policy for the catalog backup in the Vault profile is either
blank or is not of type NBU-Catalog.
Recommended Action: Verify that you specified a catalog backup policy for the
catalog backup in the Vault profile and that the policy is of type NBU-Catalog.

NetBackup status code: 350
Message: incorrect vault catalog backup schedule
Explanation: This error can occur when a Vault session tries to run a catalog
backup. The specified Vault catalog backup schedule for catalog backup in the
Vault profile is either blank or is not of type Vault Catalog Backup.
RecommendedAction: Verify that you specified a Vault Catalog Backup schedule
for the catalog backup in the Vault profile. Also verify that the schedule is of type
Vault Catalog Backup.

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup status codes, SQL Server Frequently asked questions, SQL Server Trainings.

 

Symantec NetBackup status code 341 to status code 345

SQLServerF1

Symantec NetBackup product is a backup and recovery product designed for enterprise users. Symantec NetBackup tool can be used to perform backups of SQL Server databases and provides various features.

Below are some of the NetBackup status error codes from Status Code 341 to Status Code 345 which may be received while using the Symantec NetBackup tool.

NetBackup status code: 341
Message: vault configuration serialization failed
Explanation: Vault failed to write out the Vault configuration file. It is an internal
error. Note that the Vault configuration file is located at
install_path/netbackup/db/vault/vault.xml.
Recommended Action: Contact customer support and send appropriate logs.

NetBackup status code: 342
Message: cannot modify – stale view
Explanation: This error can occur if an administration interface (NetBackup
Administration Console or Vault Administration menu user interface) tries to
modify the following:
¦ A robot or vault or profile in between the read
¦ Operations of the same robot or vault
¦ Profile by another instance of an administration interface
RecommendedAction: Check the latest attributes of the robot or vault or profile.
To check, refresh the view in the NetBackupAdministration Console or retrieve
the attributes in the VaultAdministration menu user interface again. Then retry
the operation.

NetBackup status code: 343
Message: robot already exists
Explanation: This error can occur during addition of a robot while a robot with
the same name already exists.
Recommended Action: Refresh the view in the NetBackup Administration
Console or retrieve the attributes in the VaultAdministrationmenuuser interface
again to see the robot.

NetBackup status code: 344
Message: vault already exists
Explanation: This error can occur during addition of a vault if a vault with the
same name already exists in the same robot.
Recommended Action: Choose a different name for the vault.

NetBackup status code: 345
Message: profile already exists
Explanation: This error can occur during addition of a profile if a profile with
the same name already exists within the same vault.
Recommended Action: Choose a different name for the profile.

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup status codes, SQL Server Frequently asked questions, SQL Server Trainings.

 

Symantec NetBackup status code 336 to status code 340

SQLServerF1

Symantec NetBackup product is a backup and recovery product designed for enterprise users. Symantec NetBackup tool can be used to perform backups of SQL Server databases and provides various features.

Below are some of the NetBackup status error codes from Status Code 336 to Status Code 340 which may be received while using the Symantec NetBackup tool.

NetBackup status code: 336
Message: failure occurred while updating session information
Explanation: Vault cannot update the session files. It is an internal error.
Recommended Action: Contact customer support and send appropriate logs.

NetBackup status code: 337
Message: failure occurred while updating the eject.mstr file
Explanation: Vault cannot update the eject list file. It is an internal error.
Recommended Action: Contact customer support and send appropriate logs.

NetBackup status code: 338
Message: vault eject timed out
Explanation: This error occurs when a problem exists with the robot.
Recommended Action: Do the following, as appropriate:
¦ Remove the media from the MAP if it is already full.
¦ Make sure that the MAP is closed properly.

NetBackup status code: 339
Message: vault configuration file format error
Explanation: The Vault configuration file is malformed. Unless the file has been
manually modified, this error is internal. Note that the Vault configuration file
is located at install_path/netbackup/db/vault/vault.xml.
Recommended Action: Contact customer support and send appropriate logs.

NetBackup status code: 340
Message: vault configuration tag not found
Explanation: An optional attribute may not appear in the Vault configuration
file. This internal error generally does not cause problems in Vault’s operation.
Note that the Vault configuration file is located at
install_path/netbackup/db/vault/vault.xml.
RecommendedAction: If Vault’s operation is affected, contact customer support
and send appropriate logs.

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup status codes, SQL Server Frequently asked questions, SQL Server Trainings.

 

Symantec NetBackup status code 331 to status code 335

SQLServerF1

Symantec NetBackup product is a backup and recovery product designed for enterprise users. Symantec NetBackup tool can be used to perform backups of SQL Server databases and provides various features.

Below are some of the NetBackup status error codes from Status Code 331 to Status Code 335 which may be received while using the Symantec NetBackup tool.

NetBackup status code: 331
Message: invalid container description
Explanation: This error occurs while adding a container record to the container
database. The container description is found invalid. Note that the container
database exists in file cntrDB, which is located at
install_path/netbackup/vault/sessions/cntrDB.
RecommendedAction: Verify that the string size of the container description is
a maximum of 25 characters long.

NetBackup status code: 332
Message: error getting information from EMM database
Explanation: This error can occur while the backup process communicates with
the EMM database to retrieve some information.
Recommended Action: Do the following, as appropriate:
¦ On UNIX and Linux, verify that the NetBackup Volume Manager (vmd) is
running. On Windows, verify that the NetBackup Volume Manager service is
running.
¦ See the process-specific error log directory for more details.
UNIX and Linux: /usr/openv/netbackup/logs/process_name
Windows: install_path\NetBackup\logs\process_name
For example, if you get this error while running a Vault command (such as
vltcontainers or vltopmenu), look at the following logs to learn why:
/usr/openv/netbackup/logs/vault

NetBackup status code: 333
Message: error getting information from media manager command line
Explanation: This error occurs when Vault cannot retrieve robot information
such as map information, volume information, library status, and so on. It is an
internal error.
Recommended Action: Contact customer support and send appropriate logs.

NetBackup status code: 334
Message: unable to receive response from robot; robot not ready
Explanation: This error occurs when a problem exists with the robot.
Recommended Action: Ensure that all Media and Device Management daemons
are running or the robot is live and up.

NetBackup status code: 335
Message: failure occurred while suspending media for eject
Explanation: This error occurs when Vault cannot suspend the media. It is an
internal error.
Recommended Action: Contact customer support and send appropriate logs.

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup status codes, SQL Server Frequently asked questions, SQL Server Trainings.

 

Symantec NetBackup status code 326 to status code 330

SQLServerF1

Symantec NetBackup product is a backup and recovery product designed for enterprise users. Symantec NetBackup tool can be used to perform backups of SQL Server databases and provides various features.

Below are some of the NetBackup status error codes from Status Code 326 to Status Code 330 which may be received while using the Symantec NetBackup tool.

NetBackup status code: 326
Message: specified file contains no valid entry
Explanation: The specified file contains no valid entries for media IDs or the
alphanumeric equivalent of bar codes. As per the expected format, each line should
contain only one string that represents either a media ID or the bar code numeric
equivalent.
RecommendedAction: Verify that each entry in the specified file does not exceed
the string size limit: six characters for media IDs and 16 characters for the numeric
equivalent of bar codes. Correct the invalid entries in the specified file and try
the same operation again. Read the relevant log file under the directory
install_path/netbackup/logs/vault for more details. Be aware that if this
directory does not already exist, a log file is not created.

NetBackup status code: 327
Message: no media ejected for the specified vault session
Explanation: This error occurs while moving media ejected by the specified Vault
session to a container. Either the specified Vault session has not ejected any media,
or you specified an incorrect Vault name or session ID.
Recommended Action: Verify that you have specified the correct combination
of Vault name and session ID. Verify that the specified Vault session has ejected
at least one piece of media. Read the relevant log file under the directory
netbackup/logs/vault for more details. Be aware that if this directory does not
already exist, a log file is not created.

NetBackup status code: 328
Message: invalid container id
Explanation: This error occurs while adding a container record to the container
database. The container ID is found invalid. Note that the container database
exists in file cntrDB, which is located at
install_path/netbackup/vault/sessions/cntrDB.
Recommended Action: Verify that the container ID does not contain any space
characters, and that the string size is a maximum of 29 characters long.

NetBackup status code: 329
Message: invalid recall status
Explanation: This error occurs while adding a container record to the container
database. The container recall status is found invalid. Note that the container
database exists in file cntrDB, which is located at
install_path/netbackup/vault/sessions/cntrDB.
Recommended Action: Verify that the recall status is either 1 or 0.

NetBackup status code: 330
Message: invalid database host
Explanation: This error occurs while adding a container record to the container
database. The EMM database host name is found invalid. Note that the container
database exists in file cntrDB, which is located at
install_path/netbackup/vault/sessions/cntrDB.
RecommendedAction: Verify that theEMMdatabase host name does not contain
any space characters, and that the string size is a maximum of 256 characters
long.

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup status codes, SQL Server Frequently asked questions, SQL Server Trainings.

 

Symantec NetBackup status code 321 to status code 325

SQLServerF1

Symantec NetBackup product is a backup and recovery product designed for enterprise users. Symantec NetBackup tool can be used to perform backups of SQL Server databases and provides various features.

Below are some of the NetBackup status error codes from Status Code 321 to Status Code 325 which may be received while using the Symantec NetBackup tool.

NetBackup status code: 321
Message: container cannot hold any media from the specified robot
Explanation: This error occurs while trying to place media from an unexpected
EMM database host into a container. All the media that are placed in a container
should belong to the sameEMMdatabase host. For example, you have media from
a robot that belongs to one EMM database host. Then you try to put this media
into a container that already holds media from the robots that belong to a different
EMM database host.
Recommended Action: Verify that you specified the correct container ID and
media IDs. Read the relevant log file under the directory
install_path/netbackup/logs/vault for more details. Be aware that if this
directory does not already exist, a log file is not created.

NetBackup status code: 322
Message: cannot find vault in vault configuration file
Explanation: NetBackup Vault cannot find an entry for the specified Vault name
into the Vault configuration file. Note that the Vault configuration file is located
at install_path/netbackup/db/vault/vault.xml.

Recommended Action: Verify that you specified the correct Vault name. Read

the relevant log file under the directory netbackup/logs/vault for more details.
Be aware that if this directory does not already exist, a log file is not created.

NetBackup status code: 323
Message: cannot find robot in vault configuration file
Explanation: NetBackup Vault cannot find an entry for the specified robot number
in the Vault configuration file. Note that the Vault configuration file is located at
install_path/netbackup/db/vault/vault.xml.
RecommendedAction: Verify that you specified the correct robot number. Read
the relevant log file under the directory netbackup/logs/vault for more details.
Be aware that if this directory does not already exist, a log file is not created.

NetBackup status code: 324
Message: invalid data found in retention map file for duplication
Explanation: This error occurs when the retention mapping file (either generic
or for a specific vault) contains invalid data. If the file contains too much or too
little data or the user defines invalid retention levels in the file, this error occurs.
The retention mapping file is used as follows: in a Vault session when a Vault
profile duplication is configured with the Use mappings retention level configured
for one of the copies for duplication. The product installs a mapping file template
named retention_mappings in install_path/netbackup/db/vault.
To specify a mappings file for any single vault, copy the retention_mappings
template to another file and append the name of the vault. For example,
netbackup/db/vault/retention_mappings.V1
Recommended Action: Check the entries in the retention_mappings file.

NetBackup status code: 325
Message: unable to find policy/schedule for image using retention mapping
Explanation: This error occurs with duplication of the backup policy or the
schedule of an image by Vault. The Use mappings option on the Duplication tab
of the Profile dialog box is selected, but the policy or the schedule no longer exists.
Recommended Action: Verify whether or not the backup policy or the schedule
that created the image still exists. If either one or both do not exist, the image is
not duplicated through the Vault profile.

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup status codes, SQL Server Frequently asked questions, SQL Server Trainings.

 

Symantec NetBackup status code 316 to status code 320

SQLServerF1

Symantec NetBackup product is a backup and recovery product designed for enterprise users. Symantec NetBackup tool can be used to perform backups of SQL Server databases and provides various features.

Below are some of the NetBackup status error codes from Status Code 316 to Status Code 320 which may be received while using the Symantec NetBackup tool.

NetBackup status code: 316
Message: container_id is not unique in container database
Explanation: NetBackup Vault has found a previously-existing entry for this
container ID in the container database while adding it to the container database.
Each container record in the container database must have a unique container
ID. Note that the container database exists in file cntrDB, which is located at
install_path/netbackup/vault/sessions/cntrDB.
Recommended Action: Verify that you have specified the correct container ID.

NetBackup status code: 317
Message: container database close operation failed
Explanation: This error occurs while closing the container database. This error
may occur during the reading, addition, modification, or deletion of an entry from
the container database. Note that the container database exists in file cntrDB,
which is located at install_path/netbackup/vault/sessions/cntrDB.
Recommended Action: Read the relevant log file under the directory
netbackup/logs/vault for more details. Be aware that if this directory does not
already exist, a log file is not created.

NetBackup status code: 318
Message: container database lock operation failed
Explanation: This error occurs while locking the container database. This error
may occur during the addition, modification, or deletion of an entry from the
container database. Note that the container database exists in file cntrDB, which
is located at install_path/netbackup/vault/sessions/cntrDB.
Recommended Action: Read the relevant log file under the directory
netbackup/logs/vault for more details. Be aware that if this directory does not
already exist, a log file not created.
If some other Vault operation uses the container database and locks it, wait until
that operation completes and the container database is unlocked.

NetBackup status code: 319
Message: container database open operation failed
Explanation: This error occurs while opening the container database. This error
may occur during the reading, addition, modification, or deletion of an entry from
the container database. Note that the container database exists in file cntrDB,
which is located at install_path/netbackup/vault/sessions/cntrDB.
Recommended Action: Read the relevant log file under the directory
netbackup/logs/vault for more details. Be aware that if this directory does not
already exist, a log file is not created.

NetBackup status code: 320
Message: the specified container is not empty
Explanation: This error occurs if you try to delete a container from the container
database, but the container still holds media. You can only delete empty containers.
Recommended Action: Verify that you have specified the correct container ID.
If you still want to delete this container from the container database, first empty
it by doing either of the following:
¦ Inject all the media it contains into a robot
¦ Clear the Vault container ID fields for these media from the EMM database by
using vmchange -vltcid with a value of – .
Try to delete the container again.

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup status codes, SQL Server Frequently asked questions, SQL Server Trainings.

 

Symantec NetBackup status code 311 to status code 315

SQLServerF1

Symantec NetBackup product is a backup and recovery product designed for enterprise users. Symantec NetBackup tool can be used to perform backups of SQL Server databases and provides various features.

Below are some of the NetBackup status error codes from Status Code 311 to Status Code 315 which may be received while using the Symantec NetBackup tool.

NetBackup status code: 311
Message: Iron Mountain Report is already created for this session
Explanation: This error occurs when an Iron Mountain report has already been
generated for the session.
Recommended Action: None. This report cannot be generated again.

NetBackup status code: 312
Message: invalid container database entry
Explanation: NetBackup Vault has found an invalid entry while reading the
container database. Each container entry in the container database must follow
the expected format. The container database exists in file cntrDB, which is located
at install_path/netbackup/vault/sessions/cntrDB.
RecommendedAction: To get the line number of an invalid record in the container
database, read the log file under the directory netbackup/logs/vault. Be aware
that a Vault log may not exist unless the directory netbackup/logs/vault existed
before the error occurred. Open the container database file cntrDB and correct
that invalid entry. Note that this error occurs every time Vault reads this entry
in cntrDB until either this invalid entry is deleted or it is corrected.

NetBackup status code: 313
Message: container does not exist in container database
Explanation: The specified container does not have an entry in the container
database. The container database exists in file cntrDB, which is located at
install_path/netbackup/vault/sessions/cntrDB.
Recommended Action: Verify that you put some media into this container by
using the vltcontainers command. Verify that you did not delete it by using the
vltcontainers -delete command.

NetBackup status code: 314
Message: container database truncate operation failed
Explanation: An error occurs while truncating the container database. This error
may occur during the modification or deletion of an entry from the container
database. The container database exists in file cntrDB, which is located at
install_path/netbackup/vault/sessions/cntrDB.
RecommendedAction: See the log file under the directory netbackup/logs/vault
for more details. Be aware that a log file is not created unless the
netbackup/logs/vault directory has already been created.

NetBackup status code: 315
Message: failed appending to container database
Explanation: This error can occur while appending a container record to the
container database. This error may occur with the addition, modification, or
deletion of an entry from the container database. The container database exists
in file cntrDB, which is located at
install_path/netbackup/vault/sessions/cntrDB.
Recommended Action: Read the relevant log file under the directory
install_path/netbackup/logs/vault for more details. Be aware that if this
directory does not already exist, a log file is not created.

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup status codes, SQL Server Frequently asked questions, SQL Server Trainings.

 

Symantec NetBackup status code 306 to status code 310

SQLServerF1

Symantec NetBackup product is a backup and recovery product designed for enterprise users. Symantec NetBackup tool can be used to perform backups of SQL Server databases and provides various features.

Below are some of the NetBackup status error codes from Status Code 306 to Status Code 310 which may be received while using the Symantec NetBackup tool.

NetBackup status code: 306
Message: vault duplication partially succeeded
Explanation: This error occurs when all selected images are not duplicated
successfully.
Recommended Action: Check the Vault and induplicate logs for cause of the
failure.

NetBackup status code: 307
Message: eject process has already been run for the requested Vault session
Explanation: This error occurs when vlteject is run to eject media for a session
ID for which media has already been ejected.
Recommended Action: Rerun vlteject for another session ID for which media
has not been ejected.

NetBackup status code: 308
Message: no images duplicated
Explanation: This error occurs when Vault failed to duplicate any images.
Recommended Action: For more information, review the Vault debug log in the
following directory:
UNIX and Linux: /usr/openv/netbackup/logs/vault
Windows: install_path\NetBackup\logs\vault
Also review the summary.log in each of the sidxxx directories that had problems:
UNIXand Linux: /usr/openv/netbackup/vault/sessions/<vault_name/>sidxxx
Windows: install_path\NetBackup\vault\sessions\vault_name\sidxxx
(where vault_name is the name of the vault, and xxx is the session ID)
Look for the log entry that gives the total number of images processed.Acommon
cause of failure is a lack of resources, such as no more media available in the
specified pools for duplication. Correct the problem and rerun the Vault job. Note
that the NetBackup scheduler retries a Vault job that terminates with this error.
Review the admin debug log for induplicate entries and the bptm debug log.

NetBackup status code: 309
Message: report requested without eject being run
Explanation: This error occurs when a report is run that requires media to have
been ejected first.
Recommended Action: Perform one of these actions:
¦ Rerun vlteject or vltopmenu to eject the media for the session before you
generate the reports.
¦ Reconfigure the profile to allow the eject step to be performed when the next
Vault session for this profile runs.
¦ Disable the report generation in the profile for the reports that require media
to be ejected.

NetBackup status code: 310
Message: Updating of Media Manager database failed
Explanation: This error occurs when Vault physically ejects tapes but fails to
update the EMM database to reflect the eject operation. A typical reason for this
failure is that EMM detected a mismatch between the media type and its volume
group.
RecommendedAction: To find the root cause of the error, review the Vault debug
logs in the following directory:
UNIX and Linux: /usr/openv/netbackup/logs/vault
Windows: install_path\NetBackup\logs\vault
To fix the issue may involve making configuration changes.

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup status codes, SQL Server Frequently asked questions, SQL Server Trainings.

 

Symantec NetBackup status code 301 to status code 305

SQLServerF1

Symantec NetBackup product is a backup and recovery product designed for enterprise users. Symantec NetBackup tool can be used to perform backups of SQL Server databases and provides various features.

Below are some of the NetBackup status error codes from Status Code 301 to Status Code 305 which may be received while using the Symantec NetBackup tool.

NetBackup status code: 301
Message: vmchange api_eject command failed
Explanation: During the eject process, the vmchange command is called with an
-api_eject call to begin the process to eject media. This command call failed.
RecommendedAction: Review the Vault debug log in the following directory for
detailed information about why the process failed:
UNIX and Linux: /usr/openv/netbackup/logs/vault
Windows: install_path\NetBackup\logs\vault
Also review the summary.log in each of the sidxxx directories that had problems:
UNIX and Linux: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx
Windows: install_path\NetBackup\vault\sessions\vault_name\sidxxx
(where xxx is the session ID)
When the problem is resolved, rerun the Vault session, vlteject command, or
vltopmenu command.

NetBackup status code: 302
Message: error encountered trying backup of catalog (multiple tape catalog
backup)
Explanation: This error occurs when the NetBackup command that was used for
stage one of the two-stage catalog backup fails.
Recommended Action: For the actual error that caused the failure, review the
Vault debug log in the following directory:
UNIX and Linux: /usr/openv/netbackup/logs/vault
Windows: install_path\NetBackup\logs\vault
Review the summary.log in each of the sidxxx directories that had problems:
UNIX and Linux: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx
Windows: install_path\NetBackup\vault\sessions\vault_name\sidxxx
(where xxx is the session ID)
In addition, review the admin debug log in the following directory:
UNIX and Linux: /usr/openv/netbackup/logs/admin
Windows: install_path\NetBackup\logs\admin
Correct the error and rerun the Vault session.

NetBackup status code: 303
Message: error encountered executing Media Manager command
Explanation: This error occurs when a Media and Device Management command
fails during a Vault job.
Recommended Action: For the actual error that caused the command to fail,
review the Vault debug log in the following directory:
UNIX and Linux: /usr/openv/netbackup/logs/vault
Windows: install_path\NetBackup\logs\vault
Also review the summary.log in each of the sidxxx directories that had problems:
UNIX and Linux: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx
Windows: install_path\NetBackup\vault\sessions\vault_name\sidxxx
(where xxx is the session ID)
Try running the command (with the same arguments as in the log file) to see the
actual error. Ensure that the Media and Device Management daemons are running.
Also ensure that the robot is functional and you can communicate with it (for
example, inventory the robot through the GUI).

NetBackup status code: 304
Message: specified profile not found
Explanation: This error occurs when the profile name that is specified on the
Vault command is not defined in the Vault configuration.
Recommended Action: Rerun the Vault command with a profile name that is
defined in the Vault configuration.

NetBackup status code: 305
Message: multiple profiles exist
Explanation: This error may occur when duplicate profile names are defined in
multiple Vault configurations and only the profile name is specified on the Vault
command.
Recommended Action: Rerun the Vault command with the triplet
robot_name/vault_name/profile_name. The triplet uniquely identifies the profile
in your Vault configuration.

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup status codes, SQL Server Frequently asked questions, SQL Server Trainings.

 
1 2 3 13