nbdeployutil

nbdeployutil

deployment utility that gathers and analyzes master server information regarding clients and capacity

/usr/openv/netbackup/bin/admincmd/nbdeployutil --gather

/usr/openv/netbackup/bin/admincmd/nbdeployutil --report --capacity "/path/path1/tarih_saat_mastersername"

# nbdeployutil.exe --gather --output pickedclient --start "11/01/10 
06:00:00" --end "11/02/10 01:00:00" --clients marybl2g1,marybl7g1  /
--verbose NetBackup Deployment Utility, version 7.1.0000.0000
Gathering license deployment information...
run: bpgetconfig
  Discovered master server marybl2g1
run: bpimagelist -M marybl2g1 -d "11/01/10 06:00:00" -e "11/02/10 
01:00:00" -l -client marybl2g1
run: bpimagelist -M marybl2g1 -d "11/01/10 06:00:00" -e "11/02/10 
01:00:00" -l -client marybl7g1
  Output for marybl2g1 at: pickedclient\20101102_155246_marybl2g1
Gather DONE
Execution time: 4 secs
To create a report for this master server, run the following:
  nbdeployutil.exe --report "pickedclient\20101102_155246_marybl2g1"

D:\># nbdeployutil.exe --report --capacity pickedclient\
20101102_154010_marybl2g1 --start "11/01/10 06:00:00" 
--end "11/02/10 01:00:00" --clients marybl2g1,
marybl7g1 --verbose
NetBackup Deployment Utility, version 7.1.0000.0000
Analyzing license deployment ...
  Master marybl2g1
  Report created at: pickedclient\20101102_154010_marybl2g1\
  report-20101102_155414.xls
Analysis DONE
Execution time: 2 secs

https://www.veritas.com/support/en_US/article.000110120

MS-SQL / Commands

SELECT * FROM  sys.sysprocesses order by hostname;

SELECT * FROM  sys.sysprocesses order by loginame;

Restore sonrası kullancı açılması ile db üzerined çalıştırılacak komut:

sp_change_users_login 'AUTO_FIX', 'user_name'

SQL DB OFFLINE FORCE:

USE master

GO

ALTER DATABASE DB_NAME

SET Offline WITH ROLLBACK IMMEDIATE

GO

MS-SQL / delete tempdb file

USE tempdb
GO
DBCC SHRINKFILE (tempdb4, EMPTYFILE);
GO


USE tempdb;
GO
DBCC SHRINKFILE('tempdb4', EMPTYFILE)
GO
USE master;
GO
ALTER DATABASE tempdb
REMOVE FILE tempdb4;

the specified client does not exist in the specified policy(239) / SAP BAckup

the specified client does not exist in the specified policy(239)

Sunucu üzerinde oracle\SID\dbversion\database\initSID.utl dosyası düzenlendi

Dosya içerisindeki Client SERVERNAME değerini politikada yazan ile değiştirildi

Project Server 2013 / Daily Schedule Backup

Daily Schedule Backup
(Project Server 2013)

This article describes how to use the Daily Schedule Backup settings page to select the Project Server 2013 objects that you would like to schedule for back up on a daily basis. This procedure does not back up the physical files of a database (.mdb), but creates backups of specific items in the database. These items are backed up from the Published section to the Archive section in the Project Web App database.

In order to access and use settings on the Daily Schedule Backup page, you must be a farm administrator.

Items you can schedule for backup

You can enable daily backup on the Daily Schedule Backup page for the following Project Server 2013 items:

 

Item	Description
Project	Includes project resources, assignments, tasks, custom field values, baseline data
Enterprise resource pool and calendars	Includes enterprise resources and enterprise calendars
Enterprise custom field	Includes enterprise custom field metadata, enterprise lookup table metadata, enterprise lookup table values
Enterprise global template	Includes all Project Professional table, macro, and view definitions
View definition	Includes statusing, Project Center, Portfolio Analyzer, and Resource Center view definitions
Category and group settings	Includes settings for all Project Server categories and groups.

Important:
Item-level backup and restore of category and group settings apply only in Project Permission Mode. For more information about security modes in Project Server 2013, see Plan user access in Project Server 2013.

To back up data automatically by using a daily schedule

1. In SharePoint Central Administration, click Application Management.
2. On the Application Management page, in the Service Application section, click Manage Service Applications.
3. On the Service Applications page, click the Project Application Service that contains the Project Web App instance for which you want to access the Administrative Backup settings.
4. On the Manage Project Web Apps page, click the drop-down menu for the PWA instance for which you want to access the Daily Schedule Backup settings, and click Manage.
5. On the Project Web App Server Settings page, in the Queue and Database Administration section, click Daily Schedule Backup.
6. On the Daily Backup Schedule page, in the Project Retention Policy box, type the number of versions you want to retain for projects that you back up.

   Note:
   The Project Retention Policy only pertains to projects and not to other enterprise objects. Also note that increasing this setting affects the Archive table in the Project Server 2013 database (ProjectService). The more versions you keep, the more space is required.

7. For each item in the Item section, select either Schedule or Never from the Option list to indicate whether you want to schedule a backup for that item.
8. Click Save.

By default, all items you selected on the Daily Backup Schedule page are backed daily, at a time between 12 AM and 3 AM.

As noted in the procedure, the number of versions that are backed up for projects depend on the value you set for the Project Retention Policy. All other items are only backed up to the previous version.

https://technet.microsoft.com/en-us/library/jj590896(v=office.15).aspx?tduid=(461cf739fa0e0ce4a9effcd396ccb46c)(256380)(2459594)(TnL5HPStwNw-lJGwcWCYbnMSk0SqDC7.Og)()

Project Server 2013 / Administrative Backup

Back up item-level objects through Administrative Backup (Project Server 2013)

This article describes how to back up specific project items in Project Web App. This procedure does not back up the physical files of a database (.mdb), but creates backups of specific items in the database. These items are backed up from the Published section to the Archive section in the Project Web App database.

In order to perform these procedures, you must be a farm administrator.

Backing up item-level objects

You can use the procedures in this article to back up the following project items:

 

Item	Description
Project	Includes project resources, assignments, tasks, custom field values, baseline data
Enterprise resource pool and calendars	Includes enterprise resources and enterprise calendars
Enterprise custom field	Includes enterprise custom field metadata, enterprise lookup table metadata, enterprise lookup table values
Enterprise global template	Includes all Project Professional table, macro, and view definitions
View definition	Includes statusing, Project Center, Portfolio Analyzer, and Resource Center view definitions
Category and group settings	Includes settings for all Project Server categories and groups.

Important:
Item-level backup and restore of category and group settings only applies to Project Permission Mode. For more information about security modes in Project Server 2013, see Plan user access in Project Server 2013.

The following procedure allows you to select the Project Server 2013 items you would like to backup. When the procedure is completed, the backup job is immediately sent to the queue for processing. If you would like to schedule a daily backup of these items, this is done through the Daily Backup Schedule settings page. For more information on scheduling daily backups of Project Server 2013 items, see Daily Schedule Backup (Project Server 2013).

To back up items manually

1. In SharePoint Central Administration, click Application Management.
2. On the Application Management page, in the Service Application section, click Manage Service Applications.
3. On the Service Applications page, click the Project Application Service that contains the Project Web App instance for which you want to access the Administrative Backup settings.
4. On the Manage Project Web Apps page, click the drop-down menu for the PWA instance for which you want to access the Administrative Backup settings, and click Manage.
5. On the Project Web App Server Settings page, in the Queue and Database Administration section, click Administrative Backup.
6. In the Select Items section, select the check box next to each project item that you want to back up.
7. Click Backup. A message box will display telling you that the selected items will be queued for backup. Click OK to back up the selected items.

When you backup projects for the first time, all projects are backed up. After the initial project backup, all subsequent project backups will only backup projects that have been updated since the last backup. This ensures that the latest version of the project is backed up for all projects. Note that you can configure the number of versions of a project that you would like to back up through the Project Retention Policy setting that is available in the Daily Schedule Backup page. The Project Retention policy pertains to both scheduled and manual administrative backups of projects. For more information about the Project Retention Policy setting, see Daily Schedule Backup (Project Server 2013).

All Project Server 2013 items backed up through the Administrative Backup page can be restored through the Administrative Restore page. For more information about restoring backed up Project Server 2013 items, see Restore item-level objects through Administrative Restore (Project Server 2013).

https://technet.microsoft.com/en-us/library/dd207304(v=office.15).aspx?tduid=(461cf739fa0e0ce4a9effcd396ccb46c)(256380)(2459594)(TnL5HPStwNw-VD3va83qXh5KtUDVoug_Tg)()

IBM Storwize / Remove all system information

IBM Storwize / Remove all system information

This procedure guides you through the process to completely remove all system information. When the procedure is finished, the system performs like a new installation.

Attention: This procedure makes all the volume data that you have on your system inaccessible. You cannot recover the data. This procedure affects all volumes that are managed by your system, which includes the drives in the control enclosure, in the expansion enclosures, and on the managed disks on external storage systems. The only volumes not affected are image mode volumes on external storage systems.

Do not continue unless you are certain that you want to remove all the volume data and configuration data from your system. This procedure is not used as part of any recovery action.

There are two stages to this procedure. First, the node canisters are reset. Second, the enclosure data is reset.

Procedure

1. Start the service assistant on one of the node canisters.
2. Use the service assistant node action to hold the node in service state.
3. Use the Manage System option to remove the system data from the node.
4. Perform the previous steps on the second node canister in the enclosure and then on every node in every other enclosure in the system.
5. On one node in every enclosure, open the service assistant Configure Enclosure and select the Reset System ID option.
   This action causes the system to reset.
6. Power each enclosure off and on before creating a system.

http://www.ibm.com/support/knowledgecenter/ST3FR7_6.4.1/com.ibm.storwize.v7000.641.doc/tbrd_dltclstr_9090sd.html

NetBackup / image cleanup

/usr/openv/netbackup/bin/admincmd/bpimage -cleanup -allclients

Delete users in Project Server 2013

To delete resources and users

1. On the Project Web App home page, on the Settings menu, click PWA Settings.
2. On the Server Settings page, in the Queue and Database Administration section, click Delete Enterprise Objects.
3. On the Delete Enterprise Objects page, select the Resources and Users option.
4. Select the user or resource that you want to delete.
5. Click Delete.
6. On the confirmation dialog box, click OK.

https://technet.microsoft.com/en-us/library/gg702622.aspx

MS-SQL / SQL Server 2008 Discovery Report

SQL Server Installation Center can be launched from the Start Menu

From SQL setup CD. Generate the Discovery report through the command line. 

from a command promt run “Setup.exe /Action=RunDiscovery” 

The SQL Server Discovery Report is saved to 

%ProgramFiles%\Microsoft SQL Server\100\Setup Bootstrap\Log\

Get-InitiatorPort / HBA information

Windows PowerShell  - Get all initiator ports 

Get-InitiatorPort

Gets all available initiator ports. selects only the NodeAddress and ConnectionType properties, and then displays this information.

Get-InitiatorPort | Select-Object -Property NodeAddress,ConnectionType | Format-Table -AutoSize

https://technet.microsoft.com/en-us/%5Clibrary/hh848671(v=wps.630).aspx

MS-SQL / DBCC CHECKDB

DBCC CHECKDB ('DB_NAME') WITH NO_INFOMSGS;

ALTER DATABASE DB_NAME SET SINGLE_USER WITH ROLLBACK IMMEDIATE;

DBCC CHECKDB ('DB_NAME', REPAIR_REBUILD)

ALTER DATABASE DB_NAME SET MULTI_USER;

Syntax

DBCC CHECKDB     
    [ ( database_name | database_id | 0    
        [ , NOINDEX     
        | , { REPAIR_ALLOW_DATA_LOSS | REPAIR_FAST | REPAIR_REBUILD } ]    
    ) ]    
    [ WITH     
        {    
            [ ALL_ERRORMSGS ]    
            [ , EXTENDED_LOGICAL_CHECKS ]     
            [ , NO_INFOMSGS ]    
            [ , TABLOCK ]    
            [ , ESTIMATEONLY ]    
            [ , { PHYSICAL_ONLY | DATA_PURITY } ]    
            [ , MAXDOP  = number_of_processors ]    
        }    
    ]    
]    

https://msdn.microsoft.com/en-us/library/ms176064(d=printer).aspx

REPAIR_FASTMaintains syntax for backward compatibility only. No repair actions are performed.

REPAIR_REBUILD
Performs repairs that have no possibility of data loss. This can include quick repairs, such as repairing missing rows in non-clustered indexes, and more time-consuming repairs, such as rebuilding an index.

REPAIR_REBUILD does not repair errors involving FILESTREAM data

ALL_ERRORMSGS

Displays all reported errors per object. All error messages are displayed by default. Specifying or omitting this option has no effect. Error messages are sorted by object ID, except for those messages generated from tempdb database.

InSQL Server Management Studio, the maximum number of error messages returned is 1000. When you specify ALL_ERRORMSGS, we recommend that you run the DBCC command by using the sqlcmd utility or by scheduling a SQL Server Agent job to run the command and direct the output to a file. Either of these methods will ensure that running the command once will report all error messages.

EXTENDED_LOGICAL_CHECKSIf the compatibility level is 100 (SQL Server 2008) or higher, performs logical consistency checks on an indexed view, XML indexes, and spatial indexes, where present.

NO_INFOMSGS

Suppresses all informational messages.

TABLOCK
Causes DBCC CHECKDB to obtain locks instead of using an internal database snapshot. This includes a short-term exclusive (X) lock on the database. TABLOCK will cause DBCC CHECKDB to run faster on a database under heavy load, but decreases the concurrency available on the database while DBCC CHECKDB is running.

TABLOCK limits the checks that are performed; DBCC CHECKCATALOG is not run on the database, and Service Broker data is not validated.

ESTIMATEONLY
Displays the estimated amount of tempdb space that is required to run DBCC CHECKDB with all the other specified options. The actual database check is not performed.

PHYSICAL_ONLY
Limits the checking to the integrity of the physical structure of the page and record headers and the allocation consistency of the database. This check is designed to provide a small overhead check of the physical consistency of the database, but it can also detect torn pages, checksum failures, and common hardware failures that can compromise a user's data.

MS-SQL / List of errors and severity level in sql server

SELECT *

FROM master.dbo.sysmessages

WHERE

error=605  -- error message number

AND msglangid = 1033; --language selection

MS-SQL / db index list

USE DB_NAME
GO
SELECT DB_NAME() AS Database_Name
, sc.name AS Schema_Name
, o.name AS Table_Name
, i.name AS Index_Name
, i.type_desc AS Index_Type
FROM sys.indexes i
INNER JOIN sys.objects o ON i.object_id = o.object_id
INNER JOIN sys.schemas sc ON o.schema_id = sc.schema_id
WHERE i.name IS NOT NULL
AND o.type = 'U'
ORDER BY Index_Name, i.type

MS-SQL / How to repair suspect sql db

Suspect olmuş bir veritabanını onarma:

EXEC sp_resetstatus [DB_Name];

ALTER DATABASE [DB_Name] SET EMERGENCY

DBCC checkdb([DB_Name])

ALTER DATABASE [DB_Name] SET SINGLE_USER WITH ROLLBACK IMMEDIATE

DBCC CheckDB ([DB_Name], REPAIR_ALLOW_DATA_LOSS)

ALTER DATABASE [DB_Name] SET MULTI_USER

Outlook / Safe Mode

START > RUN  outlook /safe

Install .NET Framework 3.5 with Windows installation media

Install .NET Framework 3.5 with Windows installation media

You can use the Windows installation media as the file source when you enable the .NET Framework 3.5 feature.

To do this, follow these steps:

• 1.Insert the Windows installation media. 
• 2.At an elevated command prompt, run the following command: 

Dism /online /enable-feature /featurename:NetFx3 /All /Source:<drive>:\sources\sxs /LimitAccess

Note In this command, <drive> is a placeholder for the drive letter for the DVD drive or for the Windows 8 installation media.

For example, you run the following command:

Dism /online /enable-feature /featurename:NetFx3 /All /Source:D:\sources\sxs /LimitAccess

https://support.microsoft.com/en-us/kb/2734782


C:\Windows\system32>Dism /online /enable-feature /featurename:NetFx3 /All /Sourc
e:d:\sources\sxs /LimitAccess

Deployment Image Servicing and Management tool
Version: 6.3.9600.17031

Image Version: 6.3.9600.17031

Enabling feature(s)
[==========================100.0%==========================]
The operation completed successfully.

C:\Windows\system32>

Terminal Server Install Mode

C:\>change user
Change Install Mode.

CHANGE USER {/EXECUTE | /INSTALL | /QUERY}

  /EXECUTE  Enable execute mode (default).
  /INSTALL  Enable install mode.
  /QUERY    Display current settings.

-----------------------------------------------

C:\>change user /install
User session is ready to install applications.

C:\>change user /query
Application INSTALL mode is enabled.

C:\>change user /execute
User session is ready to execute applications.

C:\>change user /query
Application EXECUTE mode is enabled.

How to Change hostname in a VMware vRealize Operations Manager vApp

1. Log into the node as root.
2. Update the hostname by running this command:
   
   $VMWARE_PYTHON_BIN /usr/lib/vmware-vcopssuite/utilities/bin/sethostname.py NewHostName
   Where NewHostName is the hostname you want to use.
   
3. Restart the node.

RSA Envision / Log Arşiv

    net use \\13.13.4.5\Envision2015 /user:domainname\username password

   lsmaint -copy \\13.13.4.5\Envision2015 -time 201501010000 201506302359

   lsmaint -delete -time 201501010000 201506302359

SAN SW log export / supportsave

SAN SW log export

SAN SW loglarını export etmek için supportsave komutunu kullanabiliriz

login as: admin

admin@192.168.6.188's password:

IBM_X32:admin> supportsave

This command collects RASLOG, TRACE, supportShow, core file, FFDC data

and then transfer them to a FTP/SCP/SFTP server or a USB device.

This operation can take several minutes.

NOTE: supportSave will transfer existing trace dump file first, then

automatically generate and transfer latest one. There will be two trace dump

files transferred after this command.

OK to proceed? (yes, y, no, n): [no] yes

Host IP or Host Name: 192.168.9.102

User Name: ftpuser

Password:

Protocol (ftp | scp | sftp): ftp

Remote Directory: /

Saving support information for switch:IBM_X32, module:RAS...

................................................................................     ..

Saving support information for switch:IBM_2498_X24, module:FTRACE_START...

Saving support information for switch:IBM_2498_X24, module:CTRACE_OLD...

Saving support information for switch:IBM_2498_X24, module:CTRACE_OLD_MNT...

Saving support information for switch:IBM_2498_X24, module:CTRACE_NEW...

Saving support information for switch:IBM_2498_X24, module:SSHOW_ISWITCH...

Saving support information for switch:IBM_2498_X24, module:FABRIC...

Using the supportSave command

The supportSave command uses the default switch name to replace the chassis name regardless of whether the chassis name has been changed to a non-factory setting. If Virtual Fabrics is enabled, the supportSave command uses the default switch name for each logical fabric.

1. Connect to the switch and log in using an account with admin permissions.
2. Enter the appropriate supportSave command based on your needs:
   • If you are saving to an FTP or SCP server, use the following command:

     supportSave [-n] [-c] 

     When invoked without operands, this command goes into interactive mode. The following operands are optional:
     -n —Does not prompt for confirmation. This operand is optional; if omitted, you are prompted for confirmation.
     -c —Uses the FTP parameters saved by the supportFtp command. This operand is optional; if omitted, specify the FTP parameters through command line options or interactively. To display the current FTP parameters, run supportFtp (on a dual-CP system, run supportFtp on the active CP).
   • On platforms that support USB devices, you can use your Brocade USB device to save the support files. To use your USB device, use the following command:

     supportsave [-U -d remote_dir]

     -U —Saves support data to an attached USB device. When using this option, a target directory must be specified with the -d option.
     -d remote_dir —Specifies the remote directory to which the file is to be transferred. When saving to a USB device, the remote directory is created in the /support directory of the USB device by default.

Microsoft Outlook 2013 / Disable Items in User Interface

Microsoft Outlook 2013 / Disable Items in User Interface

Outlook imza butonunu disabled etmek 

User Configuration

Policies

Administrative Templates: Policy definitions (ADMX files) retrieved from the central store.

Microsoft Outlook 2013 > Disable Items in User Interface > Custom

Disable command bar buttons and menu items        Enabled  5608

EMC SOFTWARE TOOLS - ESXiGrab

emcgrab.exe uygulaması ile çıktıları almak için aşağıdaki adımları uygulayabiliriz.

• - ESXi sunucu üzerinde yeni kullanıcı oluşturulur.
• - Yeni kullanıcıya admin yetkisi verilir.
• - Aşağıdaki komut çalıştırılarak outputs klasörü içerine .zip dosyasının oluşturulması sağlanır.

emcgrab.exe -host 192.168.9.121 -user newuser -password newuserpassword


E:\EMC-ESXi-GRAB-1.3.7>emcgrab.exe -host 192.168.9.123 -user newuser -password newuserpassword

ESXiGrab
Release Version : 1.3.7
Build Time: 2016-01-17 12:02:43

###############################################################################

                      EMC SOFTWARE TOOLS LICENSE AGREEMENT

                       IMPORTANT -  PLEASE READ CAREFULLY

###############################################################################



DO YOU AGREE TO ACCEPT THE TERMS & CONDITIONS OF THIS LEGAL AGREEMENT (Y/N): y
Please Enter Customer Party Number (Site ID):
Please Enter Customer Company Name:
Please Enter Customer Contact Name:
Please Enter Customer Contact Phone Number:
Please Enter Customer Contact Email Address:
Please Enter Service Request Number:


Command line options: -host 192.168.9.123 -user newuser -password *********

 EMC GRAB IDENTIFICATION INFORMATION
 -----------------------------------
Customer Party Number (Site ID):
Customer Company Name:
Customer Contact Name:
Customer Contact Phone Number:
Customer Contact Email Address:
Service Request Number: 0000000000


Collecting GRAB Data from vSphere
...............................................................................................
PowerPath is either not installed or your installed version of rpowermt is not supported.
PowerPath module will not be run.

Data Collection Started at : Tue Feb 16 07:57:29 VET 2016
Data Collection Finished at : Tue Feb 16 07:57:58 VET 2016

Creating zip file
............................................................................
Cleaning temporary data.......

THANK YOU FOR USING EMCGrab.

E:\EMC-ESXi-GRAB-1.3.7>